Planet ROS
Planet ROS - http://planet.ros.org
Planet ROS - http://planet.ros.org http://planet.ros.org
ROS Discourse General: ROS /cmd_vel MQTT bridge
Hey all,
I decided to create a small ros mqtt bridge just for the /cmd_vel topic. I do know that ros_mqtt bridge packages exist but I thought this would be easier to set up and use.
I’m using this to connect to a robot that’s not easily accessible via rosserial or rosbridge (Mindstorms ev3). MQTT makes it easy to extend ROS’s capability to such resource-constrained robots.
If anyone else is in the same situation or would like to contribute in any way, the package is linked below -
1 post - 1 participant
![[WWW] [WWW]](/moin_static197/rostheme/img/moin-www.png)
ROS Discourse General: ROS News for the Week of January 10th, 2021
ROS News for the Week of 1/10/2021
ROS Goes Racing
ROS 2 Foxy Leg Detector
Events
- Recording: Ignition Community Meeting on Fuel
- Recording: ROS Industrial EU Conference
- Recording: Secure MoveIt demo from Security WG
- 1/25/2021 Webots ROS 2 Meeting
Hardware
- First RISC-V Linux SBC Run
- New Toy Arm + Vision + Jetson Kit
- Bosch on microROS
- microROS on ESP32!
- New ROS Compatible Depth Camera
- microROS on Arduino
- PX4 MAVROS Tutorial in Python
- K3lso Quad Build on Hackaday
News
ROS Packages
- Kinetic Update
- Open Dog Runs ROS for Autonomy
- ROS 2 Dashing Update
- ROS Touchscreen Dashboard Package
- ROS 2 OpenVino Toolkit 0.9.0 Released
- Safety Hazards and Risks in ROS
- ROS 2 Foxy Compatible Leg Detector
ROS Questions
4 posts - 2 participants
![[WWW] [WWW]](/moin_static197/rostheme/img/moin-www.png)
ROS Discourse General: New packages for ROS 2 Dashing DIademata 2021-01-14
New year, new Dashing sync! Thanks as ever to those who continue to support the Dashing release.
It’s still several months away but the end of Dashing’s support cycle is coming in May 2021.
At the end of Dashing’s support cycle there will no longer be any active ROS 2 distribution with Tier 1 support for Ubuntu 18.04. ROS 2 Foxy Fitzroy is the latest LTS release of ROS 2 and will be supported until May 2023.
Package Updates for dashing
Note that package counts include dbgsym packages which have been filtered out from the list below
Added Packages [2]:
- ros-dashing-tvm-vendor: 0.7.2-1
Updated Packages [27]:
- ros-dashing-autoware-auto-msgs: 0.1.0-1 -> 1.0.0-1
- ros-dashing-gurumdds-cmake-module: 0.7.7-1 -> 0.7.8-1
- ros-dashing-rmw-gurumdds-cpp: 0.7.8-1 -> 0.7.9-1
- ros-dashing-rmw-gurumdds-shared-cpp: 0.7.8-1 -> 0.7.9-1
- ros-dashing-ros1-bridge: 0.7.7-1 -> 0.7.8-1
- ros-dashing-rqt-robot-monitor: 1.0.3-1 -> 1.0.4-1
- ros-dashing-serial-driver: 0.0.5-1 -> 0.0.6-4
- ros-dashing-system-modes: 0.4.1-1 -> 0.4.2-1
- ros-dashing-system-modes-examples: 0.4.1-1 -> 0.4.2-1
- ros-dashing-turtlebot3: 2.1.0-1 -> 2.1.1-2
- ros-dashing-turtlebot3-bringup: 2.1.0-1 -> 2.1.1-2
- ros-dashing-turtlebot3-cartographer: 2.1.0-1 -> 2.1.1-2
- ros-dashing-turtlebot3-description: 2.1.0-1 -> 2.1.1-2
- ros-dashing-turtlebot3-example: 2.1.0-1 -> 2.1.1-2
- ros-dashing-turtlebot3-navigation2: 2.1.0-1 -> 2.1.1-2
- ros-dashing-turtlebot3-node: 2.1.0-1 -> 2.1.1-2
- ros-dashing-turtlebot3-teleop: 2.1.0-1 -> 2.1.1-2
- ros-dashing-udp-driver: 0.0.5-1 -> 0.0.6-4
- ros-dashing-v4l2-camera: 0.1.1-1 -> 0.1.2-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:
- Aaron Blasdel
- Apex.AI, Inc.
- Arne Nordmann
- Dirk Thomas
- Josh Whitley
- Joshua Whitley
- Junho Lee
- Sander G. van Dijk
- Will Son
1 post - 1 participant
![[WWW] [WWW]](/moin_static197/rostheme/img/moin-www.png)
ROS Discourse General: Gazebo support for ros2_control breakout session
Hello there,
Our last ros2_control WG meeting asked for a more in-depth discussions regarding Gazebo support.
We decided to create a separate breakout session for this which will take place on 2021-01-20T18:00:00Z.
Come prepared! There will be no time for a summary of the framework so please familiarize yourself with ros2_control, specifically controller_manager, SystemInterface, SensorInterface and ActuatorInterface.
For more background on Gazebo, make sure to read this PR: gazebo_ros2_control#44
The direct link to the meeting is this one:
But also feel free to add the event from the ROS Events calendar:
note that the calendar uses PST:
See you there,
Bence
Note: Sometimes, Google Meet links don’t persist. I’ll try to ensure that the link above is up to date, but in case you can’t find people in the meeting room, double check the link on the calendar event, that is the right place.
2 posts - 2 participants
![[WWW] [WWW]](/moin_static197/rostheme/img/moin-www.png)
ROS Discourse General: New packages for Kinetic Kame 2021-01-12
We’re happy to announce an update of 47 packages for Kinetic Kame for the first release in 2021.
Thank you to everyone who helped make these updates possible!
Full details are below.
Package Updates for kinetic
Added Packages [0]:
Updated Packages [47]:
- ros-kinetic-amcl: 1.14.8-1 -> 1.14.9-1
- ros-kinetic-audio-capture: 0.3.9-1 -> 0.3.10-1
- ros-kinetic-audio-common: 0.3.9-1 -> 0.3.10-1
- ros-kinetic-audio-common-msgs: 0.3.9-1 -> 0.3.10-1
- ros-kinetic-audio-play: 0.3.9-1 -> 0.3.10-1
- ros-kinetic-axis-camera: 0.3.0-0 -> 0.3.1-1
- ros-kinetic-base-local-planner: 1.14.8-1 -> 1.14.9-1
- ros-kinetic-carrot-planner: 1.14.8-1 -> 1.14.9-1
- ros-kinetic-clear-costmap-recovery: 1.14.8-1 -> 1.14.9-1
- ros-kinetic-costmap-2d: 1.14.8-1 -> 1.14.9-1
- ros-kinetic-costmap-cspace: 0.10.4-1 -> 0.10.5-1
- ros-kinetic-dwa-local-planner: 1.14.8-1 -> 1.14.9-1
- ros-kinetic-fake-localization: 1.14.8-1 -> 1.14.9-1
- ros-kinetic-global-planner: 1.14.8-1 -> 1.14.9-1
- ros-kinetic-joystick-interrupt: 0.10.4-1 -> 0.10.5-1
- ros-kinetic-libmavconn: 1.5.0-1 -> 1.5.1-1
- ros-kinetic-librealsense2: 2.40.0-1 -> 2.41.0-1
- ros-kinetic-map-organizer: 0.10.4-1 -> 0.10.5-1
- ros-kinetic-map-server: 1.14.8-1 -> 1.14.9-1
- ros-kinetic-mavlink: 2020.12.12-1 -> 2021.1.4-1
- ros-kinetic-mavros: 1.5.0-1 -> 1.5.1-1
- ros-kinetic-mavros-extras: 1.5.0-1 -> 1.5.1-1
- ros-kinetic-mavros-msgs: 1.5.0-1 -> 1.5.1-1
- ros-kinetic-move-base: 1.14.8-1 -> 1.14.9-1
- ros-kinetic-move-slow-and-clear: 1.14.8-1 -> 1.14.9-1
- ros-kinetic-moveit-python: 0.3.4-1 -> 0.3.5-1
- ros-kinetic-nav-core: 1.14.8-1 -> 1.14.9-1
- ros-kinetic-navfn: 1.14.8-1 -> 1.14.9-1
- ros-kinetic-navigation: 1.14.8-1 -> 1.14.9-1
- ros-kinetic-neonavigation: 0.10.4-1 -> 0.10.5-1
- ros-kinetic-neonavigation-common: 0.10.4-1 -> 0.10.5-1
- ros-kinetic-neonavigation-launch: 0.10.4-1 -> 0.10.5-1
- ros-kinetic-novatel-oem7-driver: 1.1.0-1 -> 2.0.0-1
- ros-kinetic-novatel-oem7-msgs: 1.1.0-1 -> 2.0.0-1
- ros-kinetic-obj-to-pointcloud: 0.10.4-1 -> 0.10.5-1
- ros-kinetic-planner-cspace: 0.10.4-1 -> 0.10.5-1
- ros-kinetic-realsense2-camera: 2.2.20-1 -> 2.2.21-1
- ros-kinetic-realsense2-description: 2.2.20-1 -> 2.2.21-1
- ros-kinetic-robot-pose-ekf: 1.14.8-1 -> 1.14.9-1
- ros-kinetic-rotate-recovery: 1.14.8-1 -> 1.14.9-1
- ros-kinetic-safety-limiter: 0.10.4-1 -> 0.10.5-1
- ros-kinetic-sound-play: 0.3.9-1 -> 0.3.10-1
- ros-kinetic-test-mavros: 1.5.0-1 -> 1.5.1-1
- ros-kinetic-track-odometry: 0.10.4-1 -> 0.10.5-1
- ros-kinetic-trajectory-tracker: 0.10.4-1 -> 0.10.5-1
- ros-kinetic-voxel-grid: 1.14.8-1 -> 1.14.9-1
- ros-kinetic-ypspur-ros: 0.3.1-1 -> 0.3.4-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:
- Atsushi Watanabe
- Austin Hendrix
- Chris Iverach-Brereton
- David V. Lu!!
- Michael Ferguson
- NovAtel Support
- Sergey Dorodnicov
- Vladimir Ermakov
1 post - 1 participant
![[WWW] [WWW]](/moin_static197/rostheme/img/moin-www.png)
ROS Discourse General: ROS2 Foxy compatible leg detector
We at mowito have released a ROS2 Foxy port of Leg Detector for obstacle detection and human detection.
Here’s a screenshot of its working on a 0.33 resolution scanner.
The original repository worked only on ROS1 Melodic and wasn’t updated for a long time. We have ported the entire code to work on ROS2 Foxy, and have tested it on the example bags. It takes a 2D LiDAR scan and outputs an array of tracked legs in the vicinity of the robot.
If you want to try it out and give us feedback, follow the instructions here.
4 posts - 2 participants
![[WWW] [WWW]](/moin_static197/rostheme/img/moin-www.png)
ROS Discourse General: CES unveils ROS Indy racecar live 2PM EDT / 8PM CET Jan 11th
CES 2021 is unveiling a very fast robot 2PM EDT, 8PM CET today Jan 11th, watch the press conference here: indyautonomouschallenge.com
Autoware.Auto ROS 2 CycloneDDS OpenCV on rugged ADLINK Technology NVIDIA AI robotics controllers with 3 LiDARs, 5 cameras, 2 Novotel GNS w IMU, 4 Aptiv radars, New Eagle Raptor ECU with Schaeffler drive-by-wire system installed by AutonomouStuff. University robotics teams are racing a fleet of these modified Dallara IL-15 racecars head-to-head at Indy Oct 23rd.
1 post - 1 participant
![[WWW] [WWW]](/moin_static197/rostheme/img/moin-www.png)
ROS Discourse General: Community Meeting: ROS 2 and Webots
We are happy to announce the first ROS 2 and Webots Community Meeting to be held on January 25th, 2021 at 8am PST
In your time zone: 2021-01-25T16:00:00Z
Agenda:
- Introduction to Webots and ROS 2 support [Olivier Michel, Cyberbotics Ltd, Switzerland, 10 minutes]
- Contributions to the URDF2Webots converter [Simon Steinmann, DLR, Germany, 15 minutes + 5 minutes for questions]
- Roadmap for Webots and ROS 2 [Darko Lukić, Cyberbotics Ltd., Switzerland, 10 minutes]
- Round table and QA session [all, 20 minutes]
Total duration of the meeting: 60 minutes.
Meeting ID: https://meet.google.com/xpc-ugcq-fah
We will share a video of the meeting afterwards.
Looking forward to your participation.
Cheers,
-Olivier
3 posts - 2 participants
![[WWW] [WWW]](/moin_static197/rostheme/img/moin-www.png)
ROS Discourse General: ROS News for January 8th, *2021*
ROS News for January 8th, 2021
NAO Joint Control now in Ignition Fuel
Gazebo Contributions Over Time
Events
- 2/12/21 MoveIt Security Demo
- 2/12/21 Gazebo Community Meeting – intro to Ignition Fuel
- Webots Community Meeting (~Mid January)
ROS Packages
- NAO Robot Joint Control in Ignition Fuel
- 28 New and 40 Updated Packages in Foxy (lots of goodies in this one)
- Hadabot Revamps Curricula
- MoveIt Cartesian Planner Guide
- ICRA Prepub: Latency in ROS2 RMWs
- Project Dave 3.0: Underwater Robotics Simulation
- Ignition Blueprint End of Life
- ROS 2 Control for Foxy
- Fergs Rescue Robot Ranch Recap
- Gazebo Contributions over Time
- 50 New and 324 Updated Packages in Rolling Ridley
- Noetic on Windows
- MicroROS on Arduino IDE!!!
- ROS on Windows!
- Plansys 2, First Anniversary and Update
- Eloquent is now end of life
- ROS driver for ABB robots
- Kinetic Update: 6 New and 43 Updated Packages
- ROS PID Controller Tuning in Jupyter Notebook
- Melodic Update: 29 New and 108 Updated Packages
- Short Survey: New SBC Support for TB3
- Maintainer Wanted: Satellite Imagery in RVIZ package
- CARMA / DoT ROS 2 Migration Plan
- FreeRobotics.tools needs a maintainer
- Nav2 Speed Restrictions
- Webots + ROS 2 Foxy
- ROS for Human-Robot Interaction Paper
Robot News
- Remo.tv on Hackster Webcast (one of my favorite non-ROS Bay Area robot startups)
- DARPA SubT final event site and date announced
- Reddit: How to Get Started in Robotics Megathread
- Should Robots have Legal Standing?
- @fergs proposes ROS 2 Tuesday Tips – should this be a thing?
- Robotis Talks: interview of Anouk Wipprecht
- FedEx Robots working for the Holidays
- AMP Robotics Raises $55M Series B for Recycling
- Teledyne to Acquire FLIR Systems
- Dancing Boston Dynamics Robots
-
Ouster Goes Public with SPAC Merger
It has been a few weeks since the last update, and hopefully I didn’t miss anything. If you have an announcement feel free to drop it below.
1 post - 1 participant
![[WWW] [WWW]](/moin_static197/rostheme/img/moin-www.png)
ROS Discourse General: ROS2 latency using different node setups
Hi there,
as posted in this post, we recently submitted a paper to ICRA focussing on latency entailed by ROS2. We profile the latency to pinpoint the bottleneck and to find potential improvements. Different parameters are varied, e.g.
- publisher frequency
- number of nodes
- DDS middleware
- msg size
Have a closer look at the preprint: https://arxiv.org/pdf/2101.02074.pdf
Cheers,
urczf
6 posts - 3 participants
![[WWW] [WWW]](/moin_static197/rostheme/img/moin-www.png)
ROS Discourse General: New packages for Foxy Fitzroy 2021-01-07
We’re happy to announce new packages and updates for Foxy Fitzroy!
Package Updates for foxy
Added Packages [28]:
- ros-foxy-controller-interface: 0.1.2-1
- ros-foxy-controller-manager: 0.1.2-1
- ros-foxy-controller-manager-msgs: 0.1.2-1
- ros-foxy-effort-controllers: 0.1.1-1
- ros-foxy-forward-command-controller: 0.1.1-1
- ros-foxy-grasping-msgs: 0.4.0-1
- ros-foxy-hardware-interface: 0.1.2-1
- ros-foxy-joint-state-controller: 0.1.1-1
- ros-foxy-joint-trajectory-controller: 0.1.1-1
- ros-foxy-plansys2-bringup: 1.0.7-2
- ros-foxy-plansys2-bt-actions: 1.0.7-2
- ros-foxy-plansys2-core: 1.0.7-2
- ros-foxy-plansys2-domain-expert: 1.0.7-2
- ros-foxy-plansys2-executor: 1.0.7-2
- ros-foxy-plansys2-lifecycle-manager: 1.0.7-2
- ros-foxy-plansys2-msgs: 1.0.7-2
- ros-foxy-plansys2-pddl-parser: 1.0.7-2
- ros-foxy-plansys2-planner: 1.0.7-2
- ros-foxy-plansys2-popf-plan-solver: 1.0.7-2
- ros-foxy-plansys2-problem-expert: 1.0.7-2
- ros-foxy-plansys2-terminal: 1.0.7-2
- ros-foxy-position-controllers: 0.1.1-1
- ros-foxy-ros2-control: 0.1.2-1
- ros-foxy-ros2controlcli: 0.1.2-1
- ros-foxy-rosauth: 2.0.2-1
- ros-foxy-test-robot-hardware: 0.1.2-1
- ros-foxy-tvm-vendor: 0.7.2-1
- ros-foxy-velocity-controllers: 0.1.1-1
Updated Packages [40]:
- ros-foxy-autoware-auto-msgs: 0.1.0-1 -> 1.0.0-1
- ros-foxy-mavlink: 2020.11.11-1 -> 2021.1.4-1
- ros-foxy-message-filters: 3.2.4-1 -> 3.2.5-1
- ros-foxy-plotjuggler: 3.0.4-1 -> 3.0.7-1
- ros-foxy-plotjuggler-ros: 1.0.0-2 -> 1.0.2-1
- ros-foxy-rclpy: 1.0.4-1 -> 1.0.5-1
- ros-foxy-ros2bag: 0.3.5-1 -> 0.3.6-1
- ros-foxy-ros2trace: 1.0.4-1 -> 1.0.5-2
- ros-foxy-rosbag2: 0.3.5-1 -> 0.3.6-1
- ros-foxy-rosbag2-compression: 0.3.5-1 -> 0.3.6-1
- ros-foxy-rosbag2-converter-default-plugins: 0.3.5-1 -> 0.3.6-1
- ros-foxy-rosbag2-cpp: 0.3.5-1 -> 0.3.6-1
- ros-foxy-rosbag2-storage: 0.3.5-1 -> 0.3.6-1
- ros-foxy-rosbag2-storage-default-plugins: 0.3.5-1 -> 0.3.6-1
- ros-foxy-rosbag2-test-common: 0.3.5-1 -> 0.3.6-1
- ros-foxy-rosbag2-tests: 0.3.5-1 -> 0.3.6-1
- ros-foxy-rosbag2-transport: 0.3.5-1 -> 0.3.6-1
- ros-foxy-shared-queues-vendor: 0.3.5-1 -> 0.3.6-1
- ros-foxy-sqlite3-vendor: 0.3.5-1 -> 0.3.6-1
- ros-foxy-system-modes: 0.4.1-1 -> 0.4.2-1
- ros-foxy-system-modes-examples: 0.4.1-1 -> 0.4.2-1
- ros-foxy-tracetools: 1.0.4-1 -> 1.0.5-2
- ros-foxy-tracetools-launch: 1.0.4-1 -> 1.0.5-2
- ros-foxy-tracetools-read: 1.0.4-1 -> 1.0.5-2
- ros-foxy-tracetools-test: 1.0.4-1 -> 1.0.5-2
- ros-foxy-tracetools-trace: 1.0.4-1 -> 1.0.5-2
- ros-foxy-webots-ros2: 1.0.3-1 -> 1.0.5-1
- ros-foxy-webots-ros2-abb: 1.0.3-1 -> 1.0.5-1
- ros-foxy-webots-ros2-core: 1.0.3-1 -> 1.0.5-1
- ros-foxy-webots-ros2-demos: 1.0.3-1 -> 1.0.5-1
- ros-foxy-webots-ros2-epuck: 1.0.3-1 -> 1.0.5-1
- ros-foxy-webots-ros2-examples: 1.0.3-1 -> 1.0.5-1
- ros-foxy-webots-ros2-importer: 1.0.3-1 -> 1.0.5-1
- ros-foxy-webots-ros2-msgs: 1.0.3-1 -> 1.0.5-1
- ros-foxy-webots-ros2-tiago: 1.0.3-1 -> 1.0.5-1
- ros-foxy-webots-ros2-turtlebot: 1.0.3-1 -> 1.0.5-1
- ros-foxy-webots-ros2-tutorials: 1.0.3-1 -> 1.0.5-1
- ros-foxy-webots-ros2-universal-robot: 1.0.3-1 -> 1.0.5-1
- ros-foxy-webots-ros2-ur-e-description: 1.0.3-1 -> 1.0.5-1
- ros-foxy-zstd-vendor: 0.3.5-1 -> 0.3.6-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:
- Apex.AI, Inc.
- Arne Nordmann
- Bence Magyar
- Christophe Bedard
- Cyberbotics
- Davide Faconti
- Ethan Gao
- Francisco Martin Rico
- Josh Whitley
- Karsten Knese
- Michael Ferguson
- Rein Appeldoorn
- Soft_illusion
- Victor Lopez
- Vladimir Ermakov
- William Woodall
1 post - 1 participant
![[WWW] [WWW]](/moin_static197/rostheme/img/moin-www.png)
ROS Discourse General: UC3M Madrid 5G ROS Zenoh digital twin & teleop technical review & demo
Technical review and demo of Milan Groshev & Carlos Guimarães of UC3M Madrid of their work on 5G edge robotics digital twin, teleop, record & playback using ROS with Eclipse Zenoh (Rust WG overview) and other components. They also show the performance on 5G vs 4G.
TELCA, ADLINK, Ericsson, Telefonica, many others contributing and supporting their research. The work is partially funded by Horizon 2020 EU+Taiwan 5G-DIVE joint action grant #859881
1 post - 1 participant
![[WWW] [WWW]](/moin_static197/rostheme/img/moin-www.png)
ROS Discourse General: Announcing ros2_control for Foxy
Hello there folks,
We’ve had a busy 2020 at the ros2_control Working Group thinking about and discussing how to improve ros_control for ROS2.
I am pleased to announce the first release of ros2_control and ros2_controllers in Foxy!
Don’t be overly excited yet though! This is a release of only the core framework and some of the old and loved controllers, but not everything yet.
Highlighted features:
- Supported controllers:
joint_state_controller
,joint_trajectory_controller
andforward_command_controller
- Entirely component-based setup, for those of you familiar with ros_control, you can think of it as
CombinedRobotHardware
being a first class citizen. No need to write aRobotHW
anymore if someone else already made a driver for the component/robot you want to use. - ROS2 CLI support
- No more hardcoded joint or actuator interface types (i.e. can support any joint type, not only position, velocity and effort)
- Resource and lifecycle management done in a cleaner manner, leveraging some ROS2 and more modern C++ practices
- Composability with other ROS2 nodes via executors
- Support the
control_msgs/DynamicJointState
message which is a flexible alternative tosensor_msgs/JointState
Upcoming releases will include:
diff_drive_controller
JointGroup[Position/Velocity/Effort]Controller
- transmissions
- Gazebo support
- more demos and documentation.
Did you guys also watch Die Hard 2 over the Christmas break? If yes, I’m sure those orange industrial robots in the baggage-handling scene made you wonder: “When can I use ros_control
with ROS2 on my robots?” The time has come!
Full scene
As we do not yet have the Gazebo plugin working, allow me to show a KUKA and an ABB simulation thanks to Taiga Robotics. The source code for both can be found here.
ABB:
KUKA:
For getting started, try the hands-on demo from the demos repo:
For more, you may join us or follow our progress at the working group meetings or in the following repos:
- The framework: ros2_control
- The controllers: ros2_controllers
- Our ever-growing set of reference implementations following some typical robot urdfs can be found in ros2_control_demos
Warmest thanks to everyone who helped make ros2_control
happen but especially our main contributors:
Karsten Knese (Bosch), Denis Štogl (KIT), Victor Lopez & Jordan Palacios (PAL Robotics),
Edwin Fan & Alejandro Cordero (Open Robotics), Colin MacKenzie, Dmitri Ignakov (Taiga Robotics), Andy Zelenak and Lovro Ivanov (PickNik Robotics)
PS:
Until the next Foxy sync, the packages are only available from the ros2-testing
apt repository.
10 posts - 6 participants
![[WWW] [WWW]](/moin_static197/rostheme/img/moin-www.png)
ROS Discourse General: ROS on Windows: Melodic Release v20201221.0.0.2012310001
The Microsoft Azure Edge Robotics team is happy to announce the Melodic Release v20201221.0.0.2012310001 for Windows developers.
As usual, you can install it by the following steps:
mkdir c:\opt\chocolatey
set ChocolateyInstall=c:\opt\chocolatey
choco source add -n=ros-win -s="https://aka.ms/ros/public" --priority=1
choco upgrade ros-melodic-desktop_full -y --execution-timeout=0
Some highlights of this release:
- Based on the Melodic release sync 2020-12-21
- Enabled packages:
- Desktop_full
- MoveIt
- Navigation
- SLAM
- Cartographer
- OpenKarto
- OpenSLAM’s GMapping
- Libraries and Python runtime:
- Boost 1.66.0
- CMake 3.18.2
- EmPY 3.3.4
- Gazebo 9.13.1
- OGRE 1.10.11
- OpenCV 3.4.1
- PCL 1.8.1
- Poco 1.8.1
- Python 2.7.15
- Qt 5.10.1
Love your feedback and let us know on GitHub.
Also check out https://aka.ms/ros for ROS related components from Microsoft and partners which are supported on Linux and Windows. And more getting started tutorials on https://aka.ms/ros/docs.
Happy coding ROS Developers!
1 post - 1 participant
![[WWW] [WWW]](/moin_static197/rostheme/img/moin-www.png)
ROS Discourse General: ROS on Windows: Foxy Release v20201211.0.0.2012290002
The Microsoft Azure Edge Robotics team is happy to announce the Foxy Release v20201211.0.0.2012290002 for Windows developers.
As usual, you can install it by the following steps:
mkdir c:\opt\chocolatey
set ChocolateyInstall=c:\opt\chocolatey
choco source add -n=ros-win -s="https://aka.ms/ros/public" --priority=1
choco upgrade ros-foxy-desktop -y --execution-timeout=0
Some highlights of this release:
- Based on the Foxy release sync 2020-12-11.
- Enabled composition:
- Libraries and Python runtime:
- Boost 1.73.0
- CMake 3.18.2
- EmPY 3.3.4
- Gazebo 10.2.0
- OGRE 1.12.7
- OpenCV 4.3.0
- OpenSSL 1.1.1g
- PCL 1.9.1
- Poco 1.9.2
- Python 3.8.3 (embeddable distribution)
- Qt 5.15.0
Love your feedback and let us know on GitHub.
Also check out https://aka.ms/ros for ROS related components from Microsoft and partners which are supported on Linux and Windows. And more getting started tutorials on https://aka.ms/ros/docs.
Happy coding ROS Developers!
1 post - 1 participant
![[WWW] [WWW]](/moin_static197/rostheme/img/moin-www.png)
ROS Discourse General: FreeRobotics.tools is looking for a new Maintainer
Hey ROS,
I’m looking for a new maintainer of freerobotics.tools as I personally will not work in the Robotic area anymore. My focus will be on climate satellite engineering, OpenSustain.tech and LibreSelery.
By maintaining this list you will get very intensive insights about how the open-source robotics community is changing and which trends, projects, organizations and technologies are existing here. It is one of the central starting points for newcomers in the open-source robotics field and offers experts the possibility to analyze which projects are missing.
Of course, there would be a small introduction from me and I will support your work as far as I can in the future. Here is a rough description of the field of activity:
- Regular research of new projects.
- Evaluation of projects: Does documentation exist? Is the project still maintained? Is the project interesting for other users?
- Removal of inactive projects.
- Working on pull requests.
- Promotion of projects via Twitter. At the moment every new project is automatically promoted via the protontypes Twitter account by the awesome-twitter-action. We can also set up your Twitter account here. In this way people can just follow the Twitter account to get informed about listed new projects.
I would be very happy if we can keep the quality of the list in the future. If a person or organization can be found where the maintenance is secured over a long period of time, I am also willing to transfer the whole project to another namespace.
If you are interested, please contact me.
1 post - 1 participant
![[WWW] [WWW]](/moin_static197/rostheme/img/moin-www.png)
ROS Discourse General: ROS on Windows: Noetic Release v20201214.0.0.2012281717
The Microsoft Azure Edge Robotics team is happy to announce another Noetic Release v20201214.0.0.2012281717 for Windows developers.
As usual, you can install it by the following steps:
mkdir c:\opt\chocolatey
set ChocolateyInstall=c:\opt\chocolatey
choco source add -n=ros-win -s="https://aka.ms/ros/public" --priority=1
choco upgrade ros-noetic-desktop_full -y --execution-timeout=0
Some highlights of this release:
- Based on the Noetic release sync 2020-12-14
- Enabled packages:
- Desktop_full
- MoveIt
- Navigation
- ROSBridge_suite
- SLAM
- Cartographer
- OpenKarto
- Libraries and Python:
- Boost 1.73.0
- CMake 3.18.2
- EmPY 3.3.4
- Gazebo 10.2.0
- OGRE 1.12.7
- OpenCV 4.3.0
- OpenSSL 1.1.1g
- PCL 1.9.1
- Poco 1.9.2
- Python 3.8.3 (embeddable distribution)
- Qt 5.15.0
Love your feedback and let us know on GitHub.
Also check out https://aka.ms/ros for ROS related components from Microsoft and partners which are supported on Linux and Windows. And more getting started tutorials on https://aka.ms/ros/docs.
Happy coding ROS Developers!
1 post - 1 participant
![[WWW] [WWW]](/moin_static197/rostheme/img/moin-www.png)
ROS Discourse General: ROS 2 TSC Meeting Minutes: 2020-12-17
ROS 2 TSC Meeting Agenda 2020-12-17
Member contribution report (127.3 KB)
-
Attendees
- Steve Macenski - Samsung Research
- Aaron Blasdel - AWS RoboMaker (Amazon)
- Kyle Fazzari - Canonical
- Ralph Lange - Bosch
- Nick Fragale - Rover Robotics
- Jilada Eccleston - Tier IV
- Dave Coleman, Mark Moll, Henning Kayser - PickNik
- Brian Gerkey, Chris Lalancette, William Woodall, Geoff Biggs, Tully Foote, Kat Scott, Louise Poubel - Open Robotics
- Will Son - ROBOTIS
- Ian McMahon - Toyota Research Institute
- Lokesh Kumar Goel - LG Electronics
- Rob Woolley - Wind River (representing Andrei)
- Joe Speed - ADLINK
- Jaime Martin Losa - eProsima
- Jerry Towler - SwRI (representing GVSC)
-
Preliminaries
- [Gerkey] Fill in the contribution report in this doc!
-
Old business
-
New business
- [Gerkey][10 mins] Discuss new TSC applicants and call for vote
- Decision: Gerkey to open vote Dec 18, close Jan 8 to allow for holidays
- Opened late (Dec 22), so will also close late (Jan 12).
- Decision: Gerkey to open vote Dec 18, close Jan 8 to allow for holidays
- [Coleman, Kayser & Moll][15 mins] Update on MoveIt port to ROS 2
- Presentation Slides
- Extended discussion about the “chicken and egg” problem of ROS 2 / MoveIt 2 adoption: users wait for robots to be supported, but robot vendors wait for users to migrate.
- We have various experiences with encouraging adoption. We’re recommending that our customers move to ROS 2, but sometimes it’s a hard sell.
- Bigger companies are willing to make the jump earlier
- ROS 1 remains the biggest competitor to ROS 2.
- Can we do a better job of tracking what’s missing in ROS 2? (and what “business/migrations each missing item would unlock”) ROS 2 Product management / customer management?
- This will be useful, but it’s not uncommon for users to throw out issues that are “blocking” only to come up with more blockers after the initial block is removed.
- Selling based on new features (security, real-time, code quality, hybrid planning, etc.) is better than saying that they can do the same thing but with extra work.
- [Fragale][15 mins] Next-Gen Robotics Hardware Modularity
- [Pangercic][3min] Executor(s) in ROS 2
- Apex.AI started a survey document which we shared with the community experts: https://docs.google.com/document/d/1O53xOVlk4zwsfNukLaDbSWfT64wnoD9xh2EjWwX43qo/edit
- If anyone is interested in the topic of (improved) executors please consider chiming in
- [Lange][5 mins] briefly discuss about the PRs to add micro-ROS to REP-2005, i.e.
- https://github.com/ros-infrastructure/rep/pull/290
- https://github.com/ros-infrastructure/rep/pull/292
- https://github.com/ros-infrastructure/rep/pull/300
- Reminder: TSC members need to approve the PR:
- “The PR will be merged if and when the sum of TSC member vote values is >= 3 (votes of +0 and -0 are treated equally as 0 when computing the sum).”
- [Macenski][5 min] TSC Charter confidentiality proposal https://docs.google.com/document/d/1h0hXa7-7M7VlhQgAgG2VhuY34JsRz6IhuxBJqpo6BhY/edit?usp=sharing
- [Macenski][5 min] Self-reporting FTE analysis https://docs.google.com/spreadsheets/d/1IdGedh0dAvODBgs7vdKc1EeqqbidM2GLsBiq8t42R9A/edit?usp=sharing
- [Gerkey][10 mins] Discuss new TSC applicants and call for vote
-
Recurring business
- Next ROS 2 distro release
- [Lalancette][10 mins]
- Plan for setting CycloneDDS as the default RMW
- Open Robotics to post announcement of this decision on Discourse today
- C++17 - https://github.com/ros-infrastructure/rep/pull/291 - I haven’t heard any objections to this change, so we’ll probably go ahead with this
- macOS support - macOS support in ROS 2 Galactic and beyond - unless we get some kind of dedicated support for it, will probably drop it to Tier 3 in Galactic
- Follow-up about additional committers - crunched the numbers, found 3 obvious candidates for inviting to core committers. Will be sending out invitations tomorrow/early next week
- Plan for setting CycloneDDS as the default RMW
- [Pangercic][3min] Follow-up on signing up for the items in ROS 2 G
- There were no additional volunteers for the implementation of the features https://index.ros.org/doc/ros2/Roadmap/#id2
- Where is the problem? What could be improved to get these features in?
- [Lalancette][10 mins]
- Working groups [<5 mins each] [Not discussed live in the meeting]
-
[Knese] Control
-
[Speed] Edge AI
- recording and meeting minutes
- Amey Kulkarni at NVIDIA presented new ROS 2 packages for human pose estimation, classification, and object detection being provided as eloquent & foxy cyclonedds Jetson dockers.
- presentation slides
- - NVIDIA-AI-IOT/ros2_trt_pose : ROS 2 package for “trt_pose”: real-time human pose estimation on NVIDIA Jetson Platform
- - NVIDIA-AI-IOT/ros2_deepstream : ROS 2 package for NVIDIA DeepStream applications on Jetson Platforms
- - NVIDIA-AI-IOT/ros2_torch_trt : ROS 2 packages for PyTorch and TensorRT for real-time classification and object detection on Jetson Platforms
- - NVIDIA-AI-IOT/ros2_jetson_stats : ROS 2 package for monitoring and controlling NVIDIA Jetson Platform resources
- Nav2 WG needs help to get optimized Mask R-CNN on Nvidia Jetson or GPUs
- Nav2 WG needs help getting NVIDIA GPU optimized Mask-RCNN available in ROS 2. Nav2 WG has been working on a navigation pipeline for detection, tracking, and avoidance for some time and this is the last blocking thing to releasing and demos https://github.com/ros-planning/navigation2_dynamic/
- This is blocking meaningful use of GPUs in navigation.
- NVIDIA and Arm trying to figure out solution for Nav2 WG
-
[Martin Losa] Embedded
-
[Coleman] Manipulation
- Prepping for MoveIt 2 Rolling Ridley release
- ROS2_Control collaborations between MoveIt and PickNik
- Alpha UR driver for ROS 2 underway
- Developing 2021 roadmap for MoveIt 2, let us know what you’re working on!
- New Cartesian planning functionality nearly ready to be merged in
- Hybrid planning for MoveIt being built
-
[Macenski] Navigation
- New speed restricted zone capabilities merged! Docs update and discourse announcement to follow.
- Working on pure pursuit variant for integration into the stack before year’s end https://github.com/ros-planning/navigation2_tutorials/pull/17
- Various cleanup leading up to year end to start 2021 with a fresher slate.
- New first-time user startup guide to be merged before years end on TF/URDF
- GPS waypoint follower additions being reviewed and likely merged before week’s end https://github.com/ros-planning/navigation2/pulls/2111
-
[Pangercic] Real-time
- Working on the bench setup for performance testing
- Executor Design draft
-
[Biggs] Safety
- Planning two sessions on requirements elicitation and writing in January (1st and 3rd Wednesdays, in our usual meeting slot). Please join if this topic interests you.
- Have had some discussion about what we could add to REP 2004 regarding requirements.
- Safety watchdogs library and contracts library are seeing some use, judging from the issue tracker.
-
[Fazzari] Security
- Exploring a reference security implementation of a moderately complex, fairly independent real-world system.
- This will be useful as an example for others to follow, as well as a proving ground for NoDL and testing different security policies.
- Next step is to identify one or more prototypes. Demos scheduled in January for MoveIt and the Robotics Middleware Framework (community invites will be posted to discourse in January)
- Hosted a discussion on Privaros, A Framework for Privacy-Compliant Delivery Drones.
- Vulnerability remediation procedure PR approved. This is the workflow for handling vulnerabilities reported through REP 2006, ROS 2 Vulnerability Disclosure Policy.
- Future meeting minutes have moved to the ros-security community github site.
- Exploring a reference security implementation of a moderately complex, fairly independent real-world system.
-
[Blasdel] Tooling
- Rosbag2
- Evaluated new LevelDB storage implementation. Sony will contribute and release it from their own repository to avoid adding even more packages to rosbag2 repository - but it looks like a promising option for users. Performance looks good, with a smaller disk footprint than SQLite.
- New compression multithreading improves data retention in high bandwidth compression use cases
- We are considering starting a landing page like navigation.ros.org for Tooling maintained projects, most importantly Rosbag2. Question for Steve / TSC: how was access for the “navigation” subdomain granted?
- CI Actions
- Deprecation of a GitHub Action core function caused all builds using action-ros-ci to break. The fix process prompted a new release model:
- All CI actions have been bumped to minor version 0.1.0, which promises a stable API
- Have started releasing tag “v0.1” in addition to the patch-level tags e.g. “0.1.4” - Consumers can point at tag “v0.1” to receive all patch releases automatically without change to their code so that the roll-out of a fix like this can happen without intervention
- New known user: ros2_control
- Deprecation of a GitHub Action core function caused all builds using action-ros-ci to break. The fix process prompted a new release model:
- REP-2005 RCP requests
- Rosbag2
-
[Woodall] Middleware
- Agenda, minutes, and further notes:
- Had a presentation of zenoh-plugin-dds as a bridge across problematic networks.
- Progress continuing on the Events based Executor proposal from iRobot
- Review of proof of concept of network flow id’s with FastDDS, from Ericsson and eProsima
-
- Next ROS 2 distro release
1 post - 1 participant
![[WWW] [WWW]](/moin_static197/rostheme/img/moin-www.png)
ROS Discourse General: Detect Low Obstacles using Tilted 2D Lidar [experimental]
This method described in the article is experimental. It could satisfy my environment. Please do more tests if you want to use the idea on your product.
Best,
Marshal
1 post - 1 participant
![[WWW] [WWW]](/moin_static197/rostheme/img/moin-www.png)
ROS Discourse General: New packages for Kinetic Kame 2020-12-21
We’re happy to announce 6 new packages and 43 updated packages for Kinetic Kame.
Thank you to all the maintainers and contributors who have helped make these updates possible. A full listing is below.
Package Updates for kinetic
Added Packages [6]:
- ros-kinetic-color-util: 0.3.0-1
- ros-kinetic-nav-grid-server: 0.3.0-1
- ros-kinetic-robot-nav-rviz-plugins: 0.3.0-1
- ros-kinetic-robot-nav-tools: 0.3.0-1
- ros-kinetic-robot-nav-viz-demos: 0.3.0-1
- ros-kinetic-stag-ros: 0.1.1-6
Updated Packages [43]:
- ros-kinetic-cob-collision-monitor: 0.7.4-1 -> 0.7.5-1
- ros-kinetic-cob-grasp-generation: 0.7.4-1 -> 0.7.5-1
- ros-kinetic-cob-lookat-action: 0.7.4-1 -> 0.7.5-1
- ros-kinetic-cob-manipulation: 0.7.4-1 -> 0.7.5-1
- ros-kinetic-cob-moveit-bringup: 0.7.4-1 -> 0.7.5-1
- ros-kinetic-cob-moveit-interface: 0.7.4-1 -> 0.7.5-1
- ros-kinetic-cob-obstacle-distance-moveit: 0.7.4-1 -> 0.7.5-1
- ros-kinetic-costmap-queue: 0.2.5-0 -> 0.3.0-1
- ros-kinetic-dlux-global-planner: 0.2.5-0 -> 0.3.0-1
- ros-kinetic-dlux-plugins: 0.2.5-0 -> 0.3.0-1
- ros-kinetic-dwb-critics: 0.2.5-0 -> 0.3.0-1
- ros-kinetic-dwb-local-planner: 0.2.5-0 -> 0.3.0-1
- ros-kinetic-dwb-msgs: 0.2.5-0 -> 0.3.0-1
- ros-kinetic-dwb-plugins: 0.2.5-0 -> 0.3.0-1
- ros-kinetic-flexbe-behavior-engine: 1.3.0-1 -> 1.3.1-1
- ros-kinetic-flexbe-core: 1.3.0-1 -> 1.3.1-1
- ros-kinetic-flexbe-input: 1.3.0-1 -> 1.3.1-1
- ros-kinetic-flexbe-mirror: 1.3.0-1 -> 1.3.1-1
- ros-kinetic-flexbe-msgs: 1.3.0-1 -> 1.3.1-1
- ros-kinetic-flexbe-onboard: 1.3.0-1 -> 1.3.1-1
- ros-kinetic-flexbe-states: 1.3.0-1 -> 1.3.1-1
- ros-kinetic-flexbe-testing: 1.3.0-1 -> 1.3.1-1
- ros-kinetic-flexbe-widget: 1.3.0-1 -> 1.3.1-1
- ros-kinetic-global-planner-tests: 0.2.5-0 -> 0.3.0-1
- ros-kinetic-locomotor: 0.2.5-0 -> 0.3.0-1
- ros-kinetic-locomotor-msgs: 0.2.5-0 -> 0.3.0-1
- ros-kinetic-locomove-base: 0.2.5-0 -> 0.3.0-1
- ros-kinetic-mavlink: 2020.11.11-1 -> 2020.12.12-1
- ros-kinetic-nav-2d-msgs: 0.2.5-0 -> 0.3.0-1
- ros-kinetic-nav-2d-utils: 0.2.5-0 -> 0.3.0-1
- ros-kinetic-nav-core-adapter: 0.2.5-0 -> 0.3.0-1
- ros-kinetic-nav-core2: 0.2.5-0 -> 0.3.0-1
- ros-kinetic-nav-grid: 0.2.5-0 -> 0.3.0-1
- ros-kinetic-nav-grid-iterators: 0.2.5-0 -> 0.3.0-1
- ros-kinetic-nav-grid-pub-sub: 0.2.5-0 -> 0.3.0-1
- ros-kinetic-robot-navigation: 0.2.5-0 -> 0.3.0-1
- ros-kinetic-rosapi: 0.11.12-1 -> 0.11.13-1
- ros-kinetic-rosbridge-library: 0.11.12-1 -> 0.11.13-1
- ros-kinetic-rosbridge-msgs: 0.11.12-1 -> 0.11.13-1
- ros-kinetic-rosbridge-server: 0.11.12-1 -> 0.11.13-1
- ros-kinetic-rosbridge-suite: 0.11.12-1 -> 0.11.13-1
- ros-kinetic-rtabmap: 0.20.0-1 -> 0.20.7-2
- ros-kinetic-rtabmap-ros: 0.20.0-1 -> 0.20.7-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:
- Brennan Cain
- David V. Lu!!
- Felix Messmer
- Hans-Joachim Krauch
- Mathieu Labbe
- Philipp Schillinger
- Russell Toris
- Vladimir Ermakov
1 post - 1 participant
![[WWW] [WWW]](/moin_static197/rostheme/img/moin-www.png)
ROS Discourse General: New packages for Melodic 2020-12-21
We’re happy to announce the next update of ROS Melodic. There are 29 new packages as well as 108 updated packages. Full details are below.
Package Updates for melodic
Added Packages [29]:
- ros-melodic-cmd-vel-smoother: 0.1.15-1
- ros-melodic-color-util: 0.3.0-1
- ros-melodic-contact-states-observer: 0.1.15-1
- ros-melodic-eus-nlopt: 0.1.15-1
- ros-melodic-eus-qp: 0.1.15-1
- ros-melodic-eus-qpoases: 0.1.15-1
- ros-melodic-gazebo-video-monitor-msgs: 0.6.0-2
- ros-melodic-gazebo-video-monitors: 0.6.0-2
- ros-melodic-heifu-diagnostic: 0.7.2-1
- ros-melodic-heifu-mavros: 0.7.2-1
- ros-melodic-heifu-msgs: 0.7.2-1
- ros-melodic-heifu-safety: 0.7.2-1
- ros-melodic-heifu-simple-waypoint: 0.7.2-1
- ros-melodic-heifu-tools: 0.7.2-1
- ros-melodic-joy-mouse: 0.1.15-1
- ros-melodic-jsk-calibration: 0.1.15-1
- ros-melodic-jsk-ik-server: 0.1.15-1
- ros-melodic-jsk-teleop-joy: 0.1.15-1
- ros-melodic-mesh-client: 1.0.0-1
- ros-melodic-nav-grid-server: 0.3.0-1
- ros-melodic-robot-nav-rviz-plugins: 0.3.0-1
- ros-melodic-robot-nav-tools: 0.3.0-1
- ros-melodic-robot-nav-viz-demos: 0.3.0-1
- ros-melodic-stag-ros: 0.2.1-1
- ros-melodic-tvm-vendor: 0.7.2-1
- ros-melodic-vesc: 1.1.0-1
- ros-melodic-vesc-ackermann: 1.1.0-1
- ros-melodic-vesc-driver: 1.1.0-1
- ros-melodic-vesc-msgs: 1.1.0-1
Updated Packages [108]:
- ros-melodic-ackermann-steering-controller: 0.17.0-1 -> 0.17.1-1
- ros-melodic-chomp-motion-planner: 1.0.6-1 -> 1.0.7-1
- ros-melodic-cob-collision-monitor: 0.7.4-1 -> 0.7.5-1
- ros-melodic-cob-grasp-generation: 0.7.4-1 -> 0.7.5-1
- ros-melodic-cob-lookat-action: 0.7.4-1 -> 0.7.5-1
- ros-melodic-cob-manipulation: 0.7.4-1 -> 0.7.5-1
- ros-melodic-cob-moveit-bringup: 0.7.4-1 -> 0.7.5-1
- ros-melodic-cob-moveit-interface: 0.7.4-1 -> 0.7.5-1
- ros-melodic-cob-obstacle-distance-moveit: 0.7.4-1 -> 0.7.5-1
- ros-melodic-combined-robot-hw: 0.18.2-1 -> 0.18.3-1
- ros-melodic-combined-robot-hw-tests: 0.18.2-1 -> 0.18.3-1
- ros-melodic-controller-interface: 0.18.2-1 -> 0.18.3-1
- ros-melodic-controller-manager: 0.18.2-1 -> 0.18.3-1
- ros-melodic-controller-manager-msgs: 0.18.2-1 -> 0.18.3-1
- ros-melodic-controller-manager-tests: 0.18.2-1 -> 0.18.3-1
- ros-melodic-costmap-queue: 0.2.5-1 -> 0.3.0-1
- ros-melodic-diff-drive-controller: 0.17.0-1 -> 0.17.1-1
- ros-melodic-dlux-global-planner: 0.2.5-1 -> 0.3.0-1
- ros-melodic-dlux-plugins: 0.2.5-1 -> 0.3.0-1
- ros-melodic-dwb-critics: 0.2.5-1 -> 0.3.0-1
- ros-melodic-dwb-local-planner: 0.2.5-1 -> 0.3.0-1
- ros-melodic-dwb-msgs: 0.2.5-1 -> 0.3.0-1
- ros-melodic-dwb-plugins: 0.2.5-1 -> 0.3.0-1
- ros-melodic-effort-controllers: 0.17.0-1 -> 0.17.1-1
- ros-melodic-flexbe-behavior-engine: 1.3.0-1 -> 1.3.1-1
- ros-melodic-flexbe-core: 1.3.0-1 -> 1.3.1-1
- ros-melodic-flexbe-input: 1.3.0-1 -> 1.3.1-1
- ros-melodic-flexbe-mirror: 1.3.0-1 -> 1.3.1-1
- ros-melodic-flexbe-msgs: 1.3.0-1 -> 1.3.1-1
- ros-melodic-flexbe-onboard: 1.3.0-1 -> 1.3.1-1
- ros-melodic-flexbe-states: 1.3.0-1 -> 1.3.1-1
- ros-melodic-flexbe-testing: 1.3.0-1 -> 1.3.1-1
- ros-melodic-flexbe-widget: 1.3.0-1 -> 1.3.1-1
- ros-melodic-force-torque-sensor-controller: 0.17.0-1 -> 0.17.1-1
- ros-melodic-forward-command-controller: 0.17.0-1 -> 0.17.1-1
- ros-melodic-four-wheel-steering-controller: 0.17.0-1 -> 0.17.1-1
- ros-melodic-gazebo-video-monitor-plugins: 0.5.0-2 -> 0.6.0-2
- ros-melodic-global-planner-tests: 0.2.5-1 -> 0.3.0-1
- ros-melodic-gripper-action-controller: 0.17.0-1 -> 0.17.1-1
- ros-melodic-hardware-interface: 0.18.2-1 -> 0.18.3-1
- ros-melodic-imu-sensor-controller: 0.17.0-1 -> 0.17.1-1
- ros-melodic-iris-lama: 1.0.0-1 -> 1.1.0-2
- ros-melodic-iris-lama-ros: 1.0.0-1 -> 1.1.0-1
- ros-melodic-joint-limits-interface: 0.18.2-1 -> 0.18.3-1
- ros-melodic-joint-state-controller: 0.17.0-1 -> 0.17.1-1
- ros-melodic-joint-trajectory-controller: 0.17.0-1 -> 0.17.1-1
- ros-melodic-leo-gazebo: 0.1.2-1 -> 0.1.3-1
- ros-melodic-leo-simulator: 0.1.2-1 -> 0.1.3-1
- ros-melodic-locomotor: 0.2.5-1 -> 0.3.0-1
- ros-melodic-locomotor-msgs: 0.2.5-1 -> 0.3.0-1
- ros-melodic-locomove-base: 0.2.5-1 -> 0.3.0-1
- ros-melodic-lvr2: 20.11.1-1 -> 20.11.2-1
- ros-melodic-mavlink: 2020.11.11-1 -> 2020.12.12-1
- ros-melodic-moveit: 1.0.6-1 -> 1.0.7-1
- ros-melodic-moveit-chomp-optimizer-adapter: 1.0.6-1 -> 1.0.7-1
- ros-melodic-moveit-commander: 1.0.6-1 -> 1.0.7-1
- ros-melodic-moveit-controller-manager-example: 1.0.6-1 -> 1.0.7-1
- ros-melodic-moveit-core: 1.0.6-1 -> 1.0.7-1
- ros-melodic-moveit-fake-controller-manager: 1.0.6-1 -> 1.0.7-1
- ros-melodic-moveit-kinematics: 1.0.6-1 -> 1.0.7-1
- ros-melodic-moveit-planners: 1.0.6-1 -> 1.0.7-1
- ros-melodic-moveit-planners-chomp: 1.0.6-1 -> 1.0.7-1
- ros-melodic-moveit-planners-ompl: 1.0.6-1 -> 1.0.7-1
- ros-melodic-moveit-plugins: 1.0.6-1 -> 1.0.7-1
- ros-melodic-moveit-ros: 1.0.6-1 -> 1.0.7-1
- ros-melodic-moveit-ros-benchmarks: 1.0.6-1 -> 1.0.7-1
- ros-melodic-moveit-ros-control-interface: 1.0.6-1 -> 1.0.7-1
- ros-melodic-moveit-ros-manipulation: 1.0.6-1 -> 1.0.7-1
- ros-melodic-moveit-ros-move-group: 1.0.6-1 -> 1.0.7-1
- ros-melodic-moveit-ros-occupancy-map-monitor: 1.0.6-1 -> 1.0.7-1
- ros-melodic-moveit-ros-perception: 1.0.6-1 -> 1.0.7-1
- ros-melodic-moveit-ros-planning: 1.0.6-1 -> 1.0.7-1
- ros-melodic-moveit-ros-planning-interface: 1.0.6-1 -> 1.0.7-1
- ros-melodic-moveit-ros-robot-interaction: 1.0.6-1 -> 1.0.7-1
- ros-melodic-moveit-ros-visualization: 1.0.6-1 -> 1.0.7-1
- ros-melodic-moveit-ros-warehouse: 1.0.6-1 -> 1.0.7-1
- ros-melodic-moveit-runtime: 1.0.6-1 -> 1.0.7-1
- ros-melodic-moveit-servo: 1.0.6-1 -> 1.0.7-1
- ros-melodic-moveit-setup-assistant: 1.0.6-1 -> 1.0.7-1
- ros-melodic-moveit-simple-controller-manager: 1.0.6-1 -> 1.0.7-1
- ros-melodic-nav-2d-msgs: 0.2.5-1 -> 0.3.0-1
- ros-melodic-nav-2d-utils: 0.2.5-1 -> 0.3.0-1
- ros-melodic-nav-core-adapter: 0.2.5-1 -> 0.3.0-1
- ros-melodic-nav-core2: 0.2.5-1 -> 0.3.0-1
- ros-melodic-nav-grid: 0.2.5-1 -> 0.3.0-1
- ros-melodic-nav-grid-iterators: 0.2.5-1 -> 0.3.0-1
- ros-melodic-nav-grid-pub-sub: 0.2.5-1 -> 0.3.0-1
- ros-melodic-plotjuggler: 3.0.3-1 -> 3.0.5-2
- ros-melodic-position-controllers: 0.17.0-1 -> 0.17.1-1
- ros-melodic-psen-scan-v2: 0.1.2-1 -> 0.1.3-1
- ros-melodic-robot-localization: 2.6.7-1 -> 2.6.9-1
- ros-melodic-robot-navigation: 0.2.5-1 -> 0.3.0-1
- ros-melodic-ros-control: 0.18.2-1 -> 0.18.3-1
- ros-melodic-ros-controllers: 0.17.0-1 -> 0.17.1-1
- ros-melodic-rosapi: 0.11.12-1 -> 0.11.13-1
- ros-melodic-rosbridge-library: 0.11.12-1 -> 0.11.13-1
- ros-melodic-rosbridge-msgs: 0.11.12-1 -> 0.11.13-1
- ros-melodic-rosbridge-server: 0.11.12-1 -> 0.11.13-1
- ros-melodic-rosbridge-suite: 0.11.12-1 -> 0.11.13-1
- ros-melodic-rqt-controller-manager: 0.18.2-1 -> 0.18.3-1
- ros-melodic-rqt-joint-trajectory-controller: 0.17.0-1 -> 0.17.1-1
- ros-melodic-rtabmap: 0.20.0-2 -> 0.20.7-1
- ros-melodic-rtabmap-ros: 0.20.0-1 -> 0.20.7-1
- ros-melodic-sr-hand-detector: 0.0.2-1 -> 0.0.3-2
- ros-melodic-transmission-interface: 0.18.2-1 -> 0.18.3-1
- ros-melodic-urdfdom-py: 0.4.4-1 -> 0.4.5-1
- ros-melodic-velocity-controllers: 0.17.0-1 -> 0.17.1-1
- ros-melodic-video-stream-opencv: 1.1.5-0 -> 1.1.6-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:
- Alexander Gutenkunst
- Bence Magyar
- Blake Anderson
- Brennan Cain
- Błażej Sowa
- Chittaranjan Srinivas Swaminathan
- Chris Lalancette
- Dave Coleman
- David V. Lu!!
- Davide Faconti
- Eurico Pedrosa
- Felix Messmer
- Filipe Almeida
- Fábio Azevedo
- Hans-Joachim Krauch
- Isaac I. Y. Saito
- Johannes Betz
- Jon Binney
- Josh Whitley
- João Pedro Carvalho
- Masaru Morita
- Mathias Lüdtke
- Mathieu Labbe
- Michael Ferguson
- Michael Görner
- Nick Lamprianidis
- Noda Shintaro
- Philipp Schillinger
- Raghavender Sahdev
- Russell Toris
- Ryohei Ueda
- Sachin Chitta
- Sammy Pfeiffer
- Sebastian Pütz
- Shadow Robot’s Software Team
- Shunichi Nozawa
- Tom Moore
- Vincent Rousseau
- Vladimir Ermakov
- Yuki Furuta
- furuta
- nozawa
1 post - 1 participant
![[WWW] [WWW]](/moin_static197/rostheme/img/moin-www.png)
ROS Discourse General: [Poll] A possible new SBC for TurtleBot3?
Hi community,
I’m getting a good amount of inquiries about a new SBC that can replace the current RPi3B+ on TurtleBot3
and I’d like to see the actual ROS users’ preference.
Please understand that high performance modules will not be considered as possible options to keep TurtleBot3 within the affordable price.
Some users also requested to upgrade the sensor, but this may not be feasible at this time so let’s rule out the sensor part in this discussion.
SBC seems pretty dependent on the industries where the robot is deployed, so if you can also specify which the industry you are in, it’d be greatly appreciated and helpful to understand the result.
Please note that you can select multiple items for the SBC and items are listed in alphabetical order.
- Jetson Nano
- Raspberry Pi 4
- UP Squared
0 voters
In which industry do you use TurtleBot3?
- Commercial
- Educational
- Entertainment
- Industrial
- Logistics
- Research & Development
- Service
0 voters
Happy holidays and happy new year!
4 posts - 4 participants
![[WWW] [WWW]](/moin_static197/rostheme/img/moin-www.png)
ROS Discourse General: ROS News for the Week of 12/14/2020
Christmas is Cancelled from FZI
CoBot Christmas
I was gifted this by an aspiring engineer this week. If you have similar awesome technical drawnings please drop them in the comments.
Seasons Greetings
- ROS 2 Advent Calendar in Japanese
- Note, there will be no update next week due to the holiday.
- Holiday: Man’s Best Robotic Friend
- Christmas Cancelled
Events
ROS Related
- ROS 2 Default Middleware for Galactic Selected
- 2020 ROS 2 Middleware Report – includes code and data
- Proposal for Common Messages in ROS 2
- macOS moved to Tier 3 for ROS 2 Galactic
- Last Update for ROS 2 Eloquent Elusor
- Input Needed: ROS OpenVINO Toolkit Roadmap
- ARViz – Augmented Reality RVIZ
- MOCAP 4 ROS 2
- ROS Noetic Update
- Italian ROS Group
- Slow Your Roll: Nav2 Speed Restriction Support
- Cargo Delivery ODD Kick-Off Meeting
- Multiwheel Differential Drive Plugin
- TurtleBot3 and Webots
- ROSout Log Monitoring Tool
- @fmrico pluginlib / github actions tools
News
- PickNik wins Good Robot Award
- James Bruton keeps building his ROS robot
- Plus One Robotics Podcast
- Cloud Simulation for CI/CD in Robotics
- QuadSAT ROS for Testing Satellite Equipment
- Google X on Robots and Puppets
- NanoSaur Robot
- ROS Industrial: Open Source is also establishing itself in industrial robotics
- ROS Industrial Video Competition
ROS Questions
- SystemD does not work with ROS 2
- Utility to Convert Point Cloud to Height Map
- Adding external c library to a ROS2 node
1 post - 1 participant
![[WWW] [WWW]](/moin_static197/rostheme/img/moin-www.png)
ROS Industrial: ROS-Industrial Asia Pacific Workshop 2020
The Annual ROS-Industrial Asia Pacific Workshop took place on the 29th October 2020, this year in a one day digital webinar format. The workshop was opened by our Guest-of-Honor, Prof. Quek Tong Boon, Chief Executive of the Singapore National Robotics Programme. After the opening, Erik Unemyr, Consortium Manager for ROS-Industrial Asia Pacific, shared updates on the topic of “Industry Ready ROS 2 – Easy to Adopt Modules with Quality”, which comprised of the current technology focus the team has been developing in-house, including:
- easy_perception_deployment – a ROS2 Package that aims to accelerate the training and deployment of Computer Vision models for industry use (which is now in Beta release, and you can find it here)
- easy_manipulation_deployment – a ROS2 Package that has a user-friendly Graphical User Interface (GUI) to create a robotic workcell, and supports a variety of commonly used industrial end-effectors using a flexible grasp implementation approach. This will package will be released soon, to be made available on the ROS-Industrial GitHub.
Next, we had the opportunity to invite Roger Barga, General Manager at AWS Robotics, to present on “The Role of the Cloud in Future of Robotics”. During his presentation, he addressed the importance and necessity of applications in cloud computing such as using it for development of robotic applications in simulation, testing and deployment. AWS also currently supports ROS, ROS2 & Gazebo within their services.
Matt Robinson, Programme Manager for our ROS-Industrial counterpart in Americas at the Southwest Research Institute (SwRI), presented on “Enabling Production Performance in ROS-Based Systems” where he brought up the value of ROS2 for various industrial use cases and also showcased some of the developments happening at SwRI.
Sharing more details about the activities at the Advanced Remanufacturing and Technology Centre, Bai Fengjun, Technical Lead from the Advanced Robotics Applications team at ARTC, presented development on the Next Generation Hyper-Personalization Line and how ROS has played a part in the development of such applications for the Fast Moving Consumer Goods sector.
Michael Sayre, CEO & Co-Founder of Cognicept Systems, one of our Consortium Members in the Asia Pacific Region, then presented on the importance of error handling and remote management for robotic fleets, and their latest development of the ROS2 Listener agent that was developed together with the ROS-Industrial Team at ARTC. You can find the repository here.
Shortly after, Albertus Hendrawan Adiawahono, Head of the Mobility Group at the ASTAR Institute for Infocomm Research (I2R) presented on their current efforts with the local healthcare ecosystem to develop modules that would aid robots to be more resilient in the hospital ward setting, where the environment rapidly changes. They currently have completed Proof of Concepts in which the robots are able to adapt to lifts, curtains and even simulating a blue code emergency drill.
After the lunch break, we invited Jack Sheng Kee, Lab Director of the Delta Research Centre, a ROS-Industrial Consortium Member, to share on “Reconfigurable and Flexible Automation in Manufacturing” where he presented some of the existing solutions Delta has developed, and how they are all ROS supported.
We also had the team from Open Robotics, Marco Gutierrez and Grey, to present on roadmap updates with new features and future plans for Ignition Gazebo, ROS2 and also the Robotics Middleware Framework (RMF). The development of RMF has become a key effort in driving the integration and deployment of wide-scale smart robotics systems, which includes the communication between robots, building infrastructure and other edge devices.
Christoph Hellmann Santos, Consortium Manager for ROS-Industrial Europe at Fraunhofer IPA presented on the latest updates and success stories of both the ROSIN and ROS-Industrial Projects, such as the toolbox for automated delivery for the DHL Streetscooter and the real-time mapping project with Bosch Rexroth.
Prof Trygve Thomessen, Managing Director of PPM Robotics AS also presented ROSIN updates with the ROSWELD project, an application and success story of ROS being deployed in heavy industrial applications such as robotic welding. Last but not least, we had Andrei Kholodnyi, Principal Technologist at Wind River to present on “A Mixed-Critical ROS2 Implementation on VxWorks RTOS, WRLinux & Hypervisor” where he highlighted the use and importance of safety compliant and real-time solutions for ROS2 Applications.
A summarized table of all the speakers, including presentation slides and recording, is now available here!














To conclude this year’s ROS-Industrial Workshop Asia Pacific, Dr. Zhang Jing Bing, Technical Division Director for Smart Robotics and Automation (SRA) at ARTC gave his closing remarks.
The ROS-Industrial Consortium Asia Pacific @ ARTC continue with a multi-prong approach in bridging the gaps between the industry and the community in adoption of ROS and robotics, by working closely with our industry partners and to develop modules that can cater for industrial needs, providing training opportunities for aspiring roboticists as well as companies that are embarking on leveraging ROS to scale their robotics adoption.
On behalf of the ROS-Industrial Team at ARTC, we hope that you enjoyed the webinar as much as we did, and we look forward to meeting each other in 2021 for future ROS-Industrial activities!
![[WWW] [WWW]](/moin_static197/rostheme/img/moin-www.png)
ROS Discourse General: ROS 2 Galactic Default Middleware Announced
Hi All,
You may recall that one of our main motivations in designing ROS 2 with a middleware abstraction is to provide end users with a flexible transport layer supported by a rich ecosystem of vendors. This competitive approach has already yielded dividends such as the FastDDS discovery service, IceOryx zero copy memory passing, and multiple innovations in MicroROS for embedded hardware. While some have called this “The DDS Wars” I prefer to think of it as the “DDS Cambrian Explosion”, as we see more and more vendors of DDS and other middlewares become interested in ROS 2, and how their implementations can bring new features to bear on different parts of the robotics ecosystem.
ROS 2 has long supported multiple middlewares, and will continue to do so. But of course there has to be a default configuration that just works for most users. As discussed in previous posts, starting with Galactic Geochelone the default RMW configuration for each ROS 2 distro will be selected by the ROS 2 Technical Steering Committee (TSC) after a thorough vetting process. It is worth noting that when we say default, we really do mean default, and users can continue to choose non-default RMW configurations. The TSC aims to choose the best default for each distro, but that doesn’t mean that it will be the best choice for every application. Importantly, changing the RMW configuration on your robot is simply a matter of running a handful of commands.
I am happy to announce that after careful consideration the ROS 2 TSC has selected CycloneDDS to be the default RMW for ROS 2 Galactic Geochelone. This vote is the result of a thoughtful review and discussion of the available options by the ROS 2 TSC, including a comprehensive technical evaluation of the Tier 1 RMWs by the team at Open Robotics. That report, including source code and data, is available to all. The report includes performance statistics about each RMW implementation, simulated and real world testing of each RMW, a review of the code quality and responsiveness of each RMW vendor, and a community survey. On balance, the similarities among the Tier 1 RMWs are greater than their differences, and this was a hard decision for the TSC. We hope you make use of the report in selecting your RMW implementation, and feel free to send us your feedback. We intend this report and its future iterations, as well as the tools developed in generating it, to be a neutral source of RMW information for the ROS community.
We’ll start implementing the TSC’s decision soon. We expect the change of the default RMW to CycloneDDS to be merged by late January 2021, and available for testing in Rolling soon after. We realize that this change will impact many users, but we also believe the impacts will be minimal. One important difference is that, whereas Foxy’s default behavior via FastDDS is asynchronous publishing (similar to ROS 1), Galactic’s default behavior via CycloneDDS will be synchronous publishing. This will change the behavior of calls to publish on a Publisher when more data is being sent than the network can handle, and perhaps in other cases; we’ll include more details in the near future (you can also read the report). If you encounter issues related to this or other changes when you update to Galactic, please report them! And remember that, as is the case now with Foxy, you can change your RMW configuration with just a handful of commands. If you would like to help with this process or would like to beta test the latest ROS 2 release (particularly on a larger multi-robot scenario) please contact me or the core dev team.
2 posts - 2 participants
![[WWW] [WWW]](/moin_static197/rostheme/img/moin-www.png)