The autopilot is not recognize by QGroundcontrol

Blue Robotics Software QGroundControl
1

Hi everyone,

I am currently working with a BlueBoat platform running BlueOS on a Raspberry Pi 4b and I am experiencing an issue connecting to the autopilot.

The wireless connection between the Base Station and the boat appears to be working correctly. I can access the BlueOS web interface without any problem, and the system reports that BlueOS is connected.

However, BlueOS continuously displays the following errors:

  • autopilot_vehicle_type_fetch_fail

  • autopilot_firm_info_fetch_fail

As a result, QGroundControl is unable to connect to the vehicle and remains in the “Disconnected” state.

From my understanding, this suggests that BlueOS is running correctly on the Raspberry Pi but is unable to communicate with the autopilot Navigator;

Has anyone encountered a similar issue before? Are there any recommended checks or logs I should investigate to determine where the problem comes from ?

One additional detail: I am currently performing these tests inside a hangar, could maybe the lack of GPS signal somehow cause these errors or prevent QGroundControl from connecting to the vehicle, or are these issues unrelated?

Any suggestions would be greatly appreciated.

Thank you!

2

Hi @Ellio -

Welcome to the forums!

Can you navigate to the autopilot firmware page in BlueOS and confirm what firmware is running? It sounds like it may not be setup? Please share what version of BlueOS you’re running as well as what ardurover firmware version.

Otherwise, have you configured your computers static IP to be 192.168.2.1? This is not required for Cockpit, but is necessary for QGC (with the default mavlink endpoint targeting this address…)

3

Hi @tony-white

Thanks for your help. It was indeed the static IP configuration causing the issue.

My computer was not configured with the correct static IP address (192.168.2.1). After setting it properly, QGroundControl immediately connected to the vehicle and the autopilot information became available.

Everything now appears to be working as expected.

Thanks again for pointing me in the right direction!