That looks like a problem with DST in your mount. Is DST set to Y?

You may have to offset UTC by 1 in your Control panel to compensate for DST.

I think I just got to the bottom of this. It is related to DST, but it doesn't make any sense.

In my original post, I had the mount running purely on UTC time with no offset for my local zone, and daylight savings time off.

EKOS should have read that across exactly and applied UTC time but looks like EKOS was somehow compensating for DST by adding an hour.

The only combination I was able to get to finally work correctly is to set UTC time on the mount to -6 (Central time zone US). Daylight Savings time off.

Now EKOS and the mount show the same time. Somehow EKOS detects whether or not DST is in effect in your local area regardless of the time the mount sends. If I set DST on in my mount, then my mount feeds EKOS with the DST time, and EKOS compensates by adding an hour thinking it is correcting for DST time.

The correct combination of all settings in the mount, produce a problem in EKOS because only the time is sent over from the mount, and not the DST status, and it looks like EKOS is applying the DST status to the time it gets from the mount.

I have the same issue with my CEM25p, there is one hour difference between the mount set with DST:N and Ekos, same thing as you "I have KStars/EKOS set to get updated by the mount"

Check your location settings in Ekos and make sure that DST is switched off there. I don’t think this is a mount problem.


Wouter

Mine turned out to be KStars had the DST rules for my geographic location incorrect, I just made a copy of my location and put -5 hrs instead of -6 that was the rule in KStars. Fixed the issue.

It's pulling the location from the mount, and clearing out the location settings I manually put into KStars.

Maybe open a new topic here describing the issue for your location so it can be fixed? I did the same for my location a few months ago and Jasem fixed it right away.

What's the rule that requires fixing?

Mine was McAllen, Texas USA - Central US time zone.

What I discovered through my own trial and error is that the only things that sync from the mount to KStars is the actual UTC time (with no offset and no DST setting), and your GPS coordinates. It appears KStars then knows based on your location what offset and DST to apply to your current location and then corrects the time.

This means that if I plug in DST settings into the mount, KStars doesn't know that there is a DST set, because it thinks it's only getting the UTC time, and it offsets the time by DTC even though you've already done it in the mount now making KStars have the wrong time by one hour.

I don't know if this is driver dependent or not. But that seems to be the way the 10Micron driver works. It could be different for other mounts.

The rule is correct for McAllen. It's -5 now, and in the database it's -6 (RAW without DST correction). So mount should report -5 which is sent to Ekos. Ekos checks DST is on and subtracts 1, so we're back to -6 which is set as the RAW uncorrected offset (TZ0).

Andrew, so 10Micron uses LX200 and it queries <strong>Local</strong> date and time, then using the offset received from the mount, it generates the UTC time. If you turn off auto connect in your equipment profile, this allows logging to be enabled before connection to the mount is established. Then connect by pressing "Connect" and then the log should show what time/offset are received from the mount itself. The log you attached doesn't show this info yet.

Ok, I will check my mount, and make sure the DST is set to off.

I recently did a firmware update to my mount, maybe it set it to on.
Thanks for your hard work on all this, (I see you guys are doing lots of changes on invent.kde.org, lots of great stuff happening!)