Skip to main content

Report Quasi Static Load Qualification Test

SubjectDescription
Testing ModelEQM unit
Product DescriptionQuasi-Static Load Report
Test ReasonTo make sure that the CubeSat's structure can withstand the flight environment and ensure structural integrity.
  • Issue date: <Insert Date>
  • Approved by: <Insert Name>
  • Responsible Test Engineer: <Insert Name>

Quasi Static Load Qualification via Sine Burst

Testing Equipment

  • EQM unit
  • EQM adapter
  • Vibration table (from Maxon)
  • Vibration sensors

Purpose

  • To make sure that the CubeSat's structure can withstand the flight environment and ensure structural integrity.

Test Method

  • The test is inspired by the PUG of SpaceX
  • The vibration sensors shall be mounted to the EQM. There places is defined on the Overview Structural Testing page.
  • The EQM unit shall be mounted to the vibration table, with the EQM adapter as the interface.
  • Duration: 1h per axis conducted on all axis
  • The axial and lateral load factors should be taken from table 6-4 in the PUG.
  • The test parameters as well as necessary criteria are mentioned in table 6-5 of the PUG.
  • As soon as all the requirements are checked, the EQM unit will be exposed to 5 cycles of sine bursts with an input frequency < 2/3 of the CubeSat's first mode frequency.

Check Condition and Requirements

  • The mass difference between the EQM and the flight model should not exceed 2% (table 6-5 of PUG).
  • Check that the vibration sensor is recording and working properly.
  • Check that the connection between vibration table and EQM adapter, as well as the connection between EQM adapter and EQM are rigid, to ensure proper transfer of the load.
  • After the sine burst cycles, manually inspect the EQM for any damages.

Test Results

<Describe the results of the test in a short fashion>

Test Judgement

  • Measured acceleration should meet target acceleration and the EQM unit should remain fully intact.

Appendix

Photo of testing

<Insert picture of the exact testing configuration>

Testing data

<Insert a table or diagram of the exact output of the test (without intepretation)>