I have seen a few posts here and on other blogs about this topic, but I am stumped after trying all troubleshooting I can conceive or read about.
I was using a 174MM for my imaging camera until I got the 6200MM. Using a SX Lodestar for my guider and still do with my 6200MM. Once I got the 6200MM, the 174MM was repurposed to be my planetary imaging camera. Before when I was imaging DSO with my 174MM, the computer (Win10, 64bit) recognized it as a USB 3.0. When I got my 6200MM, I set it up for DSO work and got all that working. Then, once I got a FW for my 174MM, I set that up and all of a sudden, the computer only recognizes the 174MM as a USB 2.0 camera.
My troubleshooting efforts have involved:
1) Using the ZWO USB 3.0 cables that came with the 174MM camera.
2) Using any other USB 3.0 cable I have, and all with USB 3.0 length and power requisites in mind.
3) Using known working USB 3.0 ports for both cameras (6200MM and 174MM) on two different laptops.
4) Using all current drivers and software for everything I use.
5) I can connect the 6200MM using a USB 3.0 cable to a known working USB 3.0 port and can see in USB Device Viewer that it is a USB 3.0 device. I disconnect the 6200MM and connect the 174MM to the same port and using the same cable, and USB Device Viewer sees it as a USB 2.0 device.
6) It seems that the computer doesn't see the camera at all if I just plug the USB cable in normally, but if I slowly plug it in, it is seen... though still as USB 2.0.
7) I have a Pegasus Pocket Powerbox Advance, and it was through that box that I used both cameras. The 174MM in the box still shows USB 2.0 the same as when I connect the camera directly to the computer's without the box inline.
I have attached screenshots that show the whole USB Device Viewer display for each camera, and further on the 174MM screenshots, I show a suspicious Properties dialog box for the 174MM driver, stating “Device USB\VID_03C3&PID_174B\5&167de173&0&2 requires further installation” and “Driver Management has concluded the process to add Service ASICAMUSB3 for Device Instance ID USB\VID_03C3&PID_174B\5&167DE173&0&2 with the following status: 0.”
I’ve reinstalled in every conceivable order of the two drivers (ASCOM for ZWO and the ZWO native driver) and nothing new. Is there a chance that the USB card in the camera is damaged somehow and can't play as a 3.0
Thank you, Bill