cansat 2011 pdr outline version 0 4 n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
CanSat 2011 PDR Outline Version 0.4 PowerPoint Presentation
Download Presentation
CanSat 2011 PDR Outline Version 0.4

play fullscreen
1 / 82

CanSat 2011 PDR Outline Version 0.4

307 Views Download Presentation
Download Presentation

CanSat 2011 PDR Outline Version 0.4

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. CanSat 2011 PDR Outline Version 0.4 Your Team # Here Your Team Name Here CanSat 2012 PDR: 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 IMPORTANT PRESENTATION GUIDELINE FOR CANSAT 2012: Teams should focus on charts with this star icon during the presentation. Other charts should be skipped to save time; they will be reviewed by the judges off line. Presenter: Name goes here CanSat 2012 PDR: 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 Presenter: Name goes here CanSat 2012 PDR: Team ### (Team Name)

  4. Acronyms • Provide a list of acronyms used throughout the presentation. • DURING PRESENTATIONS – DO NOT READ THROUGH THESE ACRONYMS • These are here for reference only Presenter: Name goes here CanSat 2012 PDR: 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 PDR: Team ### (Team Name)

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

  7. 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 Presenter: Name goes here CanSat 2012 PDR: Team ### (Team Name)

  8. System Level CanSat Configuration Trade & Selection • Present preliminary system-level concepts considered • What configurations were considered • Present criteria for final configuration selection • Include discussion of why the final configuration was selected • Helpful to include sketches and diagrams of various concepts considered • Diagrams of non-selected configurations can include sketches of physical layouts (e.g. scans of hand sketches rather than CAD drawings) • Should include variations on CONOPS considered • Attempts should be made to limit these discussions to 1-2 slides per preliminary configuration • Presentation of the material may be at a cursory level (hit the highlights) Presenter: Name goes here CanSat 2012 PDR: Team ### (Team Name)

  9. System Concept of Operations • 1-3 slides (roughly) providing overview of CanSat operations • Should include • Launch and descent operations • Post-launch recovery and data reduction • Focus on selected configuration CONOPS • Focus on how the CanSat will operate, not what everyone on the team will be doing (to be discussed at CDR) • Simple flow diagrams and cartoons are a good way to present the CONOPS Presenter: Name goes here CanSat 2012 PDR: 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 Presenter: Name goes here CanSat 2012 PDR: Team ### (Team Name)

  11. Launch Vehicle Compatibility • Discussion of how the CanSats are integrated into the rocket payload section • Discussion of how the payload section 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 PDR this may be allocated dimensions (if this is the case, these should be requirements at the system and subsystem levels) • Notes: • In past years there were a large number of CanSats that did not deploy from the payload sections of the rocket Presenter: Name goes here CanSat 2012 PDR: Team ### (Team Name)

  12. Sensor Subsystem Design Presenter Name(s) Go Here CanSat 2012 PDR: 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 Presenter: Name goes here CanSat 2012 PDR: 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 Presenter: Name goes here CanSat 2012 PDR: Team ### (Team Name)

  15. Carrier GPS Trade & Selection • Summary of GPS sensor trade studies and selection See slide discussing trade studies Presenter: Name goes here CanSat 2012 PDR: Team ### (Team Name)

  16. Carrier Non-GPS Altitude Sensor Trade & Selection • Summary of altitude sensor trade study and selection See slide discussing trade studies Presenter: Name goes here CanSat 2012 PDR: Team ### (Team Name)

  17. Carrier Air Temperature Trade & Selection • Summary of air temperature sensor trade study and selection See slide discussing trade studies Presenter: Name goes here CanSat 2012 PDR: Team ### (Team Name)

  18. Lander Altitude Sensor Trade & Selection • Summary of lander altitude sensor trade study and selection See slide discussing trade studies Presenter: Name goes here CanSat 2012 PDR: Team ### (Team Name)

  19. Lander Impact Force Sensor Trade & Selection • SELECTABLE OBJECTIVE – ONLY REQUIRED IF SELECTED See slide discussing trade studies Presenter: Name goes here CanSat 2012 PDR: Team ### (Team Name)

  20. Carrier Camera Trade & Selection • SELECTABLE OBJECTIVE – ONLY REQUIRED IF SELECTED See slide discussing trade studies Presenter: Name goes here CanSat 2012 PDR: Team ### (Team Name)

  21. Carrier Video Camera Trade & Selection • SELECTABLE OBJECTIVE – ONLY REQUIRED IF SELECTED See slide discussing trade studies Presenter: Name goes here CanSat 2012 PDR: Team ### (Team Name)

  22. Lander Video Camera Trade & Selection • SELECTABLE OBJECTIVE – ONLY REQUIRED IF SELECTED See slide discussing trade studies Presenter: Name goes here CanSat 2012 PDR: Team ### (Team Name)

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

  24. 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 Presenter: Name goes here CanSat 2012 PDR: Team ### (Team Name)

  25. 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. Presenter: Name goes here CanSat 2012 PDR: Team ### (Team Name)

  26. Carrier Descent Control Strategy Selection and Trade • Summary of carrier DCS strategy trade studies and selection • Include: • Color selection • Shock force survival • Preflight review testability See slide discussing trade studies Presenter: Name goes here CanSat 2012 PDR: Team ### (Team Name)

  27. Lander Descent Control Strategy Selection and Trade • Summary of lander DCS strategy trade studies and selection • Include color selection See slide discussing trade studies Presenter: Name goes here CanSat 2012 PDR: Team ### (Team Name)

  28. 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 Presenter: Name goes here CanSat 2012 PDR: Team ### (Team Name)

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

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

  31. Mechanical System 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. Presenter: Name goes here CanSat 2012 PDR: Team ### (Team Name)

  32. Lander Egg Protection Trade & Selection • Egg protection system trade studies and selection See slide discussing trade studies Presenter: Name goes here CanSat 2012 PDR: Team ### (Team Name)

  33. Mechanical Layout of Components Trade & Selection • Key trade issues related to mechanical layout and component selection • Structural material selection(s) See slide discussing trade studies CanSat 2012 PDR: Team ### (Team Name)

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

  35. 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)

  36. Structure Survivability Trades • For both Carrier and Lander discuss: • Electronic component mounting methods • Electronic component enclosures • Acceleration and shock force requirements and testing See slide discussing trade studies CanSat 2012 PDR: Team ### (Team Name)

  37. 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 Presenter: Name goes here CanSat 2012 PDR: Team ### (Team Name)

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

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

  40. 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 PDR: Team ### (Team Name)

  41. Processor & Memory Trade & Selection • Include processor speed • Include data interfaces (types and numbers) • Include memory storage requirements, if applicable • Discussion for Carrier and Lander • May be more than one slide if necessary See slide discussing trade studies Presenter: Name goes here CanSat 2012 PDR: Team ### (Team Name)

  42. Carrier Antenna Trade & Selection See slide discussing trade studies Presenter: Name goes here CanSat 2012 PDR: Team ### (Team Name)

  43. 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? • 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 • Ideally you have started working with the radio and communications protocol Start Radio Prototyping and Testing Early! Presenter: Name goes here CanSat 2012 PDR: Team ### (Team Name)

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

  45. Activation of Telemetry Transmissions • Discuss how telemetry transmissions are enabled via remote command on the launch pad Presenter: Name goes here CanSat 2012 PDR: Team ### (Team Name)

  46. Locator Device Trade & Selection • This include locator devices for Carrier and Lander • How will audible locator devices be activated and deactivated? • (e.g. how and when the locators are activated and how they will be deactivated upon recovery) See slide discussing trade studies Presenter: Name goes here CanSat 2012 PDR: Team ### (Team Name)

  47. Electrical Power Subsystem Design Presenter Name(s) Go Here CanSat 2012 PDR: Team ### (Team Name)

  48. EPS Overview • ONE slide providing overview of EPS components (with purposes) • Consider a diagram Presenter: Name goes here CanSat 2012 PDR: Team ### (Team Name)

  49. EPS Requirements • Examples of what these requirements should include: • Voltage requirements (including regulation as necessary) • Battery requirements • Measurement accuracy & resolution • There should be separate requirements for the carrier, lander, and • CanSat system, as applicable. Presenter: Name goes here CanSat 2012 PDR: Team ### (Team Name)

  50. Carrier Electrical Block Diagram • High-level schematic (not down to the resistor level) showing power connections • Include required voltages • Include all major components • Include overview of how power will be controlled and verified externally without disassembling the CanSat Presenter: Name goes here CanSat 2012 PDR: Team ### (Team Name)