You are here

update of time sync via ntp

7 posts / 0 new
Last post
DL1MDR
update of time sync via ntp
How often does a AREDN-node sync the time with the ntp-server defined under setup?  It seems to me, that this is done by the node only once at startup. So if the ntp-server is not available at startup of the node, the time will not be synced any more later. Is that correct or do I have a wrong setup in my AREDN-Node?

In my case I have a Mikrotik hAP Router and a Pi configured as NTP-Server with GPS-mouse. The Pi is connected to the USB-Port of the Mikrotik for being supplied with current. This means, that the Pi is always starting up after the Mikrotik completely booted and the Mikrotik does never have a time sync with the NTP-Server of the Pi. Other nodes in the mesh get the time correctly synced with the NTP-Server of the Pi.

So is there any possibility to delay the time sync after booting up a AREDN-node?

Thanks for any helpful information.
AE6XE
AE6XE's picture
The not settings should
The not settings should regular poll the time servers, not just at startup.   I'm traveling this week, not able to confirm behavior until next week.

Joe AE6XE
k6dlc
k6dlc's picture
   The problem with ntp
   The problem with ntp configuration is that  their is no standard time zone? Do we all use UTC or are local timezone, ie EST?
nc8q
nc8q's picture
We all use UTC and optionally display local TZ.

Hi, Dan:
All my devices reference UTC, some display EDT/EDST, some display UTC.
example:
My workstations display local.
My WSJT-X station displays UTC.

3s, Chuck

 

DF2SI
Race condition

I have just discovered the same race condition between the nodes and my Raspi which runs an ntp server (chrony). My ntp server uses a GPS receiver which may take a few minutes to lock. So precise time information will only be available some minutes after startup.

Even at startup the nodes do not always sync the time, only when e.g. the time zone has been changed. Especially for testing purposes it would be good to be able to force a node to submit an ntp request in order to sync time. In the latest OS supposedly a node syncs only once a day. This may be useful in a permanent setting, but for mobile settings there should be a sync every few minutes, at least if there is any meaning to the time the nodes are holding.

AJ6GZ
RTC
Is the pi being rebooted often, perhaps in the same mobile environment as the nodes? If so, get a battery backed real time clock (RTC) module for the pi so that NTP will have less issues upon powerup/GPS lock. NTP servers are not designed to be cold booted without the symptoms you're seeing. It indeed may take some time before it starts serving the correct time if the pi's hardware clock is not already close to the correct time.
K6CCC
K6CCC's picture
Every 24 hours - normally
Under normal conditions, the nodes will request time at startup and every 24 hours thereafter.  I can easily watch my NTP server and see exactly when each device gets time.
 

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer