Re: Heads-up on possible abrupt parking problem #Absolute_Encoders #Mach2GTO #APCC

Ray Gralak


I sent you a private email, but I wanted to post here as well in case anyone else has a similar issue (unexpected parking) in the future.

In looking at the logs you supplied yesterday evening, I saw that there is an 8-minute gap in the log file (APCC-2021-08-19-195035.txt). So, it makes sense that the mount would be parked because the mount is configured to do a safety-park after 5 minutes if no commands are sent to it by APCC.

I found other shorter gaps in the log, but the one below is the one that caused the park. Notice the time jump from 20:51:50.994 to 21:00:14:084 on line 0228227:

0228273 2021-08-19 20:51:50.930: Debug, Command Thread, TX = '$HDG#'
0228274 2021-08-19 20:51:50.962: Debug, Command Thread, TX='$HDG#'|RX='+53*57:40.2#'
0228275 2021-08-19 20:51:50.966: Debug, Command Thread, TX = '$GR#'
0228276 2021-08-19 20:51:50.994: Debug, Command Thread, TX='$GR#'|RX='+244*21:46.9#'
0228277 2021-08-19 21:00:14.084: Debug, Command Thread, TX = '$GD#'
0228278 2021-08-19 21:00:14.112: Debug, Command Thread, TX='$GD#'|RX='-35*59:47.7#'

So I think you should take a look at Windows Event Viewer to see if you can see what might be happening. This could be a Windows system, memory, disk, motherboard/cpu, etc., issue.


-----Original Message-----
From: [] On Behalf Of David Johnson
Sent: Thursday, August 19, 2021 3:21 PM
Subject: Re: [ap-gto] Heads-up on possible abrupt parking problem #Mach2GTO #APCC

Also, if the driver window is blank because there is no communication with the mount than why is the APCC window
still showing the correct mount position?

Join to automatically receive all group messages.