0

I'm trying to get the precise time using PPS from the GPS module using the chrony. But every time I'm getting '#-' before the Gps as shown below

MS Name/IP address         Stratum Poll Reach LastRx Last sample               
===============================================================================
#* PPS0                          0   4   377    14   -302ns[ -374ns] +/- 1110ns
#- GPS                           0   4   377    13   -215ms[ -215ms] +/-  102ms

My chrony.conf file is as follows

#Mange the clock slower for less jitter
minsamples 10

# set larger delay to allow the NMEA source to overlap with
# the other sources and avoid the falseticker status

refclock PPS /dev/pps1 lock NMEA trust prefer
refclock SHM 0 offset 0.395 delay 0.2 refid GPS trust prefer

#refclock SHM 0 poll 3 refid GPS1
#refclock SHM 1:perm=0644 refid GPS2

keyfile /etc/chrony/chrony.keys
commandkey 1
driftfile /var/lib/chrony/chrony.drift 
log tracking measurements statistics
logdir /var/log/chrony
maxupdateskew 100.0
dumponexit
dumpdir /var/lib/chrony
# if local stratum is configured and there's a local clock issue, the PPS changes 
stratum to match this stratum 10
allow
logchange 0.5
rtconutc

Here can I reduce 1110ns to 100ns by doing any modifications in conf file?. Basically, my doubt was if I'm using two sources from which one will be the PPS socket and the other will be GPS shared memory driver so will this combination be okay to get less offset? or do I need to use only GPS socket with PPS socket or GPS shared memory with PPS shared memory.

Omkar Dixit
  • 71
  • 1
  • 7
  • ?pps is the selected source (*) https://chrony.tuxfamily.org/doc/devel/chronyc.html its also saying gps is valid but not selected. What's the actual problem you are having? – user3788685 Jul 10 '22 at 09:32
  • Basically, my doubt was if I'm using two sources from which one will be the PPS socket and the other will be GPS shared memory driver so will this combination be okay to get less offset? or do I need to use only GPS socket with PPS socket or GPS shared memory with PPS shared memory. @user3788685 – Omkar Dixit Jul 11 '22 at 04:13
  • Still don't fully understand the question but; ntp/chrony will select the best source and use that. PPS will always be better than NMEA GPS strings but PPS only marks the second boundary, it does not give you a time stamp. your setup looks like it working normally and correctly. You pps offset is -302ns vs the the slower gps source (215ms). The offset is only +/- 1.1ms ! hardly bad lol. If im still misunderstanding please help me out. – user3788685 Jul 11 '22 at 15:37

0 Answers0