ECSS Communications — ARQ Settings (space-systems/ecss/e50-arq-settings)
Use when the retransmission behaviour of a space data transfer protocol has
to be set up, per ECSS-E-ST-50C clause 5.6.13.5 — which parameters the design
exposes, whether the values chosen fit the link, and whether the operator can
change them once the spacecraft is flying.
Domain quick reference
- Adjustability is half the obligation and the half designs drop. A
retransmission timer compiled into the flight software is a timer nobody
can fix when the link turns out slower than the analysis said, and the
mission then flies the wrong value for its whole life.
- The timeout floor is the round trip plus what the far end spends before
it answers plus the jitter the path adds. A timeout under that floor
retransmits units that were never lost, and the duplicate traffic makes
the congestion that caused the delay worse.
- The window has to cover the bandwidth-delay product or the transmitter
stops and waits. That is a throughput question, separate from the
timeout, and a conservative timeout does not compensate for a short
window.
- The retry limit sets both a worst case and a residual. Worst case
delivery is the attempts times the timeout plus the final round trip;
residual loss is the per-attempt loss raised to the attempt count, and a
design owes both numbers rather than one of them.
- Per-attempt loss compounds by multiplication, so the attempt count to
reach a target is found by multiplying until the target is crossed.
Raising a small probability to a power and comparing floats at the
boundary is a worse way to answer the same question.
- Settings interact. Lengthening the timeout to stop spurious
retransmissions lengthens the worst case delivery, which may then miss
the deadline the retry limit was sized for; the set has to be checked
together, not one parameter at a time.
Workflow
- State the link as the round trip, the acknowledgement delay at the far
end, the jitter on the path, the data rate and the unit size.
- State the configuration as the timeout, the window, the retry limit and
the per-attempt loss probability, each with a flag saying whether it is
commandable in flight.
- Compute the timeout floor and compare the configured timeout against
it with a relative tolerance, so a timeout set exactly at the floor is
acceptable on every build host.
- Compute the window the bandwidth-delay product asks for and compare it
with the configured window, rounding the requirement up because a
partial unit still occupies the link.
- Compute the worst case delivery time the retry limit allows and the
residual loss probability it leaves.
- Where the residual misses the target, report the attempt count that
would reach it, found by multiplying attempt by attempt.
- Put the chosen set through end-to-end simulation before it flies,
covering the whole range of conditions the link is expected to meet,
and read every run for the two signatures the settings exist to keep
out: data the retransmissions failed to recover, and retransmissions
the losses never called for.
- Report any parameter that is not commandable as a finding in its own
right, whatever its value, and summarise the recommended set so an
operator can uplink it.
Obligations
| Item |
Step |
| ECSS-E-ST-50C Rev.2 5.6.13.5a |
7 |
Pitfalls
- Setting the timeout to the round trip alone. The far end still has to
notice the unit and build an acknowledgement, and the path still has
jitter; both sit on top of the propagation.
- Treating a short window as a timing problem. It costs throughput and no
timer setting recovers it; the window is the parameter that moves.
- Quoting a retry limit without the worst case it implies. A generous
limit can push the delivery of a single unit past the contact window,
and the retransmissions then continue into a pass that is already over.
- Reporting the residual loss and calling the configuration adequate. A
configuration that meets the residual and cannot be changed in flight
still fails the clause.
- Tuning one parameter and re-reporting the whole set as sound. The
timeout, the window and the retry limit trade against each other, so a
changed value means the set is assessed again.
Behavior contract (gate 3)
Parameter validation, the timeout floor, the bandwidth-delay window, the
worst case delivery time, the residual loss and the attempt count that
reaches a target, acceptance exactly at the timeout floor and the
commandability findings are exercised by the gate 3 contract test:
scripts/test_e50_arq_settings.py against
scripts/e50_arq_settings_logic.py (stdlib unittest, offline).
Run:
python3 scripts/test_e50_arq_settings.py
Compliance
- ECSS standards are freely downloadable (ESA); cite the source and
paraphrase per standards-map.yaml.
- compliance: STANDARDS-REF, gated: false.
1---2name: e50-arq-settings3description: "Configure the automatic repeat request parameters of a space data transfer protocol under ECSS-E-ST-50C clause 5.6.13.5, whose single normative item asks that the retransmission settings be adjustable in flight and consistent with the link they run over. Derive the retransmission timeout floor from the round trip, the acknowledgement delay and the jitter, the transmit window the bandwidth-delay product needs, the worst case delivery time a retry limit allows, and the residual loss it leaves. Report every setting that is fixed in the build rather than commandable. Use when tuning retransmission timers or reviewing an ARQ configuration. Trigger: ecss, e-st-50-communications, arq-retransmission-timeout, arq-transmit-window-sizing, arq-retry-limit-budget, ground-settable-arq-parameters, automatic-repeat-request-configuration."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)"13clauses:14 - standard: ECSS-E-ST-50C Rev.215 clause: 5.6.13.516 items: [a]17 relation: implements18metadata:19 source: https://skillmd.com/skills/ashfordeou/e50-arq-settings20 domain: space-systems21 subdomain: ecss22 tags: [ecss, e-st-50-communications, e50-arq-settings, arq-retransmission-timeout, arq-transmit-window-sizing, arq-retry-limit-budget, ground-settable-arq-parameters, automatic-repeat-request-configuration]23 version: 0.1.024 author: Aero Agent Skills25---2627# ECSS Communications — ARQ Settings (space-systems/ecss/e50-arq-settings)2829Use when the retransmission behaviour of a space data transfer protocol has30to be set up, per ECSS-E-ST-50C clause 5.6.13.5 — which parameters the design31exposes, whether the values chosen fit the link, and whether the operator can32change them once the spacecraft is flying.3334## Domain quick reference3536- Adjustability is half the obligation and the half designs drop. A37 retransmission timer compiled into the flight software is a timer nobody38 can fix when the link turns out slower than the analysis said, and the39 mission then flies the wrong value for its whole life.40- The timeout floor is the round trip plus what the far end spends before41 it answers plus the jitter the path adds. A timeout under that floor42 retransmits units that were never lost, and the duplicate traffic makes43 the congestion that caused the delay worse.44- The window has to cover the bandwidth-delay product or the transmitter45 stops and waits. That is a throughput question, separate from the46 timeout, and a conservative timeout does not compensate for a short47 window.48- The retry limit sets both a worst case and a residual. Worst case49 delivery is the attempts times the timeout plus the final round trip;50 residual loss is the per-attempt loss raised to the attempt count, and a51 design owes both numbers rather than one of them.52- Per-attempt loss compounds by multiplication, so the attempt count to53 reach a target is found by multiplying until the target is crossed.54 Raising a small probability to a power and comparing floats at the55 boundary is a worse way to answer the same question.56- Settings interact. Lengthening the timeout to stop spurious57 retransmissions lengthens the worst case delivery, which may then miss58 the deadline the retry limit was sized for; the set has to be checked59 together, not one parameter at a time.6061## Workflow62631. State the link as the round trip, the acknowledgement delay at the far64 end, the jitter on the path, the data rate and the unit size.652. State the configuration as the timeout, the window, the retry limit and66 the per-attempt loss probability, each with a flag saying whether it is67 commandable in flight.683. Compute the timeout floor and compare the configured timeout against69 it with a relative tolerance, so a timeout set exactly at the floor is70 acceptable on every build host.714. Compute the window the bandwidth-delay product asks for and compare it72 with the configured window, rounding the requirement up because a73 partial unit still occupies the link.745. Compute the worst case delivery time the retry limit allows and the75 residual loss probability it leaves.766. Where the residual misses the target, report the attempt count that77 would reach it, found by multiplying attempt by attempt.787. Put the chosen set through end-to-end simulation before it flies,79 covering the whole range of conditions the link is expected to meet,80 and read every run for the two signatures the settings exist to keep81 out: data the retransmissions failed to recover, and retransmissions82 the losses never called for.838. Report any parameter that is not commandable as a finding in its own84 right, whatever its value, and summarise the recommended set so an85 operator can uplink it.8687## Obligations8889| Item | Step |90|---|---|91| ECSS-E-ST-50C Rev.2 5.6.13.5a | 7 |9293## Pitfalls9495- Setting the timeout to the round trip alone. The far end still has to96 notice the unit and build an acknowledgement, and the path still has97 jitter; both sit on top of the propagation.98- Treating a short window as a timing problem. It costs throughput and no99 timer setting recovers it; the window is the parameter that moves.100- Quoting a retry limit without the worst case it implies. A generous101 limit can push the delivery of a single unit past the contact window,102 and the retransmissions then continue into a pass that is already over.103- Reporting the residual loss and calling the configuration adequate. A104 configuration that meets the residual and cannot be changed in flight105 still fails the clause.106- Tuning one parameter and re-reporting the whole set as sound. The107 timeout, the window and the retry limit trade against each other, so a108 changed value means the set is assessed again.109110## Behavior contract (gate 3)111112Parameter validation, the timeout floor, the bandwidth-delay window, the113worst case delivery time, the residual loss and the attempt count that114reaches a target, acceptance exactly at the timeout floor and the115commandability findings are exercised by the gate 3 contract test:116scripts/test_e50_arq_settings.py against117scripts/e50_arq_settings_logic.py (stdlib unittest, offline).118Run:119python3 scripts/test_e50_arq_settings.py120121## Compliance122123- ECSS standards are freely downloadable (ESA); cite the source and124 paraphrase per standards-map.yaml.125- compliance: STANDARDS-REF, gated: false.