Re: Parking to Home position failing
|
I have the driver park settings to "Slew to CWD before parking". I'm using Voyager Starkeeper software. At the end of my imaging run, I send a Home command that slews to CWD, then I issue Park command. I had a read through the manual at the serial commands, and it seems that a Home command will default to the CWD position, unless it's been overridden.
I will look through the logs afterwards to confirm these commands are being transmitted/receieved correctly. Everything for the past two nights, has worked flawlessly. For the past few weeks testing things, it seems that if the mount is left powered on for more than 48hours, strange things start to happen. Even worse if I Warm restart.
On Thu, 13 Jan 2022 at 19:42, Paul Kanevsky < yh@...> wrote: Daniel, Before speculating about bugs, RAM size, and null pointers, let's first see if we can find a simpler explanation. How are you issuing the park at CWD or at Home commands? Have you looked into the park setting in the driver that lets you chose where to park the mount? This is where you determine what the mount does when a park command is requested, and the wrong setting here can certainly result in the behavior you describe. For example, first option will park right where the mount is currently positioned, last setting will let you set an arbitrary Alt/Az position, etc: ? ??  If the mount doesn't remember the home position you've set, you may be losing settings between sessions.? Regards, ? ? ?-Paul On Wed, Jan 12, 2022 at 10:47 PM, Daniel Judge wrote:
Was this one ever resolved?
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.
|
