![Fix prolific usb to serial comm port for win 10](https://knopkazmeya.com/17.png)
![prolific usb to serial comm port com5 fix prolific usb to serial comm port com5 fix](http://www.esp8266basic.com/uploads/1/2/6/2/12629375/s959248005716299134_p14_i1_w500.jpeg)
- #PROLIFIC USB TO SERIAL COMM PORT COM5 FIX UPDATE#
- #PROLIFIC USB TO SERIAL COMM PORT COM5 FIX DRIVER#
- #PROLIFIC USB TO SERIAL COMM PORT COM5 FIX WINDOWS 8.1#
- #PROLIFIC USB TO SERIAL COMM PORT COM5 FIX CODE#
![prolific usb to serial comm port com5 fix prolific usb to serial comm port com5 fix](https://cdn.adlinktech.com/webupd/products/images/1087/USB-1901_1902_1903_ProductImage_en_20170116_v1.jpg)
The needed bias for a USB to RS232 chip will vary a bit with data patterns and the load on the 5v USB power signal. Dropping all power is usually the only solution once the back-bias occurs.Įdit PS: See the following article for more information. If the charge pump cannot keep the substrate biased enough to prevent the +/- 3-15 volt RS232 signal from back-biasing the signalling inputs, the chip will just lock up due to self sustaining parasitic currents. My top of the head guess as to an answer to your great question would be the problem may be an under-performing charge pump for the generation of substrate bias on the chip. While it all works fine with FTDI, my curiosity just can't let the problem go! What in the world are they doing with that serial port to make the plain 9600 bps no-handshake command-response communication stall?ītw, many thanks for creating MetaGuide! What an awesome app!
#PROLIFIC USB TO SERIAL COMM PORT COM5 FIX CODE#
I looked at the ASCOM source code for their serial port wrapper, and while it looks a bit over-engineered, there is nothing obviously wrong with it. It is just NexRemote and the ASCOM serial port helper which must be doing something. Particularly puzzling is the fact that the physical-level link must be working fine as both CFM and NSOL can communicate over it. This is the first time I ran into an adapter-specific problem. I have used (and programmed against) these particular Prolific adapters for the last 10+ years for all kinds of projects without any issues whatsoever. Also the Hand Controller is then left in a state where it is no longer responding to new commands over the serial link. Looking at ASCOM serial port traces, the port just stops taking in any more incoming bytes (or possibly the HC stops sending any more?) after the first few (or the first few dozen). I recommend joining TeamCelestron and asking there.
![prolific usb to serial comm port com5 fix prolific usb to serial comm port com5 fix](https://cdn.cnetcontent.com/5f/65/5f65f089-7864-409f-bfd2-ad10a81f4605.jpg)
So I'm not sure what problem you are hitting. Some people prefer "true" prolific adapters - but I had best luck with keyspan. I have used a number of celestron mounts with a number of USB-Com adapters and they all worked - but some might be less reliable than others.
#PROLIFIC USB TO SERIAL COMM PORT COM5 FIX WINDOWS 8.1#
NexRemote was tested on Windows 8.1 as well. The built-in “real” COM port on the desktop also worked fine for ASCOM. Communication fails on both so it is not even computer-specific. I tested Prolific adapter on Windows 8.1 both with a laptop and with a desktop computer against AVX mount. I gave up and simply spent $15 on FTDI adapter…
#PROLIFIC USB TO SERIAL COMM PORT COM5 FIX DRIVER#
I made an honest attempt to locate the corresponding source code hoping to fix it, but the current Celestron driver source is not available publicly, and ASCOM platform was just too heavy and cumbersome for a quick testing of the potential fix. All tools and apps seem to work fine with FTDI-based adapters. I find this kind of lame that in the year 2018 they somehow still managed to make the plain vanilla 9600 bps communication over a serial link adapter-depend.
#PROLIFIC USB TO SERIAL COMM PORT COM5 FIX UPDATE#
What makes this particularly bad is that both Celestron Firmware update manager (CFM) and the well-known "NexStar Observer List" tool work fine with Prolific adapters! Oh, and talking to NexStar controller from any Terminal program also works fine using Prolific. I will post it here so the info comes out in Google search results and this will hopefully save someone many hours of frustration…ĪSCOM Celestron driver does NOT work with USB-COM adapters using Prolific chipset!Ĭelestron NexRemote does NOT work with USB-COM adapters using Prolific chipset!
![Fix prolific usb to serial comm port for win 10](https://knopkazmeya.com/17.png)