Planet ROS

Planet ROS - http://planet.ros.org

Planet ROS - http://planet.ros.org[WWW] http://planet.ros.org

ROS Discourse General: Is Zenoh a closed protocol?

Hi,

To me, TCPROS is an example of open protocol - it provides specification, you can implement its own client and communicate with any ROS1 nodes over it.

DDS is also example of open protocol - it provides specification, you can implement its own client and communicate with any ROS2 nodes over it (examples of such clients are FastDDS, CycloneDDS, …).

Since Zenoh stands for “Zero Overhead Network Protocol” I was looking for any specification how this protocol works but could not find any.

Could someone point me please for such specification or if it does not exist would it mean that it is “closed protocol” and users can communicate with it only through clients which only Zenoh itself provides?

This seems important, as I could see that ROS leaning towards Zenoh to be default RMW in future (especially after watching ROSCon2024 :slight_smile: )

Just to summarize: If Zenoh is open protocol, could someone point me please for its specification

Thank you,

1 post - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/is-zenoh-a-closed-protocol/40791

ROS Discourse General: ROS News for the Week of November 18th, 2024

ROS News for the Week of November 18th, 2024


ROSConLiveStream (2)

The ROSCon 2024 videos are finally here! If you missed a talk or missed the whole event you can now catch up by watching the videos online.


Aug24GCM (1)

Join us on 2024-11-27 for our monthly Gazebo Community Meeting. We’ll have eight competitors from the NASA Space ROS Summer Sprint Challenge on to talk about their work.


image

@cottsay, one of our fantastic ROS core contributors, just added a new automatic review tool to rosdistro that should make it faster and easier to get your pull requests approved. Learn all about it in this post or by watching this ROSCon lightning talk.


snowbot
Check out this homebrew ROS 2 snow plowing robot by Serdar Abali in Finland! With winter fast approaching in the northern hemisphere this seems like an amazing project! Coming across cool DIY ROS projects like this always makes my day.

Events

News

ROS

Got a Minute? :mantelpiece_clock:

@DLu just sent over this amazing custom RViz panel tutorial to the ROS 2 documentation. We should all be more like @DLu and spend some time porting and updating ROS 1 Wiki articles to the ROS 2 documentation.

2 posts - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/ros-news-for-the-week-of-november-18th-2024/40777

ROS Discourse General: OSRA TGC meeting minutes for October, 2024

The meeting minutes for the regular meeting of the Technical Governance Committee held on the 22nd of October, 2024, were approved in the November meeting and are now available in the official minutes repository. You can find the complete minutes here.

The TGC received the usual project and technical committee updates, including the release of Gazebo Ionic, collaboration between Open-RMF and Gazebo to include Open-RMF functionality in the Gazebo Ionic demonstration world, and notice of the Infrastructure project preparing to move to Ubuntu 24.04.

In existing business, the Open-RMF PMC made a proposal to move the Nexus project under the purview of the Open-RMF PMC, due to the overlap in developers and the complementary nature of the features. The TGC agreed to make this recommendation to the OSRF Board.

In new business, the TGC discussed the pros and cons of versioning the data stored in rosbags, and of OSRF projects adopting Bazel. No decisions were made.

The next TGC meeting will take place on the 19th of December. The minutes of the November meeting should be approved in that meeting and posted publicly shortly thereafter.

3 posts - 2 participants

Read full topic

[WWW] https://discourse.ros.org/t/osra-tgc-meeting-minutes-for-october-2024/40768

ROS Discourse General: New Packages for Jazzy Jalisco 2024-11-21

Hello there everyone!

We’re happy to announce 43 new packages and 347 updates are now available in ROS 2 Jazzy Jalisco :jazzy: :jazzy: :jazzy: .

This sync was tagged as jazzy/2024-11-21 .

Added Packages [43]:

  • ros-jazzy-ess-imu-driver2: 2.0.2-1
  • ros-jazzy-irobot-create-common-bringup: 3.0.4-1
  • ros-jazzy-irobot-create-gz-bringup: 3.0.4-1
  • ros-jazzy-irobot-create-gz-sim: 3.0.4-1
  • ros-jazzy-irobot-create-gz-toolbox: 3.0.4-1
  • ros-jazzy-irobot-create-nodes: 3.0.4-1
  • ros-jazzy-plansys2-core: 2.0.14-1
  • ros-jazzy-plansys2-domain-expert: 2.0.14-1
  • ros-jazzy-plansys2-executor: 2.0.14-1
  • ros-jazzy-plansys2-lifecycle-manager: 2.0.14-1
  • ros-jazzy-plansys2-msgs: 2.0.14-1
  • ros-jazzy-plansys2-pddl-parser: 2.0.14-1
  • ros-jazzy-plansys2-planner: 2.0.14-1
  • ros-jazzy-plansys2-popf-plan-solver: 2.0.14-1
  • ros-jazzy-plansys2-problem-expert: 2.0.14-1
  • ros-jazzy-plansys2-support-py: 2.0.14-1
  • ros-jazzy-plansys2-tools: 2.0.14-1
  • ros-jazzy-pose-broadcaster: 4.16.0-1
  • ros-jazzy-ptz-action-server-msgs: 2.0.3-1
  • ros-jazzy-raspimouse-description: 2.0.0-1
  • ros-jazzy-rt-usb-9axisimu-driver: 3.0.0-1
  • ros-jazzy-sbg-driver: 3.2.0-1
  • ros-jazzy-simple-grasping: 0.5.0-1
  • ros-jazzy-turtlebot4-gz-bringup: 2.0.2-1
  • ros-jazzy-turtlebot4-simulator: 2.0.2-1

Updated Packages [347]:

  • ros-jazzy-ackermann-steering-controller: 4.15.0-1 → 4.16.0-1
  • ros-jazzy-admittance-controller: 4.15.0-1 → 4.16.0-1
  • ros-jazzy-backward-ros: 1.0.5-1 → 1.0.6-1
  • ros-jazzy-bicycle-steering-controller: 4.15.0-1 → 4.16.0-1
  • ros-jazzy-camera-calibration: 5.0.4-1 → 5.0.5-1
  • ros-jazzy-control-msgs: 5.2.0-1 → 5.3.0-1
  • ros-jazzy-control-toolbox: 3.2.0-3 → 3.3.0-1
  • ros-jazzy-controller-interface: 4.18.0-1 → 4.20.0-1
  • ros-jazzy-controller-manager: 4.18.0-1 → 4.20.0-1
  • ros-jazzy-controller-manager-msgs: 4.18.0-1 → 4.20.0-1
  • ros-jazzy-costmap-queue: 1.3.2-1 → 1.3.3-1
  • ros-jazzy-depth-image-proc: 5.0.4-1 → 5.0.5-1
  • ros-jazzy-diff-drive-controller: 4.15.0-1 → 4.16.0-1
  • ros-jazzy-dwb-core: 1.3.2-1 → 1.3.3-1
  • ros-jazzy-dwb-critics: 1.3.2-1 → 1.3.3-1
  • ros-jazzy-dwb-msgs: 1.3.2-1 → 1.3.3-1
  • ros-jazzy-dwb-plugins: 1.3.2-1 → 1.3.3-1
  • ros-jazzy-effort-controllers: 4.15.0-1 → 4.16.0-1
  • ros-jazzy-fastrtps: 2.14.1-1 → 2.14.3-1
  • ros-jazzy-force-torque-sensor-broadcaster: 4.15.0-1 → 4.16.0-1
  • ros-jazzy-forward-command-controller: 4.15.0-1 → 4.16.0-1
  • ros-jazzy-foxglove-compressed-video-transport: 1.0.0-1 → 1.0.1-1
  • ros-jazzy-generate-parameter-library: 0.3.8-4 → 0.3.9-1
  • ros-jazzy-generate-parameter-library-example: 0.3.8-4 → 0.3.9-1
  • ros-jazzy-generate-parameter-library-py: 0.3.8-4 → 0.3.9-1
  • ros-jazzy-generate-parameter-module-example: 0.3.8-4 → 0.3.9-1
  • ros-jazzy-gripper-controllers: 4.15.0-1 → 4.16.0-1
  • ros-jazzy-gz-common-vendor: 0.0.5-1 → 0.0.7-1
  • ros-jazzy-gz-math-vendor: 0.0.6-1 → 0.0.7-1
  • ros-jazzy-gz-msgs-vendor: 0.0.4-1 → 0.0.5-1
  • ros-jazzy-gz-physics-vendor: 0.0.4-1 → 0.0.5-1
  • ros-jazzy-gz-rendering-vendor: 0.0.4-1 → 0.0.5-1
  • ros-jazzy-gz-ros2-control: 1.2.7-1 → 1.2.8-1
  • ros-jazzy-gz-ros2-control-demos: 1.2.7-1 → 1.2.8-1
  • ros-jazzy-gz-sensors-vendor: 0.0.4-1 → 0.0.5-1
  • ros-jazzy-gz-sim-vendor: 0.0.5-1 → 0.0.6-1
  • ros-jazzy-gz-tools-vendor: 0.0.4-1 → 0.0.5-1
  • ros-jazzy-hardware-interface: 4.18.0-1 → 4.20.0-1
  • ros-jazzy-hardware-interface-testing: 4.18.0-1 → 4.20.0-1
  • ros-jazzy-image-pipeline: 5.0.4-1 → 5.0.5-1
  • ros-jazzy-image-proc: 5.0.4-1 → 5.0.5-1
  • ros-jazzy-image-publisher: 5.0.4-1 → 5.0.5-1
  • ros-jazzy-image-rotate: 5.0.4-1 → 5.0.5-1
  • ros-jazzy-image-view: 5.0.4-1 → 5.0.5-1
  • ros-jazzy-imu-sensor-broadcaster: 4.15.0-1 → 4.16.0-1
  • ros-jazzy-irobot-create-control: 3.0.3-1 → 3.0.4-1
  • ros-jazzy-irobot-create-description: 3.0.3-1 → 3.0.4-1
  • ros-jazzy-irobot-create-gz-plugins: 3.0.3-1 → 3.0.4-1
  • ros-jazzy-irobot-create-toolbox: 3.0.3-1 → 3.0.4-1
  • ros-jazzy-joint-limits: 4.18.0-1 → 4.20.0-1
  • ros-jazzy-joint-state-broadcaster: 4.15.0-1 → 4.16.0-1
  • ros-jazzy-joint-trajectory-controller: 4.15.0-1 → 4.16.0-1
  • ros-jazzy-joy-teleop: 1.6.0-1 → 1.7.0-1
  • ros-jazzy-key-teleop: 1.6.0-1 → 1.7.0-1
  • ros-jazzy-kinematics-interface: 1.1.0-1 → 1.2.1-1
  • ros-jazzy-kinematics-interface-kdl: 1.1.0-1 → 1.2.1-1
  • ros-jazzy-laser-filters: 2.0.7-3 → 2.0.8-1
  • ros-jazzy-leo: 3.0.3-1 → 3.0.4-1
  • ros-jazzy-leo-bringup: 1.4.0-3 → 2.0.0-1
  • ros-jazzy-leo-description: 3.0.3-1 → 3.0.4-1
  • ros-jazzy-leo-fw: 1.4.0-3 → 2.0.0-1
  • ros-jazzy-leo-gz-bringup: 2.0.0-1 → 2.0.1-1
  • ros-jazzy-leo-gz-plugins: 2.0.0-1 → 2.0.1-1
  • ros-jazzy-leo-gz-worlds: 2.0.0-1 → 2.0.1-1
  • ros-jazzy-leo-msgs: 3.0.3-1 → 3.0.4-1
  • ros-jazzy-leo-robot: 1.4.0-3 → 2.0.0-1
  • ros-jazzy-leo-simulator: 2.0.0-1 → 2.0.1-1
  • ros-jazzy-leo-teleop: 3.0.3-1 → 3.0.4-1
  • ros-jazzy-microstrain-inertial-description: 4.4.0-1 → 4.5.0-1
  • ros-jazzy-microstrain-inertial-driver: 4.4.0-1 → 4.5.0-1
  • ros-jazzy-microstrain-inertial-examples: 4.4.0-1 → 4.5.0-1
  • ros-jazzy-microstrain-inertial-msgs: 4.4.0-1 → 4.5.0-1
  • ros-jazzy-microstrain-inertial-rqt: 4.4.0-1 → 4.5.0-1
  • ros-jazzy-mouse-teleop: 1.6.0-1 → 1.7.0-1
  • ros-jazzy-mp2p-icp: 1.6.2-1 → 1.6.3-1
  • ros-jazzy-mrpt-apps: 2.14.3-1 → 2.14.5-1
  • ros-jazzy-mrpt-libapps: 2.14.3-1 → 2.14.5-1
  • ros-jazzy-mrpt-libbase: 2.14.3-1 → 2.14.5-1
  • ros-jazzy-mrpt-libgui: 2.14.3-1 → 2.14.5-1
  • ros-jazzy-mrpt-libhwdrivers: 2.14.3-1 → 2.14.5-1
  • ros-jazzy-mrpt-libmaps: 2.14.3-1 → 2.14.5-1
  • ros-jazzy-mrpt-libmath: 2.14.3-1 → 2.14.5-1
  • ros-jazzy-mrpt-libnav: 2.14.3-1 → 2.14.5-1
  • ros-jazzy-mrpt-libobs: 2.14.3-1 → 2.14.5-1
  • ros-jazzy-mrpt-libopengl: 2.14.3-1 → 2.14.5-1
  • ros-jazzy-mrpt-libposes: 2.14.3-1 → 2.14.5-1
  • ros-jazzy-mrpt-libros-bridge: 2.14.3-1 → 2.14.5-1
  • ros-jazzy-mrpt-libslam: 2.14.3-1 → 2.14.5-1
  • ros-jazzy-mrpt-libtclap: 2.14.3-1 → 2.14.5-1
  • ros-jazzy-mvsim: 0.11.0-1 → 0.11.1-1
  • ros-jazzy-nav-2d-msgs: 1.3.2-1 → 1.3.3-1
  • ros-jazzy-nav-2d-utils: 1.3.2-1 → 1.3.3-1
  • ros-jazzy-nav2-amcl: 1.3.2-1 → 1.3.3-1
  • ros-jazzy-nav2-behavior-tree: 1.3.2-1 → 1.3.3-1
  • ros-jazzy-nav2-behaviors: 1.3.2-1 → 1.3.3-1
  • ros-jazzy-nav2-bringup: 1.3.2-1 → 1.3.3-1
  • ros-jazzy-nav2-bt-navigator: 1.3.2-1 → 1.3.3-1
  • ros-jazzy-nav2-collision-monitor: 1.3.2-1 → 1.3.3-1
  • ros-jazzy-nav2-common: 1.3.2-1 → 1.3.3-1
  • ros-jazzy-nav2-constrained-smoother: 1.3.2-1 → 1.3.3-1
  • ros-jazzy-nav2-controller: 1.3.2-1 → 1.3.3-1
  • ros-jazzy-nav2-core: 1.3.2-1 → 1.3.3-1
  • ros-jazzy-nav2-costmap-2d: 1.3.2-1 → 1.3.3-1
  • ros-jazzy-nav2-dwb-controller: 1.3.2-1 → 1.3.3-1
  • ros-jazzy-nav2-graceful-controller: 1.3.2-1 → 1.3.3-1
  • ros-jazzy-nav2-lifecycle-manager: 1.3.2-1 → 1.3.3-1
  • ros-jazzy-nav2-loopback-sim: 1.3.2-1 → 1.3.3-1
  • ros-jazzy-nav2-map-server: 1.3.2-1 → 1.3.3-1
  • ros-jazzy-nav2-mppi-controller: 1.3.2-1 → 1.3.3-1
  • ros-jazzy-nav2-msgs: 1.3.2-1 → 1.3.3-1
  • ros-jazzy-nav2-navfn-planner: 1.3.2-1 → 1.3.3-1
  • ros-jazzy-nav2-planner: 1.3.2-1 → 1.3.3-1
  • ros-jazzy-nav2-regulated-pure-pursuit-controller: 1.3.2-1 → 1.3.3-1
  • ros-jazzy-nav2-rotation-shim-controller: 1.3.2-1 → 1.3.3-1
  • ros-jazzy-nav2-rviz-plugins: 1.3.2-1 → 1.3.3-1
  • ros-jazzy-nav2-simple-commander: 1.3.2-1 → 1.3.3-1
  • ros-jazzy-nav2-smac-planner: 1.3.2-1 → 1.3.3-1
  • ros-jazzy-nav2-smoother: 1.3.2-1 → 1.3.3-1
  • ros-jazzy-nav2-system-tests: 1.3.2-1 → 1.3.3-1
  • ros-jazzy-nav2-theta-star-planner: 1.3.2-1 → 1.3.3-1
  • ros-jazzy-nav2-util: 1.3.2-1 → 1.3.3-1
  • ros-jazzy-nav2-velocity-smoother: 1.3.2-1 → 1.3.3-1
  • ros-jazzy-nav2-voxel-grid: 1.3.2-1 → 1.3.3-1
  • ros-jazzy-nav2-waypoint-follower: 1.3.2-1 → 1.3.3-1
  • ros-jazzy-navigation2: 1.3.2-1 → 1.3.3-1
  • ros-jazzy-novatel-gps-driver: 4.1.3-1 → 4.2.0-1
  • ros-jazzy-novatel-gps-msgs: 4.1.3-1 → 4.2.0-1
  • ros-jazzy-octomap-msgs: 2.0.0-5 → 2.0.1-1
  • ros-jazzy-odom-to-tf-ros2: 1.0.2-4 → 1.0.3-2
  • ros-jazzy-opennav-docking: 1.3.2-1 → 1.3.3-1
  • ros-jazzy-opennav-docking-bt: 1.3.2-1 → 1.3.3-1
  • ros-jazzy-opennav-docking-core: 1.3.2-1 → 1.3.3-1
  • ros-jazzy-openni2-camera: 2.2.1-1 → 2.2.2-1
  • ros-jazzy-openvdb-vendor: 2.5.2-1 → 2.5.3-1
  • ros-jazzy-parallel-gripper-controller: 4.15.0-1 → 4.16.0-1
  • ros-jazzy-parameter-traits: 0.3.8-4 → 0.3.9-1
  • ros-jazzy-pcl-conversions: 2.6.1-4 → 2.6.2-1
  • ros-jazzy-pcl-ros: 2.6.1-4 → 2.6.2-1
  • ros-jazzy-perception-pcl: 2.6.1-4 → 2.6.2-1
  • ros-jazzy-pid-controller: 4.15.0-1 → 4.16.0-1
  • ros-jazzy-pose-cov-ops: 0.3.12-1 → 0.3.13-1
  • ros-jazzy-position-controllers: 4.15.0-1 → 4.16.0-1
  • ros-jazzy-python-mrpt: 2.14.3-1 → 2.14.5-1
  • ros-jazzy-range-sensor-broadcaster: 4.15.0-1 → 4.16.0-1
  • ros-jazzy-realtime-tools: 2.6.0-1 → 2.8.1-1
  • ros-jazzy-robot-calibration: 0.9.1-1 → 0.9.2-1
  • ros-jazzy-robot-calibration-msgs: 0.9.1-1 → 0.9.2-1
  • ros-jazzy-ros-babel-fish: 0.9.3-1 → 0.10.0-1
  • ros-jazzy-ros-babel-fish-test-msgs: 0.9.3-1 → 0.10.0-1
  • ros-jazzy-ros-gz: 1.0.5-1 → 1.0.7-1
  • ros-jazzy-ros-gz-bridge: 1.0.5-1 → 1.0.7-1
  • ros-jazzy-ros-gz-image: 1.0.5-1 → 1.0.7-1
  • ros-jazzy-ros-gz-interfaces: 1.0.5-1 → 1.0.7-1
  • ros-jazzy-ros-gz-sim: 1.0.5-1 → 1.0.7-1
  • ros-jazzy-ros-gz-sim-demos: 1.0.5-1 → 1.0.7-1
  • ros-jazzy-ros2-control: 4.18.0-1 → 4.20.0-1
  • ros-jazzy-ros2-control-test-assets: 4.18.0-1 → 4.20.0-1
  • ros-jazzy-ros2-controllers: 4.15.0-1 → 4.16.0-1
  • ros-jazzy-ros2-controllers-test-nodes: 4.15.0-1 → 4.16.0-1
  • ros-jazzy-ros2controlcli: 4.18.0-1 → 4.20.0-1
  • ros-jazzy-rqt-controller-manager: 4.18.0-1 → 4.20.0-1
  • ros-jazzy-rqt-image-overlay: 0.3.1-4 → 0.4.0-1
  • ros-jazzy-rqt-image-overlay-layer: 0.3.1-4 → 0.4.0-1
  • ros-jazzy-rqt-joint-trajectory-controller: 4.15.0-1 → 4.16.0-1
  • ros-jazzy-scenario-execution: 1.2.0-4 → 1.2.0-5
  • ros-jazzy-scenario-execution-control: 1.2.0-4 → 1.2.0-5
  • ros-jazzy-scenario-execution-coverage: 1.2.0-4 → 1.2.0-5
  • ros-jazzy-scenario-execution-gazebo: 1.2.0-4 → 1.2.0-5
  • ros-jazzy-scenario-execution-interfaces: 1.2.0-4 → 1.2.0-5
  • ros-jazzy-scenario-execution-nav2: 1.2.0-4 → 1.2.0-5
  • ros-jazzy-scenario-execution-os: 1.2.0-4 → 1.2.0-5
  • ros-jazzy-scenario-execution-py-trees-ros: 1.2.0-4 → 1.2.0-5
  • ros-jazzy-scenario-execution-ros: 1.2.0-4 → 1.2.0-5
  • ros-jazzy-scenario-execution-x11: 1.2.0-4 → 1.2.0-5
  • ros-jazzy-sdformat-vendor: 0.0.6-1 → 0.0.7-1
  • ros-jazzy-spatio-temporal-voxel-layer: 2.5.2-1 → 2.5.3-1
  • ros-jazzy-steering-controllers-library: 4.15.0-1 → 4.16.0-1
  • ros-jazzy-stereo-image-proc: 5.0.4-1 → 5.0.5-1
  • ros-jazzy-teleop-tools: 1.6.0-1 → 1.7.0-1
  • ros-jazzy-teleop-tools-msgs: 1.6.0-1 → 1.7.0-1
  • ros-jazzy-test-ros-gz-bridge: 1.0.5-1 → 1.0.7-1
  • ros-jazzy-tracetools-image-pipeline: 5.0.4-1 → 5.0.5-1
  • ros-jazzy-transmission-interface: 4.18.0-1 → 4.20.0-1
  • ros-jazzy-tricycle-controller: 4.15.0-1 → 4.16.0-1
  • ros-jazzy-tricycle-steering-controller: 4.15.0-1 → 4.16.0-1
  • ros-jazzy-turtlebot4-base: 2.0.0-1 → 2.0.1-2
  • ros-jazzy-turtlebot4-bringup: 2.0.0-1 → 2.0.1-2
  • ros-jazzy-turtlebot4-diagnostics: 2.0.0-1 → 2.0.1-2
  • ros-jazzy-turtlebot4-gz-gui-plugins: 2.0.1-1 → 2.0.2-1
  • ros-jazzy-turtlebot4-gz-toolbox: 2.0.1-1 → 2.0.2-1
  • ros-jazzy-turtlebot4-robot: 2.0.0-1 → 2.0.1-2
  • ros-jazzy-turtlebot4-setup: 2.0.1-1 → 2.0.2-1
  • ros-jazzy-turtlebot4-tests: 2.0.0-1 → 2.0.1-2
  • ros-jazzy-twist-stamper: 0.0.3-4 → 0.0.5-1
  • ros-jazzy-ur: 2.4.12-1 → 2.4.13-1
  • ros-jazzy-ur-calibration: 2.4.12-1 → 2.4.13-1
  • ros-jazzy-ur-controllers: 2.4.12-1 → 2.4.13-1
  • ros-jazzy-ur-dashboard-msgs: 2.4.12-1 → 2.4.13-1
  • ros-jazzy-ur-moveit-config: 2.4.12-1 → 2.4.13-1
  • ros-jazzy-ur-robot-driver: 2.4.12-1 → 2.4.13-1
  • ros-jazzy-velocity-controllers: 4.15.0-1 → 4.16.0-1
  • ros-jazzy-velodyne: 2.3.0-4 → 2.5.1-1
  • ros-jazzy-velodyne-driver: 2.3.0-4 → 2.5.1-1
  • ros-jazzy-velodyne-laserscan: 2.3.0-4 → 2.5.1-1
  • ros-jazzy-velodyne-msgs: 2.3.0-4 → 2.5.1-1
  • ros-jazzy-velodyne-pointcloud: 2.3.0-4 → 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:

  • Addisu Z. Taddese
  • Aditya Pande
  • Alberto Tudela
  • Alejandro Hernandez
  • Alejandro Hernández
  • Alexey Merzlyakov
  • Bence Magyar
  • Bernd Pfrommer
  • Brian Wilcox
  • Carl Delsey
  • Carlos Orduno
  • Chris Iverach-Brereton
  • David V. Lu!!
  • Denis Štogl
  • Ekumen
  • Enrique Fernandez
  • Felix Exner
  • Fictionlab
  • Francisco Martin Rico
  • Frederik Pasch
  • George Stavrinos
  • Intel Labs
  • Jon Binney
  • Jose-Luis Blanco-Claraco
  • Josh Newans
  • Josh Whitley
  • Matej Vargovcik
  • Michael Ferguson
  • Michael Jeronimo
  • Miguel Company
  • Mohammad Haghighipanah
  • P. J. Reed
  • Paul Bovbel
  • Paul Gesel
  • RT Corporation
  • Raymond Chow
  • Rob Fisher
  • Robert Wilbrandt
  • SBG Systems
  • Stefan Fabian
  • Steve Macenski
  • Tim Clephas
  • Tyler Weaver
  • Victor López
  • Vincent Rabaud
  • Víctor Mayoral-Vilches
  • Wolfgang Merkt
  • ijnek
  • paul
  • rkreinin
  • steve
  • steve macenski

Enjoy! :jazzy:

1 post - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/new-packages-for-jazzy-jalisco-2024-11-21/40763

ROS Industrial: Unlocking for Industrial Users the Power of ROS 2: ROS-I October Training Highlights

The ROS-Industrial Consortium Americas provided a hybrid, online/in-person, ROS 2 training October 22-24. The three-day ROS-I developers training class was given to trainees from across the ROS-Industrial Consortium membership.

Whether you are just starting to use or are already experienced in ROS 2, the training offered something for all levels. Newcomers learned the ropes, getting a solid foundation in the framework’s core concepts, while experienced developers delved into advanced topics such as advanced motion planning, including tuning optimization contsraint parameters.

Currently training is on ROS 2 Humble, delivered through an AWS EC2 instance. On the first day, the attendees were divided into two groups: beginner ROS developers and advanced ROS developers. The advanced group learned how to set up a basic motion planning pipeline in Tesseract, where they refined a planning pipeline increasing robustness. By the end of the day students were adding unique customizations to the pipeline.

The beginner group focused on learning the fundamentals of ROS 2, including workspace structure and best practices for adding scripts and building the workspace. They also learned about creating packages / nodes, topics (publishers / subscribers), messages, services, actions, launch files and command line parameters.

Day 2, groups gathered to learn how to develop URDF/XACROs to describe a robot, as well as how to use TFs and create a MoveIt package for an industrial robot for motion planning in a simulation environment.

Day 3 started with a tour that focused on ROS 2 robotic systems within the Robotics Department at SwRI, where the instructors were able to give insights on the capabilities of ROS 2 in more tangible working industrial examples.

In person attendees stepping through the scan-n-plan workshop demonstration

Wrapping up the training participants were given the opportunity to share with instructors and the group how they intended to use ROS in their projects and where already under way the instructors were able to provide additional assistance to address issues in their application development back home.

Hybrid training always presents challenges in making sure those online get the same attention as those in the room. However, it was rewarding to assist attendees in getting deeper into ROS 2, whether they were just starting out or wanting to expand their solution set or add features to an ongoing project. As always, as instructors, we always look forward to seeing how they apply these new skills and always look forward to interacting through the repositories or various ROS/ROS-I collaborative events.

If you are interested in an upcoming training class, they are regularly posted at https://rosindustrial.org/events-summary.

[WWW] https://rosindustrial.org/news/2024/11/21/unlocking-for-industrial-users-the-power-of-ros-2-ros-i-october-training-highlights

ROS Discourse General: Reference implementation of Zenoh-pico to micro-ROS

Zenoh is a new communication middleware that ZettaScale has developed.
At eSOL, we have been porting Zenoh-pico to micro-ROS.
Zenoh-pico is Zenoh’s implementation for microcontrollers.

This post is the announcement of the prototype of Zenoh-pico adaptation to micro-ROS.

Although it is still experimental, we confirmed it would work on the generic (Linux) or Raspbian platforms of micro-ROS.
Ideally, we would have liked to include Zenoh in the transport specification.
However, we treated it as an RTOS equivalent since Zenoh can select TCP, UDP, or serial.

This Zenoh-pico and micro-ROS system is assumed to communicate with “rmw_zenoh” on ROS. It is set as an environment variable, RMW_IMPLEMENTATION.
They can communicate directly with rmw_zenoh; the structure is just agent-less, like using embedded RTPS.

You can use it as a reference implementation. It would be even better if the ZettaScale and micro-ROS communities could discuss it.

Note:
As the previous post was from a personal account, I reposted it from the company account.

1 post - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/reference-implementation-of-zenoh-pico-to-micro-ros/40750

ROS Discourse General: Seeking Feedback from Students with Autonomous Robotics Project Experience

Hello everyone,

I’m conducting a study on skill development in autonomous robotics, specifically focusing on what students (bachelor’s, master’s, or PhD level) learn through hands-on project work. This study centers on practical experiences in projects like final assignments, student groups, and research initiatives—not typical classroom content.

If you’re currently a student involved in UAV or drone projects as part of your studies, I’d be grateful for your insights. This survey aims to uncover the unique skills and knowledge that students develop through direct, project-based work in aerial and autonomous systems.

Survey Link: https://forms.gle/ncuaduBtkcMWGfGs7

Thank you for your time and for sharing this with anyone who may be interested!

1 post - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/seeking-feedback-from-students-with-autonomous-robotics-project-experience/40727

ROS Discourse General: Another boring SMACC demo in IsaacSim

Hi Everyone,
Long time no see.

We released another demo video in IsaacSim back in Sept on Linkedin. Hope you like it.

This is what an autonomous application demo should look like.

As always, here’s the source code:

One interesting thing about this application, and the others in the repo, is that they’re built using NVIDIA Isaac ROS Dev Containers. Which are totally awesome.

https://nvidia-isaac-ros.github.io/getting_started/dev_env_setup.html

The readme for this application lays out the steps of how to use them.

I also gave a talk about the application at the NVIDIA Jetson AI Research Group last week…

JETSON AI LAB | SMACC State Machines in ROS2 & Kaya sim2real workflow (11/12/2024)

I’ve been really impressed with the Jetson AI Research Group and some of the really awesome people involved.

Cheers,

1 post - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/another-boring-smacc-demo-in-isaacsim/40709

ROS Discourse General: Next Client Library WG Meeting: Friday 22nd November 2024

Hi,
The next meeting of the Client Library Working Group will be this Friday, 22nd November 2024 at 8 AM Pacific Time.

The agenda for now includes:

Everyone is welcome to join.
If you have topics you want to discuss, feel free to anticipate them here in this thread.

5 posts - 3 participants

Read full topic

[WWW] https://discourse.ros.org/t/next-client-library-wg-meeting-friday-22nd-november-2024/40703

ROS Discourse General: Kobuki Charging Station Schematic (TurteBot 2)?

Hi,

I know it’s a old platform these days. But one of my work horse’s is a Kobuki/Turtlebot 2. I’d like to build a couple more charging bases for it. Can’t buy them any more. Wondered if anyone might know of the schematic for it. Charging circuits specifically.

Thanks

Mark

1 post - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/kobuki-charging-station-schematic-turtebot-2/40698

ROS Discourse General: ROSCon 2024 Videos are Now Available

ROSCon 2024 Videos are Now Available

Hi Everyone,

The videos from ROSCon 2024 in Odense are now available on the ROSCon Website (see the program), this Vimeo showcase, and in the ROS documentation. The ROSCon website also includes the slides from all the talks at ROSCon. I have also included a list of all the videos below.

I want to thank AMD for being our 2024 ROSCon video sponsor, their generous support makes the ROSCon live stream and videos possible.

https://vimeo.com/1024971401?app_id=122963

2024 ROSCon Talks

4 posts - 3 participants

Read full topic

[WWW] https://discourse.ros.org/t/roscon-2024-videos-are-now-available/40677

ROS Discourse General: Introducing ros2-pkg-create - New Powerful ROS 2 Package Generator

We would like to present our newly open-sourced ROS 2 Package Generator, simply called ros2-pkg-create. It supports C++ and Python nodes as well as advanced features such as C++ components or lifecycle nodes.

Instantly try it out by running:

pip install ros2-pkg-create
ros2-pkg-create --template ros2_cpp_pkg .

image

Given the recent interest in Turtle Nest, we felt it’s about time to open-source our own take at a ROS 2 package generator, which use for all of our new packages at Institute for Automotive Engineering (ika) at RWTH Aachen University.

ros2-pkg-create is an interactive CLI tool for quickly generating ROS 2 packages from basic pub/sub nodes to complex lifecycle components. It is meant to replace the official ros2 pkg create command.

You can either directly control all options through command-line arguments or use the interactive questionnaire to walk through. No more memorization of available options for such a generation tool.

ros2-pkg-create can generate ROS 2 C++ Packages, Python Packages, and Interfaces Packages. The supported features include:

  • C++ Package: publisher, subscriber, parameter loading, launch file, service server, action server, timer callback, component, lifecycle node, docker-ros
  • Python Package: publisher, subscriber, parameter loading, launch file, service server, action server, timer callback, docker-ros
  • Interfaces Package: message, service, action

Under the hood, the templates are implemented using the Jinja templating engine, which allows for easy customizability.

We are very much looking forward to your feedback!

Best,
Lennart from Aachen

7 posts - 4 participants

Read full topic

[WWW] https://discourse.ros.org/t/introducing-ros2-pkg-create-new-powerful-ros-2-package-generator/40669

ROS Discourse General: Cloud Robotics WG Meeting 2024-11-18

Please come and join us for this coming meeting at 1700-1800 UTC on Monday 21st November 2024, which will be a general catch-up! If you’re passionate about robotics or the cloud, come and say hello. We plan to discuss the latest news from the group and from the world of Cloud Robotics.

Last meeting, we had a guest talk from Julien Enoch on Eclipse Zenoh. If you’re interested to see the talk, we have published it on YouTube.

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.

My apologies for the late notice on this particular meeting. I have been off sick, and just now returned on the day of the meeting. Future meetings will have more notice, and the Meetings page on the Cloud Robotics Hub will always be the first to be updated with future meetings.

Hopefully we will see you there!

1 post - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/cloud-robotics-wg-meeting-2024-11-18/40668

ROS Discourse General: New Packages for Noetic 2024-11-15

We’re happy to announce 0 new packages and 40 updates are now available in ROS Noetic. This sync was tagged as noetic/2024-11-15.

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

Package Updates for ROS Noetic

Added Packages [0]:

Updated Packages [40]:

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:

  • Analog Devices
  • Atsushi Watanabe
  • Jose-Luis Blanco-Claraco
  • Martin Pecka
  • Rob Fisher
  • Stefan Laible

1 post - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/new-packages-for-noetic-2024-11-15/40633

ROS Discourse General: ROS News for the Week for November 11th, 2024

ROS News for the Week for November 11th, 2024


May 2023 - Nov 2024

We’re preparing for the final Iron Irwini patch and sync. If you are still using Iron now is the time to upgrade to Jazzy.

:skull: Here’s your regular reminder that Gazebo Classic goes end of life in JANUARY and ALL OF ROS 1, INCLUDING NOETIC, GOES END OF LIFE NEXT MAY. We’re working on a few surprises internally to motivate the last stragglers to move over to ROS 2 and modern Gazebo.


hackster
Check out this amazing pick and place demo using ROS 2 on Hackster. The project makes use of an Arduino Braccio++ Robotic Arm, a Luxonis depth camera, ROS 2, microROS, and Edge Impulse.


392aa4516dfa2e28f2958bada73ce89c20ba261d_2_690x393 (1)

This week some of our colleagues in Japan released Space Station OS based on ROS. The idea here is to create a standard ROS interface to space stations to enable robotic space station tending.


ROS_2_Comms_Troubleshooting_Flowchart

Clearpath’s amazing “Demystifying ROS 2 Networking” workshop at ROSCon includes this amazing network issue debugging flowchart that is worth sharing.

ROSCon 2024 videos and slides will be released Monday. :wink:

Events

News

ROS

Got a Minute?

Answering just one question a week on Robotics Stack Exchange would really help out the ROS community!

3 posts - 3 participants

Read full topic

[WWW] https://discourse.ros.org/t/ros-news-for-the-week-for-november-11th-2024/40631

ROS Discourse General: LBR-Stack paper just published in Journal of Open Source Software (JOSS)

I noticed this paper come through the JOSS Mastodon feed:

LBR-Stack: ROS 2 and Python Integration of KUKA FRI for Med and IIWA Robots

The authors submitted the paper back in 2023, but it finally published today. Congrats to them for getting it over the line!

1 post - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/lbr-stack-paper-just-published-in-journal-of-open-source-software-joss/40626

ROS Discourse General: Teaching Robots to Perform Tasks: Our Open-Source Project for Imitation Learning!

Screencastfrom10-25-202405_34_01PM-ezgif.com-video-to-gif-converter

We developed an open-source system that simplifies the training of robots to perform tasks through imitation learning. Our setup allows you to collect data, control robots, and train models in both real and simulated environments.

The system is built on the Diffusion Policy model and the ROS2 framework. To help you get started, we provide a pre-trained model and datasets, but you can also collect your own data for customized training.

We believe that imitation learning can be useful in dynamic environments where object positions can change, and our project aims to simplify this imitation learning process
We invite you to explore its capabilities and contribute to its growth! If you’re interested in training robots to perform tasks using imitation learning, check it out and let us know what you think!

1 post - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/teaching-robots-to-perform-tasks-our-open-source-project-for-imitation-learning/40617

ROS Discourse General: Status of Colcon building "standards-based" Python packages?

I have read the (now closed) topic: Call For Testing: Standards-based Python packaging with colcon. But it seems not much has happened in the linked repo since then. I have some co-workers who are asking why they need to use setup.py to use ROS, so I’m investigating for them. Should I try using this colcon-python-project Colcon extension? Or was the effort abandoned? Should I be using something else?

I also found this Poetry Colcon extension. I feel indifferent about Poetry, but could try it out. I would appreciate any sharing of thoughts about it.

13 posts - 9 participants

Read full topic

[WWW] https://discourse.ros.org/t/status-of-colcon-building-standards-based-python-packages/40578

ROS Industrial: ROS-Industrial Consortium Asia Pacific Annual Summit 2024

The ROS-Industrial Consortium Asia Pacific Annual Summit 2024, themed "Robotics in the Age of AI," concluded successfully, marking a significant milestone for the robotics and automation sector in Asia Pacific. Hosted by the ROS-Industrial Consortium Asia Pacific (RIC Asia Pacific) and managed by the Advanced Remanufacturing and Technology Center (ARTC), the summit brought together over 150 international participants, including industry leaders, researchers, and innovators, who gathered to explore the impact of AI-powered robotics on industries.

WhatsApp Image 2024-11-07 at 4.20.03 PM.jpeg
WhatsApp Image 2024-11-07 at 4.20.05 PM (1).jpeg
WhatsApp Image 2024-11-07 at 4.20.05 PM.jpeg
WhatsApp Image 2024-11-07 at 4.20.08 PM (1).jpeg
WhatsApp Image 2024-11-07 at 4.20.08 PM.jpeg
WhatsApp Image 2024-11-07 at 4.20.09 PM.jpeg
WhatsApp Image 2024-11-07 at 4.20.10 PM (1).jpeg
WhatsApp Image 2024-11-07 at 4.20.10 PM.jpeg
WhatsApp Image 2024-11-07 at 4.20.11 PM (1).jpeg
WhatsApp Image 2024-11-07 at 4.20.11 PM.jpeg
WhatsApp Image 2024-11-07 at 4.20.12 PM (1).jpeg
WhatsApp Image 2024-11-07 at 4.20.12 PM (2).jpeg
WhatsApp Image 2024-11-07 at 4.20.12 PM (3).jpeg
WhatsApp Image 2024-11-07 at 4.20.12 PM.jpeg
WhatsApp Image 2024-11-07 at 4.20.13 PM (1).jpeg
WhatsApp Image 2024-11-07 at 4.20.13 PM.jpeg
WhatsApp Image 2024-11-07 at 4.20.14 PM (1).jpeg
WhatsApp Image 2024-11-07 at 4.20.14 PM (2).jpeg
WhatsApp Image 2024-11-07 at 4.20.14 PM.jpeg
WhatsApp Image 2024-11-07 at 4.20.15 PM (1).jpeg
WhatsApp Image 2024-11-07 at 4.20.15 PM.jpeg

This year’s summit featured an impressive agenda packed with expert talks, hands-on masterclasses, and an engaging tech marketplace, all designed to highlight how AI is transforming robotics across industries, especially in manufacturing, logistics, and physical security.

Day 1 Highlights

The first day of the summit opened with a series of insightful presentations by leaders from major organizations in the AI and robotics space.

Amazon Web Services (AWS) set the tone with a talk titled "AI and Robotics-Driven Innovations for Manufacturing Excellence." Presented by Mirela Juravle, Data and AI Specialist Lead at AWS, the session showcased how robotics and AI are being leveraged to support digital transformation efforts toward achieving "lights-out" manufacturing, a concept where factories operate autonomously without human intervention. AWS shared insights on the benefits of cloud services in scaling robotic operations and optimizing workflows for increased efficiency in manufacturing.

Next, Mitsuharu Sonehara, Manager at IHI Corporation’s Technology Planning Department, presented on IHI's vision of advancing robotics and automation within logistics. Titled "From Deep Sea to Deep Space," his talk explored IHI's work in using robotics for high-stakes applications, from underwater operations to outer space logistics. He detailed the challenges and opportunities in these extreme environments and highlighted how AI and robotics can revolutionize logistics operations of the future.

Swarooph Nirmal Seshadri, Chief Technology Officer at Kabam Robotics, shared insights on the transformation of physical security through robotics, intelligence, and connectivity. His session explored how AI-driven robots are becoming crucial in the security industry, enabling smarter monitoring, data gathering, and response systems that are safer and more efficient.

Dr. Dikai Liu, a solution architect from NVIDIA, followed with an exciting presentation on NVIDIA’s suite of services, which facilitates the acceleration of robotics and AI from simulation to real-world deployment. NVIDIA’s tools and platforms empower developers to simulate complex environments and rapidly prototype AI algorithms for robotics, ultimately shortening the timeline from concept to deployment.

An important announcement on ROS2 compatibility came from Mr. Steven Chong, Senior Business Development Manager at Mitsubishi Electric Asia. He announced the release of a ROS2 driver for the MELFA robot, enabling broader integration with the ROS ecosystem. This advancement allows Mitsubishi Electric’s industrial robots to seamlessly integrate with ROS2, opening up new possibilities for automation in various industries. More details can be found on the ROS-Industrial blog here.

Wrapping up the first day’s talks, Dr. Yang Geng, Assistant Director at IMDA, presented on "Embodied AI as the Next Leap in GenAI." He described how embodied AI, which focuses on giving AI systems a physical presence, can revolutionize industries, from customer service robots to healthcare assistants, by enhancing interactions and adaptability through AI.

Day 2 Highlights

The second day of the summit was equally informative, beginning with a presentation by Matt Robinson, Consortium Manager at ROS-Industrial Consortium America. He discussed the collective global effort to standardize ROS2 drivers, aiming to establish ROS2 as the default industrial standard for robotics software. Robinson emphasized the benefits of this standardization for interoperability and efficiency in automation.

Following Robinson, Vishnuprasad Prachandabhanu, Consortium Manager of ROS-Industrial Consortium Europe, shared ongoing efforts to implement ROS2 across various applications. He highlighted a substantial EU-backed initiative with a €60 million funding commitment toward developing AI for robotics across Europe, signifying a significant investment in the advancement of open-source robotics.

Mr. Eugene Goh of JM Vistec presented next, offering insights on the integration of vision systems in robotics. His talk emphasized how JM Vistec enables robots to "see," enhancing precision and capability in industrial tasks, from quality inspection to object recognition.

Concluding the speaker sessions, Dr. Kenneth Kwok from IHPC shared cutting-edge research on enabling human-robot collaboration, powered by AI. His session emphasized the importance of human-centered AI in creating safe, efficient, and collaborative environments where robots can work alongside humans in factories, warehouses, and more.

Masterclass Lineup Participants then moved to the masterclass sessions, which provided hands-on learning experiences across various aspects of AI and robotics. Each session was designed to deepen the practical knowledge and technical skills required for integrating AI with robotics.

Empowering Innovations with MELSOFT: Led by Mr. Liu Muyao, Software Application Engineer from Mitsubishi Electric Asia, this session focused on MELSOFT, Mitsubishi's integrated software environment, which enhances the control and flexibility of industrial robots.

Introduction to Reinforcement Learning for Robot Arm Manipulation: Hosted by Mr. Shalman Khan, Mr. Santosh Balaji, and Ms. Mercedes Ramesh from ROS-Industrial Consortium Asia Pacific, this session introduced reinforcement learning principles, showing participants how to apply these techniques to control robotic arms more effectively.

Introduction to Deep Learning with YOLO and ROS: Dr. Carlos Acosta, Robotics Specialist at Singapore Polytechnic, led a session on utilizing YOLO (You Only Look Once) with ROS for object detection. The masterclass offered participants a foundation in integrating deep learning algorithms with ROS to enhance robotic vision applications.

Introduction to Fleet Management with Open-RMF: This session, led by Dr. Ricardo Tellez, CEO of The Construct, demonstrated the Open-RMF (Robot Management Framework) for multi-robot fleet management. Participants learned how to manage multiple robots collaboratively, a critical capability for applications in large facilities like hospitals and factories.

Tech Marketplace Highlights The tech marketplace featured a diverse array of participants, including Megazo, Kabam Robotics, IHPC, Parasoft, and Pepperl+Fuchs. Each company showcased their latest innovations, giving attendees a firsthand look at cutting-edge robotics solutions and AI-driven technologies designed to tackle challenges in industries like manufacturing, logistics, and safety. The marketplace provided a vibrant space for networking, collaboration, and discovering new tools that could redefine industrial automation.

RIC-AP Annual Summit 2024 also announce 2025 exciting event as we welcome the largest ROS Conference, ROSCon 2025 to Singapore. This would be the first time ROSCon will be hosted in Singapore

Finally, on behalf of everyone at ROS-Industrial Consortium Asia Pacific, we would like to thank all participants and delegates for their enthusiasm and we look forward to RIC-AP Annual summit 2025.

To sign up for our upcoming events, register your interest via this link: [https://form.gov.sg/672480d8116743c2ed31c690]

[WWW] https://rosindustrial.org/news/2024/11/11/ros-industrial-consortium-asia-pacific-annual-summit-2024

ROS Industrial: Official ROS2 Driver Release for Mitsubishi Electric Industrial Robot MELFA: MELFA ROS2 Driver

Mitsubishi Electric aims to integrate their MELFA robots into the ROS2 ecosystem, allowing robotics developers and integrators to utilize their industry proven platform seamlessly in ROS-based applications.

By developing MELFA ROS2 packages, Mitsubishi Electric seeks to enable developers to leverage on the flexibility, modularity, and extensive support of ROS2 community coupled with proven global hardware support.

MELFA ROS2 Driver is a collaborative effort between ROS-I Consortium Asia Pacific and Mitsubishi Electric Asia. MELFA ROS2 Driver consists of modular components that allow users to interface with the robot’s motion control, state monitoring, and digital/analog I/O operations in ROS2 control framework. This development bridges the gap between Mitsubishi Electric automation hardware and ROS2, providing developers with the tools needed to build, deploy, and manage robotic applications on an industrial platform effectively.

MELFA ROS2 Driver I/O controllers enable cyclic communication between ROS2 and MELFA. Developers can leverage on the IQ platform through MELFA ROS2 Driver to access other Mitsubishi Electric automation products (such as PLC, HMI, motor drives, NC machines), utilize industrial networks (such as CC-Link, PROFINET, EtherCAT, EtherNet/IP, DeviceNet, etc) and explore time sensitive networks (such as CC-Link IE TSN).

MELFA ROS2 Driver is designed for flexibility, supporting various ROS2 packages such as MoveIt2 for motion planning and custom nodes for specialized tasks.

MELFA ROS2 driver will officially support 9 models in the first batch and will aim to support more than 20 models in the near future

  • RV-2FR

    RV-4FR

    RV-4FRL

    RV-7RL

    RV-13FRL

    RV-8CRL

  • RV-5AS

  • RH-6FRH5520

    RH-6CRH6020

Users can access detailed documentation and installation instructions from the official repository [https://github.com/Mitsubishi-Electric-Asia/melfa_ros2_driver] to get started or talk to the developers from Mitsubishi Electric on [https://github.com/orgs/Mitsubishi-Electric-Asia/discussions/1]

[WWW] https://rosindustrial.org/news/2024/11/7/official-ros2-driver-release-for-mitsubishi-electric-industrial-robot-melfa-melfa-ros2-driver

ROS Discourse General: Space Station OS released! - a future where anyone can develop space stations.

Space Station OS (SSOS) is an open-source development platform for space stations, built on ROS 2 to support interoperability, modularity, and scalability across various space station projects.

s-2400x1372_v-frms_webp_bc4a92a8-b3a1-4a9a-8479-31155ca43d05_middle

By unifying core functions like thermal control, power, and life support into reusable modules, Space Station OS provides a universal environment that allows engineers globally to develop and operate space stations collaboratively. This enables rapid innovation and cross-mission compatibility, lowering development costs and enhancing sustainable space station operations.

s-2400x1372_v-frms_webp_d9b850cb-0d38-4acf-9b85-dff902f3fb9a_middle

Space Station OS represents a global effort to democratize space station technology, welcoming contributions from the international aerospace and robotics communities.

Visit us:

SSOS_LogoMark_TextSide_White_BGBlack

7 posts - 4 participants

Read full topic

[WWW] https://discourse.ros.org/t/space-station-os-released-a-future-where-anyone-can-develop-space-stations/40552

ROS Discourse General: RobotCAD 4.0.0 - released! Let you make controllable robots from GUI

Ros2_controllers are intergrated to RobotCAD 4.0.0 and let you make controllable diff drive car, manipulator, etc just from RobotCAD GUI without programming.

Also sometime before was integrated PX4 autopilot. It makes synergy of making airal - land riding robots with manipulator in 1 hour. See functionality demonstration.

RobotCAD 4.0.0 functionality demo
RobotCAD 4.0.0 functionality demo

Moreover you can extend RobotCAD controllers by adding your generic controller to ros2_controllers repository by pull request (or locally at your computer). And after that you will be able to construct your specific controllable tool via RobotCAD GUI and automatically generate code of ROS2 package and docker for it.

RobotCAD repository

1 post - 1 participant

Read full topic

[WWW] https://discourse.ros.org/t/robotcad-4-0-0-released-let-you-make-controllable-robots-from-gui/40545

ROS Discourse General: ROS News for the Week of November 4th, 2024

ROS News for the Week of November 4th, 2024


ROSCon2024Group (1)

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


Screenshot from 2024-11-08 12-06-01

@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.


Copy of ROSBTBAug24

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.


MELFA ROS2 Driver Demo

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.


366250611-56308d9a-8483-4be6-96dd-5acec60ff59c

:rocket: 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

News

ROS

Got a minute? :mantelpiece_clock:

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

Read full topic

[WWW] 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.

image

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.

image

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.

image

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 :rocket:

image

If you are interested, please contact us.

thanks,
Tomoya

5 posts - 3 participants

Read full topic

[WWW] https://discourse.ros.org/t/announcement-sony-robotics-solution-amr-agv-with-ros-2/40495

ROS Discourse General: Open Hardware Summit 2025 CFP

header

Hi Everyone,

I want to take off my ROS hat :billed_cap: for a second and put on my Open Source Hardware Association (OSHWA) hat :cowboy_hat_face: 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…

image

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

Read full topic

[WWW] https://discourse.ros.org/t/open-hardware-summit-2025-cfp/40493

Wiki: TullyFoote/TestPlanetRSS (last edited 2014-09-25 22:49:53 by TullyFoote)

Except where otherwise noted, the ROS wiki is licensed under the
Creative Commons Attribution 3.0