USUSat III - TOROID TOmographic Remote Observer of Ionospheric Disturbances Preliminary Design...
-
Upload
samuel-weaver -
Category
Documents
-
view
215 -
download
0
Transcript of USUSat III - TOROID TOmographic Remote Observer of Ionospheric Disturbances Preliminary Design...
USUSat III - TOROIDTOmographic Remote Observer of Ionospheric Disturbances
Preliminary Design ReviewPreparation
Preliminary Design Review
• August 11-12, 2005– New Engineering Building– AFRL wants attendance to all
presentations• Prep for PDR
– Small Satellite Conference Display
– PDR Slide Presentation– Satellite Demonstration– Documentation
• Budgets• Requirements
• We are trying to sell the mission and sell the satellite
RISK
Y
PDR Slides
• 15-20 Slides per subsystem• Due 5:00 pm, July 15, 2005 to Jared’s inbox• Update slides and documentation from FCR.• Slide organization:
– This is what we want to do • Your subsystem requirements. Remember that good
requirements are specific and have a reason why. Refer to SCR System requirements for flow down.
PDR Slides
• Slide organization (con’t)– This is what we are going to do – This defines the design.
• For example, Comm req 30.1 states: The communication system shall provide a link for transmitting commands from the USU Ground Station to the spacecraft. This is accomplished through the TNC and TEKK design.
– This is what we have done.• Give a status report, what aspects of the subsystem are complete
– This is the proof that our design meets our requirements• We need to show that our design meets the requirements already
laid out. This is where test results and so forth can be used
– This is what is left• Outline what remains to be completed
Documentation
• We have not received specific information from AFRL. Expect the following:– Budgets, ie Link Budget, Computing Budgets,
Mass Budget, Thermal, Power, etc. Due July 22.
– Each subsystem needs to create a Subsystem Requirements document. This will be due July 22
Example BudgetDocument Name: Computing Budget Bus Information The purpose of the computing budget is to identify modes or systems that drive the design of the C&DH system.Document Number: xx-xxx 1 direction synchronous serial, 100 kb/sRevision: 1 Bus Speed 100000 bits/secondCreated By: Stephen Forbes Should also include a block diagram of the C&DH systemDate Created: 6/9/2005Date Modified: 6/14/2005
Microcontroller Name
On Board Storage (kb) Commands
Data Generation (bits)
Storage Utilization (%)
Bus Data Transmission (bits)
Time to Transmit (seconds)
Data recipient/source
Power 100Get Voltage 176 0.176 - PowerGet Current 176 0.176 - PowerGet Exterior Temps 256 0.256 - PowerGet Interior Temps 256 0.256 - PowerSend Data Frame - - 2048 0.02048 SchedulerNav Aids On - - - PowerNav Aids Off - - - PowerToggle Interrupt line - - - All
Comm 100Send Data Frame - - 2048 0.02048 SchedulerRelay ground Command - - 640 0.0064 SchedulerRelay Telemetry 2048 2.048 - - CommGet Health data 256 0.256 - - CommToggle Interrupt Line - - - - All
Small Satellite Conference Display
• We are in the corner in the same room as last year.
• The display will include– 5’ table– Transportation frame– Computer w/ Flat Screen
monitor– Satellite – Documentation
• The computer will run– All animations– Tornado– LabVIEW– The Website
USU’s Booth
Satellite Demonstration
• During PDR, we will be in the New Engineering Building, room 101 or 103.
• Any Ideas or suggestions?
Schedule
July 11
USUSat Mtg
Monday Tuesday Wednesday Thursday Friday Saturday Sunday
12 13 14 15
Subsystem Slides DUE!!
16 17
18
USUSat Mtg
19 20 21 221. PDR Presentation Complete.2. Subsystem Documentation DUE !!
23 24
25
USUSat Mtg
26 27 28 29
1. All PDR reqs met.2. Display design done.
30
All PDR doc. available to team for review
31
PDR Presentation and Doc DUE to AFRL!!!!!
August 1
USUSat Mtg – review PDR doc.
2 3 4 5
Demonstration ready
6 7
8
USUSat MtgSmall Sat
9
Small Sat
10
Small Sat
11
Small SatPDR
12
PDR
13 14
7/11/2005 - 8/12/2005