Changelog for package rosbot_gazebo

1.2.4 (2026-09-01)

1.2.3 (2026-08-26)

• Add ROSbot 3 pro config + move camera_mount to custom yaml component (#194)

  * Add ROSbot 3 pro configuration (OAK-D Pro + RPLIDAR S2) basic stays OAK-D Lite + RPLIDAR C1; pro is the ROSbot 3 PRO sensor set, mirroring the existing basic/telepresence/autonomy split for rosbot_xl.

  * Move camera_mount to a custom yaml component for ROSbot XL Was built into rosbot_xl_macro.urdf.xacro behind an internal include_camera_mount toggle; now telepresence.yaml/autonomy.yaml add it as a [type: custom]{.title-ref} component (like man01_bracket), with camera_mount_angle_1/2 read straight off that yaml entry via the new husarion_components_description [component]{.title-ref} passthrough (bumped pin: f059bb6 -> 5f783f8).

  • Use canonical component names instead of SKU codes in manipulation configs
  • Bump firmware

  * Fix test_spawn_robot_configuration_choices to cover both models configuration is now a shared arg (rosbot: basic/pro/custom, rosbot_xl: full set) since the ROSbot 3 pro config landed, but the test still only diffed spawn_robot.yaml's choices against rosbot_xl/*.yaml, so adding [pro]{.title-ref} (which lives under config/rosbot/) tripped it as drift.

• Contributors: Rafal Gorecki

1.2.2 (2026-08-25)

• Fix tf_bridge remap tf topic bug
• Contributors: rafal-gorecki

1.2.1 (2026-08-14)

1.2.0 (2026-08-12)

• Compose tf_namespace_bridge with robot_state_publisher (#190)

  * Compose tf_namespace_bridge with robot_state_publisher RSP is the highest-frequency /tf publisher in the stack and tf_namespace_bridge is its direct subscriber, so loading both into one rclcpp_components container skips a serialize/DDS hop per transform. Also dedupes the tf_namespace_bridge standalone-node launch block, previously copy-pasted across rosbot_bringup (x2) and rosbot_gazebo, into rosbot_description's node_container — including the config file, identical in all three copies.

  • Bump tf_namespace_bridge

  * Revert composing tf_namespace_bridge with robot_state_publisher LoadComposableNodes lazily creates a shared launch_ros ROSAdapter and registers an OnShutdown handler. rosbot_controller/controller.yaml's ros2_control_node has on_exit: shutdown (deliberate fail-fast), so every exit of it -- including a completely normal shutdown -- fires an extra Shutdown that races the planned one, double-calling ros_adapter.shutdown() and raising "Cannot shutdown a ROS adapter that is not running". That exception interrupts the SIGINT->SIGTERM escalation for the remaining processes, so unrelated ones die via raw signal instead of exiting cleanly. 100% reproducible in CI, and the same symptom shows up independently in navigation2#4722 -- a launch_ros framework interaction, not fixable from our launch files. Keeps the config dedup (rosbot_description is now the sole owner of tf_namespace_bridge.yaml, previously duplicated identically across rosbot_bringup/rosbot_gazebo/rosbot_description) since that part never touched node composition and stayed green throughout.

• Contributors: Rafal Gorecki

1.1.1 (2026-06-29)

1.1.0 (2026-06-15)

• Use human date-time with ms in pinned console log format
• Pin console log format; migrate LED-strip nodes to C++ (#181)
• Drop laser_filter; reliable FTDI USB firmware flashing (#180)
• Namespace audit + bringup quieting + docs/test cleanup (#173)
• Tests: CI coverage for every rosbot_* package (#171)
• Bump tf_namespace_bridge and clean up gazebo launches
• Bump tf_namespace_bridge with frame_filters parameters
• Contributors: Rafal Gorecki, rafal-gorecki

1.0.0 (2026-04-21)

• New firmware with microros namespace pre-communication support (#168)

File truncated at 100 lines see the full file