cansat 2014 pdr outline version 1 1 n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
CanSat 2014 PDR Outline Version 1.1 PowerPoint Presentation
Download Presentation
CanSat 2014 PDR Outline Version 1.1

play fullscreen
1 / 77

CanSat 2014 PDR Outline Version 1.1

213 Views Download Presentation
Download Presentation

CanSat 2014 PDR Outline Version 1.1

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

  1. CanSat 2014 PDR Outline Version 1.1 Your Team # Here Your Team Name Here CanSat 2014 PDR: Team ### (Team Number and 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: Teams should only present charts with this star icon during the teleconference. 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. Presenter: Name goes here CanSat 2014 PDR: Team ### (Team Number and 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 2014 PDR: Team ### (Team Number and 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 2014 PDR: Team ### (Team Number and 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 2014 PDR: Team ### (Team Number and 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 2014 PDR: Team ### (Team Number and Name)

  7. 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 2014 PDR: Team ### (Team Number and 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 CanSat 2014 PDR: Team ### (Team Number and 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 CanSat 2014 PDR: Team ### (Team Number and 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 CanSat 2014 PDR: Team ### (Team Number and Name)

  11. Launch Vehicle Compatibility • Discussion of how the CanSat is 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 (no sharp protrusions) • At PDR this may be allocated dimensions (if this is the case, these should be requirements at the system and subsystem levels) • What is the clearance? (Leave margin to allow easy deployment!) • 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 or because the CanSat was too wide to fit in the rocket Presenter: Name goes here CanSat 2014 PDR: Team ### (Team Number and Name)

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

  15. Altitude Sensor Trade & Selection • Summary of altitude sensor trade study and selection • Include both Carrier and Payload, as applicable See slide discussing trade studies Presenter: Name goes here CanSat 2014 PDR: Team ### (Team Number and Name)

  16. Air Temperature Trade & Selection • Summary of air temperature sensor trade study and selection • Include both Carrier and Payload, as applicable See slide discussing trade studies Presenter: Name goes here CanSat 2014 PDR: Team ### (Team Number and Name)

  17. 3-Axis Accelerometer Sensor Trade & Selection • SELECTABLE OBJECTIVE – ONLY REQUIRED IF SELECTED See slide discussing trade studies Presenter: Name goes here CanSat 2014 PDR: Team ### (Team Number and Name)

  18. Light Sensor Camera Trade & Selection • SELECTABLE OBJECTIVE – ONLY REQUIRED IF SELECTED See slide discussing trade studies Presenter: Name goes here CanSat 2014 PDR: Team ### (Team Number and Name)

  19. Descent Control Design Presenter Name(s) Go Here CanSat 2014 PDR: Team ### (Team Number and Name)

  20. 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 CanSat 2014 PDR: Team ### (Team Number and Name)

  21. 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 2014 PDR: Team ### (Team Number and Name)

  22. 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 See slide discussing trade studies Presenter: Name goes here CanSat 2014 PDR: Team ### (Team Number and Name)

  23. Payload Descent Control Strategy Selection and Trade • Summary of Science Payload DCS strategy trade studies and selection • Include color selection • Preflight review testability See slide discussing trade studies Presenter: Name goes here CanSat 2014 PDR: Team ### (Team Number and Name)

  24. 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 2014 PDR: Team ### (Team Number and Name)

  25. Mechanical Subsystem Design Presenter Name(s) Go Here CanSat 2014 PDR: Team ### (Team Number and Name)

  26. 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 CanSat 2014 PDR: Team ### (Team Number and Name)

  27. 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 2014 PDR: Team ### (Team Number and Name)

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

  29. 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 2014 PDR: Team ### (Team Number and Name)

  30. Material Selections • Discussion of what materials will be used for the mechanical components and why CanSat 2014 PDR: Team ### (Team Number and Name)

  31. 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 • Clearance between Payload and Container Presenter: Name goes here CanSat 2014 PDR: Team ### (Team Number and Name)

  32. 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 • Descent control attachments See slide discussing trade studies CanSat 2014 PDR: Team ### (Team Number and Name)

  33. 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 and method of correction at launch site • Must clearly distinguish between Container and Payload masses • Include allocated mass for egg payload Presenter: Name goes here CanSat 2014 PDR: Team ### (Team Number and Name)

  34. Communication and Data Handling (CDH) Subsystem Design Presenter Name(s) Go Here CanSat 2014 PDR: Team ### (Team Number and Name)

  35. 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 2014 PDR: Team ### (Team Number and Name)

  36. 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 2014 PDR: Team ### (Team Number and Name)

  37. Processor & Memory Trade & Selection • Include processor speed • Include data interfaces (types and numbers) • Include memory storage requirements, if applicable • Power management See slide discussing trade studies Presenter: Name goes here CanSat 2014 PDR: Team ### (Team Number and Name)

  38. Real-Time Clock • Describe design for payload and container real-time clock functions • Hardware or software See slide discussing trade studies CanSat 2014 PDR: Team ### (Team Number and Name)

  39. Antenna Trade & Selection • Antenna selection criteria • Antenna range and patterns See slide discussing trade studies Presenter: Name goes here CanSat 2014 PDR: Team ### (Team Number and 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 Start Radio Prototyping and Testing Early! Presenter: Name goes here CanSat 2014 PDR: Team ### (Team Number and Name)

  41. Telemetry Format • What data is included? • Include custom fields • Include fields for bonus objectives • Data rate of packet? • How is data formatted? • Include example frames with complete descriptions Presenter: Name goes here CanSat 2014 PDR: Team ### (Team Number and Name)

  42. Electrical Power Subsystem (EPS) Design Presenter Name(s) Go Here CanSat 2014 PDR: Team ### (Team Number and Name)

  43. EPS Overview • One slide providing overview of EPS components (with purposes) • Use a diagram Presenter: Name goes here CanSat 2014 PDR: Team ### (Team Number and Name)

  44. EPS Requirements • Overview of EPS subsystem 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 2014 PDR: Team ### (Team Number and Name)

  45. 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 • I.e., an easily accessible external switch • Include diagrams for Container and Payload in one or two slides • Umbilical power source for use in test and safety inspection Presenter: Name goes here CanSat 2014 PDR: Team ### (Team Number and Name)

  46. Payload Energy Harvesting StrategyTrade Study • Describe payload energy harvesting strategy and considered options, including: • Power source • Energy storage • Rationale See slide discussing trade studies CanSat 2014 PDR: Team ### (Team Number and Name)

  47. Power Budget • Power budget in tabular format which includes: • Power consumption (W) of all components • Expected duty cycles for all components • Source/uncertainty for each line item • Estimate, data sheet, measurement, etc. • Total power consumed (mAh) • Power sources and total power available • Power storage devices and strategy • Graphical representation of charge / discharge cycles • Margins • Include potential one hour wait on the launch pad for the Container Presenter: Name goes here CanSat 2014 PDR: Team ### (Team Number and Name)

  48. Power Source Trade & Selection • Discussion of power source selection • Non-battery source for Payload • Container power source • Do not consider or select lithium polymer (LiPo) batteries, which are not allowed because of fire risk See slide discussing trade studies Presenter: Name goes here CanSat 2014 PDR: Team ### (Team Number and Name)

  49. Power Storage Trade & Selection • Discussion of power storage selection See slide discussing trade studies Presenter: Name goes here CanSat 2014 PDR: Team ### (Team Number and Name)

  50. Power Bus Voltage MeasurementTrade & Selection • Discuss voltage measurements technique and circuit See slide discussing trade studies Presenter: Name goes here CanSat 2014 PDR: Team ### (Team Number and Name)