Everything has been going fine for literally the last year with SGP… Everything just merrily works and I love it I have recently changed my PC, but SGP has continued to work seamlessly… You can hear the ‘but’ coming right?
A few of days ago I did a W10 update and that has been the kiss of death… Last night the meridian flip failed and despite looking at the log I have not seen anything that suggests why. I did roll back W10 to a previous restore point hoping that perhaps this issue will go away, but no… To be honest I am having a very miserable time of it right now
So, I’m sorry to be asking such a basic question, but I’d be really grateful for some kind of diagnosis here as I am literally pulling my hair out now.
SGP asked PHD to stop and doing so the guide camera got into a bad state (and actually disconnected) from there PHD couldn’t reconnect the camera but kept stating the it was still guiding.
03:36:23.363 00.000 2020 StopCapturing CaptureActive=1 continueCapturing=1 exposurePending=1
03:36:23.363 00.000 2020 Status Line: Waiting for devices...
...
03:36:25.297 00.002 2020 Alert: Lost connection to camera
PHD will make several attempts to re-connect the camera.
03:36:25.504 00.207 2020 Try camera reconnect, now = 1507599385
03:36:25.505 00.001 2020 Status Line: Connecting to Camera ...
03:36:25.507 00.002 2020 GetString("/profile/2/cam_hash/a3f9ddbc/whichCamera", "") returns ""
03:36:25.508 00.001 2020 Connecting to camera id = []
03:36:25.508 00.000 2020 wxMessageBoxProxy(No SX cameras found)
03:36:25.592 00.084 2020 evsrv: cli 001FAD30 request: {"method":"get_app_state","id":1001}
03:36:25.592 00.000 2020 case statement mapped state 6 to 3
03:36:25.592 00.000 2020 evsrv: cli 001FAD30 response: {"jsonrpc":"2.0","result":"Guiding","id":1001}
03:36:26.708 01.116 2020 evsrv: cli 001FAD30 request: {"method":"get_app_state","id":1001}
03:36:26.708 00.000 2020 case statement mapped state 6 to 3
Pretty much the entirety of the logs after that is SGP querying PHD for the status and PHD telling SGP that it’s guiding even though there appears to be no camera connected and no images being downloaded.
Maybe @Andy has a different interpretation but that’s what it seems like to me.
I agree with that interpretation, Jared. PHD2 got a read error from the camera at 03:36:19.026 was trying to automatically re-connect to the camera, but the camera could not be found.
PHD2 incorrectly put up an error message “No SX cameras found” and was waiting for somebody to click OK. After that it would have responded to SGP saying that guiding had stopped. This is a bug – PHD2 should not be requiring user input when re-connecting the camera after a dropped connection. We will fix this (PHD2 issue #644)
@swag72 Regarding the camera error, you should probably check your cable and connector to make sure the connector is not wiggling loose and that the USB cable has not gone bad.
I’ve checked all of the cables on the camera, ran it for 5 hours during the day looping in PHD and wiggling the cables etc and it was fine. So yesterday I uninstalled and re-installed the SX drivers, which do seem to have been getting a bit flaky of late and last evening there was no disconnection… Lets hope that’s cured it
I have recently changed my PC, but SGP has continued to work seamlessly… You can hear the ‘but’ coming right? 