rascol / pps-client Goto Github PK

Hi, I'm wondering whether your repo will work with the NEO-M8T GNSS Timing HAT?

Additional question 1:
From what I can tell this does not create an NTP server on the RPi?

Additional question 2:
Even though this receiver is somewhat expensive would it work?:
LEA-M8F Timing GNSS

If so how should it be wired up? Just the PPS, RXD and TXD pins?

My synchronization hardware works with a 2 power timing. Hence, the pps signal is actually every 1.048576 seconds with 50% duty cycle. Is there any way to compensate this at my client? Where should I look in the code?

Hi,
I'm generating a PPS signal (@ every 500ms) from a third party device connected to RPi GPIO_4 pin. It looks like the offset between PPS and CLOCK_REALTIME (system clock) is unstable after few seconds.
I tried disabling NIST clock in .conf file. Am I missing anything here?

Few questions

• "System clock" as described in documentation means is it CLOCK_REALTIME?
• Is it possible to use PHC2SYS instead of PPS-Client application?

Hi Ray Connell,

I tried to install this package on jetson and tested. I found jitter is not converging.
After around 20 mins jitter become 0, again restarts with big number.
Is it possible to add this package works on Jetson Nano platform?
Or please let me know how to make it converge. i will try.

Regards,
Kishore

hello!

when I first run pps-clinet , It prints
2021-05-28 12:15:12.000000 20 jitter: 0 freqOffset: 0.000000 avgCorrection: 0.000000 clamp: 32768*

some time past, it goes
2021-05-28 15:13:50.000000 10738 jitter: 0 freqOffset: 0.000000 avgCorrection: 0.000000 clamp: 1

so I thought time synchonized. But then I changed sys time with wrong time(for test) , however it did't detect/correct it, something is wrong

I've tried restart/reboot/reinstall, change time in milliseconds, and some . Nothing changes, still print
2021-05-28 17:00:31.000000 18582 jitter: 0 freqOffset: 0.000000 avgCorrection: 0.000000 clamp: 1

it seems a data/cache is saved somewhere in disk (because num keep counting on), and I can't find it, even pps-client-remove -a

This is for a Raspi3 model B, running the latest 64-bit version of Raspbian lite. PPS-Client had been working with the same setup, but stopped working after I ran an apt-get update/upgrade. After spending hours messing with different configuration settings, and reinstalling PPS-Client multiple times, I decided to try starting over with a fresh install, but the problem is still occurring.

pi@raspberrypi:~ $ sudo systemctl start pps-client
pi@raspberrypi:~ $ pps-client -v
pps-client is not running. "sudo systemctl start pps-client" to start.
pi@raspberrypi:~ $ sudo systemctl status pps-client
● pps-client.service - PPS-Client systemd service.
     Loaded: loaded (/etc/systemd/system/pps-client.service; enabled; vendor preset: enabled)
     Active: activating (start-pre) since Tue 2022-02-01 18:41:34 UTC; 1s ago
Cntrl PID: 4142 (sleep)
      Tasks: 1 (limit: 780)
        CPU: 5ms
     CGroup: /system.slice/pps-client.service
             └─4142 /bin/sleep 3

Feb 01 18:41:34 raspberrypi systemd[1]: Starting PPS-Client systemd service....
pi@raspberrypi:~ $ pps-client -v
pps-client is not running. "sudo systemctl start pps-client" to start.

contents of /var/log/pps-client.log

2022-02-01 18:22:23 Can't set pthread_attr_setstacksize(): No such file or directory
2022-02-01 18:22:46 Can't set pthread_attr_setstacksize(): No such file or directory
2022-02-01 18:23:09 Can't set pthread_attr_setstacksize(): No such file or directory
2022-02-01 18:23:22 Can't set pthread_attr_setstacksize(): No such file or directory
2022-02-01 18:23:39 Can't set pthread_attr_setstacksize(): No such file or directory
2022-02-01 18:23:42 Can't set pthread_attr_setstacksize(): No such file or directory
2022-02-01 18:23:46 Can't set pthread_attr_setstacksize(): No such file or directory

... and so on.

the PPS-Client current only support GPRMC data?
If I want to support GNGLL data, only need to add parse code? is there some demo or docs about that?

Hello,
I am checking your application for timestamping of events from adafruit GPS with PPS outout, I have managed to run your program successfully but I noticed that when I turn off the Rasberry Pi and turn it on again say 4 hours later, the date time restarts from the last datetime it was on (in this case 4 hours off). I have setup the system so uart is enabled in pps-client to get date time from GPS instead of network.
when I do cat /dev/ttyS0 I see the correct time in NMEA lines, but for some reason the pps-client does the 1 second counting from the last date time. Once rasberry pi is on the counting of datetime is as usual, expect it's offset due to time it was off. Any thoughts of what could be happening is greatly appreciated! Thanks!

Hi Ray:

I've been trying unsuccessfully to establish a stratum 1 PPS source on a pi4 for a year, all other time PPS to NTP sources eventually fail, many others on PI forums are having the same problem. I have hope that this client will finally work as it follows a different approach from the others. I was able to install the client and works flawlessly. I am feeding the PPS and NMEA data to the Pi4 using a QRPLABS GPS timeclock, the PPS is fed into GPIO 18 and the NMEA data is fed via USB.

The problem is the NEXT step.....how do I employ the accuracy of the PPS client into an onboard NTP server on the pi? I've tried using standard NTP, chrony, etc but all fall to recognize the PPS or NME source.
It seems like all want to feed using GPSD, but that would probably break the PPS client.

I'm, not a programmer, I'm a ham radio guy, so am dependent on others with advanced programming skills. It seems like I'm really close to success using this client if I can just port the PPS pulses into some type of time server that can redistribute them externally to my equipment which requires an IP-based time source. Thanks in advance for any help! Brian