Two different questions hide inside "does this work with that". The first is whether the two boxes can be wired together at all. The second is whether anything useful crosses the wire once they are. This article answers both, family by family, in tables, so you can check a panel before you buy for it rather than after.
There are two backbones. The LX panel instruments — Era, LX 10K, the iris line and their accessories — share a CAN bus on an RJ45 connector that carries data and power; the wiring rules are in LX CAN bus wiring rules. NAVIA is a different arrangement: Displays, Hub and EMU sit on one Power-over-Ethernet backbone, one cable per device; Sense and Traffic wire to the Core's serial ports; the Grip plugs into a Display. Everything outside the two families — radios, traffic receivers, tablets, cameras — arrives over a serial port, over Bluetooth or over the network.
One data model, and priority
In a NAVIA system every measurement — altitude, airspeed, position, attitude, engine data, traffic — flows into a single live data model inside the Core, and every screen shows values from that model. Each source writes with a priority, and the Core's own sensors sit in the middle of the range.
| Source priority | Effect |
|---|---|
| Higher than the built-in sensors | The external device takes over on every screen — connect a dedicated variometer or a high-grade AHRS and its data simply becomes the data |
| Lower than the built-in sensors | The external device fills gaps only, where the built-in sensors are silent |
You meet the same concept again when assigning serial devices under Airplane Settings > Devices. It is worth understanding before you add a second sensor, because "the new box changed nothing" and "the new box changed everything" are both explained by this one setting.
A glider panel
| What you have | What it connects to | Over |
|---|---|---|
| Era | AHRS module, LX Joy, flaps sensor | CAN bus — one cable per accessory, data and power |
| LX 10K | Its vario indicator (analog 57, digital 57 or digital 80) | CAN bus; main unit and indicator are always supplied as a pair |
| iris instruments | Each other and the rest of the panel | CAN bus; Gen 1 is configured over the CAN2WiFi adapter, Gen 2 has WiFi in the instrument |
| Era, LX 10K | A FLARM device | The dedicated FLARM port |
| Era, LX 10K | A radio, an Oudie or another PNA | The user port, RS232 |
| Era, LX 10K | A phone, tablet or PDA | Bluetooth |
| Colibri X | Nothing on the panel bus is required | It is a standalone recorder and works on its own |
A powered panel
The NAVIA Core Pro uses software-assigned RS232 ports rather than dedicated "radio" or "traffic" pins: wire the device to any free port and assign the protocol under Airplane Settings > Devices.
| What you are adding | How it connects | What you get |
|---|---|---|
| Navia Sense | 5 V and RS232 from the Core | AHRS, inertial and air data; connect a second Sense for automatic redundancy |
| Navia Traffic | Mounts in the Navia Rack directly on top of the Core; four wires — power, ground, two RS232 data lines | Traffic on every screen and spatial audio warnings |
| Vertical Power VP-X | One RS232 link; the Core takes its own main power from the VP-X primary EFIS output | The whole electrical system on the touchscreen: live consumption, circuit faults, flap and trim position, and voice commands that switch real circuits |
| iLevil AP or AW | RS232 from one of the iLevil's AUX ports | AHRS and ADS-B traffic; usable as the only sensor or merged with Sense, Navia Traffic and FLARM receivers |
| A radio | Any RS232 port, protocol assigned in software | Active and standby frequencies from the touchscreen, and hands-free tuning through the offline voice assistant |
| A PoE IP camera | A spare port on the Navia Hub, which supplies power and carries the video back to the Core | A camera page on an MFD, or an inset on the PFD |
| A WiFi action camera | The Core's own WiFi access point | The same, plus start and stop recording from the touchscreen |
Camera support is documented but not available in the present state of the software, and the list of supported devices is not published yet. Treat it as a planned capability, not a reason to buy a camera today.
Traffic and collision avoidance
The Core accepts any receiver that outputs traffic in FLARM-format NMEA or standard GDL90, which is what makes this list open-ended rather than a compatibility matrix.
| Device | Interface | Worth knowing |
|---|---|---|
| Navia Traffic | RS232, in the Navia Rack on top of the Core | The tightest integration; designed as part of the suite |
| PowerFlarm Core, Flarm Fusion | The 9-pin DE-9 connector for power, data and audio | Preferred over the RJ ports, because it leaves the RJ45 and RJ11 free for a dedicated FLARM display, a standalone variometer or a second traffic monitor |
| Generic FLARM devices — Flarm Eagle, RedBox, MiniBox, classic FLARM, FlarmMouse, PowerMouse | Four pins off the IGC FLARM RJ45 or RJ11: power, ground, TX, RX | The RJ11 pin order matches the middle six pins of the RJ45 |
| Air Avionics AT-1 | RS232 on the 26-pin HD D-Sub | — |
| A FLARM device on an Era or LX 10K | The instrument's FLARM port | Traffic shows on the instrument, and the PFLAx sentences are passed on to a connected tablet or PDA |
Radios and transponders
Data connection means frequency management from the screen, and on NAVIA it also means the voice assistant can tune for you. Audio, microphone and PTT are wired separately from the data lines — that is an installation subject, not a compatibility one, and the installation manual governs it.
| Radio | Works with | Worth knowing |
|---|---|---|
| TQ KRT2 | NAVIA Core Pro; Era, LX 10K, Colibri X | The KRT2 table in the NAVIA manual uses the amplified speaker output; switch to the unamplified headset output if you get ground loops or over-drive |
| Air Avionics Air Control Display | NAVIA Core Pro; Era, LX 10K, Colibri X | The Core commands the ACD, which routes to whichever COM or transponder hardware sits behind it; the ACD can also carry a built-in certified altimeter |
| Trig TY91, TY92, TY96, TY97 | NAVIA Core Pro (these models); Era, LX 10K, Colibri X (the manual names Trig only — confirm the model with us) | Same quick-release D-Sub style as the NAVIA family; the Trig Power ON pin must be grounded so the radio comes up with the Core |
| Becker GT6201, AR6201, AR62xx | NAVIA Core Pro (these models); Era, LX 10K, Colibri X (the manual names Becker only) | The 6200 series speaks RS422, so an external RS232-to-RS422 converter is mandatory; on an LX instrument a radio bridge is required |
| Funke ATR833, ATR833S | NAVIA Core Pro (both); Era, LX 10K, Colibri X (ATR833) | Wire to the standard electret microphone inputs, never the dynamic ones |
On an Era or LX 10K the radio hangs off the user port over RS232, and the supported families are KRT2, ATR833, Becker, Trig and Air Avionics. Select the radio under Setup > NMEA > Radio, tick Send APT freq., and airport frequencies arrive as the standby frequency. Step by step: connecting a radio to an LX instrument.
The Becker and the Navia Sense are the two traps in this section. The Becker needs a converter, not a cable, and buying the radio without it means a panel that will not talk. The Sense runs on 5 V logic power and must come from the Core's regulated 5 V output — connecting it to a 12 V or 24 V VP-X circuit destroys it immediately and permanently.
Tablets, phones and PDAs
| Device | Link | What crosses it |
|---|---|---|
| Android phone running XCSoar | Bluetooth | GPGGA, GPRMC, GPRMB, LXWPx, LXDT, LXBC and PFLAx; a healthy link reports Connected; Baro; Airspeed; Vario; FLARM |
| Oudie or another PNA/PDA | Bluetooth | The same sentences, plus a task declaration sent into the instrument and control of MacCready, ballast and bugs |
| Oudie on a cable | User port, RS232, with a Power & Data cable | The same data, and the instrument charges the Oudie for as long as it has external power |
| Two Oudies at once | One on Bluetooth, one on the cable | The supported way to run a pair |
| A tablet running the iLevil app | The iLevil's own link | The iLevil accepts concurrent connections, so the app keeps working alongside a NAVIA Core |
Full procedure, including baud rate and the tick boxes: connecting XCSoar, Oudie and PDAs.
Recorders and claims
| What you need to do | Where it happens |
|---|---|
| Record an IGC flight | Era, LX 10K and Colibri X each contain an approved recorder; on NAVIA it is the Sense Gliding variants that carry one |
| Declare a task | On the instrument, or sent in over Bluetooth from an Oudie or PDA |
| Get the flight out | Send to e-mail from the logbook one flight at a time, or copy flights to the microSD card |
| Send a flight by e-mail | Over WiFi: needs an address stored, a WiFi client connection, a flight in the logbook, and the instrument out of flight mode |
Accessories
| Accessory | Belongs to | Over |
|---|---|---|
| AHRS module, LX Joy, flaps sensor | Era | CAN bus |
| Vario indicator | LX 10K | CAN bus, supplied with the main unit |
| CAN2WiFi adapter | iris Gen 1 | CAN bus |
| Power & Data cable | Era, LX 10K | User port |
| Navia Hub, EMU | NAVIA | PoE, one cable each |
| Navia Grip | NAVIA | Plugs into a Display through the 9-pin Grip adapter |
| Navia UPS | NAVIA | See its installation manual |
What does not interoperate
- Equipment from other manufacturers beyond the integrations listed above is not covered by our firmware, our licences or our warranty. A device that speaks NMEA is not thereby a supported device.
- A CAN port is not an Ethernet port, and a NAVIA PoE port is not a CAN port. They take the same plug and belong to different worlds. Never patch a CAN port into a switch, a router or a PoE injector.
- CAN accessories do not become NAVIA devices. An AHRS module or an LX Joy is part of the instrument family; it does not join the Ethernet backbone, and NAVIA components do not hang off a CAN chain. The one documented bridge runs the other way: an Era or LX 10K can be declared as a serial device under
Airplane Settings > Devicesand act as a sensor and vario for the NAVIA system, ranked by priority like any other source. - A documented protocol is not a tested device. Where a model is not named in a table above, ask us before you buy it — contact us with the aircraft, the panel and the part number, and you get a definite answer rather than an optimistic one.
Where to go next
- Deciding between the families in the first place: choosing between Era, LX 10K and NAVIA
- Tablets and PDAs, step by step: connecting XCSoar, Oudie and PDAs
- Radios, step by step: connecting a radio to an LX instrument
- The theory under the wiring: the CAN bus and panel planning in the LX Academy
- Anything a table here does not settle: ask us