Hi, hot on the heals of getting the C2 ATIK drivers working.. I'm trying out the idea of using the ODroid SHOW2 TFT screen as a status screen on the scope. Literally this will be attached to the scope in the box with the C2.
Is there anyway I can get the guider images being taken, the focus FHWM, the RA & DEC, focus, connection state etc from the components on the INDI system?
I've included a test image - using a real open phd 60x60 guider star image just to demonstrate. I'll then want to create a C/C++ component that sits on the C2 and through a connection with INDI accesses the current state of the system.
I'm thinking of ideas such as disconnects to cause the screen to flash red for example so it's happily running I don't need to do anything.. infact it could cycle around including displaying the last sub taken (scaled), the current focusing image etc. IF it can get to the info!
1. KStars INDI DBus (but this assumes that KStars is running on the target device.
2. PyINDI to act as the client to get whatever data you need from the driver.
to any property status and value.
Good point on the KStars running. At the moment I'm running one C2 for Kstars + Ekos + INDI + astrometry.net. The automation project (power and network hub) has the space to split off the INDI and the astrometry.net onto a second C2.
indi prop sounds like a decent way to get that data although it would be polled rather than pushed. The TFT isn't really fast enough to be a replacement screen so I think this would work.