[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fUi3Pksf4HcOMDiQ9G9IxbjUIqWbkiJtKO6BRZPYPazk":3,"$fFKpNWZVVYTBYE3vPJn_-n27owUoP9TxN8PTy0yh8W6Y":17,"shop-vat-rates":102},{"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},"7698e2e3-2195-4b46-8ca3-2067e17da186","navia-emu-sensor-installation","NAVIA EMU: installing CHT, EGT, RPM, fuel-flow and fuel-quantity sensors","The thermocouple rules that govern everything, where CHT and EGT probes go and where they must not, RTD and pressure senders, fuel quantity and flow, RPM pickups, and two worked engine examples.","public",true,"9d0897b6-42d0-4643-8ceb-e8a02ce4a854","navia","NAVIA","2026-09-10T11:36:59.755Z","The NAVIA EMU is engine-agnostic. Nothing in it is hardcoded to a particular powerplant: every input is declared in the Configuration Portal rather than at the factory, and virtually any industry-standard sender can be connected and calibrated. That freedom lands entirely on whoever does the installation.\n\nThis article covers the sensor end of the job — where each probe goes, what it must never be wired with, and what to check before the aircraft flies again. The EMU-side pin allocations are in the installation manual and are not repeated here. What follows is the part that is the same in every aircraft: the physics that decides whether a channel is telling you the truth.\n\n## What you are wiring into\n\n| Input group | Count | Takes |\n|---|---|---|\n| Thermocouple, differential (J400) | 12 | Type J or K probes — CHT, EGT, anything thermocouple |\n| Thermocouple, auxiliary (J401) | 2 | TC13 differential, TC14 single-ended — normally turbine inlet temperature |\n| RTD | 3 | Pt100 \u002F Pt1000 — outside air, oil, carburettor |\n| Analogue \u002F digital (AIN) | 12 | Resistive senders, active 0–5 V sensors, pulse and frequency signals |\n| RPM | 2 | Engine and rotor or propeller |\n| Current clamp | 1 | Hall-effect DC clamp |\n\nAlongside these sit internally generated, individually fused +5 V and +12 V supply rails for the senders themselves (plus a 3.3 V rail for the current clamp), and the Master Warning and Master Caution lamp outputs and acknowledge-button inputs. Every channel is declared on the portal `Config` page — port, sensor model from the library, measurement type and position — so no input is committed to anything until you say so.\n\n## The thermocouple rule that governs everything\n\nA thermocouple generates its signal at the junction of two dissimilar metals, which means **every additional dissimilar-metal junction in the circuit is a measurement error**. Four rules follow, and none of them are optional.\n\n- **Matching extension wire.** Type K extension wire for type K probes, type J for type J. Never extend a thermocouple with ordinary copper, and route the run away from ignition leads and alternator cables.\n- **Polarity, checked against the wire's own datasheet.** The colour codes disagree between standards: in the American code red is always negative, in the European code white is always negative, and legacy national codes differ again — some of them using red as positive. A reversed pair does not damage the input, it just makes the reading fall as the probe heats up.\n- **Crimp, never solder.** Thermocouple wire does not solder well, and a soldered joint is a rigid point for vibration to work on. Solder-cup connectors are out for the same reason.\n- **Put the cold junction at J400.** The thermocouple-to-copper transition belongs in the connector, where the EMU measures its reference temperature.\n\n> A copper splice made somewhere convenient in the engine compartment reads perfectly on the ground and drifts by tens of degrees in flight, as the splice and the connector diverge in temperature. It is the single most common way to get a plausible, confident, wrong number.\n\n## CHT probes\n\n### Ring-terminal probes\n\nRemove the spark plug, place the ring probe under it, refit the plug. Orient the probe so its leads have the maximum available clearance from the exhaust and from engine structure.\n\n### Bayonet probes\n\nScrew the bayonet adapter into the threaded CHT well near the bottom spark plug. Adjust the locking collar on the spring so the probe tip presses firmly on the bottom of the well when locked.\n\n> The CHT well is identified by its **solid bottom**. Never use the primer hole: it is open into the cylinder. If you cannot tell the two apart on this engine, stop and consult someone who can.\n\n### Rotax under-bolt probes\n\nOn 912-series engines the stock CHT senders can be replaced by 10 mm ring probes fitted under the original sensor bolts, following the engine maker's guidance.\n\n## EGT probes\n\nWhere the engine manufacturer gives no guidance on probe location:\n\n1. Drill a 1\u002F8-inch hole in each exhaust pipe, **2–8 inches from the cylinder** — and, far more important than the exact figure, **the same distance on every cylinder**, because the whole value of EGT is in comparing one cylinder against its neighbours.\n2. Choose a straight section of pipe rather than a curve; the clamps seat properly there. Check the probe will not foul the cowl or block maintenance access.\n3. Insert the probe and tighten the clamp firmly, without over-tightening.\n\nThe probe body grounds through the exhaust pipe. That is normal and required for a stable reading. Leave slack in the leads between engine and airframe to absorb engine movement, and label every lead with its cylinder number **before** you route it — sorting that out later, on your back, in the dark, is nobody's idea of an afternoon. Do not cut probe leads to length: coil and secure the excess instead. Unused thermocouple inputs need nothing done to them, though for the tidiest readings unused pairs may be shorted together at the connector.\n\n> A loose or detached EGT probe leaves an open hole in the exhaust, leaking hot gas and carbon monoxide into the cowling. Inspect the attachment at every inspection. On pusher installations, safety-wire the probe so a failed clamp cannot let it reach the propeller.\n\n## RTD, fluid and pressure senders\n\n**Outside air temperature** from a Pt1000 probe on an RTD input needs no interface network, and placement decides the reading: out of the propeller wash and the exhaust stream, away from cowling outlets and heated skin, never behind the engine, not inside a NACA inlet, and preferably in the shade rather than under a fairing that bakes in the sun. An inspection cover under the wing, outside the propeller wash, is a reliable spot. Twist the probe leads over their full length.\n\nFit **fluid temperature senders** per the engine manufacturer's instructions. Single-terminal senders ground through their own case, so the case **must** have a good electrical connection to engine ground — use pipe thread sealing compound, not PTFE tape, which insulates. Two-terminal senders take their return to the channel ground pin.\n\nResistive pressure senders ground through the case too, so a remote-mounted one needs a dedicated ground wire back to it. The VDO 0–2 bar low-pressure sender is vibration-sensitive: mount it remotely on the firewall and reach the pressure with a hose. Active 0–5 V transducers mount with the threaded port **down or horizontal, never pointing up**, so water cannot collect inside and split the sensor when it freezes, and they are powered from the EMU's fused supply pins only; some are destroyed by direct connection to unregulated aircraft power.\n\n**Current-loop senders**, including the current-production Rotax oil pressure senders that replaced the older resistive type, are read through an external shunt resistor: the loop current develops a voltage across the shunt, and the channel is configured as an active sensor with a custom two-point curve. If your engine carries the newer sender, the resistive wiring shown for the older one simply does not apply.\n\n## Fuel quantity probes\n\nResistive float senders wire straight to an AIN channel in resistive mode and are calibrated tank-by-tank on the portal `Calibration` page. Capacitive probes use their own interface module with a 0–5 V output, and must first be taught the tank with the probe manufacturer's own empty\u002Ffull set-point procedure before the EMU channel is calibrated on top of it. Keep a capacitive probe tip at least 1\u002F4 inch clear of the tank bottom, and expect readings to take up to two minutes to settle after fuelling — the damping is deliberate, not a fault.\n\n> Electric fuel quantity indication, float or capacitive, must never be the sole basis for fuel planning. Determine fuel on board before flight by dipstick or visual check, and plan by time and consumption. Senders stick, attitudes change, and fuel sloshes.\n\n## Fuel flow transducers\n\nThe EMU counts pulses from a turbine transducer — the reference EI FT-60 is linear to about one per cent — and it is utterly unforgiving about plumbing.\n\n- Fit the transducer **downstream of the last fuel pump**. Upstream of a pump it invites vapour lock and jumpy readings.\n- Give the inlet at least five inches of straight or gently curving line, and route the outlet level with or above the transducer — never dropping away immediately after it.\n- Put a gascolator or filter upstream to keep debris out of the rotor.\n- Mount it with the **electrical wires pointing up**, because the design vents vapour that way. Thread sealant on the ports is mandatory, but never PTFE tape, which shreds into the rotor.\n- The EI FT-60 and other open-collector transducers need an external pull-up resistor of 4.7–10 kΩ to the channel's +5 V pin. Without it the channel reads zero flow, permanently and convincingly.\n- After the fuel system is closed up, run the flow and pressure tests of FAA AC 23-16 — typically 125–150% of full-throttle fuel flow — and confirm system pressure stays above the engine minimum.\n- If readings jump with the electric boost pump running, that is pulsation and not the transducer: a tee before it with 1–2 ft of capped tubing pointing vertically up will damp it.\n- On return-line systems, a second transducer in the return line lets the EMU compute net consumption — configure the two channels as fuel in and fuel return.\n\n## RPM, supplies and annunciators\n\nTwo independent RPM inputs cover engine and rotor or propeller speed. They accept **hall-effect sensors and low-voltage pulse signals** — trigger-coil outputs, electronic tachometer outputs, gearbox pickups. Pulses per revolution and, behind a gearbox, the reduction ratio are set per channel in the portal, so a channel reading exactly double or exactly half is nearly always a settings error rather than a wiring one.\n\n> Never connect a magneto P-lead or an ignition high-tension lead directly to an RPM input. Magneto-equipped engines need the series-resistor connection given in the installation manual; the raw lead carries energy the input will not survive.\n\nSender supplies come from the EMU's own fused rails, so no aircraft bus power needs to reach the engine sensors at all. A dead supply pin is usually a resettable fuse that has done its job: remove the short and power-cycle. The Master Warning and Master Caution circuits give you both halves of a classic annunciator — an indicator output for the panel lamp and an input for a momentary acknowledge button — so a combined push-button with an integrated lamp wires straight in; take the lamp connection itself from the installation manual. In a Power-over-Ethernet installation the EMU has no connection to the aircraft bus at all, so bus voltage is monitored by bringing it in through a divider network to a spare AIN channel — never above 5 V directly onto an AIN pin.\n\n## Two worked examples\n\n![NAVIA EMU typical sensor harness — the Rotax 912 ULS example wired to J401 and J400](\u002Fsite\u002Fimg\u002Fkb\u002Fnavia-emu-wiring.webp)\n\n| Measurement | Rotax 912 ULS | Lycoming O-320 |\n|---|---|---|\n| EGT | Type K probes, TC1–TC2 | Type K clamp probes, TC1–TC4 |\n| CHT | Resistive senders on AIN1–AIN2 | Bayonet probes, TC5–TC8 |\n| Oil temperature | Resistive sender, AIN3 | Pt100 RTD, RTD1 |\n| Oil and fuel pressure | Resistive sender and 0–5 V transducer, AIN4–AIN5 | Resistive senders, AIN1–AIN2 |\n| Manifold pressure | Active 0–5 V sensor, AIN6 | Active 0–5 V sensor, AIN5 |\n| Fuel quantity | Float sender, AIN11 | Float senders left and right, AIN11–AIN12 |\n| Engine RPM | Trigger coil or tacho output, RPM1 | Electronic tach output or hall pickup, RPM1 |\n| Fuel flow | Pulse transducer, AIN8 | — |\n| Carburettor temperature | — | Pt100 RTD, RTD2 |\n| Current | 300 A hall clamp, clamp input | 300 A hall clamp, clamp input |\n\nBoth are starting points: any input can be reassigned in the portal. The one allocation that is not yours to choose is a reused thermocouple harness from an existing engine information system — leave the harness alone and assign the channels to match how it is already wired.\n\n## Post-installation checkout\n\n1. **Power up and confirm the EMU is announced** to the system, or that the portal is reachable in a standalone installation. Verify the reported firmware version is current.\n2. **Check plausibility cold.** Every temperature channel should sit near ambient; a channel pegged full-scale or at zero is an open or shorted probe circuit, or the wrong sensor model selected. Pressure channels read zero. Fuel quantity matches what is actually in the tanks. System voltage matches a multimeter.\n3. **Check thermocouple polarity** by warming each probe individually and confirming the right channel **rises**. A channel that falls has its pair swapped.\n4. **Exercise the alerting loop.** Temporarily lower a threshold to force a caution and a warning, confirm the panel lamps light and the acknowledge buttons work, then restore the real thresholds and verify them again.\n5. **Run the engine.** RPM against a reference tachometer across the range (verify the reduction ratio setting), oil pressure up immediately after start, all CHT and EGT channels rising evenly, fuel flow plausible at idle and at run-up, charging current responding as loads are switched.\n6. **Inspect afterwards** for leaks at every fitting and boss, chafing along the harness, and firewall penetrations still properly sealed.\n\n## When a channel does not read right\n\n| Symptom | Likely cause | Fix |\n|---|---|---|\n| Thermocouple channel pegged full-scale or blank | Open probe circuit — broken extension wire, bad crimp, unplugged probe | Check continuity probe to J400, re-crimp, confirm the pair is in the right contacts |\n| Reading falls when the probe is heated | Reversed pair | Swap the pair at the connector |\n| Plausible on the ground, tens of degrees out in flight | Copper splice or solder joint in the thermocouple path | Remove it; matching alloy wire end to end |\n| One CHT or EGT channel erratic | Loose clamp, probe tip not grounded, or lead routed along ignition wiring | Re-tighten, reseat, reroute |\n| Resistive sender reads with a large offset | Wrong sensor model selected, or a poor sender case ground | Check the model on `Config`; measure engine case to ground bus with all loads on — over 50 mV means a bad engine ground |\n| All engine-grounded senders offset together | Voltage drop on the engine ground strap | Engine case to ground bus must read under 50 mV (ideally 20 mV) with everything on — fix the ground strap first |\n| Active 0–5 V sensor stuck at maximum | Channel left in resistive mode, or a shorted supply pin | Set the correct mode; check the supply |\n| RPM reads zero | Wrong source lead (Rotax trigger coil: try the other wire), missing external network, or wrong pulses per revolution | Verify the source for this engine; correct the portal settings |\n| RPM erratic, or exactly double or half | Wrong pulses-per-revolution setting, or ignition interference | Correct the setting; reroute the RPM lead away from ignition wiring |\n| Fuel flow reads high with the electric boost pump on | Fuel pulsation | Install a pulsation-damper tee before the transducer |\n| Fuel flow always zero | Open-collector transducer with no external pull-up | Fit the pull-up to the channel's +5 V pin |\n| Sensor supply pin dead | Resettable fuse tripped by a short | Remove the short, power-cycle |\n| Master lamp permanently on | Threshold misconfigured, or lamp on the wrong pins | Review thresholds; verify the lamp wiring |\n\n## Where to go next\n\n- Everyday operation, alerting, the fuel computer and tank calibration: [NAVIA EMU in use](\u002Fkb\u002Farticle\u002Fnavia-emu-alerts-fuel-computer-and-logbook).\n- What the numbers mean once they are on the screen: the Academy articles on [engine monitoring](\u002Facademy\u002Fengine-monitoring) and [fuel planning](\u002Facademy\u002Ffuel-planning).\n- Where the EMU sits in the aircraft: [NAVIA system architecture](\u002Fkb\u002Farticle\u002Fnavia-system-architecture), [commissioning a new aircraft](\u002Fkb\u002Farticle\u002Fnavia-commissioning-a-new-aircraft) and the [NAVIA EMU](\u002Fnavia\u002Femu) product page.\n- Pin allocations, torque figures and anything mechanical: the installation manual, then your dealer, then [us](\u002Fcontact).\n",null,{"categories":18,"articles":45,"search":101},[19,25,28,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":11,"slug":12,"name":13,"description":16,"sortOrder":26,"articleCount":27},25,10,{"id":29,"slug":30,"name":31,"description":16,"sortOrder":32,"articleCount":33},"92b87517-c814-4237-b180-19df9cb80b16","connectivity","Connectivity",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,58,64,70,76,82,83,89,95],{"id":47,"slug":48,"title":49,"summary":50,"visibility":9,"isPublished":10,"categoryId":11,"categorySlug":12,"categoryName":13,"updatedAt":51},"edb2d23e-9cd8-48c9-abbc-365420c26247","navia-system-architecture","NAVIA system architecture: how the pieces fit together","Hub, Core, Sense, Displays, Traffic, UPS, EMU and Grip — what each unit does, how power and data flow over one cable per device, and how to plan a system before ordering.","2026-09-10T11:36:59.617Z",{"id":53,"slug":54,"title":55,"summary":56,"visibility":9,"isPublished":10,"categoryId":11,"categorySlug":12,"categoryName":13,"updatedAt":57},"2e027321-055d-4b7a-9c2a-9c5036e8cc62","navia-commissioning-a-new-aircraft","NAVIA: commissioning a new aircraft","The thirteen steps from wired hardware to a configured aircraft: registering the Core to your account, aircraft identity and configurations, the polar, flight envelope and flaps, weight and balance, and the checks before the first flight.","2026-09-10T11:36:59.710Z",{"id":59,"slug":60,"title":61,"summary":62,"visibility":9,"isPublished":10,"categoryId":11,"categorySlug":12,"categoryName":13,"updatedAt":63},"47957da9-8639-4832-9d76-3c5ed57fd9dc","navia-accounts-roles-profiles-and-screens","NAVIA accounts, roles, display profiles and your phone as a screen","Personal accounts that follow you to any NAVIA aircraft, the four roles and how ownership is established in LX Cloud, pilot in command, screen and login types, display profiles, and adding a phone or tablet as an extra screen.","2026-09-10T11:36:59.718Z",{"id":65,"slug":66,"title":67,"summary":68,"visibility":9,"isPublished":10,"categoryId":11,"categorySlug":12,"categoryName":13,"updatedAt":69},"941c6fbe-cc2a-4bc7-b698-4bcffbf8475f","navia-cloud-sync-offline-and-flight-recording","NAVIA and LX Cloud: synchronisation, working offline, flight recording and the logbook","What belongs to you and what belongs to the aircraft, when synchronisation runs and why it never runs in flight, flying with no internet at all, and how a recorded flight reaches the logbook and the cloud.","2026-09-10T11:36:59.724Z",{"id":71,"slug":72,"title":73,"summary":74,"visibility":9,"isPublished":10,"categoryId":11,"categorySlug":12,"categoryName":13,"updatedAt":75},"51cc50eb-1866-421f-a066-d67a90faa095","navia-updates-databases-and-remote-support","Updating NAVIA: Core, ecosystem devices, databases and remote support","The update page and its three channels, reverting a version, why connected devices update themselves from the Core, keeping airspace and charts current, and the remote-support switch that stays off until you turn it on.","2026-09-10T11:36:59.734Z",{"id":77,"slug":78,"title":79,"summary":80,"visibility":9,"isPublished":10,"categoryId":11,"categorySlug":12,"categoryName":13,"updatedAt":81},"e9e61fe3-3e10-4cc7-98a3-52450b11f313","navia-troubleshooting","NAVIA troubleshooting: warnings, alarms and status-bar items","What each status-bar item reports, the full list of warnings and alarms with what triggers them, and a symptom-cause-fix table for the sixteen things most likely to puzzle you — several of which are not faults.","2026-09-10T11:36:59.745Z",{"id":5,"slug":6,"title":7,"summary":8,"visibility":9,"isPublished":10,"categoryId":11,"categorySlug":12,"categoryName":13,"updatedAt":14},{"id":84,"slug":85,"title":86,"summary":87,"visibility":9,"isPublished":10,"categoryId":11,"categorySlug":12,"categoryName":13,"updatedAt":88},"43d23b57-4681-4d80-9aad-ba64fd471812","navia-emu-alerts-fuel-computer-and-logbook","NAVIA EMU in use: master warning and caution, the fuel computer, calibration and the engine logbook","How the annunciators behave and what acknowledging one does, what a missing reading means in flight, the fuel computer and its limits, calibrating a tank point by point, and why the factory thresholds are not your engine limits.","2026-09-10T11:36:59.779Z",{"id":90,"slug":91,"title":92,"summary":93,"visibility":9,"isPublished":10,"categoryId":11,"categorySlug":12,"categoryName":13,"updatedAt":94},"af207643-1be9-46af-9613-c1cf9fb9c1a8","navia-sense-igc-recorder-and-calibration","NAVIA Sense: the IGC recorder, calibration and the compass swing","The integrated IGC recorder and its security seal, engine noise and when an external means-of-propulsion sensor is required, the Certificate of Calibration that replaced the barochart, and a compass that calibrates itself in flight.","2026-09-10T11:36:59.793Z",{"id":96,"slug":97,"title":98,"summary":99,"visibility":9,"isPublished":10,"categoryId":11,"categorySlug":12,"categoryName":13,"updatedAt":100},"6d3a78b9-2140-4bf8-ba3e-164ddf82b29c","navia-traffic-setup-and-firmware","NAVIA Traffic: FLARM\u002FADS-B setup, firmware modules and the range analyser","Two modules updated separately, why obstacle databases and licence files are tied to your serial number, configuring the unit from its portal, connecting it to a Core Pro, and reading the range analyser honestly.","2026-09-10T11:36:59.803Z",false,{"AT":23,"BE":103,"BG":23,"CY":104,"CZ":103,"DE":104,"DK":26,"EE":105,"ES":103,"FI":106,"FR":23,"GR":106,"HR":26,"HU":107,"IE":108,"IT":105,"LT":103,"LU":109,"LV":103,"MT":110,"NL":103,"PL":108,"PT":108,"RO":104,"SE":26,"SI":105,"SK":23},21,19,22,24,27,23,17,18]