Hello
I have in my blueboat an onboard computer.
I can view the onboard computer via screen to screen mirroring via WiFi to the bank side.
On this onboard computer I installed Qgroundcontrol (and Mission Planner). Now I want to connect the navigator autopilot to the onboard computer via a USB cable (as is possible with a Pixhawk autopilot).
But with the USB ports on the Raspberry I cannot connect to Qgroundcontroll/Mission Planner on the onboard computer.
If I connect the ethernet port of the Raspberry (with a ethernet to USB converter) to the onboard computer, I can access the blueOS, but cannot connect to Qgroundcontroll/Mission Planner
Can I use one of the serial ports on the Navigator with a JST GH to USB cable?

Or is there another way to connect the navigator to the onboard computer via USB
And where do I change the following parameters in too?
- serialX_protocol,
- serialX_baud,
- serialX_baud
Marcel
Hi @Marcel1 -
I’m a bit confused as to why you’d install an onboard computer in your BlueBoat, and use QGroundControl on it to control the vehicle? The amount of data to screen-mirror this computer is considerably more than the telemetry connection via the standard WiFi radios, so your range may be significantly worse and the overall quality of operations severely impacted…
If you’d like the onboard computer to connect, you’ll need to configure it to have a static IP address on the same subnet - like 192.168.2.65, with subnet mask 255.255.255.0. With this onboard computer connected to the Raspberry Pi via ethernet, you’ll be able to load BlueOS in its web browser. Enter pirate mode, and navigate to Mavlink Endpoints, and create a client endpoint targeted at that computer’s .2.65 IP address - this should fill in automatically if accessing via a browser running on that computer.
Again, this is not the recommended approach to controlling your blue boat! It is much easier to connect your computer to the WiFi network created by the BaseStation, or via USB-C cable, and set your IP to 192.168.2.1 - this will automatically connect you the vehicle as this is a default route in the Mavlink Endpoints configuration. I’d love to understand why you’re not taking this approach!