Troubleshooting: No EFIS Data¶

OnSpeed is configured for an EFIS but isn't receiving data.

Check 1: Is the EFIS Type Correct?¶

The most common cause. Open the OnSpeed web interface and verify the EFIS Type matches your hardware:

If the EFIS type is wrong, OnSpeed will try to parse the serial data in the wrong format and get nothing useful.

All EFIS types require 115200 baud on the OnSpeed side. The EFIS must also be configured to transmit at 115200.

Most common mistake: Dynon SkyView defaults to 9600 baud. You must change it to 115200 in the Dynon serial port setup menu.

Serial connections are crossed: the EFIS transmit (TX) pin connects to the OnSpeed receive (RX) pin.

Make sure your EFIS is configured to output data on the serial port you wired to:

Dynon SkyView: Must enable ADAHRS + EMS output (not just ADAHRS alone) on the specific serial port
Garmin G5: Must enable serial output in the G5 configuration
Garmin G3X: Must configure a serial port for data output
MGL: Must enable iLink output

Connect to the USB serial console and type:

SENSORS

Look at the EFIS data fields:

If all EFIS fields are zero, data isn't arriving
If efisAge or vnDataAge is very large (> 5000 ms), data was received at some point but has gone stale
If fields have non-zero values and small age, EFIS is working

Verify that the SERIALEFISDATA configuration option is set to true. If it's false, OnSpeed won't even try to read EFIS serial data.

Verify the wire has continuity from EFIS TX to OnSpeed RX
Check for broken wires, cold solder joints, or loose connectors
Verify ground is connected between the two devices
Check that the RS-232 level shifter (ADM3202) on the OnSpeed board has power and is functioning

If all wiring and configuration looks correct:

Try a different serial port on the EFIS (if available)
Use a USB-to-serial adapter on a laptop to verify the EFIS is actually outputting data
Check the EFIS firmware version — some older firmware versions may have serial output bugs
Try power-cycling both the EFIS and OnSpeed