Do you have a link to this python class or some interface documentation? Our dome is working with an indi driver (still being written) and we're planning on buying a planewave, so this kind of interfacing might be 'enough' to integrate the two.
I posted some time ago about automating 2 ASH domes: old topic
For some reason I could not reply to that topic and it's now categorized under 'embedded indi' ?
Anyway, I have a Raspberry Pi running an Indi driver, talking to the encoder and the relays.
So I don't see any obstacles in finishing this project but there's one annoyance: I use
This might be related to the website work, but I just noticed that all google results I tried related to indi drivers are broken.
while debugging a new dome driver I was getting the: 'stderr EOF' error just after serial communication and thought something was wrong with the serial comms. Turns out I had to delete the .xml file corresponding to my new
driver in the ~/.indi directory. Would be nice if there was a bit more error reporting around this !
Maybe start by trying
which is (as far as I've understood, haven't tried it yet) a way to wrap ascom drivers as indi.
Won't let you get rid of windows but would allow you to go all-INDI. Correct me if ascom server doesn't work the way I think
What is it that you specifically need? The source code for the ASCOM driver?
I've met the author a few times so could ask.
Maybe he doesn't want to release the source but it doesn't hurt to try.
We're resurrecting 2 ASH domes which are more than 45 years old, and would like to automate the scope + dome using kstars/ekos/indi.
All motors will be original (after refurbishing), so the idea is to start/stop the dome using an arduino + relay board, and getting position information using an encoder on a motor axis.
Now for the indi question:
- is it possible to use one of the predefined indi dome implementations? I'm guessing encoder positions and start/stop dome movement isn't so uncommon.
- where is slaving support implemented, is this in kstars/ekos or in the indi driver, so in case I need to write a custom indi driver does this slaving logic need to be reimplemented?
- what's the most common way for indi to interface with the arduino, usb/serial/... ?
- any leads to similar projects?
More information on the space science center: