ARINC 629¶

Multi-transmitter avionics data bus intended to share a bus without a single bus controller.

Identity¶

Multi-transmitter avionics data bus intended to share a bus without a single bus controller.

What This Protocol Teaches¶

• ARINC 629 is a historically important attempt to move beyond point-to-point ARINC 429.
• It teaches how to inspect terminal access protocol, multi-transmitter bus, message timing without mistaking field extraction for meaning.
• It keeps observer inference separate from system truth.

Operational Context¶

ARINC 629 appears in commercial-aviation, avionics contexts and is modeled in the atlas at the physical, data-link, media-access layer(s). The binder treats it as an inspection surface: what evidence appears, what timing matters, and what outside authority is required before assigning meaning.

draft-structure-only: this is not yet a final-copy binder page. It has an atlas-grounded teaching hook and source notes, but still needs a stronger worked trace, page-specific ambiguity case, and reviewer-validated visual before promotion.

A Concrete Artifact¶

# synthetic bus observation
terminal=3 gap=assigned word=0x1020 0x3344
terminal=7 gap=assigned word=0x2040 0x5566

Synthetic offline sample for explanation; not a real operational trace or live-system instruction.

Worked Decode¶

1. Read each line as an offline bus-observation record, not as an LRU truth claim.
2. terminal=3 and terminal=7 are terminal-access evidence in the synthetic artifact.
3. gap=assigned is a timing cue: the apparent right to speak belongs to the access discipline, not to a central controller in this page-local model.
4. The word pairs 0x1020 0x3344 and 0x2040 0x5566 are payload evidence only until an installation profile names their meaning.
5. The page can teach terminal access and bus sharing; it cannot infer aircraft function from terminal numbers alone.

Field Layout / Anatomy¶

Visual Model¶

Timing And Authority¶

Timing and authority depend on the data-bus role: scheduled, polled, arbitrated, transmitted, or logged evidence should not be read as the same kind of truth. Semantic authority is external to the raw artifact unless the artifact is itself a description or capture format; even then, provenance determines whether the description should be trusted.

Bytes rarely explain themselves. Name the source that defines meaning before naming engineering values: standard metadata, label table, DBC, PGN/SPN definition, object dictionary, register map, DID catalog, LDF, ARXML, channel metadata, or vendor profile.

Failure And Ambiguity¶

• Terminal numbers do not identify LRUs without installation authority.
• A quiet interval may be access timing, capture loss, or filtered evidence.
• Payload words can look stable while remaining semantically anonymous.

Observer Lesson¶

A passive observer can usually infer artifact boundaries, repeated structure, cadence, missingness, and candidate state transitions. The observer usually cannot prove physical truth, application intent, complete system state, or engineering-unit meaning without semantic authority and timing provenance.

Python Model¶

No current runtime example is claimed for this draft page. Keep reader claims at the artifact and source level until a separate implementation plan adds a tested model.

Local Teaching Notes¶

The artifact and diagrams are synthetic teaching material. The page intentionally omits conformance timing tables, electrical design detail, proprietary configuration, and exhaustive standard behavior.

Source Confidence¶

Source confidence is medium for scope and terminology, with semantic claims limited to public metadata, public source notes, and synthetic teaching artifacts.

Source Notes¶

References¶

Public Sources¶

• SAE ITC / ARINC
• ARINC 629 Multi-Transmitter Data Bus — canonical-standard.