49 replies to this topic

[Jade B]

Hey everyone! As the title states, I'm having issues connecting my mount to my computer. I have a Celestron 127 SLT with a cable that runs from the hand controller to a USB port in my computer.

 

I have been struggling for the longest time trying to connect my mount to any of my telescope control software, be it NINA or CPWI... When my cable is plugged into my computer, "Prolific USB-to-Serial Comm Port (COM5)" appears with a warning "This device cannot start. (Code 10)" under my ports in device manager.

First off, is this the correct driver for my Celestron mount?

 

I've tried uninstalling the prolific driver (Prolific PL2303 driver v3.3.2.102 (2008-24-09) Win8_x64_x86). Reinstall. Restart pc. No fix.

On another note, when I try to replug the USB into my computer, I now have a "Unknown USB Device (Device Descriptor Request failed)" with a "Windows has stopped this device because it has reported problems. (Code 43)" under my USBs in device manager.

 

I have no idea what's going on.

 

I have run CFM and did the connection test with my hand controller. I got a "CFM was unable to find a device." but it did show that all of my packages were successfully downloaded with no update activity.

 

Any help would be greatly appreciated.  

[mlord]

My older rev. USB Nexstar+ hand-controller successfully connected/working with MS-Windows-10:

 

 

Note the version number of the Prolific device driver.

Edited by mlord, 11 June 2024 - 09:28 AM.

[mlord]

So that was on Win10, driver version 3.8.42.0.

 

I do have a Win11pro machine here which also works fine.  The Prolific driver there was installed directly from Windows Update, and is at version 3.9.5.0 (working).

 

But I do notice there's an update pending for that from Windows Update.  So.. will install the update shortly and verify that all is still well.

 

All of those are far newer than the clunker reported on the malfunctioning setup; 3.3.2.102

 

Cheers

Edited by mlord, 11 June 2024 - 09:24 AM.

[mlord]

Here is my Win11-Pro box, completely up-to-date as of a few minutes ago (working fine, too!):

 

 

Driver version 5.2.6.2 for the PL2303GL chip in a recent revision Nexstar+ hand-controller.  This is the same revision that the original poster seems to have, so it's just a matter of installing a newer device driver from Windows Update to make it work like mine.

Edited by mlord, 11 June 2024 - 09:29 AM.

[Xeroid]

mlord,

 

Bravo!

 

Very kind of you to take the time to help the OP,  your screen shots of the driver versions will probably help several other CN users.

 

Way to go!

Edited by Xeroid, 11 June 2024 - 10:20 AM.

[Jade B]

My older rev. USB Nexstar+ hand-controller successfully connected/working with MS-Windows-10:

 

prolific.jpg

 

Note the version number of the Prolific device driver.

Hey! Thanks so much for your comment and your screenshots. Appreciate it.

Just to clarify, you are suggesting for me to install the newer version (5.2.6.2) of my existing driver (PL2303GL)? 

I'm checking the driver website rn (https://www.prolific...id=223&pcid=126), and I however only see the download link for a v4.0.1 

Edited by Jade B, 11 June 2024 - 12:14 PM.

[mlord]

I'm pretty sure I just used Windows Update to find/install the drivers on the Win11-pro machine.  So check in Windows Update, or do "Update Driver" from Device Manger and let it search Windows Update.

 

If that all fails, then just download/install whatever the latest version is from Prolific.

[mlord]

The Prolific site itself says to just use Windows Update for Win11 at least.  I don't think you've ever volunteered information here about which Windows version you are running.

 

 

Windows 11 ( 64-bit ) WDF WHQL Driver: v3.9.1.0 (08/11/2021) / v5.2.2.0 (12/03/2021)

(For PL2303 HXD, SA, RA GC, GS, GT, GL, GE , GD, GR versions)
  - Windows 11  Certified WHQL Driver ( 21H2 versions)
   - Auto-download driver via Windows Update (Windows 11)

Edited by mlord, 11 June 2024 - 12:20 PM.

[Jade B]

The Prolific site itself says to just use Windows Update for Win11 at least.  I don't think you've ever volunteered information here about which Windows version you are running.

 

 

Windows 11 ( 64-bit ) WDF WHQL Driver: v3.9.1.0 (08/11/2021) / v5.2.2.0 (12/03/2021)

(For PL2303 HXD, SA, RA GC, GS, GT, GL, GE , GD, GR versions)
  - Windows 11  Certified WHQL Driver ( 21H2 versions)
   - Auto-download driver via Windows Update (Windows 11)

I run a Win11. 

I've tried updating the driver via the windows update, but it didn't work. Let me try to reinstall the latest driver from the Prolific site. Will update here how it goes.

[Jade B]

Alright I'm still facing the issue.

What I've done:
> Install the latest version of the driver from Prolific
> Unzip, uninstalled the current one, restarted PC
> My device manager is still giving me that Code 10 issue.
> Updated driver via windows update, still doesn't work. Windows says I'm up to date.

Edited by Jade B, 12 June 2024 - 05:29 AM.

[Jade B]

I also get this.

Attached Thumbnails

• 

[mlord]

Uninstall everything you downloaded from Prolific themselves, and unplug the USB cable.

Now plug the cable back in.  MS-Windows should offer to search for a driver.  If not, go into device manager and trigger the search from there, telling it to use Windows Update.

 

I never had to download a separate driver from Prolific's site -- Windows Update installed it for me originally, and now keeps it up to date.

[Jade B]

Uninstall everything you downloaded from Prolific themselves, and unplug the USB cable.

Now plug the cable back in.  MS-Windows should offer to search for a driver.  If not, go into device manager and trigger the search from there, telling it to use Windows Update.

 

I never had to download a separate driver from Prolific's site -- Windows Update installed it for me originally, and now keeps it up to date.

Alright, lemme try that right now.

[Jade B]

Uninstall everything you downloaded from Prolific themselves, and unplug the USB cable.

Now plug the cable back in.  MS-Windows should offer to search for a driver.  If not, go into device manager and trigger the search from there, telling it to use Windows Update.

 

I never had to download a separate driver from Prolific's site -- Windows Update installed it for me originally, and now keeps it up to date.

I've uninstalled the Prolific driver in my device manager. Yet when I plugged the cable back in, it kept popping up again 4-5 times. I can't seem to get rid of it.

[Jade B]

Update: Just had a long troubleshooting session with Microsoft support. I realised that my Lenovo laptop was not up to date, but even with that update downloaded and installed, the issue still persisted. The agent helped me to uninstall the Prolific driver but he mentioned that it was an external driver which means that it will keep installing itself when the device/cable is plugged in.
 

I was recommended to contact Lenovo support, so I'm going to do that later today and see how it goes. 

[Noah4x4]

One thing to eliminate, how long is your cable? Are you perhaps sat indoors with an extreme USB cable length? USB only works over very short distances. 

[Jade B]

My cable is about 1m long. Is that considered very extreme? I got it at this length so that my computer could be safely put on the ground while controlling the telescope at a comfortable length. If I were to get a far shorter cable I don't know how my setup could work... 

[mlord]

USB (all versions) is normally fine up to at least 2m in distance/length.

[Noah4x4]

OK, it’s not USB cable. However, that leads me to this conclusion….

 

When I upgraded from Win 10, to Win 11, I faced similar problems. Win 11 doesn’t like things that are not native to it, such as ‘virtual serial ports’. However, I couldn’t find fault in Windows Device Manager. I was completely baffled after three days of perseverance. The only way I resolved this was….

 

1. Remove ALL my astronomy software and reboot computer to offer a clean Win 11 base point.

 

2. Install the Prolific 2303 driver FIRST.

 

My theory here is that the driver possibly isn’t Win 11 Plug & Play and it seizes resources that if installed after other software  might cause hidden conflicts. By loading it first, it grabs what it wants then other P & P will load around it. Ignore what Windows Device Manager says! 
 

3. Next install ASCOM to establish a platform where SharpCap, Focuser Software, and CWPI  talk to each other.

 

4. Then install CPWI, Focuser software.

 

5. Then SharpCap last.

 

This drastic solution worked. I have had other problems with Win 11. I had to delete and reinstall Windows Remote Desktop. It also wants to force a new version of Outlook on me, plus suck all my data into OneDrive. I hate Microsoft! 

[mlord]

But do please try it with a DIFFERENT USB cable.  Some cables are simply defective.

[Jade B]

Hey everyone, thanks for your support thus far! Today I will head down to the store to get a new cable, and test out the solution Noah4x4 kindly suggested. In the meantime, I have created a Lenovo support ticket as well. Will keep updating this thread till I finally reach a fix  .

[Jade B]

Hey Noah4x4, by “reboot” your computer did you mean you did a factory reset? Or just a restart? Lenovo just got back to me and they’re recommending I do a factory reset but I’m a bit hesitant.

[Noah4x4]

Hey Noah4x4, by “reboot” your computer did you mean you did a factory reset? Or just a restart? Lenovo just got back to me and they’re recommending I do a factory reset but I’m a bit hesitant.

A simple restart only. But if that doesn’t work, then try a factory reset. However…..

 

I have discovered though that many of my troubles are probably a consequence of the Norton  Driver Update utility, which is a (paid) extension of Norton Utilities. This identified that in November 2023 a revised PL2303 driver for Windows 10/11 was released. After (again) updating my drivers, I had a bundle of new (similar) trouble. I fixed this by using “Roll back to previous driver” for my PL2303 driver. You might try this first before the more drastic solution described earlier, as I might now have isolated the real issue. 

 

Lenovo will always seek to have you restore factory settings. This replaces regular Intel and other drivers with Lenovo drivers that spy on you. For example, why do Lenovo require access to my web-cam? Why does it come on in strange circumstances? Mine is now blocked by a bit of tape! 

Edited by Noah4x4, 20 June 2024 - 01:12 AM.

[Jade B]

A simple restart only. But if that doesn’t work, then try a factory reset. However…..

 

I have discovered though that many of my troubles are probably a consequence of the Norton  Driver Update utility, which is a (paid) extension of Norton Utilities. This identified that in November 2023 a revised PL2303 driver for Windows 10/11 was released. After (again) updating my drivers, I had a bundle of new (similar) trouble. I fixed this by using “Roll back to previous driver” for my PL2303 driver. You might try this first before the more drastic solution described earlier, as I might now have isolated the real issue. 

 

Lenovo will always seek to have you restore factory settings. This replaces regular Intel and other drivers with Lenovo drivers that spy on you. For example, why do Lenovo require access to my web-cam? Why does it come on in strange circumstances? Mine is now blocked by a bit of tape! 

Hey Noah4x4, for some reason, my "Roll back driver" button had always been greyed out. So, unfortunately I can't try that method. Anywho, I'm going to work on uninstalling all my astro software now.

Edited by Jade B, 20 June 2024 - 08:04 AM.

[Jade B]

1. Remove ALL my astronomy software and reboot computer to offer a clean Win 11 base point.

 

2. Install the Prolific 2303 driver FIRST.

 

My theory here is that the driver possibly isn’t Win 11 Plug & Play and it seizes resources that if installed after other software  might cause hidden conflicts. By loading it first, it grabs what it wants then other P & P will load around it. Ignore what Windows Device Manager says! 
 

3. Next install ASCOM to establish a platform where SharpCap, Focuser Software, and CWPI  talk to each other.

 

4. Then install CPWI, Focuser software.

 

5. Then SharpCap last.

Update: Did all of these, still no fix. I am still getting that Code 10 error.