[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f7dGUhVGAkaTFbcR5Zs-qc8UAwwszgn2QFujILmqCWs0":3,"$f__g4JYrlHmOg0i4Teaq8Qm143TKrTIWccjYptQjiklk":17,"shop-vat-rates":60},{"article":4},{"id":5,"slug":6,"title":7,"summary":8,"visibility":9,"isPublished":10,"categoryId":11,"categorySlug":12,"categoryName":13,"updatedAt":14,"bodyMd":15,"legacy":16,"createdAt":14},"e8d7615e-a71c-4599-b4fa-8055d06a5886","connecting-a-radio-to-an-lx-instrument","Connecting a radio to Era, LX 10K, Colibri X and NAVIA","What it means for a navigation display to control a radio, which radios are documented on which platform, wiring and menu setup, the audio and push-to-talk job that is separate from the data link, and what is documented about transponders.","public",true,"92b87517-c814-4237-b180-19df9cb80b16","connectivity","Connectivity","2026-09-10T11:36:59.820Z","A radio wired to your navigation instrument stops being a separate box you reach across the cockpit for. The instrument can read what the radio is tuned to, set the standby frequency, swap the two over, and — the part everyone actually wants — drop the frequency of the airfield you have just selected on the navigation page straight into standby, without you reading digits off a plate at 500 feet.\n\nThis article covers what that integration does and does not do, how it is wired and configured on the **Era**, **LX 10K** and **Colibri X**, and how it differs on **NAVIA**, where a radio is one of several declared devices rather than a special case. It also deals honestly with transponders, where the documentation stops short.\n\n## What \"the instrument controls the radio\" means\n\nThe link is a serial one, and the instrument speaks a documented set of commands to the radio. Depending on the model, it can read and write:\n\n- **Active frequency** and **standby frequency**\n- **Volume**, **squelch** and **VOX** level\n- **Switch** — swap active and standby\n- **Dual** — dual watch on or off\n- **Frequency spacing** — 25 kHz or 8.33 kHz\n\nThe instrument also reports back: whenever a radio parameter changes, whether you changed it on the instrument or on the radio's own knob, the instrument emits the new state. A connected PDA or tablet therefore knows the tuned frequency without asking.\n\nThis is also why the navigation page can hand an airfield frequency to the radio. The setting is `Send APT freq.` under `Setup › NMEA`: with it on, navigating to an airport puts that airport's frequency into the radio's standby.\n\n## Supported radios on the LX heads\n\n| Radio | Active \u002F standby | Volume | Squelch | VOX | Switch | Dual |\n|---|---|---|---|---|---|---|\n| KRT2 | Yes | Yes | Yes | Yes | Yes | Yes |\n| ATR833 | Yes | Yes | Yes | — | Yes | Yes |\n| Becker | Yes | — | — | — | Yes | — |\n| Trig | Yes | — | — | — | Yes | — |\n| AIR avionics (ACD) | Yes | — | — | — | Yes | — |\n\nTwo things to read out of that table. First, the **KRT2 is the fullest integration** — everything the protocol defines except frequency spacing, it does. Second, if all you need is \"put the tower frequency in standby and let me swap to it\", every radio on the list will do that.\n\n**Becker** radios need a special radio bridge for communication with the Era and LX 10K. Frequency spacing is defined in the protocol but is not listed against any of these radios — set spacing on the radio itself.\n\n## Wiring it: the user port\n\nThe radio connects to the instrument's **user port**, using RS232. That port is bidirectional NMEA, the same one a wired Oudie uses — which is why you cannot have both on it at once.\n\nThe physical wiring, connector by connector, belongs to the installation manual for your instrument and the manual for your radio. Get the cable made up properly rather than improvised: this is a connector that vibration works on, and a radio that drops out only in turbulence is a miserable thing to diagnose in the air. There are ready-made options — the [vario to KRT2 radio cable](\u002Fshop\u002Fvario-to-krt2-radio-cable), the [KBS1 cable set](\u002Fshop\u002Fkbs1-cable-set) and the [KRT2 plug adapter](\u002Fshop\u002Fplug-adapter-krt2).\n\n## Setting it up in the menu\n\n1. Go to `Setup › NMEA › Radio` and select **your** radio from the list. The wrong model on a correct cable produces silence, not an error.\n2. Tick `Send APT freq.` if you want the instrument to push the selected airport's frequency to the radio.\n3. Check the user port baud rate while you are in that menu. The default is `38400`.\n\nThere is one consequence worth knowing before you turn it on: with `Radio` set to `On`, **all other outputs on the user port are disabled**. They are still present over Bluetooth. So an installation with a radio on the cable and a PDA on Bluetooth works; a radio and a PDA both on the cable does not.\n\n## NAVIA: a radio is a declared device\n\nNAVIA Core Pro has no dedicated radio pins. It has five software-assigned RS232 ports, and you tell the system what is on which one under `Airplane Settings › Devices`. The recommended standard installation puts radio data on **RS232 3**, and takes radio power from **POWER_OUT1** so the system can switch the radio off in flight if it must. Power can equally come from a Vertical Power VP-X system or from the avionics bus through its own breaker.\n\nDocumented integrations, with wiring tables in the installation manual for each:\n\n- **TQ [KRT2](\u002Fshop\u002Fkrt2)** — full data control and centralised audio. Also available as the remote-controlled [KRT2 RC](\u002Fshop\u002Fkrt2-rc).\n- **Air Avionics [Air Control Display](\u002Fshop\u002Fair-control-display)** — a control head rather than a radio. NAVIA sends commands to the ACD, which routes them to whichever COM or transponder hardware sits behind it. It can also carry a built-in certified altimeter.\n- **Trig TY91, TY92, TY96 and TY97** — same quick-release D-Sub style as the NAVIA family, so the physical work is identical to the rest of the installation. The radio's Power ON pin must be grounded for it to come up with the system.\n- **Becker GT6201, AR6201 and AR62xx** — these use **RS422** natively. An external RS232-to-RS422 converter is mandatory. Do not skip it and hope.\n- **Funke ATR833 and ATR833S** — identical pinout for this purpose.\n\nBeyond frequency management, NAVIA's offline voice assistant will tune the radio hands-free. An [AIR COM aircraft radio](\u002Fshop\u002Fair-com-aircraft-radio) is driven through the Air Control Display — the ACD is the documented integration, not the radio itself.\n\n## Audio, microphone and PTT are a separate job\n\nDo not treat the data cable as the whole installation. The serial link carries control; audio, microphone and push-to-talk are wired separately, and the installation manual's audio section governs them. Three rules the NAVIA documentation is firm about:\n\n- Prefer the radio's **unamplified headset output** over its amplified speaker output. It gives a cleaner line-level signal and avoids over-driving the input.\n- Use **shielded** wire for all audio and microphone lines, and ground the shield **at one end only** — the NAVIA end.\n- Wire microphones to the **standard electret** inputs, not the dynamic ones.\n\n## Power: the load that finds a weak bus\n\n> A transmitting radio is the largest single current draw in most panels, and it appears as a step load rather than a steady one. If your supply run, your connectors or your battery are marginal, the transmit key is what will reveal it — usually as an instrument that reboots exactly when you talk. Measure bus voltage at the last device on the chain, during a transmit, at the end of a flying day.\n\nThat is the honest test, and it is covered properly in the academy article on [power systems](\u002Facademy\u002Fpower-systems).\n\n## Transponders: what is documented, and what is not\n\nThis section is short on purpose.\n\nOn **NAVIA**, a transponder is a declared device like any other: assign it to an RS232 port under `Airplane Settings › Devices`, and power it from a controlled output if you want the system to manage it. The Air Control Display can sit in front of a remote transponder and be driven by NAVIA. We sell the [VT-01 Mode-S transponder](\u002Fshop\u002Fvt-01-mode-s-transponder-class-2) and the [KTX2](\u002Fshop\u002Ftransponder-ktx2); ask us about a NAVIA installation before buying.\n\nOn the **Era, LX 10K and Colibri X**, there is a `Transponder` setting in `Setup › NMEA`. Switching it on drops the FLARM port to 9600 baud and transmits GPS data on that port — a transponder needs a position source, and that is how it gets one. Beyond that setting, **there is no published transponder wiring procedure for these instruments.** We are not going to invent one here. Ask your dealer, or [ask us](\u002Fcontact) with your instrument and transponder model to hand.\n\n## When it does not work\n\n| Symptom | Cause | Fix |\n|---|---|---|\n| Radio ignores the instrument entirely | Wrong model selected in `Setup › NMEA › Radio` | Select the actual radio; a near-match is a non-match |\n| Frequencies work, volume and squelch do not | That radio only supports part of the command set | Check the table above — this is expected, not a fault |\n| Airfield frequency never reaches standby | `Send APT freq.` not ticked | Tick it in `Setup › NMEA` |\n| PDA on the user port went dead when the radio was added | `Radio` on the user port disables the port's other outputs | Move the PDA to Bluetooth |\n| Becker radio silent on NAVIA | RS422, no converter fitted | Fit the RS232-to-RS422 converter |\n| Instrument reboots on transmit | Voltage drop under the transmit load | Measure at the last device during a transmit; fix the supply, not the instrument |\n| Radio does not power up with the system (Trig) | Power ON pin not grounded | Ground it per the installation manual |\n\n## Where to go next\n\n- What the commands look like on the wire: [LX NMEA sentences for developers](\u002Fkb\u002Farticle\u002Flx-nmea-sentences-for-developers).\n- The other thing that hangs off the user port: [connecting XCSoar, Oudie and other PDAs](\u002Fkb\u002Farticle\u002Fconnecting-xcsoar-oudie-and-pdas).\n- Theory: [transponders and ADS-B](\u002Facademy\u002Ftransponder-adsb) and [power systems](\u002Facademy\u002Fpower-systems).\n- Installation manuals for your instrument and radio: the [download centre](\u002Fdownloads).\n- Anything that does not match this article: your dealer first, then [LX navigation](\u002Fcontact).\n",null,{"categories":18,"articles":45,"search":59},[19,25,31,34,39],{"id":20,"slug":21,"name":22,"description":16,"sortOrder":23,"articleCount":24},"42232637-6088-4100-9314-0b4986098818","getting-started","Getting started",20,7,{"id":26,"slug":27,"name":28,"description":16,"sortOrder":29,"articleCount":30},"9d0897b6-42d0-4643-8ceb-e8a02ce4a854","navia","NAVIA",25,10,{"id":11,"slug":12,"name":13,"description":16,"sortOrder":32,"articleCount":33},30,3,{"id":35,"slug":36,"name":37,"description":16,"sortOrder":32,"articleCount":38},"db776f9a-4f67-42bf-94bc-171c93f10cea","service-repairs","Service & repairs",1,{"id":40,"slug":41,"name":42,"description":16,"sortOrder":43,"articleCount":44},"48e22b59-26c1-477f-b136-3d3728b6dc22","device-guides","Device guides",40,12,[46,52,53],{"id":47,"slug":48,"title":49,"summary":50,"visibility":9,"isPublished":10,"categoryId":11,"categorySlug":12,"categoryName":13,"updatedAt":51},"9984420d-34f3-4de1-80a2-94f35ddf5f2d","connecting-xcsoar-oudie-and-pdas","Connecting XCSoar, Oudie and other PDAs to Era, LX 10K and iris","Sending flights over WiFi, putting the instrument into Bluetooth server mode, pairing an Oudie or an Android phone, the NMEA sentences and baud rate to set, the wired user port, and configuring iris over CAN2WiFi.","2026-09-10T11:36:59.813Z",{"id":5,"slug":6,"title":7,"summary":8,"visibility":9,"isPublished":10,"categoryId":11,"categorySlug":12,"categoryName":13,"updatedAt":14},{"id":54,"slug":55,"title":56,"summary":57,"visibility":9,"isPublished":10,"categoryId":11,"categorySlug":12,"categoryName":13,"updatedAt":58},"c9717955-eee3-4027-b634-f1fd59364d8f","lx-nmea-sentences-for-developers","LX NMEA sentences: a reference for developers and integrators","Where the protocol runs, sentence anatomy and the checksum rule, the broadcast and request-response families with their command groups, a worked exchange, task declaration, and the NAVIA open platform for anyone building their own.","2026-09-10T11:36:59.828Z",false,{"AT":23,"BE":61,"BG":23,"CY":62,"CZ":61,"DE":62,"DK":29,"EE":63,"ES":61,"FI":64,"FR":23,"GR":64,"HR":29,"HU":65,"IE":66,"IT":63,"LT":61,"LU":67,"LV":61,"MT":68,"NL":61,"PL":66,"PT":66,"RO":62,"SE":29,"SI":63,"SK":23},21,19,22,24,27,23,17,18]