Team Logo Here CanSat 2013 PDR: Team ### (Team Name)1 CanSat 2013 PDR Outline Version 0.2 Your Team # Here Your Team Name Here.

  • Published on
    17-Dec-2015

  • View
    216

  • Download
    2

Embed Size (px)

Transcript

  • Slide 1
  • Team Logo Here CanSat 2013 PDR: Team ### (Team Name)1 CanSat 2013 PDR Outline Version 0.2 Your Team # Here Your Team Name Here
  • Slide 2
  • Team Logo Here (If You Want) IMPORTANT PRESENTATION GUIDELINE FOR CANSAT 2013: 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. Presentations are to be 30 minutes in length. CanSat 2013 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 Terms: Container refers to the Re-entry Container component of the CanSat Payload refers to the Science Payload component of the CanSat Presenter: Name goes here
  • Slide 3
  • Team Logo Here (If You Want) CanSat 2013 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: Presenter: Name goes here
  • Slide 4
  • Team Logo Here (If You Want) CanSat 2013 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 for reference only Presenter: Name goes here
  • Slide 5
  • Team Logo Here CanSat 2013 PDR: Team ### (Team Name)5 Systems Overview Presenter Name(s) Go Here 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.
  • Slide 6
  • Team Logo Here (If You Want) CanSat 2013 PDR: 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
  • Slide 7
  • Team Logo Here (If You Want) 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 CanSat 2013 PDR: Team ### (Team Name) 7 Presenter: Name goes here
  • Slide 8
  • Team Logo Here (If You Want) CanSat 2013 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 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) Include variations on CONOPS considered Limit 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
  • Slide 9
  • Team Logo Here (If You Want) CanSat 2013 PDR: Team ### (Team Name) 9 System Concept of Operations 1-3 slides providing overview of CanSat operations 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
  • Slide 10
  • Team Logo Here (If You Want) CanSat 2013 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 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 design Presenter: Name goes here
  • Slide 11
  • Team Logo Here (If You Want) CanSat 2013 PDR: Team ### (Team Name) 11 Launch Vehicle Compatibility Discussion of how the CanSats are integrated into the rocket payload section Discussion of how the rocket 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 (Container + Payload) 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) Note: In past years there were a large number of CanSats that did not deploy from the payload sections of the rocket because of protrusions Presenter: Name goes here
  • Slide 12
  • Team Logo Here CanSat 2013 PDR: Team ### (Team Name)12 Sensor Subsystem Design Presenter Name(s) Go Here
  • Slide 13
  • Team Logo Here (If You Want) CanSat 2013 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 Container and Payload sensors, as applicable Presenter: Name goes here
  • Slide 14
  • Team Logo Here (If You Want) CanSat 2013 PDR: Team ### (Team Name) 14 Sensor Subsystem Requirements Presenter: Name goes here 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
  • Slide 15
  • Team Logo Here (If You Want) CanSat 2013 PDR: Team ### (Team Name) 15 GPS Trade & Selection Summary of GPS sensor trade studies and selection Presenter: Name goes here
  • Slide 16
  • Team Logo Here (If You Want) CanSat 2013 PDR: Team ### (Team Name) 16 Non-GPS Altitude Sensor Trade & Selection Summary of altitude sensor trade study and selection Presenter: Name goes here
  • Slide 17
  • Team Logo Here (If You Want) CanSat 2013 PDR: Team ### (Team Name) 17 Air Temperature Trade & Selection Summary of air temperature sensor trade study and selection Presenter: Name goes here
  • Slide 18
  • Team Logo Here (If You Want) CanSat 2013 PDR: Team ### (Team Name) 18 Video Camera Trade & Selection SELECTABLE OBJECTIVE ONLY REQUIRED IF SELECTED Presenter: Name goes here
  • Slide 19
  • Team Logo Here (If You Want) CanSat 2013 PDR: Team ### (Team Name) 19 Impact Force Sensor Trade & Selection SELECTABLE OBJECTIVE ONLY REQUIRED IF SELECTED Presenter: Name goes here
  • Slide 20
  • Team Logo Here CanSat 2013 PDR: Team ### (Team Name)20 Descent Control Design Presenter Name(s) Go Here
  • Slide 21
  • Team Logo Here (If You Want) CanSat 2013 PDR: Team ### (Team Name) 21 Descent Control Overview ONE slide providing an overview of the Container and Payload descent control system(s) Include overview of the selected configurations and components necessary Include diagrams outlining descent control strategy for various flight altitude ranges Presenter: Name goes here
  • Slide 22
  • Team Logo Here (If You Want) CanSat 2013 PDR: Team ### (Team Name) 22 Descent Control Requirements Presenter: Name goes here 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
  • Slide 23
  • Team Logo Here (If You Want) CanSat 2013 PDR: Team ### (Team Name) 23 Container Descent Control Strategy Selection and Trade Summary of container DCS strategy trade studies and selection Include: Color selection Shock force survival DCS connections Preflight review testability Presenter: Name goes here
  • Slide 24
  • Team Logo Here (If You Want) CanSat 2013 PDR: Team ### (Team Name) 24 Payload Descent Control Strategy Selection and Trade Summary of Science Payload DCS strategy trade studies and selection Include color selection Presenter: Name goes here
  • Slide 25
  • Team Logo Here (If You Want) CanSat 2013 PDR: Team ### (Team Name) 25 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
  • Slide 26
  • Team Logo Here CanSat 2013 PDR: Team ### (Team Name)26 Mechanical Subsystem Design Presenter Name(s) Go Here
  • Slide 27
  • Team Logo Here (If You Want) CanSat 2013 PDR: Team ### (Team Name) 27 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 Presenter: Name goes here
  • Slide 28
  • Team Logo Here (If You Want) CanSat 2013 PDR: Team ### (Team Name) 28 Mechanical Sub-System Requirements Presenter: Name goes here 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
  • Slide 29
  • Team Logo Here (If You Want) CanSat 2013 PDR: Team ### (Team Name) 29 Egg Protection Trade & Selection Egg protection system trade studies and selection Presenter: Name goes here
  • Slide 30
  • Team Logo Here (If You Want) CanSat 2013 PDR: Team ### (Team Name) 30 Mechanical Layout of Components Trade & Selection Key trade issues related to mechanical layout and component selection Structural material selection(s)
  • Slide 31
  • Team Logo Here (If You Want) Material Selections Discussion of what materials will be used for the mechanical components and why CanSat 2013 PDR: Team ### (Team Name) 31
  • Slide 32
  • Team Logo Here (If You Want) CanSat 2013 PDR: Team ### (Team Name) 32 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
  • Slide 33
  • Team Logo Here (If You Want) Structure Survivability Trades For both 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 PDR: Team ### (Team Name) 33
  • Slide 34
  • Team Logo Here (If You Want) CanSat 2013 PDR: Team ### (Team Name) 34 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 Margin Must clearly distinguish between Container and Payload masses Include allocated mass for egg payload Presenter: Name goes here
  • Slide 35
  • Team Logo Here CanSat 2013 PDR: Team ### (Team Name)35 Communication and Data Handling (CDH) Subsystem Design Presenter Name(s) Go Here
  • Slide 36
  • Team Logo Here (If You Want) CanSat 2013 PDR: Team ### (Team Name) 36 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
  • Slide 37
  • Team Logo Here (If You Want) CanSat 2013 PDR: Team ### (Team Name) 37 CDH Requirements Presenter: Name goes here 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
  • Slide 38
  • Team Logo Here (If You Want) CanSat 2013 PDR: Team ### (Team Name) 38 Processor & Memory Trade & Selection Include processor speed Include data interfaces (types and numbers) Include memory storage requirements, if applicable Presenter: Name goes here
  • Slide 39
  • Team Logo Here (If You Want) CanSat 2013 PDR: Team ### (Team Name) 39 Antenna Trade & Selection Antenna selection criteria Antenna range and patterns Presenter: Name goes here
  • Slide 40
  • Team Logo Here (If You Want) CanSat 2013 PDR: Team ### (Team Name) 40 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 Presenter: Name goes here Start Radio Prototyping and Testing Early!
  • Slide 41
  • Team Logo Here (If You Want) CanSat 2013 PDR: Team ### (Team Name) 41 Telemetry Format What data is included? Data rate of packe...

Recommended

View more >