Hi, I can’t connect my ST2000xm, please can you help me? Firstly some information about PC and camera: PC: windows 7, 64 bits The SkyX, but not in use for camera! CCDSoft latest edition, all drivers are checked with the driver checker. Camera: ST2000xm + CFW 10 This will happened - Open the dialog box Camera in CCDSoft - Camera: SBIG TS2000xm Filter wheel: SBIG GFW 10 Radio button: imager is Checked - I connected the camera, the fan is noisy but don’t turn. This message is popping up: Undescibed error: Error 1027 (403) I Clicked ‘OK’, then something like this (Translated from Dutch) ‘USB app will not be recognized’ Please can you help me?
I would email Bill Lynch. Sounds like it needs service. Regards Tim Authorized Repair Center Bill Lynch - SBIG Service & Repair Center(please note new address) 130 Castilian Drive, Suite 102 Santa Barbara, CA 93117 Bill Lynch - bill@sbig.com Phone: (805) 308-6979 Note: Please contact our authorized service & repair center for an RMA number prior to returning your equipment.
Hello, (The following is written by a friend because my knowledge of computers and electronics is insufficient to solve this) The ST-2000XM is failing to connect to my pc (WIn7, 64 bit). This camera has worked correctly on a different computer running Windows XP for years. It has been kept stored for the past few years. But now I want to use it again on a more modern pc and OS. I installed the CCDsoft package (v5.0.0.216) and updated with the SBIG driverchecker (v3.1.1.47). But after connecting the USB cable and powering up the power-supply the pc does not recognize the device. It calls it an "Unknown device". Upon looking further in the device properties details-tab I noticed that the PID and VID values are set to 0000. To my (friend) knowledge this is not correct to the USB standard, but he is not familiar enough with camera product (see this image URL (was unable to attach image): http://www.sterrenwacht.eu/Unknowndevice(ST-2KXM).jpg These VID and PID values set to 0000 reminded my (friend) to the FTDI Driver that started bricking supposedly counterfeit devices late 2014. These drivers happend to be present on this pc (FTDI driver version 2.10) Could this be related and the ST-2000XM have been detected as a FTDI-clone chip? What are the proper values? Is there a way to reset the PID and VID to proper values? With kind regards, Gerard van den Braak
Gerard, I'd recommend you download and install the latest SBIG driver checker (its at least v4.00 build 15), and try with that. You are using an old version. The FTDI bricking issue is fiction. Prolific had the problem with massive counterfeiting, but didn't brick the devices either. You might want the latest FTDI chip drivers that support you OS.
FTDI is irrelevant because your camera uses a Cypress chipset. It could easily be a driver installation issue. Cypress uses a "re-numeration" procedure, where the camera boots up first with a generic Cypress VID and PID, which loads a driver that asks the chip what firmware to load. The driver loads the firmware and tells the camera to reboot. Once it reboots the final VID and PID appears, and the correct driver is loaded automatically by Windows. If this process fails the camera could come up with zero VID and PID. Unfortunately, if this is not the correct explanation, then the camera might be "bricked" and would have to go to SBIG Service & Repair to be reprogrammed.
Hi, The problem has been solved. I connected the camera successfully too on another pc. It seems the problem is the USU-port on my observatory-pc. That port works well with other devices, not with the 2Kxm. I using now another USB-port. Thanks for helping.
