Start-up has stopped on a configuration error

What ArduPilot says:

• Config Error: fix problem then reboot

ArduPilot found a setting or a missing part it cannot start with, and stopped on purpose in the middle of start-up. It now repeats two lines every 5 seconds: this one, and one that begins “Config Error:” and names the problem. Nothing else works, but the ground station stays connected and parameters can still be read and changed: that is the way out.

What to do, most likely first

1. A parameter asks for something this board or firmware cannot do.

   CheckWait 5 seconds with the messages tab open: the two lines alternate.

   FixFind the other “Config Error: …” line, look up its explanation, change the parameter it points to, and reboot: nothing takes effect until the reboot.

2. A sensor the firmware needs is not found: the firmware is for another board, or the part is dead.

   CheckThe error names a barometer or IMU driver. The Firmware Inspector tells which board a firmware file is for.

   FixLoad the firmware for your exact board. If the same error stays with the right firmware, the board is faulty.

3. You cannot tell which parameter did it.

   FixSave the parameters to a file, reset them all to defaults from the ground station, reboot, and load your settings back a group at a time.

Where to do it:Parameter Compare & MigrateFirmware Inspector