Recording
OnFlight Hub records flight data to a removable microSD card formatted as FAT32 while operating. A Wi-Fi connection is not required for recording.
Insert the microSD card before turning on OnFlight Hub. Before your flight, check that the Status light is solid, indicating that the inertial navigation system (INS) is initialized and healthy and a microSD card is present.
OnFlight Hub operates and logs data at 50 Hz. Slower recording rates can be selected on the Configuration webpage.
Log formats
Select the output format on the Configuration webpage to match your analysis application.
| Format | Example filename | Use |
|---|---|---|
| OnFlight | data0.onflight |
Upload directly to FlySto or convert with the OnFlight Data Converter. |
| ACROWRX | data0.acrowrx |
Upload to ACROWRX. Requires an ACROWRX key and ACROWRX output selected in the configuration. |
The number in each filename increments to avoid overwriting files already on the card.
If you plan to use ACROWRX for data analysis, follow their instructions for configuring OnFlight Hub.
Retrieve your flight logs
- Turn off OnFlight Hub before removing the microSD card.
- Remove the card and connect it to your computer using a suitable card reader.
- Copy the log files to your computer.
- Open or upload the files using your chosen analysis application.
Keep the original log files. They allow you to convert the data again later and are helpful when investigating startup issues or suspected data inaccuracies.
With firmware 10 and later, OnFlight Hub will set the log file creation and last modified date and time based off of the UTC time available from the GNSS receiver; this requires a valid GNSS fix. Earlier firmware versions or in cases where a valid GNSS fix is not received, a default date and time is used. A configurable UTC offset adjusts can adjust the UTC date and time to your local date and time. See File timestamps to configure the offset.
Review a flight
After copying your logs to your computer, follow the steps below for your chosen application. FlySto and CloudAhoy both use logs recorded in OnFlight format; CloudAhoy requires a conversion step before upload.
| Application | How to use your log files |
|---|---|
| ACROWRX | Record in ACROWRX format and upload the .acrowrx file to ACROWRX. |
| FlySto | Upload the .onflight file directly to FlySto. |
| CloudAhoy | Use the OnFlight Data Converter to convert the .onflight file to CloudAhoy format, then upload the resulting CloudAhoy CSV file to CloudAhoy. |
| Your own analysis tools | Use the OnFlight Data Converter to convert the .onflight file to CSV or MATLAB format, then open the converted data in your tools. Or use the Developer’s Manual to write your own tools against the .onflight binary format. |
OnFlight Data Converter
The OnFlight Data Converter converts .onflight logs to CSV, MATLAB, and CloudAhoy formats.
Download the OnFlight Data Converter for Windows or macOS.
ACROWRX files use a separate format intended for ACROWRX.
Moving map and attitude display
OnFlight Hub streams position and attitude data over Wi-Fi using GDL 90. Compatible applications, including ForeFlight and Garmin Pilot, can use this data to show your position on a moving map and provide a supplemental attitude display. Available display features depend on the application and subscription.
- Turn on OnFlight Hub and allow initialization to complete.
- Connect your phone or tablet to OnFlight Hub’s Wi-Fi network.
- Open your compatible flight application.
- Remain connected to OnFlight Hub’s Wi-Fi network while using these displays.
OnFlight Hub is intended for supplemental information. Do not rely on it as a primary flight instrument or navigation source.
The default GDL 90 port is 4000. It can be changed on the Configuration webpage.
OnFlight Hub continues recording to the microSD card while streaming. A Wi-Fi connection is not required for recording.
Custom live-data applications
A separate UDP interface provides a more complete set of live data at 50 Hz for custom applications.
See the Developer’s Manual for connection details, ports, packet formats, units, and status flags.