krirona quynesha cristabele
Wynellewe Gr
I have a few handheld radios that I need to update the frequencies and when I connect to the USB, it fails to connect. In device manager and Ports it says - "Please install corresponding PL2303 driver to support Windows 11 and further OS"
Hello! You've posted your question in the Tech Community Discussion space, which is intended for discussion around the Tech Community website itself, not product questions. I'm moving your question to the Windows 11 space - please post Windows 11 questions here in the future.
Windows 11 update loaded Prolific PL2303 driver 3.8.40.0 and when I go to device manager it says "Please install corresponding PL2303 driver to support Windows 11 and further OS" This driver does not even attempt to communicate with my X10 CM11 hooked to my serial port. I had to go to Prolific website and load their current driver 3.6.81.357. (uninstall driver first) Serial to X10 device now working fine. Don't install Windows update for Prolific or it will change it back.
This should resolve the issues with the serial adapter not being detected after the first connection is closed as well as an issue with multiple serial adapters on the same computer. We have seen issues with cu and screen locking up with macOS Mojave and Catalina that are unrelated to the serial adapter driver and it appears to be a problem with some of the serial connection software. The lock ups were verified without the serial adapter driver installed on the system. Additionally Catalina includes built-in support for this adapter and the separate driver is no longer needed when upgrading to Catalina ( 10.15.3 ).
I have tried the installer that you linked and it is not solving the issue. I have installed, and from the installer done a complete uninstall/reboot, then install, then insert the device.. Every time the driver that is installed is ver 3.9.1.0. There is no option to roll back any further. The device continues to not function, and in the device manager the heading only reads "PL2032TA DO NOT SUPPORT WINDOWS 11 OR LATER, PLEASE CONTACT YOUR SUPPLIER".
I've read through this whole thread (and a few others) and everyone is saying to go get the driver from the prolific site, although I think that's now been taken down, as every link takes me back to the site index. If I search on their site for drivers, I can go to the info page/brochure for the pl2303, but if I even click their own link to the drivers page it takes me back to the site index. I've also tried using a VPN to pretend being in the US, as I'm in the UK, no luck!
I had similar problems with PL2303 issues (Prolific USB to Serial Drivers) Windows 11 for communicating with the CELESTRON NEXSTAR+ & STARSENSE HAND CONTROLLERS. Standard USB-A PORTS on computers did not recognize the drivers and were unable to establish a connection using for connecting the USB-A to USB-B Mini Lead to the HAND CONTROLLERS.
The PL2303 v408 Driver for Windows 11 problem was immediately solved when I attached a USB-C Adaptor with USB-A Ports to the same computer and connection of the same lead to the CELESTRON NEXSTAR+ & STARSENSE HAND CONTROLLERS. The USB-C Adaptor & USB-A Ports were immediately recognized by the Drivers and allowed perfect communication.
Excellent advice. I turned your instructions into a PowerShell snippet with makes this procedure pretty quick. Just set the path to the driver files.
Attached is a screenshot of my Device Manager with 2 programming cables plugged in. (1 Yaesu, 1 Baofeng).
People have been reporting all sorts of trouble with these. And Prolific has stated they intend to send out a 'bug' to wreck the imitation copies of the 2303's that were pouring out of China. So one needs to beware of your source when pouring one into your computer. So I'm hoping I can attach the real thing below - or at try:
This is freeware. Prolific isn't mad because "freebies" out of China are circulating. They just don't want to be held liable if a counterfeit turns someone's mount & $16,000 telescope turn into a Whirling-Dervish and throw their scope across the county!
I'm running the Anniversary edition of Windows 10 on my laptop. After the update, the yellow exclamation mark appeared next to the USB device as expected. I disabled auto updates, deleted the new Prolific driver, selected the old Prolific driver (rather than performing a rollback) then re-enabled auto updates. So far Windows has not overwritten the old driver after several reboots.
I too had Prolific driver issues when I updated from Win7 to Win10, but at the moment everything is working consistently. I will probably invest in an FDTI-type EQDirect cable in the future. Has anyone considered making their own? I was looking at this: -online.com/web/p/products/6877828/. The EQMOD website has all the wiring details for the each mount connector. And half the price...
I swapped over to the FTDI solution a wee while ago after having connections go south in the middle of a carefully prepared imaging run. Got a Keyspan USB-Serial adapter (recommended by Astro Physics) and also Astronomiser EQMod FTDI cable. Not had one drop out since with either. Save the frustration and switch over.
What are we actually saying here - that any Prolific based usb/serial adapter are no longer fit for purpose? I'm struggling to get mine working at the moment, even reverted to running XP, and agree entirely with those comments above that it is a real pain. Win 10 really is turning out to be a complete farce, first my canon laser printer no longer works now this mess. Sombody, somewhere is making a lot of money over this.
Just to add to my little rant above - I've been trying all weekend to get EQMOD talking to my mount via a EQDir (Hitecastro). I had no luck with Win 10, even with the fixes described above. I've now swapped out to another pc running xp and still no luck. If the chip set is a counterfeit would that prevent it working even with any of the older (pre win 10) drivers or it it likely that my problem lies elsewhere in my system? I'm about to go down the DTDI cable route but I could do without spending any more money on yet another cable, winter is coming in and the children like the home warm!!! Wonder if I can burn an EQDir cable
I have used Prolific for a fair while and after lots of drop outs, win 10 issues, etc, switched. Everyone's mileage is different here, but for me the cash has been well spent switching. If Prolific is working great - if it's unreliable you spend lots of time chasing your tail.
Nice one Billy for sharing this link I have had to set my device installation settings (were it asks do you want to automatically download apps and device settings) to no. This link solved that so I can now turn that back to yes
Paul, I'm having no joy with the cable I made and I wonder if you could just confirm a few points in case I've missed something important. I used a TTL232R supplied by RS online - (the 3v variant). I spliced the TTL232R to a cat 5 patch cable as per the instructions on the eqmod sourgeforge document :
I confirmed the integrity of the splice connection using the Mitty app which confirmed the Tx and Rx lines were fine. However when connected to Eqmod via CDC I'm still getting Eqmod not recognising the com port despite Com 4 being identified by Device Manager. I've installed ASCOM and Eqmod but still the same and there is no driver conflict shown. I'm wondering if the 3v variant of the TTL232R just can't be recognised by the mount despite the advice in the Eqmod document. Alternatively, would there be any reason for a virtual com port to cause Eqmod any problems - I know little about com ports to be honest.
Just to make things even more interesting, I thought I would take a closer look at my HITEC Astro Eqdir - the wiring to the RJ45 plug does not conform to that shown on the Eqmod doc! I'll post up a photograph latter but the wires are connected to pins 5, 6 and 7. Anybody have any ideas why this should be different?
Yes the correct drivers are installed, current build of ASCOM/Eqmod and Cdc - all checks out ok until I try to talk to the mount - cdc controlling. Really a bit annoying this one, I'm at the stage where I'm considering a reinstall of Win 10. The irony is that I had Eqmod happily controlling my DIY mount via AstroEq last year before I upgraded to my current mount. Win 10, so much for plug and play - more like plug and pray
c01484d022