iRobot Create 3 is stuck in Boot loop

[Affan60]

The iRobot create 3 is stuck in booting loop. The white ring keeps swirling and it does not complete the booting process. If I press the center button, it does not power off or do anything. is there any solution for that?

[justinIRBT]

@Affan60 To confirm, your robot never plays any music (it has a multi note jingle it plays when the boot process finishes.). Did your robot ever boot successfully, were you able to go through the setup process at some point where you updated your firmware and connected your robot to the network as described here:
https://edu.irobot.com/create3-setup

If your robot is on the network, can you try pulling the logs from the robot to help us diagnose. First, you will need to access the robot’s web server, which you can access by pointing a web browser to your robot’s IP address. From there, there is a logs tab, if you are able to access it, can you attach the log.

If your robot is on the network, is any other ROS software running on your network? We have sometimes seen issues where different usages of the same topic (such as /Odom) can cause crashes in rclcpp or multiple robots on the same network conflict with each other and you have to use namespace/domain to isolate them.

[Affan60]

Hi, Thank you for the response. The robot was able to boot successfully when unpacked. I connected the robot to my laptop through wifi connection and updated the firmware as mentioned in the setup guide. Then I tried to connect it with ROS2 but I could not access the robot topics on ROS. So I changed the RMW on webpage of robot and pressed save and restart. Since then robot is not able to boot. So robot is not connected to any network. Since robot is not connected to any network or my laptop, I am unable to connect it to the web server. Regards, Affan From: Justin ***@***.***> Sent: Sunday, May 22, 2022 7:52 PM To: ***@***.***> Cc: ***@***.***>; ***@***.***> Subject: Re: [iRobotEducation/create3_docs] iRobot Create 3 is stuck in Boot loop (Discussion #61) @Affan60<https://github.com/Affan60> To confirm, your robot never plays any music (it has a multi note jingle it plays when the boot process finishes.). Did your robot ever boot successfully, were you able to go through the setup process at some point where you updated your firmware and connected your robot to the network as described here: https://edu.irobot.com/create3-setup If your robot is on the network, can you try pulling the logs from the robot to help us diagnose. First, you will need to access the robot’s web server, which you can access by pointing a web browser to your robot’s IP address. From there, there is a logs tab, if you are able to access it, can you attach the log. If your robot is on the network, is any other ROS software running on your network? We have sometimes seen issues where different usages of the same topic (such as /Odom) can cause crashes in rclcpp or multiple robots on the same network conflict with each other and you have to use namespace/domain to isolate them. — Reply to this email directly, view it on GitHub<#61 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ALW7XHSDJ4NYMT2GK4FTYH3VLLCB3ANCNFSM5WTWQ2TA>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[Affan60]

Robot completed its boot up process. I was in process to switch it back to cyclonedds (not completed the process) and I heard the robot's happy sound. It happened without me entering curl -X POST -d "ros_domain_id=0&ros_namespace=&rmw_implementation=rmw_cyclonedds_cpp" "http://192.168.186.2/ros-config-save-main"

However, I clicked the "reboot the robot" and "Restart the application" multiple times when I was on 192.168.186.2.

I checked the robot configurations. It shows that robot was on cyclonedds. It did not complete the change of RMW at the first place.

All in all, robot is working now.

[shamlian]

I'm glad to hear the robot is working! Would you mind grabbing the logs for us before you reboot again, so that we can try to understand what might have happened?

[Affan60]

messages.txt

Logs are attached. Thanks for all the help

[shamlian]

Also -- while you've got the robot up -- I would recommend connecting it to your local Wi-Fi network, just so that debugging becomes easier if necessary in the future.

[shamlian]

One final thought -- it's not recommended to use this robot in access point mode for an extended period of time. If your intention is to connect over Wi-Fi, you should connect to an external access point.