I am using a U.S. Converters wireless-serial adapter plugged into the GTOCP3 (Q chip). SkySafari can connect to the wireless network but fails to connect to the telescope. I know that cabling and connections are fine because I can directly communicate with the GTOCP3 via the wireless-serial adapter and I can directly enter AP mount control commands and receive the correct responses. Examining the SkySafari logs indicates a time-out error (error -13) upon issuing either a :GD# (get declination) command or a :Stxx*xx# (set current latitude) command. Example log file looks like this:
Sent ASCII at 2020/08/22 15:58:58 with error 0:
:V#
Received ASCII at 2020/08/22 15:58:58 with error 0:
Q#
Sent ASCII at 2020/08/22 15:58:58 with error 0:
:St+20*00#
Received ASCII at 2020/08/22 15:59:01 with error -13:
Sent ASCII at 2020/08/22 15:59:01 with error 0:
:GR#
Received ASCII at 2020/08/22 15:59:01 with error 0:
19:43:06.9#
Sent ASCII at 2020/08/22 15:59:01 with error 0:
:RC3#
Sent ASCII at 2020/08/22 15:59:01 with error 0:
:GD#
Received ASCII at 2020/08/22 15:59:04 with error -13:
Interpretation here is that:
1: SkySafari asks for the GTOCP3 version number and the mount responds with the correct version "Q"
2: SkySafari tells GTOCP3 the current observer latitude (or the one set in SkySafari), SkySafari does not appear to get a response... "error -13"
3. SkySafari asks for mount Right Ascension and the mount responds with the correct RA "19:43:06.9"
4 SkySafari sets GTOCPS button rates for slewing to RC3 - AP command language does not require response
5: SkySafari asks for the mounts current Declination, SkySafari does not appear to get a response... "error -13"
However, I can issue these exact same commands directly (bypassing SkySafari) and all works perfectly. SkySafari ALWAYS fails on these 2 AP commands:
:St+xx*xx#
:GD#
Is simmulationcurriculum working on this bug/error or is there a workaround anyone knows of?