I run KStars/Ekos/Indi all on a Raspberrry PI (in fact, running StellarmateOS on it). I typically image at home, but recently went to the GSSP star party
goldenstatestarparty.org/ which was great, but a remote site. In all cases where you drive 6 hours to setup your telescope, something is bound to go wrong. Here's what happened to me:
In my case, all worked except for plate solving (the alignment module would not figure out the coordinates of the image taken). It took a while, but I finally tracked this down to "the computer had the wrong date and time". It was 2.5 days off. I guess the Raspberry Pi doesn't keep the time, and when I image at home it picks up the time from my network, but when I imaged remotely, perhaps it used last time it was running? Once I realized what the issue was (an hour later), a quick 'sudo date -s "month/day/year hour:minute"' worked and all was good. Of course, from now on, when I image remotely, I'll check and set the time at boot.
My suggestion:
It would be great to detect when the system time/date is unreliable. KStars/Ekos could warn on that, as I imagine I'm not the only one who's had this happen to them.
I would think the OS "knows" if it have gotten the time from the network, or if it's just relying on the last time saved from the last time the OS ran (which would be unreliable).
I don't know if the OS releases this type of info.
Thanks for listening,
Hy