1. <Your Team # > Your Team Name Here
<University Name>
TÜRKSAT Model Satellite Competition Critical Design Review (CDR) Presentation Version 1.0
<Your Team # >
Your Team Name Here

2. <Presenter Name Here>
Systems Overview
<Presenter Name Here>
Presenter:

3. Summarize overview design changes since PDR
Please list the changes without detail.
Details of the changes will be discussed in the following sections.
Presenter:

4. Model Satellite Design
If there is a change in the model satellite design;
The design of the Model Satellite, which is decided, shall be shown in general terms.
Present criterias for determined design
Include discussion of why the design was determined
Please indicate if there is no change in your model satellite design.
Presenter:

5. Demonstrate physical layout of selected model satellite design clearly
Components(Container, Science payload, Mechanisms)
Dimensions
Relevant configurations (Mounting component and Seperation mechanism)
Dimensions and positions of electronic components
Exploded model can be demonstrate
Specify a detailed idea about Model Satellite design. It should be a CAD drawing and CAD drawings should include arrows pointing to three axes.
Presenter:

6. Sensor Subsystem Design
<Presenter Name Here>
Presenter:

7. Subsystem Changes Since PDR
Sensor subsystem changes since PDR must be specified in a table.
The reasons for the changes will be explained clearly.
Power restrictions,
Tests,
Component size,
Usability,
Price.
If this subsystem has not been changed, this slide shall only contain the text <<No Change!>>
Presenter:

8. GPS Sensor Trade & Specifications
GPS sensor that can be used in the designed Model Satellite shall be specified in a table in this slide. In the table:
Sensor specifications,
Dimensions and Weight,
Price etc.
Indicate how to trade the GPS sensor and order status.
Solutions must be specified in detail to ensure the continuity of the GPS data!
Presenter:

9. Auto-Gyro Sensor Trade & Selection
Auto-Gyro Sensor that can be used in the designed Model Satellite shall be specified in a table in this slide. In the table:
Sensor specifications,
Working Principle,
Dimensions and weight,
Price etc.
Indicate how to trade the Auto-Gyro Sensor and order status.
How to position the gyro sensor in the design, posture information and the evaluation of the axis to be simulated must be explained in detail!
Presenter:

10. Descent Control Design
< Presenter Name Here >
Presenter:

11. Subsystem Changes Since PDR
Descent control subsystem changes since PDR must be specified in a table.
The reasons for the changes will be explained clearly.
If this subsystem has not been changed, this slide shall only contain the text <<No Change!>>
Presenter:

12. Container Descent Control Strategy
Describe the descent control strategy and specify what needs to be traded for this strategy.
Indicate how to mount and seperate the passive or active descent control system
Presenter:

13. Science Payload Descent Control Strategy
Describe the descent control strategy and specify what needs to be traded for this strategy.
Indicate how to mount and seperate the passive or active descent control system
Presenter:

14. Mechanical Subsystem Design
< Presenter Name Here >
Presenter:

15. Subsystem Changes Since PDR
Mechanical subsystem changes since PDR must be specified in a table.
The reasons for the changes will be explained clearly.
If this subsystem has not been changed, this slide shall only contain the text <<No Change!>>
Presenter:

16. Container and Science Payload Interface
Explain separation mechanism of container and science payload.
Indicate how to mount these two parts of the model satellite. (Easy mounting design is recommended)
The connection and separation mechanism shall be clearly indicated;
The separation mechanism shall be shown using visuals from different angles.
The working principles of the separation mechanism shall be explained.
More than one page can be used.
Presenter:

17. Communication and Data Handling (CDH) Subsystem Design
< Presenter Name Here >
Presenter:

18. Subsystem Changes Since PDR
Communication and Data Handling Subsystem changes since PDR must be specified in a table.
The reasons for the changes will be explained clearly.
If this subsystem has not been changed, this slide shall only contain the text <<No Change!>>
Presenter:

19. Telecommand
5-digit password information (e.g. X123C) defined for each team will be sent as telecommand at the time of flight from the ground station interface. The science payload shall save the password to the SD Card.
Describe working principle.
Indicate Password information panel on ground station interface.
Show block diagram of the process from password entry on the ground station to saving the password to the SD Card in the science payload.
Presenter:

20. Electrical Power Subsystem (EPS) Design
< Presenter Name Here >
Presenter:

21. Changes in the EPS subsystem since PDR shall be specified in a table.
EPS Changes Since PDR
Changes in the EPS subsystem since PDR shall be specified in a table.
Clearly explain the reasons for the changes.
If this sub-system has not been changes; the slide shall only contain the text «No Change!».
Presenter:

22. Power Budget Power budget in tabular format which includes;
Power consumption of each component(W)
Expected duty cycles for each component
Each line shall contain the tolerance value and the source of the information
Estimated, data sheet, measurement
Total power consumed(mAh)
How to charge if the battery (s) can be charged and what is the charging time?
It should be indicated whether the total power of the battery can feed the whole system for more than 1 hour.
The flight operation is expected to take a maximum of 20 minutes. (pre-flight + flight+ after flight). Calculations shall be made according to 60 minutes for possible problems.
Presenter:

23. Flight Software (FSW) Design
< Presenter Name Here >
Presenter:

24. Changes in the FSW subsystem since PDR shall be specified in a table.
FSW Changes Since PDR
Changes in the FSW subsystem since PDR shall be specified in a table.
Clearly explain the reasons for the changes.
If this sub-system has not been changes; the slide shall only contain the text «No Change!».
Presenter:

25. FSW recovery to correct state after processor reset during flight
FSW State Diagram
Flight Software Diagram; includes the states of the Model Satellite during flight.
Include:
Sampling of sensors (including rates)
Communications (command and telemetry data)
Mechanism activations (separation algorithm)
Major decision points
Power management
Algorithm on how the landing is understood.
FSW recovery to correct state after processor reset during flight
What data is used to recovery?
Include which data will be used for recovery of satellite after landing.
Presenter:

26. Ground Control Station (GCS) Design
< Presenter Name Here >
Presenter:

27. Changes in the GCS subsystem since PDR shall be specified in a table.
GCS Changes Since PDR
Changes in the GCS subsystem since PDR shall be specified in a table.
Clearly explain the reasons for the changes.
If this sub-system has not been changes; the slide shall only contain the text «No Change!».
Presenter:

28. GCS Antenna Trade & Selection
Specify the properties of the ground station antenna
How to configure antenna mechanism
Indicate the strategy of transporting and installing the antenna in the competition area
How to position the antenna to perform its task
How to take security measures
Presenter:

29. Indicate which software package will be used
GCS Software
Indicate which software package will be used
A screenshot showing the user interface shall be shown.
Describe telemetry data recording and media presentation to judges for inspection
Describe .csv/excel telemetry file creation
Show how to create the simulation of the position information of the model satellite in the ground station interface.
Presenter:

30. Model Satellite Integration and Test
< Presenter Name Here >
Presenter:

31. Model Satellite Integration and Test Overview
Discuss how to integrate subsystems
The sequence of integrating subsystems shall be shown in a diagram((The diagram showing the stages respectively shall be used))
Discuss system and subsystem level testing
Transitions in diagram; decribe which tests are to be applied to combine with the next subsystem.
The goal(s) at CDR are;
Team members together to determine the integration of the system's sub- systems(So how to assemble) and show them in a diagram.
Team members shall be determined which tests are carried out at which integration stage of the system. …
Presenter:

32. System Level Testing Plan
For fully assembled Carrier and Science Payload (Model Satellite);
Communication Testing Plan
Mechanism Testing Plan
Separation Testing Plan
Test plans shall be included the following information.
What to do step by step for each test,
What is targeted with the test
Presenter:

33. Enviromental Test Plan
For fully assembled Carrier and Science Payload (Model Satellite);
Drop Test
Thermal Test
Vibration Test
Test plans shall be included the following information.
What to do step by step for each test,
What is targeted with the test
Presenter:

34. Mission Operations & Analysis
< Presenter Name Here >
Presenter:

35. Model Satellite Location and Recovery
How to determine the location of the Science Payload shall be specified for location detection and rescue operation.
NOTE: Address and contact information shall be added to both the Container and the Science Payload.
Presenter:

36. Requirements Compliance
<Presenter Name Here>
Presenter:

37. Requirements Compliance Overview
Indicate state of current design compliance to the requirements
In this slide;
It shall be specified in numerical form that how many requests are compatible, partial, or incompatible.
If the design does not comply to the requirements, that is a serious issue. The cause of incompatible shall be explained.
Presenter:

38. Requirements Compliance
The following format shall be used.
List the requirements in the competition guide.
Color each well as yellow (Partial Compliance), red (No Comply) or green (Comply).
Requirements
Comply / No Comply / Partial
X-Ref Slide(s) Demonstrating Compliance
Team Comments
or Notes
The Model Satellite shall consist of two parts: Science Payload and Container.
Comply
x, y, z
Compatible
Total mass of the Model Satellite (science payload and container) shall be grams +/- 20 grams.. --
The science payload shall acquire outside temperature, air pressure, altitude, descent rate position, battery voltage and axes data during the fligth.
Partial
Medium Problem; Why?
The satellite should send the measured data continuously to the ground station every second (1 Hz) in the form of packages suitable for the given telemetry format.
No Comply
Big Problem; Why? and Solution suggestion.
The Model Satellite shall give an audible warning when science payload is landed.
The video shall be monitored in real time on the ground station and recorded in the ground station.
The computer where the ground station software is to be operated shall have at least two hours of battery full.
Presenter:

39. <Presenter Name Here>
Management
<Presenter Name Here>
Presenter:

40. Summary and conclusions In general include the following;
Completed work
Unfinished work
At which stage of the plan
Presenter:

41. Additional Information
Do not include the following slides and this slide in the your presentation.

42. Template Use 1 2 3 4 5 All teams must use this template Team logos:
Team logo « view – slide master – (logo is added to the top left corner of the top template) – close master view»
Each team shall add team name and number to the template.
View – slide master – (make necessary arrangement in the relevant part of the top template) – close master view
On each slide, replace the “Presenter” in the bottom left corner with the name of the person(s) preparing that slide 1 2 3 4 5

43. Create an Additional Slide
You can use extra slides;
A slide including a different heading will not be created!
The same slide heading will be created in the additional slide according to the following example.
For example; Model Satellite Integration and Test Overview has 6 slides
The slide headings will look like this;
Model Satellite Integration and Test Overview (1/6)
Model Satellite Integration and Test Overview (2/6) .
Model Satellite Integration and Test Overview (6/6)