RflyMAD: A Dataset for Multicopter Fault Detection and Health Assessment

This site presents the RflyMAD dataset which is used for multicopter fault detection and isolation (FDI) or health assessment (HA). The dataset is collected from RflySim platform and real flight by Beihang Reliable Flight Control Group (Rfly). There are 5629 flight cases in total in the dataset, 2566 for software-in-the-loop (SIL) simulatin, 2566 for hardware-in-the-loop (HIL) simulation and 497 for real flight. The dataset includes 11 types of common faults under 6 flight statuses to cover more occasions in which the multicopters have different mobility levels when faults occur.

The introduction video of the RflyMAD dataset is now available at https://www.youtube.com/watch?v=MZby4mOPRu4.

1. What is RflyMAD?

Different from research fields like computer vision, batteries, and mechanical vibration, there are relatively few publicly datasets related to the FDI, PHM and HA problems of aircraft systems. Regarding the lack of fault dataset, we form RflyMAD dataset. The RflyMAD dataset contains both simulation and real flight data, and covers sufficient fault types and flight statuses, ensuring both quantity and quality.

The hierarchy of RflyMAD dataset is shown in the following figure.

Note: In Real Flight Data, there are extra wind data about velocity and direction at the experiment time recorded in the dataset.

1.1 Varied Multicopters

In real flight experiments, in order to enhance the generalization of the dataset, three multicopters with different diagonal sizes are used to collect data. They are Droneyee X200 (Diagonal size of 200mm, 1.054kg), Droneyee X450 (Diagonal size of 450mm, 2.084kg) and Droneyee X680 (Diagonal size of 680mm, 4.068kg).

Note: The physical parameters of multicopter dynamic model uesd in SIL simulation and HIL simulation are achieved from Droneyee X450, including weights, moment of inertia and motor parameters.

1.2 Broad Fault Types

There are 11 fault types in RflyMAD dataset, including actuators, sensors of the multicopter and environmental effects. The exact cases in each fault type are listed in the following table.

Type of FaultsSIL SimulationHIL SimulationReal Flight
Motor(1-4)921921231
Propeller(1-4)435435×
Low Voltage2020×
Wind Affect150150×
Load Lose150150×
Sensors' Noise505082
Accelerometer12812820
Gyroscope12812820
Magnetometer12812820
Barometer12812820
GPS12812820
No Fault20020084
Total25662566497

Note: × represents this item does not exist in sub-dataset and the number means the amount of corrresponding cases.

Motor(1-4) represents the number of failure motors is in range of 1 to 4.

1.3 Sufficient Flight Statuses

The following table lists all 6 flight statuses in this dataset.

Flight statusSIL SimulationHIL SimulationReal Flight
Hover
Waypoints
Velocity Control
Circling
Acceleration
Deceleration×

Note: represents this item exists in sub-dataset and × represents not.

1.4 Exact Data in One Flight Case

As shown in the figure of dataset hierarchy, each flight within the dataset contains four types of raw data and their processed files, and they could be described as follows:

Note: It is worth noting that the GTData only exists in simulation data and the BAG files only in real flight data, so there are still four types of data associated with each flight.

1.5 Meanings of Flight Command in Flight Information

In Flight Information, there are flight commands, fault types and fault parameters. The exact meaning of these elements can be seen from here. The various elements contained within the flight information are common in both simulation and real-flight data collection. These elements encompass not only flight control commands and fault information for the multicopter but also serve as labeling information within the dataset.

1.6 When Faults Occur in RflyMAD

In the RflyMAD dataset, each instance of data encompasses stages from takeoff to fault injection and concludes with the end of the fault, providing a comprehensive reflection of the impact of faults on the multicopter. In the dataset, for ULOG, ROSBAG and GTDData, specific message types serve as indicators of the presence of faults in each data type. Here, we will introduce them in detail. For ULOG data, message rfly_ctrl_lxl contains fault id and fault parameter, which indicate whether a faut has occurred by altering the specific numerical values of signals in this message. The following figure shows when a fault occurs in one flight in ULOG.

For ROSBAG data, just like ULOG data, message rfly_ctrl_lxl contains fault id and fault parameter. The above figure also shows when a fault occurs in one flight in ROSBAG. For GTData, message fault_state, which located in file TrueState_data.xlsx and UAVState_data.xlsx, indicates whether there is a fault or not. When a fault occurs, the value of fault_state turns to 1, otherwise, it stays 0 as the following figure shows.

2. Citation

Our data paper is now available at Arxiv. If you are interested in our dataset, you can also read our data paper ! If you find our dataset is useful, and use our data in your research, please cite it as:

3. Downloads

3.1 Datasets Downloads

Note: The files below are restored on Beihang University Yunpan. If you have access to download them directly, please use this download link with a faster speed. Or if you have any problems to download the dataset from the above link, you can download them with Kaggle.

Raw data and their related processed files are included in each .zip.

NameLinkSizeRemark
SIL-Motor(1).zip4.61GBSIL Simulation data, including flight statuses like hover and circling
SIL-Motor(2).zip4.06GBSIL Simulation data, including flight statuses like waypoints, velocity, acceleration and deceleration
SIL-Prop.zip3.60GBSIL Simulation data, including all flight statuses with propeller fault
SIL-Sensors.zip5.68GBSIL Simulation data, including all flight statuses with accelerometer, gyroscope, magnetometer, barometer and GPS fault
SIL-Voltage.zip313MBSIL Simulation data, low-voltage fault type
SIL-Wind.zip4.08GBSIL Simulation data, different wind types and strength
SIL-Load.zip2.31GBSIL Simulation data, changing the weight or distribution of loads in multicopter during the flight
SIL-No Fault.zip1.64GBSIL Simulation data, including all flight statuses with no fault
HIL-Motor(1).zip4.81GBHIL Simulation data, including flight statuses like hover and circling
HIL-Motor(2).zip4.5GBHIL Simulation data, including flight statuses like waypoints, velocity, acceleration and deceleration
HIL-Prop.zip3.76GBHIL Simulation data, including all flight statuses with propeller fault
HIL-Sensors.zip5.91GBHIL Simulation data, including all flight statuses with accelerometer, gyroscope, magnetometer, barometer and GPS fault
HIL-Voltage.zip357MBHIL Simulation data, low-voltage fault type
HIL-Wind.zip3.89GBHIL Simulation data, different wind types and strength
HIL-Load.zip2.62GBHIL Simulation data, changing the weight or distribution of loads in multicopter during the flight
HIL-No Fault.zip1.41GBSIL Simulation data, including all flight statuses with no fault
Real-Motor.zip5.57GBReal flight data, including three diagonal size multicopters
Real-Sensors.zip4.01GBReal flight data, including three diagonal size multicopters
Real-No Fault.zip973MBReal flight data, including three diagonal size multicopters

Apart from the above formal data in RflyMAD, we also provide a sample dataset with a smaller size for users to use and check. The processed files of the sample dataset is also given in the following link. The data processing tools used to generate processed files will be introduced in Quick Use.

NameLinkSizeRemark
SampleData.zip340.34MBSample data, including 12 flight cases in each sub-dataset, so there are 36 flight cases in total.
ProcessData.zip12.25MBProcessed data of SampleData, generated by data processing tools.

3.2 AutoTest Platform Downloads

If users want to collect their own simulation data (including SIL simulation and HIL simulation data), an autotest platform is provided for users to download from the following link:

BuaaAutoTestPlatform : https://github.com/lerlis/BuaaAutoTestPlatForm

With this platform, users can change the parameters of the multicopter and add their own flight statues and fault types. Detailed information could be seen from the above link.

4. Quick Use

After downloading the RflyMAD dataset, you'd better to reorganize the resources in the following format, just like the hierarchy mentioned before, in order to use our toolkit conveniently.

The detailed information about how to use our data processing tools to extract processed data from RflyMAD dataset is introduced in our Github repository and the download link is in the following

Data processing tools : https://github.com/lerlis/Data_processing_tools.

Please check this site to learn more about our data processing tools in order to use our dataset quickly. After using data processing tools, the program will generate processed data files in --restore_path, and the file names of the processed data files are arranged according to specific codes as shown in the figure below

The first number in the code represents the type of data, whether it is real flight data, SIL or HIL data, and the second number represents the flight status of the UAV, the third and fourth numbers represent the fault types. The last six numbers are a simple number arrangement within the same data type. And the specific meaning of the numbers on each coding position could be obtained in the following table

NumberSub-datasetNumberFault Type
1SIL0motor
2HIL1propeller
3Real2low voltage
----------------------3wind affect
NumberFlight Status4load lose
0hover5accelerometer
1waypoint6gyroscope
2velocity7magnetometer
3circling8barometer
4acce9GPS
5dece10No fault

For example, if a processed data file named 'Case_3109000005.csv', it means the UAV is flying waypoints under GPS faults, and this flight case is a real flight. 000005 means it maybe the sixth flight case with the same situation during the data extraction process this time.

5. Samples

Here we show two examples to diagnose faults of multicopters by using data in RflyMAD. The one is data-driven method and the other one is model-based method. On the one hand, users could learn how to use RflyMAD in their research by these two examples. And on the other hand, the support relationship between the simulation and real flight data is also be verified by the transfer learning method.

5.1 Data-driven Method --- Transfer Learning

The detailed methods and results can be accessed from Supplementary experiments to verify data support ability based on transfer learning.

5.2 Model-based Method --- Kalman Filter

In this method, we use Kalman Filter to estimate the fault conditions of one flight case in RflyMAD dataset. The detailed information about how a simplified dynamic model is established for the multicopter and how to use kalman filtering method in the process of fault diagnosis while utilizing appropriate data can be found in the Model-based Method: Kalman Filter.

6. Notes

For more information about how to use our dataset, please check other parts of our OpenHA websites.

7. Licence

RflyMAD dataset is copyright by Reliable Flight Control Group, Beihang University. The dataset and related work are supposed to be used in non-commercial situations. If you are intended to use it for commercial purposes, please contact us or from email: qq_buaa@buaa.edu.cn or lexiangli@buaa.edu.cn.