Good afternoon, About two months ago I started getting the 30008 error from both my STF-8300M and ST-i cameras. I haven't had time to work on the problem until now, but in early May I updated the SBIG drivers. Today I got back to it, and the problem was still there. Both cameras are attached with long USB cables (no hub). I'm running TheSkyX Professional. Everything had been working fine for a long time (most recently in lat April), and nothing that I am aware of changed in early May. The same error occurs with both cameras, and it manifests the same way: TheSkyX connects to the camera just fine, I go to take an image (Dark, light, doesn't matter), it does the exposing with the progress bar, but then instead of downloading, it sits there for a few seconds and then throws the error window. I searched for help articles on this forum, and found the posting about shutting off the windows power management features. (https://forum.diffractionlimited.co...rn-off-usb-selective-suspend.7848/#post-42928) I followed those instructions, and I then rebooted the computer, but the problem persisted. I checked the device settings, and the power management features were still off. Nothing changed about the hardware between when it worked and when it didn't. I have no idea if there were Windows updates in that time frame. I am not sure what else to try. Can someone suggest steps I might take? Thank you in advance, Don Smith
Hi Don, TSX error 30008 corresponds to a Receive Timeout error - the driver is waiting to hear from the camera and gives up. That could be a bad cable, problem with a USB port or hub, software/driver problem, or a camera hardware problem. 1. What exact version of TheSky X are you using? eg TheSky X Professional x64 (64 bit) 10.5.0 Daily Build 13936 2. Since you mention drivers, let's start with that. Do you have SBIG Driver Checker 4.05 ? The [About/Help] button will show you. If not, then download it here: https://cdn.diffractionlimited.com/downloads/SetupDriverChecker64.exe 3. Check the 32-bit version of SBIGUdrv.dll Launch the SBIG Driver Checker, it will show you the versions of files on the system. It will show the 32-bit version of SBIGudrv.dll, which is normally 5.1.1.0. If not, update the drivers. 4. Check the 64-bit version of SBIGUdrv.dll The 64-bit version normally is found in C:\Windows\System32 Right-click, Properties, and then go to the details. It should be 5.1.1.0, like this: 5. Did TheSkyX install an old version? If you are running 64-bit TheSky: When you install or update TSX, it may install a copy of SBIGUdrv.dll (64-bit) which might not be the final, correct one. Have a look in: C:\Program Files (x86)\Software Bisque\TheSkyX Professional Edition\TheSky64 Check for sbigudrv.dll, and verify it is version 5.1.1.0 Generally it is safe to rename it to something like "sbigudrv.old", and then TSX will use the one in C:\Windows\System32 6. Try other software. a) Disconnect one of the cameras (eg the ST-I). Launch the SBIG Driver checker. Go to the Firmware tab. [Get firmware version from camera] If it finds the camera, then all should be ok. Then disconnect the ST-I, and repeat for the 8300 camera. You could also try MaxIm or CCDOps. 7. Try connecting the cameras, one at a time, with a known good cable, directly to a USB port on the back of the computer. (not one on the front of the case). Eliminate any hubs, extenders, etc. Don't connect the cameras to the USB ports in the Versaplate if you have a Paramount. That USB hub is known to have limitations and can cause trouble with cameras. 8. If that doesn't solve it, what changed?
Good morning! Thank you for the response. Is it really plausible that both USB cables would suddenly fail at the same time? I'll explore that option last. But let me go through every option you raise, systematically. 1. TheSkyX version 10.5.0, build 13507. I am not sure how to tell if it's 64 or 32 bit. 2. SBIG Driver checker 64 4.0.5.0 3. According to SBIGDriverChecker64, sbigudrv.dll 5.1.1.0 6/4/24 4. Under C:\Windows\System, I found a file called sbigudrv.dll, and its properties window said 5.1.1.0 5. Interesting. I looked in C:\Program Files (x86)\Software Bisque\TheSkyX Professional Edition\TheSky64, and the sbigudrv.dll file there says 4.9.9.8. I have now renamed it, as you suggested. I do have one of the cameras plugged into the front of the computer, because I ran out of ports in the back. If this doesn't work, I will try to switch it with something in the back. But like I said in my original post, there are no hubs -- they're both connected directly to the computer with single cables each. To me, the key question is the one you ask at the end: what changed? Everything worked fine in late April, and then suddenly in early May, it didn't. The computer is running Windows 10 Pro, version 22H2, in case that matters. It says the version install was 5/1/2023, so not this May. I am now rebooting the computer, then I'll see if I need to move on to trying the physical replugging options. Nope. That didn't do it. I will post this, and then try the physical replugging process. Yours, Don
Good morning, I tried checking the firmware as you suggested, and the driver checker says the ST-i is up to date (version 2.37), but the STF-8300 is not (stf-8300usb.bf2 is 2.45 not 2.64, and stf-8300ga.bf2 is 2.15 not 2.25). I will need to get our IT people to let the driver checker go through our firewall to be able to do the upgrade, but I will get that in motion. Yours, Don
Help... About in TSX will tell you. Also, there is an X icon for the 32-bit, and a 64X icon for the 64-bit. Since you found that SBIGUdrv.dll where I mentioned, you've got probably got 64-bit installed, but I don't know if that is what you are running. The firmware is likely already downloaded onto the PC, that's how it knows what is current.
How long does the firmware upgrade usually take? It's been sitting like the image below for about a half hour now. Yours, Don
Sometimes the process is actually complete, but it got stuck at the end. So.. if you are feeling lucky... You could try to stop the process - it might have succeeded, or failed in a safe way. If it didn't then the camera may be unresponsive and have to come in for service. You could: a) pull the USB cable out of the camera. Wait and see what happens to the update. b) stop the update program. You might have to use Task Manager. Then reconnect/restart the Driver Checker, and see if it sees the camera. c) Power off the camera. Wait 30-60s. Power on. Restart the Driver Checker, and see if it can get Firmware version. If it updated, hooray. If it did not update, but talks, phew, you could try again. If it won't find it, power everything off including the PC, wait, reboot the computer, power up the camera, and try again. If none of the above works, it might have to come in.
Okay. It's been an hour. I'm going to try a, b, and then c, as you suggest. I hope I don't have to send it in, because my observatory budget has been cut down to zero. Wish me luck... Don
a) pulled the USB out. No change on firmware updater. b) Killed the driver checker. Did not need the task manager. Plugged the camera back in, and Windows says device not recognized. That doesn't seem to be a good sign. Launched driver checker and now it can't find the camera. c) Powered camera off. Waited a couple minutes. Powered camera on (USB device not recognized). Driver Checker did not find camera. Powering computer down. Rebooting... turning camera back on... Hm. Did NOT get the USB not recognized. That's a little less terrifying. Holy smokes! The driver checker found it! But now it says it's on 2.63, not 2.64, and the "ga" file is unchanged. Still 2.15, not 2.25. TheSkyX connects to the STF8300 camera... taking a 1 s dark... it worked!!!! Plugging the ST-i back in... connecting works... took a 1 s dark... it worked!!! Okay, unless you tell me otherwise, I'm going to count myself lucky and quit meddling. Do I need to worry about the firmware not being fully up to date? Yours, Don
The "usb" side manages the interface, the "ga" side manages the field-programmable gate array. Normally they are a set. Ideally, you'd want the firmware fully up to date. You could give it another go if you wish and if it get stuck after 30mins, power it all off, wait, and check.
Greetings, I tried it one more time, and the same thing happened. It said it was updating the ST-8300 to 2.64, the progress bar went all the way over (I heard the camera make noises and the computer made the little tune it plays when you plug in a USB, so perhaps the camera power cycled itself?), but then it just stopped. I hit "Done" and the driver checker quit just fine. Relaunching found it was still on 2.63, and it never did anything with the other firmware file (the 2.15). I was able to connect to both cameras and take pictures, so I don't know if I can (or should) do anything else. Is it all right to just leave it in this state, since it seems to be working? Thank you for your time, Don
You missed a key step. After you hit "Done" and quit, you MUST power OFF the camera. Then wait about 30s. Power ON. Launch the Driver Checker and confirm firmware is updated. Otherwise, DC is still talking to the old firmware that is still running. Camera has to be power cycled for it to load its new firmware. Another tip: Make sure you only have 1 camera attached at a time. eg unplug USB from ST-I when you are working on updating ST-8300.
Ok. I aded that step. Everything ran as before. It got to the end of the progress bar and stopped. The computer played the little "USB unplugged" tune, then the camera made the "click-click-click" noise it makes when you turn it on, and the computer played the little "USB plugged in" tune. The Driver checker remained paused. So I hit Done on the driver checker, then powered off the camera. Waited a couple minutes, then powered it back on. Launched the driver checker, and it still said 6.23 instead of 6.24. And yes, I've been unplugging the ST-i for all of this. Yours, Don
The USB "unplug" sound could be caused by the firmware update happening. It could also be caused by a problem with the camera hardware, the USB cable, and anything you have plugged in between, hubs, extenders bad ports on the PC. If you have a second computer, you could try updating the firmware with the second computer. I'm not sure this is worth spending more time on. Is this an ST-8300 or STF-8300? (Sometimes you've left off the "F" in your messages) Camera serial number? I recommend you go get the updated TheSky X.
Greetings, Thanks for all your help. I also think it might not be worth more time. They are currently working, both cameras, so I am inclined to not poke the bear any more, unless you think it's really important to get that firmware updated. I would love to get the updated TheSky X. Is it free? Because my observatory budget has been cut to zero at the moment. Very frustrating. I will post the exact serial number next time I get a chance to get up to the observatory, but according to my records, it's an STF-8300M. We bought it 16 Sept 2013. Yours, Don
You'll have to check with Software Bisque - usually they charge a fairly modest fee to stay current. If you log in on their website, it will tell you what you can download. Sorry to hear that - it seems a lot of people are having to scrape together a few bucks due to cutbacks. Well, a dozen years is a pretty good run. If it's behaving, keep on using it. We have a limited supply of circuit boards left if it needs to be repaired.
