[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fiTP_V3QY8nTLaUIXlNzEQft0ai6aQ0I3fr0S73vcq4o":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},"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.","public",true,"92b87517-c814-4237-b180-19df9cb80b16","connectivity","Connectivity","2026-09-10T11:36:59.813Z","An Era, an LX 10K or a Colibri X will happily feed a second device — an Oudie, a phone running XCSoar, a tablet — with the numbers it already has: indicated airspeed, vario, wind, altitude, GPS position and FLARM traffic. The instrument does the sensors; the second device does the moving map. This article covers the three links that carry that traffic — WiFi, Bluetooth and the wired user port — and the adapter that gets you into an iris.\n\nThe procedure is identical on the **Era**, the **LX 10K** and the **Colibri X**. Where this article says \"the instrument\", read whichever of the three is in your panel: the menus sit in the same places and the settings have the same names. iris and NAVIA work differently and get their own sections at the end.\n\n## What each link is actually for\n\n| Link | What it carries | Direction |\n|---|---|---|\n| WiFi | Finished `.igc` flights, sent to e-mail | Out only |\n| Bluetooth | Live NMEA data, task declarations, MacCready\u002Fballast\u002Fbugs | Both ways |\n| User port (RS232) | The same NMEA data, plus charging power for the PNA | Both ways |\n\nThe most common misunderstanding lives in that first row. **WiFi is not the data link.** On these instruments the WiFi connection exists to send flights to an e-mail address, and at present it does nothing else. If you want live data on a PDA, you want Bluetooth or the cable.\n\n## Sending a flight over WiFi\n\nFour things must be true before a flight will go anywhere: an e-mail address is stored, a WiFi connection is established, a flight exists in the logbook, and you are not in flight mode.\n\n1. **Add the address.** `Setup › Network › Mail › Add mail`, then type it on the alphanumeric keyboard. Caps are ignored here. Several addresses can be stored at once — mark the ones you want active, and the flight goes to all of them.\n2. **Join the network.** `Setup › Network › Wireless mode`, choose `WiFi Client`. Go back out, open `Wireless setup`, and you will see networks listed under `Available`, with anything you are joined to under `Connected`.\n3. **Enter the password.** Select the network, type the password — this one **is** case-sensitive — and choose `Connect`. The name shifts from `Available` to `Connected` when it works.\n4. **Send it.** `Logbook`, select the flight, scroll down the `Flight info` page and choose `Send to email`. You get a `Preparing data` box, then an hourglass, then a confirmation. Then check your inbox.\n\nFor what makes that file worth having, see the academy article on [IGC logs](\u002Facademy\u002Figc-logs).\n\n## Bluetooth: putting the instrument in server mode\n\nEverything on the Bluetooth side starts the same way, whichever device you are pairing.\n\nGo to `Setup › Network › Wireless mode` and choose `Bluetooth server`. Back out of that menu and open `Wireless setup`: it shows the instrument's Bluetooth name and its password. You need both.\n\n## Pairing an Oudie or other PNA\u002FPDA\n\n1. On the Oudie, go to `Menu › Settings › Input › Bluetooth…` and press `Lookup`.\n2. Your instrument appears in the list under a name like `LX LX 10k 34xxx`. Select it and press pair.\n3. When prompted for a password, type `1234`.\n4. Set the port up exactly as follows.\n\n### Oudie port settings\n\n| Setting | Value |\n|---|---|\n| Port | `COM5:` (Bluetooth) |\n| Speed | `38400` |\n| Parity | None |\n| Bits | 8 |\n| Stop bit | 1 |\n| Set DTR | Checked |\n| Set RTS | Checked |\n\nThen, on the Oudie, `Menu › Settings › Hardware › Device` and select `LX navigation` (the manual marks this driver name as pending; if your version lists it differently, choose the LX driver offered). If you open the Terminal you should see NMEA sentences scrolling past. That is the honest test — a \"connected\" indicator is not.\n\n## Pairing an Android phone for XCSoar\n\nSame shape, fewer steps. With the instrument in `Bluetooth server` mode, turn Bluetooth on, find the instrument in the phone's `Available devices` list and connect. Then in XCSoar, `Config › Devices › B: › Edit`: set the port to the one carrying your instrument's Bluetooth name, set the driver to `LX navigation`, and leave `Passthrough device` off.\n\nWhen it works, XCSoar's connection state stops saying `Not connected` and starts listing what it has found: `Connected; Baro; Airspeed; Vario; FLARM`.\n\n## The NMEA sentences to switch on\n\nThis step is done on the instrument, and it is the one people skip. Go to `Setup › NMEA`, set the NMEA baud rate to `38400`, and tick:\n\n`GPGGA` · `GPRMC` · `GPRMB` · `LXWPx` · `LXDT` · `LXBC` · `PFLAx`\n\nBetween them these carry the GPS fix, recommended navigation data, flight and device parameters, broadcast data such as AHRS, and the FLARM traffic sentences. Unless something specifically tells you otherwise, this is the set you want.\n\n## What the other device can send back\n\nThe link is not one-way. Over Bluetooth a third-party device can push a **task declaration** into the instrument, and can change **MacCready, ballast and bugs** while you fly. That is why a declaration typed into the PDA on the grid lands in the recorder that actually matters, and why changing MC on the map changes the speed-to-fly ring on the panel.\n\n## The user port: a wired Oudie\n\nThe user port is a bidirectional RS232 link carrying the same NMEA traffic. The reason to use it is power: as long as the instrument has an external supply, the cable charges the Oudie. It is also how you run **two** PNAs — one on Bluetooth, one on the cable.\n\nYou need a [power and data cable](\u002Fshop\u002Flx-eos-pna-power-data); for devices that take a micro USB feed there is the [micro USB power and data interface](\u002Fshop\u002Fmicro-usb-power-and-data-interface). Set the Oudie's input to `COM4`, serial cable, and tick the same NMEA sentences on the instrument as above.\n\n## iris: configuring over CAN2WiFi\n\nGen 1 iris instruments have no display menus of their own worth speaking of — they are configured over the [CAN2WiFi adapter](\u002Fshop\u002Firis-can2wifi).\n\n1. Use the supplied CAN bus cable to connect the **CAN port on the iris device to the CAN port on the CAN2WiFi**.\n2. Power up the iris. The CAN2WiFi takes its power from that same cable — there is no second supply to find.\n3. The adapter comes up as an access point with SSID `LX CAN2WIFI XXXXXX`, where `XXXXXX` is its serial number, and key `lxnavigation`.\n4. Join it from any phone, tablet or laptop. Your browser is normally redirected to the web interface; if it is not, go to `192.168.4.1` by hand.\n\n**iris Gen 2 has WiFi in the instrument itself** and needs no adapter. Documentation for the adapter lives on its [download page](\u002Fdownloads\u002Fdevice\u002Firis-can2wifi).\n\n## NAVIA: a phone is a screen, not a client\n\nNAVIA does not need any of this. A phone or tablet joins the aircraft's own network and becomes an additional screen with its own profile — see [NAVIA accounts, roles, profiles and screens](\u002Fkb\u002Farticle\u002Fnavia-accounts-roles-profiles-and-screens).\n\n## When nothing arrives\n\n| Symptom | Usual cause | Fix |\n|---|---|---|\n| Terminal empty, no sentences at all | Baud mismatch — the PNA is at a different speed from `Setup › NMEA` | Put both at `38400` and try again |\n| Paired, but the app shows no data | Nothing ticked in `Setup › NMEA` | Tick `GPGGA`, `GPRMC`, `GPRMB`, `LXWPx`, `LXDT`, `LXBC`, `PFLAx` |\n| Data arrives but the app misreads it | Wrong driver selected | `LX navigation` on the Oudie and in XCSoar, not a generic NMEA driver |\n| Second device will not pair | The documented way to run two devices is one on Bluetooth and one on the cable | Put the second device on the user port cable |\n| `Send to email` does not send | Still in flight mode, or no flight in the logbook | Land, end the flight, then send |\n| Flight sent, nothing received | Usual cause: address stored but not marked active | Check the address is ticked in `Setup › Network › Mail` |\n\n## Where to go next\n\n- Getting the instrument itself set up: [Era setup and first flight](\u002Fkb\u002Farticle\u002Fera-setup-and-first-flight).\n- Talking to the instrument in code rather than through an app: [LX NMEA sentences for developers](\u002Fkb\u002Farticle\u002Flx-nmea-sentences-for-developers).\n- Manuals and firmware for your device: the [download centre](\u002Fdownloads).\n- Anything that behaves differently from 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,47,53],{"id":5,"slug":6,"title":7,"summary":8,"visibility":9,"isPublished":10,"categoryId":11,"categorySlug":12,"categoryName":13,"updatedAt":14},{"id":48,"slug":49,"title":50,"summary":51,"visibility":9,"isPublished":10,"categoryId":11,"categorySlug":12,"categoryName":13,"updatedAt":52},"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.","2026-09-10T11:36:59.820Z",{"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]