ROS Discourse · 实时热榜

Hi ROS Community! For years, there has been a strong and consistent demand for seamless Protobuf serialization in ROS/ROS 2. While there are excellent existing tools in the community, integrating them cleanly into a high-performance, production-ready pipeline often comes with friction. Today, we’re excited to introduce protoros2 — a middleware wrapper and orchestration engine designed to provide zero-intrusive protobuf support for ROS 2. ZhenshengLee/protoros2: use protobuf in ros2 without compr

Hi everyone, I would like to introduce ros2_cuda_ipc, an experimental ROS 2 library for sharing GPU-resident data between processes without copying it through CPU memory. github.com GitHub - dskkato/ros2_cuda_ipc: ROS 2/CUDA IPC support ROS 2/CUDA IPC support Motivation GPU-accelerated perception pipelines often separate camera or LiDAR preprocessing, DNN inference, visualization, and encoding into different components. Composable nodes can avoid inter-process copies, but they also place compone

Hello, and welcome back to This Week at Open Robotics HQ! Did you know we have 53 sponsors (and counting) for ROSCon Global ? And that each one of those sponsors needs assistance with logistics and planning and the like? And all of them are keen to learn more about, get intros to, and work with the community? Just keeping everything straight is practically a full-time job. We’re especially happy about how many OSRA members are increasing their community support by sponsoring ROSCon Global! Let’s

Hi everyone, Here is Simulation Demo 3 for QERRA-v2 Classical. In robotics, we take physical safety boundaries for granted — if a robot is about to hit a wall or a person, it stops. But in real-world HRI, moral boundaries carry just as much practical value. A robot that blindly executes a directive to coerce an employee, doctor analytics, or gaslight staff creates massive legal and operational fallout. Practicality and moral guardrails aren’t opposites — they are real-world allies for deploying

We’re planning for a Humble sync on Fri, Aug 7, 2026 4:00 AM UTC . There are currently 703 regressions and 477 packages to release. The very high number of regressions is due to an issue with low disk space on buildfarm agents. The infra team is working on it, so hopefully packages get successfully built over the next few days. Otherwise, I will push the sync date back a bit. We will start holding rosdistro PRs for the sync today ( Tue, Aug 4, 2026 4:00 AM UTC ) and will plan to do the sync on F

Hi Everyone, Quick reminder, the last day to purchase regular price tickets for ROSCon Global in Toronto is Tue, Aug 25, 2026 6:59 AM UTC . 1 post - 1 participant Read full topic

We are reviewing a compact robot compute enclosure that uses custom copper heat-spreading components. The hardware test plan tracks inlet and outlet temperature, coolant flow, hotspot sensors, load profile, and build revision. The manufacturing side also has constraints such as wall thickness, internal channels, and machining allowance. This engineering guide to pure-copper additive manufacturing is the background reference for the component design. For teams using diagnostic_msgs and rosbag2, d

Boston Robot Hackers is pleased share info about our August meeting: Topic: Forward & Inverse Kinematics: The Math: From joint angles to end-effector poses" Speaker: Shivam Chopra, PhD Date: August 6 2026 Time: 7:00pm to 9:00pm Location: Artisans Asylum, Alston, Boston Shivam will introduce the concepts of Forward and Inverse Kinematics, explain where it fits into robotics (and how important it is!) and get into technical details of how to apply it and how the math works. Also featured two light

Younuo Zhixing (UnoMove) | Build the “Brain Architecture” for Robots Vision-Only · Embodied AI · Edge-Deployed Large Models · Real-World Deployment Website: younuozhixing.com ｜Location: Suzhou, China Who We Are Younuo Zhixing (UnoMove) — a vision-only, no-LiDAR-stacking embodied AI company. While others “patch” perception with LiDAR, we use cameras + AI to make robots truly understand the world . Our core product, UnoBox , is more than an edge-computing box — it’s a digital brain that gives robo

Hello everyone, Some of you may remember my earlier post about curobo_ros , a lightweight ROS 2 wrapper around NVIDIA’s cuRobo planner. I’m happy to share that the package has now been migrated to cuRobo v2 (v0.8.0) , which was a major rewrite upstream, and the wrapper has been updated accordingly. What’s new in v2: Native perception pipeline : cuRobo v2 ships a block-sparse TSDF + GPU ESDF mapper built in, so we could drop our homegrown nvblox / nvblox_torch forks entirely. Depth cameras now fe

Hi everyone, I’m new to Nav2 and I am currently using Isaac Sim as my simulation platform. The AMR is the official Nova Carter, equipped with a single front-mounted 2D LiDAR. Navigation works well in a relatively small indoor factory environment. The AMR follows the planned path correctly and AMCL localization appears stable. However, after switching to the larger road environment shown in the attached images, I started experiencing some unusual behavior: The AMR moves in a zigzag pattern during

Hi Gazebo Community! This week’s meeting was held on Mon, Aug 3, 2026 6:00 PM UTC and the following is a summary: PMC Business None New agenda items ROSCon PMC Dinner Meeting : Confirmed a PMC dinner meeting on Mon, Sep 21, 2026 12:00 AM UTC (adjusting evening time to accommodate travel schedules). Location suggestions and a poll to finalize timing are being coordinated on Zulip. Buildfarm Security & Infrastructure : Scraper / Crawler Mitigation : Jenkins buildfarm scrapers caused performance is

MantaClaus runs its entire autonomy stack on a Raspberry Pi , a Blue Robotics Navigator Flight Controller , and a single simple USB webcam . I built it independently on a tight budget for the Singapore Autonomous Underwater Vehicle Challenge (SAUVC), where it managed to snag 2nd place ! Key Features & Architecture Software: Built on ROS 2 . I extended and forked the ROS 2 BlueOS Extension to run a containerized environment inside BlueOS for seamless deployment and node management. Vision & Navig

Hello Gazebo Community, I am the author of the Localize The Docs organization. And I’m glad to announce that the gazebosim-docs-l10n project is published now: Preview: gazebosim-docs-l10n Crowdin: gazebosim-docs-l10n GitHub: gazebosim-docs-l10n The goal of this project is to translate The Gazebo Documentation into multiple languages. Translations are contributed via the Crowdin platform, automatically synchronized with the GitHub repository, and can be previewed on GitHub Pages. We welcome anyon

Meeting Link Calendar Link Thu, Aug 6, 2026 3:00 PM UTC This year the Open-RMF project participated in Google Summer of Code with two contributors to help with different aspects of the Next Generation initiative. At this session of the Interoperability Special Interest Group, these contributors will present what they’ve done so far. 1. Zhen Wan: Crossflow Diagram Editor Crossflow is a recently developed flow-based programming library aimed at making highly asynchronous service-driven systems eas

Join an Industry Leader in Robotics RealMan Intelligent Technology (Beijing) Co., Ltd. develops robotic technologies that are widely recognized as setting the benchmark in the industry. Our deployable robotic arms and actuator modules account for over 80% of the domestic market, reflecting both our technological leadership and manufacturing excellence. The role We are seeking a Technical Support Engineer to support our collaborative robot (cobot) products for customers across North America. This

We have been working on adding real-time functionality to rcl and rclcpp since 2022. In response to this proposal, we have created a new package that provides real-time functionality without changing the existing packages. esol-community/ros2_realtime_support Background The previous discussion is as follows: ROS lacks a unified mechanism to formally support real-time functionality, and we have tried to achieve this by adding functionality to rcl and rclcpp . On the other hand, it has been pointe

TL;DR : A workspace-level uv-managed venv works on stock apt-installed ROS 2 — including a PyTorch+CUDA node — but we hit five reproducible failure modes on the way (verified on Jazzy; none of the mechanisms are Jazzy-specific). Key measurement: the known shebang workaround ( [build_scripts] executable = /usr/bin/env python3 ) does not cover --symlink-install , so when colcon is launched from the system Python there is currently no complete workaround. Below are four minimal change proposals for

QERRA-v2 Classical is an open-source, fully explainable safety middleware layer designed to evaluate autonomous robot actions before execution. The architecture uses a two-layer design: QERRA-HSR (Physical Safety Layer): A zero-ML, pure Python module that evaluates physical hazard proximity and human distress signals to trigger immediate fail-closed safety halts. SEMEV-12 (Moral Deliberation Engine): A hybrid semantic-pattern engine that evaluates prospective natural-language tasks against 12 hu

Hi all, Robotics software engineering has an oddly scattered job market. Openings end up on a single university page, a company careers site, or a mailing list, and the people who’d be the right fit often never see them. There’s no obvious place to look if you specifically care about the software side of robotics: testing, verification, architecture, middleware, tooling, and so on. So the RoSE community (the Robot Software Engineering workshop, most recently at ICRA) has put together a small job

Not all roles are robotics-centred, some generic software. and DEFINITELY don’t need medical specialisation (I’m pure robotics).. But we all get to say we’re working on a medical robot Impactful roles on Aussie medical imaging robot! Jobs Many robotics engineers were excited to support Vexev’s mission after my ROSCon keynote - now we have space for more team members in Sydney. We work on cutting edge robotics in a real (=impactful) medical device that we are excitedly turning into an FDA-cleared

Many robotics engineers were excited to support Vexev’s mission after my ROSCon keynote - now we have space for more team members in Sydney. We work on cutting edge robotics in a real (=impactful) medical device that we are excitedly turning into an FDA-cleared product. Our robots have made people cry at the impact they will have in dialysis clinics Long-term this work will generalise to worldwide cardiovascular health. We proudly and (gratefully ) use ROS 2 but not all roles are robotics-centre

Our next meeting is on Monday. All supported combinations have been sync’d and the work for Navigation2, MoveIt2, and ros2_control has been merged in across all combinations. Related work includes adding support for PX4 via meta-px4 as well as improving the developer workflow through enhancements in the Oeros reference distro. Date/Time Monday, August 3rd, 2026 @ 3pm UTC, (5pm CEST / 11am EDT / 8am PDT) Google Meet Video call link: Google Meet meeting Dial-in numbers: https://meet.google.com/tel

ROS News for the Week of July 27th, 2026 ROSCon Japan in Tsukuba is happening next week! We’re really looking forward to seeing all of the cool projects happening in Japan right now. Our next ROS By-The-Bay will happen on Thursday, August 13th, at the InOrbit Robot Space in Mountain View. We’ve got some great speakers lined up, including InOrbit CEO Florian Pestoni, my colleague @Andrew_Symington , who will tease his new ROS Central Registry, and Ramon Yvarra, who helped build a working Johnny 5

Hi all, I’ve been working on a global planning engine aimed at warehouse/fleet deployments, and I just opened a free API tier. I’d love feedback from people running real Nav2 fleets. What it does You upload an occupancy grid once. It solves a field for your goal (charging station, pick station, dock), and from then on every path query — from any start cell — returns a strictly optimal path in microseconds, without re-searching the map. The pitch for fleet operators: the cost of global planning s

site: GitHub - yjphhw/ros2_pkg_create: A utility script for generating ROS 2 package templates that support both C++ and Python nodes, simplifying mixed-language development within a single package. · GitHub useage is very easy, just download the ros2_pkg_create.py and put in a workspace(direction), and run python3 ros2_pkg_create <package_name> such as create demo_pkg: python3 ros2_pkg_create demo_pkg output is : 正在生成混合功能包: my_pkg 已创建: src/my_pkg/CMakeLists.txt 已创建: src/my_pkg/package.xml 已创建:

Hello ROS2 community, I’m exploring a challenge that I believe will become increasingly important as ROS2-based autonomous systems move from development environments into large-scale real-world deployments. Today, ROS2 enables powerful robotic applications through communication, orchestration, and ecosystem tooling. However, as autonomy increases, teams are facing additional questions: How do we understand why an autonomous system made a specific decision? How do we determine whether an action s

Hi everyone, I’m curious about how other ROS 2 developers approach understanding a large or unfamiliar workspace. When joining an existing project or reviewing a large codebase, I often find myself asking questions like: Which packages depend on each other? Which nodes communicate together? What topics, services, and actions are used? Are there isolated nodes or communication issues? Does the implementation still match the intended architecture? How do you quickly get a high-level understanding

Framatome, Inc. Installed Base NDE services team in Lynchburg, VA, USA is hiring a Robotics Perception/Autonomy Software Engineer. This role is crucial for supporting the development of automated processes for non-destructive examination (NDE) that supports commercial nuclear power plants in USA, Canada, and Europe. We are looking for self-driven individuals who are eager to push the boundaries of NDE inspections. The position is on-site in Lynchburg, VA. Software Engineer - Robotic Autonomy and

Hello ROS Community, The OSRF Infrastructure Project is planning to update the Jenkins version of https://build.ros2.org as part of our ongoing efforts to maintain and improve the ROS buildfarm infrastructure. To facilitate this migration, the following services will experience downtime during the maintenance window: https://build.ros2.org (Jenkins) will be temporarily unavailable or in shutdown mode (not running jobs). The migration is scheduled to begin on Monday Mon, Aug 3, 2026 11:30 AM UTC

Motivation Since the Lyrical release, the client library working group has been considering various approaches to reduce the amount of bloat in rclcpp and rclpy , remove or re-implement half-baked features, make behavior more consistent and performant across the different client library implementations, and foster more code reuse. I want to propose a concretely scoped step in the direction of “Less is More” with what seems like a fairly obvious candidate for de-duplication. Currently, between rc

Been lurking here for a while, finally posting because this has been eating my week. We run a small fleet of AMRs (nothing fancy, mostly ROS 2 Humble on Jetson Orins with a couple of STM32s handling motor control and safety). The high level stack is fine, we push updates over the air and roll back if something misbehaves. The pain is the low level side. Every time we touch the microcontroller firmware, someone somewhere has to physically plug in a cable. On three robots that’s annoying. On thirt

The next ROS Deliberation Community Group meeting will be held on Mon, Aug 17, 2026 3:00 PM UTC . IMPORTANT: This is an “off-cycle” meeting. We are combining the August and September meetings into this one, since we also did not want to have a meeting too close to ROSCon. This means the next meeting after this one is planned for October 5, 2026. Google Meet link: Google Meet meeting Agenda: Tool spotlight: PyTrees release 2.5 Presentation: Contract-Grounded Behavior Tree Synthesis via Coding Age

Just saw that newly imported Chinese legged and humanoid robots are now banned in USA , what other alternatives are there? I know Unitree had ROS interface in both Go2 dog and G1 humanoid (and you could jailbreak cheap base version instead of expensive research one). What other alternatives are there? Will this spur open source/open hardware design? Again, I’m adding poll of what legged/humanoid robots have you used/planned to use What legged/humanoid robots have you used/will use? Chinese( Unit

Register here - registration is handled by the University of Edinburgh’s ePay service. Partial programme is up as well: three days of workshops, deep dives, talks, lightning talks, tours and demos. Early registration closes on 31 August. Late registration then runs until 14 October. Tickets are limited and go first-come, first-served. That includes workshops, which you pick while registering, so if there’s one you particularly want, don’t leave it too late. Do not worry if you can’t get your pic

Hello, I’m a mechanical engineer/controls guy/self taught C++ programmer (please forgive (and correct) me if I use the wrong terminology). I’ve been using ROS professionally for a few years. I started with humble. It’s got it’s warts but for the most part I love it! The most frequent complaint I hear from my “real” software developer co-workers is that “ROS is bloated”. I never really knew what they were talking about until it came time to actually package and “ship” our code. Here are my though

The ROS PMC meeting for this week was on Tuesday, July 28, 2026. The notes from the meeting are available at ROS PMC weekly meeting agenda . ROS PMC Business Async Formal Decision: Rolling sync policy. The proposal has been posted for a week with no negative feedback, so @mjcarroll will send the async vote out this afternoon. It enables automatic Rolling syncs to main. The Rolling ROS Boss will own the threshold, with input from the next release’s ROS Boss once that person exists. @yadunund hold

Welcome to This Week at Open Robotics Headquarters! This is a new and (hopefully) regular update on what’s happening behind the scenes of Open Robotics. These updates are to give folks some insight into what we do, as well as basic information about what we have in the works. Because I hope to keep them short, I’ll only list some of the highlights from the week. As always, questions/comments/feedback welcome! This first edition will be a little longer though, as I share a quick refresher on the