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.
Interesting, I would have never figured that out. When I put all the correct information into my mount, UTC offset -6 for Central Time (Houston Texas). Currently observing DST (DST On). KStars somehow is off by 1 hour. So I have to turn DST off on the mount, then Kstars displays the correct time. So maybe Kstars is adjusting for DST itself?
I should have mentioned too, that I don't auto connect. So the log should show the time. Just search for UTC, and you'll find where it gets the time from the mount. I thought I quoted the relevant line in that post with the log unless that was something else.
Yes, this seemed obvious to me. But that's not what it's doing. The mount Offset is -6. That's one setting. Then there's a separate DST setting to Yes or No.
When DST is set to Yes, he mount's clock represents this correctly. But the offset in the mount is still -6.
So the internal mount clock is only for display purposes in the hand controller. And the mount information is not determined by that, but by the actual UTC time (it says this in the manual). So I have to operate the mount with incorrect settings (no DST), and the hand controller shows the wrong time, but EKOS now has the right time.
Yeah, this is correct. I just brought in all my equipment as we're about to have another hurricane in our area. But I'm going to test every parameter around time, and see what comes into EKOS from the mount with each option just to confirm everything before any changes are made.
Despite using the settings I prescribed above, and having the correct time in EKOS as pulled from the mount, my meridian flip went early about 1 hour, so something is still not correct.
Of course, if I make EKOS the master time keeper, everything works as planned. It's only when I make the mount the time and location master that things go wrong. Pointing accuracy is hurt when I sync time and location to the mount, so do need to get the issue sorted out.
I'm not sure if this issue still exists. I've not had it myself. I have no MGPBOX or GPS and use the 'kstars updates time' setting.
If ppl still have this issue then next to Jasem's enable debug log before you connect post earlier in this thread is a good place to start, and maybe this helps for those that are not afraid to telnet to an API :
The 10micron API can be reached on port 3490 as follows :
telnet <your mount IP address or DNS name> 3490
here you can give commands to the mount, like 'what is todays date' and I've added my mounts' responses so you have an idea what format expect
or what is your timezone offset ?
or what time do you think it is now ?
Maybe this helps anyone in finding any discrepancies.
I know this is an old thread but wondering if this was ever resolved. Previously I had my 10micron updating kstars and it all seemed to work. After updating kstars to 3.5.9 on ubuntu linux I now seem to have kstars time offset by 1 hour from correct local time and meridian flip is messing up. It seems OK if I set kstars update mount. I have also seen it suggested to not have mount and kstars trying to sync time and let GPS set mount independently of kstars. What is the currently understood best way to do this?
Borg 107FL on RST-135 + QHY268C, Astro-Tech AT130EDT on GM1000HPS + QHY600PH Chroma LRGBHSO; IR Guiding WO Uniguide 50 & QHY5-III-462C ASUS PN51 and Mele Quieter 3 ubuntu, kstars/ekos, & firecapture; Pegasus PPBA; WO Redcat, Skyguider Pro RT90C, Canon 7DmkII, rPi4/stellarmate
The way I manage this is by setting the Linux box time upfront (I'm using RTC) and making sure it is updated, then I run KStars and it is set up to allow KStars to control the time and location of everything else (e.g. the mount)
C9.25 f/10, HEQ5, MyFocuserPro2, OAG, ASI174MC guide, ASI533MC Pro