I reverted the driver to one dated (in my case 2017) and now the system is as solid as a rock again. The whole connection process became random from start up to running when it would drop at random intervals. Later as in the last few months (cannot remember which update) Windows installed a new driver apparently not bothered which chip set was being used. The problem for me started on an update a couple of years back which refused to work with my cable which unbeknownst to me was a clone chip. The word now is because I have noticed that the latest Windows updates keep changing this driver despite in my case tellng it not to. On Thu, at 15:38, george_fleming2 via groups.io wrote: Can I suggest that you check the dates of the Prolific driver that you are now using. If you have this kind of problem check any messages on your driver and be ready to try previous versions - they should be on your system if you have been running long enough but should be accessible on the internet - look for your chipset drivers or its clones. Thanks in advance to all who may respond.Ĭan I suggest that you check the dates of the Prolific driver that you are now using. Almost as if CDC and EQmod occasionally stopped talking to each other. So I had to switch back to Solar tracking to get it started. I was tracking the sun and EQmod seemed to drop tracking quite a few times. Even then was trying to use EQMod with CDC. So in desperation I turned PC direct mode ( which works). Where / how do I begin to debug / troubleshoot this problem? I would rather do that and be certain that the serial / usb converter is dead before I buy a new unit. A black command window with the cursor in the top left hand corner. I think I was successful as I got a telnet session even though there was no space for me to type anything. In desperation I used Kitty ( putty fork) to connect via telnet. 9600, I had multiple selections in the driver set up dialog. I also noticed that the baud rate drop down in comms statistics had only two speeds. I can see the prolific driver in Devmgmt.msc and it doesn't have any exclamation marks or disabled or anything easy to spot. Due various comments I have seen on the internet I set the com port to 6 (as the default was 4). When I fire up Tools and use Comms statistics and set the com port and baud rate correctly I get the above error. connected to usb 2.0 port via a pluggable usb to serial dongle. On Wed, at 17:41, wrote: So I have a NEQ6 pro. Thanks in advance to all who may respond.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |