Our BlueBoat is currently configured with the default GCS Client Link (IP 192.168.2.1, Port 14550) and GCS Server Link MAVLink Endpoints (IP 0.0.0.0, Port 14550), which we use to connect a base station computer at the IP 192.168.2.1 to the boat to mission plan using QGroundControl.
Recently, we had another USV system crash and it is currently offline. One of our interns wrote a MissionPlanner plugin to provide a depth visualization using single beam sonar depth measurements from the USV, but has not yet been able to test it. We are now attempting to replicate that functionality on the BlueBoat so they can validate their MissionPlanner plugin. For this, we would like to maintain the default GCS Client functionality to do mission planning on our original computer using QGroundControl, while a second computer running MissionPlanner watches the Mavlink traffic to update the plugin.
To try and accomplish this, we created new UDP Server and UDP Client MAVLink Endpoints, with the Client pointing to the static IP of the second computer (192.168.2.7), and both Client and Server pointing to the port 14990. After launching MissionPlanner on the second computer, we receive the pop-up message “A Mavlink stream has been detected, blueos(192.168.2.2). Would you like to connect to it?” However, after attempting to connect, the connection times out after 30 seconds with the error message “No Heartbeat Packets Received.” Is there further configuration needed for MAVLink to send messages over the new UDP connection we’ve created? Furthermore, is there a better way to accomplish what we’re trying to do (1 “Read/Write” connection and 1 “Read Only” connection)?