I believe that the 'parking the scope' function isn't working while in the following situation:
EQmod: Dome parking policy set to: Both
Dome: Telescope parking policy set to: Telescope locks
Dome is open, scope is unparked. I issue a park for the dome, in theory it should park the scope then park the dome. However this does not work as intended.
Dome: "2020-02-16T13:51:31: [WARNING] Cannot close dome when mount is locking. See: Telescope parkng policy, in options tab "
EQmod: "2020-02-16T13:51:21: [INFO] Mount is unparked. " <-- mount hasn't parked despite the policy set to Both
"2020-02-16T13:53:25: [INFO] Warning: Dome parking policy set to: Both. This disallows the scope from unparking when dome is parked, and tells scope to park if dome is parking. This will disable the locking for dome parking, EVEN IF MOUNT PARKING FAILS. "
Also tried with the simulators, it's not working.
Kstars Mac osx
Odroid C4 / WO Redcat51 / CEM25p / ZWO183MM / QHY5L-II-M (OAG) / ZWO mini FW
Ok I can confirm this... do we have a matrix of the different combination of the policies between the two devices and what they can lead do? If not, it would be greatly appreciated if you can draft the the table for this to clarify it for us and end users.
As a late follow-up on this topic, I am about to complete my clamshell KStars/EKOS/INDI controlled observatory (based on Gonzothegreat), and wanted to test the appropriate mount and dome policies to make sure that no mount and dome collision would happen. I used the Dome Scripting Gateway driver.
As the mount unpark was working correctly when both mount and dome were parked, I only tested dome park when mount was not parked. I positionned the mount close but not at its park position such as if the dome was closed (parked) no collision would occur.
I tested the following 2 conditions:
1. Mount Locks - Dome Both
After issuing a dome park command, the dome parked first and the mount parked after the dome was closed. So, unless your mount is in a position that would avoid collision, there will likely be damage to mount and scope, as mentionned in Gonzo's case study.
2. Mount Locks - Dome Locks
After issuing a dome park command, the dome parked first and the mount did not park after the dome was closed, it was still tracking. as in the previous case, unless your mount is in a position that would avoid collision, there will likely be damage to mount and scope, but furthermore, as the mount is still tracking, damage will ultimately occur.
I understand the mount should explicitely be parked before the dome is but I assume the safest sequence should be that if a dome park command is issued, it should make sure that the mount is parked first before parking the dome, and if not, it should tell the mount driver to park the mount before it parks the dome. I realize the the python scripts may need to do the appropriate checking but I thought that INDI was taking care of that.
Is the code related to parking policy in the specific mount and dome drivers (i.e. lx200_OnStep and Dome Scripting Gateway in my case) or somewhere else in the indiserver? Had a look in dome_script.cpp and lx200_OnStep.cpp but did not find anything obvious regarding parking policy.
Ok, I think we need to come up with a matrix of all possible actions and what needs to be done between the dome/mount so that it can be coded safely to handle all possible conditions . Maybe a google sheet?
I think that if we want to come up with a matrix of all permitted combinations, we need to also specify a dome/roof type as, depending of the type, parking will either likely cause damage (roof, ROR or clamshell) or not (hemispherical dome, where there is no mount movement restriction) and as such parking policy combinations may be allowed or not (e.g. for a roof the combination "Dome Locks - Ignore Telescope" shall not be allowed). That also means that the DOME driver will need to have a DOME type option added. Does that make sense to you?