Hi,
We are encountering a very strange problem, that I’ve not been able to track down a solution for through other googling.
When our ROSBot 3’s boot, and they have internet, chrony
correctly finds and synchonsies to an NTP server and the time on the rosbot is correct.
However, if they boot without internet the timestamp is very wrong. It resets to an old time, that can be hours, or even months out of date. This causes obvious issues when using ROS nodes external to the ROSBot as the timestamps are way off. Only when re-connecting to a network with internet do the timestamps update.
I’ve tried tracking down the issue, but it seems to be some combination of what chrony is doing with the raspberry pi 5 as the hardware clock, system clock or rtc. The best I can find is if I run sudo chronyc makestep
, chrony will force the clock to actually be ok. But then on the next boot (without internet) the timestamp gets reset to the match the time when I ran the manual makestep command. I can’t seem to find any setting from chrony to make this functionality permanent, and keep the hardware/rtc clock up-to-date.
Any insights would be greatly appreciated, because we don’t always have our wireless network with internet access.
Regards,
Tim