Rudolphe, this is some data for you. I am using X2 plugin. I tried to park my dome last night and it executed the park command, the dome moved to location, but then it immediately tried to return to sync with the telescope. I hit the abort button to stop it moving and it did for about two seconds then insisted on going to the scope position. The MyT Mount was at home position with tracking off at the time.
I realized that the dome was coupled to the telescope under the dome setup tab. So I uncoupled and then the park was successful. Same with abort.
I thought I might recommend that if a park or abort command is sent that the driver should uncouple the dome from the telescope. If parking then the user probably doesn’t want to continue tracking the scope. If abort then the user probably sees a problem with where the dome is going and just wants it to stop moving completely. I could see that there could be a safety issue with equipment or something if the dome continues to insist on coupling to the scope and moving after an abort.
just thought I would give you a data point. Otherwise I prefer the X2 over the ascom driver because it stays on track better. Thanks for all your work.
I can confirm the issue is the built in retry on homing. This was added for the old firmware as the homing was often passing the home sensor and then reporting it had stopped and was not on the home position so the plugin was doing 1 retry to get to the proper home position (as this was a small move at this point).
Now when you abort, it retries and if you abort again when it restart it will stop for good.
I'll remove that retry and will build a new plugin