Lesson 5 of 8 · ITASAT and system integration
ITASAT: make purchased and custom parts work together
8 minute lesson · 3 checks along the way
Your goal for this lessonExplain why an integrated spacecraft needs system-level verification even when individual components are available.
In this lesson 3 sections · 3 checks
Using archive links & definitions
Follow a linked name to explore its archive card. “Back to your lesson” brings you to the same part of the reading.
Words with a dotted underline open a short definition right here in the lesson.
Read & understand
A training project becomes a 6U spacecraft
ITASAT-1 was developed through ITA with INPE participation and a wider network of collaborators. The project began in 2005, changed toward a approach in 2013 and launched aboard Falcon 9 on December 3, 2018. Its flown 6U combined student training with technology demonstration. This history is a reminder to identify the relevant design version when comparing an early proposal with the hardware that eventually reached space.
ITA’s engineering account describes a mixture of commercial components and custom integration work. The payload set included a data-collection transponder, a GPS receiver, a camera and the DCX-2 communications experiment. The platform provided the power, data handling, orientation control and other services that these activities needed. A list of payloads establishes intended capabilities, while performance claims need the corresponding test or flight records.
Check 1 of 3
10 pointsUse the reading above. You can try again without losing points.
Read & understand
Buying a component does not buy integration
Commercial off-the-shelf hardware can reduce the amount a team must design from scratch. It also introduces interfaces that the team must understand and verify. Voltage levels, timing, startup sequences and software assumptions may differ between suppliers. The spacecraft is a connected system: a component that meets its own specification can still be unsuitable for the surrounding design or require an adapter and a revised operating procedure.
Consider a fictional camera that needs more electrical power during startup than during steady operation. A power budget based only on its steady value could appear acceptable while the real startup sequence resets another subsystem. Measuring the transient demand and testing the combined sequence would reveal more than separate demonstrations of the camera and power supply. This is an illustrative integration problem, not a claim about an ITASAT camera failure.
Verify the complete activity
Original teaching diagram. Select components. Check interfaces. Test combined loads. Send a real command. Trace the data path. Decode the result. A proven component is evidence to evaluate, not a guarantee for every new application.
Open full-size diagram in a new tab: Verify the complete activityCheck 2 of 3
10 pointsUse the reading above. You can try again without losing points.
Read & understand
Test the mission’s route from command to result
An follows an intended activity through the assembled system. For a fictional image request, that could include a ground command, onboard interpretation, pointing readiness, image capture, storage, transmission and ground decoding. Every connection matters. A successful camera exposure alone does not demonstrate that operators can obtain the resulting image, just as a working radio does not prove that the stored file has the expected format.
ITA presents lessons learned about interfaces, assembly, software and mission operations as part of the project’s educational contribution. Readers should connect those lessons with specific configurations and evidence rather than assume that one flown component is automatically qualified for every future mission. Different thermal, electrical or operational conditions can require additional checks. ITASAT shows why systems engineering remains central even when a spacecraft is relatively small and many parts already exist.
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: ITA: ITASAT-1 design and lessons learnedInstitutional engineering account describes the 6U spacecraft, payloads, integration and 2018 launch. Conflicting mass and current-status statements are not used as settled facts.
- Read: NASA: product realizationCompare the explanation and its assumptions with the worked example in this lesson.
- Read: NASA: system design processesCompare the explanation and its assumptions with the worked example in this lesson.