Hallo!
I’m having trouble getting BlueOS to detect my Pixhawk board (used in a BlueROV2 old version possible R2 or R1).
I’m completely unable to flash firmware — neither from cloud nor file.
What I’ve Tried:
192.168.2.2Hi @Dion,
If you’re not already, please try using BlueOS 1.4 (the latest stable version), and turning on Pirate Mode in case it’s failed a previous firmware update and is currently only showing up in bootloader mode.
I’m unfamiliar with this kind of setup - has it worked for you previously in your ROV? How/where is the Pixhawk plugged in to the onboard computer (Raspberry Pi) running BlueOS?
Hello! I managed to connect the pixhawk directly to pc and flash the firmware using QGC. The pixhawk is connected to raspberry pi by usb, sorry for the confusion with sbus/rcin pins.
The problem now is trying to calibrate the accelerometer in the QGC app. Every time i boot the computer (inside the BlueRov) the autopilot specifies Vehicle type: sub which is good, i believe. However as i try to calibrate accelerometer (Roll90) from QGC i cant progress an further (see image below: Next button is unclickable and no yellow border like the images).
After being stalled in trying to calibrate the accelerometer, the vehicle type specified in autopilot has changed from Sub to Unknown. Restarting the autopilot leads to the board not being detected so i need to reboot the Bluerov computer once again and the cycle repeats.
PS: I am new to this so i dont have any previous experience in operating or setting up the BlueRov2 R1.
Hi @Dion -
What version of BlueOS are you using? As Eliot mentioned, the newest 1.4 stable supports pixhawks on older systems better than ever before. It seems like BlueOS has not successfully communicated with your Pixhawk, yet…
Trying another USB port, cable, and making sure you’re on 1.4 are the best troubleshooting steps.
I am indeed using v1.4.
Every time i power off and on the Autopilot Firmware section in blueos UI displays this:
How can you know that the pixhawk does not communicate with the computer? Then how does the computer know both the vehicle type and firmware after hard booting?
When suggesting to use another USB port, is that the USB connecting the pixhawk with the rov computer? Is there a way to capture any error messages that i assume exist (otherwise it would all just work)? Could there be a hardware fault with the pixhawk board and/or Sd card mounted on it?
In QGC app it says config error: unable to detect board type when i connect pixhawk directly to my laptop
Hi @Dion -
If the Pixhawk isn’t recognized when you plug it into your computer with QGC, it or the USB cable you’re using could be faulty…
However, since BlueOS seems to recognize it in your screenshot, it may be ok?
If you can download and share here the system logs from the gear icon in the lower left of BlueOS, we can review them to see what may be going wrong…
