Red[space]men · CDR Presentation Content • Section 1: Mission Overview – Mission Overview –...

Red[space]men

Critical Design Review

Carthage College Steven Mathe, Kevin Lubick, Eric Ireland,

Steven Metallo, Alexander Powers Faculty Advisors: Dr. Kevin Crosby, Dr.

Brant Carlson NASA Advisor: Rudy Werlink, NASA KSC

CDR Presentation Content

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

• Section 2: Design Description – Requirement/Design Changes Since PDR – De-Scopes/Off-Ramps – Structural Design Elements – Electrical Subsystem Design Elements – Software Design Elements – Hydraulic Subsystem Design Elements – Science Subsystem Design Elements

2

CDR Presentation Contents

• Section 3: Prototyping/Analysis – Analysis Results

• Interpretation to requirements

– Prototyping Results • Interpretation to requirements

– Detailed Mass Budget – Detailed Power Budget – Detailed Interfacing to Wallops

• Section 4: Manufacturing Plan – Structural Elements – Electrical Subsystem Elements – Software Elements – Hydraulic Subsystem Elements – Science Subsystem Elements

3


• Section 5: Testing Plan – Structural Elements – Science Subsystem Elements – Electrical Subsystem Elements – Software Elements – Hydraulic Subsystem Elements – Integration and System Level Testing

• Section 6: Risks – Risks from PDR to CDR

• Walk-down

– Critical Risks Remaining

4


• Section 7: User Guide Compliance – Compliance Table

– Sharing Logistics

• Section 8: Project Management Plan – Schedule

– Budget • Mass

• Monetary

– Work Breakdown Structure

• Conclusion

5

Mission Overview

Name of Presenter

6

Mission Overview Problem

Figure 1a: Settled propellant tanks showing 1-g and microgravity environments

Figure 1b: Unsettled propellant tanks showing fluid slosh characteristic of transient dynamics during orbital maneuvers.

Liquid mass-gauging in zero-g is not

possible using traditional level-based

sensors. In a settled state (Fig. 1A) the

liquid-gas interface is a surface of

constant curvature.

Liquid slosh further complicates mass

gauging in zero-g. There is currently no

reliable way of measuring the volume of

unsettled propellants in the reduced

gravity environment.

Liquids in Zero-g

Mission Overview Primary Objective

The primary objective of this mission is to test the ability of an experimental modal analysis (EMA) technique to measure the volume of a settled, non-sloshing propellant simulant under microgravity conditions.

Mission Overview Modal Analysis

Experimental Modal Analysis (EMA) involves recording the vibration spectrum of a solid object and using the spectral characteristics to infer the structural properties of the object.

Mission Overview Technique Overview

We apply EMA to tank with varying amounts

of fluid and record frequency response

functions (FRF) of the tank.

Mission Overview

• Expect to establish the resolution of EMA fuel gauging on settled fluids in microgravity conditions

• EMA fuel gauging has the potential to: – Offer increased fuel gauging resolution over

current techniques

– Reduce the mass of unusable fuel reserves in spacecraft

– Reduce the mass of required fuel gauging hardware in spacecraft

Mission Overview Minimum Success Requirements

• Objective: to test the ability of an experimental modal analysis (EMA) technique to measure the volume of a settled, non-sloshing propellant simulant under microgravity conditions

• Minimum success criteria – Data from piezoelectric sensors should be

measured continuously from g-switch activation to the end of the flight and at least one mode peak detected

Mission Overview Expected Results

• Non-sloshing fluid expected to increase resolution of the frequency change between fill fractions over sloshing case

• Rocket flight resolution expected to exceed maximum resolution achieved during microgravity flights: 1.5%

Organizational Chart

Project Manager Kevin Lubick

Systems Engineer Steven Mathe

Structural Steven Mathe

Steven Metallo Eric Ireland

Electrical/Software Kevin Lubick Alec Powers

Hydraulics Steven Metallo

Kevin Lubick Alec Powers

Sensor Eric Ireland

Steven Mathe

Faculty Advisor Kevin Crosby

Faculty Advisor Brant Carlson

Primary Investigator Rudy Werlink

Concept of Operations

• G-switch activates software and initiates event timer • Microcontroller/Software:

– Generates white noise signal for tank excitation – Performs DAC of white noise sampling for amplification – Performs ADC conversion of sensor output – Writes sensor data to flash memory

• Event timer triggers pump and solenoid valve twice during flight – T+125 sec – T+200 sec

• Each fill fraction change adds 150 ml (10%) to tank from reservoir

Concept of Operations

t ≈ 15 min

Splash Down

t = 125 sec

Pump adds 150ml to tank

-G switch triggered

-Software activated

-Event timer initiated

t = 0 min

t = 200 sec

Pump adds 150ml to tank

Apogee

t ≈ 2.8 min

Altitude: ≈115 km

End of Orion Burn

t ≈ 0.6 min

Altitude: 52 km

Altitude

t ≈ 5.5 min

Chute Deploys

Design Description

Name of Presenter

17

Overview of Changes since PDR

• Electrical Subsystem

– A suitably small Solenoid Valve was found

– Rather than using the RSK-600 Amplifier, a PZT amplifier will be used (Inductive load vs capacitive load)

De-Scopes since the PDR

• The scope of the project has not changed since the PDR. The mission objectives have stayed the same.

19

Off-Ramps

• If system that controls the changing of the fill fractions becomes too mechanically or programmatically complicated, the number of fill fractions can be reduced to 2 or 1. Then, the data analysis would probe the variability of the method, rather than the accuracy.

• The volume of water carried can be reduced if mass becomes a limiting factor

20

Off-Ramps

• If the microcontroller cannot handle generating a white-noise signal and collecting data simultaneously, an external shield will be added to the design that will read a prerecorded white-nose signal from a microSD card and send that through the amplifier.

– This would not negatively impact the mission objectives, but would require additional power and space on the electronics deck.

Structural Subsystem Diagram

All dimensions

are in units of

inches.

Structural Subsystem: Experimental Tank

• Material: 1/8” thick 6061 T6 Aluminum

• Mass: 1.83 lbs.

• Volume: 0.375 gallons

• Two 1/4" NPT ports for fill and drain

• Sealed with rubber O-ring

• Model propellant tank containing water for experiment

Structural Subsystem: Tank

All dimensions

are in units of

inches.

Structural Subsystem: Hanger


• Mass: 0.62 lbs

• Supports Hydraulics subsystem, except for experimental tank

• Rests on top of stand-offs inside secondary

Structural Subsystem: Hanger

All dimensions

are in units of

inches.

Structural Subsystem: Secondary Containment


• Mass: 4.54 lbs

• Encloses entire Hydraulics Subsystem

• Sealed with rubber O-ring

• Provides mounting point for Electrical Subsystem

• Provides mounting points for RockSat can

Structural Subsystem: Secondary Containment

All dimensions

are in units of

inches.

Structural Subsystem: Electronics Plate

• Material: 1/4" Makrolon polycarbonate plate

• Mass: 0.55 lbs

• Previously flown on RockOn 2012 flight

• Supports entire Electrical Subsystem

• Mounts to top of secondary

Structural Subsystem: Electronics Plate

All dimensions

are in units of

inches.

Structural Subsystem: Secondary Standoff

• Material: 3/8” hex pattern 6061 T6 Aluminum

• Mass: 0.10 lbs each

• Provides increased structural rigidity for entire payload

• Supports hanger inside secondary

• Helps to attach tank to secondary bottom

Structural Subsystem: Secondary Standoff

All dimensions

are in units of

inches.

Structural Subsystem: Electronics Standoff

• Material: 3/8” hex pattern 6061 T6 Aluminum

• Mass: 0.02 lbs each

• Spans vertical distance between electronics plate and RockSat can bulkhead

• Provides upper mounting point to bulkhead

Structural Subsystem: Electronics Standoff

All dimensions

are in units of

inches.

Electrical Subsystem Design Overview

Microcontroller Circuit

12 Volt NiMH

G-Switch And Latch

Power Regulator LEGEND

3.3 Volts

5 Volts

24 Volts

White Noise Signal

Data

Whitenoise Signal Amplification

Circuit

Signal Conditioning Circuit

From Sensors

To Actuator

Relay Circuit

To Pump

To Flow Meter

12 Volts

To Solenoid

Valve

Electrical Subsystem Design Battery Pack

• Planning to use four 6V 2200mA-h NiMH rechargeable battery packs.

• Total Voltage: 12V

• Total Charge: 4400mA-h

Electrical Subsystem Design Power Regulator

37

Given a 12V power source, we need an output

of 4 different voltages to power our various devices

•3.3V – Microcontroller

•5V – Relay, Signal Conditioner, Flow Totalizer

•12V – Signal Amplifier, Fluid Pump

•24V – Solenoid Valve

•We used TI-Webench’s Power Architect to design 4

circuits for these voltages.

We are still looking into

using prebuilt DC-DC

converters. Size is the

limiting factor.

These would be on 1 or 2

breadboards.

Electrical Subsystem Design Power Regulator

38

Electrical Subsystem Design Microcontroller Trade Study

• Requirements – Must have onboard ADC able to sample two (2) analog samples

simultaneously at a rate of at least 32 kilosamples per second, with each sample being at least 10 bits. Therefore, the microcontroller should have at least 2 ADC channels. The analog-digital conversion lag is not terribly important (our system is simply passively recording), but it must be accurate. As we would like to monitor the signals while the fluid volume is being changed, being able to sample at least 3 simultaneous analog samples is better.

– Must be able to generate an analog white-noise signal. This means the microcontroller will need at least one DAC unit. This signal must be generated while the two analog signals (as described above) are recorded.

– Must be able to generate a digital signal to trigger the relay. – Must be able to output data to the external data drive. For the sake of

size constraints, a microSD card is preferable, but an SD card would do. – Must be able to program the microcontroller to a non-volatile memory,

as the device will be powered off before launch – Less than 1 inch tall and less than 20 square inches in area.

Part Name TI Piccolo F28027 TI Stellaris M4F Tern B-Engine

Cost 10 10 0

ADC measuring 7 9 8

Output (Digital and Analog)

9 5 10

External Storage 6 6 10

Non volatile programming

10 10 6

Programming Ease 9 9 4

Size 8 6 8

Average: 8.4 7.9 6.6

Electrical Subsystem Design Microcontroller Trade Study

Electrical Subsystem Design Microcontroller Circuit

2.0 in x 2.6 in x 0.75 in

Electrical Subsystem Design Whitenoise Signal Amplifier

• Requirements

– Must be able to take the analog white noise signal output by the microcontroller (after passing through the DAC) and amplify it from TTL to 50V. This signal will drive the piezoelectric actuator, a capacitive load.

– Must be less than 1 inch tall.

– Ideal Candidates will be prebuilt.

42

Part Name E - 835

Cost 5

Gain 9

Power Required 3

Assembly Requirements

9*

Size 9*

Average: 7.6

Finding an amplifier this small and that could handle the output voltages that we want at a sufficient bandwidth was rather difficult. This was the best candidate. Note on Power Required: Scored low because it requires 1.7 Amps at 12 volts, which is more power than all other components.

*Size and Assembly requirements were most important and counted twice



The schematic for this device is proprietary. Size: 3.43 in x 1.97 in x 0.83 in

E-OEM Piezo Amplifier

Electrical Subsystem Design Electric Relay Trade Study

• Requirements – Can be solid state or electromechanical. As far as

size constraints go, solid state should be more accommodating

– Should be able to be triggered by (digital) TTL voltages

– Should draw less than 200mA while “open”

– Should be able to relay the power required by the pump and the solenoid valves

Part Name Vishay VO14642AT

Panasonic AQZ102 Panasonic AQZ202

Cost 10 9 9

Max Voltage 10 10 10

Max Sustained Load

8 10 9

Peak Load 9 10 10

Power dissipation 9 7 7

Power requirements

9 9 9

Size* 10 9 9

Average: 9.4 9.2 9

Electrical Subsystem Design Electric Relay Trade Study

*Size is the most important factor here and counts twice.

Electrical Subsystem Design Electrical Relay Circuit

47

• Requirements

– Must be able to take the two (2) signals from the piezoelectric sensors, which will be in the hundreds of millivolts range to a readable voltage for microcontroller (to a magnitude of ones to tens of volts)

– Must have a slew rate of at least 0.5 V/μs

– Must be less than 1 inch tall and small enough to be integrated into a circuit.

Electrical Subsystem Design Input Signal Conditioner

Part Name TI - INA128 Analog Devices - AD8221

Maxim - MAX4197

Cost 10 8 10

Slew Rate 10 10 0

Gain 10 10 7

Quiescent current 8 7 7

2 channels? 10 0 0

Size 10 10 10

Average: 9.7 7.5 5.7

Electrical Subsystem Design Input Signal Conditioner

Electrical Subsystem Design ISC Schematic

50

This is the schematic for the Amplifier. R1 and R2 will be adjusted

after bench testing.

Software Design

• After the g-switch activates:

– The microcontroller produces a white noise signal

– The microcontroller records data from PZT sensors to disk

– The event timer starts

Software Design

• The Event timer, at T+125 and T+200 activates the following sequence of events: – Zeros the Totalizer

– Open the relay, powering the pump and opening the solenoid

– Wait 10s or until the Totalizer signals that 150ml has been pumped

– Close the relay

– Record totalizer data to disk as well as time pumped

Software Design

Hydraulic Subsystem Design

Experimental Tank

Water Bladder Leatt Hydration Pack

Air Bladder Leatt Hydration Pack

Pump Simply Pumps

HP400S

Flow Totalizer Flo - 30

Solenoid valve (or replacement)

Hydraulic Subsystem Design Pump Trade Study

• Requirements

– Must transfer fluid at a rate of 0.25 gal/min

– Must draw less than 1.0 A current

– Must require less than 24 V input voltage

– Must weigh less than 0.5 lbs

– Must have a volume of less than 2.0 in3


Simply Pumps HP400S Altia Micropump

Cost 7 4

Current Draw 9 8

Input Voltage 9 8

Weight 10 10

Size 10 10

Average: 9 8


size:

1.58”x1.01”x.98”

Hydraulic Subsystem Design Bladder Trade Study

• Requirements

– Must be able to hold 0.132 gal (500 ml)

– Must be able to withstand launch conditions

– Must be flexible


Platypus Softbottle CC Leatt Hydration Pack

Cost 8 10

Capacity 10 10

Durability 7 10

Flexibility 10 10

Average: 8.75 10


size:

4.7”x6.3”x1.6”

Hydraulic Subsystem Design Micro Flow Totalizer Trade Study

• Requirements

– Must be able to detect fluid flowing at .25 gal/min

– Must be able to output data to microcontroller (either AC or DC is fine)

– Must occupy volume of less than 20 in3


SparkFun Flo-30

Omega FTB321

Omniflow 2000 Micro Flow

Meter

KEM ZHA01/2

Cost 10 8 4 0(Unknown)

Flow Range 3 9 7 10

Size 10 2 6 9

Average: 7.7 6.3 5.7


size:

.62”x2.22”x.38”

Hydraulic Subsystem Design Solenoid Valve Trade Study

• Requirements – Must be able to close off the flow of water and

prevent “backwash” from leaking out of the tank back down the tubing to the reservoir.

– Must draw as little current as possible while active (open). Less than 2.0 amps total, or what ever the maximum current of the relay device, whichever is less.

– Must occupy volume of less than 10 in3 with the smallest dimension less than 1.5 in long and the largest dimension no greater than 3.0 in.


Unbranded 1

Unbranded 2

Unbranded 3

Grainger Solenoid

Cost 10 10 8 8

Power Requirements

8 8 7 6

Size 0 0 0 6

Average: 6 6 5 6.7


size:

1.6”x1”x2.25”

Science Subsystem Design

67

• Consists of actuator and two sensors

• Used and proven to work well in previous experiments

• Actuator: Smart Material Corp. M8557P1

• Monitor/Sensor: Smart Material Corp. M8528P1

Experimental Tank

Actuator: Smart

Material Corp.

M8557P1

Monitor: Smart

Material Corp.

M8528P1

Sensor: Smart

Material Corp.

M8528P1

Input Signal Conditioner

Output Signal

Amplifier

Science Subsystem Design

Prototyping/Analysis

Kevin Lubick

69

Analysis Results

• Analyzed structural components using SolidWorks Simulation Xpress

• Loaded components with 50 times the mass they support to simulate 50g in launch direction

• Loaded components with 20 times the mass they support to simulate loading from spinning

• All components passed with factors of safety greater than 2

70

Prototyping Results

• Hydraulic results

– Bladders can survive a load of at least 20kg (the equivalent of 40g) without leaking

– Failure upon application of 200 lbs of force, equivalent to 200g

71

72

Mass Budget

Subsystem Mass (lbf)

Structural 8.44

Electrical 1.72

Hydraulic 2.29

Sensor 0.10

Container 6.9

Misc. Weight (min) 0.35

TOTAL 19.80

OVER/UNDER 0.00

Power Discussion

73

Power Requirements (Estimated)

Part Volts Amps Watts Number of Minutes

powered Amp-Hours

for flight

Microcontroller 3.3 0.2 0.66 20 0.067 Output Signal

Amplifier 12 1.7 20.4 20 0.57 Input Signal Conditioner 5 0.1 0.5 20 0.033

Relay Device 5 0.015 0.075 0.5 0.00013

Flow Totalizer 5 0.2 1 20 0.067

Fluid Pump 12 0.5 6 0.5 0.0042

Solenoid Valve 24 0.3 7.2 0.5 0.0025

Total (peak) 35.835 0.74

(normal) 22.56

This chart shows

our estimation of

the power

requirements

for our experiment.

Power Discussion

• Our system will be drawing quite a bit of power, 23 W continuous, 36 W peak.

• The planned power source is to use four 6V rechargeable battery packs with 2200mA-h of charge, thus giving us 4400mA-h of charge at 12V.

74

Power Discussion

• Peukert's law approximation of total battery life.

• The estimated discharge time (t) is 0.52 hours at the absolutely maximal current drawn.

• A more realistic approximation, where I = 3.6A, gives t = 0.7 hours.

H = Rated Discharge time = 20 hours

C = Rated Capacity = 4.4AH

I = Actual Current Drawn = 4.6A (max)

k = Peukert's constant = 1.2

Interfacing to Wallops

• Our rig will not need to be turned on early and will be triggered with the g-switch activation.

Manufacturing Plan

Name of Presenter

77

Manufacturing Plan Structural Elements

• Majority of structure is custom-machined

• Current lead time estimate is 30 business days

• Order on January 19th

• Expected arrival on March 4th

• Structural Subsystem fit check completed by March 7th

• Expected to be least troublesome subsystem

Manufacturing Plan Electrical Elements

• Expected to build power distribution, signal conditioner, and relay circuitry

– Still investigating prebuilt alternatives

• Expected lead time is 14 days maximum

• Order parts on January 19th

• Receive by February 2nd

• Final breadboard configuration by February 11th

• Order printed circuit boards on February 11th

Manufacturing Plan Electrical Elements

• Anticipated Revisions

– Power Distribution: 2

– Signal Conditioner: 1

– Relay: 1

Manufacturing Plan Software Elements

• From Nov 24 – Jan 18, the two software engineers will be studying our microcontroller and getting familiar with operations and programming.

• The first revision of the software will be done by the completion of the electrical components, Feb 11th.

• Final revision of the software will hopefully be on 4/27, the day after the full systems test.

• Software frozen 7 days prior to launch – 6/13/13

Manufacturing Plan Software Elements

For each of the 4 basic functions of the electronics, – a prototype of the software will be built

concurrently with the building of the breadboarding of all electrical components.

– The software will be revised to work with the breadboarded electronics.

– The electronic components will be finished.

– The software will be re-revised to work with manufactured components.

Manufacturing Plan Hydraulic Elements

• Hydraulics subsystem is custom-built




• Fit check parts by February 4th

• Test functionality with bread boarded electrical subsystem by February 13th

Manufacturing Plan Science Subsystem Elements

• Sensors will be ready to integrate upon arrival




• Test sensor functionality with hardware from microgravity flights

• Test functionality with bread boarded electrical subsystem by February 13th

Testing Plan

Name of Presenter

85

Testing Plan Structural

• All components must be rated to withstand 40g in the positive z direction on launch

– This will be analyzed using SolidWorks models

• This rating will be verified with weights upon delivery and assembly of the Structural system.

• Vibration testing will be conducted during flight week in June.

Testing Plan Science Subsystem

• The sensors that make up the science subsystem will be co-tested during both the electrical subsystem testing as well as the software testing.

Testing Plan Electrical Subsystem

• General Testing Guidelines – Breadboard all circuits first. Then solder onto

printed circuit boards.

– Test as we build, using Multisim to verify the right voltages are in the right places.

• Microcontroller – Prebuilt. Testing will occur with software

• Output Signal Amplifier – Prebuilt. Will test signal amplification with

oscilloscope to verify wave forms and amplitude.

• Power Supply Circuit – When Power Supply circuit is being breadboarded, all

electrical components will be hooked up to verify that they work.

– As each sub-circuit is constructed (3.3V, 5V, etc) the components that would be powered by the given voltage will be connected and verified working.

• Signal Conditioner – The Resistances of R1 and R2 will be determined will

breadboarding the circuit by hooking up the sensors to a mocked up tank that is getting a signal.

– Upon integration with the actual tank, the values of R1 and R2 will be verified to be sufficient to get clear, undistorted data.


• Relay Circuit

– Functionality will be tested while on breadboard by hooking up the pump and the solenoid valves to the relayed power.


Testing Plan Software

• There are 4 jobs the software does and each will be tested with the corresponding electronic components – Generating white noise signal: Hook up

microcontroller to output amplifier and actuator and verify that an amplified whitenoise signal is being produced.

– Reading and recording signal : Hook up microcontroller to signal conditioner and sensors and verify that a good signal is being recorded. Also replace sensors with a function generator and verify that the waveform is accurately being saved.

Testing Plan Software

• There are 4 jobs the software does and each will be tested with the corresponding electronic components

– Event timer trigger: Hook up microcontroller to relay with an LED as the load. Verify that the LED lights up and shuts off at the appropriate times.

– Record pump data: repeat “event timer trigger” test while also attached to flow meter. induce flow and verify that the proper amount of water was recorded.

Testing Plan Hydraulic Subsystem

• Hydraulics must not leak – We will fill the tank with water, seal it, and shake around

• Hydraulics must transfer .25 gal/min – We will test the set up multiple times to gauge the

variability of pumping technique and pump accuracy

• Hydraulics must function under rotational conditions – We will simulate spinning conditions and test the system

• Bladders must be able to withstand launch conditions – We tested the bladders until failure

– Fails at about 200-g, well above the requirements of launch.

Testing Plan Systems Integration

Integration Steps:

1. Integrate the Electrical System with the Science System and verify that all the Software is working as expected in bench tests.

2. Integrate Hydraulic Subsystem into Structural.

3. Integrate ES/SS into Structural, using Ethernet feedthrough.

4. Connect Hydraulics to ES/SS.

Testing Plan Systems Integration

Finally, test all hydraulics software code and verify that the code triggering electronics is still functional.

Risks

Name of Presenter

96

Biggest Risks (Part 1) C

on

seq

uen

ce

StrS.RSK.2, StrS.RSK.3,

SS.RSK.1, SS.RSK.2


ES.RSK.1, ES.RSK.2, HS.RSK.1

HS.RSK.3

StrS.RSK.2

StrS.RSK.4 StrS.RSK.4, HS.RSK.2

Possibility

• StrS.RSK.1 Mission Objective is not met if structure fails during flight.

• StrS.RSK.2 Other experiments can be damaged if water leaks through secondary.

– If leaking is of concern, put absorbent material inside secondary.

• StrS.RSK.3 Mission Objective is not met if water leaks through experimental tank.

– Rigorous ground testing will address leaking issue.

• StrS.RSK.4 Integration and testing can be delayed if parts do not arrive on schedule.

– Parts will be ordered as early as possible.


on

seq

uen

ce


SS.RSK.1, SS.RSK.2



HS.RSK.3

StrS.RSK.2

StrS.RSK.4 StrS.RSK.4, HS.RSK.2

Possibility

• ES.RSK.1 Mission Objective is not met if microcontroller fails in flight.

• ES.RSK.2 Mission Objective is not met if amplifiers fails in flight


on

seq

uen

ce


SS.RSK.1, SS.RSK.2



HS.RSK.3

StrS.RSK.2

StrS.RSK.4, HS.RSK.2


Possibility

• HS.RSK.1 Mission Objective is not met if Hydraulics downstream of totalizer leak.

• HS.RSK.2 Integration will be delayed if parts do not arrive on schedule. – Parts will be ordered as early

as possible.

• HS.RSK.3 Unscheduled fluid change may occur if suitable replacement for solenoid valve is not found.


on

seq

uen

ce


SS.RSK.1, SS.RSK.2



HS.RSK.3

StrS.RSK.2



Possibility

• SS.RSK. 1 Mission Objectives aren’t met if actuator fails in flight.

• SS.RSK. 2 Mission Objectives aren’t met if monitor or sensor fails in flight.

New Risks C

on

seq

uen

ce

ES.RSK.4 ES.RSK.4

Possibility

• ES.RSK.4 Partial data would be collected if power fails during flight.

– Lab tests and full flight simulation will be conducted.

– More battery packs would be added if power fails during testing.

User Guide Compliance

Name of Presenter

102

User’s Guide Compliance

• The canister and payload will weigh approximately 19.45 lbs without any balancing weights

• Approximate CG is 0.35” below payload center (within limits) – This has been found through SolidWorks.

• Four 6V battery packs will be connected in series/parallel to get us 12V into the power supply

• We are not using high voltage • We are not using any ports

Sharing Logistics (if applicable)

104

• Payload requires entire can

• Sharing logistics does not apply to this experiment

Project Management Plan

Kevin Lubick

105

Schedule

106

Mile Stone Date

CDR Due, All candidate parts selected. Electric system

prototyped in software. 11/30/2012

Lead Times estimated on all parts. Handle any problems

with getting parts on time. 12/15/2012

Down Select 1/18/2013

All parts ordered 1/19/2013

Sub Systems mostly assembled and testing begun 2/1/2013

Subsystem Testing Report Due 2/15/2013

If selected, a more detailed schedule will be formalized by early February

for all events prior to launch.

107

Budget

Item Supplier Est. Individual Cost Number Required Total Cost

RockSat Registration $12,000.00 1 $12,000.00

Travel/Lodging $1,800.00 7 $12,600.00

Structure emachineshop.com $2,932.00 1 $2,932.00

Misc. Hardware $100.00 1 $100.00

Microcontroller Texas Instruments $4.00 2 $8.00

Input Conditioner $6.00 2 $12.00

Output Amplifier E-835 $350.00 2 $700.00

Relay Vishay $5.00 2 $10.00

Battery Pack $40.00 4 $160.00

Misc. Electronics $100.00 1 $100.00

Bladders (5 pack) Leatt $30.00 1 $30.00

Pump Simply Pumps $140.00 2 $280.00

Flow Totalizer SparkFun $133.00 2 $266.00

Solenoid Valve Grainger $40.00 2 $80.00

Misc. Hydraulics $100.00 1 $100.00

Actuator Smart Materials Corp $265.00 2 $530.00

Monitor/Sensor Smart Materials Corp $151.00 4 $604.00

Grand Total $30,512.00

Margin 0.1 Grand Total w/ Margin $33,563.20

Budget

• While our budget looks very high upon first glance, more than a third of the budget is food and lodging for the 7 of us while in Virginia.

• We will be petitioning our Student Government for funds to offset this cost.

Project Summary

109

• Test a zero-g fuel gauge design that uses modal analysis to determine the amount of fuel in a tank

• Remaining issues:

– Determine if we are going to build our own power supply circuits or get manufactured ones.

– Lead time on custom machined parts will take some time.

Conclusion

110

• Action items before winter break

– Software team continue becoming familiar with microcontroller board.

– Finalize power supply circuitry/parts

– Complete model with RockSAT can SolidWorks designs.

Red[space]men · CDR Presentation Content • Section 1: Mission Overview – Mission Overview –...

Documents

Transcript of Red[space]men · CDR Presentation Content • Section 1: Mission Overview – Mission Overview –...