Planet ROS
Planet ROS - http://planet.ros.org
Planet ROS - http://planet.ros.org http://planet.ros.org
ROS Discourse General: ROS News for the Week of April 14th, 2025
ROS News for the Week of April 14th, 2025
The ROS 2 Kilted Kaiju feature freeze was Monday! We should have information about the release process early next week!
I’ve scheduled a ROS By-The-Bay meetup for 2025-05-01T01:00:00Z UTC coincide with the Kilted Kaiju Test and Tutorial Party.
Check out this teaser for, “Any6D: Model-free 6D Pose Estimation of Novel Objects” by KAIST and NVIDIA that will be presented at CVPR 2025! The demo seems to show ROS integration. Source code isn’t out yet but you can read the paper here. Heads up, we’re planning a ROS meetup at CVPR this year, more details will be out in a couple of weeks.
The fine folks at ETH Zurich have released ORCA Hand, an open source software and hardware hand you can build at home for under $2000.
The fine folks at HuggingFace

the equally awesome folks at Pollen Robotics. No word yet on what the merger means for the team, but we expect it to be awesome!
I came across a wonderful gif this week about the upcoming ROS 1 end-of-life on May 31st.
Events
- 2025-04-24 Autonomous Driving Meetup #6 Berlin
- 2025-04-26 Robotics Club SF: Dolores Hangout
- 2025-04-28 International Workshop on Robotics Software Engineering
- 2025-04-30 ROS By-The-Bay
- 2025-05-01 Kilted Kaiju Test and Tutorial Party – announcement soon
- 2025-04-30 Robotics Summit & Expo wsg @gbiggs.
- 2025-05-01 Career Fair @ Robotics Summit & Expo Boston
- 2025-05-02 CFP Deadline for Space Robotics Workshop at IEEE SMC-IT/SCC
- 2025-05-05 ROSCon 2025 Workshop CFP Deadline
- 2025-05-10 => 2025-05-11 ROBORACER @ ICRA 2025
- 2025-05-11 CFP Deadline for Robotics & AI Track @ CppCon
- 2025-05-12 The OpenCV-SID Conference on Computer Vision & AI
- 2025-05-15 ROS-Industrial Consortium Americas 2025 Annual Meeting Detroit
- 2025-05-19 Robotics Startup Bootcamp at ICRA
- 2025-05-23 ROSConJP CFP Deadline
- 2025-05-23 ICRA 2025 Advancing Quantitative and QUAlitative SIMulators for marine applications
- 2025-05-24 ROS MeetUp in Cali, Colombia!
- 2025-05-26 ROSCon UK 2025 CFP Closes
- 2025-05-30 => 2025-05-31 2025 Open Hardware Summit in Edinburgh
- 2025-05-31 ROS Noetic End-of-Life
- 2025-06-02 ROSCon 2025 Talk Submission Deadline
- 2025-08-29 => 2025-09-05 ROS Summer School 2025 at FH Aachen
- 2025-09-09 ROSCon JP in Nagoya
- 2025-09-15 => 2025-09-17 Inaugral ROSCon UK in Edinburgh
- 2025-10-27 => 2025-10-30 ROSCon Singapore
- 2025-11-17 => 2025-11-20 Joint ROSCon Germany and France
News
- Cosmic Robotics is Building Robots for Solar Power Deployments
- Robots, Mirrors, Music
- Hugging Face bridges gap between AI and physical world with Pollen Robotics acquisition
- Peppermint Robotics Raises $4M
- Scout.ai Raises $15M
- Physical AI startup RLWRLD brings in $15M
- Overland AI launches ULTRA autonomous ground systems for defense
- Request for Comment: URDF Joint Limits
- Robotics in Africa is trending upward and has a bright future
- Video: Space ROS x Medical: shared goals and tools
- Video: ROS I Developers’ Meeting
- Video: Isaac Sim in under half an hour
- Video: Embodied Intelligence: How AI is Powering the Next Generation of Robotics
- Request for Beta Testing: Nav2 Route Server
- RobotCAD 8.0.0 Released!
- PyRoboSim 4.0.0 is now available!
- Monarch Tractor partners with Dairy Farmers of America for autonomous feed pushing
- Revolutionizing Dairy Farming: How Robots Benefit Cows & Farmers
- Autonomous trucking developer Kodiak Robotics to go public via SPAC
- ABB plans to spin off its robotics division as a separately listed company – The Robot Report
ROS
New TurtleBot3 Examples Are Here!
- Autonomous Navigation and Docking for Panther & Lynx UGVs
- Navigating through the Robotic Simulation Landscape
- Optimizing Video Streaming in ROS 2
- ROS 2 URDF Converter
- A curated list of awesome robot descriptions (URDF, MJCF)
- AQUA-SLAM
- ARMADA Robot Arms from KAIST
- BeetleBot Differential Drive Robot Template for Gazebo / ROS 2
- New packages for ROS 2 Rolling Ridley 2025-04-16
- Generic Controller for Omnidirectional Robots using Omni Wheels
- Understanding the benefits and challenges for adopting behavior trees
- Standalone C++17 ROS 1 client
- Rviz Publisher
- ROS 2 Humble (C++) Communication with Siemens PLC — Modbus TCP vs OPC UA?
- Path Planning for Multi-Robot Navigation in Duckietown
- Video: Autonomous Mobile Robotics & ROS 2: the next step for robotics
Orca Hand
- Set of tutorials to practice robotics concepts with Webots and Python
Any6D: Model-free 6D Pose Estimation of Novel Objects
- ROS 2 URDF Converter
- Robot Manipulation Baselines
- ROS 2 AI Lecture
- SOTA robust LiDAR odometry
- Automate Robot Modeling with Onshape-to-Robot
- Example of ROS 2 and Gazebo on Pixi
- RoboVerse: Towards a Unified Platform, Dataset and Benchmark for Scalable and Generalizable Robot Learning
- Performing feature matching using the DeDoDev2 model in PyTorch
- ROS Node to converts sensor_msgs/PointCloud2 LIDAR data to nav_msgs/OccupancyGrid 2D map
- Automatic Target-Less Camera-LiDAR Calibration from Motion and Deep Point Correspondences
Got a Minute? 
We’re looking for three new contributors to help us with two new features and one issue with the Open-RMF Site Editor. Open-RMF is our brand new open source multi-robot fleet manager written in Rust:crab: and is the bleeding edge of what we are working on!
Open-RMF Site Editor #217: We’re need someone to create a way to save the user’s view point in the Open-RMF Site Editor that can we loaded when the user starts the application.
Open-RMF Site Editor #216: There is a bug such that deleting a fiducial that belongs to a group will permanently block any other fiducial in its drawing from being able to join that group.
Open-RMF Site Editor #225: We need a simple dialog that warns users before discarding unsaved changes. This is a great first issue for those just getting started with Rust.
6 posts - 4 participants
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: Next Client Library WG Meeting: Friday 18th April 2024 8AM PT
Hi,
The next meeting of the Client Library Working Group will be this Friday, 4th April 2025 at 8 AM Pacific Time.
- Meeting link: https://meet.google.com/oij-atzj-znw
- Meeting minutes and agenda: ROS 2 Client Libraries Working Group - Google Docs
- Google group if you want to be notified of future meetings: https://groups.google.com/g/ros-2-client-library-wg
Everyone is welcome to join and bring their own topics for discussion, just add them to the agenda!
3 posts - 2 participants
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: New packages for ROS 2 Rolling Ridley 2025-04-16
Hello everyone!
We’re happy to announce 17 new package and 206 updates are now available in ROS 2 Rolling Ridley
This sync was tagged as rolling/2025-04-16
.
Package Updates for rolling
Added Packages [17]:
- ros-rolling-autoware-internal-metric-msgs: 1.8.1-2
- ros-rolling-autoware-internal-metric-msgs-dbgsym: 1.8.1-2
- ros-rolling-autoware-lanelet2-extension: 0.7.0-1
- ros-rolling-autoware-lanelet2-extension-dbgsym: 0.7.0-1
- ros-rolling-autoware-lanelet2-extension-python: 0.7.0-1
- ros-rolling-autoware-lanelet2-extension-python-dbgsym: 0.7.0-1
- ros-rolling-autoware-msgs: 1.6.0-1
- ros-rolling-diagnostic-remote-logging: 4.4.3-1
- ros-rolling-diagnostic-remote-logging-dbgsym: 4.4.3-1
- ros-rolling-ld08-driver: 1.1.1-1
- ros-rolling-ld08-driver-dbgsym: 1.1.1-1
- ros-rolling-rmw-test-fixture: 0.14.1-1
- ros-rolling-rmw-test-fixture-implementation: 0.14.1-1
- ros-rolling-rmw-test-fixture-implementation-dbgsym: 0.14.1-1
- ros-rolling-turtlebot3-gazebo: 2.3.2-1
- ros-rolling-turtlebot3-gazebo-dbgsym: 2.3.2-1
- ros-rolling-turtlebot3-simulations: 2.3.2-1
Updated Packages [206]:
- ros-rolling-ament-cmake-ros: 0.14.0-1 → 0.14.1-1
- ros-rolling-ament-cmake-ros-core: 0.14.0-1 → 0.14.1-1
- ros-rolling-autoware-cmake: 1.0.1-1 → 1.0.2-1
- ros-rolling-autoware-common-msgs: 1.3.0-1 → 1.6.0-1
- ros-rolling-autoware-common-msgs-dbgsym: 1.3.0-1 → 1.6.0-1
- ros-rolling-autoware-control-msgs: 1.3.0-1 → 1.6.0-1
- ros-rolling-autoware-control-msgs-dbgsym: 1.3.0-1 → 1.6.0-1
- ros-rolling-autoware-internal-debug-msgs: 1.5.0-1 → 1.8.1-2
- ros-rolling-autoware-internal-debug-msgs-dbgsym: 1.5.0-1 → 1.8.1-2
- ros-rolling-autoware-internal-msgs: 1.5.0-1 → 1.8.1-2
- ros-rolling-autoware-internal-msgs-dbgsym: 1.5.0-1 → 1.8.1-2
- ros-rolling-autoware-internal-perception-msgs: 1.5.0-1 → 1.8.1-2
- ros-rolling-autoware-internal-perception-msgs-dbgsym: 1.5.0-1 → 1.8.1-2
- ros-rolling-autoware-internal-planning-msgs: 1.5.0-1 → 1.8.1-2
- ros-rolling-autoware-internal-planning-msgs-dbgsym: 1.5.0-1 → 1.8.1-2
- ros-rolling-autoware-lint-common: 1.0.1-1 → 1.0.2-1
- ros-rolling-autoware-localization-msgs: 1.3.0-1 → 1.6.0-1
- ros-rolling-autoware-localization-msgs-dbgsym: 1.3.0-1 → 1.6.0-1
- ros-rolling-autoware-map-msgs: 1.3.0-1 → 1.6.0-1
- ros-rolling-autoware-map-msgs-dbgsym: 1.3.0-1 → 1.6.0-1
- ros-rolling-autoware-perception-msgs: 1.3.0-1 → 1.6.0-1
- ros-rolling-autoware-perception-msgs-dbgsym: 1.3.0-1 → 1.6.0-1
- ros-rolling-autoware-planning-msgs: 1.3.0-1 → 1.6.0-1
- ros-rolling-autoware-planning-msgs-dbgsym: 1.3.0-1 → 1.6.0-1
- ros-rolling-autoware-sensing-msgs: 1.3.0-1 → 1.6.0-1
- ros-rolling-autoware-sensing-msgs-dbgsym: 1.3.0-1 → 1.6.0-1
- ros-rolling-autoware-system-msgs: 1.3.0-1 → 1.6.0-1
- ros-rolling-autoware-system-msgs-dbgsym: 1.3.0-1 → 1.6.0-1
- ros-rolling-autoware-v2x-msgs: 1.3.0-1 → 1.6.0-1
- ros-rolling-autoware-v2x-msgs-dbgsym: 1.3.0-1 → 1.6.0-1
- ros-rolling-autoware-vehicle-msgs: 1.3.0-1 → 1.6.0-1
- ros-rolling-autoware-vehicle-msgs-dbgsym: 1.3.0-1 → 1.6.0-1
- ros-rolling-camera-ros: 0.3.0-1 → 0.4.0-1
- ros-rolling-camera-ros-dbgsym: 0.3.0-1 → 0.4.0-1
- ros-rolling-chomp-motion-planner: 2.13.0-1 → 2.13.2-1
- ros-rolling-chomp-motion-planner-dbgsym: 2.13.0-1 → 2.13.2-1
- ros-rolling-control-toolbox: 5.0.0-1 → 5.1.0-1
- ros-rolling-control-toolbox-dbgsym: 5.0.0-1 → 5.1.0-1
- ros-rolling-diagnostic-aggregator: 4.4.2-1 → 4.4.3-1
- ros-rolling-diagnostic-aggregator-dbgsym: 4.4.2-1 → 4.4.3-1
- ros-rolling-diagnostic-common-diagnostics: 4.4.2-1 → 4.4.3-1
- ros-rolling-diagnostic-updater: 4.4.2-1 → 4.4.3-1
- ros-rolling-diagnostic-updater-dbgsym: 4.4.2-1 → 4.4.3-1
- ros-rolling-diagnostics: 4.4.2-1 → 4.4.3-1
- ros-rolling-domain-coordinator: 0.14.0-1 → 0.14.1-1
- ros-rolling-dynamixel-hardware-interface: 1.4.0-1 → 1.4.2-1
- ros-rolling-dynamixel-hardware-interface-dbgsym: 1.4.0-1 → 1.4.2-1
- ros-rolling-dynamixel-sdk: 3.8.2-1 → 3.8.3-1
- ros-rolling-dynamixel-sdk-custom-interfaces: 3.8.2-1 → 3.8.3-1
- ros-rolling-dynamixel-sdk-custom-interfaces-dbgsym: 3.8.2-1 → 3.8.3-1
- ros-rolling-dynamixel-sdk-dbgsym: 3.8.2-1 → 3.8.3-1
- ros-rolling-dynamixel-sdk-examples: 3.8.2-1 → 3.8.3-1
- ros-rolling-dynamixel-sdk-examples-dbgsym: 3.8.2-1 → 3.8.3-1
- ros-rolling-fastcdr: 2.2.5-1 → 2.3.0-1
- ros-rolling-fastcdr-dbgsym: 2.2.5-1 → 2.3.0-1
- ros-rolling-fastdds: 3.1.2-2 → 3.2.1-1
- ros-rolling-fastdds-dbgsym: 3.1.2-2 → 3.2.1-1
- ros-rolling-ffmpeg-image-transport: 2.0.1-1 → 2.0.2-1
- ros-rolling-ffmpeg-image-transport-dbgsym: 2.0.1-1 → 2.0.2-1
- ros-rolling-flir-camera-description: 3.0.0-1 → 3.0.1-1
- ros-rolling-flir-camera-msgs: 3.0.0-1 → 3.0.1-1
- ros-rolling-flir-camera-msgs-dbgsym: 3.0.0-1 → 3.0.1-1
- ros-rolling-foxglove-compressed-video-transport: 1.0.1-1 → 1.0.2-1
- ros-rolling-foxglove-compressed-video-transport-dbgsym: 1.0.1-1 → 1.0.2-1
- ros-rolling-gz-ros2-control: 2.0.6-1 → 2.0.7-1
- ros-rolling-gz-ros2-control-dbgsym: 2.0.6-1 → 2.0.7-1
- ros-rolling-gz-ros2-control-demos: 2.0.6-1 → 2.0.7-1
- ros-rolling-gz-ros2-control-demos-dbgsym: 2.0.6-1 → 2.0.7-1
- ros-rolling-hatchbed-common: 0.1.1-1 → 0.1.2-1
- ros-rolling-libcamera: 0.4.0-1 → 0.5.0-2
- ros-rolling-libcamera-dbgsym: 0.4.0-1 → 0.5.0-2
- ros-rolling-mapviz: 2.4.5-1 → 2.4.6-1
- ros-rolling-mapviz-dbgsym: 2.4.5-1 → 2.4.6-1
- ros-rolling-mapviz-interfaces: 2.4.5-1 → 2.4.6-1
- ros-rolling-mapviz-interfaces-dbgsym: 2.4.5-1 → 2.4.6-1
- ros-rolling-mapviz-plugins: 2.4.5-1 → 2.4.6-1
- ros-rolling-mapviz-plugins-dbgsym: 2.4.5-1 → 2.4.6-1
- ros-rolling-message-filters: 7.0.2-1 → 7.1.0-1
- ros-rolling-message-filters-dbgsym: 7.0.2-1 → 7.1.0-1
- ros-rolling-moveit: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-common: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-configs-utils: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-core: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-core-dbgsym: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-hybrid-planning: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-hybrid-planning-dbgsym: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-kinematics: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-kinematics-dbgsym: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-planners: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-planners-chomp: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-planners-chomp-dbgsym: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-planners-ompl: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-planners-ompl-dbgsym: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-planners-stomp: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-planners-stomp-dbgsym: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-plugins: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-py: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-py-dbgsym: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-resources-prbt-ikfast-manipulator-plugin: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-resources-prbt-ikfast-manipulator-plugin-dbgsym: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-resources-prbt-moveit-config: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-resources-prbt-pg70-support: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-resources-prbt-support: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-ros: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-ros-benchmarks: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-ros-benchmarks-dbgsym: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-ros-control-interface: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-ros-control-interface-dbgsym: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-ros-move-group: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-ros-move-group-dbgsym: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-ros-occupancy-map-monitor: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-ros-occupancy-map-monitor-dbgsym: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-ros-perception: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-ros-perception-dbgsym: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-ros-planning: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-ros-planning-dbgsym: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-ros-planning-interface: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-ros-planning-interface-dbgsym: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-ros-robot-interaction: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-ros-robot-interaction-dbgsym: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-ros-tests: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-ros-trajectory-cache: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-ros-trajectory-cache-dbgsym: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-ros-visualization: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-ros-visualization-dbgsym: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-ros-warehouse: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-ros-warehouse-dbgsym: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-runtime: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-servo: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-servo-dbgsym: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-setup-app-plugins: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-setup-app-plugins-dbgsym: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-setup-assistant: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-setup-assistant-dbgsym: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-setup-controllers: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-setup-controllers-dbgsym: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-setup-core-plugins: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-setup-core-plugins-dbgsym: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-setup-framework: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-setup-framework-dbgsym: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-setup-srdf-plugins: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-setup-srdf-plugins-dbgsym: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-simple-controller-manager: 2.13.0-1 → 2.13.2-1
- ros-rolling-moveit-simple-controller-manager-dbgsym: 2.13.0-1 → 2.13.2-1
- ros-rolling-mp2p-icp: 1.6.6-1 → 1.6.7-1
- ros-rolling-mp2p-icp-dbgsym: 1.6.6-1 → 1.6.7-1
- ros-rolling-multires-image: 2.4.5-1 → 2.4.6-1
- ros-rolling-multires-image-dbgsym: 2.4.5-1 → 2.4.6-1
- ros-rolling-nobleo-socketcan-bridge: 1.0.1-1 → 1.0.2-1
- ros-rolling-nobleo-socketcan-bridge-dbgsym: 1.0.1-1 → 1.0.2-1
- ros-rolling-pcl-conversions: 2.6.1-3 → 2.6.3-1
- ros-rolling-pcl-ros: 2.6.1-3 → 2.6.3-1
- ros-rolling-pcl-ros-dbgsym: 2.6.1-3 → 2.6.3-1
- ros-rolling-perception-pcl: 2.6.1-3 → 2.6.3-1
- ros-rolling-pilz-industrial-motion-planner: 2.13.0-1 → 2.13.2-1
- ros-rolling-pilz-industrial-motion-planner-dbgsym: 2.13.0-1 → 2.13.2-1
- ros-rolling-pilz-industrial-motion-planner-testutils: 2.13.0-1 → 2.13.2-1
- ros-rolling-pilz-industrial-motion-planner-testutils-dbgsym: 2.13.0-1 → 2.13.2-1
- ros-rolling-polygon-demos: 1.1.0-1 → 1.2.0-1
- ros-rolling-polygon-demos-dbgsym: 1.1.0-1 → 1.2.0-1
- ros-rolling-polygon-msgs: 1.1.0-1 → 1.2.0-1
- ros-rolling-polygon-msgs-dbgsym: 1.1.0-1 → 1.2.0-1
- ros-rolling-polygon-rviz-plugins: 1.1.0-1 → 1.2.0-1
- ros-rolling-polygon-rviz-plugins-dbgsym: 1.1.0-1 → 1.2.0-1
- ros-rolling-polygon-utils: 1.1.0-1 → 1.2.0-1
- ros-rolling-rcl: 10.0.2-1 → 10.1.0-1
- ros-rolling-rcl-action: 10.0.2-1 → 10.1.0-1
- ros-rolling-rcl-action-dbgsym: 10.0.2-1 → 10.1.0-1
- ros-rolling-rcl-dbgsym: 10.0.2-1 → 10.1.0-1
- ros-rolling-rcl-lifecycle: 10.0.2-1 → 10.1.0-1
- ros-rolling-rcl-lifecycle-dbgsym: 10.0.2-1 → 10.1.0-1
- ros-rolling-rcl-yaml-param-parser: 10.0.2-1 → 10.1.0-1
- ros-rolling-rcl-yaml-param-parser-dbgsym: 10.0.2-1 → 10.1.0-1
- ros-rolling-rclcpp: 29.3.0-1 → 29.4.0-1
- ros-rolling-rclcpp-action: 29.3.0-1 → 29.4.0-1
- ros-rolling-rclcpp-action-dbgsym: 29.3.0-1 → 29.4.0-1
- ros-rolling-rclcpp-components: 29.3.0-1 → 29.4.0-1
- ros-rolling-rclcpp-components-dbgsym: 29.3.0-1 → 29.4.0-1
- ros-rolling-rclcpp-dbgsym: 29.3.0-1 → 29.4.0-1
- ros-rolling-rclcpp-lifecycle: 29.3.0-1 → 29.4.0-1
- ros-rolling-rclcpp-lifecycle-dbgsym: 29.3.0-1 → 29.4.0-1
- ros-rolling-rcutils: 6.9.4-1 → 6.9.5-1
- ros-rolling-rcutils-dbgsym: 6.9.4-1 → 6.9.5-1
- ros-rolling-realtime-tools: 4.1.0-1 → 4.2.0-1
- ros-rolling-realtime-tools-dbgsym: 4.1.0-1 → 4.2.0-1
- ros-rolling-rosidl-typesupport-fastrtps-c: 3.7.1-3 → 3.8.0-1
- ros-rolling-rosidl-typesupport-fastrtps-c-dbgsym: 3.7.1-3 → 3.8.0-1
- ros-rolling-rosidl-typesupport-fastrtps-cpp: 3.7.1-3 → 3.8.0-1
- ros-rolling-rosidl-typesupport-fastrtps-cpp-dbgsym: 3.7.1-3 → 3.8.0-1
- ros-rolling-self-test: 4.4.2-1 → 4.4.3-1
- ros-rolling-self-test-dbgsym: 4.4.2-1 → 4.4.3-1
- ros-rolling-spinnaker-camera-driver: 3.0.0-1 → 3.0.1-1
- ros-rolling-spinnaker-camera-driver-dbgsym: 3.0.0-1 → 3.0.1-1
- ros-rolling-spinnaker-synchronized-camera-driver: 3.0.0-1 → 3.0.1-1
- ros-rolling-spinnaker-synchronized-camera-driver-dbgsym: 3.0.0-1 → 3.0.1-1
- ros-rolling-teleop-twist-joy: 2.6.2-1 → 2.6.3-1
- ros-rolling-teleop-twist-joy-dbgsym: 2.6.2-1 → 2.6.3-1
- ros-rolling-tile-map: 2.4.5-1 → 2.4.6-1
- ros-rolling-tile-map-dbgsym: 2.4.5-1 → 2.4.6-1
- ros-rolling-turtlebot3-fake-node: 2.2.5-4 → 2.3.2-1
- ros-rolling-turtlebot3-fake-node-dbgsym: 2.2.5-4 → 2.3.2-1
- ros-rolling-ur-client-library: 1.8.0-1 → 1.9.0-1
- ros-rolling-ur-client-library-dbgsym: 1.8.0-1 → 1.9.0-1
- ros-rolling-ur-description: 3.0.2-1 → 3.1.0-1
- ros-rolling-zed-msgs: 4.2.5-1 → 5.0.0-1
- ros-rolling-zed-msgs-dbgsym: 4.2.5-1 → 5.0.0-1
Removed Packages [34]:
- ros-rolling-behaviortree-cpp
- ros-rolling-behaviortree-cpp-dbgsym
- ros-rolling-behaviortree-cpp-v3
- ros-rolling-behaviortree-cpp-v3-dbgsym
- ros-rolling-data-tamer-cpp
- ros-rolling-data-tamer-cpp-dbgsym
- ros-rolling-fastrtps
- ros-rolling-fastrtps-dbgsym
- ros-rolling-fuse
- ros-rolling-fuse-constraints
- ros-rolling-fuse-constraints-dbgsym
- ros-rolling-fuse-core
- ros-rolling-fuse-core-dbgsym
- ros-rolling-fuse-graphs
- ros-rolling-fuse-graphs-dbgsym
- ros-rolling-fuse-loss
- ros-rolling-fuse-loss-dbgsym
- ros-rolling-fuse-models
- ros-rolling-fuse-models-dbgsym
- ros-rolling-fuse-optimizers
- ros-rolling-fuse-optimizers-dbgsym
- ros-rolling-fuse-publishers
- ros-rolling-fuse-publishers-dbgsym
- ros-rolling-fuse-tutorials
- ros-rolling-fuse-tutorials-dbgsym
- ros-rolling-fuse-variables
- ros-rolling-fuse-variables-dbgsym
- ros-rolling-fuse-viz
- ros-rolling-fuse-viz-dbgsym
- ros-rolling-ifm3d-core
- ros-rolling-septentrio-gnss-driver
- ros-rolling-septentrio-gnss-driver-dbgsym
- ros-rolling-tuw-geometry
- ros-rolling-tuw-geometry-dbgsym
The packages removed were failing to build due to regressions and the maintainers have been informed / fixes are underway. These packages will be restored in the next sync if new releases with fixes are bloomed by then.
Note:
fastrtps
was removed as the package was renamed tofastdds
- Regression on ROS 2 Buildfarm for Rolling · Issue #396 · locusrobotics/fuse · GitHub
- Regression on ROS 2 Buildfarm for Rolling · Issue #474 · ifm/ifm3d · GitHub
- Regression on ROS 2 Buildfarm for Rolling · Issue #5 · tuw-robotics/tuw_geometry · GitHub
- Regression on ROS 2 Buildfarm for Rolling · Issue #960 · BehaviorTree/BehaviorTree.CPP · GitHub
- Regression on ROS 2 Buildfarm for Rolling · Issue #155 · septentrio-gnss/septentrio_gnss_driver · GitHub
Thanks to all ROS maintainers who make packages available to the ROS community. The above list of packages was made possible by the work of the following maintainers:
- Alejandro Hernandez
- Alejandro Hernandez Cordero
- Alejandro Hernández
- Alexander Gutenkunst
- Apex.AI, Inc.
- Audrow Nash
- Austin Hendrix
- Bence Magyar
- Berkay Karaman
- Bernd Pfrommer
- Blake Anderson
- Brandon Ong
- Chittaranjan Srinivas Swaminathan
- Christian Henkel
- Christian Rauch
- Daan Wijffels
- David V. Lu!!
- Felix Exner
- Geoffrey Biggs
- Henning Kayser
- Ivan Paunovic
- Jose-Luis Blanco-Claraco
- Luis Camero
- M. Fatih Cırıt
- Mamoru Sobue
- Marc Alban
- Michael Görner
- Miguel Company
- MoveIt Release Team
- Paul Bovbel
- Peter David Fagan
- Pyo
- Ramon Wijnands
- Raul Sanchez Mateos
- Ryohsuke Mitsudome
- STEREOLABS
- Shane Loretz
- Southwest Research Institute
- Takagi, Isamu
- Temkei Kem
- Yukihiro Saito
- Yutaka Kondo
- kminoda
- mitsudome-r
1 post - 1 participant
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: RobotCAD 8.0.0 - Library - released!
This release integrates ready to use models library.
1 post - 1 participant
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: Understanding the benefits and challenges for adopting behavior trees
HI everyone,
This is my first interaction with the ROS community My name is Razan Ghzouli, and I am a PhD at Chalmers University.
I am trying to build knowledge about the benefits and challenges of using BTs in practice. There is not much information on capturing practitioners’ experience on this topic to improve things further. You can help by answering this short survey to build this knowledge (15 minutes). I would really appreciate it
3 posts - 2 participants
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: Continued Discussion: Uploading Robot Data to the Cloud | Cloud Robotics WG Meeting 2025-05-05
The next meeting for the Cloud Robotics Working Group will be at 2025-04-21T17:00:00Z UTC→2025-04-21T18:00:00Z UTC 2025-05-05T17:00:00Z UTC→2025-05-05T18:00:00Z UTC, where we will continue discussing uploading robot data to the cloud. We will attempt to come up with several categories of robotics, recommend the most important data to store for each category, and publish our work so that others can contribute. In the end, we hope to produce a reference for any developer looking to validate their own use of cloud storage.
Last meeting, we discussed how to collect information, and started working on a Google Doc to contain our work. The doc is available here: Data Collection Categories - Google Docs
If you would like to see the meeting, the recording is available on YouTube. Also, if you would like to propose a topic you are interested in discussing with the group, please add a comment on the Github Issue.
The meeting link is here, and you can sign up to our calendar or our Google Group for meeting notifications or keep an eye on the Cloud Robotics Hub.
Hopefully we will see you there!
2 posts - 1 participant
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: Deadline approaching for Diversity Scholarship ROSCon 2025
The deadline for the Diversity scholarship for ROSCon 2025 (this October in Singapore) is coming reaaalllyy soon, namely this Friday, 18th of April. So if you are thinking about applying, you should do it now.
Deadline: 2025-04-19T06:59:00Z UTC
Call for scholarship applications: ROSCon 2025
Direct form link: Google form.
If you know anyone from an minority group within robotics, that would qualify for this scholarship, please help us out and share this with them.
1 post - 1 participant
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: Rviz Publisher
Hi!
I’d like to show you a tool I’ve been working on and that I think could be useful to many people.
I suppose more than once some of you have had to create an RVIZ plugin, and you’ve probably been quite lost the first time, as always happens when you enter a new world. In my case, I’ve always ended up looking for someone else’s plugin to learn how to do it and seeing everything the QT library could offer. In the end, I’d end up wasting a day or two just making a simple panel to debug my application.
To avoid having to deal with QT, whether learning or simply having to design the application yourself, I’ve prepared the following package:
With this package, we can generate our own RVIZ plugin. For now, just a panel with buttons, where we can publish any messages we want.
Still in development, it’s based on the rosidl_defaults_generator function, which, for those who don’t know, is the package we use to create our custom messages and does the magic so we can use them jajaja. Let me tell you a little about how it works:
First, we add the following lines to the CMakeLists.txt
of the package that will generate a plugin:
find_package(rviz_publisher_cmake REQUIRED)
generate_rviz_panel(
<path_to_the_yaml>
)
Next, we configure the yaml file we’re going to add to our CMakeLists.txt
in a similar way:
panel:
- name: "Hello"
topic: "/example"
topic_type: "std_msgs/msg/String"
message:
data: "Hello, world!"
- name: "Forward"
topic: "/cmd_vel"
topic_type: "geometry_msgs/msg/Twist"
message:
linear:
x: 0.5
- name: "Move"
topic: "/cmd_vel"
topic_type: "geometry_msgs/msg/Twist"
message:
linear:
x: 0.5
y: 0.0
angular:
z: 0.5
Finally, we build, open rviz, add our panel, and magic happens.
So, nothing. I hope it’s useful to people who, as I’ve already said, don’t want to spend too much time creating their own plugin, although it’s always good to learn new things jeje.
And I’m posting this now, even though there’s still a lot missing, because I’d also like to gather ideas about what people would like to have, since I also plan to use it for actions, services, and to generate sliders…
Finally, I would like to say that I know that rviz is ultimately a tool used to visualize information, not to publish, and that rqt_publisher would also be used for that. However, having an all-in-one is always useful when you want to debug things, and having to switch windows or write in a terminal ends up being too repetitive, and I think this is going to help a lot.
Thank you very much for reading, and I hope it helps.
Best regards.
3 posts - 3 participants
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: ROS News for the Week of April 7th, 2025
ROS News for the Week of April 7th, 2025
Announcing the First Ever ROSCon UK!

It is official, ROS Noetic will go end-of-life on May 31, 2025.. I’ve put together some guidance on how to migrate to ROS 2.
Our friends at OpenCV are holding their first ever Conference! The event is schedule for May 12th, 2025 in San Jose, California.

Lots of interesting URDF news this week. Check out this cool automatic URDF generation paper @arjo129 found.There is also this handy tool to generate differential drive robots for Gazebo.
This week I came across this one dependency, pip-installable, easy to use camera calibration utility. This should make robot camera calibration so much easier!
Events
- 2025-04-11 Mistral AI Robotics Hackathon Paris
- 2025-04-14 ROS 2 Rust Meeting: April 2025
- 2025-04-17 Aerial Robotics Meeting
- 2025-04-18 ROSCon Diversity Scholarship applications due
- 2025-04-24 Autonomous Driving Meetup #6 Berlin
- 2025-04-28 International Workshop on Robotics Software Engineering
- 2025-04-30 Robotics Summit & Expo wsg @gbiggs.
- 2025-05-02 CFP Deadline for Space Robotics Workshop at IEEE SMC-IT/SCC
- 2025-05-05 ROSCon 2025 Workshop CFP Deadline
- 2025-05-11 CFP Deadline for Robotics & AI Track @ CppCon
- 2025-05-12 The OpenCV-SID Conference on Computer Vision & AI
- 2025-05-15 ROS-Industrial Consortium Americas 2025 Annual Meeting Detroit
- 2025-05-23 ROSConJP CFP Deadline
- 2025-05-23 ICRA 2025 Advancing Quantitative and QUAlitative SIMulators for marine applications
- 2025-05-24 ROS MeetUp in Cali, Colombia!
- 2025-05-30 => 2025-05-31 2025 Open Hardware Summit in Edinburgh
- 2025-06-02 ROSCon 2025 Talk Submission Deadline
- 2025-09-09 ROSCon JP in Nagoya
- 2025-09-15 => 2025-09-17 Inaugral ROSCon UK in Edinburgh
- 2025-10-27 =>2025-10-30 ROSCon Singapore
- 2025-11-17 => 2025-11-20 Joint ROSCon Germany and France
News
- Announcing the First Ever ROSCon UK!
- Introducing The OpenCV-SID Conference on Computer Vision & AI
- ROS PMC Minutes for April 8, 2025
- Heex Joins the Open Source Robotics Alliance (OSRA): Empowering the Future of Open Robotics
- Introducing the Audrow Nash Podcast Jobs Board
- These robotics companies are hiring
- CppCon 2025 Robotics and AI Track Call for Submissions!
- Embodied Intelligence: How AI is Powering the Next Generation of Robotics
- OSRA member Dexory wins the Jury Special Prize for Intralogistics Innovation at SITL 2025
- OSRA Member Seegrid’s Tom Panzarella wins 2025 CTO of the Year at the Pittsburgh Tech Council awards
- March 2025 Open Source Hardware Certification Roundup - Hackster.io
- How Chef Robotics found success by turning away its original customers
- Okibo opens New Jersey HQ and launches EG7 robot in U.S. market
- Saildrone brings its USVs to Europe with Denmark subsidiary
- BRINC raises $75M in funding for emergency response drones
ROS
- ROS Noetic End-of-Life: May 31, 2025
- ROS: Upcoming ROS 1 End of Life
- Upcoming ROS 2 Feature Freeze for Kilted Kaiju on April 14th
- Upcoming RMW Feature Freeze for ROS 2 Kilted Kaiju on April 7 2025
- What’s the current state of mirrors? Are there any ROS 2 mirrors?
- Generic Controller for Omnidirectional Robots using Omni Wheels
- New packages and patch release 4 for Jazzy Jalisco 2025-04-07
- New Packages for Noetic 2025-04-08
- Invitation to Collaborate on AsyncAPI Specification for ROS 2
- New ROSDep Search Tool
- Low-cost micro-ROS/LiDAR/Motor drivers board available commercially
- BeetleBot Differential Drive Robot Template for GZ sim ROS2
- Gatorcat: EtherCAT on Zenoh / ROS
- ROS 2 / Android Sensor Bridge
- All About The New OpenMV N6 & AE3 Cameras - OpenCV Live
- Gesture Based Mobile Robot Control in ROS 2
- The MBot Ecosystem: Open Source HW/SW Robot
- SOTA robust LiDAR odometry
- Depth Obstacle Detection ROS
- Workshop on how to develop ROS 2 applications using the Rust language
- Aerial Robotics Landscape
- Zero-Drift Point Cloud Mapping using Map Priors
- An alternative simulator to Gazebo for doing ROS 2 simulation
- MAVLink library for Rust
- Dynamic Initialization for LiDAR-inertial SLAM
- Overview about state-of-art imitation learning techniques for robotic manipulation
- Video: Basics of URDF Robot Modeling for ROS2 Jazzy: Links, Joints, and Frames
- Simple URDF Loading Example
- AutoURDF: Unsupervised Robot Modeling from Point Cloud Frames Using Cluster Registration
- ROS 2 Omni Robot Simulation
- Off-road driving by learning from interaction and demonstration - AirLab
- Pip Installable EZ Camera Calibration
- Convert various Autoware msg types to CSV file
- Kachaka ROS 2 Dev Kit
- Infinite Mobility: Scalable High-Fidelity Synthesis of Articulated Objects via Procedural Generation
- Real-is-Sim: Bridging the Sim-to-Real Gap with a Dynamic Digital Twin for Real-World Robot Policy Evaluation
Got a minute? 
A friendly fuzzer just dumped a bunch of issues in RViz and Geometry2. We would love to get these fixed before the Kilted feature freeze on 2025-04-14. If you have some time why not send us a pull request?
- Geometry2 #770: Overflow Issue in durationFromSec() Function when Handling Extremely Large or Small Values
- Geometry2 #771: operator== Comparison Logic Issue in TransformStorage
- Geometry2 #768: Data Overwrite Issue in StaticCache Class’s insertData and getData Methods
- Geometry2 #769: tf2::StaticCache::getData() Returns true Even When Cache is Empty or Timestamp Mismatches
- RViz #1356: Config Class Copy Constructor Issue
- RViz #1363: QosProfileProperty Destructor Fails to Properly Clean Up Child Properties, Leading to Memory Leak
- RViz #1364: Issue with SelectionManager::select Function Not Returning Empty Selection Result for Invalid Coordinates
- RViz #1371: SelectionManager Selection Issue Report
1 post - 1 participant
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: Generic Controller for Omnidirectional Robots using Omni Wheels
Hello everyone! I have made a ros2_controller for omnidirectional robots that are using 3 or more omni wheels.
I have made a PR, submitting this controller into the official repository so that it can have a wider reach, but the maintainers haven’t gotten the time yet to review and test the controller.
It would be really nice if someone from the community could go ahead and review/test the controller.
You can find the kinematics used by the controller in the official docs.
4 posts - 2 participants
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: ROS Noetic End-of-Life: May 31, 2025
Hello ROS Noetic users and maintainers!
This week the ROS PMC formally voted to set the Noetic end-of-life (EOL) date to May 31, 2025. This is the same day Ubuntu Focal reaches end of standard support.
I’m a ROS Noetic user, what do I need to know?
You need to know that it is time to upgrade! 80% of the ROS community has already made the switch.
We put together a single page of guidance for current ROS Noetic users who need to upgrade to ROS 2: ROS: Upcoming ROS 1 End of Life
I’m a ROS Noetic maintainer
How long do I have to make releases?
If you maintain a ROS Noetic repository and you haven’t made a release in a while, then you should make a release now.
There are only a few syncs left. The last two syncs will follow this schedule:
- May 13th:
- A ros/rosdistro freeze for the second to last sync begins
- You must bloom-release your package before this date to guarantee it is included in the second to last sync
- May 15th:
- The second to last sync is performed [1]
- May 16th:
- A freeze for the last sync begins
- You must bloom-release your package before this date to guarantee it is included in the last sync
- May 16th through May 29th:
- ros/rosdistro PRs will only be merged if they fix regressions
- ros/rosdistro PRs adding new features will not be merged
- ros/rosdistro PRs adding new packages will not be merged
- May 29th
- The last sync is performed [1]
- No new ROS Noetic ros/rosdistro PRs will be accepted
- May 31st - ROS Noetic is marked EOL
[1] The sync dates may be delayed if releases cause regressions that need to be resolved or rolled back.
What should maintainers do to prepare for EOL?
First, if you have unreleased changes, then make a release now.
There won’t be an opportunity to fix regressions in binary packages once ROS Noetic goes EOL, so consider reducing the risk of regressions when reviewing PRs by:
- Closing all pull requests breaking API or ABI
- Closing all pull requests adding new features
- Asking bug fix PR authors to recruit multiple reviewers to test it
Some users will build ROS Noetic from source, for example, to use the ros1_bridge. Consider merging PRs that make your package build on newer Ubuntu versions.
If your repository only supports ROS 1, and you are not going to maintain it after ROS Noetic goes EOL, then make that clear to your users on May 31, 2025 by:
- Closing open PRs and issues
- Archiving the repo
If your repository supports ROS 1 and ROS 2, then make sure the default branch supports ROS 2, preferably ROS Rolling.
9 posts - 4 participants
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: Rosdep search
Greetings fellow roboticists,
if you’re a commendable package creator and always try to specify all your dependencies, you might know the struggle of trying to guess the right dependency key.
Maybe you’re lucky and guess it; otherwise, you have to take the cumbersome route of visiting the rosdep repo and checking the base.yaml
for the key for your dependency.
This should really be easier, shouldn’t it?
Well, now it can be!
I’ve added a search
command to rosdep in my fork and opened a PR #997.
This command enables you to simply search your rosdep database (which can also include additional sources to the official ones) for the keys matching your search with 1 allowed error (missing, wrong, or extra letter).
It checks both for keys and packages, so you can search for the package name in your Linux distros package manager.
Examples:
$ rosdep search libpcl-dev
Closest keys:
libfcl-dev
Closest packages:
libpcl-all-dev: libpcl-dev [debian]
libpcl-all-dev: libpcl-dev [ubuntu]
acl: libacl-devel [fedora]
acl: libacl-devel [rhel]
$ rosdep search pinoccio
Closest keys:
kinematics_interface_pinocchio
pinocchio
I hope this will be useful for you and this post helps get the PR some attention so it can be finalized and merged in a timely fashion
If it wasn’t useful, here’s a picture to make up for your time:
5 posts - 4 participants
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: New Packages for Noetic 2025-04-08
We’re happy to announce 2 new packages and 5 updates are now available in ROS Noetic. This sync was tagged as noetic/2025-04-08
.
Package Updates for noetic
Added Packages [2]:
- ros-noetic-qoi-image-transport: 1.0.4-1
- ros-noetic-qoi-image-transport-dbgsym: 1.0.4-1
Updated Packages [5]:
- ros-noetic-depthai: 2.29.0-1 → 2.30.0-1
- ros-noetic-depthai-dbgsym: 2.29.0-1 → 2.30.0-1
- ros-noetic-ur-client-library: 1.8.0-1 → 1.9.0-1
- ros-noetic-ur-client-library-dbgsym: 1.8.0-1 → 1.9.0-1
- ros-noetic-xacro: 1.14.19-1 → 1.14.20-1
Removed Packages [0]:
Thanks to all ROS maintainers who make packages available to the ROS community. The above list of packages was made possible by the work of the following maintainers:
- Adam Serafin
- Felix Exner
- Martin Pecka
- Robert Haschke
1 post - 1 participant
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: CppCon 2025 Robotics and AI Track Call for Submissions!
The C++ programming community is excited to announce the Robotics and AI Track for the upcoming CppCon 2025, taking place on-site at the Gaylord Rockies in Aurora, Colorado September 13th-19th. We invite robotics practitioners from industry, academia, and the hobbyist domain to share their insights, experiences, and knowledge about using C++ in a robotics context.
Deadline for Submission is May 11th!
The track has a focus on C++ used in a Robotics or AI context so that we can share best practices and strengthen our community. It differs from events such as ROSCon or ICRA as it has an emphasis on code on slides and talks are typically 1 hour long.
Last year’s presentations included:
- Code generation for optimized forward kinematics
- Modern implementation of particle filters using range adaptors
- Parameterized test case generation for autonomous driving
Below is a playlist of presentations from last year’s track as well as 2023, which should give you an idea of the subject matter and C++ emphasis the track welcomes.
CppCon 2024 Robotics Track Playlist
CppCon 2023 Robotics Track Playlist
For more information (and links to submit your talk proposal) see this longer post here:
Deadline for Submission is May 11th!
1 post - 1 participant
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: New packages and patch release 4 for Jazzy Jalisco 2025-04-07
We’re happy to announce 24 new packages and 473 updates are now available on Ubuntu Noble
on amd64
for Jazzy Jalisco.
This sync was tagged as jazzy/2025-04-07
.
Package Updates for jazzy
Added Packages [24]:
- ros-jazzy-clearpath-generator-gz: 2.2.0-1
- ros-jazzy-clearpath-gz: 2.2.0-1
- ros-jazzy-clearpath-simulator: 2.2.0-1
- ros-jazzy-clearpath-tests: 0.2.9-1
- ros-jazzy-dynamixel-hardware-interface: 1.4.1-1
- ros-jazzy-dynamixel-hardware-interface-dbgsym: 1.4.1-1
- ros-jazzy-ld08-driver: 1.1.1-1
- ros-jazzy-ld08-driver-dbgsym: 1.1.1-1
- ros-jazzy-multisensor-calibration: 2.0.3-1
- ros-jazzy-multisensor-calibration-dbgsym: 2.0.3-1
- ros-jazzy-multisensor-calibration-interface: 2.0.3-1
- ros-jazzy-multisensor-calibration-interface-dbgsym: 2.0.3-1
- ros-jazzy-nobleo-socketcan-bridge: 1.0.2-1
- ros-jazzy-nobleo-socketcan-bridge-dbgsym: 1.0.2-1
- ros-jazzy-ros2-control-cmake: 0.1.1-1
- ros-jazzy-slg-msgs: 3.9.2-1
- ros-jazzy-slg-msgs-dbgsym: 3.9.2-1
- ros-jazzy-small-gicp-vendor: 2.0.3-1
- ros-jazzy-small-gicp-vendor-dbgsym: 2.0.3-1
- ros-jazzy-turtlebot3-gazebo: 2.3.2-1
- ros-jazzy-turtlebot3-gazebo-dbgsym: 2.3.2-1
- ros-jazzy-turtlebot3-simulations: 2.3.2-1
- ros-jazzy-zed-msgs: 5.0.0-1
- ros-jazzy-zed-msgs-dbgsym: 5.0.0-1
Updated Packages [473]:
- ros-jazzy-ackermann-steering-controller: 4.21.0-1 → 4.22.0-1
- ros-jazzy-ackermann-steering-controller-dbgsym: 4.21.0-1 → 4.22.0-1
- ros-jazzy-actionlib-msgs: 5.3.5-1 → 5.3.6-1
- ros-jazzy-actionlib-msgs-dbgsym: 5.3.5-1 → 5.3.6-1
- ros-jazzy-admittance-controller: 4.21.0-1 → 4.22.0-1
- ros-jazzy-admittance-controller-dbgsym: 4.21.0-1 → 4.22.0-1
- ros-jazzy-ament-clang-format: 0.17.1-1 → 0.17.2-1
- ros-jazzy-ament-clang-tidy: 0.17.1-1 → 0.17.2-1
- ros-jazzy-ament-cmake-clang-format: 0.17.1-1 → 0.17.2-1
- ros-jazzy-ament-cmake-clang-tidy: 0.17.1-1 → 0.17.2-1
- ros-jazzy-ament-cmake-copyright: 0.17.1-1 → 0.17.2-1
- ros-jazzy-ament-cmake-cppcheck: 0.17.1-1 → 0.17.2-1
- ros-jazzy-ament-cmake-cpplint: 0.17.1-1 → 0.17.2-1
- ros-jazzy-ament-cmake-flake8: 0.17.1-1 → 0.17.2-1
- ros-jazzy-ament-cmake-lint-cmake: 0.17.1-1 → 0.17.2-1
- ros-jazzy-ament-cmake-mypy: 0.17.1-1 → 0.17.2-1
- ros-jazzy-ament-cmake-pclint: 0.17.1-1 → 0.17.2-1
- ros-jazzy-ament-cmake-pep257: 0.17.1-1 → 0.17.2-1
- ros-jazzy-ament-cmake-pycodestyle: 0.17.1-1 → 0.17.2-1
- ros-jazzy-ament-cmake-pyflakes: 0.17.1-1 → 0.17.2-1
- ros-jazzy-ament-cmake-uncrustify: 0.17.1-1 → 0.17.2-1
- ros-jazzy-ament-cmake-xmllint: 0.17.1-1 → 0.17.2-1
- ros-jazzy-ament-copyright: 0.17.1-1 → 0.17.2-1
- ros-jazzy-ament-cppcheck: 0.17.1-1 → 0.17.2-1
- ros-jazzy-ament-cpplint: 0.17.1-1 → 0.17.2-1
- ros-jazzy-ament-flake8: 0.17.1-1 → 0.17.2-1
- ros-jazzy-ament-lint: 0.17.1-1 → 0.17.2-1
- ros-jazzy-ament-lint-auto: 0.17.1-1 → 0.17.2-1
- ros-jazzy-ament-lint-cmake: 0.17.1-1 → 0.17.2-1
- ros-jazzy-ament-lint-common: 0.17.1-1 → 0.17.2-1
- ros-jazzy-ament-mypy: 0.17.1-1 → 0.17.2-1
- ros-jazzy-ament-package: 0.16.3-3 → 0.16.4-1
- ros-jazzy-ament-pclint: 0.17.1-1 → 0.17.2-1
- ros-jazzy-ament-pep257: 0.17.1-1 → 0.17.2-1
- ros-jazzy-ament-pycodestyle: 0.17.1-1 → 0.17.2-1
- ros-jazzy-ament-pyflakes: 0.17.1-1 → 0.17.2-1
- ros-jazzy-ament-uncrustify: 0.17.1-1 → 0.17.2-1
- ros-jazzy-ament-xmllint: 0.17.1-1 → 0.17.2-1
- ros-jazzy-autoware-cmake: 1.0.0-1 → 1.0.1-1
- ros-jazzy-autoware-common-msgs: 1.3.0-1 → 1.4.0-1
- ros-jazzy-autoware-common-msgs-dbgsym: 1.3.0-1 → 1.4.0-1
- ros-jazzy-autoware-control-msgs: 1.3.0-1 → 1.4.0-1
- ros-jazzy-autoware-control-msgs-dbgsym: 1.3.0-1 → 1.4.0-1
- ros-jazzy-autoware-lanelet2-extension: 0.6.2-1 → 0.7.0-1
- ros-jazzy-autoware-lanelet2-extension-dbgsym: 0.6.2-1 → 0.7.0-1
- ros-jazzy-autoware-lanelet2-extension-python: 0.6.2-1 → 0.7.0-1
- ros-jazzy-autoware-lanelet2-extension-python-dbgsym: 0.6.2-1 → 0.7.0-1
- ros-jazzy-autoware-lint-common: 1.0.0-1 → 1.0.1-1
- ros-jazzy-autoware-localization-msgs: 1.3.0-1 → 1.4.0-1
- ros-jazzy-autoware-localization-msgs-dbgsym: 1.3.0-1 → 1.4.0-1
- ros-jazzy-autoware-map-msgs: 1.3.0-1 → 1.4.0-1
- ros-jazzy-autoware-map-msgs-dbgsym: 1.3.0-1 → 1.4.0-1
- ros-jazzy-autoware-perception-msgs: 1.3.0-1 → 1.4.0-1
- ros-jazzy-autoware-perception-msgs-dbgsym: 1.3.0-1 → 1.4.0-1
- ros-jazzy-autoware-planning-msgs: 1.3.0-1 → 1.4.0-1
- ros-jazzy-autoware-planning-msgs-dbgsym: 1.3.0-1 → 1.4.0-1
- ros-jazzy-autoware-sensing-msgs: 1.3.0-1 → 1.4.0-1
- ros-jazzy-autoware-sensing-msgs-dbgsym: 1.3.0-1 → 1.4.0-1
- ros-jazzy-autoware-system-msgs: 1.3.0-1 → 1.4.0-1
- ros-jazzy-autoware-system-msgs-dbgsym: 1.3.0-1 → 1.4.0-1
- ros-jazzy-autoware-v2x-msgs: 1.3.0-1 → 1.4.0-1
- ros-jazzy-autoware-v2x-msgs-dbgsym: 1.3.0-1 → 1.4.0-1
- ros-jazzy-autoware-vehicle-msgs: 1.3.0-1 → 1.4.0-1
- ros-jazzy-autoware-vehicle-msgs-dbgsym: 1.3.0-1 → 1.4.0-1
- ros-jazzy-bicycle-steering-controller: 4.21.0-1 → 4.22.0-1
- ros-jazzy-bicycle-steering-controller-dbgsym: 4.21.0-1 → 4.22.0-1
- ros-jazzy-camera-calibration-parsers: 5.1.5-1 → 5.1.6-1
- ros-jazzy-camera-calibration-parsers-dbgsym: 5.1.5-1 → 5.1.6-1
- ros-jazzy-camera-info-manager: 5.1.5-1 → 5.1.6-1
- ros-jazzy-camera-info-manager-dbgsym: 5.1.5-1 → 5.1.6-1
- ros-jazzy-camera-info-manager-py: 5.1.5-1 → 5.1.6-1
- ros-jazzy-clearpath-bt-joy: 2.1.0-1 → 2.2.0-1
- ros-jazzy-clearpath-common: 2.1.0-1 → 2.2.0-1
- ros-jazzy-clearpath-config: 2.1.1-1 → 2.2.2-1
- ros-jazzy-clearpath-control: 2.1.0-1 → 2.2.0-1
- ros-jazzy-clearpath-customization: 2.1.0-1 → 2.2.0-1
- ros-jazzy-clearpath-description: 2.1.0-1 → 2.2.0-1
- ros-jazzy-clearpath-generator-common: 2.1.0-1 → 2.2.0-1
- ros-jazzy-clearpath-generator-common-dbgsym: 2.1.0-1 → 2.2.0-1
- ros-jazzy-clearpath-manipulators: 2.1.0-1 → 2.2.0-1
- ros-jazzy-clearpath-manipulators-description: 2.1.0-1 → 2.2.0-1
- ros-jazzy-clearpath-motor-msgs: 2.1.0-1 → 2.2.2-1
- ros-jazzy-clearpath-motor-msgs-dbgsym: 2.1.0-1 → 2.2.2-1
- ros-jazzy-clearpath-mounts-description: 2.1.0-1 → 2.2.0-1
- ros-jazzy-clearpath-msgs: 2.1.0-1 → 2.2.2-1
- ros-jazzy-clearpath-platform-description: 2.1.0-1 → 2.2.0-1
- ros-jazzy-clearpath-platform-msgs: 2.1.0-1 → 2.2.2-1
- ros-jazzy-clearpath-platform-msgs-dbgsym: 2.1.0-1 → 2.2.2-1
- ros-jazzy-clearpath-sensors-description: 2.1.0-1 → 2.2.0-1
- ros-jazzy-common-interfaces: 5.3.5-1 → 5.3.6-1
- ros-jazzy-control-msgs: 5.3.0-1 → 5.4.0-1
- ros-jazzy-control-msgs-dbgsym: 5.3.0-1 → 5.4.0-1
- ros-jazzy-dataspeed-can: 2.0.5-1 → 2.0.6-1
- ros-jazzy-dataspeed-can-msg-filters: 2.0.5-1 → 2.0.6-1
- ros-jazzy-dataspeed-can-msgs: 2.0.5-1 → 2.0.6-1
- ros-jazzy-dataspeed-can-msgs-dbgsym: 2.0.5-1 → 2.0.6-1
- ros-jazzy-dataspeed-can-tools: 2.0.5-1 → 2.0.6-1
- ros-jazzy-dataspeed-can-tools-dbgsym: 2.0.5-1 → 2.0.6-1
- ros-jazzy-dataspeed-can-usb: 2.0.5-1 → 2.0.6-1
- ros-jazzy-dataspeed-can-usb-dbgsym: 2.0.5-1 → 2.0.6-1
- ros-jazzy-depthai: 2.29.0-1 → 2.30.0-1
- ros-jazzy-depthai-bridge: 2.11.0-1 → 2.11.2-1
- ros-jazzy-depthai-bridge-dbgsym: 2.11.0-1 → 2.11.2-1
- ros-jazzy-depthai-dbgsym: 2.29.0-1 → 2.30.0-1
- ros-jazzy-depthai-descriptions: 2.11.0-1 → 2.11.2-1
- ros-jazzy-depthai-examples: 2.11.0-1 → 2.11.2-1
- ros-jazzy-depthai-examples-dbgsym: 2.11.0-1 → 2.11.2-1
- ros-jazzy-depthai-filters: 2.11.0-1 → 2.11.2-1
- ros-jazzy-depthai-filters-dbgsym: 2.11.0-1 → 2.11.2-1
- ros-jazzy-depthai-ros: 2.11.0-1 → 2.11.2-1
- ros-jazzy-depthai-ros-driver: 2.11.0-1 → 2.11.2-1
- ros-jazzy-depthai-ros-driver-dbgsym: 2.11.0-1 → 2.11.2-1
- ros-jazzy-depthai-ros-msgs: 2.11.0-1 → 2.11.2-1
- ros-jazzy-depthai-ros-msgs-dbgsym: 2.11.0-1 → 2.11.2-1
- ros-jazzy-diagnostic-msgs: 5.3.5-1 → 5.3.6-1
- ros-jazzy-diagnostic-msgs-dbgsym: 5.3.5-1 → 5.3.6-1
- ros-jazzy-diff-drive-controller: 4.21.0-1 → 4.22.0-1
- ros-jazzy-diff-drive-controller-dbgsym: 4.21.0-1 → 4.22.0-1
- ros-jazzy-ds-dbw: 2.3.2-1 → 2.3.3-1
- ros-jazzy-ds-dbw-can: 2.3.2-1 → 2.3.3-1
- ros-jazzy-ds-dbw-can-dbgsym: 2.3.2-1 → 2.3.3-1
- ros-jazzy-ds-dbw-joystick-demo: 2.3.2-1 → 2.3.3-1
- ros-jazzy-ds-dbw-joystick-demo-dbgsym: 2.3.2-1 → 2.3.3-1
- ros-jazzy-ds-dbw-msgs: 2.3.2-1 → 2.3.3-1
- ros-jazzy-ds-dbw-msgs-dbgsym: 2.3.2-1 → 2.3.3-1
- ros-jazzy-dynamixel-interfaces: 1.0.0-1 → 1.0.1-1
- ros-jazzy-dynamixel-interfaces-dbgsym: 1.0.0-1 → 1.0.1-1
- ros-jazzy-dynamixel-sdk: 3.8.1-1 → 3.8.3-1
- ros-jazzy-dynamixel-sdk-custom-interfaces: 3.8.1-1 → 3.8.3-1
- ros-jazzy-dynamixel-sdk-custom-interfaces-dbgsym: 3.8.1-1 → 3.8.3-1
- ros-jazzy-dynamixel-sdk-dbgsym: 3.8.1-1 → 3.8.3-1
- ros-jazzy-dynamixel-sdk-examples: 3.8.1-1 → 3.8.3-1
- ros-jazzy-dynamixel-sdk-examples-dbgsym: 3.8.1-1 → 3.8.3-1
- ros-jazzy-dynamixel-workbench: 2.2.3-5 → 2.2.4-1
- ros-jazzy-dynamixel-workbench-toolbox: 2.2.3-5 → 2.2.4-1
- ros-jazzy-dynamixel-workbench-toolbox-dbgsym: 2.2.3-5 → 2.2.4-1
- ros-jazzy-effort-controllers: 4.21.0-1 → 4.22.0-1
- ros-jazzy-effort-controllers-dbgsym: 4.21.0-1 → 4.22.0-1
- ros-jazzy-examples-rclcpp-async-client: 0.19.4-1 → 0.19.5-1
- ros-jazzy-examples-rclcpp-async-client-dbgsym: 0.19.4-1 → 0.19.5-1
- ros-jazzy-examples-rclcpp-cbg-executor: 0.19.4-1 → 0.19.5-1
- ros-jazzy-examples-rclcpp-cbg-executor-dbgsym: 0.19.4-1 → 0.19.5-1
- ros-jazzy-examples-rclcpp-minimal-action-client: 0.19.4-1 → 0.19.5-1
- ros-jazzy-examples-rclcpp-minimal-action-client-dbgsym: 0.19.4-1 → 0.19.5-1
- ros-jazzy-examples-rclcpp-minimal-action-server: 0.19.4-1 → 0.19.5-1
- ros-jazzy-examples-rclcpp-minimal-action-server-dbgsym: 0.19.4-1 → 0.19.5-1
- ros-jazzy-examples-rclcpp-minimal-client: 0.19.4-1 → 0.19.5-1
- ros-jazzy-examples-rclcpp-minimal-client-dbgsym: 0.19.4-1 → 0.19.5-1
- ros-jazzy-examples-rclcpp-minimal-composition: 0.19.4-1 → 0.19.5-1
- ros-jazzy-examples-rclcpp-minimal-composition-dbgsym: 0.19.4-1 → 0.19.5-1
- ros-jazzy-examples-rclcpp-minimal-publisher: 0.19.4-1 → 0.19.5-1
- ros-jazzy-examples-rclcpp-minimal-publisher-dbgsym: 0.19.4-1 → 0.19.5-1
- ros-jazzy-examples-rclcpp-minimal-service: 0.19.4-1 → 0.19.5-1
- ros-jazzy-examples-rclcpp-minimal-service-dbgsym: 0.19.4-1 → 0.19.5-1
- ros-jazzy-examples-rclcpp-minimal-subscriber: 0.19.4-1 → 0.19.5-1
- ros-jazzy-examples-rclcpp-minimal-subscriber-dbgsym: 0.19.4-1 → 0.19.5-1
- ros-jazzy-examples-rclcpp-minimal-timer: 0.19.4-1 → 0.19.5-1
- ros-jazzy-examples-rclcpp-minimal-timer-dbgsym: 0.19.4-1 → 0.19.5-1
- ros-jazzy-examples-rclcpp-multithreaded-executor: 0.19.4-1 → 0.19.5-1
- ros-jazzy-examples-rclcpp-multithreaded-executor-dbgsym: 0.19.4-1 → 0.19.5-1
- ros-jazzy-examples-rclcpp-wait-set: 0.19.4-1 → 0.19.5-1
- ros-jazzy-examples-rclcpp-wait-set-dbgsym: 0.19.4-1 → 0.19.5-1
- ros-jazzy-examples-rclpy-executors: 0.19.4-1 → 0.19.5-1
- ros-jazzy-examples-rclpy-guard-conditions: 0.19.4-1 → 0.19.5-1
- ros-jazzy-examples-rclpy-minimal-action-client: 0.19.4-1 → 0.19.5-1
- ros-jazzy-examples-rclpy-minimal-action-server: 0.19.4-1 → 0.19.5-1
- ros-jazzy-examples-rclpy-minimal-client: 0.19.4-1 → 0.19.5-1
- ros-jazzy-examples-rclpy-minimal-publisher: 0.19.4-1 → 0.19.5-1
- ros-jazzy-examples-rclpy-minimal-service: 0.19.4-1 → 0.19.5-1
- ros-jazzy-examples-rclpy-minimal-subscriber: 0.19.4-1 → 0.19.5-1
- ros-jazzy-examples-rclpy-pointcloud-publisher: 0.19.4-1 → 0.19.5-1
- ros-jazzy-examples-tf2-py: 0.36.8-1 → 0.36.9-1
- ros-jazzy-ffmpeg-encoder-decoder: 1.0.1-1 → 2.0.0-1
- ros-jazzy-ffmpeg-encoder-decoder-dbgsym: 1.0.1-1 → 2.0.0-1
- ros-jazzy-ffmpeg-image-transport: 1.0.2-1 → 2.0.2-1
- ros-jazzy-ffmpeg-image-transport-dbgsym: 1.0.2-1 → 2.0.2-1
- ros-jazzy-ffmpeg-image-transport-tools: 1.0.1-2 → 2.1.1-1
- ros-jazzy-ffmpeg-image-transport-tools-dbgsym: 1.0.1-2 → 2.1.1-1
- ros-jazzy-flir-camera-description: 3.0.0-1 → 3.0.1-1
- ros-jazzy-flir-camera-msgs: 3.0.0-1 → 3.0.1-1
- ros-jazzy-flir-camera-msgs-dbgsym: 3.0.0-1 → 3.0.1-1
- ros-jazzy-force-torque-sensor-broadcaster: 4.21.0-1 → 4.22.0-1
- ros-jazzy-force-torque-sensor-broadcaster-dbgsym: 4.21.0-1 → 4.22.0-1
- ros-jazzy-forward-command-controller: 4.21.0-1 → 4.22.0-1
- ros-jazzy-forward-command-controller-dbgsym: 4.21.0-1 → 4.22.0-1
- ros-jazzy-foxglove-compressed-video-transport: 1.0.1-1 → 1.0.2-1
- ros-jazzy-foxglove-compressed-video-transport-dbgsym: 1.0.1-1 → 1.0.2-1
- ros-jazzy-geometry-msgs: 5.3.5-1 → 5.3.6-1
- ros-jazzy-geometry-msgs-dbgsym: 5.3.5-1 → 5.3.6-1
- ros-jazzy-geometry2: 0.36.8-1 → 0.36.9-1
- ros-jazzy-gpio-controllers: 4.21.0-1 → 4.22.0-1
- ros-jazzy-gpio-controllers-dbgsym: 4.21.0-1 → 4.22.0-1
- ros-jazzy-gripper-controllers: 4.21.0-1 → 4.22.0-1
- ros-jazzy-gripper-controllers-dbgsym: 4.21.0-1 → 4.22.0-1
- ros-jazzy-image-common: 5.1.5-1 → 5.1.6-1
- ros-jazzy-image-transport: 5.1.5-1 → 5.1.6-1
- ros-jazzy-image-transport-dbgsym: 5.1.5-1 → 5.1.6-1
- ros-jazzy-imu-sensor-broadcaster: 4.21.0-1 → 4.22.0-1
- ros-jazzy-imu-sensor-broadcaster-dbgsym: 4.21.0-1 → 4.22.0-1
- ros-jazzy-joint-state-broadcaster: 4.21.0-1 → 4.22.0-1
- ros-jazzy-joint-state-broadcaster-dbgsym: 4.21.0-1 → 4.22.0-1
- ros-jazzy-joint-trajectory-controller: 4.21.0-1 → 4.22.0-1
- ros-jazzy-joint-trajectory-controller-dbgsym: 4.21.0-1 → 4.22.0-1
- ros-jazzy-kinematics-interface: 1.2.1-1 → 1.3.0-1
- ros-jazzy-kinematics-interface-dbgsym: 1.2.1-1 → 1.3.0-1
- ros-jazzy-kinematics-interface-kdl: 1.2.1-1 → 1.3.0-1
- ros-jazzy-kinematics-interface-kdl-dbgsym: 1.2.1-1 → 1.3.0-1
- ros-jazzy-kitti-metrics-eval: 1.6.2-1 → 1.6.3-1
- ros-jazzy-kitti-metrics-eval-dbgsym: 1.6.2-1 → 1.6.3-1
- ros-jazzy-launch: 3.4.3-1 → 3.4.4-1
- ros-jazzy-launch-pytest: 3.4.3-1 → 3.4.4-1
- ros-jazzy-launch-ros: 0.26.6-1 → 0.26.7-1
- ros-jazzy-launch-testing: 3.4.3-1 → 3.4.4-1
- ros-jazzy-launch-testing-ament-cmake: 3.4.3-1 → 3.4.4-1
- ros-jazzy-launch-testing-examples: 0.19.4-1 → 0.19.5-1
- ros-jazzy-launch-testing-ros: 0.26.6-1 → 0.26.7-1
- ros-jazzy-launch-xml: 3.4.3-1 → 3.4.4-1
- ros-jazzy-launch-yaml: 3.4.3-1 → 3.4.4-1
- ros-jazzy-libcurl-vendor: 3.4.3-1 → 3.4.4-1
- ros-jazzy-mapviz: 2.4.5-1 → 2.4.6-1
- ros-jazzy-mapviz-dbgsym: 2.4.5-1 → 2.4.6-1
- ros-jazzy-mapviz-interfaces: 2.4.5-1 → 2.4.6-1
- ros-jazzy-mapviz-interfaces-dbgsym: 2.4.5-1 → 2.4.6-1
- ros-jazzy-mapviz-plugins: 2.4.5-1 → 2.4.6-1
- ros-jazzy-mapviz-plugins-dbgsym: 2.4.5-1 → 2.4.6-1
- ros-jazzy-mecanum-drive-controller: 4.21.0-1 → 4.22.0-1
- ros-jazzy-mecanum-drive-controller-dbgsym: 4.21.0-1 → 4.22.0-1
- ros-jazzy-message-filters: 4.11.4-1 → 4.11.5-1
- ros-jazzy-message-filters-dbgsym: 4.11.4-1 → 4.11.5-1
- ros-jazzy-metavision-driver: 2.0.0-1 → 2.0.1-1
- ros-jazzy-metavision-driver-dbgsym: 2.0.0-1 → 2.0.1-1
- ros-jazzy-mola: 1.6.2-1 → 1.6.3-1
- ros-jazzy-mola-bridge-ros2: 1.6.2-1 → 1.6.3-1
- ros-jazzy-mola-bridge-ros2-dbgsym: 1.6.2-1 → 1.6.3-1
- ros-jazzy-mola-demos: 1.6.2-1 → 1.6.3-1
- ros-jazzy-mola-imu-preintegration: 1.7.0-1 → 1.8.0-1
- ros-jazzy-mola-imu-preintegration-dbgsym: 1.7.0-1 → 1.8.0-1
- ros-jazzy-mola-input-euroc-dataset: 1.6.2-1 → 1.6.3-1
- ros-jazzy-mola-input-euroc-dataset-dbgsym: 1.6.2-1 → 1.6.3-1
- ros-jazzy-mola-input-kitti-dataset: 1.6.2-1 → 1.6.3-1
- ros-jazzy-mola-input-kitti-dataset-dbgsym: 1.6.2-1 → 1.6.3-1
- ros-jazzy-mola-input-kitti360-dataset: 1.6.2-1 → 1.6.3-1
- ros-jazzy-mola-input-kitti360-dataset-dbgsym: 1.6.2-1 → 1.6.3-1
- ros-jazzy-mola-input-mulran-dataset: 1.6.2-1 → 1.6.3-1
- ros-jazzy-mola-input-mulran-dataset-dbgsym: 1.6.2-1 → 1.6.3-1
- ros-jazzy-mola-input-paris-luco-dataset: 1.6.2-1 → 1.6.3-1
- ros-jazzy-mola-input-paris-luco-dataset-dbgsym: 1.6.2-1 → 1.6.3-1
- ros-jazzy-mola-input-rawlog: 1.6.2-1 → 1.6.3-1
- ros-jazzy-mola-input-rawlog-dbgsym: 1.6.2-1 → 1.6.3-1
- ros-jazzy-mola-input-rosbag2: 1.6.2-1 → 1.6.3-1
- ros-jazzy-mola-input-rosbag2-dbgsym: 1.6.2-1 → 1.6.3-1
- ros-jazzy-mola-kernel: 1.6.2-1 → 1.6.3-1
- ros-jazzy-mola-kernel-dbgsym: 1.6.2-1 → 1.6.3-1
- ros-jazzy-mola-launcher: 1.6.2-1 → 1.6.3-1
- ros-jazzy-mola-launcher-dbgsym: 1.6.2-1 → 1.6.3-1
- ros-jazzy-mola-lidar-odometry: 0.7.0-1 → 0.7.1-1
- ros-jazzy-mola-lidar-odometry-dbgsym: 0.7.0-1 → 0.7.1-1
- ros-jazzy-mola-metric-maps: 1.6.2-1 → 1.6.3-1
- ros-jazzy-mola-metric-maps-dbgsym: 1.6.2-1 → 1.6.3-1
- ros-jazzy-mola-msgs: 1.6.2-1 → 1.6.3-1
- ros-jazzy-mola-msgs-dbgsym: 1.6.2-1 → 1.6.3-1
- ros-jazzy-mola-pose-list: 1.6.2-1 → 1.6.3-1
- ros-jazzy-mola-pose-list-dbgsym: 1.6.2-1 → 1.6.3-1
- ros-jazzy-mola-relocalization: 1.6.2-1 → 1.6.3-1
- ros-jazzy-mola-relocalization-dbgsym: 1.6.2-1 → 1.6.3-1
- ros-jazzy-mola-state-estimation: 1.7.0-1 → 1.8.0-1
- ros-jazzy-mola-state-estimation-simple: 1.7.0-1 → 1.8.0-1
- ros-jazzy-mola-state-estimation-simple-dbgsym: 1.7.0-1 → 1.8.0-1
- ros-jazzy-mola-state-estimation-smoother: 1.7.0-1 → 1.8.0-1
- ros-jazzy-mola-state-estimation-smoother-dbgsym: 1.7.0-1 → 1.8.0-1
- ros-jazzy-mola-traj-tools: 1.6.2-1 → 1.6.3-1
- ros-jazzy-mola-traj-tools-dbgsym: 1.6.2-1 → 1.6.3-1
- ros-jazzy-mola-viz: 1.6.2-1 → 1.6.3-1
- ros-jazzy-mola-viz-dbgsym: 1.6.2-1 → 1.6.3-1
- ros-jazzy-mola-yaml: 1.6.2-1 → 1.6.3-1
- ros-jazzy-mola-yaml-dbgsym: 1.6.2-1 → 1.6.3-1
- ros-jazzy-multires-image: 2.4.5-1 → 2.4.6-1
- ros-jazzy-multires-image-dbgsym: 2.4.5-1 → 2.4.6-1
- ros-jazzy-nav-msgs: 5.3.5-1 → 5.3.6-1
- ros-jazzy-nav-msgs-dbgsym: 5.3.5-1 → 5.3.6-1
- ros-jazzy-novatel-oem7-driver: 24.0.0-1 → 24.1.0-1
- ros-jazzy-novatel-oem7-driver-dbgsym: 24.0.0-1 → 24.1.0-1
- ros-jazzy-novatel-oem7-msgs: 24.0.0-1 → 24.1.0-1
- ros-jazzy-novatel-oem7-msgs-dbgsym: 24.0.0-1 → 24.1.0-1
- ros-jazzy-openeb-vendor: 2.0.1-1 → 2.0.2-2
- ros-jazzy-openeb-vendor-dbgsym: 2.0.1-1 → 2.0.2-2
- ros-jazzy-osrf-pycommon: 2.1.5-1 → 2.1.6-1
- ros-jazzy-parallel-gripper-controller: 4.21.0-1 → 4.22.0-1
- ros-jazzy-parallel-gripper-controller-dbgsym: 4.21.0-1 → 4.22.0-1
- ros-jazzy-picknik-reset-fault-controller: 0.0.3-3 → 0.0.4-1
- ros-jazzy-picknik-reset-fault-controller-dbgsym: 0.0.3-3 → 0.0.4-1
- ros-jazzy-picknik-twist-controller: 0.0.3-3 → 0.0.4-1
- ros-jazzy-picknik-twist-controller-dbgsym: 0.0.3-3 → 0.0.4-1
- ros-jazzy-pid-controller: 4.21.0-1 → 4.22.0-1
- ros-jazzy-pid-controller-dbgsym: 4.21.0-1 → 4.22.0-1
- ros-jazzy-pinocchio: 2.6.21-3 → 3.4.0-2
- ros-jazzy-pinocchio-dbgsym: 2.6.21-3 → 3.4.0-2
- ros-jazzy-point-cloud-transport: 4.0.3-1 → 4.0.4-1
- ros-jazzy-point-cloud-transport-dbgsym: 4.0.3-1 → 4.0.4-1
- ros-jazzy-point-cloud-transport-py: 4.0.3-1 → 4.0.4-1
- ros-jazzy-pose-broadcaster: 4.21.0-1 → 4.22.0-1
- ros-jazzy-pose-broadcaster-dbgsym: 4.21.0-1 → 4.22.0-1
- ros-jazzy-position-controllers: 4.21.0-1 → 4.22.0-1
- ros-jazzy-position-controllers-dbgsym: 4.21.0-1 → 4.22.0-1
- ros-jazzy-pybind11-vendor: 3.1.2-2 → 3.1.3-1
- ros-jazzy-range-sensor-broadcaster: 4.21.0-1 → 4.22.0-1
- ros-jazzy-range-sensor-broadcaster-dbgsym: 4.21.0-1 → 4.22.0-1
- ros-jazzy-rcl: 9.2.4-1 → 9.2.5-1
- ros-jazzy-rcl-action: 9.2.4-1 → 9.2.5-1
- ros-jazzy-rcl-action-dbgsym: 9.2.4-1 → 9.2.5-1
- ros-jazzy-rcl-dbgsym: 9.2.4-1 → 9.2.5-1
- ros-jazzy-rcl-lifecycle: 9.2.4-1 → 9.2.5-1
- ros-jazzy-rcl-lifecycle-dbgsym: 9.2.4-1 → 9.2.5-1
- ros-jazzy-rcl-yaml-param-parser: 9.2.4-1 → 9.2.5-1
- ros-jazzy-rcl-yaml-param-parser-dbgsym: 9.2.4-1 → 9.2.5-1
- ros-jazzy-rclcpp: 28.1.6-1 → 28.1.8-1
- ros-jazzy-rclcpp-action: 28.1.6-1 → 28.1.8-1
- ros-jazzy-rclcpp-action-dbgsym: 28.1.6-1 → 28.1.8-1
- ros-jazzy-rclcpp-components: 28.1.6-1 → 28.1.8-1
- ros-jazzy-rclcpp-components-dbgsym: 28.1.6-1 → 28.1.8-1
- ros-jazzy-rclcpp-dbgsym: 28.1.6-1 → 28.1.8-1
- ros-jazzy-rclcpp-lifecycle: 28.1.6-1 → 28.1.8-1
- ros-jazzy-rclcpp-lifecycle-dbgsym: 28.1.6-1 → 28.1.8-1
- ros-jazzy-rclpy: 7.1.3-1 → 7.1.4-1
- ros-jazzy-rcpputils: 2.11.1-1 → 2.11.2-1
- ros-jazzy-rcpputils-dbgsym: 2.11.1-1 → 2.11.2-1
- ros-jazzy-resource-retriever: 3.4.3-1 → 3.4.4-1
- ros-jazzy-resource-retriever-dbgsym: 3.4.3-1 → 3.4.4-1
- ros-jazzy-rmw: 7.3.1-1 → 7.3.2-1
- ros-jazzy-rmw-connextdds: 0.22.0-2 → 0.22.1-1
- ros-jazzy-rmw-connextdds-common: 0.22.0-2 → 0.22.1-1
- ros-jazzy-rmw-connextdds-common-dbgsym: 0.22.0-2 → 0.22.1-1
- ros-jazzy-rmw-connextdds-dbgsym: 0.22.0-2 → 0.22.1-1
- ros-jazzy-rmw-cyclonedds-cpp: 2.2.2-1 → 2.2.3-1
- ros-jazzy-rmw-cyclonedds-cpp-dbgsym: 2.2.2-1 → 2.2.3-1
- ros-jazzy-rmw-dbgsym: 7.3.1-1 → 7.3.2-1
- ros-jazzy-rmw-desert: 1.0.3-1 → 2.0.2-1
- ros-jazzy-rmw-desert-dbgsym: 1.0.3-1 → 2.0.2-1
- ros-jazzy-rmw-fastrtps-cpp: 8.4.1-1 → 8.4.2-1
- ros-jazzy-rmw-fastrtps-cpp-dbgsym: 8.4.1-1 → 8.4.2-1
- ros-jazzy-rmw-fastrtps-dynamic-cpp: 8.4.1-1 → 8.4.2-1
- ros-jazzy-rmw-fastrtps-dynamic-cpp-dbgsym: 8.4.1-1 → 8.4.2-1
- ros-jazzy-rmw-fastrtps-shared-cpp: 8.4.1-1 → 8.4.2-1
- ros-jazzy-rmw-fastrtps-shared-cpp-dbgsym: 8.4.1-1 → 8.4.2-1
- ros-jazzy-rmw-implementation: 2.15.4-1 → 2.15.5-1
- ros-jazzy-rmw-implementation-cmake: 7.3.1-1 → 7.3.2-1
- ros-jazzy-rmw-implementation-dbgsym: 2.15.4-1 → 2.15.5-1
- ros-jazzy-rmw-zenoh-cpp: 0.2.2-1 → 0.2.3-1
- ros-jazzy-rmw-zenoh-cpp-dbgsym: 0.2.2-1 → 0.2.3-1
- ros-jazzy-robot-localization: 3.8.1-1 → 3.8.2-1
- ros-jazzy-robot-localization-dbgsym: 3.8.1-1 → 3.8.2-1
- ros-jazzy-ros-gz: 1.0.9-1 → 1.0.11-1
- ros-jazzy-ros-gz-bridge: 1.0.9-1 → 1.0.11-1
- ros-jazzy-ros-gz-bridge-dbgsym: 1.0.9-1 → 1.0.11-1
- ros-jazzy-ros-gz-image: 1.0.9-1 → 1.0.11-1
- ros-jazzy-ros-gz-image-dbgsym: 1.0.9-1 → 1.0.11-1
- ros-jazzy-ros-gz-interfaces: 1.0.9-1 → 1.0.11-1
- ros-jazzy-ros-gz-interfaces-dbgsym: 1.0.9-1 → 1.0.11-1
- ros-jazzy-ros-gz-sim: 1.0.9-1 → 1.0.11-1
- ros-jazzy-ros-gz-sim-dbgsym: 1.0.9-1 → 1.0.11-1
- ros-jazzy-ros-gz-sim-demos: 1.0.9-1 → 1.0.11-1
- ros-jazzy-ros2-controllers: 4.21.0-1 → 4.22.0-1
- ros-jazzy-ros2-controllers-test-nodes: 4.21.0-1 → 4.22.0-1
- ros-jazzy-ros2action: 0.32.2-1 → 0.32.3-1
- ros-jazzy-ros2cli: 0.32.2-1 → 0.32.3-1
- ros-jazzy-ros2cli-test-interfaces: 0.32.2-1 → 0.32.3-1
- ros-jazzy-ros2cli-test-interfaces-dbgsym: 0.32.2-1 → 0.32.3-1
- ros-jazzy-ros2component: 0.32.2-1 → 0.32.3-1
- ros-jazzy-ros2doctor: 0.32.2-1 → 0.32.3-1
- ros-jazzy-ros2interface: 0.32.2-1 → 0.32.3-1
- ros-jazzy-ros2launch: 0.26.6-1 → 0.26.7-1
- ros-jazzy-ros2lifecycle: 0.32.2-1 → 0.32.3-1
- ros-jazzy-ros2lifecycle-test-fixtures: 0.32.2-1 → 0.32.3-1
- ros-jazzy-ros2lifecycle-test-fixtures-dbgsym: 0.32.2-1 → 0.32.3-1
- ros-jazzy-ros2multicast: 0.32.2-1 → 0.32.3-1
- ros-jazzy-ros2node: 0.32.2-1 → 0.32.3-1
- ros-jazzy-ros2param: 0.32.2-1 → 0.32.3-1
- ros-jazzy-ros2pkg: 0.32.2-1 → 0.32.3-1
- ros-jazzy-ros2run: 0.32.2-1 → 0.32.3-1
- ros-jazzy-ros2service: 0.32.2-1 → 0.32.3-1
- ros-jazzy-ros2topic: 0.32.2-1 → 0.32.3-1
- ros-jazzy-rqt-joint-trajectory-controller: 4.21.0-1 → 4.22.0-1
- ros-jazzy-rqt-robot-steering: 1.0.0-6 → 1.0.1-2
- ros-jazzy-rti-connext-dds-cmake-module: 0.22.0-2 → 0.22.1-1
- ros-jazzy-rttest: 0.17.0-3 → 0.17.1-3
- ros-jazzy-rttest-dbgsym: 0.17.0-3 → 0.17.1-3
- ros-jazzy-rviz-assimp-vendor: 14.1.7-1 → 14.1.8-1
- ros-jazzy-rviz-common: 14.1.7-1 → 14.1.8-1
- ros-jazzy-rviz-common-dbgsym: 14.1.7-1 → 14.1.8-1
- ros-jazzy-rviz-default-plugins: 14.1.7-1 → 14.1.8-1
- ros-jazzy-rviz-default-plugins-dbgsym: 14.1.7-1 → 14.1.8-1
- ros-jazzy-rviz-ogre-vendor: 14.1.7-1 → 14.1.8-1
- ros-jazzy-rviz-ogre-vendor-dbgsym: 14.1.7-1 → 14.1.8-1
- ros-jazzy-rviz-rendering: 14.1.7-1 → 14.1.8-1
- ros-jazzy-rviz-rendering-dbgsym: 14.1.7-1 → 14.1.8-1
- ros-jazzy-rviz-rendering-tests: 14.1.7-1 → 14.1.8-1
- ros-jazzy-rviz-visual-testing-framework: 14.1.7-1 → 14.1.8-1
- ros-jazzy-rviz2: 14.1.7-1 → 14.1.8-1
- ros-jazzy-rviz2-dbgsym: 14.1.7-1 → 14.1.8-1
- ros-jazzy-sensor-msgs: 5.3.5-1 → 5.3.6-1
- ros-jazzy-sensor-msgs-dbgsym: 5.3.5-1 → 5.3.6-1
- ros-jazzy-sensor-msgs-py: 5.3.5-1 → 5.3.6-1
- ros-jazzy-shape-msgs: 5.3.5-1 → 5.3.6-1
- ros-jazzy-shape-msgs-dbgsym: 5.3.5-1 → 5.3.6-1
- ros-jazzy-spinnaker-camera-driver: 3.0.0-1 → 3.0.1-1
- ros-jazzy-spinnaker-camera-driver-dbgsym: 3.0.0-1 → 3.0.1-1
- ros-jazzy-spinnaker-synchronized-camera-driver: 3.0.0-1 → 3.0.1-1
- ros-jazzy-spinnaker-synchronized-camera-driver-dbgsym: 3.0.0-1 → 3.0.1-1
- ros-jazzy-sros2: 0.13.2-1 → 0.13.3-1
- ros-jazzy-sros2-cmake: 0.13.2-1 → 0.13.3-1
- ros-jazzy-std-msgs: 5.3.5-1 → 5.3.6-1
- ros-jazzy-std-msgs-dbgsym: 5.3.5-1 → 5.3.6-1
- ros-jazzy-std-srvs: 5.3.5-1 → 5.3.6-1
- ros-jazzy-std-srvs-dbgsym: 5.3.5-1 → 5.3.6-1
- ros-jazzy-steering-controllers-library: 4.21.0-1 → 4.22.0-1
- ros-jazzy-steering-controllers-library-dbgsym: 4.21.0-1 → 4.22.0-1
- ros-jazzy-stereo-msgs: 5.3.5-1 → 5.3.6-1
- ros-jazzy-stereo-msgs-dbgsym: 5.3.5-1 → 5.3.6-1
- ros-jazzy-teleop-twist-joy: 2.6.2-1 → 2.6.3-1
- ros-jazzy-teleop-twist-joy-dbgsym: 2.6.2-1 → 2.6.3-1
- ros-jazzy-test-ros-gz-bridge: 1.0.9-1 → 1.0.11-1
- ros-jazzy-tf2: 0.36.8-1 → 0.36.9-1
- ros-jazzy-tf2-bullet: 0.36.8-1 → 0.36.9-1
- ros-jazzy-tf2-dbgsym: 0.36.8-1 → 0.36.9-1
- ros-jazzy-tf2-eigen: 0.36.8-1 → 0.36.9-1
- ros-jazzy-tf2-eigen-kdl: 0.36.8-1 → 0.36.9-1
- ros-jazzy-tf2-eigen-kdl-dbgsym: 0.36.8-1 → 0.36.9-1
- ros-jazzy-tf2-geometry-msgs: 0.36.8-1 → 0.36.9-1
- ros-jazzy-tf2-kdl: 0.36.8-1 → 0.36.9-1
- ros-jazzy-tf2-msgs: 0.36.8-1 → 0.36.9-1
- ros-jazzy-tf2-msgs-dbgsym: 0.36.8-1 → 0.36.9-1
- ros-jazzy-tf2-py: 0.36.8-1 → 0.36.9-1
- ros-jazzy-tf2-py-dbgsym: 0.36.8-1 → 0.36.9-1
- ros-jazzy-tf2-ros: 0.36.8-1 → 0.36.9-1
- ros-jazzy-tf2-ros-dbgsym: 0.36.8-1 → 0.36.9-1
- ros-jazzy-tf2-ros-py: 0.36.8-1 → 0.36.9-1
- ros-jazzy-tf2-sensor-msgs: 0.36.8-1 → 0.36.9-1
- ros-jazzy-tf2-tools: 0.36.8-1 → 0.36.9-1
- ros-jazzy-tile-map: 2.4.5-1 → 2.4.6-1
- ros-jazzy-tile-map-dbgsym: 2.4.5-1 → 2.4.6-1
- ros-jazzy-tlsf-cpp: 0.17.0-3 → 0.17.1-3
- ros-jazzy-tlsf-cpp-dbgsym: 0.17.0-3 → 0.17.1-3
- ros-jazzy-trajectory-msgs: 5.3.5-1 → 5.3.6-1
- ros-jazzy-trajectory-msgs-dbgsym: 5.3.5-1 → 5.3.6-1
- ros-jazzy-tricycle-controller: 4.21.0-1 → 4.22.0-1
- ros-jazzy-tricycle-controller-dbgsym: 4.21.0-1 → 4.22.0-1
- ros-jazzy-tricycle-steering-controller: 4.21.0-1 → 4.22.0-1
- ros-jazzy-tricycle-steering-controller-dbgsym: 4.21.0-1 → 4.22.0-1
- ros-jazzy-turtlebot3-fake-node: 2.2.5-5 → 2.3.2-1
- ros-jazzy-turtlebot3-fake-node-dbgsym: 2.2.5-5 → 2.3.2-1
- ros-jazzy-uncrustify-vendor: 3.0.0-2 → 3.0.1-1
- ros-jazzy-ur: 3.1.0-1 → 3.1.1-1
- ros-jazzy-ur-calibration: 3.1.0-1 → 3.1.1-1
- ros-jazzy-ur-calibration-dbgsym: 3.1.0-1 → 3.1.1-1
- ros-jazzy-ur-client-library: 1.7.1-1 → 1.9.0-1
- ros-jazzy-ur-client-library-dbgsym: 1.7.1-1 → 1.9.0-1
- ros-jazzy-ur-controllers: 3.1.0-1 → 3.1.1-1
- ros-jazzy-ur-controllers-dbgsym: 3.1.0-1 → 3.1.1-1
- ros-jazzy-ur-dashboard-msgs: 3.1.0-1 → 3.1.1-1
- ros-jazzy-ur-dashboard-msgs-dbgsym: 3.1.0-1 → 3.1.1-1
- ros-jazzy-ur-description: 3.0.1-1 → 3.1.0-1
- ros-jazzy-ur-moveit-config: 3.1.0-1 → 3.1.1-1
- ros-jazzy-ur-msgs: 2.1.0-1 → 2.2.0-1
- ros-jazzy-ur-msgs-dbgsym: 2.1.0-1 → 2.2.0-1
- ros-jazzy-ur-robot-driver: 3.1.0-1 → 3.1.1-1
- ros-jazzy-ur-robot-driver-dbgsym: 3.1.0-1 → 3.1.1-1
- ros-jazzy-velocity-controllers: 4.21.0-1 → 4.22.0-1
- ros-jazzy-velocity-controllers-dbgsym: 4.21.0-1 → 4.22.0-1
- ros-jazzy-visualization-msgs: 5.3.5-1 → 5.3.6-1
- ros-jazzy-visualization-msgs-dbgsym: 5.3.5-1 → 5.3.6-1
- ros-jazzy-xacro: 2.0.11-2 → 2.0.13-1
- ros-jazzy-zenoh-cpp-vendor: 0.2.2-1 → 0.2.3-1
- ros-jazzy-zenoh-cpp-vendor-dbgsym: 0.2.2-1 → 0.2.3-1
Removed Packages [4]:
- ros-jazzy-autoware-utils
- ros-jazzy-autoware-utils-dbgsym
- ros-jazzy-kinematics-interface-pinocchio
- ros-jazzy-kinematics-interface-pinocchio-dbgsym
Thanks to all ROS maintainers who make packages available to the ROS community. The above list of packages was made possible by the work of the following maintainers:
- Adam Serafin
- Aditya Pande
- Alberto Tudela
- Alejandro Hernandez
- Alejandro Hernandez Cordero
- Alejandro Hernández
- Alex Moriarty
- Andrea Sorbini
- Apex.AI, Inc.
- Audrow Nash
- Bence Magyar
- Bernd Pfrommer
- Brandon Ong
- Chris Iverach-Brereton
- Chris Lalancette
- Davide Costa
- Denis Štogl
- Dharini Dutia
- Dirk Thomas
- Erik Boasson
- Felix Exner
- G.A. vd. Hoorn
- Geoffrey Biggs
- Ivan Paunovic
- Jose Luis Blanco-Claraco
- Jose Mastrangelo
- Jose-Luis Blanco-Claraco
- Justin Carpentier
- Kevin Hallenbeck
- Luis Camero
- M. Fatih Cırıt
- Mamoru Sobue
- Micho Radovnikovich
- Miguel Granero
- NovAtel Support
- Pyo
- ROS Security Working Group
- Ramon Wijnands
- Robert Haschke
- Roni Kreinin
- Ryohsuke Mitsudome
- STEREOLABS
- Scott K Logan
- Shane Loretz
- Southwest Research Institute
- Takagi, Isamu
- Tom Moore
- Tony Baltovski
- Tully Foote
- William Woodall
- Yadunund
- Yutaka Kondo
- kminoda
- lovro
- miguel
- mitsudome-r
Enjoy!
4 posts - 4 participants
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: Upcoming ROS 2 Feature Freeze for Kilted Kaiju on April 14th
We’ve just entered the RMW Feature Freeze period for ROS 2 Kilted Kaiju, and this means that we’re only one week away from the same milestone for all ROS 2 core package in Rolling (soon to be Kilted). At that time, all ros_core packages will be feature and API frozen in Rolling Ridley until we branch Kilted from Rolling on 2025-04-21T00:00:00Z UTC. Feature and API changes can be merged into the Rolling branches once again after the branching is complete.
As always, refer to the Kilted Kaiju Release Timeline for all of the important dates and milestones as we approach World Turtle Day and the release of Kilted Kaiju!
Thanks!
– ROS 2 Team
2 posts - 1 participant
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: BeetleBot Differential Drive Robot Template for GZ sim ROS2
Beetlebot Repo.This repository contains different configurations for the BeetleBot differential drive robot with Gazebo sim to make it easier for beginners to create thier own robot for gazebo sim in sdf or URDF format also make it easier to understand the diffrences between SDF and URDF .
Each branch in this repository represents a unique configuration of the same beetlebot robot in the world it operates in.
In this branch beetlebot robot is writen in SDF format and spawnd inside the main world using spawner cmd
in the launch file.
In this branch beetlebot robot is written as URDF and spawned inside the main world using spawner cmd
in the launch file.
2 posts - 2 participants
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: ROS Deliberation Community Group Survey
Following our latest meeting today, I would like to learn a bit more on what you guys expect from the Deliberation Community group.
Please answer this quick (<5 mins) survey:
ROS Deliberation Community Group Survey
Thanks
Christian
1 post - 1 participant
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: Location for ROSCon 2026?
Hi,
given that traditionally the rotation for locations for ROSCon has been Europe → Asia → North America, and after this year it’ll be the turn of North America for 2026, I’d like to ask if the location been decided yet. I imagine so, given that the effort for organizing ROSCon is not to be dismissed (thanks MeetGreen, Vanessa, Geoff, Kat and everyone else involved!)
I’m asking because of recent travel warnings that several countries have issued (European countries, Canada issue advisories for travelers to U.S. : NPR) and cases like the one of a French researcher who was on his way to attend a conference in Houston, but was denied entry to the US because immigration officers had found messages on his phone where he criticized the current US administration (French scientist denied US entry after phone messages critical of Trump found | US news | The Guardian). Or now that the US government only recognizes two genders, possibly denying entry to trans people who have an X on their passport or the gender on their passport does not match the gender assigned at birth (https://edition.cnn.com/2025/04/03/travel/trans-people-travel-advisories-united-states/index.html)
I’m not trying to start a political thread here. As a very wise man once said when he arrived on Coruscant, “I’m not brave enough for politics”, but I’m only asking if these concerns could be taken into account for ROSCon 2026 before a final decision is made and if possible, other locations in North America like Canada or Mexico could be considered.
Or maybe even somewhere in a new region, like Oceania, South America or Africa, that would be really cool.
Looking forward to seeing you all in Singapore!
5 posts - 4 participants
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: New to ROS – Learning ROS2 as a Student, Open to Suggestions
Hi everyone!
My name is Jorge Andrés Duque, a Mechatronics Engineering student from Colombia currently diving into ROS2 as part of my university and personal projects. I’ve worked with embedded systems, AI, and VEX Robotics, but ROS is something I’m now truly focused on learning more deeply.
I’m especially interested in applying ROS2 for autonomous robots, and I’ve started experimenting with PID control and basic perception using sensors.
If anyone has suggestions for beginner-friendly ROS2 packages, tutorials, or simulation environments you’ve found useful, I’d love to hear from you!
Thanks and I look forward to learning and contributing in the future!
5 posts - 4 participants
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: Gatorcat: EtherCAT on Zenoh / ROS
I have been developing an open-source EtherCAT maindevice and it might be interesting to ROS folks.
Here is a summary of its capabilities:
- Available as a single statically linked binary or docker image for linux and windows.
- Automatically scan and operate an ethercat network with zero configuration required.
- Optionally provide a config file that describes the contents of the ethercat network to validate against.
- CoE startup parameters via the config file.
- Publishes ethercat inputs on zenoh. (CBOR encoded)
- Subscribes on zenoh (CBOR encoded) for controlling ethercat outputs.
- Written in zig (also available as a zig module).
- Optionally specify a real-time priority (PREEMPT_RT)
- CLI utility for scanning, running, and debugging ethercat networks.
Notably missing features (coming soon!):
- distributed clocks.
- enhanced NIC performance using linux XDP (currently uses raw sockets).
ROS folks may be using a lot of distributed clocks for motor drives, I have not tested it extensively with motor drives. It is well suited for digital / analog output/input modules right now.
1 post - 1 participant
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: Upcoming RMW Feature Freeze for ROS 2 Kilted Kaiju on April 7 2025
Hi all,
On 2025-04-08T06:59:00Z UTC we will freeze all RMW related packages in preparation for the upcoming Kilted Kaiju
release on May 23, 2025.
Once this freeze goes into effect, we will no longer accept additional features to RMW packages, which includes rmw_fastrtps, rmw_cyclonedds, rmw_connextdds, rmw_zenoh; as well as their vendor packages, Fast-DDS, Fast-CDR , cyclonedds, iceoryx and zenoh_cpp.
Bug fixes will still be accepted after the freeze date.
You may find more information on the Kilted Kaiju release timeline here: ROS 2 Kilted Kaiju (codename ‘kilted’; May, 2025).
2 posts - 2 participants
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: ROS News for the Week March 31st, 2025
ROS News for the Week March 31st, 2025
Applications for GSoC 2025, the OSRF’s only paid internship program, are due on 2025-04-08T18:00:00Z UTC. I checked this morning and there are only ~30 legitimate applications. A few of the “less sexy” projects don’t have any applications. All of this is to say, if you take the time to apply you have a really good shot at getting accepted!
ROSCon 2025 Diversity Scholarship applications are due in two weeks, on 2025-04-18T07:00:00Z UTC.
Join us for on 2025-04-30T07:00:00Z UTC for our next Gazebo Community meeting on RoSE Terrain Generator (RTG): Monocular Depth-Based Synthetic DEM Generation
The Robot Report’s 50 most innovative robotics companies were released this week. More than half of them are ROS users, including OSRA members NVIDIA, Clearpath, Roboto, Asensus, and Locus.

Check out this super cool open hardware / open software dexterous hand that runs ROS!. Source code and CAD available here.
Our colleagues over at University of Michigan have released OceanSim: A GPU-Accelerated Underwater Robot Perception Simulation Framework. Even better, it has ROS baked right in. Source code available here.
Check out FACTR an open hardware / open software teleop and RL training framework based on ROS. FACTR Hardware - FACTR Teleop - FACTR Training
There’s finally a low-cost micro-ROS/LiDAR/Motor drivers board thats available commercially?. THIS IS HUGE!

Events
- 2025-04-07 ROS Deliberation Community Group Meeting
- 2025-04-11 Mistral AI Robotics Hackathon Paris
- 2025-04-28 International Workshop on Robotics Software Engineering
- 2025-04-30 Robotics Summit & Expo wsg @gbiggs.
- 2025-04-30 Gazebo Community meeting: RoSE Terrain Generator (RTG): Monocular Depth-Based Synthetic DEM Generation
- 2025-04-30 Application Deadline 2nd ACM SIGSOFT Summer School on Software Engineering in Robotics in Delft
- 2025-05-02 CFP Deadline IEEE SMC-IT/SCC Space Robotics Workshop CFP
- 2025-05-15 ROS-Industrial Consortium Americas 2025 Annual Meeting Detroit
- 2025-05-23 ICRA 2025 Advancing Quantitative and QUAlitative SIMulators for marine applications
- 2025-05-24 ROS MeetUp in Cali, Colombia!
- 2025-05-30 => 2025-05-31 2025 Open Hardware Summit in Edinburgh
- 2025-09-09 ROSCon JP in Nagoya
- 2025-10-27 =>2025-10-30 ROSCon Singapore
- 2025-11-17 => 2025-11-20 Joint ROSCon Germany and France
- 2025-05-11 CFP Deadline for Robotics & AI Track @ CppCon
News
- OSRF Google Summer of Code 2025
– Paid Internship – APPLICATIONS DUE 2025-04-08T07:00:00Z UTC
- We’re Creating a Willow Garage Oral History – tell us what you want to hear about
- Robot Report’s 50 most innovative robotics companies - Half are ROS users, including OSRA members NVIDIA, Clearpath, Roboto, Asensus, and Locus.
- New Canadian / Danish Robotics Cluster Alliance
- Introducing Autoware Foundation 2.0!
- Video: SwRI Develops COMOT Mobile Manipulator Robot
- OSRA TGC meeting minutes for February, 2025
- ROS 2 tutorials upgrade & entrance level complexity
- Autonomous forest exploration and wildlife monitoring robot.
- Invitation to Collaborate on AsyncAPI Specification for ROS 2
- U of Alberta research focuses on robotics in medical applications
- A Roboticist’s First Time at the European Robotics Forum
- Haply Robotics to offer its haptic controller with PickNik’s MoveItPro
- Hyundai to buy ‘tens of thousands’ of Boston Dynamics robots
- Chef Robotics raises $20.6 million to continue building AI robot arms- Pitch Deck
- Agility Robotics reportedly raising $400M for humanoid warehouse robots
- What is a Servo Motor and How it Works
- More ROS Train Robots!!!
- Video Friday
- Nurturing New Contributors: The Art of Crafting Good First Issues on GitHub
- Weekly Robotics #306
ROS & Robotics
- Robotec’s new standard interfaces for interacting with simulators from ROS 2
New ROS Dexterous Hand - source code
OceanSim: A GPU-Accelerated Underwater Robot Perception Simulation Framework - source code
FACTR open hardware / software teleop and training – FACTR Hardware - FACTR Teleop - Training
Vision Model for Drones
- Low-cost micro-ROS/LiDAR/Motor drivers board available commercially
- New ROS 2 package for multi-sensor calibration
- Input for Aerial Vehicles ROS Support Guide
- Preparing for Noetic Sync 2025-04-08
- New packages and patch release for Humble Hawksbill 2025-03-31
- New packages for ROS 2 Rolling Ridley 2025-03-28
- Odometry for a Simulated Mobile Robot in a cool world with ROS & Gazebo
- Community interest in a Vector Field Histogram global path planning algorithm
- New Online Course: Building Gazebo Simulations with Blender
- New LineTurtle mini Robot
- ROS 2 / Gazebo OmniDirectional Robot Simulator
- New YOLO annotator with some nice automation
- Openwalker ROS Robot
- On Learning Robot Racing Policies
- A ROS 1 and ROS 2 node that converts PointCloud2 LIDAR data to OccupancyGrid 2D map data based on intensity and / or height
- Building Autonomous Vehicle in Carla- PID Controller & ROS 2
- Source code for an end-to-end autonomous vehicle stack
- A precise and methodical process designed to assess the mechanical and sensory capabilities of the UR robot in real-world applications.
Workshop on developing ROS 2 applications using the Rust language
- ROS 2 Laser Segmentation Tools
- ros2-pkg-create: Powerful ROS 2 Package Generator
- Autoware Core 1.0!
- Towards a robotic intrusion prevention system: Combining security and safety in cognitive social robots
- ROS 2 platform based program designed to control and Monitor ATVs.
- MIT Course: Visual Navigation for Autonomous Vehicles
- MIT-SPARK/spark-fast-lio: FAST-LIO2 on ROS 2 with various functionalities for LIO mapping
- Video: How to Utilize LeRobot, Isaac Sim and ROS 2
- New SLAM-Handbook
- Int-Ball2 Technology Demonstration Platform ROS/Gazebo Simulator
- ROS# for .Net Applications
- OpenArm
- MegaRover ROS / Gazebo Simulation
- New Open Hardware Arm
Got a Minute? 
- We could really use someone’s help backporting this point cloud transformation to Humble.
- There’s still time to get this update to launch for custom log file names into Kilted.
1 post - 1 participant
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: New ROS 2 package for multi-sensor calibration
Hello there!
We are excited to announce the release of a new package for ROS 2 Jazzy (we also have a ROS 1 branch, but please note that it will not be maintained). This package enables much faster and easier extrinsic calibration of camera and LiDAR sensors through a user-friendly GUI application—no coding required!
Currently, the calibration process utilizes a physical target, but the package is designed to be extensible, allowing for other target geometries or even targetless calibration.
We are actively working on adding new calibration modalities (e.g. intrinsic calibration of cameras) and would greatly appreciate your input, ideas, and contributions in the form of pull requests!
For more information, please visit our GitHub repository:
Thank you for your interest, and we look forward to your feedback!
Best regards,
Miguel
1 post - 1 participant
![[WWW] [WWW]](./rostheme/img/moin-www.png)
ROS Discourse General: Low-cost micro-ROS/LiDAR/Motor drivers board available commercially
Hello,
I have designed, manufactured and made available commercially a low-cost all-in-one board for beginners building DIY robots capable of ROS2/Nav2 mapping, navigation, SLAM and frontier exploration. Everything is open source.
This board has a 2D LiDAR port, 2 channel DC 12/24V motor drivers. Think of this PCB as a miniature robot “motherboard” for building small differential two-wheel educational LiDAR robots. Out-of-the-box firmware, ROS2 packages and starter robot body for easy robot building are provided as well.
The board accepts an ESP32 development board and runs micro-ROS for Arduino connected over WiFi to a local PC running ROS2 Iron. Here is an example interfacing this board to a LiDAR and two N20 encoder motors.
Here is a video example of what you can build in action, running glorious Nav2 and frontier exploration.
The board comes with the following:
- off-the-shelf firmware
- firmware supports ~15 2D LiDAR models
- firmware supports both brushed and brushless motors
- a starter 120mm 3D printed robot body design that you can 3D print yourself
- ROS2 Iron PC software (Ubuntu and Windows) using Docker and direct install
- with all necessary additional packages
- including a pre-configured starter robot package
- step-by-step video instruction series for beginners
- covering assembly, software/firmware setup, bring-up and operation including mapping, SLAM, autonomous navigation and autonomous frontier exploration
- the board features include
- an integrated motor power supply (12V default, configurable to 24V) for stable motor power across a wide range of battery discharge voltage
- an integrated 5V regulated power supply for the 2D LiDAR and ESP32
- a battery voltage monitoring circuit (using ESP32 built-in ADC)
- board power specs
- motor voltage Vmot options 12V default, 24V selectable
- alkaline batteries power
- protected rechargeable batteries can be used with additional precautions
- board input voltage range Vbatt 6V to 21V
- Vbatt 6V to 10V for Vmot=12V motor voltage
- Vbatt 6V to 21V for Vmot=24V motor voltage
- Max total motors current 3A
- Max total motors battery draw 2A
- Individual motor current limit 2.2A (driver IC built-in protection)
- 5V supply max output current 3.5A
- Max total battery draw 3A
- two board version are available
- BDC-30P compatible with 30-pin ESP32 development kit modules
- BDC-38C4 compatible with 38-pin ESP32 DevKitC V4
Extensive troubleshooting instructions and a technical support forum are available as help resources.
I hope this robot board can be useful for the ROS community.
3 posts - 2 participants
![[WWW] [WWW]](./rostheme/img/moin-www.png)