SkySafari's Celestron CGEM driver.

So I just tried to run EQMod using ser2net and it worked right away without any issues (using new code in INDI, not yet available in PPA). I tried to connect from SkySafari but it doesn't have EQMod so I couldn't check there but I would guess it would work since the port was working fine. Hopefully when I'm done testing this, it will go back to INDI and you'll see the changes.

Great news! If you wish me to test let me know.

Having these two work together would be excellent and I will help where possible.

Thank you Jasem

Tried the connection via tcp/ip to ser2net with the CGEM via the update tonight.

There is a connection. The RA/DEC cannot be retrieved and there is a park error.

Attached is the logs I could get. If there is a better way to provide the logs please let me know. .

also regarding , thing worked well with ASI cameras after tonights update - Thank you.

Please try to update again and see if it works.

A quick test and thing seem really good:

- connected to ser2cat via indi
- disconnected
- connected via skysafari
- disconnected
- connected back with INDI

Question: once guiding and imaging, is it reasonable to disconnect and switch between indi and skysafari to check positioning as long as no slewing or such is done?

I will test some more tomorrow, and also see if I can connect both at same time.

Thank you very much the new function!

There may be an issue in the tracking.

Choosing track on, say M51, does put the telescope on M51. M51 would eventually move out of view which it did not do before.

I my have had time wrong between the CGEM and the RPI3, and need to test again tonight.

Otherwise, the switching between Skysafari and indi seemed to go fine.

Thank you

The connections worked the other night.

Not sure if I ran into a related problem though.

Kstars is reporting a 1 hour time difference compared to the CGEM, and the RPI3 command line.

Specifically:

- CGEM is configured with Long/Lat, current 24h, zone, and DST for the current time
- RPI3 is booted and used to get time and location from device
- Command line - date - reports correct time
- viewing time on Kstars is one hour in future.

It is not clear if this is due to the TCP/IP connection to port. I doubt it though.

iOS/Mac devices though do not update Nexstar when connect. This problem was found earlier and fixed.

Actually, thinking about it, I just did a quick test:

1. rebooted RPI3
2. Not connected to mount
3. connected to RPI3
4. update date: sudo ntpdate -v time.nrc.ca
5. date - displays current time
6. Kstars - displays time one hour in future

Ideas?

Maybe edit your geo location and change DST offset in KStars?

That I think is it. The Geographic... settings for DST rules do not have one that matches what happened in Canada this year. In Canada we changed DST on March 18/19.

I will jig the settings to get it to match, as I cannot find one that does, by temporarily changing time zone.

Thank you.

KStars uses still a custom TZ file for time-zone and not the system stuff. This is what we have now:

#"US": DST starts on the first Sunday of April, reverts on the
# last Sunday of October (2:00 am). Canada uses this
# rule as well.
US Mar 2Sun 02:00 Nov 1Sun 02:00

EDIT: The KStars rules are outdated. Maybe they should be dropped. If you choose NO DST rule correction, KStars date/time are correct and match the system's?