全部/科技/实时热榜

Planet ROS · 实时热榜

  • 01
    ROS Discourse General: Adaptation needs in robotic systems
    Hi robotic developers, Are you working with Behavior Trees, robotics, ROS/ROS 2, autonomous systems, or robot decision-making ? We are conducting a research study on adaptation needs in robotic systems that use Behavior Trees. If you work with robotic systems, we’d greatly appreciate your input. We’re conducting a short survey to answer two key questions: The relevance of different adaptation needs in robotic systems. The suitability of different BT adaptation approaches for addressing those nee
  • 02
    ROS Discourse General: Announcing ros-env: Access ROS 2 messages from Rust with just Cargo
    Hey all! I’m one of the maintainers of ros2_rust , and we recently released a new crate, ros-env , that aims to unify ROS 2 message consumption in Rust. If you’re already generating Rust code for your message interfaces with rosidl_generator_rs , you can add ros-env as a regular Cargo dependency and access the message types from any packages in your sourced ROS 2 environment. // Assuming the Rust crate for `shape_msgs` is in `AMENT_PREFIX_PATH` use ros_env::shape_msgs::msg::Plane; You don’t need
  • 03
    ROS Discourse General: Real-time robot dashboards in React without a separate visualization server
    If you’ve built an operator UI or ground station in React, you’ve probably hit the same wall I did: the moment you need real-time telemetry visualization, your options are to run Foxglove or Grafana as separate infrastructure and iframe them in, or hand-roll canvas components from scratch. Neither is great when what you actually want is telemetry views that live natively inside the app you’re already building. So I built Altara: a set of MIT-licensed React components for real-time telemetry, wit
  • 04
    ROS Discourse General: Plotjuggler 4 (beta!) is here. Unleashing mulit-modal data
    After few months of hard work, PlotJuggler 4 is finally ready for an early preview! Expect bugs and missing features, but also ton of awesomeness unleashed. plotjuggler.io PlotJuggler 4 — Juggle with data The fast, open-source timeseries visualization tool for robotics. GitHub Release Plotjuggler 4: beta 1 · PlotJuggler/PlotJuggler The Time Series Visualization Tool that you deserve. - Release Plotjuggler 4: beta 1 · PlotJuggler/PlotJuggler Everything was brutally optimized. Playing a compressed
  • 05
    ROS Discourse General: Mastering NERO | How to Configure CAN Leader–Follower Linkage for Dual 7-DoF Robotic Arms
    Dual-arm robots are becoming increasingly important in embodied AI, teleoperation, imitation learning, and collaborative manipulation research. This tutorial demonstrates how to configure two AgileX NERO 7-DOF robotic arms in a leader-follower setup using CAN bus communication. Once configured, the follower arm will automatically replicate the motion of the leader arm in real time. What You’ll Build By the end of this guide, you’ll be able to: Synchronize two NERO robot arms Enable real-time lea
  • 06
    ROS Industrial: ros2_canopen: Natively Integrating CANopen Devices into the ROS 2 Ecosystem
    CANopen has long been one of the most widely used communication standards in industrial automation. Built on top of the CAN bus and standardised by CAN in Automation (CiA), it connects motor drives, I/O modules, sensors and other field devices across machines, robots and vehicles. The ros2_canopen stack, maintained under the ROS-Industrial umbrella, brings this ecosystem natively into ROS 2. It lets developers describe a CAN bus, bring up a CANopen master, and talk to every device on the bus thr
  • 07
    ROS Discourse General: Offboard Control with PX4 & ROS 2 (Micro XRCE-DDS)
    I wanted to share an architectural pattern for handling autonomous drone navigation using ROS 2 (Jazzy) and PX4 Autopilot via Micro XRCE-DDS, specifically regarding the Offboard mode failsafe. The Problem: When developing an autonomous flight node in C++, transitioning to PX4’s Offboard mode can be tricky. PX4 implements a strict failsafe: it will reject any VEHICLE_CMD_DO_SET_MODE to Offboard unless it detects a continuous stream of setpoints (e.g., TrajectorySetpoint and OffboardControlMode )
  • 08
    ROS Discourse General: Pyspacemouse axis conventions
    Thanks to new contributor, we have documentation of, and several options for, axis conventions in pyspacemouse not yet released to pypi, but please try it out (you can pip install directly from github!) and let me know what you think. Longer term, the plan is to change the default convention to HID , because the LEGACY convention is, frankly, insane, and I don’t want all users to have to “fix it” on their own. spacemouse.kubaandrysek.cz Axis Conventions - API documentation for this tool - PySpac
  • 09
    ROS Discourse General: Guidelines for AI-Assisted Contributions in the ROS Project
    Hello fellow ROS users, maintainers, contributors and anyone else who may be passing by. Due to a recent uptick in LLM-authored pull requests, the ROS PMC has elected to extend the upstream OSRF policy on the use of generative tools to help provide some boundaries/guidelines on the use of these tools. These tools and technologies are constantly changing, so this isn’t intended to serve as a permanent policy, but rather it is to provide a framework for how to interact on ROS-related projects. The
  • 10
    ROS Discourse General: Logging and Observability Guide Review | Cloud Robotics WG Meeting 2026-07-13
    The group is not meeting today (2026-06-29) due to lack of available members! Please come and join us for this coming meeting at Mon, Jul 13, 2026 4:00 PM UTC → Mon, Jul 13, 2026 5:00 PM UTC , where we will be editing the first draft of the Logging and Observability guide, generated by AI. The AI used the skeleton of the guide from the previous session and transcripts from all meeting recordings to generate a guide. The group will edit this starting point together in the coming session. Please n
  • 11
    ROS Discourse General: A Standard Interface from LLM to Robot Actions
    Hi ROS community, I’m working on ClawsJoy Robotics, a proposal for a standard interface between LLM-based cognitive systems and ROS/2 robots. The core idea: any LLM outputs an action, any robot implements these standard topics. The Problem Every robotics company maps “pick up the cup” to different ROS/2 interfaces: Company A: custom service /manipulation/pick Company B: action server /grasp_object Company C: proprietary SDK There’s no standard way for an LLM agent to tell a robot what to do. The
  • 12
    ROS Discourse General: Cad to urdf conversion
    If you’re a robotics engineer, you’ve probably lost hours to URDF generation. Not because the robot is complex but because the tooling is. Renaming mates. Fixing joint axes. Recreating reference frames. Starting over because the CAD came from the “wrong” software. I got tired of that workflow, so I built Jointly. Upload a STEP assembly then get a draft URDF with inferred joints, inertia, collision meshes, and a live 3D preview. It’s not magic , you’ll still review the result. But it turns hours
  • 13
    ROS Discourse General: Ros2-dev-suite, a StudioCode extension
    As shared in a lightning talk at ROSConFr: I have finally completed and “clauded” a comprehensive VS Code extension for ROS 2 development: a unified explorer, live parameter tuner, service/topic/action caller, log viewer, and syntax highlighting for interface files. My favorite features of the extension, among others: Dynamically changing node ROS parameters at runtime via a YAML panel and comparing live params vs. edits: very handy for tuning PIDs, covariances, etc. Possibility to edit an exist
  • 14
    ROS Discourse General: 🍺 ros2-jazzy is now available on Homebrew!
    All three ROS 2 distros are now native on Homebrew-macOS: brew tap idesign0/ros2 brew install ros2-humble brew install ros2-jazzy brew install ros2-kilted One tap to get ROS 2 Jazzy with full simulation and robotics stack support: Gazebo (gz-sim8) — Gazebo Harmonic simulation out of the box ros2_control — Hardware abstraction & controllers MoveIt 2 — Motion planning Nav2 — Autonomous navigation No Docker. No VMs. Native macOS. And the best part? These aren’t one-time snapshots — they stay in syn
  • 15
    ROS Discourse General: Sony AI's Ace (Nature cover, beat a pro table tennis player) — running on ROS 2
    Can you believe this is running ROS 2? Sony’s Ace Robot Beats Top Table Tennis Pros in Real Matches Sony AI’s Ace just landed on the cover of Nature — the first robot ever to beat a professional table tennis player. Let that sink in for a second: • It tracks a ball moving at 20 m/s with spin over 9,000 rpm • Perceives it in 10.2 ms (event-based vision) • Decides and swings on a 1 kHz control loop • And returns the ball at up to 19.6 m/s This is physical AI right at the edge of what’s possible —
  • 16
    ROS Discourse General: A tutorial to make your quadruped robot on ROS
    Hello guys ! I made a tutorial to make your own quadruped using ros2 jazzy ! github.com GitHub - joschmaCYU/quadruped: The code base for my quadruped robot. I build this... The code base for my quadruped robot. I build this with ros2 jazzy. On an esp32 and raspberry pi If you have any feed back I am happy to hear it 1 post - 1 participant Read full topic
  • 17
    ROS Discourse General: Rclnodejs 2.1: Native ESM for a Web-Native ROS 2 SDK
    Hi all, rclnodejs 2.1.0 is out — and it’s a step toward making rclnodejs a web-native SDK for ROS 2 : a platform for bringing ROS 2 to the browser and the modern JavaScript ecosystem. With 2.1.0, the whole package is now native ESM , so building web dashboards, teleop UIs, and browser bridges on ROS 2 feels native to today’s web tooling — with the full ROS 2 runtime still underneath whenever you need real nodes. TL;DR — 2.1.0 makes rclnodejs native ESM end-to-end. import rclnodejs from 'rclnodej
  • 18
    ROS Discourse General: Anomaly Detection. Beta testers wanted
    Hi, I used to work at a robotics startup that built robotic dishwashers. ( https://armstrong.ai/ ) And part of my job was to set up diagnostics, monitoring and alerting. Aside from not being the most interesting part of my job, it was just plain tedious to manually set (and continually tune) thresholds for various signals, topics, etc. I frequently thought it would be nice to have a system that would automate that part of my job and now that the company has closed, I built it. Now I have reached
  • 19
    ROS Discourse General: VL53L0X Time-of-Flight sensor as a Nav2 obstacle layer (ESP32 + ROS 2 Humble)
    Sharing a small open-source project that integrates a low-cost VL53L0X Time-of-Flight sensor into the Nav2 costmap as an obstacle source, in case it’s useful to anyone working with cheap range sensors on small robots. Pipeline VL53L0X --I2C–> ESP32 --USB serial–> serial_bridge → sensor_msgs/Range → tof_to_scan → sensor_msgs/LaserScan → nav2_costmap_2d::ObstacleLayer What’s included ESP32 firmware (Arduino, Pololu VL53L0X library) streaming distance over serial with sensor-disconnect recovery An
  • 20
    ROS Discourse General: Embeddable React telemetry components — a browser ground station for MAVROS
    I maintain Altara, a set of MIT-licensed React components for real-time robotics telemetry (PFD, moving map, gauges, event log), and I wrote up building a small drone ground station with them that talks to MAVROS over rosbridge. The thing I was trying to solve: I wanted a status dashboard our team could open in a browser tab and drop into our own app, rather than running a separate native GCS. So the components are embeddable and themeable rather than a standalone tool. Writeup (the rosbridge/MA
  • 21
    ROS Discourse General: KRS Unleashed: Easier Hardware Acceleration Prototyping on FPGA
    Hey All, I want to present KRS Unleashed , the tool I am now developing/refactoring/extending since 1 year as part of my PhD. Some of you might still know KRS (short for Kria Robotic Stack as originally developed by Xilinx/AMD for their Kria platform) as the toolchain developed until 2023 by the ROS 2 Hardware Acceleration Working Group · GitHub . (Short Summary for those who don’t) It was a proof-of-concept framework that allowed to synthesize bitstreams, create a sysroot and cross-compile appl
  • 22
    ROS Discourse General: Minimum CMake version to support Humble at this time
    REP 2000 specifies MacOS support for CMake 3.14.4 in Humble: This is the lowest number for the whole Humble release. However, MacOS has this note: " ** " means that the dependency may see multiple version changes, because the dependency uses a package manager that continually updates the dependency without a stable API. I don’t work with MacOS myself, so I don’t know how it behaves. Is it still needed nowadays to support 3.14.4 to get full support for Humble on MacOS, or can I just ignore this a
  • 23
    ROS Discourse General: Dual-Arm Nero Reinforcement Learning in Isaac Lab: Reach Task Training Example
    Robotic manipulation remains one of the most important research directions in embodied AI. While traditional kinematics-based controllers provide stable motion execution, they often struggle in unstructured environments where adaptability is required. Recent advances in Reinforcement Learning (RL) have enabled robotic arms to learn task-oriented behaviors directly from interaction, making it possible to achieve robust control policies without manually designing every motion strategy. In this pro
  • 24
    ROS Discourse General: Open-source ROS2 LiDAR robot vacuum cleaner
    Hello, would you be interested in building a ROS2 vacuum cleaner robot? If yes Build/develop vs convert existing? 3D print vs off-the-shelf? Convert existing - root or swap board? I’d really appreciate your input. As an example of what I’m doing I have connected my vacuum to ROS including /scan, /imu, /cmd_vel, /odom, brushes (main, side), vacuum fan, IR sensors. Open source here GitHub - makerspet/proscenic-m6pro: ROS2 robot description for Proscenic M6 Pro · GitHub I have had a consumer vacuum
  • 25
    ROS Discourse General: AIC Phase 1: How to run custom aic_model service in Flowstate with AIC_ROUTER_ADDR?
    Hi Intrinsic / AIC team, I’m working on AIC Phase 1 in Flowstate and trying to run my participant model as a custom Service instance named exactly aic_model . The baseline AIC Phase 1 Submission process expects: lifecycle service: /aic_model/change_state action server: /insert_cable I have a local Docker image: my-solution:phase1_basic_control_ladder The image works in local Docker Compose when launched with the AIC router environment variables. Its entrypoint requires: AIC_ROUTER_ADDR and may r
Planet ROS实时热榜 | 什么火了