All explanations
540 explanations of what ArduPilot Copter and Plane say and log, by topic. Each tells what the message means and what to do, the most likely cause first.
Start-up and what the board reports
The flight controller was restarted by its watchdogForcing safety off for watchdogThe firmware cannot tell which board it is running onConfig Error: Pixhawk2 requires FMUv3 firmwareStart-up has stopped on a configuration errorConfig Error: fix problem then rebootThe IO co-processor could not be given its firmwareConfig Error: Failed to update IO firmwareThe board's name and the processor's unique IDThe revision of the operating system under ArduPilotThe firmware's name, version and source revisionThe motor layout this copter is set up forFrame: …/…The ground station announcing itselfStart-up is running, then finishedArduPilot ReadyThe plane starts without an airspeed sensorNo airspeed sensorFactory calibration values were restored from the bootloader areaLoaded N persistent parameters (N errors)Which signal each output sendsA request to enter the loader or replace the bootloaderEntering DFU modeHow fast an IMU is readIMUN:…… sampling N.NkHz/N.NkHzThe board's second processor was foundIOMCU: 0x… 0x… 0x…The ground station connected before the motors were set upmotors not allocatedStart-up: the gyros are being calibrated, keep the plane stillGround start with delay
Arming, disarming and the safety switch
Another aircraft is too close, by ADS-BPreArm: ADSB threat detectedA controller gain is zero or negativePreArm: Bad parameter: …
ANGLE_MAX is outside 10° to 80°PreArm: Check ANGLE_MAXThe pilot's maximum climb rate is zero or negativePreArm: Check PILOT_SPD_UPThe disarm switch is in its “disarm” positionPreArm: Disarm Switch onThe ground station link is lost right nowPreArm: GCS failsafe onThe safety switch has not been pressedPreArm: Hardware safety switchThe IMU heater has not reached its temperature yetPreArm: heater temp low (N.N < N)The copter thinks it is tilted too far to armPreArm: LeaningThe current flight mode does not allow armingPreArm: … mode not armableThe motor interlock switch is in the wayPreArm: Interlock/E-Stop ConflictThe motor emergency stop is activePreArm: Motors Emergency StoppedArduPilot has not finished startingPreArm: System not initialisedRemote ID is not readyARM_STATUS not availableThe minimum airspeed is set below 5 m/sPreArm: AIRSPEED_MIN too low (N < N)A roll or pitch limit is too small to fly withPreArm: PTCH_LIM_MAX_DEG too small (N.N)On a QuadPlane, AUTO needs a mission that begins with a take-offTakeoff waypoint requiredThe long failsafe is set to come before the short onePreArm: FS_LONG_TIMEOUT < FS_SHORT_TIMEOUTThe mission is still in its landing partPreArm: In landing sequenceThe plane will not arm in this flight modenot Q modeArming or disarming with the rudder stick was refusedRudder disarm: disabledThe throttle input is reversed and the failsafe value is on the wrong sidePreArm: Invalid THR_FS_VALUE for rev throttleMid-stick cruise throttle is on, but the throttle trim is not in the middlePreArm: Throttle trim not near center stick(N)It armed with the arming checks switched offWarning: Arming Checks DisabledThe motors are armedThe motors are disarmed, and how to see whyThe lost-copter alarm was switched on with the sticksLocate Copter alarmThe plane was armed or disarmedThrottle armedRadio control
The throttle failsafe value does not fit the throttle rangePreArm: Check FS_THR_VALUEThe VTOL forward-throttle control is not at its minimumPreArm: VTOL Fwd Throttle is not zeroA radio calibration is in progressPreArm: RC calibratingIt is in radio failsafe right nowPreArm: Radio failsafe onMore than one serial port is set to RC inputPreArm: Multiple SERIAL ports configured for RC inputThe receiver has not been seen since power-onPreArm: RC not foundA stick's calibrated range is too smallPreArm: … radio min too highA stick is off-centre at the moment of armingPreArm: … (RCN) is not neutralTwo switches, or a switch and the mode channel, are set to the same jobPreArm: Mode channel and RCN_OPTION conflictThe throttle channel reads below the failsafe valuePreArm: … below failsafeThe throttle stick is too high to armPreArm: … too highA channel's trim lies outside its minimum and maximumPreArm: RCN_MAX is less than RCN_TRIMThe plane is waiting for its receiverPreArm: Waiting for RCThe receiver's port is a poor choice, or two telemetry set-ups collide…: passthrough telemetry conflict on SERIALNA switch is set to a function this firmware does not haveInvalid channel option (N)A second serial port is set to RC input and is ignoredSERIALN_PROTOCOL: duplicate RCIN not permittedThe radio link reports its speed…: RX device ping failedThe receiver's protocol was recognisedRCInput: decoding … (…)A switch on the transmitter changed positionRCN: … …
Compass
The compass in use has stopped sending dataPreArm: Compass not healthyThe calibration failed: the compass does not face the way its settings sayMag(N) bad orientation: N/N N.NThe calibration failed: the field strength is far from what is expected hereMag(N) bad radius N.N expected N.NThe compass calibration would not startCompass cal requires GPS lockReboot after the compass calibrationPreArm: Compass calibrated requires rebootA compass calibration is in progressPreArm: Compass calibration runningThe magnetic field the compass measures is too strong or too weakPreArm: Check mag field: N.N, max N, min NThe measured field does not match the Earth's field at this placePreArm: Check mag field (z diff:N.N>N)The quick (fixed-heading) compass calibration failedMag: WMM table errorA compass that is in use has no calibrationCompass not calibratedA compass on the priority list did not show up at start-upCompass N not foundThe first compass needs too large a correctionPreArm: Compass offsets too highThe compass order was changed: reboot before going onCompass cal requires reboot after priority changeThe compasses disagree with each otherPreArm: Compasses inconsistentCompassmot ended without a resultFailedThe motor interference test (compassmot) would not startRC not calibratedThe compass was calibrated without knowing where it isMagCal: No location, fix_radius skippedThe log shows the compass dropping out (ERR COMPASS)ERR COMPASS (Subsys 3)A missing compass was dropped from the list, or replaced by a new oneMag: Compass #N with DEVID N removedThe calibration confirmed, or corrected, the compass orientationMag(N) good orientation: N N.NIn-flight compass learning has started, or finishedCompassLearn: FinishedCompassmot is running, or has finishedCalibration successful
GPS
GPS blending is asked for, but this firmware does not have itPreArm: GPS_AUTO_SWITCH==2 but no blendingThe GPS position and ArduPilot's own position estimate are apartPreArm: GPS and AHRS differ by N.NmThe GPS has no 3D fix yetPreArm: GPS N: Bad fixThe two GPS receivers cannot be blendedGPS blending unhealthyThe DroneCAN node numbers chosen for the GPS receivers do not fitSelected GPS Node N not set as instance NThe position estimator does not trust the GPS right nowPreArm: GPS glitchingThe satellites in view give too imprecise a positionPreArm: High GPS HDOPThe pair of GPS receivers is not giving a headingIncorrect Role set for DroneCAN GPS, N should be BaseA configured GPS has never answeredGPS N: was not foundThe GPS is not sending positions fast and regularly enoughPreArm: GPS N: not healthyThe two GPS receivers report different placesPreArm: GPS positions differ by N.NmArduPilot's main GPS slot is emptyPreArm: GPS N: primary but TYPE 0A GPS has not finished being set up by ArduPilotPreArm: GPS N still configuring this GPSThe u-blox GPS has not accepted one of ArduPilot's settingsGPS N: u-blox … configuration 0x0x…The u-blox GPS refused to switch a satellite signal on or offGPS N: unable to configure band 0x0x…ArduPilot is checking, and may erase, what is stored in the u-blox GPSGPS N: Requesting all config (…) pos=NA GPS receiver was foundGPS N: probing for … at N baudThe u-blox GPS says what it isGPS N: Legacy config unsupportedArduPilot is configuring a newer u-blox GPSGPS N: updating GNSS modeThe u-blox GPS is told to remember its settingsGPS N: u-blox saving config
Position and attitude estimate (EKF, AHRS)
The EKF threw the compass heading away and took one worked out from GPSEKF2 IMUN emergency yaw resetThe EKF's sensors disagree: the position estimate is no longer trustedEKF varianceThe chosen estimator is not the one in usenot using configured AHRS typeThe position and attitude estimate is not ready to flyPreArm: AHRS: …Home has not been set yetPreArm: AHRS: waiting for homeThe attitude estimate is not ready at the moment of armingPreArm: AHRS not healthyNo height estimate yet for a mode that holds heightPreArm: Need Alt EstimateThe external AHRS has no GPS fix or has not finished aligningSensAItion AligningThe external AHRS is switched on but not set upExternalAHRS: Invalid backendThe external AHRS is not sending good dataVectorNav received VNERR code: …The EKF has no usable attitude yetPreArm: EKF attitude is badTwo attitude estimates disagree… … inconsistent N deg. Wait or rebootOne copy of the EKF reports itself unhealthyEKF3 core N unhealthyA plane's EKF will not start without a GPS fixEKF3 init failure: No GPS lock
EK3_MAG_CAL still holds a value that older versions used for external yawEK3_MAG_CAL and EK3_SRC1_YAW inconsistentThere was not enough memory to start the EKFEKF2 IMUNGSF: allocation failedA sensor disagrees with the EKF too much to armPreArm: EKF velocity varianceAn EKF source parameter holds a value that is not allowedCheck EK3_SRCN_POSZThe EKF has not finished startingEKF2 not startedGPS speed and the EKF's speed differ by more than 2 m/s on the groundEKF3[N] vel error N.NThe EKF cannot start until the GPS has been identifiedEKF3 waiting for GPS config dataArduPilot does not yet know where the copter isPreArm: Fence enabled, need position estimateThe EKF gave up on one compass and moved to the nextEKF2 IMUN switching to compass NA copy of the EKF was restarted on the groundEKF2 IMUN forced resetThe compass was disturbed on the ground; the heading was corrected during the climbEKF2 IMUN MAGN ground mag anomaly, yaw re-alignedThe aircraft changed to another copy of the EKFNavEKF2: lane switch NA request to set the EKF origin was refused: it already has oneEKF2 refusing set originThe EKF no longer has a position: it holds attitude and height onlyEKF3 IMUN stopped aidingGPS heading was lost in flight; the EKF fell back on the compassEKF3 IMUN yaw fallback activeThe EKF switched to another core (ERR EKF_PRIMARY)ERR EKF_PRIMARY (Subsys 24)The transmitter's telemetry warns that a sensor disagrees with the EKFError terrain alt varianceWhich estimator is supplying attitude and position nowAHRS: … activeThe EKF set its heading again once clear of the groundEKF3 IMUN MAGN in-flight yaw alignment completeA copy of the EKF has startedEKF3 IMUN initialisedThe EKF has fixed the point it measures positions fromEKF3 IMUN origin setThe EKF started using a position source other than GPSEKF2 IMUN is using range beaconsThe EKF knows which way is downEKF2 IMUN tilt alignment completeThe EKF has started using the GPS: position modes are availableEKF3 IMUN is using GPSThe EKF set its heading without the compassEKF2 IMUN yaw aligned using GPSThe EKF has taken its first heading from the compassEKF3 IMUN MAGN initial yaw alignment completeIMU: accelerometers, gyros, vibration
Vibration is spoiling the height estimate; the copter changed how it holds heightVibration compensation ONThe accelerometers have no valid calibrationPreArm: 3D Accel calibration neededThe accelerometer calibration is saved; reboot before flyingPreArm: Accels calibrated requires rebootThe accelerometers of two IMUs disagreePreArm: Accels inconsistentRaw IMU logging was switched on but is not running yetFailed to allocate N bytes for IMU batch samplingThe in-flight noise analyser (FFT) is not readyFFT: resolution is N.NHz, increase lengthA gyro is read too slowly for the main loop rateGyro N rate NHz < loop ratex1.8 NHzThe gyros of two IMUs disagreePreArm: Gyros inconsistentThe gyros could not find their zero at power-onPreArm: Gyros not calibratedThe level calibration was refusedtrim over maximum of 10 degreesNo IMU was found at start-upINS: unable to initialise driverAn IMU is not delivering dataPreArm: Accels not healthyAn IMU temperature calibration is being learnedPreArm: temperature cal runningThe notch filter settings ask for more filters than the board allowsConfig Error: Too many notches: N > NThe FFT tune switch tried to set the notch filter from a hoverFFT: Notch frequency N.NHz and ref N.N selectedA gyro filter or the noise analyser could not get its memoryFailed to allocate window for AP_GyroFFTOne motor's vibration is getting through the gyro filtersNoise %.fdB on motor N at %.fHzHow an IMU is being read (LSM6DSV16X, external AHRS)IMUN: LSM6DSV16X … sampling N.NkHzThe level calibration succeededTrim OK: roll=N.N pitch=N.N yaw=N.NThe level trim was saved, or an AutoTrim endedTrim saved
Barometer and airspeed
Airspeed and GPS speed disagree: the airspeed sensor is suspectAirspeed sensor N failure. DisablingThe airspeed sensor is not readyPreArm: Airspeed N not healthyThe EKF's height and the barometer's height differ by more than 1 mPreArm: Altitude disparityNo working barometer at start-upConfig Error: Baro: all sensors uncalibratedThe barometer's altitude and the GPS altitude are impossibly far apartGPS alt error N.Nm (see BARO_ALTERR_MAX)A barometer is not giving usable readingsPreArm: Baro: …The airspeed sensor does not answerAirspeed N init failedThe airspeed zero moved a lot since last time: wind was probably in the tubeArspd N offset change large;cover and recalThe barometer stopped giving usable readings (ERR BARO)ERR BARO (Subsys 18)The airspeed sensor's zero was measuredAirspeed N calibrated, offset = N.NThe barometer was zeroed at start-upBaro: no sensors found, skipping calibrationThe height of the take-off field above sea level was set, or could not beField Elevation Set: N.NmThe barometer's ground level was set againBarometer calibration complete
Battery and power
The battery failsafe has triggeredBattery N is … N.NV used N.N mAhA battery failsafe from the last flight is still setPreArm: Battery failsafeThe flight controller's own 5 V supply is too low or too highPreArm: Board (N.Nv) out of range N.N-N.NvThe servo rail voltage is below the limit you setPreArm: Servo voltage to low (N.Nv < N.Nv)A battery monitor refuses armingBattery N …The battery is already at a failsafe levelThe battery is below the level set as the minimum to armThe critical battery threshold is not below the low oneNo analog input is left for the battery monitorConfig Error: No analog voltage channel for battery NA battery monitor is switched on but gives no readingA smart battery says it is switching offVehicle N battery N is powering offNotices from a DroneCAN battery or solar chargerBattery N: Node change from N to N for Id N
Failsafes and emergencies in flight
Crash detected: the motors were stoppedCrash: Disarming: AngErr=N.N>N.N, Accel=N.N<N.NDead reckoning: flying on an estimated position, without GPSERR FAILSAFE_DEADRECKON (Subsys 31)The dead-reckoning script: flying home without GPSDR: could not get home or vehicle locationAvoiding a manned aircraft (ERR
FAILSAFE_ADSB)ERR FAILSAFE_ADSB (Subsys 20)Loss of control: the parachute was released (ERR CRASH_CHECK-2)ERR CRASH_CHECK-2 (Subsys 12, ECode 2)The EKF stopped agreeing with its sensors (ERR EKFCHECK)ERR EKFCHECK (Subsys 16)EKF failsafe: the position estimate is no longer trustedEKF FailsafeA fence was crossed (ERR FAILSAFE_FENCE)ERR FAILSAFE_FENCE (Subsys 9)No frame from the receiver in time (ERR RADIO-2)ERR RADIO (Subsys 2)Thrust loss: full throttle and still descending (ERR THRUST_LOSS_CHECK-1)ERR THRUST_LOSS_CHECK (Subsys 25)Vibration failsafe: height is being held in a cruder way (ERR FAILSAFE_VIBE)ERR FAILSAFE_VIBE (Subsys 29)Battery failsafe: land nowERR FAILSAFE_BATT (Subsys 6)A failsafe triggered, but the copter carries on with what it was doingThe ground station went silent: the copter is acting on its ownERR FAILSAFE_GCS-1 (Subsys 8, ECode 1)Radio link lost: the copter is acting on its ownERR FAILSAFE_RADIO-1 (Subsys 5, ECode 1)SmartRTL could not start: falling back to RTL or LandSmartRTL Unavailable, Trying RTL ModeTerrain failsafe: the height above ground is no longer knownFailsafe: Terrain …The failsafe's first choice was refused: falling back to RTL or LandTrying Land ModeThe aircraft crossed a fenceThe EKF no longer trusts the GPS (or the heading is wrong)GPS Glitch or Compass errorAnother aircraft is close: the plane is avoiding itAvoid: Performing action: NThe Advanced Failsafe is ending the flight on purposeTerminating due to fence breachPlane decided it has crashed or landed hardHard landing detectedLong failsafe: the radio or the ground station stayed lost… Failsafe On: switched to …The parachute was releasedParachute: Released againShort failsafe: the first seconds after the radio is lostRC Short Failsafe: switched to …The radio link was lost (“on”) or has come back (“off”)Throttle failsafe …RTL lost the ground height and started again at a height above homeRestarting RTL - Terrain data missingRTL could not work out its pathRTL: unexpected error setting climb targetA flight termination was asked for and not done, or called offUnable to terminate, termination is not configuredThe ground station asked for the parachute and Plane refusedParachute already releasedFS_GCS_ENABLE is set to 2, a value that no longer existsPreArm: FS_GCS_ENABLE=2 removed, see FS_OPTIONSA failsafe came while on the ground: the motors were stoppedRTL wanted a height above ground and is using a height above homeRTL: no terrain data, using alt-above-homeThe ground station is heard againGCS Failsafe ClearedThe radio link is back, but the copter keeps the failsafe modeRadio Failsafe ClearedBack inside every fenceFence breach clearedThe fence stands back for 10 s after a mode changeManual recovery startedThe EKF trusts the GPS againGlitch clearedThe Advanced Failsafe changed stateAFS State: GPS_LOSSFlight modes
Auto refused: armed on the ground and the mission does not begin with a take-offAuto: Missing Takeoff CmdAUTO RTL refused: the mission has no return path or landing sequenceMode change to AUTO RTL failed: No landing sequence foundFollow mode is switched offSet FOLL_ENABLE = 1The flight mode change was refusedMode change to … failed: …The ground station is not allowed to select this modeGCS entry disabled (FLTMODE_GCSBLOCK)Mode changes are locked while the copter recovers from a fence breachin fence recoveryA stick-flown mode cannot be entered while the radio is in failsafein RC failsafeThe mode's own start-up check said noinit failedThis mode holds height itself, and there is no height estimateneed alt estimateThis mode needs a position estimate, and there is nonerequires positionThe throttle stick is too high to switch to a manual-throttle mode on the groundthrottle too highAUTOLAND: the landing direction, and why the mode can refuseMust already be flying!The mode change was refused, and the message says whyMode change to … denied, GCS entry disabled (FLTMODE_GCSBLOCK)The new flight mode refused to startFlight mode change failedA flight mode was asked for that this firmware does not haveNo such mode NThis mode cannot be paused or resumedFlight Mode Pause failedSmartRTL has stopped recording the way backSmartRTL deactivated: init failedSmartRTL was left part-way and one point of the return path was lostSmartRTL: lost one pointThe recorded way back is nearly fullSmartRTL Low on space!A flip was abandoned (ERR FLIP-2)ERR FLIP (Subsys 13)Follow took the present distance to the lead vehicle as its offsetRelative follow offset loadedSimple or Super Simple mode was switchedSIMPLE mode offThrow mode: from the hand to a steady hoverheight achieved - controlling positionTurtle mode is waiting for the throttleTurtle: raise throttle to armZigZag mode: storing the two ends of the line and flying between them…: moving to … (line N/N)
Motors, ESCs and outputs
Full throttle and still sinking: a motor may have failedPotential Thrust Loss (N)The engine stopped by itself, or would not startEngine max crank attempts reached
FRAME_CLASS names a helicopter, but this is multicopter firmwarePreArm: Invalid MultiCopter FRAME_CLASSThe motor setup is not completePreArm: Motors: …The throttle was high at power-on: ArduPilot waits for a restartESC calibration: Restart boardThe FETtec OneWire ESCs are not readyN of N ESCs are not sending telemetryThe board's output co-processor is not working properlyPreArm: IOMCU is unhealthyThe motor test was refused: the copter is not ready for it…: Board initialisingThe motor test was refused: the outputs are blocked…: Motor Emergency StoppedThe motor test was refused: the radio is not calibrated…: RC not calibratedArduPilot does not know what frame this isCheck frame class and typeA motor of this frame has no outputno SERVOx_FUNCTION set to MotorNThe motor output range is not validCheck …PWM_MIN and …PWM_MAXThe armed idle speed is above the in-flight minimum…SPIN_ARM > …SPIN_MINThe minimum motor speed in flight is set too high…SPIN_MIN too high N.N > 0.3The tricopter's tail servo has no outputno SERVOx_FUNCTION set to Motor7 for tail servoA PiccoloCAN ESC or servo is missing or inhibitedESC N not detectedA command to start the engine was refusedEngine: start control disabledReboot refused: it would start an automatic ESC calibrationReboot rejected, ESC cal on rebootA servo command was refused: that output belongs to something elseServoRelayEvent: Channel N is already in useA PWM device is on an output that DShot or an LED strip has taken overPreArm: SERVON_FUNCTION=N on disabled channelAn output's trim lies outside its minimum and maximumPreArm: SERVON_MIN is greater than SERVON_TRIMTake-off is held back until the motors are seen to spin… ESC RPM out of rangeThe flight controller is in ESC calibration, not in normal operationESC calibration: Passing pilot throttle to ESCsThese outputs cannot produce DShot or drive an LED stripChan N to N, …: …The engine went above its maximum RPMEngine: Above redline RPMThe copter is using most of its yaw authority only to hold its headingYaw Imbalance N.N%An ESC bus driver reported at start-upFTW using Half-DuplexA test of the configuration link to one ESCESC: Test …The motor test started, finished or was cut shortstarting motor testThe combustion engine is being started or stoppedTakeoff height set to N.NmMissions, fence, rally points, terrain
No route around the fences could be worked outDijkstra: …RTL is set to fly above the terrain, and has no way to measure itPreArm: no rangefinderThe fence's altitude limits contradict each otherInvalid FENCE_ALT_MIN valueThe fence is switched on, but no fence existsFences enabled, but none selectedThe fence margin or a circle's radius is wrongInvalid FENCE_MARGIN valueThe drawn fence stored on the aircraft could not be loadedPolygon fence(s) invalidThe fence is on, but there is no position to check it againstFence requires positionThe aircraft refused the fence the ground station sentReceived incorrect type (want=N got=N)The aircraft is already outside the fence on the groundVehicle breaching …The mission lacks an item that is required for armingPreArm: Missing mission item: …The mode is Auto, but there is no mission to flyPreArm: No mission library presentA rally point is required, and none is close enoughPreArm: Can't check rally without positionThe mission or fence file on the SD card could not be openedPreArm: Failed to open fence storagePath planning around obstacles needs a reboot to startOA requires rebootThe mission has a landing marker, but RTL is not told to use itPreArm: DO_RETURN_PATH_START set and RTL_AUTOLAND disabledNo memory for the terrain databaseTerrain: Allocation failedThe terrain files on the SD card are from before a correctionterrain data expired, possible errorsThe flight needs terrain heights, and the terrain database is offTERRAIN_SPACING can't be <= 0Terrain heights for this flight have not all arrived yetwaiting for terrain dataThe mission was changed while the copter was flying itAuto mission changed but failed to restart commandThe mission holds a command this firmware cannot carry outSkipping invalid cmd #NA mission command needed the ground height, and it was not availablebad do_loiter_to_altA navigation target could not be used (ERR NAVIGATION)ERR NAVIGATION (Subsys 22)This way of switching the fence on by itself is being retiredFENCE_AUTOENABLE is N, will be removed in 4.7, use 3The aircraft is close to a fence… in N.NmA ground station is using the old way of sending fencesInvalid fence point, bad count (N vs N)An upload of a mission, fence or rally points did not finishFence upload timeoutThe mission has no landing approach to jump toUnable to start find a landing abort sequencePayload place gave up without releasing the load… PLDP_RNG_MAX set and rangefinder not enabledThe terrain data and the aircraft disagree about the height of the take-off spotTerrain: clamping offset N.N to N.NThe mission is moving onDelaying N secA fence was switched on or offMin Alt fence enabled (auto enable)The whole mission arrived and was storedFlight plan receivedThe stored mission was erased at start-upClearing MissionA mission command has startedMission: N … NThe mission jumped to its landing approach or its way backReturn path startedA resumed mission repeats the last stretch of its routeMission: Returned to interrupted WPA failsafe let the mission go on, because the landing is closer that wayRejecting RTL: closer land if mis continuedPayload place: the stages of setting a load down… payload release thrust threshold: N.NA loiter command in the mission is finishedLoiter orbits completeThe mission ran out of commands: the plane returns homeReached RTL locationA change-speed command was appliedSet throttle NA mission waypoint is donePassed waypoint #N dist Nm
Plane: take-off, landing, QuadPlane
The VTOL takeoff was abandoned: airspeed above the takeoff limitFailed to complete takeoff, excessive windThe automatic VTOL takeoff took too long and was abandonedFailed to complete takeoff within time limitThe lift motors are at full power and the aircraft is still sinkingPotential VTOL Thrust Loss (N)The aircraft did not reach flying speed in the time allowedTransition failed, exceeded time limitThe landing type is one this firmware cannot flyLanding configuration error, invalid LAND_TYPEThe launch was felt and then rejected: the motor stays stoppedTimeout AUTOThe take-off was given up: the plane never reached 4 m/sTakeoff timeout: N.N m/s speed < 4m/s
Q_ANGLE_MAX is outside 10° to 80°PreArm: Check Q_ANGLE_MAXThe airspeed for lift-motor assistance has not been chosenPreArm: Q_ASSIST_SPEED is not setAUTO will not arm: the mission is not at a VTOL takeoffnot in VTOL takeoffQ_ENABLE is on, but the VTOL code has not startedPreArm: Quadplane enabled but not runningThe lift-motor layout in Q_FRAME_CLASS is not supportedConfig Error: Unsupported Q_FRAME_CLASS NForward throttle in Q modes is switched on for a tailsitterPreArm: set Q_FWD_THR_USE to 0The takeoff command from the ground station was refusedUser Takeoff only in GUIDED modeThe last waypoint is too close to the VTOL landing pointPreArm: VTOL land too short, min N.NmThe main loop is too slow for a QuadPlanePreArm: quadplane needs SCHED_LOOP_RATE >= 100The lift-motor test was refusedMust be disarmed for motor testA VTOL function was asked for, but the VTOL code is not runningVTOL not availableToo little free memory to start the QuadPlane codeConfig Error: Not enough memory for quadplaneTwo settings both decide how RTL endsPreArm: unset one of RTL_AUTOLAND or Q_RTL_MODETailsitter or tiltrotor was enabled after start-upPreArm: tailsitter setup not complete, rebootTailsitter and tiltrotor are both enabledPreArm: set TAILSIT_ENABLE 0 or TILT_ENABLE 0Takeoff is waiting for the rudder stick to be centredTakeoff waiting for rudder releaseThe VTOL transition command was refusedVTOL transition only in AUTOThe landing was broken off: the plane goes aroundLanding aborted, climbing to NmThe landing could not be started again; the plane goes to RTLUnable to restart landing sequenceThe lift motors started because the aircraft was too lowAlt assist N.NmThe lift motors started because the aircraft was badly out of attitudeAngle assist r=N p=NThe landing approach was cut short: the aircraft could not hold its speedVTOL pos1 low speed as=N.N at=N.NLift-motor ESC calibration is running: stabilisation is offStarting ESC calibrationThe aircraft flew past the landing point, or is pointing away from itVTOL Overshoot d=N.N cs=N.N yerr=N.NA tailsitter's transition was cut short by roll or by timeTransition VTOL done, roll errorDisarmed by itself after the automatic landingAuto disarmedAutomatic take-off: the launch was felt, then the motor was releasedTriggered AUTO. GPS speed = N.NFBWA take-off help for tail-wheel planes switched on or offFBWA tdrag offThe automatic landing has begunLanding approach start at N.NmThe flare began, and where the plane ended upDistance from LAND point=N.NmThe rangefinder took over, or gave up, the height for landingRangefinder engaged at N.NmThe landing will be flown again, and from whereRestarted landing via DO_LAND_START: NA switch changed reverse thrust, crow flaps or terrain followingNON AUTO TERRN: …A switch changed QuadPlane assistanceQAssist: Force enabledThe soaring system reports what it is doingSoaring: Enabled, automatic mode changes.TAKEOFF mode says what it is going to doClimbing to TKOFF alt then loiteringSteps of an automatic take-offHolding course N at N.Nm/s (N.N)The QuadPlane code started, with this motor layoutQuadPlane initialised, …Leaving the circle to fly the approach line into the windStarting VTOL land approach pathThe stages of the approach to a VTOL landingVTOL position2 started v=N.N d=N.N h=N.NThe aircraft has detected that it is on the groundLand completeThe vertical descent has begun, then its slow last partLand descend startedThe mission switched between multicopter and fixed-wing flightEntered VTOL modeA tailsitter has finished turning nose-up to hoverTransition VTOL done, zero throttleThe transition to flying on the wing has finishedTransition airspeed reached N.NThe lift motors are carrying the aircraft while it gains airspeedTransition started airspeed N.NAutoTune and control
The Acro levelling rate is larger than the angle gainPreArm: Check ACRO_BAL_ROLL/PITCHThe maximum lean angle is outside 10° to 80°…_ANGLE_MAX must be >= 10 and <= 80An attitude controller gain is zero or negative…_…_D must be >= 0AutoTune gave up: it could not find a gainAutoTune: Angle P Gain Determination FailedAutoTune gave up: the aircraft would not settle levelAutoTune: Failed to level, please tune manuallyAutoTune did not startAutoTune: failed yaw allocationSaving the trims from the switch was refusedtrim failed, large roll and pitch inputA position controller gain is zero or negative…_POSZ_P must be > 0SystemID mode would not startAxis requires switch from LoiterAutoTune could not measure D on this axis and left it at the minimumAutoTune: Min Rate D limit reachedQuicktune stopped, or would not startQuicktune: attitude error N.Ndeg - ABORTINGThe QuikTune script stopped, or would not startTuning: attitude error N.Ndeg - ABORTINGThe system identification test stopped before its endSystemID Parameter ErrorAutoTrim was started by holding the yaw stick while armingAutoTrim startAutoTune finished an axis: the gains it foundAutoTune: … Angle P:N.N, Max Accel:N.NAutoTune's gains were saved, tried or put backAutoTune: must be complete to test gainsAutoTune is paused because a stick is off centreAutoTune: Paused: Pilot Override ActiveWhat AutoTune is testing right nowAutoTune: Updating GainsAutoTune began its tests, or stopped themAutoTune: StartedAutoTune finished every axisAutoTune: SuccessFixed-wing AutoTune started, finished an axis, or stoppedStopped autotuneThe stick and servo trims were savedtrim completePlane's in-flight tuning knob changed, saved or reverted a valueTuning: revertedQuicktune is tuning the QuadPlane's hover gainsQuicktune: SavedThe QuikTune script is tuning the hover gainsTuning: starting tuneA system identification test started or finishedSystemID Starting: axis=NThe aircraft is turning itself into the windWeathervane Active: …
Logging and storage
A log download is in progressPreArm: Downloading logsThe flight log cannot be writtenPreArm: No SD cardNo log file could be opened at the moment of armingPreArm: Logging not started
LOG_BACKEND_TYPE asks for logging this board cannot doConfig Error: Too many logger backendsA request to download logs was refusedDisarm for log downloadThe firmware expects a parameter that is not in this buildConfig Error: param deflt fail:…The logging code found its own books out of orderInternal errors 0x1 (logger_mapfailure)One log has filled the whole on-board flash chipChip full, logging stoppedA dump of an earlier firmware crash was savedSaved crash_dump.binThe folder for the logs could not be created on the cardFailed to create log directory … : …The on-board log chip is being erased or repairedChip erase completeThe part of ArduPilot that writes the log is stuckAP_Logger: IO thread diedAll stored parameters were erasedAll parameters reset, reboot boardA parameter could not be changed from outsideParam write denied (…)The mission kept on the microSD card could not be savedMission storage failedAn error subsystem that Copter and Plane do not writeERR MAIN (Subsys 1)Notes ArduPilot writes at the start of a logNew missionThe card or the on-board flash is being formattedFormat flash: Failed (N)Board, internal errors, CAN, scripting
The main loop stopped for 2 secondsERR CPU (Subsys 19)The log recorded an internal errorERR INTERNAL_ERROR (Subsys 30)An IMU keeps sending damaged dataInternal errors 0x1000000 (imu_reset)The board's second processor restarted or stopped answeringInternal errors 0x1000 (iomcu_reset)The main loop stood still for half a secondInternal errors 0x8000 (main_loop_stuck)A calculation produced something that is not a numberInternal errors 0x400 (constraining_nan)The firmware stopped itself: it could not go onInternal errors 0x20 (panic)A chip on the board did not answer in timeInternal errors 0x4000 (spi_fail)A part of the firmware almost ran out of its own memoryInternal errors 0x800000 (stack_overflow)The processor was restarted by its watchdogForcing logging for watchdog resetThe board restarted itself while armed; arming checks are skippedWatchdog: resume WP NA Lua script has to allow arming, and has notPreArm: Too many auxiliary authorisersA device on the CAN bus stops armingPreArm: DroneCAN: …The firmware crashed earlier and left a crash dumpCrash Dump incomplete, dumping what we got!No memory was left at start-up for terrain data or ADS-BPreArm: ADSB out of memoryAn input pin is flooded with pulses and has been switched offPin N disabled (ISR flood)ArduPilot caught itself in a state that should never happenInternal Errors 0x0x…The processor cannot keep up with the main loopPreArm: Main loop slow (NHz < NHz)The parameters cannot be savedPreArm: parameter storage fullTwo different CAN devices claim the same node numberDuplicate Node …../N!A CAN device says it is not healthyNode N unhealthy!A calibration was asked for while armedDisarm to allow calibrationAn orientation parameter holds a number that is not an orientationInternal errors 0x400000 (bad_rotation)The scripts on board are not the ones that were approvedScripting: loaded CRC incorrect want: 0x0x…Lua scripting reports a problem and blocks armingScripting: …A serial option has moved to the MAVLink link in 4.7SERIALN_OPTIONS bit 10 ('no forward mavlink') must not be set; use MAVn_OPTIONS bit 1 insteadThe table of CAN node numbers is full, or was clearedDroneCAN DNA allocation failed; database fullFile transfer over the telemetry link is not availableFTP disabledThe ground station speaks an older dialect of MAVLinkgot MISSION_REQUEST; use MISSION_REQUEST_INT!A message was asked for more often than ArduPilot can send itRequested rate for message ID N too fast. Increase SCHED_LOOP_RATEThe MAVLink signing key could not be setERROR: Won't setup signing when armedA pin or a data channel of the processor misbehavedInternal errors 0x2000000 (gpio_isr)An I2C bus was flooded with interruptsInternal errors 0x80000 (i2c_isr)The parameters were restored from the backup copyInternal errors 0x10000000 (params_restored)The code reached a place it should never reachInternal errors 0x100000 (flow_of_control)ArduPilot found no place to load scripts from, or no scriptsLua: open directory (…) failedA Lua script stopped with an errorError: …A script uses something this 4.7 firmware does not offerWarning: userdata creation does not take arguments, will be fatal in futureThe Lua scripts do not have enough memoryInsufficent memory loading …The Lua script engine stopped, restarted or could not startScripting: …A Lua script ran for too long in one go… exceeded time limitA health flag, put into words for the transmitter's screenBad GPS HealthMain loop timing, printed because
SCHED_DEBUG is onPERF: N/N [N:N] F=NHz sd=N Ex=NA message from a CAN device itselfCAN[N] …A serial port now works as an adapter to the CAN busCANManager: Starting SLCAN Passthrough on Serial N with CANNHigh-latency telemetry was switched on or offHigh Latency …Two serial ports are joined straight throughPassthru disabledLines from the network connectionNET: Failed to allocate buffersThe fast attitude loop changed its rateRate CPU …, rate set to NHzStand-by was switched on or offStand By EnabledToy mode: messages of the SkyViper toy coptersTmode: throttle armRangefinder, optical flow, camera, OSD and other devices
A device that is switched on in the parameters is not readyPreArm: FETtec: …The proximity sensor sees something within 0.6 mPreArm: Proximity N deg, N.Nm (want > N.Nm)The pin of a button or an RPM sensor cannot be usedBTN_PINN=N, set SERVON_FUNCTION=-1The hydrogen fuel cell is not running, or stopped answeringGenerator: IE using … protocolA Loweheiser or Cortex generator is not ready for flightLH: Generator warming up (waiting for data)The RichenPower generator is not ready for flightrequested state is not RUNThe generator is switched on or off in the parameters, but not in the running systemGenerator: No serial port foundA gimbal type is set, but its driver did not startcheck TYPEA menu is open on the video screenIn OSD menuTwo OSDs are set, but only one could startOSD_TYPE2 not compatible with first OSDThe parachute has been released since power-onChute is releasedThe parachute is enabled, but nothing is set up to release itChute has no relayA proximity sensor is not sending distancesPRXN: Not ConnectedA rangefinder's driver is running, but no readings arriveRangefinder 0x…: Not ConnectedA rangefinder is switched on in the parameters, but no driver started for itRangefinder 0x…: Not DetectedThe rangefinder's input pin is not set, or cannot be usedRNGFNDN_PIN=N, set SERVON_FUNCTION=-1A relay's pin cannot be used, or two relays share one pin…=N invalidThe RunCam camera has not answered yetRunCam device not foundSurface tracking has no rangefinder pointing that waySurfaceTracking: no upward rangefinderThe tracking camera (visual odometry) is not ready or disagrees with the attitudeyaw diff N.N deg (>10)The winch is enabled, but not workingwinch unhealthyThe ADS-B receiver's driver could not startADSB: Unable to initialize ADSB driverThe ADS-B unit stopped answering or reports a failureADSB: Transceiver heartbeat timed outA pulse input cannot be read on the pin you chose…: Failed to detach interrupt from NThe camera did not start or stop recording when the aircraft armedCamera: failed to … recordingThe engine's fuel-injection type is not one this firmware knowsUnknown EFI typeThe optical-flow calibration rejected its result… scalar…:N.N too low (<N.N)The optical flow calibration ran out of timeA Topotek or XFRobot gimbal camera could not do what was asked… tracking failedThe gimbal driver refused a commandMount: …The point the camera looks at could not be worked outPOI: distance > 5km: N.N mA Siyi gimbal camera could not record, or its firmware is oldSiyi: can't start recording: No CardA Xacti gimbal camera reports an error… time …setThe store of obstacles for path planning was not set upDB init failed . Sizes queue:N, db:NThe digital OSD has no serial port to talk throughMSP backend not availableThe OSD font could not be loadedOSD: Failed to load font NA manual parachute release was refusedParachute: Too lowThe landing target is sent in a coordinate frame ArduPilot does not acceptPlnd: Frame not supportedPrecision landing saw its target: the first lock failed, or succeededPrecLand: Init CompleteThe copter is trying again to find the landing target, or has given upPrecLand: Retry CompletedPrecision landing can no longer see its targetPrecLand: Target LostA DroneCAN proximity sensor has no range setConfigure PRXN_MIN and PRXN_MAXA Benewake lidar on I2C answered, but cannot be usedTFS20L: No response from sensorThe radar altimeter reports a fault of its ownRangeFinder: Temperature alertAn I2C temperature sensor did not answer at start-up… reset failedThe winch was told to move, and the line is not moving… unstuckThe ADS-B unit was found, or its settings changedADSB:Detected … vN.N.N SN:N …A button wired to the flight controller did its jobButton N: executing (… …)A camera answered and described itselfCamera: … … fw:N.N.N.NA rangefinder or proximity sensor was foundRPLidar: (…)The optical-flow calibration is running or has finishedFlowCal: StartedThe gripper was told to close or openGripper load grabbingThe landing gear was told to go down or upLandingGear: RETRACTA mission command closed or opened the gripperGripper ReleasedThe gimbal camera reports what it is doing… get/set … res:NThe gimbal answered and reported its model and firmwareMount: Siyi zoom fw vN.N.NThe gimbal's point-of-interest lock changed statePOI: ClearedPrecision landing has picked up its targetPrecLand: Target FoundThe video transmitter was found; these are its settingsVTX: …N NMHz, PWR: NmWThe winch reports what it is doing… move state unknown