Hi,
I tried to search online without any real solution. I have the latest firmware on my AM5 mount 1.6.3. In my advance sequencer in NINA, if the safety monitor detect an issue I run the instruction to park the mount. The mount slews to the park position but the instruction in NINA keeps running until it says "Park cancelled". Is this happening to someone else? Do you know why this happens? And how can be solved? Please avoid answer like "go home" because it is a remote observatory so i need to put the mount in park position to avoid collissions.
Thanks in advance for your help
AstroHelmut23 Hi it seems that I have more or less the same problem as you have. At the end of a sequence I ask to park the mount and it ends with mount not parked after 10mn but when you look at the AM5 log it is "almost " parked with altitude very close to 0 but not exactly 0 something like 0.000xxx. I had no real problem with that but two days ago the park position was completely crazy with the scope upside down very close from a collision with the pier BUT the mount still reporting that it was almost parked and az 270 alt 0.000xx. The rest of the session was ok so I am really wondering how the viewed park position and the physical park position could be different after a complete session with good pointing and tracking.. CS Frédéric
More info about the verison of driver and firmware for each component: ASIMount -> firmware 1.6.3 ASCOM Driver for the mount -> 6.5.21 NINA version -> 3.1HF2 Ascom Platform -> 6.6 SP2 (tried also with latest 7.1)
I raised a ticket about this in February 2024. ZWO said that they would be working on a fix.
Someone on the NINA Discord said that ZWO had not implemented "AtPark" in their ASCOM driver.
I await an update (im)patiently!
They replied to me that in NINA 3.2 this behaviour should be fixed. I have not tried because 3.2 is the nightly version. When they will release the stable version I ll give it a try. In the meantime I implemented a custom function in NINA that after the park command checks every 5 secs if the mount has reached the park position.
I have NINA 3.2, the latest firmware and up to date ASCOM and the problem still persists..
Yeah, as of the end of March 2025, this hasn't been fixed. It's a simple ask, in fact, it should've been in the code at launch. Why even bother having a park position if the mount can't even confirm that it's parked? It's just novelty at this point.
@ASIMount@ZWO Any chance that the ASCOM driver could implement AtPark?
Internally the AM5n seems to know it is parked, but if that isn't exposed to ASCOM than the Park command in NINA just hangs forever.
[unknown] Hi it seems that I have more or less the same problem as you have. At the end of a sequence I ask to park the mount and it ends with mount not parked after 10mn but when you look at the AM5 log it is "almost " parked with altitude very close to 0 but not exactly 0 something like 0.000xxx. I had no real problem with that but two days ago the park position was completely crazy with the scope upside down very close from a collision with the pier BUT the mount still reporting that it was almost parked and az 270 alt 0.000xx. The rest of the session was ok so I am really wondering how the viewed park position and the physical park position could be different after a complete session with good pointing and tracking.. CS Frédéric
