Discussion in 'CCDOPS and SBIG Universal Driver' started by Adam Robichaud, Sep 15, 2016.
Have you noticed any OS Errors popping up in CC_QUERY_COMMAND_STATUS calls that *don't* fail?
No, not yet Adam. I will be collecting logs tonight though and will upload if I catch a timeout.
just wanted to let you know that I continue to try to trap the timeout error but the comprehesive logging continues to hinder those attempts. Of course, as soon as I turn logging off, the darn camera hangs and there is no specific time period that elapses.
If you get to the point of your analysis whereby you can start to refine the logging options, let us know, and perhaps we can offer more data.
I can also confirm what Martin reports. For example during imaging last night I had two timeout errors in a few hours. So today I did a bench test with a small subframe switching between bin 1x1 and 2x2 for 1600 continuous exposures and logging on. No errors.
Adam or anyone else,
Can you confirm this error I get in CCDAuotpilot when my SBIG STXL camera quits is related or not related to the previous Transmisssion Timeout errors?
COleException: Not enough storage is available to complete this operation.
(8007000E) SCODE: 8007000e
For the last 5 sessions I get this error terminating my imaging run. The camera is usually downloading an image, auto focusing or downloading an autoguider image. This occurs when SBIG logging is off. I have not been able to "trap" any errors with the various drivers and logging on. I'm currently trying the newest Beat drive you released.
Martin: you could try turning everything off except:
• Read COM Pipe
• Write COM Pipe
• Async Read
• Async Write
That's still a large portion of the logging, but it should speed things up considerably...
Robert: I can't confirm that it's not related to any timeouts, since I can't rule anything out without a little more context, but I suspect it's not — could you start a new thread, and upload some SBIG Driver Logs so we can start an investigation?
What is the status of the TX Timeout problem? I still have to restart my camera 1-2 times per night after a TX Timeout error message stops the exposures.
The investigation is ongoing. At the moment, we've had limited success reproducing the issue, but error logs from different users are pointing to different causes. We're still trying to suss out the causes, and formulate a plan of attack.
Apologies, but I have removed my scope and camera from the remote obs as I am about to relocate back to AUS so I am unable to assist with logging.
hello has there been any update on this investigation? I am having TSX crash after 3-4 exposures every night now, hoping the test cases have given some direction.
The guys are closing in on it. We can replicate the problem, but it usually takes a couple of days of continuous camera operation before it fails! So we set up a test and then let the camera click away until it fails.
Data is currently pointing towards a firmware glitch of some kind. That is a tentative conclusion, subject to the results of another test run - which is underway as we speak. That will provide more detailed information.
How can I go back to an older driver for my STXL 11002 camera? The ColeException error is a show stopper for me with current beta driver. I have heard going back to a May driver will at least get rid of this error. For me the transmission timeout error occurs less frequently so I would rather deal with that error and get some imaging done.
Rob did you figure it out? I think all you need to do is put back the .dll file. Look here.
No I still have the beta driver installed that has enhanced logging. I never got a response from SBIG on how to get a copy of the older driver. After reading your post I found a version dated 5/13/16 so I may try that.
I cannot get through a night's worth of imaging currently. Still wondering if a fix is coming.
Yeah I still get lock ups too - Guys any update on this "fix"?
Adam is back from holidays on Tuesday, should be able to update you.
As stated by Doug in November "the guys are closing in on it".
Are the STXL camera timeouts still under investigation? My silence does not mean the problem has gone away.
Adam is gearing up to do a driver release. It should clear up a couple of things.
A new driver update was released on Friday. We're not certain if this issue is resolved, but please give it a try.
Is the update specific to STXL cameras for transmission timeout errors?
Separate names with a comma.