Slewing to Home position before parking was part of a script routine I was running. I'll remove Home slew command and just run park command.
I will collect the logs and share on dropbox if you wish to go through and see if you can decipher what might be causing it.
I'm referencing the serial commands from manual:
From what I can see only the driver can set the park position ? I'm missing what the serial commands are to do so here to the mount. Or is it the case where the driver does not set the command to the mount where the home position is? Does the driver store the parameters of this position?
On Fri, 14 Jan 2022 at 02:15, Brian Valente <brian@...> wrote:
>>> I'm experiencing the same issue after running the mount in a remote installation. I'm becoming more confident in that the mount just isn't cutout for this work. Bugs everywhere..
?
?
Daniel I run 4+ Losmandy mounts remotely , virtually every night, unattended and powered on 24/7. I don¡¯t have any issues with parking, as I must park each mount at CWD every night, and startup from CWD as well (power is left on, so I¡¯m not restarting the mount every time. I do power cycle the entire setup from time to time)
?
Of course I¡¯m not there with you so I can¡¯t see what exactly is happening with your mount, but based on some of the things you mentioned, it¡¯s worth looking at how you are using it with Voyager.
?
Better yet, if you have ascom and voyager logs from any of the times that behavior has happened, that would be ideal. Data is always a great help to hunting down questions
I'm experiencing the same issue after running the mount in a remote installation. I'm becoming more confident in that the mount just isn't cutout for this work. Bugs everywhere..
With the mount powered on for two days, it's suddently not able to park to CWD. I have been powering on from CWD, Cold Start. I will plate solve and sync to 4-5 stars covering the West/East of the Meridian and then do my imaging run, which does it's own plate solve and sync on repositioning during the imaging run.
For two days it has finished the session, run the HOME command, then PARK command. And everytime it slews to CWD position and goes into Park mode. Now just on the third night.. at the end of the session, HOME command just stopped the mount in it's last position when the last image was taken; pointing at the Western horizon and parked itself in the same position. If I unpark, then from the Gemini.net hand controller go to Park at CWD, it just parks itself in the same position.
Is there a limit to the amount of saved positions in RAM. I'm wondering if the saved position for Park mode is being overwritten, or returning null. I need to go through the logs later and see if I can work out if it's something obvious or not.