Hi, I need help and advice for the recurring and chaotic SBIG message error since I switched to Windows 10. (STL4020) But always during a long exposure (1200 seconds) unrelated to the delay since the beginning of the acquisition (1, 3, 4 or 12 minutes !!). This error immediately leads to an interruption of the communication with the paramount MX +. # one example : 11:05:25 C:\Users\Gerard astro\Desktop\Trappe\10Dark_1x1_Ha_1200s_20170715.00110.fit 11:05:25 Download time: 14,8 sec., cooler at 9,8 °C, 34% power. 11:05:26 Exposure 5 of 10 11:05:26 Exposing... 11:13:34 I:TI1, CCDSoft2XAdaptor.CCDSoft5Camera.1: SBIG driver: Operating system error. Error = 30032. 11:13:34 *** Aborting session due to data acquisition failure 11:13:34 Attempting to park telescope 11:13:34 Attempting to turn tracking off 11:13:36 Telescope is not connected. Tracking Off command ignored. My setup is :FSQ106/SBIG STL4020M/MX+ Windows 10 2016 RAM 16G 64b - USB power management disabled cleaned 5 m long USB cable Paramount MX+ ASCOM 6.3 SBIG STL 4020M (2007) SBIGDriverCheck64 : V4.03 (build 4) - latest update (same issue) SBIGudr.dll V4.97 b2 (1/6/17) TSX 10.5.0/build 10857 ( I moved from build 10305 - same issue) CCDAP5 V5.10.1 (latest update) I read all the posts to find a solution. I tried several changes. I systematically find this fixed error but of random appearance when to its delay of occurrence. Thank you again for your advices. Best regards Gérard
Have you tried uninstalling the SBIGudrv.dll and all other SBIG drivers using the SBIGDriverChecker64 software, then reinstall?
No, I did not tried. I am going to do that. Thank you for this advice. I will inform you of the result. Gérard
Tim, After 4 weeks of repeated errors, taking into account all the good advices or suggestions given by the SB team, Daniel and Colin, the error continues with a random occurrence except that it appears systemically during prolonged exposure. I followed your advice. Uninstall and re-install: SbigDriverCheck: 4.03 b4 (64b) / Sbigudr.dll 4.97 b1 ( 05.25.17) Note that it appears during run session with CCDAP5 but also with TSX alone (take series) !!! 22:14:34 Exposing... 22:18:27 I:TI1, CCDSoft2XAdaptor.CCDSoft5Camera.1: SBIG driver: Operating system error. Error = 30032. 22:18:27 *** Aborting session due to data acquisition failure 22:18:27 Attempting to park telescope 22:18:27 Attempting to turn tracking off 22:18:29 Telescope is not connected. Tracking Off command ignored. 22:18:31 I: CO1, CCDSoft2XAdaptor.CCDSoft5Camera.1: SBIG driver: Operating system error. Error = 30032. 22:18:31 Imager cooler control failed. 22:18:31 Guider cooler set to 6,0 degrees C 22:18:31 I: CO2, CCDSoft2XAdaptor.CCDSoft5Camera.1: SBIG driver: Operating system error. Error = 30032. 22:18:31 Guider cooler control failed. I recall all the actions taken: - TSX 10.5.0 (build 11012) - Turn off Windows Power Management, USB Selective Suspend, power management on USB Root hubs, USB hub, and all attached USB devices and COM ports. - Change for short USB 2.0 cables (50 cm for SBIG / flat and 1.8 m for MX + / PC DELL) - Direct connection to USB 2.0 port PC Windows 10 Dell (I was using the USB3.0 ports at the beginning of the problems). - Precise checking of each connector. - I performed the minimalist CCD test according to the recommendations (8 steps) as recommanded by Daniel Bisque = OK. - I read all the recommanded bisque document (Software Bisque Knowledge Base Article - 1239 and Software Bisque Knowledge Base Article - 1236 USB DEVICE). I am a little desperate by this mistake and help will be very appreciated. Thank you in advance Gérard
Can you please do the following: 1.) Open the SBIGDriverChecker64 software and click the "Debug Log" button. 2.) Click the "ALL" button, then click the "Set Path" button and choose a path and filename for the log file. 3.) Run the software, and recreate the error you are experiencing to log the details of the failure. Then send us the resulting log file for analysis.
Thank you Tim for your quick reply. I will apply your analysis proposal as soon as I return to the observatory and will promptly send you the file. Gérard
Tim, I applied the process SBIGDriverChecker64 software "Bebug log" but I do not understand the final approach: Select All: OK Set Path and file name: OK I leave SBIGDriverChecker64 software open I run after my run session: CCDAP5 / TSX / FocusMAx4 for 5 to 6 long exposures. The logfiles.txt file remains the same and almost empty (just the different versions of sbigdriverchecker). I do something wrong. Sorry. Gérard
Is CCDAP5 / TSX / FocusMAx configured to use the SBIG drivers? Can you send a screenshot of the SBIG debug window? Can you download and try the camera with our CCDOps software? You can download it here: ftp://ftp.sbig.com/pub/InstOps.exe
