LOG_BACKEND_TYPE asks for logging this board cannot do
What ArduPilot says:
- Config Error: Too many logger backends
- Config Error: Too many backends
- Config Error: Unknown logger backend
LOG_BACKEND_TYPE is a sum of the places to log to: 1 File (microSD card), 2 MAVLink (a stream to the ground), 4 Block (an on-board flash chip). At most two can be used at once; three stop the start-up with “Config Error: Too many backends”, repeated until it is fixed. A place this firmware was not built with (4 on a board with no flash chip, 1 on a board with no card slot) is ignored without a word: there is then no log at all, and no arming check either.
What to do, most likely first
The value was copied from another board with different log storage.
CheckDoes this board have a card slot, a log flash chip, or both? The Firmware Inspector shows what the firmware file was built with.
FixSet
LOG_BACKEND_TYPEto 1 for a card slot or 4 for a flash chip, and reboot.All three places are selected (the value is 7).
FixChoose one or two: 1 or 4 for normal use, and add 2 only if a program on the ground records the log stream.
Parameters to look at
| Parameter | What it is |
|---|---|
LOG_BACKEND_TYPE | AP_Logger Backend Storage type |
Where to do it:Setup & Tuning GuideFirmware Inspector
The code that sends it
Config Error: Too many logger backends
libraries/AP_Logger/AP_Logger.cpp AP_Logger::init() · Open in ArduPilot Copter-4.7.1
Config Error: Too many backends
libraries/AP_Logger/AP_Logger.cpp AP_Logger::init() · Open in ArduPilot Copter-4.6.3
Config Error: Unknown logger backend
libraries/AP_Logger/AP_Logger.cpp AP_Logger::init() · Open in ArduPilot Copter-4.7.1