June 16, 2015SPP/FIELDS SOC CDR: Integration & Test SPP/FIELDS Integration and Test SOC Critical Design Review Keith Goetz University of Minnesota

June 16, 2015 1SPP/FIELDS SOC CDR: Integration & Test

SPP/FIELDSIntegration and Test

SOC Critical Design Review

Keith GoetzUniversity of Minnesota

[email protected]


FIELDS Block Diagram


I&T Plans

• Philosophy– Requirements are verified as early as possible at a low level

• Verifies subsystems, Retires risk– Requirements are verified at the highest level of assembly possible

• Often involves verifying a requirement at several levels– Maintain flexibility in test sequencing to maintain schedule

• Tests on ETU/EM ✔– Substantial environmental test program on EM hardware– FIELDS EM units have been assembled, integrated and tested– Includes TV

• Tests on Flight Units– Full environmental test program on Flight units

• Typical Test Levels:– Subassembly (circuit board): functional– Component (e.g. V1, MAG, SCM, MEP): functional, mass properties,

vibration, TV, deployments, magnetics– Instrument: functional, calibration, interface, EMC, TV


Planned ETU I&T Flow


Planned FM I&T Flow


Procedures

• Each test will be documented by a Test Procedure– Test procedure shall identify IRD requirements to be verified by the test– Test procedure shall include pass/fail criteria– System Engineer, QA, Subsystem lead to sign off on procedure before use– System Engineer, QA to sign off on completed as-run procedure– QA to ensure Red-lines to be transferred into procedure before next use

• Each completed test to be documented by a Test Report– ETU and subassembly test reports may be a combination of the as-run

procedure and lab notebook– System Engineer to sign off on test reports, and determine if test adequately

verifies associated requirements• Discrepancies found during tests to be documented in a Problem

Failure Report (PFR)– Starting with first functional tests at FM subassembly level– Includes any problem (including software) not immediately identified as a test

setup or operator problem which cannot stress the flight article– QA will track PFRs to closure with concurrence of the Failure Review Board

(includes APL)


Calibrations

• Co-I hardware institutions will deliver fully calibrated sub-assemblies

• Once FIELDS instrument is fully integrated– Several verification cals in ambient and at temperature– Timing– SWEAP

• Antennas – as mechanical elements – can be tested separately


Interfaces

• Interface tests verify interfaces meet requirements from ICD and/or specifications.

• FIELDS ETU well tested with APL S/C mini emulators• FIELDS FM to be tested with APL S/C full emulators• FIELDS TDS ETU/FM to be tested with SWEAP (at UCB)• At other times (prior to Observatory I&T) interfaces simulated with

GSE – Board, Component level tests performed with

• Board Interface Simulation GSE– Instrument-level tests performed with:

• APL-provided spacecraft emulators• Command and Telemetry GSE software• Stimulation GSE or internal test signal• SWEAP simulator (FIG)• Deployment actuator simulators

– GSE functionality, design described in GSE section


Mechanical Testing

• Antenna mechanisms can be tested independently of electronics• Full functional testing• Vibration• TV• Where appropriate, testing will include whips

• FIELDS Contamination Control Plan documents how FIELDS will meet Project contamination control requirements


Thermal Testing

• Tests per SPP Environmental Spec– 1 survival and 6 operational thermal vacuum cycles– Temperature ranges detailed in thermal presentation

• Per FIELDS V&V and T&C plan– V1-V4 PAs in one range– V5 PA in one range– MAG sensors (at GSFC)– SCM assembly (at LPC2E)– MEP is the simplest

• Includes all sensors– Antenna mechanisms

• Proposed Thermal Balance test using ETU FIELDS boom and ETU sensors – fall 2015


EMC Tests

• Tests per EMECP

• Electro-Static Discharge Test (EM only)• DC Magnetics (sniff test)• Surface Charging / Electrostatic Cleanliness• Ground Bonding and Isolation• Turn On/Off Transients• CE, CS, RE, RS Tests as detailed in EMECP

– ETU will only do CE measurements on the bench ✔


S/C-level I&T

• FIELDS and APL have had discussions w/r/t S/C level I&T

• FIELDS integration will involve a number of hardware elements (~20)

• FIELDS magnetic sensors will have protective enclosures• FIELDS will have external stimulus to support CPT functional testing

• Antennas will not be deployed at Spacecraft level– Too hard to implement off-loading GSE at spacecraft level– First motion without whips

• Actuator simulators will be provided to perform simulated boom deployments– Simulators contain flight-like resetable actuators (or equivalent loads)– Simulators attach to S/C deployment harnessing– Simulators can be used at spacecraft-level TV


FIELDS Flight Configuration


FIELDS Bench Testing Configuration


FIELDS CPT Configuration


FIELDS Flight Configuration

SOC


GSE Evolution

• SOC development will flow naturally from GSE• GSE and GSEOS are fully functional with FIELDS EM

– FIELDS1 and FIELDS2 EMs• GSE and GSEOS will continue with FM development

– At all hardware institutions• UCB, UMN, LASP, GSFC

– Used for all commanding• FIELDS1/FIELDS2

– Used for acquiring all telemetry• FIELDS1/FIELDS2

– Will move with us to APL for S/C level I&T• GSE and GSEOS will evolve into components of SOC

after launch– Used to build, test and send command loads– Used to operate EM test-beds at UCB and UMN


Commissioning - 1

• FIELDS has a number of critical steps in the commissioning period

• Deployment of the magnetometer boom (day ~3)– Turn on and check out FIELDS MEP– Turn on and check out FIELDS MAGs

• Command for high rate MAG data– Turn on and check out FIELDS SCM

• Command for SCM configuration– Gather background data - stowed– Deploy MAG Boom– Gather background data - deployed


Commissioning - 2

• Deployment of the V1234 Antennas (day ~30)– Turn on and check out FIELDS MEP

• Command for data acquisition– Deploy Antennas

• Deploy V1– Gather background data - stowed– Deploy V1– Gather background data – deployed

• Deploy V2– Gather background data - stowed– Deploy V2– Gather background data - deployed

• Deploy V3– Gather background data - stowed– Deploy V3– Gather background data - deployed

• Deploy V4– Gather background data - stowed– Deploy V4– Gather background data – deployed

– Survey deployed antenna beam patterns


Commissioning - 3

• Observe Probable Interference from TWTA (day ~30)– Start TWTA X-band contact– Turn on FIELDS MEP

• Command for data acquisition– Turn off TWTA– Send FIELDS science data to spacecraft SSR– Turn on TWTA by timed command– Playback recorded data

– Repeat


Commissioning - 4

• Observe Interactions with Other SPP Instrument (day ~40)– Start TWTA X-band contact– Turn on FIELDS MEP

• Command for data acquisition– Turn on SWEAP

• Test inter-instrument interface• Run in noisy mode

– Turn on EPI (2)• Run in noisy mode

– Turn on WISPR• Run in noisy mode

– Repeat in reverse order looking for interference


Commissioning - 5

• Observe Interactions with SPP Spacecraft (day TBD)– Start TWTA X-band contact– Turn on FIELDS MEP

• Command for data acquisition– Turn on other instruments as desired

– Run reaction wheel speed program– Run SA flap and feather– Run HGA motion survey

– Repeat - looking for interference


Commissioning - 6

• Observe SPP Spacecraft Attitudes (day TBD)– Start TWTA X-band contact– Turn on FIELDS MEP

• Command for data acquisition– Turn on other instruments as desired

– Run some rolls – fast– Run some slews

• Run a roll while slewed

– Repeat


Conclusion

• Instrument I&T plans are in good shape– Previous experience helps

• Spacecraft I&T plans are getting started– Previous experience helps here too

• FIELDS SOC is ready to move forward

June 16, 2015SPP/FIELDS SOC CDR: Integration & Test SPP/FIELDS Integration and Test SOC Critical Design Review Keith Goetz University of Minnesota

Documents