Great work! (both for dokeeffe but also for all the people involved in indi/ekos)
Jasem, some years ago I used to do photometry (both exoplanets and variable stars) with gcx:
(cmatei tried to add some INDI support but I don't know the current state)
Anyway, the first link contains a lot of documentation and all the math involved is sound and well described.
The log says:
[2017-11-20T13:58:02.175 CST INFO ][ org.kde.kstars.indi] - MoonLite : "[INFO] Error retreiving data from MoonLite, please ensure MoonLite controller is powered and the port is correct. " [...] [2017-11-20T13:58:07.455 CST DEBG ][ org.kde.kstars.indi] - MoonLite : "[DEBUG] Connecting to /dev/cu.wchusbserial1410 " [2017-11-20T13:58:07.457 CST INFO ][ org.kde.kstars.indi] - MoonLite : "[ERROR] Failed to connect to port (/dev/cu.wchusbserial1410). Error: Port failure Error: Resource busy. Check if device is connected to this port. " [...] [2017-11-20T13:58:07.455 CST DEBG ][ org.kde.kstars.indi] - MoonLite : "[DEBUG] Connecting to /dev/cu.wchusbserial1410 " [2017-11-20T13:58:07.457 CST INFO ][ org.kde.kstars.indi] - MoonLite : "[ERROR] Failed to connect to port (/dev/cu.wchusbserial1410). Error: Port failure Error: Resource busy. Check if device is connected to this port. "
I think something else opened the serial port before the indi driver, have you disconnected the arduino serial monitor before starting indi/kstars?
I also like a lot the idea but it would be nice to use the INDI logo instead of the ASCOM one... I don't know how enforceable are the ascom guidelines (see below) but surely it isn't fair to use it.
still great work!
I wish you clear skies, and don't forget to post your setup here when you'll be happy with it: indilib.org/forum/general/1014-post-your-indi-setup.html
Your reasoning is reasonable, and in theory you could just use one single reference object. But in practice DSOs are different from each other and have different brightness profiles, so I'd build a library of sample objects as you suggest.
(what I usually do instead is try with my "mmmh this should be fine" settings and see what I need to correct for that specific field I'm capturing at the moment)
And also, as usually we try to make pretty pictures, you have to consider field stars to avoid pixels blooming: stars are brighter and smaller than diffuse objects (so, for example, I ramp up exposure time until stars get worse). See en.wikipedia.org/wiki/Surface_brightness#General_description
Or some kind of electro-mechanical interlocks... Last year with some friends I made plans for an automated observatory and we thought about some kind of slipping cover that could be closed by its own weight in case of missing power.
Any news on this?
Just in case... a lot of time ago the main author of RTS2 (an open source autonomous observatory control system) wrote about porting the device layer to indi: http://indilib.org/forum/general/365-indi-autonomous-operations.html
a couple of months ago at the Italian Linux Day we did another talk about INDI.
WRT the last time the talk was scheduled in the afternoon so we planned to show a little ETX telescope and take some photo of the Sun with a Coronado PST. In the end the sky was cloudy so we did just half of the demo and shot some pic of the people attending with indi_gphoto_ccd.
BUT this time we have the slides!
(they are not very serious but keep in mind that the event was a lot less formal than the last time and we knew almost anyone attending)
Riccardo and Massimiliano