You should reprogram the Artex dongle when its firmware no longer matches the aircraft's ELT configuration, when the unit fails a self-test, when the aircraft registration or country code changes, or when a manufacturer service bulletin mandates a firmware revision. Before any of that, confirm the dongle is the actual fault by reading the ELT's diagnostic codes, because a large share of suspected dongle failures trace to wiring, antenna, or battery issues instead. Reprogramming is a configuration and firmware operation, not a repair, and it only solves problems the firmware and settings can actually cause.
What the dongle actually does
The Artex dongle is the programming and interface module that sits between a technician's computer and an Artex emergency locator transmitter (ELT). It does three jobs. It writes aircraft identity data into the ELT's non-volatile memory, including the 15-character hexadecimal beacon ID, the country of registration, and the aircraft type. It flashes firmware that governs how the ELT encodes and transmits on 406 MHz. And it reads back diagnostic and self-test records so a technician can see whether the beacon is healthy.
The reason reprogramming matters is that a 406 MHz ELT is not a dumb radio. Each transmission carries a digital message encoded with the beacon's identity and, depending on the protocol, position data. If the identity written into memory does not match the aircraft and the national registry, the alert reaches the wrong file or gets flagged as invalid. Reprogramming is the process of making the memory and firmware agree with reality.
A useful mental model: the ELT is the transmitter, but the dongle writes the label that gets broadcast to rescue coordinators. A wrong label is functionally a wrong aircraft.
Quantified context: when the data says reprogram
The strongest mechanical argument for reprogramming on a schedule is battery and beacon aging. Most 406 MHz ELT batteries must be replaced at intervals the manufacturer specifies, commonly every five years for the main battery, and the transmitter itself is typically designed for a service life measured in years of cumulative operation. When the battery is replaced, the ELT firmware and configuration are often refreshed as part of the same work order.
Self-test cadence is the other quantified trigger. A 406 MHz ELT performs an internal self-test that a pilot can monitor, and the governing standard for the onboard test is that the ELT must self-test at least once every 30 days, with many units running a test on power-up and a longer test at intervals the installer sets. The 406 MHz signal itself is monitored for accuracy within a few parts per billion, because the rescue system uses frequency stability to distinguish a real beacon from interference.
For the dongle specifically, no single universal "reprogram every N months" rule exists across all Artex models. The trigger is event-driven or condition-driven, and the manufacturer's maintenance manual for your exact ELT model is the authority. What the numbers do show is the cost of getting it wrong: an invalid or mismatched beacon identity delays the alert from reaching the correct rescue coordination center.
Timeline: the reprogramming lifecycle
| Stage | What happens | Typical trigger |
|---|---|---|
| Installation | Dongle writes beacon ID, country, aircraft type into ELT memory | New ELT or new aircraft |
| Annual check | Self-test records read; battery and wiring inspected | Scheduled maintenance |
| Registration change | Beacon ID and country code rewritten | Aircraft sold or re-registered |
| Battery replacement | Firmware and configuration refreshed | Manufacturer interval, commonly 5 years |
| Service bulletin | Firmware updated to address a known issue | Manufacturer notice |
| Failure indication | Diagnostic codes read; reprogram or replace | Self-test fault |
| Post-repair | Configuration rewritten after ELT or antenna work | Any alteration to the install |
The pattern in that table is the core answer. Reprogramming clusters around installation, identity changes, battery service, and fault diagnosis. It is not a routine calendar event like an oil change.
Edge cases that change the decision
Several situations make the standard advice unreliable. A dongle that reads back a correct beacon ID but still throws a self-test fault is usually a hardware or antenna problem, not a programming one. Reprogramming in that case wastes time and can overwrite a diagnostic record you need.
A second edge case is a used aircraft imported from another country. The country code and beacon ID must be rewritten to match the new national registry, and this is a reprogramming event even if the ELT is otherwise healthy. A third is a firmware revision that changes the transmission protocol or the encoding of position data; here the dongle is the tool, but the manufacturer must supply the new firmware, and a technician cannot invent it.
The counterintuitive detail professionals know: a dongle can pass its own programming check while the ELT still transmits a stale identity, because the check verifies that the write succeeded, not that the written value is the legally correct one. Always verify the identity against the registration document, not just against the dongle's success message.
Red flags that argue against reprogramming as the fix: Self-test failure with correct beacon ID — suspect antenna or cabling first. Repeated write failures — suspect dongle hardware or connector, not firmware. Unknown firmware source — never flash firmware of unverified origin. ELT physically damaged — reprogramming cannot correct a failed transmitter. No manufacturer documentation for the model — stop and get the manual.
Misconceptions worth correcting
The most common misconception is that reprogramming is the same as repairing. It is not. Reprogramming writes configuration and firmware; it does not replace a depleted battery, a corroded connector, or a cracked antenna. A dongle cannot make a failing transmitter pass.
Another misconception is that any computer with the right cable can do the job safely. Artex dongles are paired with manufacturer software and model-specific firmware. Using generic tools risks writing an invalid beacon ID, which is worse than a known-bad state because it can produce a plausible-looking but wrong transmission.
A third misconception is that reprogramming resets the maintenance clock. It does not. Battery life, transmitter aging, and inspection intervals are tracked separately from the firmware configuration. Refreshing firmware does not extend the battery replacement interval.
Comparison of options when an ELT misbehaves:
| Option | What it fixes | When it is wrong |
|---|---|---|
| Reprogram firmware | Known firmware defects, protocol updates | Hardware faults, wrong identity |
| Rewrite beacon ID | Registration or country change | Firmware corruption |
| Replace battery | Low or expired battery | Programming errors |
| Replace antenna/cable | Weak or failed signal path | Configuration errors |
| Replace ELT | Transmitter failure | Simple configuration issues |
| Professional bench test | Diagnoses ambiguous faults | Never wrong as a first step |
The table makes the decision tree explicit. Reprogramming sits in the configuration column, not the repair column.
Practical actions and thresholds
Start with documentation, not the dongle. Pull the maintenance manual for your exact Artex ELT model and confirm which firmware revisions are approved for it. Then read the ELT's self-test and diagnostic records through the dongle before changing anything, so you have a baseline.
Concrete steps and thresholds: Verify the beacon ID against the aircraft registration document character by character; a single wrong character is a mismatch. Confirm the country code matches the registry, especially after import or sale. Check the battery replacement date against the manufacturer interval; if it is due, schedule battery service and reprogram in the same visit. Read firmware version; compare to the manufacturer's current approved revision; reprogram only if they differ and the manual approves the update. After any reprogram, run the self-test and confirm the read-back identity matches the registration before returning the aircraft to service.
Reconciling the thresholds: the 30-day self-test is a monitoring rule, the five-year battery interval is a service rule, and the firmware-match check is a configuration rule. They answer different questions. Reprogram when the configuration rule is violated or when a service event changes the data; use the self-test and battery rules to decide when to look, not automatically when to reprogram.
Limitations and what this cannot tell you
This explainer describes stable mechanisms: what a dongle writes, why identity and firmware matter, and the categories of triggers that justify reprogramming. It cannot substitute for the maintenance manual for your specific ELT model, and it does not provide the beacon ID format, firmware numbers, or programming procedures, because those are model-specific and change over time.
No universal reprogramming interval applies across all Artex units. Any source claiming one specific number for all models is overgeneralizing. The authoritative answer for your aircraft is the manufacturer's current documentation plus your national aviation authority's registration requirements. Treat the decision as a documented maintenance action, not a guess.