preliminary design review - cosgc home 2013/te… · – system/project level requirement...

75
2013 PDR WVU Rocketeers Preliminary Design Review West Virginia University Alex Bouvy, Ben Kryger, Marc Gramlich 11-12-2012 1

Upload: others

Post on 14-Jun-2020

0 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

WVU Rocketeers Preliminary Design Review

West Virginia University Alex Bouvy, Ben Kryger, Marc Gramlich

11-12-2012

1

Page 2: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

PDR Presentation Content

2

•  Section 1: Mission Overview –  Mission Overview –  Theory and Concepts –  Concept of Operations –  Expected Results

•  Section 2: System Overview –  Functional Block Diagram –  Drawings/Pictures of Design –  Critical Interfaces (ICDs?) –  System/Project Level Requirement Verification Plan –  User Guide Compliance –  Sharing Logistics

Page 3: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

PDR Presentation Contents

• Section 3: Subsystem Design – Organizational Chart – Structures – Power – Science – Command and Data Handling – Software – Other

3

Page 4: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

PDR Presentation Contents

• Section 4: Initial Test/Prototyping Plan • Section 5: Project Management Plan

– Schedule – Budget – Availability Matrix – Team Contact info

4

Page 5: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

Mission Overview Ben Kryger

5

Page 6: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

Mission Overview: Mission Statement

6

•  Mission statement: Develop a payload which will measure the following properties of the space environment (up to 160 km) during the RockSat-X flight.

–  Plasma density/frequency –  Magnetic field –  Flight dynamics –  Magnetic effects on ferrofluids in microgravity –  Eject a standalone picosatellite. The satellite will house a basic payload

consisting of IMU and magnetometer, as well as a transceiver to transmit data back to earth.

•  Goal: To measure and analyze data from the flight, and compare the results

to known atmospheric models. Track the ejected picosatellite to obtain measurements as it descends to earth.

Page 7: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

Mission Overview: Theory and Concepts

7

•  Plasma conditions continuously change in the ionosphere with altitude and time of day. At these given times, the plasma fields resonate at different frequencies. The experiment will compare the instantaneous plasma density and frequency distribution to current atmospheric models.

•  Earth’s magnetic field decreases as a function of distance from the center of the earth. The magnetic field reflects and traps many charged particles. Measuring field intensity can yield information required to accurately model this phenomena.

•  Comparison between these measurements and current models will show

if assumptions made in these models hold up to an extent that they can be accurately used in future atmospheric applications.

Page 8: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

Mission Overview: Theory and Concepts cont.

•  Ferrofluids are liquids that respond to magnetic fields. They are typically composed of iron particles suspended in a solvent (usually oil based). In near zero g conditions, it becomes difficult to control how a liquid is oriented in a container. Assuring the fluid remains in a certain location is useful in fuel tanks experiencing zero gravity. The goal is to use an electromagnet in order to sustain the location of the fluid within it’s container.

8

Page 9: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

Mission Requirements: Mission Objectives

9

•  A payload shall be constructed from which measurements can be made and viable science data obtained.

•  The power block designed shall distribute power to each and every subsystem, and each and every subsystem shall be powered on.

•  The science data obtained should improve upon current data from previous projects.

•  The full payload shall fit on a single RockSat-X deck.

•  The system shall survive the vibration characteristics prescribed by the RockSat-X program.

Page 10: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

Mission Requirements: System Level Objectives: Flight Dynamics (FD)

10

•  A system shall be developed to measure the dynamics of the rocket flight, including acceleration, pitch, yaw, and roll.

Page 11: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

Mission Requirements: System Level Objectives: Ferrofluid Experiment (FFE)

11

•  A system shall be developed such that a ferrofluid in a closed container can be monitored via external camera.

•  The containment vessel shall be designed/selected to prevent possible spills/leaks of the ferrofluid.

•  The camera system implemented shall properly record video/take pictures on command.

Page 12: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

Mission Requirements: System Level Objectives: Radio Plasma Experiment (RPE)

12

•  A system shall be developed to measure the density of a low-energy plasma in the space environment.

•  Both a MHz and GHz antenna shall be designed and implemented to properly transmit corresponding MHz and GHz waves.

•  A functional Langmuir Probe shall be designed and implemented.

•  The antennas and probe should be interfaced to the RockSat-X deck in such a manner as to provide for optimal conditions for measurements to be made.

Page 13: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

Mission Requirements: System Level Objectives: Picosatellite Experiment (PSE)

13

•  A picosatellite shall be developed to house a basic payload, as well as a transceiver to transmit telemetry.

•  A transmission protocol shall be implemented to dictate transmission format.

•  An ejection cylinder shall be designed to properly eject

the picosatellite upon command.

Page 14: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

Mission Requirements: Minimum Success Criteria

1.  The payload shall conform to the requirements set forth in the RockSat-X User Guide

2.  The system shall measure the density of a low-energy plasma throughout the flight at no less than 50Hz.

3.  The system shall measure data from each and every inertial sensor throughout the flight at no less than 50Hz.

4.  The system shall observe the effects of ferrofluids in the presence of an electromagnet intermittently throughout flight, accumulating no less than 2 total minutes of video footage.

5.  The payload shall eject a picosatellite to produce a rapidly decaying orbit. Telemetry data shall be received from the picosatellite.

6.  The system shall save high resolution data on a hard disk. 7.  The system shall transmit acquired data through WFF-provided

telemetry for data assurance. 14

Page 15: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

15

Mission Overview: Expected Results: Plasma

•  Expect at least one or two peaks: –  Plasma frequency –  Gyrofrequency –  Other frequencies possible (upper-hybrid frequency)

•  Gyrofrequency varies little with altitude, plasma frequency significantly:

0.00E+00

5.00E+05

1.00E+06

1.50E+06

2.00E+06

2.50E+06

3.00E+06

3.50E+06

4.00E+06

4.50E+06

0 20 40 60 80 100 120 140 160

Freq

uenc

y (H

z)

Altitude (km)

Frequency Variability

f_ce (Hz)

f_pe (Hz)

f_uh (Hz)

Page 16: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

•  The observed magnetic field is expected to decay following an inverse cube law as a function of distance from the Earth.

•  Note: Earth’s magnetosphere is dynamic and should not be overgeneralized by

an inverse cube law. However, considering an expected altitude maximum of 160 km, standard dipole magnetism models are expected.

16

Mission Overview: Expected Results: Magnetic Field

Page 17: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

Mission Overview: Expected Results: Ferrofluid

•  Under the influence of a strong magnetic field, it is expected that the magnetic fluid remain oriented towards the electromagnet throughout the duration of the flight.

•  Fluid sloshing should be reduced in comparison to the non-magnetic control fluid.

•  The control fluid is expected to move freely in it’s container.

17

Page 18: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

18

h=0 km (T=0) Launch

h=160 km (T=2.8 min) Apogee Nose Cone Separation Picosatellite Ejected

h=10.5 km (T=5.5 min) Chute deploys

h=0 km (T=15 min) Splashdown

RockSat-X 2013: Concept of Operations

h=10.5 km (T=5.78 min) Experiments Power Off

h=52 km (T=.5 min) End of Malamute Burn

h=0 km (T=-2 min) All systems on, begin data

acquisition

Page 19: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

System Overview Alex Bouvy

19

Page 20: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

Design Overview

20

•  For most experiments (Flight Dynamics, Radio Plasma) heritage elements from previous WVU RockSat-C flights will be integrated into this year’s design.

•  These experiments will go largely unchanged.

•  The remaining Ferrofluid and Picosatellite Experiments will be implemented from scratch.

Page 21: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

Functional Block Diagram Picosatellite  Ejection  

 

 

 

 

 

 

 

 

uController  System  

 

Langmuir  Experiment  

 

 

 

 

Flight  Dynamics  

 

 

 

 

Radio  Plasma  Experiment  

 

 

 

 

 

Wallops  Power  &  Telemetry  lines  

 

GSE-­‐1  

GSE-­‐2  

TE-­‐R  

TE-­‐NR1  

TE-­‐NR2  

TE-­‐NR3  

Parallel  Bits  1-­‐8  

 

Power  Block  

Langmuir  Board  

IMU  

Z-­‐Accelerometer  

Magnetometer  

uController  

Ejection  Cylinder  

Langmuir  Probe  

SD  Card  Power  

Distribution  

LEGEND  Power:    Red  

Digital  Signal:  Gold  

Analog  Signal:  Olive  

Parallel  Bits:  Lavendar  

RPE  Board  

Antenna  

Page 22: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

FBD – Mechanical Diagram (rough)

22

Power

LP

RPE

FD

FFE

RPE LPE

Makrolon Layer 1 (PCBs)

Makrolon Layer 2 (Exp. Apparatus)

PSE

Page 23: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

Design Overview: SolidWorks Rendering v1

23

PSE

FFE RPE

Page 24: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

Design Overview: Multi View Drawings

24

Page 25: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

Critical Interfaces: PCBs/RockSat Deck

•  Brief Description –  All of the PCBs for each subsystem must be attached to the RockSat

deck. The PCBs must withstand at least 25 Gs of quasi-static loading in all three axes with possible impulses of approximately 50 Gs in the Z (longitudinal) axis.

•  Possible Solution

–  In the past, the PCBs have been loosely mounted to makrolon plates using aluminum machine screws. Additionally, plastic risers were implemented to mitigate stress.

25

Page 26: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

Critical Interfaces: uC/PSE

•  Brief Description –  The microcontroller must be connected to the ejection cylinder

of The PSE in such a manner to allow autonomous ejection.

•  Possible Solution –  One potential fix is to make use of an SSR (as used in some

legacy subsystems) to allow triggering of the event.

26

Page 27: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

Critical Interfaces: FFE/RockSat Deck

•  Brief Description –  The ferrofluid experiment, consisting of a camera and a

sealed vessel containing a ferrofluid, must be mounted to the RockSat-X Deck. The container must be mounted in such a manner as to avoid leaks.

•  Possible Solution

–  In previous years, containers filled with liquid have been successfully mounted through a portion of a makrolon plate with no incident. This approach may again be utilized.

27

Page 28: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

Critical Interfaces: PSE/RockSat Deck

•  Brief Description –  The ejection cylinder must have a clear path to space free of

obstructions in order to launch the satellite. –  The cylinder must be securely mounted in order to properly

eject the picosatellite.

•  Possible Solution –  In order to securely fasten the ejection cylinder, metal set

screws can be utilized to lock the cylinder into place.

28

Page 29: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

Requirements Verification (1 of 2)

29

Requirement Verification Method Description

The full system shall fit on a single RockSat-X deck Inspection Visual inspection will verify this

requirement

The sytem shall survive the vibration characteristics prescribed by the RockSat-X program.

TestThe system will be subjected to these vibration loads in June during testing week.

FFE: The containment vessel shall be designed/selected to prevent possible spills/leaks of the ferrofluid.

Test

The system will be subjected to these vibration loads in June during testing week. Additionally, thorough in-house testing will occur prior to this.

FFE: The camera system implemented shall properly record video/take pictures on command.

Demonstration The camera system will be demonstrated to verify proper operation.

Page 30: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

Requirements Verification (2 of 2)

30

Requirement Verification Method Description

RPE: Both a MHz and GHz antenna shall be designed and implemented to properly transmit corresponding MHz and GHz waves.

Demonstration

System will be demonstrated to verify proper transmission and propagation of waves using such devices as an oscilloscope and a spectrum analyzer.

RPE: A functional Langmuir Probe shall be designed and implemented.

Demonstration Proper operation of the Langmuir Probe will be demonstrated in a lab setting.

RPE: The antennas and probe should be interfaced to the RockSat-X deck in such a manner as to provide for optimal conditions for measurements to be made.

Analysis

The probe and antennas should be placed in the most functional position allowed by the envelope of other subsystems. CAD modeling will be used as a planning aid to most efficiently place subsystems.

PSE: The ejection cylinder shall properly eject the picosatellite upon command.

Demonstration System will demonstrate that the picosatellite is ejected on command.

Page 31: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

RockSat-X 2013 User’s Guide Compliance

Preliminary Mass Budget

31

Subsystem/  Component Mass  (lb)

RPE 2 Total  Mass  Alotted  (lb)FFE 1 15±0.5FD 0.5PSE 3 Total  Mass  (lb)uC 0.25 10

Power  Block 0.25Makrolon/Deck 2

Other 1

Page 32: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

RockSat-X 2013 User’s Guide Compliance

Timed Event Lines: –  One timed event line will be used to time the ejection of our picosatellite.

ADC Lines:

–  The 5 allotted ADC lines for our team will be used for the RPE subsystem.

Parallel bits: –  The 8 parallel bits allotted will monitor the status of each of our

individual subsystems. Asynchronous line:

–  Our asynchronous line will be used for RS-232 communications to transmit data from our other subsystems (Flight Dynamics, etc.). Bit rate will be shared evenly with canister partner.

32

Page 33: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

Shared Can Logistics

33

Johns Hopkins University: •  Measure electron density using a dual frequency

GPS as well as observe effects on an aerogel container.

•  Communication will consist of team e-mails, phone calls, and occasional in-person meetings.

•  Payloads will be interfaced at WFF. Interfacing standards TBD.

Page 34: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

Subsystem Design Ben Kryger

34

Page 35: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

Organizational Chart

35

Project Manager Alex Bouvy

Systems Engineer Ben Kryger

Faculty Advisors Dimitris Vassiliadis

Marcus Fisher Sponsors WVSGC,

Dept. of Physics, Testing Partners ATK Aerospace

WVU CEMR

Safety Engineer Phil Tucker

RPE A. Bouvy (lead)

M. Gramlich

FFE B. Kryger (lead)

A. Bouvy

FD B. Kryger (lead)

A. Bouvy

Power Mgmt. M. Gramlich (lead)

A. Bouvy

Test Lead M. Gramlich

PSE A. Bouvy (lead)

B. Kryger

Page 36: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

Subsystem Design: Flight Dynamics (FD)

•  Critical components: –  Inertial Measurement Unit (IMU) –  Magnetometer –  Hi-Res Accelerometer –  Hi-Res Gyroscope

•  Approximate mass: .5 lb.

36

Page 37: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

Subsystem Design: Flight Dynamics (FD) Schematics

37

Page 38: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

Subsystem Design: Flight Dynamics (FD) Schematics

38

Page 39: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

Subsystem Design: Flight Dynamics (FD) Model

39

Page 40: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

Flight Dynamics

40

Page 41: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

Subsystem Design: Radio Plasma Experiment (RPE)

•  Critical components: –  Langmuir Probe –  GHz Antenna –  MHz Antenna

•  Approximate Mass: 2 lb.

41

Page 42: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

Subsystem Design: Radio Plasma Experiment (RPE) Schematics

42

Page 43: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

Subsystem Design: Radio Plasma Experiment (RPE) Schematics

43

Page 44: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

Subsystem Design: Radio Plasma Experiment (RPE) Model

44

Page 45: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

Subsystem Design: Radio Plasma Experiment (RPE) Model

45

Page 46: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

Subsystem Design: Radio Plasma Experiment (RPE) Model

46

Page 47: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

Subsystem Design: Ferrofluid Experiment (FFE)

•  Critical components: –  HD Camera

•  Prospective camera: GoPro HD Hero –  Ferrofluid vessel –  Potential full experiment enclosure depending on tested

durability. •  Prevent leaks •  Protect camera and vessels

•  Approximate Mass: 1 lb. •  Electrical configuration

–  GoPro (included in FD PCB) –  Backlit grid powered from Power PCB

47

Page 48: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

FFE

48

Page 49: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

Subsystem Design: Picosatellite Ejection (PSE)

•  Critical components: –  Ejection cylinder –  Payload (IMU/Magnetometer) –  Transceiver

•  Approximate Mass: 3 lb.

49

Page 50: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

Test/Prototyping Plan Alex Bouvy

50

Page 51: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

Test/Prototyping Plan: FFE

•  Experiment will be constructed and tested qualitatively. Vessel containing ferrofluid will be thoroughly tested to ensure no leaks will occur.

•  Experiment will also be tested to determine the magnetic field produced by the electromagnet with respect to distance from the magnet. –  Magnetometers can be calibrated using know magnetic

values. Earth’s magnetic field in Morgantown, WV= 0.5256 gauss. (source: www.ngdc.noaa.gov)

•  Additionally, the GoPro camera will be thoroughly experimented

with to demonstrate proper operation through autonomous use.

51

Page 52: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

Test/Prototyping Plan: FD

•  Board will be constructed and individual sensors tested as follows:

52

Sensor Testing  Plan

MagnetometerMagnetic  field  by  latitude  and  longitude  of  the  earth  is  known.  Magnetic    field  magnitude  for  Morgantown  is  known.  In  the  presence  of  no  magnet,  

the  magnetometer  reading  should  produce  this.

AccelerometerBy  moving  the  board  around,  increases/decreases  in  respective  directions  

for  the  accelerometer  should  be  observed.  Additionally,  at  rest  the  accelerometer  should  read  9.81  m/s^2

Hi-­‐Res  Accelerometer

Same  as  Accelerometer

Temperature Temperature  taken  with  respect  to  a  reference  temperature.

GyroscopeSimilar  to  the  approach  with  the  accelerometer,  changes  in  corresponding  

xyz-­‐directions  should  be  observed  when  moving  the  sensor.

Page 53: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

Test/Prototyping Plan: RPE

•  RPE will be tested to verify MHz and GHz transmissions are being made. This will include oscilloscope testing as well as spectrum analysis.

•  By placing conductive materials opposite the antennas, a varying received signal response can be observed.

53

Page 54: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

Test/Prototyping Plan: PSE

•  Upon completion, ejection cylinder will be tested to verify proper operation.

•  Picosatellite payload will be tested in the same fashion as FD sensors.

•  Picosatellite transmission will be tested on the ground to verify transmissions are made and received.

54

Page 55: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

Test/Prototyping Plan: Power System

•  Upon completion, the output voltages and amperages of the power system simply should be measured in order to verify proper operation. By measuring these values, it can be ensured that our power system will provide the calculated values to other subsystems.

•  Our power system can then be integrated to remaining subsystems to verify proper operation of subsystems from supplied power.

55

Page 56: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

Risk Analysis Alex Bouvy

56

Page 57: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

Risk Analysis

•  Mission Requirements: –  RSK.1: The system does not survive the vibration

characteristics prescribed by the RockSat-X program. –  RSK.2: During flight, the power block does not properly

operate and fails to provide power to the subsystems.

•  System Requirements: FFE: –  RSK.3: During flight, the containing vessel fails and

ferrofluid is leaked into the surrounding environment. –  RSK.4: Upon testing the electromagnet to be implemented, it

is determined that too strong a magnetic field will be produced and will interfere with others’ payloads.

57

Page 58: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

Risk Analysis

•  System Requirements: RPE: –  RSK.5: The antennas/probe are interfaced in such a manner

that meaningful data is not received.

•  System Requirements: PSE: –  RSK.6: During flight, the picosatellite fails to eject. –  RSK.7: It is deemed that ejection of the picosatellite will be

unsafe. –  RSK.8: It is determined that picosatellite radio transmissions

will interfere with WFF telemetry.

58

Page 59: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

Risk Analysis

59

Con

sequ

ence

RSK.2    

RSK.3 RSK.5 RSK.6 RSK.7  

  RSK.1 RSK.4

RSK.8

 

Possibility

Page 60: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

Risk Analysis: Risk 1

60

Risk Title RSK.1: Critical Failure on Vibration Testing

Risk Statement The system does not survive the vibration characteristics prescribed by the RockSat-X program.

Context Statement The system will be submitted to vibration testing at WFF in June. It is possible that this vibration testing will cause critical failure in one or more of the components/subsystems.

Closure Criteria If the system experiences a critical failure, the team must re-evaluate designs and rebuild before launch.

Consequence Rationale Likelihood Rationale

2 Upon failure, the team will be forced to re-evaluate designs and rebuild failed systems. The team will have approximately 2 months to do this.

2 Because the system will be submitted to vibration testing (through ATK) before vibration testing at WFF, the team should be fully prepared for vibration testing.

Con

sequ

ence

 

  RSK.1

 

Possibility

Page 61: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

Risk Analysis: Risk 2

61

Risk Title RSK.2: Power Block Failure

Risk Statement During flight, the power block does not properly operate and fails to provide power to the subsystems.

Context Statement If the power block fails, no subsystems will receive power and will therefore not be active during flight.

Closure Criteria This is a realized risk. Thorough testing will be done prior to flight to ensure this mission critical element is in place.

Consequence Rationale Likelihood Rationale

4 If no systems power on, this means that no data will be obtained and minimum success criteria will not be met.

1 This is unlikely to happen. The power block will be thoroughly tested prior to integration.

Con

sequ

ence

RSK.2    

 

 

Possibility

Page 62: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

Risk Analysis: Risk 3

62

Risk Title RSK.3: Ferrofluid Containment Failure

Risk Statement During flight, the containing vessel fails and ferrofluid is leaked into the surrounding environment.

Context Statement The ferrofluid must be contained in a sealed vessel. It is possible that vessel will break, and the ferrofluid will leak out.

Closure Criteria The vessel must be thoroughly tested before flight to mitigate risk of leaks.

Consequence Rationale Likelihood Rationale

3 If the ferrofluid spills and contacts other system components, it could cause a critical failure to the subsystem.

1

As in the case of the power block , this is another component that will be thoroughly tested before flight. It will be submitted to both vibrations and thermal testing at ATK, and then vibrations testing again at WFF.

Con

sequ

ence

 

RSK.3

 

 

Possibility

Page 63: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

Risk Analysis: Risk 4

63

Risk Title RSK.4: Electromagnet Too Strong

Risk Statement Upon testing the electromagnet to be implemented, it is determined that too strong a magnetic field will be produced and will interfere with others’ payloads.

Context Statement It is possible that, upon measuring the magnitude of the magnetic field output from the electromagnet, the field will be deemed too strong to use as it may cause interference with ours and other payloads.

Closure Criteria If the magnetic field is deemed too strong, the experiment may be removed.

Consequence Rationale Likelihood Rationale

2 The discovery of unmitigable interference may result in the removal of the subsystem. 3

It is known that the electromagnet will produce a considerably strong field. It is very possible that it will be discovered that this field interferes with other payload subsystems.

Con

sequ

ence

 

  RSK.4

 

Possibility

Page 64: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

Risk Analysis: Risk 5

64

Risk Title RSK.5: Antenna/Probe Misplacement

Risk Statement The antennas/probe are interfaced in such a manner that meaningful data is not received.

Context Statement

If the Langmuir probe is placed too close to the center of the payload, it may not interact with the space environment in an ideal manner. Additionally, if the GHz antenna is placed in such a manner that interference will be produced, its results may also be clouded.

Closure Criteria The payload subsystems should be laid out such a manner that the probes are placed in ideal positions.

Consequence Rationale Likelihood Rationale

3 If the probes are not placed correctly, valid science data may not be received from the subsystem.

2 It most likely that placing the probe/antenna near the edge will result in acceptable readings, providing valid science data/

Con

sequ

ence

 

RSK.5

 

 

Possibility

Page 65: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

Risk Analysis: Risk 6

65

Risk Title RSK.6: PSE Ejection Failure

Risk Statement During flight, the picosatellite fails to eject.

Context Statement It is possible that upon command, the picosatellite will not eject, and remain in the payload.

Closure Criteria The ejection cylinder will be thoroughly tested prior to launch. Additionally, if the picosatellite does not launch, it is possible that telemetry data from the satellite will still be received.

Consequence Rationale Likelihood Rationale

3 If the payload is not ejected, minimum success criteria will not be met. 2 This subsystem component will be tested

thoroughly prior to launch to help avoid this issue.

Con

sequ

ence

 

RSK.6

 

 

Possibility

Page 66: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

Risk Analysis: Risk 7

66

Risk Title RSK.7: PSE Ejection Deemed Unsafe

Risk Statement It is deemed that ejection of the picosatellite will be unsafe.

Context Statement It is possible that it will be determined by WFF that the ejection of the picosatellite is not safe.

Closure Criteria In this case, the satellite cannot be ejected and will become a fixed component in the payload. Satellite telemetry will still be implemented and measurements obtained.

Consequence Rationale Likelihood Rationale

3 If the picosatellite cannot be ejected, the subsystem must be redesigned and implemented as a fixed component.

3 It is very possible that the deployable will be deemed unsafe, as this is at the discretion of WFF.

Con

sequ

ence

 

RSK.7  

 

 

Possibility

Page 67: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

Risk Analysis: Risk 8

67

Risk Title RSK.8: PSE Telemetry Interference

Risk Statement It is determined that picosatellite radio transmissions will interfere with WFF telemetry.

Context Statement It is possible that WFF will determine that transmissions on the 435MHz band will interfere will WFF telemetry and will not be permitted.

Closure Criteria In this case, satellite telemetry will likely be removed from the subsystem, and the measurements stored on a hard disk.

Consequence Rationale Likelihood Rationale

2 Again, in the case of this, the subsystem must be redesigned. 3

It is considerably possible that the transmissions will interfere, as this is a common RF band used for telemetry.

Con

sequ

ence

 

  RSK.8

 

Possibility

Page 68: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

Project Management Plan Ben Kryger

68

Page 69: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

Schedule

69

Task Start  DateDuration  (days)

End  Date

Critical  Design  Review12-­‐Nov 28 10-­‐Dec

Wallops  Deliverable:

FD  Development12-­‐Nov 21 3-­‐Dec

Internal  Deadline:

FFE  Development 12-­‐Nov 28 10-­‐DecRPE  Development 26-­‐Nov 28 24-­‐Dec

Power  Block  Development 17-­‐Dec 35 21-­‐Jan

PSE  Development 14-­‐Jan 28 11-­‐FebIndividual  Subsystem  

Testing  Report 21-­‐Jan 28 18-­‐FebSubsystem  Integration 18-­‐Feb 28 18-­‐MarPayload  Subsystem  and  

Integration  Report   18-­‐Feb 28 18-­‐MarDITL  Test  Report  1 18-­‐Mar 28 15-­‐AprDITL  Test  Report  2 15-­‐Apr 28 13-­‐May

Integration  Readiness  Review 13-­‐May 21 3-­‐Jun

Launch  Readiness  Review 3-­‐Jun 49 22-­‐Jul

Legend:

Page 70: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

70

12-Nov 1-Jan 20-Feb 11-Apr 31-May 20-Jul

Critical Design Review

FD Development

FFE Development

RPE Development

Power Block Development

PSE Development

Individual Subsystem Testing Report

Subsystem Integration

Payload Subsystem and Integration Report

DITL Test Report 1

DITL Test Report 2

Integration Readiness Review

Launch Readiness Review

Page 71: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

Budget

71

Subsystem Cost  ($)FD 1000 Total  Budget  ($)FFE 200RPE 300PSE 500 Total  Spending  ($)

Power  Block 200 2200

Page 72: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

Team Availability Matrix

72

Monday Tuesday Wednesday Thursday Friday

7:00  AM no no no no no

8:00  AM no no no no no All  times  Eastern  Time  Zone

9:00  AM no no no

10:00  AM no no no

11:00  AM no no yes yes no

12:00  PM yes no yes yes no

1:00  PM no no no yes no

2:00  PM no no yes no no

3:00  PM yes no yes no no

4:00  PM yes no yes yes no

11/13-­‐11/16  RS-­‐X  Team  Availability  Matrix

WVU  Rocketeers

Page 73: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

Contact Matrix

73

Role Name Phone Email Citizenship OK  to  Add  to  Mailing  List?PM Alex  Bouvy (304)  376-­‐0770 [email protected] U.S. YesFaculty  advisorDimitris  Vassiliadis (304)  293-­‐4920 [email protected]. Yes" " (202)  315-­‐6976 [email protected] -­‐ -­‐Media/Web William  Kryger (444)  878-­‐5166 [email protected] U.S. YesTeam  Member Marc  Gramlich (304)  550-­‐3462 [email protected] U.S. Yes

WVU  RocketeersFall  2012  RS-­‐X  Contact  Matrix

Page 74: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

• D-sub connector

• Thermal protection container: model suggestions

Conclusion

74

Page 75: Preliminary Design Review - COSGC Home 2013/te… · – System/Project Level Requirement Verification Plan – User Guide Compliance – Sharing Logistics . 2013 PDR PDR Presentation

2013 PDR

•  Mission statement: Develop a payload which will measure the following properties of the space environment (up to 160 km) during the RockSat-X flight.

–  Plasma density/frequency –  Magnetic field –  Flight dynamics –  Magnetic effects on ferrofluids in microgravity –  Eject a standalone picosatellite. The satellite will house a basic payload

consisting of IMU and magnetometer, as well as a transceiver to transmit data back to earth.

Action Items: –  Begin FD construction/ testing / software development –  Begin FFE construction/ testing/ software development

Conclusion

75