I went through the logs with a fine comb and couldn't see anything that would stand out as an issue; however one thing stood out that was strange.
My Voyager software logs showed a park command issued that was 17min different to the ascom logs. Ahead of time.. not sure what that entails. RTC issue, something else.
2022/01/13 03:29:54 105 - INFO????? - [ParkMount??????????????????? ] - [PARK_Code??????????????????????????????????? ] - Mount Parking ...
2022/01/13 03:29:54 301 - INFO????? - [ParkMount??????????????????? ] - [PARK_WAIT_Code?????????????????????????????? ] - Mount Parked
ASCOM.Gemini Telescope .NET.2022.278060.txt:03:12:00.007 Serial received:????????? TID:11 [0]: :h?, 0
ASCOM.Gemini Telescope .NET.2022.278060.txt:03:12:02.229 Serial received:????????? TID:11 [0]: :h?, 0
ASCOM.Gemini Telescope .NET.2022.278060.txt:03:12:04.443 Serial received:????????? TID:11 [0]: :h?, 1
ASCOM.Gemini Telescope .NET.2022.278060.txt:03:12:06.672 Serial received:????????? TID:11 [0]: :h?, 1
ASCOM.Gemini Telescope .NET.2022.278060.txt:03:12:08.898 Serial received:????????? TID:11 [0]: :h?, 1
I will try again from complete cold start after powercycling the mount, and keep testing.
After each night, I do disconnect from the mount after session ending. But not sure that this would cause some issue if the mount is still powered on, and the driver is establishing a new connection.
I will test again without disonnecting the ascom driver from the mount and see what happens as well.
