Peer Review DINO July 9 2003 1 Agenda

Peer Review DINO July 9, 2003 1

Agenda l Overview l Structures l ADCS l Thermal l C&DH l Systems l COMM l CM l PWR l Actions and l Science l Software Review Summary 2

Overview Purpose: For everyone to understand the satellite at a systems level, help other subsystems with their current design, and to determine that interfaces between subsystems are correct. l Action Item forms l 3

ADCS Peer Review Jeff Parker Stephen Stankevich 4

Requirements Maintain attitude knowledge to within 2°. l Control s/c in 60° cone for boom deployment. l Maintain control in roll/pitch axis to +/- 10°. l Maintain yaw control per science requirements ~ +/- 10°. l 5

Requirements System use of less than 2 kg and 4 W l Weight l l Actuators < 1. 5 kg l Sensors < 1. 5 kg l More weight allotment possible l Power l Acuators @5 V and < 2. 5 W l Sensors < 1 W 6

Possible Hardware l Sensors l Magnetometer l Sun Sensor l Earth Sensor l Rate Gyro l GPS l Actuator l Torque Rod/Coil l Reaction Wheel 7

Sensor Trade Studies l Magnetometer l l l Sun Sensor l l Accurate measurement of s/c - sun direction vector in 2 axis. Earth Sensor l l l Low cost, low weight, low power Effective measurement of field to compare with model. Medium weight and power draw Very accurate measurement of earth horizon (Yaw Axis). Rate Gyro l l Large weight and expense Excellent measure of s/c rotation rates. 8

Sensors l Magnetometer l l l Honeywell HMC 2003 100 g 20 m. A @ 12 V 40μGauss Resolution with +/- 2 Gauss Range $200 Sun Sensor l Possible donation from Ithaco Space Systems 9

Torque Rods l l l Less complex and lighter than reaction wheels. Commonly made of cylindrical iron core wrapped with copper wire. The output is a magnetic dipole moment based on the current passed through the wire, # of turns of wire, and area of the rod. (M=INA) Dipole moment interacts with Earth’s magnetic field to create the desired torque. (T = Mx. B) Need to actuate torque rods as multiple current levels. 10

Torquer Sizing l Power l l l l l I = 150 m. A V = 5 V P = 0. 75 W Length = 0. 75” Diameter = 1. 8” Moment = 1 A*m 2 Mass < 0. 3 kg Power Dissipation < 0. 02 W # Turns ~ 40 11

Slew Times l l Torque Rods will not allow for immediate slew maneuvers of the s/c The larger the torque rods the quicker the slew times. 12

Converters l A/D Converters will be needed for the magnetometer and sun sensors l Intersil HI 7188 for magnetometer l 8 Channel, 16 Bit l. 1 m. A @ 5 V l D/A converter may be necessary for torque rods 13

ADCS Control Diagram 14

ADCS Flow Diagram 15

C&DH Peer Review 16

Why RPX_LITE? Processor: MPC 823 E l Software compatibility l Supports necessary interfaces l Lightweight, low power l 17

Requirements Imposed by EPS: 1 RS-232 serial port for subsystems control l Current Sensor readings? l General purpose I/O Lines? l 18

Requirements Imposed by COMM 1 dedicated RS-232 serial port to TNC l 1 RS-232 serial port to radios l 19

Requirements Imposed by Science l Multiple USB ports for cameras. l I think Science should be responsible for USB hub l Control lines? 20

Requirements Imposed by ADCS l 16 bit ADC with 4 channels (minimum) 21

Requirements Imposed by Tip. Mass l 802. 11 b link between main satellite and tip -mass 22

Other Requirements? l Structures l -? l Thermal l -? 23

Interface Board FLIGHT COMPUTER USB RESET SMC 1 SMC 2 I 2 C PCMCIA General Purpose I/O Pins TIP-MASS SCIENCE USB HUB RS 232 DRIVER RS 232 Serial 802. 11 b MULTIPLEXER CPLD ADC INTERFACE BOARD TNC RADIO COMM EPS ADCS Multiple Wires 24 Wireless

Power Needs FLIGHT COMPUTER (5 V, 1 A) RESET USB SMC 1 SMC 2 PCMCIA I 2 C General Purpose I/O Pins TIP-MASS SCIENCE RS 232 Serial RS 232 DRIVER USB HUB 802. 11 b (5 V, 1 A) (5 V, 7 m. A) (5 V min) MULTIPLEXER CPLD (5 V) (5 V, 150 m. A) ADC INTERFACE BOARD TNC RADIO COMM EPS ADCS Multiple Wires 25 Wireless

Communication System DINO Peer Review July 9, 2003 26

Subsystem Block Diagram 27

Power Requirements l Daytime Operation l Receiver: 0. 54 W (6 V, 90 m. A) always. l TNC: 5. 52 W (13. 8 V, 400 m. A) always. l Transmitter: 8. 4 W (6 V, 1. 4 A) for approx. 2 minutes, otherwise same as Receiver (0. 54 W). 28

Power Requirements l Nighttime Operation l Receiver: 0. 54 W (6 V, 90 m. A) always. l TNC: 5. 52 W (13. 8 V, 400 m. A) always. l Transmitter: 8. 4 W (6 V, 1. 4 A) for approx. 4 seconds, otherwise same as Receiver (0. 54 W). l Safe Mode l Same as nighttime. 29

Calculating Transmission Time l Time needed to send one packet: l 10 bits/byte * 256 bytes/packet 9600 bits/sec = 0. 267 sec/packet l Total transmission time (assuming 50 k. B per pass during daytime): l 0. 267 sec/packet * 50 k. B/pass 256 bytes/packet = 52 sec/pass 30

Transceiver Trade Study: Four Choices l ICOM IC-ID 1 1. 2 GHz digital l Pros Allows for small antenna l Built-in TNC with 64 -128 kbps baud rate l USB interface l l Cons Expensive l Only one frequency band: need half-duplex comm. l Newly released, untested, unlicensed by FCC l Needs new ground equipment l 31

Transceiver Trade Study l Kenwood TH-D 7 dual band 70 cm/ 2 m l Pros Operates in 2 frequency bands l One third of the cost of the ICOM radio l Compatible ground equipment already set up l Previous experience from other missions l l Cons Max. baud rate of 9. 6 kbps. l Requires larger antenna than ICOM l Uses RS-232 interface l 32

Transceiver Trade Study l TEKK SD-5200 synthesized radio and TEKK KS 960 crystal radio l Pros Can be set to one frequency by the manufacturer: no actual programming required (unlike Kenwood) l Currently being proven in space flight on Stanford’s Quakesat mission l Significantly cheaper than the Kenwood radios l l Cons l Only UHF version available: so we would need a different radio for VHF (no longer advantageous) 33

Design Decision l l Two Kenwood TH-D 7 radios: one for uplink, the other for downlink. Reasons l l Only choice that allows two distinct channels for uplink and downlink, respectively. Much better to use same model for both channels 9. 6 kbps should be a sufficient baud rate for the purposes of this mission No idea when the ICOM 1. 2 GHz radio will ever be available for our use. 34

Antenna Trade Study l Monopole l Pros l Simple design l Does not take up space on the satellite’s surface l Cons l Deployable l Could be very long (~50 cm) 35

Antenna Trade Study l Patch l Pros l Preferable gain pattern l Non-deployable l Cons l Could occupy a lot of space on nadir surface l More complicated design process l More expensive 36

Power DINO Peer Review 37

ADCS COMM 12 Volt Line Science 5 Volt Line Structures 28 Volt Line C&DH EPS System Inhibits Batteries FITS Solar Array Side Panel and Aero Fins 38

EPS System Voltage Bus Batteries Charge Controller Switches Microprocessor Sensors C&DH 39

The Ball Systems vs. CU System The drop dead decision date is tomorrow l Ball: Complicated, Clean, Expensive l CU: Simple, Cheap, Not as good l Ball will advise regardless l 40

Power Distribution and Monitoring l Must distribute and regulate power to all subsystems l l l +24 V (regulated) +15 V (unregulated) +12 V (regulated) +5 V (regulated) Must be commandable by C&DH l l Communication will be through a RS-232 port The PWR team must provide a commands list to C&DH and Software 41

Power Distribution and Monitoring l 4 internal temperature monitors for each battery cell l Voltage Monitoring l Battery Stack Voltage l All major voltage buses l Each solar panel l The current draws from each subsystem must be monitored 42

Power Distribution and Monitoring The temperature should nominal be 20ºC and can fluctuate ± 20ºC. l The latest sample from the monitoring must be able to be stored in memory. l All subsystems must be able to turn on/off. l 43

Structural Concerns • The power system shall weight less than 2. 25 kg The system will use only required components The system will use the lightest components possible • The power system shall be structurally supported The batteries will be in a contained box with potting material The EPS will be in box mounted to a side panel of the satellite • The structure ground will be separate from the electrical ground The structure will have less than an 1 ohms resistance The boxes of the structure will be anodize to prevent electrical shorts 44

Power Safety l Meeting all safety concerns Following NASA’s guidelines for safety The proper connections will be made between systems The system will be properly grounded and tested Inhibits will be used to ensure systems are NOT powered 4 inhibits will be used to separate the power sources switches will be used to turn on and off devices Ball Aerospace will assist us in testing Selection of batteries will be supervised Charge control system will be test with Ball Engineers 45

Switch l l Pros Simple setup, Is either on or off. Low power usage, using less than a Mw. Controlled by high and low signals. The cost of switches will between $1 -3. Cons There is no fail safe. May not be able to handle the power going through it. Relays l Pros Manages large amounts of power. Used on previous mission. Resets to a open state. Simple circuit design Widely available costing about $2 -5 l Cons Has a bulky size, about 2 -3 cm tall. Will require a driver to trigger. Slow reaction time, the time is based how fast the coils will charge. A switch can do most of the same functions 46

Lithium Batteries 4 Cell Stack l~3. 7 V/Cell, 14. 8 V Stack l. At least 4 A-hr capacity l. Cells must be structurally contained l. Cells from Valence Tech. 47

Why Lithium-Polymer? High capacity, small physical size and weight make an unbeatable combination l No liquid electrolyte reduces risk of fire/short l Support from Ball Aerospace l 3. 7 V/Cell l Nickel-based cells are too heavy and lack enough capacity l 48

What’s the catch? l Cell stack will need careful charging to make it last for entire mission l l l Charge controllers will need to have different, optimal charge profiles Each cell in the stack will need temperature monitoring and shunt diodes Cells have no integral structure and must be completely supported No Space Shuttle flight heritage Battery system must be two-fault tolerant 49

Science Jessica Pipis 50

51

Power Needs For Camera’s l l l A 5 Volt line going to each camera is needed. To start up, each camera will require 190 m. A. When idle, each camera will require 178 m. A. While taking a picture, each camera will require 186 m. A. An interface board will require power to switch between camera’s. 52

Data Each picture is about 200 k at maximum resolution (1248 x 960). l Takes about 10 -15 seconds for images to store. l Takes a couple minutes to pull pictures off of the camera’s. l l May take more or less time depending on software. 53

Durability of Camera’s All components (except for lens) look to be secured to circuit board. l The circuit board will need to be conformal coated. l Housing for lens is only concern. l l Not secured to circuit board. l A box can be built to secure it. l Unknown plastic used for casing We may find way to get plastic analyzed. l We may find a replacement casing. l 54

Software Subsystem 55

Overview l Ground software l Uplink commands/schedule to spacecraft l Downlink H&S/science data from spacecraft l Flight software l Perform commands from ground l Gather H&S and process science data l Update schedule based on opportunities or problems 56

Ground S/W - Uplink Immediate Cmds Web browser Scheduled My. SQL Cmds Events SCL Cmds COMM Pkts STK Schedules Disk/ Files = H/W Interface 57

Ground S/W - Downlink Sci data Web browser Sensor data My. SQL Orbit data H&S (All) SCL COMM Pkts STK H&S (ADCS) Pictures = H/W Interface Disk/ Files Sci data (pictures) 58

Ground S/W – H/W Interfaces l Radio to Communications module (COMM) l Could be different for each ground station l CU’s radio requires serial RS-232 connection l Software will handle serial RS-232 and have the ability to add others as needed l TNC to Communications module (COMM) l Could be different for each ground station l CU’s TNC requires serial RS-232 connection l Software will handle serial RS-232 and have the ability to add others as needed 59

Ground S/W – S/W Interfaces l Web to My. SQL l Perl l Inputs and outputs: TBD l Web to STK l Perl or C++ l Inputs and outputs: TBD l Web to SCL l Perl or C++ l Inputs and outputs: TBD 60

Ground S/W – S/W Interfaces l COMM to SCL l C++ l Inputs and outputs: TBD l COMM to STK l C++ l Inputs and outputs: TBD l COMM to My. SQL l C++ l Inputs and outputs: TBD 61

Ground S/W – S/W Interfaces l STK to My. SQL l Perl l Inputs and outputs: TBD 62

Ground S/W – Human Interfaces l Website to issue commands l MOPS interface l Distributed Investigator interface l General Public interface l Website to see H&S and Sci data l MOPS interface l Distributed Investigator interface l General Public interface 63

Ground S/W – Human Interfaces STK to visualize current and expected orbit characteristics – MOPS interface only l SCL to visualize data/cmds flowing to and from spacecraft – MOPS interface only l 64

Flight S/W – Process_Cmd ? BPGEN ? SCI ? SWM ? I 2 C_mgr serialmgr usbmgr SCL DB COMM Route_cmd ADCS POWER SCL ? = H/W Interface 65

Flight S/W – Process_Reply ? BPGEN ? SCI ? SWM ? I 2 C_mgr serialmgr usbmgr SCL DB COMM Return_reply ADCS POWER SCL ? = H/W Interface 66

Flight S/W – H/W Interfaces l Radio to Communications module (COMM) l Either serial or USB l TNC to Communications module (COMM) l Either serial or USB Software to Serial (exists) l Software to I 2 C (exists) l Software to USB (yet to be developed) l 67

Flight S/W – S/W Interfaces l Process. Task functions to Process. Task objects l l l SCL to Process. Task objects l l l C++ Inputs and outputs: exists Process. Task objects to IO managers l l C++ Inputs and outputs: serial and I 2 C exist, USB TBD 68

Flight S/W – S/W Interfaces l Process. Task objects to SCL DB l C++ l Inputs and outputs: exists l Process. Task objects to COMM l C++ l Inputs and outputs: exists 69

Other S/W Tasks l Besides the existing Process. Tasks talking to hardware, DINO Software needs to: l l Convert stereo images to topo maps Reschedule failed events within SCL Schedule new images when unexpected opportunities arise (i. e. new clouds are seen) No new interfaces needed but this is all new software code that needs to be written and tested. 7 70

Trade Studies l Linux vs. Vx. Works l Linux has bigger kernel l Linux = about 3 mb +/- 1 mb l Vx. Works = about 1 mb +/- 0. 5 mb l Flight software needs to be ported l All kernel calls changed = 2 -3 week task l Memory management (i. e. shared memory) = 3 -4 week task l Flight code compiled into own libraries l Starting flight code would change 71

Trade Studies l Linux vs. Vx. Works (cont) l Cross compiling needed for PPC l Need to compile kernel on a machine like Thinker or another Linux computer l Much bigger knowledge base for Linux l New students to Space Grant can help development much quicker than learning Vx. Works l Questions can be posted on discussion groups and more likely to be answered 72

Trade Studies l Linux vs. Vx. Works (cont) l l Our recommendation: Linux (mostly for the student’s ability to start work with it) Vx. Works will be contingency OS if Linux development/porting takes too long (time TBD) Still need to decide on which distribution of Linux: l l Commercial: Monta. Vista, Red. Hat, Time. Sys Free: Debian, mu. Linux, Thin. Linux, etc. 73

Structures and Mechanisms - Peer Design Review - 10/7/2020 Jen Getz Anthony Lowrey Grayson Mc. Arthur Tim Shilling Terry Song

- Table Of Contents Structure l Deployable l Block Diagram l Needed from other Teams l 75

Revision C Structure Dimensions: 18. 15 in x Ø 17. 75 in Mass: 5. 78 kg Material: Aluminum 6061 * All dimensions are in inches * 76

Revision C Mounting Holes * All dimensions are in inches * Side Top 77

Revision C Clearance * All dimensions are in inches * Side Bottom Top 78

Boxes Tall Components Short Components Benefits * Less wasted material = Lower Cost * Internal components more accessible * Mounting is more flexible 79

Boom Deployment l Open Loop System (Push tip mass away with springs and let the system deploy on its own) l Mini-Lightband release ring or Hop Release 80

Hight Output Paraffin Actuator (H. O. P) l Pin Puller Less then 120 g l Small, only about 3 inches tall and ¾ inch diameter l 50 lbs of force l Activated with 28 V at 18 watts, which heats up the wax inside the piston, expanding it and causing the pin puller to move l 81

Thin Film Solar Arrays FITs solar Array Deployment 82

One H. O. P = Multiple Deployments 83

FITs and Aerofins Release Mechanism Spring Pushes Latch H. O. P Released Pin Released 84

Aerofins and FITS solar Arrays Input and Control Aerofins and FITs Solar Arrays H. O. P 18 watts @ 28 V for 1. 5 minutes High/Low output (Switch signaling final released position) Composite Hinges 10 watts @ 28 V per Hinge for 1 minute 2 -4 Hinges required High/Low output (Switch signaling final deployed position) 85

Boom Input and Control OR H. O. P 18 watts @ 28 V for 1. 5 minutes Lightband Separator 10 watts @ 12 V for 1 minute High/Low output (Switch successful separation and final deployed position) 86

Antenna Input and Control Solenoid 5 watts at 12 V High/Low output (Switch signaling final deployed position) 87

Summarized Structure’s Needs l l l 7 -9 hi/low output lines, signaling various stages of deployment 2 Solenoids, 5 watts at 12 V (May not be needed) 1 or 2 H. O. Ps, 18 watts @ 28 V for 1. 5 minutes 1 possible Lightband Separator, 10 watts @ 12 V for 1 minute 4 total, 2 at a time deployment Composite Hinges, 10 watts @ 28 V per Hinge for 1 minute 88

Thermal Subsystem Peer Review 7 -9 -3 89

Objective: To maintain all components of the space craft within their specific temperature range 90

Method Model Empty Spacecraft for entire orbit: Assumptions: • ISS Orbit • Thermal Properties • Structure Results: • Heat gain from Radiation • Heat reflected within satellite 91

Inside-the-Box Modeling Thermistors Used to monitor temperatures at specific locations during orbit. This will allow for us to troubleshoot during the mission when components are not acting properly. • Sensor is glued to surface of interest, where it creates a specific resistance in response to temperature measurement. • Approximately, 50 thermistors will be required at $3 -$6 each. 92

Inside-the-Box Modeling Temperature Control • Isolation Some sensitive electrical components will need to be isolated from the radiative/conductive environment. We can do this thru MLI blankets. • Heat Reservoirs Components which are exposed to alternating hot and cold modes, will need to be in contact with heat reservoirs which will both gather and supply heat when needed. 93

Inside-the-Box Modeling Heat Expulsion • Radiator: The radiator rejects excess heat into space. • Placement: The best position for the radiator is the earth facing side of the satellite. This should not affect the cameras, and is standard practice. 94

What’s Next? • Thermal Model Upon reporting specifications of materials and equipment, as well as their modes of operation, our model can be expanded to increase accuracy. • Placement of Thermistors will result from the reporting of these specifications, so we can identify points of interest for temperature measurement. 95

References • http: //www. angels-crossing. com/gifts. html • gore. ocean. washington. edu/. . . / Students/Crone/therm. htm • http: //www. resonancepub. com/images/Image 20. g if • www. facesofyve. com/business/ index. shtml 96

Systems Peer Review 97

Satellite Communications Serial Digital Data Ethernet Analog Data PWR Cam 1 Cam 2 GSE Imaging Wireless USB RF FIN 1 FIN 2 C&DH TNC Thermal HOP Mag. Sun Sen. Radio 1 Radio 2 FITS 1 Boom RX Ant. TX Ant. FITS 2 98

15 V 12 V Satellite Power Cam 1 Cam 2 Imaging HOP SW Radio 2 5 V 28 V Thermal FIN SW 1 Batt GSE FIN SW 2 Radio 1 FITS SW 1 C&DH FITS SW 2 Power Wireless HOP TNC Sun Sen. EMC 1 Prim SA Back SA Mag. Boom EMC 2 EMC 3 TR 1 TR 2 TR 3 EMC 4 99

Satellite Mass Budget Allocation (%) Goal (Budget) Current (kg) ADCS 14 2. 63 0. 12 C&DH 3 0. 56 0. 15 Comm 5 0. 94 0. 70 Power 14 2. 63 1. 44 Science 8 1. 50 0. 07 Software 0 0. 00 Str/Mech 49 9. 19 6. 94 Thermal 2 0. 38 0. 00 Cabling 5 0. 94 Total 18. 75 Margin 6. 25 100% 25. 00 9. 42 Subsystems Total 100

Tip Payload Mass Budget Allocation (%) Goal (Budget) Current (kg) ADCS 0 0. 00 C&DH 0 0. 00 Comm 10 0. 38 0. 00 Power 20 0. 75 0. 31 Science 13 0. 49 0. 00 Software 0 0. 00 Str/Mech 52 1. 95 0. 00 Thermal 2 0. 08 0. 00 Cabling 3 0. 11 Total 3. 75 Margin 1. 25 100% 5. 00 0. 31 Subsystems Total 101

Daytime Power Budget Goal (Budget) Power Available Subsystems Goal (Budge t) Current Mission Power (W) Duration (min) Budget (Whr) Allocation (%) 30. 0 55 27. 50 ADCS 4. 0 55 3. 67 16. 7 3. 7 0. 3 C&DH 4. 0 55 3. 67 16. 7 3. 6 Comm Rx 1. 0 55 0. 92 4. 2 0. 9 6. 7 Comm Tx 19. 0 5 1. 58 7. 2 1. 6 0. 1 Power 1. 0 55 0. 92 4. 2 0. 9 -2. 6 Science 11. 0 50 9. 17 41. 7 9. 2 1. 1 Software 0. 0 55 0. 00 0. 0 Str/Mech 0. 0 0. 0 Thermal 2. 3 55 2. 09 9. 5 2. 1 0. 0 22. 0 5. 5 100. 0% 27. 5 9. 2 Total Margin Total 102

Nighttime Power Budget Goal (Budget) Power Available Subsystems Power (W) Duration (min) Budget (W -hr) Allocation (%) 30. 0 35 17. 50 Goal (Budget) Current Miss ion Pow er ADCS 4. 0 20 1. 33 9. 5 1. 3 0. 3 C&DH 4. 0 35 2. 33 16. 7 2. 3 Comm Rx 1. 0 35 0. 58 4. 2 0. 6 10. 0 Comm Tx 19. 0 3 0. 95 6. 8 1. 0 0. 0 Power 1. 0 35 0. 58 4. 2 0. 6 13. 6 Science 0. 0 0. 0 Software 0. 0 35 0. 00 0. 0 Str/Mech 0. 0 0. 0 Thermal 2. 0 35 1. 17 8. 3 1. 2 0. 0 14. 0 3. 5 49. 6% 17. 5 Total Margin Total 26. 2103

Configuration Management Document Naming l DINO-SUBSYS-TYPE-NAME, Rev. 1 l l SUBSYS: A two to four letter description of the subsystem involved. l TYPE: A two to four letter description of the type of document. l NAME: A six letter abbreviation of the document title. 104

Subsystems Management MNG Systems SYS Software SW Structures STR Mission Operations MOPS Communications COMM Thermal THR Attitude Determination/ Control ADCS Command Data Handling CDH Power PWR Mechanisms MECH Imaging IMG 105

Document Type Requirements RQT Part Lists PL Material Lists ML Report RPT Plan PLN Procedures/Instructions PROC Manual MAN Policy POL Drawing DRW Part PRT Assembly (not a plan) ASM 106

Actions and Summary Action Items from review l Requirements updating l Requirements Review on 7/23/03 l SHOT Workshop l l Thursday at 2: 00 Power and Inhibits l Friday at 8: 15 Nano. Sat PDR Overview l Logo Contest July 17, 2003 at the huddle 107