It hurts me to say this as an IT engineer, but Ekos/INDI caused me so many issues that I entirely stopped using it and moved back to windows and NINA.
I tried for about 2 years before I pulled the plug about 6 months ago.
NINA works flawlessly, its scheduler is much robust and can handle any given scenario. I also love the fact that you can edit the sequence while it is running. Last but not the least, NINA starts exposing next image as soon as the current one is downloaded whereas Ekos waits until it has streched it and analyzed what it need to. As a 6200 owner this was a big issue on the RPI4 I used for Ekos, overall I take much more images per night with NINA.
My current sequence in NINA is an all year sequence with 3 groups:
- Moon nights with moon down
- Moon nights with moon up
- New moon nights
My opinion is that Ekos suffers a lot from its multiple state machines architecture. Also I believe bringing it at Google summer camps to have it amended by students not knowing the first thing about it or astronomy might also add more issues.
I know you have been involved in the INDI driver for gemini L6 and that makes it even harder to move away. But I can only vouch for NINA. Since I switched to it I can concentrate on what matters, not making sure it works as expected.
Again as an IT an engineer I would have never thought I would have advised people to move away from Linux for increased stability.
Carl
toggle quoted message
Show quoted text
On Fri, Mar 3, 2023 at 04:29 PM, Jamie Amendolagine wrote:
I take back my recommendation. I tried it (rpi4) last night and had quite a struggle working around all the bugs -- mostly in the android app. It's a shame, especially since Jasem has put so much effort into the entire stack. The free part of the stack works great, but the pay part, not so much...?
Jamie
