1. The adapter they had to build twice
Jim Lovell and Jeffrey Kluger’s Lost Moon returns as the recalled work because the Apollo 13 crew built their CO2 adapter once under pressure, but on the ground it would have been built, tested, and rebuilt until it worked every time. A good test matrix is the list of conditions under which the adapter, or the payload, must work every time. The matrix is not exhaustive; it is the set of combinations that expose the most dangerous uncertainties.
This entry defines the payload integration and operation test matrix.
2. Payload selection
The test needs representative payloads, not flight hardware. For the desktop, three proxy payloads are enough to cover the main interface risks:
- Simple sensor: low power, low data rate, intermittent operation. Represents the majority of small hosted payloads.
- High-rate compute module: high power, high data rate, sustained operation. Tests thermal, power, and data path limits.
- Mechanical actuator: a small motor, valve, or print head that draws variable current and creates transient loads. Tests inrush, EMC, and command sequencing.
These proxies are not mission payloads. They are stand-ins that exercise the interface layers defined in Entry 694.
3. Integration test matrix
The integration tests verify that the payload connects to the desktop safely:
| Configuration | What it tests |
|---|---|
| Mechanical fit and alignment | Mounting envelope, bolt pattern, keep-out, center of mass. |
| Electrical mating | Connector pinout, voltage rails, current limits, grounding, inrush. |
| Power-on sequence | Correct sequencing, no bus collapse, no back-feeding. |
| Thermal soak | Steady-state temperatures under operating and survival conditions. |
| Vibration and shock | Launch loads and release transients with payload installed. |
| EMC | Conducted and radiated emissions and susceptibility. |
| Safe mode | Payload behavior when the desktop commands a shutdown or safing. |
4. Operation test matrix
The operation tests verify that the platform can command and schedule the payload:
| Configuration | What it tests |
|---|---|
| Basic command and telemetry | Platform can turn payload on, off, and read status. |
| Scheduled operation | Payload executes at a requested time within constraints. |
| Power-limited scheduling | Scheduler defers or reduces payload activity when battery is low. |
| Thermal-limited scheduling | Scheduler defers activity when predicted temperature exceeds limit. |
| Pointing conflict | Scheduler resolves or rejects requests that conflict with attitude needs. |
| Multiple payloads | Platform shares resources between two payloads without violation. |
| Fault injection | Payload fault triggers safe shutdown and operator notification. |
| Autonomous override | Safety-critical condition overrides the scheduled payload activity. |
5. Environment conditions
Each test configuration should be exercised under representative conditions:
- Nominal: standard power, thermal, and communication state.
- Eclipse: reduced solar input, battery-only operation.
- Hot case: maximum solar heating, high radiator load.
- Cold case: minimum solar heating, survival heater load.
- Ground silence: no real-time ground contact, forcing autonomous decisions.
- Degraded bus: one subsystem constrained, such as reduced power or data storage.
6. What this changes
- The test matrix combines payload proxies, integration checks, operation scenarios, and environmental conditions.
- The matrix is designed to find interface and autonomy faults before they reach orbit.
- The next entry will define success and failure criteria for each test.