[Documentation] [TitleIndex] [WordIndex] 

Planet ROS

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

Planet ROS - http://planet.ros.org[WWW] http://planet.ros.org

ROS Discourse General: ROS News for the week of May 5th, 2025

ROS News for the week of May 5th, 2025

AutomateMeetup2025

Our ROS Meetup in Detroit at Automate is next Tuesday. Looking forward to seeing everyone there!


OpenCV-SID-1x1-Poster@1x

Our friends over at OpenCV have organized their first conference which is happening on Monday! If you are in San Jose tickets are still available.


EdinburgMay25ROSMeetup

Copy of SGMay25ROSMeetup

GCMMay25 (1)

Publicacion exponer

We have a ton of other events coming up this month! Please take a look at the event list below.


sync_blender_reachy
The team over at Le Robot / Pollen Robotics have released this fantastic Blender plugin that let’s you automatically build robot poses and movements using Blender and ROS. I’ve been saying for awhile that something like this would be really useful for robot developers, particularly people who lean more towards animitronics!


osh_humanoid
A team over at Berkeley has released a low-cost, 3D printable, open source hardware and software humanoid robot. You can build your own for less than US$5000!


robot-arm-circle-a4db3d5f76ae7bef20461feaa379cb9e
Check out this fantastic tutorial on controlling a 6DOF robot arm with ros2_control.

Events

News

ROS

Got a minute?

KiltedTestFinal
The Kilted Kaiju Test and Tutortial party is ongoing! We really need Windows testers to step up so we can wrap up testing!

1 post - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/ros-news-for-the-week-of-may-5th-2025/43669

ROS Discourse General: New Packages for Noetic 2025-05-08

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

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

:double_exclamation_mark:Next week is the last sync that ROS Noetic will accept new packages and/or new features‼️ Releases with new packages and/or features must be bloom-release’d AND merged into ros/rosdistro BEFORE May 13th:double_exclamation_mark:

Package Updates for ROS Noetic

Added Packages [0]:

Updated Packages [175]:

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:

1 post - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/new-packages-for-noetic-2025-05-08/43657

ROS Discourse General: ROS2 Hosting / Open Source Lab

I’ve noticed that the main ROS2 apt repository appears to be hosted by Oregon State University’s Open Source Lab, which appears to be facing a funding issue, and may shut down later this year if it does not receive it.

I’ve seen some threads online regarding other projects hosted by the OSL, but haven’t seen anything from the ROS community. Hopefully it won’t come to it, but are there plans to migrate hosting if the funding is not received?

3 posts - 3 participants

Read full topic

[WWW] https://discourse.ros.org/t/ros2-hosting-open-source-lab/43638

ROS Discourse General: ROS Meetup Nigeria

Screenshot from 2025-05-08 09-13-13

Hello ROS Developers,

We are excited to announce another ROS Meetup Lagos in Nigeria happening this May :robot:
This is going to be an exciting and educational as it would be about Aerial Robotics and AI :fire:
It will also be fully Virtual.

Speakers: Tosin Oseni and Tejal Barnwal

Tejal Barnwal, a Robotics Engineer at Newspace Research and Technologies with skills in perception systems, including vision-based drone navigation and sensor fusion, alongside open-source contributions, will be Demystifying ROS2 for Aerial Robotics
while
Tosin Oseni, a Robotics and AI Researcher with skills in Reinforcement Learning and Visual Systems will take us through some cool AI applications in Robotics.

Kindly register for the ROS Meetup Lagos

Venue: Virtual only
Date: 2025-05-24T11:00:00Z UTC→2025-05-24T13:00:00Z UTC
Contact Email Address: rosnaija.ng@gmail.com

1 post - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/ros-meetup-nigeria/43635

ROS Discourse General: Space Station OS v0.8.2 released - ROS 2 update with space station control systems and simulation

SSOS v0.8.2 Released - Now with Configurable CMG Control Dynamics

We’re pleased to announce the release of SSOS v0.8.2, now including configurable CMG (Control Moment Gyroscope) control - a key component in attitude control systems for large spacecraft like space stations.

This update finalizes a series of improvements around dynamic modeling, modular control, and simulation-driven development. It brings us closer to our goal of building a complete, ROS2-native platform for space station system development.

A quick overview of what’s included and what’s coming next is shown below.

What’s included in v0.8.2

This release focuses on building blocks that are familiar to robotics developers, but applied to the space domain:

See full release notes here:

What’s next in v0.8.3

About SSOS

Space Station OS (SSOS) is an open-source ROS2 platform designed to unify the development and simulation of space station subsystems - guidance and control (GNC), power (EPS), thermal, communications, and life support (ECLSS).

It is built around modular software architecture and simulation-first development principles. Our goal is to accelerate prototyping, testing, and integration of complex spacecraft systems, with a clear path from simulation to hardware.

Even if you’re not working on space systems, the challenges overlap heavily with mobile robotics, autonomous platforms, and modular simulation - so your skills are highly relevant.

How to get involved

We welcome collaboration and discussion, especially in the following areas:

GitHub: GitHub - space-station-os/space_station_os: Space Station OS. A future where anyone can develop space stations.
Feel free to reach out via Issues or Discussions.

Official site:

1 post - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/space-station-os-v0-8-2-released-ros-2-update-with-space-station-control-systems-and-simulation/43618

ROS Discourse General: Looking for Noetic Tshirt

It’s 2025, might be late, but I wanted to buy a Noetic Tshirt. :slight_smile:

Any idea or hint on it? Where can I find it?

2 posts - 2 participants

Read full topic

[WWW] https://discourse.ros.org/t/looking-for-noetic-tshirt/43596

ROS Discourse General: ROS 2 L Name Brainstorming

We are now less than three weeks from the release of ROS 2 Kilted Kaiju. As we traditionally announce the name of the following distribution when a new distribution is released, it’s time to start thinking about the next release after Kilted Kaiju.

Following tradition, the next ROS 2 release name will be an adjective starting with L followed by a turtle-related word or name, also starting with L.

Important to note that L-turtle will be an LTS release spanning 5 years.

Here are the existing ROS 2 names and code names.

And here are the ROS 1 names and code names.

To get your namestorming going, here are some useful lists.

For reference, here is the namestorming thread for ROS 1 Lunar Loggerhead from back in 2016. (See if there are any names you recognize).

Please share your suggestions and comments. There are no rules to this part of the process so be creative!

74 posts - 54 participants

Read full topic

[WWW] https://discourse.ros.org/t/ros-2-l-name-brainstorming/43582

ROS Discourse General: Announcing "Maps": Show robots live on a map on the web

Show your robots live on a map (OccupancyGrid), incl.:

You can also relocalize your robots right from your browser or watch your map evolve from afar while a robot is mapping! As always, you can embed this capability’s UI components in your own web dashboards or fork our open-source transAct dashboard – and yes, it works with both ROS 1 and 2.

Knowing where your robots are at all times is crucial for operations. In fact, many companies build their entire fleet management system around the concept of locations and maps as these elegantly tie together the entire fleet. So we are excited to finally provide this badly needed capability.

Please let me know if you try it and have feedback or suggestions. We are already planning a lot more features, but would love to hear your needs. :folded_hands:

Details

Demo:

Transitive Maps Capability Demo

2 posts - 2 participants

Read full topic

[WWW] https://discourse.ros.org/t/announcing-maps-show-robots-live-on-a-map-on-the-web/43575

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”

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

[WWW] 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.

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

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

[WWW] 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?

35 posts - 15 participants

Read full topic

[WWW] 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

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

[WWW] 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
:kilted: 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.


KiltedSwag

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


1746183415805
879cf6ac7e9324bf2ce9d2d0c62524ac32a0cf6a_2_500x500

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.


AutomateMeetup2025

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.


image

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? :alarm_clock:

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

[WWW] 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!

KiltedSwag

Hi Folks,

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

All of our swag is available at :backhand_index_pointing_right: spring.ros.org. :backhand_index_pointing_left:

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

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

All proceeds go to support the Open Source Robotics Foundation! :heart:

6 posts - 3 participants

Read full topic

[WWW] 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

KiltedKaiju_WithBackground

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:

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:

  1. Please fill out the Google form for your first issue so we have your contact information.

  2. First go to the Tutorial Party Github repo and read the README.md.

  3. Figure out your setup!

  4. Note your computer’s host operating system (either Ubuntu Nobel, Windows, or RHEL-9)

  5. Note your chipset, either AMD64 or ARM64, if you don’t know it is probably AMD64.

  6. Note your installed DDS Vendor (this varies by host OS).

  7. Figure out how you want to install the ROS Kilted Kaiju Beta, your options are:

  8. 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.

  9. 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

  10. 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.

  11. 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.

  12. 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.”

  13. 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.

4 posts - 1 participant

Read full topic

[WWW] 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

[WWW] 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:

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

Supported RMW:

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_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:

  1. teleops - CLI application which sends commands to MoveIt2 Servo
  2. 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:

r2d2 flow diagram

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

[WWW] 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:

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:

modules and the scan-n-plan framework

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

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:

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.

draft ros-i roadmap 2025

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.

[WWW] 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.

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

[WWW] 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 .

:jazzy: :jazzy: :jazzy:

Package Updates for jazzy

Added Packages [46]:

Updated Packages [567]:

Removed Packages [3]:

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:

Enjoy! :jazzy:m

1 post - 1 participant

Read full topic

[WWW] 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:

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

- Sebastian

2 posts - 2 participants

Read full topic

[WWW] 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!

:light_bulb: Project Overview

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

:hammer_and_wrench: Key Features:

:seedling: 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

Screenshot from 2025-04-29 19-28-15

Screenshot from 2025-04-29 20-50-32

simplescreenrecorder-2025-04-29_15.06.52

4 posts - 2 participants

Read full topic

[WWW] 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:

OSRA Delegates/TGC Reps:

OSRA Observers

AGENDA

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

Existing Business

  1. Confirmation of minutes of meeting TGC-20250227-Regular

    • Approved by consensus

  2. 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

  3. 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

Other Items

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

ACTION ITEMS

  1. The meeting minutes will be circulated to the TGC for review and approval before the next meeting by the TGC Chair.
  2. 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

[WWW] 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


KiltedTAndT

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!


ROSBTBMay25 (1)

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


image

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

:clock: 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

[WWW] 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]:

Updated Packages [395]:

Removed Packages [1]:

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:

1 post - 1 participant

Read full topic

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

2025-05-10 13:11