Pixhawk often starts in bootloader mode, so re-flash is the only option

AntennaTracker V1.2.0-dev (6843d0e6)

As title say, in that condition you are forced to re-upload the firmware (QGroundControl).

However I’ve found that with BRD_BOOT_DELAY=2000 the problem disappear.

Curious to know why and glad to help developers and other users


@peterbarker @iampete might be able to comment. Which build target and specific hardware?

that’s quite odd, I think James is correct you need to check you have ended up with the correct build for your controller. You could always try flashing to copter and back to wipe everything and have a clean start.

QGroundControl see the board as “PX4 FMU V2” and I’ve installed

AntennaTracker V1.2.0-dev (6843d0e6)

from https://firmware.ardupilot.org/AntennaTracker/2020-02/2020-02-13-10:02/fmuv2/

By the way I’m happy that works now, It was very frustrating
My Antenna Tracker is working good


What board do you have exactly? I would recommend using the Pixhawk1 build over the FMU V2.

Pixhawk 2.4.8


Try this version


With the Pixhawk version the problem is even much worse. Never had this issue with airplane and copters

Problem persist also with this newest version https://firmware.ardupilot.org/AntennaTracker/2020-02/2020-02-17-22:02/Pixhawk1/

The problem is also present even when from Mission Planner you do a PREFLIGHT_REBOOT_SHUTDOWN action

Is this a tracker issue or does it happen on the same board on plane or copter? Maybe there is a hardware issue.

Reading on the web, at least I’m not the only one facing this issue. However I’am here in order to make some testing whith my platform if required. I’have 3D printed a beautiful 360 continuous rotation platform with tilt