Planet ROS · 实时热榜

So, current issue of the launching VLAs on the Humanoids, like G1 Unitree\EngineAI T800\another, is the realsense pack of cams. F.e., for the unifolm vla ( GitHub - unitreerobotics/unifolm-vla · GitHub ), you need 2 on wrists + 2 on shoulders, so its kinda there is no another way without realsense? Currently kinda stuck on this type of the issue, maybe someone know the solution? 1 post - 1 participant Read full topic

One of the most common questions we get is some version of “how do I start contributing?” Here is a concrete answer: join us for Waffle, Thursdays, 30 minutes. What it is Waffle is a weekly triage meeting. We go through the issues and pull requests coming into the ROS 2 repositories that nobody has picked up yet, and we quickly discuss, triage, and assign them. It moves fast. Most items get a minute or two: what is this, is it valid, who should look at it. We assign things live in the meeting ra

A few weeks ago @jopequ shared mcp-rosbags + mcp-lab ( Another MCP Server to analyze your rosbags with LLMs + a UI to benchmark it against different LLM providers ) — an MCP server with purpose-built analysis tools (trajectories, laser scans, tf, plotting) and a neat UI for benchmarking providers on it. We’ve been working on the same problem at Pixel Robotics (AMRs for pallet transport) and just wrote up our approach, which lands on a different point in the design space, so I thought a compariso

So I went into a bit of a rabbit whole last week! CI on windows kept on getting this particular error: 2: [WARNING] [python.exe-2]: 'SIGINT' sent to process[python.exe-2] not supported on Windows, escalating to 'SIGTERM' Apparently, windows does not have a proper way to handle SIGINT, which means that it always straight goes to the ungraceful shutdown of SIGTERM. So I thought “oh! is that perhaps the reason why we keep getting all of the unhandy access violation ( 3221225477) that we see ever si

I am prototyping **EdgeAI Forge**, a local-first engineering architecture intended to help generate, test, benchmark, and document ROS 2 and machine-vision pipelines. The initial target workflow is a ROS 2 vision pipeline generator. Given a requirement such as: > Read frames from a USB camera, run object detection, publish detections, expose health status, benchmark performance, and prepare deployment to Jetson. the system should eventually produce reviewed artifacts including: - package manifes

Hi everyone! I’m a 2nd-year Mechanical Engineering student at NIT Jalandhar, currently exploring Robotics and Automation. I’m starting my journey with C++/Python, electronics, CAD and eventually ROS 2. My long-term goal is to work on real robotics projects and eventually pursue research/internship opportunities in robotics. I’m looking to connect with: • Students who are also learning Robotics/ROS 2 • People working on interesting robotics projects • Researchers/engineers who are open to collabo

Hi all, I’m an MEng Robotics & AI student at UCL working on perception/tracking pipelines (recently built a person re-ID and tracking evaluation pipeline, and a Gaussian-splat reconstruction quality evaluator). I’m trying to understand a specific problem better: how do teams currently notice when a perception or sensor-fusion stack has silently degraded in production, before it causes a visible failure? Do you rely on manual spot-checks, logging + alerts, a formal calibration schedule, or someth

I’m a 4th-year Computer Engineering student in Palestine (Birzeit University, graduating 2027). I focus on embedded systems and robotics. I have US citizenship, but I never lived or worked in the US. There’s no embedded or robotics industry here at all, so I can’t really build experience or a network locally. I’m trying to move to the US, but I’m not sure where to start. My background: ROS2 control software for a multi-agent robotics platform, FreeRTOS firmware on custom boards, and a competitio

I’ve been working on a ROS2 Dev Container Feature and just updated my VSCode ROS2 Workspace Template to use it instead of my pre-built ROS Docker images. The feature is here: GitHub Build software better, together GitHub is where people build software. More than 150 million people use GitHub to discover, fork, and contribute to over 420 million projects. Source: github.com GitHub - althack/devcontainers: My vscode devcontainers My vscode devcontainers The main thing I wanted was to select the RO

I have been looking into rosidl::Buffer and the current buffer backend support, particularly for large variable-length payloads such as images and point clouds. One idea I am interested in is a CPU shared-memory backend for rosidl::Buffer . I realize that this overlaps to some extent with functionality that already exists at lower layers. For example, some middleware / RMW implementations already provide shared-memory transport or other zero-copy optimizations. Depending on the implementation, m

I briefly mentioned an order-sensitive state diagnostic in another thread, but that was the wrong place for it. Posting it separately here with an executable reproducer. The idea is simple: three consecutive pose samples in, one scalar residual out. It quantifies how much the result shifts when you change the nesting order of state composition. Synthetic test results: Smooth linear motion: 4.9848e-08 Abrupt pose/orientation jump: 0.000881456 This is absolutely not a validated anomaly detector ye

Organization: OSRF Contributor: Ammaar Ahmed ( GitHub , LinkedIn ) Mentors: Kimberly McGuire ( GitHub ) and Skyler Medeiros ( GitHub ) GSoC project: ROS 2 Client Library Performance Monitoring Repository: ros2-performance-monitoring Live dashboard: performance.ammaar.lol Hello everyone, I am Ammaar Ahmed. I am pursuing a bachelor’s degree in Robotics and Automation Engineering at FAST NUCES Islamabad, Pakistan. My interest in ROS began about a year and a half ago, when I started building robots

For industrial robotics teams, simulation is useful only when the important parts of the simulated system behave enough like the real system to support better engineering decisions. A robot arm that looks right but reaches to the wrong pose is an obvious problem. A gripper that looks right but responds differently during contact can be harder to notice, and in manipulation work it may matter even more. At Southwest Research Institute, we have been developing and evaluating Physical AI approaches

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

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

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

Hi ROS Community! We are opening early-access evaluations for ADEL 2.0 (Autonomous Deterministic Executive Layer), a bare-metal C++/Rust execution engine built for ultra-low latency, zero-jitter control loops. While designed for microsecond satellite maneuver planning under severe compute bounds, ADEL 2.0 provides immediate utility for terrestrial robotics, BVLOS drone flight controllers, and autonomous hardware running ROS/ROS2 node topologies. Key Highlights: Microsecond-latency spatial trajec

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

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 已创建:

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

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

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( Un

Hi everyone, Recently, I’ve been learning more about Zenoh and its role in the ROS 2 ecosystem. Since most ROS 2 applications rely on DDS for communication, I was curious about how Zenoh approaches the same problem and where it can provide advantages. From what I’ve learned so far, Zenoh offers a lightweight communication layer that aims to reduce latency, minimize bandwidth usage, and simplify communication across distributed systems. These characteristics make it particularly interesting for r