Planet ROS

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

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

ROS Discourse General: Recursive Fiducial Marker

I would like to share an ongoing development of a fiducial marker with recursive feature. The marker would be useful to multi-range applications.

1 post - 1 participant

Read full topic

https://discourse.openrobotics.org/t/recursive-fiducial-marker/50847

ROS Discourse General: ROSGraph Working Group kickoff

Hey all! From the announcement in my ROSCon talk “Escape Velocity: How to be good at launch” - here is the launch of the new working group!

If you’re just in it for the slides & launch snippets, you can find them at GitHub - emersonknapp/roscon2025_launch_snippets: Slides and code snippets for ROSCon 2025 presentation "Escape Velocity: Smarter, Cleaner ROS 2 Launch Patterns, a.k.a How to write good launchfiles"

Otherwise if you’re still with me… Come start the conversation about launch, declarative node interfaces, health monitoring, and more - the tooling that will help us reason holistically about ROS applications and their structure.

Initial meeting is next Tuesday, November 11.

If you join the mailing list https://groups.google.com/u/1/g/rosgraph-wg you will receive the calendar invite.

Key links:

I’m working on the official processes to put up a charter and get onto shared calendars, but for now we can, as Kat said, “just do things” - let’s get started!

I’ll note that this is the continuation/evolution of “Robograph Project” that I discussed earlier this year Declarative ROS presentation slides & the Robograph project kickoff - just a slightly new framing to continue on the same work.

1 post - 1 participant

Read full topic

https://discourse.openrobotics.org/t/rosgraph-working-group-kickoff/50846

ROS Discourse General: ROS Asia Pacific Developer Meeting #1 7th.Nov

ROS Users and Developers in Asia Pacific region

As I announced at ROSCon 2025 Singapore Lightening Talk, we will have 1st ROS Asia Pacific Developer Meeting on this Friday 7th.Nov Convert Your Time.

ROS_APAC_Developer_Meeting-LT.pdf (3.6 MB)

If you are willing to start the contribution to ROS open source projects, please come and join us

ROS APAC Developer Meeting #1
Friday, November 7 · 17:00 – 17:50 Japan Standard Time
Time zone: Asia/Tokyo Convert Your Time
Google Meet joining info
Video call link: https://meet.google.com/miv-whfs-yjy

Please join https://groups.google.com/g/ros-apac-developer-meeting, so you won’t miss the meeting.

looking forward to e-meeting you all

Best,
Tomoya

1 post - 1 participant

Read full topic

https://discourse.openrobotics.org/t/ros-asia-pacific-developer-meeting-1-7th-nov/50837

ROS Discourse General: FOSDEM 2026: Robotics & Simulation Devroom, 2nd edition!

As spoiled at ROSCon Singapore: We have another developer room for Robotics and Simulation at FOSDEM! FOSDEM arguably the largest open source software developer conference in the world (and it’s free!).

It full event takes place on 2026 Jan 31th - Feb 1th (Sat, Jan 31, 2026 8:00 AM UTC→Sun, Feb 1, 2026 5:00 PM UTC) and it is all on the ULB Solbosch Campus, Brussels, Belgium.

Thanks to the success last year, we will have a full day assigned this time, namely on the Saturday (31th). We now have a call for participation open, in which you can find more information about what kind of talks/projects we are looking for! Deadline for proposal submission is 1th of December!

In the true spirit of FOSDEM, everyone is welcome from any robotics community working in open source. Of course, we would love many of the ROS community to join this time as well, as many of you showed up for the last year edition!

Here is some pictures of last year:

If you want inspiration you check out the recorded talks of last year. Make sure that it needs to be about an open source work, preferably project based, and focus on the sharing of knowledge.

Also make sure that you see any other interesting accepted devrooms you’d like to attend during the event! We will be doing the same ourselves on Sunday, being fueled on club mate.

See you in Brussels!

Arnaud, Mat, Fred, Lucas and Kim

1 post - 1 participant

Read full topic

https://discourse.openrobotics.org/t/fosdem-2026-robotics-simulation-devroom-2nd-edition/50828

ROS Discourse General: NAV2 demonstration on a real robot

I have a repo and YouTube demo of NAV2 running on a real robot.

This will not interest experienced NAV2 users. Also if you are interested in NAV2 in simulation there are better tutorials for this out there.

This is aimed at home hobbyists, who have got their mobile robot working under manual control (e.g. ROS2 Control), but may have struggled to get NAV2 working well. That was me!

YouTube link: https://youtu.be/xmR9_JrH2SY

Repo link: GitHub - jfrancis71/ros2_nav2_demo: Demonstration of how to use the ROS2 Nav2 stack for navigation

Hope this is of interest to someâ€¦

Julian.

1 post - 1 participant

Read full topic

https://discourse.openrobotics.org/t/nav2-demonstration-on-a-real-robot/50815

ROS Discourse General: New ROS 2 Features for Mini Pupper 2

New ROS 2 Features - Mini Pupper 2

Hello everyone,

I’m Kishan Grewal, a Robotics and AI student at University College London (UCL). Over the summer, I interned at MangDang in Hong Kong, where I extended the ROS 2 software stack for the Mini Pupper 2 quadruped robot.

My work broadened the Mini Pupper 2’s ROS 2 ecosystem with additional packages that work across different hardware configurations. Depending on your setup, you can now explore person tracking, autonomous navigation, or multi-robot coordination - all through ROS 2.

Vision-Based Tracking

I developed a tracking node that performs real-time person detection and tracking using a YOLO11n ONNX model with multi-object detection and IMU feedback for stable control.

If you have a Mini Pupper 2 with a compatible Pi camera, this package lets the robot visually follow a person while maintaining orientation. The system includes a lightweight Flask web interface and RViz visualization.

Demo - Vision Tracking

Code - mini_pupper_tracking package

Multi-Robot Fleet Coordination

I created a fleet package that uses ROS 2 namespacing and synchronised state estimation to enable cooperative motion, shared heading control, and distributed communication.

So if you have access to multiple Mini Pupper 2 robots, try out coordinated multi-robot teleoperation.

Demo - Fleet Coordination

Code - mini_pupper_fleet package

Navigation and SLAM

If you’ve fitted your Mini Pupper 2 with a LiDAR sensor, the navigation stack now allows you to use SLAM Toolbox and Nav2 to perform reliable map-based localization and path planning. The configuration is currently tuned for table-area navigation but can be altered for other environments.

This setup enables a Mini Pupper 2 with LiDAR to perform autonomous indoor navigation and mapping.

Demo - Navigation and SLAM

Code - mini_pupper_navigation package

All of these developments have been pushed upstream to the MangDang Robotics Club ROS repository and are available for anyone to explore with their own Mini Pupper 2.

I’d be happy to discuss implementation details or hear from others experimenting with ROS 2 on small quadruped platforms.

Best regards,

Kishan Grewal

GitHub | LinkedIn

4 posts - 2 participants

Read full topic

https://discourse.openrobotics.org/t/new-ros-2-features-for-mini-pupper-2/50806

ROS Discourse General: [First Release] Asyncio For Robotics: Asyncio interface for ROS 2

Hello fellow ROS 2 users,

I wanted to use asyncio with ROS 2 for a while, but didn’t find anything good enough. So I made a library: asyncio_for_robotics: https://github.com/2lian/asyncio-for-robotics

I am looking for feedback from the community, especially as this is my first release . What would you like to see? What is missing? What do you find confusing? What should I put forward?

VVV About the project VVV

Why asyncio?

Asyncio (native python) syntax is easier, with extensive support and documentation.
My lab sees many short term students, enable to grasp the Future/Callback and executor of ROS 2.
- I am very used to it, but what is it the point if the people I code with never understand it?
We work on multi-robots coordination and synchronization.
- The ROS 2 syntax becomes bloated and unreadable fast.
- I for example need to wait for a set of robots (or motors) to reach their target, adding a timeout on top of that.
Asyncio does not have dependencies, is usable with other communication systems. So I can for example, ask a team to process images using RTSP transport (no ROS code), while I work with ROS transport, and we can merge our work.

How `asyncio_for_robotics` works? What’s different?

I spin the ROS node in a background thread (similarly to rclpy_async). The user can directly provide a – possibly custom – node to spin in the background, and the user can still interact with the node object – it is just a standard ros node.

This background node sends data onto the main asyncio thread. I provide the user with only a subscription object that exposes several ways to wait for data: wait for data, wait for new data, wait for next data, async for loop to process all data. This object exposes the data stream of ROS objects: Timer, Subscriber, Service Server (Action Server is not implemented yet). On the other hand, Publisher doesn’t need to be implemented, because the user can directly use the node to create one. Service Client has a very small implementation returning an asyncio future of the call.

Finally, it is named asyncio_for_robotics because it can be used with other transport protocol (like zenoh), if you make an interface for it – there’s a quick tutorial on how to do that.

3 posts - 2 participants

Read full topic

https://discourse.openrobotics.org/t/first-release-asyncio-for-robotics-asyncio-interface-for-ros-2/50795

ROS Discourse General: Cloud Robotics WG Meeting 2025-11-05

Please come and join us for this coming meeting at Wed, Nov 5, 2025 4:00 PM UTC→Wed, Nov 5, 2025 5:00 PM UTC, where we will have a general catch-up, including reviewing the last few sessions with guest talks and how they contribute to our overall goal of building a Logging & Observability community guide.

Last meeting,Sergi Grau-Moya, Co-founder and CEO of INSAION, and Victor Massagué Respall, Co-founder and CTO of INSAION, presented the INSAION platform to the group. This platform is an observability platform for your robot fleet, allowing users to optimise robot operations and explore advanced robot diagnostics. It also has some very impressive visualisations! If you’re interested to see the meeting, it is available on YouTube.

The meeting link for next meeting is here, and you can sign up to our calendar or our Google Group for meeting notifications or keep an eye on the Cloud Robotics Hub.

Hopefully we will see you there!

1 post - 1 participant

Read full topic

https://discourse.openrobotics.org/t/cloud-robotics-wg-meeting-2025-11-05/50752

ROS Discourse General: Free ROSCon 2025 Live Stream

ROSCon 2025 Live Stream is up!

The ROSCon 2025 Live Stream is up!

Weâ€™ve got two channels, one for each session.

You can follow the schedule here.

3 posts - 2 participants

Read full topic

https://discourse.openrobotics.org/t/free-roscon-2025-live-stream/50718

ROS Discourse General: Announcement: rclrs 0.6.0 Release

We’re excited to announce the latest official release of rclrs, right on time for ROSCon ‘25 in Singapore! This new release includes support for two long awaited features: timers and actions!

And not only that, but the Rust code generator is now one of the core generators in Rolling rosidl_core/rosidl_core_generators/package.xml at rolling · ros2/rosidl_core · GitHub

Join us on our Matrix channel if you want to talk about the future of Rust in ROS

I’ll be giving a talk about the ros2-rust project at ROSCon, if your’re around, come say hi!

This release has been possible thanks to the work of these amazing people:

Agustin Alba Chicar
Esteve Fernández
Jesús Silva
Kimberly N. McGuire
Michael X. Grey
Nathan Wiebe Neufeldt
Sam Privett

1 post - 1 participant

Read full topic

https://discourse.openrobotics.org/t/announcement-rclrs-0-6-0-release/50710

ROS Discourse General: Introducing `colcon_gephi` – Generate Rich Dependency Graphs Compatible With Graph Visualization Tools

Have you ever run colcon graph --dot | dot -Tpng -o graph.png, waited a few minutes, and looked at unhelpful pngs?

Have you ever asked thought-provoking questions like:

What package is depended on the most?
Who maintains the most packages in this workspace?
What is the predominant language used in this workspace?

Introducing: colcon_gephi

A colcon plugin to generate rich dependency graphs for a ROS 2 workspace that are compatible with graph visualization tools!

Below is an example graph of the workspace for the ros2 rolling repos. For details on what the graph actually is showing, see Example Graph Details.

Features

Currently supports exporting in:

DOT (default, for Graphviz and other generic graph tools)
GML (human-readable text format, supported by many graph libraries)
GEXF (ideal for Gephi, preserves complex attributes)

Unlike colcon graph, this extension preserves extra package metadata (e.g., maintainers, repository info, build type) as node attributes. This makes it easier to analyze dependency relationships visually in Gephi.

Generates a graph file from your ROS 2 workspace using the same package descriptors as colcon graph.
Automatically includes the following as node attributes:
- Package path
- Build type
- Maintainers
- Version
- Git repository name and remote URL (if applicable)
- Lines of Code (LOC) stats (see Optional Dependencies)
Includes edges for build, run, and test dependencies between packages in the workspace.
Produces output ready to open in Gephi — no manual attribute editing required.

Usage

cd ros2_rolling/ 
colcon gephi_graph

The generated .dot file will have the name of the directory the command was run in. So in this case, it is ros2_rolling.dot.

To change the file format, pass the --format flag.

colcon gephi_graph --format gml

Notes

Graph Visualization Tools

As you can probably guess based on the plugin name, I primarily use Gephi as my graph visualization tool of choice. However, there are more out there which might work with some of the supported output formats. Cytoscape and Argo Lite are two examples although I do not test with these.

Example Graph Details

The graph generated at the top of this post was laid out by following this video. Larger nodes are nodes with more “in-degree” edges (i.e. edges pointing into them), which gives a visual representation of how many packages depend on them. Finally, the colors are based on the package build_type (i.e. ros.ament_cmake, ros.ament_python, etc).

1 post - 1 participant

Read full topic

https://discourse.openrobotics.org/t/introducing-colcon-gephi-generate-rich-dependency-graphs-compatible-with-graph-visualization-tools/50705

ROS Discourse General: Looking for a mentor to guide me in real-world ROS 2 applications — interested in embedded robotics and simulation.

I’m new to the world of robotics, and I’ve been learning ROS2 for a while. I really enjoy it, but to be honest — I’m very confused right now about how to move forward and how to start building real projects.

I’ve studied the basics of ROS2, URDF, and simulation (Gazebo), but I feel stuck when it comes to applying what I’ve learned to something practical.

I’m looking for a mentor — someone with real experience in robotics and ROS2 — who can guide me, help me gain confidence, and point me in the right direction for building real applications.

If you’re open to sharing advice or mentoring someone who’s eager to learn and work hard, I’d be really grateful to connect with you

Thank you in advance for any guidance or suggestions!

3 posts - 2 participants

Read full topic

https://discourse.openrobotics.org/t/looking-for-a-mentor-to-guide-me-in-real-world-ros-2-applications-interested-in-embedded-robotics-and-simulation/50698

ROS Discourse General: RKO-LIO: LiDAR-Inertial Odometry

Hey everyone,

I wanted to share my new LiDAR-Inertial Odometry system, RKO-LIO:

Below is an example of the results on data from different platforms and environments.

One of the main goals was to make the odometry run with little to no configuration, out of the box. The only real requirement for the system is the extrinsic calibration between the IMU and LiDAR. If that’s available, the defaults should just work. If tuning is needed, the parameters are straightforward and their number minimal.

Supported ROS distros: Humble, Jazzy, Kilted, and Rolling.
The package is already released, so you can simply install it with:

sudo apt install ros-${ROS_DISTRO}-rko-lio
ros2 launch rko_lio odometry.launch.py

For a quick test, there’s also a Python interface you can install via pip (no ROS setup needed)

pip install rko_lio rosbags rerun-sdk
rko_lio -v /path/to/your/rosbag

If your bag includes a TF tree, the extrinsics will be automatically extracted.

Documentation is also available and being updated over time, at

Note that the docs there may trail a few days behind the main repo (as and when the ROS build farm runs the doc job).

I’d really appreciate it if the community could try it out, and share any feedback.

Best,
Meher

1 post - 1 participant

Read full topic

https://discourse.openrobotics.org/t/rko-lio-lidar-inertial-odometry/50696

ROS Discourse General: Questions to intrinsic and extrinsic calibration. Any help?

Hi folks,

I am planning to build a calibration station for intrinsic and extrinsic parameters using a monitor as the target.
Has anyone here tried using a monitor for calibration before?
Any tips on which type of monitor works best for this setup?

Cheers,
Your Calibration man

2 posts - 2 participants

Read full topic

https://discourse.openrobotics.org/t/questions-to-intrinsic-and-extrinsic-calibration-any-help/50687

ROS Discourse General: Blog post: Reproducible cross-platform ROS installation with Pixi

Hey all,

We’ve seen a big increase in the interest on making ROS supported on multiple platforms. And in general easier to install. This is not the first time I post on this forum about this, but seeing it’s a recurring topic, I would like to cross-post our latest blog post on the matter.

Blog post: Pixi: Modern package management for Robotics | prefix.dev

I’ve included a few of short videos to showcase what it could look like if you use ROS through Pixi.

I’m really looking forward to discussing the topic further at ROSCon2025. There will be two related BOF’s on Monday:

10:00: Deployment & Launch Tooling, by Emerson Knapp
15:00: Tools for Environment Isolation, by Nathan Brooks

And @KimMcG and myself will present on the topic on Wednesday starting at 14:00.

Please try it out and let me know what you think!

Let’s make it easy and quick to install ROS anywhere and bring ROS to a new level of users it can reach!

10 posts - 8 participants

Read full topic

https://discourse.openrobotics.org/t/blog-post-reproducible-cross-platform-ros-installation-with-pixi/50683

ROS Discourse General: Introducing: `ros2_fmt_logger`

Tired of fixing compile issues like:

warning: format ‘%d’ expects argument of type ‘int’, but argument has type ‘std::vector<int>::size_type’ {aka ‘long unsigned int’} [-Wformat=]

when you want to print a vector size?

Or writing .c_str() when printing an std::string?

Confused when using milliseconds to throttle?^[1]

Introducing:

ros2_fmt_logger

A modern, ROS 2 logging library that provides fmt-style formatting as a replacement for RCLCPP logging macros.

Features

Function calls instead of macros: logger.info("Hello, {}!", name) instead of RCLCPP_INFO(logger, "Hello, %s", name.c_str())
Additional .on_change() method for logging changes in values
chrono syntax for throttling: logger.warn_throttle(1s, "Warning: {}", value)
backwards compatible with the macros, so easy to start using in existing projects without a full rewrite of the current log statements

Examples

Once-only logging

logger.info_once("This message will only appear once, no matter how many times called");

Throttled logging

using std::chrono_literals::operator""s;
logger.warn_throttle(1s, "This warning appears at most once per second: {}", value);

Change-based logging

// Log only when the value changes
logger.info_on_change(sensor_value, "Sensor reading changed to: {}", sensor_value);

// Log only when change exceeds threshold
logger.error_on_change(temperature, 5.0, "Temperature changed significantly: {:.1f}°C", temperature);

Format String Syntax

Uses the powerful fmt library format syntax:

// Basic formatting
logger.info("Hello, {}!", name);

// Positional arguments
logger.info("Processing {1} of {0} items", total, current);

// Format specifiers
logger.info("Progress: {:.1%}", progress);  // Percentage with 1 decimal
logger.info("Value: {:08.2f}", value);     // Zero-padded floating point
logger.info("Hex: {:#x}", number);         // Hexadecimal with 0x prefix

// Container formatting (requires fmt/ranges.h)
logger.info("Values: {}", std::vector{1, 2, 3, 4});

See demo_ros2_fmt_logger.cpp for more examples.

NAQ

Why not use std::format?
- fmt is still more powerful, like when printing ranges. Also rclcpp already depends on it indirectly, so it’s kind of free.

Isn’t this why we have _STREAM macros?

Yes, but it’s longer

double progress = 0.756;
logger.info("Progress: {:.1} %", progress);
RCLCPP_INFO_STREAM(logger, "Progress: " << std::setprecision(1) << progress << " %");

This is a direct violation of REP-103 ↩︎

3 posts - 2 participants

Read full topic

https://discourse.openrobotics.org/t/introducing-ros2-fmt-logger/50665

ROS Discourse General: Gamepad Teleoperation for Robotic Arm—A New Intuitive Control Experience

Hi everyone!

Iâ€™d like to share a project that enables intuitive control of the PiPER robotic arm using a standard gamepad. This might be useful for those working on robotic arm teleoperation or looking for a ready-to-use control interface.

Overview

This project provides precise and intuitive control of the PiPER robotic arm through a conventional game controller in a visual environment. It supports multiple kinematics libraries and offers both joint-space and task-space control modes.

Control a Robotic Arm Like a Game! ğŸ�®

Key Features:

Gamepad-based teleoperation
Joint control and Pose control modes
Gripper control with intuitive triggers
Forward/Inverse kinematics support
Web-based visualization
Position memory and playback

Repository: GitHub - kehuanjack/Gamepad_PiPER: This project implements the functionality of teleoperating a PiPER robotic arm using a gamepad.
Organization: GitHub - agilexrobotics/Agilex-College: Agilex College

Environment Setup

Requirements:

Operating System: Ubuntu 20.04 or higher
Python: 3.9 or higher (Anaconda/Miniconda recommended)

Installation:

git clone https://github.com/kehuanjack/Gamepad_PiPER.git
cd Gamepad_PiPER

Choose your kinematics library (cuRobo recommended):

Option 1: pinocchio library (Python 3.9) (click for more details) Option 2: PyRoKi library (Python â‰¥ 3.10) (click for more details) Option 3: cuRobo library (Python â‰¥ 3.8, CUDA 11.8 recommended) â� (click for more details)

Quick Start

Connect robotic arm and activate CAN:

   sudo ip link set can0 up type can bitrate 1000000

Connect gamepad via USB or Bluetooth
Launch control service:

   python3 main_virtual.py  # Recommended for first-time testing
   # or
   python3 main.py  # For real robot control

Open web interface: Navigate to http://localhost:8080 for visualization

Gamepad Control Mapping

Button Functions

Button	Short Press	Long Press
HOME	Connect/Disconnect arm	-
START	Switch upper control mode (Joint/Pose)	Switch lower control mode
BACK	Switch command mode (0x00/0xAD)	-
Y	Return to zero position	-
A	Save current position	Clear saved position
B	Restore last saved position	-
X	Toggle playback order	Clear all positions
LB	Increase speed factor	Decrease speed factor
RB	Increase movement speed	Decrease movement speed

Joysticks & Triggers

Control	Joint Mode	Pose Mode
Left Stick	J1 (Left/Right), J2 (Up/Down)	End-effector X/Y movement
Right Stick	J3 (Up/Down), J6 (Left/Right)	End-effector Z & rotation around Z
D-pad	J4 (Left/Right), J5 (Up/Down)	End-effector rotation around X/Y
LT	Close gripper	Close gripper
RT	Open gripper	Open gripper

Additional Features

Gripper Control: 0-100% range with quick toggle at extremes
Speed Control: 0.25x to 5.0x multipliers, 10%-100% movement speed
Position Memory: Save multiple waypoints with sequential/reverse playback

Safety Warnings

Start with virtual testing: Run main_virtual.py first
Begin at low speeds until familiar with controls
Maintain safe distance during operation
Beware of singularities: Numerical IK solutions may cause sudden joint movements
Quick response mode (0xAD) is dangerous: Use with extreme caution

Contributing & Feedback

Feel free to try it out and share your feedback! Issues and pull requests are welcome on the GitHub repository.

Has anyone else worked on similar gamepad teleoperation projects? Would love to hear about your experiences!

Cheers!

2 posts - 2 participants

Read full topic

https://discourse.openrobotics.org/t/gamepad-teleoperation-for-robotic-arm-a-new-intuitive-control-experience/50664

ROS Discourse General: Announcing rosetta: a ROS 2 ⇄ LeRobot bridge

Announcing rosetta: a ROS 2 ⇄ LeRobot bridge

LeRobot is great for experimenting with state-of-the-art policies and sharing datasets/pretrained models. But actually using or fine-tuning those models on ROS 2 robots isn’t easy.

I’m working on rosetta, a ROS 2 package that helps LeRobot models play nicely with ROS 2 robots.

What’s inside

EpisodeRecorderServer — Action-driven recording to rosbag2; each episode stores a task/prompt in bag metadata for later export.
bag_to_lerobot.py — Converts one or more bags into a ready-to-train LeRobot v3 dataset (Parquet + MP4 with rich metadata).
PolicyBridge — Runs a pretrained LeRobot policy at the contract rate, subscribes to ROS 2 topics as observations, and publishes actions (e.g., geometry_msgs/Twist).
Contract YAML — Assigns which topics are used as observations and which are used as actions (plus specifics on handling, timing, and rates). The same contract is used consistently from data collection through to inference to keep everything aligned.

A simple example to start

I’ve posted a TurtleBot3 demo dataset (53 short episodes) and a lightweight ACT checkpoint trained on that data for a couple hours on a laptop. It’s far from a great dataset (I crash during training in places and kept the episode count modest), but it should help you get going—then swap in your robot by editing the contract and start iterating.

Dataset: https://huggingface.co/datasets/iblnk/turtlebot3_demo
Model (ACT): https://huggingface.co/iblnk/act-turtlebot3_demo

What’s next

I’ve got a backlog I’m actively working through:

More built-in decoders/encoders for common message types
A refactor into separate client/policy composable nodes
Leveraging an async policy server so inference can run off-robot (no ROS 2 on the GPU box)
Fixes for a growing list of bugs

I’d love feedback

Thanks for taking a look!

1 post - 1 participant

Read full topic

https://discourse.openrobotics.org/t/announcing-rosetta-a-ros-2-lerobot-bridge/50657

ROS Discourse General: Extending meta-ros with ros2 + openembedded (yocto)

Hey all,

not sure if this is the right place for it or if I should jump over to discord. We have our own ros2 workspace extending kilted that we’d like to include in our yocto image. Is there a preferred way for creating the receipes - and if so how? After a bit of looking around it seems there’s superflore but I’m not sure if it is intended for use outside of meta-ros.
It seems like the other option is to manually create the receipes for each package in our workspace based off the autogenerated ones?
Is there a third option I am missing?

Thanks in advance,
Nico

2 posts - 2 participants

Read full topic

https://discourse.openrobotics.org/t/extending-meta-ros-with-ros2-openembedded-yocto/50650

ROS Discourse General: Announcing GitHub syntax highlighting for ROS msg files

Hi folks â€“ wanted to share that msg/srv/action files are now highlighted with pretty colors on GitHub! This works via a new ROS tmLanguage grammar that I added to GitHub Linguist.

For example, Imu.msg now looks like this:

You can also get highlighting in multi-line code blocks by tagging them with ```rosmsg.

The same syntax highlighting support is also available for Visual Studio Code via the Robotics Development Extensions maintained by @ooeygui.

Enjoy! I hope this makes your life just a little bit easier

6 posts - 4 participants

Read full topic

https://discourse.openrobotics.org/t/announcing-github-syntax-highlighting-for-ros-msg-files/50642

ROS Discourse General: Come Join Me At ROSCon 2025 in Singapore

Can’t wait to see you all at ROSCon 2025 in Singapore!

I’ll be there with my NVIDIA colleagues, and we’re excited to connect with you at our workshops and talks—an awesome chance to learn directly from the experts.

Here are some talks you won’t want to miss:

Monday, October 27th - 8am-12pm SST: Scalable Multi-Robot Scene Workflows Using ROS Simulation Interfaces Standard in Isaac Sim

The new ROS Simulation Interfaces standard (developed in collaboration with O3DE, NVIDIA Isaac Sim, and Gazebo) provides a unified approach to interacting with simulation environments, regardless of the engine used. This workshop highlights the practical implementation of Simulation Interfaces within NVIDIA Isaac Sim and will showcase how this standard facilitates multi robot scene generation, deployment and environmental manipulation, in a reproducible manner suited for automated testing. Isaac Sim’s support offers photorealistic simulation and is GPU-accelerated. By harnessing the capabilities of the new Simulation Interfaces standard, researchers and developers in perception, navigation, and manipulation can benefit by quickly building workflows, switching between simulators, or using multiple simulators in parallel.

Monday, October 27th - 12:30pm-1:30pm SST: Evolving ROS 2 for Real-Time Control of Learned Policy-Driven Robots

Advancing the state of the art in robotics today requires tackling the challenges of physical AI. For humanoids, this requires running computationally intensive AI models with extensive sets of sensors and actuators all with the strictest demands of real-time performance. There is a clear opportunity for a collaborative effort to grow ROS 2 as the ideal platform and ecosystem for enabling embodied AI agents. This talk will explore a vision for enhancing the ROS 2 core to become accelerator-aware yet accelerator-agnostic, where accelerated compute becomes a first-class partner in learned, real-time control. We will discuss open, vendor-neutral strategies for this integration, aiming to provide the entire community with a more powerful and reliable foundation for developing and deploying intelligent robots.

Tuesday, October 28th - 11:10am SST: On Use of Nav2 Route Server

We introduce Nav2’s newest server, Nav2 Route. It performs sparse route graph-based planning and progress tracking to enable routing across massive regions in real-time, enforcing deterministic execution, and/or performing operations throughout task execution leveraging arbitrary graph-defined metadata. This fills a broad need in the community for production capabilities in indoor logistics, massive outdoor spaces, and placing limits on navigable regions. This package uses several unique plugin interfaces to allow use-case specific behaviors to create bespoke applications easily. This talk will go over the key points of the server, demonstrations, and how to enable it in user applications.

Tuesday, October 28th - 15:50-16:00 SST: SWAGGER: Sparse Waypoint Graph Generation for Efficient Routing

SWAGGER (Sparse WAypoint Graph Generation for Efficient Routing) automatically generates sparse waypoint graphs from occupancy grid maps, enabling efficient path planning through pre-computed connectivity.

Using a multi-stage approach combining skeleton extraction and strategic node placement, SWAGGER creates optimized graphs that reduce computational complexity from O(n²) grid-based search to O(k²) graph search where k << n. Beyond single-robot navigation, these sparse graphs enable efficient large-scale multi-robot planning. We demonstrate practical integration as a drop-in ROS 2 Nav2 global planner plugin and show how the same graphs can guide neural navigation systems like NVIDIA’s COMPASS. This lightning talk will present the core algorithm, showcase integration patterns, and provide actionable insights for immediate adoption in existing ROS 2 navigation stacks.

Wednesday, October 29th - 17:00-17:10 SST: Building Foundation Models for Generalist Robots: Insights and Challenges in Robot Learning

This session focuses on the recent advancements in robot learning, specifically the development of foundation models for general-purpose robots. Key areas will be explored, including imitation learning, reinforcement learning, and vision-language-action (VLA) models. A highlight will be our NVIDIA’s GR00T with open-source VLA models. We will discuss the research work, infrastructure, ROS implementation, and challenges encountered in the domain. Finally, we will discuss the future of robotics enhanced by learning-based systems.

Wednesday, October 29th - 17:00-17:20 SST: Introducing the New ROS Simulation Standard

This talk brings forward simulation interfaces package, a new standard for ROS, and its implementation in popular simulators. There are multiple simulators with ROS integrations. Each has unique strengths; none is best for everyone. Still, the way they are used is often very similar. The new standard makes it easier to build integrations, switch between simulators, or even use multiple simulators in parallel. You will learn how to use its highly useful features such as spawning robots and other objects, moving things around for testing, stepping through simulation, and querying the virtual world for ground truth data.

Looking forward to connecting at ROSCon. Hope to see you there!

To learn more about NVIDIA at ROSCon go here > https://www.nvidia.com/en-us/events/roscon/

Full ROSCon Singapore details here ROSCon 2025

1 post - 1 participant

Read full topic

https://discourse.openrobotics.org/t/come-join-me-at-roscon-2025-in-singapore/50637

ROS Discourse General: ManyMove v0.2.0 - Setup with Docker container and unified main branch

Hi!
I just created a new branch main for ManyMove: this represents a unified codebase that compiles on both Humble and Jazzy while retaining all previous functionalities.

To make testing ManyMove easier, I also created docker builds that will prepare a container ready to run examples.The most complete container is the one that also sets up xarm_ros2, so you’ll be able to run all examples.

Here’s an even shorter startup than the one in the docs for a quick setup for humble. Change
MANYMOVE_ROS_WS to your desired folder:

export MANYMOVE_ROS_WS=~/workspaces/dev_ws
mkdir -p ${MANYMOVE_ROS_WS}/src
cd ${MANYMOVE_ROS_WS}/src
git clone https://github.com/pastoriomarco/manymove.git -b main
${MANYMOVE_ROS_WS}/src/manymove/manymove_bringup/docker/run_manymove_xarm_container.sh humble

Then, inside the container, for Panda example:

ros2 launch manymove_bringup panda_moveitcpp_fake_cpp_trees.launch.py

Still inside the container, for UFactory dual robot example:

ros2 launch manymove_bringup dual_moveitcpp_fake_app.launch.py

I’m not sure this unified humble/jazzy approach is a good one, but I was investing too much time propagating the development on both branches. At least now I have some simple CI and tests to keep it checked, and I need to update just one branch. The dev branch will be the one where I keep developing, merging to main when the new code is stable and checked.

If anyone finds trouble setting up or running ManyMove let me know!

PS: I mainly tested it in Ubuntu 22.04 and 24.04, but it seems it works on WSL2 on Win11 too, just make sure to install docker following ubuntu instructions, including linux postinstall

1 post - 1 participant

Read full topic

https://discourse.openrobotics.org/t/manymove-v0-2-0-setup-with-docker-container-and-unified-main-branch/50630

ROS Discourse General: Join My Workshop at ROSCon Singapore

Excited to head to Singapore next week for ROSCon!

Join me Monday at 12:30 SST for my workshop:
Evolving ROS 2 for Real-Time Control of Learned Policy-Driven Robots

Weâ€™ll explore how ROS 2 can evolve to power the next generation of embodied AI and how we can make it both accelerator aware and accelerator agnostic to drive physical AI forward together.
See you there!
More about ROSCon Singapore ROSCon 2025

1 post - 1 participant

Read full topic

https://discourse.openrobotics.org/t/join-my-workshop-at-roscon-singapore/50629

ROS Discourse General: New packages for Humble Hawksbill 2025-10-20

Package Updates for humble

Added Packages [61]:

ros-humble-bcr-arm: 0.1.1-1
ros-humble-bcr-arm-description: 0.1.1-1
ros-humble-bcr-arm-gazebo: 0.1.1-1
ros-humble-bcr-arm-moveit-config: 0.1.1-1
ros-humble-bcr-arm-ros2: 0.1.1-1
ros-humble-etsi-its-conversion-srvs: 3.4.0-1
ros-humble-etsi-its-conversion-srvs-dbgsym: 3.4.0-1
ros-humble-jrl-cmakemodules: 1.1.0-2
ros-humble-kuka-kss-message-handler: 1.0.0-1
ros-humble-kuka-kss-message-handler-dbgsym: 1.0.0-1
ros-humble-kuka-rsi-driver: 1.0.0-1
ros-humble-kuka-rsi-driver-dbgsym: 1.0.0-1
ros-humble-launch-frontend-py: 0.1.0-1
ros-humble-mola-input-lidar-bin-dataset: 2.0.0-1
ros-humble-mola-input-lidar-bin-dataset-dbgsym: 2.0.0-1
ros-humble-moveit-task-constructor-capabilities: 0.1.3-1
ros-humble-moveit-task-constructor-capabilities-dbgsym: 0.1.3-1
ros-humble-moveit-task-constructor-core: 0.1.3-1
ros-humble-moveit-task-constructor-core-dbgsym: 0.1.3-1
ros-humble-moveit-task-constructor-demo: 0.1.3-1
ros-humble-moveit-task-constructor-demo-dbgsym: 0.1.3-1
ros-humble-moveit-task-constructor-msgs: 0.1.3-1
ros-humble-moveit-task-constructor-msgs-dbgsym: 0.1.3-1
ros-humble-moveit-task-constructor-visualization: 0.1.3-1
ros-humble-moveit-task-constructor-visualization-dbgsym: 0.1.3-1
ros-humble-orbbec-camera: 1.5.14-1
ros-humble-orbbec-camera-dbgsym: 1.5.14-1
ros-humble-orbbec-camera-msgs: 1.5.14-1
ros-humble-orbbec-camera-msgs-dbgsym: 1.5.14-1
ros-humble-orbbec-description: 1.5.14-1
ros-humble-ouster-sensor-msgs: 0.13.14-2
ros-humble-ouster-sensor-msgs-dbgsym: 0.13.14-2
ros-humble-pal-pro-gripper: 1.7.2-1
ros-humble-pal-pro-gripper-bringup: 1.7.2-1
ros-humble-pal-pro-gripper-controller-configuration: 1.7.2-1
ros-humble-pal-pro-gripper-description: 1.7.2-1
ros-humble-pal-pro-gripper-wrapper: 1.7.2-1
ros-humble-play-motion-builder: 1.4.0-1
ros-humble-play-motion-builder-dbgsym: 1.4.0-1
ros-humble-play-motion-builder-msgs: 1.4.0-1
ros-humble-play-motion-builder-msgs-dbgsym: 1.4.0-1
ros-humble-pluginlib-dbgsym: 5.1.2-1
ros-humble-pymoveit2: 4.0.0-1
ros-humble-rko-lio: 0.1.6-1
ros-humble-rko-lio-dbgsym: 0.1.6-1
ros-humble-rmw-stats-shim: 0.2.2-1
ros-humble-rmw-stats-shim-dbgsym: 0.2.2-1
ros-humble-ros2-fmt-logger: 1.0.1-1
ros-humble-ros2-fmt-logger-dbgsym: 1.0.1-1
ros-humble-ros2plugin: 5.1.2-1
ros-humble-rosgraph-monitor: 0.2.2-1
ros-humble-rosgraph-monitor-dbgsym: 0.2.2-1
ros-humble-rosgraph-monitor-msgs: 0.2.2-1
ros-humble-rosgraph-monitor-msgs-dbgsym: 0.2.2-1
ros-humble-rqt-play-motion-builder: 1.4.0-1
ros-humble-rqt-play-motion-builder-dbgsym: 1.4.0-1
ros-humble-rviz-marker-tools: 0.1.3-1
ros-humble-rviz-marker-tools-dbgsym: 0.1.3-1
ros-humble-tiago-pro-head-bringup: 1.6.0-1
ros-humble-tiago-pro-head-controller-configuration: 1.6.0-1
ros-humble-tiago-pro-head-description: 1.6.0-1

Updated Packages [475]:

ros-humble-ackermann-steering-controller: 2.50.0-1 → 2.50.1-1
ros-humble-ackermann-steering-controller-dbgsym: 2.50.0-1 → 2.50.1-1
ros-humble-action-tutorials-cpp: 0.20.5-1 → 0.20.6-1
ros-humble-action-tutorials-cpp-dbgsym: 0.20.5-1 → 0.20.6-1
ros-humble-action-tutorials-interfaces: 0.20.5-1 → 0.20.6-1
ros-humble-action-tutorials-interfaces-dbgsym: 0.20.5-1 → 0.20.6-1
ros-humble-action-tutorials-py: 0.20.5-1 → 0.20.6-1
ros-humble-admittance-controller: 2.50.0-1 → 2.50.1-1
ros-humble-admittance-controller-dbgsym: 2.50.0-1 → 2.50.1-1
ros-humble-bicycle-steering-controller: 2.50.0-1 → 2.50.1-1
ros-humble-bicycle-steering-controller-dbgsym: 2.50.0-1 → 2.50.1-1
ros-humble-clearpath-common: 1.3.6-1 → 1.3.7-1
ros-humble-clearpath-config: 1.3.2-1 → 1.3.3-1
ros-humble-clearpath-control: 1.3.6-1 → 1.3.7-1
ros-humble-clearpath-customization: 1.3.6-1 → 1.3.7-1
ros-humble-clearpath-description: 1.3.6-1 → 1.3.7-1
ros-humble-clearpath-generator-common: 1.3.6-1 → 1.3.7-1
ros-humble-clearpath-generator-common-dbgsym: 1.3.6-1 → 1.3.7-1
ros-humble-clearpath-manipulators: 1.3.6-1 → 1.3.7-1
ros-humble-clearpath-manipulators-description: 1.3.6-1 → 1.3.7-1
ros-humble-clearpath-mounts-description: 1.3.6-1 → 1.3.7-1
ros-humble-clearpath-platform-description: 1.3.6-1 → 1.3.7-1
ros-humble-clearpath-sensors-description: 1.3.6-1 → 1.3.7-1
ros-humble-coal: 3.0.1-1 → 3.0.2-1
ros-humble-coal-dbgsym: 3.0.1-1 → 3.0.2-1
ros-humble-composition: 0.20.5-1 → 0.20.6-1
ros-humble-composition-dbgsym: 0.20.5-1 → 0.20.6-1
ros-humble-control-toolbox: 3.6.1-1 → 3.6.2-1
ros-humble-control-toolbox-dbgsym: 3.6.1-1 → 3.6.2-1
ros-humble-costmap-queue: 1.1.18-1 → 1.1.19-1
ros-humble-costmap-queue-dbgsym: 1.1.18-1 → 1.1.19-1
ros-humble-demo-nodes-cpp: 0.20.5-1 → 0.20.6-1
ros-humble-demo-nodes-cpp-dbgsym: 0.20.5-1 → 0.20.6-1
ros-humble-demo-nodes-cpp-native: 0.20.5-1 → 0.20.6-1
ros-humble-demo-nodes-cpp-native-dbgsym: 0.20.5-1 → 0.20.6-1
ros-humble-demo-nodes-py: 0.20.5-1 → 0.20.6-1
ros-humble-diff-drive-controller: 2.50.0-1 → 2.50.1-1
ros-humble-diff-drive-controller-dbgsym: 2.50.0-1 → 2.50.1-1
ros-humble-draco-point-cloud-transport: 1.0.11-1 → 1.0.12-1
ros-humble-draco-point-cloud-transport-dbgsym: 1.0.11-1 → 1.0.12-1
ros-humble-dummy-map-server: 0.20.5-1 → 0.20.6-1
ros-humble-dummy-map-server-dbgsym: 0.20.5-1 → 0.20.6-1
ros-humble-dummy-robot-bringup: 0.20.5-1 → 0.20.6-1
ros-humble-dummy-sensors: 0.20.5-1 → 0.20.6-1
ros-humble-dummy-sensors-dbgsym: 0.20.5-1 → 0.20.6-1
ros-humble-dwb-core: 1.1.18-1 → 1.1.19-1
ros-humble-dwb-core-dbgsym: 1.1.18-1 → 1.1.19-1
ros-humble-dwb-critics: 1.1.18-1 → 1.1.19-1
ros-humble-dwb-critics-dbgsym: 1.1.18-1 → 1.1.19-1
ros-humble-dwb-msgs: 1.1.18-1 → 1.1.19-1
ros-humble-dwb-msgs-dbgsym: 1.1.18-1 → 1.1.19-1
ros-humble-dwb-plugins: 1.1.18-1 → 1.1.19-1
ros-humble-dwb-plugins-dbgsym: 1.1.18-1 → 1.1.19-1
ros-humble-dynamixel-hardware-interface: 1.4.14-1 → 1.4.16-1
ros-humble-dynamixel-hardware-interface-dbgsym: 1.4.14-1 → 1.4.16-1
ros-humble-effort-controllers: 2.50.0-1 → 2.50.1-1
ros-humble-effort-controllers-dbgsym: 2.50.0-1 → 2.50.1-1
ros-humble-eigenpy: 3.11.0-1 → 3.12.0-1
ros-humble-eigenpy-dbgsym: 3.11.0-1 → 3.12.0-1
ros-humble-eiquadprog: 1.2.9-2 → 1.3.0-1
ros-humble-eiquadprog-dbgsym: 1.2.9-2 → 1.3.0-1
ros-humble-etsi-its-cam-coding: 3.3.0-1 → 3.4.0-1
ros-humble-etsi-its-cam-coding-dbgsym: 3.3.0-1 → 3.4.0-1
ros-humble-etsi-its-cam-conversion: 3.3.0-1 → 3.4.0-1
ros-humble-etsi-its-cam-msgs: 3.3.0-1 → 3.4.0-1
ros-humble-etsi-its-cam-msgs-dbgsym: 3.3.0-1 → 3.4.0-1
ros-humble-etsi-its-cam-ts-coding: 3.3.0-1 → 3.4.0-1
ros-humble-etsi-its-cam-ts-coding-dbgsym: 3.3.0-1 → 3.4.0-1
ros-humble-etsi-its-cam-ts-conversion: 3.3.0-1 → 3.4.0-1
ros-humble-etsi-its-cam-ts-msgs: 3.3.0-1 → 3.4.0-1
ros-humble-etsi-its-cam-ts-msgs-dbgsym: 3.3.0-1 → 3.4.0-1
ros-humble-etsi-its-coding: 3.3.0-1 → 3.4.0-1
ros-humble-etsi-its-conversion: 3.3.0-1 → 3.4.0-1
ros-humble-etsi-its-conversion-dbgsym: 3.3.0-1 → 3.4.0-1
ros-humble-etsi-its-cpm-ts-coding: 3.3.0-1 → 3.4.0-1
ros-humble-etsi-its-cpm-ts-coding-dbgsym: 3.3.0-1 → 3.4.0-1
ros-humble-etsi-its-cpm-ts-conversion: 3.3.0-1 → 3.4.0-1
ros-humble-etsi-its-cpm-ts-msgs: 3.3.0-1 → 3.4.0-1
ros-humble-etsi-its-cpm-ts-msgs-dbgsym: 3.3.0-1 → 3.4.0-1
ros-humble-etsi-its-denm-coding: 3.3.0-1 → 3.4.0-1
ros-humble-etsi-its-denm-coding-dbgsym: 3.3.0-1 → 3.4.0-1
ros-humble-etsi-its-denm-conversion: 3.3.0-1 → 3.4.0-1
ros-humble-etsi-its-denm-msgs: 3.3.0-1 → 3.4.0-1
ros-humble-etsi-its-denm-msgs-dbgsym: 3.3.0-1 → 3.4.0-1
ros-humble-etsi-its-denm-ts-coding: 3.3.0-1 → 3.4.0-1
ros-humble-etsi-its-denm-ts-coding-dbgsym: 3.3.0-1 → 3.4.0-1
ros-humble-etsi-its-denm-ts-conversion: 3.3.0-1 → 3.4.0-1
ros-humble-etsi-its-denm-ts-msgs: 3.3.0-1 → 3.4.0-1
ros-humble-etsi-its-denm-ts-msgs-dbgsym: 3.3.0-1 → 3.4.0-1
ros-humble-etsi-its-mapem-ts-coding: 3.3.0-1 → 3.4.0-1
ros-humble-etsi-its-mapem-ts-coding-dbgsym: 3.3.0-1 → 3.4.0-1
ros-humble-etsi-its-mapem-ts-conversion: 3.3.0-1 → 3.4.0-1
ros-humble-etsi-its-mapem-ts-msgs: 3.3.0-1 → 3.4.0-1
ros-humble-etsi-its-mapem-ts-msgs-dbgsym: 3.3.0-1 → 3.4.0-1
ros-humble-etsi-its-mcm-uulm-coding: 3.3.0-1 → 3.4.0-1
ros-humble-etsi-its-mcm-uulm-coding-dbgsym: 3.3.0-1 → 3.4.0-1
ros-humble-etsi-its-mcm-uulm-conversion: 3.3.0-1 → 3.4.0-1
ros-humble-etsi-its-mcm-uulm-msgs: 3.3.0-1 → 3.4.0-1
ros-humble-etsi-its-mcm-uulm-msgs-dbgsym: 3.3.0-1 → 3.4.0-1
ros-humble-etsi-its-messages: 3.3.0-1 → 3.4.0-1
ros-humble-etsi-its-msgs: 3.3.0-1 → 3.4.0-1
ros-humble-etsi-its-msgs-utils: 3.3.0-1 → 3.4.0-1
ros-humble-etsi-its-primitives-conversion: 3.3.0-1 → 3.4.0-1
ros-humble-etsi-its-rviz-plugins: 3.3.0-1 → 3.4.0-1
ros-humble-etsi-its-rviz-plugins-dbgsym: 3.3.0-1 → 3.4.0-1
ros-humble-etsi-its-spatem-ts-coding: 3.3.0-1 → 3.4.0-1
ros-humble-etsi-its-spatem-ts-coding-dbgsym: 3.3.0-1 → 3.4.0-1
ros-humble-etsi-its-spatem-ts-conversion: 3.3.0-1 → 3.4.0-1
ros-humble-etsi-its-spatem-ts-msgs: 3.3.0-1 → 3.4.0-1
ros-humble-etsi-its-spatem-ts-msgs-dbgsym: 3.3.0-1 → 3.4.0-1
ros-humble-etsi-its-vam-ts-coding: 3.3.0-1 → 3.4.0-1
ros-humble-etsi-its-vam-ts-coding-dbgsym: 3.3.0-1 → 3.4.0-1
ros-humble-etsi-its-vam-ts-conversion: 3.3.0-1 → 3.4.0-1
ros-humble-etsi-its-vam-ts-msgs: 3.3.0-1 → 3.4.0-1
ros-humble-etsi-its-vam-ts-msgs-dbgsym: 3.3.0-1 → 3.4.0-1
ros-humble-fastrtps-cmake-module: 2.2.2-2 → 2.2.3-1
ros-humble-force-torque-sensor-broadcaster: 2.50.0-1 → 2.50.1-1
ros-humble-force-torque-sensor-broadcaster-dbgsym: 2.50.0-1 → 2.50.1-1
ros-humble-forward-command-controller: 2.50.0-1 → 2.50.1-1
ros-humble-forward-command-controller-dbgsym: 2.50.0-1 → 2.50.1-1
ros-humble-foxglove-bridge: 0.8.5-1 → 3.2.1-1
ros-humble-foxglove-bridge-dbgsym: 0.8.5-1 → 3.2.1-1
ros-humble-foxglove-msgs: 2.3.0-1 → 3.2.1-1
ros-humble-foxglove-msgs-dbgsym: 2.3.0-1 → 3.2.1-1
ros-humble-fri-configuration-controller: 0.9.2-1 → 1.0.0-1
ros-humble-fri-configuration-controller-dbgsym: 0.9.2-1 → 1.0.0-1
ros-humble-fri-state-broadcaster: 0.9.2-1 → 1.0.0-1
ros-humble-fri-state-broadcaster-dbgsym: 0.9.2-1 → 1.0.0-1
ros-humble-gpio-controllers: 2.50.0-1 → 2.50.1-1
ros-humble-gpio-controllers-dbgsym: 2.50.0-1 → 2.50.1-1
ros-humble-gripper-controllers: 2.50.0-1 → 2.50.1-1
ros-humble-gripper-controllers-dbgsym: 2.50.0-1 → 2.50.1-1
ros-humble-gz-ros2-control: 0.7.16-1 → 0.7.17-1
ros-humble-gz-ros2-control-dbgsym: 0.7.16-1 → 0.7.17-1
ros-humble-gz-ros2-control-demos: 0.7.16-1 → 0.7.17-1
ros-humble-gz-ros2-control-demos-dbgsym: 0.7.16-1 → 0.7.17-1
ros-humble-gz-ros2-control-tests: 0.7.16-1 → 0.7.17-1
ros-humble-hebi-cpp-api: 3.13.0-1 → 3.15.0-1
ros-humble-hebi-cpp-api-dbgsym: 3.13.0-1 → 3.15.0-1
ros-humble-ign-ros2-control: 0.7.16-1 → 0.7.17-1
ros-humble-ign-ros2-control-demos: 0.7.16-1 → 0.7.17-1
ros-humble-ign-ros2-control-demos-dbgsym: 0.7.16-1 → 0.7.17-1
ros-humble-iiqka-moveit-example: 0.9.2-1 → 1.0.0-1
ros-humble-iiqka-moveit-example-dbgsym: 0.9.2-1 → 1.0.0-1
ros-humble-image-tools: 0.20.5-1 → 0.20.6-1
ros-humble-image-tools-dbgsym: 0.20.5-1 → 0.20.6-1
ros-humble-imu-sensor-broadcaster: 2.50.0-1 → 2.50.1-1
ros-humble-imu-sensor-broadcaster-dbgsym: 2.50.0-1 → 2.50.1-1
ros-humble-intra-process-demo: 0.20.5-1 → 0.20.6-1
ros-humble-intra-process-demo-dbgsym: 0.20.5-1 → 0.20.6-1
ros-humble-joint-group-impedance-controller: 0.9.2-1 → 1.0.0-1
ros-humble-joint-group-impedance-controller-dbgsym: 0.9.2-1 → 1.0.0-1
ros-humble-joint-state-broadcaster: 2.50.0-1 → 2.50.1-1
ros-humble-joint-state-broadcaster-dbgsym: 2.50.0-1 → 2.50.1-1
ros-humble-joint-trajectory-controller: 2.50.0-1 → 2.50.1-1
ros-humble-joint-trajectory-controller-dbgsym: 2.50.0-1 → 2.50.1-1
ros-humble-kinematics-interface: 0.4.0-1 → 0.4.1-1
ros-humble-kinematics-interface-dbgsym: 0.4.0-1 → 0.4.1-1
ros-humble-kinematics-interface-kdl: 0.4.0-1 → 0.4.1-1
ros-humble-kinematics-interface-kdl-dbgsym: 0.4.0-1 → 0.4.1-1
ros-humble-kitti-metrics-eval: 1.9.0-1 → 2.0.0-1
ros-humble-kitti-metrics-eval-dbgsym: 1.9.0-1 → 2.0.0-1
ros-humble-kompass: 0.3.1-1 → 0.3.2-1
ros-humble-kompass-interfaces: 0.3.1-1 → 0.3.2-1
ros-humble-kompass-interfaces-dbgsym: 0.3.1-1 → 0.3.2-1
ros-humble-kuka-control-mode-handler: 0.9.2-1 → 1.0.0-1
ros-humble-kuka-control-mode-handler-dbgsym: 0.9.2-1 → 1.0.0-1
ros-humble-kuka-controllers: 0.9.2-1 → 1.0.0-1
ros-humble-kuka-driver-interfaces: 0.9.2-1 → 1.0.0-1
ros-humble-kuka-driver-interfaces-dbgsym: 0.9.2-1 → 1.0.0-1
ros-humble-kuka-drivers: 0.9.2-1 → 1.0.0-1
ros-humble-kuka-drivers-core: 0.9.2-1 → 1.0.0-1
ros-humble-kuka-drivers-core-dbgsym: 0.9.2-1 → 1.0.0-1
ros-humble-kuka-event-broadcaster: 0.9.2-1 → 1.0.0-1
ros-humble-kuka-event-broadcaster-dbgsym: 0.9.2-1 → 1.0.0-1
ros-humble-kuka-iiqka-eac-driver: 0.9.2-1 → 1.0.0-1
ros-humble-kuka-iiqka-eac-driver-dbgsym: 0.9.2-1 → 1.0.0-1
ros-humble-kuka-rsi-simulator: 0.9.2-1 → 1.0.0-1
ros-humble-kuka-sunrise-fri-driver: 0.9.2-1 → 1.0.0-1
ros-humble-kuka-sunrise-fri-driver-dbgsym: 0.9.2-1 → 1.0.0-1
ros-humble-laser-geometry: 2.4.0-2 → 2.4.1-1
ros-humble-laser-geometry-dbgsym: 2.4.0-2 → 2.4.1-1
ros-humble-launch: 1.0.10-1 → 1.0.11-1
ros-humble-launch-pytest: 1.0.10-1 → 1.0.11-1
ros-humble-launch-testing: 1.0.10-1 → 1.0.11-1
ros-humble-launch-testing-ament-cmake: 1.0.10-1 → 1.0.11-1
ros-humble-launch-xml: 1.0.10-1 → 1.0.11-1
ros-humble-launch-yaml: 1.0.10-1 → 1.0.11-1
ros-humble-lifecycle: 0.20.5-1 → 0.20.6-1
ros-humble-lifecycle-dbgsym: 0.20.5-1 → 0.20.6-1
ros-humble-lifecycle-py: 0.20.5-1 → 0.20.6-1
ros-humble-logging-demo: 0.20.5-1 → 0.20.6-1
ros-humble-logging-demo-dbgsym: 0.20.5-1 → 0.20.6-1
ros-humble-mecanum-drive-controller: 2.50.0-1 → 2.50.1-1
ros-humble-mecanum-drive-controller-dbgsym: 2.50.0-1 → 2.50.1-1
ros-humble-message-filters: 4.3.8-1 → 4.3.11-1
ros-humble-message-filters-dbgsym: 4.3.8-1 → 4.3.11-1
ros-humble-mola: 1.9.0-1 → 2.0.0-1
ros-humble-mola-bridge-ros2: 1.9.0-1 → 2.0.0-1
ros-humble-mola-bridge-ros2-dbgsym: 1.9.0-1 → 2.0.0-1
ros-humble-mola-demos: 1.9.0-1 → 2.0.0-1
ros-humble-mola-imu-preintegration: 1.10.0-1 → 1.13.1-1
ros-humble-mola-imu-preintegration-dbgsym: 1.10.0-1 → 1.13.1-1
ros-humble-mola-input-euroc-dataset: 1.9.0-1 → 2.0.0-1
ros-humble-mola-input-euroc-dataset-dbgsym: 1.9.0-1 → 2.0.0-1
ros-humble-mola-input-kitti-dataset: 1.9.0-1 → 2.0.0-1
ros-humble-mola-input-kitti-dataset-dbgsym: 1.9.0-1 → 2.0.0-1
ros-humble-mola-input-kitti360-dataset: 1.9.0-1 → 2.0.0-1
ros-humble-mola-input-kitti360-dataset-dbgsym: 1.9.0-1 → 2.0.0-1
ros-humble-mola-input-mulran-dataset: 1.9.0-1 → 2.0.0-1
ros-humble-mola-input-mulran-dataset-dbgsym: 1.9.0-1 → 2.0.0-1
ros-humble-mola-input-paris-luco-dataset: 1.9.0-1 → 2.0.0-1
ros-humble-mola-input-paris-luco-dataset-dbgsym: 1.9.0-1 → 2.0.0-1
ros-humble-mola-input-rawlog: 1.9.0-1 → 2.0.0-1
ros-humble-mola-input-rawlog-dbgsym: 1.9.0-1 → 2.0.0-1
ros-humble-mola-input-rosbag2: 1.9.0-1 → 2.0.0-1
ros-humble-mola-input-rosbag2-dbgsym: 1.9.0-1 → 2.0.0-1
ros-humble-mola-input-video: 1.9.0-1 → 2.0.0-1
ros-humble-mola-input-video-dbgsym: 1.9.0-1 → 2.0.0-1
ros-humble-mola-kernel: 1.9.0-1 → 2.0.0-1
ros-humble-mola-kernel-dbgsym: 1.9.0-1 → 2.0.0-1
ros-humble-mola-launcher: 1.9.0-1 → 2.0.0-1
ros-humble-mola-launcher-dbgsym: 1.9.0-1 → 2.0.0-1
ros-humble-mola-lidar-odometry: 0.9.0-1 → 1.0.0-1
ros-humble-mola-lidar-odometry-dbgsym: 0.9.0-1 → 1.0.0-1
ros-humble-mola-metric-maps: 1.9.0-1 → 2.0.0-1
ros-humble-mola-metric-maps-dbgsym: 1.9.0-1 → 2.0.0-1
ros-humble-mola-msgs: 1.9.0-1 → 2.0.0-1
ros-humble-mola-msgs-dbgsym: 1.9.0-1 → 2.0.0-1
ros-humble-mola-pose-list: 1.9.0-1 → 2.0.0-1
ros-humble-mola-pose-list-dbgsym: 1.9.0-1 → 2.0.0-1
ros-humble-mola-relocalization: 1.9.0-1 → 2.0.0-1
ros-humble-mola-relocalization-dbgsym: 1.9.0-1 → 2.0.0-1
ros-humble-mola-state-estimation: 1.10.0-1 → 1.11.0-1
ros-humble-mola-state-estimation-simple: 1.10.0-1 → 1.11.0-1
ros-humble-mola-state-estimation-simple-dbgsym: 1.10.0-1 → 1.11.0-1
ros-humble-mola-state-estimation-smoother: 1.10.0-1 → 1.11.0-1
ros-humble-mola-state-estimation-smoother-dbgsym: 1.10.0-1 → 1.11.0-1
ros-humble-mola-traj-tools: 1.9.0-1 → 2.0.0-1
ros-humble-mola-traj-tools-dbgsym: 1.9.0-1 → 2.0.0-1
ros-humble-mola-viz: 1.9.0-1 → 2.0.0-1
ros-humble-mola-viz-dbgsym: 1.9.0-1 → 2.0.0-1
ros-humble-mola-yaml: 1.9.0-1 → 2.0.0-1
ros-humble-mola-yaml-dbgsym: 1.9.0-1 → 2.0.0-1
ros-humble-mp2p-icp: 1.8.0-1 → 2.0.0-1
ros-humble-mp2p-icp-dbgsym: 1.8.0-1 → 2.0.0-1
ros-humble-mqtt-client: 2.4.1-1 → 2.4.1-2
ros-humble-mqtt-client-dbgsym: 2.4.1-1 → 2.4.1-2
ros-humble-mqtt-client-interfaces: 2.4.1-1 → 2.4.1-2
ros-humble-mqtt-client-interfaces-dbgsym: 2.4.1-1 → 2.4.1-2
ros-humble-mrpt-apps: 2.14.12-1 → 2.14.16-1
ros-humble-mrpt-apps-dbgsym: 2.14.12-1 → 2.14.16-1
ros-humble-mrpt-libapps: 2.14.12-1 → 2.14.16-1
ros-humble-mrpt-libapps-dbgsym: 2.14.12-1 → 2.14.16-1
ros-humble-mrpt-libbase: 2.14.12-1 → 2.14.16-1
ros-humble-mrpt-libbase-dbgsym: 2.14.12-1 → 2.14.16-1
ros-humble-mrpt-libgui: 2.14.12-1 → 2.14.16-1
ros-humble-mrpt-libgui-dbgsym: 2.14.12-1 → 2.14.16-1
ros-humble-mrpt-libhwdrivers: 2.14.12-1 → 2.14.16-1
ros-humble-mrpt-libhwdrivers-dbgsym: 2.14.12-1 → 2.14.16-1
ros-humble-mrpt-libmaps: 2.14.12-1 → 2.14.16-1
ros-humble-mrpt-libmaps-dbgsym: 2.14.12-1 → 2.14.16-1
ros-humble-mrpt-libmath: 2.14.12-1 → 2.14.16-1
ros-humble-mrpt-libmath-dbgsym: 2.14.12-1 → 2.14.16-1
ros-humble-mrpt-libnav: 2.14.12-1 → 2.14.16-1
ros-humble-mrpt-libnav-dbgsym: 2.14.12-1 → 2.14.16-1
ros-humble-mrpt-libobs: 2.14.12-1 → 2.14.16-1
ros-humble-mrpt-libobs-dbgsym: 2.14.12-1 → 2.14.16-1
ros-humble-mrpt-libopengl: 2.14.12-1 → 2.14.16-1
ros-humble-mrpt-libopengl-dbgsym: 2.14.12-1 → 2.14.16-1
ros-humble-mrpt-libposes: 2.14.12-1 → 2.14.16-1
ros-humble-mrpt-libposes-dbgsym: 2.14.12-1 → 2.14.16-1
ros-humble-mrpt-libros-bridge: 2.14.12-1 → 2.14.16-1
ros-humble-mrpt-libros-bridge-dbgsym: 2.14.12-1 → 2.14.16-1
ros-humble-mrpt-libslam: 2.14.12-1 → 2.14.16-1
ros-humble-mrpt-libslam-dbgsym: 2.14.12-1 → 2.14.16-1
ros-humble-mrpt-libtclap: 2.14.12-1 → 2.14.16-1
ros-humble-namosim: 0.0.3-1 → 0.0.4-2
ros-humble-nav-2d-msgs: 1.1.18-1 → 1.1.19-1
ros-humble-nav-2d-msgs-dbgsym: 1.1.18-1 → 1.1.19-1
ros-humble-nav-2d-utils: 1.1.18-1 → 1.1.19-1
ros-humble-nav-2d-utils-dbgsym: 1.1.18-1 → 1.1.19-1
ros-humble-nav2-amcl: 1.1.18-1 → 1.1.19-1
ros-humble-nav2-amcl-dbgsym: 1.1.18-1 → 1.1.19-1
ros-humble-nav2-behavior-tree: 1.1.18-1 → 1.1.19-1
ros-humble-nav2-behavior-tree-dbgsym: 1.1.18-1 → 1.1.19-1
ros-humble-nav2-behaviors: 1.1.18-1 → 1.1.19-1
ros-humble-nav2-behaviors-dbgsym: 1.1.18-1 → 1.1.19-1
ros-humble-nav2-bringup: 1.1.18-1 → 1.1.19-1
ros-humble-nav2-bt-navigator: 1.1.18-1 → 1.1.19-1
ros-humble-nav2-bt-navigator-dbgsym: 1.1.18-1 → 1.1.19-1
ros-humble-nav2-collision-monitor: 1.1.18-1 → 1.1.19-1
ros-humble-nav2-collision-monitor-dbgsym: 1.1.18-1 → 1.1.19-1
ros-humble-nav2-common: 1.1.18-1 → 1.1.19-1
ros-humble-nav2-constrained-smoother: 1.1.18-1 → 1.1.19-1
ros-humble-nav2-constrained-smoother-dbgsym: 1.1.18-1 → 1.1.19-1
ros-humble-nav2-controller: 1.1.18-1 → 1.1.19-1
ros-humble-nav2-controller-dbgsym: 1.1.18-1 → 1.1.19-1
ros-humble-nav2-core: 1.1.18-1 → 1.1.19-1
ros-humble-nav2-costmap-2d: 1.1.18-1 → 1.1.19-1
ros-humble-nav2-costmap-2d-dbgsym: 1.1.18-1 → 1.1.19-1
ros-humble-nav2-dwb-controller: 1.1.18-1 → 1.1.19-1
ros-humble-nav2-graceful-controller: 1.1.18-1 → 1.1.19-1
ros-humble-nav2-graceful-controller-dbgsym: 1.1.18-1 → 1.1.19-1
ros-humble-nav2-lifecycle-manager: 1.1.18-1 → 1.1.19-1
ros-humble-nav2-lifecycle-manager-dbgsym: 1.1.18-1 → 1.1.19-1
ros-humble-nav2-map-server: 1.1.18-1 → 1.1.19-1
ros-humble-nav2-map-server-dbgsym: 1.1.18-1 → 1.1.19-1
ros-humble-nav2-mppi-controller: 1.1.18-1 → 1.1.19-1
ros-humble-nav2-mppi-controller-dbgsym: 1.1.18-1 → 1.1.19-1
ros-humble-nav2-msgs: 1.1.18-1 → 1.1.19-1
ros-humble-nav2-msgs-dbgsym: 1.1.18-1 → 1.1.19-1
ros-humble-nav2-navfn-planner: 1.1.18-1 → 1.1.19-1
ros-humble-nav2-navfn-planner-dbgsym: 1.1.18-1 → 1.1.19-1
ros-humble-nav2-planner: 1.1.18-1 → 1.1.19-1
ros-humble-nav2-planner-dbgsym: 1.1.18-1 → 1.1.19-1
ros-humble-nav2-regulated-pure-pursuit-controller: 1.1.18-1 → 1.1.19-1
ros-humble-nav2-regulated-pure-pursuit-controller-dbgsym: 1.1.18-1 → 1.1.19-1
ros-humble-nav2-rotation-shim-controller: 1.1.18-1 → 1.1.19-1
ros-humble-nav2-rotation-shim-controller-dbgsym: 1.1.18-1 → 1.1.19-1
ros-humble-nav2-rviz-plugins: 1.1.18-1 → 1.1.19-1
ros-humble-nav2-rviz-plugins-dbgsym: 1.1.18-1 → 1.1.19-1
ros-humble-nav2-simple-commander: 1.1.18-1 → 1.1.19-1
ros-humble-nav2-smac-planner: 1.1.18-1 → 1.1.19-1
ros-humble-nav2-smac-planner-dbgsym: 1.1.18-1 → 1.1.19-1
ros-humble-nav2-smoother: 1.1.18-1 → 1.1.19-1
ros-humble-nav2-smoother-dbgsym: 1.1.18-1 → 1.1.19-1
ros-humble-nav2-system-tests: 1.1.18-1 → 1.1.19-1
ros-humble-nav2-system-tests-dbgsym: 1.1.18-1 → 1.1.19-1
ros-humble-nav2-theta-star-planner: 1.1.18-1 → 1.1.19-1
ros-humble-nav2-theta-star-planner-dbgsym: 1.1.18-1 → 1.1.19-1
ros-humble-nav2-util: 1.1.18-1 → 1.1.19-1
ros-humble-nav2-util-dbgsym: 1.1.18-1 → 1.1.19-1
ros-humble-nav2-velocity-smoother: 1.1.18-1 → 1.1.19-1
ros-humble-nav2-velocity-smoother-dbgsym: 1.1.18-1 → 1.1.19-1
ros-humble-nav2-voxel-grid: 1.1.18-1 → 1.1.19-1
ros-humble-nav2-voxel-grid-dbgsym: 1.1.18-1 → 1.1.19-1
ros-humble-nav2-waypoint-follower: 1.1.18-1 → 1.1.19-1
ros-humble-nav2-waypoint-follower-dbgsym: 1.1.18-1 → 1.1.19-1
ros-humble-navigation2: 1.1.18-1 → 1.1.19-1
ros-humble-novatel-oem7-driver: 20.7.0-1 → 20.8.0-1
ros-humble-novatel-oem7-driver-dbgsym: 20.7.0-1 → 20.8.0-1
ros-humble-novatel-oem7-msgs: 20.7.0-1 → 20.8.0-1
ros-humble-novatel-oem7-msgs-dbgsym: 20.7.0-1 → 20.8.0-1
ros-humble-pal-gazebo-plugins: 4.0.6-1 → 4.1.0-1
ros-humble-pal-gazebo-plugins-dbgsym: 4.0.6-1 → 4.1.0-1
ros-humble-pal-statistics: 2.6.4-1 → 2.7.0-1
ros-humble-pal-statistics-dbgsym: 2.6.4-1 → 2.7.0-1
ros-humble-pal-statistics-msgs: 2.6.4-1 → 2.7.0-1
ros-humble-pal-statistics-msgs-dbgsym: 2.6.4-1 → 2.7.0-1
ros-humble-pendulum-control: 0.20.5-1 → 0.20.6-1
ros-humble-pendulum-control-dbgsym: 0.20.5-1 → 0.20.6-1
ros-humble-pendulum-msgs: 0.20.5-1 → 0.20.6-1
ros-humble-pendulum-msgs-dbgsym: 0.20.5-1 → 0.20.6-1
ros-humble-pid-controller: 2.50.0-1 → 2.50.1-1
ros-humble-pid-controller-dbgsym: 2.50.0-1 → 2.50.1-1
ros-humble-pinocchio: 3.6.0-1 → 3.8.0-1
ros-humble-pinocchio-dbgsym: 3.6.0-1 → 3.8.0-1
ros-humble-play-motion2: 1.5.3-1 → 1.7.0-1
ros-humble-play-motion2-dbgsym: 1.5.3-1 → 1.7.0-1
ros-humble-play-motion2-msgs: 1.5.3-1 → 1.7.0-1
ros-humble-play-motion2-msgs-dbgsym: 1.5.3-1 → 1.7.0-1
ros-humble-plotjuggler: 3.10.11-1 → 3.13.2-1
ros-humble-plotjuggler-dbgsym: 3.10.11-1 → 3.13.2-1
ros-humble-pluginlib: 5.1.0-3 → 5.1.2-1
ros-humble-point-cloud-interfaces: 1.0.11-1 → 1.0.12-1
ros-humble-point-cloud-interfaces-dbgsym: 1.0.11-1 → 1.0.12-1
ros-humble-point-cloud-transport: 1.0.18-1 → 1.0.19-1
ros-humble-point-cloud-transport-dbgsym: 1.0.18-1 → 1.0.19-1
ros-humble-point-cloud-transport-plugins: 1.0.11-1 → 1.0.12-1
ros-humble-point-cloud-transport-py: 1.0.18-1 → 1.0.19-1
ros-humble-pose-broadcaster: 2.50.0-1 → 2.50.1-1
ros-humble-pose-broadcaster-dbgsym: 2.50.0-1 → 2.50.1-1
ros-humble-position-controllers: 2.50.0-1 → 2.50.1-1
ros-humble-position-controllers-dbgsym: 2.50.0-1 → 2.50.1-1
ros-humble-python-qt-binding: 1.1.2-1 → 1.1.3-1
ros-humble-quality-of-service-demo-cpp: 0.20.5-1 → 0.20.6-1
ros-humble-quality-of-service-demo-cpp-dbgsym: 0.20.5-1 → 0.20.6-1
ros-humble-quality-of-service-demo-py: 0.20.5-1 → 0.20.6-1
ros-humble-range-sensor-broadcaster: 2.50.0-1 → 2.50.1-1
ros-humble-range-sensor-broadcaster-dbgsym: 2.50.0-1 → 2.50.1-1
ros-humble-rcpputils: 2.4.5-1 → 2.4.6-1
ros-humble-rcpputils-dbgsym: 2.4.5-1 → 2.4.6-1
ros-humble-realtime-tools: 2.14.0-1 → 2.14.1-1
ros-humble-realtime-tools-dbgsym: 2.14.0-1 → 2.14.1-1
ros-humble-rmw-fastrtps-cpp: 6.2.8-1 → 6.2.9-1
ros-humble-rmw-fastrtps-cpp-dbgsym: 6.2.8-1 → 6.2.9-1
ros-humble-rmw-fastrtps-dynamic-cpp: 6.2.8-1 → 6.2.9-1
ros-humble-rmw-fastrtps-dynamic-cpp-dbgsym: 6.2.8-1 → 6.2.9-1
ros-humble-rmw-fastrtps-shared-cpp: 6.2.8-1 → 6.2.9-1
ros-humble-rmw-fastrtps-shared-cpp-dbgsym: 6.2.8-1 → 6.2.9-1
ros-humble-rmw-zenoh-cpp: 0.1.6-1 → 0.1.7-1
ros-humble-rmw-zenoh-cpp-dbgsym: 0.1.6-1 → 0.1.7-1
ros-humble-ros2-controllers: 2.50.0-1 → 2.50.1-1
ros-humble-ros2-controllers-test-nodes: 2.50.0-1 → 2.50.1-1
ros-humble-rosidl-generator-py: 0.14.5-1 → 0.14.6-1
ros-humble-rosidl-typesupport-fastrtps-c: 2.2.2-2 → 2.2.3-1
ros-humble-rosidl-typesupport-fastrtps-c-dbgsym: 2.2.2-2 → 2.2.3-1
ros-humble-rosidl-typesupport-fastrtps-cpp: 2.2.2-2 → 2.2.3-1
ros-humble-rosidl-typesupport-fastrtps-cpp-dbgsym: 2.2.2-2 → 2.2.3-1
ros-humble-rpyutils: 0.2.1-2 → 0.2.2-1
ros-humble-rqt: 1.1.7-1 → 1.1.8-1
ros-humble-rqt-gui: 1.1.7-1 → 1.1.8-1
ros-humble-rqt-gui-cpp: 1.1.7-1 → 1.1.8-1
ros-humble-rqt-gui-cpp-dbgsym: 1.1.7-1 → 1.1.8-1
ros-humble-rqt-gui-py: 1.1.7-1 → 1.1.8-1
ros-humble-rqt-joint-trajectory-controller: 2.50.0-1 → 2.50.1-1
ros-humble-rqt-py-common: 1.1.7-1 → 1.1.8-1
ros-humble-rviz-assimp-vendor: 11.2.20-1 → 11.2.22-1
ros-humble-rviz-common: 11.2.20-1 → 11.2.22-1
ros-humble-rviz-common-dbgsym: 11.2.20-1 → 11.2.22-1
ros-humble-rviz-default-plugins: 11.2.20-1 → 11.2.22-1
ros-humble-rviz-default-plugins-dbgsym: 11.2.20-1 → 11.2.22-1
ros-humble-rviz-ogre-vendor: 11.2.20-1 → 11.2.22-1
ros-humble-rviz-ogre-vendor-dbgsym: 11.2.20-1 → 11.2.22-1
ros-humble-rviz-rendering: 11.2.20-1 → 11.2.22-1
ros-humble-rviz-rendering-dbgsym: 11.2.20-1 → 11.2.22-1
ros-humble-rviz-rendering-tests: 11.2.20-1 → 11.2.22-1
ros-humble-rviz-visual-testing-framework: 11.2.20-1 → 11.2.22-1
ros-humble-rviz2: 11.2.20-1 → 11.2.22-1
ros-humble-rviz2-dbgsym: 11.2.20-1 → 11.2.22-1
ros-humble-steering-controllers-library: 2.50.0-1 → 2.50.1-1
ros-humble-steering-controllers-library-dbgsym: 2.50.0-1 → 2.50.1-1
ros-humble-tecgihan-driver: 0.1.1-1 → 0.1.2-1
ros-humble-teleop-twist-keyboard: 2.4.0-1 → 2.4.1-1
ros-humble-topic-monitor: 0.20.5-1 → 0.20.6-1
ros-humble-topic-statistics-demo: 0.20.5-1 → 0.20.6-1
ros-humble-topic-statistics-demo-dbgsym: 0.20.5-1 → 0.20.6-1
ros-humble-tricycle-controller: 2.50.0-1 → 2.50.1-1
ros-humble-tricycle-controller-dbgsym: 2.50.0-1 → 2.50.1-1
ros-humble-tricycle-steering-controller: 2.50.0-1 → 2.50.1-1
ros-humble-tricycle-steering-controller-dbgsym: 2.50.0-1 → 2.50.1-1
ros-humble-tsid: 1.8.0-1 → 1.9.0-1
ros-humble-tsid-dbgsym: 1.8.0-1 → 1.9.0-1
ros-humble-turtle-nest: 1.2.0-1 → 1.2.1-1
ros-humble-turtle-nest-dbgsym: 1.2.0-1 → 1.2.1-1
ros-humble-turtlesim: 1.4.2-1 → 1.4.3-1
ros-humble-turtlesim-dbgsym: 1.4.2-1 → 1.4.3-1
ros-humble-ur: 2.8.1-1 → 2.9.0-1
ros-humble-ur-bringup: 2.8.1-1 → 2.9.0-1
ros-humble-ur-calibration: 2.8.1-1 → 2.9.0-1
ros-humble-ur-calibration-dbgsym: 2.8.1-1 → 2.9.0-1
ros-humble-ur-client-library: 2.3.0-1 → 2.4.0-1
ros-humble-ur-client-library-dbgsym: 2.3.0-1 → 2.4.0-1
ros-humble-ur-controllers: 2.8.1-1 → 2.9.0-1
ros-humble-ur-controllers-dbgsym: 2.8.1-1 → 2.9.0-1
ros-humble-ur-dashboard-msgs: 2.8.1-1 → 2.9.0-1
ros-humble-ur-dashboard-msgs-dbgsym: 2.8.1-1 → 2.9.0-1
ros-humble-ur-description: 2.7.0-1 → 2.8.0-1
ros-humble-ur-moveit-config: 2.8.1-1 → 2.9.0-1
ros-humble-ur-robot-driver: 2.8.1-1 → 2.9.0-1
ros-humble-ur-robot-driver-dbgsym: 2.8.1-1 → 2.9.0-1
ros-humble-ur-simulation-gz: 0.3.0-1 → 0.5.0-1
ros-humble-velocity-controllers: 2.50.0-1 → 2.50.1-1
ros-humble-velocity-controllers-dbgsym: 2.50.0-1 → 2.50.1-1
ros-humble-yasmin: 3.4.0-1 → 3.5.0-1
ros-humble-yasmin-dbgsym: 3.4.0-1 → 3.5.0-1
ros-humble-yasmin-demos: 3.4.0-1 → 3.5.0-1
ros-humble-yasmin-demos-dbgsym: 3.4.0-1 → 3.5.0-1
ros-humble-yasmin-msgs: 3.4.0-1 → 3.5.0-1
ros-humble-yasmin-msgs-dbgsym: 3.4.0-1 → 3.5.0-1
ros-humble-yasmin-ros: 3.4.0-1 → 3.5.0-1
ros-humble-yasmin-ros-dbgsym: 3.4.0-1 → 3.5.0-1
ros-humble-yasmin-viewer: 3.4.0-1 → 3.5.0-1
ros-humble-yasmin-viewer-dbgsym: 3.4.0-1 → 3.5.0-1
ros-humble-zed-msgs: 5.0.1-2 → 5.1.0-1
ros-humble-zed-msgs-dbgsym: 5.0.1-2 → 5.1.0-1
ros-humble-zenoh-cpp-vendor: 0.1.6-1 → 0.1.7-1
ros-humble-zenoh-cpp-vendor-dbgsym: 0.1.6-1 → 0.1.7-1
ros-humble-zenoh-security-tools: 0.1.6-1 → 0.1.7-1
ros-humble-zenoh-security-tools-dbgsym: 0.1.6-1 → 0.1.7-1
ros-humble-zlib-point-cloud-transport: 1.0.11-1 → 1.0.12-1
ros-humble-zlib-point-cloud-transport-dbgsym: 1.0.11-1 → 1.0.12-1
ros-humble-zstd-point-cloud-transport: 1.0.11-1 → 1.0.12-1
ros-humble-zstd-point-cloud-transport-dbgsym: 1.0.11-1 → 1.0.12-1

Removed Packages [2]:

ros-humble-kuka-kss-rsi-driver
ros-humble-kuka-kss-rsi-driver-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:

Aditya Pande
Aina Irisarri
Alberto Tudela
Alejandro Hernandez Cordero
Alexey Merzlyakov
Andrej Orsula
Aron Svastits
Audrow Nash
Automatika Robotics
Bence Magyar
Brian Wilcox
Carl Delsey
Carlos Orduno
Chris Bollinger
Chris Lalancette
David Brown
David V. Lu!!
David ter Kuile
Davide Faconti
Denis Štogl
Dorian Scholz
Emerson Knapp
Ethan Gao
Felix Exner
Foxglove
Guilhem Saurel
Jacob Perron
Janne Karttunen
Jean-Pierre Busch
Jeremie Deray
Joe Dong
Jordan Palacios
Jose Luis Blanco-Claraco
Joseph Mirabel
Justin Carpentier
Kristof Matyas Pasztor
Lennart Reiher
Luis Camero
Mabel Zhang
Martin Pecka
Matej Vargovcik
Meher Malladi
Michael Goerner
Michael Jeronimo
Michael v4hn Goerner
Michel Hidalgo
Miguel Ángel González Santamarta
Mohammad Haghighipanah
Noel Jimenez
NovAtel Support
Oscar Martinez
Pyo
Robert Haschke
STEREOLABS
Shane Loretz
Shigeru Wakida
Steve Macenski
Tim Clephas
Vimarsh Shah
Yadunund
davidfernandez
miguel
ouster developers
steve
toosimple
user

1 post - 1 participant

Read full topic

https://discourse.openrobotics.org/t/new-packages-for-humble-hawksbill-2025-10-20/50628

ROS Discourse General: RclGo v0.4.1 Release

rclgo v0.4.1 Released - ROS 2 Filesystem Logging & CLI Parameter Overrides

I’m excited to announce rclgo v0.4.1, a Go client library for ROS 2 Humble! This release brings two critical features for production robotics deployments.

What’s New

ROS 2 Filesystem Logging

rclgo nodes now properly write logs to ~/.ros/log/ with full ROS 2 formatting, matching rclcpp/rclpy behavior:

Logs automatically written to ~/.ros/log/<node_name>.log
Compatible with ROS 2 logging infrastructure (spdlog backend)
Works seamlessly with ros2 launch and standalone execution

CLI Parameter Overrides

Full support for command-line parameter overrides, a critical feature for dynamic configuration:
ros2 run my_package my_node --ros-args -p camera.fps:=60 -p exposure:=0.05

Compatible with launch file LaunchConfiguration substitutions
Updates existing declared parameters or declares new ones
Supports all ROS 2 parameter types (bool, int64, double, string, arrays)

Why rclgo?

rclgo enables writing ROS 2 nodes in Go, bringing:

Performance: Native compiled binaries, efficient concurrency with goroutines
Simplicity: Clean, idiomatic Go APIs for ROS 2 concepts
Production-ready: Growing feature parity with rclcpp/rclpy

Current Feature Support

Publisher/Subscriber:white_check_mark: Services:white_check_mark: Parameters (declare, get, set, YAML, CLI overrides) QoS Policies:white_check_mark: ROS Time & /use_sim_time:white_check_mark: Named loggers with filesystem output

Coming soon: Actions, Lifecycle nodes, Multi-threaded executor

Installation

go get github.com/merlindrones/rclgo@v0.4.1

Full documentation and examples: GitHub - MerlinDrones/rclgo: Go bindings for ROS2. Forked from https://github.com/tiiuae/rclgo

Feedback Welcome

This project targets ROS 2 Humble and aims for production-grade parity with rclcpp/rclpy. Feedback, bug reports, and contributions are very welcome!

1 post - 1 participant

Read full topic

https://discourse.openrobotics.org/t/rclgo-v0-4-1-release/50619

ROS 2 Documentation

Wiki

Page

User

Planet ROS

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

ROS Discourse General: Recursive Fiducial Marker

ROS Discourse General: ROSGraph Working Group kickoff

ROS Discourse General: ROS Asia Pacific Developer Meeting #1 7th.Nov

ROS Discourse General: FOSDEM 2026: Robotics & Simulation Devroom, 2nd edition!

ROS Discourse General: NAV2 demonstration on a real robot

ROS Discourse General: New ROS 2 Features for Mini Pupper 2

New ROS 2 Features - Mini Pupper 2

Vision-Based Tracking

Multi-Robot Fleet Coordination

Navigation and SLAM

ROS Discourse General: [First Release] Asyncio For Robotics: Asyncio interface for ROS 2

VVV About the project VVV

Why asyncio?

Other solutions

How asyncio_for_robotics works? What’s different?

ROS Discourse General: Cloud Robotics WG Meeting 2025-11-05

ROS Discourse General: Free ROSCon 2025 Live Stream

ROSCon 2025 Live Stream is up!

ROS Discourse General: Announcement: rclrs 0.6.0 Release

ROS Discourse General: Introducing `colcon_gephi` – Generate Rich Dependency Graphs Compatible With Graph Visualization Tools

Introducing: colcon_gephi

Features

Usage

Notes

Graph Visualization Tools

Example Graph Details

ROS Discourse General: Looking for a mentor to guide me in real-world ROS 2 applications — interested in embedded robotics and simulation.

ROS Discourse General: RKO-LIO: LiDAR-Inertial Odometry

ROS Discourse General: Questions to intrinsic and extrinsic calibration. Any help?

ROS Discourse General: Blog post: Reproducible cross-platform ROS installation with Pixi

ROS Discourse General: Introducing: `ros2_fmt_logger`

Introducing:

ros2_fmt_logger

Features

Examples

Once-only logging

Throttled logging

Change-based logging

Format String Syntax

NAQ

ROS Discourse General: Gamepad Teleoperation for Robotic Arm—A New Intuitive Control Experience

Overview

Environment Setup

Quick Start

Gamepad Control Mapping

Button Functions

Joysticks & Triggers

Additional Features

Safety Warnings

Contributing & Feedback

ROS Discourse General: Announcing rosetta: a ROS 2 ⇄ LeRobot bridge

Announcing rosetta: a ROS 2 ⇄ LeRobot bridge

What’s inside

A simple example to start

What’s next

I’d love feedback

ROS Discourse General: Extending meta-ros with ros2 + openembedded (yocto)

ROS Discourse General: Announcing GitHub syntax highlighting for ROS msg files

ROS Discourse General: Come Join Me At ROSCon 2025 in Singapore

ROS Discourse General: ManyMove v0.2.0 - Setup with Docker container and unified main branch

ROS Discourse General: Join My Workshop at ROSCon Singapore

ROS Discourse General: New packages for Humble Hawksbill 2025-10-20

Package Updates for humble

Added Packages [61]:

Updated Packages [475]:

Removed Packages [2]:

ROS Discourse General: RclGo v0.4.1 Release

How `asyncio_for_robotics` works? What’s different?