October 26th, 2011

1. The New Jersey Space Grant Consortium at Stevens Institute of Technology and Rutgers UniversityMike Giglia, Ethan Hayon, Robert Hopkins, Jenny Jean,  Mark Siembab, Sean WattsPreliminary Design Review October 26th, 2011

2. Purpose of PDR • Confirm that: • Science objectives and required system performance have been translated into verifiable requirements • Payload Design: to specifications from requirements, can be met through proposed design (trade studies) • Project risks have been identified, and mitigation plans exist • Project management plan is adequate to meet schedule and budget • Project is at a level to proceed to prototyping of high risk items gnurf.net

3. PDR Presentation Content • Section 1: Mission Overview • Mission Overview • Organizational Chart • Theory and Concepts • Concept of Operations • Expected Results • Section 2: System Overview • Subsystem Definitions • Critical Interfaces (ICDs?) • System Level Block Diagram • System/Project Level Requirement Verification Plan • User Guide Compliance • Sharing Logistics

4. PDR Presentation Contents • Section 3: Subsystem Design • Subsystem 1 (AMS) • AMS Block Diagram • AMS Key Trade Studies (3) • AMS Risk Matrix • Subsystem 2 (ITS) • ITS Block Diagram • ITS Key Trade Studies (1) • ITS Risk Matrix  • Subsystem 3 (Misc. Sensors) • Misc. Sensor Block Diagram

5. PDR Presentation Contents • Section 4: Prototyping Plan • Item “A” to be Prototyped • Item “B” to be Prototyped • Etc., Etc… • Section 5: Project Management Plan • Schedule • Budget • Work Breakdown Structure

6. Mission Overview Robert Hopkins

7. Mission Overview • Mission statement • To collect and analyze data for future space research operations through various experiments designed and implemented on a payload. • Experiments: • Atmospheric • O3, CH4, CO2 • Vibration • Piezo vibration of sensor plate • Temperature • Infrared sensor pointed at inside of rocket skin • Rotational Frequency •  Measure rotational frequency using a gyroscope

8. Mission Overview - Theory of Concepts • At launch we will begin to take atmospheric readings. As the rocket ascends and the ports are opened completely air will flow in the dynamic port across our sensors and out the static port. • This will be able to show us different levels of various gases at changing altitudes. • Gathered information is to provide future payloads as to what they will come in contact with during flight to avoid using anything that may malfunction or receive interference as a result of the environment  • The Earth's atmosphere is composed of 71% Nitrogen, 21% Oxygen, 8% CO2, and 1% various other gases. • The top greenhouse gases (GHG's) in our atmosphere are CO2, CH4, and O3. As a result we chose to test for these three gases specifically. • We are taking various other physical readings in order to get a better understanding of the flight environment.

9. Mission Overview - Theory and Concepts • Ground level ozone (O3) - a key constituent of the troposphere. It is also a constituent of certain regions of the stratosphere commonly known as the Ozone layer. At abnormally high concentrations brought about by human activities (largely the combustion of fossil fuel), it is a pollutant, and a constituent of smog. • Methane (CH4) - a hydrocarbon that is the primary component of natural gas as well as a very potent and important greenhouse gas, which is a very efficient GHG which contributes to global warming. Both air pollution and global warming could be reduced by controlling emissions of methane gas.  • Carbon dioxide (CO2) - a colorless, odorless, non-toxic greenhouse gas associated with ocean acidification, emitted from sources such as combustion, cement production, and respiration.

10. Example ConOps t ≈ 1.7 min Altitude: 95 km Continue all readings Altitude t ≈ 4.0 min Altitude: 95 km Close redundant air valve t ≈ 1.3 min Altitude: 75 km Continue all readings Apogee t ≈ 2.8 min Altitude: ≈115 km t ≈ 4.5 min Altitude: 75 km Stop atmospheric readings End of Orion Burn t ≈ 0.6 min Altitude: 52 km t ≈ 5.5 min Chute Deploys -G switch triggered -All systems on -Begin data collection t = 0 min t ≈ 15 min Splash Down

11. Mission Overview - Expected Results • Expected Results: • Increase in temperature readings because of friction and exhaust • Instant High-Z and Low X and Y accelerometer readings • Rotational Frequency readings of ~7Hz • Pollution level gradient as we ascend, prior to closing of atmosph. port • Minimum Success Criteria • At least partial gas sensor readings • AVR records all sensor data and stores in successfully on the flash mem • Temperature readings show some variation during ascent • Rotational frequency readings show ~7Hz

12. System Overview Ethan Hayon

13. Subsystem Design – Physical Model

14. Critical Interfaces • At the PDR level you should at minimum identify these interfaces Interface Name Brief Description Potential Solution AVR/BPL The AVR data acquisition board will be mounted to the bottom makrolon plate (BPL) using short plastic spacers and stainless steel fasteners. The board mount must be able to withstand a 25G load on launch.  We plan to use a similar mounting system used during RockOn 2011. The AVR board will be mounted directly to the makrolon plate with plastic spacers in between itself and the AVR board.  EPS/BPL The electrical power supply must be mounted rigidly to the bottom plate. Similar to the AVR board, the battery supplying the power must be mounted in a manner that is able to withstand a 25G shock on launch. Careful position is important - the battery is a relatively heavy element. The battery must be positioned so that the center of mass of the payload is towards the center of the canister. The sensor board must be mounted rigidly to the top plate. This fixture must be able to withstand the 25G force from launch. Careful placement is also important - the center of mass must be carefully analyzed.  SEN/TPL The sensor board will be mounted to the top plate the same way that the AVR board is mounted to the bottom plate. Stainless steel fasteners and spacers are used for mounting.  ACV/TPL The air containment vessel (ACV) must be mounted securely to the bottom plate. This fixture must be able to withstand a 25G force on launch. Due to it's irregular shape, the ACV must be attached with a bracket to the bottom plate.  The ACV will be mounted to the top plate with a bracket. Due to the irregular shape, extreme caution must be taken when mounting this element. 

15. System Level Block Diagram green - power & data red - power blue/black - data

16. Requirement Verification • At the PDR level you should highlight the most critical (Top3?) system and project level requirements and how they will be verified prior to flight. Requirement Verification Method Description The system will be powered up - RBF pin shorted. The armed LED shall blink steadily if the payload is armed.  The AVR board boots and the system armed LED blinks steadily.  Demonstration SolidWorks will be used to determine the stress the vessel is placed under. The vessel will also be pressurized to ensure there are no leaks. The air vessel must be able to withstand dynamic pressure. Analysis 3D models will be sent to the partner school. Teams will cooperatively ensure the payload will fit in the canister. The payload will fit into half of a canister.  Inspection The system shall survive the vibration characteristics prescribed by the RockSat-C program. The system will be subjected to these vibration loads in June during testing week. Test

17. RockSat-X 2011 User’s Guide Compliance • We are using one static and one dynamic atmospheric port. • We are not using high voltage. We have started building the schematics while breadboarding individual subsystems of our boards.  • Rough mass estimate: 10  lbs • Center of Mass: Not yet determined - plan to keep center of mass towards center of canister. 

18. Sharing Logistics • Our partner school is Mitchell Community College • They plan to implement various generators for passively collecting energy, such as solar and magnetic. • We plan to communicate through email and teleconference.  • We will share SolidWorks or equivalent 3D models with our partner school to plan how space will be used in the canister. • We have not yet determined whether or not there will be clearance issues. These questions will be cleared up within the next week.

19. Subsystem Design (1)Atmospheric Measurement System(AMS) Mark Siembab

20. AMS: Block Diagram (24V)

21. AMS: Trade Studies

22. AMS: Risk Matrix Rsk. 2 Rsk. 3 Rsk. 1 • Rsk.1: Low sample time establishes a poor pollution gradient • Rsk.2: Preheat period not complete by T minus zero • Rsk.3: Power loss prevents redundant valve closure

23. Subsystem Design (2)Infrared Temperature Sensor(ITS) Mark Siembab

24. ITS: Block Diagram Rocket Skin

25. ITS: Trade Studies

26. ITS: Risk Matrix Rsk. 1 Rsk. 2 Rsk. 3 • Rsk.1: Inadequate line of sight to rocket skin • Rsk.2: Launch vibrations shift sensor and cause it to read temperature of irrelevant area • Rsk.3: Launch pad conditions distort skin temperature data

27. Subsystem Design (3)Gyroscope and Vibration Sensor(Misc. Sensors) Mark Siembab

28. Misc. Sensors: Block Diagram

29. Prototyping Plan Sean Watts

30. Prototyping Plan • What will you build/test between now and CDR to mitigate risk? Risk/Concern Action Verify the fit and stability of the board on the plate. Concern about mounting the AVR board to the deck has been expressed AVR We will use a combination between metal latches and zip ties and possibly hot glue to mount the battery securely to the plate. Concerns about mounting the power supply have been expressed. EPS We will try to find sensors with a shorter or zero warm up time. Otherwise we will test the sensors before hand to calibrate them accordingly. Some of the atmospheric sensors have a 24hr warm up time. SEN We will use SolidWorks to design and place the ACV on our plate. We will test a variety of valves to control air flow to our sensors specifications. The ACV will require strategic mounting and proper airflow ACV/AMS

31. Project Management Plan Jenny Jean

32. Organizational Chart  Atmospheric Sampling      Subsystem Design Programming/ Software Design  Atmospheric Sampling      Subsystem Design Programming/ Software Design Electrical Design

33. Schedule

34. Budget

35. WBS • Present a very top-level work break down schedule • One can look up the tree for large scope goals • One can look down the tree for dependencies • Help each subsystem “see” the path ahead PMP EPS STR PM DEP • Obtain PM from LASP • EEF Proposal for funding • … • … • Trade Studies • Schematics • Schematic Review • ICDs • First Revision of Boards • … • … • Trade Studies • Order Materials • Work Request Into Shop • … • … • Obtain PM from LASP • EEF Proposal for funding • … • … • Obtain PM from LASP • EEF Proposal for funding • … • …

36. Conclusion • Before CDR usable sensors must be found.  Mounting of both the sensor board and the power supply should be finalized.  Design of ACV will be started for possible early testing. • Issues • Would heating elements be allowed if sensors without preheat are not obtained? • Would preheat time lead to poor data collection?