Planet ROS

Planet ROS - http://planet.ros.org

Planet ROS - http://planet.ros.org http://planet.ros.org

ROS Discourse General: Issues Simulating Parallel Manipulator in Gazebo Harmonic: Joint Parent Conflict

Hi all,

I’m working on simulating a parallel manipulator (a Stewart platform) using Gazebo Harmonic and running into issues related to joint definitions and model structure. I hope someone can help clarify what’s going wrong or suggest a workaround.

Problem Summary

When I launch my simulation, I get errors related to joint creation, specifically about a child link already having a parent joint. This seems to be a problem with the closed-loop kinematics in my SDF model.

model.sdf

<?xml version="1.0"?>
<sdf version="1.9">
  <model name="closed_loop_arm">
    <link name="base_link">
      <pose>0 0 0 0 0 0</pose>
      <inertial>
        <mass>1.0</mass>
        <inertia>
          <ixx>0.01</ixx>
          <ixy>0.0</ixy>
          <ixz>0.0</ixz>
          <iyy>0.01</iyy>
          <iyz>0.0</iyz>
          <izz>0.01</izz>
        </inertia>
      </inertial>
      <visual name="visual">
        <geometry>
          <box>
            <size>0.2 0.2 0.1</size>
          </box>
        </geometry>
        <material>
          <ambient>0.2 0.2 0.2 1</ambient>
          <diffuse>0.2 0.2 0.2 1</diffuse>
          <specular>0.2 0.2 0.2 1</specular>
        </material>
      </visual>
      <collision name="collision">
        <geometry>
          <box>
            <size>0.2 0.2 0.1</size>
          </box>
        </geometry>
      </collision>
      <enable_wind>false</enable_wind>
    </link>

    <link name="arm1_link">
      <pose relative_to="base_link">0.1 0 0.05 0 0 0</pose>
      <inertial>
        <mass>0.5</mass>
        <inertia>
          <ixx>0.005</ixx>
          <ixy>0.0</ixy>
          <ixz>0.0</ixz>
          <iyy>0.005</iyy>
          <iyz>0.0</iyz>
          <izz>0.005</izz>
        </inertia>
      </inertial>
      <visual name="visual">
        <geometry>
          <cylinder>
            <radius>0.03</radius>
            <length>0.8</length>
          </cylinder>
        </geometry>
        <pose>0 0 0.4 0 0 0</pose>
        <material>
          <ambient>0.0 0.0 0.8 1</ambient>
          <diffuse>0.0 0.0 0.8 1</diffuse>
          <specular>0.0 0.0 0.8 1</specular>
        </material>
      </visual>
      <collision name="collision">
        <geometry>
          <cylinder>
            <radius>0.03</radius>
            <length>0.8</length>
          </cylinder>
        </geometry>
        <pose>0 0 0.4 0 0 0</pose>
      </collision>
    </link>

    <joint name="joint1" type="revolute">
      <parent>base_link</parent>
      <child>arm1_link</child>
      <pose relative_to="base_link">0.1 0 0.05 0 0 0</pose>
      <axis>
        <xyz>0 0 1</xyz>
      </axis>
      <limit>
        <lower>-1.57</lower>
        <upper>1.57</upper>
      </limit>
    </joint>

    <link name="arm2_link">
      <pose relative_to="base_link">-0.1 0 0.05 0 0 0</pose>
      <inertial>
        <mass>0.5</mass>
        <inertia>
          <ixx>0.005</ixx>
          <ixy>0.0</ixy>
          <ixz>0.0</ixz>
          <iyy>0.005</iyy>
          <iyz>0.0</iyz>
          <izz>0.005</izz>
        </inertia>
      </inertial>
      <visual name="visual">
        <geometry>
          <cylinder>
            <radius>0.03</radius>
            <length>0.8</length>
          </cylinder>
        </geometry>
        <pose>0 0 0.4 0 0 0</pose>
        <material>
          <ambient>0.8 0.0 0.0 1</ambient>
          <diffuse>0.8 0.0 0.0 1</diffuse>
          <specular>0.8 0.0 0.0 1</specular>
        </material>
      </visual>
      <collision name="collision">
        <geometry>
          <cylinder>
            <radius>0.03</radius>
            <length>0.8</length>
          </cylinder>
        </geometry>
        <pose>0 0 0.4 0 0 0</pose>
      </collision>
    </link>

    <joint name="joint2" type="revolute">
      <parent>base_link</parent>
      <child>arm2_link</child>
      <pose relative_to="base_link">-0.1 0 0.05 0 0 0</pose>
      <axis>
        <xyz>0 0 1</xyz>
      </axis>
      <limit>
        <lower>-1.57</lower>
        <upper>1.57</upper>
      </limit>
    </joint>

    <link name="platform_link">
      <pose relative_to="arm1_link">0 0 0.8 0 0 0</pose>
      <inertial>
        <mass>0.8</mass>
        <inertia>
          <ixx>0.05</ixx>
          <ixy>0.0</ixy>
          <ixz>0.0</ixz>
          <iyy>0.05</iyy>
          <iyz>0.0</iyz>
          <izz>0.05</izz>
        </inertia>
      </inertial>
      <visual name="visual">
        <geometry>
          <box>
            <size>0.3 0.1 0.05</size>
          </box>
        </geometry>
        <pose>0.15 0 -0.025 0 0 0</pose>
        <material>
          <ambient>0.8 0.8 0.0 1</ambient>
          <diffuse>0.8 0.8 0.0 1</diffuse>
          <specular>0.8 0.8 0.0 1</specular>
        </material>
      </visual>
      <collision name="collision">
        <geometry>
          <box>
            <size>0.3 0.1 0.05</size>
          </box>
        </geometry>
        <pose>0.15 0 -0.025 0 0 0</pose>
      </collision>
      <enable_wind>false</enable_wind>
    </link>

    <joint name="joint3" type="revolute">
      <parent>arm1_link</parent>
      <child>platform_link</child>
      <pose relative_to="arm1_link">0 0 0.8 0 0 0</pose>
      <axis>
        <xyz>0 1 0</xyz>
      </axis>
    </joint>

    <joint name="joint4" type="revolute">
      <parent>arm2_link</parent>
      <child>platform_link</child>
      <pose relative_to="arm2_link">0 0 0.8 0 0 0</pose>
      <axis>
        <xyz>0 1 0</xyz>
      </axis>
    </joint>
  </model>
</sdf>

platform_test.sdf

<?xml version="1.0"?>
<sdf version="1.9">
  <world name="default">
    <physics type="dart" default="true">
      <max_step_size>0.001</max_step_size>
      <real_time_factor>1</real_time_factor>
      <real_time_update_rate>1000</real_time_update_rate>
    </physics>

    <gravity>0 0 -9.81</gravity>

    <plugin
      filename="libgz-sim-physics-system.so"
      name="gz::sim::systems::Physics">
    </plugin>
    <plugin
      filename="libgz-sim-user-commands-system.so"
      name="gz::sim::systems::UserCommands">
    </plugin>
    <plugin
      filename="libgz-sim-scene-broadcaster-system.so"
      name="gz::sim::systems::SceneBroadcaster">
    </plugin>

    <include>
      <uri>https://fuel.gazebosim.org/1.0/OpenRobotics/models/Ground Plane</uri>
    </include>

    <include>
      <uri>https://fuel.gazebosim.org/1.0/OpenRobotics/models/Sun</uri>
    </include>

    <include>
      <uri>model://stewart</uri>
      <name>stewart</name>
      <pose>0 0 0.2 0 0 0</pose>
    </include>

  </world>
</sdf>

Error Message

Here is the relevant error from the log:

[Err] [SDFFeatures.cc:1111] Asked to create a joint between links [arm2_link] as parent and [platform_link] as child, but the child link already has a parent joint of type [RevoluteJoint].
[Wrn] [EntityManagementFeatures.cc:469] No joint named [joint4] for modelID [5]
[Err] [SDFFeatures.cc:1111] Asked to create a joint between links [arm2_link] as parent and [platform_link] as child, but the child link already has a parent joint of type [RevoluteJoint].

Question

Is there a way to model closed-loop kinematics (parallel manipulators) in SDF for Gazebo Harmonic?
Is there a workaround or plugin that allows multiple parent joints for a single link, or a way to “mimic” this behavior for simulation purposes?
Any advice on how to restructure the model to avoid this error, or pointers to example Stewart platform models that work with Gazebo Harmonic?

Thanks in advance for your help!

1 post - 1 participant

Read full topic

https://discourse.ros.org/t/issues-simulating-parallel-manipulator-in-gazebo-harmonic-joint-parent-conflict/43570

ROS Discourse General: Energy efficiency in ROS communication: a comparison across programming languages and workloads

Hello folks,
I was wondering if this paper would be of interest for some people here:
“Energy efficiency in ROS communication: a comparison across programming languages and workloads”

Front. Robot. AI, 02 April 2025
Sec. Computational Intelligence in Robotics
Volume 12 - 2025 | DOI: Frontiers | Energy efficiency in ROS communication: a comparison across programming languages and workloads

TD;DR:
Introduction: The Robot Operating System (ROS) is a widely used framework for robotic software development, providing robust client libraries for both C++ and Python. These languages, with their differing levels of abstraction, exhibit distinct resource usage patterns, including power and energy consumption–an increasingly critical quality metric in robotics.

Methods: In this study, we evaluate the energy efficiency of ROS two nodes implemented in C++ and Python, focusing on the primary ROS communication paradigms: topics, services, and actions. Through a series of empirical experiments, with programming language, message interval, and number of clients as independent variables, we analyze the impact on energy efficiency across implementations of the three paradigms.

Results: Our data analysis demonstrates that Python consistently demands more computational resources, leading to higher power consumption compared to C++. Furthermore, we find that message frequency is a highly influential factor, while the number of clients has a more variable and less significant effect on resource usage, despite revealing unexpected architectural behaviors of underlying programming and communication layers.

4 posts - 4 participants

Read full topic

https://discourse.ros.org/t/energy-efficiency-in-ros-communication-a-comparison-across-programming-languages-and-workloads/43553

ROS Discourse General: How should sensor descriptions be standardized?

Hello.
I’m developing the Tools to use Isaac Sim as an alternative to Gazebo.

Isaac Sim

I created a Unity-based simulator based on the simulation_interfaces completed in the issue.

Unity-based Simulator - sample

What I am concerned about is how to spawn the sensor models. In Gazebo, sensor information was specified using the <gazebo> tag in URDF. Following that, in Unity, I used the <unity> tag, and in Isaac Sim, I used the <isaac> tag. However, if we are aiming for a common interface, shouldn’t the description of the sensor models also be standardized?

1 post - 1 participant

Read full topic

https://discourse.ros.org/t/how-should-sensor-descriptions-be-standardized/43550

ROS Discourse General: Organizing a ROS Meetup in Boston

Update!

If you are lurking or have not yet responded, please do so! You can be one of the founders of this new group and help decide what it will be about. Show your interest by responding to this post!

Notice

My background is as a professional software engineer, who switched careers late to academia where I taught computer science and software engineering for years. Over time I got involved with Robotics, teaching it, learning with students, and spending a lot of my personal time learning more and more.

I live in Boston. I belong to a super-smart ROS users group in California. They are a wonderful bunch of hands on experimenters with all kinds of robots. Most of us are doing it as a hobby/obsession. We have a very active mailing list, and regular meetings.

I am looking to join or organize something similar in the Boston area so the members can be in the Boston timezone.

Any leads for existing groups? Any interest in joining one?

11 posts - 10 participants

Read full topic

https://discourse.ros.org/t/organizing-a-ros-meetup-in-boston/43537

ROS Discourse General: Actuate 2025 - Call for Presentations

Last week we publicly announced this year’s Actuate conference! It will be hosted in San Francisco at the SFJAZZ on September 23rd and 24th.

We moved to a 2-day format based on speaker demand from last year, and have an already stellar lineup of speakers.

There are 12 presentation slots still open that we plan to fill on a rolling-basis over the next 4 months. If you’re interested in presenting, click the link at the top of the website: actuate.foxglove.dev

20-minute presentation slots
technical presentation targeting robotics developers
focused on workflows, challenges, and breakthroughs related to commercializing/scaling autonomous robotics

If you have any questions, you can also reach out to us directly: actuate@foxglove.dev

Hope to see a lot of you there!

4 posts - 4 participants

Read full topic

https://discourse.ros.org/t/actuate-2025-call-for-presentations/43514

ROS Discourse General: ROS News for the Week of April 28th, 2025

ROS News for the Week of April 28th, 2025

KiltedTestFinal
The Kilted Kaiju Test and Tutorial Party is live! We would really appreciate your help testing Kilted ahead of the release on May 23rd! Our top 20 testers will get their choice of OSRA membership or ROS swag.

Kilted Kaiju swag sale is now live. Pick up a shirt, show your ROS pride, and help support our open source projects!

This week we’re happy to announce three new ROS meetups! One in Nivelles, Belgium, one in Lagos, Nigeria, and one in New York City.

If you are headed to Automate in Detroit, we have ROS meetup planned for Tuesday, May 13th sponsored by ROS-Industrial and and Picknik. Both Automate and the meetup are free and open to everyone! If you are within driving distance of Detroit we recommend you attend!

output
Check out this really impressive project: ROSplat an Online, ROS 2 Based, Gaussian Splat Visualizer. ROS finally has a gaussian splat visualizer!

quad
This week I came across this really impressive quadruped robot project put together by
Bontalakoti Harshavardhan at the National Institute of Technology Silchar. Check out the video here.

For over a decade the Oregon State University Open Source Lab (OSUOSL) has hosted all of our ROS websites and most of our ROS binaries, along with numerous other open source projects. They seem to be having some funding difficulties and are looking for additional financial support from the open source community. If you or your employer are in a position to help them out it would be greatly appreciated!

Events

News

ROS

Got a Minute?

It was a really busy week this week! The core team was mostly occupied getting the Kilted Beta out the door. I have three issues from the ROS / Gazebo PMC meetings where we would appreciate the community pitching in some developement time.

2 posts - 2 participants

Read full topic

https://discourse.ros.org/t/ros-news-for-the-week-of-april-28th-2025/43511

ROS Discourse General: Kilted Kaiju Swag Sale :t_shirt:

Kilted Kaiju Swag Sale!

Hi Folks,

It is that time of year already! The Kilted Kaiju swag sale is now open.

All of our swag is available at spring.ros.org.

This time around we’re making the following swag available:

T-shirts for men, women, children, and infants in multiple colors.
Long sleeve t-shirts
Sweatshirts
Beach slides
Water bottles
STICKERS
Desk mats
Tote bags
Water bottles
Mugs

If you order today you’ll probably get your swag by release day!

All proceeds go to support the Open Source Robotics Foundation!

6 posts - 3 participants

Read full topic

https://discourse.ros.org/t/kilted-kaiju-swag-sale/43495

ROS Discourse General: Kilted Kaiju Test and Tutorial Party Instructions

Kilted Kaiju Test and Tutorial Party Instructions

Hi Everyone,

As mentioned previously, we’re conducting a testing and tutorial party for the next ROS release, Kilted Kaiju. If you happened to miss the kickoff of the Kilted Kaiju Testing and Tutorial party (video) this morning I have put together some written instructions that should let everyone, no matter their time zone, participate.

TL;DR

We need your help to test the next ROS Distro before its release on 5/23/2025. We’re asking the community to pick a particular system setup, that is to say a combination of host operating system, CPU architecture, RMW vendor, and build type (source, debian, binary), and run through a set of ROS tutorials to make sure everything is working smoothly. Depending on the outcome of your tutorials you can either close the ticket or report the errors you found. If you can’t assign the ticket to yourself leave a comment and an admin will take care of it for you. Please do not sign up for more than one ticket at any given time. Everything you need to know about this process to know can be found in this Github repository.

As a thank you for your help we’re planning to provide the top twenty people who contribute to the testing repository with their choice of either ROS Kilted swag or OSRA membership. To be eligible to receive swag you must register using this short Google Form so we can match e-mail addresses to Github user names and count the total tickets closed.

The testing and tutorial party will close on 2025-05-15T07:00:00Z UTC, but we’re asking everyone to get started right away!

Full Instructions

We’re planning to release ROS 2 Kilted Kaiju on May 23, 2025 and we need the community’s help to make sure that we’ve thoroughly tested the distro on a variety of platforms before we make the final release. What do we mean by testing? Well, lots of things, but in the context of the testing and tutorial party we are talking about the package-level ROS unit tests and anything else you want to test. What do we mean by tutorials? We also want to make sure all our ROS tutorials are in working order before the release.

The difficulty in testing a ROS release is that people have lots of different ways they use ROS, and we can’t possibly test all of those combinations. For the testing and tutorial party we have created what we call, “a setup.” A setup is a combination of:

DDS vendor: FASTDDS, CYCLONEDDS, CONNEXTDDS or ZENOH
BuildType: binary, debian or source
Os: Ubuntu Noble, Windows and RHEL-9
Chipset: Amd64 or Arm64

If you already have a particular system setup that you work with, we suggest that you roll with that, otherwise feel free to create a new system setup just for testing purposes. If you normally use Windows or RHEL (or binary compatible distributions to RHEL like Rocky Linux / Alma Linux) we would really appreciate your help as we don’t have a ton of internal resources to test these distributions.

Here are the steps for participating in the testing and tutorial party:

Please fill out the Google form for your first issue so we have your contact information.
First go to the Tutorial Party Github repo and read the README.md.
Figure out your setup!
Note your computer’s host operating system (either Ubuntu Nobel, Windows, or RHEL-9)
Note your chipset, either AMD64 or ARM64, if you don’t know it is probably AMD64.
Note your installed DDS Vendor (this varies by host OS).
Figure out how you want to install the ROS Kilted Kaiju Beta, your options are:
- Binaries
- Source installation
- Docker – see below
Once you’ve got your “setup” all figured out take a look at the open tickets in the tutorial repo (at the bottom of the page). There should be a set of tickets for your “setup”. Click on the links and review the available tickets. If you want to test something other than the available tickets, feel free to open a new ticket and describe exactly what you are testing.
Pick a single ticket for your setup and use the assignees option to assign it to yourself. If you can’t assign yourself, leave a comment and an admin will assign the ticket to you
Take a look at the ticket and do as it asks in the “Links” section. For example, in this ticket, its links section points you to this tutorial. You should use your new ROS Kilted Kaiju setup to run through that tutorial.
Once you complete the links section things will either go smoothly or you will run into problems. Please indicate the results using the check boxes in the “Checks” section of your Github issue.
If everything goes well, note as such in your ticket’s comment section. We ask that you attach your terminal’s output as a code block or as a gist file. At this point feel free to close the ticket by clicking “close as completed.”
If something went poorly, also note it in your ticket’s comment section. Please include a full stack trace or other debug output if possible. You can use the discussion board or our Discord channel to report issues. To join the Discord server use this link.

If you run into issues please feel free to post them to our discussion board on Github. The testing and tutorial party wraps up on May 15, 2025 , but we’re asking everyone to get started early as we will need some lead time to address any bugs.

Happy testing and thanks for all your help! If you have any questions please include them in the comments.

Docker Containers

As discussed last year, Shane and Martin have worked hard to create ROS Open Container Initiative (OCI) Docker Images for all supported ROS distros. These unofficial OCI Docker images already have a beta version of Kilted Kaiju ready to go.

Try ROS Kilted out on your machine by running:

docker run --rm=true -ti ghcr.io/sloretz/ros-testing:kilted-desktop bash

The images are updated every 6 hours. Keep your copy up to date by running:

docker pull ghcr.io/sloretz/ros-testing:kilted-desktop

We encourage you to use these containers to participate in the T&T Party, or to test Kilted with your existing ROS project. The official docker images will be available shortly after the Kilted release.

If you run into issues with Kilted while using these images or containers to test your personal codebase please use our Kilted issue tracker to report them.

3 posts - 1 participant

Read full topic

https://discourse.ros.org/t/kilted-kaiju-test-and-tutorial-party-instructions/43483

ROS Discourse General: ROS 2 Kilted Beta and Call for Testing

We’re in the “beta” phase of development for ROS 2 Kilted Kaiju! As such, there are now binary packages available for Ubuntu Noble and RHEL 9, and rosdistro is open for newly released packages for Kilted.

Testing the Kilted beta

Installation instructions have been published for Kilted here. The only notable deviation from these instructions is that binary packages for Kilted have not had the first “sync”, and are therefore only available in the testing repository.

The pre-release testing instructions describe how to enable the ros-testing repository so that you can install the ros-kilted-* packages.

For those using the comprehensive archive for installation or are building from source, we’ve also provided a pre-release tag which includes fresh binary builds of the ROS 2 Kilted Beta.

If you’re having trouble or think you’ve discovered a bug, please check the open issues and PRs on the related repository, discuss the issue in this thread, and open a new issue as appropriate. We’ll triage the issue or PR and decide if it should be merged prior to release or backported for a subsequent patch release of Kilted.

Releasing your packages

If you maintain a package you would like to release in ROS 2 Kilted Kaiju we encourage you to do so by following the guide to releasing a ROS 2 package with bloom .

Reminder that the tutorial party is starting 2025-05-01T07:00:00Z UTC. You can find all the details in this post.

Thanks!

The ROS 2 Team

1 post - 1 participant

Read full topic

https://discourse.ros.org/t/ros-2-kilted-beta-and-call-for-testing/43477

ROS Discourse General: Java based ROS2 controller for Dorna2 robotic arm

This document focuses on a new jros2control Java module which allows direct integration of robots with ROS2 (Robot Operating System), avoiding writing JNI libraries for ros2_control and implementing C++ Hardware Component interface. jros2control is part of the jrosclient ecosystem of packages for interacting with ROS from Java.

Additionally, this document describes the process of integrating a physical Dorna2 robotic arm with ROS2 through jros2control.

Integrating robots with ROS2

The standard method for integrating robots with ROS2 is by utilizing ros2_control. However, using jros2control can provide additional benefits due to its Java-based nature.

Using ros2_control (standard way)

ros2_control serves as a bridge between physical robots (robotic arms, autonomous mobile robots, …) and ROS2 ecosystem (MoveIt2, Nav2, …).

ros2_control comes with different controllers already available for variety type of robots:

wheeled mobile robots - differential drive controller, mecanum drive controller, …
robot manipulators - forward command controller, joint trajectory controller, …

To integrate physical robot with any of the existing ros2_control controllers users suppose to implement C++ Hardware Component interface for the controller they want to use.

Many robots already come with ros2_control integration available (see list of supported robots)

Using jros2control

jros2control tries to extend some of the ideas behind ros2_control to the Java world. Instead of implementing C++ interfaces, defining JNI bindings to them and then packaging all of that separately from the Java application, with jros2control users can implement Java interfaces and use them directly inside the Java application to control the robots.

jros2control controllers are independent from ros2_control controllers, they are completely Java based and run same ROS2 Subscriber/Publisher/Service/Action which ordinary ros2_control controllers do. This allows other ROS2 components (like MoveIt2 etc) to interact with jros2control controllers as they normally do with any of the ros2_control controllers.

jros2control is not meant to be a replacement for ros2_control, users can have some robots in the fleet operating with ros2_control and others with jros2control.

Currently jros2control supports only one controller (joint trajectory controller).

Supported ROS2 versions

Humble Hawksbill

Supported RMW:

To implement ROS2 Action Servers and Services jros2control depends on jros2services. This means that jros2control supports only those RMW which are supported by jros2services.
- NOTE: jros2services supports DDS-RPC, which supposed to be implemented by all DDS RMW implementations (see Services and Actions). Unfortunately, as of Jazzy, only FastDDS implements DDS-RPC. As more RMW migrate to DDS-RPC the jros2services can be extended to support them too.

Introduction to r2d2 package for Dorna2 arms

Dorna2 robotic arm does not have support for ROS2 controllers. The existing controllers which are available all target ROS1:

This document gives overview of a new ROS2 package for Dorna2 arms called r2d2 (ros2dorna2)

r2d2 uses jros2control to integrate Dorna2 with ROS2 and it consists from the following list of standard ROS packages (which most of the ROS users are familiar already):

r2d2_urdf - URDF definitions for Dorna2 robotic arm (The original URDF was taken from Perceptive-Pick-And-Place-Robot)
r2d2_moveit_config - package contains MoveIt2 configuration files for Dorna2 robotic arm
r2d2_servo - package contains MoveIt2 Servo node for Dorna2 robotic arm
r2d2_control - package with all the ROS controller logic implemented using jros2control. This package is the main focus of the next paragraphs.

r2d2_control

r2d2_control is a hybrid package: aside from containing all ROS package required files (“package.xml”, “CMakeLists.txt”, etc.) it is also a Java Gradle project and comes with “build.gradle” and Java classes.

The Gradle project inside r2d2_control builds a standalone Java CLI application, which when started runs ROS2 controller. Gradle is not required to use jros2control, users can similarly use any other Java build system (Maven etc.)

r2d2_control standalone application is integrated with ROS Launch system, so it is started automatically, together will all other r2d2 ROS components:

      ...
      # Run Java based r2d2_control controller
      # Make sure to build r2d2_control package by following instructions inside it
      # See r2d2_control documentation for all supported options
      ExecuteProcess(
        cmd=['java',
             '-jar', PathJoinSubstitution([control_folder, "libs", "r2d2_control.jar"]),
             '-moveItConfigPath=' + str(moveit_config.package_path),
             '-debug=true'],
        output='screen'),
      ...

See complete r2d2_launch.py for more details.

Most important code of r2d2_control is where the ActuatorHardware is implemented and then passed to jros2control controller JointTrajectoryController through the factory class JointTrajectoryControllerFactory:

        ActuatorHardware dornaJointStateSender =
                jointState -> {
                    dornaClient.jmove(
                            Joints.ofRadians(jointState.positions()),
                            false,
                            true,
                            true,
                            dornaConfig.velocity(),
                            dornaConfig.acceleration(),
                            dornaConfig.jerk());
                };
        var controllers = List.of(dornaJointStateSender);
        // use configBuilder to override default parameters (network interface, RTPS settings etc)
        try (var client = new JRos2ClientFactory().createClient(configBuilder.build());
                var jointStateBroadcaster =
                        new JointStateBroadcaster(
                                client,
                                joints,
                                Optional.of(() -> toJointState(dornaClient.getLastMotion())),
                                broadcasterRate);
                var controller =
                        new JointTrajectoryControllerFactory()
                                .create(
                                        client,
                                        controllers,
                                        joints,
                                        initialPositions,
                                        controllerName); ) {
            jointStateBroadcaster.start();
            controller.start();
            CommandLineInterface.cli.askPressEnter();
        }

Demonstration

The demonstration consists from two use cases where we control the Dorna2 arm with:

teleops - CLI application which sends commands to MoveIt2 Servo
MoveIt Planning plugin (inside RViz) which sends commands to MoveIt2

In both cases, all MoveIt2 components interact with r2d2_control to control the robot. The entire flow looks like this:

Demonstration videos

Servoing the Dorna robotic arm with teleops

r2d2: servoing the Dorna robotic arm with teleops

Planning and executing trajectories with MoveIt MotionPlanning plugin

r2d2: planning and executing trajectories with MoveIt MotionPlanning plugin

1 post - 1 participant

Read full topic

https://discourse.ros.org/t/java-based-ros2-controller-for-dorna2-robotic-arm/43476

ROS Industrial: ROS-Industrial Roadmap Journey and a Path Forward

The previous significant update to the ROS-Industrial roadmap centered mainly on the technical capabilities in various areas, aiming to create a vibrant open-source robotics development ecosystem. The main challenge was the lack of detail regarding when these capabilities would become available, in an ever-changing technological landscape.

Since then, a more generalized vision has been shared, focusing on four broad areas of interest: Ease of Use, Advanced Capability, Interoperability, and Human Interface & Reaction. However, the challenge of integrating a time component and actual deliverables has persisted.

Vision for ros-i based on four pillars of ease of use, advanced capability, interoperability, and human robot interaction

Over the years, member and community feedback has aligned with these four pillars. We have been collaborating with members to improve and distill these elements into manageable components that can be delivered within a reasonable timeframe. The requests from the 2023 ROS-Industrial workshops reflect this ongoing effort.

community feedback via regular workshops

In recent years there has been a pivot to think more towards building frameworks and modular components that enable applications to be developed with minimal custom code. The vision is a toolbox of intuitive and useful robotics modules, exemplified by the Scan-N-Plan initiative. This approach has led to more reusable code and greater flexibility.

The ROS-Industrial project has always sought to bring forward usable open source tools, but now with helping to improve the developer experience by:

Providing clear and cohesive concepts/interfaces
Offering easy-to-build and customizable modules
Ensuring decent documentation
Making it relatively simple to create specific applications

Projects such as behavior tree, Open3D, and ros2_control have demonstrated this replicable experience.

An example demonstrating this approach is Tesseract , a motion planning framework for industrial processing applications. Tesseract offers:

Abstract interfaces for core capabilities
Planning pipelines and capabilities as modules
Customizable plugins
Complex task pipelines
Meta-planning and visualization tools

Similarly, the noether repository for tool path planning has evolved to include:

Clear and cohesive interfaces
Numerous out-of-the-box capability modules
Mesh modification tools, tool path planners, and modifiers
Available graphical user interface and quick pipeline configurations
Customization and front-end presentation capabilities
Tutorials from the 2024 ROSCon workshop

And now Tesseract and noether also both include development checklsts towards release milestones or a roadmap, enabling improved visibility and collaboration on capability progression.

Progress through collaboration

The Robotic Blending Milestone 5 Focused Technical Project , sponsored by the Steel Foundersâ€™ Society of America, recently demonstrated significant advancements by leveraging and improving modularity. Key achievements of this program include:

Successful deployment at three sites with three distinct hardware setups:
- Fisher Cast Steel (end-user)
- Iowa State University (ISU)
- Southwest Research Institute (SwRI)
Creation of an application example
Integration of contributions from ISU
Enhancement of capabilities and documentation for modules

Future Direction

We have begun the work to move towards the release of modules and frameworks with clearly defined, trackable lists of items to be completed before release. These module releases will include comprehensive documentation and additional basic application examples that may serve as templates. Additionally, we aim to create best practice documents, including guidelines for OEM Driver Creation.

Global Collaboration and Synergy

Global collaboration strategy developed by RIC AP and agreed upon in 2024

This progress aligns with the global collaboration vision developed and shared in 2024 within each ROS-Industrial Consortia region. The ROS-Industrial Consortia Global Workplan, developed by the ROS-Industrial Asia-Pacific team in late 2024, highlights areas of synergy across regions. This plan seeks to optimize outcomes for all members by reducing redundancy and making efficient use of global resources.

Community Engagement

The updated ROS-Industrial roadmap will be a central focus at the upcoming 2025 RIC Americas Annual Meeting. We encourage current members and those interested in membership to participate in this event. There will be opportunities for broader community engagement and feedback following the publication of the workshop outcomes.

A living vision and roadmap

We look forward to working with the global consortia supporting ROS-Industrial, our open source collaborators, and the broader community. Our goal is to continuously improve ROS-Industrial resources. We recognize that a dynamic program requires a living vision and roadmap, so stay tuned for updates and new capabilities that align with the evolving roadmap.

Once again, we extend our gratitude to those who have supported the ROS-Industrial open source project and everyone who has contributed to enhancing open source for industry.

https://rosindustrial.org/news/2025/4/30/ros-industrial-roadmap-journey-and-a-path-forward

ROS Discourse General: Next Client Library WG Meeting: Friday 2nd May 2025 8AM PT

Hi,

The next meeting of the Client Library Working Group will be this Friday, 4th April 2025 at 8 AM Pacific Time.

Meeting link: https://meet.google.com/oij-atzj-znw
Meeting minutes and agenda: ROS 2 Client Libraries Working Group - Google Docs
Google group if you want to be notified of future meetings: https://groups.google.com/g/ros-2-client-library-wg

Everyone is welcome to join and bring their own topics for discussion, just add them to the agenda!

1 post - 1 participant

Read full topic

https://discourse.ros.org/t/next-client-library-wg-meeting-friday-2nd-may-2025-8am-pt/43471

ROS Discourse General: New packages and patch release 5 for Jazzy Jalisco 2025-04-30

We’re happy to announce 46 new packages and 567 updates are now available on Ubuntu Noble on amd64 for Jazzy Jalisco.

This sync was tagged as jazzy/2025-04-30 .

Package Updates for jazzy

Added Packages [46]:

ros-jazzy-autoware-internal-metric-msgs: 1.8.1-1
ros-jazzy-autoware-internal-metric-msgs-dbgsym: 1.8.1-1
ros-jazzy-autoware-msgs: 1.6.0-1
ros-jazzy-depth-obstacle-detect-ros: 2.0.0-1
ros-jazzy-depth-obstacle-detect-ros-dbgsym: 2.0.0-1
ros-jazzy-depth-obstacle-detect-ros-msgs: 2.0.0-1
ros-jazzy-depth-obstacle-detect-ros-msgs-dbgsym: 2.0.0-1
ros-jazzy-diagnostic-remote-logging: 4.2.3-1
ros-jazzy-diagnostic-remote-logging-dbgsym: 4.2.3-1
ros-jazzy-etsi-its-mcm-uulm-coding: 3.2.0-1
ros-jazzy-etsi-its-mcm-uulm-coding-dbgsym: 3.2.0-1
ros-jazzy-etsi-its-mcm-uulm-conversion: 3.2.0-1
ros-jazzy-etsi-its-mcm-uulm-msgs: 3.2.0-1
ros-jazzy-etsi-its-mcm-uulm-msgs-dbgsym: 3.2.0-1
ros-jazzy-fkie-message-filters: 3.0.2-1
ros-jazzy-fkie-message-filters-dbgsym: 3.0.2-1
ros-jazzy-gps-sensor-broadcaster: 4.23.0-1
ros-jazzy-gps-sensor-broadcaster-dbgsym: 4.23.0-1
ros-jazzy-hatchbed-common: 0.1.2-1
ros-jazzy-laser-segmentation: 3.0.4-1
ros-jazzy-laser-segmentation-dbgsym: 3.0.4-1
ros-jazzy-log-view: 0.2.5-1
ros-jazzy-log-view-dbgsym: 0.2.5-1
ros-jazzy-om-joint-trajectory-command-broadcaster: 3.2.1-1
ros-jazzy-om-joint-trajectory-command-broadcaster-dbgsym: 3.2.1-1
ros-jazzy-open-manipulator-bringup: 3.2.1-1
ros-jazzy-open-manipulator-description: 3.2.1-1
ros-jazzy-open-manipulator-gui: 3.2.1-1
ros-jazzy-open-manipulator-gui-dbgsym: 3.2.1-1
ros-jazzy-open-manipulator-moveit-config: 3.2.1-1
ros-jazzy-open-manipulator-playground: 3.2.1-1
ros-jazzy-open-manipulator-playground-dbgsym: 3.2.1-1
ros-jazzy-open-manipulator-teleop: 3.2.1-1
ros-jazzy-open-sound-control: 0.0.2-1
ros-jazzy-open-sound-control-bridge: 0.0.2-1
ros-jazzy-open-sound-control-msgs: 0.0.2-1
ros-jazzy-open-sound-control-msgs-dbgsym: 0.0.2-1
ros-jazzy-turtlebot3: 2.2.9-1
ros-jazzy-turtlebot3-bringup: 2.2.9-1
ros-jazzy-turtlebot3-cartographer: 2.2.9-1
ros-jazzy-turtlebot3-description: 2.2.9-1
ros-jazzy-turtlebot3-example: 2.2.9-1
ros-jazzy-turtlebot3-navigation2: 2.2.9-1
ros-jazzy-turtlebot3-node: 2.2.9-1
ros-jazzy-turtlebot3-node-dbgsym: 2.2.9-1
ros-jazzy-turtlebot3-teleop: 2.2.9-1

Updated Packages [567]:

ros-jazzy-ackermann-steering-controller: 4.22.0-1 → 4.23.0-1
ros-jazzy-ackermann-steering-controller-dbgsym: 4.22.0-1 → 4.23.0-1
ros-jazzy-admittance-controller: 4.22.0-1 → 4.23.0-1
ros-jazzy-admittance-controller-dbgsym: 4.22.0-1 → 4.23.0-1
ros-jazzy-ament-cmake: 2.5.3-1 → 2.5.4-1
ros-jazzy-ament-cmake-auto: 2.5.3-1 → 2.5.4-1
ros-jazzy-ament-cmake-core: 2.5.3-1 → 2.5.4-1
ros-jazzy-ament-cmake-export-definitions: 2.5.3-1 → 2.5.4-1
ros-jazzy-ament-cmake-export-dependencies: 2.5.3-1 → 2.5.4-1
ros-jazzy-ament-cmake-export-include-directories: 2.5.3-1 → 2.5.4-1
ros-jazzy-ament-cmake-export-interfaces: 2.5.3-1 → 2.5.4-1
ros-jazzy-ament-cmake-export-libraries: 2.5.3-1 → 2.5.4-1
ros-jazzy-ament-cmake-export-link-flags: 2.5.3-1 → 2.5.4-1
ros-jazzy-ament-cmake-export-targets: 2.5.3-1 → 2.5.4-1
ros-jazzy-ament-cmake-gen-version-h: 2.5.3-1 → 2.5.4-1
ros-jazzy-ament-cmake-gmock: 2.5.3-1 → 2.5.4-1
ros-jazzy-ament-cmake-google-benchmark: 2.5.3-1 → 2.5.4-1
ros-jazzy-ament-cmake-gtest: 2.5.3-1 → 2.5.4-1
ros-jazzy-ament-cmake-include-directories: 2.5.3-1 → 2.5.4-1
ros-jazzy-ament-cmake-libraries: 2.5.3-1 → 2.5.4-1
ros-jazzy-ament-cmake-pytest: 2.5.3-1 → 2.5.4-1
ros-jazzy-ament-cmake-python: 2.5.3-1 → 2.5.4-1
ros-jazzy-ament-cmake-target-dependencies: 2.5.3-1 → 2.5.4-1
ros-jazzy-ament-cmake-test: 2.5.3-1 → 2.5.4-1
ros-jazzy-ament-cmake-vendor-package: 2.5.3-1 → 2.5.4-1
ros-jazzy-ament-cmake-version: 2.5.3-1 → 2.5.4-1
ros-jazzy-autoware-cmake: 1.0.1-1 → 1.0.2-1
ros-jazzy-autoware-common-msgs: 1.4.0-1 → 1.6.0-1
ros-jazzy-autoware-common-msgs-dbgsym: 1.4.0-1 → 1.6.0-1
ros-jazzy-autoware-control-msgs: 1.4.0-1 → 1.6.0-1
ros-jazzy-autoware-control-msgs-dbgsym: 1.4.0-1 → 1.6.0-1
ros-jazzy-autoware-internal-debug-msgs: 1.5.0-2 → 1.8.1-1
ros-jazzy-autoware-internal-debug-msgs-dbgsym: 1.5.0-2 → 1.8.1-1
ros-jazzy-autoware-internal-msgs: 1.5.0-2 → 1.8.1-1
ros-jazzy-autoware-internal-msgs-dbgsym: 1.5.0-2 → 1.8.1-1
ros-jazzy-autoware-internal-perception-msgs: 1.5.0-2 → 1.8.1-1
ros-jazzy-autoware-internal-perception-msgs-dbgsym: 1.5.0-2 → 1.8.1-1
ros-jazzy-autoware-internal-planning-msgs: 1.5.0-2 → 1.8.1-1
ros-jazzy-autoware-internal-planning-msgs-dbgsym: 1.5.0-2 → 1.8.1-1
ros-jazzy-autoware-lint-common: 1.0.1-1 → 1.0.2-1
ros-jazzy-autoware-localization-msgs: 1.4.0-1 → 1.6.0-1
ros-jazzy-autoware-localization-msgs-dbgsym: 1.4.0-1 → 1.6.0-1
ros-jazzy-autoware-map-msgs: 1.4.0-1 → 1.6.0-1
ros-jazzy-autoware-map-msgs-dbgsym: 1.4.0-1 → 1.6.0-1
ros-jazzy-autoware-perception-msgs: 1.4.0-1 → 1.6.0-1
ros-jazzy-autoware-perception-msgs-dbgsym: 1.4.0-1 → 1.6.0-1
ros-jazzy-autoware-planning-msgs: 1.4.0-1 → 1.6.0-1
ros-jazzy-autoware-planning-msgs-dbgsym: 1.4.0-1 → 1.6.0-1
ros-jazzy-autoware-sensing-msgs: 1.4.0-1 → 1.6.0-1
ros-jazzy-autoware-sensing-msgs-dbgsym: 1.4.0-1 → 1.6.0-1
ros-jazzy-autoware-system-msgs: 1.4.0-1 → 1.6.0-1
ros-jazzy-autoware-system-msgs-dbgsym: 1.4.0-1 → 1.6.0-1
ros-jazzy-autoware-v2x-msgs: 1.4.0-1 → 1.6.0-1
ros-jazzy-autoware-v2x-msgs-dbgsym: 1.4.0-1 → 1.6.0-1
ros-jazzy-autoware-vehicle-msgs: 1.4.0-1 → 1.6.0-1
ros-jazzy-autoware-vehicle-msgs-dbgsym: 1.4.0-1 → 1.6.0-1
ros-jazzy-bicycle-steering-controller: 4.22.0-1 → 4.23.0-1
ros-jazzy-bicycle-steering-controller-dbgsym: 4.22.0-1 → 4.23.0-1
ros-jazzy-camera-calibration: 5.0.9-1 → 5.0.10-1
ros-jazzy-camera-ros: 0.3.0-1 → 0.4.0-1
ros-jazzy-camera-ros-dbgsym: 0.3.0-1 → 0.4.0-1
ros-jazzy-chomp-motion-planner: 2.12.2-1 → 2.12.3-1
ros-jazzy-chomp-motion-planner-dbgsym: 2.12.2-1 → 2.12.3-1
ros-jazzy-clearpath-bt-joy: 2.2.0-1 → 2.3.1-1
ros-jazzy-clearpath-common: 2.2.0-1 → 2.3.1-1
ros-jazzy-clearpath-config: 2.2.2-1 → 2.3.0-1
ros-jazzy-clearpath-control: 2.2.0-1 → 2.3.1-1
ros-jazzy-clearpath-customization: 2.2.0-1 → 2.3.1-1
ros-jazzy-clearpath-description: 2.2.0-1 → 2.3.1-1
ros-jazzy-clearpath-generator-common: 2.2.0-1 → 2.3.1-1
ros-jazzy-clearpath-generator-common-dbgsym: 2.2.0-1 → 2.3.1-1
ros-jazzy-clearpath-generator-gz: 2.2.0-1 → 2.3.0-1
ros-jazzy-clearpath-gz: 2.2.0-1 → 2.3.0-1
ros-jazzy-clearpath-manipulators: 2.2.0-1 → 2.3.1-1
ros-jazzy-clearpath-manipulators-description: 2.2.0-1 → 2.3.1-1
ros-jazzy-clearpath-motor-msgs: 2.2.2-1 → 2.3.0-1
ros-jazzy-clearpath-motor-msgs-dbgsym: 2.2.2-1 → 2.3.0-1
ros-jazzy-clearpath-mounts-description: 2.2.0-1 → 2.3.1-1
ros-jazzy-clearpath-msgs: 2.2.2-1 → 2.3.0-1
ros-jazzy-clearpath-platform-description: 2.2.0-1 → 2.3.1-1
ros-jazzy-clearpath-platform-msgs: 2.2.2-1 → 2.3.0-1
ros-jazzy-clearpath-platform-msgs-dbgsym: 2.2.2-1 → 2.3.0-1
ros-jazzy-clearpath-ros2-socketcan-interface: 2.1.0-1 → 2.1.1-2
ros-jazzy-clearpath-ros2-socketcan-interface-dbgsym: 2.1.0-1 → 2.1.1-2
ros-jazzy-clearpath-sensors-description: 2.2.0-1 → 2.3.1-1
ros-jazzy-clearpath-simulator: 2.2.0-1 → 2.3.0-1
ros-jazzy-clearpath-tests: 0.2.9-1 → 2.3.1-1
ros-jazzy-control-toolbox: 4.0.1-1 → 4.2.0-1
ros-jazzy-control-toolbox-dbgsym: 4.0.1-1 → 4.2.0-1
ros-jazzy-controller-interface: 4.27.0-1 → 4.28.1-1
ros-jazzy-controller-interface-dbgsym: 4.27.0-1 → 4.28.1-1
ros-jazzy-controller-manager: 4.27.0-1 → 4.28.1-1
ros-jazzy-controller-manager-dbgsym: 4.27.0-1 → 4.28.1-1
ros-jazzy-controller-manager-msgs: 4.27.0-1 → 4.28.1-1
ros-jazzy-controller-manager-msgs-dbgsym: 4.27.0-1 → 4.28.1-1
ros-jazzy-costmap-queue: 1.3.5-1 → 1.3.6-1
ros-jazzy-costmap-queue-dbgsym: 1.3.5-1 → 1.3.6-1
ros-jazzy-depth-image-proc: 5.0.9-1 → 5.0.10-1
ros-jazzy-depth-image-proc-dbgsym: 5.0.9-1 → 5.0.10-1
ros-jazzy-diagnostic-aggregator: 4.2.2-1 → 4.2.3-1
ros-jazzy-diagnostic-aggregator-dbgsym: 4.2.2-1 → 4.2.3-1
ros-jazzy-diagnostic-common-diagnostics: 4.2.2-1 → 4.2.3-1
ros-jazzy-diagnostic-updater: 4.2.2-1 → 4.2.3-1
ros-jazzy-diagnostic-updater-dbgsym: 4.2.2-1 → 4.2.3-1
ros-jazzy-diagnostics: 4.2.2-1 → 4.2.3-1
ros-jazzy-diff-drive-controller: 4.22.0-1 → 4.23.0-1
ros-jazzy-diff-drive-controller-dbgsym: 4.22.0-1 → 4.23.0-1
ros-jazzy-dwb-core: 1.3.5-1 → 1.3.6-1
ros-jazzy-dwb-core-dbgsym: 1.3.5-1 → 1.3.6-1
ros-jazzy-dwb-critics: 1.3.5-1 → 1.3.6-1
ros-jazzy-dwb-critics-dbgsym: 1.3.5-1 → 1.3.6-1
ros-jazzy-dwb-msgs: 1.3.5-1 → 1.3.6-1
ros-jazzy-dwb-msgs-dbgsym: 1.3.5-1 → 1.3.6-1
ros-jazzy-dwb-plugins: 1.3.5-1 → 1.3.6-1
ros-jazzy-dwb-plugins-dbgsym: 1.3.5-1 → 1.3.6-1
ros-jazzy-dynamixel-hardware-interface: 1.4.1-1 → 1.4.3-1
ros-jazzy-dynamixel-hardware-interface-dbgsym: 1.4.1-1 → 1.4.3-1
ros-jazzy-effort-controllers: 4.22.0-1 → 4.23.0-1
ros-jazzy-effort-controllers-dbgsym: 4.22.0-1 → 4.23.0-1
ros-jazzy-etsi-its-cam-coding: 3.1.0-1 → 3.2.0-1
ros-jazzy-etsi-its-cam-coding-dbgsym: 3.1.0-1 → 3.2.0-1
ros-jazzy-etsi-its-cam-conversion: 3.1.0-1 → 3.2.0-1
ros-jazzy-etsi-its-cam-msgs: 3.1.0-1 → 3.2.0-1
ros-jazzy-etsi-its-cam-msgs-dbgsym: 3.1.0-1 → 3.2.0-1
ros-jazzy-etsi-its-cam-ts-coding: 3.1.0-1 → 3.2.0-1
ros-jazzy-etsi-its-cam-ts-coding-dbgsym: 3.1.0-1 → 3.2.0-1
ros-jazzy-etsi-its-cam-ts-conversion: 3.1.0-1 → 3.2.0-1
ros-jazzy-etsi-its-cam-ts-msgs: 3.1.0-1 → 3.2.0-1
ros-jazzy-etsi-its-cam-ts-msgs-dbgsym: 3.1.0-1 → 3.2.0-1
ros-jazzy-etsi-its-coding: 3.1.0-1 → 3.2.0-1
ros-jazzy-etsi-its-conversion: 3.1.0-1 → 3.2.0-1
ros-jazzy-etsi-its-conversion-dbgsym: 3.1.0-1 → 3.2.0-1
ros-jazzy-etsi-its-cpm-ts-coding: 3.1.0-1 → 3.2.0-1
ros-jazzy-etsi-its-cpm-ts-coding-dbgsym: 3.1.0-1 → 3.2.0-1
ros-jazzy-etsi-its-cpm-ts-conversion: 3.1.0-1 → 3.2.0-1
ros-jazzy-etsi-its-cpm-ts-msgs: 3.1.0-1 → 3.2.0-1
ros-jazzy-etsi-its-cpm-ts-msgs-dbgsym: 3.1.0-1 → 3.2.0-1
ros-jazzy-etsi-its-denm-coding: 3.1.0-1 → 3.2.0-1
ros-jazzy-etsi-its-denm-coding-dbgsym: 3.1.0-1 → 3.2.0-1
ros-jazzy-etsi-its-denm-conversion: 3.1.0-1 → 3.2.0-1
ros-jazzy-etsi-its-denm-msgs: 3.1.0-1 → 3.2.0-1
ros-jazzy-etsi-its-denm-msgs-dbgsym: 3.1.0-1 → 3.2.0-1
ros-jazzy-etsi-its-denm-ts-coding: 3.1.0-1 → 3.2.0-1
ros-jazzy-etsi-its-denm-ts-coding-dbgsym: 3.1.0-1 → 3.2.0-1
ros-jazzy-etsi-its-denm-ts-conversion: 3.1.0-1 → 3.2.0-1
ros-jazzy-etsi-its-denm-ts-msgs: 3.1.0-1 → 3.2.0-1
ros-jazzy-etsi-its-denm-ts-msgs-dbgsym: 3.1.0-1 → 3.2.0-1
ros-jazzy-etsi-its-mapem-ts-coding: 3.1.0-1 → 3.2.0-1
ros-jazzy-etsi-its-mapem-ts-coding-dbgsym: 3.1.0-1 → 3.2.0-1
ros-jazzy-etsi-its-mapem-ts-conversion: 3.1.0-1 → 3.2.0-1
ros-jazzy-etsi-its-mapem-ts-msgs: 3.1.0-1 → 3.2.0-1
ros-jazzy-etsi-its-mapem-ts-msgs-dbgsym: 3.1.0-1 → 3.2.0-1
ros-jazzy-etsi-its-messages: 3.1.0-1 → 3.2.0-1
ros-jazzy-etsi-its-msgs: 3.1.0-1 → 3.2.0-1
ros-jazzy-etsi-its-msgs-utils: 3.1.0-1 → 3.2.0-1
ros-jazzy-etsi-its-primitives-conversion: 3.1.0-1 → 3.2.0-1
ros-jazzy-etsi-its-rviz-plugins: 3.1.0-1 → 3.2.0-1
ros-jazzy-etsi-its-rviz-plugins-dbgsym: 3.1.0-1 → 3.2.0-1
ros-jazzy-etsi-its-spatem-ts-coding: 3.1.0-1 → 3.2.0-1
ros-jazzy-etsi-its-spatem-ts-coding-dbgsym: 3.1.0-1 → 3.2.0-1
ros-jazzy-etsi-its-spatem-ts-conversion: 3.1.0-1 → 3.2.0-1
ros-jazzy-etsi-its-spatem-ts-msgs: 3.1.0-1 → 3.2.0-1
ros-jazzy-etsi-its-spatem-ts-msgs-dbgsym: 3.1.0-1 → 3.2.0-1
ros-jazzy-etsi-its-vam-ts-coding: 3.1.0-1 → 3.2.0-1
ros-jazzy-etsi-its-vam-ts-coding-dbgsym: 3.1.0-1 → 3.2.0-1
ros-jazzy-etsi-its-vam-ts-conversion: 3.1.0-1 → 3.2.0-1
ros-jazzy-etsi-its-vam-ts-msgs: 3.1.0-1 → 3.2.0-1
ros-jazzy-etsi-its-vam-ts-msgs-dbgsym: 3.1.0-1 → 3.2.0-1
ros-jazzy-event-camera-py: 1.3.6-1 → 2.0.0-1
ros-jazzy-examples-tf2-py: 0.36.9-1 → 0.36.10-1
ros-jazzy-force-torque-sensor-broadcaster: 4.22.0-1 → 4.23.0-1
ros-jazzy-force-torque-sensor-broadcaster-dbgsym: 4.22.0-1 → 4.23.0-1
ros-jazzy-forward-command-controller: 4.22.0-1 → 4.23.0-1
ros-jazzy-forward-command-controller-dbgsym: 4.22.0-1 → 4.23.0-1
ros-jazzy-geometry2: 0.36.9-1 → 0.36.10-1
ros-jazzy-gpio-controllers: 4.22.0-1 → 4.23.0-1
ros-jazzy-gpio-controllers-dbgsym: 4.22.0-1 → 4.23.0-1
ros-jazzy-gripper-controllers: 4.22.0-1 → 4.23.0-1
ros-jazzy-gripper-controllers-dbgsym: 4.22.0-1 → 4.23.0-1
ros-jazzy-gz-ros2-control: 1.2.11-1 → 1.2.12-1
ros-jazzy-gz-ros2-control-dbgsym: 1.2.11-1 → 1.2.12-1
ros-jazzy-gz-ros2-control-demos: 1.2.11-1 → 1.2.12-1
ros-jazzy-gz-ros2-control-demos-dbgsym: 1.2.11-1 → 1.2.12-1
ros-jazzy-hardware-interface: 4.27.0-1 → 4.28.1-1
ros-jazzy-hardware-interface-dbgsym: 4.27.0-1 → 4.28.1-1
ros-jazzy-hardware-interface-testing: 4.27.0-1 → 4.28.1-1
ros-jazzy-hardware-interface-testing-dbgsym: 4.27.0-1 → 4.28.1-1
ros-jazzy-image-pipeline: 5.0.9-1 → 5.0.10-1
ros-jazzy-image-proc: 5.0.9-1 → 5.0.10-1
ros-jazzy-image-proc-dbgsym: 5.0.9-1 → 5.0.10-1
ros-jazzy-image-publisher: 5.0.9-1 → 5.0.10-1
ros-jazzy-image-publisher-dbgsym: 5.0.9-1 → 5.0.10-1
ros-jazzy-image-rotate: 5.0.9-1 → 5.0.10-1
ros-jazzy-image-rotate-dbgsym: 5.0.9-1 → 5.0.10-1
ros-jazzy-image-view: 5.0.9-1 → 5.0.10-1
ros-jazzy-image-view-dbgsym: 5.0.9-1 → 5.0.10-1
ros-jazzy-imu-sensor-broadcaster: 4.22.0-1 → 4.23.0-1
ros-jazzy-imu-sensor-broadcaster-dbgsym: 4.22.0-1 → 4.23.0-1
ros-jazzy-joint-limits: 4.27.0-1 → 4.28.1-1
ros-jazzy-joint-limits-dbgsym: 4.27.0-1 → 4.28.1-1
ros-jazzy-joint-state-broadcaster: 4.22.0-1 → 4.23.0-1
ros-jazzy-joint-state-broadcaster-dbgsym: 4.22.0-1 → 4.23.0-1
ros-jazzy-joint-trajectory-controller: 4.22.0-1 → 4.23.0-1
ros-jazzy-joint-trajectory-controller-dbgsym: 4.22.0-1 → 4.23.0-1
ros-jazzy-joy-teleop: 1.7.0-1 → 1.8.0-1
ros-jazzy-key-teleop: 1.7.0-1 → 1.8.0-1
ros-jazzy-ld08-driver: 1.1.1-1 → 1.1.3-1
ros-jazzy-ld08-driver-dbgsym: 1.1.1-1 → 1.1.3-1
ros-jazzy-leo: 3.0.4-1 → 3.1.0-1
ros-jazzy-leo-description: 3.0.4-1 → 3.1.0-1
ros-jazzy-leo-gz-bringup: 2.0.1-1 → 2.0.2-1
ros-jazzy-leo-gz-plugins: 2.0.1-1 → 2.0.2-1
ros-jazzy-leo-gz-plugins-dbgsym: 2.0.1-1 → 2.0.2-1
ros-jazzy-leo-gz-worlds: 2.0.1-1 → 2.0.2-1
ros-jazzy-leo-msgs: 3.0.4-1 → 3.1.0-1
ros-jazzy-leo-msgs-dbgsym: 3.0.4-1 → 3.1.0-1
ros-jazzy-leo-simulator: 2.0.1-1 → 2.0.2-1
ros-jazzy-leo-teleop: 3.0.4-1 → 3.1.0-1
ros-jazzy-libcaer-driver: 1.3.3-1 → 1.5.0-1
ros-jazzy-libcaer-driver-dbgsym: 1.3.3-1 → 1.5.0-1
ros-jazzy-libcamera: 0.4.0-1 → 0.5.0-1
ros-jazzy-libcamera-dbgsym: 0.4.0-1 → 0.5.0-1
ros-jazzy-liblz4-vendor: 0.26.6-1 → 0.26.7-1
ros-jazzy-mcap-vendor: 0.26.6-1 → 0.26.7-1
ros-jazzy-mcap-vendor-dbgsym: 0.26.6-1 → 0.26.7-1
ros-jazzy-mecanum-drive-controller: 4.22.0-1 → 4.23.0-1
ros-jazzy-mecanum-drive-controller-dbgsym: 4.22.0-1 → 4.23.0-1
ros-jazzy-message-filters: 4.11.5-1 → 4.11.6-1
ros-jazzy-message-filters-dbgsym: 4.11.5-1 → 4.11.6-1
ros-jazzy-microstrain-inertial-description: 4.5.0-1 → 4.6.0-1
ros-jazzy-microstrain-inertial-driver: 4.5.0-1 → 4.6.0-1
ros-jazzy-microstrain-inertial-driver-dbgsym: 4.5.0-1 → 4.6.0-1
ros-jazzy-microstrain-inertial-examples: 4.5.0-1 → 4.6.0-1
ros-jazzy-microstrain-inertial-msgs: 4.5.0-1 → 4.6.0-1
ros-jazzy-microstrain-inertial-msgs-dbgsym: 4.5.0-1 → 4.6.0-1
ros-jazzy-microstrain-inertial-rqt: 4.5.0-1 → 4.6.0-1
ros-jazzy-mouse-teleop: 1.7.0-1 → 1.8.0-1
ros-jazzy-moveit: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-common: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-configs-utils: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-core: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-core-dbgsym: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-hybrid-planning: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-hybrid-planning-dbgsym: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-kinematics: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-kinematics-dbgsym: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-planners: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-planners-chomp: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-planners-chomp-dbgsym: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-planners-ompl: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-planners-ompl-dbgsym: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-planners-stomp: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-planners-stomp-dbgsym: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-plugins: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-py: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-py-dbgsym: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-resources-prbt-ikfast-manipulator-plugin: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-resources-prbt-ikfast-manipulator-plugin-dbgsym: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-resources-prbt-moveit-config: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-resources-prbt-pg70-support: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-resources-prbt-support: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-ros: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-ros-benchmarks: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-ros-benchmarks-dbgsym: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-ros-control-interface: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-ros-control-interface-dbgsym: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-ros-move-group: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-ros-move-group-dbgsym: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-ros-occupancy-map-monitor: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-ros-occupancy-map-monitor-dbgsym: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-ros-perception: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-ros-perception-dbgsym: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-ros-planning: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-ros-planning-dbgsym: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-ros-planning-interface: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-ros-planning-interface-dbgsym: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-ros-robot-interaction: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-ros-robot-interaction-dbgsym: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-ros-tests: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-ros-trajectory-cache: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-ros-trajectory-cache-dbgsym: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-ros-visualization: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-ros-visualization-dbgsym: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-ros-warehouse: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-ros-warehouse-dbgsym: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-runtime: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-servo: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-servo-dbgsym: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-setup-app-plugins: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-setup-app-plugins-dbgsym: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-setup-assistant: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-setup-assistant-dbgsym: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-setup-controllers: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-setup-controllers-dbgsym: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-setup-core-plugins: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-setup-core-plugins-dbgsym: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-setup-framework: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-setup-framework-dbgsym: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-setup-srdf-plugins: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-setup-srdf-plugins-dbgsym: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-simple-controller-manager: 2.12.2-1 → 2.12.3-1
ros-jazzy-moveit-simple-controller-manager-dbgsym: 2.12.2-1 → 2.12.3-1
ros-jazzy-mp2p-icp: 1.6.6-1 → 1.6.7-1
ros-jazzy-mp2p-icp-dbgsym: 1.6.6-1 → 1.6.7-1
ros-jazzy-nav-2d-msgs: 1.3.5-1 → 1.3.6-1
ros-jazzy-nav-2d-msgs-dbgsym: 1.3.5-1 → 1.3.6-1
ros-jazzy-nav-2d-utils: 1.3.5-1 → 1.3.6-1
ros-jazzy-nav-2d-utils-dbgsym: 1.3.5-1 → 1.3.6-1
ros-jazzy-nav2-amcl: 1.3.5-1 → 1.3.6-1
ros-jazzy-nav2-amcl-dbgsym: 1.3.5-1 → 1.3.6-1
ros-jazzy-nav2-behavior-tree: 1.3.5-1 → 1.3.6-1
ros-jazzy-nav2-behavior-tree-dbgsym: 1.3.5-1 → 1.3.6-1
ros-jazzy-nav2-behaviors: 1.3.5-1 → 1.3.6-1
ros-jazzy-nav2-behaviors-dbgsym: 1.3.5-1 → 1.3.6-1
ros-jazzy-nav2-bringup: 1.3.5-1 → 1.3.6-1
ros-jazzy-nav2-bt-navigator: 1.3.5-1 → 1.3.6-1
ros-jazzy-nav2-bt-navigator-dbgsym: 1.3.5-1 → 1.3.6-1
ros-jazzy-nav2-collision-monitor: 1.3.5-1 → 1.3.6-1
ros-jazzy-nav2-collision-monitor-dbgsym: 1.3.5-1 → 1.3.6-1
ros-jazzy-nav2-common: 1.3.5-1 → 1.3.6-1
ros-jazzy-nav2-constrained-smoother: 1.3.5-1 → 1.3.6-1
ros-jazzy-nav2-constrained-smoother-dbgsym: 1.3.5-1 → 1.3.6-1
ros-jazzy-nav2-controller: 1.3.5-1 → 1.3.6-1
ros-jazzy-nav2-controller-dbgsym: 1.3.5-1 → 1.3.6-1
ros-jazzy-nav2-core: 1.3.5-1 → 1.3.6-1
ros-jazzy-nav2-costmap-2d: 1.3.5-1 → 1.3.6-1
ros-jazzy-nav2-costmap-2d-dbgsym: 1.3.5-1 → 1.3.6-1
ros-jazzy-nav2-dwb-controller: 1.3.5-1 → 1.3.6-1
ros-jazzy-nav2-graceful-controller: 1.3.5-1 → 1.3.6-1
ros-jazzy-nav2-graceful-controller-dbgsym: 1.3.5-1 → 1.3.6-1
ros-jazzy-nav2-lifecycle-manager: 1.3.5-1 → 1.3.6-1
ros-jazzy-nav2-lifecycle-manager-dbgsym: 1.3.5-1 → 1.3.6-1
ros-jazzy-nav2-loopback-sim: 1.3.5-1 → 1.3.6-1
ros-jazzy-nav2-map-server: 1.3.5-1 → 1.3.6-1
ros-jazzy-nav2-map-server-dbgsym: 1.3.5-1 → 1.3.6-1
ros-jazzy-nav2-mppi-controller: 1.3.5-1 → 1.3.6-1
ros-jazzy-nav2-mppi-controller-dbgsym: 1.3.5-1 → 1.3.6-1
ros-jazzy-nav2-msgs: 1.3.5-1 → 1.3.6-1
ros-jazzy-nav2-msgs-dbgsym: 1.3.5-1 → 1.3.6-1
ros-jazzy-nav2-navfn-planner: 1.3.5-1 → 1.3.6-1
ros-jazzy-nav2-navfn-planner-dbgsym: 1.3.5-1 → 1.3.6-1
ros-jazzy-nav2-planner: 1.3.5-1 → 1.3.6-1
ros-jazzy-nav2-planner-dbgsym: 1.3.5-1 → 1.3.6-1
ros-jazzy-nav2-regulated-pure-pursuit-controller: 1.3.5-1 → 1.3.6-1
ros-jazzy-nav2-regulated-pure-pursuit-controller-dbgsym: 1.3.5-1 → 1.3.6-1
ros-jazzy-nav2-rotation-shim-controller: 1.3.5-1 → 1.3.6-1
ros-jazzy-nav2-rotation-shim-controller-dbgsym: 1.3.5-1 → 1.3.6-1
ros-jazzy-nav2-rviz-plugins: 1.3.5-1 → 1.3.6-1
ros-jazzy-nav2-rviz-plugins-dbgsym: 1.3.5-1 → 1.3.6-1
ros-jazzy-nav2-simple-commander: 1.3.5-1 → 1.3.6-1
ros-jazzy-nav2-smac-planner: 1.3.5-1 → 1.3.6-1
ros-jazzy-nav2-smac-planner-dbgsym: 1.3.5-1 → 1.3.6-1
ros-jazzy-nav2-smoother: 1.3.5-1 → 1.3.6-1
ros-jazzy-nav2-smoother-dbgsym: 1.3.5-1 → 1.3.6-1
ros-jazzy-nav2-system-tests: 1.3.5-1 → 1.3.6-1
ros-jazzy-nav2-system-tests-dbgsym: 1.3.5-1 → 1.3.6-1
ros-jazzy-nav2-theta-star-planner: 1.3.5-1 → 1.3.6-1
ros-jazzy-nav2-theta-star-planner-dbgsym: 1.3.5-1 → 1.3.6-1
ros-jazzy-nav2-util: 1.3.5-1 → 1.3.6-1
ros-jazzy-nav2-util-dbgsym: 1.3.5-1 → 1.3.6-1
ros-jazzy-nav2-velocity-smoother: 1.3.5-1 → 1.3.6-1
ros-jazzy-nav2-velocity-smoother-dbgsym: 1.3.5-1 → 1.3.6-1
ros-jazzy-nav2-voxel-grid: 1.3.5-1 → 1.3.6-1
ros-jazzy-nav2-voxel-grid-dbgsym: 1.3.5-1 → 1.3.6-1
ros-jazzy-nav2-waypoint-follower: 1.3.5-1 → 1.3.6-1
ros-jazzy-nav2-waypoint-follower-dbgsym: 1.3.5-1 → 1.3.6-1
ros-jazzy-navigation2: 1.3.5-1 → 1.3.6-1
ros-jazzy-ntrip-client: 1.4.0-1 → 1.4.1-1
ros-jazzy-opennav-docking: 1.3.5-1 → 1.3.6-1
ros-jazzy-opennav-docking-bt: 1.3.5-1 → 1.3.6-1
ros-jazzy-opennav-docking-bt-dbgsym: 1.3.5-1 → 1.3.6-1
ros-jazzy-opennav-docking-core: 1.3.5-1 → 1.3.6-1
ros-jazzy-opennav-docking-dbgsym: 1.3.5-1 → 1.3.6-1
ros-jazzy-openvdb-vendor: 2.5.4-1 → 2.5.5-1
ros-jazzy-parallel-gripper-controller: 4.22.0-1 → 4.23.0-1
ros-jazzy-parallel-gripper-controller-dbgsym: 4.22.0-1 → 4.23.0-1
ros-jazzy-pid-controller: 4.22.0-1 → 4.23.0-1
ros-jazzy-pid-controller-dbgsym: 4.22.0-1 → 4.23.0-1
ros-jazzy-pilz-industrial-motion-planner: 2.12.2-1 → 2.12.3-1
ros-jazzy-pilz-industrial-motion-planner-dbgsym: 2.12.2-1 → 2.12.3-1
ros-jazzy-pilz-industrial-motion-planner-testutils: 2.12.2-1 → 2.12.3-1
ros-jazzy-pilz-industrial-motion-planner-testutils-dbgsym: 2.12.2-1 → 2.12.3-1
ros-jazzy-polygon-demos: 1.1.0-1 → 1.2.0-1
ros-jazzy-polygon-demos-dbgsym: 1.1.0-1 → 1.2.0-1
ros-jazzy-polygon-msgs: 1.1.0-1 → 1.2.0-1
ros-jazzy-polygon-msgs-dbgsym: 1.1.0-1 → 1.2.0-1
ros-jazzy-polygon-rviz-plugins: 1.1.0-1 → 1.2.0-1
ros-jazzy-polygon-rviz-plugins-dbgsym: 1.1.0-1 → 1.2.0-1
ros-jazzy-polygon-utils: 1.1.0-1 → 1.2.0-1
ros-jazzy-pose-broadcaster: 4.22.0-1 → 4.23.0-1
ros-jazzy-pose-broadcaster-dbgsym: 4.22.0-1 → 4.23.0-1
ros-jazzy-position-controllers: 4.22.0-1 → 4.23.0-1
ros-jazzy-position-controllers-dbgsym: 4.22.0-1 → 4.23.0-1
ros-jazzy-range-sensor-broadcaster: 4.22.0-1 → 4.23.0-1
ros-jazzy-range-sensor-broadcaster-dbgsym: 4.22.0-1 → 4.23.0-1
ros-jazzy-rcl: 9.2.5-1 → 9.2.6-1
ros-jazzy-rcl-action: 9.2.5-1 → 9.2.6-1
ros-jazzy-rcl-action-dbgsym: 9.2.5-1 → 9.2.6-1
ros-jazzy-rcl-dbgsym: 9.2.5-1 → 9.2.6-1
ros-jazzy-rcl-lifecycle: 9.2.5-1 → 9.2.6-1
ros-jazzy-rcl-lifecycle-dbgsym: 9.2.5-1 → 9.2.6-1
ros-jazzy-rcl-yaml-param-parser: 9.2.5-1 → 9.2.6-1
ros-jazzy-rcl-yaml-param-parser-dbgsym: 9.2.5-1 → 9.2.6-1
ros-jazzy-rclcpp: 28.1.8-1 → 28.1.9-1
ros-jazzy-rclcpp-action: 28.1.8-1 → 28.1.9-1
ros-jazzy-rclcpp-action-dbgsym: 28.1.8-1 → 28.1.9-1
ros-jazzy-rclcpp-components: 28.1.8-1 → 28.1.9-1
ros-jazzy-rclcpp-components-dbgsym: 28.1.8-1 → 28.1.9-1
ros-jazzy-rclcpp-dbgsym: 28.1.8-1 → 28.1.9-1
ros-jazzy-rclcpp-lifecycle: 28.1.8-1 → 28.1.9-1
ros-jazzy-rclcpp-lifecycle-dbgsym: 28.1.8-1 → 28.1.9-1
ros-jazzy-realtime-tools: 3.4.0-1 → 3.5.0-1
ros-jazzy-realtime-tools-dbgsym: 3.4.0-1 → 3.5.0-1
ros-jazzy-ros2-control: 4.27.0-1 → 4.28.1-1
ros-jazzy-ros2-control-test-assets: 4.27.0-1 → 4.28.1-1
ros-jazzy-ros2-controllers: 4.22.0-1 → 4.23.0-1
ros-jazzy-ros2-controllers-test-nodes: 4.22.0-1 → 4.23.0-1
ros-jazzy-ros2action: 0.32.3-1 → 0.32.4-1
ros-jazzy-ros2bag: 0.26.6-1 → 0.26.7-1
ros-jazzy-ros2cli: 0.32.3-1 → 0.32.4-1
ros-jazzy-ros2cli-test-interfaces: 0.32.3-1 → 0.32.4-1
ros-jazzy-ros2cli-test-interfaces-dbgsym: 0.32.3-1 → 0.32.4-1
ros-jazzy-ros2component: 0.32.3-1 → 0.32.4-1
ros-jazzy-ros2controlcli: 4.27.0-1 → 4.28.1-1
ros-jazzy-ros2doctor: 0.32.3-1 → 0.32.4-1
ros-jazzy-ros2interface: 0.32.3-1 → 0.32.4-1
ros-jazzy-ros2lifecycle: 0.32.3-1 → 0.32.4-1
ros-jazzy-ros2lifecycle-test-fixtures: 0.32.3-1 → 0.32.4-1
ros-jazzy-ros2lifecycle-test-fixtures-dbgsym: 0.32.3-1 → 0.32.4-1
ros-jazzy-ros2multicast: 0.32.3-1 → 0.32.4-1
ros-jazzy-ros2node: 0.32.3-1 → 0.32.4-1
ros-jazzy-ros2param: 0.32.3-1 → 0.32.4-1
ros-jazzy-ros2pkg: 0.32.3-1 → 0.32.4-1
ros-jazzy-ros2run: 0.32.3-1 → 0.32.4-1
ros-jazzy-ros2service: 0.32.3-1 → 0.32.4-1
ros-jazzy-ros2topic: 0.32.3-1 → 0.32.4-1
ros-jazzy-rosbag2: 0.26.6-1 → 0.26.7-1
ros-jazzy-rosbag2-compression: 0.26.6-1 → 0.26.7-1
ros-jazzy-rosbag2-compression-dbgsym: 0.26.6-1 → 0.26.7-1
ros-jazzy-rosbag2-compression-zstd: 0.26.6-1 → 0.26.7-1
ros-jazzy-rosbag2-compression-zstd-dbgsym: 0.26.6-1 → 0.26.7-1
ros-jazzy-rosbag2-cpp: 0.26.6-1 → 0.26.7-1
ros-jazzy-rosbag2-cpp-dbgsym: 0.26.6-1 → 0.26.7-1
ros-jazzy-rosbag2-examples-cpp: 0.26.6-1 → 0.26.7-1
ros-jazzy-rosbag2-examples-cpp-dbgsym: 0.26.6-1 → 0.26.7-1
ros-jazzy-rosbag2-examples-py: 0.26.6-1 → 0.26.7-1
ros-jazzy-rosbag2-interfaces: 0.26.6-1 → 0.26.7-1
ros-jazzy-rosbag2-interfaces-dbgsym: 0.26.6-1 → 0.26.7-1
ros-jazzy-rosbag2-performance-benchmarking: 0.26.6-1 → 0.26.7-1
ros-jazzy-rosbag2-performance-benchmarking-msgs: 0.26.6-1 → 0.26.7-1
ros-jazzy-rosbag2-py: 0.26.6-1 → 0.26.7-1
ros-jazzy-rosbag2-storage: 0.26.6-1 → 0.26.7-1
ros-jazzy-rosbag2-storage-dbgsym: 0.26.6-1 → 0.26.7-1
ros-jazzy-rosbag2-storage-default-plugins: 0.26.6-1 → 0.26.7-1
ros-jazzy-rosbag2-storage-mcap: 0.26.6-1 → 0.26.7-1
ros-jazzy-rosbag2-storage-mcap-dbgsym: 0.26.6-1 → 0.26.7-1
ros-jazzy-rosbag2-storage-sqlite3: 0.26.6-1 → 0.26.7-1
ros-jazzy-rosbag2-storage-sqlite3-dbgsym: 0.26.6-1 → 0.26.7-1
ros-jazzy-rosbag2-test-common: 0.26.6-1 → 0.26.7-1
ros-jazzy-rosbag2-test-msgdefs: 0.26.6-1 → 0.26.7-1
ros-jazzy-rosbag2-test-msgdefs-dbgsym: 0.26.6-1 → 0.26.7-1
ros-jazzy-rosbag2-tests: 0.26.6-1 → 0.26.7-1
ros-jazzy-rosbag2-transport: 0.26.6-1 → 0.26.7-1
ros-jazzy-rosbag2-transport-dbgsym: 0.26.6-1 → 0.26.7-1
ros-jazzy-rosidl-generator-py: 0.22.0-2 → 0.22.1-1
ros-jazzy-rqt-controller-manager: 4.27.0-1 → 4.28.1-1
ros-jazzy-rqt-joint-trajectory-controller: 4.22.0-1 → 4.23.0-1
ros-jazzy-rviz-assimp-vendor: 14.1.8-1 → 14.1.10-1
ros-jazzy-rviz-common: 14.1.8-1 → 14.1.10-1
ros-jazzy-rviz-common-dbgsym: 14.1.8-1 → 14.1.10-1
ros-jazzy-rviz-default-plugins: 14.1.8-1 → 14.1.10-1
ros-jazzy-rviz-default-plugins-dbgsym: 14.1.8-1 → 14.1.10-1
ros-jazzy-rviz-ogre-vendor: 14.1.8-1 → 14.1.10-1
ros-jazzy-rviz-ogre-vendor-dbgsym: 14.1.8-1 → 14.1.10-1
ros-jazzy-rviz-rendering: 14.1.8-1 → 14.1.10-1
ros-jazzy-rviz-rendering-dbgsym: 14.1.8-1 → 14.1.10-1
ros-jazzy-rviz-rendering-tests: 14.1.8-1 → 14.1.10-1
ros-jazzy-rviz-visual-testing-framework: 14.1.8-1 → 14.1.10-1
ros-jazzy-rviz2: 14.1.8-1 → 14.1.10-1
ros-jazzy-rviz2-dbgsym: 14.1.8-1 → 14.1.10-1
ros-jazzy-self-test: 4.2.2-1 → 4.2.3-1
ros-jazzy-self-test-dbgsym: 4.2.2-1 → 4.2.3-1
ros-jazzy-shared-queues-vendor: 0.26.6-1 → 0.26.7-1
ros-jazzy-slam-toolbox: 2.8.2-1 → 2.8.3-1
ros-jazzy-slam-toolbox-dbgsym: 2.8.2-1 → 2.8.3-1
ros-jazzy-spatio-temporal-voxel-layer: 2.5.4-1 → 2.5.5-1
ros-jazzy-spatio-temporal-voxel-layer-dbgsym: 2.5.4-1 → 2.5.5-1
ros-jazzy-sqlite3-vendor: 0.26.6-1 → 0.26.7-1
ros-jazzy-steering-controllers-library: 4.22.0-1 → 4.23.0-1
ros-jazzy-steering-controllers-library-dbgsym: 4.22.0-1 → 4.23.0-1
ros-jazzy-stereo-image-proc: 5.0.9-1 → 5.0.10-1
ros-jazzy-stereo-image-proc-dbgsym: 5.0.9-1 → 5.0.10-1
ros-jazzy-swri-cli-tools: 3.7.3-1 → 3.7.4-1
ros-jazzy-swri-console-util: 3.7.3-1 → 3.7.4-1
ros-jazzy-swri-console-util-dbgsym: 3.7.3-1 → 3.7.4-1
ros-jazzy-swri-dbw-interface: 3.7.3-1 → 3.7.4-1
ros-jazzy-swri-geometry-util: 3.7.3-1 → 3.7.4-1
ros-jazzy-swri-geometry-util-dbgsym: 3.7.3-1 → 3.7.4-1
ros-jazzy-swri-image-util: 3.7.3-1 → 3.7.4-1
ros-jazzy-swri-image-util-dbgsym: 3.7.3-1 → 3.7.4-1
ros-jazzy-swri-math-util: 3.7.3-1 → 3.7.4-1
ros-jazzy-swri-math-util-dbgsym: 3.7.3-1 → 3.7.4-1
ros-jazzy-swri-opencv-util: 3.7.3-1 → 3.7.4-1
ros-jazzy-swri-opencv-util-dbgsym: 3.7.3-1 → 3.7.4-1
ros-jazzy-swri-roscpp: 3.7.3-1 → 3.7.4-1
ros-jazzy-swri-roscpp-dbgsym: 3.7.3-1 → 3.7.4-1
ros-jazzy-swri-route-util: 3.7.3-1 → 3.7.4-1
ros-jazzy-swri-route-util-dbgsym: 3.7.3-1 → 3.7.4-1
ros-jazzy-swri-serial-util: 3.7.3-1 → 3.7.4-1
ros-jazzy-swri-serial-util-dbgsym: 3.7.3-1 → 3.7.4-1
ros-jazzy-swri-system-util: 3.7.3-1 → 3.7.4-1
ros-jazzy-swri-system-util-dbgsym: 3.7.3-1 → 3.7.4-1
ros-jazzy-swri-transform-util: 3.7.3-1 → 3.7.4-1
ros-jazzy-swri-transform-util-dbgsym: 3.7.3-1 → 3.7.4-1
ros-jazzy-teleop-tools: 1.7.0-1 → 1.8.0-1
ros-jazzy-teleop-tools-msgs: 1.7.0-1 → 1.8.0-1
ros-jazzy-teleop-tools-msgs-dbgsym: 1.7.0-1 → 1.8.0-1
ros-jazzy-tf2: 0.36.9-1 → 0.36.10-1
ros-jazzy-tf2-bullet: 0.36.9-1 → 0.36.10-1
ros-jazzy-tf2-dbgsym: 0.36.9-1 → 0.36.10-1
ros-jazzy-tf2-eigen: 0.36.9-1 → 0.36.10-1
ros-jazzy-tf2-eigen-kdl: 0.36.9-1 → 0.36.10-1
ros-jazzy-tf2-eigen-kdl-dbgsym: 0.36.9-1 → 0.36.10-1
ros-jazzy-tf2-geometry-msgs: 0.36.9-1 → 0.36.10-1
ros-jazzy-tf2-kdl: 0.36.9-1 → 0.36.10-1
ros-jazzy-tf2-msgs: 0.36.9-1 → 0.36.10-1
ros-jazzy-tf2-msgs-dbgsym: 0.36.9-1 → 0.36.10-1
ros-jazzy-tf2-py: 0.36.9-1 → 0.36.10-1
ros-jazzy-tf2-py-dbgsym: 0.36.9-1 → 0.36.10-1
ros-jazzy-tf2-ros: 0.36.9-1 → 0.36.10-1
ros-jazzy-tf2-ros-dbgsym: 0.36.9-1 → 0.36.10-1
ros-jazzy-tf2-ros-py: 0.36.9-1 → 0.36.10-1
ros-jazzy-tf2-sensor-msgs: 0.36.9-1 → 0.36.10-1
ros-jazzy-tf2-tools: 0.36.9-1 → 0.36.10-1
ros-jazzy-tracetools-image-pipeline: 5.0.9-1 → 5.0.10-1
ros-jazzy-tracetools-image-pipeline-dbgsym: 5.0.9-1 → 5.0.10-1
ros-jazzy-transmission-interface: 4.27.0-1 → 4.28.1-1
ros-jazzy-transmission-interface-dbgsym: 4.27.0-1 → 4.28.1-1
ros-jazzy-tricycle-controller: 4.22.0-1 → 4.23.0-1
ros-jazzy-tricycle-controller-dbgsym: 4.22.0-1 → 4.23.0-1
ros-jazzy-tricycle-steering-controller: 4.22.0-1 → 4.23.0-1
ros-jazzy-tricycle-steering-controller-dbgsym: 4.22.0-1 → 4.23.0-1
ros-jazzy-ur: 3.1.1-1 → 3.2.0-1
ros-jazzy-ur-calibration: 3.1.1-1 → 3.2.0-1
ros-jazzy-ur-calibration-dbgsym: 3.1.1-1 → 3.2.0-1
ros-jazzy-ur-controllers: 3.1.1-1 → 3.2.0-1
ros-jazzy-ur-controllers-dbgsym: 3.1.1-1 → 3.2.0-1
ros-jazzy-ur-dashboard-msgs: 3.1.1-1 → 3.2.0-1
ros-jazzy-ur-dashboard-msgs-dbgsym: 3.1.1-1 → 3.2.0-1
ros-jazzy-ur-moveit-config: 3.1.1-1 → 3.2.0-1
ros-jazzy-ur-robot-driver: 3.1.1-1 → 3.2.0-1
ros-jazzy-ur-robot-driver-dbgsym: 3.1.1-1 → 3.2.0-1
ros-jazzy-ur-simulation-gz: 2.1.0-2 → 2.2.0-1
ros-jazzy-velocity-controllers: 4.22.0-1 → 4.23.0-1
ros-jazzy-velocity-controllers-dbgsym: 4.22.0-1 → 4.23.0-1
ros-jazzy-wireless-msgs: 1.1.3-1 → 1.1.4-1
ros-jazzy-wireless-msgs-dbgsym: 1.1.3-1 → 1.1.4-1
ros-jazzy-wireless-watcher: 1.1.3-1 → 1.1.4-1
ros-jazzy-wireless-watcher-dbgsym: 1.1.3-1 → 1.1.4-1
ros-jazzy-yasmin: 3.1.0-1 → 3.2.0-1
ros-jazzy-yasmin-demos: 3.1.0-1 → 3.2.0-1
ros-jazzy-yasmin-demos-dbgsym: 3.1.0-1 → 3.2.0-1
ros-jazzy-yasmin-msgs: 3.1.0-1 → 3.2.0-1
ros-jazzy-yasmin-msgs-dbgsym: 3.1.0-1 → 3.2.0-1
ros-jazzy-yasmin-ros: 3.1.0-1 → 3.2.0-1
ros-jazzy-yasmin-viewer: 3.1.0-1 → 3.2.0-1
ros-jazzy-zstd-vendor: 0.26.6-1 → 0.26.7-1

Removed Packages [3]:

ros-jazzy-canopen-ros2-controllers
ros-jazzy-canopen-ros2-controllers-dbgsym
ros-jazzy-canopen-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:

Alberto Tudela
Alejandro Hernandez
Alejandro Hernandez Cordero
Alejandro Hernández
Alexander Gutenkunst
Alexey Merzlyakov
Analog Devices
Apex.AI, Inc.
Audrow Nash
Austin Hendrix
Bence Magyar
Berkay Karaman
Bernd Pfrommer
Blake Anderson
Brandon Ong
Brian Wilcox
Carl Delsey
Carlos Orduno
Chittaranjan Srinivas Swaminathan
Chris Iverach-Brereton
Chris Lalancette
Christian Henkel
Christian Rauch
Daan Wijffels
David V. Lu!!
Dharini Dutia
Enrique Fernandez
Felix Exner
Fictionlab
Foxglove
Geoffrey Biggs
Henning Kayser
Ivan Paunovic
Jean-Pierre Busch
Jose-Luis Blanco-Claraco
Luis Camero
M. Fatih Cırıt
Marc Alban
Matej Vargovcik
Michael Görner
Michael Jeronimo
Michael Orlov
Miguel Ángel González Santamarta
Mohammad Haghighipanah
MoveIt Release Team
Peter David Fagan
Pyo
ROS Tooling Working Group
Rob Fisher
Roni Kreinin
Ryohsuke Mitsudome
Southwest Research Institute
Steve Macenski
Takagi, Isamu
Temkei Kem
Tim Clephas
Timo Röhling
Tony Baltovski
Vincent Rabaud
Víctor Mayoral-Vilches
Yukihiro Saito
Yutaka Kondo
geoff
kminoda
miguel
rkreinin
steve
steve macenski

Enjoy! m

1 post - 1 participant

Read full topic

https://discourse.ros.org/t/new-packages-and-patch-release-5-for-jazzy-jalisco-2025-04-30/43464

ROS Discourse General: ROS Deliberation Community Group Meeting - May 5, 2025

The next ROS Deliberation Community Group meeting will be on 2025-05-05T15:00:00Z UTC.

Google Meet link: https://meet.google.com/njs-ieym-dgk

Agenda:

Deliberation tool spotlight: TreeSense - VSCode extension for BehaviorTree.CPP XML files.
Survey: Benefits and challenges for adopting behavior trees
Open discussion: Machine Learning (ML) policies in the ROS 2 deliberation stack
- Motivating example: Flatland Reinforcement Learning tutorial using ROS 2

Feel free to propose additional agenda items, join the mailing list, or the Discord server.

- Sebastian

2 posts - 2 participants

Read full topic

https://discourse.ros.org/t/ros-deliberation-community-group-meeting-may-5-2025/43450

ROS Discourse General: Smart Turtle Powered by Behavior Trees, ROS2 & Groot! 🐢

Hey ROS community!
I’m excited to share a fun and educational project I’ve been working on using ROS2, BehaviorTree.CPP, and Groot to control a smart turtle in the classic turtlesim simulation!

Project Overview

This project uses a Behavior Tree (BT) to manage the robot’s decision-making based on its battery level .

If the battery is high → the turtle navigates to its assigned goals.
If the battery is low → it automatically moves to a charging station, recharges, and then resumes its mission.

Key Features:

Battery level monitoring and automatic charging behavior
Goal-based movement with adjustable speed and duration
Pen color changes depending on the turtle’s current goal
Dynamic background color updates based on robot state
Behavior Tree visualization, execution, and debugging using Groot

Why Behavior Trees?

Instead of relying on deeply nested code, Behavior Trees structure robot logic in a visual and modular way. They simplify complex decisions and transitions between tasks — making development and debugging much easier, especially in ROS2.

this is Github rebo

simplescreenrecorder-2025-04-29_15.06.52

3 posts - 2 participants

Read full topic

https://discourse.ros.org/t/smart-turtle-powered-by-behavior-trees-ros2-groot/43449

ROS Discourse General: OSRA TGC meeting minutes for March, 2025

The meeting minutes for the regular meeting of the Technical Governance Committee held on the 27th of March, 2025, were approved in the April meeting and are now available in the official minutes repository. You can find the complete minutes here, as well as a Markdown version below. The PDF version is the official version.

The next TGC meeting will take place in late May, 2025. The minutes of the April meeting should be approved in that meeting and posted publicly shortly thereafter.

TECHNICAL GOVERNANCE COMMITTEE

MEETING MINUTES

27 MAR 2025 / 22:00-23:30 UTC / VIRTUAL VIA ZOOM

ATTENDEES

OSRF:

Geoff Biggs (TGC Chair)
Kat Scott (Developer Advocate)
Vanessa Yamzon Orsi (Secretary)
Vicky Brasseur (OSRA Governance Advisor)

OSRA Delegates/TGC Reps:

Bence Magyar (ros-controls PMC Lead)
Carlos Aguero, (Gazebo Lead Proxy)
Clara Berendesen (Infra PMC Representative)
Christian Henkel (Gold Rep, Bosch)
Daniel Gordon (Gold Rep, Huawei)
David Lu!! (Individual Rep)
Hemal Shah (Platinum Rep, NVIDIA)
Maria Vergo (Silver Rep, ROS-I)
Michael Carroll (ROS PMC Interim Lead)
Michael Grey (Open-RMF)
Michel Hidalgo (Silver Rep, Ekumen)
Steve Peters (Gazebo)
Steven! Ragnarok (Infrastructure PMC Lead)
Tully Foote (Platinum Rep, Intrinsic)
Zhaoyuan Cheng (Platinum Rep, Qualcomm)

OSRA Observers

Carmelo Di Franco (Aitronik)
Henning Kayser (PickNik)
Nick Hehr (Viam)
Tom Panzarella (Seegrid)
Todd Sutton (Zachry)

AGENDA

Geoff Biggs, TGC Chair called the meeting to order at 22:06 on 27 Mar 2025 UTC

Existing Business

Confirmation of minutes of meeting TGC-20250227-Regular
- Approved by consensus
Project reports
- Project update: ROS
  - Presented by Michael Carroll, PMC Lead
    - Committer updates:
      - Christophe Bedard from Apex has proposed to mentor Emerson Knapp from Polymath Robotics to move up from Committer to PMC member
      - Janosch Machowinski Is now a full Committer for the ROS project
    - Official votes coming up:
      - Change needed in REP-2005 to rename FastRTPS
      - Remove ROS Geometry 2 from core-maintained repositories
      - Proposed schedule for ROS 1 Noetic EOL - tentatively scheduled for May 31, 2025
    - ROS Developments:
      - Completed the pixi installation for Windows CI and user installations; great community feedback received for ease of use
      - 1.5 weeks away from Kilted feature freeze, working on getting rmw-zenoh to Tier 1 status beforehand
      - Also working on FastDDS updates to 3.2.x, action introspection, rclpy executor implementation
      - Moving python launch files to default the community to xml and yaml
      - Common simulation interfaces pull request completed
    - GSoC season underway
    - docs.ros.org rebrand has launched
    - Key Kilted release dates
    - PMC will start L-Turtle roadmap, will seek TGC input
- Project update: Gazebo
  - Presented by Carlos Aguero, PMC Member on behalf of the Project Leader
    - Launched effort to collect data on CI jobs in order to understand trends and usage to improve efficiency on allocating resources
    - Testing migration from BC package to Conda to reproduce cloud environment for testing and debugging
    - Prototype for zenoh on gz-transport considered complete, includes basic pubsub and basic services. Design document circulated to the community for feedback.
    - Efforts to migrate from qt5 to 6 in the summer
    - Exploring possibility of removing immersion numbers from package names to reduce overhead for releases; proposal will remove ability to run side-by-side versions of Gazebo, considering implications vs more efficiency for releases
    - Reducing discrepancy between optical frames between ROS and Gazebo via the rosbridge
    - Deprecating gz launch in favor of other more used tools, tutorials now available for other methods
    - Efforts to increase contributions - curated list of issues from maintainers, focused on making them more scoped and prioritized per repo then made public to the community. Reception has been great and issues are being crossed off.
    - GSoC season in progress
- Project update: Open-RMF
  - Presented by Michael Grey, PMC Lead
    - Runtime generation of workflows now supports buffers useful for synchronizing multiple threads that are running simultaneously.
    - We will soon support a concept of sections for runtime generated workflows
    - Adding new capability called dynamic events to allow external support for more complex behaviors as requested by the community
- Project update: ROS Controls
  - Presented by Bence Magyar, PMC Lead
    - Started adding organization-wide templates for issue report, feature request and useful websites following the ROS project
    - Created a ros2 control cmake package and to help move users from Humble, also created gz ros2 control in addition to ignition ros2 control for seamless migration
  - Excited about the structured parameter handling project
  - Participating in GSoC with two projects
  - Reiterated call for input on adding joint limit support
- Project update: Infrastructure
  - Presented by Steven! Ragnarok, PMC Lead
    - ROS Build farm now runs Ubuntu 24.0.4
    - Support for EmPy 4
    - Support for non-GPU Windows agents on the Gazebo Build farm
    - Build farmers working on a scaling schedule to try and optimize resources and improve throughout on the Gazebo CI
    - Assessed security risks from a broad software supply chain compromise in a popular GitHub action
      - Conclusion: no impact on OSRF projects, tracked down instances and prevented any chance of compromise
    - RedHat’s Fedora Robotics SIG is exploring the possibility of getting Fedora built binaries on the official ROS Build farm
    - Upcoming: Getting ROS migration distro script ready to be used for Kilted branching, moving snapshot and bootstrap servers, getting Windows 11 compatible server running on the ROS 2 CI farm
Existing Business
- Status of SIGs/TCs
  - Technical Committee on Enhancement Proposal Processes
    - Goal: Upgrade and improvements over REP
    - Chair: Geoff Biggs
    - Members: PMC Leads
    - Update:
      - Geoff presented the current draft of the Enhancement Proposal Process steps, from drafting to ratification. The high-level planning is now complete.
      - Next steps:
        
        Documentation of detailed process description, including implementation, tools, steps, discussion forums, document archiving, example/s.
        
        Feedback from PMCs and TGC
      - Vote requested: Approve extension of TC to June 2025 and update members (removing 2 who are now unavailable and adding 1 new member)
        
        Approved by consensus
  - SIG on Interoperability
    - Chair: Michael Grey
    - Grey presented a preview of how async programming will work on rclrs, observed uptick in activity of community users on rclrs GitHub
- Results of vote to recommend adoption of GAI policy
  - Following the failed motion prior to the previous TGC meeting, this item needs to be revisited and a second attempt made at explicitly accepting or rejecting the proposed Generative AI Policy and Guidance. No changes have been made since the previous vote.
    - Approved by consensus
- Discussion on communications and processes in the TGC
  - An in-depth discussion on the communications methods and processes used in the TGC was held.
  - Data from the survey sent to all TGC Members was discussed, including pros and cons of various platforms, what features are requested, effort to standardize across projects and groups if possible to allow for easier oversight and cross-collaboration.
  - Suggestions for improving interactions during TGC meetings.
  - Explored ideas for asynchronous communication and collaboration.
  - Discussed processes around decision-making, with the goal of understanding how we can ensure all TGC Members have enough time to participate fully. Issues discussed include: time to discuss with their constituents (other Gold and Silver OSRA members, their Project’s PMC, or their organisation, depending on the TGC Member); how votes are carried out within and outside of meetings; inbuilt process delays between raising a topic and making the decision; enabling dissent; open proposals of agenda items; and increasing between-meeting discussion amongst TGC Members.
  - Location of pertinent documents and reference materials for items discussed during meetings.
    - Action Item: The TGC Chair will write up the items discussed and circulate to the TGC for further review and iteration.

New Business

None

Other Items

None

Adjournment - Geoff Biggs adjourned the meeting at 22:56 UTC.

ACTION ITEMS

The meeting minutes will be circulated to the TGC for review and approval before the next meeting by the TGC Chair.
The TGC Chair will write up the items discussed regarding communication methods and procedures within the TGC/OSRA and circulate to the TGC for further review and iteration.

8 posts - 5 participants

Read full topic

https://discourse.ros.org/t/osra-tgc-meeting-minutes-for-march-2025/43425

ROS Discourse General: ROS News for the Week of April 21st, 2025

ROS News for the Week of April 21st, 2025

Join us next Thursday, 2025-05-01T16:00:00Z UTC to kick off the Kilted Kaiju Test and Tutorial Party We need your help to beta test Kilted!

If you are in the Bay Area join us on Wednesday, April 30th, for ROS By-The-Bay. I will have Kilted stickers!

Join us next Wednesday, 2025-04-30T16:00:00Z UTC, for our monthly Gazebo Community Meeting.

gene1-deepblue-small
THIS IS HUGE! The fine folks over at Hugging Face / Pollen Robotics just open sourced the entire stack for Pollen Robotic’s Reachy robot!

trackers
The fine folks at RoboFlow have released a unified open source library for object tracking featuring clean room re-implementations of the leading multi-object tracking algorithms. – source

TurtleBot3 81 ROS 2 Humble Home Service Challenge

Our friends at Robotis have put together a fantastic tutorial on how to simulate your own home service robot using the TurtleBot3, ROS 2, and Gazebo!

Events

News

ROS

Got a Minute?

At this week’s waffle meeting we had a set of issues came up and we would really like the community’s help in solving them, A new contributor with a static analyzer has been analyzing RViz2 and then filing issues where necessary. We need the community’s help to verify that these issue are indeed actual issues and to then fix them as necessary.

1 post - 1 participant

Read full topic

https://discourse.ros.org/t/ros-news-for-the-week-of-april-21st-2025/43400

ROS Discourse General: New packages for Humble Hawksbill 2025-04-25

Package Updates for humble

Added Packages [37]:

ros-humble-aruco-markers: 0.0.2-1
ros-humble-aruco-markers-dbgsym: 0.0.2-1
ros-humble-aruco-markers-msgs: 0.0.2-1
ros-humble-aruco-markers-msgs-dbgsym: 0.0.2-1
ros-humble-autoware-internal-metric-msgs: 1.8.1-1
ros-humble-autoware-internal-metric-msgs-dbgsym: 1.8.1-1
ros-humble-autoware-msgs: 1.6.0-1
ros-humble-diagnostic-remote-logging: 4.0.3-1
ros-humble-diagnostic-remote-logging-dbgsym: 4.0.3-1
ros-humble-etsi-its-mcm-uulm-coding: 3.2.0-1
ros-humble-etsi-its-mcm-uulm-coding-dbgsym: 3.2.0-1
ros-humble-etsi-its-mcm-uulm-conversion: 3.2.0-1
ros-humble-etsi-its-mcm-uulm-msgs: 3.2.0-1
ros-humble-etsi-its-mcm-uulm-msgs-dbgsym: 3.2.0-1
ros-humble-fkie-message-filters: 3.0.2-1
ros-humble-fkie-message-filters-dbgsym: 3.0.2-1
ros-humble-franka-inria-inverse-dynamics-solver: 1.0.0-1
ros-humble-franka-inria-inverse-dynamics-solver-dbgsym: 1.0.0-1
ros-humble-gz-ros2-control: 0.7.14-1
ros-humble-gz-ros2-control-dbgsym: 0.7.14-1
ros-humble-gz-ros2-control-demos: 0.7.14-1
ros-humble-gz-ros2-control-demos-dbgsym: 0.7.14-1
ros-humble-gz-ros2-control-tests: 0.7.14-1
ros-humble-inverse-dynamics-solver: 1.0.0-1
ros-humble-inverse-dynamics-solver-dbgsym: 1.0.0-1
ros-humble-kdl-inverse-dynamics-solver: 1.0.0-1
ros-humble-kdl-inverse-dynamics-solver-dbgsym: 1.0.0-1
ros-humble-ld08-driver: 1.1.3-1
ros-humble-ld08-driver-dbgsym: 1.1.3-1
ros-humble-open-manipulator-x-bringup: 3.0.1-1
ros-humble-open-manipulator-x-description: 3.0.1-1
ros-humble-open-manipulator-x-gui: 3.0.1-1
ros-humble-open-manipulator-x-gui-dbgsym: 3.0.1-1
ros-humble-open-manipulator-x-playground: 3.0.1-1
ros-humble-open-manipulator-x-playground-dbgsym: 3.0.1-1
ros-humble-ur10-inverse-dynamics-solver: 1.0.0-1
ros-humble-ur10-inverse-dynamics-solver-dbgsym: 1.0.0-1

Updated Packages [395]:

ros-humble-ackermann-steering-controller: 2.43.0-1 → 2.44.0-1
ros-humble-ackermann-steering-controller-dbgsym: 2.43.0-1 → 2.44.0-1
ros-humble-admittance-controller: 2.43.0-1 → 2.44.0-1
ros-humble-admittance-controller-dbgsym: 2.43.0-1 → 2.44.0-1
ros-humble-autoware-cmake: 1.0.1-1 → 1.0.2-1
ros-humble-autoware-common-msgs: 1.3.0-1 → 1.6.0-1
ros-humble-autoware-common-msgs-dbgsym: 1.3.0-1 → 1.6.0-1
ros-humble-autoware-control-msgs: 1.3.0-1 → 1.6.0-1
ros-humble-autoware-control-msgs-dbgsym: 1.3.0-1 → 1.6.0-1
ros-humble-autoware-internal-debug-msgs: 1.5.0-1 → 1.8.1-1
ros-humble-autoware-internal-debug-msgs-dbgsym: 1.5.0-1 → 1.8.1-1
ros-humble-autoware-internal-msgs: 1.5.0-1 → 1.8.1-1
ros-humble-autoware-internal-msgs-dbgsym: 1.5.0-1 → 1.8.1-1
ros-humble-autoware-internal-perception-msgs: 1.5.0-1 → 1.8.1-1
ros-humble-autoware-internal-perception-msgs-dbgsym: 1.5.0-1 → 1.8.1-1
ros-humble-autoware-internal-planning-msgs: 1.5.0-1 → 1.8.1-1
ros-humble-autoware-internal-planning-msgs-dbgsym: 1.5.0-1 → 1.8.1-1
ros-humble-autoware-lanelet2-extension: 0.6.3-1 → 0.7.0-1
ros-humble-autoware-lanelet2-extension-dbgsym: 0.6.3-1 → 0.7.0-1
ros-humble-autoware-lanelet2-extension-python: 0.6.3-1 → 0.7.0-1
ros-humble-autoware-lanelet2-extension-python-dbgsym: 0.6.3-1 → 0.7.0-1
ros-humble-autoware-lint-common: 1.0.1-1 → 1.0.2-1
ros-humble-autoware-localization-msgs: 1.3.0-1 → 1.6.0-1
ros-humble-autoware-localization-msgs-dbgsym: 1.3.0-1 → 1.6.0-1
ros-humble-autoware-map-msgs: 1.3.0-1 → 1.6.0-1
ros-humble-autoware-map-msgs-dbgsym: 1.3.0-1 → 1.6.0-1
ros-humble-autoware-perception-msgs: 1.3.0-1 → 1.6.0-1
ros-humble-autoware-perception-msgs-dbgsym: 1.3.0-1 → 1.6.0-1
ros-humble-autoware-planning-msgs: 1.3.0-1 → 1.6.0-1
ros-humble-autoware-planning-msgs-dbgsym: 1.3.0-1 → 1.6.0-1
ros-humble-autoware-sensing-msgs: 1.3.0-1 → 1.6.0-1
ros-humble-autoware-sensing-msgs-dbgsym: 1.3.0-1 → 1.6.0-1
ros-humble-autoware-system-msgs: 1.3.0-1 → 1.6.0-1
ros-humble-autoware-system-msgs-dbgsym: 1.3.0-1 → 1.6.0-1
ros-humble-autoware-v2x-msgs: 1.3.0-1 → 1.6.0-1
ros-humble-autoware-v2x-msgs-dbgsym: 1.3.0-1 → 1.6.0-1
ros-humble-autoware-vehicle-msgs: 1.3.0-1 → 1.6.0-1
ros-humble-autoware-vehicle-msgs-dbgsym: 1.3.0-1 → 1.6.0-1
ros-humble-bicycle-steering-controller: 2.43.0-1 → 2.44.0-1
ros-humble-bicycle-steering-controller-dbgsym: 2.43.0-1 → 2.44.0-1
ros-humble-camera-ros: 0.3.0-1 → 0.4.0-1
ros-humble-camera-ros-dbgsym: 0.3.0-1 → 0.4.0-1
ros-humble-chomp-motion-planner: 2.5.8-1 → 2.5.9-1
ros-humble-chomp-motion-planner-dbgsym: 2.5.8-1 → 2.5.9-1
ros-humble-clearpath-common: 1.2.0-1 → 1.3.2-1
ros-humble-clearpath-config: 1.2.0-1 → 1.3.0-1
ros-humble-clearpath-control: 1.2.0-1 → 1.3.2-1
ros-humble-clearpath-customization: 1.2.0-1 → 1.3.2-1
ros-humble-clearpath-description: 1.2.0-1 → 1.3.2-1
ros-humble-clearpath-generator-common: 1.2.0-1 → 1.3.2-1
ros-humble-clearpath-generator-common-dbgsym: 1.2.0-1 → 1.3.2-1
ros-humble-clearpath-generator-gz: 1.0.0-1 → 1.3.0-1
ros-humble-clearpath-gz: 1.0.0-1 → 1.3.0-1
ros-humble-clearpath-manipulators: 1.2.0-1 → 1.3.2-1
ros-humble-clearpath-manipulators-description: 1.2.0-1 → 1.3.2-1
ros-humble-clearpath-mecanum-drive-controller: 0.1.0-1 → 0.1.1-1
ros-humble-clearpath-mecanum-drive-controller-dbgsym: 0.1.0-1 → 0.1.1-1
ros-humble-clearpath-mounts-description: 1.2.0-1 → 1.3.2-1
ros-humble-clearpath-platform-description: 1.2.0-1 → 1.3.2-1
ros-humble-clearpath-ros2-socketcan-interface: 1.0.1-2 → 1.0.2-1
ros-humble-clearpath-ros2-socketcan-interface-dbgsym: 1.0.1-2 → 1.0.2-1
ros-humble-clearpath-sensors-description: 1.2.0-1 → 1.3.2-1
ros-humble-clearpath-simulator: 1.0.0-1 → 1.3.0-1
ros-humble-control-toolbox: 3.6.0-1 → 3.6.1-1
ros-humble-control-toolbox-dbgsym: 3.6.0-1 → 3.6.1-1
ros-humble-controller-interface: 2.49.0-1 → 2.50.0-1
ros-humble-controller-interface-dbgsym: 2.49.0-1 → 2.50.0-1
ros-humble-controller-manager: 2.49.0-1 → 2.50.0-1
ros-humble-controller-manager-dbgsym: 2.49.0-1 → 2.50.0-1
ros-humble-controller-manager-msgs: 2.49.0-1 → 2.50.0-1
ros-humble-controller-manager-msgs-dbgsym: 2.49.0-1 → 2.50.0-1
ros-humble-diagnostic-aggregator: 4.0.2-1 → 4.0.3-1
ros-humble-diagnostic-aggregator-dbgsym: 4.0.2-1 → 4.0.3-1
ros-humble-diagnostic-common-diagnostics: 4.0.2-1 → 4.0.3-1
ros-humble-diagnostic-updater: 4.0.2-1 → 4.0.3-1
ros-humble-diagnostic-updater-dbgsym: 4.0.2-1 → 4.0.3-1
ros-humble-diagnostics: 4.0.2-1 → 4.0.3-1
ros-humble-diff-drive-controller: 2.43.0-1 → 2.44.0-1
ros-humble-diff-drive-controller-dbgsym: 2.43.0-1 → 2.44.0-1
ros-humble-dynamixel-hardware-interface: 1.4.0-1 → 1.4.3-1
ros-humble-dynamixel-hardware-interface-dbgsym: 1.4.0-1 → 1.4.3-1
ros-humble-dynamixel-sdk: 3.8.2-1 → 3.8.3-1
ros-humble-dynamixel-sdk-custom-interfaces: 3.8.2-1 → 3.8.3-1
ros-humble-dynamixel-sdk-custom-interfaces-dbgsym: 3.8.2-1 → 3.8.3-1
ros-humble-dynamixel-sdk-dbgsym: 3.8.2-1 → 3.8.3-1
ros-humble-dynamixel-sdk-examples: 3.8.2-1 → 3.8.3-1
ros-humble-dynamixel-sdk-examples-dbgsym: 3.8.2-1 → 3.8.3-1
ros-humble-effort-controllers: 2.43.0-1 → 2.44.0-1
ros-humble-effort-controllers-dbgsym: 2.43.0-1 → 2.44.0-1
ros-humble-etsi-its-cam-coding: 3.1.0-1 → 3.2.0-1
ros-humble-etsi-its-cam-coding-dbgsym: 3.1.0-1 → 3.2.0-1
ros-humble-etsi-its-cam-conversion: 3.1.0-1 → 3.2.0-1
ros-humble-etsi-its-cam-msgs: 3.1.0-1 → 3.2.0-1
ros-humble-etsi-its-cam-msgs-dbgsym: 3.1.0-1 → 3.2.0-1
ros-humble-etsi-its-cam-ts-coding: 3.1.0-1 → 3.2.0-1
ros-humble-etsi-its-cam-ts-coding-dbgsym: 3.1.0-1 → 3.2.0-1
ros-humble-etsi-its-cam-ts-conversion: 3.1.0-1 → 3.2.0-1
ros-humble-etsi-its-cam-ts-msgs: 3.1.0-1 → 3.2.0-1
ros-humble-etsi-its-cam-ts-msgs-dbgsym: 3.1.0-1 → 3.2.0-1
ros-humble-etsi-its-coding: 3.1.0-1 → 3.2.0-1
ros-humble-etsi-its-conversion: 3.1.0-1 → 3.2.0-1
ros-humble-etsi-its-conversion-dbgsym: 3.1.0-1 → 3.2.0-1
ros-humble-etsi-its-cpm-ts-coding: 3.1.0-1 → 3.2.0-1
ros-humble-etsi-its-cpm-ts-coding-dbgsym: 3.1.0-1 → 3.2.0-1
ros-humble-etsi-its-cpm-ts-conversion: 3.1.0-1 → 3.2.0-1
ros-humble-etsi-its-cpm-ts-msgs: 3.1.0-1 → 3.2.0-1
ros-humble-etsi-its-cpm-ts-msgs-dbgsym: 3.1.0-1 → 3.2.0-1
ros-humble-etsi-its-denm-coding: 3.1.0-1 → 3.2.0-1
ros-humble-etsi-its-denm-coding-dbgsym: 3.1.0-1 → 3.2.0-1
ros-humble-etsi-its-denm-conversion: 3.1.0-1 → 3.2.0-1
ros-humble-etsi-its-denm-msgs: 3.1.0-1 → 3.2.0-1
ros-humble-etsi-its-denm-msgs-dbgsym: 3.1.0-1 → 3.2.0-1
ros-humble-etsi-its-denm-ts-coding: 3.1.0-1 → 3.2.0-1
ros-humble-etsi-its-denm-ts-coding-dbgsym: 3.1.0-1 → 3.2.0-1
ros-humble-etsi-its-denm-ts-conversion: 3.1.0-1 → 3.2.0-1
ros-humble-etsi-its-denm-ts-msgs: 3.1.0-1 → 3.2.0-1
ros-humble-etsi-its-denm-ts-msgs-dbgsym: 3.1.0-1 → 3.2.0-1
ros-humble-etsi-its-mapem-ts-coding: 3.1.0-1 → 3.2.0-1
ros-humble-etsi-its-mapem-ts-coding-dbgsym: 3.1.0-1 → 3.2.0-1
ros-humble-etsi-its-mapem-ts-conversion: 3.1.0-1 → 3.2.0-1
ros-humble-etsi-its-mapem-ts-msgs: 3.1.0-1 → 3.2.0-1
ros-humble-etsi-its-mapem-ts-msgs-dbgsym: 3.1.0-1 → 3.2.0-1
ros-humble-etsi-its-messages: 3.1.0-1 → 3.2.0-1
ros-humble-etsi-its-msgs: 3.1.0-1 → 3.2.0-1
ros-humble-etsi-its-msgs-utils: 3.1.0-1 → 3.2.0-1
ros-humble-etsi-its-primitives-conversion: 3.1.0-1 → 3.2.0-1
ros-humble-etsi-its-rviz-plugins: 3.1.0-1 → 3.2.0-1
ros-humble-etsi-its-rviz-plugins-dbgsym: 3.1.0-1 → 3.2.0-1
ros-humble-etsi-its-spatem-ts-coding: 3.1.0-1 → 3.2.0-1
ros-humble-etsi-its-spatem-ts-coding-dbgsym: 3.1.0-1 → 3.2.0-1
ros-humble-etsi-its-spatem-ts-conversion: 3.1.0-1 → 3.2.0-1
ros-humble-etsi-its-spatem-ts-msgs: 3.1.0-1 → 3.2.0-1
ros-humble-etsi-its-spatem-ts-msgs-dbgsym: 3.1.0-1 → 3.2.0-1
ros-humble-etsi-its-vam-ts-coding: 3.1.0-1 → 3.2.0-1
ros-humble-etsi-its-vam-ts-coding-dbgsym: 3.1.0-1 → 3.2.0-1
ros-humble-etsi-its-vam-ts-conversion: 3.1.0-1 → 3.2.0-1
ros-humble-etsi-its-vam-ts-msgs: 3.1.0-1 → 3.2.0-1
ros-humble-etsi-its-vam-ts-msgs-dbgsym: 3.1.0-1 → 3.2.0-1
ros-humble-ffmpeg-image-transport: 2.0.1-1 → 2.0.2-1
ros-humble-ffmpeg-image-transport-dbgsym: 2.0.1-1 → 2.0.2-1
ros-humble-flir-camera-description: 3.0.0-1 → 3.0.1-1
ros-humble-flir-camera-msgs: 3.0.0-1 → 3.0.1-1
ros-humble-flir-camera-msgs-dbgsym: 3.0.0-1 → 3.0.1-1
ros-humble-force-torque-sensor-broadcaster: 2.43.0-1 → 2.44.0-1
ros-humble-force-torque-sensor-broadcaster-dbgsym: 2.43.0-1 → 2.44.0-1
ros-humble-forward-command-controller: 2.43.0-1 → 2.44.0-1
ros-humble-forward-command-controller-dbgsym: 2.43.0-1 → 2.44.0-1
ros-humble-foxglove-compressed-video-transport: 1.0.1-1 → 1.0.2-1
ros-humble-foxglove-compressed-video-transport-dbgsym: 1.0.1-1 → 1.0.2-1
ros-humble-gpio-controllers: 2.43.0-1 → 2.44.0-1
ros-humble-gpio-controllers-dbgsym: 2.43.0-1 → 2.44.0-1
ros-humble-gripper-controllers: 2.43.0-1 → 2.44.0-1
ros-humble-gripper-controllers-dbgsym: 2.43.0-1 → 2.44.0-1
ros-humble-hardware-interface: 2.49.0-1 → 2.50.0-1
ros-humble-hardware-interface-dbgsym: 2.49.0-1 → 2.50.0-1
ros-humble-hardware-interface-testing: 2.49.0-1 → 2.50.0-1
ros-humble-hardware-interface-testing-dbgsym: 2.49.0-1 → 2.50.0-1
ros-humble-ign-ros2-control: 0.7.12-1 → 0.7.14-1
ros-humble-ign-ros2-control-demos: 0.7.12-1 → 0.7.14-1
ros-humble-ign-ros2-control-demos-dbgsym: 0.7.12-1 → 0.7.14-1
ros-humble-imu-sensor-broadcaster: 2.43.0-1 → 2.44.0-1
ros-humble-imu-sensor-broadcaster-dbgsym: 2.43.0-1 → 2.44.0-1
ros-humble-joint-limits: 2.49.0-1 → 2.50.0-1
ros-humble-joint-limits-dbgsym: 2.49.0-1 → 2.50.0-1
ros-humble-joint-state-broadcaster: 2.43.0-1 → 2.44.0-1
ros-humble-joint-state-broadcaster-dbgsym: 2.43.0-1 → 2.44.0-1
ros-humble-joint-trajectory-controller: 2.43.0-1 → 2.44.0-1
ros-humble-joint-trajectory-controller-dbgsym: 2.43.0-1 → 2.44.0-1
ros-humble-leo: 1.2.4-1 → 1.3.0-1
ros-humble-leo-description: 1.2.4-1 → 1.3.0-1
ros-humble-leo-gz-bringup: 1.1.1-1 → 1.1.2-1
ros-humble-leo-gz-plugins: 1.1.1-1 → 1.1.2-1
ros-humble-leo-gz-plugins-dbgsym: 1.1.1-1 → 1.1.2-1
ros-humble-leo-gz-worlds: 1.1.1-1 → 1.1.2-1
ros-humble-leo-msgs: 1.2.4-1 → 1.3.0-1
ros-humble-leo-msgs-dbgsym: 1.2.4-1 → 1.3.0-1
ros-humble-leo-simulator: 1.1.1-1 → 1.1.2-1
ros-humble-leo-teleop: 1.2.4-1 → 1.3.0-1
ros-humble-libcaer-driver: 1.1.3-1 → 1.5.0-1
ros-humble-libcaer-driver-dbgsym: 1.1.3-1 → 1.5.0-1
ros-humble-mapviz: 2.4.5-1 → 2.4.6-1
ros-humble-mapviz-dbgsym: 2.4.5-1 → 2.4.6-1
ros-humble-mapviz-interfaces: 2.4.5-1 → 2.4.6-1
ros-humble-mapviz-interfaces-dbgsym: 2.4.5-1 → 2.4.6-1
ros-humble-mapviz-plugins: 2.4.5-1 → 2.4.6-1
ros-humble-mapviz-plugins-dbgsym: 2.4.5-1 → 2.4.6-1
ros-humble-mecanum-drive-controller: 2.43.0-1 → 2.44.0-1
ros-humble-mecanum-drive-controller-dbgsym: 2.43.0-1 → 2.44.0-1
ros-humble-message-filters: 4.3.6-1 → 4.3.7-1
ros-humble-message-filters-dbgsym: 4.3.6-1 → 4.3.7-1
ros-humble-microstrain-inertial-description: 4.5.0-1 → 4.6.0-1
ros-humble-microstrain-inertial-driver: 4.5.0-1 → 4.6.0-1
ros-humble-microstrain-inertial-driver-dbgsym: 4.5.0-1 → 4.6.0-1
ros-humble-microstrain-inertial-examples: 4.5.0-1 → 4.6.0-1
ros-humble-microstrain-inertial-msgs: 4.5.0-1 → 4.6.0-1
ros-humble-microstrain-inertial-msgs-dbgsym: 4.5.0-1 → 4.6.0-1
ros-humble-microstrain-inertial-rqt: 4.5.0-1 → 4.6.0-1
ros-humble-moveit: 2.5.8-1 → 2.5.9-1
ros-humble-moveit-chomp-optimizer-adapter: 2.5.8-1 → 2.5.9-1
ros-humble-moveit-chomp-optimizer-adapter-dbgsym: 2.5.8-1 → 2.5.9-1
ros-humble-moveit-common: 2.5.8-1 → 2.5.9-1
ros-humble-moveit-configs-utils: 2.5.8-1 → 2.5.9-1
ros-humble-moveit-core: 2.5.8-1 → 2.5.9-1
ros-humble-moveit-core-dbgsym: 2.5.8-1 → 2.5.9-1
ros-humble-moveit-hybrid-planning: 2.5.8-1 → 2.5.9-1
ros-humble-moveit-hybrid-planning-dbgsym: 2.5.8-1 → 2.5.9-1
ros-humble-moveit-kinematics: 2.5.8-1 → 2.5.9-1
ros-humble-moveit-kinematics-dbgsym: 2.5.8-1 → 2.5.9-1
ros-humble-moveit-planners: 2.5.8-1 → 2.5.9-1
ros-humble-moveit-planners-chomp: 2.5.8-1 → 2.5.9-1
ros-humble-moveit-planners-chomp-dbgsym: 2.5.8-1 → 2.5.9-1
ros-humble-moveit-planners-ompl: 2.5.8-1 → 2.5.9-1
ros-humble-moveit-planners-ompl-dbgsym: 2.5.8-1 → 2.5.9-1
ros-humble-moveit-plugins: 2.5.8-1 → 2.5.9-1
ros-humble-moveit-resources-prbt-ikfast-manipulator-plugin: 2.5.8-1 → 2.5.9-1
ros-humble-moveit-resources-prbt-ikfast-manipulator-plugin-dbgsym: 2.5.8-1 → 2.5.9-1
ros-humble-moveit-resources-prbt-moveit-config: 2.5.8-1 → 2.5.9-1
ros-humble-moveit-resources-prbt-pg70-support: 2.5.8-1 → 2.5.9-1
ros-humble-moveit-resources-prbt-support: 2.5.8-1 → 2.5.9-1
ros-humble-moveit-ros: 2.5.8-1 → 2.5.9-1
ros-humble-moveit-ros-benchmarks: 2.5.8-1 → 2.5.9-1
ros-humble-moveit-ros-benchmarks-dbgsym: 2.5.8-1 → 2.5.9-1
ros-humble-moveit-ros-control-interface: 2.5.8-1 → 2.5.9-1
ros-humble-moveit-ros-control-interface-dbgsym: 2.5.8-1 → 2.5.9-1
ros-humble-moveit-ros-move-group: 2.5.8-1 → 2.5.9-1
ros-humble-moveit-ros-move-group-dbgsym: 2.5.8-1 → 2.5.9-1
ros-humble-moveit-ros-occupancy-map-monitor: 2.5.8-1 → 2.5.9-1
ros-humble-moveit-ros-occupancy-map-monitor-dbgsym: 2.5.8-1 → 2.5.9-1
ros-humble-moveit-ros-perception: 2.5.8-1 → 2.5.9-1
ros-humble-moveit-ros-perception-dbgsym: 2.5.8-1 → 2.5.9-1
ros-humble-moveit-ros-planning: 2.5.8-1 → 2.5.9-1
ros-humble-moveit-ros-planning-dbgsym: 2.5.8-1 → 2.5.9-1
ros-humble-moveit-ros-planning-interface: 2.5.8-1 → 2.5.9-1
ros-humble-moveit-ros-planning-interface-dbgsym: 2.5.8-1 → 2.5.9-1
ros-humble-moveit-ros-robot-interaction: 2.5.8-1 → 2.5.9-1
ros-humble-moveit-ros-robot-interaction-dbgsym: 2.5.8-1 → 2.5.9-1
ros-humble-moveit-ros-visualization: 2.5.8-1 → 2.5.9-1
ros-humble-moveit-ros-visualization-dbgsym: 2.5.8-1 → 2.5.9-1
ros-humble-moveit-ros-warehouse: 2.5.8-1 → 2.5.9-1
ros-humble-moveit-ros-warehouse-dbgsym: 2.5.8-1 → 2.5.9-1
ros-humble-moveit-runtime: 2.5.8-1 → 2.5.9-1
ros-humble-moveit-servo: 2.5.8-1 → 2.5.9-1
ros-humble-moveit-servo-dbgsym: 2.5.8-1 → 2.5.9-1
ros-humble-moveit-setup-app-plugins: 2.5.8-1 → 2.5.9-1
ros-humble-moveit-setup-app-plugins-dbgsym: 2.5.8-1 → 2.5.9-1
ros-humble-moveit-setup-assistant: 2.5.8-1 → 2.5.9-1
ros-humble-moveit-setup-assistant-dbgsym: 2.5.8-1 → 2.5.9-1
ros-humble-moveit-setup-controllers: 2.5.8-1 → 2.5.9-1
ros-humble-moveit-setup-controllers-dbgsym: 2.5.8-1 → 2.5.9-1
ros-humble-moveit-setup-core-plugins: 2.5.8-1 → 2.5.9-1
ros-humble-moveit-setup-core-plugins-dbgsym: 2.5.8-1 → 2.5.9-1
ros-humble-moveit-setup-framework: 2.5.8-1 → 2.5.9-1
ros-humble-moveit-setup-framework-dbgsym: 2.5.8-1 → 2.5.9-1
ros-humble-moveit-setup-srdf-plugins: 2.5.8-1 → 2.5.9-1
ros-humble-moveit-setup-srdf-plugins-dbgsym: 2.5.8-1 → 2.5.9-1
ros-humble-moveit-simple-controller-manager: 2.5.8-1 → 2.5.9-1
ros-humble-moveit-simple-controller-manager-dbgsym: 2.5.8-1 → 2.5.9-1
ros-humble-mp2p-icp: 1.6.6-1 → 1.6.7-1
ros-humble-mp2p-icp-dbgsym: 1.6.6-1 → 1.6.7-1
ros-humble-multires-image: 2.4.5-1 → 2.4.6-1
ros-humble-multires-image-dbgsym: 2.4.5-1 → 2.4.6-1
ros-humble-ntrip-client: 1.4.0-1 → 1.4.1-1
ros-humble-off-highway-can: 0.7.0-1 → 0.8.0-1
ros-humble-off-highway-can-dbgsym: 0.7.0-1 → 0.8.0-1
ros-humble-off-highway-general-purpose-radar: 0.7.0-1 → 0.8.0-1
ros-humble-off-highway-general-purpose-radar-dbgsym: 0.7.0-1 → 0.8.0-1
ros-humble-off-highway-general-purpose-radar-msgs: 0.7.0-1 → 0.8.0-1
ros-humble-off-highway-general-purpose-radar-msgs-dbgsym: 0.7.0-1 → 0.8.0-1
ros-humble-off-highway-premium-radar-sample: 0.7.0-1 → 0.8.0-1
ros-humble-off-highway-premium-radar-sample-dbgsym: 0.7.0-1 → 0.8.0-1
ros-humble-off-highway-premium-radar-sample-msgs: 0.7.0-1 → 0.8.0-1
ros-humble-off-highway-premium-radar-sample-msgs-dbgsym: 0.7.0-1 → 0.8.0-1
ros-humble-off-highway-radar: 0.7.0-1 → 0.8.0-1
ros-humble-off-highway-radar-dbgsym: 0.7.0-1 → 0.8.0-1
ros-humble-off-highway-radar-msgs: 0.7.0-1 → 0.8.0-1
ros-humble-off-highway-radar-msgs-dbgsym: 0.7.0-1 → 0.8.0-1
ros-humble-off-highway-sensor-drivers: 0.7.0-1 → 0.8.0-1
ros-humble-off-highway-sensor-drivers-examples: 0.7.0-1 → 0.8.0-1
ros-humble-off-highway-sensor-drivers-examples-dbgsym: 0.7.0-1 → 0.8.0-1
ros-humble-off-highway-uss: 0.7.0-1 → 0.8.0-1
ros-humble-off-highway-uss-dbgsym: 0.7.0-1 → 0.8.0-1
ros-humble-off-highway-uss-msgs: 0.7.0-1 → 0.8.0-1
ros-humble-off-highway-uss-msgs-dbgsym: 0.7.0-1 → 0.8.0-1
ros-humble-pid-controller: 2.43.0-1 → 2.44.0-1
ros-humble-pid-controller-dbgsym: 2.43.0-1 → 2.44.0-1
ros-humble-pilz-industrial-motion-planner: 2.5.8-1 → 2.5.9-1
ros-humble-pilz-industrial-motion-planner-dbgsym: 2.5.8-1 → 2.5.9-1
ros-humble-pilz-industrial-motion-planner-testutils: 2.5.8-1 → 2.5.9-1
ros-humble-pilz-industrial-motion-planner-testutils-dbgsym: 2.5.8-1 → 2.5.9-1
ros-humble-polygon-demos: 1.1.0-1 → 1.2.0-1
ros-humble-polygon-demos-dbgsym: 1.1.0-1 → 1.2.0-1
ros-humble-polygon-msgs: 1.1.0-1 → 1.2.0-1
ros-humble-polygon-msgs-dbgsym: 1.1.0-1 → 1.2.0-1
ros-humble-polygon-rviz-plugins: 1.1.0-1 → 1.2.0-1
ros-humble-polygon-rviz-plugins-dbgsym: 1.1.0-1 → 1.2.0-1
ros-humble-polygon-utils: 1.1.0-1 → 1.2.0-1
ros-humble-pose-broadcaster: 2.43.0-1 → 2.44.0-1
ros-humble-pose-broadcaster-dbgsym: 2.43.0-1 → 2.44.0-1
ros-humble-position-controllers: 2.43.0-1 → 2.44.0-1
ros-humble-position-controllers-dbgsym: 2.43.0-1 → 2.44.0-1
ros-humble-range-sensor-broadcaster: 2.43.0-1 → 2.44.0-1
ros-humble-range-sensor-broadcaster-dbgsym: 2.43.0-1 → 2.44.0-1
ros-humble-realtime-tools: 2.12.0-1 → 2.13.0-1
ros-humble-realtime-tools-dbgsym: 2.12.0-1 → 2.13.0-1
ros-humble-ros2-control: 2.49.0-1 → 2.50.0-1
ros-humble-ros2-control-test-assets: 2.49.0-1 → 2.50.0-1
ros-humble-ros2-controllers: 2.43.0-1 → 2.44.0-1
ros-humble-ros2-controllers-test-nodes: 2.43.0-1 → 2.44.0-1
ros-humble-ros2controlcli: 2.49.0-1 → 2.50.0-1
ros-humble-rqt-controller-manager: 2.49.0-1 → 2.50.0-1
ros-humble-rqt-joint-trajectory-controller: 2.43.0-1 → 2.44.0-1
ros-humble-self-test: 4.0.2-1 → 4.0.3-1
ros-humble-self-test-dbgsym: 4.0.2-1 → 4.0.3-1
ros-humble-spinnaker-camera-driver: 3.0.0-1 → 3.0.1-1
ros-humble-spinnaker-camera-driver-dbgsym: 3.0.0-1 → 3.0.1-1
ros-humble-spinnaker-synchronized-camera-driver: 3.0.0-1 → 3.0.1-1
ros-humble-spinnaker-synchronized-camera-driver-dbgsym: 3.0.0-1 → 3.0.1-1
ros-humble-steering-controllers-library: 2.43.0-1 → 2.44.0-1
ros-humble-steering-controllers-library-dbgsym: 2.43.0-1 → 2.44.0-1
ros-humble-swri-cli-tools: 3.7.3-2 → 3.7.4-1
ros-humble-swri-console-util: 3.7.3-2 → 3.7.4-1
ros-humble-swri-console-util-dbgsym: 3.7.3-2 → 3.7.4-1
ros-humble-swri-dbw-interface: 3.7.3-2 → 3.7.4-1
ros-humble-swri-geometry-util: 3.7.3-2 → 3.7.4-1
ros-humble-swri-geometry-util-dbgsym: 3.7.3-2 → 3.7.4-1
ros-humble-swri-image-util: 3.7.3-2 → 3.7.4-1
ros-humble-swri-image-util-dbgsym: 3.7.3-2 → 3.7.4-1
ros-humble-swri-math-util: 3.7.3-2 → 3.7.4-1
ros-humble-swri-math-util-dbgsym: 3.7.3-2 → 3.7.4-1
ros-humble-swri-opencv-util: 3.7.3-2 → 3.7.4-1
ros-humble-swri-opencv-util-dbgsym: 3.7.3-2 → 3.7.4-1
ros-humble-swri-roscpp: 3.7.3-2 → 3.7.4-1
ros-humble-swri-roscpp-dbgsym: 3.7.3-2 → 3.7.4-1
ros-humble-swri-route-util: 3.7.3-2 → 3.7.4-1
ros-humble-swri-route-util-dbgsym: 3.7.3-2 → 3.7.4-1
ros-humble-swri-serial-util: 3.7.3-2 → 3.7.4-1
ros-humble-swri-serial-util-dbgsym: 3.7.3-2 → 3.7.4-1
ros-humble-swri-system-util: 3.7.3-2 → 3.7.4-1
ros-humble-swri-system-util-dbgsym: 3.7.3-2 → 3.7.4-1
ros-humble-swri-transform-util: 3.7.3-2 → 3.7.4-1
ros-humble-swri-transform-util-dbgsym: 3.7.3-2 → 3.7.4-1
ros-humble-tile-map: 2.4.5-1 → 2.4.6-1
ros-humble-tile-map-dbgsym: 2.4.5-1 → 2.4.6-1
ros-humble-transmission-interface: 2.49.0-1 → 2.50.0-1
ros-humble-transmission-interface-dbgsym: 2.49.0-1 → 2.50.0-1
ros-humble-tricycle-controller: 2.43.0-1 → 2.44.0-1
ros-humble-tricycle-controller-dbgsym: 2.43.0-1 → 2.44.0-1
ros-humble-tricycle-steering-controller: 2.43.0-1 → 2.44.0-1
ros-humble-tricycle-steering-controller-dbgsym: 2.43.0-1 → 2.44.0-1
ros-humble-turtlebot3: 2.2.5-1 → 2.2.9-1
ros-humble-turtlebot3-bringup: 2.2.5-1 → 2.2.9-1
ros-humble-turtlebot3-cartographer: 2.2.5-1 → 2.2.9-1
ros-humble-turtlebot3-description: 2.2.5-1 → 2.2.9-1
ros-humble-turtlebot3-example: 2.2.5-1 → 2.2.9-1
ros-humble-turtlebot3-fake-node: 2.2.5-3 → 2.3.0-1
ros-humble-turtlebot3-fake-node-dbgsym: 2.2.5-3 → 2.3.0-1
ros-humble-turtlebot3-gazebo: 2.2.5-3 → 2.3.0-1
ros-humble-turtlebot3-gazebo-dbgsym: 2.2.5-3 → 2.3.0-1
ros-humble-turtlebot3-manipulation-bringup: 2.1.1-1 → 2.2.0-1
ros-humble-turtlebot3-manipulation-cartographer: 2.1.1-1 → 2.2.0-1
ros-humble-turtlebot3-manipulation-description: 2.1.1-1 → 2.2.0-1
ros-humble-turtlebot3-manipulation-hardware: 2.1.1-1 → 2.2.0-1
ros-humble-turtlebot3-manipulation-hardware-dbgsym: 2.1.1-1 → 2.2.0-1
ros-humble-turtlebot3-manipulation-navigation2: 2.1.1-1 → 2.2.0-1
ros-humble-turtlebot3-navigation2: 2.2.5-1 → 2.2.9-1
ros-humble-turtlebot3-node: 2.2.5-1 → 2.2.9-1
ros-humble-turtlebot3-node-dbgsym: 2.2.5-1 → 2.2.9-1
ros-humble-turtlebot3-simulations: 2.2.5-3 → 2.3.0-1
ros-humble-turtlebot3-teleop: 2.2.5-1 → 2.2.9-1
ros-humble-ur: 2.6.0-1 → 2.7.0-1
ros-humble-ur-bringup: 2.6.0-1 → 2.7.0-1
ros-humble-ur-calibration: 2.6.0-1 → 2.7.0-1
ros-humble-ur-calibration-dbgsym: 2.6.0-1 → 2.7.0-1
ros-humble-ur-client-library: 1.8.0-1 → 1.9.0-1
ros-humble-ur-client-library-dbgsym: 1.8.0-1 → 1.9.0-1
ros-humble-ur-controllers: 2.6.0-1 → 2.7.0-1
ros-humble-ur-controllers-dbgsym: 2.6.0-1 → 2.7.0-1
ros-humble-ur-dashboard-msgs: 2.6.0-1 → 2.7.0-1
ros-humble-ur-dashboard-msgs-dbgsym: 2.6.0-1 → 2.7.0-1
ros-humble-ur-description: 2.1.11-1 → 2.5.0-1
ros-humble-ur-moveit-config: 2.6.0-1 → 2.7.0-1
ros-humble-ur-robot-driver: 2.6.0-1 → 2.7.0-1
ros-humble-ur-robot-driver-dbgsym: 2.6.0-1 → 2.7.0-1
ros-humble-ur-simulation-gz: 0.1.1-2 → 0.2.0-1
ros-humble-velocity-controllers: 2.43.0-1 → 2.44.0-1
ros-humble-velocity-controllers-dbgsym: 2.43.0-1 → 2.44.0-1
ros-humble-yasmin: 3.1.0-1 → 3.2.0-2
ros-humble-yasmin-demos: 3.1.0-1 → 3.2.0-2
ros-humble-yasmin-demos-dbgsym: 3.1.0-1 → 3.2.0-2
ros-humble-yasmin-msgs: 3.1.0-1 → 3.2.0-2
ros-humble-yasmin-msgs-dbgsym: 3.1.0-1 → 3.2.0-2
ros-humble-yasmin-ros: 3.1.0-1 → 3.2.0-2
ros-humble-yasmin-viewer: 3.1.0-1 → 3.2.0-2
ros-humble-zed-msgs: 4.2.5-1 → 5.0.0-1
ros-humble-zed-msgs-dbgsym: 4.2.5-1 → 5.0.0-1

Removed Packages [1]:

ros-humble-ign-ros2-control-dbgsym

Thanks to all ROS maintainers who make packages available to the ROS community. The above list of packages was made possible by the work of the following maintainers:

Alejandro Hernández
Alexander Gutenkunst
Apex.AI, Inc.
Austin Hendrix
Bence Magyar
Berkay Karaman
Bernd Pfrommer
Blake Anderson
Chittaranjan Srinivas Swaminathan
Christian Henkel
Christian Rauch
Daan Wijffels
David Brown
David V. Lu!!
Enrico Ferrentino
Ethan Gao
Felix Exner
Fictionlab
Henning Kayser
Jean-Pierre Busch
Jose-Luis Blanco-Claraco
Luis Camero
M. Fatih Cırıt
Mamoru Sobue
Michael Görner
Miguel Ángel González Santamarta
MoveIt Release Team
Pyo
Raghavender Sahdev
Rob Fisher
Robin Petereit
Ryohsuke Mitsudome
STEREOLABS
Sarah Huber
Southwest Research Institute
Takagi, Isamu
Temkei Kem
Timo Röhling
Yukihiro Saito
Yutaka Kondo
kminoda
miguel
mitsudome-r

1 post - 1 participant

Read full topic

https://discourse.ros.org/t/new-packages-for-humble-hawksbill-2025-04-25/43398

ROS Discourse General: New Packages for Noetic 2025-04-24

We’re happy to announce 25 new packages and 168 updates are now available in ROS Noetic. This sync was tagged as noetic/2025-04-24.

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

Package Updates for ROS Noetic

Added Packages [25]:

ros-noetic-abb: 1.5.0-1
ros-noetic-abb-crb15000-support: 1.5.0-1
ros-noetic-abb-irb120-support: 1.5.0-1
ros-noetic-abb-irb1200-support: 1.5.0-1
ros-noetic-abb-irb1600-support: 1.5.0-1
ros-noetic-abb-irb2400-support: 1.5.0-1
ros-noetic-abb-irb2600-support: 1.5.0-1
ros-noetic-abb-irb4400-support: 1.5.0-1
ros-noetic-abb-irb4600-support: 1.5.0-1
ros-noetic-abb-irb52-support: 1.5.0-1
ros-noetic-abb-irb5400-support: 1.5.0-1
ros-noetic-abb-irb6600-support: 1.5.0-1
ros-noetic-abb-irb6640-support: 1.5.0-1
ros-noetic-abb-irb6650s-support: 1.5.0-1
ros-noetic-abb-irb6700-support: 1.5.0-1
ros-noetic-abb-irb7600-support: 1.5.0-1
ros-noetic-abb-resources: 1.5.0-1
ros-noetic-depth-obstacle-detect-ros: 1.0.0-2
ros-noetic-depth-obstacle-detect-ros-msgs: 1.0.0-2
ros-noetic-etsi-its-mcm-uulm-coding: 3.2.0-1
ros-noetic-etsi-its-mcm-uulm-conversion: 3.2.0-1
ros-noetic-etsi-its-mcm-uulm-msgs: 3.2.0-1
ros-noetic-openrtm-aist-python: 1.1.0-8
ros-noetic-ur12e-moveit-config: 1.4.0-1
ros-noetic-ur7e-moveit-config: 1.4.0-1

Updated Packages [168]:

ros-noetic-actionlib: 1.14.0-1 → 1.14.1-1
ros-noetic-actionlib-tools: 1.14.0-1 → 1.14.1-1
ros-noetic-angles: 1.9.13-1 → 1.9.14-1
ros-noetic-camera-calibration-parsers: 1.12.0-1 → 1.12.1-1
ros-noetic-camera-info-manager: 1.12.0-1 → 1.12.1-1
ros-noetic-catkin: 0.8.10-1 → 0.8.11-1
ros-noetic-class-loader: 0.5.0-1 → 0.5.1-1
ros-noetic-cmake-modules: 0.5.0-1 → 0.5.1-1
ros-noetic-costmap-cspace: 0.17.6-1 → 0.17.7-1
ros-noetic-ddynamic-reconfigure: 0.3.2-1 → 0.4.2-1
ros-noetic-dynamic-reconfigure: 1.7.3-1 → 1.7.4-1
ros-noetic-eigen-conversions: 1.13.2-1 → 1.13.3-1
ros-noetic-etsi-its-cam-coding: 3.1.0-1 → 3.2.0-1
ros-noetic-etsi-its-cam-conversion: 3.1.0-1 → 3.2.0-1
ros-noetic-etsi-its-cam-msgs: 3.1.0-1 → 3.2.0-1
ros-noetic-etsi-its-cam-ts-coding: 3.1.0-1 → 3.2.0-1
ros-noetic-etsi-its-cam-ts-conversion: 3.1.0-1 → 3.2.0-1
ros-noetic-etsi-its-cam-ts-msgs: 3.1.0-1 → 3.2.0-1
ros-noetic-etsi-its-coding: 3.1.0-1 → 3.2.0-1
ros-noetic-etsi-its-conversion: 3.1.0-1 → 3.2.0-1
ros-noetic-etsi-its-cpm-ts-coding: 3.1.0-1 → 3.2.0-1
ros-noetic-etsi-its-cpm-ts-conversion: 3.1.0-1 → 3.2.0-1
ros-noetic-etsi-its-cpm-ts-msgs: 3.1.0-1 → 3.2.0-1
ros-noetic-etsi-its-denm-coding: 3.1.0-1 → 3.2.0-1
ros-noetic-etsi-its-denm-conversion: 3.1.0-1 → 3.2.0-1
ros-noetic-etsi-its-denm-msgs: 3.1.0-1 → 3.2.0-1
ros-noetic-etsi-its-denm-ts-coding: 3.1.0-1 → 3.2.0-1
ros-noetic-etsi-its-denm-ts-conversion: 3.1.0-1 → 3.2.0-1
ros-noetic-etsi-its-denm-ts-msgs: 3.1.0-1 → 3.2.0-1
ros-noetic-etsi-its-mapem-ts-coding: 3.1.0-1 → 3.2.0-1
ros-noetic-etsi-its-mapem-ts-conversion: 3.1.0-1 → 3.2.0-1
ros-noetic-etsi-its-mapem-ts-msgs: 3.1.0-1 → 3.2.0-1
ros-noetic-etsi-its-messages: 3.1.0-1 → 3.2.0-1
ros-noetic-etsi-its-msgs: 3.1.0-1 → 3.2.0-1
ros-noetic-etsi-its-msgs-utils: 3.1.0-1 → 3.2.0-1
ros-noetic-etsi-its-primitives-conversion: 3.1.0-1 → 3.2.0-1
ros-noetic-etsi-its-rviz-plugins: 3.1.0-1 → 3.2.0-1
ros-noetic-etsi-its-spatem-ts-coding: 3.1.0-1 → 3.2.0-1
ros-noetic-etsi-its-spatem-ts-conversion: 3.1.0-1 → 3.2.0-1
ros-noetic-etsi-its-spatem-ts-msgs: 3.1.0-1 → 3.2.0-1
ros-noetic-etsi-its-vam-ts-coding: 3.1.0-1 → 3.2.0-1
ros-noetic-etsi-its-vam-ts-conversion: 3.1.0-1 → 3.2.0-1
ros-noetic-etsi-its-vam-ts-msgs: 3.1.0-1 → 3.2.0-1
ros-noetic-filters: 1.9.2-1 → 1.9.3-1
ros-noetic-gencpp: 0.7.0-1 → 0.7.1-1
ros-noetic-genmsg: 0.6.0-1 → 0.6.1-1
ros-noetic-genpy: 0.6.15-1 → 0.6.17-1
ros-noetic-geometry: 1.13.2-1 → 1.13.3-1
ros-noetic-geometry-tutorials: 0.2.3-1 → 0.2.4-1
ros-noetic-geometry2: 0.7.7-1 → 0.7.8-1
ros-noetic-gl-dependency: 1.1.2-1 → 1.1.3-1
ros-noetic-image-common: 1.12.0-1 → 1.12.1-1
ros-noetic-image-transport: 1.12.0-1 → 1.12.1-1
ros-noetic-interactive-marker-tutorials: 0.11.0-1 → 0.11.1-1
ros-noetic-interactive-markers: 1.12.0-1 → 1.12.1-1
ros-noetic-joint-state-publisher: 1.15.1-1 → 1.15.2-1
ros-noetic-joint-state-publisher-gui: 1.15.1-1 → 1.15.2-1
ros-noetic-joystick-interrupt: 0.17.6-1 → 0.17.7-1
ros-noetic-kdl-conversions: 1.13.2-1 → 1.13.3-1
ros-noetic-laser-geometry: 1.6.7-1 → 1.6.8-1
ros-noetic-librviz-tutorial: 0.11.0-1 → 0.11.1-1
ros-noetic-map-organizer: 0.17.6-1 → 0.17.7-1
ros-noetic-microstrain-inertial-description: 4.5.0-1 → 4.6.0-1
ros-noetic-microstrain-inertial-driver: 4.5.0-1 → 4.6.0-1
ros-noetic-microstrain-inertial-examples: 4.5.0-1 → 4.6.0-1
ros-noetic-microstrain-inertial-msgs: 4.5.0-1 → 4.6.0-1
ros-noetic-microstrain-inertial-rqt: 4.5.0-1 → 4.6.0-1
ros-noetic-mk: 1.15.8-1 → 1.15.9-1
ros-noetic-neonavigation: 0.17.6-1 → 0.17.7-1
ros-noetic-neonavigation-common: 0.17.6-1 → 0.17.7-1
ros-noetic-neonavigation-launch: 0.17.6-1 → 0.17.7-1
ros-noetic-ntrip-client: 1.4.0-1 → 1.4.1-1
ros-noetic-obj-to-pointcloud: 0.17.6-1 → 0.17.7-1
ros-noetic-planner-cspace: 0.17.6-1 → 0.17.7-1
ros-noetic-pluginlib: 1.13.0-1 → 1.13.1-1
ros-noetic-polled-camera: 1.12.0-1 → 1.12.1-1
ros-noetic-python-qt-binding: 0.4.4-1 → 0.4.5-1
ros-noetic-qt-dotgraph: 0.4.2-1 → 0.4.3-1
ros-noetic-qt-gui: 0.4.2-1 → 0.4.3-1
ros-noetic-qt-gui-app: 0.4.2-1 → 0.4.3-1
ros-noetic-qt-gui-core: 0.4.2-1 → 0.4.3-1
ros-noetic-qt-gui-cpp: 0.4.2-1 → 0.4.3-1
ros-noetic-qt-gui-py-common: 0.4.2-1 → 0.4.3-1
ros-noetic-resource-retriever: 1.12.8-1 → 1.12.9-1
ros-noetic-robot-state-publisher: 1.15.2-1 → 1.15.3-1
ros-noetic-ros: 1.15.8-1 → 1.15.9-1
ros-noetic-ros-tutorials: 0.10.2-1 → 0.10.3-1
ros-noetic-rosbag-migration-rule: 1.0.1-1 → 1.0.2-1
ros-noetic-rosbash: 1.15.8-1 → 1.15.9-1
ros-noetic-rosboost-cfg: 1.15.8-1 → 1.15.9-1
ros-noetic-rosbuild: 1.15.8-1 → 1.15.9-1
ros-noetic-rosclean: 1.15.8-1 → 1.15.9-1
ros-noetic-rosconsole: 1.14.3-1 → 1.14.4-1
ros-noetic-rosconsole-bridge: 0.5.4-1 → 0.5.5-1
ros-noetic-roscpp-tutorials: 0.10.2-1 → 0.10.3-1
ros-noetic-roscreate: 1.15.8-1 → 1.15.9-1
ros-noetic-rosgraph-msgs: 1.11.3-1 → 1.11.4-1
ros-noetic-roslang: 1.15.8-1 → 1.15.9-1
ros-noetic-roslib: 1.15.8-1 → 1.15.9-1
ros-noetic-rosmake: 1.15.8-1 → 1.15.9-1
ros-noetic-rospack: 2.6.2-1 → 2.6.3-1
ros-noetic-rospy-tutorials: 0.10.2-1 → 0.10.3-1
ros-noetic-rosunit: 1.15.8-1 → 1.15.9-1
ros-noetic-rqt: 0.5.3-1 → 0.5.4-1
ros-noetic-rqt-action: 0.4.9-1 → 0.4.10-1
ros-noetic-rqt-bag: 0.5.1-1 → 0.5.2-1
ros-noetic-rqt-bag-plugins: 0.5.1-1 → 0.5.2-1
ros-noetic-rqt-common-plugins: 0.4.9-1 → 0.4.10-1
ros-noetic-rqt-console: 0.4.12-1 → 0.4.13-1
ros-noetic-rqt-dep: 0.4.12-1 → 0.4.13-1
ros-noetic-rqt-graph: 0.4.14-1 → 0.4.15-1
ros-noetic-rqt-gui: 0.5.3-1 → 0.5.4-1
ros-noetic-rqt-gui-cpp: 0.5.3-1 → 0.5.4-1
ros-noetic-rqt-gui-py: 0.5.3-1 → 0.5.4-1
ros-noetic-rqt-image-view: 0.4.17-1 → 0.4.18-1
ros-noetic-rqt-msg: 0.4.10-1 → 0.4.11-1
ros-noetic-rqt-plot: 0.4.13-2 → 0.4.15-1
ros-noetic-rqt-pose-view: 0.5.11-1 → 0.5.12-1
ros-noetic-rqt-pr2-dashboard: 0.4.1-1 → 0.4.2-1
ros-noetic-rqt-publisher: 0.4.10-1 → 0.4.11-1
ros-noetic-rqt-py-common: 0.5.3-1 → 0.5.4-1
ros-noetic-rqt-py-console: 0.4.10-1 → 0.4.11-1
ros-noetic-rqt-reconfigure: 0.5.5-1 → 0.5.6-1
ros-noetic-rqt-robot-steering: 0.5.12-1 → 0.5.13-1
ros-noetic-rqt-rviz: 0.7.0-1 → 0.7.1-1
ros-noetic-rqt-service-caller: 0.4.10-1 → 0.4.11-1
ros-noetic-rqt-srv: 0.4.9-1 → 0.4.10-1
ros-noetic-rqt-top: 0.4.10-1 → 0.4.11-1
ros-noetic-rqt-topic: 0.4.13-1 → 0.4.14-1
ros-noetic-rqt-web: 0.4.10-1 → 0.4.11-1
ros-noetic-rviz-plugin-tutorials: 0.11.0-1 → 0.11.1-1
ros-noetic-rviz-python-tutorial: 0.11.0-1 → 0.11.1-1
ros-noetic-safety-limiter: 0.17.6-1 → 0.17.7-1
ros-noetic-std-msgs: 0.5.13-1 → 0.5.14-1
ros-noetic-std-srvs: 1.11.3-1 → 1.11.4-1
ros-noetic-tf: 1.13.2-1 → 1.13.3-1
ros-noetic-tf-conversions: 1.13.2-1 → 1.13.3-1
ros-noetic-tf2: 0.7.7-1 → 0.7.8-1
ros-noetic-tf2-bullet: 0.7.7-1 → 0.7.8-1
ros-noetic-tf2-eigen: 0.7.7-1 → 0.7.8-1
ros-noetic-tf2-geometry-msgs: 0.7.7-1 → 0.7.8-1
ros-noetic-tf2-kdl: 0.7.7-1 → 0.7.8-1
ros-noetic-tf2-msgs: 0.7.7-1 → 0.7.8-1
ros-noetic-tf2-py: 0.7.7-1 → 0.7.8-1
ros-noetic-tf2-ros: 0.7.7-1 → 0.7.8-1
ros-noetic-tf2-sensor-msgs: 0.7.7-1 → 0.7.8-1
ros-noetic-tf2-tools: 0.7.7-1 → 0.7.8-1
ros-noetic-track-odometry: 0.17.6-1 → 0.17.7-1
ros-noetic-trajectory-tracker: 0.17.6-1 → 0.17.7-1
ros-noetic-turtle-tf: 0.2.3-1 → 0.2.4-1
ros-noetic-turtle-tf2: 0.2.3-1 → 0.2.4-1
ros-noetic-turtlesim: 0.10.2-1 → 0.10.3-1
ros-noetic-universal-robots: 1.3.3-1 → 1.4.0-1
ros-noetic-ur-description: 1.3.3-1 → 1.4.0-1
ros-noetic-ur-gazebo: 1.3.3-1 → 1.4.0-1
ros-noetic-ur10-moveit-config: 1.3.3-1 → 1.4.0-1
ros-noetic-ur10e-moveit-config: 1.3.3-1 → 1.4.0-1
ros-noetic-ur16e-moveit-config: 1.3.3-1 → 1.4.0-1
ros-noetic-ur20-moveit-config: 1.3.3-1 → 1.4.0-1
ros-noetic-ur3-moveit-config: 1.3.3-1 → 1.4.0-1
ros-noetic-ur30-moveit-config: 1.3.3-1 → 1.4.0-1
ros-noetic-ur3e-moveit-config: 1.3.3-1 → 1.4.0-1
ros-noetic-ur5-moveit-config: 1.3.3-1 → 1.4.0-1
ros-noetic-ur5e-moveit-config: 1.3.3-1 → 1.4.0-1
ros-noetic-urdf: 1.13.2-1 → 1.13.3-1
ros-noetic-urdf-parser-plugin: 1.13.2-1 → 1.13.3-1
ros-noetic-visualization-marker-tutorials: 0.11.0-1 → 0.11.1-1
ros-noetic-visualization-tutorials: 0.11.0-1 → 0.11.1-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:

Analog Devices
Atsushi Watanabe
Chris Lalancette
Claire Wang
Dave Hershberger
Denis Štogl
Dharini Dutia
Dirk Thomas
Dorian Scholz
G.A. vd. Hoorn
G.A. vd. Hoorn (TU Delft Robotics Institute)
Geoffrey Biggs
Hilario Tome
Ivan Paunovic
Jack O’Quin
Jacob Perron
Jean-Pierre Busch
Kei Okada
Koji Terada
Mabel Zhang
Michael Carroll
Michael Jeronimo
Michel Hidalgo
Mikael Arguedas
ROS-Industrial community
Rob Fisher
Robert Haschke
Sammy Pfeiffer
Scott Logan
Steven! Ragnarök
Tully Foote
Vincent Rabaud
Vincenzo Di Pentima
William Woodall

3 posts - 2 participants

Read full topic

https://discourse.ros.org/t/new-packages-for-noetic-2025-04-24/43390

ROS Discourse General: Kilted Test and Tutorial Party and Release Events :tada:

Kilted Test and Tutorial Party and Release Events

What is a Test and Tutorial Party?

We want Kilted Kaiju to be our best ROS 2 release yet, and to get there we need to make sure that we thoroughly test Kilted before it is released to the general public. We also want to make sure that the ROS documentation on docs.ros.org continues to be clear, concise, and correct. That’s where we need your help! We’re looking for community volunteers to join us for our annual ROS Testing and Tutorial Party. If you are looking to start dipping your toes into ROS development this is a great place to start.

So, what is a testing and tutorial party you may ask? Well, it is a chance for the community to meet and systematically review all of the current ROS tutorials while also testing the latest ROS release. What we attempt to do at the party is to test every ROS tutorial for every “flavor” of ROS user, or in other words, every combination of operating system (Ubuntu Linux, RedHat Linux, Windows, etc.), RMW implementation (FastDDS, Cyclone DDS, etc.), installation method, and CPU architecture (amd64, aarch64, etc.).

Now that we’ve frozen the Kilted release, the core developer team is working on generating a set of “early release” binary and source packages for Kilted Kaiju. We plan to make these pre-release binaries publicly available before the Testing and Tutorial Party. During the party we’ll release our testing repository with a long list of tests we would like to run on the testing version of Kilted Kaiju. These tests will first ask contributors to pick a particular release “setup”, and then run either the test suite or work through one or more of the existing ROS 2 tutorials on docs.ros.org. Each “setup” is a specific combination of RMW vendor (FastDDS/Cyclone DDS/Zenoh), build type (binary tarball/packages/source), host operating system (Ubuntu Noble/RHEL-9/Windows 10), and architecture (amd64/aarch64). For each setup, we would like to perform a number of tests that validate our tutorials, core ROS functionality, and important features. With dozens possible setup configurations, testing each and every one internally just isn’t feasible. To ensure reproducibility of the tests it’s also valuable to get multiple evaluations of each test, which is why we need your help!

Tutorial party participants are asked to perform the tests they sign up for and report back the results. If you happen to find an issue or bug while participating in the tutorial party you’ll need to report it to us so it can get corrected before the Kilted release.

Tutorial Party Information

We are planning to kick-off the Kilted tutorial party off at 2025-05-01T16:00:00Z UTC with a meeting where we explain the whole Testing and Tutorial Party Process. That meeting can be found on the OSRF Official Events Calendar. We’ll record the meeting and post instructions on Discourse for those who can’t make the meeting. To help motivate participants, we will be giving away either OSRA membership or ROS Kilted Kaiju swag to the testers who complete the most tests during the tutorial party. Once you have completed your first test or tutorial, and close the Github issue, you will need to fill out a short Google form so we know how to contact you. We’ll post more details about the tutorial party in about two weeks when we kick things off. For now, we’re outlining a rough sequence of events so everyone can set aside some time to participate.

This year we’re organizing two events to coincide with the Kilted Kaiju release that are worth mentioning. First we’ve scheduled our regular ROS By-The-Bay meetup to coincide with the T&T Party Kickoff. If you are in the Bay Area and want to learn more about the T&T party in person please register for ROS By-The-Bay. Second, and this is still tentative, we’re organizing a ROS Meetup / Kilted Release Party at ICRA. More information about that event should be available in the next two weeks!

Here are the key dates you’ll want to remember:

April 21st, 2025 Kilted Branch
April 30th, 2025 6:00 PM ROS By-The-Bay (T&T party for locals)
May 1, 2025 ROS 2 Kilted logo and swag sale begins (tentative)
May 1st, 2025 Tutorial & Testing Party begins
2025-05-01T16:00:00Z UTC Tutorial & Testing Party Hangout + Q&A
- Hangout Link
- Calendar Invite / Open Robotics Events Calendar
Thursday May 15th, 2025 Tutorial and Testing Party ends
Wednesday, May 21st, 2025 ROS Meetup / Kilted Release Party at ICRA (tentative)
Friday, May 23rd, 2025 ROS 2 Kilted Kaiju released

We have added these events to the OSRF Official Events Calendar, but the big one that you won’t want to miss is the kick-off event on 2025-05-01T16:00:00Z UTC . In the meantime we would like your help spreading the word about the Testing and Tutorial Party. We hope to see you there on May 1st!

Finally, if you would like to help support Open Robotics, and events like these, consider making a donation or joining the OSRA.

6 posts - 3 participants

Read full topic

https://discourse.ros.org/t/kilted-test-and-tutorial-party-and-release-events/43386

ROS Discourse General: Mark Your Calendars: Autonomous Grand Challenge 2025 @ ICCV & IROS

The CVPR2025 submission deadline is approaching fast — don’t forget to upload your results by May 10th! Right after CVPR, the ICCV2025 season begins.
Coming in early May: The AgiBot World Challenge! In this challenge, we are going beyond the lab and into the real world — deploying them on real robots, live at IROS2025.
Learn more at http://opendrivelab.com/challenge2025

1 post - 1 participant

Read full topic

https://discourse.ros.org/t/mark-your-calendars-autonomous-grand-challenge-2025-iccv-iros/43380

ROS Discourse General: Interoperability Special Interest Group skipping May 2025

Since the regularly scheduled date of May 1st happens to be a holiday in Singapore, we’ll be skipping the next session.

Please join us when we return on 2025-06-05T15:00:00Z UTC to talk about how to define executable workflow diagrams using JSON. We’ll cover various workflow mechanisms like forks, buffers, joins, listeners, and streams, and demonstrate how to incorporate these mechanisms into a workflow diagram.

We’ll also talk about reusable workflow “sections” which allow you to encapsulate portions of a workflow into a reusable unit, selectively exposing specific input slots, output signals, and buffers of your section that can be connect with other elements in your workflow. “Sections” allow you to apply good software engineering practices to your workflow design by defining an API (the set of inputs, outputs, and buffers that your section exposes) and plugging the section into any workflow where it may be useful. Complex workflows can be simplified by breaking them down into sections, and the responsibility of designing each section can be delegated across multiple team members or even across different teams. Sections can also be used inside of other sections, allowing multiple layers of abstraction.

1 post - 1 participant

Read full topic

https://discourse.ros.org/t/interoperability-special-interest-group-skipping-may-2025/43374

ROS Discourse General: New tool for working with Behavior Trees

Hello everyone!

I’ve just published TreeSense, a new VS Code extension that brings basic IntelliSense to BehaviorTree.CPP XML files. With TreeSense you can:

Ctrl+Click on any <SubTree> ID to jump straight to its definition
Hover over a tree reference to see a clean, indented outline of its structure

It’s still early days and possibly doesn’t cover every edge case, but I hope you find it useful. I’d love to hear any feedback or feature suggestions as you try it out!

5 posts - 3 participants

Read full topic

https://discourse.ros.org/t/new-tool-for-working-with-behavior-trees/43369

ROS Discourse General: Looking for Visual Odometry Resources in Simulation (ROS 2 + Gazebo)

Hi,

I’m working on a project that involves visual odometry, and I’m specifically looking to implement and test everything in simulation using ROS 2 (Preferably Humble or Jazzy) and Gazebo—no physical hardware or cameras involved.

I’d really appreciate it if anyone could share:

Tutorials or guides for setting up visual odometry pipelines in ROS 2 with Gazebo
Recommended simulation setups (e.g., camera plugins, world files, robot models)
Open-source packages or repos that work well in simulation
Any datasets or tools that help evaluate VO performance in a simulated environment

Kind regards,

Johanes

4 posts - 4 participants

Read full topic

https://discourse.ros.org/t/looking-for-visual-odometry-resources-in-simulation-ros-2-gazebo/43338

ROS Discourse General: ROS News for the Week of April 14th, 2025

ROS News for the Week of April 14th, 2025

The ROS 2 Kilted Kaiju feature freeze was Monday! We should have information about the release process early next week!

I’ve scheduled a ROS By-The-Bay meetup for 2025-05-01T01:00:00Z UTC coincide with the Kilted Kaiju Test and Tutorial Party.

6Dpose
Check out this teaser for, “Any6D: Model-free 6D Pose Estimation of Novel Objects” by KAIST and NVIDIA that will be presented at CVPR 2025! The demo seems to show ROS integration. Source code isn’t out yet but you can read the paper here. Heads up, we’re planning a ROS meetup at CVPR this year, more details will be out in a couple of weeks.

The fine folks at ETH Zurich have released ORCA Hand, an open source software and hardware hand you can build at home for under $2000.

The fine folks at HuggingFace

, the maintainers of LeRobot, have acquired
the equally awesome folks at Pollen Robotics. No word yet on what the merger means for the team, but we expect it to be awesome!

1744801225808
I came across a wonderful gif this week about the upcoming ROS 1 end-of-life on May 31st.

Events

News

ROS

Got a Minute?

We’re looking for three new contributors to help us with two new features and one issue with the Open-RMF Site Editor. Open-RMF is our brand new open source multi-robot fleet manager written in Rust:crab: and is the bleeding edge of what we are working on!

Open-RMF Site Editor #217: We’re need someone to create a way to save the user’s view point in the Open-RMF Site Editor that can we loaded when the user starts the application.

Open-RMF Site Editor #216: There is a bug such that deleting a fiducial that belongs to a group will permanently block any other fiducial in its drawing from being able to join that group.

Open-RMF Site Editor #225: We need a simple dialog that warns users before discarding unsaved changes. This is a great first issue for those just getting started with Rust.

35 posts - 17 participants

Read full topic

https://discourse.ros.org/t/ros-news-for-the-week-of-april-14th-2025/43289

ROS 2 Documentation

Wiki

Page

User

Planet ROS

Planet ROS - http://planet.ros.org

ROS Discourse General: Issues Simulating Parallel Manipulator in Gazebo Harmonic: Joint Parent Conflict

Problem Summary

model.sdf

platform_test.sdf

Error Message

Question

ROS Discourse General: Energy efficiency in ROS communication: a comparison across programming languages and workloads

ROS Discourse General: How should sensor descriptions be standardized?

ROS Discourse General: Organizing a ROS Meetup in Boston

Update!

Notice

ROS Discourse General: Actuate 2025 - Call for Presentations

ROS Discourse General: ROS News for the Week of April 28th, 2025

ROS News for the Week of April 28th, 2025

Events

News

ROS

Got a Minute?

ROS Discourse General: Kilted Kaiju Swag Sale :t_shirt:

Kilted Kaiju Swag Sale!

ROS Discourse General: Kilted Kaiju Test and Tutorial Party Instructions

Kilted Kaiju Test and Tutorial Party Instructions

TL;DR

Full Instructions

Docker Containers

ROS Discourse General: ROS 2 Kilted Beta and Call for Testing

Testing the Kilted beta

Releasing your packages

ROS Discourse General: Java based ROS2 controller for Dorna2 robotic arm

Integrating robots with ROS2

Using ros2_control (standard way)

Using jros2control

Supported ROS2 versions

Introduction to r2d2 package for Dorna2 arms

r2d2_control

Demonstration

Demonstration videos

Servoing the Dorna robotic arm with teleops

Planning and executing trajectories with MoveIt MotionPlanning plugin

ROS Industrial: ROS-Industrial Roadmap Journey and a Path Forward

Progress through collaboration

Future Direction

Global Collaboration and Synergy

Community Engagement

A living vision and roadmap

ROS Discourse General: Next Client Library WG Meeting: Friday 2nd May 2025 8AM PT

ROS Discourse General: New packages and patch release 5 for Jazzy Jalisco 2025-04-30

Package Updates for jazzy

Added Packages [46]:

Updated Packages [567]:

Removed Packages [3]:

ROS Discourse General: ROS Deliberation Community Group Meeting - May 5, 2025

ROS Discourse General: Smart Turtle Powered by Behavior Trees, ROS2 & Groot! 🐢

Project Overview

Key Features:

Why Behavior Trees?

ROS Discourse General: OSRA TGC meeting minutes for March, 2025

TECHNICAL GOVERNANCE COMMITTEE

MEETING MINUTES

27 MAR 2025 / 22:00-23:30 UTC / VIRTUAL VIA ZOOM

ATTENDEES

Existing Business

Adjournment - Geoff Biggs adjourned the meeting at 22:56 UTC.

ACTION ITEMS

ROS Discourse General: ROS News for the Week of April 21st, 2025

ROS News for the Week of April 21st, 2025

Events

News

ROS

Got a Minute?

ROS Discourse General: New packages for Humble Hawksbill 2025-04-25

Package Updates for humble

Added Packages [37]:

Updated Packages [395]: