i have an STT-8300M with the FW8G-STT OAG filter wheel cover. since i am using PHD2 for guiding, i must use the SGP API Guider shim to connect to the guide camera from PhD2.
i am having a problem where PhD intermittently reports that the guider camera is disconnected. this seems to be happening between exposures, possibly as a result of pausing guiding. there’s nothing terribly expository in the logs; both programs just report that the camera is no longer connected. on the last exposure that worked, the guider API returns kind of a long total time relative to all the previous exposures. one odd thing is that apparently SGP does not know how to parse the result codes coming back from the guider CCD as evidenced by lots of “status check: Unknown” messages in the log.
SGP version: 2.4.2.11
PHD2 version: 2.5.0
sbigudrv.dll: 4.88 build 4 (this is actually downrev and i will try with build 11 tonight)
sbigu32.sys: 2.41.0.1338
when i woke up this morning to find the sequence was aborted, i was able to reconnect PhD to the guider API, so it’s not clear that there was any kind of hardware issue. with any luck it’s as simple as PhD still trying to pull a guider image while the main image is being downloaded.
below is a link to a shared folder with the logs - check around 01:48 AM. thanks for any help with this issue.
I believe there is an easy fix for this. You can increase the camera timeout setting in the camera tab in the brain in PHD2. PHD2 2.5.0’s default value of 5 seconds is too aggressive for the SGP API Guider camera. Try a higher value like 60 seconds or 120 seconds.
In later versions of PHD2 we have increased the default setting and made the error message more descriptive (including instructions about increasing the setting.)
Also, in the 2.4.3 beta, we allow SBIG cameras to pause guiding during download. Many SBIG users have reported this successfully stops the issue you are experiencing from happening.
[10/13/2015 1:48:16 AM] [DEBUG] [Sequence Thread] Resuming auto guiding (settling)…
[10/13/2015 1:48:16 AM] [DEBUG] [Sequence Thread] Checking PHD2 state…
[10/13/2015 1:48:16 AM] [DEBUG] [Sequence Thread] PHD2 GetPhdStatus - Pre-Wait : Paused
[10/13/2015 1:48:16 AM] [DEBUG] [Sequence Thread] Sending to PHD2:
[10/13/2015 1:48:16 AM] [DEBUG] [PHD2 Listener Thread] Could not process PHD2 input: “The camera has been disconnected. Please resolve the problem and re-connect the camera.”,“Type”:“warning”}" : Unexpected character encountered while parsing value: T. Path ‘’, line 0, position 0.
[10/13/2015 1:48:16 AM] [DEBUG] [Sequence Thread] PHD2 GetPhdStatus - Post-Wait: Paused
Ya… mystery to me. There is code in 2.4.2 to do this (the logs lines you made huge), but the option to toggle it on and off is hidden… so I am not sure how you managed to turn this feature on.
As I mentioned, this feature will be formally released in 2.4.3.
ha no idea! i thought this might be tied to the fact that the guider API was in use, since it seems like a probable SBIG requirement that only one imager could be read out at any given moment.
alright! after increasing the camera timeout in PHD2 i had a full night of successful imaging last night. thanks andy for the suggestion. now if you can just do something about the clouds i’ll be all set.