Test

EM FlatSat Test Plan and Procedure

Test Summary

FM FlatSat Test Plan and Procedure

Test Summary

Procedures

1-Battery/ESP/ADCS/CDH Interface

2-ESP/ADCS (Stand-In)/CDH Interface

3-ESP/COMMS Transceiver (Stand-In) Interface

4-CDH/Payload Stand-In Interface

5-Flight Software Test

5.1-Flight Software Command Handling (Power)

5.2-Flight Software Command Handling (ADCS)

5.3-Flight Software Command Handling (COMMS Stand-In)

5.4-Flight Software Command Handling (Payload Stand-In)

EM FlatSat Test Plan and Procedure

Start Date:

October 7, 2024

End Date:

November 8, 2024

Part Name:

Application:

Integration of EM Hardware

Quantity:

Test Summary

Item

T5.1

T5.2

Test Item

Battery/ESP/ADCS/CDH Interface

ESP/ADCS (Stand-In)/CDH Interface

Flight Software Test

Flight Software Command Handling (Power)

Flight Software Command Handling (ADCS)

Test Result

Successful

Details

FM FlatSat Test Plan and Procedure

Start Date:

End Date:

Part Name:

Application:

Integration of FM Hardware

Quantity:

Test Summary

Item

T5.1

T5.2

T5.3

T5.4

Test Item

Battery/ESP/ADCS/CDH Interface

ESP/ADCS (Stand-In)/CDH Interface

ESP/COMMS (Stand-In) Interface

CDH/Payload Stand-In Interface

Flight Software Test

Flight Software Command Handling (Power)

Flight Software Command Handling (ADCS)

Flight Software Command Handling (COMMS)

Flight Software Command Handling (Payload)

ESP/COMMS Interface

Test Result

Details

Procedures

1-Battery/ESP/ADCS/CDH Interface

Item

Test Item

Battery Pack, ESP Board, ADCS Board, CDH Board

Test Specification

Test safe charging of the power board to the expected voltage and maintain power throughout the FlatSat. Test safe charging of ADCS and CDH boards to the expected voltage.

Judge Criteria

EPS board draws 6.5 V (set by power supply) from the battery pack after 100s of hold mode.

ADCS and CDH receive the same amount of power that is provided by the battery to the Power board.

Test Period:

Test Equipment:

Major Problem:

Warning:

Recommendation:

November 8, 2024 (1 day)

Battery Pack, Power Board, Multimeter, Logic Analyzer

None

Raw Data:

Board Assembly:

Place the power board, ADCS board, and CDH board on the P1, P2, and P3 spots on the FlatSat board respectively. Use M2 screws to secure the boards on the assembly. Place the battery saddle above the P1 spot on the FlatSat board. Connect Power hardware to the ADCS and the ADCS hardware to CDH using the FlatSat connectors.

Test Attempt

Hold Duration

100s

Drawn Voltage (Power)

6.544V

Drawn Voltage (CDH)

6.535V

Drawn Voltage (Power)

6.533V

Comments

Refer to image below for hold mode.

It is apparent that the power is high on the Power board (channel 4), but the functionality of the other boards (in this case SPI on CDH) is activated after 100 seconds.

Detailed Instructions:

Connect the battery pack to the battery terminals.

Connect the logic analyzer to Ground and VCC pins to measure the hold duration.

At this point the protection circuit will not allow current to pass. Connect a 7.2V power supply to battery terminals J21 and J20 to charge the batteries and make the protection circuit work normally.

Now the ground leg needs to get connected as it is inhibited through the ground leg inhibit circuit. To do this, connect the jumper between J35 and J37. Now the 3.3V and 5V auxiliary power buses are powered and the board is ready.

Remove the jumper between J34 and J36. Wait for 100 seconds.

Measure the output voltage of the power bus using a multimeter. The voltage should measure between 5V to 7.2V.

To discontinue power to the board, remove the jumper connecting J35 and J37, connect the jumper between J34 and J36, remove the power supply to battery terminals J21 and J20, and disconnect the battery.

2-ESP/ADCS (Stand-In)/CDH Interface

Item

Test Item

ESP Board, ADCS Stand-In, and CDH Hardware

Test Specification

Test proper interface and connection of ESP board to the ADCS unit and ADCS unit to the CDH unit. Test if both ADCS and CDH properly charge up and have functional SPI interface.

Judge Criteria

-ADCS and CDH draw 6.95 V (power supply set voltage)

-SPI interface is functional between CDH and stand-in ADCS hardware

Test Period:

Test Equipment:

Major Problem:

Warning:

Recommendation:

November 8, 2024 (1 day)

Battery Pack, Power Board, ADCS Stand-In , CDH Board, Multimeter, Logic analyzer, Power supply

Interfacing Simulink on Arduino and Arduino SPI to CDH board (Resolved)

Arduino does not have a default slave SPI setting. It will have to be set up manually.

None

Raw Data:

Board Assembly:

Follow the board assembly instruction from T1. Place the ADCS stand-in in the space between P1 and P3 spots. Connect the stand-in to CDH hardware and logic analyzer as explained in the Detailed Instructions.

Test Attempt

ADCS Input Voltage

6.85 V

CDH Input Voltage

6.86 V

SPI Interface

SPI protocol is functional both ways.

Comments

command "0x16 is received from CDH and reflected back in ADCS response followed by data ("12345"). SPI is only activated 100s after the power supply is turned on, complying with the 100s hold mode.

Detailed Instructions:

Connect the ESP hardware to the ADCS hardware through the main connector.

Connect the ADCS hardware to the CDH hardware through the main connector.

Connect the available SPI pins on CDH board to the corresponding SPI pins on the Arduino (ADCS stand-in) as showed in the image bellow using the provided connector. Connect the ground of the Arduino to a ground pin on CDH board.

On the breadboard, connect the SPI pins drawn from the Arduino to the first 4 channels of the logic analyzer. Connect the ground of the logic analyzer to the same ground as the CDH and Arduino.

Power up the board (using the detailed instructions from T1).

Use a multimeter to measure the input power to the ADCS and CDH hardware.

Test SPI interface between ADCS and CDH modules. Note that for this test, the testADCSDriver test function is running on the CDH, which keeps asking for gyro measurements from ADCS by sending the command "22" or "0x16". In response of this command from CDH, ADCS shall repeat the "0x16" command followed by 6 digits of its reading (in this case 123456)

3-ESP/COMMS Transceiver (Stand-In) Interface

Item

Test Item

ESP Board and COMMS Transceiver Stand-In

Test Specification

Measure the input power to the COMMS stand-in and make sure the proper message is being transferred both ways on the CAN bus.

Judge Criteria

-COMMS stand-in draws TBD V and TBD A and charges up

-CAN interface is functional between ESP and COMMS hardware

Test Period:

Test Equipment:

Major Problem:

Warning:

Recommendation:

Battery Pack, ESP Board, COMMS Stand-In, Multimeter, Logic Analyzer

Raw Data:

Board Assembly:

Follow the board assembly instruction from T1. Place the COMMS stand-in in the space between P1 and P3 spots. Connect the stand-in to ESP hardware and logic analyzer.

Test Attempt

Voltage Drawn

CAN Interface

Comments

Detailed Instructions:

Connect the ESP hardware and COMMS stand-in through the provided connector.

Power up the board (using the detailed instructions from T1).

Use a multimeter to measure the input power to the COMMS stand-in.

Test CAN interface between Power and COMMS module.

4-CDH/Payload Stand-In Interface

Item

Test Item

CDH Hardware and Payload Stand-In

Test Specification

Measure the input power to the Payload stand-in and make sure the proper message is being transferred both ways on the CAN bus.

Judge Criteria

-Payload stand-in draws TBD V and TBD A and charges up

-CAN interface is functional between payload stand-in and CDH hardware

Test Period:

Test Equipment:

Major Problem:

Warning:

Recommendation:

Battery Pack, CDH Board, Payload Stand-In, Multimeter, Logic Analyzer

Raw Data:

Board Assembly:

Follow the board assembly instruction from T1. Place the Payload stand-in in the space between P3 and P5 spots. Connect the stand-in to CDH hardware and logic analyzer.

Test Attempt

Drawn Voltage

CAN Interface

Comments

Detailed Instructions:

Follow the assembly in T1 to prepare the ESP, ADCS, and CDH hardware for interfacing.

Connect the CDH hardware and Payload stand-in through the provided connector.

Power up the board (using the detailed instructions from T1).

Use a multimeter to measure the input power to the payload stand-in.

Test CAN interface between CDH and Payload module.

5-Flight Software Test

Item

Test Item

Flight software

Test Specification

Making sure the flight software commands are delivered to each subsystem and get the appropriate response back.

Judge Criteria

T5.1 to T5.4 commands send and receive are successful

Test Period:

Test Equipment:

Major Problem:

Warning:

Recommendation:

November 8, 2024 (1 day)

Battery Pack, ESP Board, CDH Board, Multimeter, CDH JTAG programmer, Logic analyzer, Computer with Libero 2022.2 and SoftConsole V6.5, Secondary SPI device

None

Raw Data:

Board Assembly:

Follow the board assembly instruction from T1.

Test Attempt

T5.1

Successful

T5.2

Successful

T5.3

T5.5

Comments

Test attempt 1 was done for EM. Payload and COMMS stand-ins where not included in this attempt.

Detailed Instructions:

Follow instructions from T1.

5.1-Flight Software Command Handling (Power)

Item

T5.1

Test Item

Flight software commands to Power

Judge Criteria

The command to power is sent successfully through CAN.

Raw Data:

Test Attempt

CAN Communication

successful

Comments

"hello word" command sent successfully over CAN as shown below.

Detailed Instructions:

Manually send "hello world" from power to CDH over CAN

5.2-Flight Software Command Handling (ADCS)

Item

T5.2

Test Item

Flight software commands to ADCS

Judge Criteria

The command to ADCS is sent successfully and responds from CDH is received

Raw Data:

Test Attempt

SPI Communication

successful send and receive

Comments

"0x18" command sent successfully over SPI and reflected in the response from ADCS as shown below.

Detailed Instructions:

manually send command "0x18" (ADCS_SELECT_SS4) to ADCS.

5.3-Flight Software Command Handling (COMMS Stand-In)

Item

T5.3

Test Item

Flight software commands to COMMS stand-in

Judge Criteria

The command to COMMS stand-in is sent successfully

Raw Data:

Test Attempt

Criteria 1

Comments

Detailed Instructions:

5.4-Flight Software Command Handling (Payload Stand-In)

Item

T5.4

Test Item

Flight software commands to payload stand-in

Judge Criteria

The command to payload stand-in is sent successfully

Raw Data:

Test Attempt

Criteria 1

Comments

Detailed Instructions:

Page updated

Google Sites

Report abuse