Cansat 2013 critical design review cdr outline version 6
This presentation is the property of its rightful owner.
Sponsored Links
1 / 102

CanSat 2013 Critical Design Review (CDR) Outline Version 6 PowerPoint PPT Presentation


  • 61 Views
  • Uploaded on
  • Presentation posted in: General

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:

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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


Cansat 2013 critical design review cdr outline version 6

CanSat 2013 Critical Design Review (CDR)OutlineVersion 6

Your Team Number Here

Your Team Name Here

CanSat 2013 CDR: Team ### (Team Name)


Presentation outline

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)


Team organization

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)


Acronyms

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)


System overview

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)


Mission summary

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)


Summary of changes since pdr

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)


System requirement summary

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)


System concept of operations

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)


Physical layout

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)


Launch vehicle compatibility

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)


Sensor subsystem design

Sensor Subsystem Design

Presenter Name(s) Go Here

CanSat 2013 CDR: Team ### (Team Name)


Sensor subsystem overview

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)


Sensor subsystem requirements

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)


Sensor changes since pdr

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)


Gps summary

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)


Non gps altitude sensor summary

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)


Air temperature summary

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)


Video camera summary

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)


Impact force sensor summary

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)


Descent control design

Descent Control Design

Presenter Name(s) Go Here

CanSat 2013 CDR: Team ### (Team Name)


Descent control overview

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)


Descent control changes since pdr

Descent Control Changes Since PDR

  • List changes since the PDR

  • Include rationale

  • Prototype testing

CanSat 2013 CDR: Team ### (Team Name)


Descent control requirements

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)


Container descent control hardware summary

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)


Payload descent control hardware summary

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)


Descent rate estimates

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)


Mechanical subsystem design

Mechanical Subsystem Design

Presenter Name(s) Go Here

CanSat 2013 CDR: Team ### (Team Name)


Mechanical subsystem overview

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)


Mechanical subsystem changes since pdr

Mechanical Subsystem Changes Since PDR

  • Highlight mechanical changes since PDR. Details should be discussed on subsequent slides

CanSat 2013 CDR: Team ### (Team Name)


Mechanical sub system requirements

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)


Egg protection overview

Egg Protection Overview

  • Details of how the egg will be protected during flight and landing

CanSat 2013 CDR: Team ### (Team Name)


Mechanical layout of components

Mechanical Layout of Components

  • Dimensioned diagrams showing:

    • Major structural elements

    • Overall dimensions of the CanSat

    • Component presentation

CanSat 2013 CDR: Team ### (Team Name)


Material selections

Material Selections

  • Discussion of what materials will be used for the mechanical components and why

CanSat 2013 CDR: Team ### (Team Name)


Container payload interface

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)


Structure survivability

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)


Mass budget

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)


Communication and data handling subsystem design

Communication and Data Handling Subsystem Design

Presenter Name(s) Go Here

CanSat 2013 CDR: Team ### (Team Name)


Cdh overview

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)


Cdh changes since pdr

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)


Cdh requirements

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)


Processor memory selection

Processor & Memory Selection

  • Include processor speed

  • Include data interfaces (types and numbers)

  • Include memory storage requirements, if applicable

CanSat 2013 CDR: Team ### (Team Name)


Antenna selection

Antenna Selection

  • Description and characteristics of the antenna selected for the CanSat

  • Discuss:

    • Performance

    • Mass

CanSat 2013 CDR: Team ### (Team Name)


Radio configuration

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)


Telemetry format

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)


Activation of telemetry transmissions

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)


Locator device and labeling

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)


Electrical power subsystem design

Electrical Power Subsystem Design

Presenter Name(s) Go Here

CanSat 2013 CDR: Team ### (Team Name)


Eps overview

EPS Overview

  • ONE slide providing overview of EPS components (with purposes)

  • Consider a diagram

CanSat 2013 CDR: Team ### (Team Name)


Eps changes since pdr

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)


Eps requirements

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


Electrical block diagram

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

Presenter: Name goes here

CanSat 2013 CDR: Team ### (Team Name)


Power budget

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 available/ battery capacity (mAh)

    • Margins

      • Include potential one hour wait on the launch pad

Presenter: Name goes here

CanSat 2013 CDR: Team ### (Team Name)


Power source summary

Power Source Summary

  • Discussion of power source selection

  • Do not consider or select lithium polymer (LiPo) batteries, which are not allowed because of fire risk

Presenter: Name goes here

CanSat 2013 CDR: Team ### (Team Name)


Battery voltage measurement

Battery Voltage Measurement

  • Details of how the battery voltage is measured.

  • This should include a discussion of the measurement range and resolution, data conversions, etc.

CanSat 2013 CDR: Team ### (Team Name)


Flight software design

Flight Software Design

Presenter Name(s) Go Here

CanSat 2013 CDR: Team ### (Team Name)


Fsw overview

FSW Overview

  • Overview of the CanSat FSW design

  • Should discuss

    • Basic FSW architecture

    • Programming languages

    • Development environments

    • Brief summary of what the FSW has to do

Presenter: Name goes here

CanSat 2013 CDR: Team ### (Team Name)


Fsw changes since pdr

FSW Changes Since PDR

  • Overview of the CanSat FSW changes since the PDR. Details of the changes should be discussed in subsequent slides.

CanSat 2013 CDR: Team ### (Team Name)


Fsw requirements

FSW 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)


Cansat fsw state diagram

CanSat FSW State Diagram

  • Software state diagram defining the states and transition conditions of the flight software

  • Things to include:

    • Sampling of sensors (including rates)

    • Communications (command and telemetry)

    • Data storage (if applicable)

    • Mechanism activations

    • Major decision points in the logic

  • FSW recovery to correct state after processor reset during flight

    • What data is used to recover?

Presenter: Name goes here

CanSat 2013 CDR: Team ### (Team Name)


Software development plan

Software Development Plan

  • A common CanSat problem is late software development

  • Present a slide describing the plan for software development and plans to reduce the risk of late software development

  • Include:

    • Prototyping and prototyping environments

    • Software subsystem development sequence

    • Development team

    • Test methodology

  • Discuss progress since PDR

Presenter: Name goes here

CanSat 2013 CDR: Team ### (Team Name)


Ground control system gcs design

Ground Control System (GCS) Design

Presenter Name(s) Go Here

CanSat 2013 CDR: Team ### (Team Name)


Gcs overview

GCS Overview

  • Include a simple context diagram showing major components (computers, antenna, adaptors, etc.)

CanSat 2013 CDR: Team ### (Team Name)


Gcs requirements

GCS Requirements

  • Overview of GCS requirements

  • Use bullets or a table to demonstrate an understanding of the requirements for the GCS

  • 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 the GCS

  • Examples of requirements to include:

  • Antenna placement (field-of-view requirements)

  • Computational requirements

  • Analysis SW requirements

  • Mission operations sequence of events

Presenter: Name goes here

CanSat 2013 CDR: Team ### (Team Name)


Gcs antenna selection

GCS Antenna Selection

  • Discussion of the selection of the GCS antenna

  • Include:

    • Antenna placement and coverage

      • Diagram is recommended

    • Antenna height and mounting strategy

      • Launch day construction

    • Distance link predictions and margins

    • Screen shot of ground control software in operation

CanSat 2013 CDR: Team ### (Team Name)


Gcs software

GCS Software

  • Telemetry display screen shots

  • Commercial off the shelf (COTS) software packages used

  • Real-time plotting software design

  • Data archiving and retrieval approach

  • Command software and interface

  • Progress since PDR

  • Testing

CanSat 2013 CDR: Team ### (Team Name)


Cansat integration and test

CanSat Integration and Test

Presenter Name(s) Go Here

CanSat 2013 CDR: Team ### (Team Name)


Cansat integration and test overview

CanSat Integration and Test Overview

  • 3-5 slides

  • Discussion of how the CanSat subsystems will be integrated

  • Discussion of system-level tests to be performed on the integrated CanSat

  • Discuss subsystem integration

    • Sequence (which subsystems are needed prior to others)

    • Test equipment necessary

    • Test environments necessary

  • The goal(s) at CDR are

    • Convey integration plans

    • Convey plans of how the CanSat is tested as a unit

Presenter: Name goes here

CanSat 2013 CDR: Team ### (Team Name)


Sensor subsystem testing overview

Sensor Subsystem Testing Overview

  • Discuss tests being performed in order to verify the sensor subsystem.

  • The test selection should demonstrate an understanding of what is important for testing each sensor at the subsystem and system levels.

  • It is not necessary to go through each test in detail, but provide:

    • What each test is to accomplish?

    • Constraints on testing (necessary operational subsystems, ground support equipment, etc.)

    • Pass/fail criteria and expected results – what are you looking for? (not just “it works” – discuss how you know it works)

CanSat 2013 CDR: Team ### (Team Name)


Video camera testing overview

Video Camera Testing Overview

  • SELECTABLE OBJECTIVE – ONLY REQUIRED IF SELECTED

  • Include:

    • Overview of camera testing and results, including pass/fail criteria, etc.

    • Include sample pictures, triggering mechanism, and diagrams of camera location and test setup

    • Test through put results

    • Image recovery

CanSat 2013 CDR: Team ### (Team Name)


Impact force sensor testing

Impact Force Sensor Testing

  • SELECTABLE OBJECTIVE – ONLY REQUIRED IF SELECTED

  • Overview of impact force sensor testing and results, including pass/fail criteria, etc.

  • Data storage sizing and format

CanSat 2013 CDR: Team ### (Team Name)


Dcs subsystem testing overview

DCS Subsystem Testing Overview

  • Discuss tests being performed in order to verify the DCS

  • Demonstrate an understanding of what is important for testing each components at the subsystem and system levels

  • It is not necessary to go through each test in detail, but provide:

    • What each test is to accomplish?

    • Constraints on testing (necessary operational subsystems, ground support equipment, etc.)

    • Pass/fail criteria and expected results – what are you looking for? (not just “it works” – discuss how you know it works)

    • Drop testing / simulation

CanSat 2013 CDR: Team ### (Team Name)


Mechanical subsystem testing overview

Mechanical Subsystem Testing Overview

  • Discuss tests being performed in order to verify the Mechanical Subsystem.

  • Demonstrate an understanding of what is important for mechanical testing at the subsystem and system levels. What each test is to accomplish?

    • Constraints on testing (necessary operational subsystems, ground support equipment, etc.)

    • Pass/fail criteria and expected results – what are you looking for? (not just “it works” – discuss how you know it works)

    • Deployment / separation testing

    • Acceleration / shock / survivability requirement testing

CanSat 2013 CDR: Team ### (Team Name)


Cdh subsystem testing overview

CDH Subsystem Testing Overview

  • Discuss tests being performed in order to verify the CDH Subsystem

  • Demonstrate an understanding of what is important for testing each component at the subsystem and system levels

  • It is not necessary to go through each test in detail, but provide:

    • What each test is to accomplish?

    • Constraints on testing (necessary operational subsystems, ground support equipment, etc.)

    • Pass/fail criteria and expected results – what are you looking for? (not just “it works” – discuss how you know it works)

    • Simulation test beds / ground system checkout tests

CanSat 2013 CDR: Team ### (Team Name)


Eps testing overview

EPS Testing Overview

  • Discuss the test being performed to verify the EPS

  • Demonstrate an understanding of what is important for testing each component at the subsystem and system levels

  • It is not necessary to go through each test in detail, but provide:

    • What each test is to accomplish?

    • Constraints on testing (necessary operational subsystems, ground support equipment, etc.)

    • Voltage sensor testing

    • Pass/fail criteria and expected results – what are you looking for? (not just “it works” – discuss how you know it works)

CanSat 2013 CDR: Team ### (Team Name)


Fsw testing overview

FSW Testing Overview

  • Discuss tests being performed in order to verify the flight software

  • Test selection should demonstrate an understanding of what is important for software at subsystem and system levels

  • It is not necessary to go through each test in detail, but provide:

    • What each test is to accomplish?

    • Constraints on testing (necessary operational subsystems, ground support equipment, etc.)

    • Pass/fail criteria and expected results – what are you looking for? (not just “it works” – discuss how you know it works)

    • Simulation test beds / ground system checkout tests

CanSat 2013 CDR: Team ### (Team Name)


Gcs testing overview

GCS Testing Overview

  • Discuss tests being performed in order to verify the GCS.

  • Demonstrate an understanding of what is important for testing each sensor at the subsystem and system levels

  • It is not necessary to go through each test in detail, but provide:

    • What each test is to accomplish?

    • Constraints on testing (necessary operational subsystems, ground support equipment, etc.)

    • Pass/fail criteria and expected results – what are you looking for? (not just “it works” – discuss how you know it works)

    • Simulation test beds / ground system checkout tests

CanSat 2013 CDR: Team ### (Team Name)


Mission operations analysis

Mission Operations & Analysis

Presenter Name(s) Go Here

CanSat 2013 CDR: Team ### (Team Name)


Overview of mission sequence of events

Overview of Mission Sequence of Events

  • Launch-day sequence of events

    • Should start with arrival at the launch site and proceed through recovery and data analysis

  • Include

    • Flow chart of events

    • Team member roles and responsibilities

    • Antenna construction and ground system setup

    • CanSat assembly and test

    • Delivery of telemetry data file to field judge for review

Presenter: Name goes here

CanSat 2013 CDR: Team ### (Team Name)


Field safety rules compliance

Field Safety Rules Compliance

  • Discuss development and content of the Missions Operations Manual for your CanSat

    • Two copies of the Mission Operations Manual are due at the Flight Readiness Review the day before launch

      • Assemble in three ring binders (the Texas launch site may be windy)

      • One copy is for the Flight Coordinator

  • Discuss development status

Presenter: Name goes here

CanSat 2013 CDR: Team ### (Team Name)


Cansat location and recovery

CanSat Location and Recovery

  • Discuss how you will find your CanSats in the field

Presenter: Name goes here

CanSat 2013 CDR: Team ### (Team Name)


Mission rehearsal activities

Mission Rehearsal Activities

  • Description of mission operations rehearsal activities including:

    • Details of activities rehearsed to date

      • Ground system radio link check procedures

      • Loading the egg payload

      • Powering on/off the CanSat

      • Launch configuration preparations (e.g., final assembly and stowing appendages)

      • Loading the CanSat in the launch vehicle

      • Telemetry processing, archiving, and analysis

      • Recovery

  • Description of written procedures developed/required

CanSat 2013 CDR: Team ### (Team Name)


Requirements compliance

The purpose of this section is to summarize and cross reference the compliance to the CanSat Competition Mission Guide requirements.

Requirements Compliance

Presenter Name(s) Go Here

CanSat 2013 CDR: Team ### (Team Name)


Requirements compliance overview

Requirements Compliance Overview

  • State current design compliance to requirements

  • Summarize content of the detailed slides that follow

  • If the design does not comply to the requirements, that is a serious issue – why?

CanSat 2013 CDR: Team ### (Team Name)


Requirements compliance 1 of 7

Requirements Compliance (1 of 7)

Use the Green (Comply), Yellow (Partial Compliance), and Red (No Comply) color codes as shown in the examples above for each requirement

CanSat 2013 CDR: Team ### (Team Name)


Requirements compliance 2 of 7

Requirements Compliance (2 of 7)

CanSat 2013 CDR: Team ### (Team Name)


Requirements compliance 3 of 7

Requirements Compliance (3 of 7)

CanSat 2013 CDR: Team ### (Team Name)


Requirements compliance 4 of 7

Requirements Compliance (4 of 7)

CanSat 2013 CDR: Team ### (Team Name)


Requirements compliance 5 of 7

Requirements Compliance (5 of 7)

CanSat 2013 CDR: Team ### (Team Name)


Requirements compliance 6 of 7

Requirements Compliance (6 of 7)

CanSat 2013 CDR: Team ### (Team Name)


Requirements compliance 7 of 7

Requirements Compliance (7 of 7)

CanSat 2013 CDR: Team ### (Team Name)


Management

Management

Presenter Name(s) Go Here

CanSat 2013 CDR: Team ### (Team Name)


Status of procurements

Status of Procurements

  • Provide status of sensor and component procurements

    • What has been ordered, when it arrives, etc.

    • This should include flight and GCS hardware (and software if being ordered)

  • This information should be reflected in the overall schedule

Presenter: Name goes here

CanSat 2013 CDR: Team ### (Team Name)


Cansat budget hardware

CanSat Budget – Hardware

  • Provide a table listing the costs of the CanSat flight hardware

  • Table should include

    • Cost of major components and hardware

    • Indication of whether these costs are actual, estimates, or budgeted values

    • Indication of hardware re-use from previous years

      • The current market value for re-used components should be included

    • Total expenses and compare to requirement(s)

CanSat 2013 CDR: Team ### (Team Name)


Cansat budget other costs

CanSat Budget – Other Costs

  • Table(s) (same format as Hardware Budget) showing

    • Ground control station costs

    • Other costs

      • Prototyping

      • Test facilities and equipment

      • Rentals

      • Computers

      • Travel

    • Income

      • Sources of project income

  • The goal(s) of this budget are

    • To provide an understanding of the overall design and development costs

    • Get the teams thinking about the overall costs including necessary funds for travel

    • Identify shortfalls in the budget that require attention

      • In the past some teams have not been able to attend the competition due to a lack of funds

      • If caught early enough, there are a number of resources for funding that may available to teams

        • THE COMPEITION DOES NOT PROVIDE ANY DEVELOPMENT FUNDING OR DONORS

CanSat 2013 CDR: Team ### (Team Name)


Program schedule

Program Schedule

  • Overview of development schedule to include

    • Competition milestones

    • Academic milestones and holidays

    • Major development activities

    • Component/hardware deliveries

    • Major integration and test activities and milestones

  • The schedule should be “wrapped up” to 1-2 levels

    • Show high-level tasks only in order to make the schedule readable

    • It is recommended a schedule at lower levels is developed in order to provide the team with tools for tracking progress and assessing trouble areas

  • The goals of this schedule are to

    • Provide a tool for the team to track progress of CanSat design and development

    • Provide tool for judges to assess trouble areas and offer ways for the team to best meet the objectives of the competition

  • A Gantt chart on one slide showing task start and stop dates and durations is recommended

    • Schedule should include linkages between tasks to provide the team with an idea of what happens in the overall flow when milestones are not met on time

  • Make sure the schedule is readable in the presentation

    • This may require the schedule to be broken between multiple slides

      • Failure to do so will result in a loss of points

CanSat 2013 CDR: Team ### (Team Name)


Shipping and transportation

Shipping and Transportation

  • Discuss plans for shipping/transporting the CanSat hardware to the launch site

  • In past competitions, CanSat hardware checked with airlines was lost

    • Consider options for shipping hardware to the launch site (typical for a satellite and ground system program)

    • Consider carry-on restrictions

  • Consider shipping/transportation of tools and equipment

    • Antenna mast and assembly

CanSat 2013 CDR: Team ### (Team Name)


Conclusions

Conclusions

  • Presentation summary and conclusions

  • In general include the following:

    • Major accomplishments

    • Major unfinished work

    • Testing to complete

    • Flight software status

CanSat 2013 CDR: Team ### (Team Name)


Presentation scoring additional information

Do Not Include the Following Charts in the Presentations

Presentation Scoring & Additional Information

The following slides provide additional information regarding presentation scoring, as well as recommendations for the presentations and slides

CanSat 2013 CDR: Team ### (Team Name)


Presentation scoring

Presentation Scoring

  • Each slide in this template is scored on a scale of 0 to 2 points

    • 0 = missing or no compliance to the intent of the requirement

    • 1 = topic incomplete or partial compliance to requirement(s)

    • 2 = complete and demonstrates requirement(s) met

  • Each section of the presentation (System Overview, Sensor Subsystems, etc.) is weighted according to the table

  • Each team will receive a link to a summary score sheet that will contain all their competition scores

CanSat 2013 CDR: Team ### (Team Name)


Ppt template use

PPT Template Use

  • All teams shall use this presentation template

  • Team logos

    • A team logo can be inserted into the placeholder location (and size) on the master slide

    • If no logo is to be used, remove the placeholder from the master slide

  • Team numbers in the footer should be updated in the footer information view

    • REMEMBER TO PUT YOUR TEAM NUMBER IN THE FOOTER

    • Team names are optional – if no team name is used, please delete from footer text

  • On each slide, replace the “Name goes here” in the bottom left corner with the name of the person(s) presenting that slide

    • This will allow the judges to know the person to address any questions or comments to

CanSat 2013 CDR: Team ### (Team Name)


Presentation template update log do not include in presentation

Presentation Template Update Log (Do not include in presentation)

  • 0.1 – Initial version for 2013

  • 2 – Updated with comments and shipping slide

  • 3 – Updated with telemetry data file on chart 79

  • 4 – Deleted extra Acronyms slide

  • 5x – Introduced compliance matrix (experimental)

  • 6 – Updated version for 2013 CDRs

CanSat 2013 CDR: Team ### (Team Name)


  • Login