Planet ROS
Planet ROS - http://planet.ros.org
Planet ROS - http://planet.ros.org![[WWW]](/moin_static197/rostheme/img/moin-www.png "[WWW]"){kind=small}
http://planet.ros.org
ROS Discourse General: ROS News for the Week of November 4th, 2024
ROS News for the Week of November 4th, 2024
ROSCon 2024 is in the bag and most of the team is finally home! The videos should be up on the web soon (please don’t ask when, they’ll be up as soon as we can get them edited and uploaded).
In the meantime there are some great resources that came out of the event. Sebastian Castro put together a fantastic summary of the event. You can also check out @mjcarroll and @jennuine’s
r2s: Text User Interface (TUI) for ROS 2, this Zenoh + ROS 2 ROSCon Workshop, this demystifying ROS 2 networking workshop, and my intro to ROS 2 workshop
@Anis_Koubaa has put together a comprehensive survey on ROS 2.. They survey includes an amazing webpage that allows you to search through ROS papers that is worth bookmarking.
ROS By-The-Bay with Red Rabbit Robotics and @methyldragon is scheduled for next Thursday, November 14th in Mountain View. There are maybe ten RSVPs left.
Our friends at ROS Industrial had their annual European and Asian consortium meetings over the past two weeks. One of the big take aways is the new Mitsubishi MELFA ROS 2 driver. You can check out the source code here.
Space ROS Humble 2024.10.0 has been released!. I suggest you take a look at the Space ROS Demo repository’s pull requests. There is some really cool stuff in there!
Along those lines, check out ROSA being demonstrated for Neil deGrasse Tyson at JPL.
Events
- 2024-11-11 Arab ROS Meetup Workshop 4
- 2024-11-11 CFP for International Workshop on Robotics Software Engineering
- 2024-11-11
ROS 2 Rust November Meeting - 2024-11-12 Embodied AI Community Group
- 2024-11-14 ROS By-The-Bay wsg Red Rabbit Robotic and @methyldragon
- CoRL Workshop on Lifelong Learning in Home Robotics
- 2024-11-22 F1Tenth Learning to Trust Autonomy Workshop at BU
- 2024-12-03 ROSCon Germany
- 2024-12-05 ROSCon India
- 2024-12-07 → 2024-12-08 ROSCon China in Shenzhen
- 2024-12-11 =>2024-12-12 Humanoids Summit Bay Area
- 2024-12-16 => 2024-12-19 F1Tenth Sim Racing League at CDC 2024
- 2024-12-22 Open Hardware Summit CFP Deadline
- 2024-12-31 Deadline for Natural Robotics Contest
- 2025-02-01 FOSDEM 25 – See Robotics and Sim Room
- 2025-04-28 International Workshop on Robotics Software Engineering
- 2025-05-30 => 2025-05-31 2025 Open Hardware Summit in Edinburgh
News
- Ag Robotics Hackathon at FIRA 2025
- Highlights from ROSCon 2024
- Open Hardware Summit 2025 CFP
- Free Clearpath Robots for Startups and Labs
- A comprehensive list of Implicit Representations and NeRF papers relating to Robotics/RL domain
- Autonomous Cars Race On The Las Vegas Speedway At CES 2025
- Disarmament in Times of War: Interview with Ryan Gariepy
- ROSCon India CFP Extended
- A first look at supporting ROS within the Intrinsic platform
- ROSA demonstrated for Neil deGrasse Tyson at JPL.
- Ulysses is using robots to restore seagrass populations
- More Layoffs at iRobot
- Cynlr Raises $10M Series A
- Pipedream Labs deploys underground robotic delivery system in Texas drive thru
- Robotics investments top $3.7B in September
- Third Wave Automation picks up $27M Series C
- Agtonomy adds $10M to Series A round
- Relay Robotics proposes levels of autonomous navigation for indoor robots
- FarmDroid obtains over $11M to deploy its modular robot globally
- Outrider brings in $62M to drive commercial scaling in 2025
- Carbon Robotics brings in $70M to scale LaserWeeder
- Life-seeking, ice-melting robots could punch through Europa’s icy shell
- Video Friday
ROS
- Black Coffee Robotics Bot – Now with Isaac Sim
- Comprehensive Survey on ROS 2
- Space ROS Humble Release 2024.10.0
- r2s: Text User Interface (TUI) for interacting with various aspects of a ROS 2 system
- ROSCon 2024 Workshop: Zenoh + ROS 2
- ROSCon 2024 Workshop: Demystifying ROS 2 Networking
- ROSCon 2024 Workshop: Intro to ROS 2
- ROS 2 PMC Meeting Minutes 2024-11-05
- AMR / AGV ROS 2 Framework from Sony
- Introducing FIREBRINGER - A generalised autonomous navigation algorithm
- ROS 2 Jazzy and Rolling on Kobuki Robot
- Iron End-of-Life Plan
- 4 New and 74 Updated Packages for Iron
- 3 New and and 48 updated Packages for Noetic
- 9 New and 140 Updated Packages for Humble Hawksbill
- ROS 2 Pick and Place System with Edge Impulse
- ROS 1 EOL Migration Sprint
- October Maritime Community Group Meeting
- NASA JPL Robust High-Speed State Estimation for Off-road Navigation using Radar Velocity Factor – Video – Related Paper
- DM-VIO: Delayed Marginalization Visual-Inertial Odometry–Source code
- Arduino Opta PLC supports OPC UA
- RoboCasa: Large-Scale Simulation of Everyday Tasks for Generalist Robots
- ROS2 package designed to extrinsically calibrate a set of cameras distributed throughout a room.
- RVIZ Visuals Tutorial
- Misubishi MELFA ROS 2 Driver Demo from ROS Industrial - Code
- How to control a robot from ros2_control to make Unity easier to use.
- Articulate Robotics with Muhammad Luqman
- TurtleSim using Pixi
Got a minute? 
We desperately need more contributors to the ROS Documentation. If you learned something new this week why not share it with the community?
3 posts - 2 participants
https://discourse.ros.org/t/ros-news-for-the-week-of-november-4th-2024/40497
ROS Discourse General: [Announcement] Sony Robotics Solution (AMR/AGV) with ROS 2
Hi ROS users,
We Sony would like to make an quick announcement that we has released our robotics solution for AMR.
AutonMate
Autonomous Mobile Robot (AMR) that assists with picking through collaboration with humans, aiming to reduce labor. AMRs, positioned as the next generation of Automatic Guided Vehicles (AGVs), can travel without guides and move autonomously while avoiding people and obstacles.
Those robotics packages are already running in the market and actual workspace in Japan !!!
System Overview
The system is constructed with 2 components, the one is Fleet Management System and the other is Robot Navigation System.
All these proprietary system application are built on top of ROS 2 humble and Fast-DDS.
The system does many things such as map creation, autonomous navigation and device management. Based on our experiences especially for edge IoT and embedded devices, we develop the stable and robust system for the robots.
ROS Open Source Eco-System in Sony
Sony has been working to make a lot of contribution to the mainline based on the requirements from business logics, then we can use ROS as a user to the business applications. We really appreciate ROS community and ROS open source, and we will keep it up
If you are interested, please contact us.
thanks,
Tomoya
4 posts - 2 participants
https://discourse.ros.org/t/announcement-sony-robotics-solution-amr-agv-with-ros-2/40495
ROS Discourse General: Open Hardware Summit 2025 CFP
Hi Everyone,
I want to take off my ROS hat 
for a second and put on my Open Source Hardware Association (OSHWA) hat 
for second.
As some of you may know I’ve been on the board of the Open Source Hardware Association for some time now. The OSHWA team is really busy with an exciting new NSF project at the moment so I am stepping up to help with organizing this year’s Open Hardware Summit. I presented a Lightning Talk at ROSCon about this year’s summit and the response was so positive I figured I should also make an announcement on ROS Discourse. I might also be in the process of planning a ROS meetup in Edinburgh. If that’s something you would be interested in helping with please reach out to me directly via DM.
Open Hardware Summit 2025
This year’s Open Hardware Summit will be held in Edinburgh, Scotland on 2025-05-29T23:00:00Z UTC→2025-05-30T23:00:00Z UTC and tickets just went on sale. If you’ve never been to Open Hardware Summit you can get a taste of the event by watching our 2024 Summit Live Stream. Our keynote this year was from Danielle Boyer, a Ojibwe roboticist who is builds open hardware educational robots that teach students their indigenous languages.
OSHWA currently has an open call for proposals for this year’s Open Hardware Summit. If you have an open source hardware robot, or an interesting open hardware project that you would like to share, please consider submitting a talk or workshop proposal! Applications are due by 2024-12-22T08:00:00Z UTC.
While I have your attention…
I want to remind the ROS community that they should consider certifying their open hardware designs! Certification ensures that your project meets the minimum documentation requirements to be considered open source hardware, lists your project on our certification website, and provides you with a slick badge that you can include on your designs.
The OSHWA certification website is a gold mine of close to 3000 open hardware projects that you are free to study and use as part of your robotics project. The certification website currently includes 19 different motor drivers (like this stepper driver and this Grove Motor Driver from TU Delft ), 229 different robots (such as the NASA JPL Rover), and 312 different sensors (like this line sensor, and this pneumatics controller). I recommend you bookmark the certification website for easy reference!
2 posts - 2 participants
https://discourse.ros.org/t/open-hardware-summit-2025-cfp/40493
ROS Discourse General: Comprehensive Survey on ROS 2
ğ�— ğ�—¶ğ�—¹ğ�—²ğ�˜€ğ�˜�ğ�—¼ğ�—»ğ�—² ğ�—”ğ�—°ğ�—µğ�—¶ğ�—²ğ�˜ƒğ�—²ğ�—ºğ�—²ğ�—»ğ�˜�: ğ�—§ğ�—µğ�—² ğ�— ğ�—¼ğ�˜€ğ�˜� ğ�—–ğ�—¼ğ�—ºğ�—½ğ�—¿ğ�—²ğ�—µğ�—²ğ�—»ğ�˜€ğ�—¶ğ�˜ƒğ�—² ğ�—¦ğ�˜‚ğ�—¿ğ�˜ƒğ�—²ğ�˜† ğ�—¼ğ�—» ğ�—¥ğ�—¢ğ�—¦ ğ�Ÿ®:rocket:
I am excited to announce that our latest survey paper,
��� � �� � ��������: � ������
co-authored with Abdulrahman S. Al-Batati and Dr. Mohamed AbdelKader, is now available on Preprints.org! 
Credits go to Abdulrahman S. Al-Batati for the great efforts in gathering this volume of related works and also in building the first repository of ROS/ROS2 publications available at:
���/���� ����������: https://ros.riotu-lab.org/
���� �����: LinkedIn
This study stands as the ğ�—ºğ�—¼ğ�˜€ğ�˜� ğ�—°ğ�—¼ğ�—ºğ�—½ğ�—¿ğ�—²ğ�—µğ�—²ğ�—»ğ�˜€ğ�—¶ğ�˜ƒğ�—² ğ�˜€ğ�˜‚ğ�—¿ğ�˜ƒğ�—²ğ�˜† to date on the transition from ğ�—¥ğ�—¢ğ�—¦ ğ�Ÿ ğ�˜�ğ�—¼ ğ�—¥ğ�—¢ğ�—¦ ğ�Ÿ®, offering a deep dive into the enhancements, challenges, and future directions for ROS 2.
Our analysis covers:
Real-time capabilities
Enhanced modularity
Security improvements
Middleware and distributed systems
Multi-robot system applications
We carefully analyzed ğ�Ÿ³,ğ�Ÿ°ğ�Ÿµğ�Ÿ´ ğ�—¥ğ�—¢ğ�—¦-ğ�—¿ğ�—²ğ�—¹ğ�—®ğ�˜�ğ�—²ğ�—± ğ�—®ğ�—¿ğ�˜�ğ�—¶ğ�—°ğ�—¹ğ�—²ğ�˜€, with a focused review of ğ�Ÿ°ğ�Ÿ¯ğ�Ÿ ğ�—¥ğ�—¢ğ�—¦ ğ�Ÿ®-ğ�˜€ğ�—½ğ�—²ğ�—°ğ�—¶ğ�—³ğ�—¶ğ�—° ğ�—½ğ�˜‚ğ�—¯ğ�—¹ğ�—¶ğ�—°ğ�—®ğ�˜�ğ�—¶ğ�—¼ğ�—»ğ�˜€, making this a key resource for researchers, developers, and enthusiasts in the ROS community.
Our goal is to provide a cohesive synthesis that helps deepen the understanding of ROS 2’s contributions and guides future research in robotic systems design.
Join us in exploring the potential of ROS 2 and shaping the future of robotics! 
hashtag#ROS2 hashtag#Robotics hashtag#ROS hashtag#Research hashtag#AI hashtag#MachineLearning hashtag#RoboticsCommunity hashtag#ROSCommunity hashtag#OpenSource hashtag#Survey
7 posts - 5 participants
https://discourse.ros.org/t/comprehensive-survey-on-ros-2/40483
ROS Discourse General: Next Client Library WG Meeting: Friday 8th November 2024
Hi,
after a break I would like to start again the recurring meetings of the client library working group.
The next meeting will be this Friday, 8th November 2024 at 8 AM Pacific Time.
- Meeting link: https://meet.google.com/oij-atzj-znw
- Calendar invite: https://calendar.app.google/zArSBuxFXJnmBdsV6
- Google group if you want to be notified of future meetings: https://groups.google.com/g/ros-2-client-library-wg
The agenda for now includes:
- Improvements/Reworks of storage of goal results on the action servers Fix Memory Leak in Actions Using `EventsExecutor` by mauropasse · Pull Request #2661 · ros2/rclcpp · GitHub
- Discuss client library working group charter, to make this wg official under the new OSRA organization. See wg charter template and TGC policies
Everyone is welcome to join.
If you have topics you want to discuss, feel free to anticipate them here in this thread.
2 posts - 1 participant
https://discourse.ros.org/t/next-client-library-wg-meeting-friday-8th-november-2024/40457
ROS Discourse General: Introducing FIREBRINGER - A generalised autonomous navigation algorithm
Hey all,
Our company GEEAR (full announcement soon) has been developing FIREBRINGER - a generalised autonomous navigation algorithm implemented on ROS2 for field-robotic applications.
The algorithm is meant to support a variety of missions from simple point-to-point travelling and trajectory tracking, to more advanced interaction with third-party vehicles and our favourite - real-world dense robotic swarms (in the full academic sense of emergent collaborative behaviour). We will continue working on populating our library of mission types/functionalities so you can expect more in the future.
So far we have validated FIREBRINGER on real-world boats and ground vehicles and on copters and fixed-winged aircraft in gazebo, (real-world experiments coming soon). You can find our recent video unveiling our autonomous vessel prototype here.
The algorithm is meant to be easy to use and tune, only requiring basic physical characteristics of the robot (maximum linear/angular velocity and maximum acceleration for each degree of freedom of the robot), and it offers plug-n-play functionality when combined with an Ardupilot autopilot through MAVROS.
It is based on a lightweight, robust NMPC-variant integrated with artificial potential field theory. It can typically run at 100Hz on a normal PC and 25Hz on a RPi4B for all vehicle types. So far, it can receive topics regarding the location of other vehicles (third-party and collaborative), trajectory (e.g., NAV2 global path), destination (complete pose), and various other mission specific info. We are currently working on incorporating point-cloud/costmap information for surrounding obstacle avoidance. Our aim is to allow integration with any ROS2 perception package that may be used in field robotics. The algorithm outputs an optimal velocity for each degree of freedom so it needs to be combined with appropriate low-level actuation control (or connected to a well-tuned Ardupilot autopilot which will do the work).
We are currently considering creating and publishing a complete ROS2 package for the algorithm and we may propose some type of fusion with NAV2 in the future, but we wanted to gauge interest first. Obviously we are open to ideas and recommendations (and some criticism)!
2 posts - 2 participants
https://discourse.ros.org/t/introducing-firebringer-a-generalised-autonomous-navigation-algorithm/40440
ROS Discourse General: Clarification of Infrastructure PMC meeting time
tl;dr:
Infrastructure PMC meetings are held online at Mondays 16:00 UTC
The event is open to public observers who can join via the information on the OSRF Official Events calendar
Hello everyone,
The Infrastructure Project Management Committee meeting has been on the OSRF Official Events calendar since we made the switch from the earlier Infrastructure Project Committee to the OSRA-chartered Infrastructure PMC.
When I created the event, I accidentally did so using my local timezone instead of UTC pinning, as result, the meeting time was shown an hour later than previous weeks when the US clocks changed. Another PMC member noticed and reported this and I corrected the event.
My apologies to observers who joined an hour later, when the meeting time was originally posted.
3 posts - 2 participants
https://discourse.ros.org/t/clarification-of-infrastructure-pmc-meeting-time/40425
ROS Discourse General: New packages for Humble Hawksbill 2024-11-04
Package Updates for Humble
Added Packages [9]:
- ros-humble-etsi-its-vam-ts-coding: 2.3.0-1
- ros-humble-etsi-its-vam-ts-coding-dbgsym: 2.3.0-1
- ros-humble-etsi-its-vam-ts-conversion: 2.3.0-1
- ros-humble-etsi-its-vam-ts-msgs: 2.3.0-1
- ros-humble-etsi-its-vam-ts-msgs-dbgsym: 2.3.0-1
- ros-humble-sbg-driver: 3.2.0-1
- ros-humble-sbg-driver-dbgsym: 3.2.0-1
- ros-humble-web-video-server: 2.0.1-1
- ros-humble-web-video-server-dbgsym: 2.0.1-1
Updated Packages [140]:
- ros-humble-clearpath-msgs: 0.3.0-2 → 1.0.0-1
- ros-humble-clearpath-platform-msgs: 0.3.0-2 → 1.0.0-1
- ros-humble-clearpath-platform-msgs-dbgsym: 0.3.0-2 → 1.0.0-1
- ros-humble-control-toolbox: 3.2.0-1 → 3.3.0-1
- ros-humble-control-toolbox-dbgsym: 3.2.0-1 → 3.3.0-1
- ros-humble-etsi-its-cam-coding: 2.2.0-1 → 2.3.0-1
- ros-humble-etsi-its-cam-coding-dbgsym: 2.2.0-1 → 2.3.0-1
- ros-humble-etsi-its-cam-conversion: 2.2.0-1 → 2.3.0-1
- ros-humble-etsi-its-cam-msgs: 2.2.0-1 → 2.3.0-1
- ros-humble-etsi-its-cam-msgs-dbgsym: 2.2.0-1 → 2.3.0-1
- ros-humble-etsi-its-cam-ts-coding: 2.2.0-1 → 2.3.0-1
- ros-humble-etsi-its-cam-ts-coding-dbgsym: 2.2.0-1 → 2.3.0-1
- ros-humble-etsi-its-cam-ts-conversion: 2.2.0-1 → 2.3.0-1
- ros-humble-etsi-its-cam-ts-msgs: 2.2.0-1 → 2.3.0-1
- ros-humble-etsi-its-cam-ts-msgs-dbgsym: 2.2.0-1 → 2.3.0-1
- ros-humble-etsi-its-coding: 2.2.0-1 → 2.3.0-1
- ros-humble-etsi-its-conversion: 2.2.0-1 → 2.3.0-1
- ros-humble-etsi-its-conversion-dbgsym: 2.2.0-1 → 2.3.0-1
- ros-humble-etsi-its-cpm-ts-coding: 2.2.0-1 → 2.3.0-1
- ros-humble-etsi-its-cpm-ts-coding-dbgsym: 2.2.0-1 → 2.3.0-1
- ros-humble-etsi-its-cpm-ts-conversion: 2.2.0-1 → 2.3.0-1
- ros-humble-etsi-its-cpm-ts-msgs: 2.2.0-1 → 2.3.0-1
- ros-humble-etsi-its-cpm-ts-msgs-dbgsym: 2.2.0-1 → 2.3.0-1
- ros-humble-etsi-its-denm-coding: 2.2.0-1 → 2.3.0-1
- ros-humble-etsi-its-denm-coding-dbgsym: 2.2.0-1 → 2.3.0-1
- ros-humble-etsi-its-denm-conversion: 2.2.0-1 → 2.3.0-1
- ros-humble-etsi-its-denm-msgs: 2.2.0-1 → 2.3.0-1
- ros-humble-etsi-its-denm-msgs-dbgsym: 2.2.0-1 → 2.3.0-1
- ros-humble-etsi-its-messages: 2.2.0-1 → 2.3.0-1
- ros-humble-etsi-its-msgs: 2.2.0-1 → 2.3.0-1
- ros-humble-etsi-its-msgs-utils: 2.2.0-1 → 2.3.0-1
- ros-humble-etsi-its-primitives-conversion: 2.2.0-1 → 2.3.0-1
- ros-humble-etsi-its-rviz-plugins: 2.2.0-1 → 2.3.0-1
- ros-humble-etsi-its-rviz-plugins-dbgsym: 2.2.0-1 → 2.3.0-1
- ros-humble-generate-parameter-library: 0.3.8-3 → 0.3.9-1
- ros-humble-generate-parameter-library-example: 0.3.8-3 → 0.3.9-1
- ros-humble-generate-parameter-library-example-dbgsym: 0.3.8-3 → 0.3.9-1
- ros-humble-generate-parameter-library-py: 0.3.8-3 → 0.3.9-1
- ros-humble-generate-parameter-module-example: 0.3.8-3 → 0.3.9-1
- ros-humble-lanelet2: 1.2.1-1 → 1.2.2-1
- ros-humble-lanelet2-core: 1.2.1-1 → 1.2.2-1
- ros-humble-lanelet2-core-dbgsym: 1.2.1-1 → 1.2.2-1
- ros-humble-lanelet2-examples: 1.2.1-1 → 1.2.2-1
- ros-humble-lanelet2-examples-dbgsym: 1.2.1-1 → 1.2.2-1
- ros-humble-lanelet2-io: 1.2.1-1 → 1.2.2-1
- ros-humble-lanelet2-io-dbgsym: 1.2.1-1 → 1.2.2-1
- ros-humble-lanelet2-maps: 1.2.1-1 → 1.2.2-1
- ros-humble-lanelet2-matching: 1.2.1-1 → 1.2.2-1
- ros-humble-lanelet2-matching-dbgsym: 1.2.1-1 → 1.2.2-1
- ros-humble-lanelet2-projection: 1.2.1-1 → 1.2.2-1
- ros-humble-lanelet2-projection-dbgsym: 1.2.1-1 → 1.2.2-1
- ros-humble-lanelet2-python: 1.2.1-1 → 1.2.2-1
- ros-humble-lanelet2-python-dbgsym: 1.2.1-1 → 1.2.2-1
- ros-humble-lanelet2-routing: 1.2.1-1 → 1.2.2-1
- ros-humble-lanelet2-routing-dbgsym: 1.2.1-1 → 1.2.2-1
- ros-humble-lanelet2-traffic-rules: 1.2.1-1 → 1.2.2-1
- ros-humble-lanelet2-traffic-rules-dbgsym: 1.2.1-1 → 1.2.2-1
- ros-humble-lanelet2-validation: 1.2.1-1 → 1.2.2-1
- ros-humble-lanelet2-validation-dbgsym: 1.2.1-1 → 1.2.2-1
- ros-humble-launch-pal: 0.4.0-1 → 0.7.0-1
- ros-humble-mrpt-apps: 2.14.3-1 → 2.14.4-1
- ros-humble-mrpt-apps-dbgsym: 2.14.3-1 → 2.14.4-1
- ros-humble-mrpt-libapps: 2.14.3-1 → 2.14.4-1
- ros-humble-mrpt-libapps-dbgsym: 2.14.3-1 → 2.14.4-1
- ros-humble-mrpt-libbase: 2.14.3-1 → 2.14.4-1
- ros-humble-mrpt-libbase-dbgsym: 2.14.3-1 → 2.14.4-1
- ros-humble-mrpt-libgui: 2.14.3-1 → 2.14.4-1
- ros-humble-mrpt-libgui-dbgsym: 2.14.3-1 → 2.14.4-1
- ros-humble-mrpt-libhwdrivers: 2.14.3-1 → 2.14.4-1
- ros-humble-mrpt-libhwdrivers-dbgsym: 2.14.3-1 → 2.14.4-1
- ros-humble-mrpt-libmaps: 2.14.3-1 → 2.14.4-1
- ros-humble-mrpt-libmaps-dbgsym: 2.14.3-1 → 2.14.4-1
- ros-humble-mrpt-libmath: 2.14.3-1 → 2.14.4-1
- ros-humble-mrpt-libmath-dbgsym: 2.14.3-1 → 2.14.4-1
- ros-humble-mrpt-libnav: 2.14.3-1 → 2.14.4-1
- ros-humble-mrpt-libnav-dbgsym: 2.14.3-1 → 2.14.4-1
- ros-humble-mrpt-libobs: 2.14.3-1 → 2.14.4-1
- ros-humble-mrpt-libobs-dbgsym: 2.14.3-1 → 2.14.4-1
- ros-humble-mrpt-libopengl: 2.14.3-1 → 2.14.4-1
- ros-humble-mrpt-libopengl-dbgsym: 2.14.3-1 → 2.14.4-1
- ros-humble-mrpt-libposes: 2.14.3-1 → 2.14.4-1
- ros-humble-mrpt-libposes-dbgsym: 2.14.3-1 → 2.14.4-1
- ros-humble-mrpt-libros-bridge: 2.14.3-1 → 2.14.4-1
- ros-humble-mrpt-libros-bridge-dbgsym: 2.14.3-1 → 2.14.4-1
- ros-humble-mrpt-libslam: 2.14.3-1 → 2.14.4-1
- ros-humble-mrpt-libslam-dbgsym: 2.14.3-1 → 2.14.4-1
- ros-humble-mrpt-libtclap: 2.14.3-1 → 2.14.4-1
- ros-humble-mvsim: 0.11.0-1 → 0.11.1-1
- ros-humble-mvsim-dbgsym: 0.11.0-1 → 0.11.1-1
- ros-humble-octomap-rviz-plugins: 2.1.0-1 → 2.1.1-1
- ros-humble-octomap-rviz-plugins-dbgsym: 2.1.0-1 → 2.1.1-1
- ros-humble-omni-base-2dnav: 2.3.0-1 → 2.4.0-1
- ros-humble-omni-base-bringup: 2.4.0-1 → 2.4.1-1
- ros-humble-omni-base-controller-configuration: 2.4.0-1 → 2.4.1-1
- ros-humble-omni-base-description: 2.4.0-1 → 2.4.1-1
- ros-humble-omni-base-gazebo: 2.1.0-1 → 2.2.0-1
- ros-humble-omni-base-laser-sensors: 2.3.0-1 → 2.4.0-1
- ros-humble-omni-base-navigation: 2.3.0-1 → 2.4.0-1
- ros-humble-omni-base-rgbd-sensors: 2.3.0-1 → 2.4.0-1
- ros-humble-omni-base-robot: 2.4.0-1 → 2.4.1-1
- ros-humble-omni-base-simulation: 2.1.0-1 → 2.2.0-1
- ros-humble-parameter-traits: 0.3.8-3 → 0.3.9-1
- ros-humble-pmb2-bringup: 5.3.0-1 → 5.3.1-1
- ros-humble-pmb2-controller-configuration: 5.3.0-1 → 5.3.1-1
- ros-humble-pmb2-description: 5.3.0-1 → 5.3.1-1
- ros-humble-pmb2-robot: 5.3.0-1 → 5.3.1-1
- ros-humble-pose-cov-ops: 0.3.12-1 → 0.3.13-1
- ros-humble-pose-cov-ops-dbgsym: 0.3.12-1 → 0.3.13-1
- ros-humble-python-mrpt: 2.14.3-1 → 2.14.4-1
- ros-humble-realtime-tools: 2.6.0-1 → 2.7.0-1
- ros-humble-realtime-tools-dbgsym: 2.6.0-1 → 2.7.0-1
- ros-humble-sick-scan-xd: 3.5.0-1 → 3.6.0-1
- ros-humble-sick-scan-xd-dbgsym: 3.5.0-1 → 3.6.0-1
- ros-humble-tiago-bringup: 4.5.0-1 → 4.6.0-1
- ros-humble-tiago-controller-configuration: 4.5.0-1 → 4.6.0-1
- ros-humble-tiago-description: 4.5.0-1 → 4.6.0-1
- ros-humble-tiago-moveit-config: 3.0.18-1 → 3.1.0-1
- ros-humble-tiago-robot: 4.5.0-1 → 4.6.0-1
- ros-humble-ur: 2.2.15-1 → 2.2.16-5
- ros-humble-ur-bringup: 2.2.15-1 → 2.2.16-5
- ros-humble-ur-calibration: 2.2.15-1 → 2.2.16-5
- ros-humble-ur-calibration-dbgsym: 2.2.15-1 → 2.2.16-5
- ros-humble-ur-controllers: 2.2.15-1 → 2.2.16-5
- ros-humble-ur-controllers-dbgsym: 2.2.15-1 → 2.2.16-5
- ros-humble-ur-dashboard-msgs: 2.2.15-1 → 2.2.16-5
- ros-humble-ur-dashboard-msgs-dbgsym: 2.2.15-1 → 2.2.16-5
- ros-humble-ur-description: 2.1.7-1 → 2.1.8-2
- ros-humble-ur-moveit-config: 2.2.15-1 → 2.2.16-5
- ros-humble-ur-robot-driver: 2.2.15-1 → 2.2.16-5
- ros-humble-ur-robot-driver-dbgsym: 2.2.15-1 → 2.2.16-5
- ros-humble-urdf-test: 2.0.3-1 → 2.1.0-1
- ros-humble-velodyne: 2.4.0-1 → 2.5.1-1
- ros-humble-velodyne-driver: 2.4.0-1 → 2.5.1-1
- ros-humble-velodyne-driver-dbgsym: 2.4.0-1 → 2.5.1-1
- ros-humble-velodyne-laserscan: 2.4.0-1 → 2.5.1-1
- ros-humble-velodyne-laserscan-dbgsym: 2.4.0-1 → 2.5.1-1
- ros-humble-velodyne-msgs: 2.4.0-1 → 2.5.1-1
- ros-humble-velodyne-msgs-dbgsym: 2.4.0-1 → 2.5.1-1
- ros-humble-velodyne-pointcloud: 2.4.0-1 → 2.5.1-1
- ros-humble-velodyne-pointcloud-dbgsym: 2.4.0-1 → 2.5.1-1
Removed Packages [0]:
Thanks to all ROS maintainers who make packages available to the ROS community. The above list of packages was made possible by the work of the following maintainers:
- Andrea Capodacqua
- Armin Hornung
- Bence Magyar
- Błażej Sowa
- Denis Stogl
- Fabian Immel
- Felix Exner
- Jan-Hendrik Pauls
- Jean-Pierre Busch
- Jordan Palacios
- Jordi Pages
- Jose-Luis Blanco-Claraco
- Josh Whitley
- Paul Gesel
- Roni Kreinin
- SBG Systems
- TIAGo PAL support team
- Tyler Weaver
- Yue Erro
- paul
- rostest
1 post - 1 participant
https://discourse.ros.org/t/new-packages-for-humble-hawksbill-2024-11-04/40422
ROS Discourse General: Interoperability Interest Group November 07, 2024: What's in an interface?
2024-11-07T15:00:00Z UTC
That which we call an API by any other name would serve just as well. But when there are many diverging opinions on exactly what names to use or exactly how to structure things, we may end up scattering our efforts instead of working together.
The OSRA TGC opened a technical committee to examine the ROS Enhancement Proposal (REP) process to refine it and apply it to all of the projects that are governed by the OSRA, including Open-RMF. The PMC of Open-RMF sees this as an opportunity to formalize something similar to a Request For Comments (RFC) process for Open-RMF where we can define interfaces for our next generation development and receive comments from the public, especially from stakeholders, to make sure that we’ll be developing the most useful tools possible for everyone. This would also define a formal way for anyone from the general public to propose new interfaces for Open-RMF to support.
At this session of the special interest group, Grey will present a working draft of what kind of process we are considering for Open-RMF.
We are eager to get feedback from the Open-RMF community and beyond about how to make this process as effective as possible. Effectiveness would be measured both in terms of making sure we are producing the highest quality stable interfaces possible and also getting contributions (proposals, feedback, and implementation) from as many community stakeholders as possible.
After presenting our current ideas, we want to open up the session to discussion and feedback, so please come ready to share your own thoughts. We will especially appreciate input from anyone that has experience (both positive and negative experiences) working with standardization bodies.
1 post - 1 participant
https://discourse.ros.org/t/interoperability-interest-group-november-07-2024-whats-in-an-interface/40390
ROS Discourse General: New Packages for Iron Irwini 2024-11-01
Hello everyone!
We’re happy to announce 4 new package and 74 updates are now available in ROS 2 Iron Irwini 
.
This sync was tagged as iron/2024-11-01 .
Package Updates for iron
Added Packages [4]:
- ros-iron-performance-test: 2.3.0-1
- ros-iron-performance-test-dbgsym: 2.3.0-1
- ros-iron-sbg-driver: 3.2.0-1
- ros-iron-sbg-driver-dbgsym: 3.2.0-1
Updated Packages [74]:
- ros-iron-control-toolbox: 3.2.0-1 → 3.3.0-1
- ros-iron-control-toolbox-dbgsym: 3.2.0-1 → 3.3.0-1
- ros-iron-diagnostic-aggregator: 4.1.0-1 → 4.1.0-2
- ros-iron-diagnostic-aggregator-dbgsym: 4.1.0-1 → 4.1.0-2
- ros-iron-diagnostic-common-diagnostics: 4.1.0-1 → 4.1.0-2
- ros-iron-diagnostic-updater: 4.1.0-1 → 4.1.0-2
- ros-iron-diagnostic-updater-dbgsym: 4.1.0-1 → 4.1.0-2
- ros-iron-diagnostics: 4.1.0-1 → 4.1.0-2
- ros-iron-generate-parameter-library: 0.3.8-3 → 0.3.9-1
- ros-iron-generate-parameter-library-example: 0.3.8-3 → 0.3.9-1
- ros-iron-generate-parameter-library-example-dbgsym: 0.3.8-3 → 0.3.9-1
- ros-iron-generate-parameter-library-py: 0.3.8-3 → 0.3.9-1
- ros-iron-generate-parameter-module-example: 0.3.8-3 → 0.3.9-1
- ros-iron-mrpt-apps: 2.14.3-1 → 2.14.4-1
- ros-iron-mrpt-apps-dbgsym: 2.14.3-1 → 2.14.4-1
- ros-iron-mrpt-libapps: 2.14.3-1 → 2.14.4-1
- ros-iron-mrpt-libapps-dbgsym: 2.14.3-1 → 2.14.4-1
- ros-iron-mrpt-libbase: 2.14.3-1 → 2.14.4-1
- ros-iron-mrpt-libbase-dbgsym: 2.14.3-1 → 2.14.4-1
- ros-iron-mrpt-libgui: 2.14.3-1 → 2.14.4-1
- ros-iron-mrpt-libgui-dbgsym: 2.14.3-1 → 2.14.4-1
- ros-iron-mrpt-libhwdrivers: 2.14.3-1 → 2.14.4-1
- ros-iron-mrpt-libhwdrivers-dbgsym: 2.14.3-1 → 2.14.4-1
- ros-iron-mrpt-libmaps: 2.14.3-1 → 2.14.4-1
- ros-iron-mrpt-libmaps-dbgsym: 2.14.3-1 → 2.14.4-1
- ros-iron-mrpt-libmath: 2.14.3-1 → 2.14.4-1
- ros-iron-mrpt-libmath-dbgsym: 2.14.3-1 → 2.14.4-1
- ros-iron-mrpt-libnav: 2.14.3-1 → 2.14.4-1
- ros-iron-mrpt-libnav-dbgsym: 2.14.3-1 → 2.14.4-1
- ros-iron-mrpt-libobs: 2.14.3-1 → 2.14.4-1
- ros-iron-mrpt-libobs-dbgsym: 2.14.3-1 → 2.14.4-1
- ros-iron-mrpt-libopengl: 2.14.3-1 → 2.14.4-1
- ros-iron-mrpt-libopengl-dbgsym: 2.14.3-1 → 2.14.4-1
- ros-iron-mrpt-libposes: 2.14.3-1 → 2.14.4-1
- ros-iron-mrpt-libposes-dbgsym: 2.14.3-1 → 2.14.4-1
- ros-iron-mrpt-libros-bridge: 2.14.3-1 → 2.14.4-1
- ros-iron-mrpt-libros-bridge-dbgsym: 2.14.3-1 → 2.14.4-1
- ros-iron-mrpt-libslam: 2.14.3-1 → 2.14.4-1
- ros-iron-mrpt-libslam-dbgsym: 2.14.3-1 → 2.14.4-1
- ros-iron-mrpt-libtclap: 2.14.3-1 → 2.14.4-1
- ros-iron-mvsim: 0.11.0-1 → 0.11.1-1
- ros-iron-mvsim-dbgsym: 0.11.0-1 → 0.11.1-1
- ros-iron-octomap-rviz-plugins: 2.1.0-1 → 2.1.1-1
- ros-iron-octomap-rviz-plugins-dbgsym: 2.1.0-1 → 2.1.1-1
- ros-iron-parameter-traits: 0.3.8-3 → 0.3.9-1
- ros-iron-pose-cov-ops: 0.3.12-1 → 0.3.13-1
- ros-iron-pose-cov-ops-dbgsym: 0.3.12-1 → 0.3.13-1
- ros-iron-python-mrpt: 2.14.3-1 → 2.14.4-1
- ros-iron-realtime-tools: 2.6.0-1 → 2.7.0-1
- ros-iron-realtime-tools-dbgsym: 2.6.0-1 → 2.7.0-1
- ros-iron-self-test: 4.1.0-1 → 4.1.0-2
- ros-iron-self-test-dbgsym: 4.1.0-1 → 4.1.0-2
- ros-iron-sick-scan-xd: 3.5.0-1 → 3.6.0-1
- ros-iron-sick-scan-xd-dbgsym: 3.5.0-1 → 3.6.0-1
- ros-iron-ur: 2.3.10-1 → 2.3.11-2
- ros-iron-ur-calibration: 2.3.10-1 → 2.3.11-2
- ros-iron-ur-calibration-dbgsym: 2.3.10-1 → 2.3.11-2
- ros-iron-ur-controllers: 2.3.10-1 → 2.3.11-2
- ros-iron-ur-controllers-dbgsym: 2.3.10-1 → 2.3.11-2
- ros-iron-ur-dashboard-msgs: 2.3.10-1 → 2.3.11-2
- ros-iron-ur-dashboard-msgs-dbgsym: 2.3.10-1 → 2.3.11-2
- ros-iron-ur-description: 2.3.2-1 → 2.3.3-2
- ros-iron-ur-moveit-config: 2.3.10-1 → 2.3.11-2
- ros-iron-ur-robot-driver: 2.3.10-1 → 2.3.11-2
- ros-iron-ur-robot-driver-dbgsym: 2.3.10-1 → 2.3.11-2
- ros-iron-velodyne: 2.3.0-3 → 2.5.1-1
- ros-iron-velodyne-driver: 2.3.0-3 → 2.5.1-1
- ros-iron-velodyne-driver-dbgsym: 2.3.0-3 → 2.5.1-1
- ros-iron-velodyne-laserscan: 2.3.0-3 → 2.5.1-1
- ros-iron-velodyne-laserscan-dbgsym: 2.3.0-3 → 2.5.1-1
- ros-iron-velodyne-msgs: 2.3.0-3 → 2.5.1-1
- ros-iron-velodyne-msgs-dbgsym: 2.3.0-3 → 2.5.1-1
- ros-iron-velodyne-pointcloud: 2.3.0-3 → 2.5.1-1
- ros-iron-velodyne-pointcloud-dbgsym: 2.3.0-3 → 2.5.1-1
Removed Packages [0]:
Thanks to all ROS maintainers who make packages available to the ROS community. The above list of packages was made possible by the work of the following maintainers:
- Apex AI, Inc.
- Armin Hornung
- Austin Hendrix
- Bence Magyar
- Denis Stogl
- Felix Exner
- Jose-Luis Blanco-Claraco
- Josh Whitley
- Paul Gesel
- SBG Systems
- Tyler Weaver
- paul
- rostest
1 post - 1 participant
https://discourse.ros.org/t/new-packages-for-iron-irwini-2024-11-01/40384
ROS Discourse General: New Packages for Noetic 2024-10-31
We’re happy to announce 3 new packages and 48 updates are now available in ROS Noetic. This sync was tagged as noetic/2024-10-31.
Thank you to every maintainer and contributor who made these updates available!
Package Updates for ROS Noetic
Added Packages [3]:
- ros-noetic-etsi-its-vam-ts-coding: 2.3.0-1
- ros-noetic-etsi-its-vam-ts-conversion: 2.3.0-1
- ros-noetic-etsi-its-vam-ts-msgs: 2.3.0-1
Updated Packages [48]:
- ros-noetic-etsi-its-cam-coding: 2.2.0-1 → 2.3.0-1
- ros-noetic-etsi-its-cam-conversion: 2.2.0-1 → 2.3.0-1
- ros-noetic-etsi-its-cam-msgs: 2.2.0-1 → 2.3.0-1
- ros-noetic-etsi-its-cam-ts-coding: 2.2.0-1 → 2.3.0-1
- ros-noetic-etsi-its-cam-ts-conversion: 2.2.0-1 → 2.3.0-1
- ros-noetic-etsi-its-cam-ts-msgs: 2.2.0-1 → 2.3.0-1
- ros-noetic-etsi-its-coding: 2.2.0-1 → 2.3.0-1
- ros-noetic-etsi-its-conversion: 2.2.0-1 → 2.3.0-1
- ros-noetic-etsi-its-cpm-ts-coding: 2.2.0-1 → 2.3.0-1
- ros-noetic-etsi-its-cpm-ts-conversion: 2.2.0-1 → 2.3.0-1
- ros-noetic-etsi-its-cpm-ts-msgs: 2.2.0-1 → 2.3.0-1
- ros-noetic-etsi-its-denm-coding: 2.2.0-1 → 2.3.0-1
- ros-noetic-etsi-its-denm-conversion: 2.2.0-1 → 2.3.0-1
- ros-noetic-etsi-its-denm-msgs: 2.2.0-1 → 2.3.0-1
- ros-noetic-etsi-its-messages: 2.2.0-1 → 2.3.0-1
- ros-noetic-etsi-its-msgs: 2.2.0-1 → 2.3.0-1
- ros-noetic-etsi-its-msgs-utils: 2.2.0-1 → 2.3.0-1
- ros-noetic-etsi-its-primitives-conversion: 2.2.0-1 → 2.3.0-1
- ros-noetic-etsi-its-rviz-plugins: 2.2.0-1 → 2.3.0-1
- ros-noetic-lanelet2: 1.2.1-2 → 1.2.2-2
- ros-noetic-lanelet2-core: 1.2.1-2 → 1.2.2-2
- ros-noetic-lanelet2-examples: 1.2.1-2 → 1.2.2-2
- ros-noetic-lanelet2-io: 1.2.1-2 → 1.2.2-2
- ros-noetic-lanelet2-maps: 1.2.1-2 → 1.2.2-2
- ros-noetic-lanelet2-matching: 1.2.1-2 → 1.2.2-2
- ros-noetic-lanelet2-projection: 1.2.1-2 → 1.2.2-2
- ros-noetic-lanelet2-python: 1.2.1-2 → 1.2.2-2
- ros-noetic-lanelet2-routing: 1.2.1-2 → 1.2.2-2
- ros-noetic-lanelet2-traffic-rules: 1.2.1-2 → 1.2.2-2
- ros-noetic-lanelet2-validation: 1.2.1-2 → 1.2.2-2
- ros-noetic-mrpt-apps: 2.14.3-1 → 2.14.4-1
- ros-noetic-mrpt-libapps: 2.14.3-1 → 2.14.4-1
- ros-noetic-mrpt-libbase: 2.14.3-1 → 2.14.4-1
- ros-noetic-mrpt-libgui: 2.14.3-1 → 2.14.4-1
- ros-noetic-mrpt-libhwdrivers: 2.14.3-1 → 2.14.4-1
- ros-noetic-mrpt-libmaps: 2.14.3-1 → 2.14.4-1
- ros-noetic-mrpt-libmath: 2.14.3-1 → 2.14.4-1
- ros-noetic-mrpt-libnav: 2.14.3-1 → 2.14.4-1
- ros-noetic-mrpt-libobs: 2.14.3-1 → 2.14.4-1
- ros-noetic-mrpt-libopengl: 2.14.3-1 → 2.14.4-1
- ros-noetic-mrpt-libposes: 2.14.3-1 → 2.14.4-1
- ros-noetic-mrpt-libros-bridge: 2.14.3-1 → 2.14.4-1
- ros-noetic-mrpt-libslam: 2.14.3-1 → 2.14.4-1
- ros-noetic-mrpt-libtclap: 2.14.3-1 → 2.14.4-1
- ros-noetic-mvsim: 0.11.0-1 → 0.11.2-1
- ros-noetic-pose-cov-ops: 0.3.12-1 → 0.3.13-1
- ros-noetic-python-mrpt: 2.14.3-1 → 2.14.4-1
- ros-noetic-sick-scan-xd: 3.5.0-1 → 3.6.0-1
Removed Packages [0]:
Thanks to all ROS maintainers who make packages available to the ROS community. The above list of packages was made possible by the work of the following maintainers:
- Fabian Immel
- Jan-Hendrik Pauls
- Jean-Pierre Busch
- Jose-Luis Blanco-Claraco
- rostest
1 post - 1 participant
https://discourse.ros.org/t/new-packages-for-noetic-2024-10-31/40376
ROS Discourse General: Kobuki in ROS 2 Jazzy & Rolling + Gazebo Harmonic
Hello everyone!
Let me introduce myself, my name is Juan Carlos Manzanares and I belong to a robotics research group called Intelligent Robotics Lab , belonging to the Rey Juan Carlos University, Madrid, Spain. In this group we develop some projects, such as MOCAP4ROS2 , PlanSys2 , CascadeLifecycle, marathon for nav2 , robocups, go2_robot, tiago_harmonic…
Today I would like to show you a package that we have prepared to be able to install and use TurtleBot2 Kobuki in a more comfortable way, either with a real robot or using the new gazebo simulator.
This package directly uses the kobuki_ros packages, which have been tested and prepared so that they can be used in the Jazzy and Rolling versions. In addition, I have retouched the urdf to my liking, so that in a more comfortable way you can add/remove the camera and lidar sensors, the structure, or indicate whether or not you are going to use the gazebo plugin.
Simulated Kobuki in Gazebo Harmonic ROS 2 Jazzy
Finally, it is also prepared so that you can launch Navigation2 from the package.
Real Kobuki using Nav2 in ROS 2 Jazzy
Simulated Kobuki using Nav2 in Gazebo Harmonic ROS 2 Jazzy
This package is being used by students from the Rey Juan Carlos University, and I hope it will be useful to all of you who have a kobuki and don’t know what to do with it. And of course, we are open to any PR to make everything work better, any problem you find, or to clarify the steps much more.
Thank you very much for reading the post and I hope it helps many of you.
Greetings.
4 posts - 3 participants
https://discourse.ros.org/t/kobuki-in-ros-2-jazzy-rolling-gazebo-harmonic/40372
ROS Discourse General: Agenda for upcoming meeting of the ROS Deliberation Community Group
Hi!
This will be the agenda for upcoming meeting:
- Review of workshop results
- Presentation of new co-moderator @scastro
- New: meetings now on google meet
- Meetings in the future will not be recorded
- Discussion of new direction for community group
Please join us if you want to discuss the future direction of the community group.
The next meeting will be on 2024-11-04T15:00:00Z UTC
Find all necessary information to join here: ROS Deliberation Community Group - Google Docs
10 posts - 6 participants
https://discourse.ros.org/t/agenda-for-upcoming-meeting-of-the-ros-deliberation-community-group/40371
ROS Discourse General: Iron Irwini EOL Plan
Hello everyone,
ROS 2 Iron Irwini which was released on 23rd May 2023 is a non-LTS release and is due to be marked end-of-life (EOL) by the end of November 2024.
If you are using Iron, it is strongly recommended to switch to Jazzy Jalisco which will be supported until May 2029.
Once EOL, we will no longer release updates to core and community managed packages through the ROS Buildfarm. We will also not backport any changes to the iron branches of core repositories. The distribution will be frozen forever.
The plan for the next month is as follows:
- We will perform a regular sync on 1st Nov as announced here.
- Between 1st Nov and 15th Nov, will be aim to merge all open backport PRs in the core repositories and release binaries for these packages.
- On 15th Nov, we will perform the final Patch release of all core packages and sync community packages one last time.
- Between 15th Nov and 23rd Nov, we will update infrastructure and documentation to mark Iron as EOL. During this time we will also address any issues from the final sync.
If you’re a maintainer of a package released on Iron, this is your call to get the final versions of your packages released on the Buildfarm over the next couple of weeks. Remember Iron will be in sync hold a few days prior to Nov 15th so please plan in advance.
Yadu
2 posts - 2 participants
https://discourse.ros.org/t/iron-irwini-eol-plan/40365
ROS Discourse General: FOSDEM 2025: Robotics & Simulation... first edition!
We’re excited to announce the first Robotics and Simulation devroom at FOSDEM 2025, scheduled for Sunday, February 2nd in Brussels!
A Robotics and Simulation developer room at FOSDEM, focused on core robotics libraries, frameworks, simulation tools, and open-source platforms. The selected talks will cover key tools like ROS and Gazebo, showcasing advancements and projects in the field. The half-day event will feature four presentations and a lightning talk session, offering a platform for developers to share work and foster collaboration.
Scope of Talks
Because of the varied and interdisciplinary nature of robotics as a field, plenty of topics could fit a ‘Robotics and Simulation’ devroom. To help the speakers target their presentations to a specific audience, and to minimize the overlap with other established FOSDEM devrooms, we defined the scope of this devroom by listing key areas of interest:
- Core robotics libraries and applications. Mapping, planning, localization, perception, and control solutions would fit this category. For example, Cartographer, OMPL, grid_map, Octomap, PCL, OpEn, OpenRMF
- Frameworks used when building robotics applications, being robotic specific tools, or generic tools used for robotics applications. Examples include ROS, Dora-RS, OpenRR, YARP, Zenoh, and Eclipse iceoryx Of course this is the ROS discourse but FOSDEM invites all types of robotic frameworks so please see this as an opportunity to learn from each other.
- Specific robotic simulation software like Gazebo, Coppelia, or simulations using non robotic specific tools, like Bevy, Godot.
- Robotic-specific devops and related tooling, like webviz, MCAP
- Robotics platforms friendly for open source development, like Andino, Crazyflie, Turtlebot.
- Robotic products implemented using open source software. This can include examples of AI methods used to teach robots to perform certain tasks, or controlling robots using LLMs. For example, dora-rs, ros2ai, robo-gym
The examples mentioned are meant to be descriptive and not restricted. Talks could be improvements to any of the mentioned packages, interesting uses of them, alternatives with different degrees of maturity, or totally unrelated to them.
Submission instructions
Talks proposal submission:
- Deadline: 1st December 2024
- Accepted talks notification: 6th December 2024
- Format (indicate that in the proposal notes)
- 20 mins + 5 mins for Q&A
- 5 min lightning talks
- Use this link: FOSDEM 2025 :: pretalx and please choose “Robotics and Simulation” as the “Track” when submitting your talk.
See you in Brussels!
Committee
- Arnaud Taffanel (Bitcraze)
- Fred Gurr (Eclipse Foundation)
- Lucas Chiesa (Ekumen) @tulku
- Kimberly McGuire (Bitcraze) @KimMcG
- Mat Sadowski (Weekly Robotics) @msadowski
7 posts - 5 participants
https://discourse.ros.org/t/fosdem-2025-robotics-simulation-first-edition/40349
ROS Discourse General: ROS2 diagnostics from Jetson with jrosclient and isaac_ros_jetson_stats
Hi,
ROS2 diagnostics messages are part of jros2client starting from version 10.0.
We wrote a short article which covers how users can use ROS2 diagnostics, by subscribing to it with jros2client directly from Java. All received ROS diagnostics message are converted to OpenTelemetry metrics and sent to OpenTelemetry for further processing.
In our example, as a source of all diagnostics we use Jetson Orin Nano. All diagnostics from Jetson is gathered and published to ROS by isaac_ros_jetson_stats.
The entire flow looks like this:
Read full article OR
Check the complete code
1 post - 1 participant
https://discourse.ros.org/t/ros2-diagnostics-from-jetson-with-jrosclient-and-isaac-ros-jetson-stats/40337
ROS Discourse General: Vizanti Mission Planner - Jazzy Release, RWS, & Other News
Hey everyone 
You know, I’ve suddenly realized been over a year since my last post on this topic and there have been a lot of additions so I figured I ought to compile a short rundown of the more notable bits.
For those new to it, Vizanti is a community maintained open source control and visualization command center for ROS 1/2 in the web browser, targeting primarily outdoor use cases like marine, field, and aerial robotics on mobile and desktop devices.
Jazzy Release
This mainly involved waiting for rosbridge and rws to update, since there was little in terms of breaking changes. So far the ros2 branch can stay common to both Humble and Jazzy, which reduces overhead for backporting changes. The stability and usability is now more or less on par with Noetic, which will continue to get equal feature updates at least until the end of 2025 as well.
Well I wrote “release” there, but there isn’t exactly an apt release for the package yet, for various popen, rws, and other reasons. TBD.
RWS - ROS Websocket Server
Since web browsers are mostly restricted to TCP and as such can’t really connect with a DDS (or even ros_comm for that matter), an intermediary server is needed to pack traffic up into websockets.
Originally this was established by rosbridge suite on ROS, but due to a multitude of reasons it’s not nearly as performant on ROS 2. That’s why I’ve been working with v-kiniv to integrate his drop in replacement server, RWS.
There were a few things to fix up and a feature or two to add, but after nearly a year I think we’re at a point where it’s basically there now.
While a bit more of a hassle to set up, it uses significantly fewer resources while providing much higher throughput, enabling use on low end platforms like the Pi 4 and 5 where the ROS 2 version of Rosbridge isn’t efficient enough to function under typical load.
Right now it’s the recommended backend to use with Vizanti on Humble and Jazzy. And unless you’re using client side services, probably for your roslibjs project as well.
Updates
There are a handful of new widgets, and a few existing ones have been expanded to support multiple topics for better compatibility.
Grid Cells
This one is somewhat underused in Rviz in my experience, but extremely efficient for sparse grid data, such as the occasional obstacle in an open field. Comes in any 24-bit colour.
Altimeter
Yes a way to finally see the Z axis, very good. Ah, but it’s not just for observation, tapping the meter sends a Float32 target with the clicked value for direct depth/altitude control.
What it tracks exactly is the position of a chosen TF link relative to the fixed frame. Comes in depth (blue) and altitude (green) versions with adjustable units, but doesn’t do both at the same time. I have to apologise if any of you happen to be working on aerial submarines, but those simply won’t fly.
Folder
Is your tiny screen getting filled up with rows and rows of widgets? Well, now they can be grouped together, just like in rviz.
There are some limitations, mainly that the widget has to be created in the folder and can’t be moved around. I’m still figuring out a way to even conceptually do that UX-wise now that both the short and long click are taken, and mobile has no right click…
Speedometer
Okay this one’s a bit funky, it lets you measure the relative speed of any two tf links in various scientific (and unscientific) units. A handy thing to check if your nav stack is set to drive at the correct velocity and/or if your boat props have weeds in them.
In the gif above, the first few dials track turtle1 relative to world in various units, the next one turtle1 relative to turtle2, final one tracks turtle2 to world.
General improvements
Covariance rendering is correct now:
(what do you mean it was wrong before
, aaah you saw nothing)
The icons will reflect the visualizer color by recoloring the svg, so it’s easier to find which icon corresponds to what’s being rendered:
Map rendering has code-exact rendering parity with rviz in terms of colour mapping (as well as the raw display mode), except for a slightly more transparent tinge for unknown pixels, which imo looks slightly better:
TF frames now get grouped together by prefix, for clarity:
Community Contributions
A notable change to the satelite tile renderer was started by kosmonauta144 and darkhannibal, which enabled the use of other tile zoom levels, letting you see your robot from orbit:
The tiles themselves are now exportable and importable, so it’s possible to just load up the entire area beforehand and load it up offline on another device.
Thanks to samkys, all versions now also support building and running a Docker container, for those of you trying to run the wrong versions of ROS on the wrong OS 
I also have to thank tony2guo for adding base url support, which essentially lets you namespace the browser path, and of course v-kiniv for his continuing help in integrating RWS.
Etc.
And there’s of course a lot of gradual improvements in general stability, rendering accuracy, speed, etc. There is also a github wiki now that contains everything from introductory to more esoteric info.
In Conclusion?
Well there’s still a lot left to do, features and visualizers to add, widgets to rework, performance to improve, bugs to fix, Firefox rendering to speed up. If anyone feels like helping along or has a good idea, I’m always up for a code review
1 post - 1 participant
https://discourse.ros.org/t/vizanti-mission-planner-jazzy-release-rws-other-news/40333
ROS Discourse General: I'm giving a talk on ROS to an Open Automation Club today at 1 PM
Sorry that this is short notice, but I’m giving a presentation about ROS to a club that meets online monthly to discuss laboratory automation. I’ll warn you in advance that I am NOT an expert in ROS, but I know enough that I wanted to talk about it. If anyone is available, you can find information here: Robot Operating System: October 28 with Andy Gross
And the link is here:
Feel free to stop by and possibly correct me on anything I miscommunicate!
1 post - 1 participant
https://discourse.ros.org/t/im-giving-a-talk-on-ros-to-an-open-automation-club-today-at-1-pm/40319
ROS Discourse General: Guest Talk by Julien Enoch - Cloud Robotics WG Meeting 2024-11-04
Please come and join us for this coming meeting at 1700-1800 UTC on Monday 4th November 2024, where Julien Enoch will be talking about Eclipse Zenoh and its offering for Cloud Connectivity.
Julien is a a Senior Solutions Architect at ZettaScale Technology and Eclipse Zenoh committer. He will talk about the Zenoh protocol, which can run everywhere, from micro-controllers to the Cloud; over TCP, UDP, QUIC, and Websockets. Zenoh provides a software router that can be deployed in any Cloud instance such as AWS EC2, and that can route the protocol between different subsystems. This talk will cover how this is particularly helpful for Connectivity in Cloud Robotics.
Last meeting, we had a general catch-up and a discussion about the current progress of the working group. If you’re interested to see our discussion, please check the meeting recording.
If you are willing and able to give a talk on cloud robotics in future meetings, we would be happy to host you - please reply here, message me directly, or sign up using the Guest Speaker Signup Sheet. We will record your talk and host it on YouTube with our other meeting recordings too!
The meeting link is here, and you can sign up to our calendar or our Google Group for meeting notifications.
Hopefully we will see you there!
1 post - 1 participant
https://discourse.ros.org/t/guest-talk-by-julien-enoch-cloud-robotics-wg-meeting-2024-11-04/40303
ROS Discourse General: Announcing `swarm_sync_sim`: a synchronized (lock-stepped) numerical simulation platform for multi-robot swarm systems based on ROS
Hey everyone, I would like to announce my recent ROS package kit swarm_sync_sim for multi-robot simulation:
This simulator supports PX4 rotor UAVs, Tello UAVs, wheel UGVs And fixed-wing UAVs. It is lightweight (low cpu consumption), scalable (tested with 100+ nodes) and fast (up to 10x acceleration).
It is suitable for simulating motion planning and control algorithms of multi-robot systems based on ROS, while the code can be directly used in real experiments with only slight modifications.Hope it will help multi-robot researchers.
1 post - 1 participant
https://discourse.ros.org/t/announcing-swarm-sync-sim-a-synchronized-lock-stepped-numerical-simulation-platform-for-multi-robot-swarm-systems-based-on-ros/40296
ROS Discourse General: Hardware Acceleration WG still active?
Hi, I just wanted to ask since the last meeting was mid of 2023 if this group is still active and if any further meetings are planned?
2 posts - 2 participants
https://discourse.ros.org/t/hardware-acceleration-wg-still-active/40286
ROS Discourse General: ROS 2 Migration Sprint
Hello everyone,
With 7 months left before the Noetic EoL and as a way to conclude this year’s edition of ROSCon, I was wondering if there are any open source projects that require help to migrate to ROS 2?
Otherwise, I also know that there are projects that are searching for contributors, especially for documentation. If you’re maintaining or contributing to a ROS-related open-source project with good first issues for new contributors, please share the link to your project here 
.
For example, here is a link on the ROS 2 Documentation Website with tips for contributing to the ROS 2 project.
Thanks !
2 posts - 2 participants
https://discourse.ros.org/t/ros-2-migration-sprint/40241
Isaac Saito: To rename ROS package systematically
Not specific to ROS, but still nice to have a memo like this for myself.
A couple of scripts can be used when you change the name of your ROS package "foo" to "bar".
1: cd /tmp && cp -R `rospack find foo` .
2: (shopt -s nullglob && _() { for P in "$1"*/; do Q="${P//[Ff][Oo][Oo]/bar}"; mv -- "$P" "$Q"; _ "$Q"; done } && _ ./)
3: find . -type f -print0 | xargs -0 sed -i 's/foo/bar/g'
Line by line:
- At first line, you copy the entire package to somewhere safe; this prevents changing CVS data (.git, .svn etc.) without knowing.
- 2nd line is influenced by this thread
- So as the 3rd line (this thread)
If you want to change the packages you've already "released", see this thread.
----
Update 2024/10/21 If the targeted files are under (a local) git repository, there's much more user-friendly command (thanks to superuser.com#1110337).
git grep -lz foo | xargs -0 sed -i '' -e 's/foo/bar/g'
http://ros-logger.blogspot.com/2015/09/to-change-ros-package-name.html
ROS Discourse General: 🇧🇷 ROS Meetup Recife, Brazil 2024 @ Rec'n'Play
We are excited to announce the ROS Meetup Recife 2024, part of the larger Rec’n’Play festival, taking place in Recife, Brazil. This meetup aims to strengthen the ROS community in Brazil, promote ROS development, and showcase exciting local projects. It’s a fantastic opportunity for researchers, companies, students, and anyone interested in robotics to connect, collaborate, and share knowledge.
Whether you’re a ROS beginner or an experienced developer, this event will have something for everyone!
Event Highlights:
- Workshops on Autonomous Mobile Robots (AMRs)
- Unmanned Aerial Vehicles (UAVs) demonstrations
- Hands-on sessions with Robotic Arms
- Training with MoveIt for robotic motion planning
- Live robot exhibitions
The event offers an excellent chance to network, learn, and be inspired by the latest innovations in robotics.
When?
- ROS Meetup Recife 2024 will be part of the Rec’n’Play festival from 07 to 08 of November.
Where?
- Recife, Brazil The Event will be held on Porto Digital. Additional information and the precise lectures and workshops’ rooms are available at website.
How to participate:
To register for the event and see the full agenda, visit www.recnplay.pe.
We warmly invite the local and international ROS community to join us for this exciting event in Brazil. Let’s build the future of robotics together!
For more details, check out our event page: ROS Meetup Recife 2024.
1 post - 1 participant
https://discourse.ros.org/t/ros-meetup-recife-brazil-2024-recnplay/40208
ROS Discourse General: :free: ROSCon 2024 Live Stream
The free ROSCon 2024 live stream page is up! The show should be active during ROSCon hours (9am-6pm CEST) from 2024-10-22T07:00:00Z UTC→2024-10-23T16:00:00Z UTC. You can convert your time zone to CEST here.
- Day 1 Primary Live Stream
- Day 1 Secondary Live Stream (Now Live!)
- Day 2 Primary Live Stream
- Day 2 Secondary Live Stream
- ROSCon Stream Page
- ROSCon 2024 Schedule
Heads up, the link for the live stream is going to change between days. I’ll update Discourse when I get the link.
Videos will be posted 2-3 weeks after ROSCon. We would really appreciate it if you could help us spread the word about the free live stream.
Thanks to our friends at AMD for making the free live stream possible!
18 posts - 11 participants
https://discourse.ros.org/t/roscon-2024-live-stream/40202
