Quisiera configurar chrony de maner que tome la señal PPS pero no logro que sincronize de manera correcta.
Estoy usando UART4 y el pin P8_07 para la señal PPS
Este es el archovo de configuracion de chrony.
Welcome to the chrony configuration file. See chrony.conf(5) for more
-information about usuable directives.
#-pool 2.debian.pool.ntp.org iburst
refclock PPS /dev/pps0 lock NMEA refid GPS
refclock SOCK /var/run/chrony.clk.ttyS4.sock offset 0.5 delay 0.2 refid NMEA noselect
#-refclock SHM offset 0.5 delay 0.2 NMEA noselect
#- This directive specify the location of the file containing ID/key pairs for
#- NTP authentication.
keyfile /etc/chrony/chrony.keys
#- This directive specify the file into which chronyd will store the rate
#- information.
driftfile /var/lib/chrony/chrony.drift
#- Uncomment the following line to turn logging on.
#- log tracking measurements statistics
#- Log files location.
logdir /var/log/chrony
#- Stop bad estimates upsetting machine clock.
maxupdateskew 100.0
#- This directive enables kernel synchronisation (every 11 minutes) of the
#- real-time clock. Note that it can’t be used along with the ‘rtcfile’ directive.
rtcsync
#- Step the system clock instead of slewing it if the adjustment is larger than
#- one second, but only in the first three clock updates.
makestep 1 3
Screen /dev/ttyS4 9600 me da datos NMEA correctos
$GPGLL,2032.21781,N,10015.28489,W,183955.00,A,A7C
$GPRMC,183956.00,A,2032.21782,N,10015.28491,W,0.051,110823,A61
$GPVTG,T,M,0.051,N,0.094,K,A2A
$GPGGA,183956.00,2032.21782,N,10015.28491,W,1,08,0.91,1935.5,M,-8.5,M,6B
$GPGSA,A,3,29,15,23,18,10,24,13,32,1.86,0.91,1.6302
$GPGSV,4,1,13,05,01,062,10,29,281,29,13,10,038,27,15,42,039,3371
$GPGSV,4,2,13,16,03,288,23,18,54,003,31,23,47,323,23,24,29,115,3178
$GPGSV,4,3,13,25,03,181,26,03,261,27,04,323,29,51,174,357A
$GPGSV,4,4,13,32,15,213,28*44
ppstest parece que funciona correctamente
sudo ppstest /dev/pps0
trying PPS source “/dev/pps0”
found PPS source “/dev/pps0”
ok, found 1 source(s), now start fetching data…
source 0 - assert 1691717598.290366211, sequence: 3072 - clear 0.000000000, sequence: 0
source 0 - assert 1691717599.290401420, sequence: 3073 - clear 0.000000000, sequence: 0
source 0 - assert 1691717600.290438878, sequence: 3074 - clear 0.000000000, sequence: 0
Revisando el servicio chrony parece estar funcionando son errores
debian@beaglebone:~$ systemctl status chrony.service
● chrony.service - chrony, an NTP client/server
Loaded: loaded (/lib/systemd/system/chrony.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2023-08-11 01:30:31 UTC; 3min 51s ago
Docs: man:chronyd(8)
man:chronyc(1)
man:chrony.conf(5)
Main PID: 2826 (chronyd)
Tasks: 2 (limit: 1027)
Memory: 568.0K
CGroup: /system.slice/chrony.service
├─2826 /usr/sbin/chronyd -F -1
└─2827 /usr/sbin/chronyd -F -1
Aug 11 01:30:31 beaglebone systemd[1]: Starting chrony, an NTP client/server…
Aug 11 01:30:31 beaglebone chronyd[2826]: chronyd version 3.4 starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGND +ASYNCDNS +SECH
Aug 11 01:30:31 beaglebone chronyd[2826]: Frequency 0.000 +/- 1000000.000 ppm read from /var/lib/chrony/chrony.drift
Aug 11 01:30:31 beaglebone chronyd[2826]: Loaded seccomp filter
Aug 11 01:30:31 beaglebone systemd[1]: Started chrony, an NTP client/server.
[5]+ Stopped systemctl status chrony.service
Pero al revisar la sincronizacion con GPS (GT-U7) No tengo ningun enlace correcto.
debian@beaglebone:~$ chronyc tracking
Reference ID : 00000000 ()
Stratum : 0
Ref time (UTC) : Thu Jan 01 00:00:00 1970
System time : 0.000000000 seconds fast of NTP time
Last offset : +0.000000000 seconds
RMS offset : 0.000000000 seconds
Frequency : 0.000 ppm slow
Residual freq : +0.000 ppm
Skew : 0.000 ppm
Root delay : 1.000000000 seconds
Root dispersion : 1.000000000 seconds
Update interval : 0.0 seconds
Leap status : Not synchronised
debian@beaglebone:~$ chronyc sources
210 Number of sources = 2
MS Name/IP address Stratum Poll Reach LastRx Last sample
±-------------------------------------------------------------------------------------------------------------------------+
#? GPS 0 4 0 - +0ns[ +0ns] +/- 0ns
#? NMEA 0 4 0 - +0ns[ +0ns] +/- 0ns