May 16, 2025
Summer Hackathon with ROSCon 2025 Awards

Dear Open Robotics Community,

I would like to suggest organizing a Summer Hackathon from June to August 2025 to boost contributions to the ROS ecosystem during the summer period.

Many students and contributors have more free time during summer, making it the perfect opportunity to engage them in open-source development.

Key Highlights:

  • Timeline: June → August 2025
  • Focus: Contributions via GitHub issues and pull requests across ROS, Gazebo, Ros-controls, and related projects.
  • Community Engagement: Open to everyone students, researchers, hobbyists, and professionals.
  • Recognition: Winners selected by a review panel and announced at ROSCon 2025.

This would be a great way to strengthen community involvement, discover new talent, and accelerate development across the ecosystem.

2 posts - 2 participants

Read full topic

by yassine_cherni on May 16, 2025 09:26 PM

ROS News for the Week of May 12th, 2025

ROS News for the Week of May 12th, 2025


Are you heading to ICRA 2025 in Atlanta! Thanks to support from our friends at Intrinsic, PAL Robotics, and Foxglove we’ve organized a Kilted Kaiju launch party and ROS meetup at ICRA 2025 in Atlanta


Europe - The Final Countdown (Official Video)

The final Noetic Sync will be on 2025-05-29. It is the final countdown for ROS 1!


This week I was at Automate / ROS Industrial Annual meeting in Detroit. We had a fantastic ROS meetup thanks to help from PickNik and ROS Industrial.

:tada: The big news out of ROS Industrial is that Fanuc now has an official ROS 2 driver! You need to ask your Fanuc rep for the details and source code. Want to know more about ROS support for various arm vendors? Check out this compatibility guide from PickNik.



A team at UMass Lowell, Rutgers, WPI, Yale, and University of South Florida have just launched robot-manipulation.org. This new website is a one stop shop for all things open source manipulation.



Two weeks from today join us for an Edinburgh ROS Meetup and ROS 1 wake.



:clap: ROSCON :clap: 2025 :clap: TALK :clap: PROPOSALS :clap: ARE :clap: DUE :clap: IN :clap: TWO :clap: WEEKS! :clap:

Events

News

ROS

Got a Minute? :alarm_clock:

We could sure use your help with the following issues: :heart:

1 post - 1 participant

Read full topic

by Katherine_Scott on May 16, 2025 04:28 PM

New packages for Humble Hawksbill 2025-05-16

Package Updates for humble

Added Packages [33]:

  • ros-humble-autoware-utils-debug: 1.4.0-1
  • ros-humble-autoware-utils-diagnostics: 1.4.0-1
  • ros-humble-autoware-utils-diagnostics-dbgsym: 1.4.0-1
  • ros-humble-autoware-utils-geometry: 1.4.0-1
  • ros-humble-autoware-utils-geometry-dbgsym: 1.4.0-1
  • ros-humble-autoware-utils-logging: 1.4.0-1
  • ros-humble-autoware-utils-logging-dbgsym: 1.4.0-1
  • ros-humble-autoware-utils-math: 1.4.0-1
  • ros-humble-autoware-utils-math-dbgsym: 1.4.0-1
  • ros-humble-autoware-utils-pcl: 1.4.0-1
  • ros-humble-autoware-utils-rclcpp: 1.4.0-1
  • ros-humble-autoware-utils-system: 1.4.0-1
  • ros-humble-autoware-utils-system-dbgsym: 1.4.0-1
  • ros-humble-autoware-utils-tf: 1.4.0-1
  • ros-humble-autoware-utils-uuid: 1.4.0-1
  • ros-humble-autoware-utils-visualization: 1.4.0-1
  • ros-humble-autoware-utils-visualization-dbgsym: 1.4.0-1
  • ros-humble-broll: 0.1.0-1
  • ros-humble-broll-dbgsym: 0.1.0-1
  • ros-humble-mocap-optitrack: 1.0.1-1
  • ros-humble-mocap-optitrack-dbgsym: 1.0.1-1
  • ros-humble-mola-input-video: 1.7.0-1
  • ros-humble-mola-input-video-dbgsym: 1.7.0-1
  • ros-humble-rai-interfaces: 0.2.2-1
  • ros-humble-rai-interfaces-dbgsym: 0.2.2-1
  • ros-humble-sicks300-2: 1.3.3-1
  • ros-humble-sicks300-2-dbgsym: 1.3.3-1
  • ros-humble-tsid: 1.8.0-1
  • ros-humble-tsid-dbgsym: 1.8.0-1
  • ros-humble-turtlebot3-autorace: 1.2.2-1
  • ros-humble-turtlebot3-autorace-camera: 1.2.2-1
  • ros-humble-turtlebot3-autorace-detect: 1.2.2-1
  • ros-humble-turtlebot3-autorace-mission: 1.2.2-1

Updated Packages [304]:

Removed Packages [3]:

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

  • Adam Dabrowski
  • Adria Roig
  • Alberto Tudela
  • Alejandro Hernandez
  • Andrea Capodacqua
  • Antonio Brandi
  • Apex.AI, Inc.
  • Austin Hendrix
  • Bence Magyar
  • Bernd Pfrommer
  • Brandon Ong
  • Daan Wijffels
  • Davide Faconti
  • Emerson Knapp
  • Felix Exner
  • Guilhem Saurel
  • Jacob Perron
  • Jian Kang
  • Jordan Palacios
  • Jordi Pages
  • Jose Luis Blanco-Claraco
  • Jose-Luis Blanco-Claraco
  • Justin Carpentier
  • Louise Poubel
  • Luis Camero
  • M. Fatih Cırıt
  • Mabel Zhang
  • Mamoru Sobue
  • Miguel Company
  • Noel Jimenez
  • Olivier Kermorgant
  • P. J. Reed
  • Pyo
  • Rob Fisher
  • Roni Kreinin
  • Stefan Laible
  • Steve Macenski
  • Takagi, Isamu
  • Team Spatzenhirn
  • Tibor Dome
  • Tim Clephas
  • Timo Röhling
  • Tony Baltovski
  • Tully Foote
  • Vincent Rabaud
  • Vladimir Ermakov
  • Víctor Mayoral-Vilches
  • Yue Erro
  • Yutaka Kondo
  • kminoda
  • mitsudome-r

1 post - 1 participant

Read full topic

by christophebedard on May 16, 2025 03:23 PM

Next Client Library WG Meeting: Friday 16th May 2025 8AM PT

Hi,

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

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

1 post - 1 participant

Read full topic

by mjcarroll on May 16, 2025 12:50 PM

May 15, 2025
New Packages for Noetic 2025-05-15

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

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

Package Updates for ROS Noetic

Added Packages [3]:

Updated Packages [94]:

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:

  • Atsushi Watanabe
  • Dirk Thomas
  • Felix Exner
  • G.A. vd. Hoorn
  • G.A. vd. Hoorn (TU Delft Robotics Institute)
  • Geoffrey Biggs
  • Isaac I.Y. Saito
  • Martin Günther
  • Martin Pecka
  • Michael Carroll
  • Tibor Dome
  • Vincenzo Di Pentima

1 post - 1 participant

Read full topic

by sloretz on May 15, 2025 11:50 PM

May 14, 2025
Join us for the Robotics in Africa Forum at ICRA 2025 in Atlanta

Hi Everyone,

Please join us for the Robotics in Africa Forum at ICRA 2025 with the theme: Harnessing Learning, Data, Foundation Models and Open Source: How African Scientists are Advancing Robotics Research.

The forum will be held on Wednesday, May 21 from 9:30am - 12:15pm

There are options for both in-person attendance and virtual participation.

Please share this call with faculty, grad students and collaborators in your network.

Thank you.

1 post - 1 participant

Read full topic

by SimeonOA on May 14, 2025 09:33 PM

ROS Meetup at ICRA 2025 in Atlanta

Hi Everyone!

Thanks to the generous support from our from our friends at Foxglove, PAL Robotics, and Intrinsic, I am happy to announce that we’ve organized a ROS Meetup / Kilted Kaiju Release Party at ICRA 2025 in Atlanta on 2025-05-21T21:00:00Z UTC2025-05-21T04:00:00Z UTC at the Wild Leap Brewery.

Space is limited so please RSVP. More importantly, only RSVP if you plan on actually showing up in person.

1 post - 1 participant

Read full topic

by Katherine_Scott on May 14, 2025 02:28 PM

May 13, 2025
Ideas for Cloud Robotics Guides | Cloud Robotics WG Meeting 2025-05-19

The next meeting for the Cloud Robotics Working Group will be at 2025-05-19T16:00:00Z UTC→2025-05-19T17:00:00Z UTC, where we will discuss possible subjects for Cloud Robotics guides to be published on https://cloudroboticshub.github.io. We will attempt to come up with different subjects and rank/categorise them based on how useful they will be to the community.

Last meeting, we continued our prior discussion on collecting and uploading robot data to the cloud. If you would like to see the meeting, the recording is available on YouTube.

The meeting link 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

by mikelikesrobots on May 13, 2025 10:22 AM

Planned changes to the OSRF Discourse(s)

Dear Community,

We are excited to announce a new chapter in discussions for the OSRF’s open-source projects! To foster collaboration and communication between projects, we have decided to consolidate the disparate discussion forums used by our projects into a single Discourse instance. This transition aims to create a vibrant, unified space where all involved in any of our projects, in any way, can engage with each other, share ideas, learn from each other, and work together for the good of all OSRF projects.

As part of this process, we will be reorganising the categories we use in Discourse to organise discussion topics, in order to better reflect the needs of the projects and of the community. As always, our goal is to ensure that everyone feels welcome to participate actively (and constructively) in the community, and can find the discussions that matter most to them.

This work is expected to begin in June, 2025. If you have any questions or feedback about this plan, please respond to this post, or reach out to community@openrobotics.org. The sooner you get your feedback to us, the faster we can integrate it, but in general feedback should be provided by the 1st of June.

1. What will happen

  1. The ROS Discourse instance will be transformed into the Open Robotics Discourse.
    1. New categories will be created to restructure the topics for all projects (see section 3, below).
    2. Existing categories that will no longer be used will be archived, although some may have their content moved to one of the new categories.
    3. The topics with a matching sub-category under the ROS category (see section 3, below) at the Open Robotics Discourse will be moved to that category.
  2. The Gazebo Discourse instance will be closed down and its content will be migrated to the Open Robotics Discourse (former ROS Discourse). We are working with the Discourse migration team to make this happen, so the timeline for this is not yet set. However, it will not happen any earlier than the 16th of June.
    1. The topics with a matching sub-category under the Gazebo category (see section 3, below) at the Open Robotics Discourse will be moved to that category.
    2. The remaining topics will be placed into the Gazebo/General category, ensuring that they remain findable and can still be posted to, if the conversation is on-going.
  3. The Open-RMF Discussion page at GitHub will be closed to new topics.
    1. We are still working on possible solutions for archiving the conversations at this page into a read-only and searchable form outside of GitHub, as GitHub does not itself provide this capability in an easy-to-use way.
    2. If it is possible to do with reasonable effort, we will copy the existing topics at GitHub into the Open Robotics Discourse. However, this is a best-effort and non-urgent task due to the amount of effort potentially required. (If you know of or are interested in writing us a script to do this copying, please speak up!)
  4. The existing Discourse subdomains (discourse.ros.org and community.gazebosim.org) will go through automatic URL rewriting so that an existing external link to a topic on the ROS or Gazebo Discourse will be directed to that topic’s new location on the Open Robotics Discourse.

There will additionally be some changes to how we moderate the forums.

  1. The existing moderator teams from the disparate forums will be merged - since they are very nearly the same people anyway. We will be posting an introduction to your moderators shortly after the Open Robotics Discourse has been set up.
  2. Each project category (see section 3, below) will additionally have one or two people from the project’s PMC who are moderators, in order to provide more contextual moderation when necessary - particularly in the PMC discussions area.
  3. As always, we will heavily rely on community flags rather than proactive moderation by patrolling guards. If you see something that you feel is against the community guidelines, or just not good for the community in general, flag it! This will bring it to the attention of the moderators, who can then review it and take any appropriate action. If enough people flag a post before a moderator gets to it, the system will also take automatic action.

2. When will it happen

These changes will be made in stages throughout the month of June, 2025. The changes to the ROS Discourse to transform it into the Open Robotics Discourse will be made first, in the first two weeks of June, followed by migrating data from the Gazebo Discourse, and finally shutting down the other discussion forums.

The migration of content from the Gazebo Discourse will be performed by the Discourse migration team, which is a contracted service. For this reason, the timeline of this task is not yet pinned down. We do not plan for it to happen any earlier than the 16th of June.

The changes to the ROS Discourse should be the least disruptive, as the Discourse instance itself will not be removed, just re-configured. You will hopefully not need to update your bookmarks if you are used to going straight to a particular category, as the URL rewriting should take care of that.

3. Proposed categories at the Open Robotics Discourse

The following categories are going to be created.

  • One category per project (ROS, Gazebo, Open-RMF, ROS Controls, and Infrastructure), containing:
    • PMC Discussions
      • For PMC Members and Committers to discuss ongoing work beyond the scope of GitHub issues and PRs.
      • This category can be viewable by anyone, and in general anyone can reply to topics (so that the whole community can participate in discussions), but only PMC Members and Committers will have access to create new topics.
    • Announcements
      • For the posting of project news (new releases, upcoming deadlines, weekly updates, etc.) and PMC meeting minutes.
      • Replies to the news posts by anyone will be allowed, but starting topics will be restricted to news posters.
    • REPs
      • A category to discuss proposed REPs (or what will replace them later this year - watch this space!) relevant to this project.
    • Packing and Release Management
      • For public discussion of packaging and release management
      • Only created for projects where it makes sense.
    • General
      • For general discussion relevant to this project, for topics that don’t fit in one of the above categories.
    • For the Infrastructure project only:
      • Buildfarm
        • For discussion of use and maintenance of the buildfarm.
      • Mirrors
        • For discussion by maintainers of mirrors.
  • OSRA Announcements
    • For the posting of TGC minutes and other announcements by the OSRA.
    • Anyone can reply to a topic, but only OSRA officers will be able to start new topics.
  • Community News
    • A category for news about and from the community.
    • News posters will be able to post new topics.
    • Everyone will be able to reply to topics.
    • Anyone will be able to post a new topic about some news from the community they wish to share; the new topic will initially be hidden. News posters will review each topic and approve those that are relevant to the Open Robotics Discourse and the community for public publication.
  • Projects
    • For anyone to post about something they’ve built using OSRF projects. Tell us about your awesome robot gardener project, so @gbiggs can build one, too, and finally have plants that don’t die!
  • TurtleBot
    • For discussing working and learning with any of the OSRF’s TurtleBots.
  • Jobs
    • For posting job advertisements relevant to OSRF projects.
  • Local User Groups
    • One subcategory for each local user group, created on request.
    • Intended to be used for discussion in that user group’s preferred language.
    • The existing local user group categories will be moved here.
  • Community Groups
    • One subcategory for each community group that wants one, created on request.
    • Intended to be used for discussion relevant specifically to that community group’s topic.
    • Some of the existing categories (such as maritime robotics and Nav2) at the ROS Discourse can be moved here. We would like to know that they are wanted, however. If you are involved in a community group using an existing category on the ROS Discourse, let us know!

If you see a problem or think of a missing category, now is your chance to let us know by replying to this topic, or contacting us at community@openrobotics.org.

Update 2025/05/14: We no longer plan to create project-specific sub-domains. There are concerns about causing confusion for people not familiar with Open Robotics, and we want to focus on URL rewriting for discourse.ros.org.

6 posts - 3 participants

Read full topic

by gbiggs on May 13, 2025 08:37 AM

GPSFix vs. NavSatFix

TLDR; Which of these alternative message types for satellite navigation data are people using today?

As some of you know we have written software that fuses satellite navigation data with LIDAR and camera data and puts it all in to a particle filter based navigation stack that runs on a Raspberry Pi. In the current software this was implemented using the NavSatFix messages.

We are doing a hardware upgrade cycle across all our robots and will be building a high performance satellite navigation module, that connects with a Raspberry pi and publishes Satellite Navigation fix data as a topic under ROS2. In addition to being a multi-constellation module that can, for example, make use of newer high accuracy modes in Galileo, the new module will be dual antenna and thus, potentially, will be able to provide heading and other data that is not supported by the NavSatFix messages. What does everyone use for the satellite navigation message types? What do they want?

We can rewrite all the current software, including our indoor/ourdoor nav. stack, to use GPSFix messages but before we do I thought I’d ask people, what are you all using? What would be most useful for the community? Are there other standards that I should think about?

22 posts - 7 participants

Read full topic

by davecrawley on May 13, 2025 08:06 AM

Launching Robot-Manipulation.org! Your resource for open-source and benchmarking for robot manipulation

Launching Robot-Manipulation.org!

Your resource for open-source and benchmarking robot manipulation, replete with repositories of software components, hardware designs, object datasets, benchmarking protocols, events, and more!

robot-manipulation_web_banner_500px_black_transparent

This website serves as a landing page for open-source and benchmarking in robot manipulation, continuously updated as new research and assets are published. We’re actively building repositories for grasp planning, motion planning, learning, simulation, objects and artifacts, benchmarking tools, protocols, leaderboards, and events like workshops and competitions. Check it out!

:robot: Robot-Manipulation.org is constantly evolving, but we can’t build it alone. As a community resource, we rely on researchers like you! Are we missing something? Do you want to see your research contributions featured? Use this submission form: https://forms.gle/LHrtmDpm82X4qrDk6

:robot: Have an event coming up related to robot manipulation that should be featured on our Robot Manipulation Events Calendar? Submit it here: https://forms.gle/PfiSRjcuQnavbPNS9


Robot-Manipulation.org is also the home of the COMPARE Ecosystem, a project aimed at creating a greater cohesion between open-source products towards improving the modularity of software components in the robot manipulation pipeline for more effective performance benchmarking. Learn more by visiting the website!

:robot: Want to stay up-to-date on the latest in robot manipulation research and the COMPARE Ecosystem?
• Collaborate with other researchers by joining the COMPARE Slack workspace! Slack
• Receive announcements in your inbox by joining the COMPARE Google Group! https://tinyurl.com/compare-group


See you at ICRA!


Adam Norton, Community Facilitator, COMPARE Ecosystem
Improving Open-Source and Benchmarking for Robot Manipulation
https://robot-manipulation.org/
compare.ecosystem@gmail.com

1 post - 1 participant

Read full topic

by COMPARE_Ecosystem on May 13, 2025 06:03 AM

Remote (internet-based) control of ROS 2-based robots

What are the best practices for enabling remote (internet-based) control of ROS 2-based robots through web or mobile applications?

I’m aware of the following options:

•	rosbridge
•	MQTT (though ROS 2 doesn’t natively support MQTT communication)

Are there any recommended approaches or best practices for this use case?

3 posts - 3 participants

Read full topic

by Raman on May 13, 2025 04:25 AM

May 12, 2025
Diagnostic Remote Logging Announcement

Want to do more with your robot’s diagnostics data?

Thanks to the excellent contributions from @dwffls, you can now log diagnostics data from ROS 2 systems directly to an InfluxDB using the new diagnostic_remote_logging package.

This enables long-term trend analysis, visualisation in Grafana, and makes it easier to monitor larger deployments across multiple systems.

The diagnostic_remote_logging package is available in all current ROS 2 distributions.

We’d love to hear your feedback—try it out and let us know what you think!

1 post - 1 participant

Read full topic

by ct2034 on May 12, 2025 12:13 PM

OSRF Adopts Policy on Use of Generative AI in Contributions

As the use of Generative AI tools becomes increasingly prevalent in software development, open-source projects face unique challenges and opportunities. These tools can enhance productivity, foster creativity, and streamline workflows, but they also raise important questions regarding ownership, licensing, attribution, and ethical use of generated content. As the OSRF’s open-source community embraces the capabilities of Generative AI, developing a comprehensive policy has become crucial. This will not only safeguard the integrity of the projects but also foster an inclusive and innovative environment for all contributors.

In response to requests from the community, the Open Source Robotics Alliance’s Technical Governance Committee (TGC) chartered a Technical Committee (TC). This TC investigated how other open source foundations and projects are approaching the unique challenges of Generative AI, and drafted a policy for the OSRF. The policy has now been reviewed and approved, and has been publicly posted in the OSRF’s Policies and Procedures repository. It is available in PDF form, and is also summarised below.


The OSRF allows the use of Generative AI tools in contributions (code, docs, etc.) but contributors are responsible for:

  • Understanding the tools and their limitations.
  • Ensuring the output is high-quality, original, and doesn’t violate copyright.
  • Clearly disclosing the use of AI tools in their contributions.
  • Verifying the accuracy and appropriateness of AI-generated content.

Basically, use AI responsibly, be transparent, and make sure your contributions are still top-notch!

5 posts - 3 participants

Read full topic

by gbiggs on May 12, 2025 01:30 AM

May 11, 2025
Manipulation in ROS2 (2025): What’s everyone using these days?

Hey everyone,

I’ve been exploring manipulation options and wanted to check in with the community - what’s everyone using in 2025?

From the classical side, here’s what I’ve seen so far:

  • MoveIt2
  • cuRobo
  • Tesseract

Now on the learning side, I’ve come across:

  • Imitation Learning
  • Genetic Algorithms and other evolutionary strategies

I’m curious:
:brain: What’s the state of the art right now in both classical and learning-based manipulation?

Would love to hear what folks are using, especially in real-world deployments or sim-to-real setups.
Any insight, links, or personal experiences would be super helpful.

Thanks in advance!

2 posts - 2 participants

Read full topic

by elsayedelsheikh on May 11, 2025 10:12 PM

May 09, 2025
ROS News for the week of May 5th, 2025

ROS News for the week of May 5th, 2025


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



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





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


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


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


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

Events

News

ROS

Got a minute?

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

1 post - 1 participant

Read full topic

by Katherine_Scott on May 09, 2025 07:46 PM

May 08, 2025
New Packages for Noetic 2025-05-08

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

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

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

Package Updates for ROS Noetic

Added Packages [0]:

Updated Packages [175]:

Removed Packages [0]:

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

  • Aaron Blasdel
  • Analog Devices
  • Chris Lalancette
  • Claire Wang
  • Dharini Dutia
  • Dirk Thomas
  • Dorian Scholz
  • Felix Exner
  • Geoffrey Biggs
  • Guglielmo Gemignani
  • Guillaume Autran
  • Isaac I.Y. Saito
  • Ivan Paunovic
  • Jacob Perron
  • Jose-Luis Blanco-Claraco
  • Koji Terada
  • Mabel Zhang
  • Martin Günther
  • Mathieu Labbe
  • Michael Carroll
  • Michael Jeronimo
  • Michel Hidalgo
  • Mikael Arguedas
  • Robert Haschke
  • Roberto G. Valenti
  • Scott Logan
  • Steven! Ragnarök
  • Tully Foote
  • Vincent Rabaud
  • Vladimir Ermakov
  • William Woodall
  • ipa-lth

1 post - 1 participant

Read full topic

by sloretz on May 08, 2025 10:51 PM

ROS2 Hosting / Open Source Lab

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

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

3 posts - 3 participants

Read full topic

by TSNoble on May 08, 2025 11:30 AM

May 07, 2025
Space Station OS v0.8.2 released - ROS 2 update with space station control systems and simulation

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

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

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

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


What’s included in v0.8.2

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

  • Modular modeling of a space station
    Define sensor and actuator configurations using structured descriptions

  • Physics simulation

    • Attitude control logic based on torque models
    • Gravity-gradient disturbance modeling
    • Parameterized dynamics for CMGs, enabling system tuning and integration
    • Thruster support for backup and hybrid control
  • Ground station interface

    • Database logging and retrieval
    • Integration with visualization tools (e.g., yamcs)
  • Simulation support

    • Basic physics simulator
    • Software-in-the-loop (SILS) structure to enable integration with external software
  • ECLSS (Environmental Control and Life Support System)

    • Initial integration under way

See full release notes here:


What’s next in v0.8.3

  • CMG unloading strategies
  • Thruster reboost modeling
  • Additional external torques (e.g., air drag, magnetic effects)
  • Runtime updates of mass properties
  • Full-loop ECLSS simulation

About SSOS

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

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

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


How to get involved

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

  • Mechatronics and physical modeling
  • Autonomous control and planning
  • ROS2-based architecture and integration
  • SILS/HILS development
  • Environmental systems and closed-loop simulation
  • Data handling and visualization for robotic platforms

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

Official site:

1 post - 1 participant

Read full topic

by yuyuqq on May 07, 2025 11:50 PM

Looking for Noetic Tshirt

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

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

2 posts - 2 participants

Read full topic

by MJavadZallaghi on May 07, 2025 08:52 AM

ROS 2 L Name Brainstorming

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

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

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

Here are the existing ROS 2 names and code names.

  • Ardent Apalone - ardent
  • Bouncy Bolson - bouncy
  • Crystal Clemmys - crystal
  • Dashing Diademata - dashing
  • Eloquent Elusor - eloquent
  • Foxy Fitzroy - foxy
  • Galactic Geochelone - galactic
  • Humble Hawksbill - humble
  • Iron Irwini - iron
  • Jazzy Jalisco - jazzy
  • Kilted Kaiju - kilted

And here are the ROS 1 names and code names.

  • Boxturtle - boxturtle
  • C Turtle - cturtle
  • Diamondback - diamondback
  • Electric Emys - electric
  • Fuerte - fuerte
  • Groovy Galapagos - groovy
  • Hydro Medusa - hydro
  • Indigo Igloo - indigo
  • Jade Turtle - jade
  • Kinetic Kame - kinetic
  • Lunar Loggerhead - lunar
  • Melodic Morenia - melodic
  • Noetic Ninjemys - noetic

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

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

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

79 posts - 58 participants

Read full topic

by mjcarroll on May 07, 2025 02:16 AM

May 06, 2025
Announcing "Maps": Show robots live on a map on the web

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

  • speed and access maps,
  • navigation plans and
  • laser scans.

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

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

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

Details

Demo:

Transitive Maps Capability Demo

2 posts - 2 participants

Read full topic

by chfritz on May 06, 2025 07:21 PM

May 05, 2025
Energy efficiency in ROS communication: a comparison across programming languages and workloads

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

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

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

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

4 posts - 4 participants

Read full topic

by ThiloZimmermann on May 05, 2025 03:44 PM

How should sensor descriptions be standardized?

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

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

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

1 post - 1 participant

Read full topic

by hijimasa on May 05, 2025 12:39 PM

May 04, 2025
Organizing a ROS Meetup in Boston

Update!

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

Notice

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

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

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

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

16 posts - 14 participants

Read full topic

by pitosalas on May 04, 2025 05:32 PM


Powered by the awesome: Planet