[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fsDnROKyrMytSMHtxOX6gtCcWbO7Z-C3WPbHpfCj_jZE":3,"$fRLpWT0a09BaP0_tYnrDDSLsNT5lLUcMU-reY_R96hL8":17,"shop-vat-rates":113},{"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},"6812afc1-2a07-45d4-a3ea-9fa2e09b4bdb","colibri-x-declaration-logging-and-download","Colibri X: task declaration, logging and getting the flight out","Declaring a task before flight, the five ways a task reaches the recorder, what the declaration carries besides turnpoints, the logger settings that matter, and the three routes for getting the IGC file off the instrument.","public",true,"48e22b59-26c1-477f-b136-3d3728b6dc22","device-guides","Device guides","2026-09-10T11:36:59.663Z","The Colibri X is a flight recorder with a full navigation instrument wrapped around it, and the two halves follow different rules. The half you fly with is forgiving: change your mind about the task at any point and the instrument keeps up. The half that writes the `.igc` file is not forgiving at all, because that file has to convince somebody who was not there.\n\nThis article covers declaring a task before flight, what the declaration carries besides turnpoints, the logger settings that shape the file, and the routes for getting a finished flight out of the instrument.\n\n## What the recorder is for\n\nThe Colibri X records to internal memory in the IGC format, continuously, from the moment it decides you are flying. That file is the evidence for a badge, a record or a competition claim, and on most days it is the only artefact a scorer will ever look at.\n\nTwo things follow. First, the file is only as good as what you told the instrument **before** takeoff — the recorder cannot invent your name, your glider or your intended task after the event. Second, the original file is the one that counts: validate the G-record before submitting, and keep the original somewhere you will still have it next season. The theory behind all of this is in the academy article on [IGC logs](\u002Facademy\u002Figc-logs).\n\n## Declare before you fly, not after\n\nA **declaration** is the statement of intent written into the header of the IGC file: who is flying, in what, and where they intend to go. It must be in the instrument before takeoff.\n\nA task loaded after landing is not a claim. It is a route drawn over a flight that has already happened, and it will be rejected. This is the commonest way a good flight becomes an unclaimable flight, and it costs nothing to avoid — set the task on the ground, with time to read it back.\n\n## The five ways a task arrives\n\nA task can be built from turnpoints, airports, or a mixture of both, and it can reach the Colibri X by five routes:\n\n1. **Uploaded from a Zeus**, where the Colibri X sits alongside it in the panel.\n2. **Sent from a third-party device over Bluetooth** as a declaration — a phone running XCSoar, an Oudie or a similar PNA.\n3. **Downloaded from the web.**\n4. **Created on the device**, on the `Edit task` sub-page.\n5. **Loaded from a `.cup` file** through `Load task`.\n\nOn a two-seat installation the front-seat device can send the task back to the second seat. Task files must be `.cup`; nothing else is read.\n\n> The Colibri X forwards a task declaration onward to external devices — a MOP sensor, a FLARM unit — when it receives one over the user port, when it receives one over Bluetooth, when a task is loaded from a `.cup` file, and whenever you **leave** the task-edit page. Edit a task and stay on that page, and the downstream devices have not yet been told.\n\n## What goes into the declaration besides turnpoints\n\nTurnpoints are the part pilots remember. The rest of the header is set once and then quietly stays wrong for a season.\n\n| Field | Where it lives | Why it matters |\n|---|---|---|\n| Pilot name and surname | `Setup > Pilot` | Written into the IGC declaration. Wrong here, wrong on the claim. |\n| Copilot name and surname | `Setup > Pilot` | Same, and easy to leave behind from the last two-seat flight. |\n| Registration number | `Setup > Glider` | Saved to the IGC declaration. |\n| Competition ID | `Setup > Glider` | Saved to the IGC declaration. |\n| Class | `Setup > Glider` | Saved to the IGC declaration. |\n\nEach pilot profile is also the user profile that all your other settings are saved into, so creating a profile per pilot is worth the two minutes rather than editing one shared entry.\n\n## Logger settings\n\nThe `Logger` sub-menu holds everything that shapes the file itself:\n\n- **Interval** — how often a position fix is written in normal flight.\n- **Event interval** — the faster rate used while the event function is active.\n- **Event fixes** — how long the event interval stays in force, counted in fixes.\n- **Start speed** — the indicated airspeed at which logging begins.\n\nThe **event function** is an IGC-mandated feature. Pressing it switches the logging rate to the event interval for a set period and writes a distinct event line into the `.igc`. It exists because memory used to be scarce and normal intervals were coarse, so a sector had to be caught at higher resolution on demand. Today it is more often used to mark intent — some competition start procedures ask the pilot to mark the moment of crossing — and it remains genuinely useful any time you want a timestamp you can find again.\n\nTrigger it either with an external button wired to the inputs interface, or from the info page with the lower push-rotary knob. Either way a notification box confirms it.\n\n## Getting the flight out\n\n### To a microSD card\n\nThe default route, and the one that works with no infrastructure. Open the `Logbook` page, scroll to the flight, press in to open the flight info, and choose the transfer to microSD card. The list is long on a well-used instrument: turning the upper knob jumps ten flights at a time, and pressing it in while turning jumps a hundred.\n\n### By e-mail over WiFi\n\nFour conditions must all be true before this works:\n\n1. An e-mail address is set up, under `Setup > Network > Mail > Add mail`, and marked active.\n2. A WiFi connection is established — set `Wireless mode` to `WiFi Client`, then pick the network in `Wireless setup` and enter the password. Passwords are case-sensitive; the address is not.\n3. The flight exists in the logbook.\n4. You are not in flight mode.\n\nThen open the flight from the `Logbook` page and choose `Send to email`. The instrument prepares the data, uploads it, and tells you when it is done.\n\n### Over Bluetooth\n\nBluetooth is not a download route, and expecting it to be one wastes an evening. It carries live NMEA data out to a phone or PNA, and carries declarations and settings such as MacCready, bugs and ballast back in. The finished `.igc` still leaves by card or by e-mail.\n\n## Housekeeping\n\nInternal memory is generous — 8 GB on earlier units, 16 GB on newer ones — which is exactly why flights accumulate for years. Download them anyway, on a schedule, and keep them somewhere that is not the instrument. Memory being large is not the same as memory being a backup.\n\nUpdates come from LX support: send your contact details, device type, target software version and serial number, and you will be given an update code. Copy the `.lxu` file to the root of the microSD card, then `Setup > Service > Software update`, enter the code, and confirm afterwards in `Setup > Service > Device info` that the version really changed. On a standalone unit the instrument switches off after copying the file — press the lower push-rotary knob to turn it on again so the update continues; the Zeus version restarts by itself.\n\n> Do not cut power during an update. Data corruption can follow; if it does, contact [LX support](\u002Fcontact) immediately to recover the unit. After the main unit finishes, leave the Colibri X on for at least five minutes so it can update the CAN devices behind it.\n\n## When it goes wrong\n\n| Symptom | Cause | Fix |\n|---|---|---|\n| Claim rejected, task looks right on the trace | Task was loaded after landing | Declare before takeoff. Nothing recovers this after the fact. |\n| FLARM or MOP does not have the declaration | You edited the task and never left the edit page | Leave the task-edit page, or reload the task from the `.cup` file. |\n| Task file not listed in `Load task` | Not a `.cup`, or a `.cup` with no task saved in it | `Load task` lists only `.cup` files that contain a task. Save the task into the file, or build it on the device. |\n| `Email not selected` when sending, or `Send to email` unavailable | Still in flight mode, or no active address | Finish the flight, then check `Setup > Network > Mail` for an active entry. |\n| WiFi will not connect | Password typed with the wrong case | Passwords are case-sensitive. Retype, then `Connect`. |\n| Logging starts late | `Start speed` set above your actual liftoff IAS | Lower it to suit the glider and the launch method. |\n| Wrong pilot in the header | Old profile still active | Select your own profile under `Setup > Pilot` before flight; the name written into the declaration is the active profile's. |\n\n## Where to go next\n\n- Firmware and databases for this instrument: the [Colibri X download page](\u002Fdownloads\u002Fdevice\u002Fcolibri-x).\n- What a valid claim actually requires: the academy articles on [IGC logs](\u002Facademy\u002Figc-logs) and [task flying](\u002Facademy\u002Ftask-flying).\n- Product details and accessories: [Colibri X](\u002Fshop\u002Fcolibri-x).\n- Anything that behaves differently from this article: your dealer first, then [LX support](\u002Fcontact).\n",null,{"categories":18,"articles":45,"search":112},[19,25,31,37,42],{"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":32,"slug":33,"name":34,"description":16,"sortOrder":35,"articleCount":36},"92b87517-c814-4237-b180-19df9cb80b16","connectivity","Connectivity",30,3,{"id":38,"slug":39,"name":40,"description":16,"sortOrder":35,"articleCount":41},"db776f9a-4f67-42bf-94bc-171c93f10cea","service-repairs","Service & repairs",1,{"id":11,"slug":12,"name":13,"description":16,"sortOrder":43,"articleCount":44},40,12,[46,52,58,64,70,71,77,83,89,95,101,106],{"id":47,"slug":48,"title":49,"summary":50,"visibility":9,"isPublished":10,"categoryId":11,"categorySlug":12,"categoryName":13,"updatedAt":51},"4598cd7d-27e8-4f6b-b5a6-8d8d90e711ff","era-setup-and-first-flight","Era: setup, wiring and first flight","What is in the box, how the Era is installed and wired, what to configure before the first flight, and the settings pilots most often get wrong.","2026-09-10T11:36:59.585Z",{"id":53,"slug":54,"title":55,"summary":56,"visibility":9,"isPublished":10,"categoryId":11,"categorySlug":12,"categoryName":13,"updatedAt":57},"45083b20-c641-4b98-a8b1-b0c6e01b8754","iris-efis-install-and-calibration","iris EFIS: installation, configuration and calibration","Choosing the right iris, mounting it so the attitude is accurate, pitot and static, alignment, the calibrations that belong to the aircraft, and a troubleshooting table.","2026-09-10T11:36:59.598Z",{"id":59,"slug":60,"title":61,"summary":62,"visibility":9,"isPublished":10,"categoryId":11,"categorySlug":12,"categoryName":13,"updatedAt":63},"1ad481da-0559-4838-863b-2569f03c0fe2","lx10k-upgrade-from-legacy-lx-systems","Upgrading an LX 4000 \u002F 5000 \u002F 7000 \u002F 7007 to the LX 10K","What carries over from the old system, what is new behind the panel, how to choose the vario indicator, what data to bring across, and the first-flight checks.","2026-09-10T11:36:59.607Z",{"id":65,"slug":66,"title":67,"summary":68,"visibility":9,"isPublished":10,"categoryId":11,"categorySlug":12,"categoryName":13,"updatedAt":69},"6d7a9e82-64ef-4e28-bb81-9a83735534ff","lx-can-bus-wiring-rules","CAN bus wiring rules for LX instruments","Termination, topology, where to feed the power, cable and connector practice — the five installation mistakes behind almost every intermittent panel fault.","2026-09-10T11:36:59.640Z",{"id":5,"slug":6,"title":7,"summary":8,"visibility":9,"isPublished":10,"categoryId":11,"categorySlug":12,"categoryName":13,"updatedAt":14},{"id":72,"slug":73,"title":74,"summary":75,"visibility":9,"isPublished":10,"categoryId":11,"categorySlug":12,"categoryName":13,"updatedAt":76},"98973fbb-d216-45d9-a636-c45d3556a0ed","powerflarm-eagle-installation-antennas-and-range","PowerFLARM Eagle: installation, antennas, licences and range","Power, the two FLARM ports, antenna placement that decides your range, which licences unlock which functions, and how to verify your installation from recorded contacts rather than from the ground.","2026-09-10T11:36:59.670Z",{"id":78,"slug":79,"title":80,"summary":81,"visibility":9,"isPublished":10,"categoryId":11,"categorySlug":12,"categoryName":13,"updatedAt":82},"73b335e4-d58a-41be-ac95-7405c493fe86","flarm-led-display-pro-what-the-lights-mean","FLARM LED Display Pro: what every light and screen means","The LED ring colour by colour, the start-up sequence, the idle and warning screens, the fault indications and the audio warnings — plus which cable your FLARM needs.","2026-09-10T11:36:59.678Z",{"id":84,"slug":85,"title":86,"summary":87,"visibility":9,"isPublished":10,"categoryId":11,"categorySlug":12,"categoryName":13,"updatedAt":88},"0a95709f-0c50-45ad-b498-6ec8aef900b5","traffic-square-and-traffic-monitor-setup","Traffic Square and Traffic Monitor: setup, pages and updates","Two instruments that share their software: the gestures and knobs that drive them, the pages they show, the databases they need, the settings worth doing once, and how to update them.","2026-09-10T11:36:59.685Z",{"id":90,"slug":91,"title":92,"summary":93,"visibility":9,"isPublished":10,"categoryId":11,"categorySlug":12,"categoryName":13,"updatedAt":94},"8d3f442c-f0de-4f8c-bb68-b7d330aa0e99","era-and-lx10k-warnings-explained","Every warning on the Era and LX 10K, explained","What the red warning square means for each of the ten switchable warnings, what triggers it, what to do about it — and the warnings that are really settings, including the silent vario and the airspace alert that never comes.","2026-09-10T11:36:59.694Z",{"id":96,"slug":97,"title":98,"summary":99,"visibility":9,"isPublished":10,"categoryId":11,"categorySlug":12,"categoryName":13,"updatedAt":100},"f2f97977-fe7f-4efd-a445-f60e0cef2124","flarm-eagle-wifi-update","FLARM Eagle WiFi update","This document describes FLARM Eagle WiFi update procedure.","2026-08-06T20:07:08.090Z",{"id":102,"slug":103,"title":104,"summary":105,"visibility":9,"isPublished":10,"categoryId":11,"categorySlug":12,"categoryName":13,"updatedAt":100},"2068be72-a5e8-414b-9a22-7f87ee57fe7d","iris-backup-battery-functions","Iris backup battery functions","All Iris devices contain internal backup battery that enables the device to run uninterruptible in case of the main power supply malfunction.",{"id":107,"slug":108,"title":109,"summary":110,"visibility":9,"isPublished":10,"categoryId":11,"categorySlug":12,"categoryName":13,"updatedAt":111},"e0cc10ba-d60f-45e1-ae82-23096d94460b","legacy-lx-instruments-support-and-upgrades","Zeus, Eos, Helios, Colibri II and the LX 7007: support status and upgrade paths","What still exists for instruments out of production: repair while parts last, IGC recalibration and resealing, download-centre pages per device, getting your data off before retirement, and the natural upgrade for each family.","2026-09-10T11:36:59.703Z",false,{"AT":23,"BE":114,"BG":23,"CY":115,"CZ":114,"DE":115,"DK":29,"EE":116,"ES":114,"FI":117,"FR":23,"GR":117,"HR":29,"HU":118,"IE":119,"IT":116,"LT":114,"LU":120,"LV":114,"MT":121,"NL":114,"PL":119,"PT":119,"RO":115,"SE":29,"SI":116,"SK":23},21,19,22,24,27,23,17,18]