Skip to content

RflySim PHM - Fault Injection and Health Assessment Interface Library

The RflySim PHM (Prognostics and Health Management) library provides a comprehensive suite of tools for fault injection and health assessment, supporting modeling, injection, and evaluation of various hardware faults on UAVs. It is designed to validate the fault tolerance and fault-handling performance of flight control systems.

Module List

Power System Faults

Module Function Description
Motor Fault Motor fault injection, supporting fault modes such as reduced motor efficiency, stalling, and complete shutdown
Prop Fault Propeller fault injection, supporting fault modes such as blade damage, detachment, and efficiency degradation
Battery Fault Battery fault injection, supporting fault modes such as voltage drop, capacity decay, and increased internal resistance

Environmental Disturbance Faults

Module Function Description
Wind Fault Wind disturbance fault injection, supporting environmental disturbances such as gusts, turbulence, and wind shear
Load Fault Load fault injection, supporting fault modes such as sudden load changes, center-of-gravity shift, and payload detachment

Sensor Faults

Module Function Description
GPS Fault GPS fault injection, supporting fault modes such as positioning drift, signal loss, and reduced accuracy
Sensor Fault General-purpose sensor fault injection, supporting faults in IMU, magnetometer, barometer, and other sensors

Utility Modules

Module Function Description
Fault Params Extract Fault parameter extraction module, used to extract and parse fault parameters from fault configuration files

Fault Type Descriptions

Power System Faults

Fault Type Typical Manifestations Application Scenarios
Motor efficiency degradation Reduced rotational speed, slower response Motor aging, thermal protection activation
Motor stalling Complete loss of thrust Mechanical failure, foreign object blockage
Propeller damage Reduced thrust, increased vibration Blade impact, fatigue cracks
Battery voltage drop Insufficient power, premature landing Low-temperature operation, deep discharge

Environmental Disturbance Faults

Fault Type Typical Manifestations Application Scenarios
Gust disturbance Attitude oscillation, position deviation Strong wind conditions, urban wind fields
Turbulence disturbance Random vibration, control difficulty Complex terrain, wake regions
Sudden load change Center-of-gravity shift, reduced control margin Payload release, suspended payload swing

Sensor Faults

Fault Type Typical Manifestations Application Scenarios
GPS drift Increased positioning error, navigation failure Signal obstruction, multipath effects
IMU drift Attitude estimation bias, spin divergence Temperature drift, vibration interference
Magnetometer interference Yaw angle jumps, calibration failure Electromagnetic interference, hard-iron effects

Application Scenarios

Fault-Tolerant Control Algorithm Validation

  • Fault Detection: Validate the flight control system’s ability to detect various faults and its response speed
  • Control Reconfiguration: Test the system’s ability to reconfigure control and implement degraded control after fault occurrence
  • Safe Landing: Validate emergency landing strategies under severe fault conditions

Sensor Fusion Algorithm Testing

  • Fault Identification: Test the capability of multi-sensor fusion to identify single-sensor faults
  • Weight Adjustment: Validate adaptive sensor weight adjustment under fault conditions
  • State Estimation: Evaluate state estimation accuracy under fault conditions

Flight Safety Assessment

  • Fault Coverage: Assess the flight control system’s coverage capability across different fault modes
  • Fault Propagation: Analyze fault propagation paths and impact scope within the system
  • Safety Boundary: Determine safe flight boundaries under various fault conditions

Usage Considerations

Fault Parameter Configuration

  1. Fault Intensity: Fault intensity parameters must be set within a reasonable range; excessively large values may cause simulation divergence or crash.
  2. Gradual Injection: It is recommended to inject faults gradually to avoid simulation instability caused by instantaneous abrupt changes.
  3. Injection Timing: Select appropriate fault injection timing to avoid injecting severe faults during critical control phases (e.g., takeoff or landing).
  4. Parameter Consistency: Ensure fault parameters match the corresponding fault type to avoid incompatible parameter combinations.

Simulation Safety

  1. Boundary Protection: Set reasonable flight boundaries; automatically terminate the simulation if the UAV’s state exceeds safe limits.
  2. Fault Recovery: When designing fault recovery tests, ensure sufficient time and space for recovery.
  3. Multiple Faults: Exercise caution when testing simultaneous multiple faults to avoid unpredictable interaction effects.
  4. Logging: Enable detailed simulation logging for post-analysis and fault reproduction.

Interaction with Flight Control System

  1. Message Frequency: The frequency of fault injection messages must match the flight control processing cycle to avoid message accumulation or loss.
  2. Protocol Compatibility: Ensure fault parameter formats are consistent with those expected by the flight control system to prevent parsing errors.
  3. Permission Management: Thoroughly validate fault injection logic in simulation before conducting real-flight tests.
  4. Emergency Stop: Ensure a reliable emergency stop mechanism is available during real-flight tests to immediately take over control in case of fault loss of control.

Note: This document serves as the index for the RflySim PHM library. For detailed usage instructions for each module, please refer to the corresponding standalone module documentation pages.