data might not have been written correctly

Voltage and/or amperage meter sources have been changed but not saved

Prearm switch is not activated or prearm has not been toggled after disarm

Configuration changes have been detected

required number of satellites has not been fixed

The accelerometer has not been calibrated and features are enabled that rely on it

Your flight controller does not have a compatible dataflash chip available

Your flight controller does not have an integrated BetaFlight OSD

Mass storage mode can not be activated because the storage device is not ready

written message

written order

Will additionally print addresses that are being read/written to and the sent/received payload

Check that the Roll, Pitch and other bar graphs move correctly

Configure the Receiver settings correctly

udev rules are installed correctly

verify all motors are spinning correctly

Values above X might damage motor and/or ESC

Read the release notes to understand what changed and what you might need to adjust

Setting volume of the beacon too high might damage the motors

Setting volume of the startup beeps too high might damage the motors

flashing might fail, especially on highly integrated AIOs

updating might fail

When you enabled 3D mode in your flight controller, make sure the ESCs are also set up for 3D mode, otherwise the motors might go off with full power

been there, done that

in the period in which the communications channel has been open

Beeps when gyro has been calibrated

Configuration has been applied

Paralyze mode has been activated

Runway Takeoff Prevention has been triggered

Total time craft has been armed on current power cycle

Total time the craft has been armed in the current power cycle

Total time the craft has been powered on

Your radio has been detected to be on!