Planet ROS · 实时热榜

The next meeting of the CRWG will be at Mon, Oct 19, 2026 4:00 PM UTC → Mon, Oct 19, 2026 5:00 PM UTC , where we will continue editing the first draft of the Logging and Observability guide. This will be very similar to the last meeting, except that the group hopes to finish the edit of the guide this meeting and send it to our prior guest speakers for review. 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 a

Hi everyone, We at eProsima are sharing a preview of the upcoming AI capabilities in DDS Monitor Pro, with a workflow that is also relevant to engineers working with DDS-based ROS 2 systems. The Monitor’s built-in Model Context Protocol (MCP) server connects an MCP-compatible AI assistant to the system information and operations available in the Monitor. You can ask questions about the running system and inspect the resulting entities, charts and operations in the workspace. The preview demons

Send a goal, follow the feedback, get the result. rclnodejs 2.3.0 , the ROS 2 client library for Node.js, brings ROS 2 actions to web apps over WebSocket and HTTP/SSE. ROS 2 Actions from the Browser The browser SDK derives TypeScript goal, feedback and result types from generated ROS declarations. OpenAPI export also includes action schemas. With an HTTP runtime on port 9001 exposing a running Fibonacci action server as /fibonacci : import { connect } from 'rclnodejs/web'; const ros = await conn

Quick heads-up for anyone maintaining hardware components or controllers on Rolling or Lyrical : ros2_control 6.12.0 removes the API that has been deprecated since Jazzy. It has been released into Lyrical and Rolling and will reach users with the next sync. We’ve patched most simulators and many public drivers already. If your package currently builds with deprecation warnings from hardware_interface or controller_interface , it will very likely fail to build after the sync. Jazzy and Kilted are

We’ve released an open-source ROS 2 bridge for the Rokoko Device SDK. It takes solved hand data from Smartgloves II and publishes it natively into ROS 2. What’s included: 26-joint hand poses per solved frame, in OpenXR XrHandJointEXT order. TF transforms , one per joint (opt-in). RViz visualization of the hand skeleton (opt-in). Per-hand diagnostics on /diagnostics , once a second. A calibrate service to set which direction is “forward”. One launch command starts the driver, hand solver and brid

Hi everyone, I’m Mattie Nejati, a Ph.D. candidate at the University of Waterloo. I’m recruiting participants for a user study on understanding the impact of changes to CMake build specifications . Since CMake is widely used in the ROS ecosystem, I thought developers in this community might be particularly interested in participating. We are evaluating a new approach that aims to help developers identify how a modification to a CMake build specification affects the resulting build configuration.

Hi everyone, I’m working on setting up a stereo camera PS5 HD Camera in ROS 2 Galactic for stereo depth estimation using stereo_image_proc ( DisparityNode ), with the end goal of feeding the depth data into RTAB-Map for 3D reconstruction. I transitioned from StereoBM to StereoSGBM ( stereo_algorithm: 1 ) to handle the wide-angle camera setup better, but I’m having trouble finding the optimal combination of parameters which result in a dense point cloud with smooth surfaces. My depth output keeps

It’s been a long time since I posted any news. Many new features and fixes have been released. Here is a list of some of them that have appeared in recent versions. Added RobotCAD MCP server for agentic robot assembling. Updated Models Library. More models (219 now) and faster import . Added xacro and mjcf models import from Models Library. Added sensors field of view with reacting to sensor parameters. Other features and fixes: Fixed an error in collision creation for objects obtained via a lin

I have been trying to work out how a hand eye calibration should be validated and I have not found any complete answer yet There are some tools I looked at (MoveIt Calibration, easy_handeye, Kalibr) that just print reprojection error or transform, but I could not find a clear way to decide from that whether the result can be trusted or not. I read some of their GitHub issues and many people seem to end up in the same place “result looks off” and the only way to find out why is to ask someone mor

I need a much better way of grabbing the current value of every parameter of every node running on my system. Not just the dynamic ones, but the defaults and overrides from the launch system. From an experiment documentation standpoint, this is extremely important to understanding exactly how things are configured when producing data and later if data is changing figuring if one of these changed. Sure some nodes may be less important and their parameters not matter much, but there would remain m

Hello ROS Community, I want to share a comprehensive step-by-step video tutorial on configuring MoveIt 2 from scratch for a custom robotic manipulator on ROS 2 Jazzy and Ubuntu 24.04 . While most official tutorials use high-DOF industrial manipulators (like the Franka Emika Panda), building configurations for smaller or custom arms often introduces unique glitches that standard guides don’t cover ( 0:33 ). In this video, I take a 3-joint printed arm model ( arduinobot ) with a gripper ( 0:17 )

TLDR: come work on NoDL in the rosgraph-wg . Join the mailing list for automatic calendar invites to meetings: https://groups.google.com/u/1/g/rosgraph-wg Hi everyone! @emersonknapp and I presented “The Legible Node” at ROSCon last week. We talked about two things: Thin nodes - your node is an interface adapter, it should not contain robot logic NoDL - the node definition language that allows you to statically declare your node interfaces If you didnt catch it, here are the slides (the_legible_n

Hey all! ECE undergrad here, exploring an inference-routing idea for robots (deciding at runtime whether a perception or higher-level AI task runs onboard, on a nearby edge server, or in the cloud, based on deadlines, network conditions, and local compute load) and trying to validate the problem before building anything. For those running real robots: is your local/remote split for perception or AI tasks fixed, or does it ever change dynamically? Has latency or local compute contention ever actu

Hi everyone, A small-but-important update for ros2_unbag Starting with v1.3.0 , ros2_unbag is now released through the official ROS 2 buildfarm. That means installation is now as simple as: sudo apt install ros-<distro>-unbag and then: ros2 unbag No separate pip install, no cloning, no building from source — just a regular ROS package. For anyone who hasn’t come across ros2_unbag yet: Your robot packs the bags; ros2_unbag brings them to your room, unpacks them, and sorts out the mess. No lost lu

Hi All those who joined the k8s/kubeedge with ROS 2 meetup at ROSCon Toronto, here is the thread that we follow up more information. please subscribe this thread so that you will not miss the notification. as we mentioned, let’s follow up more details about this topic after ROSCon. i will send the online meeting once i get back to Tokyo, probably in Oct we can have the follow up online meeting. thanks, Tomoya 5 posts - 3 participants Read full topic

Today we announced that PickNik Inc. and Qualcomm Technologies, Inc. are joining forces . Before I go into that, I want to talk about MoveIt, because MoveIt is the reason any of this happened. If you have learned about robotic arm manipulation in the past decade and a half, or been involved in manipulation R&D, there’s a good chance you’ve used MoveIt. More than 560 people have contributed code across the MoveIt project, which today spans 40 repositories, 6,700 GitHub stars, and 4,400 forks. The

We’re happy to announce the release of rclrs v0.8.0! Continuing our proud tradition of Conference-Driven Development (CDD), this release arrives just in time for ROSCon Global 2026 in Toronto . If you are at ROSCon, do not miss Michael Grey’s talk on composable actions concurrency with rclrs. What’s New ROS 2 Lyrical Support rclrs now supports ROS 2 Lyrical Luth. Bindings have been regenerated for Humble, Jazzy, Kilted, Lyrical, and Rolling. ros-env Message Access ROS message packages are now ac

ROSCon Global 2026 live from Toronto! Streams are both on the ROSCon website. Primary ROSCon 2026 Live Stream on Vimeo (Grand Ballroom West/Centre) Secondary ROSCon 2026 Live Stream on Vimeo (Grand Ballroom East) (starts after lunch) 3 posts - 1 participant Read full topic

Hi all, I’d like to share a research prototype that connects medical CT imaging to ROS 2 visualization and robot simulation . The pipeline starts from a DICOM / NIfTI CT scan, segments kidneys and nearby organs, finds stone candidates, builds 3D meshes, ranks PCNL (percutaneous nephrolithotomy) access corridors, then visualizes the anatomy in RViz and Gazebo . A Franka FR3 with a surgical needle can replay the selected path in simulation. This is not a clinical tool and not medical advice. It is

Lately I’ve been intermittently but often getting this message when trying to access ROS documentation (like c++ API etc). Am I the only one running into this? I definitely have browser cookies enabled, and I’m not going through a VPN. The below messages was obtained by browsing to this location . 14 posts - 7 participants Read full topic

Hi everyone! Here’s from the D-Robotics team. We’re excited to share that our team will be at ROSCon Global 2026 in Toronto, September 22–24 . We’re looking forward to meeting fellow ROS developers and robotics folks in person. For D-Robotics , ROS 2 is not an add-on — it is a core part of the RDK robotics development experience. Across the RDK platform, we support multiple ROS 2 distributions, while TogetheROS.Bot builds on ROS 2 with hardware-accelerated capabilities tailored for robotics. If

This demo uses the new SMACC PX4 Client Library to autonomously control the following drone in a Gazebo environment. SMACC and PX4 flight stack simulation in the Strait of Hormuz As always, here’s the source code: SMACC2/smacc2_sm_reference_library/sm_cl_px4_mr_test_4 at jazzy · robosoft-ai/SMACC2 · GitHub The readme for this application lays out the steps of how to use it. And here’s a link to the original linkedin post: #ros2 #px4 #smacc2 #physicalai #gazebo #qgroundcontrol #nav2 | Brett Aldri

Hi, I have been experimenting with native DDS for ROS 2 on Zephyr and recently got the standard ROS 2 C client stack running on an ESP32-S3 over Wi-Fi. The current stack is: rclc -> rcl -> rmw_cyclonedds_c -> Cyclone DDS -> Zephyr The board joins the DDS/RTPS network directly, without a Micro XRCE-DDS Agent. The work is split into two repositories: ros2_zephyr for the Zephyr integration and static ROS 2 build rmw_cyclonedds_c for the C RMW implementation and generated Cyclone DDS type support I

Ahead of ROSCon, anyone using ROS in a medical context is welcome to update the community here with a quick status update. I’ll go first on behalf of Vexev! Ps if you haven’t seen, there will be a Birds of a Feather session at ROSCon Toronto! 9am Tuesday. Followed by a community meeting online in October. Context: We use ROS in our 8dof ultrasound imaging robot. We’re a startup, pre regulatory submission. Full context in the 2024 ROSCon Keynote: Keynote: Saving lives sooner: leveraging ROS 2 for

The EU Cyber Resilience Act reporting obligation for manufacturers starts on 11 September 2026: early warning within 24 hours of becoming aware of an actively exploited vulnerability or severe incident, and full notification within 72 hours, through the ENISA Single Reporting Platform. Open-source stewards are covered from 11 December 2027 under Article 24(3). Source: Cyber Resilience Act - Reporting obligations | Shaping Europe’s digital future I am not posting this as a compliance warning. Mos