Re: Chrony not taking SOCKET data from Application
sarveshwar k <[email protected]>
| Newsgroups | gmane.comp.time.chrony.user |
|---|---|
| Message-ID | <CAAik_Wx14vZmnHOLU-sSy073QYpujdnyZ4aSibqM4JVJcV54pQ@mail.gmail.com> |
Hi Miroslav Lichvar, Thank you. Now I am able to configure and sync system time based on 1PPS and GPS information. One more query is: Is it possible to sync system clock with RTC time until GPS fix is received. And whenever GPS data is not available, RTC should be the reference clock. Thanks & Regards Sarveshwar.K On Wed, Jan 25, 2023 at 2:05 PM Miroslav Lichvar <[email protected]> wrote: > On Wed, Jan 25, 2023 at 01:12:42PM +0530, sarveshwar k wrote: > > I see the reference time of GPS is taken by Chronyd, but not > synchronizing > > the system clock. > > The tracking "system time" offset is very large. That means it needs > to step. You have makestep in your configuration, which suggests the > offset is changing over time. You will need to figure out why, or > allow unlimited steps, e.g. "makestep 1 -1". > > -- > Miroslav Lichvar > > > -- > To unsubscribe email chrony-users-request-kWFZVVI9zxvPqho9SqqRMmD2FQJk+8+b@public.gmane.org > with "unsubscribe" in the subject. > For help email chrony-users-request-kWFZVVI9zxvPqho9SqqRMmD2FQJk+8+b@public.gmane.org > with "help" in the subject. > Trouble? Email [email protected] > >
chrony_work.conf
(application/octet-stream, 1.6 KB)
# Use public NTP servers from the pool.ntp.org project.
# Please consider joining the pool project if possible by running your own
# server(s).
# If you are a vendor distributing a product using chrony, you *MUST*
# read and comply with http://www.pool.ntp.org/vendors.html
#pool 0.openembedded.pool.ntp.org iburst
# Use a local timeserver in preference to the pool, if it's reachable.
#server 192.168.22.22 iburst minpoll 2 prefer
# Sync to pulse-per-second from an onboard GPS.
#refclock PPS /dev/pps1 poll 0 prefer
# You'll want to enable CONFIG_PPS and CONFIG_PPS_CLIENT_GPIO in your kernel,
# and an entry something like this in your device tree:
# pps {
# compatible = "pps-gpio";
# gpios = <&ps7_gpio_0 56 0>;
# };
# In first three updates step the system clock instead of slew
# if the adjustment is larger than 1 second.
makestep 0.005 -1
# Record the rate at which the system clock gains/loses time,
# improving accuracy after reboot
driftfile /var/lib/chrony/drift
# Enable kernel synchronization of the hardware real-time clock (RTC).
#rtcsync
# Allow NTP client access from local network.
#allow 192.168/16
# Serve time even if not synchronized to any NTP server.
#local stratum 10
local stratum 1
# Specify file containing keys for NTP authentication.
#keyfile /etc/chrony.keys
# Specify directory for log files.
logdir /var/log/chrony
# Select which information is logged.
log measurements statistics tracking refclocks
logdir /var/run/chrony
refclock PPS /dev/pps1 poll 0 lock GPS trust prefer
refclock SOCK /var/run/chrony/udssocket.sock poll 0 refid GPS noselect