Cannot detect Navio2

Blue Robotics Software
1

Hello!

I’m having a little trouble with my current setup. I have a Navio2 flight controller board hooked up to the GPIO pins of my Raspberry Pi 3B+, and though I’d updated the firmware using Emlid’s Raspbian image (link to that is here: Raspberry Pi configuration | Navio2), I can’t seem to get BlueOS to detect the board.

image
image1123×910 72.5 KB

I can get it working just fine on the Raspbian image, with a steady yellow blinking light on the Navio2, and I can hear my thrusters start up, but when I try to set the board in the latest version of BlueOS, I’m only presented with SITL as the board option, the indicator light on the Navio2 stays lit green, and I fail to hear my thrusters activate.

I’ve tried running ardupilot_fw_uploader.py --identify, but I fail to get any sort of response back from the board.

Is there, perhaps, a step I’m missing? I’ve been running back and forth trying to get this working, to no avail.

2

Hi @Tisch_CANBUS -
Welcome to the forums!
BlueOS expects to reach external autopilots via a USB comm port - not the GPIO pins. When using the Navigator, the autopilot is actually running on the Pi, and using the GPIO pins to communicate with supporting hardware.
In your case, since a USB connection is not available, you may need to modify BlueOS to look for autopilots on the built in serial ports? There is an open issue on this…feel free to comment what pins your Navio2 needs to be identified at!

3

Hello! @tony-white

Ahh, that makes sense. I’ll take a look at that, thank you!

4

as this is a linux board, you need to check the sensors it expects here:

You also need to add support for detecting the Navio2 board in flight_controller_detected AND make sure the kernel overlays are properly loaded for accessing the SPI and i2c peripherals.

2 Likes