| Bad accelerometer health |
Indicates that one or more of the accelerometers are unhealthy. |
The operator should immediately begin the preplanned landing sequence. |
| Bad attitude reference (AHRS) health |
Indicates an unhealthy estimation of the system's attitude. This is normal during the first part of the preflight and should resolve before takeoff. |
The operator should intiate an emergency landing if this persists for more than 5 seconds. |
| Low battery |
An aircraft is low, and the aircraft needs to be landed before it is exhausted. |
If the main battery is low then the aircraft will automatically jump to the preplanned landing in the mission. If the VTOL battery is low then the aircraft will change modes to QLand, and land in place. |
| Bad airspeed health |
The aircraft is unable to read the airspeed sensor. |
The operator should immediately begin the preplanned landing sequence if this persists for more than 5 seconds. The aircraft may stall without an airspeed sensor and the operator should be ready to activate an Emergency Landing if this happens |
| Bad GPS Health |
The aircraft has lost GPS fix, has insufficent GPS fix, or the GPS is reporting an error. |
If this persists for more then five seconds the operator should land the vehicle using a combination of FBWB and QStabilize flight modes. QLand, QLoiter, and normal planned landings cannot be safely performed without GPS. |
| Bad gyroscope health |
Indicates that one or more of the gyroscopes are unhealthy. |
The operator should initiate an emergency landing |
| Logging Error |
The autopilot is unable to log to its SD card. |
If on the ground, first try restarting the aircraft. If the problem persists, power down the aircraft and reformat the SD card. If this happens during flight, you may safely continue flying, but no autopilot data for post-processing or logs for analysis will be available. If this data is needed, land as soon as practical |
| Bad magnetometer health |
Indicates that one or more of the magnetometers are unhealthy. |
The operator should immediately begin the preplanned landing sequence. |
| Bad barometer health |
Indicates that one or more of the barometers are unhealthy. |
The operator should immediately begin the preplanned landing sequence. |
| No RC input |
Indicates that the aircraft is not receiving signal from the RC controller. |
Use the GCS to bring the aircraft back within range if RC signal is required for flight. If the aircraft does not regain link within 15 seconds (by default) it will change flight modes to Rally |
| Failsafe active |
Indicates that an automated failsafe, such as loss of RC, loss of GCS telemetry, or low battery is active. |
Consult the list of failsafes to determine an appropriate action. Except for loss of GCS telemetry this will always be accompanied by another warning. |
| EKF: Compass variance |
The main AHRS algorithm is rejecting compass data. |
The operator should intiate an emergency landing if this persists for more than 15 seconds. |
| EKF: Position horizontal variance |
The main AHRS algorithm is rejecting horizontal GPS data. |
The operator should intiate an emergency landing if this persists for more than 15 seconds. |
| EKF: Position vertical variance |
The main AHRS algorithm is rejecting vertical GPS data. |
The operator should intiate an emergency landing if this persists for more than 15 seconds. |
| EKF: Velocity varaince |
The main AHRS algorithm is rejecting GPS velocity data. |
The operator should intiate an emergency landing if this persists for more than 15 seconds. |
| Excessive X vibration |
The aircraft is suffering from an excessive amount of vibration. This could be from damage to the main motor or VTOL system. |
The operator should initiate an emergency landing if this persists for more than 5 seconds. |
| Excessive Y vibration |
The aircraft is suffering from an excessive amount of vibration. This could be from damage to the main motor or VTOL system. |
The operator should initiate an emergency landing if this persists for more than 5 seconds. |
| Excessive Z vibration |
The aircraft is suffering from an excessive amount of vibration. This could be from damage to the main motor or VTOL system. |
The operator should initiate an emergency landing if this persists for more than 5 seconds. |
| High wind |
The aircraft has detected that it has exceeded it's wind limit. |
The operator should immediately begin the preplanned landing sequence. |
| No telemetry signal |
The GCS has not recieved any data from the aircraft in the last second. |
The aircraft will switch to flight mode Rally automatically after 15 seconds (by default) of not recieving data from the GCS and fly to the nearest rally point. See the failsafes section for more details. |
| High telemetry radio noise |
The telemetry radio link to the aircraft is experiencing an excessive level of RF noise. |
Do not takeoff with this warning active. If in flight move to improve the radio link and try and reduce noise, or begin the preplanned landing sequence. |
| High autopilot temperature |
The autopilot is excessively warm. |
If on the ground power off the system and let it cool before restarting the preflight. Avoid direct sunlight on the avionics while preflighting in warm ambient conditions. If in flight then begin the planned landing sequence if the warning does not clear within a minute. |
| Autopilot error |
The autopilot has encountered an unexpected internal condition. |
If in flight land immediately. Contact support and provide the log files from the flight so that this may be rectified for the future. The aircraft may be rebooted and flown again to clear the error. |