Celestron mount stops responding with SGP and PHD2

There are related topics in this forum but none with solutions.

I have had a recurring problem with my mount disconnecting or becoming unresponsive during imaging sessions with SGP. This issue used to happen constantly when I was using a different computer but seemed to go away briefly when I switched to a new one. Now it is happening again.

Thanks to a stretch of good weather, I’ve had my rig outside for the past two nights. Two nights ago, I had no problems. This morning, however, when I checked my imaging computer, I was greeted by an error message saying the Celestron mount server stopped working or responding (just after I went to bed, naturally.) I regret that I did not have the presence of mind to take a screen shot of the error.

I think the logs indicate the mount stopped responding around 12:25 AM:

[05/20/17 00:25:10.212][DEBUG] [PHD2 Listener Thread] Unknown object from PHD2: {"Event":"Alert","Timestamp":1495265110.206,"Host":"NUC","Inst":1,"Msg":"PulseGuide command to mount has failed - guiding is likely to be ineffective.","Type":"warning"}
[05/20/17 00:25:11.068][DEBUG] [PHD2 Listener Thread] Unknown object from PHD2: {"Event":"Alert","Timestamp":1495265111.034,"Host":"NUC","Inst":1,"Msg":"PulseGuide command to mount has failed - guiding is likely to be ineffective.","Type":"warning"}
[05/20/17 00:25:13.971][DEBUG] [Sequence Thread] SaveFileAscom: Done
[05/20/17 00:25:13.971][DEBUG] [Sequence Thread] =========== Save file took 23131 ms
[05/20/17 00:25:13.974][DEBUG] [Sequence Thread] Resuming auto guiding (settling)...
[05/20/17 00:25:13.974][DEBUG] [Sequence Thread] Checking PHD2 state...
[05/20/17 00:25:13.974][DEBUG] [Sequence Thread] PHD2 GetPhdStatus - Pre-Wait : Guiding
[05/20/17 00:25:13.974][DEBUG] [Sequence Thread] Sending to PHD2:
{"method": "get_app_state", "id": 1001}

[05/20/17 00:25:14.075][DEBUG] [Sequence Thread] PHD2 GetPhdStatus - Post-Wait: Guiding
[05/20/17 00:25:14.075][DEBUG] [Sequence Thread] PHD2: Requested unpause, but PHD2 reports it is not in a paused state
[05/20/17 00:25:14.075][DEBUG] [Sequence Thread] EventMarker 18 - t:M51 (1); e:0; f:14; o:
[05/20/17 00:25:14.081][DEBUG] [Sequence Thread] EventMarker 19 - t:M51 (1); e:0; f:15; o:
[05/20/17 00:25:14.081][DEBUG] [Sequence Thread] EventMarker 20 - t:M51 (1); e:0; f:15; o:
[05/20/17 00:25:14.081][DEBUG] [Sequence Thread] Running post event...
[05/20/17 00:25:14.081][DEBUG] [Sequence Thread] EventMarker 21 - t:M51 (1); e:0; f:15; o:
[05/20/17 00:25:14.082][DEBUG] [Sequence Thread] Incremented numComplete (15) for event[0]...
[05/20/17 00:25:14.083][DEBUG] [Sequence Thread] Attempting to find next event...
[05/20/17 00:25:14.083][DEBUG] [Sequence Thread] Current event[0] frame count: 15/100...
[05/20/17 00:25:14.083][DEBUG] [Sequence Thread] Current event event[0] has remaining frames.  Returning current event.
[05/20/17 00:25:14.083][DEBUG] [Sequence Thread] Checking for auto manual focus (post)...
[05/20/17 00:25:14.083][DEBUG] [Main Thread] PopulateDataModel:  Transferring view to the data model...
[05/20/17 00:25:14.089][DEBUG] [Sequence Thread] Attempting to move to next event...
[05/20/17 00:25:14.089][DEBUG] [Sequence Thread] Attempting to find next event...
[05/20/17 00:25:14.089][DEBUG] [Sequence Thread] Current event[0] frame count: 15/100...
[05/20/17 00:25:14.089][DEBUG] [Sequence Thread] Current event event[0] has remaining frames.  Returning current event.
[05/20/17 00:25:14.089][DEBUG] [Sequence Thread] Running pre event...
[05/20/17 00:25:14.097][DEBUG] [Sequence Thread] Current target has end time at 5/20/2017 3:30:00 AM
[05/20/17 00:25:14.097][DEBUG] [Sequence Thread] End time of next frame is at 5/20/2017 12:28:14 AM
[05/20/17 00:25:14.097][DEBUG] [Sequence Thread] Target is still before end time, continuing...
[05/20/17 00:25:14.097][DEBUG] [Sequence Thread] Running capture event...
[05/20/17 00:25:14.097][DEBUG] [Sequence Thread] SetStartTemp: Using focuser for temperature...
[05/20/17 00:25:14.097][DEBUG] [Sequence Thread] Set start frame temp to 16.06...
[05/20/17 00:25:14.832][DEBUG] [PHD2 Listener Thread] Unknown object from PHD2: {"Event":"Alert","Timestamp":1495265114.796,"Host":"NUC","Inst":1,"Msg":"PulseGuide command to mount has failed - guiding is likely to be ineffective.","Type":"warning"}
[05/20/17 00:25:30.092][DEBUG] [Main Thread] PopulateDataModel:  Transferring view to the data model...
[05/20/17 00:25:30.096][DEBUG] [MF Update Thread] Performing serialize...
[05/20/17 00:26:14.838][DEBUG] [PHD2 Listener Thread] PHD2 - No messages received from PHD2 for 1 minute, checking socket with status...
[05/20/17 00:26:14.838][DEBUG] [PHD2 Listener Thread] Checking PHD2 state...
[05/20/17 00:26:14.838][DEBUG] [PHD2 Listener Thread] PHD2 GetPhdStatus - Pre-Wait : Guiding
[05/20/17 00:26:14.838][DEBUG] [PHD2 Listener Thread] Sending to PHD2:
{"method": "get_app_state", "id": 1001}

Link to logs:
logs.zip (243.4 KB)

My setup:
Celestron AVX mount running latest firmware
Intel NUC7i5BNK mini PC running fully updated Windows 10
Powered USB 3 hub
SGP 2.6.0.23
PHD2 2.6.3
ASCOM platform 6.3
latest Celestron ASCOM driver

Thanks for looking. I’d sure appreciate any help you can offer.

Glenn

It happened again the other night. I turned on logging for the ASCOM mount driver. Hopefully that will provide some additional clues. I will post logs when I get a chance.

I noticed that, once the error has occurred, the COM port is not available (or at least not visible for selection) within the ASCOM mount driver. Curious.

@Starship

It’s hard for me to say what is going on with the mount. That said, I am concerned that the sequence just simply stopped responding… that’s no good.

There are a couple of components that could cause this:

  1. USB Hub
  2. USB 2 Serial (RS232) dongle/drivers
  3. Hand Controller Extension Cable

Have you tried doing a run without the USB Hub and seeing if you still have the problem?

A few years back, I made the mistake of buying a Hand Controller Extension cable off of ebay… mistake on my part… it was cheaply made and caused intermitten disconnects with my mount… took me forever to figure out what it was.

I’ve also seen cheaply made USB hubs cause disconnects… i had to try 3 different hubs before I found one that works reliably with my setup.

1 Like

Dave, thank you.

I am using a built-for-astronomy USB 3 hub by Deep Space Products, and it seems very well built. Regardless, I think your idea of bypassing it to rule it out as a problem is an excellent one. I will definitely try that when my work schedule allows.

I wonder If my USB-serial adapter or its driver might be playing a role in this problem. I am using the Keyspan USA-19HS.

https://www.tripplite.com/keyspan-high-speed-usb-to-serial-adapter~USA19HS/

Does anyone have anything good or bad to say about it?

Check your power management settings. Some laptops can put usb ports ‘to sleep’ if they are inactive for a period of time.

Usually get there by clicking on the battery icon.

1 Like

That is an excellent idea. I will do that. Thanks!

I use this exact serial adaptor on my CGE Pro without a hitch. I have used it on my laptop and desktop. Most unfortunately Celestron has not updated NexRemote in like forever and that is my bane.

Bob

1 Like