<<

5/1/19

Seminar 11 Management & System Design Guidance Robert Stengel FRS 148, From the to the Princeton University Project Management & Spacecraft Design Fundamentals of Systems, Ch 1 NASA-SP-2016-6105 Spacecraft Guidance: Understanding Space Sec 12.3

Copyright 2019 by Robert Stengel. All rights reserved. For educational use only. 1 http://www.princeton.edu/~stengel/FRS.html

Systems Engineering and Management § Introduction § Fundamentals of System Engineering § Concepts in Systems Engineering § Project Development Process § Management of the Development of Space Systems § Organization

Pisacane, V., Fundamentals of Space System Design, Ch. 1

2

1 5/1/19

Systems Engineering

3 Pisacane, V., Fundamentals of Space System Design, Ch. 1

Product Development

Pisacane, V., Fundamentals of Space System Design, Ch. 1

4

2 5/1/19

NASA-2016-6105 5

6 NASA-2016-6105

3 5/1/19

Spacecraft Mission Objectives and Requirements

Fortescue 7

Requirements Definition

• What must the system accomplish? • Why must it be done? • How do we achieve the design goal? • What are the alternatives? • What sub-systems perform what functions? • Are all functions technically feasible? • How can the system be tested to show that it satisfies requirements?

Wertz and Larson 8

4 5/1/19

Program Management: Gantt Chart

• Project schedule • Task breakdown and dependency • Start, interim, and finish elements • Time elapsed, time to go

9

Program Evaluation and Review Technique (PERT) Chart

• Milestones • Path descriptors • Activities, precursors, and successors • Timing and coordination • Identification of critical path • Optimization and constraint

10

5 5/1/19

PERT Charts

11

Project Phases

12

6 5/1/19

Life Cycle Cost Impacts

13

Spacecraft Subsystems

14

7 5/1/19

Satellite Systems

• Power and •Structure • Propulsion –Skin, frames, ribs, – –Solar cells stringers, –Control bulkheads –Kick motor/ –Radio payload assist –Propellant tanks transmitters and module (PAM) –Heat/solar/ receivers –Attitude-control –Radar shields, insulation –-adjustment transponders –Articulation/ –Antennas –station-keeping deployment –Batteries, fuel mechanisms cells –-gradient –Pressure tanks tether –De-orbit systems –Re-entry system (e.g., sample return)

15

Functional Requirements of Spacecraft Subsystems

1. Payload must be pointed in the right direction 2. Payload must be operable 3. Data must be communicated to the ground 4. Desired orbit for the mission must be maintained 5. Payload must be held together and mounted on the spacecraft structure 6. Payload must operate reliably over some specified period 7. Adequate power must be provided

16

8 5/1/19

LADEE Typical Mass Breakdown

• Satellite without on-orbit/de-orbit propulsion • Kick motor/ PAM can add significant mass 17

Communications Satellite Mass Breakdown

18

9 5/1/19

Recommended Mass Growth Margins

Pisacane, V., Fundamentals of Space System Design, Ch. 1 19

Guidance, Navigation, and Control

20

10 5/1/19

Guidance, Navigation, and Control

• Navigation: Where are we? • Guidance: How do we get to our destination? • Control: What do we tell our vehicle to do?

21

First Program Contract MIT Instrumentation Laboratory August 9, 1961

22

11 5/1/19

Components of Apollo CSM Primary Navigation Guidance and Control System (“PNGCS”)

Mindell, D., Digital Apollo, Ch. 5 23

Landmark Tracking for Apollo Guidance

Mindell, D., Digital Apollo, Ch. 5 24

12 5/1/19

IMU Alignment and State Update

Mindell, D., Digital Apollo, Ch. 5

25

Apollo Guidance Computer

• Parallel processor • 16-bit word length (hexadecimal) • Memory – 36,864 words (fixed) – 2,048 words (variable) • 1st operational solid-state computer • Identical computers in CSM and LM – Different software (with many identical subroutines) http://klabs.org/history/build_agc/ 26

13 5/1/19

Apollo Guidance Computer Magnetic Core Memory Ropes

1 core = 1 bit 1 Kiloword Memory Bank

§ No built-in redundancy § No redundant computers § No failures § Mean time between failures = ∞

27

Apollo Lunar Module Radars • radar • Rendezvous radar – 3-beam Doppler – continuous-wave radar altimeter tracking radar – LM descent stage – LM ascent stage

28

14 5/1/19

Apollo Guidance Computer Commands • Display/Keyboard (DSKY) • Sentence – Subject and predicate – Subject is implied • , or • GNC system – Sentence describes action to be taken employing or involving an object • Predicate – Verb = Action – Noun = Variable or Program (i.e., the object)

29

Numerical Codes for Verbs and Nouns in Apollo Guidance Computer Programs

Verb Code Description Remarks 01 Display 1st component of Octal display of data on REGISTER 1 02 Display 2nd component of Octal display of data on REGISTER 1 03 Display 3rd component of Octal display of data on REGISTER 1

Noun Code Description Scale/Units 01 Specify machine address XXXXX 02 Specify machine address XXXXX 03 (Spare) 04 (Spare) 05 Angular error XXX.XX degrees 06 Pitch angle XXX.XX degrees Heads up-down +/- 00001 07 Change of program or major mode 11 Engine ON enable 30

15 5/1/19

Verbs and Nouns in Apollo Guidance Computer Programs

• Verbs (Actions) • Selected Nouns • Selected Programs – Display (Variables) (CM) – Enter – Checklist – AGC Idling – Monitor – Self-test ON/OFF – Gyro Compassing – Write – Star number – LET Abort – Terminate – Failure register – Landmark Tracking – Start code – – Change – Event time Determination – Align – Inertial velocity – Return to Earth – Lock – Altitude – SPS Minimum – Set – Latitude Impulse – CSM/IMU Align – Return – Miss distance – Test – Delta time of burn – Final Phase – First Abort Burn – Calculate – Velocity to be gained – Update 31

A Little AGC Digital Autopilot Code

32

16 5/1/19

Apollo GNC Software Testing and Verification

• Major areas of testing – Computational accuracy – Proper logical sequences • Testing program – Comprehensive test plans – Specific initial conditions and operating sequences – Performance of tests – Comparison with prior simulations, evaluation, and re-testing • Levels of testing – 1: Specifications coded in higher-order language for non-flight hardware (e.g., mainframe then, PCs now) – 2: Digital simulation of flight code – 3: Verification of complete programs or routines on laboratory flight hardware – 4: Verification of program compatibility in mission scenarios – 5: Repeat 3 and 4 with flight hardware to be used for actual mission – 6: Prediction of mission performance using non-flight computers and laboratory flight hardware 33

Lunar Module Navigation, Guidance, and Control Configuration

34

17 5/1/19

Lunar Descent Guidance

35

Lunar Module Transfer to Powered Descent Initiation

36

18 5/1/19

Lunar Module Powered Descent

37

Lunar Module Descent Events

38

19 5/1/19

Lunar Module Descent Targeting Sequence

• Braking Phase (P63) • Approach Phase (P64) 39 • Terminal Descent Phase (P66)

Characterize Braking Phase By Five Points

40

20 5/1/19

Lunar Module Descent Guidance Logic (Klumpp, Automatica, 1974)

• Reference (nominal) trajectory, rr(t), from target position back to starting point (Braking Phase example) – Calculated before mission – Three 4th-degree polynomials in time – 5 points needed to specify each polynomial ⎡ x(t)⎤ t 2 t 3 t 4 ⎢ ⎥ r (t) = r + v t + a + j + s r(t) = y(t) r t t t 2 t 6 t 24 ⎢ ⎥ ⎣⎢ z(t)⎦⎥

41

Coefficients of the Polynomials

t 2 t 3 t 4 r (t) = r + v t + a + j + s r t t t 2 t 6 t 24

• r = position vector • v = velocity vector ⎡ ⎤ • a = acceleration vector ⎡ x⎤ ⎡ x! ⎤ vx ⎢ ⎥ dr ⎢ ⎥ • j = jerk vector (time v ⎢ y ⎥ v r = y = = ⎢ ! ⎥ = ⎢ y ⎥ derivative of acceleration) ⎢ ⎥ dt ⎢ z⎥ ⎢ z! ⎥ ⎢ ⎥ ⎣ ⎦ ⎣ ⎦ vz • s = snap vector (time ⎣⎢ ⎦⎥ derivative of jerk)

⎡ ⎤ ⎡ ⎤ ⎡ ⎤ ax jx sx dv ⎢ ⎥ da ⎢ ⎥ dj ⎢ ⎥ a = = a j = = j s = = s dt ⎢ y ⎥ dt ⎢ y ⎥ dt ⎢ y ⎥ ⎢ a ⎥ ⎢ j ⎥ ⎢ s ⎥ ⎣⎢ z ⎦⎥ ⎣⎢ z ⎦⎥ ⎣⎢ z ⎦⎥ 42

21 5/1/19

Corresponding Reference Velocity and Acceleration Vectors t 2 t 3 v (t) = v + a t + j + s r t t t 2 t 6 t 2 a (t) = a + j t + s r t t t 2

• ar(t) is the reference control vector – Descent engine thrust / mass = total acceleration – Vector components controlled by orienting yaw and pitch angles of the Lunar Module 43

Guidance Logic Defines Desired Acceleration Vector • If initial conditions, dynamic model, and thrust control were perfect, ar(t) would produce rr(t)

t 2 a (t) = a + j t + s ⇒ r t t t 2 t 2 t 3 t 4 r (t) = r + v t + a + j + s r t t t 2 t 6 t 24

• ... but they are not • Therefore, feedback control is required to follow the reference trajectory

44

22 5/1/19

Guidance Law for the Lunar Module Descent

Linear feedback guidance law (real time

acommand (t) =

ar (t) + KV [v measured (t) − vr (t)]+ KR [rmeasured (t) − rr (t)]

KV :velocity error gain

KR :position error gain • Nominal acceleration profile is corrected for measured differences between actual and reference flight paths • Considerable modifications made in actual LM implementation (see Klumpps paper on Blackboard) 45

LM Manual Control Response During Simulated Landing

46

23 5/1/19

Simulated LM Manual Control Response To Rate Command

47

Next Time: The Future of Space Flight Telemetry, Communications & Tracking

48

24 5/1/19

Supplemental Material

49

Apollo GNC Software Specification Control

Operations Plan (GSOP) – NASA-approved specifications document for mission software – Changes must be approved by NASA Software Control Board • Change control procedures – Program Change Request (NASA) or Notice (MIT) – Anomaly reports – Program and operational notes • Software control meetings – Biweekly internal meetings – Joint development plan meetings – First Article Configuration Inspection – Customer Acceptance Readiness Review – Flight Software Readiness Review

50

25 5/1/19

Apollo GNC Software Documentation and Mission Support

• Documentation generation and review – GSOP: 1: Prelaunch 2: Data links 3: Digital autopilots 4: Operational modes 5: Guidance equations 6: Control data – Functional description document: H/W-S/W interfaces, flowcharts of procedures – Computer listing of flight code – Independently generated program flowchart – Users Guide to AGC – NASA program documents: Apollo Operations Handbook, Flight Plans and Mission Rules, various procedural documents • Mission support – Pre-flight briefings to the crew – Personnel in Mission Control and at MIT during mission

51

Ascent (Launch) Guidance

52

26 5/1/19

Gravity-Turn Flight Path

Hermann Oberth

• “Oberth’s Synergy Curve” • Gravity-turn flight path is function of 3 variables – Initial pitchover angle (from vertical launch) – Velocity at pitchover – Acceleration profile, T(t)/m(t) • Gravity-turn program closely approximated by tangent steering laws

53

Tangent Steering Laws Approximate

• Neglecting surface curvature

⎛ t ⎞ tanθ(t) = tanθo ⎜1− ⎟ ⎝ tBO ⎠

• Open-loop command, i.e., no feedback of vehicle state • Accounting for effect of Earth surface curvature on burnout flight path angle

⎡ t ⎛ t ⎞ ⎤ tanθ(t) = tanθo ⎢1− − tanβ ⎜ ⎟ ⎥ ⎣ tBO ⎝ tBO ⎠ ⎦ 54

27 5/1/19

Feedback Guidance Law Errors due to disturbances and modeling errors corrected by feedback control with damping

Thrust Angle(t) = cθ [θc (t) −θ(t)]− cqq(t) dθ q = = pitch rate dt

55

Phases of Ascent Guidance

• Vertical liftoff • Roll to launch azimuth • Pitch program to atmospheric exit – Jet stream penetration – Booster cutoff and staging • Explicit guidance to desired orbit – Booster separation – Acceleration limiting – Orbital insertion

56

28 5/1/19

Jet Stream Profiles

must able to fly through strong wind profiles • Design profiles assume 95th-99th-percentile worst winds and wind shear

57

Thrust Vector Control During Launch

– Attitude and rate feedback • Drift-minimum control – Attitude and accelerometer feedback – Increased loads • Load relief control – Rate and accelerometer feedback – Increased drift

58

29 5/1/19

Explicit Guidance Law ~Lunar Module Ascent, Launch (Brand, Brown, Higgins, and Pu, CSDL, 1972)

• Initial conditions – End of pitch program, outside • Final condition – Insertion in desired orbit • Initial inputs – Desired radius – Desired velocity magnitude – Desired flight path angle – Desired inclination angle – Desired longitude of the ascending/descending node • Continuing outputs – Unit vector describing desired thrust direction – Throttle setting 59

Guidance Program Initialization

• Thrust acceleration estimate • Mass/mass flow rate • Acceleration limit (~ 3g) • Effective exhaust velocity • Various coefficients • Unit vector normal to desired orbital plane, iq

⎡ sinid sinΩd ⎤ ⎢ ⎥ iq = sinid cosΩd i :desired inclination angle ⎢ ⎥ d

⎣⎢ cosid ⎦⎥ Ωd :desired longitude of descending node 60

30 5/1/19

Guidance Program Operation: Position and Velocity

• Thrust acceleration estimate, aT, from guidance system • Compute corresponding mass/flow rate and throttle setting, δT • Position ⎡ r⎤ ⎡ r ⎤ ⎢ ⎥ ⎢ 1 ⎥ y rsin− i i ⎢ ⎥ = ⎢ ( r • q )⎥ ⎣⎢ z⎦⎥ ⎣⎢ open ⎦⎥

• Velocity ⎡ r˙ ⎤ ⎡ vIMU •ir ⎤ ⎢ ⎥ ⎢ ⎥ y˙ = v •i ⎢ ⎥ ⎢ IMU q ⎥ v IMU :velocity estimate in IMU frame ⎣⎢ z˙ ⎦⎥ ⎣⎢ vIMU •iz ⎦⎥ 61

Guidance Program: Velocity and Time to Go • Effective gravitational acceleration 2 µ r × v g = − + eff r2 r3 • Time to go (to burnout) t = t − Δt gonew goold Δt :guidance interval • Velocity to be gained ⎡ ⎤ (r!d − r!) − geff tgo / 2 ⎢ ⎥ v go = ⎢ −y! ⎥ ⎢ ⎥ z!d − z! ⎣⎢ ⎦⎥ • Time to go prediction (prior to acceleration limiting)

m −vgo / ceff t 1 e ceff :effective exhaust velocity go = ( − ) m˙ 62

31 5/1/19

Guidance Program Commands • Guidance law produces required radial and cross-range accelerations a = a A + B t − t − g Tr T [ ( o )] eff a = a C + D t − t Ty T [ ( o )]

aT = net available acceleration, accounting for limit • Guidance coefficients, A, B , C, and D are functions of ˙ (rd ,r,r, tgo ) ˙ (y,y ,tgo) plus c ,m m! , acceleration limit eff 63

Guidance Program Commands

• Required thrust direction, iT (i.e., vehicle orientation in (ir, iq, iz) frame

⎡ a ⎤ Tr ⎢ ⎥ a a a ; i T T = ⎢ Ty ⎥ T = ⎢ ⎥ aT what's left over ⎣⎢ ⎦⎥ • Guidance philosophy • Force spacecraft into desired orbital plane • Climb toward desired 2-D orbit • Achieve orbital velocity 64

32