RealTimeClock accuracy
- This topic has 6 replies, 3 voices, and was last updated 6 years, 11 months ago by .
Viewing 7 posts - 1 through 7 (of 7 total)
Viewing 7 posts - 1 through 7 (of 7 total)
- You must be logged in to reply to this topic.
Home › Forums › Conduit: mLinux Model › RealTimeClock accuracy
Does anyone know the accuracy of the RealTimeClock on the conduit? Specificially looking to find the maximum drift per year, and which RTC chip is in place?
Thanks
Ken
If ntpd is running, it will periodically update the real time clock (hardware clock). Also, shutdown (/etc/init.d/hwclock.sh stop) will update the real time clock with the system clock.
There is also the script /etc/network/if-up.d/ntpdate-sync script that can be configured through /etc/default/ntpdate to update the hardware clock, if it can reach an ntpserver, when a network is brought up.
hwclock –systohc will set the hardware clock to UTC, based on the system clock.
Thanks John,
in the event that the gateway is unplugged for a period of time, how much drift is expected in the RTC, in the event that there is no connectivity when it is rebooted?
Ken
So can no-one tell me the accuracy of the RTC?
The RTC is the internal RTC on the AT91SAM9G25 processor. The 32 kHz crystal tolerance is 20 ppm. So the error could be as much as 2 seconds a day.
Thanks Tim
I was hoping for a physical RTC onboard, given that there’s an onboard battery – what does that power if it’s not an RTC?
Cheers
Ken