| 1. | Identify which sensors are in need of simulation; which can be left alone. | —/ Complete /— | |
|---|---|---|---|
| 2. | Research on currently existing HIL testing setups; add documentation. | Notes: |
—/ Complete / — |
| 2.a. | Research specific CubeSat systems that can be used to test com protocols | Notes: Refer to Day 1. Currently advancing project status by ideating implementation for sensor emulation | —/ Complete /— |
| 2.b. | Ideate Sensor Emulation Implementation | Notes: Understanding of system architecture is required, therefore adding additional documentation to HIL Test Setups. | —/ Complete /— |
| 3. | Develop high level design of the HIL setup. | —/ Complete /— | |
| 4. | Determine Boards and Modules for HIL | —/ Complete /— | |
| 5. | Research Possible Testing Frameworks | Notes: Frameworks must allow testers to easily make tests using high level logic | —/ In Progress /— |
| 5.a. | Research OpenHTF | —/ Complete /— | |
| 5.b. | Research GoogleTest | —/ In Progress /— |
Figure 1: Firmware Hardware Interactions
Figure 2: FlatSAT reference image of a general HIL architecture
For HIL system architectures, the EGSE essentially stimulates the sat’s response to an environment change. For example, if we take a look at the FlatSat hardware / peripherals shown in figure 2, to stimulate the Power main bus, EPS emulation is added, connected via power ports to the main bus. Following this, sat response to the stimulates environment by altering data inputs can be measured. The purpose of our current HIL setup can be derived from this in a more selective manner.
Selected Sensors for Simulation: