← All tools

Message & Error Explainer

What an ArduPilot message means and what to do about it

Українська

The firmware cannot tell which board it is running on

Stops itStart-up and what the board reports

What ArduPilot says:

Firmware for the Pixhawk family serves several boards and works out which one it is on from the sensors it finds; BRD_TYPE can name the board instead (0 is automatic). “Unable to detect board type”: the sensors found match no known board. “Unknown board type”: BRD_TYPE holds a number this firmware does not know. “Board Validation … Failed”: the board's self-test did not find the part named. Each is shown as a “Config Error:” every 5 seconds and start-up goes no further.

What to do, most likely first

  1. BRD_TYPE came from a parameter file made for another board.

    FixSet BRD_TYPE to 0 and reboot.

  2. The firmware is for another board of the same family.

    CheckCompare the board name in the start-up lines with the one printed on the board.

    FixLoad the firmware built for your exact board.

  3. A sensor on the board has failed, or the board is a copy with other parts.

    CheckThe same error stays with the correct firmware and BRD_TYPE 0.

    FixAsk the seller for a replacement. A board that fails its own check is not one to fly.

Parameters to look at

ParameterWhat it is
BRD_TYPEBoard type
BRD_OPTIONSBoard options
The code that sends it

Config Error: Pixhawk2 requires FMUv3 firmware

libraries/AP_BoardConfig/board_drivers.cpp AP_BoardConfig::validate_board_type() · Open in ArduPilot Copter-4.7.1

Config Error: Unable to detect board type

libraries/AP_BoardConfig/board_drivers.cpp AP_BoardConfig::board_autodetect() · Open in ArduPilot Copter-4.7.1

Config Error: Board Validation … Failed

libraries/AP_BoardConfig/board_drivers.cpp AP_BoardConfig::board_autodetect() · Open in ArduPilot Copter-4.7.1

Config Error: Unknown board type

libraries/AP_BoardConfig/board_drivers.cpp AP_BoardConfig::board_setup_drivers() · Open in ArduPilot Copter-4.6.3

And 1 more messages, sent from the same places.

Written here for Copter 4.6. In the tool you choose your vehicle and version, see your own parameter values beside the ones named here, and drop a flight log to have every message in it explained.

Open it in the Message & Error Explainer