1 / 43

< Your Team # > Your Team Name Here

< University Name >. TÜRKSAT Model Satellite Competition 201 9 Critical Design Review ( C DR ) Presentation Version 1 . 0. < Your Team # > Your Team Name Here. Systems Overview. < Pre senter Name Here >. Changes Since PDR. Summarize overview design changes since PDR

raymondgroff
Télécharger la présentation

< Your Team # > Your Team Name Here

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. <UniversityName> TÜRKSATModel SatelliteCompetition2019CriticalDesign Review (CDR)PresentationVersion 1.0 <Your Team # > Your Team Name Here

  2. Systems Overview <Presenter NameHere>

  3. Changes Since PDR Summarizeoverviewdesignchanges since PDR Please list the changes without detail. Details of the changes will be discussed in the following sections.

  4. Model Satellite Design • If there is a change in the model satellite design; • The design of the Model Satellite, which is decided, shallbe shown in general terms. • Present criteriasfor determineddesign • Include discussion of why the design was determined • Please indicate if there is no change in your model satellite design.

  5. Physical Layout • Demonstratephysical layout of selected model satellitedesignclearly • Components(Container, Sciencepayload, Mechanisms) • Dimensions • Relevant configurations(MountingcomponentandSeperationmechanism) • 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.

  6. Sensor Subsystem Design <Presenter NameHere>

  7. Subsystem Changes Since PDR • Sensor subsystemchangessince PDR must be specified in a table. • The reasons for the changes will be explainedclearly. • Power restrictions, • Tests, • Component size, • Usability, • Price. • If this subsystem has not been changed, thisslideshallonlycontainthetext<<No Change!>>

  8. GPS Sensor Trade & Specifications Solutionsmustbe specified in detail to ensure the continuity of the GPS data! • GPS sensorthat can be used in the designed Model Satelliteshallbe specifiedin a table in this slide. Inthetable: • Sensor specifications, • Dimensions andWeight, • Priceetc. • Indicate how totrade the GPS sensor andorderstatus.

  9. Auto-GyroSensor Trade & Selection 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! • Auto-GyroSensor that can be used in the designed Model Satelliteshall bespecified in a table in this slide.Inthetable: • Sensor specifications, • WorkingPrinciple, • Dimensions andweight, • Priceetc. • Indicate how totradetheAuto-GyroSensor andorderstatus.

  10. Descent Control Design <Presenter NameHere >

  11. Subsystem Changes Since PDR • Descentcontrolsubsystemchanges since PDR must be specified in a table. • The reasons for the changes will be explainedclearly. • If this subsystem has not been changed, thisslideshallonlycontainthetext <<No Change!>>

  12. ContainerDescent Control Strategy Describe the descent control strategy and specifywhatneedsto be tradedforthisstrategy. Indicatehow to mountand seperatethe passive or active descentcontrol system

  13. SciencePayloadDescent Control Strategy • Describe the descentcontrol strategy and specify what needs to be tradedforthisstrategy. • Indicatehow to mount and seperatethe passive or active descent control system

  14. Mechanical Subsystem Design <Presenter NameHere >

  15. Subsystem Changes Since PDR • Mechanicalsubsystemchanges since PDR must be specified in a table. • The reasons for the changes will be explainedclearly. • If this subsystem has not been changed, thisslideshallonlycontainthetext <<No Change!>>

  16. Container and SciencePayloadInterface • Explain separationmechanism of containerand sciencepayload. • Indicate how to mount these two parts of the modelsatellite. (Easymountingdesign is recommended) • The connection and separation mechanismshallbe clearly indicated; • The separation mechanism shallbe shown using visuals from different angles. • The working principles of the separation mechanism shallbe explained. • Morethanonepage can be used.

  17. Communication and Data Handling (CDH) Subsystem Design <Presenter NameHere >

  18. Subsystem Changes Since PDR • Communicationand Data Handling Subsystemchanges since PDR must be specified in a table. • The reasons for the changes will be explainedclearly. • If this subsystem has not been changed, thisslideshallonlycontainthetext <<No Change!>>

  19. Telecommand • 5-digit passwordinformation (e.g. X123C) definedforeachteamwill be sent as telecommand at the time of flightfromthegroundstationinterface. Thesciencepayloadshallsavethepasswordtothe SD Card. • Describeworkingprinciple. • IndicatePasswordinformation panel on groundstationinterface. • Show blockdiagram of theprocessfrompasswordentry on thegroundstationtosavingthepasswordtothe SD Card in thesciencepayload.

  20. ElectricalPower Subsystem (EPS) Design <Presenter NameHere >

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

  22. Power Budget The flight operation is expected to take a maximum of 20 minutes. (pre-flight + flight+ afterflight). Calculations shallbe made according to 60 minutes for possibleproblems. • Power budget in tabular format which includes; • Power consumption of each component(W) • Expected duty cycles for eachcomponent • 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.

  23. Flight Software (FSW) Design <Presenter NameHere >

  24. FSWChanges Since PDR • Changes in the FSWsubsystem 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 shallonly contain the text «No Change!».

  25. FSW StateDiagram • Flight Software Diagram; includes the states of the Model Satellite duringflight. • Include: • Samplingof sensors (includingrates) • Communications (command and telemetry data) • Mechanismactivations (separationalgorithm) • Majordecisionpoints • Powermanagement • Algorithm on how thelandingis understood. • FSW recoverytocorrectstateafterprocessorresetduringflight • Whatdata is usedtorecovery? • Includewhich data will be used for recovery of satellite after landing.

  26. GroundControl Station (GCS) Design <Presenter Name Here >

  27. GCS Changes Since PDR • Changes in the GCSsubsystem 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 shallonly contain the text «No Change!».

  28. GCS AntennaTrade & Selection • Specify the properties of the ground station antenna • How toconfigureantennamechanism • 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

  29. GCS Software Indicate which software packagewill be used A screenshot showing the user interface shallbe shown. Describetelemetry data recording and media presentation to judges for inspection Describe .csv/excel telemetry file creation Show how to create the simulation of the positioninformation of the model satellite in the groundstationinterface.

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

  31. Model Satellite Integration and Test Overview … • Discusshow tointegratesubsystems • The sequence of integrating subsystems shallbe shown in a diagram((The diagram showing the stages respectively shallbe used)) • Discusssystem and subsystemleveltesting • Transitions in diagram; decribewhichtestsareto be appliedtocombinewiththenextsubsystem. • Thegoal(s) at CDR are; • Team members together to determine the integration of the system's sub-systems(So how toassemble)and show them in a diagram. • Team membersshall be determinedwhichtestsarecarriedout at whichintegrationstage of thesystem.

  32. SystemLevel Testing Plan • For fully assembled Carrier and Science Payload (Model Satellite); • CommunicationTestingPlan • MechanismTestingPlan • Separation Testing Plan • Test plansshall be included the following information. • What to do step by step for each test, • What is targeted with the test

  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

  34. Mission Operations & Analysis <Presenter Name Here >

  35. Model Satellite Location andRecovery • How to determine the locationof the SciencePayloadshall be specifiedfor location detection and rescue operation. NOTE: Address and contact information shall be added to both the Container and the SciencePayload.

  36. Requirements Compliance <Presenter Name Here>

  37. Requirements Compliance Overview • Indicate stateof current design compliance to therequirements • Inthisslide; • It shallbe specified in numerical form that how many requests are compatible, partial, orincompatible. • If the design does not comply to the requirements, that is a serious issue. The cause of incompatibleshallbe explained.

  38. RequirementsCompliance • The following format shall be used. • List the requirements in thecompetition guide. • Color each well as yellow (PartialCompliance), red(No Comply) or green(Comply).

  39. Management <Presenter Name Here>

  40. Conclusions • Summaryandconclusions In general include the following; • Completedwork • Unfinishedwork • At which stage of the plan

  41. AdditionalInformation Do not includethefollowingslidesandthisslide in theyourpresentation.

  42. TemplateUse 1 2 3 4 5 • All teams mustuse this template • Team logos: • Team logo « view – slidemaster – (logo is added to the top left corner of the top template)– closemasterview» • Each team shall add teamname and number to the template. • View– slidemaster – (makenecessary arrangement in the relevant part of the top template) – closemasterview • On each slide, replace the “Presenter” in the bottom left corner with the name of the person(s)preparingthat slide

  43. Createan AdditionalSlide • You can use extra slides; • A slideincludinga different headingwill not be created! • The same slideheadingwill be created in the additional slide according to the following example. • Forexample; Model Satellite Integration and Test Overview has 6 slides • The slide headingswill 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)

More Related