ECSS SpaceWire CCSDS Transfer — EOP Character (space-systems/ecss/e5053-eop-character)
Use when the task is the terminator of a SpaceWire packet carrying the
CCSDS packet transfer protocol, per ECSS-E-ST-50-53C clause 5.4.1.8 —
deciding whether a received transfer may be handed to the user at all,
and what a run of bad terminators is telling you about the link.
Domain quick reference
- A SpaceWire packet ends with a marker, not a length. The normal
end-of-packet character says the sender finished where it meant to;
the error end-of-packet character says the packet was abandoned in
flight, by a disconnect, a parity error or a receiver that ran out of
buffer.
- Clause 5.4.1.8 makes the marker the gate on delivery. Only a transfer
ended by the normal marker carries a CCSDS packet the receiving entity
may pass up. Anything else is a fragment, and a fragment is discarded
rather than repaired — there is no retransmission or reassembly in
this protocol to repair it with.
- A third case exists and is not the same as the error marker: no
terminator at all, because the reception was cut off or the buffer
filled before any marker arrived. The packet never ended, so its
length is unknown rather than wrong.
- The marker is checked before the payload. A fragment can hold a
structurally perfect primary header and a plausible length field;
parsing it first invites the receiver to trust content from a packet
that the link already declared broken.
- A marker census over many transfers is the diagnostic that a single
transfer cannot give. A link that passes bit-error tests can still
return an error terminator on a steady fraction of packets, and that
fraction against a budget is what separates a working link from a
degraded one.
Workflow
- Normalise the terminator reported by the link interface into one of
three tokens — normal, error, or absent — accepting the spelled-out
and lower-case spellings interfaces actually emit, and refusing any
token that is neither.
- Derive the disposition from the token alone, before touching the
payload: normal delivers, error discards, absent discards.
- Keep the reason alongside the disposition. The error terminator and
the absent terminator both discard, but they point at different
faults and must not collapse into one message.
- Where the expected transfer length is known, compare it with what
arrived. A short transfer that still carried a normal terminator is
a sender framing defect, not a link fault, and is reported that way.
- Over a received sequence, count each terminator kind, derive the
discard ratio, and compare it with the acceptable budget.
- Report the transfer deliverable only when the terminator was normal
and no length discrepancy was raised against it.
Pitfalls
- Parsing the payload before reading the terminator. The header of an
abandoned packet parses perfectly often enough that content checks
will pass and the fragment will be delivered.
- Folding the absent terminator into the error terminator. Both
discard, so the verdict looks the same, and then the operator cannot
tell a link that reports errors from a receiver that is running out
of buffer.
- Trying to salvage the octets that arrived before an error terminator.
The protocol has no reassembly; a partially received packet has no
defined remainder and keeping it substitutes a guess for data.
- Reading a normal terminator as proof the transfer is whole. The
marker says the sender stopped deliberately; it does not say the
sender sent everything it should have, which is why the length
comparison stays in the assessment.
- Grading a link on a single transfer. One error terminator is noise;
a ratio against a budget over a run is the measurement, and it is the
only one that distinguishes a degraded link from an unlucky packet.
Behavior contract (gate 3)
The marker normalisation, disposition rule, length cross-check and
sequence grading are exercised by the gate 3 contract test:
scripts/test_e5053_eop_character.py against
scripts/e5053_eop_character_logic.py (stdlib unittest, offline). Run:
python3 scripts/test_e5053_eop_character.py
Compliance
- ECSS standards are freely downloadable (ESA); cite the source and
paraphrase per standards-map.yaml.
- compliance: STANDARDS-REF, gated: false.
1---2name: e5053-eop-character3description: "Evaluate the end-of-packet marker that terminates a SpaceWire transfer carrying a CCSDS packet under ECSS-E-ST-50-53C clause 5.4.1.8: separate a normal terminator from an error terminator and from no terminator at all, decide deliver or discard from that marker before any payload is parsed, and grade a received sequence against a discard-ratio budget so a link that is up but shredding packets is visible. Use when receiving, discarding or fault-finding CCSDS transfers on a SpaceWire link. Trigger: ecss, e-st-50-53c, spacewire-eop-character, spacewire-eep-error-terminator, ccsds-transfer-discard-rule, spacewire-packet-truncation, link-discard-ratio, terminator-disposition."4license: Apache-2.05compliance: STANDARDS-REF6standards:7 - id: ecss8 reference-only: true9gated: false10domain: space-systems11pack: space-systems12compatibility: "agentskills.io SKILL.md; any SKILL.md host (Claude Code, Hermes, OpenClaw)"13metadata:14 source: https://skillmd.com/skills/ashfordeou/e5053-eop-character15 domain: space-systems16 subdomain: ecss17 tags: [ecss, e-st-50-53-ccsds-packet-transfer, e5053-eop-character, spacewire-eop-character, spacewire-eep-error-terminator, ccsds-transfer-discard-rule, spacewire-packet-truncation, link-discard-ratio]18 version: 0.1.019 author: Aero Agent Skills20---2122# ECSS SpaceWire CCSDS Transfer — EOP Character (space-systems/ecss/e5053-eop-character)2324Use when the task is the terminator of a SpaceWire packet carrying the25CCSDS packet transfer protocol, per ECSS-E-ST-50-53C clause 5.4.1.8 —26deciding whether a received transfer may be handed to the user at all,27and what a run of bad terminators is telling you about the link.2829## Domain quick reference3031- A SpaceWire packet ends with a marker, not a length. The normal32 end-of-packet character says the sender finished where it meant to;33 the error end-of-packet character says the packet was abandoned in34 flight, by a disconnect, a parity error or a receiver that ran out of35 buffer.36- Clause 5.4.1.8 makes the marker the gate on delivery. Only a transfer37 ended by the normal marker carries a CCSDS packet the receiving entity38 may pass up. Anything else is a fragment, and a fragment is discarded39 rather than repaired — there is no retransmission or reassembly in40 this protocol to repair it with.41- A third case exists and is not the same as the error marker: no42 terminator at all, because the reception was cut off or the buffer43 filled before any marker arrived. The packet never ended, so its44 length is unknown rather than wrong.45- The marker is checked before the payload. A fragment can hold a46 structurally perfect primary header and a plausible length field;47 parsing it first invites the receiver to trust content from a packet48 that the link already declared broken.49- A marker census over many transfers is the diagnostic that a single50 transfer cannot give. A link that passes bit-error tests can still51 return an error terminator on a steady fraction of packets, and that52 fraction against a budget is what separates a working link from a53 degraded one.5455## Workflow56571. Normalise the terminator reported by the link interface into one of58 three tokens — normal, error, or absent — accepting the spelled-out59 and lower-case spellings interfaces actually emit, and refusing any60 token that is neither.612. Derive the disposition from the token alone, before touching the62 payload: normal delivers, error discards, absent discards.633. Keep the reason alongside the disposition. The error terminator and64 the absent terminator both discard, but they point at different65 faults and must not collapse into one message.664. Where the expected transfer length is known, compare it with what67 arrived. A short transfer that still carried a normal terminator is68 a sender framing defect, not a link fault, and is reported that way.695. Over a received sequence, count each terminator kind, derive the70 discard ratio, and compare it with the acceptable budget.716. Report the transfer deliverable only when the terminator was normal72 and no length discrepancy was raised against it.7374## Pitfalls7576- Parsing the payload before reading the terminator. The header of an77 abandoned packet parses perfectly often enough that content checks78 will pass and the fragment will be delivered.79- Folding the absent terminator into the error terminator. Both80 discard, so the verdict looks the same, and then the operator cannot81 tell a link that reports errors from a receiver that is running out82 of buffer.83- Trying to salvage the octets that arrived before an error terminator.84 The protocol has no reassembly; a partially received packet has no85 defined remainder and keeping it substitutes a guess for data.86- Reading a normal terminator as proof the transfer is whole. The87 marker says the sender stopped deliberately; it does not say the88 sender sent everything it should have, which is why the length89 comparison stays in the assessment.90- Grading a link on a single transfer. One error terminator is noise;91 a ratio against a budget over a run is the measurement, and it is the92 only one that distinguishes a degraded link from an unlucky packet.9394## Behavior contract (gate 3)9596The marker normalisation, disposition rule, length cross-check and97sequence grading are exercised by the gate 3 contract test:98scripts/test_e5053_eop_character.py against99scripts/e5053_eop_character_logic.py (stdlib unittest, offline). Run:100python3 scripts/test_e5053_eop_character.py101102## Compliance103104- ECSS standards are freely downloadable (ESA); cite the source and105 paraphrase per standards-map.yaml.106- compliance: STANDARDS-REF, gated: false.