Closed royito55 closed 12 months ago
I found that for this case, the best "solution" is to factory reset the create3
Not sure what to say here except that the log snippet you posted does indeed show the NTP daemon restarting.
You will find that we have just released G.5.1 / H.2.1 which allows direct configuration of ntp.conf; please feel free to reconfigure the daemon as you please, and let us know when you find a configuration which works in your particular use case.
In case it helps: Clearpath has an example ntp.conf for the Turtlebot 4 use case; perhaps this can help with yours. https://github.com/turtlebot/turtlebot4/issues/216
Checking in again -- users have had some success with this -- see https://github.com/iRobotEducation/create3_docs/issues/401 . Would be curious to know if this solves your problem as well.
Checking in one last time before I close this "cannot reproduce."
There is no way to sync the create3 to an NPT server or whatever the default configuration is in there.
I've seen it work 2 out of 200 times probably, and I don't know the conditions for it to work properly.
The Restart ntpd Beta Feature does nothing. After clicking it, I get this every single time:
It does not work either, because it is configuring the Create3 as the server, but it seems the server never starts correctly.
I can't disconnect the create3 (workaround described here: https://github.com/turtlebot/turtlebot4_robot/issues/8) from WiFi because I'm using CycloneDDS and I haven't found a way to see the topics coming from the create3 with a CycloneDDS config file. If anyone has managed this I'm all ears!
I can't switch to Fast-DDS to disconnect the create3 because of the many issues involving nav2 (I've successfully ran it in CycloneDDS countless times) described here: https://github.com/ros2/ros2/issues/1253 https://github.com/ros-planning/navigation2/issues/3033
I tried Turtlebot4's
chrony.conf
but it didn't work for the same reason as all the above: https://github.com/turtlebot/turtlebot4_setup/blob/galactic/conf/chrony.confAlso tried this workaround but didn't work: https://github.com/iRobotEducation/create3_docs/issues/401
Hopefully the user will have more "configuration power" and not have the create3 be a black box that prevents it from working unless it is in very simple setups.
PS I forgot to mention, I don't think it's a firewall issue either, I tried pinging those addresses that ntpd can't find from another machine in the same network and it arrives no problem.