I'm unable to get CCDOps to connect to the camera when trying to "Establish Link". It just says "Establishing a link with the camera..." and then freezes. I've waited for up to half an hour without any response. When I first try to establish a link, the red light on the camera will flash quickly, stay on for a second, then flash quickly again before staying on. I tried this on two different computers, one that's on Win7 and one that's on Win10. The Win7 PC already had a set of older drivers and the camera has worked in the past on that PC. I was replacing a Navitar zoom that's attached to this camera and now I can't get CCDOps to establish a link to the camera. I can't establish a link to the camera through SBIGDriverCehcker64 under the "Firmware" tab and clicking the "Get Firmware from Camera" button. CCDOps version: 5.61 Drivers: Driver Name | Version | Date sbigudrv.dll | 4.97 Build 1 | 01-06-17 sbigu64.dll | 2.41.0.1338 | 01-27-15 sbigucam.hex | 2.42 | 01-27-15 sbiglcam.hex | 2.40 | 01-27-15 sbigfcam.hex | 2.25 | 01-27-15 sbigfga.bin | 2004.11.10 | 01-27-15 A longer version of the log is attached; Here's some snippet from the logs: At t = 0.000: ========================= At t = 0.002: Application Path Name : C:\Program Files (x86)\SBIG\CCDOps5\Ccdops.exe At t = 0.003: ========================= At t = 0.004: CC_OPEN_DRIVER : err = 00 - No Error At t = 0.006: ========================= At t = 0.007: CC_CLOSE_DEVICE : begin At t = 0.008: CC_CLOSE_DEVICE : end, err = 28 - Device not Open At t = 0.009: ========================= At t = 0.010: CC_QUERY_USB2 : begin At t = 0.012: CC_QUERY_USB2 : driver supports up to 8 cameras. At t = 0.013: ========================= At t = 0.015: CC_OPEN_DEVICE : begin At t = 0.022: CC_OPEN_DEVICE : end, err = 00 - No Error At t = 0.023: ========================= At t = 0.024: CC_ESTABLISH_LINK : begin At t = 0.027: MicroCommand : MC_GET_VERSION At t = 0.029: ------------------------- At t = 0.029: WriteComPipe : SyncWrite -> Trial=1, Ask/Wrt=2/2 At t = 0.030: data : A5, 60 At t = 0.031: ReadComPipe : Ask/Got = 4/4, -> MC = MC_GET_VERSION At t = 0.031: data : A5, 62, 02, 25 At t = 0.032: ------------------------- At t = 0.032: WriteComPipe : SyncWrite -> Trial=1, Ask/Wrt=5/5 At t = 0.033: data : A5, 73, 80, DD, A0 At t = 0.034: data : A5, 71, 00, 25 At t = 0.035: ------------------------- At t = 0.035: WriteComPipe : SyncWrite -> Trial=1, Ask/Wrt=5/5 At t = 0.036: data : A5, 73, 81, DD, A0 At t = 0.036: data : A5, 71, FC, 25 At t = 0.037: ------------------------- At t = 0.037: WriteComPipe : SyncWrite -> Trial=1, Ask/Wrt=5/5 At t = 0.038: data : A5, 73, 82, DD, A0 At t = 0.038: data : A5, 71, 01, 25
Start by confirming this isn't a cable problem. Check the Windows Device Manager, and see if the SBIG Camera is detected by Windows. Try changing the USB 2.0 cable. Use a short one (6 feet 2m or less). Try changing USB 2.0 ports, to a different one, preferably that is on the back of the PC, direct on the motherboard, not front panel extended cables. Make sure Windows Power Management, USB Selective Suspend is turned off: and make sure your USB hubs, root hubs, ports, and PCIe devices aren't powering off: As an aside, I noticed you're running obsolete drivers and software. You can find the most recent version here, under the USB Port cameras: https://diffractionlimited.com/support/sbig-archives/
Hi Colin, thanks for the suggestions. The camera is being detected by Windows in Device Manager. I've tried two different USB 2.0 cables, both are 6 feet long, didn't seem to make any difference. I've tried both USB ports on my laptop (Win10), and tried 3 different USB ports on the back of the desktop PC (Win7). Windows Power Management, USB Selective Suspend was on for my laptop but turning it off didn't make a difference. USB hubs, root hubs, ports, and PCIe devices are not powering off in Device Manager. I updated SBIGDriverChecker64 and CCDOps to the latest version on the website, that didn't work either. What's the likelihood that something has failed inside the camera? Anything you can discern from the logs?
It is odd that the Device Manager is seeing the camera, and there is some communication in the log. Did you remember to exit CCDops BEFORE trying to check the firmware in the camera with SBIGUDrv ? Only one application can access the camera at a time. I'm suspecting firmware or hardware failure in the camera, but it's not quite like other failures I've seen with these. Our repair expert @Bill will need to weigh in on this.
I did in fact exit CCDOps before trying to check the firmware in the camera with SBIGUDrv. I just tried plugging it in to the Win7 PC using the original power and USB cables that were connected and I'm still getting the same behavior. My previous testing where I tried two different USB cables were from a testing/calibration tool kit that we use.
I managed to get this resolved. The root cause was the power supply to the camera. When I used a different 12V power supply, I can now successfully establish a link to the camera in CCDOps.
Thanks for letting us know. Was the original (supplied by us) power supply the one causing the problem? One other tip: The coaxial power connector on the camera body may have a split centre pin, where the two halves are separated by a gap, and they push against the inside of the DC power cord. The two halves get compressed after years of use or strain. A tiny flat jeweller's screwdriver can be used to gently spread the halves just a bit, to make better contact if this is part of the problem.
