Odometry and IMU reset fails: ros2 service call /reset Trigger_Response success=False

[slider]

I have been using turtlebot3 since 2019 very well with Ros1. Now migrating to Ros2: all working quite well too thanks…. BUT:

reset service worked fine in ros1. In ros2 it seems to fail…

ros2 service call /reset std_srvs/srv/Trigger {}
waiting for service to become available…
requester: making request: std_srvs.srv.Trigger_Request()

response:
std_srvs.srv.Trigger_Response(success=False, message=‘Failed to write data[TxRxResult] There is no status packet!’)

It triggers this … but with above error…

[turtlebot3_ros-2] [INFO] [1762755430.661318054] [turtlebot3_node]: Start Calibration of Gyro
[turtlebot3_ros-2] [INFO] [1762755435.661697551] [turtlebot3_node]: Calibration End

Any explanation for the error and how to fix please ?

Thanks

[roboteer]

@slider
Are you using the standard configuration of PC + RPi3/4 for your TB3? Perhaps instead of looking at fixing this issue, would you be interested in another approach? Recently ROBOTIS releases a new TB3 branch (for beta testers) that uses DOCKER + ROS2 that combines the PC and SBC functionalities into a single computing platform. So far I tested this branch on a Burger and with a Jetson Orin Nano and also on an RPi5 (by itself). I have tested only “teleop” via the keyboard, but all components seemed to be working OK. If you are interested, a detailed post is available here:

Using TB3 and OMX together in Docker on Jetson Orin Nano

UPDATE 11/4/2025 From the previous post, I could see that the JON still had quite a bit of spare computing resources, thus I wanted to “go further” and to get rid of the Co-Controller RPi5 altogether. Conceptually, this means that “PC” and “SBC” capabilities should be combined into a single file. I tried to combine PC+SBC Docker files but could not get them to work cleanly (blogs in DISCORD). But @Woojin-Crive got back from ROSCON 2025 and helped with a new version of the feature-docker-upda…

I do not have an RPi3 or RPi4 anymore so I don’t know if DOCKER + ROS2 would work on them.

[slider]

Interesting, but yes I use high-end PC (5080GPU) & Pi4 + a NucBox on tb3.

… but for you does “reset” service work ???

…

[roboteer]

To be exact, my test set up merged PC+SBC into a single RPi5 16 GB running on Trixie OS (see enclosed picture). And then I installed that new TB3 branch using DOCKER and ROS2 JAZZY. So my TB3 is completely run within a DOCKER container.

And I did not have any issue with the Gyro during bring-up:

So I meant that this DOCKER TB3 set up was using much simpler communication connections (all serial comm. are within the same RPi5) than the current TB3 JAZZY setup shown on the ROBOTIS e-manual. Does your high end PC act as the PC component for your TB3 system? Or does the NucBox act as the PC component for your TB3 system? Your RPi4 has the OpenCR right? Is the RPi4 on Ubuntu 24.04 LTS Server? And you used Ethernet or WiFi to wrap around all 3 components of your robot? I only used Ethernet to test mine so far.

Recently ROBOTIS started a DISCORD site where you can report turtlebot3 issues also and it seemed that you would get quicker and direct responses from the ROBOTIS software engineers. Have you joined that DISCORD site yet?

Join the new ROBOTIS Discord Server!

Hello everyone, We’re excited to announce the launch of our new ROBOTIS Discord server! We created this space to help us all connect and support each other. This is a great place to ask questions, share your projects, and get help from our community. Also, we’d like to let you know that the ROBOTIS forum is being revamped with a new look and improved features. We’re working to make it an even better place for our community. Here’s what you can expect on the Discord Server: Technical Sup…