Changelog for package rosbot_utils

1.2.4 (2026-09-01)

• Bump dependencies
• Contributors: rafal-gorecki

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 flash_firmware NACK on read-protected STM32 MCUs
• Contributors: rafal-gorecki

1.2.1 (2026-08-14)

1.2.0 (2026-08-12)

• Restore vendored stb_image.h and the controllers pin rationale (#189) clang-format rewrote 6.3k lines of upstream stb_image v2.30 before the third_party exclusion landed, so the file could no longer be resynced against upstream.

• Merge pull request #188 from husarion/feature/twist-mux-controller Feature/twist mux controller

• Move animation_publisher parameters into the model config

• Follow cmd_vel source on the LED strip nav2 driving shows the navigation animation, a human or nobody shows ready. The controller latches the source, so the subscription has to be transient_local + reliable.

• Add navigation animation and rename car_wave to ready

• Rename animation and add choices

• pre-commit fix

• Clean up

• Select LED animations from config_dir without a restart current_animation now re-reads <name>.png/.yaml from disk on every set, so a PNG dropped into config_dir needs no driver restart. create_config_dir no longer aborts the whole copy on a dangling symlink.

• Restore led_strip/enable service on animation_publisher The service is documented in ROS_API.md but was lost when the led_strip_car_wave/rainbow nodes were retired.

• feat(rosbot_utils): parameter-selectable LED animation publisher Replace the two hard-coded LED nodes (led_strip_rainbow / led_strip_car_wave) with a single animation_publisher that plays user-definable PNG animations (row = frame, column = LED) selected by the current_animation node parameter.

  - Animations are auto-discovered from rosbot_utils/animations (shipped) and an optional user dir; each is a <name>.png + <name>.yaml sidecar (frequency, brightness, optional color tint). Filename stem = animation name.

  - Publishes the firmware contract unchanged: sensor_msgs/Image 1x18 rgb8, BEST_EFFORT, at the animation's frequency. Wider PNG rows are cropped to the first 18 columns, narrower rows padded black.

  - current_animation is validated on set (on-set-parameters callback); the reserved 'none' publishes nothing so the firmware idle animation shows.

File truncated at 100 lines see the full file