← All tools

Message & Error Explainer

What an ArduPilot message means and what to do about it

Українська

No working barometer at start-up

Stops itBarometer and airspeed

What ArduPilot says:

ArduPilot stops at start-up with a configuration error and will not arm. “unable to initialise driver”: no barometer answered at all. “unable to calibrate”: one was found, but gave no healthy reading within 0.5 s while its ground pressure was being measured. “all sensors uncalibrated”: none of the barometers produced a single good reading during the calibration. Parameters can still be read and changed.

What to do, most likely first

  1. The firmware was built for another board, or another revision with a different barometer chip.

    CheckCompare the board name in the firmware with the board itself and its revision.

    FixFlash the firmware for exactly this board.

  2. The board has no barometer of its own and expects an external one that is not connected or not being looked for.

    CheckThe board's documentation says “no barometer”; BARO_PROBE_EXT has no bit for the sensor you fitted.

    FixWire the external barometer to an I2C port, set its bit in BARO_PROBE_EXT (and BARO_EXT_BUS if needed) and reboot.

  3. The barometer chip is dead: water, a crash, or a solder joint.

    CheckThe right firmware is on the board and the error stays at every boot.

    FixReplace the flight controller, or add an external barometer as above.

Parameters to look at

ParameterWhat it is
BARO_PROBE_EXTExternal barometers to probe
BARO_EXT_BUSExternal baro bus
The code that sends it

Config Error: Baro: all sensors uncalibrated

libraries/AP_Baro/AP_Baro.cpp AP_Baro::calibrate() · Open in ArduPilot Copter-4.7.1

Config Error: Baro: unable to calibrate

libraries/AP_Baro/AP_Baro.cpp AP_Baro::calibrate() · Open in ArduPilot Copter-4.7.1

Config Error: Baro: unable to initialise driver

libraries/AP_Baro/AP_Baro.cpp AP_Baro::init() · Open in ArduPilot Copter-4.7.1

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