Lesson 3 of 6 · Command sequences
Send a sequence the spacecraft can execute
8 minute lesson · 3 checks along the way
Your goal for this lessonExplain command dependencies, time conventions and confirmation of execution.
In this lesson 3 sections · 3 checks
Using archive links & definitions
Words with a dotted underline open a short definition right here in the lesson.
Read & understand
A command is part of a planned behavior
A command tells a spacecraft to perform an action or change a setting. A sequence orders commands so their dependencies and timing produce an intended result. Turning on a camera, waiting for readiness, pointing, exposing and storing data are different actions; a successful individual command does not guarantee that the complete sequence achieves its purpose.
Ground teams review the sequence against the spacecraft configuration and available resources. A rehearsal or simulation can expose conflicts before upload. The version sent to the spacecraft must be identifiable so the team can compare expected behavior with the events actually reported.
Check 1 of 3
10 pointsUse the reading above. You can try again without losing points.
Read & understand
Choose the clock deliberately
Commands may use specified execution times or other mission-defined triggers. The time convention matters, especially when communication takes minutes. An event observed on Earth happened earlier at the spacecraft. A sequence-of-events record connects onboard activity, ground contacts and the corresponding times rather than treating them as simultaneous.
In a fictional case, one-way light time is four minutes and processing time is ignored. A command transmitted at 10:00 cannot arrive before 10:04. An immediate acknowledgement sent then cannot reach Earth before 10:08. This minimum round trip is a physical delay, not evidence that a controller typed slowly.
Follow a command and its reply
Original teaching diagram. OUTBOUND. 10:00 transmission. 10:04 earliest receipt. INBOUND. 10:04 immediate reply. 10:08 earliest Earth receipt. Four-minute one-way light time; processing delays omitted in this example.
Open full-size diagram in a new tab: Follow a command and its replyCheck 2 of 3
10 pointsUse the reading above. You can try again without losing points.
Read & understand
Distinguish receipt, execution and outcome
A command accepted into memory has not necessarily executed. A reported execution has not necessarily achieved the physical result intended. For example, software might issue a deployment command while a mechanism fails to move. The team needs appropriate state or sensor evidence to establish the outcome.
Build a fictional checklist with three entries: the correct sequence was received, the intended events occurred at the expected times, and measurements support the desired physical state. These entries prevent a common reasoning shortcut in both operations and software: mistaking successful message delivery for successful completion of the whole task.
Check 3 of 3
10 pointsUse the reading above. You can try again without losing points.
Put it together
Your lesson progress
Each check connects to a part of the story. Complete all 3 to earn your 25-point lesson bonus.
Explore further · Optional
Go to the source
Explore the evidence behind this lesson. These optional readings and videos open in a new tab.
- Read: NASA: cruise operationsUse the operational principles in this historical training text. Dated vehicle descriptions and forecasts are not a statement of current mission status.
- Read: NASA: telecommunicationsUse the operational principles in this historical training text. Dated vehicle descriptions and forecasts are not a statement of current mission status.