_:n6a15ad45d290429290589e5bf376e49dxb2
<http://schema.org/text>
"Hi,\n\n\n\n\tI am having troubles connecting my Sawyer to a local NTP server.\n\n\n\n\tI have a local NTP server on my network that I know to be working : I can query it using some Linux machine and get offset, jitter, etc.\n\tI want to connect Sawyer to it so that it is in sync with my development computer (otherwise I can't use MoveIt! nor tf, pretty embarrassing...)\n\n\n\n\tI followed the Time and NTP tutorial, booted Sawyer into the FSM, replaced the NTP pool list with the IP address of my NTP server and rebooted into the SDK.\n\tHowever it didn't work, timestamps published by the robot are still off by about 6 hours.\n\n\n\n\tFor completeness:\n\n\n\n\t\tThe robot Intera version 5.2.2\n\t \n\t\n\t\tThe development computer Intera version is 5.2\n\t \n\t\n\t\tI work in France so I am on GMT+2 timezone\n\t \n\t\n\t\tThe `ntpdate` command does not work, it raises the error:\n\t \n\nserver 192.168.212.60, stratum 0, offset 0.000000, delay 0.00000\n11 Jun 10:28:25 ntpdate[4829]: no server suitable for synchronization found\n\n\n\t\tThe `clockdiff` command works and outputs the above offset:\n\t \n\nhost=192.168.212.60 rtt=562(280)ms/0ms delta=-17953355ms/-17953355ms Mon Jun 11 10:54:02 2018\n\n\n\t\tI spent some time on the FSM trying to get this working and I might have disrupted some parameters. For instance, the `ntpdate` was working at first but it no longer does.\n\t \n\n\tHow can I investigate on why is the robot not connecting to the server ?\n\tNormally it should burst on it at boot time as the offset is way bigger than 17 minutes.\n\n\n\n\tThanks for your help.\n"
<https://rethinkrobotics.interaforum.com/topic/562-cannot-sync-with-ntp-server/?tab=comments#comment-1676>