I built a custom mount and wrote custom driver software with a GUI to run it on a Raspberry Pi 4. So far, so good, but I am now in a predicament where I must choose one thing or the other.


The unforeseen event which put me in this predicament is finding out that my ZWO 294 camera won't work on Ubuntu 18.04 (arm64) without Ekos. I suppose I underestimated the level of sophistication involved with these cameras.


My two choices are now:


1) Rewrite the custom driver in INDI format and abandon the camera functionality and the GUI, using kstars/ekos instead

2) Determine how Ekos makes the ZWO library work and integrate that functionality into my existing software


The easy route would be to take option number 1 -- however, I was planning on using plate solving as a fundamental component of the driver itself. For example, I was going to automate backlash measurements and correct for geometric error via a procedure involving obtaining true position by plate solving. I realize kstars/ekos has some sort of plate solving functionality, but it probably would not be easy to integrate with my reformatted driver. Or, would it?


Alternatively, I could dig through ekos source code and try to figure out how to make the zwo camera work in my homebrew software which is already pretty far along. I was using a makeshift camera for while to develop streaming and snapping pictures within the GUI beside the controls.


I'm curious which option you guys think I should choose and why. I realize how amazing kstars/ekos is, but my goal is to make a much simpler bit of software. That is the main reason option 2 is even on the table. Here is a screen shot indicating the level of simplicity I'm shooting for.