You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi. Recently I needed to run Astrobee in ROS2 and wanted to be able to do the following:
See the images from dock/nav cam.
Use the undock behavior.
Send the Astrobee simple one-point goals.
Run a multi-robot simulation, with Bumble and Honey.
To do this, the management/executive is needed. I took as reference Katie's PR: #777 and added the following modifications:
Converted sys_monitor.
Fix the way in which ConfigClient is given a node argument (otherwise it crashes due to its using SyncParametersClient).
Fix a few bugs in the time utilities (seconds were being converted to nanoseconds).
Fix a few bugs in the launch files (specifically, use_sim_time was not being set in the right parameter field).
Upgrade Gazebo to be version 11.14. Current version in the rolling image is 11.11 (which makes sense, as this is the latest version that was available last April, when the rolling image for astrobee was last built). This version is needed for the nav_cam/dock_cam sensors (wideanglecamera) to be parsed.
Added a few edits to the launch files to support the namespacing of launch files (using PushRosNamespace)
Add the robot_namespace parameter for the gazebo spawn node.
Hi. Recently I needed to run Astrobee in ROS2 and wanted to be able to do the following:
To do this, the management/executive is needed. I took as reference Katie's PR: #777 and added the following modifications:
My changes are in this branch: https://github.com/traclabs/astrobee/tree/ros2_executive . With these changes I am currently able to undock the robot and move it around, either in the default setup or with Bumble/Honey (video attached).
I'd be happy to send a PR if it is helpful, thanks!
Multi-robot testing:
multiple_astrobees_ros2_5x_hb.mp4
Default robot testing
astrobee_ros2_migration_5x_hb.mp4
The text was updated successfully, but these errors were encountered: