July 19, 2024
ROS News for the Week of July 15th, 2024

ROS News for the Week of July 15th, 2024



The next ROS By-The-Bay is scheduled for 2024-08-02T01:00:00Z UTC. I’ve lined up a fantastic visiting speaker, Prof. Florian Pokorny from KTH Royal Institute of Technology, for this month’s event. Prof. Pokorny’s and his team are behind the fantastic work at cloudgripper.org.

We also have two other ROS events happening this week:



My colleague @quarkytale has organized a Women in Robotics event featuring female open source robotics developer for July 30th at the Intrinsic offices. We would love to see you there!


32a59074a4ccb5c4d8bf7d86f4cabdc05f437476_2_690x482
MoveIt for ROS 2 Jazzy is out now and available on an apt server near you!



ROSDoc2 Now Available Now in Apt and PyPI! If you are a package maintainer please, please, please regularly set aside some time to update your documentation. The post above includes documentation on how to write good ROS documentation.


image
Our friends at Autoware have announced their 2024 challenge. There is over US$25K in prize money for contributions to the project!

Events

News

ROS


Got a minute? :timer_clock:

We just added ROSDoc 2 to the ROS apt packages.. If you are a package maintainer please make sure your package renders on docs.ros.org using this documentation. If your package isn’t on ROS Index consider taking the time to add it.

1 post - 1 participant

Read full topic

by Katherine_Scott on July 19, 2024 05:32 PM

MoveIt released for ROS 2 Jazzy!

We are very excited to announce that MoveIt 2 Jazzy is finally here. The newest LTS release Jazzy 2.10 will take Humble’s place as the recommended MoveIt version. It can be installed using the ROS Debian binaries on Ubuntu Noble 24.04, or through a Linux source build. The same version has also been released for Rolling Ridley.

New features in the Jazzy LTS release compared to Humble include (ordered randomly):

  • A refactored version of MoveIt Servo
  • MoveIt Python bindings
  • Multi-dof trajectory execution support
  • Refactored planning pipeline
  • Improved logging (rosout, namespaces) and ROS parameter API
  • Improved Cartesian Interpolator
  • A new implementation of the STOMP motion planner
  • Support for parallel planning pipelines
  • Several improvements to trajectory processing (TOTG, Ruckig, butterworth filtering)
  • Refactored planning pipeline API to better represent request and response adapters

The full changelogs are provided in the changelogs files in the MoveIt 2 repository, breaking changes are documented in the migration guide. We are still working on fixing and updating the tutorials to reflect the latest changes.

Jazzy development continues on the MoveIt main branch for the upcoming weeks. Once we are sure the MoveIt API can remain stable, we will branch off Jazzy to a stable branch for future releases, just like we did for past distributions. In the meantime, we will maintain source build support for Jazzy on the MoveIt main branch while Humble and Iron support are being phased out. The corresponding stable branches are not affected by this.

A big Thank You to all the great contributors whose work is featured in this release: Abhijeet Das Gupta, Abishalini Sivaraman, AdamPettinger, Alaa, Alex Moriarty, Alex Navarro, AlexWebb, AM4283, Amal Nanavati, AndyZe, Anthony Baker, Antoine Duplex, Ashton Larkin, azalutsky, Bhargav, Shirin Nalamati, cambel, Captain Yoshi, Carlo Rizzardo, Chance Cardona, Chris Lalancette, Chris Thrasher, Christian Henkel, CihatAltiparmak, Cory Crean, David V. Lu!!, Dongya Jiang, Erik Holum, Ezra Brooks, Filip Sund, Forrest Rogers-Marcovitz, Gaël Écorchard, hacker1024, Henning Kayser, Heramb Modugula, HX2003, Igor Medvedev, Ikko Eltociear Ashimine, Jafar, Jens Vanhooydonck, J. Javan Jochen Sprickerhof, Jonathan Grebe, Jorge Nicho, Jorge Pérez Ramos, Joseph Schornak, light-tech, Lucas Wendland, Marc Bestmann, Marco Magri, Mario Prats, Marq Rasmussen, Matej Vargovcik, Matthijs van der Burgh, methylDragon, Michael Ferguson, Michael Görner, Michael Marron, Michael Wiznitzer, Michael Wrock, Nacho Mellado, Nathan Brooks, Nils-Christian Iseke, Pablo Iñigo Blasco, Paul Gesel, Peter David Fagan, Rayene Messaoud, Robert Haschke, Rufus Wong, Sameer Gupta, Sami Alperen Akgün, Sarah Nix, Sarvajith Adyanthaya, Scott K Logan, Sebastian Castro, Sebastian Jahr, Shane Loretz, Shobuj Paul, Simon Schmeisser, Solomon Wiznitzer, Stephanie Eng, s-trinh, Surav Shrestha, tbastiaens-riwo, Tyler Weaver, Vatan Aksoy Tezer, V Mohammed Ibrahim, werner291, Will Yadu, Yang Lin

Please share your feedback and learnings on using MoveIt Jazzy on GitHub Discussions. Happy testing!

(originally posted on the PickNik Blog)

1 post - 1 participant

Read full topic

by Henning_Kayser on July 19, 2024 02:34 PM

July 18, 2024
New Packages for Noetic 2024-07-18

We’re happy to announce 3 new packages and 16 updates are now available in ROS Noetic. This sync was tagged as noetic/2024-07-18.

Thank you to every maintainer and contributor who made these updates available!

Package Updates for ROS Noetic

Added Packages [3]:

  • ros-noetic-etsi-its-cpm-ts-coding: 2.1.0-3
  • ros-noetic-etsi-its-cpm-ts-conversion: 2.1.0-3
  • ros-noetic-etsi-its-cpm-ts-msgs: 2.1.0-3

Updated Packages [16]:

  • ros-noetic-etsi-its-cam-coding: 2.0.2-2 → 2.1.0-3
  • ros-noetic-etsi-its-cam-conversion: 2.0.2-2 → 2.1.0-3
  • ros-noetic-etsi-its-cam-msgs: 2.0.2-2 → 2.1.0-3
  • ros-noetic-etsi-its-coding: 2.0.2-2 → 2.1.0-3
  • ros-noetic-etsi-its-conversion: 2.0.2-2 → 2.1.0-3
  • ros-noetic-etsi-its-denm-coding: 2.0.2-2 → 2.1.0-3
  • ros-noetic-etsi-its-denm-conversion: 2.0.2-2 → 2.1.0-3
  • ros-noetic-etsi-its-denm-msgs: 2.0.2-2 → 2.1.0-3
  • ros-noetic-etsi-its-messages: 2.0.2-2 → 2.1.0-3
  • ros-noetic-etsi-its-msgs: 2.0.2-2 → 2.1.0-3
  • ros-noetic-etsi-its-msgs-utils: 2.0.2-2 → 2.1.0-3
  • ros-noetic-etsi-its-primitives-conversion: 2.0.2-2 → 2.1.0-3
  • ros-noetic-etsi-its-rviz-plugins: 2.0.2-2 → 2.1.0-3
  • ros-noetic-foxglove-bridge: 0.7.3-1 → 0.7.10-1
  • ros-noetic-mrpt2: 2.13.3-1 → 2.13.3-2
  • ros-noetic-udp-msgs: 0.0.4-1 → 0.0.5-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:

  • Evan Flynn
  • Jean-Pierre Busch
  • John Hurliman
  • Jose-Luis Blanco-Claraco

1 post - 1 participant

Read full topic

by sloretz on July 18, 2024 10:11 PM

July 17, 2024
How to run multiple tests in parallel with colcon test?

I am currently engaged in a ROS2 project aimed at optimizing our testing processes by enabling concurrent execution of tests within a single package using colcon test.

Initially, I attempted to utilize the --parallel-workers flag. However, this approach did not resolve the issue as intended. It facilitates parallel execution across multiple packages, but intra-package test execution remains sequential.

Each test is implemented using the launch_testing framework and integrated into colcon via the add_launch_test macro within the CMakeLists.txt file.

Key specifics include:

  • ROS2 version: Humble
  • Operating System: Ubuntu 22.04
  • Test execution command: colcon test

I am seeking guidance or practical examples that outline best practices for achieving concurrent test execution at the ROS2 package level.

In case what I am asking turned out to be not supported, I suggest to add it to the list of desired features to be implemented. Thank you in advance!

1 post - 1 participant

Read full topic

by LastStarDust on July 17, 2024 10:52 PM

New Packages for Iron Irwini 2024-07-17

Hello everyone!

We’re happy to announce 9 new packages and 92 updates are now available on Ubuntu Jammy on amd64 and more importantly we’ve restored 114 packages on arm64 that disappeared after Iron Irwini sync earlier this week

This sync was tagged as iron/2024-07-17 :iron: :irwini:

Package Updates for iron on amd64

Added Packages [9]:

  • ros-iron-camera-aravis2: 1.0.0-1
  • ros-iron-camera-aravis2-dbgsym: 1.0.0-1
  • ros-iron-camera-aravis2-msgs: 1.0.0-1
  • ros-iron-camera-aravis2-msgs-dbgsym: 1.0.0-1
  • ros-iron-etsi-its-cpm-ts-coding: 2.1.0-1
  • ros-iron-etsi-its-cpm-ts-coding-dbgsym: 2.1.0-1
  • ros-iron-etsi-its-cpm-ts-conversion: 2.1.0-1
  • ros-iron-etsi-its-cpm-ts-msgs: 2.1.0-1
  • ros-iron-etsi-its-cpm-ts-msgs-dbgsym: 2.1.0-1

Updated Packages [92]:

  • ros-iron-classic-bags: 0.1.0-1 → 0.3.0-1
  • ros-iron-etsi-its-cam-coding: 2.0.2-1 → 2.1.0-1
  • ros-iron-etsi-its-cam-coding-dbgsym: 2.0.2-1 → 2.1.0-1
  • ros-iron-etsi-its-cam-conversion: 2.0.2-1 → 2.1.0-1
  • ros-iron-etsi-its-cam-msgs: 2.0.2-1 → 2.1.0-1
  • ros-iron-etsi-its-cam-msgs-dbgsym: 2.0.2-1 → 2.1.0-1
  • ros-iron-etsi-its-coding: 2.0.2-1 → 2.1.0-1
  • ros-iron-etsi-its-conversion: 2.0.2-1 → 2.1.0-1
  • ros-iron-etsi-its-conversion-dbgsym: 2.0.2-1 → 2.1.0-1
  • ros-iron-etsi-its-denm-coding: 2.0.2-1 → 2.1.0-1
  • ros-iron-etsi-its-denm-coding-dbgsym: 2.0.2-1 → 2.1.0-1
  • ros-iron-etsi-its-denm-conversion: 2.0.2-1 → 2.1.0-1
  • ros-iron-etsi-its-denm-msgs: 2.0.2-1 → 2.1.0-1
  • ros-iron-etsi-its-denm-msgs-dbgsym: 2.0.2-1 → 2.1.0-1
  • ros-iron-etsi-its-messages: 2.0.2-1 → 2.1.0-1
  • ros-iron-etsi-its-msgs: 2.0.2-1 → 2.1.0-1
  • ros-iron-etsi-its-msgs-utils: 2.0.2-1 → 2.1.0-1
  • ros-iron-etsi-its-primitives-conversion: 2.0.2-1 → 2.1.0-1
  • ros-iron-etsi-its-rviz-plugins: 2.0.2-1 → 2.1.0-1
  • ros-iron-etsi-its-rviz-plugins-dbgsym: 2.0.2-1 → 2.1.0-1
  • ros-iron-foxglove-bridge: 0.7.7-1 → 0.7.9-1
  • ros-iron-foxglove-bridge-dbgsym: 0.7.7-1 → 0.7.9-1
  • ros-iron-geometry-tutorials: 0.3.6-4 → 0.4.0-1
  • ros-iron-metavision-driver: 1.2.8-1 → 2.0.0-1
  • ros-iron-metavision-driver-dbgsym: 1.2.8-1 → 2.0.0-1
  • ros-iron-ompl: 1.5.2-4 → 1.6.0-1
  • ros-iron-ompl-dbgsym: 1.5.2-4 → 1.6.0-1
  • ros-iron-openeb-vendor: 1.2.2-1 → 2.0.0-1
  • ros-iron-openeb-vendor-dbgsym: 1.2.2-1 → 2.0.0-1
  • ros-iron-rmf-api-msgs: 0.1.1-1 → 0.1.2-1
  • ros-iron-rmf-charger-msgs: 3.1.2-1 → 3.1.3-1
  • ros-iron-rmf-charger-msgs-dbgsym: 3.1.2-1 → 3.1.3-1
  • ros-iron-rmf-charging-schedule: 2.2.5-1 → 2.2.6-1
  • ros-iron-rmf-dispenser-msgs: 3.1.2-1 → 3.1.3-1
  • ros-iron-rmf-dispenser-msgs-dbgsym: 3.1.2-1 → 3.1.3-1
  • ros-iron-rmf-door-msgs: 3.1.2-1 → 3.1.3-1
  • ros-iron-rmf-door-msgs-dbgsym: 3.1.2-1 → 3.1.3-1
  • ros-iron-rmf-fleet-adapter: 2.2.5-1 → 2.2.6-1
  • ros-iron-rmf-fleet-adapter-dbgsym: 2.2.5-1 → 2.2.6-1
  • ros-iron-rmf-fleet-adapter-python: 2.2.5-1 → 2.2.6-1
  • ros-iron-rmf-fleet-msgs: 3.1.2-1 → 3.1.3-1
  • ros-iron-rmf-fleet-msgs-dbgsym: 3.1.2-1 → 3.1.3-1
  • ros-iron-rmf-ingestor-msgs: 3.1.2-1 → 3.1.3-1
  • ros-iron-rmf-ingestor-msgs-dbgsym: 3.1.2-1 → 3.1.3-1
  • ros-iron-rmf-lift-msgs: 3.1.2-1 → 3.1.3-1
  • ros-iron-rmf-lift-msgs-dbgsym: 3.1.2-1 → 3.1.3-1
  • ros-iron-rmf-obstacle-msgs: 3.1.2-1 → 3.1.3-1
  • ros-iron-rmf-obstacle-msgs-dbgsym: 3.1.2-1 → 3.1.3-1
  • ros-iron-rmf-scheduler-msgs: 3.1.2-1 → 3.1.3-1
  • ros-iron-rmf-scheduler-msgs-dbgsym: 3.1.2-1 → 3.1.3-1
  • ros-iron-rmf-site-map-msgs: 3.1.2-1 → 3.1.3-1
  • ros-iron-rmf-site-map-msgs-dbgsym: 3.1.2-1 → 3.1.3-1
  • ros-iron-rmf-task-msgs: 3.1.2-1 → 3.1.3-1
  • ros-iron-rmf-task-msgs-dbgsym: 3.1.2-1 → 3.1.3-1
  • ros-iron-rmf-task-ros2: 2.2.5-1 → 2.2.6-1
  • ros-iron-rmf-task-ros2-dbgsym: 2.2.5-1 → 2.2.6-1
  • ros-iron-rmf-traffic-msgs: 3.1.2-1 → 3.1.3-1
  • ros-iron-rmf-traffic-msgs-dbgsym: 3.1.2-1 → 3.1.3-1
  • ros-iron-rmf-traffic-ros2: 2.2.5-1 → 2.2.6-1
  • ros-iron-rmf-traffic-ros2-dbgsym: 2.2.5-1 → 2.2.6-1
  • ros-iron-rmf-websocket: 2.2.5-1 → 2.2.6-1
  • ros-iron-rmf-websocket-dbgsym: 2.2.5-1 → 2.2.6-1
  • ros-iron-rmf-workcell-msgs: 3.1.2-1 → 3.1.3-1
  • ros-iron-rmf-workcell-msgs-dbgsym: 3.1.2-1 → 3.1.3-1
  • ros-iron-ros-gz: 0.254.1-1 → 0.254.2-1
  • ros-iron-ros-gz-bridge: 0.254.1-1 → 0.254.2-1
  • ros-iron-ros-gz-bridge-dbgsym: 0.254.1-1 → 0.254.2-1
  • ros-iron-ros-gz-image: 0.254.1-1 → 0.254.2-1
  • ros-iron-ros-gz-image-dbgsym: 0.254.1-1 → 0.254.2-1
  • ros-iron-ros-gz-interfaces: 0.254.1-1 → 0.254.2-1
  • ros-iron-ros-gz-interfaces-dbgsym: 0.254.1-1 → 0.254.2-1
  • ros-iron-ros-gz-sim: 0.254.1-1 → 0.254.2-1
  • ros-iron-ros-gz-sim-dbgsym: 0.254.1-1 → 0.254.2-1
  • ros-iron-ros-gz-sim-demos: 0.254.1-1 → 0.254.2-1
  • ros-iron-ros-ign: 0.254.1-1 → 0.254.2-1
  • ros-iron-ros-ign-bridge: 0.254.1-1 → 0.254.2-1
  • ros-iron-ros-ign-bridge-dbgsym: 0.254.1-1 → 0.254.2-1
  • ros-iron-ros-ign-gazebo: 0.254.1-1 → 0.254.2-1
  • ros-iron-ros-ign-gazebo-dbgsym: 0.254.1-1 → 0.254.2-1
  • ros-iron-ros-ign-gazebo-demos: 0.254.1-1 → 0.254.2-1
  • ros-iron-ros-ign-image: 0.254.1-1 → 0.254.2-1
  • ros-iron-ros-ign-image-dbgsym: 0.254.1-1 → 0.254.2-1
  • ros-iron-ros-ign-interfaces: 0.254.1-1 → 0.254.2-1
  • ros-iron-ros-ign-interfaces-dbgsym: 0.254.1-1 → 0.254.2-1
  • ros-iron-ros2-socketcan: 1.2.0-1 → 1.3.0-1
  • ros-iron-ros2-socketcan-dbgsym: 1.2.0-1 → 1.3.0-1
  • ros-iron-ros2-socketcan-msgs: 1.2.0-1 → 1.3.0-1
  • ros-iron-ros2-socketcan-msgs-dbgsym: 1.2.0-1 → 1.3.0-1
  • ros-iron-test-ros-gz-bridge: 0.254.1-1 → 0.254.2-1
  • ros-iron-turtle-tf2-cpp: 0.3.6-4 → 0.4.0-1
  • ros-iron-turtle-tf2-cpp-dbgsym: 0.3.6-4 → 0.4.0-1
  • ros-iron-turtle-tf2-py: 0.3.6-4 → 0.4.0-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:

  • Aaron Chong
  • Aditya Pande
  • Alejandro Hernandez
  • Alejandro Hernández Cordero
  • Arjo Chakravarty
  • Bernd Pfrommer
  • Boitumelo Ruf
  • Brandon Ong
  • David V. Lu!!
  • Grey
  • Jean-Pierre Busch
  • John Hurliman
  • Josh Whitley
  • Louise Poubel
  • Marco A. Gutiérrez
  • Mark Moll
  • Morgan Quigley
  • Rushyendra Maganty
  • Yadunund
  • methylDragon

Package Updates for iron on arm64

Added Packages [114]:

  • ros-iron-ackermann-steering-controller: 3.25.0-1
  • ros-iron-ackermann-steering-controller-dbgsym: 3.25.0-1
  • ros-iron-admittance-controller: 3.25.0-1
  • ros-iron-admittance-controller-dbgsym: 3.25.0-1
  • ros-iron-bicycle-steering-controller: 3.25.0-1
  • ros-iron-bicycle-steering-controller-dbgsym: 3.25.0-1
  • ros-iron-camera-aravis2: 1.0.0-1
  • ros-iron-camera-aravis2-dbgsym: 1.0.0-1
  • ros-iron-camera-aravis2-msgs: 1.0.0-1
  • ros-iron-camera-aravis2-msgs-dbgsym: 1.0.0-1
  • ros-iron-controller-interface: 3.26.0-1
  • ros-iron-controller-interface-dbgsym: 3.26.0-1
  • ros-iron-controller-manager: 3.26.0-1
  • ros-iron-controller-manager-dbgsym: 3.26.0-1
  • ros-iron-diff-drive-controller: 3.25.0-1
  • ros-iron-diff-drive-controller-dbgsym: 3.25.0-1
  • ros-iron-effort-controllers: 3.25.0-1
  • ros-iron-effort-controllers-dbgsym: 3.25.0-1
  • ros-iron-etsi-its-cpm-ts-coding: 2.1.0-1
  • ros-iron-etsi-its-cpm-ts-coding-dbgsym: 2.1.0-1
  • ros-iron-etsi-its-cpm-ts-conversion: 2.1.0-1
  • ros-iron-etsi-its-cpm-ts-msgs: 2.1.0-1
  • ros-iron-etsi-its-cpm-ts-msgs-dbgsym: 2.1.0-1
  • ros-iron-force-torque-sensor-broadcaster: 3.25.0-1
  • ros-iron-force-torque-sensor-broadcaster-dbgsym: 3.25.0-1
  • ros-iron-forward-command-controller: 3.25.0-1
  • ros-iron-forward-command-controller-dbgsym: 3.25.0-1
  • ros-iron-gripper-controllers: 3.25.0-1
  • ros-iron-gripper-controllers-dbgsym: 3.25.0-1
  • ros-iron-gz-ros2-control: 1.1.8-1
  • ros-iron-gz-ros2-control-dbgsym: 1.1.8-1
  • ros-iron-gz-ros2-control-demos: 1.1.8-1
  • ros-iron-gz-ros2-control-demos-dbgsym: 1.1.8-1
  • ros-iron-imu-sensor-broadcaster: 3.25.0-1
  • ros-iron-imu-sensor-broadcaster-dbgsym: 3.25.0-1
  • ros-iron-joint-state-broadcaster: 3.25.0-1
  • ros-iron-joint-state-broadcaster-dbgsym: 3.25.0-1
  • ros-iron-joint-trajectory-controller: 3.25.0-1
  • ros-iron-joint-trajectory-controller-dbgsym: 3.25.0-1
  • ros-iron-kinova-gen3-6dof-robotiq-2f-85-moveit-config: 0.2.2-1
  • ros-iron-kinova-gen3-7dof-robotiq-2f-85-moveit-config: 0.2.2-1
  • ros-iron-kortex-description: 0.2.2-1
  • ros-iron-moveit: 2.8.0-1
  • ros-iron-moveit-hybrid-planning: 2.8.0-1
  • ros-iron-moveit-hybrid-planning-dbgsym: 2.8.0-1
  • ros-iron-moveit-planners: 2.8.0-1
  • ros-iron-moveit-plugins: 2.8.0-1
  • ros-iron-moveit-py: 2.8.0-1
  • ros-iron-moveit-py-dbgsym: 2.8.0-1
  • ros-iron-moveit-ros: 2.8.0-1
  • ros-iron-moveit-ros-control-interface: 2.8.0-1
  • ros-iron-moveit-ros-control-interface-dbgsym: 2.8.0-1
  • ros-iron-moveit-ros-planning-interface: 2.8.0-1
  • ros-iron-moveit-ros-planning-interface-dbgsym: 2.8.0-1
  • ros-iron-moveit-ros-visualization: 2.8.0-1
  • ros-iron-moveit-ros-visualization-dbgsym: 2.8.0-1
  • ros-iron-moveit-runtime: 2.8.0-1
  • ros-iron-moveit-servo: 2.8.0-1
  • ros-iron-moveit-servo-dbgsym: 2.8.0-1
  • ros-iron-moveit-setup-app-plugins: 2.8.0-1
  • ros-iron-moveit-setup-app-plugins-dbgsym: 2.8.0-1
  • ros-iron-moveit-setup-assistant: 2.8.0-1
  • ros-iron-moveit-setup-assistant-dbgsym: 2.8.0-1
  • ros-iron-moveit-setup-controllers: 2.8.0-1
  • ros-iron-moveit-setup-controllers-dbgsym: 2.8.0-1
  • ros-iron-moveit-setup-core-plugins: 2.8.0-1
  • ros-iron-moveit-setup-core-plugins-dbgsym: 2.8.0-1
  • ros-iron-moveit-setup-framework: 2.8.0-1
  • ros-iron-moveit-setup-framework-dbgsym: 2.8.0-1
  • ros-iron-moveit-setup-srdf-plugins: 2.8.0-1
  • ros-iron-moveit-setup-srdf-plugins-dbgsym: 2.8.0-1
  • ros-iron-moveit-simple-controller-manager: 2.8.0-1
  • ros-iron-moveit-simple-controller-manager-dbgsym: 2.8.0-1
  • ros-iron-picknik-reset-fault-controller: 0.0.3-1
  • ros-iron-picknik-reset-fault-controller-dbgsym: 0.0.3-1
  • ros-iron-picknik-twist-controller: 0.0.3-1
  • ros-iron-picknik-twist-controller-dbgsym: 0.0.3-1
  • ros-iron-pid-controller: 3.25.0-1
  • ros-iron-pid-controller-dbgsym: 3.25.0-1
  • ros-iron-pilz-industrial-motion-planner: 2.8.0-1
  • ros-iron-pilz-industrial-motion-planner-dbgsym: 2.8.0-1
  • ros-iron-position-controllers: 3.25.0-1
  • ros-iron-position-controllers-dbgsym: 3.25.0-1
  • ros-iron-range-sensor-broadcaster: 3.25.0-1
  • ros-iron-range-sensor-broadcaster-dbgsym: 3.25.0-1
  • ros-iron-robotiq-controllers: 0.0.1-1
  • ros-iron-robotiq-controllers-dbgsym: 0.0.1-1
  • ros-iron-ros2-control: 3.26.0-1
  • ros-iron-ros2-controllers: 3.25.0-1
  • ros-iron-ros2controlcli: 3.26.0-1
  • ros-iron-rqt-controller-manager: 3.26.0-1
  • ros-iron-steering-controllers-library: 3.25.0-1
  • ros-iron-steering-controllers-library-dbgsym: 3.25.0-1
  • ros-iron-tricycle-controller: 3.25.0-1
  • ros-iron-tricycle-controller-dbgsym: 3.25.0-1
  • ros-iron-tricycle-steering-controller: 3.25.0-1
  • ros-iron-tricycle-steering-controller-dbgsym: 3.25.0-1
  • ros-iron-ur: 2.3.9-1
  • ros-iron-ur-calibration: 2.3.9-1
  • ros-iron-ur-calibration-dbgsym: 2.3.9-1
  • ros-iron-ur-controllers: 2.3.9-1
  • ros-iron-ur-controllers-dbgsym: 2.3.9-1
  • ros-iron-ur-moveit-config: 2.3.9-1
  • ros-iron-ur-robot-driver: 2.3.9-1
  • ros-iron-ur-robot-driver-dbgsym: 2.3.9-1
  • ros-iron-velocity-controllers: 3.25.0-1
  • ros-iron-velocity-controllers-dbgsym: 3.25.0-1
  • ros-iron-webots-ros2: 2023.1.2-1
  • ros-iron-webots-ros2-control: 2023.1.2-1
  • ros-iron-webots-ros2-control-dbgsym: 2023.1.2-1
  • ros-iron-webots-ros2-epuck: 2023.1.2-1
  • ros-iron-webots-ros2-tiago: 2023.1.2-1
  • ros-iron-webots-ros2-turtlebot: 2023.1.2-1
  • ros-iron-webots-ros2-universal-robot: 2023.1.2-1

Updated Packages [319]:

  • ros-iron-action-tutorials-cpp: 0.27.1-1 → 0.27.2-1
  • ros-iron-action-tutorials-cpp-dbgsym: 0.27.1-1 → 0.27.2-1
  • ros-iron-action-tutorials-interfaces: 0.27.1-1 → 0.27.2-1
  • ros-iron-action-tutorials-interfaces-dbgsym: 0.27.1-1 → 0.27.2-1
  • ros-iron-action-tutorials-py: 0.27.1-1 → 0.27.2-1
  • ros-iron-ament-clang-format: 0.14.3-1 → 0.14.4-1
  • ros-iron-ament-clang-tidy: 0.14.3-1 → 0.14.4-1
  • ros-iron-ament-cmake: 2.0.5-1 → 2.0.6-1
  • ros-iron-ament-cmake-auto: 2.0.5-1 → 2.0.6-1
  • ros-iron-ament-cmake-clang-format: 0.14.3-1 → 0.14.4-1
  • ros-iron-ament-cmake-clang-tidy: 0.14.3-1 → 0.14.4-1
  • ros-iron-ament-cmake-copyright: 0.14.3-1 → 0.14.4-1
  • ros-iron-ament-cmake-core: 2.0.5-1 → 2.0.6-1
  • ros-iron-ament-cmake-cppcheck: 0.14.3-1 → 0.14.4-1
  • ros-iron-ament-cmake-cpplint: 0.14.3-1 → 0.14.4-1
  • ros-iron-ament-cmake-export-definitions: 2.0.5-1 → 2.0.6-1
  • ros-iron-ament-cmake-export-dependencies: 2.0.5-1 → 2.0.6-1
  • ros-iron-ament-cmake-export-include-directories: 2.0.5-1 → 2.0.6-1
  • ros-iron-ament-cmake-export-interfaces: 2.0.5-1 → 2.0.6-1
  • ros-iron-ament-cmake-export-libraries: 2.0.5-1 → 2.0.6-1
  • ros-iron-ament-cmake-export-link-flags: 2.0.5-1 → 2.0.6-1
  • ros-iron-ament-cmake-export-targets: 2.0.5-1 → 2.0.6-1
  • ros-iron-ament-cmake-flake8: 0.14.3-1 → 0.14.4-1
  • ros-iron-ament-cmake-gen-version-h: 2.0.5-1 → 2.0.6-1
  • ros-iron-ament-cmake-gmock: 2.0.5-1 → 2.0.6-1
  • ros-iron-ament-cmake-google-benchmark: 2.0.5-1 → 2.0.6-1
  • ros-iron-ament-cmake-gtest: 2.0.5-1 → 2.0.6-1
  • ros-iron-ament-cmake-include-directories: 2.0.5-1 → 2.0.6-1
  • ros-iron-ament-cmake-libraries: 2.0.5-1 → 2.0.6-1
  • ros-iron-ament-cmake-lint-cmake: 0.14.3-1 → 0.14.4-1
  • ros-iron-ament-cmake-mypy: 0.14.3-1 → 0.14.4-1
  • ros-iron-ament-cmake-pclint: 0.14.3-1 → 0.14.4-1
  • ros-iron-ament-cmake-pep257: 0.14.3-1 → 0.14.4-1
  • ros-iron-ament-cmake-pycodestyle: 0.14.3-1 → 0.14.4-1
  • ros-iron-ament-cmake-pyflakes: 0.14.3-1 → 0.14.4-1
  • ros-iron-ament-cmake-pytest: 2.0.5-1 → 2.0.6-1
  • ros-iron-ament-cmake-python: 2.0.5-1 → 2.0.6-1
  • ros-iron-ament-cmake-target-dependencies: 2.0.5-1 → 2.0.6-1
  • ros-iron-ament-cmake-test: 2.0.5-1 → 2.0.6-1
  • ros-iron-ament-cmake-uncrustify: 0.14.3-1 → 0.14.4-1
  • ros-iron-ament-cmake-vendor-package: 2.0.5-1 → 2.0.6-1
  • ros-iron-ament-cmake-version: 2.0.5-1 → 2.0.6-1
  • ros-iron-ament-cmake-xmllint: 0.14.3-1 → 0.14.4-1
  • ros-iron-ament-copyright: 0.14.3-1 → 0.14.4-1
  • ros-iron-ament-cppcheck: 0.14.3-1 → 0.14.4-1
  • ros-iron-ament-cpplint: 0.14.3-1 → 0.14.4-1
  • ros-iron-ament-flake8: 0.14.3-1 → 0.14.4-1
  • ros-iron-ament-lint: 0.14.3-1 → 0.14.4-1
  • ros-iron-ament-lint-auto: 0.14.3-1 → 0.14.4-1
  • ros-iron-ament-lint-cmake: 0.14.3-1 → 0.14.4-1
  • ros-iron-ament-lint-common: 0.14.3-1 → 0.14.4-1
  • ros-iron-ament-mypy: 0.14.3-1 → 0.14.4-1
  • ros-iron-ament-pclint: 0.14.3-1 → 0.14.4-1
  • ros-iron-ament-pep257: 0.14.3-1 → 0.14.4-1
  • ros-iron-ament-pycodestyle: 0.14.3-1 → 0.14.4-1
  • ros-iron-ament-pyflakes: 0.14.3-1 → 0.14.4-1
  • ros-iron-ament-uncrustify: 0.14.3-1 → 0.14.4-1
  • ros-iron-ament-xmllint: 0.14.3-1 → 0.14.4-1
  • ros-iron-classic-bags: 0.1.0-1 → 0.3.0-1
  • ros-iron-composition: 0.27.1-1 → 0.27.2-1
  • ros-iron-composition-dbgsym: 0.27.1-1 → 0.27.2-1
  • ros-iron-demo-nodes-cpp: 0.27.1-1 → 0.27.2-1
  • ros-iron-demo-nodes-cpp-dbgsym: 0.27.1-1 → 0.27.2-1
  • ros-iron-demo-nodes-cpp-native: 0.27.1-1 → 0.27.2-1
  • ros-iron-demo-nodes-cpp-native-dbgsym: 0.27.1-1 → 0.27.2-1
  • ros-iron-demo-nodes-py: 0.27.1-1 → 0.27.2-1
  • ros-iron-dummy-map-server: 0.27.1-1 → 0.27.2-1
  • ros-iron-dummy-map-server-dbgsym: 0.27.1-1 → 0.27.2-1
  • ros-iron-dummy-robot-bringup: 0.27.1-1 → 0.27.2-1
  • ros-iron-dummy-sensors: 0.27.1-1 → 0.27.2-1
  • ros-iron-dummy-sensors-dbgsym: 0.27.1-1 → 0.27.2-1
  • ros-iron-etsi-its-cam-coding: 2.0.2-1 → 2.1.0-1
  • ros-iron-etsi-its-cam-coding-dbgsym: 2.0.2-1 → 2.1.0-1
  • ros-iron-etsi-its-cam-conversion: 2.0.2-1 → 2.1.0-1
  • ros-iron-etsi-its-cam-msgs: 2.0.2-1 → 2.1.0-1
  • ros-iron-etsi-its-cam-msgs-dbgsym: 2.0.2-1 → 2.1.0-1
  • ros-iron-etsi-its-coding: 2.0.2-1 → 2.1.0-1
  • ros-iron-etsi-its-conversion: 2.0.2-1 → 2.1.0-1
  • ros-iron-etsi-its-conversion-dbgsym: 2.0.2-1 → 2.1.0-1
  • ros-iron-etsi-its-denm-coding: 2.0.2-1 → 2.1.0-1
  • ros-iron-etsi-its-denm-coding-dbgsym: 2.0.2-1 → 2.1.0-1
  • ros-iron-etsi-its-denm-conversion: 2.0.2-1 → 2.1.0-1
  • ros-iron-etsi-its-denm-msgs: 2.0.2-1 → 2.1.0-1
  • ros-iron-etsi-its-denm-msgs-dbgsym: 2.0.2-1 → 2.1.0-1
  • ros-iron-etsi-its-messages: 2.0.2-1 → 2.1.0-1
  • ros-iron-etsi-its-msgs: 2.0.2-1 → 2.1.0-1
  • ros-iron-etsi-its-msgs-utils: 2.0.2-1 → 2.1.0-1
  • ros-iron-etsi-its-primitives-conversion: 2.0.2-1 → 2.1.0-1
  • ros-iron-etsi-its-rviz-plugins: 2.0.2-1 → 2.1.0-1
  • ros-iron-etsi-its-rviz-plugins-dbgsym: 2.0.2-1 → 2.1.0-1
  • ros-iron-examples-rclcpp-async-client: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclcpp-async-client-dbgsym: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclcpp-cbg-executor: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclcpp-cbg-executor-dbgsym: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclcpp-minimal-action-client: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclcpp-minimal-action-client-dbgsym: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclcpp-minimal-action-server: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclcpp-minimal-action-server-dbgsym: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclcpp-minimal-client: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclcpp-minimal-client-dbgsym: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclcpp-minimal-composition: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclcpp-minimal-composition-dbgsym: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclcpp-minimal-publisher: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclcpp-minimal-publisher-dbgsym: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclcpp-minimal-service: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclcpp-minimal-service-dbgsym: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclcpp-minimal-subscriber: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclcpp-minimal-subscriber-dbgsym: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclcpp-minimal-timer: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclcpp-minimal-timer-dbgsym: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclcpp-multithreaded-executor: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclcpp-multithreaded-executor-dbgsym: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclcpp-wait-set: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclcpp-wait-set-dbgsym: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclpy-executors: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclpy-guard-conditions: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclpy-minimal-action-client: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclpy-minimal-action-server: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclpy-minimal-client: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclpy-minimal-publisher: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclpy-minimal-service: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclpy-minimal-subscriber: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclpy-pointcloud-publisher: 0.18.0-2 → 0.18.1-1
  • ros-iron-foxglove-bridge: 0.7.7-1 → 0.7.9-1
  • ros-iron-foxglove-bridge-dbgsym: 0.7.7-1 → 0.7.9-1
  • ros-iron-geometry-tutorials: 0.3.6-4 → 0.4.0-1
  • ros-iron-image-tools: 0.27.1-1 → 0.27.2-1
  • ros-iron-image-tools-dbgsym: 0.27.1-1 → 0.27.2-1
  • ros-iron-intra-process-demo: 0.27.1-1 → 0.27.2-1
  • ros-iron-intra-process-demo-dbgsym: 0.27.1-1 → 0.27.2-1
  • ros-iron-launch-testing-examples: 0.18.0-2 → 0.18.1-1
  • ros-iron-libcurl-vendor: 3.2.2-3 → 3.2.3-1
  • ros-iron-lifecycle: 0.27.1-1 → 0.27.2-1
  • ros-iron-lifecycle-dbgsym: 0.27.1-1 → 0.27.2-1
  • ros-iron-lifecycle-py: 0.27.1-1 → 0.27.2-1
  • ros-iron-logging-demo: 0.27.1-1 → 0.27.2-1
  • ros-iron-logging-demo-dbgsym: 0.27.1-1 → 0.27.2-1
  • ros-iron-mcap-vendor: 0.22.6-1 → 0.22.7-1
  • ros-iron-mcap-vendor-dbgsym: 0.22.6-1 → 0.22.7-1
  • ros-iron-metavision-driver: 1.2.8-1 → 2.0.0-1
  • ros-iron-metavision-driver-dbgsym: 1.2.8-1 → 2.0.0-1
  • ros-iron-ompl: 1.5.2-4 → 1.6.0-1
  • ros-iron-ompl-dbgsym: 1.5.2-4 → 1.6.0-1
  • ros-iron-openeb-vendor: 1.2.2-1 → 2.0.0-1
  • ros-iron-openeb-vendor-dbgsym: 1.2.2-1 → 2.0.0-1
  • ros-iron-pendulum-control: 0.27.1-1 → 0.27.2-1
  • ros-iron-pendulum-control-dbgsym: 0.27.1-1 → 0.27.2-1
  • ros-iron-pendulum-msgs: 0.27.1-1 → 0.27.2-1
  • ros-iron-pendulum-msgs-dbgsym: 0.27.1-1 → 0.27.2-1
  • ros-iron-quality-of-service-demo-cpp: 0.27.1-1 → 0.27.2-1
  • ros-iron-quality-of-service-demo-cpp-dbgsym: 0.27.1-1 → 0.27.2-1
  • ros-iron-quality-of-service-demo-py: 0.27.1-1 → 0.27.2-1
  • ros-iron-rcl: 6.0.5-1 → 6.0.6-1
  • ros-iron-rcl-action: 6.0.5-1 → 6.0.6-1
  • ros-iron-rcl-action-dbgsym: 6.0.5-1 → 6.0.6-1
  • ros-iron-rcl-dbgsym: 6.0.5-1 → 6.0.6-1
  • ros-iron-rcl-lifecycle: 6.0.5-1 → 6.0.6-1
  • ros-iron-rcl-lifecycle-dbgsym: 6.0.5-1 → 6.0.6-1
  • ros-iron-rcl-yaml-param-parser: 6.0.5-1 → 6.0.6-1
  • ros-iron-rcl-yaml-param-parser-dbgsym: 6.0.5-1 → 6.0.6-1
  • ros-iron-rclcpp: 21.0.6-1 → 21.0.7-1
  • ros-iron-rclcpp-action: 21.0.6-1 → 21.0.7-1
  • ros-iron-rclcpp-action-dbgsym: 21.0.6-1 → 21.0.7-1
  • ros-iron-rclcpp-components: 21.0.6-1 → 21.0.7-1
  • ros-iron-rclcpp-components-dbgsym: 21.0.6-1 → 21.0.7-1
  • ros-iron-rclcpp-dbgsym: 21.0.6-1 → 21.0.7-1
  • ros-iron-rclcpp-lifecycle: 21.0.6-1 → 21.0.7-1
  • ros-iron-rclcpp-lifecycle-dbgsym: 21.0.6-1 → 21.0.7-1
  • ros-iron-rclpy: 4.1.5-1 → 4.1.6-1
  • ros-iron-rcpputils: 2.6.3-1 → 2.6.4-1
  • ros-iron-rcpputils-dbgsym: 2.6.3-1 → 2.6.4-1
  • ros-iron-resource-retriever: 3.2.2-3 → 3.2.3-1
  • ros-iron-resource-retriever-dbgsym: 3.2.2-3 → 3.2.3-1
  • ros-iron-rmf-api-msgs: 0.1.1-1 → 0.1.2-1
  • ros-iron-rmf-charger-msgs: 3.1.2-1 → 3.1.3-1
  • ros-iron-rmf-charger-msgs-dbgsym: 3.1.2-1 → 3.1.3-1
  • ros-iron-rmf-charging-schedule: 2.2.5-1 → 2.2.6-1
  • ros-iron-rmf-dispenser-msgs: 3.1.2-1 → 3.1.3-1
  • ros-iron-rmf-dispenser-msgs-dbgsym: 3.1.2-1 → 3.1.3-1
  • ros-iron-rmf-door-msgs: 3.1.2-1 → 3.1.3-1
  • ros-iron-rmf-door-msgs-dbgsym: 3.1.2-1 → 3.1.3-1
  • ros-iron-rmf-fleet-adapter: 2.2.5-1 → 2.2.6-1
  • ros-iron-rmf-fleet-adapter-dbgsym: 2.2.5-1 → 2.2.6-1
  • ros-iron-rmf-fleet-adapter-python: 2.2.5-1 → 2.2.6-1
  • ros-iron-rmf-fleet-msgs: 3.1.2-1 → 3.1.3-1
  • ros-iron-rmf-fleet-msgs-dbgsym: 3.1.2-1 → 3.1.3-1
  • ros-iron-rmf-ingestor-msgs: 3.1.2-1 → 3.1.3-1
  • ros-iron-rmf-ingestor-msgs-dbgsym: 3.1.2-1 → 3.1.3-1
  • ros-iron-rmf-lift-msgs: 3.1.2-1 → 3.1.3-1
  • ros-iron-rmf-lift-msgs-dbgsym: 3.1.2-1 → 3.1.3-1
  • ros-iron-rmf-obstacle-msgs: 3.1.2-1 → 3.1.3-1
  • ros-iron-rmf-obstacle-msgs-dbgsym: 3.1.2-1 → 3.1.3-1
  • ros-iron-rmf-scheduler-msgs: 3.1.2-1 → 3.1.3-1
  • ros-iron-rmf-scheduler-msgs-dbgsym: 3.1.2-1 → 3.1.3-1
  • ros-iron-rmf-site-map-msgs: 3.1.2-1 → 3.1.3-1
  • ros-iron-rmf-site-map-msgs-dbgsym: 3.1.2-1 → 3.1.3-1
  • ros-iron-rmf-task-msgs: 3.1.2-1 → 3.1.3-1
  • ros-iron-rmf-task-msgs-dbgsym: 3.1.2-1 → 3.1.3-1
  • ros-iron-rmf-task-ros2: 2.2.5-1 → 2.2.6-1
  • ros-iron-rmf-task-ros2-dbgsym: 2.2.5-1 → 2.2.6-1
  • ros-iron-rmf-traffic-msgs: 3.1.2-1 → 3.1.3-1
  • ros-iron-rmf-traffic-msgs-dbgsym: 3.1.2-1 → 3.1.3-1
  • ros-iron-rmf-traffic-ros2: 2.2.5-1 → 2.2.6-1
  • ros-iron-rmf-traffic-ros2-dbgsym: 2.2.5-1 → 2.2.6-1
  • ros-iron-rmf-websocket: 2.2.5-1 → 2.2.6-1
  • ros-iron-rmf-websocket-dbgsym: 2.2.5-1 → 2.2.6-1
  • ros-iron-rmf-workcell-msgs: 3.1.2-1 → 3.1.3-1
  • ros-iron-rmf-workcell-msgs-dbgsym: 3.1.2-1 → 3.1.3-1
  • ros-iron-rmw-fastrtps-cpp: 7.1.3-1 → 7.1.4-1
  • ros-iron-rmw-fastrtps-cpp-dbgsym: 7.1.3-1 → 7.1.4-1
  • ros-iron-rmw-fastrtps-dynamic-cpp: 7.1.3-1 → 7.1.4-1
  • ros-iron-rmw-fastrtps-dynamic-cpp-dbgsym: 7.1.3-1 → 7.1.4-1
  • ros-iron-rmw-fastrtps-shared-cpp: 7.1.3-1 → 7.1.4-1
  • ros-iron-rmw-fastrtps-shared-cpp-dbgsym: 7.1.3-1 → 7.1.4-1
  • ros-iron-rmw-implementation: 2.12.0-2 → 2.12.1-1
  • ros-iron-rmw-implementation-dbgsym: 2.12.0-2 → 2.12.1-1
  • ros-iron-ros-gz: 0.254.1-1 → 0.254.2-1
  • ros-iron-ros-gz-bridge: 0.254.1-1 → 0.254.2-1
  • ros-iron-ros-gz-bridge-dbgsym: 0.254.1-1 → 0.254.2-1
  • ros-iron-ros-gz-image: 0.254.1-1 → 0.254.2-1
  • ros-iron-ros-gz-image-dbgsym: 0.254.1-1 → 0.254.2-1
  • ros-iron-ros-gz-interfaces: 0.254.1-1 → 0.254.2-1
  • ros-iron-ros-gz-interfaces-dbgsym: 0.254.1-1 → 0.254.2-1
  • ros-iron-ros-gz-sim: 0.254.1-1 → 0.254.2-1
  • ros-iron-ros-gz-sim-dbgsym: 0.254.1-1 → 0.254.2-1
  • ros-iron-ros-gz-sim-demos: 0.254.1-1 → 0.254.2-1
  • ros-iron-ros-ign: 0.254.1-1 → 0.254.2-1
  • ros-iron-ros-ign-bridge: 0.254.1-1 → 0.254.2-1
  • ros-iron-ros-ign-bridge-dbgsym: 0.254.1-1 → 0.254.2-1
  • ros-iron-ros-ign-gazebo: 0.254.1-1 → 0.254.2-1
  • ros-iron-ros-ign-gazebo-dbgsym: 0.254.1-1 → 0.254.2-1
  • ros-iron-ros-ign-gazebo-demos: 0.254.1-1 → 0.254.2-1
  • ros-iron-ros-ign-image: 0.254.1-1 → 0.254.2-1
  • ros-iron-ros-ign-image-dbgsym: 0.254.1-1 → 0.254.2-1
  • ros-iron-ros-ign-interfaces: 0.254.1-1 → 0.254.2-1
  • ros-iron-ros-ign-interfaces-dbgsym: 0.254.1-1 → 0.254.2-1
  • ros-iron-ros2-socketcan: 1.2.0-1 → 1.3.0-1
  • ros-iron-ros2-socketcan-dbgsym: 1.2.0-1 → 1.3.0-1
  • ros-iron-ros2-socketcan-msgs: 1.2.0-1 → 1.3.0-1
  • ros-iron-ros2-socketcan-msgs-dbgsym: 1.2.0-1 → 1.3.0-1
  • ros-iron-ros2action: 0.25.6-1 → 0.25.7-1
  • ros-iron-ros2bag: 0.22.6-1 → 0.22.7-1
  • ros-iron-ros2cli: 0.25.6-1 → 0.25.7-1
  • ros-iron-ros2cli-test-interfaces: 0.25.6-1 → 0.25.7-1
  • ros-iron-ros2cli-test-interfaces-dbgsym: 0.25.6-1 → 0.25.7-1
  • ros-iron-ros2component: 0.25.6-1 → 0.25.7-1
  • ros-iron-ros2doctor: 0.25.6-1 → 0.25.7-1
  • ros-iron-ros2interface: 0.25.6-1 → 0.25.7-1
  • ros-iron-ros2lifecycle: 0.25.6-1 → 0.25.7-1
  • ros-iron-ros2lifecycle-test-fixtures: 0.25.6-1 → 0.25.7-1
  • ros-iron-ros2lifecycle-test-fixtures-dbgsym: 0.25.6-1 → 0.25.7-1
  • ros-iron-ros2multicast: 0.25.6-1 → 0.25.7-1
  • ros-iron-ros2node: 0.25.6-1 → 0.25.7-1
  • ros-iron-ros2param: 0.25.6-1 → 0.25.7-1
  • ros-iron-ros2pkg: 0.25.6-1 → 0.25.7-1
  • ros-iron-ros2run: 0.25.6-1 → 0.25.7-1
  • ros-iron-ros2service: 0.25.6-1 → 0.25.7-1
  • ros-iron-ros2topic: 0.25.6-1 → 0.25.7-1
  • ros-iron-ros2trace: 6.3.1-1 → 6.3.2-1
  • ros-iron-rosbag2: 0.22.6-1 → 0.22.7-1
  • ros-iron-rosbag2-compression: 0.22.6-1 → 0.22.7-1
  • ros-iron-rosbag2-compression-dbgsym: 0.22.6-1 → 0.22.7-1
  • ros-iron-rosbag2-compression-zstd: 0.22.6-1 → 0.22.7-1
  • ros-iron-rosbag2-compression-zstd-dbgsym: 0.22.6-1 → 0.22.7-1
  • ros-iron-rosbag2-cpp: 0.22.6-1 → 0.22.7-1
  • ros-iron-rosbag2-cpp-dbgsym: 0.22.6-1 → 0.22.7-1
  • ros-iron-rosbag2-examples-cpp: 0.22.6-1 → 0.22.7-1
  • ros-iron-rosbag2-examples-cpp-dbgsym: 0.22.6-1 → 0.22.7-1
  • ros-iron-rosbag2-examples-py: 0.22.6-1 → 0.22.7-1
  • ros-iron-rosbag2-interfaces: 0.22.6-1 → 0.22.7-1
  • ros-iron-rosbag2-interfaces-dbgsym: 0.22.6-1 → 0.22.7-1
  • ros-iron-rosbag2-performance-benchmarking: 0.22.6-1 → 0.22.7-1
  • ros-iron-rosbag2-performance-benchmarking-msgs: 0.22.6-1 → 0.22.7-1
  • ros-iron-rosbag2-py: 0.22.6-1 → 0.22.7-1
  • ros-iron-rosbag2-storage: 0.22.6-1 → 0.22.7-1
  • ros-iron-rosbag2-storage-dbgsym: 0.22.6-1 → 0.22.7-1
  • ros-iron-rosbag2-storage-default-plugins: 0.22.6-1 → 0.22.7-1
  • ros-iron-rosbag2-storage-mcap: 0.22.6-1 → 0.22.7-1
  • ros-iron-rosbag2-storage-mcap-dbgsym: 0.22.6-1 → 0.22.7-1
  • ros-iron-rosbag2-storage-sqlite3: 0.22.6-1 → 0.22.7-1
  • ros-iron-rosbag2-storage-sqlite3-dbgsym: 0.22.6-1 → 0.22.7-1
  • ros-iron-rosbag2-test-common: 0.22.6-1 → 0.22.7-1
  • ros-iron-rosbag2-test-msgdefs: 0.22.6-1 → 0.22.7-1
  • ros-iron-rosbag2-test-msgdefs-dbgsym: 0.22.6-1 → 0.22.7-1
  • ros-iron-rosbag2-tests: 0.22.6-1 → 0.22.7-1
  • ros-iron-rosbag2-transport: 0.22.6-1 → 0.22.7-1
  • ros-iron-rosbag2-transport-dbgsym: 0.22.6-1 → 0.22.7-1
  • ros-iron-rqt-bag: 1.3.4-1 → 1.3.5-1
  • ros-iron-rqt-bag-plugins: 1.3.4-1 → 1.3.5-1
  • ros-iron-rqt-graph: 1.4.2-1 → 1.4.3-1
  • ros-iron-rviz-assimp-vendor: 12.4.7-1 → 12.4.8-1
  • ros-iron-rviz-common: 12.4.7-1 → 12.4.8-1
  • ros-iron-rviz-common-dbgsym: 12.4.7-1 → 12.4.8-1
  • ros-iron-rviz-default-plugins: 12.4.7-1 → 12.4.8-1
  • ros-iron-rviz-default-plugins-dbgsym: 12.4.7-1 → 12.4.8-1
  • ros-iron-rviz-ogre-vendor: 12.4.7-1 → 12.4.8-1
  • ros-iron-rviz-ogre-vendor-dbgsym: 12.4.7-1 → 12.4.8-1
  • ros-iron-rviz-rendering: 12.4.7-1 → 12.4.8-1
  • ros-iron-rviz-rendering-dbgsym: 12.4.7-1 → 12.4.8-1
  • ros-iron-rviz-rendering-tests: 12.4.7-1 → 12.4.8-1
  • ros-iron-rviz-visual-testing-framework: 12.4.7-1 → 12.4.8-1
  • ros-iron-rviz2: 12.4.7-1 → 12.4.8-1
  • ros-iron-rviz2-dbgsym: 12.4.7-1 → 12.4.8-1
  • ros-iron-shared-queues-vendor: 0.22.6-1 → 0.22.7-1
  • ros-iron-sqlite3-vendor: 0.22.6-1 → 0.22.7-1
  • ros-iron-test-ros-gz-bridge: 0.254.1-1 → 0.254.2-1
  • ros-iron-topic-monitor: 0.27.1-1 → 0.27.2-1
  • ros-iron-topic-statistics-demo: 0.27.1-1 → 0.27.2-1
  • ros-iron-topic-statistics-demo-dbgsym: 0.27.1-1 → 0.27.2-1
  • ros-iron-tracetools: 6.3.1-1 → 6.3.2-1
  • ros-iron-tracetools-dbgsym: 6.3.1-1 → 6.3.2-1
  • ros-iron-tracetools-launch: 6.3.1-1 → 6.3.2-1
  • ros-iron-tracetools-read: 6.3.1-1 → 6.3.2-1
  • ros-iron-tracetools-test: 6.3.1-1 → 6.3.2-1
  • ros-iron-tracetools-trace: 6.3.1-1 → 6.3.2-1
  • ros-iron-turtle-tf2-cpp: 0.3.6-4 → 0.4.0-1
  • ros-iron-turtle-tf2-cpp-dbgsym: 0.3.6-4 → 0.4.0-1
  • ros-iron-turtle-tf2-py: 0.3.6-4 → 0.4.0-1
  • ros-iron-zstd-vendor: 0.22.6-1 → 0.22.7-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:

  • Aaron Chong
  • Aditya Pande
  • Alejandro Hernandez
  • Alejandro Hernandez Cordero
  • Alejandro Hernández
  • Alejandro Hernández Cordero
  • Alex Moriarty
  • Anthony Baker
  • Arjo Chakravarty
  • Audrow Nash
  • Bence Magyar
  • Bernd Pfrommer
  • Blake Anderson
  • Boitumelo Ruf
  • Brandon Ong
  • Christian Henkel
  • Christophe Bedard
  • Cyberbotics
  • David V. Lu!!
  • Denis Stogl
  • Denis Štogl
  • Felix Exner
  • Foxglove
  • Geoffrey Biggs
  • Grey
  • Henning Kayser
  • Ivan Paunovic
  • Jean-Pierre Busch
  • John Hurliman
  • Josh Whitley
  • Louise Poubel
  • Marco A. Gutiérrez
  • Mark Moll
  • Michael Görner
  • Michael Jeronimo
  • Michael Orlov
  • Morgan Quigley
  • MoveIt Release Team
  • Peter David Fagan
  • ROS Tooling Working Group
  • Rushyendra Maganty
  • Shane Loretz
  • William Woodall
  • Yadunund
  • geoff
  • lovro
  • methylDragon

3 posts - 2 participants

Read full topic

by Yadunund on July 17, 2024 09:58 PM

Rosdoc2 now available in the ROS repositories

rosdoc2, the utility used to generate ROS 2 package documentation via doc jobs. Is now available in the ROS package repositories for Ubuntu and Debian and on PyPI for other platforms*.

The ROS build farm currently installs the main branch of rosdoc2 rather than the current release, but we’ll likely switch to releases in the near feature.

Updated installation instructions are available in the project README.md.

*: If you install from PyPI please note that doxygen and graphviz are system dependencies that need to be manually installed

1 post - 1 participant

Read full topic

by nuclearsandwich on July 17, 2024 09:40 PM

Announcing Autoware Challenge 2024

Overview

Autoware is the world’s first “all-in-one” open-source software for autonomous driving based on ROS hosted under the Autoware Foundation. As one of the main contributors of Autoware, TIER IV is sponsoring a new challenge to encourage development of autonomous driving technology.

Through the challenge, participants will come up with their own idea that would improve Autoware and present their solution. At the end of the challenge, TIER IV will examine the presentation and choose a winner who came up with the best solution that improves Autoware functionality.

Visit our website for the details.

Awards

First Place: 15,000 USD
Second Place: 7,000 USD
Third Place: 3,500 USD

Timeline

Registration/Abstract Deadline: September 2nd, 2024
Proposal Submission Deadline: January 31st, 2024
Online Presentation: February 7th, 2025
Announcement of the Results: February 21st, 20225

3 posts - 2 participants

Read full topic

by NaoyoriTanzawa on July 17, 2024 01:57 AM

July 14, 2024
How does the odometer act in mobile robots like Limo?

For mobile robots, there are three basic questions: Where am I? Where am I going? How do I get there? The first question is describing a robot positioning topic. The positioning topic can be explained in more detail as follows: the mobile robot determines its position and posture in the world (global or local) in real time based on its own state and sensor information.

In this project, we will discuss details about odometer in the mobile base such as Limo.

Introduction of robot wheel odometer and calibration test

The main positioning solutions for driverless cars in Ackerman turned to include: wheel odometer, visual odometer, laser odometer, inertial navigation module (IMU+GPS), and multi-sensor fusion. Wheel odometer is the simplest and lowest-cost method. Like other positioning solutions, the wheel odometer also requires sensors to perceive external information, but the motor speed measurement module used by the wheel odometer is a very low-cost sensor. The speed module is shown in figure below.
image

The pose model of a mobile robot is the state of the robot in the world coordinate system. The random variable Xt = (xt, yt, θt) is often used to describe the state of the robot in the world coordinate system at time t, referred to as pose. Among them, (xt, yt) represents the position of the robot in the world coordinate system at time t, and θt represents the direction of the robot. The positive X-axis of the world coordinate system is assumed to be the positive direction, and the counterclockwise rotation is the positive direction of rotation.

At the initial moment, the robot coordinate system and the world coordinate system coincide. The pose description of the robot at a certain time t is shown in the figure.

The rotational angular velocity of the two wheels can be obtained through the wheel speed odometer. Therefore, the angular velocity of the wheel is needed to represent the x displacement, y displacement, and angle calculated by the odometer.

The quantities we need to calibrate are the wheel spacing and the wheel radius. The formula for establishing the mathematical model is to use the wheel spacing and wheel radius to represent the angular velocity and linear velocity of the vehicle body. The wheel spacing diagram is shown.


The angular velocity of the chassis center relative to the body’s rotation center is equal to the angular velocity of the two wheels relative to the body’s rotation center. That is:
image
Through the relationship between linear velocity and angular velocity, d is introduced:
image
So we can get r:
image
The motion solution solves w. Bringing r back, we can find w as:
image
Solve v in motion. By simplifying w*r, we can get v as:
image

The calculation of the odometer refers to the cumulative calculation of the robot’s position and posture in the world coordinate system at any time, starting from the moment the robot is powered on (the robot’s heading angle is the positive direction of the world coordinate system X).

The usual method for calculating the odometer is speed integral calculation: the speeds VL and VR of the left and right wheels of the robot are measured by the encoders of the left and right motors. In a short moment △t, the robot is considered to be moving at a uniform speed, and the increments of the X and Y axes of the robot in the world coordinate system at that moment are calculated based on the heading angle of the robot at the previous moment. The increments are then accumulated, and the yaw value of the IMU is used for the heading angle θ. Then the robot’s odometer can be obtained based on the above description.
The specific calculation is shown in the figure below:

Wheel odometer calibration

The three main sources of odometer system errors are “the deviation between the actual diameter of the left and right wheels and the nominal diameter”, “the deviation between the actual spacing between the left and right wheels and the nominal spacing” and “the actual average of the diameters of the two wheels is not equal to the nominal average”.

“The deviation between the actual diameter of the left and right wheels and the nominal diameter” will cause the distance error of linear motion. “The deviation between the actual spacing between the left and right wheels and the nominal spacing” will cause the direction error of rotational motion. “The actual average of the diameters of the two wheels is not equal to the nominal average” will affect both linear motion and rotational motion.

We usually assume that the actual position is linearly related to the wheel odometer. By recording the actual position by ourselves and the position x and y of the odometer of the car, we can use the least squares rule to obtain a linear equation: y=ax+b. The coefficients of the equation can be added when calculating the odometer to correct the odometer.
The code can be viewed in the driver package scout_base/src/scout_messenger.cpp of the robot.

First, data needs to be collected, that is, the actual distance moved by the car and the distance of the odometer of the car.
Running the code in Matlab, the results are as follows
p = [1.0482 -0.0778]
That is, a=1.0482, b=-0.0778, which are the calibration parameters in the x direction. Similarly, the calibration parameters in the y direction and the yaw angle can be calculated. This calibration is reflected in line 28 of the following code.

Detailed explanation of the wheel odometer code released by ROS

  1. Create package
catkin_create_pkg pub_odom roscpp tf nav_msgs
  1. Create the pub_odom_node.cpp file in the src folder under the pub_odom function package and add the following code:
#include <ros/ros.h>
#include <tf/transform_broadcaster.h>
#include <nav_msgs/Odometry.h>

int main(int argc, char** argv)
{
    ros::init(argc, argv, "odometry_publisher");  // Init ROS code
    ros::NodeHandle n;  // Create handle

    // Create publish object to publish odometer message
    ros::Publisher odom_pub = n.advertise<nav_msgs::Odometry>("odom", 50);

    // Create TransformBroadcaster object to publish transformation
    tf::TransformBroadcaster odom_broadcaster;

    // Initial status of robot
    double x = 0.0;
    double y = 0.0;
    double th = 0.0;
    double vx = 0.1;
    double vy = -0.1;
    double vth = 0.1;

    // Init time
    ros::Time current_time, last_time;
    current_time = ros::Time::now();
    last_time = ros::Time::now();

    // set roop as1Hz
    ros::Rate r(1.0);

    // Enter loop
    while(n.ok())
    {
        ros::spinOnce();  

        current_time = ros::Time::now();  // Get current time

        // 计算机器人的位移
        double dt = (current_time - last_time).toSec();  // calculate time difference
        double delta_x = (vx * cos(th) - vy * sin(th)) * dt;  //Calculate the x-direction displacement
        double delta_y = (vx * sin(th) + vy * cos(th)) * dt;  // Calculate the y-direction displacement
        double delta_th = vth * dt;  // Calculate the angle change

        // Update robot position and angle
        x += delta_x;
        y += delta_y;
        th += delta_th;

        // publish robot transformation
        geometry_msgs::Quaternion odom_quat = tf::createQuaternionMsgFromYaw(th);  // Convert angle to quaternion
        geometry_msgs::TransformStamped odom_trans;
        odom_trans.header.stamp = current_time;
        odom_trans.header.frame_id = "odom";
        odom_trans.child_frame_id = "base_link";
        odom_trans.transform.translation.x = x;
        odom_trans.transform.translation.y = y;
        odom_trans.transform.translation.z = 0.0;
        odom_trans.transform.rotation = odom_quat;
        odom_broadcaster.sendTransform(odom_trans);

        // pubilsh odometer
        nav_msgs::Odometry odom;
        odom.header.stamp = current_time;
        odom.header.frame_id = "odom";
        odom.pose.pose.position.x = x;
        odom.pose.pose.position.y = y;
        odom.pose.pose.position.z = 0.0;
        odom.pose.pose.orientation = odom_quat;
        odom.child_frame_id = "base_link";
        odom.twist.twist.linear.x = vx;
        odom.twist.twist.linear.y = vy;
        odom.twist.twist.angular.z = vth;
        odom_pub.publish(odom);

        last_time = current_time;  // Update timestamp
        r.sleep();  
    }
}

Code Review

ros::Publisher odom_pub = n.advertise<nav_msgs::Odometry>("odom", 50);
tf::TransformBroadcaster odom_broadcaster;

We need to create a ros::Publisher and a tf::TransformBroadcaster to send messages using ROS and tf respectively.

double x = 0.0;
double y = 0.0;
double th = 0.0;

We assume that the robot starts at the origin of the “odom” coordinate system.

double vx = 0.1;
double vy = ‐0.1;
double vth = 0.1;

Here we will set some velocities which will cause the “base_link” frame to move in the “odom” frame at 0.1m/s in the x direction, -0.1m/s in the y direction, and 0.1rad/s in the th direction. This will more or less cause our simulated robot to go in a circle.

ros::Rate r(1.0);

In this example, we will publish the mileage information at a rate of 1 Hz to make the display more concise, most systems will publish the mileage information at a higher rate.

//compute odometry in a typical way given the velocities of the robot
double dt = (current_time ‐ last_time).toSec();
double delta_x = (vx * cos(th) ‐ vy * sin(th)) * dt;
double delta_y = (vx * sin(th) + vy * cos(th)) * dt;
double delta_th = vth * dt;
x += delta_x;// x = a * x + b;
x = 1.0482x -0.0778;
y += delta_y;// y = m * m + n;
th += delta_th;// th = q * th + p;

Here we are updating our mileage information based on the constant speed we set. Of course, a real mileage system would incorporate speed into its calculations.

//since all odometry is 6DOF we'll need a quaternion created from yaw
geometry_msgs::Quaternion odom_quat = tf::createQuaternionMsgFromYaw(th);

We generally try to use 3D versions of all messages in our system to allow 2D and 3D components to work together where appropriate and to keep the number of messages to a minimum. Therefore, it is necessary to convert our yaw values ​​to quaternions. tf provides functions that allow quaternions to be easily created from yaw, and yaw values ​​to be easily obtained from quaternions.

//first, we'll publish the transform over tf
geometry_msgs::TransformStamped odom_trans;
odom_trans.header.stamp = current_time;
odom_trans.header.frame_id = "odom";
odom_trans.child_frame_id = "base_link";

Here, we’ll create a TransformStamped message to send over tf. We want to publish the transform from the “odom” coordinate system to the “base_link” coordinate system at current_time. So, we’ll set the message header and child_frame_id accordingly, making sure to use “odom” as the parent coordinate system and “base_link” as the child coordinate system.

odom_trans.transform.translation.x = x;
odom_trans.transform.translation.y = y;
odom_trans.transform.translation.z = 0.0;
odom_trans.transform.rotation = odom_quat;
//send the transform
odom_broadcaster.sendTransform(odom_trans);

Stuff our odometry data into the transform message and send the transform using the TransformBroadcaster.

//next, we'll publish the odometry message over ROS
nav_msgs::Odometry odom;
odom.header.stamp = current_time;
odom.header.frame_id = "odom";

We also need to publish a nav_msgs/Odometry message type so the navigation package can get velocity information from it. We set the header of the message to the current_time and the “odom” frame.

//set the position
odom.pose.pose.position.x = x;
odom.pose.pose.position.y = y;
odom.pose.pose.position.z = 0.0;
odom.pose.pose.orientation = odom_quat;
//set the velocity
odom.child_frame_id = "base_link";
odom.twist.twist.linear.x = vx;
odom.twist.twist.linear.y = vy;
odom.twist.twist.angular.z = vth;

This will populate the message with the mileage data and send it off. We set the child_frame_id of the message to the “base_link” frame, since that’s the frame we want to send velocity information to.

  1. Add the following two lines of code in the CMakeLists.txt file
add_executable(pub_odom_node src/pub_odom_node.cpp)
target_link_libraries(pub_odom_node
${catkin_LIBRARIES}
)
  1. Compile using catkin_make
  2. Run the code
    First open roscore
    Then run the code we wrote
rosrun pub_odom pub_odom_node
  1. After the code runs successfully, use rostopic echo to view the published odom information
rostopic echo /odom

Test result

After-class QUIZS
● In ROS, how to use the robot’s wheel odometer data to realize the robot’s pose estimation? Please write a ROS node, subscribe to the robot’s wheel odometer data, use the odometer data to realize the robot’s pose estimation, and publish the estimated pose information.

● How to calibrate the robot’s wheel odometer? Please write a ROS node, let the robot move on a specific trajectory, record the robot’s wheel odometer data and real pose information, and use the calibration algorithm to calibrate the wheel odometer, and finally save the calibration results in the ROS parameter server.

About Limo

If you are interested in Limo or have some technical questions about it, feel free to join AgileX Robotics or AgileX Robotics. Let’s talk about it!

2 posts - 2 participants

Read full topic

by Agilex_Robotics on July 14, 2024 03:28 AM

July 13, 2024
Patch Release 6 and New Packages for Iron Irwini 2024-07-12

We’re happy to announce the latest ROS 2 Iron Irwini release :iron: :irwini: :tada:

The latest sync brings 12 new packages and 358 updates to ROS 2 Iron Irwini. This sync was tagged as iron/2024-07-12 .

Package Updates for iron

Added Packages [12]:

  • ros-iron-flex-sync: 2.0.0-1
  • ros-iron-mrpt-sensor-gnss-nmea: 0.2.1-1
  • ros-iron-mrpt-sensor-gnss-nmea-dbgsym: 0.2.1-1
  • ros-iron-mrpt-sensor-gnss-novatel: 0.2.1-1
  • ros-iron-mrpt-sensor-gnss-novatel-dbgsym: 0.2.1-1
  • ros-iron-pid-controller: 3.25.0-1
  • ros-iron-pid-controller-dbgsym: 3.25.0-1
  • ros-iron-rosx-introspection: 1.0.1-1
  • ros-iron-situational-graphs-datasets: 0.0.0-1
  • ros-iron-situational-graphs-reasoning-msgs: 0.0.0-1
  • ros-iron-situational-graphs-reasoning-msgs-dbgsym: 0.0.0-1
  • ros-iron-situational-graphs-wrapper: 0.0.0-1

Updated Packages [358]:

  • ros-iron-ackermann-steering-controller: 3.24.0-1 → 3.25.0-1
  • ros-iron-ackermann-steering-controller-dbgsym: 3.24.0-1 → 3.25.0-1
  • ros-iron-action-tutorials-cpp: 0.27.1-1 → 0.27.2-1
  • ros-iron-action-tutorials-cpp-dbgsym: 0.27.1-1 → 0.27.2-1
  • ros-iron-action-tutorials-interfaces: 0.27.1-1 → 0.27.2-1
  • ros-iron-action-tutorials-interfaces-dbgsym: 0.27.1-1 → 0.27.2-1
  • ros-iron-action-tutorials-py: 0.27.1-1 → 0.27.2-1
  • ros-iron-admittance-controller: 3.24.0-1 → 3.25.0-1
  • ros-iron-admittance-controller-dbgsym: 3.24.0-1 → 3.25.0-1
  • ros-iron-ament-clang-format: 0.14.3-1 → 0.14.4-1
  • ros-iron-ament-clang-tidy: 0.14.3-1 → 0.14.4-1
  • ros-iron-ament-cmake: 2.0.5-1 → 2.0.6-1
  • ros-iron-ament-cmake-auto: 2.0.5-1 → 2.0.6-1
  • ros-iron-ament-cmake-clang-format: 0.14.3-1 → 0.14.4-1
  • ros-iron-ament-cmake-clang-tidy: 0.14.3-1 → 0.14.4-1
  • ros-iron-ament-cmake-copyright: 0.14.3-1 → 0.14.4-1
  • ros-iron-ament-cmake-core: 2.0.5-1 → 2.0.6-1
  • ros-iron-ament-cmake-cppcheck: 0.14.3-1 → 0.14.4-1
  • ros-iron-ament-cmake-cpplint: 0.14.3-1 → 0.14.4-1
  • ros-iron-ament-cmake-export-definitions: 2.0.5-1 → 2.0.6-1
  • ros-iron-ament-cmake-export-dependencies: 2.0.5-1 → 2.0.6-1
  • ros-iron-ament-cmake-export-include-directories: 2.0.5-1 → 2.0.6-1
  • ros-iron-ament-cmake-export-interfaces: 2.0.5-1 → 2.0.6-1
  • ros-iron-ament-cmake-export-libraries: 2.0.5-1 → 2.0.6-1
  • ros-iron-ament-cmake-export-link-flags: 2.0.5-1 → 2.0.6-1
  • ros-iron-ament-cmake-export-targets: 2.0.5-1 → 2.0.6-1
  • ros-iron-ament-cmake-flake8: 0.14.3-1 → 0.14.4-1
  • ros-iron-ament-cmake-gen-version-h: 2.0.5-1 → 2.0.6-1
  • ros-iron-ament-cmake-gmock: 2.0.5-1 → 2.0.6-1
  • ros-iron-ament-cmake-google-benchmark: 2.0.5-1 → 2.0.6-1
  • ros-iron-ament-cmake-gtest: 2.0.5-1 → 2.0.6-1
  • ros-iron-ament-cmake-include-directories: 2.0.5-1 → 2.0.6-1
  • ros-iron-ament-cmake-libraries: 2.0.5-1 → 2.0.6-1
  • ros-iron-ament-cmake-lint-cmake: 0.14.3-1 → 0.14.4-1
  • ros-iron-ament-cmake-mypy: 0.14.3-1 → 0.14.4-1
  • ros-iron-ament-cmake-pclint: 0.14.3-1 → 0.14.4-1
  • ros-iron-ament-cmake-pep257: 0.14.3-1 → 0.14.4-1
  • ros-iron-ament-cmake-pycodestyle: 0.14.3-1 → 0.14.4-1
  • ros-iron-ament-cmake-pyflakes: 0.14.3-1 → 0.14.4-1
  • ros-iron-ament-cmake-pytest: 2.0.5-1 → 2.0.6-1
  • ros-iron-ament-cmake-python: 2.0.5-1 → 2.0.6-1
  • ros-iron-ament-cmake-target-dependencies: 2.0.5-1 → 2.0.6-1
  • ros-iron-ament-cmake-test: 2.0.5-1 → 2.0.6-1
  • ros-iron-ament-cmake-uncrustify: 0.14.3-1 → 0.14.4-1
  • ros-iron-ament-cmake-vendor-package: 2.0.5-1 → 2.0.6-1
  • ros-iron-ament-cmake-version: 2.0.5-1 → 2.0.6-1
  • ros-iron-ament-cmake-xmllint: 0.14.3-1 → 0.14.4-1
  • ros-iron-ament-copyright: 0.14.3-1 → 0.14.4-1
  • ros-iron-ament-cppcheck: 0.14.3-1 → 0.14.4-1
  • ros-iron-ament-cpplint: 0.14.3-1 → 0.14.4-1
  • ros-iron-ament-flake8: 0.14.3-1 → 0.14.4-1
  • ros-iron-ament-lint: 0.14.3-1 → 0.14.4-1
  • ros-iron-ament-lint-auto: 0.14.3-1 → 0.14.4-1
  • ros-iron-ament-lint-cmake: 0.14.3-1 → 0.14.4-1
  • ros-iron-ament-lint-common: 0.14.3-1 → 0.14.4-1
  • ros-iron-ament-mypy: 0.14.3-1 → 0.14.4-1
  • ros-iron-ament-pclint: 0.14.3-1 → 0.14.4-1
  • ros-iron-ament-pep257: 0.14.3-1 → 0.14.4-1
  • ros-iron-ament-pycodestyle: 0.14.3-1 → 0.14.4-1
  • ros-iron-ament-pyflakes: 0.14.3-1 → 0.14.4-1
  • ros-iron-ament-uncrustify: 0.14.3-1 → 0.14.4-1
  • ros-iron-ament-xmllint: 0.14.3-1 → 0.14.4-1
  • ros-iron-backward-ros: 1.0.2-5 → 1.0.5-1
  • ros-iron-backward-ros-dbgsym: 1.0.2-5 → 1.0.5-1
  • ros-iron-behaviortree-cpp: 4.6.1-1 → 4.6.2-1
  • ros-iron-behaviortree-cpp-dbgsym: 4.6.1-1 → 4.6.2-1
  • ros-iron-behaviortree-cpp-v3: 3.8.6-1 → 3.8.7-1
  • ros-iron-behaviortree-cpp-v3-dbgsym: 3.8.6-1 → 3.8.7-1
  • ros-iron-bicycle-steering-controller: 3.24.0-1 → 3.25.0-1
  • ros-iron-bicycle-steering-controller-dbgsym: 3.24.0-1 → 3.25.0-1
  • ros-iron-composition: 0.27.1-1 → 0.27.2-1
  • ros-iron-composition-dbgsym: 0.27.1-1 → 0.27.2-1
  • ros-iron-controller-interface: 3.25.0-1 → 3.26.0-1
  • ros-iron-controller-interface-dbgsym: 3.25.0-1 → 3.26.0-1
  • ros-iron-controller-manager: 3.25.0-1 → 3.26.0-1
  • ros-iron-controller-manager-dbgsym: 3.25.0-1 → 3.26.0-1
  • ros-iron-controller-manager-msgs: 3.25.0-1 → 3.26.0-1
  • ros-iron-controller-manager-msgs-dbgsym: 3.25.0-1 → 3.26.0-1
  • ros-iron-demo-nodes-cpp: 0.27.1-1 → 0.27.2-1
  • ros-iron-demo-nodes-cpp-dbgsym: 0.27.1-1 → 0.27.2-1
  • ros-iron-demo-nodes-cpp-native: 0.27.1-1 → 0.27.2-1
  • ros-iron-demo-nodes-cpp-native-dbgsym: 0.27.1-1 → 0.27.2-1
  • ros-iron-demo-nodes-py: 0.27.1-1 → 0.27.2-1
  • ros-iron-diagnostic-aggregator: 3.1.2-3 → 4.1.0-1
  • ros-iron-diagnostic-aggregator-dbgsym: 3.1.2-3 → 4.1.0-1
  • ros-iron-diagnostic-common-diagnostics: 3.1.2-3 → 4.1.0-1
  • ros-iron-diagnostic-updater: 3.1.2-3 → 4.1.0-1
  • ros-iron-diagnostic-updater-dbgsym: 3.1.2-3 → 4.1.0-1
  • ros-iron-diagnostics: 3.1.2-3 → 4.1.0-1
  • ros-iron-diff-drive-controller: 3.24.0-1 → 3.25.0-1
  • ros-iron-diff-drive-controller-dbgsym: 3.24.0-1 → 3.25.0-1
  • ros-iron-dummy-map-server: 0.27.1-1 → 0.27.2-1
  • ros-iron-dummy-map-server-dbgsym: 0.27.1-1 → 0.27.2-1
  • ros-iron-dummy-robot-bringup: 0.27.1-1 → 0.27.2-1
  • ros-iron-dummy-sensors: 0.27.1-1 → 0.27.2-1
  • ros-iron-dummy-sensors-dbgsym: 0.27.1-1 → 0.27.2-1
  • ros-iron-effort-controllers: 3.24.0-1 → 3.25.0-1
  • ros-iron-effort-controllers-dbgsym: 3.24.0-1 → 3.25.0-1
  • ros-iron-examples-rclcpp-async-client: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclcpp-async-client-dbgsym: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclcpp-cbg-executor: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclcpp-cbg-executor-dbgsym: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclcpp-minimal-action-client: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclcpp-minimal-action-client-dbgsym: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclcpp-minimal-action-server: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclcpp-minimal-action-server-dbgsym: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclcpp-minimal-client: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclcpp-minimal-client-dbgsym: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclcpp-minimal-composition: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclcpp-minimal-composition-dbgsym: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclcpp-minimal-publisher: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclcpp-minimal-publisher-dbgsym: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclcpp-minimal-service: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclcpp-minimal-service-dbgsym: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclcpp-minimal-subscriber: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclcpp-minimal-subscriber-dbgsym: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclcpp-minimal-timer: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclcpp-minimal-timer-dbgsym: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclcpp-multithreaded-executor: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclcpp-multithreaded-executor-dbgsym: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclcpp-wait-set: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclcpp-wait-set-dbgsym: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclpy-executors: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclpy-guard-conditions: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclpy-minimal-action-client: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclpy-minimal-action-server: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclpy-minimal-client: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclpy-minimal-publisher: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclpy-minimal-service: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclpy-minimal-subscriber: 0.18.0-2 → 0.18.1-1
  • ros-iron-examples-rclpy-pointcloud-publisher: 0.18.0-2 → 0.18.1-1
  • ros-iron-force-torque-sensor-broadcaster: 3.24.0-1 → 3.25.0-1
  • ros-iron-force-torque-sensor-broadcaster-dbgsym: 3.24.0-1 → 3.25.0-1
  • ros-iron-forward-command-controller: 3.24.0-1 → 3.25.0-1
  • ros-iron-forward-command-controller-dbgsym: 3.24.0-1 → 3.25.0-1
  • ros-iron-gazebo-ros2-control: 0.6.6-1 → 0.6.7-1
  • ros-iron-gazebo-ros2-control-dbgsym: 0.6.6-1 → 0.6.7-1
  • ros-iron-gazebo-ros2-control-demos: 0.6.6-1 → 0.6.7-1
  • ros-iron-gazebo-ros2-control-demos-dbgsym: 0.6.6-1 → 0.6.7-1
  • ros-iron-gripper-controllers: 3.24.0-1 → 3.25.0-1
  • ros-iron-gripper-controllers-dbgsym: 3.24.0-1 → 3.25.0-1
  • ros-iron-gz-ros2-control: 1.1.6-1 → 1.1.8-1
  • ros-iron-gz-ros2-control-dbgsym: 1.1.6-1 → 1.1.8-1
  • ros-iron-gz-ros2-control-demos: 1.1.6-1 → 1.1.8-1
  • ros-iron-gz-ros2-control-demos-dbgsym: 1.1.6-1 → 1.1.8-1
  • ros-iron-hardware-interface: 3.25.0-1 → 3.26.0-1
  • ros-iron-hardware-interface-dbgsym: 3.25.0-1 → 3.26.0-1
  • ros-iron-hardware-interface-testing: 3.25.0-1 → 3.26.0-1
  • ros-iron-hardware-interface-testing-dbgsym: 3.25.0-1 → 3.26.0-1
  • ros-iron-image-tools: 0.27.1-1 → 0.27.2-1
  • ros-iron-image-tools-dbgsym: 0.27.1-1 → 0.27.2-1
  • ros-iron-imu-sensor-broadcaster: 3.24.0-1 → 3.25.0-1
  • ros-iron-imu-sensor-broadcaster-dbgsym: 3.24.0-1 → 3.25.0-1
  • ros-iron-intra-process-demo: 0.27.1-1 → 0.27.2-1
  • ros-iron-intra-process-demo-dbgsym: 0.27.1-1 → 0.27.2-1
  • ros-iron-joint-limits: 3.25.0-1 → 3.26.0-1
  • ros-iron-joint-state-broadcaster: 3.24.0-1 → 3.25.0-1
  • ros-iron-joint-state-broadcaster-dbgsym: 3.24.0-1 → 3.25.0-1
  • ros-iron-joint-trajectory-controller: 3.24.0-1 → 3.25.0-1
  • ros-iron-joint-trajectory-controller-dbgsym: 3.24.0-1 → 3.25.0-1
  • ros-iron-launch-testing-examples: 0.18.0-2 → 0.18.1-1
  • ros-iron-libcurl-vendor: 3.2.2-3 → 3.2.3-1
  • ros-iron-lifecycle: 0.27.1-1 → 0.27.2-1
  • ros-iron-lifecycle-dbgsym: 0.27.1-1 → 0.27.2-1
  • ros-iron-lifecycle-py: 0.27.1-1 → 0.27.2-1
  • ros-iron-logging-demo: 0.27.1-1 → 0.27.2-1
  • ros-iron-logging-demo-dbgsym: 0.27.1-1 → 0.27.2-1
  • ros-iron-mcap-vendor: 0.22.6-1 → 0.22.7-1
  • ros-iron-mcap-vendor-dbgsym: 0.22.6-1 → 0.22.7-1
  • ros-iron-mp2p-icp: 1.5.0-1 → 1.5.1-1
  • ros-iron-mp2p-icp-dbgsym: 1.5.0-1 → 1.5.1-1
  • ros-iron-mrpt-generic-sensor: 0.2.0-1 → 0.2.1-1
  • ros-iron-mrpt-generic-sensor-dbgsym: 0.2.0-1 → 0.2.1-1
  • ros-iron-mrpt-sensor-bumblebee-stereo: 0.2.0-1 → 0.2.1-1
  • ros-iron-mrpt-sensor-bumblebee-stereo-dbgsym: 0.2.0-1 → 0.2.1-1
  • ros-iron-mrpt-sensor-imu-taobotics: 0.2.0-1 → 0.2.1-1
  • ros-iron-mrpt-sensor-imu-taobotics-dbgsym: 0.2.0-1 → 0.2.1-1
  • ros-iron-mrpt-sensorlib: 0.2.0-1 → 0.2.1-1
  • ros-iron-mrpt-sensors: 0.2.0-1 → 0.2.1-1
  • ros-iron-mrpt2: 2.13.2-1 → 2.13.3-1
  • ros-iron-mrpt2-dbgsym: 2.13.2-1 → 2.13.3-1
  • ros-iron-octomap-mapping: 2.0.0-4 → 2.3.0-1
  • ros-iron-octomap-ros: 0.4.3-3 → 0.4.4-1
  • ros-iron-octomap-ros-dbgsym: 0.4.3-3 → 0.4.4-1
  • ros-iron-octomap-rviz-plugins: 2.0.0-4 → 2.1.0-1
  • ros-iron-octomap-rviz-plugins-dbgsym: 2.0.0-4 → 2.1.0-1
  • ros-iron-octomap-server: 2.0.0-4 → 2.3.0-1
  • ros-iron-octomap-server-dbgsym: 2.0.0-4 → 2.3.0-1
  • ros-iron-pendulum-control: 0.27.1-1 → 0.27.2-1
  • ros-iron-pendulum-control-dbgsym: 0.27.1-1 → 0.27.2-1
  • ros-iron-pendulum-msgs: 0.27.1-1 → 0.27.2-1
  • ros-iron-pendulum-msgs-dbgsym: 0.27.1-1 → 0.27.2-1
  • ros-iron-position-controllers: 3.24.0-1 → 3.25.0-1
  • ros-iron-position-controllers-dbgsym: 3.24.0-1 → 3.25.0-1
  • ros-iron-quality-of-service-demo-cpp: 0.27.1-1 → 0.27.2-1
  • ros-iron-quality-of-service-demo-cpp-dbgsym: 0.27.1-1 → 0.27.2-1
  • ros-iron-quality-of-service-demo-py: 0.27.1-1 → 0.27.2-1
  • ros-iron-range-sensor-broadcaster: 3.24.0-1 → 3.25.0-1
  • ros-iron-range-sensor-broadcaster-dbgsym: 3.24.0-1 → 3.25.0-1
  • ros-iron-rcl: 6.0.5-1 → 6.0.6-1
  • ros-iron-rcl-action: 6.0.5-1 → 6.0.6-1
  • ros-iron-rcl-action-dbgsym: 6.0.5-1 → 6.0.6-1
  • ros-iron-rcl-dbgsym: 6.0.5-1 → 6.0.6-1
  • ros-iron-rcl-lifecycle: 6.0.5-1 → 6.0.6-1
  • ros-iron-rcl-lifecycle-dbgsym: 6.0.5-1 → 6.0.6-1
  • ros-iron-rcl-yaml-param-parser: 6.0.5-1 → 6.0.6-1
  • ros-iron-rcl-yaml-param-parser-dbgsym: 6.0.5-1 → 6.0.6-1
  • ros-iron-rclcpp: 21.0.6-1 → 21.0.7-1
  • ros-iron-rclcpp-action: 21.0.6-1 → 21.0.7-1
  • ros-iron-rclcpp-action-dbgsym: 21.0.6-1 → 21.0.7-1
  • ros-iron-rclcpp-components: 21.0.6-1 → 21.0.7-1
  • ros-iron-rclcpp-components-dbgsym: 21.0.6-1 → 21.0.7-1
  • ros-iron-rclcpp-dbgsym: 21.0.6-1 → 21.0.7-1
  • ros-iron-rclcpp-lifecycle: 21.0.6-1 → 21.0.7-1
  • ros-iron-rclcpp-lifecycle-dbgsym: 21.0.6-1 → 21.0.7-1
  • ros-iron-rclpy: 4.1.5-1 → 4.1.6-1
  • ros-iron-rcpputils: 2.6.3-1 → 2.6.4-1
  • ros-iron-rcpputils-dbgsym: 2.6.3-1 → 2.6.4-1
  • ros-iron-resource-retriever: 3.2.2-3 → 3.2.3-1
  • ros-iron-resource-retriever-dbgsym: 3.2.2-3 → 3.2.3-1
  • ros-iron-rmw-fastrtps-cpp: 7.1.3-1 → 7.1.4-1
  • ros-iron-rmw-fastrtps-cpp-dbgsym: 7.1.3-1 → 7.1.4-1
  • ros-iron-rmw-fastrtps-dynamic-cpp: 7.1.3-1 → 7.1.4-1
  • ros-iron-rmw-fastrtps-dynamic-cpp-dbgsym: 7.1.3-1 → 7.1.4-1
  • ros-iron-rmw-fastrtps-shared-cpp: 7.1.3-1 → 7.1.4-1
  • ros-iron-rmw-fastrtps-shared-cpp-dbgsym: 7.1.3-1 → 7.1.4-1
  • ros-iron-rmw-implementation: 2.12.0-2 → 2.12.1-1
  • ros-iron-rmw-implementation-dbgsym: 2.12.0-2 → 2.12.1-1
  • ros-iron-ros2-control: 3.25.0-1 → 3.26.0-1
  • ros-iron-ros2-control-test-assets: 3.25.0-1 → 3.26.0-1
  • ros-iron-ros2-controllers: 3.24.0-1 → 3.25.0-1
  • ros-iron-ros2-controllers-test-nodes: 3.24.0-1 → 3.25.0-1
  • ros-iron-ros2action: 0.25.6-1 → 0.25.7-1
  • ros-iron-ros2bag: 0.22.6-1 → 0.22.7-1
  • ros-iron-ros2cli: 0.25.6-1 → 0.25.7-1
  • ros-iron-ros2cli-test-interfaces: 0.25.6-1 → 0.25.7-1
  • ros-iron-ros2cli-test-interfaces-dbgsym: 0.25.6-1 → 0.25.7-1
  • ros-iron-ros2component: 0.25.6-1 → 0.25.7-1
  • ros-iron-ros2controlcli: 3.25.0-1 → 3.26.0-1
  • ros-iron-ros2doctor: 0.25.6-1 → 0.25.7-1
  • ros-iron-ros2interface: 0.25.6-1 → 0.25.7-1
  • ros-iron-ros2lifecycle: 0.25.6-1 → 0.25.7-1
  • ros-iron-ros2lifecycle-test-fixtures: 0.25.6-1 → 0.25.7-1
  • ros-iron-ros2lifecycle-test-fixtures-dbgsym: 0.25.6-1 → 0.25.7-1
  • ros-iron-ros2multicast: 0.25.6-1 → 0.25.7-1
  • ros-iron-ros2node: 0.25.6-1 → 0.25.7-1
  • ros-iron-ros2param: 0.25.6-1 → 0.25.7-1
  • ros-iron-ros2pkg: 0.25.6-1 → 0.25.7-1
  • ros-iron-ros2run: 0.25.6-1 → 0.25.7-1
  • ros-iron-ros2service: 0.25.6-1 → 0.25.7-1
  • ros-iron-ros2topic: 0.25.6-1 → 0.25.7-1
  • ros-iron-ros2trace: 6.3.1-1 → 6.3.2-1
  • ros-iron-rosbag2: 0.22.6-1 → 0.22.7-1
  • ros-iron-rosbag2-compression: 0.22.6-1 → 0.22.7-1
  • ros-iron-rosbag2-compression-dbgsym: 0.22.6-1 → 0.22.7-1
  • ros-iron-rosbag2-compression-zstd: 0.22.6-1 → 0.22.7-1
  • ros-iron-rosbag2-compression-zstd-dbgsym: 0.22.6-1 → 0.22.7-1
  • ros-iron-rosbag2-cpp: 0.22.6-1 → 0.22.7-1
  • ros-iron-rosbag2-cpp-dbgsym: 0.22.6-1 → 0.22.7-1
  • ros-iron-rosbag2-examples-cpp: 0.22.6-1 → 0.22.7-1
  • ros-iron-rosbag2-examples-cpp-dbgsym: 0.22.6-1 → 0.22.7-1
  • ros-iron-rosbag2-examples-py: 0.22.6-1 → 0.22.7-1
  • ros-iron-rosbag2-interfaces: 0.22.6-1 → 0.22.7-1
  • ros-iron-rosbag2-interfaces-dbgsym: 0.22.6-1 → 0.22.7-1
  • ros-iron-rosbag2-performance-benchmarking: 0.22.6-1 → 0.22.7-1
  • ros-iron-rosbag2-performance-benchmarking-msgs: 0.22.6-1 → 0.22.7-1
  • ros-iron-rosbag2-py: 0.22.6-1 → 0.22.7-1
  • ros-iron-rosbag2-storage: 0.22.6-1 → 0.22.7-1
  • ros-iron-rosbag2-storage-dbgsym: 0.22.6-1 → 0.22.7-1
  • ros-iron-rosbag2-storage-default-plugins: 0.22.6-1 → 0.22.7-1
  • ros-iron-rosbag2-storage-mcap: 0.22.6-1 → 0.22.7-1
  • ros-iron-rosbag2-storage-mcap-dbgsym: 0.22.6-1 → 0.22.7-1
  • ros-iron-rosbag2-storage-sqlite3: 0.22.6-1 → 0.22.7-1
  • ros-iron-rosbag2-storage-sqlite3-dbgsym: 0.22.6-1 → 0.22.7-1
  • ros-iron-rosbag2-test-common: 0.22.6-1 → 0.22.7-1
  • ros-iron-rosbag2-test-msgdefs: 0.22.6-1 → 0.22.7-1
  • ros-iron-rosbag2-test-msgdefs-dbgsym: 0.22.6-1 → 0.22.7-1
  • ros-iron-rosbag2-tests: 0.22.6-1 → 0.22.7-1
  • ros-iron-rosbag2-transport: 0.22.6-1 → 0.22.7-1
  • ros-iron-rosbag2-transport-dbgsym: 0.22.6-1 → 0.22.7-1
  • ros-iron-rqt-bag: 1.3.4-1 → 1.3.5-1
  • ros-iron-rqt-bag-plugins: 1.3.4-1 → 1.3.5-1
  • ros-iron-rqt-controller-manager: 3.25.0-1 → 3.26.0-1
  • ros-iron-rqt-graph: 1.4.2-1 → 1.4.3-1
  • ros-iron-rqt-joint-trajectory-controller: 3.24.0-1 → 3.25.0-1
  • ros-iron-rtabmap: 0.21.4-1 → 0.21.5-1
  • ros-iron-rtabmap-conversions: 0.21.4-2 → 0.21.5-1
  • ros-iron-rtabmap-conversions-dbgsym: 0.21.4-2 → 0.21.5-1
  • ros-iron-rtabmap-dbgsym: 0.21.4-1 → 0.21.5-1
  • ros-iron-rtabmap-demos: 0.21.4-2 → 0.21.5-1
  • ros-iron-rtabmap-examples: 0.21.4-2 → 0.21.5-1
  • ros-iron-rtabmap-launch: 0.21.4-2 → 0.21.5-1
  • ros-iron-rtabmap-msgs: 0.21.4-2 → 0.21.5-1
  • ros-iron-rtabmap-msgs-dbgsym: 0.21.4-2 → 0.21.5-1
  • ros-iron-rtabmap-odom: 0.21.4-2 → 0.21.5-1
  • ros-iron-rtabmap-odom-dbgsym: 0.21.4-2 → 0.21.5-1
  • ros-iron-rtabmap-python: 0.21.4-2 → 0.21.5-1
  • ros-iron-rtabmap-ros: 0.21.4-2 → 0.21.5-1
  • ros-iron-rtabmap-rviz-plugins: 0.21.4-2 → 0.21.5-1
  • ros-iron-rtabmap-rviz-plugins-dbgsym: 0.21.4-2 → 0.21.5-1
  • ros-iron-rtabmap-slam: 0.21.4-2 → 0.21.5-1
  • ros-iron-rtabmap-slam-dbgsym: 0.21.4-2 → 0.21.5-1
  • ros-iron-rtabmap-sync: 0.21.4-2 → 0.21.5-1
  • ros-iron-rtabmap-sync-dbgsym: 0.21.4-2 → 0.21.5-1
  • ros-iron-rtabmap-util: 0.21.4-2 → 0.21.5-1
  • ros-iron-rtabmap-util-dbgsym: 0.21.4-2 → 0.21.5-1
  • ros-iron-rtabmap-viz: 0.21.4-2 → 0.21.5-1
  • ros-iron-rtabmap-viz-dbgsym: 0.21.4-2 → 0.21.5-1
  • ros-iron-rviz-assimp-vendor: 12.4.7-1 → 12.4.8-1
  • ros-iron-rviz-common: 12.4.7-1 → 12.4.8-1
  • ros-iron-rviz-common-dbgsym: 12.4.7-1 → 12.4.8-1
  • ros-iron-rviz-default-plugins: 12.4.7-1 → 12.4.8-1
  • ros-iron-rviz-default-plugins-dbgsym: 12.4.7-1 → 12.4.8-1
  • ros-iron-rviz-ogre-vendor: 12.4.7-1 → 12.4.8-1
  • ros-iron-rviz-ogre-vendor-dbgsym: 12.4.7-1 → 12.4.8-1
  • ros-iron-rviz-rendering: 12.4.7-1 → 12.4.8-1
  • ros-iron-rviz-rendering-dbgsym: 12.4.7-1 → 12.4.8-1
  • ros-iron-rviz-rendering-tests: 12.4.7-1 → 12.4.8-1
  • ros-iron-rviz-visual-testing-framework: 12.4.7-1 → 12.4.8-1
  • ros-iron-rviz2: 12.4.7-1 → 12.4.8-1
  • ros-iron-rviz2-dbgsym: 12.4.7-1 → 12.4.8-1
  • ros-iron-self-test: 3.1.2-3 → 4.1.0-1
  • ros-iron-self-test-dbgsym: 3.1.2-3 → 4.1.0-1
  • ros-iron-shared-queues-vendor: 0.22.6-1 → 0.22.7-1
  • ros-iron-simple-launch: 1.10.0-1 → 1.10.1-1
  • ros-iron-sqlite3-vendor: 0.22.6-1 → 0.22.7-1
  • ros-iron-steering-controllers-library: 3.24.0-1 → 3.25.0-1
  • ros-iron-steering-controllers-library-dbgsym: 3.24.0-1 → 3.25.0-1
  • ros-iron-topic-monitor: 0.27.1-1 → 0.27.2-1
  • ros-iron-topic-statistics-demo: 0.27.1-1 → 0.27.2-1
  • ros-iron-topic-statistics-demo-dbgsym: 0.27.1-1 → 0.27.2-1
  • ros-iron-tracetools: 6.3.1-1 → 6.3.2-1
  • ros-iron-tracetools-dbgsym: 6.3.1-1 → 6.3.2-1
  • ros-iron-tracetools-launch: 6.3.1-1 → 6.3.2-1
  • ros-iron-tracetools-read: 6.3.1-1 → 6.3.2-1
  • ros-iron-tracetools-test: 6.3.1-1 → 6.3.2-1
  • ros-iron-tracetools-trace: 6.3.1-1 → 6.3.2-1
  • ros-iron-transmission-interface: 3.25.0-1 → 3.26.0-1
  • ros-iron-transmission-interface-dbgsym: 3.25.0-1 → 3.26.0-1
  • ros-iron-tricycle-controller: 3.24.0-1 → 3.25.0-1
  • ros-iron-tricycle-controller-dbgsym: 3.24.0-1 → 3.25.0-1
  • ros-iron-tricycle-steering-controller: 3.24.0-1 → 3.25.0-1
  • ros-iron-tricycle-steering-controller-dbgsym: 3.24.0-1 → 3.25.0-1
  • ros-iron-udp-msgs: 0.0.3-6 → 0.0.5-1
  • ros-iron-udp-msgs-dbgsym: 0.0.3-6 → 0.0.5-1
  • ros-iron-ur: 2.3.8-1 → 2.3.9-1
  • ros-iron-ur-calibration: 2.3.8-1 → 2.3.9-1
  • ros-iron-ur-calibration-dbgsym: 2.3.8-1 → 2.3.9-1
  • ros-iron-ur-controllers: 2.3.8-1 → 2.3.9-1
  • ros-iron-ur-controllers-dbgsym: 2.3.8-1 → 2.3.9-1
  • ros-iron-ur-dashboard-msgs: 2.3.8-1 → 2.3.9-1
  • ros-iron-ur-dashboard-msgs-dbgsym: 2.3.8-1 → 2.3.9-1
  • ros-iron-ur-moveit-config: 2.3.8-1 → 2.3.9-1
  • ros-iron-ur-robot-driver: 2.3.8-1 → 2.3.9-1
  • ros-iron-ur-robot-driver-dbgsym: 2.3.8-1 → 2.3.9-1
  • ros-iron-velocity-controllers: 3.24.0-1 → 3.25.0-1
  • ros-iron-velocity-controllers-dbgsym: 3.24.0-1 → 3.25.0-1
  • ros-iron-zstd-vendor: 0.22.6-1 → 0.22.7-1

Removed Packages [2]:

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:

  • Aditya Pande
  • Alejandro Hernandez
  • Alejandro Hernandez Cordero
  • Alejandro Hernández
  • Armin Hornung
  • Audrow Nash
  • Austin Hendrix
  • Bence Magyar
  • Bernd Pfrommer
  • Brandon Ong
  • Christophe Bedard
  • Davide Faconti
  • Denis Stogl
  • Denis Štogl
  • Evan Flynn
  • Felix Exner
  • Foxglove
  • Geoffrey Biggs
  • Ivan Paunovic
  • Jose-Luis Blanco-Claraco
  • José Luis Blanco-Claraco
  • Mathieu Labbe
  • Michael Jeronimo
  • Michael Orlov
  • Olivier Kermorgant
  • ROS Tooling Working Group
  • Shane Loretz
  • Victor López
  • William Woodall
  • Wolfgang Merkt
  • adminpc
  • geoff

1 post - 1 participant

Read full topic

by Yadunund on July 13, 2024 05:58 PM

July 12, 2024
ROS News for the Week of July 8th, 2024

ROS News for the Week of July 8th, 2024


:tada: The full ROSCon talk schedule has been published! :tada:

We also just announced that we’ll be offering tours of the Teradyne / Universal Robotics / MiR offices during ROSCon.



It seems like everyone is building open-hardware robot arms right now!
There’s the MikataArm (above), a new open source arm from Source Robotics, and I recently came across this open source hardware gripper. Some of these projects already have downstream users like this imitation learning project that uses and open-hardware arm and an iPhone.

Why build just an arm when you can build a whole humanoid? Personally, I’m a big fan of the work of @lethic1 on Twitter and their new Red Rabbit Robotics project

AD_4nXeuPnaYknU6GOMwFfJCmm0Ix2d0ITFy9EULPHrJUZXDfZxtKgsgyned6t9EeDMH6V_ihkrdLE2k4sGE-_mUBZ901XmAys2U9sMmX78-mdgaR0SUGx4bUMGKHbIukPbs62Rx6LF5udYhQzUG-JKVSYH6vhFY

Check out this fantastic thread of student summer thesis projects using ROS. If you know a student please encourage them to contribute!


home

The team over at the Intelligent Robotics Lab at Universidad Rey Juan Carlos
have released a ROS 2 Humble package for the Unitree Go 2 Quadruped.

Events

News

ROS

Got a Minute?

:open_book: Consider sending us a pull request to improve the ROS documentation.

2 posts - 2 participants

Read full topic

by Katherine_Scott on July 12, 2024 08:55 PM

July 10, 2024
Launch of Open-RMF Project Management Committee open sessions

I’m pleased to announce the launch of the Open-RMF Project Management Committee (PMC) open sessions. These are sessions where the Open-RMF PMC will discuss matters pertaining to the upkeep, development, and direction of the project, with an opportunity for the public to observe as well as potentially share feedback with the committee as the agenda permits. The sessions will be run according to the project charter designated by the OSRA.

Sessions will take place at a two-week cadence with the first session at 2024-07-16T01:00:00Z UTC.

Unfortunately the timing is not favorable to folks in a European timezone, but all the current PMC members are in Asia or California. Folks in Europe who are interested in interoperability are encouraged to join the OSRF Interoperability Special Interest Group which takes place during a Euro-friendly timeslot.

1 post - 1 participant

Read full topic

by grey on July 10, 2024 02:23 PM

July 09, 2024
Exploring ROS2 Basics: Training at Mitsubishi Electric Nagoya Works

Recently, our consortium conducted a comprehensive ROS2 Basics training session at the Mitsubishi Electric Nagoya Works Factory Automation Centre in Japan, from May 14th to 17th . This training brought together our consortium members from IHI, Mitsubishi Electric, Pepperl+Fuchs, and Panasonic,as well as the training team from RIC-AP (Glenn Tan, Adriel Ho, Sheila Suppiah), all eager to delve into the topics of ROS2 Basics.

The sessions covered essential topics including the publisher/subscriber model, service client model, launch files, and parameter tuning in ROS2. A significant focus was also placed on comparing ROS1 and ROS2, highlighting the advancements and improvements in the latter.

To ensure a solid foundation, the course began with an introduction to the Linux operating system and command line interface, which is essential for ROS2 development. The engagement from our consortium members was great, with active participation and thoughtful questions that contributed to a vibrant learning environment. Their enthusiasm underscores a shared commitment to advancing robotics through ROS based technologies.

As part of their final assessment, students applied their newfound knowledge in a practical application focusing on the usage of a TurtleBot3 Burger. This hands-on approach allowed them to demonstrate their understanding of ROS2 concepts in a real-world context, further solidifying their learning.

The feedback from participants was generally positive, with many expressing their interest to delve deeper into more advanced ROS topics in the future. We also had the opportunity to further enrich the learning experience, as we concluded the training with an insightful factory tour of Mitsubishi Electric.

This training session wouldn't have been possible without the continuous support and dedication of our consortium members. Their unwavering interest in ROS2 is paving the way for future advancements in robotics, demonstrating the power of collaboration in driving innovation forward.

We look forward to our next run of trainings in Japan! Do drop a comment or contact us if you are interested to participate in subsequent runs. #goROS

by Sheila Devi on July 09, 2024 01:52 PM

July 08, 2024
New Packages for Noetic 2024-07-08

We’re happy to announce 0 new packages and 39 updates are now available in ROS Noetic. This sync was tagged as noetic/2024-07-08.

Thank you to every maintainer and contributor who made these updates available!

Package Updates for noetic

Added Packages [0]:

Updated Packages [39]:

  • ros-noetic-beluga: 2.0.1-1 → 2.0.2-1
  • ros-noetic-beluga-amcl: 2.0.1-1 → 2.0.2-1
  • ros-noetic-beluga-amcl-dbgsym: 2.0.1-1 → 2.0.2-1
  • ros-noetic-beluga-ros: 2.0.1-1 → 2.0.2-1
  • ros-noetic-leo-bringup: 2.4.0-1 → 2.4.1-2
  • ros-noetic-leo-fw: 2.4.0-1 → 2.4.1-2
  • ros-noetic-leo-fw-dbgsym: 2.4.0-1 → 2.4.1-2
  • ros-noetic-leo-robot: 2.4.0-1 → 2.4.1-2
  • ros-noetic-mrpt2: 2.13.1-1 → 2.13.3-1
  • ros-noetic-mrpt2-dbgsym: 2.13.1-1 → 2.13.3-1
  • ros-noetic-rqt-pr2-dashboard: 0.4.0-1 → 0.4.1-1
  • ros-noetic-rtabmap: 0.21.4-1 → 0.21.5-1
  • ros-noetic-rtabmap-conversions: 0.21.4-1 → 0.21.5-1
  • ros-noetic-rtabmap-conversions-dbgsym: 0.21.4-1 → 0.21.5-1
  • ros-noetic-rtabmap-costmap-plugins: 0.21.4-1 → 0.21.5-1
  • ros-noetic-rtabmap-costmap-plugins-dbgsym: 0.21.4-1 → 0.21.5-1
  • ros-noetic-rtabmap-dbgsym: 0.21.4-1 → 0.21.5-1
  • ros-noetic-rtabmap-demos: 0.21.4-1 → 0.21.5-1
  • ros-noetic-rtabmap-demos-dbgsym: 0.21.4-1 → 0.21.5-1
  • ros-noetic-rtabmap-examples: 0.21.4-1 → 0.21.5-1
  • ros-noetic-rtabmap-examples-dbgsym: 0.21.4-1 → 0.21.5-1
  • ros-noetic-rtabmap-launch: 0.21.4-1 → 0.21.5-1
  • ros-noetic-rtabmap-legacy: 0.21.4-1 → 0.21.5-1
  • ros-noetic-rtabmap-legacy-dbgsym: 0.21.4-1 → 0.21.5-1
  • ros-noetic-rtabmap-msgs: 0.21.4-1 → 0.21.5-1
  • ros-noetic-rtabmap-odom: 0.21.4-1 → 0.21.5-1
  • ros-noetic-rtabmap-odom-dbgsym: 0.21.4-1 → 0.21.5-1
  • ros-noetic-rtabmap-python: 0.21.4-1 → 0.21.5-1
  • ros-noetic-rtabmap-ros: 0.21.4-1 → 0.21.5-1
  • ros-noetic-rtabmap-rviz-plugins: 0.21.4-1 → 0.21.5-1
  • ros-noetic-rtabmap-rviz-plugins-dbgsym: 0.21.4-1 → 0.21.5-1
  • ros-noetic-rtabmap-slam: 0.21.4-1 → 0.21.5-1
  • ros-noetic-rtabmap-slam-dbgsym: 0.21.4-1 → 0.21.5-1
  • ros-noetic-rtabmap-sync: 0.21.4-1 → 0.21.5-1
  • ros-noetic-rtabmap-sync-dbgsym: 0.21.4-1 → 0.21.5-1
  • ros-noetic-rtabmap-util: 0.21.4-1 → 0.21.5-1
  • ros-noetic-rtabmap-util-dbgsym: 0.21.4-1 → 0.21.5-1
  • ros-noetic-rtabmap-viz: 0.21.4-1 → 0.21.5-1
  • ros-noetic-rtabmap-viz-dbgsym: 0.21.4-1 → 0.21.5-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:

  • Fictionlab
  • Gerardo Puga
  • Jose-Luis Blanco-Claraco
  • Mathieu Labbe
  • Sammy Pfeiffer

1 post - 1 participant

Read full topic

by sloretz on July 08, 2024 11:15 PM

Announcing ros-tool: The easiest way to create web UIs for ROS

Our new, free ros-tool capability makes it trivial to interact with ROS from the web. It provides a React API for subscribing and publish to topics and for placing service calls. It works with both ROS 1 and 2, and unlike rosbridge, it caches all data in the cloud, which means your UIs will work even when your robot is offline (just showing the latest data). Since all data is synced via the cloud, it is also much easier and more efficient to aggregate data from multiple robots, e.g., for showing your fleet on a map.

Example

Here is an example of how to use it on the web:

import { CapabilityContext, CapabilityContextProvider } from '@transitive-sdk/utils-web'

const MyROSComponent = () => {
  // import the API exposed by the ros-tool capability
  const { ready, subscribe, deviceData, publish, call } = useContext(CapabilityContext)

  useEffect(() => {
      if (ready) {
        // subscribe to a ROS 1 topic on the robot
        subscribe(1, '/amcl_pose');
      }
    }, [ready, subscribe])

  // get the pose from the reactively updating device data
  const pose = deviceData?.ros[1].messages?.amcl_pose?.pose.pose;
  if (!pose) return <div>Connecting..</div>;

  // Show pose x and y on page as text:
  return <div>
      x: {pose.position.x},
      y: {pose.position.y}
    </div>
}

const MyPage = () => <CapabilityContextProvider jwt={jwt}>
    <MyROSComponent />
  <CapabilityContextProvider>
>

Getting Started

The easiest way to get started with this is to use our hosted solution on transitiverobotics.com where you can create a (free) account, add your robots, and install the ros-tool capability. Then you can use the playground UI to try it out without writing any code. The playground UI shows you the list of topics on the robot and let’s you subscribe to them. For publishing messages and placing service calls it fetches the message/service schema and uses it to pre-populate an editor with a template where you can just edit the values and send it off.

And yes, Transitive is open-source, so if you prefer to self-host the service, you can.

Demo and Details

Watch the demo here.

ros-tool (Transitive Robotics)

6 posts - 4 participants

Read full topic

by chfritz on July 08, 2024 06:57 PM

July 05, 2024
New packages for Jazzy Jalisco 2024-07-05

Package Updates for jazzy

Note that package counts include dbgsym packages which have been filtered out from the list below

Added Packages [123]:

  • ros-jazzy-autoware-common-msgs: 1.1.0-1
  • ros-jazzy-autoware-control-msgs: 1.1.0-1
  • ros-jazzy-autoware-localization-msgs: 1.1.0-1
  • ros-jazzy-autoware-map-msgs: 1.1.0-1
  • ros-jazzy-autoware-perception-msgs: 1.1.0-1
  • ros-jazzy-autoware-planning-msgs: 1.1.0-1
  • ros-jazzy-autoware-sensing-msgs: 1.1.0-1
  • ros-jazzy-autoware-system-msgs: 1.1.0-1
  • ros-jazzy-autoware-vehicle-msgs: 1.1.0-1
  • ros-jazzy-bondpy: 4.1.0-1
  • ros-jazzy-costmap-queue: 1.3.1-1
  • ros-jazzy-dwb-core: 1.3.1-1
  • ros-jazzy-dwb-critics: 1.3.1-1
  • ros-jazzy-dwb-msgs: 1.3.1-1
  • ros-jazzy-dwb-plugins: 1.3.1-1
  • ros-jazzy-librealsense2: 2.55.1-1
  • ros-jazzy-mola-navstate-fg: 1.0.6-1
  • ros-jazzy-moveit: 2.10.0-1
  • ros-jazzy-moveit-ros: 2.10.0-1
  • ros-jazzy-moveit-ros-benchmarks: 2.10.0-1
  • ros-jazzy-moveit-ros-tests: 2.10.0-1
  • ros-jazzy-nav-2d-msgs: 1.3.1-1
  • ros-jazzy-nav-2d-utils: 1.3.1-1
  • ros-jazzy-nav2-amcl: 1.3.1-1
  • ros-jazzy-nav2-behavior-tree: 1.3.1-1
  • ros-jazzy-nav2-behaviors: 1.3.1-1
  • ros-jazzy-nav2-bringup: 1.3.1-1
  • ros-jazzy-nav2-bt-navigator: 1.3.1-1
  • ros-jazzy-nav2-collision-monitor: 1.3.1-1
  • ros-jazzy-nav2-common: 1.3.1-1
  • ros-jazzy-nav2-constrained-smoother: 1.3.1-1
  • ros-jazzy-nav2-controller: 1.3.1-1
  • ros-jazzy-nav2-core: 1.3.1-1
  • ros-jazzy-nav2-costmap-2d: 1.3.1-1
  • ros-jazzy-nav2-dwb-controller: 1.3.1-1
  • ros-jazzy-nav2-graceful-controller: 1.3.1-1
  • ros-jazzy-nav2-lifecycle-manager: 1.3.1-1
  • ros-jazzy-nav2-map-server: 1.3.1-1
  • ros-jazzy-nav2-mppi-controller: 1.3.1-1
  • ros-jazzy-nav2-msgs: 1.3.1-1
  • ros-jazzy-nav2-navfn-planner: 1.3.1-1
  • ros-jazzy-nav2-planner: 1.3.1-1
  • ros-jazzy-nav2-regulated-pure-pursuit-controller: 1.3.1-1
  • ros-jazzy-nav2-rotation-shim-controller: 1.3.1-1
  • ros-jazzy-nav2-rviz-plugins: 1.3.1-1
  • ros-jazzy-nav2-simple-commander: 1.3.1-1
  • ros-jazzy-nav2-smac-planner: 1.3.1-1
  • ros-jazzy-nav2-smoother: 1.3.1-1
  • ros-jazzy-nav2-system-tests: 1.3.1-1
  • ros-jazzy-nav2-theta-star-planner: 1.3.1-1
  • ros-jazzy-nav2-util: 1.3.1-1
  • ros-jazzy-nav2-velocity-smoother: 1.3.1-1
  • ros-jazzy-nav2-voxel-grid: 1.3.1-1
  • ros-jazzy-nav2-waypoint-follower: 1.3.1-1
  • ros-jazzy-navigation2: 1.3.1-1
  • ros-jazzy-opennav-docking: 1.3.1-1
  • ros-jazzy-opennav-docking-bt: 1.3.1-1
  • ros-jazzy-opennav-docking-core: 1.3.1-1
  • ros-jazzy-realsense2-camera: 4.55.1-3
  • ros-jazzy-realsense2-camera-msgs: 4.55.1-3
  • ros-jazzy-realsense2-description: 4.55.1-3
  • ros-jazzy-rmf-building-map-tools: 1.9.1-1
  • ros-jazzy-rmf-dev: 0.1.0-1
  • ros-jazzy-rmf-traffic-editor: 1.9.1-1
  • ros-jazzy-rmf-traffic-editor-assets: 1.9.1-1
  • ros-jazzy-rmf-traffic-editor-test-maps: 1.9.1-1
  • ros-jazzy-slam-toolbox: 2.8.1-2
  • ros-jazzy-spinnaker-camera-driver: 2.0.20-1
  • ros-jazzy-spinnaker-synchronized-camera-driver: 2.0.20-1
  • ros-jazzy-steering-functions: 0.3.0-1

Updated Packages [440]:

  • ros-jazzy-action-tutorials-cpp: 0.33.3-1 → 0.33.4-1
  • ros-jazzy-action-tutorials-interfaces: 0.33.3-1 → 0.33.4-1
  • ros-jazzy-action-tutorials-py: 0.33.3-1 → 0.33.4-1
  • ros-jazzy-ament-clang-format: 0.17.0-2 → 0.17.1-1
  • ros-jazzy-ament-clang-tidy: 0.17.0-2 → 0.17.1-1
  • ros-jazzy-ament-cmake: 2.5.0-2 → 2.5.2-1
  • ros-jazzy-ament-cmake-auto: 2.5.0-2 → 2.5.2-1
  • ros-jazzy-ament-cmake-catch2: 1.4.0-3 → 1.4.1-1
  • ros-jazzy-ament-cmake-clang-format: 0.17.0-2 → 0.17.1-1
  • ros-jazzy-ament-cmake-clang-tidy: 0.17.0-2 → 0.17.1-1
  • ros-jazzy-ament-cmake-copyright: 0.17.0-2 → 0.17.1-1
  • ros-jazzy-ament-cmake-core: 2.5.0-2 → 2.5.2-1
  • ros-jazzy-ament-cmake-cppcheck: 0.17.0-2 → 0.17.1-1
  • ros-jazzy-ament-cmake-cpplint: 0.17.0-2 → 0.17.1-1
  • ros-jazzy-ament-cmake-export-definitions: 2.5.0-2 → 2.5.2-1
  • ros-jazzy-ament-cmake-export-dependencies: 2.5.0-2 → 2.5.2-1
  • ros-jazzy-ament-cmake-export-include-directories: 2.5.0-2 → 2.5.2-1
  • ros-jazzy-ament-cmake-export-interfaces: 2.5.0-2 → 2.5.2-1
  • ros-jazzy-ament-cmake-export-libraries: 2.5.0-2 → 2.5.2-1
  • ros-jazzy-ament-cmake-export-link-flags: 2.5.0-2 → 2.5.2-1
  • ros-jazzy-ament-cmake-export-targets: 2.5.0-2 → 2.5.2-1
  • ros-jazzy-ament-cmake-flake8: 0.17.0-2 → 0.17.1-1
  • ros-jazzy-ament-cmake-gen-version-h: 2.5.0-2 → 2.5.2-1
  • ros-jazzy-ament-cmake-gmock: 2.5.0-2 → 2.5.2-1
  • ros-jazzy-ament-cmake-google-benchmark: 2.5.0-2 → 2.5.2-1
  • ros-jazzy-ament-cmake-gtest: 2.5.0-2 → 2.5.2-1
  • ros-jazzy-ament-cmake-include-directories: 2.5.0-2 → 2.5.2-1
  • ros-jazzy-ament-cmake-libraries: 2.5.0-2 → 2.5.2-1
  • ros-jazzy-ament-cmake-lint-cmake: 0.17.0-2 → 0.17.1-1
  • ros-jazzy-ament-cmake-mypy: 0.17.0-2 → 0.17.1-1
  • ros-jazzy-ament-cmake-pclint: 0.17.0-2 → 0.17.1-1
  • ros-jazzy-ament-cmake-pep257: 0.17.0-2 → 0.17.1-1
  • ros-jazzy-ament-cmake-pycodestyle: 0.17.0-2 → 0.17.1-1
  • ros-jazzy-ament-cmake-pyflakes: 0.17.0-2 → 0.17.1-1
  • ros-jazzy-ament-cmake-pytest: 2.5.0-2 → 2.5.2-1
  • ros-jazzy-ament-cmake-python: 2.5.0-2 → 2.5.2-1
  • ros-jazzy-ament-cmake-target-dependencies: 2.5.0-2 → 2.5.2-1
  • ros-jazzy-ament-cmake-test: 2.5.0-2 → 2.5.2-1
  • ros-jazzy-ament-cmake-uncrustify: 0.17.0-2 → 0.17.1-1
  • ros-jazzy-ament-cmake-vendor-package: 2.5.0-2 → 2.5.2-1
  • ros-jazzy-ament-cmake-version: 2.5.0-2 → 2.5.2-1
  • ros-jazzy-ament-cmake-xmllint: 0.17.0-2 → 0.17.1-1
  • ros-jazzy-ament-copyright: 0.17.0-2 → 0.17.1-1
  • ros-jazzy-ament-cppcheck: 0.17.0-2 → 0.17.1-1
  • ros-jazzy-ament-cpplint: 0.17.0-2 → 0.17.1-1
  • ros-jazzy-ament-flake8: 0.17.0-2 → 0.17.1-1
  • ros-jazzy-ament-lint: 0.17.0-2 → 0.17.1-1
  • ros-jazzy-ament-lint-auto: 0.17.0-2 → 0.17.1-1
  • ros-jazzy-ament-lint-cmake: 0.17.0-2 → 0.17.1-1
  • ros-jazzy-ament-lint-common: 0.17.0-2 → 0.17.1-1
  • ros-jazzy-ament-mypy: 0.17.0-2 → 0.17.1-1
  • ros-jazzy-ament-pclint: 0.17.0-2 → 0.17.1-1
  • ros-jazzy-ament-pep257: 0.17.0-2 → 0.17.1-1
  • ros-jazzy-ament-pycodestyle: 0.17.0-2 → 0.17.1-1
  • ros-jazzy-ament-pyflakes: 0.17.0-2 → 0.17.1-1
  • ros-jazzy-ament-uncrustify: 0.17.0-2 → 0.17.1-1
  • ros-jazzy-ament-xmllint: 0.17.0-2 → 0.17.1-1
  • ros-jazzy-beluga: 2.0.1-1 → 2.0.2-1
  • ros-jazzy-beluga-amcl: 2.0.1-1 → 2.0.2-1
  • ros-jazzy-beluga-ros: 2.0.1-1 → 2.0.2-1
  • ros-jazzy-bond: 4.0.0-5 → 4.1.0-1
  • ros-jazzy-bond-core: 4.0.0-5 → 4.1.0-1
  • ros-jazzy-bondcpp: 4.0.0-5 → 4.1.0-1
  • ros-jazzy-camera-calibration-parsers: 5.1.3-1 → 5.1.4-1
  • ros-jazzy-camera-info-manager: 5.1.3-1 → 5.1.4-1
  • ros-jazzy-chomp-motion-planner: 2.9.0-1 → 2.10.0-1
  • ros-jazzy-composition: 0.33.3-1 → 0.33.4-1
  • ros-jazzy-cv-bridge: 4.0.0-2 → 4.1.0-1
  • ros-jazzy-cyclonedds: 0.10.4-4 → 0.10.5-1
  • ros-jazzy-demo-nodes-cpp: 0.33.3-1 → 0.33.4-1
  • ros-jazzy-demo-nodes-cpp-native: 0.33.3-1 → 0.33.4-1
  • ros-jazzy-demo-nodes-py: 0.33.3-1 → 0.33.4-1
  • ros-jazzy-dummy-map-server: 0.33.3-1 → 0.33.4-1
  • ros-jazzy-dummy-robot-bringup: 0.33.3-1 → 0.33.4-1
  • ros-jazzy-dummy-sensors: 0.33.3-1 → 0.33.4-1
  • ros-jazzy-examples-rclcpp-async-client: 0.19.3-2 → 0.19.4-1
  • ros-jazzy-examples-rclcpp-cbg-executor: 0.19.3-2 → 0.19.4-1
  • ros-jazzy-examples-rclcpp-minimal-action-client: 0.19.3-2 → 0.19.4-1
  • ros-jazzy-examples-rclcpp-minimal-action-server: 0.19.3-2 → 0.19.4-1
  • ros-jazzy-examples-rclcpp-minimal-client: 0.19.3-2 → 0.19.4-1
  • ros-jazzy-examples-rclcpp-minimal-composition: 0.19.3-2 → 0.19.4-1
  • ros-jazzy-examples-rclcpp-minimal-publisher: 0.19.3-2 → 0.19.4-1
  • ros-jazzy-examples-rclcpp-minimal-service: 0.19.3-2 → 0.19.4-1
  • ros-jazzy-examples-rclcpp-minimal-subscriber: 0.19.3-2 → 0.19.4-1
  • ros-jazzy-examples-rclcpp-minimal-timer: 0.19.3-2 → 0.19.4-1
  • ros-jazzy-examples-rclcpp-multithreaded-executor: 0.19.3-2 → 0.19.4-1
  • ros-jazzy-examples-rclcpp-wait-set: 0.19.3-2 → 0.19.4-1
  • ros-jazzy-examples-rclpy-executors: 0.19.3-2 → 0.19.4-1
  • ros-jazzy-examples-rclpy-guard-conditions: 0.19.3-2 → 0.19.4-1
  • ros-jazzy-examples-rclpy-minimal-action-client: 0.19.3-2 → 0.19.4-1
  • ros-jazzy-examples-rclpy-minimal-action-server: 0.19.3-2 → 0.19.4-1
  • ros-jazzy-examples-rclpy-minimal-client: 0.19.3-2 → 0.19.4-1
  • ros-jazzy-examples-rclpy-minimal-publisher: 0.19.3-2 → 0.19.4-1
  • ros-jazzy-examples-rclpy-minimal-service: 0.19.3-2 → 0.19.4-1
  • ros-jazzy-examples-rclpy-minimal-subscriber: 0.19.3-2 → 0.19.4-1
  • ros-jazzy-examples-rclpy-pointcloud-publisher: 0.19.3-2 → 0.19.4-1
  • ros-jazzy-fastcdr: 2.2.1-2 → 2.2.2-1
  • ros-jazzy-fastrtps: 2.14.0-2 → 2.14.1-1
  • ros-jazzy-flir-camera-description: 2.0.15-2 → 2.0.20-1
  • ros-jazzy-flir-camera-msgs: 2.0.15-2 → 2.0.20-1
  • ros-jazzy-geometric-shapes: 2.2.0-1 → 2.2.1-1
  • ros-jazzy-image-common: 5.1.3-1 → 5.1.4-1
  • ros-jazzy-image-geometry: 4.0.0-2 → 4.1.0-1
  • ros-jazzy-image-tools: 0.33.3-1 → 0.33.4-1
  • ros-jazzy-image-transport: 5.1.3-1 → 5.1.4-1
  • ros-jazzy-intra-process-demo: 0.33.3-1 → 0.33.4-1
  • ros-jazzy-irobot-create-msgs: 3.0.0-1 → 3.0.0-2
  • ros-jazzy-kitti-metrics-eval: 1.0.5-1 → 1.0.6-1
  • ros-jazzy-launch-testing-examples: 0.19.3-2 → 0.19.4-1
  • ros-jazzy-libcurl-vendor: 3.4.2-2 → 3.4.3-1
  • ros-jazzy-liblz4-vendor: 0.26.3-1 → 0.26.4-1
  • ros-jazzy-libstatistics-collector: 1.7.2-1 → 1.7.3-1
  • ros-jazzy-lifecycle: 0.33.3-1 → 0.33.4-1
  • ros-jazzy-lifecycle-py: 0.33.3-1 → 0.33.4-1
  • ros-jazzy-logging-demo: 0.33.3-1 → 0.33.4-1
  • ros-jazzy-lttngpy: 8.2.0-2 → 8.2.1-1
  • ros-jazzy-mcap-vendor: 0.26.3-1 → 0.26.4-1
  • ros-jazzy-mola: 1.0.5-1 → 1.0.6-1
  • ros-jazzy-mola-bridge-ros2: 1.0.5-1 → 1.0.6-1
  • ros-jazzy-mola-demos: 1.0.5-1 → 1.0.6-1
  • ros-jazzy-mola-imu-preintegration: 1.0.5-1 → 1.0.6-1
  • ros-jazzy-mola-input-euroc-dataset: 1.0.5-1 → 1.0.6-1
  • ros-jazzy-mola-input-kitti-dataset: 1.0.5-1 → 1.0.6-1
  • ros-jazzy-mola-input-kitti360-dataset: 1.0.5-1 → 1.0.6-1
  • ros-jazzy-mola-input-mulran-dataset: 1.0.5-1 → 1.0.6-1
  • ros-jazzy-mola-input-paris-luco-dataset: 1.0.5-1 → 1.0.6-1
  • ros-jazzy-mola-input-rawlog: 1.0.5-1 → 1.0.6-1
  • ros-jazzy-mola-input-rosbag2: 1.0.5-1 → 1.0.6-1
  • ros-jazzy-mola-kernel: 1.0.5-1 → 1.0.6-1
  • ros-jazzy-mola-launcher: 1.0.5-1 → 1.0.6-1
  • ros-jazzy-mola-metric-maps: 1.0.5-1 → 1.0.6-1
  • ros-jazzy-mola-navstate-fuse: 1.0.5-1 → 1.0.6-1
  • ros-jazzy-mola-pose-list: 1.0.5-1 → 1.0.6-1
  • ros-jazzy-mola-relocalization: 1.0.5-1 → 1.0.6-1
  • ros-jazzy-mola-traj-tools: 1.0.5-1 → 1.0.6-1
  • ros-jazzy-mola-viz: 1.0.5-1 → 1.0.6-1
  • ros-jazzy-mola-yaml: 1.0.5-1 → 1.0.6-1
  • ros-jazzy-moveit-common: 2.9.0-1 → 2.10.0-1
  • ros-jazzy-moveit-configs-utils: 2.9.0-1 → 2.10.0-1
  • ros-jazzy-moveit-core: 2.9.0-1 → 2.10.0-1
  • ros-jazzy-moveit-hybrid-planning: 2.9.0-1 → 2.10.0-1
  • ros-jazzy-moveit-kinematics: 2.9.0-1 → 2.10.0-1
  • ros-jazzy-moveit-planners: 2.9.0-1 → 2.10.0-1
  • ros-jazzy-moveit-planners-chomp: 2.9.0-1 → 2.10.0-1
  • ros-jazzy-moveit-planners-ompl: 2.9.0-1 → 2.10.0-1
  • ros-jazzy-moveit-planners-stomp: 2.9.0-1 → 2.10.0-1
  • ros-jazzy-moveit-plugins: 2.9.0-1 → 2.10.0-1
  • ros-jazzy-moveit-py: 2.9.0-1 → 2.10.0-1
  • ros-jazzy-moveit-resources-prbt-ikfast-manipulator-plugin: 2.9.0-1 → 2.10.0-1
  • ros-jazzy-moveit-resources-prbt-moveit-config: 2.9.0-1 → 2.10.0-1
  • ros-jazzy-moveit-resources-prbt-pg70-support: 2.9.0-1 → 2.10.0-1
  • ros-jazzy-moveit-resources-prbt-support: 2.9.0-1 → 2.10.0-1
  • ros-jazzy-moveit-ros-control-interface: 2.9.0-1 → 2.10.0-1
  • ros-jazzy-moveit-ros-move-group: 2.9.0-1 → 2.10.0-1
  • ros-jazzy-moveit-ros-occupancy-map-monitor: 2.9.0-1 → 2.10.0-1
  • ros-jazzy-moveit-ros-perception: 2.9.0-1 → 2.10.0-1
  • ros-jazzy-moveit-ros-planning: 2.9.0-1 → 2.10.0-1
  • ros-jazzy-moveit-ros-planning-interface: 2.9.0-1 → 2.10.0-1
  • ros-jazzy-moveit-ros-robot-interaction: 2.9.0-1 → 2.10.0-1
  • ros-jazzy-moveit-ros-visualization: 2.9.0-1 → 2.10.0-1
  • ros-jazzy-moveit-ros-warehouse: 2.9.0-1 → 2.10.0-1
  • ros-jazzy-moveit-runtime: 2.9.0-1 → 2.10.0-1
  • ros-jazzy-moveit-servo: 2.9.0-1 → 2.10.0-1
  • ros-jazzy-moveit-setup-app-plugins: 2.9.0-1 → 2.10.0-1
  • ros-jazzy-moveit-setup-assistant: 2.9.0-1 → 2.10.0-1
  • ros-jazzy-moveit-setup-controllers: 2.9.0-1 → 2.10.0-1
  • ros-jazzy-moveit-setup-core-plugins: 2.9.0-1 → 2.10.0-1
  • ros-jazzy-moveit-setup-framework: 2.9.0-1 → 2.10.0-1
  • ros-jazzy-moveit-setup-srdf-plugins: 2.9.0-1 → 2.10.0-1
  • ros-jazzy-moveit-simple-controller-manager: 2.9.0-1 → 2.10.0-1
  • ros-jazzy-mp2p-icp: 1.4.3-1 → 1.5.0-1
  • ros-jazzy-mrpt2: 2.13.1-1 → 2.13.2-1
  • ros-jazzy-nav2-minimal-tb3-sim: 1.0.0-1 → 1.0.1-1
  • ros-jazzy-nav2-minimal-tb4-description: 1.0.0-1 → 1.0.1-1
  • ros-jazzy-nav2-minimal-tb4-sim: 1.0.0-1 → 1.0.1-1
  • ros-jazzy-nlohmann-json-schema-validator-vendor: 0.4.0-3 → 0.4.1-1
  • ros-jazzy-openeb-vendor: 1.3.1-1 → 1.3.2-1
  • ros-jazzy-pendulum-control: 0.33.3-1 → 0.33.4-1
  • ros-jazzy-pendulum-msgs: 0.33.3-1 → 0.33.4-1
  • ros-jazzy-pilz-industrial-motion-planner: 2.9.0-1 → 2.10.0-1
  • ros-jazzy-pilz-industrial-motion-planner-testutils: 2.9.0-1 → 2.10.0-1
  • ros-jazzy-point-cloud-transport: 4.0.1-1 → 4.0.2-1
  • ros-jazzy-point-cloud-transport-py: 4.0.1-1 → 4.0.2-1
  • ros-jazzy-pybind11-json-vendor: 0.4.1-3 → 0.4.2-1
  • ros-jazzy-quality-of-service-demo-cpp: 0.33.3-1 → 0.33.4-1
  • ros-jazzy-quality-of-service-demo-py: 0.33.3-1 → 0.33.4-1
  • ros-jazzy-rclcpp: 28.1.2-1 → 28.1.3-1
  • ros-jazzy-rclcpp-action: 28.1.2-1 → 28.1.3-1
  • ros-jazzy-rclcpp-components: 28.1.2-1 → 28.1.3-1
  • ros-jazzy-rclcpp-lifecycle: 28.1.2-1 → 28.1.3-1
  • ros-jazzy-resource-retriever: 3.4.2-2 → 3.4.3-1
  • ros-jazzy-rmf-api-msgs: 0.2.1-3 → 0.3.1-1
  • ros-jazzy-rmf-battery: 0.3.0-3 → 0.3.1-1
  • ros-jazzy-rmf-building-map-msgs: 1.4.0-3 → 1.4.1-1
  • ros-jazzy-rmf-charger-msgs: 3.2.1-3 → 3.3.1-1
  • ros-jazzy-rmf-charging-schedule: 2.6.0-2 → 2.7.2-1
  • ros-jazzy-rmf-dispenser-msgs: 3.2.1-3 → 3.3.1-1
  • ros-jazzy-rmf-door-msgs: 3.2.1-3 → 3.3.1-1
  • ros-jazzy-rmf-fleet-adapter: 2.6.0-2 → 2.7.2-1
  • ros-jazzy-rmf-fleet-adapter-python: 2.6.0-2 → 2.7.2-1
  • ros-jazzy-rmf-fleet-msgs: 3.2.1-3 → 3.3.1-1
  • ros-jazzy-rmf-ingestor-msgs: 3.2.1-3 → 3.3.1-1
  • ros-jazzy-rmf-lift-msgs: 3.2.1-3 → 3.3.1-1
  • ros-jazzy-rmf-obstacle-msgs: 3.2.1-3 → 3.3.1-1
  • ros-jazzy-rmf-scheduler-msgs: 3.2.1-3 → 3.3.1-1
  • ros-jazzy-rmf-site-map-msgs: 3.2.1-3 → 3.3.1-1
  • ros-jazzy-rmf-task: 2.4.0-3 → 2.5.1-1
  • ros-jazzy-rmf-task-msgs: 3.2.1-3 → 3.3.1-1
  • ros-jazzy-rmf-task-ros2: 2.6.0-2 → 2.7.2-1
  • ros-jazzy-rmf-task-sequence: 2.4.0-3 → 2.5.1-1
  • ros-jazzy-rmf-traffic: 3.3.1-3 → 3.3.3-1
  • ros-jazzy-rmf-traffic-examples: 3.3.1-3 → 3.3.3-1
  • ros-jazzy-rmf-traffic-msgs: 3.2.1-3 → 3.3.1-1
  • ros-jazzy-rmf-traffic-ros2: 2.6.0-2 → 2.7.2-1
  • ros-jazzy-rmf-utils: 1.6.0-3 → 1.6.2-1
  • ros-jazzy-rmf-visualization: 2.2.1-3 → 2.3.2-1
  • ros-jazzy-rmf-visualization-building-systems: 2.2.1-3 → 2.3.2-1
  • ros-jazzy-rmf-visualization-fleet-states: 2.2.1-3 → 2.3.2-1
  • ros-jazzy-rmf-visualization-floorplans: 2.2.1-3 → 2.3.2-1
  • ros-jazzy-rmf-visualization-msgs: 1.4.0-3 → 1.4.1-1
  • ros-jazzy-rmf-visualization-navgraphs: 2.2.1-3 → 2.3.2-1
  • ros-jazzy-rmf-visualization-obstacles: 2.2.1-3 → 2.3.2-1
  • ros-jazzy-rmf-visualization-rviz2-plugins: 2.2.1-3 → 2.3.2-1
  • ros-jazzy-rmf-visualization-schedule: 2.2.1-3 → 2.3.2-1
  • ros-jazzy-rmf-websocket: 2.6.0-2 → 2.7.2-1
  • ros-jazzy-rmf-workcell-msgs: 3.2.1-3 → 3.3.1-1
  • ros-jazzy-rmw-fastrtps-cpp: 8.4.0-2 → 8.4.1-1
  • ros-jazzy-rmw-fastrtps-dynamic-cpp: 8.4.0-2 → 8.4.1-1
  • ros-jazzy-rmw-fastrtps-shared-cpp: 8.4.0-2 → 8.4.1-1
  • ros-jazzy-rmw-implementation: 2.15.2-1 → 2.15.3-1
  • ros-jazzy-ros2bag: 0.26.3-1 → 0.26.4-1
  • ros-jazzy-ros2trace: 8.2.0-2 → 8.2.1-1
  • ros-jazzy-rosbag2: 0.26.3-1 → 0.26.4-1
  • ros-jazzy-rosbag2-compression: 0.26.3-1 → 0.26.4-1
  • ros-jazzy-rosbag2-compression-zstd: 0.26.3-1 → 0.26.4-1
  • ros-jazzy-rosbag2-cpp: 0.26.3-1 → 0.26.4-1
  • ros-jazzy-rosbag2-examples-cpp: 0.26.3-1 → 0.26.4-1
  • ros-jazzy-rosbag2-examples-py: 0.26.3-1 → 0.26.4-1
  • ros-jazzy-rosbag2-interfaces: 0.26.3-1 → 0.26.4-1
  • ros-jazzy-rosbag2-performance-benchmarking: 0.26.3-1 → 0.26.4-1
  • ros-jazzy-rosbag2-performance-benchmarking-msgs: 0.26.3-1 → 0.26.4-1
  • ros-jazzy-rosbag2-py: 0.26.3-1 → 0.26.4-1
  • ros-jazzy-rosbag2-storage: 0.26.3-1 → 0.26.4-1
  • ros-jazzy-rosbag2-storage-default-plugins: 0.26.3-1 → 0.26.4-1
  • ros-jazzy-rosbag2-storage-mcap: 0.26.3-1 → 0.26.4-1
  • ros-jazzy-rosbag2-storage-sqlite3: 0.26.3-1 → 0.26.4-1
  • ros-jazzy-rosbag2-test-common: 0.26.3-1 → 0.26.4-1
  • ros-jazzy-rosbag2-test-msgdefs: 0.26.3-1 → 0.26.4-1
  • ros-jazzy-rosbag2-tests: 0.26.3-1 → 0.26.4-1
  • ros-jazzy-rosbag2-transport: 0.26.3-1 → 0.26.4-1
  • ros-jazzy-rosidl-adapter: 4.6.2-1 → 4.6.3-1
  • ros-jazzy-rosidl-cli: 4.6.2-1 → 4.6.3-1
  • ros-jazzy-rosidl-cmake: 4.6.2-1 → 4.6.3-1
  • ros-jazzy-rosidl-generator-c: 4.6.2-1 → 4.6.3-1
  • ros-jazzy-rosidl-generator-cpp: 4.6.2-1 → 4.6.3-1
  • ros-jazzy-rosidl-generator-type-description: 4.6.2-1 → 4.6.3-1
  • ros-jazzy-rosidl-parser: 4.6.2-1 → 4.6.3-1
  • ros-jazzy-rosidl-pycommon: 4.6.2-1 → 4.6.3-1
  • ros-jazzy-rosidl-runtime-c: 4.6.2-1 → 4.6.3-1
  • ros-jazzy-rosidl-runtime-cpp: 4.6.2-1 → 4.6.3-1
  • ros-jazzy-rosidl-typesupport-interface: 4.6.2-1 → 4.6.3-1
  • ros-jazzy-rosidl-typesupport-introspection-c: 4.6.2-1 → 4.6.3-1
  • ros-jazzy-rosidl-typesupport-introspection-cpp: 4.6.2-1 → 4.6.3-1
  • ros-jazzy-rviz-assimp-vendor: 14.1.1-1 → 14.1.2-1
  • ros-jazzy-rviz-common: 14.1.1-1 → 14.1.2-1
  • ros-jazzy-rviz-default-plugins: 14.1.1-1 → 14.1.2-1
  • ros-jazzy-rviz-ogre-vendor: 14.1.1-1 → 14.1.2-1
  • ros-jazzy-rviz-rendering: 14.1.1-1 → 14.1.2-1
  • ros-jazzy-rviz-rendering-tests: 14.1.1-1 → 14.1.2-1
  • ros-jazzy-rviz-visual-testing-framework: 14.1.1-1 → 14.1.2-1
  • ros-jazzy-rviz2: 14.1.1-1 → 14.1.2-1
  • ros-jazzy-shared-queues-vendor: 0.26.3-1 → 0.26.4-1
  • ros-jazzy-smclib: 4.0.0-5 → 4.1.0-1
  • ros-jazzy-sqlite3-vendor: 0.26.3-1 → 0.26.4-1
  • ros-jazzy-sros2: 0.13.0-3 → 0.13.2-1
  • ros-jazzy-sros2-cmake: 0.13.0-3 → 0.13.2-1
  • ros-jazzy-swri-console: 2.0.4-7 → 2.0.5-1
  • ros-jazzy-topic-monitor: 0.33.3-1 → 0.33.4-1
  • ros-jazzy-topic-statistics-demo: 0.33.3-1 → 0.33.4-1
  • ros-jazzy-tracetools: 8.2.0-2 → 8.2.1-1
  • ros-jazzy-tracetools-launch: 8.2.0-2 → 8.2.1-1
  • ros-jazzy-tracetools-read: 8.2.0-2 → 8.2.1-1
  • ros-jazzy-tracetools-test: 8.2.0-2 → 8.2.1-1
  • ros-jazzy-tracetools-trace: 8.2.0-2 → 8.2.1-1
  • ros-jazzy-vision-opencv: 4.0.0-2 → 4.1.0-1
  • ros-jazzy-zstd-vendor: 0.26.3-1 → 0.26.4-1

Removed Packages [4]:

  • ros-jazzy-rmf-cmake-uncrustify
  • ros-jazzy-test-bond
  • ros-jazzy-test-bond-dbgsym
  • ros-jazzy-webots-ros2-tests

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:

  • Aaron Chong
  • Aditya Pande
  • Alberto Soragna
  • Alberto Tudela
  • Alejandro Hernandez Cordero
  • Alejandro Hernández
  • Alexander Gutenkunst
  • Alexey Merzlyakov
  • Apex.AI, Inc.
  • Arjo Chakravarty
  • Bernd Pfrommer
  • Blake Anderson
  • Brandon Ong
  • Brian Wilcox
  • Carl Delsey
  • Carlos Orduno
  • Chittaranjan Srinivas Swaminathan
  • Chris Lalancette
  • Christian Henkel
  • Christophe Bedard
  • David V. Lu!!
  • Eclipse Foundation, Inc.
  • Emerson Knapp
  • Foxglove
  • Geoffrey Biggs
  • Gerardo Puga
  • Grey
  • Henning Kayser
  • Holger Banzhaf
  • Ivan Paunovic
  • Jose-Luis Blanco-Claraco
  • Kenji Brameld
  • LibRealSense ROS Team
  • Luca Della Vedova
  • Luis Camero
  • M. Fatih Cırıt
  • Marco A. Gutiérrez
  • Matej Vargovcik
  • Michael Görner
  • Michael Jeronimo
  • Michael Orlov
  • Miguel Company
  • Mohammad Haghighipanah
  • Morgan Quigley
  • MoveIt Release Team
  • Peter David Fagan
  • ROS Security Working Group
  • ROS Tooling Working Group
  • Rushyendra Maganty
  • Southwest Research Institute
  • Steve Macenski
  • Takagi, Isamu
  • Tyler Weaver
  • William Woodall
  • Yadunund
  • Yutaka Kondo
  • geoff
  • kminoda
  • methylDragon
  • steve

1 post - 1 participant

Read full topic

by marcogg on July 05, 2024 04:36 PM

July 04, 2024
New Implementation for Unitree GO 2 in ROS 2 Humble

home

Hello everyone!!

Let me introduce myself, my name is Juan Carlos Manzanares and I belong to a robotics research group called Intelligents Robotics Lab, belonging to the Rey Juan Carlos University, Madrid, Spain. In this group we develop some projects, such as MOCAP4ROS2, PlanSys2, CascadeLifecycle, marathon for nav2, robocups

Today, together with @Fmrico and @juanscelyg, I come to present our implementation to make the unitree go 2 robot work in ros2, in this case for dds.

This implementation is given since once you connect to this robot you can see topics, but you do not see any launched nodes. Furthermore, there is too much information in these topics that we are not typically used to seeing in a robot. By this I mean being able to see a /robot_description, being able to see the /joints_states of the motors, being able to move our robot easily using a /cmd_vel.

In the previous repository, you can find how to use our “driver”, fully implemented in c++, with all the steps to follow to change your robot’s mode, change settings, command speeds, etc… Also, you can find a small list of implementations that we already have done, or which we are currently working on.

I show you some images of what was mentioned:

We are currently developing support to be able to do slam and nav2 with this robot, so we hope to update within a couple of weeks with new news about it ^ ^. Also, in the future (hopefully soon), we want to have a gazebo simulation ready, so that anyone who does not have this robot can also work with it.

This post is not only to show our work, but also to invite the entire community to contribute to it, helping to find small bugs, developing new things… So I invite everyone to contribute to this repository.

Thank you very much for reading the post and I hope it helps many of you.

Greetings.

8 posts - 7 participants

Read full topic

by Juancams on July 04, 2024 03:11 PM

July 03, 2024
New packages for Humble Hawksbill 2024-07-03

Package Updates for Humble

Added Packages [41]:

  • ros-humble-autoware-common-msgs: 1.1.0-1
  • ros-humble-autoware-common-msgs-dbgsym: 1.1.0-1
  • ros-humble-autoware-control-msgs: 1.1.0-1
  • ros-humble-autoware-control-msgs-dbgsym: 1.1.0-1
  • ros-humble-autoware-lanelet2-extension: 0.4.0-1
  • ros-humble-autoware-lanelet2-extension-dbgsym: 0.4.0-1
  • ros-humble-autoware-lanelet2-extension-python: 0.4.0-1
  • ros-humble-autoware-lanelet2-extension-python-dbgsym: 0.4.0-1
  • ros-humble-autoware-localization-msgs: 1.1.0-1
  • ros-humble-autoware-localization-msgs-dbgsym: 1.1.0-1
  • ros-humble-autoware-map-msgs: 1.1.0-1
  • ros-humble-autoware-map-msgs-dbgsym: 1.1.0-1
  • ros-humble-autoware-perception-msgs: 1.1.0-1
  • ros-humble-autoware-perception-msgs-dbgsym: 1.1.0-1
  • ros-humble-autoware-planning-msgs: 1.1.0-1
  • ros-humble-autoware-planning-msgs-dbgsym: 1.1.0-1
  • ros-humble-autoware-sensing-msgs: 1.1.0-1
  • ros-humble-autoware-sensing-msgs-dbgsym: 1.1.0-1
  • ros-humble-autoware-system-msgs: 1.1.0-1
  • ros-humble-autoware-system-msgs-dbgsym: 1.1.0-1
  • ros-humble-autoware-vehicle-msgs: 1.1.0-1
  • ros-humble-autoware-vehicle-msgs-dbgsym: 1.1.0-1
  • ros-humble-create3-coverage: 0.0.5-1
  • ros-humble-create3-coverage-dbgsym: 0.0.5-1
  • ros-humble-create3-examples-msgs: 0.0.5-1
  • ros-humble-create3-examples-msgs-dbgsym: 0.0.5-1
  • ros-humble-create3-examples-py: 0.0.5-1
  • ros-humble-create3-lidar-slam: 0.0.5-1
  • ros-humble-create3-republisher: 0.0.5-1
  • ros-humble-create3-republisher-dbgsym: 0.0.5-1
  • ros-humble-create3-teleop: 0.0.5-1
  • ros-humble-flex-sync: 2.0.0-1
  • ros-humble-mola-navstate-fg: 1.0.6-1
  • ros-humble-mola-navstate-fg-dbgsym: 1.0.6-1
  • ros-humble-pal-gripper-simulation: 3.2.0-1
  • ros-humble-rosx-introspection: 1.0.1-1
  • ros-humble-situational-graphs-datasets: 0.0.0-1
  • ros-humble-situational-graphs-reasoning-msgs: 0.0.0-1
  • ros-humble-situational-graphs-reasoning-msgs-dbgsym: 0.0.0-1
  • ros-humble-situational-graphs-wrapper: 0.0.0-1
  • ros-humble-tiago-gazebo-dbgsym: 4.1.7-1

Updated Packages [176]:

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:

  • Aina Irisarri
  • Alberto Soragna
  • Alejandro Hernández
  • Antonio Brandi
  • Apex.AI, Inc.
  • Austin Hendrix
  • Bernd Pfrommer
  • Davide Faconti
  • Denis Stogl
  • Felix Exner
  • Gerardo Puga
  • Jordan Palacios
  • Jordi Pages
  • Jose-Luis Blanco-Claraco
  • Kevin Hallenbeck
  • M. Fatih Cırıt
  • Mamoru Sobue
  • Mathieu Labbe
  • Micho Radovnikovich
  • Sai Kishor Kothakota
  • Southwest Research Institute
  • TIAGo PAL support team
  • Takagi, Isamu
  • Yue Erro
  • Yutaka Kondo
  • adminpc
  • jkearns
  • kminoda
  • mitsudome-r

1 post - 1 participant

Read full topic

by audrow on July 03, 2024 07:30 PM

Interoperabiility Interest Group July 4, 2024: Open Mic Night

Community Page

Meeting Link

Calendar Link

With the Fourth of July being a major holiday in the United States, the next special interest group meeting will be a (lightly moderated) open mic night. There will not be any special topic or presentation, so feel free to chat with the rest of the group about anything remotely in the sphere of interoperability.

We will not be recording this session, but I might take notes if anything particularly interesting develops from the conversations.

1 post - 1 participant

Read full topic

by grey on July 03, 2024 06:24 AM

New documentation on how to take a message from a subscriber without executing a callback function

Hello everyone!

Autoware Documentation provides a guideline to take a message from Subscription without executing any callback function.

https://autowarefoundation.github.io/autoware-documentation/main/contributing/coding-guidelines/ros-nodes/topic-message-handling/

I believe that the document must be helpful for many users and projects even though it only explains the take() method defined in the rclcpp::Subscription class. The official rclcpp API document and ros2/examples modestly introduce the take() method, but there is less documentation that tells how to use the take() method.

In ROS based projects, it is often seen that a callback function is called when a topic based message is received by a subscriber. The programming manner seems to be common sense in the ROS community because it is explained in tutorials and ros2/demos.

Autoware developers also had this common sense but it was a burden for Autoware. Autoware is one of the large applications based on ROS 2. Autoware is composed of many nodes and has a large number of message communication for inter-process and intra-process communication. The large number of message communication implies too much execution of callback functions which wastes CPU resources. It is easy to understand that wasting CPU resources can be one of the causes of high CPU load of Autoware. Besides, a thread may not necessarily be assigned to a callback function even though it is ready to run if the system is too busy to allocate enough CPU time to ready tasks.

I think that overuse of callback functions can be detrimental to a large application like Autoware. I have suggested that Autoware should use the rclcpp:Subscription’s take() method instead of a callback function to reference a topic message. I think that the take() method will give us some advantages;

  • The take() method can reduce the number of subscription callback function calls
  • There is no need to take a topic message from a subscription that is not consumed in the user logic
  • There is no mandatory thread waking for the callback function which bothers programmers; thread forces them to worry about parallelism and data race

We believe that the take() method can be helpful for many users and projects. If you want to utilize ROS 2 and want more details than the tutorial, please visit the following page.

Topic message handling guideline - Autoware Documentation

8 posts - 5 participants

Read full topic

by takamine on July 03, 2024 04:31 AM

June 30, 2024
How to control cobot arm on Limo in both ROS1 and ROS2?

Limo Cobot is a Limo series robot equipped with a cobot arm base on Limo Pro base. More details please visit: LIMO PRO – Agilex Robotics

Limo Cobot(Pro) can be integrated with both ROS1 and ROS2. In this project the instructions of how to control cobot robotic arm in both ROS1 and ROS2 will be introduced.

Set connection between robot and arm

The Cobot robot has two control methods.

First, you can directly call the API interface to control the robot by assigning six joint angles. This method allows users to directly specify the robot’s motion trajectory and posture, thereby accurately controlling its movements.

Second, Cobot also supports control using MoveIt. Users can set the target point, and MoveIt calculates the six joint angles and sends these angles to the robot. This method is more flexible and can achieve more complex motion planning and control by setting the target point, while also being able to adapt to different work scenarios and needs.

Whether calling the API interface directly or using MoveIt, the Cobot robot can provide efficient and accurate robot control to meet the needs of users in different scenarios.

Open the robot and enter the following interface, where communication configuration is required. Select Transponder and click OK.
通讯模式1

Then, choose USB UART and click ok.

When ‘Atom:ok’ shows, the connection is successfull.
通讯模式3

Control cobot robotic arm:

Control the Robot Arm Using Sliders

Start the slider control node. Open a new terminal, and enter the command in the terminal:

ros2 launch mycobot_280 slider_control.launch.py port:=/dev/ttyACM0 baud:=115200

In ros1, please run:

roslaunch mycobot_280 slider_control.launch

and then, run

rosrun mycobot_280 slider_control.py _port:=/dev/ttyACM0 _baud:=115200

to start the real arm.


The angles of the six axes of the real robot arm can be controlled through the slider control interface.

The model follows the real robot arm

To start the model following the robot arm function, open a new terminal and enter:

 ros2 launch mycobot_280 mycobot_follow.launch.py 

In ros1:
Start the robot model, open a new terminal, and enter in the terminal:

roslaunch mycobot_280 mycobot_follow.launch

Start the model follow node:

rosrun mycobot_280 follow_display.py _port:=/dev/ttyACM0 _baud:=115200

After successful startup, the robot arm will be unlocked. At this time, you can use your hand to bend the robot arm, and the model in rviz will follow and move.

Return back to rivz. The model in rviz will follow the real robotic arm.

GUI control robotic arm

Use a simple GUI interface to control the movement of the robotic arm. Start a new terminal and enter the command in the terminal:

ros2 launch mycobot_280 simple_gui.launch.py

In ros1, run:

roslaunch mycobot_280 simple_gui.launch

After starting up successfully, you can enter the angle information or position information of each joint in the GUI interface.


After setting the angle of the robot arm axis, click the SET button and the robot arm will move to the set position. JAW and pimp are the switches corresponding to the gripper and suction pump device respectively.

Keyboard control

ros2 launch mycobot_280 teleop_keyboard.launch.py

After running this, a interface will appear.


Next, open another terminal and run:

ros2 run mycobot_280 teleop_keyboard

You can see the output:

Mycobot Teleop Keyboard Controller
---------------------------
Movimg options(control coordinations [x,y,z,rx,ry,rz]):
              w(x+)

    a(y-)     s(x-)     d(y+)

    z(z-) x(z+)

u(rx+)   i(ry+)   o(rz+)
j(rx-)   k(ry-)   l(rz-)

Gripper control:
    g - open
    h - close

Other:
    1 - Go to init pose
    2 - Go to home pose
    3 - Resave home pose
    q - Quit

currently:    speed: 10    change percent: 2


In this terminal, you can control the state of the robot arm and move the robot arm by pressing keys in the terminal.

In ros1:
Use the keyboard to control the machine. Open a new terminal and enter the following in the terminal:

roslaunch mycobot_280 teleop_keyboard.launch

Wait for the terminal to display ready and then open a command line:

rosrun mycobot_280 teleop_keyboard.py

After the startup is successful, you can use the keys w a s d to control the movement of the robot arm.

Moveit control

Open a new terminal and run:

ros2 launch mycobot_280_moveit demo.launch.py 

After running, the following RVIZ interface will appear:


To control the real robot arm through Moveit, you need to enable another command:

ros2 run mycobot_280 sync_plan 

Then you can drag the model on the Moveit to control the real robotic arm.

In ros1:
Start the moveit robot control node, open a new terminal, and enter in the terminal:

roslaunch limo_cobot_moveit_config demo.launch

Start the real robot synchronization node:

rosrun mycobot_280_moveit sync_plan.py _port:=/dev/ttyACM0 _baud:=115200

Move and grab in ROS1

In the mobile grabbing function, use move_base to navigate the Limo robot to the target point location. Once the robot reaches the target position, it triggers the robot arm to perform a grabbing motion by calling the API interface of the robot arm, realizing the complete process of the mobile grabbing function. This combination of navigation and robotic arm control allows the robot to move in dynamic environments and perform grasping tasks.

(1)Open a new terminal, and enter the command to launch the LiDAR:

roslaunch limo_bringup limo_start.launch pub_odom_tf:=false

(2)Open a new terminal, and enter the command to start the navigation.

roslaunch limo_bringup limo_navigation_diff.launch

Record first position.


Drive Limo to the grabbing location and record the second location.

Fill in the data in /home/agilex/agilex_ws/src/set_nav_point/more_task_node.py as shown in the figure.
First one:

Second one:

(3)Start the mobile grabbing function node. Open a new terminal, and enter the command in the terminal:

rosrun set_nav_point more_task_node.py

After successful startup, Limo will go to the grabbing location. After arriving, the robotic arm will perform the grabbing action.

About Limo

If you are interested in Limo or have some technical questions about it, feel free to join AgileX Robotics or AgileX Robotics. Let’s talk about it!

2 posts - 2 participants

Read full topic

by Agilex_Robotics on June 30, 2024 05:38 AM

June 28, 2024
Cloud Robotics WG Meeting 2024-07-01

Last meeting, we heard from Gui Manzato, who is a Partner and CEO at Ekumen , an engineering services company specialized in robotics. Thank you, Gui!

Next meeting, we will have a few points in our agenda:

  1. Start with a retrospective of how the WG is doing. Any changes that come from this meeting will affect future meetings.
  2. Divide up the work for processing survey results. Some volunteers will be welcome to push this along outside of meetings, as we have spent several meetings on this.
  3. Build a roadmap of what the group is trying to build, working backwards from the deliverables we would like to produce.

The meeting link is here.

Hopefully we will see you there!

1 post - 1 participant

Read full topic

by mikelikesrobots on June 28, 2024 09:40 PM

ROS News for the Week of June 24th, 2024

ROS News for the Week for June 24th, 2024

This week @opfernandez announced a new ROS 2 wrapper node for “Depth Anything V2” that was just published at CVPR 2024.. This new algorithm can translate a conventioal RGB camera image into a depth camera image. Really cool stuff!



Austin Texas is getting its first ROS Meetup! If you are in the area swing by on July 25th.


aa0854c9d72a1d8f9f8e1a7087a5eabf611e5017_2_690x185 (1)
@alsora has a great post explaining all the changes to ROS 2 executors in Jazzy Jalisco. The performance of executors in Jazzy has increased substantially so it is worth checking out the post.


This week we announced the first of many events that are happening in conjunction with ROSCon! Teradyne, the parent company of MiR and Universal Robotics, will be hosting tours of their new research center in Odense on the first day of ROSCon. Details are on the ROSCon website, and you can sign up for a tour during ROSCon registration.


Events

News

ROS

Got a Minute?

Why not answer a couple of questions on Robotics Stack Exchange? Your knowledge and expertise is needed by your colleagues! s

1 post - 1 participant

Read full topic

by Katherine_Scott on June 28, 2024 09:16 PM

New Packages for Iron Irwini 2024-06-28

We’re happy to announce 2 new packages and 74 updates are now available in ROS 2 Iron Irwini :iron: :irwini: . This sync was tagged as iron/2024-06-28 .

Package Updates for iron

Added Packages [2]:

Updated Packages [74]:

  • ros-iron-beluga: 2.0.1-1 → 2.0.2-1
  • ros-iron-beluga-amcl: 2.0.1-1 → 2.0.2-1
  • ros-iron-beluga-amcl-dbgsym: 2.0.1-1 → 2.0.2-1
  • ros-iron-beluga-ros: 2.0.1-1 → 2.0.2-1
  • ros-iron-eigenpy: 3.6.0-1 → 3.7.0-1
  • ros-iron-eigenpy-dbgsym: 3.6.0-1 → 3.7.0-1
  • ros-iron-kitti-metrics-eval: 1.0.5-1 → 1.0.6-1
  • ros-iron-kitti-metrics-eval-dbgsym: 1.0.5-1 → 1.0.6-1
  • ros-iron-launch: 2.0.3-1 → 2.0.4-1
  • ros-iron-launch-pytest: 2.0.3-1 → 2.0.4-1
  • ros-iron-launch-testing: 2.0.3-1 → 2.0.4-1
  • ros-iron-launch-testing-ament-cmake: 2.0.3-1 → 2.0.4-1
  • ros-iron-launch-xml: 2.0.3-1 → 2.0.4-1
  • ros-iron-launch-yaml: 2.0.3-1 → 2.0.4-1
  • ros-iron-mola: 1.0.5-1 → 1.0.6-1
  • ros-iron-mola-bridge-ros2: 1.0.5-1 → 1.0.6-1
  • ros-iron-mola-bridge-ros2-dbgsym: 1.0.5-1 → 1.0.6-1
  • ros-iron-mola-demos: 1.0.5-1 → 1.0.6-1
  • ros-iron-mola-imu-preintegration: 1.0.5-1 → 1.0.6-1
  • ros-iron-mola-imu-preintegration-dbgsym: 1.0.5-1 → 1.0.6-1
  • ros-iron-mola-input-euroc-dataset: 1.0.5-1 → 1.0.6-1
  • ros-iron-mola-input-euroc-dataset-dbgsym: 1.0.5-1 → 1.0.6-1
  • ros-iron-mola-input-kitti-dataset: 1.0.5-1 → 1.0.6-1
  • ros-iron-mola-input-kitti-dataset-dbgsym: 1.0.5-1 → 1.0.6-1
  • ros-iron-mola-input-kitti360-dataset: 1.0.5-1 → 1.0.6-1
  • ros-iron-mola-input-kitti360-dataset-dbgsym: 1.0.5-1 → 1.0.6-1
  • ros-iron-mola-input-mulran-dataset: 1.0.5-1 → 1.0.6-1
  • ros-iron-mola-input-mulran-dataset-dbgsym: 1.0.5-1 → 1.0.6-1
  • ros-iron-mola-input-paris-luco-dataset: 1.0.5-1 → 1.0.6-1
  • ros-iron-mola-input-paris-luco-dataset-dbgsym: 1.0.5-1 → 1.0.6-1
  • ros-iron-mola-input-rawlog: 1.0.5-1 → 1.0.6-1
  • ros-iron-mola-input-rawlog-dbgsym: 1.0.5-1 → 1.0.6-1
  • ros-iron-mola-input-rosbag2: 1.0.5-1 → 1.0.6-1
  • ros-iron-mola-input-rosbag2-dbgsym: 1.0.5-1 → 1.0.6-1
  • ros-iron-mola-kernel: 1.0.5-1 → 1.0.6-1
  • ros-iron-mola-kernel-dbgsym: 1.0.5-1 → 1.0.6-1
  • ros-iron-mola-launcher: 1.0.5-1 → 1.0.6-1
  • ros-iron-mola-launcher-dbgsym: 1.0.5-1 → 1.0.6-1
  • ros-iron-mola-metric-maps: 1.0.5-1 → 1.0.6-1
  • ros-iron-mola-metric-maps-dbgsym: 1.0.5-1 → 1.0.6-1
  • ros-iron-mola-navstate-fuse: 1.0.5-1 → 1.0.6-1
  • ros-iron-mola-navstate-fuse-dbgsym: 1.0.5-1 → 1.0.6-1
  • ros-iron-mola-pose-list: 1.0.5-1 → 1.0.6-1
  • ros-iron-mola-pose-list-dbgsym: 1.0.5-1 → 1.0.6-1
  • ros-iron-mola-relocalization: 1.0.5-1 → 1.0.6-1
  • ros-iron-mola-relocalization-dbgsym: 1.0.5-1 → 1.0.6-1
  • ros-iron-mola-traj-tools: 1.0.5-1 → 1.0.6-1
  • ros-iron-mola-traj-tools-dbgsym: 1.0.5-1 → 1.0.6-1
  • ros-iron-mola-viz: 1.0.5-1 → 1.0.6-1
  • ros-iron-mola-viz-dbgsym: 1.0.5-1 → 1.0.6-1
  • ros-iron-mola-yaml: 1.0.5-1 → 1.0.6-1
  • ros-iron-mola-yaml-dbgsym: 1.0.5-1 → 1.0.6-1
  • ros-iron-mp2p-icp: 1.4.3-1 → 1.5.0-1
  • ros-iron-mp2p-icp-dbgsym: 1.4.3-1 → 1.5.0-1
  • ros-iron-mrpt2: 2.13.1-1 → 2.13.2-1
  • ros-iron-mrpt2-dbgsym: 2.13.1-1 → 2.13.2-1
  • ros-iron-openeb-vendor: 1.2.1-1 → 1.2.2-1
  • ros-iron-openeb-vendor-dbgsym: 1.2.1-1 → 1.2.2-1
  • ros-iron-rqt-tf-tree: 1.0.4-3 → 1.0.5-1
  • ros-iron-simple-launch: 1.9.2-1 → 1.10.0-1
  • ros-iron-swri-console: 2.0.4-1 → 2.0.5-1
  • ros-iron-swri-console-dbgsym: 2.0.4-1 → 2.0.5-1
  • ros-iron-teleop-twist-joy: 2.5.0-1 → 2.5.1-1
  • ros-iron-teleop-twist-joy-dbgsym: 2.5.0-1 → 2.5.1-1
  • ros-iron-ur: 2.3.7-1 → 2.3.8-1
  • ros-iron-ur-calibration: 2.3.7-1 → 2.3.8-1
  • ros-iron-ur-calibration-dbgsym: 2.3.7-1 → 2.3.8-1
  • ros-iron-ur-controllers: 2.3.7-1 → 2.3.8-1
  • ros-iron-ur-controllers-dbgsym: 2.3.7-1 → 2.3.8-1
  • ros-iron-ur-dashboard-msgs: 2.3.7-1 → 2.3.8-1
  • ros-iron-ur-dashboard-msgs-dbgsym: 2.3.7-1 → 2.3.8-1
  • ros-iron-ur-moveit-config: 2.3.7-1 → 2.3.8-1
  • ros-iron-ur-robot-driver: 2.3.7-1 → 2.3.8-1
  • ros-iron-ur-robot-driver-dbgsym: 2.3.7-1 → 2.3.8-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:

  • Aditya Pande
  • Alejandro Hernandez Cordero
  • Bernd Pfrommer
  • Denis Stogl
  • Felix Exner
  • Gerardo Puga
  • Isaac I.Y. Saito
  • Jose-Luis Blanco-Claraco
  • Justin Carpentier
  • Olivier Kermorgant
  • Southwest Research Institute

1 post - 1 participant

Read full topic

by Yadunund on June 28, 2024 06:14 PM

Introducing Foxglove integration with rosboard for real-time visualizations

Hi everyone!

At Kiwibot, we develop sidewalk delivery robots. As we continue to deploy an increasing number of Kiwibots worldwide, we realized the necessity for a robust remote debugging tool. While rosbags can be great for this purpose, they tend to become huge files that are hard to distribute and serve only for offline analysis. Often, it is useful to be able to debug the system online and in real-time. Such a tool would allow us to stream topics over a limited bandwidth LTE network connection between the robots and our remote personal computers to visualize and diagnose any problems easily.

Previously, we solved this by introducing the rosboard client. Nonetheless, this required our local setup to have all ROS dependencies installed and involved a cumbersome setup. Fortunately, there is Foxglove, a great web-based alternative that allows excellent debugging and visualization of ROS systems, all by just needing a browser. They offer streaming of topics by running either rosbridge_suite or foxglove_websocket_protocol on the robots’ side. This was our first option when testing, but it consumed a lot of bandwidth and accumulated significant latency over time, which was unsuitable for our case.

As discussed in our previous post, although rosboard was not originally designed for streaming over the Internet, we have seen it overcome these bandwidth and latency problems by relying on a set of subsampling and compression techniques. It requires few dependencies and is easily installable.

The Kiwibot team wanted to have the excellent visualization capabilities of Foxglove while keeping the data transfer advantages of rosboard’s networking protocol. For that reason, we are releasing our Foxglove fork and rosboard fork that were modified to:

  • Add an additional connection type to Foxglove to allow connection to a rosboard server.
  • Make small modifications on rosboard’s side to communicate with the Foxglove client.
  • Add a button to rosboard’s original interface to redirect to Foxglove’s for instant connection.

You can play with the foxglove version using our docker image from dockerhub and our mentioned rosboard fork. Caveat: at the moment we only support ROS2 systems.

foxglove_rosboard-ezgif.com-optimize

Example of using ngrok to make the robot available to the internet and then connect to the robot using Foxglove to visualize cameras, costmaps, pointcloud and navigation information

Thanks to this new tool, we can simultaneously stream several costmaps, laserscans, RGB images, paths, and transforms in near real-time over a bandwidth-limited LTE cellular network and visualize them using Foxglove without any issues.

With ngrok, you can effortlessly make the server on your robot’s local network accessible over the internet as shown in the demo video.

Credits to @franyol and @charlielito who made this integration possible. Credits to @dheera for developing the rosboard server and all the foxglove team for the amazing visualization tool.

We are thrilled to receive feedback from the community!

Happy debugging!

8 posts - 4 participants

Read full topic

by kiwibot-ai on June 28, 2024 05:15 PM

Results: Survey on Requirements for Toolchain to Achieve Robust Robot Deliberation

Dear ROS Developers of Autonomous Systems,

in the EU-funded project CONVINCE we wanted to get better insights on and determine requirements for our toolchain to achieve robust deliberation using: verification, planning, monitoring, and learning. Therefore, we advertised a short questionnaire in this thread to get more information on which deliberation language, logic, and engine they are working with and what their needs, problems, etc. are.

We are now able to release the results of the survey. An overview can be found on our website and the detailed answers are available here.

In case of interest, we can also share the raw files of the survey with you.

We hope that the results are also interesting for you and give you more insights on the current needs in the community.

Best,
Michaela

2 posts - 1 participant

Read full topic

by Michaela.Klauck on June 28, 2024 01:47 PM


Powered by the awesome: Planet