Skip to content

OnFlight Hub and Hub Plus / Data Converter Manual

RDM-300 conversion

Offload an OFH+ RDM-300 recording and export full-rate CSV or MATLAB data.

On this page

Use Appareo RDM Utility to offload the RDM-300, then use the OnFlight Data Converter to produce CSV or MATLAB files. The converter preserves each recorded 25 Hz snapshot and unpacks the analog and GNSS measurements automatically.

For installation, calibration, and the recorded channels, see RDM-300 integration.

Convert an RDM-300 recording

  1. Offload with Appareo RDM Utility. Save the original binary offload (.bin) or its raw ARINC CSV export. Keep the original offload.
  2. Copy the input to a folder on your computer where the converter can save the output.
  3. Open the OnFlight Data Converter and choose Select File To Convert. Select the .bin or raw ARINC .csv file.
  4. Check that Input format shows RDM-300. Snapshots Found is the number of recorded snapshots available for conversion, including partial snapshots.
  5. Enter Pilot Name, Tail Number, and Aircraft Type if desired. These values are included in the CSV header; they are not part of the RDM recording or MAT output.
  6. Choose CSV (25 Hz) or MAT (25 Hz), then choose Convert.
  7. Open the output at the path shown under File Saved As.

Choose the raw ARINC CSV, not the utility’s summary CSV. A summary export can have fewer samples; the converter cannot recover samples absent from that file. RDM input offers CSV and MAT output.

The converter reads the OFH+ RDM format directly, so there is no ICD spreadsheet selection in this workflow. Use the ICD spreadsheet when exporting decoded CSV with Appareo RDM Utility.

Output files

Outputs are saved beside the input. The _raw_arinc suffix is removed from a raw-export filename before adding the output suffix.

Input CSV output MATLAB output
flight.bin flight_rdm300.csv flight_rdm300.mat
flight_raw_arinc.csv flight_rdm300.csv flight_rdm300.mat
flight_6_raw_arinc.csv flight_6_rdm300.csv flight_6_rdm300.mat

The source file is preserved. A successful conversion replaces an existing output with the same name; a failed conversion leaves an existing export intact. Inputs with the same base name produce the same output name.

CSV layout

RDM CSV follows the same layout as a native OnFlight CSV:

Row Contents
1 Pilot name entered in the converter.
2 Tail number entered in the converter.
3 Aircraft type entered in the converter.
4 Readable column headings, with units where applicable.
5 onward One recorded snapshot per row.

Shared measurements use the same headings as native OnFlight exports, for example INS Pitch [deg], GNSS Alt WGS84 [ft], and GNSS Horz Pos Acc [ft]. Exports contain 39 measurement and recorder-time columns. Packed words and status fields are decoded internally.

MATLAB layout

MAT output contains one named numeric column vector per field. Corresponding entries in every vector describe the same snapshot. Shared variable names match the native OnFlight export, including ins_pitch_deg, gnss_alt_wgs84_ft, and gnss_horz_pos_acc_ft. Unavailable numbers use NaN. Pilot and aircraft header text is omitted.

For example, load the file and plot pitch against elapsed recorder time:

data = load('flight_rdm300.mat');
plot(data.rdm_elapsed_s, data.ins_pitch_deg);
xlabel('Elapsed recorder time (s)');
ylabel('Pitch (deg)');

Measurements and units

The export includes the recorded attitude, raw body acceleration and angular rates, INS position and velocity, pressure altitude, analog inputs, UTC, and GNSS measurements. See recorded fields and rates for the channel list.

Quantity Convention
INS and GNSS latitude/longitude Decimal degrees, with 0.0000001 degree resolution.
INS and GNSS altitude Feet above the WGS84 ellipsoid, with 0.125 ft resolution.
GNSS horizontal/vertical accuracy Feet; receiver accuracy estimates.
Pressure altitude Feet, standard pressure, with 0.125 ft resolution.
Pitch and roll Signed degrees.
True heading 0–360 degrees.
Body acceleration g; aircraft X forward, Y right, Z down.
Body angular rates Degrees/second.
INS north/east/down velocity Knots; down is positive.
Analog position Normalized value: 0–1 for two-point calibration, −1–+1 for three-point calibration.
Analog voltage Volts.

INS coordinate labels 071/072 and 073/074 use the same two-word encoding as GNSS. Missing or invalid coordinate halves leave that coordinate unavailable.

Only channels sent to the RDM are included. This recording does not provide the native Hub log’s temperature, magnetic-field, MSL altitude, control-assignment metadata, or separate INS health fields.

Time and sampling

Each output row represents one observed 25 Hz snapshot, normally spaced about 0.04 seconds apart. Actual recorder timestamps are preserved. The converter does not resample the recording onto an artificial time grid or create rows for entirely missing snapshots.

The converter assembles each GNSS update across packets A/B/D and the following A, placing all its fields on the original update’s row.

New GNSS measurements normally arrive at 5 Hz. The converter repeats the latest decoded GNSS values across the intervening 25 Hz rows. These are repeated samples, not new receiver measurements. Before the first GNSS update, values are unavailable. If a new update contains a missing or invalid field, that field becomes unavailable rather than retaining an older value. Coordinate parts are always decoded from the same update. A new recorder session clears the retained GNSS values.

RDM Device Time [s] / rdm_device_time_s is the recorder timestamp of the first retained word in the snapshot. It is distinct from the Hub’s native sys_time_s and is not an independent sensor acquisition timestamp. RDM Elapsed Time [s] / rdm_elapsed_s starts at zero for each detected recorder session.

If recorder time moves backward within an input file, elapsed time starts over.

Binary offloads retain recorder ticks of 1/16000 second (62.5 microseconds). Raw ARINC CSV uses its exported millisecond timestamps. These are timestamp resolutions, not guarantees of timing accuracy.

UTC fields combine the recorded time (150), date (260), and microsecond fraction (070) from the same snapshot, with 1 microsecond resolution. UTC Sec / utc_s includes the fractional second, for example 6.563864. All three words must be available and valid to produce the decoded UTC fields; the fraction must be from 0 to 999,999 microseconds. This resolution is distinct from the 25 Hz update rate and the recorder timestamp resolutions above. RDM exports do not contain the native Hub Plus GPS week, time-of-week, or clock-initialization fields.

Unavailable and partial data

An unavailable or missing measurement is blank in CSV and NaN in MAT. A valid recorded zero stays zero.

Numeric words with normal SSM 3 are decoded. UTC date uses normal SSM 0. Other numeric statuses, including 1 = NCD (no computed data), produce unavailable measurement values. The converter checks status internally; SSM columns are not exported.

INS estimates continue to be exported when the sender retains them during degraded navigation. Normal SSM indicates that an estimate is available; it does not establish INS health or accuracy. A separate INS health flag is not in the RDM stream. Use the native OFH+ microSD log when that flag is needed.

Analog positions and voltages

Each physical channel has a Val and a Volt column (ain0_val / ain0_volt through ain3_val / ain3_volt). Only the active type has a value in each row. When calibration is available, the recorder carries a normalized position; otherwise it carries measured voltage. Unlike a native OnFlight log, an RDM word does not carry both forms for the same channel at once.

If a channel’s measurement type changes, the inactive position or voltage column becomes unavailable. The converter does not carry a previous position or voltage forward.

Channels retain the physical AIN0–AIN3 order. The RDM stream does not identify which control is attached to each channel. Follow Analog inputs and calibration to connect and calibrate control-position sensors.

Troubleshooting

Symptom What to check
The CSV is rejected as a summary export. Select the raw ARINC CSV or the original binary offload from Appareo RDM Utility.
CRC, parity, truncation, or format error. Check that the input is a complete OFH+ RDM offload or raw export. Keep the original file and include the exact error when contacting support.
GNSS values repeat across rows. New receiver measurements normally arrive at 5 Hz; the converter repeats the latest decoded values in the intervening 25 Hz rows.
GNSS values are blank in CSV or NaN in MAT. No GNSS sample is available yet, or the latest update contains an unavailable or missing measurement.
Analog position is blank but voltage is present. The channel is using voltage fallback. Verify its calibration and wiring.
INS latitude or longitude is unavailable. Both coordinate halves must be present and valid in the same snapshot.

For assistance, see Support.

Appendix: output field reference

The following table lists the 39 CSV columns and matching MAT variable names in export order. Shared names follow the native OnFlight convention. The converter combines coordinate halves and unpacks measurements automatically; packed words, codes, SSM, and snapshot diagnostics are not exported.

CSV heading MAT variable
RDM Device Time [s] rdm_device_time_s
RDM Elapsed Time [s] rdm_elapsed_s
IMU Accel X [G] imu_accel_x_g
IMU Accel Y [G] imu_accel_y_g
IMU Accel Z [G] imu_accel_z_g
IMU Gyro X [deg/s] imu_gyro_x_dps
IMU Gyro Y [deg/s] imu_gyro_y_dps
IMU Gyro Z [deg/s] imu_gyro_z_dps
GNSS Fix gnss_fix
GNSS Num Sats gnss_num_sv
UTC Year utc_year
UTC Month utc_month
UTC Day utc_day
UTC Hour utc_hour
UTC Min utc_min
UTC Sec utc_s
GNSS Horz Pos Acc [ft] gnss_horz_pos_acc_ft
GNSS Vert Pos Acc [ft] gnss_vert_pos_acc_ft
GNSS Alt WGS84 [ft] gnss_alt_wgs84_ft
GNSS Lat [deg] gnss_lat_deg
GNSS Lon [deg] gnss_lon_deg
INS Pitch [deg] ins_pitch_deg
INS Roll [deg] ins_roll_deg
INS Heading True [deg] ins_heading_true_deg
INS North Vel [kts] ins_ned_vel_x_kts
INS East Vel [kts] ins_ned_vel_y_kts
INS Down Vel [kts] ins_ned_vel_z_kts
INS Alt WGS84 [ft] ins_alt_wgs84_ft
INS Lat [deg] ins_lat_deg
INS Lon [deg] ins_lon_deg
Air Data Pres Alt [ft] air_data_pres_alt_ft
AIN0 Volt ain0_volt
AIN0 Val ain0_val
AIN1 Volt ain1_volt
AIN1 Val ain1_val
AIN2 Volt ain2_volt
AIN2 Val ain2_val
AIN3 Volt ain3_volt
AIN3 Val ain3_val