1 / 102

CanSat 2013 Critical Design Review (CDR) Outline Version 6

CanSat 2013 Critical Design Review (CDR) Outline Version 6. Your Team Number Here Your Team Name Here. Presentation Outline. Provide a simple outline of the presentation If possible, indicate the team member(s) who will be presenting each section Terms:

ady
Download Presentation

CanSat 2013 Critical Design Review (CDR) Outline Version 6

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CanSat 2013 Critical Design Review (CDR)OutlineVersion 6 Your Team Number Here Your Team Name Here CanSat 2013 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 • Terms: • Container refers to the Re-entry Container component of the CanSat • Payload refers to the Science Payload component of the CanSat IMPORTANT PRESENTATION GUIDELINE FOR CANSAT 2013: Teams should focus on charts with this star icon during the presentation. Other charts are to be skipped to save time; they will be reviewed by the judges off line. Do not remove the star icon from the slides. Presentations are to be 30 minutes in length. Presenter: Name goes here CanSat 2013 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 2013 CDR: Team ### (Team Name)

  4. Acronyms • Provide a list of acronyms used throughout the presentation • During presentations, do not read through these acronyms • These are for reference only Presenter: Name goes here CanSat 2013 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. System Overview Presenter Name(s) Go Here CanSat 2013 CDR: Team ### (Team Name)

  6. Mission Summary • Overview of the mission objectives • Indicate which one (1) selectable objective is being attempted • Describe selection rationale • Include any external objectives (personal, laboratory or sponsor, class, etc.) relevant to the design Presenter: Name goes here CanSat 2013 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 2013 CDR: Team ### (Team Name)

  8. System Requirement Summary • Overview of system (mission) level requirements • Use bullets or a table to demonstrate an understanding of the mission requirements • This chart may be expanded to multiple charts as needed • The purpose of the chart is to demonstrate the team understands the system-level requirements Presenter: Name goes here CanSat 2013 CDR: Team ### (Team Name)

  9. System Concept of Operations • 1 to 3 slides 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 2013 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 • Container, payload, 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 2013 CDR: Team ### (Team Name)

  11. Launch Vehicle Compatibility • Discussion of how the CanSat is 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 (Container + Payload) • 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 2013 CDR: Team ### (Team Name)

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

  14. Sensor Subsystem Requirements • Overview of sensor subsystem requirements • Use bullets or a table to demonstrate an understanding of the requirements for this subsystem • This chart may be expanded to multiple charts as needed • The purpose of the chart is to demonstrate to the judges an understanding of the requirements that apply to the subsystem • Clearly indicate: • Which Competition Guide Requirements are allocated to this subsystem • Any derived requirements for the subsysytem Presenter: Name goes here CanSat 2013 CDR: Team ### (Team Name)

  15. Sensor Changes Since PDR • One slide providing an overview of the CanSat sensor system changes since PDR • Include rationale • Clearly explain why changes were made, including things like: • Power limitations • Testing • Component size • Availability CanSat 2013 CDR: Team ### (Team Name)

  16. 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 2013 CDR: Team ### (Team Name)

  17. 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 2013 CDR: Team ### (Team Name)

  18. 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 2013 CDR: Team ### (Team Name)

  19. Video Camera Summary • 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 2013 CDR: Team ### (Team Name)

  20. 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 2013 CDR: Team ### (Team Name)

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

  22. Descent Control Overview • One slide providing an overview of the Container and Payload descent control system • Include overview of the selected configurations and components necessary • Include diagrams outlining descent control strategy for various flight altitude ranges CanSat 2013 CDR: Team ### (Team Name)

  23. Descent Control Changes Since PDR • List changes since the PDR • Include rationale • Prototype testing CanSat 2013 CDR: Team ### (Team Name)

  24. Descent Control Requirements • Overview of subsystem requirements • Use bullets or a table to demonstrate an understanding of the DCS requirements • This chart may be expanded to multiple charts as needed • The purpose of the chart is to demonstrate to the judges that the team understands the system-level requirements • Clearly indicate: • Which Competition Guide Requirements are allocated to this subsystem • Any derived requirements for the subsystem Presenter: Name goes here CanSat 2013 CDR: Team ### (Team Name)

  25. Container Descent Control Hardware Summary • Summary of DCS component 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 2013 CDR: Team ### (Team Name)

  26. Payload Descent Control Hardware Summary • Summary of 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 2013 CDR: Team ### (Team Name)

  27. Descent Rate Estimates • Present estimates for the following CanSat configurations • Container + Payload post separation (prior to deployment of the Payload) • Container following deployment of the Payload • Payload following separation from the Container • Include discussion of • Calculations used • Assumptions • This discussion can carry over to multiple slides if necessary Presenter: Name goes here CanSat 2013 CDR: Team ### (Team Name)

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

  29. Mechanical Subsystem Overview • One slide providing overview of the mechanical subsystem • Include overview of major structural elements, material selection, and interface definitions • Include Container and Payload mechanical configurations CanSat 2013 CDR: Team ### (Team Name)

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

  31. Mechanical Sub-System Requirements • Overview of mechanical sub-system requirements • Use bullets or a table to demonstrate an understanding of the mission requirements • This chart may be expanded to multiple charts as needed • The purpose of the chart is to demonstrate to the judges that the team understands the requirements that apply to this sub-system • Clearly indicate: • Which Competition Guide Requirements are allocated to this subsystem • Any derived requirements for the subsytem Presenter: Name goes here CanSat 2013 CDR: Team ### (Team Name)

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

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

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

  35. Container - Payload Interface • Describe how the Payload will be connected to and released (mechanically) from the Container • Include: • Discussion of how descent control apparatus will be accommodated • Diagrams • Method of operation Presenter: Name goes here CanSat 2013 CDR: Team ### (Team Name)

  36. Structure Survivability • As applicable for the Container and Payload, discuss: • Electronic component mounting methods • Electronic component enclosures • Acceleration and shock force requirements and testing • Securing electrical connections (glue, tape, etc.) • Consider required judge verification during pre-flight check in CanSat 2013 CDR: 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 compared to requirement(s) • Margins • Must clearly distinguish between Container and Payload masses • Include allocated mass for egg payload CanSat 2013 CDR: Team ### (Team Name)

  38. Communication and Data Handling Subsystem Design Presenter Name(s) Go Here CanSat 2013 CDR: 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) CanSat 2013 CDR: Team ### (Team Name)

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

  41. CDH Requirements • Overview of CDH sub-system requirements • Use bullets or a table to demonstrate an understanding of the mission requirements • This chart may be expanded to multiple charts as needed • The purpose of the chart is to demonstrate to the judges that the team understands the requirements that apply to this sub-system • Clearly indicate: • Which Competition Guide Requirements are allocated to this subsystem • Any derived requirements for the subsystem Presenter: Name goes here CanSat 2013 CDR: Team ### (Team Name)

  42. Processor & Memory Selection • Include processor speed • Include data interfaces (types and numbers) • Include memory storage requirements, if applicable CanSat 2013 CDR: Team ### (Team Name)

  43. Antenna Selection • Description and characteristics of the antenna selected for the CanSat • Discuss: • Performance • Mass CanSat 2013 CDR: Team ### (Team Name)

  44. Radio Configuration • Demonstrate an understanding of the protocol and configuration (e.g., mode and NETID) 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 2013 CDR: Team ### (Team Name)

  45. Telemetry Format • What data is included? • Data rate of packet? • How is data formatted? • Include example frames with complete descriptions • Does the presented format match the Competition Guide requirements? Presenter: Name goes here CanSat 2013 CDR: Team ### (Team Name)

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

  47. Locator Device and Labeling • How is the audible locator device activated and deactivated? • (e.g. how and when is locator activated and how will it be deactivated upon recovery) • Include: • Power consumption • Audible volume with comparison to requirements • Activation trigger • Switch • Describe labeling to facilitate return if the CanSat is not recovered on launch day CanSat 2013 CDR: Team ### (Team Name)

  48. Electrical Power Subsystem Design Presenter Name(s) Go Here CanSat 2013 CDR: Team ### (Team Name)

  49. EPS Overview • ONE slide providing overview of EPS components (with purposes) • Consider a diagram CanSat 2013 CDR: Team ### (Team Name)

  50. EPS Changes Since PDR • List changes to the EPS subsystem since PDR. Details of changes should be discussed in subsequent slides. CanSat 2013 CDR: Team ### (Team Name)

More Related