AIT FlatSat Plan

FlatSat Test Plan

The following diagram and table describe the FlatSat testing (block 2 in the functional flow diagram). FlatSat testing will be performed on subsystem Engineering Models (EM) or Flight Models (FM). The FlatSat will consist of components connected together by harnessing, with no structural components unless they are integral to the component (ie. battery saddle). The only exception to this is for testing the solar panel and antenna deployment mechanisms. To test the deployment mechanisms we will connect two half-modules into the FlatSat, the half modules that contain the antenna and solar array deployment mechanisms. These half modules will have only the parts necessary to test the deployment installed.

As subsystem EMs successfully complete verification activities, they will be integrated into an EM FlatSat. The EM FlatSat will serve as an initial subsystem interface test, allowing for early fault detection. Additionally, this FlatSat will allow us to test software as flight hardware undergoes testing and integration activities. After Iris is launched, the EM FlatSat will be used by the team to test software updates before sending it to Iris.

The first diagram identifies the functional flow of the FlatSat testing on subsystem Flight Models, while the table includes more details of the test steps followed. Note that while the power subsystem (including the flight battery) will be connected into the FlatSat in order to test the battery heaters and thermistors, for the entirety of the FlatSat testing the power to the components will be provided by an external power umbilical. The Power Control Unit (PCU) will control the switching and supply of power, but the power itself will come from the umbilical rather than the flight battery.