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.

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.

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.

Hello,

CHRONY is completely integrated in to AstroBerry Server. Removing CHRONY would destroy AstroBerry. This leaves the OS in a quandary. Right now, everything is working. Nothing needs to be done.

If I recall correctly, chrony was added by Radek only on the latest update from 2.0.0 to 2.0.1.


Sorry I don’t understand - my GPS dongle works only in certain circumstances. After good luck and a helpful pattern of experiences last night, this morning KStars says Nofix. It is as if the GPS unit is not plugged in, yet gpsd and Indi-gpsd are running and gpsmon shows an excellent fix has been found. For me, there are a number of bugs to isolate and cure to make this work reliably.

I'm not aware that timesync can get time from GPS. That's why I made Astroberry dependent on chrony in Astroberry 2.0.1.
What is proper configuration of timesync that supports GPS? If anybody got it working please share. I can easily come back to pure timesync and forget chrony.

Hello,

I am looking into the GPS issues. I am seeing a n issue now. I have my GPS installed. I ran XGPS. I see two GPS devices, /dev/ttyACM0 and /tmp/vgps. A conflict exists between the two. Looks like VirtualGPS is running. It gives the default site for Warsaw, Poland. This is interfering with the device and INDI driver. I am disabling VirtualGPS.

Hello,

I disabled VirtualGPS and that cleared up GPSD. INDI and GPSD are happy now.

Hello Kaczorek,

Thank you for your work. The documentation I shared show its last example working with GPS.

I was looking at how to configure timedatectl when CHRONY stood in the way. I remember installing CHRONY myself. When I tried to remove it, I found AB 2.0.1 dependent on it.

I can stop CHRONY and start TIMEDATECTL to see if XGPS runs well. If so, then not much work. If not, then TIMEDATECTL is too dependent on NETWORK NTP. Getting it to be flexible would be the next step. A conditional serviced maybe in order.

Hi AradoSKYindi, I looked at the link before posting. Example is not really helping bacause there is no actual configuration used for timedatectl to get data from GPS. It just shows "Reference: GPS"
All the sources I know say that timedatectl and timesync do not dupport GPS as a time source. Any specific advice and an example of working solution?

Hello,

As I stated, I stopped CHRONY and started TIMEDATECTL and TIMESYNC. I then plugged my U-Blox 7 device in. It took awhile to link. Once it did, it worked.



The network is unplugged. The GPS is running. The key is using udevadm.

The service TIMESYNCD is tied to CHRONY. With CHRONY stopped, TIMESYNC fails to operate.

I'm working with a gps_nmea indi driver, i set a smarthphone with netGPS (this app works as gps_nmea) and as you can see i see "gps udpate timer disabled"
What i can ceck?