Feature · ingestion
DLU Decoder
Vendor-specific decoders that don't pretend the world is standard
At a glance
- ▸ Honeywell DLU empirical decoder (production)
- ▸ Per-channel decoders mapped to recorder documentation
- ▸ Multi-vendor architecture (Honeywell first, more to come)
- ▸ Slot-level audit trail with byte-offset traceability
- ▸ Hot-swap decoder configs without redeploying
What it does
ARINC 717 says “here’s the standard.” DLU documents from Honeywell, Boeing, and Airbus say “here’s what we actually wrote.” Aviation AI Pro models DLUs as named channels with per-recorder mappings, so when a customer says “we use Honeywell on the A320 and Recorder Co. X on the 737,” the decoder picks the right path automatically.
Every byte of a decoded value is traceable back to its slot + frame number — when an auditor asks “where did this flap angle reading come from?”, the answer is one query away.