turtlebot3 icon indicating copy to clipboard operation
turtlebot3 copied to clipboard

[ROS2 Humble] turtlebot3_node dies with 'namespace must be initialized' error when launching robot.launch.py

Open tae8554 opened this issue 7 months ago • 1 comments

Operating System:

Ubuntu 22.04 64-bit on Raspberry Pi 4

ROS version :

ROS 2 Humble Hawksbill

Turtlebot3 Model:

Burger

Description

I'm using ROS 2 Humble with TurtleBot3 Burger on Ubuntu 22.04.

When launching the bringup with:

ros2 launch turtlebot3_bringup robot.launch.py

i got this error:

terminate called after throwing an instance of 'rclcpp::exceptions::UninitializedStaticallyTypedParameterException'
what(): Statically typed parameter 'namespace' must be initialized.

### Steps to reproduce issue

1. Set up TurtleBot3 on Raspberry Pi with ROS 2 Humble installed.
2. Clone and build turtlebot3 repositories inside `~/ros2_ws/src/`
3. Make sure burger.yaml contains the following:

```yaml
turtlebot3_node:
  ros__parameters:
    namespace: ""

4. Run 


export TURTLEBOT3_MODEL=burger
export LDS_MODEL=LDS-01
cd ~/ros2_ws
colcon build --symlink-install
source install/setup.bash
ros2 launch turtlebot3_bringup robot.launch.py


5. The following error appears immediately:

terminate called after throwing an instance of 'rclcpp::exceptions::UninitializedStaticallyTypedParameterException'
what(): Statically typed parameter 'namespace' must be initialized.


### What Have You Tried?

```shell
I made sure my burger.yaml contains:

turtlebot3_node:
  ros__parameters:
    namespace: ""


I also ran the following steps:
Cleaned and rebuilt: rm -rf build/ install/ log/ && colcon build --symlink-install
Verified burger.yaml inside install/.../param also has namespace: ""
Re-sourced with source install/setup.bash

I suspect this may be due to a recent change in how static parameters are validated in ROS 2 Humble.

Any clarification or fix would be greatly appreciated!

Relevant logs / Terminal output


Screenshots or Diagrams

No response

Additional Information (Optional)

No response

tae8554 avatar May 29 '25 10:05 tae8554

Hello @tae8554 I tested it after running sudo apt upgrade, but I couldn't reproduce the error. If your suspicion is correct — that this might be due to a recent change in how static parameters are validated in ROS 2 Humble — we’ll need to update the package. Could you please share the exact steps you followed to run it, in detail?

GyuH13 avatar May 30 '25 02:05 GyuH13

Hello, since there has been no further discussion, I will close this issue. If you have any additional issues, please open a new one. Thank you.

GyuH13 avatar Sep 10 '25 06:09 GyuH13