• Created by Unknown User (adamsa@mit.edu), last modified by Unknown User (salazarj@mit.edu) on Oct 06, 2018 10:47

Overview

The payload for the Space Shot engages with the local community and collects data on the rocket flight. See data types in requirements below. 

Primary scope items include a multi-faceted Data Acquisiton Package and an outreach payload with mass and local collection of signages to send beyond the Karman Line. 

 

Requirements (as of 9/23/2018, not firm)

Outreach Payload

  1. Cargo and enclosure
    1. Post cards
    2. SD card 
    3. Screen for altitude and photo file display
    4. Camera
      1. Must have view of at least  the post cards and SD card
  2. Hardware Form Factor
    1. Fits 4" airframe diameter
    2. Concentric frame
    3. Structures for bulkhead attachment
  3. Operational
    1. 2 hours of on-pad life
      1. Battery 
    2. Altimeter alerts for target altitude 

Instrumentation Package

  1. Data Type
    1. Temperature
      1. at least 1 under NC tip, at least 4 on surface
      2. at least 2 on the cylindrical walls
      3. Thermocouples must operate at >800K (930 F)
    2. Load
      1. Load cells on chutes
      2. Strain gauges on tubes
    3. Accelerometer
      1. Pyxida's IMU mounted on payload frame
    4. Vibrations 
      1. Airframe (region near NC)
      2. Piezoelectric based sensor mounted on payload frame
    5. Spine Axial Load Experiment
      1. Fabric sensors or alternative
    6. Fin Deflection (Fin Flutter PT. 2)
      1. 1 Camera for each fin, mounted on payload frame
  2. Data Rate & Storage
    1. Temperature 10-100Hz
      1. at least 1 under NC tip, at least 4 on surface
      2. at least 2 on the cylindrical walls
    2. Load - 100 Hz
    3. Accelerometer - O(10kHz)
    4. Microphone
    5. Piezos
    6. etc.
  3. Hardware Form Factor
    1. Does not affect recovery system deployment
    2. Thermocouple map onto nose cone
      1. Interface w/ Structures for NC geometry
    3. Length limit 10"
      1. Set by NC space for 1st-stage only descope
    4. TBD architecture of S2 with IP
  4. Operational
    1. 2 hours of on-pad life
      1. Data Storage
      2. Thermal 
      3. Battery life
      4. Acceptable sensor drift
      5. Remote Arming via Pyxida
    2. Relay data to Pyxida
    3. Integration time < 1/2 hour

Tests Based on Requirements

Requirement 1: 

  • Bench test w/ sensors running 
  • Life test: 2 hrs. of "on pad" simulated with hardware
    • Data Storage
    • Thermal 
    • Battery life
    • Acceptable sensor drift
    • Remote Arming

Requirement 2: 

  • Bench test & life test (see req. 1)

Requirement 3: 

  • CRIMP

Requirement 4: 

  • Life test (see req. 1)
  • CRIMP

 

 

 

  • No labels