Solved StarGo Ascom driver does not cooperate with Voyager astronomy automation

  • Hugues
  • Topic Author
  • Offline
  • New Member
  • New Member
More
27 Apr 2020 22:02 - 18 Sep 2020 07:37 #246 by Hugues
Hello,

I've recently tested voyager automation software and face some error with the Ascom StarGO which does not seems to cooperate.
The function that reporting error are Home and Park. I've discussed with Leonardo from Voyager and it's seems that the ascom driver of the mount does not comply with some ascom standard ?

The homing command result is correct and the telescope move to the home position and put the mount in a terrestrial tracking mode (Stopped)
But it's seems the driver StarGo is not cooperating with voyager. The command immediately report an Error before the mount have completed the slew to the home position.
2020/04/23 00:24:05 592 - INFO      - [Homing Mount                 ] - [Funzione                                     ] - Action Start
2020/04/23 00:24:05 608 - INFO      - [Homing Mount                 ] - [HOMING_Code                                  ] - Start Homing Mount ... this is a Sync process...
2020/04/23 00:24:07 123 - CRITICAL  - [Homing Mount                 ] - [Funzione                                     ] - Action Aborted for Error : [(ASCOM) ASCOM.AvalonStarGo.NET.Telescope] cannot Find Home ()
2020/04/23 00:24:07 139 - INFO      - [ATOMIC_HOMING_MOUNT          ] - [Funzione                                     ] - Action Time [ATOMIC_HOMING_MOUNT] => 0 [m] 1 [s] 
2020/04/23 00:24:07 139 - INFO      - [ATOMIC_HOMING_MOUNT          ] - [Funzione                                     ] - Action Time Mobile Mean [ATOMIC_HOMING_MOUNT] => 0 [m] 1 [s] 
2020/04/23 00:24:07 155 - INFO      - [Homing Mount                 ] - [Funzione                                     ] - Action End : FINISHED_ERROR

The mount park correctly but there is no tracking status after park. (In reality the mount is stopped and parked).
the function doest seems implemented or is this a misconfiguration my StarGo ?
2020/04/26 04:02:33 876 - INFO      - [Telescopio                   ] - [PushFunction                                 ] - PierSide= pierEast (SW)(2) ; LastGotoPierSide= pierEast (SW) ; FlipStatus= FATTO ; MeridianQuery= IDLE ; LST= 16:08:47 (SW) ; RA= 12:13:01 ; LST-RA= 03:55:46(3,92951488888889) ; AZ= 292° 03' 41" ; ALT= 51° 53' 20"
2020/04/26 04:03:19 225 - INFO      - [Mount Parking                ] - [Funzione                                     ] - Action Start
2020/04/26 04:03:19 225 - INFO      - [ParkMount                    ] - [PARK_Code                                    ] - Mount Parking ...
2020/04/26 04:03:33 927 - INFO      - [Telescopio                   ] - [PushFunction                                 ] - PierSide= pierEast (SW)(2) ; LastGotoPierSide= pierEast (SW) ; FlipStatus= FATTO ; MeridianQuery= IDLE ; LST= 16:09:47 (SW) ; RA= 10:10:50 ; LST-RA= 05:58:57(5,98260355555556) ; AZ= 344° 43' 00" ; ALT= 47° 47' 00"
2020/04/26 04:03:46 161 - INFO      - [ParkMount                    ] - [PARK_WAIT_Code                               ] - Mount Parked
2020/04/26 04:03:46 176 - INFO      - [ParkMount                    ] - [TRACKING_STOP_CHECK_Code                     ] - Mount Parked but Driver say Tracking is ON, try stopping ...
2020/04/26 04:03:46 442 - WARNING   - [ParkMount                    ] - [TRACKING_STOP_WAIT_Code                      ] - Mount Parked but Driver say Tracking is ON, and Cannot stopping it !!!
2020/04/26 04:03:46 442 - CRITICAL  - [Mount Parking                ] - [Funzione                                     ] - Action Aborted for Error : Cannot Stop Mount Tracking After Parked

Why would the mount report traking ON if the mount is correctly parked ?

For short it seems that with this mount the ASCOM driver for command Park and Home work but report a false positive error to Voyager ?
Last edit: 18 Sep 2020 07:37 by Stefano82. Reason: formating

Please Log in or Create an account to join the conversation.

  • Stefano82
  • Stefano82's Avatar
  • Offline
  • Administrator
  • Administrator
  • Don't panic
More
30 Apr 2020 09:18 #250 by Stefano82
Hello

At the moment we are in contact with Leonardo from Voyager in order to fix this issue.

Soon as we will have a solution we will let you know about.

Best regards.

Stefano
Avalon Instruments Team

Please Log in or Create an account to join the conversation.

  • Hugues
  • Topic Author
  • Offline
  • New Member
  • New Member
More
08 May 2020 02:09 #268 by Hugues
Thank you stephano, that's a very good news ;)

Please Log in or Create an account to join the conversation.

  • Stefano82
  • Stefano82's Avatar
  • Offline
  • Administrator
  • Administrator
  • Don't panic
More
12 May 2020 12:05 #279 by Stefano82
Hi Hugues

We received a feedback from Leonardo, the Voyager developer. He told us that in next Voyager release the issue will be fixed.

Best regards.

Stefano
Avalon Instruments Team

Please Log in or Create an account to join the conversation.

  • Stefano82
  • Stefano82's Avatar
  • Offline
  • Administrator
  • Administrator
  • Don't panic
More
18 Sep 2020 07:37 #404 by Stefano82
Hi Hugues

A new version of Voyager that correct the bug noticed was released, it can be downloaded from the following link

forum.starkeeper.it/t/voyager-2-2-10-rel...uild-2020-06-03/1614

Best regards

Stefano
Avalon Instruments Team

Please Log in or Create an account to join the conversation.