Can no longer connect to ST-8XME

I can no longer connect to my ST8-XME camera after installing and using DriverChecker64 is Version 4.02 Build 1 (32) bit and downloading the latest Drivers available as of 6/5/2016. Note that I've tried the same hardware on my Windows 10 laptop (upgraded from Win 8.2) and the same DriverChecker64 it has no problem at all with the same cables, hub and camera. It works fine but was a fresh install (no previous SBIG drivers or DriverChecker)

The machine in question Dell Optiplex 755, Windows 10 Home edition upgraded from Windows 7.

This machine used to recognize the camera on the USB ports on the back of the machine but now that I've upgraded to DriverChecker64, the PC doesn't see any device at all when I plug in the same camera, cables and USB hub on the back ports. So closely following the related SBIG readme"EXTREMELY IMPORTANT:" instructions I've come to the following dead-end:

I tried the same camera, cables and hub on the two front USB ports. Starting up DriverChecker64 (as Admin) it asks if I want to remove the older "Classic" driver. I did. When I click on the USB icon in the hidden icons (lower right of screen) Devices and Printers feature shows a device there but complains of an Unknown Device (Device Descriptor Request Failed) with yellow warning. When I try to manually add the camera driver there is a Device Status Window that opens showing that Windows Stopped this devices because it has reported problems (Code 43). I gather from the README that this is all expected.
Attempting to do a manual driver install, I did select for 32 bit system and the Pro folder (as my PC and camera is respectfully). I select the information SBIG folder that contains the information file (.inf) then click OK I get:

"The folder you specified does not contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for 32-bit systems."

This doesn't make sense to me on two levels. First of all I did select for a 32 bit OS which it is, however, there is NOT a driver in that one Pro folder, just the information file (.inf). So, shouldn't there be something like an sbigudrv.dll in that same folder?

It is worth noting again that I've tried the same hardware on my Windows 10 laptop (upgraded from Win 8.2) and it has no problem at all with the same cables, hub and camera. It works fine (virgin install though)!

I think I'm caught in a classic Catch 22 with the DriverChecker64.

If anyone knows where the "gotcha" is here it would be greatly appreciated. I've installed the DiffractionSupport software on the PC in question but need about 30 min. lead time to get to the observatory where it is located.

Thanks,

John Ott
303-319-1180
metrtens@gmail.com

 

Hi John,

I tried to reach you by phone and left a msg.

 

All,

I got the ST-8XME camera to communicate and with the latest Driver checker and to use the latest drivers!! Long story short; intuition told me to bypass my hub (which communicates fine between a newer Windows 10 laptop and the camera leading me to believe it couldn't be an issue - it was). Now being direct from camera to the front USB ports then my PC started showing SBIG camera without firmware just under the Processors in Device Manager. I was then able to bind new drivers to camera. I'm really not sure why the PC stopped recognizing the camera on the PC's back USB ports. If all else fails, I can work with a direct connect from camera to PC on front USB ports. It is just nice to have those USB hub ports easily accessible remote at the scope.

One of the "gotchas" was the unknown device in the Device List that that I thought was the camera was actually the hub. After all these gyrations I might need to reinstall a driver for the hub or just chuck the thing!

At any rate I'm back up and running.


Thanks,

John Ott

 

I've gotten everything to work as before, hub, camera and all and with latest drivers. What happened is two of the six USB ports on the back of the PC died. In the process of troubleshooting this problem I moved the camera/hub cable to one of two USB ports on the front of the PC. At this point, I think the Hardware and Sound -> Devices and Printers list fooled me into believing that a non-operational device listed there was the SBIG camera when in fact it was the hub who's driver was deleted (not sure if I inadvertently did that in the troubleshooting process or not). In any case, this caused me in circles trying to bind SBIG drivers to a device listed there that was not the camera. Here's an important point that caused me waste my and the SBIG Rep, Tim Pucket's time (many apologies Tim): Windows 10 has three and maybe four different ways to look at USB connected devices. The ONLY method you should use in Windows 10 to view the SBIG (ST-8 STXME USB 1.0 ) camera status is the DEVICE MANAGER (right click on the Windows icon/Start) and NOT the list of USB devices further down. If the driver is properly installed and the camera powered and connected it will show up just under the Processor Listing. It bears repeating, when it comes to checking the connectivity and related driver status of the camera, look at the SBIG USB Devices --> SBIG Camera With Firmware NOT the USB listing at the bottom of the DEVICE MANAGER.

So once I had I.D. the two failed USB ports and reinstalled the hub driver and camera drivers and bound those to the camera I was fully operational again.

I will post this to the related Yahoo user's group too then go have a glass or two of wine!

Regards,

John Ott

 

Hi John,

Thanks for your call yesterday.
I am glad you were able to get the issues resolved.