Port mav_planning_rviz plugins to ROS 2 Humble #23
Conversation
Do you need me to test on mide side to see if the display issues are MacOS specific? |
No, the display issues are now resolved. It’s a case of chasing down the service calls from each button to make sure they are running correctly with the correct inputs. The most recent updates are in this branch: https://github.com/srmainwaring/terrain-navigation/tree/wips/wip-ap-dds-launch |
srmainwaring
force-pushed
the
wips/wip-ros2-mav-rviz
branch
4 times, most recently
from
83bd047
to
3f218e8
Compare
- Port goal_marker, edit_button, pose_widget. Signed-off-by: Rhys Mainwaring <[email protected]> - Port planning_interactive_markers. Signed-off-by: Rhys Mainwaring <[email protected]> - Partial port of planning_panel. Signed-off-by: Rhys Mainwaring <[email protected]> - Update service calls. Signed-off-by: Rhys Mainwaring <[email protected]> - Remove lib prefix from mav_planning_rviz plugin Signed-off-by: Rhys Mainwaring <[email protected]> - Use recommended ament install destinations Signed-off-by: Rhys Mainwaring <[email protected]> - Add python launch file for terrain_navigation_ros Signed-off-by: Rhys Mainwaring <[email protected]>
srmainwaring
force-pushed
the
wips/wip-ros2-mav-rviz
branch
from
3f218e8
to
178521a
Compare
Follow-up to #20. This updates the mav_planning_rviz plugins for ROS 2.
This version builds and runs, however there are currently issues with the interactive markers to resolve and a test environment running on a ROS 2 supported version of PX4 or ArduPilot is required (either using mavros for ROS 2 or preferably with DDS integration).
Dependencies
Tasks