×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

Ekos, INDI, SkySafari, and NexStar

  • Posts: 333
  • Thank you received: 24
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.

File Attachment:

File Name: log.zip
File Size:10 KB
.

also regarding , thing worked well with ASI cameras after tonights update - Thank you.
7 years 1 week ago #15156
Attachments:

Please Log in or Create an account to join the conversation.

Please try to update again and see if it works.
7 years 1 week ago #15171

Please Log in or Create an account to join the conversation.

  • Posts: 333
  • Thank you received: 24
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!
7 years 1 week ago #15207

Please Log in or Create an account to join the conversation.

  • Posts: 333
  • Thank you received: 24
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
7 years 1 week ago #15289

Please Log in or Create an account to join the conversation.

  • Posts: 333
  • Thank you received: 24
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.
7 years 5 days ago #15551

Please Log in or Create an account to join the conversation.

  • Posts: 333
  • Thank you received: 24
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?
7 years 5 days ago #15552

Please Log in or Create an account to join the conversation.

Maybe edit your geo location and change DST offset in KStars?
Last edit: 7 years 5 days ago by Jasem Mutlaq.
7 years 5 days ago #15555

Please Log in or Create an account to join the conversation.

  • Posts: 333
  • Thank you received: 24
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.
7 years 4 days ago #15581

Please Log in or Create an account to join the conversation.

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?
Last edit: 7 years 4 days ago by Jasem Mutlaq.
7 years 4 days ago #15583

Please Log in or Create an account to join the conversation.

  • Posts: 333
  • Thank you received: 24
You have the rules right:

2 a.m. on the Second Sunday in March to
2 a.m. on the First Sunday of November.

I thought I read in the DST rule first sun in April for US.

Of course I also have a typo in the above as it was Mar 11/12 that time changed.

I will check again.
7 years 4 days ago #15585

Please Log in or Create an account to join the conversation.

  • Posts: 333
  • Thank you received: 24
Please know DST Rule link does say for US: 1st Sun Apr, Last Sun Oct. However, the rule you have above is correct.

I have reset the settings to my location, US DST rule, and proper timezone offset now and the time is correct in KStars. I can only assume I messed it up somehow in a reboot, or something.

Thank you for the suggestion to check this in Kstars.

I hope to image this weekend, and will report back as soon as I get to. Things seem to be going well though.

Last items for me are to confirm CGEM, Kstars, RPI3 all in sync with time, RA/DEC, and switching between INDI and SkySafari (when not imaging as imaging is INDI only). Then plate solving - which did work better and saved me last weekend.

Cheers!
7 years 4 days ago #15599

Please Log in or Create an account to join the conversation.

  • Posts: 333
  • Thank you received: 24
Well, I am hoping for some help determining the best Ekos/INDI settings, or steps to correct to ththe CGEM. The imaging session got cut short tonight, as there was little time to debug the time setting issue I have been encountering verse helping my daughter have fun.

The connect to the CGEM over tcp/ip seems to work, as does the connection to Skysafri. skysafari slew to Jupiter nad M13 beautifully.

The problem is that something is change the time on the CGEM TO 2018.

Below is my procedure. Tonight out at a dark site meant no internet to use a time server on RPI3.

1. Power up cameras, RPI3, CGEM, and dew heaters with everything connected.
2. Setup CGEM - long/lat, time and date
3. Align mount using auto two star
4. Mac connects to cameras for the alignment (have not figured out how/if I can use Ekos for the Alignmwnt yet )
5. Once all aligned, launch Eros/kstars
6. Disconnect INDI mount and connect skysafari
7. Connect mount in skysafari wilpthout changing date and time.
8. Slew to M66, disconnect, reconnect INDI mount
9. Notice time was set to July 2018...

Maybe I did not have too, but after checking CGEM and seeing it too was 2018, I powered off mount and tried again, only have it happen again.

I would like to have the RPI3 use the long/lat enter on CGEM as well as date and time.

Skysafari is set to not change these setting.

What is the right was to do this?
7 years 2 days ago #15664

Please Log in or Create an account to join the conversation.

Time to create page: 1.203 seconds