Prolific Usb To Serial Driver Windows 10 Old Version
Gualtar Pennington
I have successfully downloaded programs to 8 systems using laptop (Lenovo 510) running windows10 and visilogix 9.8.65. I installed drivers once only. No problems after that. [ note: V130 cable is USB to serial port adapter + mj10-22-cs25 + modem cable to port 1 on V130.]
HOWEVER-Yesterday went to site with same laptop and same cables to download . No luck ! We ended up with errors on both the V130 and V1210. Both had unsuccessful downloads.
Yes, this is almost certainly a Windows 10 updating issue. Do these PLCs have Ethernet cards installed? If so, you might consider doing all the updating by Ethernet. I do this routinely and generally recommend an Ethernet card as part of the system integration.
However, I had problems with the USB to COM driver once due to interference from the computer's power supply.
It was powered from a different power than the machine to which it was connected.
Disconnecting the power supply from the mains and running on batteries solved the problem in this case.
On Joe's comment about the programming computers, I also have some systems that are complete standalone dedicated for a particular job. They are not connected to anything, hence have no security risks. But they are the only way I can get some older things to work properly, now that "modern" thinking has over-ridden perfectly good stuff.
I use a MacBook Air since day one. Installed parallels desktop and running windows 7 on the virtual machine. The windows 7 is set up with no internet connection. Runs without ANY glitches. Check my emails and web on the Mac side, do the plc stuff on the windows side. The battery lasts 7-8 hours, it is way more durable than most pc (hard aluminum shell) weights 2.2lbs. I use it in a very dusty environment. The best setup in my opinion.
@azzido no problem, windows 11 always updates drivers if newer cones out if the software don't see the programer it's easy just removed the recent update driver by windows 11 and all will work perfect. The drivers I provide are from the pl2303 maker so the latest for Windows 11 and 10. Regards
For reference, I attache the 2 drivers that work for me to this message. Only one is needed, just that they have different install methods (one is .exe and the other is right click on the INF), if you run the .exe version and you already have another version of the driver it will ask you if you want to uninstall (which I usually do) and then run again the .exe to install the driver.
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
Cheers Paul, I think I'll bite the bullet and place an order for a commercial FTDI based cable. I'll wait and see what that throws up before I go through the motions of reinstalling Win 10, like you say it would be easier. I really don't want to have to reinstall everything I have on the laptop at the moment. I'm starting to fear the worst though - dare I start to suspect my mount! Having said that it works fine with the handset.
c80f0f1006