NAV2 Support

[dhallaparamvijay-wq]

Robot Model

Turtlebot4 Standard

ROS distro

Jazzy

Networking Configuration

I do not know

OS

Ubuntu 24.04

Built from source or installed?

Built from Source

Package version

Built from source. I can provide the exact commit hash or package version if required. The robot has been rebuilt and reconfigured multiple times during troubleshooting.

Type of issue

Navigation (SLAM, Nav2 etc.)

Expected behaviour

The TurtleBot 4 should initialize correctly, complete startup without errors, successfully localize, navigate to goals reliably, and operate consistently without controller failures or unexpected interruptions.

Actual behaviour

The robot has been unreliable during normal operation.

The system frequently experiences navigation failures and inconsistent behavior. Navigation cannot be relied upon for normal use despite repeated software installation, rebuilding the workspace, updating packages, and following the official documentation.

After extensive troubleshooting, the robot still does not consistently perform as expected, leading me to believe there may be an underlying hardware issue rather than only a software configuration problem.

The product has therefore not been reliable enough for its intended purpose.

Error messages

Navigation failures, controller server failures, and inconsistent startup behavior have been observed during testing.

Unfortunately I do not currently have complete terminal logs available. If there are specific diagnostic logs you would like me to collect, I would be happy to provide them.

To Reproduce

1. Power on the TurtleBot 4 Standard.
2. Launch the normal navigation stack.
3. Initialize localization and mapping.
4. Send navigation goals.
5. Observe inconsistent navigation behavior, intermittent controller failures, and unreliable operation.
6. The behavior persists even after rebuilding the software, reinstalling packages, and repeating the setup process.

Other notes

Product Information

• Product: Clearpath Robotics TurtleBot 4 Standard
• Purchased From: RobotShop
• Original Order Reference: #1441098
• Invoice: #11283109

RobotShop directed me to open this GitHub issue because the robot is currently under the manufacturer's warranty.

I would appreciate assistance determining whether this is a hardware defect and what additional diagnostics should be performed.

If repair or replacement is required under warranty, I am happy to cooperate with the diagnostic process.

If it is possible under the applicable warranty or return policy, I would also appreciate consideration of a refund, as my project requirements have changed since the original purchase.

I am happy to provide additional logs, photographs, videos, or perform any diagnostic procedures requested.

Contact - dhallaparamvijay@gmail.com

[dhallaparamvijay-wq]

Following up?

[RustyCPR]

Hi @dhallaparamvijay-wq
Sorry to hear your TurtleBot 4 is not behaving as expected.
From your description, it sounds like the core TurtleBot 4 functionality is working correctly, which suggests this may not be a hardware issue. To help us investigate further, could you clarify whether the unexpected behavior only occurs when using Nav2 and SLAM?

Could you also provide the following diagnostic information:

1. TurtleBot 4 system logs: journalctl -b > turtlebot4_log.txt
2. Create 3 logs from the robot: https://iroboteducation.github.io/create3_docs/webserver/logs/
3. 10 second ROS 2 bag file while operating the Turtlebot4 and recreate the Navigation error condition while recording:

sudo apt-get install ros-$ROS_DISTRO-rosbag2-storage-mcap
ros2 bag record -s mcap --include-hidden-topics --all

While it is recording, you can stop/cancel the Bag recording by pressing: Ctrl + C

4. Please provide details of your remote PC model and specifications.
5. Detail what is being launched on the TB4 and what is being launched on the remote PC.
   Thank you,
   Rusty

[dhallaparamvijay-wq]

Hi Rusty, Thank you for your response and for outlining the diagnostic steps. Unfortunately, since my original report, the situation has become significantly worse. The TurtleBot 4 is now no longer consistently appearing on the network. In many instances it does not show up on Wi-Fi at all, making it impossible to establish a connection. Even after multiple restart attempts and waiting for the system to initialize, the robot frequently remains unreachable over the network. When it does briefly become accessible, the connection is unstable and unreliable, preventing any meaningful testing or navigation. Because of this, I have been unable to consistently reproduce or troubleshoot the issue. The robot has become increasingly unreliable, and I have already spent a considerable amount of time attempting to diagnose and recover it. Unfortunately, instead of improving, the overall behavior has continued to deteriorate. Given the amount of time invested, the persistent instability, and the fact that the system is no longer functioning reliably enough for its intended purpose, I no longer have confidence in the product. For that reason, I would respectfully like to request a refund rather than continue with additional troubleshooting or a replacement unit. I believe this would be the most appropriate resolution given the circumstances. If there is any final information you require to process my request, please let me know. Thank you for your time and understanding. Best regards, Param Dhalla

…

On Fri, Jul 24, 2026 at 9:20 AM RustyCPR ***@***.***> wrote: *RustyCPR* left a comment (turtlebot/turtlebot4#705) <#705 (comment)> Hi @dhallaparamvijay-wq <https://github.com/dhallaparamvijay-wq> Sorry to hear your TurtleBot 4 is not behaving as expected. From your description, it sounds like the core TurtleBot 4 functionality is working correctly, which suggests this may not be a hardware issue. To help us investigate further, could you clarify whether the unexpected behavior only occurs when using Nav2 and SLAM? Could you also provide the following diagnostic information: 1. TurtleBot 4 system logs: journalctl -b > turtlebot4_log.txt 2. Create 3 logs from the robot: https://iroboteducation.github.io/create3_docs/webserver/logs/ 3. 10 second ROS 2 bag file while operating the Turtlebot4 and recreate the Navigation error condition while recording: sudo apt-get install ros-$ROS_DISTRO-rosbag2-storage-mcap ros2 bag record -s mcap --include-hidden-topics --all While it is recording, you can stop/cancel the Bag recording by pressing: Ctrl + C 4. Please details your remote PC model and specifications. 5. Detail what is being launched on the TB4 and what is being launched on the remote PC. Thank you, Rusty — Reply to this email directly, view it on GitHub <#705?email_source=notifications&email_token=CJPJNIDG42T732WU2H667K35GOEETA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBXGE4DONZVHEY2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-5071877591>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/CJPJNID5OEJ5X75ON3DXF4D5GOEETAVCNFSNUABFKJSXA33TNF2G64TZHM2DKNZRGAZDENRQHNEXG43VMU5TIOJVGQZTGMZYGIZKC5QC> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/CJPJNIFFQT566PTGKNWUK735GOEETA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBXGE4DONZVHEY2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJKTGN5XXIZLSL5UW64Y> and Android <https://github.com/notifications/mobile/android/CJPJNIFDZHJ3247ODF3TT7D5GOEETA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBXGE4DONZVHEY2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>