×

INDI Library v1.9.1 Released (26 Jun 2021)

Bi-monthly INDI Library v1.9.1 is released bringing a few new drivers and improvements to existing drivers.

Using GPS with Astroberry 2.0.0

  • Posts: 197
  • Thank you received: 17
Hi Radek and Astroberry fans,
Trying to set up a fresh Astroberry installion to use with a GPS dongle. I checked that GPSD is running, so I edited /etc/default/gpsd to include DEVICES= "/dev/ttyACM0". The GPS signal is recognised in KStars/Ekos/Indi and updates the location and the time and date, which is fine for that session, but I would like it to also update the RPi4 system clock time. In another installation of KStars etc on the RPi4 using the AstroPi3 Raspian script, I have installed chrony. Should I do this also on Astroberry or did you envisage a different approach? Thanks, Ed
Currently running KStars/Ekos/Indi on a Raspberry Pi 4B 4GByte under Raspberry Pi OS thanks to Astroberry
Sky-Watcher ED80 Pro with 0.85x FR/Corrector with Canon DSLR and ASI533MC on AZ-EQ5 GT mount
Other Sky-Watcher scopes - SkyMax 150 Pro Maksutov Cassegrain and Explorer 150p Newtonian
1 year 7 months ago #46899

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

  • Posts: 1039
  • Thank you received: 130

I am using a GPS dongle with AB 2.0, and worked straight away no file editing needed, not needed to install any other software either... :)
Stellarmate OS on Raspberry pi4b
Skywatcher EQ8 pro, on steel pier
Takahashi FSQ85, FS60cb & Meade 8” SCT (de-forked)
Starlight Xpress SXVR H18, SXVR M25c, Lodestar x2 Guide Camera
Pegasus Ultimate Hub V2 for all USB & Power
Pegasus focus motors on all scopes
1 year 7 months ago #46906

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

  • Posts: 197
  • Thank you received: 17
Interesting - does your system time get updated by the GPS, or do you connect to the Internet via WiFi or Ethernet? In my case I don't connect to the Internet at all in a typical session.
Currently running KStars/Ekos/Indi on a Raspberry Pi 4B 4GByte under Raspberry Pi OS thanks to Astroberry
Sky-Watcher ED80 Pro with 0.85x FR/Corrector with Canon DSLR and ASI533MC on AZ-EQ5 GT mount
Other Sky-Watcher scopes - SkyMax 150 Pro Maksutov Cassegrain and Explorer 150p Newtonian
1 year 7 months ago #46918

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

  • Posts: 960
  • Thank you received: 365
Astroberry 2.0.0 uses timedatectl with built-in ntp so it can get time from RTC and network, but not directly from GPS. It is a bad side of obsoleting old good ntpd, which can access gpsd directly via shared memory. Chrony is the only solution I know, but I left that to users to implement this change in their systems.

Regarding hot-plugging GPS - it works for USB devices but does not work with hardware serial port (/dev/ttyACM0). To use hardware serial port you need to either edit /etc/default/gpsd and set DEVICES or you can leave the file alone and run: sudo gpsdctl add /dev/ttyACM0
To make the second approach persistent you can add gpsdctl add /dev/ttyACM0 to /etc/rc.local
--
Radek Kaczorek
Astroberry Server | NEQ6 | Atik 460EX | Atik EFW2 | ASI 120MM
The following user(s) said Thank You: Ed Wilson , Christian T
1 year 7 months ago #46919

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

  • Posts: 1039
  • Thank you received: 130

Ah, yes I do use the hotspot to connect to, but I also have a USB WiFi dongle in as well for internet access... :)
Stellarmate OS on Raspberry pi4b
Skywatcher EQ8 pro, on steel pier
Takahashi FSQ85, FS60cb & Meade 8” SCT (de-forked)
Starlight Xpress SXVR H18, SXVR M25c, Lodestar x2 Guide Camera
Pegasus Ultimate Hub V2 for all USB & Power
Pegasus focus motors on all scopes
1 year 7 months ago #46923

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

  • Posts: 12
  • Thank you received: 0
I am experimenting with my smartphone with netGPS which works as a gps server. It works well, but now I can't understand how I can implement it in the system as the rtc provided by the gps. The application requires the configured indi gps_nmea driver
1 year 5 months ago #48851

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

  • Posts: 29
  • Thank you received: 1
On my system it is /dev/ttyS0, and the GPS is connected to the RaspberryPi UART on the header. Actually, I am not sure the time is really updated from the GPSD at all, how can I tell? I see that it gets updated from the custom RTC on start, since the time is up-to-date even without internet connection. How should I make crony synchronize system time, RTC (possibly also NTP if connection ever available?) and GPSD (if signal available) by their logical priority?
1 year 5 months ago #48855

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

  • Posts: 197
  • Thank you received: 17
I have now tried out a fresh image of Astroberry 2.0.1 and the updated version with chrony configured definitely gets its system clock from my gps dongle (ublox-7). However in my Kstars/Ekos/Indi profile, with gps set as the source of timing and location for Kstars, the time is never updated.
So my approach now at switch on is to leave a period of time for the gps to capture satellites and to update the system time, and only then start up Kstars with the option set for updating Kstars from system time and no longer the gps. However the gps location is no longer providing useful information. Is there some other switch to set?
Currently running KStars/Ekos/Indi on a Raspberry Pi 4B 4GByte under Raspberry Pi OS thanks to Astroberry
Sky-Watcher ED80 Pro with 0.85x FR/Corrector with Canon DSLR and ASI533MC on AZ-EQ5 GT mount
Other Sky-Watcher scopes - SkyMax 150 Pro Maksutov Cassegrain and Explorer 150p Newtonian
1 year 5 months ago #48938

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

  • Posts: 960
  • Thank you received: 365
... just to make sure we're on the safe side - is indi-gpsd driver up and running in your profile?
--
Radek Kaczorek
Astroberry Server | NEQ6 | Atik 460EX | Atik EFW2 | ASI 120MM
1 year 5 months ago #48977

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

  • Posts: 385
  • Thank you received: 13
Hello,

Thank Radek for giving us a glimpse under the covers. I looked up timedatectl. The last example in this link shows GPS as the time source.

Timedatectl usage

Under AB2.0.0, I never noticed GPSD not providing time. I will look at the time/date and GPS soon. Maybe, timedatectl does work with GPSD. However, I think it is going to be GPS or Network.
1 year 5 months ago #49013

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

  • Posts: 197
  • Thank you received: 17
I have located an issue with the operation of GPS which seems to very much in Indi area. I can now make the fault appear in all my micro SD card implementations! However I can also make the issue disappear in all three! My workaround is to enter the Options tab in INDI Control Panel - GPSD - and choose Time Source <strong>System</strong> and not <strong>GPS</strong>. The actions window still shows that there are two GPS fixes per 60 seconds, but the system time and KStars time match well enough <1 sec differential.
and if I set the Time Source choice to GPS this is the result where the updated UTC time each minute only increments one second.
Currently running KStars/Ekos/Indi on a Raspberry Pi 4B 4GByte under Raspberry Pi OS thanks to Astroberry
Sky-Watcher ED80 Pro with 0.85x FR/Corrector with Canon DSLR and ASI533MC on AZ-EQ5 GT mount
Other Sky-Watcher scopes - SkyMax 150 Pro Maksutov Cassegrain and Explorer 150p Newtonian
Last edit: 1 year 5 months ago by Ed Wilson . Reason: Adding images
1 year 5 months ago #49018
Attachments:

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

  • Posts: 385
  • Thank you received: 13
Hello,

Yesterday, I spent some time looking at AB 2.0.1 and GPS Time. In my instance of AB 2.0.1, I found a real conflict between CHRONY and TIMEDATECTL. If I started one, the other would stop. Ok.

I looked at the configuration of TIMEDATECTL and the default CONF file is GPS ready. So, I can see why CHRONY is redundant. My plan is to remove CHRONY and seek a solution between TIMEDATECTL and GPSD. As it stands, my system is working as ttyACM. Raspbian picked ttyACM as the resultant solution to the u-blox-7 DYI GPS USB and AstroEQ.

I came to this solution as Raspbian took me there. I could not run two ACM devices at the same time. The AstroEQ and u-blox fought over ttyACM0. I originally looked at INDI-GPUSB thinking that these devices are USB. Nope. Raspbian is very persistent, ttyACM or nothing. I then used udevadm as the path to managing two ttyACM devices. Understanding udevadm first, was the good step. Using udevadm resolved the conflict.

The u-blox 7 was faster to the draw than the AstroEQ. I tried loading things sequentially. The u-blox was insistent. INDI server was the battleground. Using udevadm made INDI server happy and EKOS knowing location, time zone, and time.
The following user(s) said Thank You: Ed Wilson
1 year 5 months ago #49061

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

Moderators: Radek Kaczorek
Time to create page: 0.848 seconds