On Sun, May 19, 2024 at 07:04 PM, Sean wrote:
On Sun, May 19, 2024 at 07:50 PM, Chip Louie wrote:
I know you think the Gemini 2 controller has been correctly configured but everything you are saying indicates there is a time and coordinate error. If the Gemini 2 wakes up and knows where it is on one side of the pier after you do a single star alignment on that side of the pier the issue sounds more like NINA or ASCOM is updating the time and location data without your knowledge. I have not used NINA in quite sometime but this sounds like a commonly heard complaint by NINA and Gemini users. Do a search here and maybe on CN and see what you find. It is usually some checkbox that allows an application or ASCOM to update Gemini data.?
When you connect to the mount with NINA it will prompt you if the settings do not match, and I can select to either use the mounts or NINA's settings. Now you may be on to something here.?
- When I connect NINA I get error "The mount's clock differs from the computer clock by 73959 seconds...", that is 20 hour difference.??
- Web UI State: UTC Date (dd.mm.yyyy): ? 20.05.2024 UTC Time: 01:51:46 which is correct ( UTC: Monday, May 20, 2024 at 1:51:27 am ? Minneapolis (USA ¨C Minnesota) ? ?Sunday, May 19, 2024 at 8:51:27 pm ? ?CDT ? ?UTC-5 hours)
- NTP server tested. Set time to 20:42. After change was set I hit NTP Query button and it updated to 20:46 (which was time Windows on my screen). I did login to the server running NTP (Chrony) and checked, time is accurate.
So hand controller, web UI all show "correct" time. On a whim I opened ASCOM Device Hub and connected the Gemini mount. I then connected to Device Hub in NINA and did NOT get the error. I disconnected and then reconnected and this time NINA did not throw an error about the time difference. Next chance to see and test won't be until Wednesday if I am lucky.
You have to pick a time and location reference and propagate these reference points across ALL apps and devices. IDK if you are connected to the internet when you are imaging but if you are you should pick a single NTP server and use it across all apps and hardware. The Gemini can sync on an NTP server if you provide an IP for Gemini to sync on. Of course this only works for those using an Ethernet connection that occasionally gets on the internet. Just pick one and use it across all devices and apps.
IDK how NINA works with respect to UTC but if you can use UTC the Gemini will be very happy to use it as the time reference. I use UTC and offset -0 when using the GM8G visually with a planetarium app and the Gemini GOTO works great. With the ASIAIR on the G11G I have no choice but to use local time and it is always off by one hour but it works fine. The GOTOs commanded by the ASIAIR to the G11G are always almost perfectly centered and plate solving to center works 100% reliably even with the wrong time for some reason. But this is a known issue with ASIAIR that has been there since the beginning and never resolved.??
Try turning off everything that automatically reads and populates time and location data. If you can set the time and location manually for everything. I think it can be done but it only works if carefully configured and you understand what impacts what when.
Keep us posted on what you learn, especially if you figure it out!? ??
--
Chip Louie Chief Daydreamer Imagination Hardware?
? ?Astrospheric Weather Forecast - South Pasadena, CA?
Chip Louie