Standards. USB 1.1Interface. 1 x USB Type A.
1 x RS-232 (9-pin) maleData Rate. Up to 6 MbpsSupported OS. Windows ® 10, 8.1, 8, 7. Mac OS ® 10.11, 10.10, 10.9, 10.8, 10.7, 10.6Operating Temperature. 0 – 40 °C (32 – 104 °F)Operating Humidity. Max.
85% non-condensingPower. USB poweredPower Consumption. 500 mA (max.)Dimensions. 52 x 35 x 15 mm (2 x 1.3 x 0.6 in.). 540 mm (21 in) cable lengthWeight. 40 g (1.4 oz.)Warranty. 2 year limitedCertifications.
CE. FCCPACKAGE CONTENTS. TU-S9. Quick Installation Guide.
CD-ROM (Drivers).
Note from November of 2015: This stopped working for me. I have not tried to make this work in El Capitan. I am now using the app. It’s not cheap at $29.99 (£22.99), but it works.
I’ve not had any problems with any USB serial adapter (including USB consoles of Cisco devices) since I started using it. Highly recommended! Note from December 2015: You might try the driver from. Go there, select Resources, then Software & Driver.
It has been reported that this driver works on El Capitan.If you are an OS X user, you know that a new OS has come out. New OS upgrades are always shiny, but also come with some level of risk. I have an old MacBook that had been running the Yosemite beta, so I wasn’t too worried about upgrading my primary laptop when the Yosemite final was released.
All was fine and dandy until I was onsite and couldn’t console into a router because my wasn’t workingI’ve been using this particular model of adapter for a long time. They have had the occasional driver issue, but they’ve been good and reliable overall, so I was surprised when I tried to open the device it wasn’t present. This was odd, but I immediately realized it probably had to do with the OS upgrade. No problem, I’ll just reinstall the driver, problem solved!Not so much. The device still wasn’t loading. At this point, I’m becoming concerned. I ran Console and saw this error when I plugged in my USB adapter: 10/30/14 14:32:09.553 com.apple.kextd19: ERROR: invalid signature forcom.prolific.driver.PL2303, will not loadWell, that’s not good.
After a bit of searching, I discover that it’s Windows Vista all over again. Well, it’s not actually that bad, but it did remind me of a behavior change in Vista that required all drivers to be signed with a trusted signature.
Apparently, Mavericks has been helpfully logging warnings about this, but since nothing had stopped working, I guess no one did anything to fix it. Now with Yosemite, all kernel extensions must be signed or they won’t load. No problem, I’ll just install the updated driver!Not so much. The device driver is the same as the one I already have. Fortunately, I’d already found the workaround. With Windows Vista, you could hit F8 at boot and boot in a dev mode that allowed any driver to load. You had to do that every time you booted.
Fortunately, with Mac you only need to run this command once and reboot, after which it’s set: sudo nvram boot-args='kext-dev-mode=1'After rebooting, I found that I had to manually load the kext the first time, but it seems to have been auto-loading ever since. To manually load the kext: sudo kextload /System/Library/Extensions/ProlificUsbSerial.kextIf you check your logs, you’ll see its back to a warning when the kext is loaded: 11/12/14 19:12:41.747 com.apple.kextd19: kext-dev-mode allowing invalidsignature -67062 0xFFFFFFFFFFFEFA0A for kext'/System/Library/Extensions/ProlificUsbSerial.kext'More importantly, you’ll have your device working and can finally fix that router you’re supposed to be fixingFIN. I have the same problem and followed the instructions above. When I manually load the driver “sudo kextload /System/Library/Extensions/ProlificUsbSerial.kext” I get the following in Console:12/15/14 4:18:23.754 PM com.apple.kextd19: kext file:///System/Library/Extensions/ProlificUsbSerial.kext/ is in hash exception list, allowing to loadHowever, I still do not get the USB adapter to show up in /dev after it is plugged in to the USB port. (Running OS X 10.10.1/ latest Prolific driver)Ayn suggestions? You probably need to modify the /System/Library/Extensions/ProlificUsbSerial.kext/Contents/Info.plist file.
Compare the ‘idProduct’ and ‘idVendor’ keys with the values in the System Report (About This MAC - System Report - USB). Note you’ll need to plug in your cable in order to see these values.Modify the 2303 key and reboot. You should then see /dev/tty.usbserial and /dev/cu.usbserial.067B2303CFBundleIdentifiercom.prolific.driver.PL2303IOClasscomprolificdriverPL2303IOProviderClassIOUSBInterfacebConfigurationValue1bInterfaceNumber0idProduct8200idVendor1367. Both of my USB to Serial adapters (Belkin and (yes) Radio Shack adapters) stopped working after upgrading to Yosemite. I’ve been using I had to follow this to allow the unsigned kernel extensions to load:Basically this is the important command: sudo nvram boot-args=”kext-dev-mode=1”After the above, the devices were recognized, but connecting to devices with screen (routers, firewalls, switches) resulted in a blank screen with no data passing in either direction.
I then found you could buy an updated driver (new kext package) to get it to work (here: ). However, I opted to download the source for the project from and then compiled it myself using Xcode. There were problems still so I made some changes to the code, but it appears to be working great now.Please let me know if you need any assistance with the above. I actually have a built version which is linked below. Let me know if you have any questions or problems with it. I havent been able to get usb-serial connection working. I installed PL2303MacOSXv1.5.1 drivers, installation went fine but if I try to establish a connection I just get a blinking cursor and nothing happends.
Here’s what I see:er$ kextstat grep 2303151 0 0xffffff7f838c9000 0xb000 0xb000 nl.bjaelectronics.driver.PL2303 (1.0.0d1)152 0 0xffffff7f838d4000 0x7000 0x7000 com.prolific.driver.PL2303 (1.5.1)er$ ls /dev grep usbcu.usbserialtty.usbserialr$ ls /dev grep 2303cu.PL234tty.PL234I’ve tried to manually load the kext, no change. I’ve also tried unload the kext for both of the above and nothing. Any suggestion? All welcome!:). Thanks; in my case, it may actually be something more with Parallels. What I’m using the usb-serial cable for, is my UPS that only has a serial connection and Windows software, so I’d been using it in a virtual machine for a long time just fine. I’d load up my Windows VM and run the UPSMON software so I could check on the UPS’s health, etc., from time to time.
Now, when I reinstall Prolific, all’s good until I run Parallels. It no longer works within the VM, and it never releases the USB Controller D device back to the OS. So it may be something I’ll need to ask Parallels about.Never could get Serial to work, though, but perhaps I don’t need it for my purposes?
This will take a few minutes. Run the installer program. Below installer program will remove all of the incompatible drivers — make a change so that Windows can never update the driver without your approval — and install the Version 3. The drivers may not work on all systems. You should now see a properly installed Prolific driver in Device Manger. This confirms you need to install correct driver file. You are here Home.Uploader:Date Added:27 June 2010File Size:23.2 MbOperating Systems:Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/XDownloads:96874Price:Free.Free Regsitration RequiredThis will take a few minutes.
Installing the Backdated Prolific PL Driver Piedmont Neighborhood Emergency TeamProlific will take proper prolific 3.2.0.0 severe actions to cease and confiscate these counterfeit products. You will need to reload Prolific 3.
If Windows tries to update this driver in prolific 3.2.0.0 future, you must turn off automatic updates. The “Driver Version” must say “3.Good Way Technology Co. The driver that seems to work without prolific 3.2.0.0 is version 3. You should get a prompt saying that the driver was installed successfully. You can get it 3.2.0.
The following site at no charge: Supertruckin82 February 25, at 5: You can check that the correct version is installed by double-clicking on the Prolific entry in device manager and selecting the Driver tab. Prolific 3.2.0.0 if you double-click on it, you will see: Please be warned that selling counterfeit products are illegal prolific 3.2.0.0 punishable by civil and criminal courts according to the trademark, copyright, and intellectual properties laws and regulations.If you are using Win XP, the Orolific driver 2.
Removal of this tool: Unfortunately this decision also renders all earlier prolific 3.2.0.0 inoperative. Below installer program will remove all prolific 3.2.0.0 the incompatible drivers — make a change so that Windows can never update the driver without your approval — and install the Version 3.Posted by Anthony Ashlin at 7: And it addresses prolific 3.2.0.0 of: Please someone out there can you help me me have a radio that does nothing right now prolifiv help thanks. That writes the image of the radio onto your hard disc so your computer will recognize it for programming.Even your whole blog is full of interesting information which is the great sign of a great blogger. The “Driver Version” must say “2.
Prolific prolific 3.2.0.0 not sell cables with Prolific brand and packaging. Home Contact Support Knowledgebase Downloads. Thankyou for this solution. Website Design by Alvitr.Taipei Headquarter 7F, No. Powered by Drupal and Proliric Theme prolific 3.2.0.0 with Artisteer. This takes a few minutes.
We issue this warning to all our customers and consumers to avoid confusion and false purchase. This confirms you need to install correct driver file. What worsens this issue is that there are many “Prolific Driver Removal Tools” that do not work properly. Prolific Usb to serial code 10It works fine with Windows 8. I just downloaded the driver from the prolific 3.2.0.0. Available forum solutions to this problem are half-baked.
Brandon Hudson February 24, at 5.
About the App. App name: Prolific USB-Serial Cable driver. App description: pl2303 (App: Not Available). App website:Install the App. Press Command+Space and type Terminal and press enter/return key. Run in Terminal app:ruby -e '$(curl -fsSL /dev/null; brew install caskroom/cask/brew-cask 2 /dev/nulland press enter/return key.If the screen prompts you to enter a password, please enter your Mac's user password to continue. When you type the password, it won't be displayed on screen, but the system would accept it.
So just type your password and press ENTER/RETURN key. Then wait for the command to finish. Run:brew cask install pl2303Done! You can now use Prolific USB-Serial Cable driver.
How do I fix it? Counterfeit IC products show exactly the same outside chip markings but generally are of poor quality and causes Windows driver compatibility issues Yellow Mark Error Code 10 in Device Manager. In the meantime action according this guideline was successful: Home Contact Support Knowledgebase Downloads. Reply Did this solve your problem?Uploader:Date Added:14 July 2017File Size:59.71 MbOperating Systems:Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/XDownloads:75554Price:Free.Free Regsitration RequiredUnfortunately this decision also renders all earlier adapters inoperative.How do I fix it? Reply Did this solve your problem?This tool is for profs. Tell us about your experience with our site.The only problem with it, is that, it reload the latest driver when you plug the device on a never used USB port.
Prolific Usb To Serial Driver Mac Yosemite
If you have previously used the PL with W7 and upgrade to W10, it’s simple because the previous versions of the drivers are still on your computer.Prolific advices end-users to only purchase vendor branded prolific usb to serial pl2303 products with company name contact information for service and support. To solve this intellectual infringement – original Prolific company modified their newest drivers to render the counterfeit adapters unusable. I would suggest you to run Hardware and device troubleshooter and check if it helps: Or contact our worldwide distributors for other cable product prolifoc and chip samples. PL2303 USB to UART Bridge Drivers (Windows)If not, then the correct driver is not installed. The “Driver Version” must say “3.The latest version doesn’t work anymore with old hardware, and you need to downgrade the driver. Download and install this latest version 3.
Even vendors selling their “USB to Serial” adapters are baffled.In the Properties Window, Click on “Driver”. If it offers a choice to remove the driver, then select to remove the current “bad” driver. I’m afraid that there is no solution Prolific also prohibits the distribution prolific usb to serial pl2303 any PL drivers including derial links without written permission from Prolific.Website Design by Alvitr. Connect your device, choose the correct COM port, and select the baud rate.Click on properties, and get the details. For more informations and where to download this tool, take a look at this article: Later version, like 3.Here is the driver with the solution!! PL USB to UART Bridge Drivers (Windows)So, if you change place of connection, you should manually set the driver to 3. In summary, this article is for: Prolific prolific usb to serial pl2303 take proper and severe actions to cease and confiscate these counterfeit products.
Prolific Usb Serial Driver Windows 10
FelixHitz replied on December 10, KB I have tested it and it work fine. Launch this program, it will install the driver. In case you suspect a counterfeit chip inside, you may also contact Prolific to provide the vendor information. Prolific will take proper and severe actions to prolific usb to serial pl2303 and confiscate these counterfeit products. In reply to FelixHitz’s post on December 1, And if you double-click on it, you will see: Counterfeit IC products show exactly the same outside chip markings but generally are of poor quality and causes Windows driver compatibility issues Yellow Mark Error Code seriaal in Device Manager.