Ferrante Enriques replied to the topic 'Indi-dome-scripting' in the forum. 2 years ago

hi Gunter,
in my case (it's a roll off roof, not a dome) abort.py is meant to immediately stop the roof motion.

About the state, what kind of communication you have from/to the device? I mean it's over http, local serial/usb port?
If it's http for example, status.py could be used to poll the device status as the protocol is asynchronous and to update the /tmp/indi-status file.

As these template scripts are executed outside of Ekos, any return value like the parking status (roof open or roof close) must be send to Ekos in some way.
In park.py, if parking is successful, the file 'indi-status' stores the value '1 0 0' ( '0 0 0' if roof open) then Ekos reads this value and so is aware of the parking status.

Btw if the protocol is http  I found more efficient that status.py periodically read/write the /tmp/status-indi while park/unpark/abort just manage to issue commands to the device.    

If you want a more stable integration of your device (roof or dome) with Ekos consider writing a new INDI driver and not to rely on these scripts only*. My approach (it's the third time so far)  is to use the scripts at first and in the meantime write and test the INDI driver. 

* one big  issue with the scripts (in the roof case) is that only parked / unparked states are sent to Ekos. There's no way as far as I know to tell Ekos that the roof  is moving opening or closing etc. 
Ferrante

Read More...