You will definitely want to use the initstepslew option in your chrony
On Wed, 2010-05-05 at 12:00 -0700, Enea Scioni wrote:
> Yes, infact embedded board doesn't have a button battery, so every reboot
> means that the date will reset on 1 Jan 1970: for that reason the offset is...
Yes, infact embedded board doesn't have a button battery, so every reboot means that the date will reset on 1 Jan 1970: for that reason the offset is very high. I'll try chrony to fix this, and I let's you know the result.
The output it's the same, both IP and Hostname:
5 May 20:55:46 ntpdate...
... your chrony
> On Wed, 2010-05-05 at 12:00 -0700, Enea Scioni wrote:
> > Yes, infact embedded board doesn't have a button battery, so every reboot
> > means that the date will reset on 1 Jan 1970: for that reason the offset
> > very high. I'll try chrony to fix this...
Chrony has been working well for us. We have computer 2 on the robot
synchronize with computer 1, and computer 1 synchronize with the outside
world. The key is to properly set the initstepslew so that at boot time
computer steps to the correct time. We have computer 1 set to
initstepslew to the...
You might also want to look into chrony
(http://chrony.tuxfamily.org/). If you search the ros-users archives
you'll find a couple of threads on its use.
On Sun, Feb 6, 2011 at 7:44 AM, kadir <kadirfu@...> wrote:
> Hi Stuart, Tully,
> The problem is...
... this problem? I have heard that Chrony is a
possible solution and would be interested to hear of any experiences
with it or any other method.
ros-users mailing list
... to provide our own implementation when we can leverage existing technologies such as Network Time Protocol.
For the use case of a system that starts without a system clock. It's relatively straight forward to have it run ntpdate or chrony on startup to get it to the right system time...
... this attempt at synchronization
> is working, though.
> How have others approached this problem? I have heard that Chrony is a
> possible solution and would be interested to hear of any experiences
> with it or any other method.
First of all, it looks like the offset is really, really high between your
embedded board and your laptop. You can probably use "chrony" to sync them:
ntp_monitor.py checks against both the remote host, and the computer. If
either one of these commands fails, then...
... diagnostic info shown in things like chrony (https://docs.fedoraproject.org/en-US/Fedora/18/html/System_Administrators_Guide/sect-Checking_if_chrony_is_synchronized.html) would be key in allowing the clock skew and frequency skew be automatically calculated by the clock node.
I think having a...
[Discourse.ros.org] [General] A do-it-yourself Turtlebot
([Discourse.ros.org] [TurtleBot] A do-it-yourself Turtlebot)
... chrony to synchronize the time different 'nodes' are running at, this is because the Pi doesn't have a real time clock, and if your Wifi is not connected to the Internet, the Pi will have the wrong time.
Next I suggest you load the following ROS packages into your catkin_ws/src workspace: