I have KStars set up to pull time and location off my mount, whose GPS is set for my 6-hour UTC offset and so reads out in local time.
However, I notice that KStars always puts log entries and the like in UTC, though it appears to think that's local time. Maybe this is why plate solving is goofed sometimes, and the mount tends to hare off into La-La Land?
At any rate, how to I get KStars and Ekos to actually believe the UTC offset? I can tell the Pi to get its time via the Internet when I'm imaging at home, but that's no use in the field.
Thank you. The "LT" in the KStars time display is a little misleading in that respect! If I just do everything (e.g. scheduler) in UTC I should be OK, then.
I had to deactivate pulling the location from my CEM120 mount - it does not work. It works on the CEM25 I own, but not the CEM120. I'm not sure what gets messed up but the location is WAY off and I had to keep resetting KStars manually after it pulled the incorrect data from my mount. Oddly, I would manually enter the data that comes from my mount handset, so the mount's GPS is correct - but something gets messed up in the transfer.
But when I pull data from my CEM120 mount, the TIME is correct, but the LOCATION is so far off that the LOCAL date shifts ahead to the next day!
For some reason, on the CEM120 driver, the location's LONGITUDE does not get converted properly. The latitude is correct, only the longitude is messed up. I have to go back into Kstars and simply change my location back to my actual location (using either the map, or the exact longitude data from my mount's handset) and then the time gets shifted back properly. I've mentioned this before but there's been no action on it.
Huh. For me, if I set KStars to the correct local time, the sky is off by six hours (my UTC offset). If I set it to UTC, everything is hunky-dory. It's not just the planetarium that is incorrect, Ekos is too if I use local time. Eg. I have to set start times for the Scheduler in UTC. Just figured that out yesterday, in fact.
I'm going to revert to my previous version of StellarMate OS for unrelated reasons, I'll see if the old stuff has the same problem.