I'm developing a driver for my home-grown Dome-control hardware; and I have reached a point of confusion.
My driver works on Ubuntu, where the dome interface is in the single Dome class (file indidome.h); This matches the online doc www.indilib.org/api/classINDI_1_1Dome.html
On raspberrry pi my driver does not work. I notice that here there is an additional DomeInterface class, (in file indidomeinterface.h).
NOTE: 1. I have the latest raspberry pi download of indi-full.
The question is, would some kind and knowledgeable person please offer me some guidance? Is there some doc for the RPi implementation?
Dome driver working very satisfactorily with simulated hardware. The only loose ends I have to get my head around are parking and homing. Apropos homing, I find that the property DOME_PARAMS=>HOME_POSITION appears to be missing from the latest RPi distribution (2015-09-16 22:02:27). Should I be implementing this property or is it to be included in the dome base?
NOTE: I really like KSTARS/INDI and the way the system is evolving. Up front It provides such a lot of essential support and is excellent to extend. With this platform I now (finally) see my way clear to progress quite quickly from manual observation, to remote, then to fully-unattended operation.
1. Implement homing in the UnPark() call, as tools like Ekos expect that after a dome is "unparked" then it is ready to go.
2. Store the home positions in the Presets group (If you have relative/absolute dome positions). Then just click on the preset to go to the home position.
Gonzo might share his dome implementation, he already has it working on the hardware level.