My Create3 Went Berserk Over "Time" #548
Replies: 3 comments 2 replies
-
One tip I might have is trying the NTP configuration settings suggested here: turtlebot/turtlebot4#216 I found this improved NTP sync and reduced the frequency of those delay too high messages. As for the crashing, that is very odd. I can't say what it means, but it is interesting that the logs indicate the crash loop is consistently preceded by the setting of the fast discovery server environmental variable. |
Beta Was this translation helpful? Give feedback.
-
I think my Create3 needs a backup ntp source accessible via WiFi , because when I put the Pi5 to nap for the night, and then wake it up again, it is having a hard time getting resynchronized. Before the nap all was going very well:
But after the nap:
I don't understand ROS message routing, with a discovery server, a usb0 ethernet connection and multicast WiFi connection to the Create3, to know if I am going to have to remove the Create3 WiFi connection to achieve the benefit of using the discovery server. If so, that would leave the Create3 without an ntp sync during the Pi5 naps. I think that is not a big deal, but I have seen documentation discussing the situation of large time differences taking several reboots or additional time to sync up - not understanding what I was reading actually. |
Beta Was this translation helpful? Give feedback.
-
Today all seems good in WaLi land. WaLi woke up from his 10 hour nap at 07:12 EST, the Create3 noticed the Pi5 coming alive on the USB0 port and re-established ntp sync with the chronyd running on the Pi5 with no further complaints. I'm going to call this one solved. WaLi Log in EST: (EST is UTC-5h)
Create3 Log UTC: (UTC is EST+5)
|
Beta Was this translation helpful? Give feedback.
-
How are you connecting to your Create 3?
Wi-Fi and USB Ethernet (ROS 2)
Computer(s) Model(s) and Operating System(s)
Ubuntu 22.04 in Docker over Raspberry Pi 5 PiOS Bookworm
Which version of ROS 2 is installed on your computer?
Humble
Which firmware version is installed on your robot?
H.2.4
Which RMW is your robot running?
FastRTPS
Does your robot have an assigned namespace? If so, please share.
No response
Is the robot connected to a network? If so, what is the network type?
Yes: 2.4GHz Home WiFi
Are there multiple Create 3 robots connected to your network?
No
Is multicast enabled?
Yes
What is the Adapter Board's USB/BLE Toggle currently switched to?
USB
Describe your question.
I completed the "Install/Configure Chrony on Compute Board" step,
and seeing "ignoring"
performed a "Power down to storage/ship mode", reboot.
The first reboot reported the Create3 "crashed", and a second cold reboot continued reporting crashing:
First_Boot_Crashes.txt
Eventually, another reboot from storage mode succeeded, but the ntp time sync to the Pi5 "compute board" is still failing:
FinallySuccess2.txt
Should I ignore this error and proceed to "install discovery server" step?
UPDATE: Have restarted Create3 again and did not experience crashes.
Beta Was this translation helpful? Give feedback.
All reactions