Pl2303 Driver Windows 11 64-bit Download

0 views
Skip to first unread message

Rita Seliba

unread,
Aug 4, 2024, 2:11:37 PM8/4/24
to cabarmitigs
See next post]

I bought an Arduino nano clone on ebay. It came with PL2303 instead of FTDI chip. When I plugged it in the usb port, it gets recognized and win 8.1 installed a driver automatically. But the driver can't start.


I can't even find where the pl2303 driver install program unzipped the drivers. A PL2303 driver IS installed after I plugged in the Nano but it shows error messages. The manufacturer specifically says PL2303 HXA is obsolete and has no win8 driver. Have you tried it yourself?


I haven't tried but I have used that way to install some old drivers. I don't think it is a hardware limitation, it might be something like chineses cloned that chip too much that prolific stopped supporting these old versions or something like that.


eried:

I haven't tried but I have used that way to install some old drivers. I don't think it is a hardware limitation, it might be something like chineses cloned that chip too much that prolific stopped supporting these old versions or something like that.


That was in my thoughts too. Make it obsolete. If you have the driver, can you tell me the file name. I just couldn't find where the install program unzipped the driver so I can't specify where to find driver


Not really an argument, when you can't afford to buy everything genuine ... well you just can't _o - pretty much the same thing as saying "another good reason to only buy industrial-grade laser CNC machines / 3D printer / insert really expensive device here".


I am using a Garmin 4 pin to USB all-in-one cable with a Prolific PL2303 driver to connect the Venture to my Mac. The Venture screen shows the unit is charging (electric plug icon). Sending downloaded Geocaching.com pocket queries from my Mac to my Venture works perfectly.


Not familiar with the venture, but I upgraded a etrex using a serial cable with the prolific chipset. I just used the Garmin webupdater, once I registered the device it notified me of an update and installed the firmware.


My guess is that it has something to do with the serial cable. Many people have issues with these types of cables. My recommendation is to pick up a USB cable for your device that has the serial to USB conversion done in the cable itself. I use one like this on my etrex and it works just fine under Windows 7 and OSX.


WebUpdater cannot be used if the Venture won't show up on the desktop. As I mentioned in my post, I have tried 2 different cables - an original PC serial cable and a new USB cable with Prolific chipset. The Venture refuses to show up on the desktop of any PC or Mac. Appreciate the feedback nevertheless.


My recommendation is to pick up a USB cable for your device that has the serial to USB conversion done in the cable itself. I use one like this on my etrex and it works just fine under Windows 7 and OSX.


I purchased exactly the same sort of cable last month. The eTrex Venture charges OK (as I mentioned in my post), and I can sent PQ's to it, so I know the cable works. But it doesn't enable the Venture to show up on the desktop on a PC or a Mac, so WebUpdater can't be used. Perhaps it's a flaw in this old Garmin model.


Oh, BTW: WebUpdater for Mac is not compatible with Palm, Pocket PC, serial, fixed-mount marine, chartplotters, fishfinders and some discontinued devices. So you don't have to bother trying to update on a Macintosh system.


The standalone firmware.exe file will not install using any PC I've tried whether via serial or USB. Again, the device will not show up on the desktop or be recognized, which is a requirement to install.


You say "My eTrex has never shown up on the desktop on Windows or Mac and webupdater works fine. Where are you getting that from?" I'm baffled - what model eTrex? And how are you updating firmware (if at all)? PC? Mac? Serial? USB?


To sum up, I down load a PQ, import it into MacCaching, then send it via the above cable to my old green eTrex Venture (or I can select single caches to send). They show up correctly as waypoints on the Venture. This saves a lot of manual entry. At the same time as this cable is connected, the battery icon on the Venture display is replaced by a power plug icon. As a result, I do not think this cable is faulty. The charging icon also shows when this cable is connected to a PC.


I'm also wondering about the USB-Serial cable.. 1st of all, what version of Windows are you running? Windows Vista, and up (and I imagine the 64-Bit version of XP) do not use the standard 32-bit Prolific chip driver. You'll have to search for the 64-bit driver. I ran into this when I tried feeding my old serial equipment (Robots, GPS's, other devices) to Vista (and later Win-7) .. Ironic, there is a universal driver set-up for the parallax Basic Stamp MCU, which uses standard serial (yes, even their USB version of the B-O-E has a prolific chip on it.)


Despite the varied suggestions and feedback (which are very much appreciated ) I think it's best to wait until someone who actually owns or uses a Venture responds to the two questions posed in my original post:


In one of those amazing million-to-one co-incidences out here in rural Australia, last week I bumped into another geocacher who was using exactly the same model. I told him my story, gave him the info, he went home (several hundred km away) and updated his Venture successfully.


Dear visitor, we have detected that you are using an ad blocker. We want to remind you that this website is supported by advertising, which allows us to offer you our content for free. Please consider disabling your ad blocker to support us and continue enjoying our content. Thank you for your understanding!


- I recently had a query regarding the ELM327 in its USB version. That person did not get the computer to recognize the ELM327 device, his computer has a windows 10 64 bit installed. Fortunately I have at my disposal 3 computers with Windows 7 and 2 with Windows 10.I started testing on my usual computer and where I had already used these ELM327 devices without problems. To my surprise, out of 10 I tried none worked. In all cases, in the device manager, a yellow error signal appeared on the COM port where the device was connected.


- As always I hope that Windows give me some useful information about the problem. So went to check the error code and cause message. And as always I stay as I was before reading that information. It simply informs me that a non-existent device has been specified, indicating error code 10.


- Immediately tested the same devices on the other computer with Windows 10, with the same result. After testing every one on the computers with Windows 7 installed and checking that they all worked perfectly I came to the conclusion that it was due to a compatibility problem with the operating system. After searching for information on the internet about it and reading lots of tips indicating downloading the latest version (without result), disabling some specific devices in the device manager (without result) and the like, I came to the conclusion that I had to start from the beginning.


- The first thing would be to find out what chip for the USB communication had built-in these ELM327 USB. After dismounting one of them and see the inscription PL-2303HX on the serial communication chip, I went to the manufacturer's page where I found the following driver information for this chip. They indicate that it works for PL2303 HXA, XA, HXD, EA, RA, SA, TA and TB chips, with the important caveat that it does not work for Windows 8, 8.1 and 10 for the PL-2303HXA and PL-2303X versions that are EOL (End Of Life). What comes to say more or less they are no longer manufactured and have been left to give support in the latest driver versions.


- As the inscription of the chip is PL-2303HX now had to know if it is the HXA (without support) or the version HXD (new version that does have support). In the chip itself, after that inscription appears another one of the following style LFXXXXXA, where the X are numbers from 0 to 9. This code identifies the revision of the chip and the last letter, A in this case, indicates that it is the Chip PL-2303HXA. Just the one that has been left without support for windows 8, 8.1 and 10 in the latest versions of the driver.


- The possible solution was now to find an earlier driver that would support the PL-2303HXA. After much searching I found an old version for Windows Vista (version 3.2.0.0) and that, theoretically, could support the version of the chip of these devices. Also in both versions, 32bit and 64bit. You can download them below, in the download section.

3a8082e126
Reply all
Reply to author
Forward
0 new messages