SpaceWire¶

Spacecraft onboard serial network for high-speed links among instruments, processors, memory, and telemetry systems.

Identity¶

Spacecraft onboard serial network for high-speed links among instruments, processors, memory, and telemetry systems.

What This Protocol Teaches¶

• SpaceWire is what serial links look like when the machine is expensive and far away.
• It teaches how to inspect data/control characters, packet routing, wormhole routing without mistaking field extraction for meaning.
• It keeps observer inference separate from system truth.

Operational Context¶

SpaceWire appears in spacecraft, aerospace contexts and is modeled in the atlas at the physical, data-link, packet 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 SpaceWire packet fragment
path: 0x21 0x04  data: de ad be ef  eop

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

Worked Decode¶

1. Treat path: 0x21 0x04 as routing evidence in a synthetic packet fragment.
2. data: de ad be ef is an opaque payload until a mission or device protocol names it.
3. eop marks an end-of-packet condition in the artifact, not an application success state.
4. Routing bytes can be inspected separately from payload semantics and network topology truth.

Field Layout / Anatomy¶

Visual Model¶

Timing And Authority¶

Timing and authority depend on the spacecraft-network 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¶

• Path bytes can be routing evidence without naming the application source.
• End-of-packet markers do not prove payload validity.
• Topology assumptions can make a fragment look more complete than it is.

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 high for scope and terminology, with semantic claims limited to public metadata, public source notes, and synthetic teaching artifacts.

Source Notes¶

References¶

Public Sources¶

• ECSS
• ECSS-E-ST-50-12C Rev.1 SpaceWire — canonical-standard.
• ESA
• SpaceWire overview — official-public.