Replies: 1 comment 4 replies
-
|
Hmm, that's not expected behavior during normal operation. Are you able to share a bit more about what precedes the red light? Does it happen more often under certain circumstances? If there's any way to post the logs from the robot, that would be incredibly helpful. If you have a Raspberry Pi connected via Ethernet over usb (sounds like you do since you have a TurtleBot), you could try running |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for your quick response. When I enter I noticed in the log data that the time doesn't match mine; there is an hour difference. I don't know if that leads to problems or how I can change that. The Create 3 had a red light at log times between approximately 1:30 p.m. and 1:50 p.m. I had stopped my running processes, closed the terminals, and waited until it came back from the state by itself. Logs: |
Beta Was this translation helpful? Give feedback.
-
|
Ok, in looking at the logs, it would appear the cause is the robot reaching 100% CPU usage, which appears to have been followed by it running out of memory. Based on what you're describing, the first thing I would try is launch everything except for the diagnostics node and window. Diagnostics does tend to cause an increase in CPU usage. For the time delay, it looks like you do have an NTP server running on the Pi and the robot is recognizing that. However, it has determined the difference between the time the NTP is serving and the current Create 3 time is too big so it will not sync. This can usually be resolved by rebooting the robot. |
Beta Was this translation helpful? Give feedback.
-
|
Just to add to @brianabouchard's message -- you shouldn't have to go so far as to reboot the robot to get the time to resync -- you should just have to restart ntpd, which is an option in the Beta Features menu in the webserver. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for the answers. I restarted my ntp but the time in the log data was still not correct, and rebooting the robot also didn't help. I had launched everything except for the diagnostics node and window, but the ring light flashed red again. It's getting so bad now that it's switching back and forth between the states. The light turns red, then green and white again with the chime noise. This happens several times in a row at short intervals. I have added the relevant log data. Log-Data: |
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)
Raspberry Pi 400, Ubuntu 20.04
Which version of ROS 2 is installed on your computer?
Galactic
Which firmware version is installed on your robot?
G.4.5
Which RMW is your robot running?
CycloneDDS
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?
No response
Are there multiple Create 3 robots connected to your network?
No
Is multicast enabled?
None
What is the Adapter Board's USB/BLE Toggle currently switched to?
USB
Describe your question.
The Create 3's light ring regularly lights up in solid red. When that happens I can't turn it off and many functions no longer work. This condition lasts from a few minutes to several hours. What could be the reason for this malfunction and what can I do so that I can at least switch off and restart my Turtlebot 4/ Create 3 in this state?
Beta Was this translation helpful? Give feedback.
All reactions