💡
aColor-BlueRov2
  • aColor-BlueRov2 ROS implementation
  • Topside computer
    • Required configuration
    • File system and ROS architecture
    • Launch ROS implementation
    • ROS-MAVlink bridge
    • Controllers
      • Depth control
      • Heading control
      • Velocity control
      • Gamepad
    • Commander
    • Graphical User Interface (GUI)
      • GUI modification
    • Additional IMUs : client
  • Companion computer
    • Required configuration
    • Additional IMUs : server
  • ArduSub
    • ArduSub parameters
  • MAVlink message
    • Pymavlink
  • Configure new frame
    • Custom Ardusub 3.5
  • Bibliography
    • Bibliography
Powered by GitBook
On this page
  • Launch the link ROS-MAVlink
  • Launch IMU client
  • Launch controllers and GUI

Was this helpful?

  1. Topside computer

Launch ROS implementation

Once the tether and the USB cable is connected to the topside computer with the right IP address you will need to execute the files that do the bridge between MAVlink messages from PixHawk and ROS messages on the surface computer.

Launch the link ROS-MAVlink

roslaunch bluerov_ros_playground bluerov2_node.launch

The ROS-MAVlink bridge use the 'udpin:192.168.2.1:14560' endpoint of mavlink stream. 192.168.2.1 is the IP address of the topside computer, and 14560 the port used. For mavlink stream, topside computer works as server while the companion computer runing mavproxy works as a client.

QGroundControl (GQC) use the 192.168.2.1:14550 endpoint. So you can run QGC and ROS bridge at the same time

Launch IMU client

To connect topside computer to a server running on companion computer

rosrun bluerov_ros_playground Imu_bridge.py

Launch controllers and GUI

roslaunch bluerov_ros_playground control.launch   
PreviousFile system and ROS architectureNextROS-MAVlink bridge

Last updated 5 years ago

Was this helpful?