Hello everyone!!
I am really glad some of the community members have been using the ROS2 extension ^-^
Based on some of the questions I’ve been getting, I added some extra feature to the extension
MAVROS: Includes a launch file to communicate with the flight controller (vehicle)
Foxglove : Web-based RViz for visualizing ROS2 data
mavros_control: Includes a python script to control the vehicle using GPS-based waypoints (BlueBoat) and RC-control (BlueROV2) via mavros
The extension also mounts the following folder on the computer running BlueOS to the home directory folder in the extension’s Docker container, which can be used to store files that need to persist across reboots, such as a ROS2 workspace with custom code:
Hi! I have been using your original blueos-ros2 extension that launches MAVROS through Docker. I am having issues with sending RC commands. I can ARM/DISARM the vehicle through MAVROS, and can echo the MAVROS topics. However, I can’t seem to get the /mavros/rc/OverrideRCIn topic to do anything.
This is based on a MAVLink UDP Client endpoint I made on Port 14770 (through the blueos webpage) to another Pi which I am intending on using as the control station computer.
I have read that I may need to change the sys id on QGC to 1? Is there anything else I need to consider? Should I also include a gcs_url in my launch command?
Thank you! I have enjoyed working with your extension so far.
Yup, you need to change the sys id to 1. But also the fcu url is different on BlueOS, the extension launches mavros with the correct fcu_url, you shouldn’t have to change it
As I try and clone your repository using your commands provided online, I get an error when trying the fetch the mavros_control submodule path. Following it through GitHub too I find that it is not accessible. I am not sure if the issue is on my end?
