CanSat 2011 CDR Outline Version 0.2

1. CanSat 2011 CDR OutlineVersion 0.2 Your Team # Here Your Team Name Here CanSat 2012 CDR: Team ### (Team Name)

2. Presentation Outline • Provide a simple outline of the presentation • If possible, indicate the team member(s) who will be presenting each section CanSat 2012 CDR: Team ### (Team Name)

3. Team Organization • Single slide listing the team members and their roles • If possible, please include year (freshman, sophomore, etc.) for reference • This only needs to be provided once for team members showing up multiple times on the org chart • Good format is the use of an organization chart, such as below: Sample CanSat 2012 CDR: Team ### (Team Name)

4. Acronyms • Provide a list of acronyms used throughout the presentation. • DURING PRESENTATIONS – DO NOT READ THROUGH THESE ACRONYMS CanSat 2012 CDR: Team ### (Team Name)

5. The purpose of this section is to introduce the reviewer to the overall requirements and configuration of the CanSat. This provides a basis for the details presented in the subsystem sections. Systems Overview Presenter Name(s) Go Here CanSat 2012 CDR: Team ### (Team Name)

6. Mission Summary • Overview of the mission objectives • Indicate which one (1) selectable objective is being attempted • Selection rationale? • Also include any external objectives (personal, laboratory or sponsor, class, etc.) relevant to the design CanSat 2012 CDR: Team ### (Team Name)

7. Summary of Changes Since PDR • Overview design changes since PDR • Details of the changes are discussed in subsequent sections. CanSat 2012 CDR: Team ### (Team Name)

8. System Requirements • Table of system (mission) level requirements • This chart may be expanded to multiple charts as needed • See Competition Guide for more information on format and content • DO NOT READ THROUGH THE REQUIREMENTS DURING THE PRESENTATION – HIT HIGHLIGHT (IMPORTANT REQUIREMENTS) & GIVE A FEW MOMENTS FOR REVIEWERS TO LOOK THROUGH THE REQUIREMENTS BUT DO NOT READ THROUGH EACH REQUIREMENT • This holds for ALL discussion of requirements throughout the presentation CanSat 2012 CDR: Team ### (Team Name)

9. System Concept of Operations • 1-3 slides (roughly) providing overview of CanSat operations • Should include • Pre-launch activities • Launch and descent operations • Post-launch recovery and data reduction • Focus on launch day activities • Team member roles and responsibilities on launch day • Simple flow diagrams and cartoons are a good way to present the CONOPS CanSat 2012 CDR: Team ### (Team Name)

10. Physical Layout • Diagram(s) showing physical layout of selected CanSat configuration • Make sure to include: • Dimensions • Placement of major components • Relevant configurations • Carrier, lander, launch configuration, deployed, etc. • The goal is to present the physical idea of what the CanSat will look like for reference prior to getting into details of the CanSat design CanSat 2012 CDR: Team ### (Team Name)

11. Launch Vehicle Compatibility • Discussion of how the CanSats are integrated into the rocket payload section • Discussion of how the CanSat compatibility will be verified prior to launch day • Include a dimensioned drawing that shows clearances with the payload section • Focus on launch configuration (carrier + lander) • Include all descent control apparatus • At CDR this should include measured and/or prototype dimensions • Notes: • In past years there were a large number of CanSats that did not deploy from the payload sections of the rocket CanSat 2012 CDR: Team ### (Team Name)

12. Sensor Subsystem Design Presenter Name(s) Go Here CanSat 2012 CDR: Team ### (Team Name)

13. Sensor Subsystem Overview • One slide providing an overview of the CanSat sensor system • Include summary of the selected sensors (type & models) • Include brief discussion of what the sensors are used for • Focus on selected component (not all components trades) • Include overview of both carrier and lander sensors, as applicable CanSat 2012 CDR: Team ### (Team Name)

14. Sensor Subsystem Requirements • Examples of what these requirements should include: • Required sensor data ranges and resolutions • Operating voltage ranges • Data interfaces • Data rates CanSat 2012 CDR: Team ### (Team Name)

15. Sensor Changes Since PDR • ONE slide providing an overview of the CanSat sensor system changes since PDR • Include rationale • Include changes to both carrier and lander sensors CanSat 2012 CDR: Team ### (Team Name)

16. Carrier GPS Summary • Summary of GPS sensor selection and characteristics • Include: • GPS data accuracy and data format • Overview of data processing (including equations, as appropriate) CanSat 2012 CDR: Team ### (Team Name)

17. Carrier Non-GPS Altitude Sensor Summary • Summary of altitude sensor selection and characteristics • Include: • Sensor accuracy and data format • Overview of data processing (including equations, as appropriate) CanSat 2012 CDR: Team ### (Team Name)

18. Carrier Air Temperature Summary • Summary of air temperature sensor selection and characteristics • Include: • Sensor accuracy and data format • Overview of data formats (including equations, as appropriate) CanSat 2012 CDR: Team ### (Team Name)

19. Lander Altitude Sensor Summary • Summary of lander altitude sensor selection and characteristics • Include: • Sensor accuracy and data format • Overview of data formats (including equations, as appropriate) CanSat 2012 CDR: Team ### (Team Name)

20. Lander Impact Force Sensor Summary • SELECTABLE OBJECTIVE – ONLY REQUIRED IF SELECTED • Summary of sensor selection and characteristics • Include: • Sensor accuracy and data format • Overview of data processing (including equations, as appropriate) CanSat 2012 CDR: Team ### (Team Name)

21. Carrier Camera Summary • SELECTABLE OBJECTIVE – ONLY REQUIRED IF SELECTED • Summary of camera selection and characteristics • Include: • Image resolution • Data formats • How images are handled onboard and reconstructed on the ground CanSat 2012 CDR: Team ### (Team Name)

22. Carrier Video Camera Trade & Selection • SELECTABLE OBJECTIVE – ONLY REQUIRED IF SELECTED • Image resolution • Data formats • Frame rate • How images are handled, stored onboard, and reconstructed on the ground Presenter: Name goes here CanSat 2012 CDR: Team ### (Team Name)

23. Lander Video Camera Trade & Selection • SELECTABLE OBJECTIVE – ONLY REQUIRED IF SELECTED • Image resolution • Data formats • Frame rate • How images are handled, stored onboard, and reconstructed on the ground Presenter: Name goes here CanSat 2012 CDR: Team ### (Team Name)

24. Descent Control Design Presenter Name(s) Go Here CanSat 2012 CDR: Team ### (Team Name)

25. Descent Control Overview • ONE slide providing an overview of the carrier and lander descent control system • Include overview of the selected configurations and components necessary CanSat 2012 CDR: Team ### (Team Name)

26. Descent Control Changes Since PDR • List changes since the PDR for both Carrier and Lander CanSat 2012 CDR: Team ### (Team Name)

27. Descent Control Requirements • Examples of what these requirements should include: • Volume constraints • Packaging • Masses • Target descent rates • Deployment mechanisms • There should be separate requirements for the carrier, lander, and • CanSat system, as applicable. CanSat 2012 CDR: Team ### (Team Name)

28. Carrier Descent Control Hardware Summary • Summary of Carrier DCS sensors and actuator selection and characteristics • Shock force survival • Preflight Review testability • For passive components, discuss: • Component sizing • Key design considerations • Color selection(s) • For active components, discuss: • Sensor accuracy and data formats • Overview of sensor data processing • Actuator control, command rates, and data formats CanSat 2012 CDR: Team ### (Team Name)

29. Lander Descent Control Hardware Summary • Summary of Lander DCS sensors and actuator selection and characteristics • Include deployment trigger and mechanism • For passive components, discuss: • Component sizing • Key design considerations • Color selection(s) • For active components, discuss: • Sensor accuracy and data formats • Overview of sensor data processing • Actuator control, command rates, and data formats CanSat 2012 CDR: Team ### (Team Name)

30. Descent Rate Estimates • Cover estimates for the following CanSat configurations • Carrier + lander post separation (prior to deployment of the lander) • Carrier following deployment of the lander • Lander following separation from the carrier • Include discussion of • Calculations used • Assumptions • This discussion can carrier over to multiple slides if necessary CanSat 2012 CDR: Team ### (Team Name)

31. Mechanical Subsystem Design Presenter Name(s) Go Here CanSat 2012 CDR: Team ### (Team Name)

32. Mechanical Subsystem Overview • ONE slide providing overview of the mechanical subsystem • Include overview of major structural elements, material selection, and interface definitions CanSat 2012 CDR: Team ### (Team Name)

33. Mechanical Subsystem Changes Since PDR • Highlight mechanical changes since PDR. Details should be discussed on subsequent slides. CanSat 2012 CDR: Team ### (Team Name)

34. Mechanical Subsystem Requirements • Examples of what these requirements should include: • Mass allocations • Volume and dimensions constraints • Structural strength/load requirements • There may be separate requirements for the carrier, lander, and • CanSat system, as applicable. CanSat 2012 CDR: Team ### (Team Name)

35. Lander Egg Protection Overview • Details of how the egg will be protected during flight and landing CanSat 2012 CDR: Team ### (Team Name)

36. Mechanical Layout of Components • Dimensioned diagrams showing: • Major structural elements • Overall dimensions of the CanSat • Component presentation CanSat 2012 CDR: Team ### (Team Name)

37. Material Selections • Discussion of what materials will be used for the mechanical components and why CanSat 2012 CDR: Team ### (Team Name)

38. Carrier-Lander Interface • DESCRIBES HOW THE LANDER WILL BE CONNECTED TO AND RELEASED (MECHANICALLY) FROM THE CARRIER • Needs to include discussion of how descent control apparatus will be accommodated Presenter: Name goes here CanSat 2012 PDR: Team ### (Team Name)

39. Carrier-Lander Interface • Describe how the lander will be connected to and released (mechanically) from the carrier • Needs to include discussion of how descent control apparatus will be accommodated • Redundancy / failure modes? CanSat 2012 CDR: Team ### (Team Name)

40. Structure and Survivability • For both Carrier and Lander discuss: • Electronic component mounting methods • Electronic component enclosures • Acceleration and shock force requirements and testing CanSat 2012 CDR: Team ### (Team Name)

41. Mass Budget • Table(s) providing the following: • Mass of all components • Mass of all structural elements • Sources/uncertainties – whether the masses are estimates, from data sheets, measured values, etc. • Total mass • Margins • Must clearly distinguish between carrier and lander masses • Include allocated mass for egg payload CanSat 2012 CDR: Team ### (Team Name)

42. Communication and Data Handling Subsystem Design Presenter Name(s) Go Here CanSat 2012 CDR: Team ### (Team Name)

43. CDH Overview • ONE slide providing overview of the CDH subsystem • Should include selected components (with brief mention of what each component is for) CanSat 2012 CDR: Team ### (Team Name)

44. CDH Changes Since PDR • List changes to the CDH since PDR. Details of the changes should be discussed in subsequent slides. CanSat 2012 CDR: Team ### (Team Name)

45. CDH Requirements • Examples of what these requirements should include: • Processor speeds • Memory requirements • I/O ports (number & types) • There should be separate requirements for the carrier, lander, and • CanSat system, as applicable. Presenter: Name goes here CanSat 2012 CDR: Team ### (Team Name)

46. Processor & Memory Selection • Include processor speed • Include data interfaces (types and numbers) • Include memory storage requirements, if applicable • Discussion for both Carrier and Lander • May be more than one slide if necessary CanSat 2012 CDR: Team ### (Team Name)

47. Carrier Antenna Selection • Description and characteristics of the antenna selected for the CanSat • Consider: • Performance • Mass CanSat 2012 CDR: Team ### (Team Name)

48. Data Package Definitions • Demonstrate an understanding of the communications protocols and packets for each component of the Carrier and Lander design • Radio • GPS • Other sensors • Optional sensors (camera / impact force sensor) • Storage device protocols CanSat 2012 CDR: Team ### (Team Name)

49. Radio Configuration • Demonstrate an understanding of the protocol required to initialize and utilize the XBEE radio module • Provide description of the impact those requirements have on the CanSat design • Include transmission control • How is this managed during each mission phase? • Prototype progress and testing results to date • Note: • Communications failures have occurred often over the past several years of the competition • You are encouraged to use your radios in all of your development and testing to better ensure mission success Complete Radio Prototyping and Testing Early! CanSat 2012 CDR: Team ### (Team Name)

50. Carrier Telemetry Format • What data is included? • Data rate of packet? • How is data formatted? • Include example frames with descriptions CanSat 2012 CDR: Team ### (Team Name)