Bug 409125

OK, I'll do my best.

The buttons for moving the dome and one for abort is more or less straight forward. But what functionality do you expect from the slaving button? 

For me it looks like it is OK when slaving is set up in the INDI configuration (as well as snoop devices etc). Or do you want to be able enabling and disabling slaving during runtime?

I own a dome : This means that the scope must always match the dome aperture orientation.
The dome parameters can be set in the INDI Control Panel.
However after numerous trials I could not succeed to enter the right dome parameters which would align the scope and the dome aperture in all part of the sky.
This is why I need to correct sometime the dome position with the buttons CW and CCW.
But the dome being slaved, it doesn't like that and return immediately to the calculated position (which I don't want).
Thus if a correction is made with the buttons CW or CCW the dome must be unslaved.
Having all these buttons in the new Observatory module would allow to control the dome within EKOS without using the INDI Control panel.

Jean-Claude,
I need you help for testing, since I am not sure whether slaving is working appropriately. Could you please check out the branch observatory_work_motion from my kstars clone:
https://github.com/sterne-jaeger/kstars/tree/observatory_work_motion

I am testing with dome simulator and telescope simulator. When I turn on slaving, the dome moves to 270° - no matter where the scope is pointing to.

Hi Wolfgang,
I'm sorry but I can't help you with code.
However if you live in Europe or a have compatible UTC, you could play with my whole setup through a TeamViewer session.
My private mail is jcjesior at free.fr

Sorry, I misunderstood.
I tried KStars 331 with the scope simulator and the dome simulator.
I slew to several targets and the dome followed as expected.
Here is the INDI Control panel info :
2019-07-02T19:23:21: [INFO] Dome reached requested azimuth angle. 
2019-07-02T19:23:19: [INFO] Dome is syncing to position 137.647 degrees... 
2019-07-02T19:23:19: [INFO] Dome is moving to position 137.647 degrees... 
2019-07-02T19:22:59: [INFO] Dome reached requested azimuth angle. 
2019-07-02T19:22:44: [INFO] Dome is syncing to position 173.043 degrees... 
2019-07-02T19:22:44: [INFO] Dome is moving to position 173.043 degrees... 
2019-07-02T19:22:19: [INFO] Dome reached requested azimuth angle. 
2019-07-02T19:22:18: [INFO] Dome is syncing to position 340.718 degrees... 
2019-07-02T19:22:18: [INFO] Dome is moving to position 340.718 degrees... 
2019-07-02T19:21:54: [INFO] Dome synced to position 319.961 degrees. 
2019-07-02T19:21:54: [INFO] Dome moved to position 319.961 degrees. 
2019-07-02T19:21:48: [INFO] Dome reached requested azimuth angle. 
2019-07-02T19:21:20: [INFO] Dome is syncing to position 325.406 degrees... 
2019-07-02T19:21:20: [INFO] Dome is moving to position 325.406 degrees... 
2019-07-02T19:21:10: [INFO] Dome reached requested azimuth angle. 
2019-07-02T19:20:39: [INFO] Dome is syncing to position 29.9402 degrees... 
2019-07-02T19:20:39: [INFO] Dome is moving to position 29.9402 degrees... 
2019-07-02T19:20:39: [INFO] Dome reached requested azimuth angle. 
2019-07-02T19:20:35: [INFO] Dome already unparked. 
2019-07-02T19:20:05: [INFO] Device configuration applied. 
2019-07-02T19:20:05: [INFO] Dome is syncing to position 344.32 degrees... 
2019-07-02T19:20:05: [INFO] Dome is moving to position 344.32 degrees... 
2019-07-02T19:20:05: [INFO] Auto park is disabled. 
2019-07-02T19:20:05: [INFO] Auto search is enabled. When connecting, the driver shall attempt to communicate with all available system ports until a connection is established. 
2019-07-02T19:20:05: [INFO] Auto search is enabled. When connecting, the driver shall attempt to communicate with all available system ports until a connection is established. 
2019-07-02T19:20:05: [INFO] Loading device configuration... 
2019-07-02T19:20:04: [INFO] Dome is unparked. 
2019-07-02T19:20:03: [INFO] Auto search is enabled. When connecting, the driver shall attempt to communicate with all available system ports until a connection is established.

I understand what happened : you didn't set the Measurements in the Slaving tab !
If all parameters are = 0, this will result in :
2019-07-02T19:39:29: [INFO] Dome reached requested azimuth angle. 
2019-07-02T19:39:22: [INFO] Dome is syncing to position 270 degrees... 
2019-07-02T19:39:22: [INFO] Dome is moving to position 270 degrees... 
2019-07-02T19:39:22: [INFO] Dome reached requested azimuth angle. 
2019-07-02T19:38:48: [INFO] Device configuration applied. 

Please try my measurements :
• Dome geometry (KStars)
- Autosync threshold (deg.) = 0.50°
- Radius (m) = 1.150 m
- Shutter width (m) = 0.600 m
- N displacement (m) = 0.120 m
- E displacement (m) = 0.100 m
- Up displacement (m) = -0.217 m
- OTA offset (m) = 0.405 m
With the dome simulator you will not need to set :
- Home + Park azimuth = 73.00°
- Ticks per turn = 357

Please tell me if it helped.

Ah, I found the problem. In my simulator setup, I had dome radius etc. all set to 0. When I set the dome radius to 5m, it's working fine.

OK, should be ready for testing. I posted a new diff:
https://phabricator.kde.org/D22224

As I wrote earlier I'm not competent to test the code but if you want to test it on my equipment you're welcome.

Should be in one of the nexts nightly builds.