RBSP EFW ConOps

1. RBSP EFWConOps EFW Instrument Concept of Operations (ConOps) John Bonnell Space Sciences Laboratory University of California, Berkeley EFW INST+SOC PDR

2. EFW ConOpsOutline • EFW Concept of Operations (ConOps) • Progress since I-PDR and M-PDR. • Instrument Commissioning: • Turn-On and Check Out • Boom Deploys • Nominal Operations: • Conditions for Nominal Operations • State-of-Health Monitoring and Trending • Commanding and Day-to-Day Operations EFW INST+SOC PDR

3. EFW ConOpsProgress Since I-PDR and M-PDR • Provided measurements of SPB boom cable damping parameters in support of Project GNC boom dynamics modeling efforts (Q3-Q4 2008): • Boom settling to < 0.5-deg within 8-12 hours post-repointing. • Worked with Project GNC and L&EO Planning to flesh out AXB deploy and length trim plan. • Data collection in support of trim occurs in parallel with subsequent instrument commissioning activities. • Worked with Project L&EO Planning to detail EFW Commissioning timeline activites: • Instrument Turn-On • SPB Deploys • AXB Deploys and Length Trims EFW INST+SOC PDR

4. EFW ConOpsInstrument Commissioning • EFW Commissioning consists of two phases: • Initial instrument turn on and check out. • Radial and axial boom deploys. • May occur at RBSP MOC (using Test SOC; prefered) or at EFW SOC (using Flight SOC). • Turn-On and Checkout consists of stowed functional tests (duplicates of SC-level INT procs and data, which are in turn duplicates of Inst-level INT procs and data). EFW INST+SOC PDR

5. EFW ConOpsInstrument Commissioning: Radial Booms Deploy • Initial EFW boom deploy plan already developed: RBSP_EFW_TN_003C_EFW_BoomDeploySequence.doc. • Boom deploy power controlled by MOC (SC service). • Boom deploy commanding through EFW SOC (test or flight). • Spin rate changes during staged, pairwise boom deploy illustrated below. • Spin rate vs. boom stroke and time during deploy used to monitor state of deploy and abort, if required. • Baseline 15-day parallel deploy schedule between both observatories incorporated into current Mission Timeline. Fine wire unfurling EFW INST+SOC PDR

6. EFW ConOpsInstrument Commissioning: Axial Booms Deploy • Axial boom deploy occurs after radial boom deploy is complete, and observatory mass properties and dynamics confirmed (typically no significant delay required). • Axial booms deployed singly, in stages using motor deploy system to ≈5-m stroke (≈10-m tip-to-tip). • Final deploy lengths trimmed in few-cm increments using Survey axial E-field and SC potential estimates to reduce common-mode signal. • Trim phase occurs in parallel with other instrument commissioning activities. • See the following EFW Technical Note for further analysis and details: • RBSP_EFW_TN_023C_AXB_motor_drive_and_measurement_requirement.doc EFW INST+SOC PDR

7. EFW ConOpsValidity Conditions for Nominal Operations • Sensors Illuminated -- All EFW sensors illuminated (goal for aft axial sensor). • Attitude Known -- Post-processed Observatory attitude (spin axis pointing and spin phase) known to accuracy better than 3 deg. • Ephemerides Known -- Post-processed Observatory position and velocity known to accuracy better than (10 km, 30 m/s, 0.1 deg; 3-sigma). • Booms Settled -- EFW radial booms within 0.5 deg of nominal position. • DC B-Field Known – Post-Processed DC B-field known to accuracy better than 1%. • EFW-MAG-SCM Relative Orientation Known – Post-processed relative orientation of EFW, MAG, and SCM sensor axes known to better than 2 degrees. EFW INST+SOC PDR

8. EFW ConOpsInstrument Health and Status Monitoring • Instrument State-of-Health (SOH) monitored through near-real-time or playback engineering data via the SOC-CTG. • SOH compared against red/yellow limit database. • Off-Nominal conditions leads to: • Notification of EFW SOC personnel (page, e-mail). • Issuance of scripted commands, for certain, well-known off-nominal conditions (example: CRRES DDD-false commanding and resets). • Long-term trending and storage of SOH data: • New solution in GSEOS as part of CTG efforts or… • Incorporation into existing UCB MOC BTAPS database (decision: part of Phase III development, 2010 time frame). EFW INST+SOC PDR

9. EFW ConOpsNormal On-Orbit Operations (1) • Commanding • Complete instrument state (sensor biasing and data collection) set by ~50 commands. • Instrument configuration changes infrequently (~1/few weeks, after initial commissioning phase). • ~daily commanding to support ground selection of burst segments as needed. • ~monthly Sensor Diagnostic Tests (bias sweeps) to confirm and optimize instrument biasing. • Data Management • 12 kbps daily average: • ~ 5 kbps continuous Survey data (32 S/s E and V; auto- and cross-spectral data products). • ~ 7 kbps Burst1 and Burst2 data (0.5 and 16 kS/s E, V, and SCM data). EFW INST+SOC PDR

10. EFW ConOpsNormal On-Orbit Operations (2) • Burst Management (RBSP_EFW_SYS_016B_BurstTriggers) • Higher-rate waveform data (E, V, and SCM) collected continuously and banked into SDRAM and FLASH in seconds to minutes long segments (many days of B1 storage; many minutes of B2 storage). • Each segment tagged with “Burst Quality” computed on-board from DC or AC fields data cues (Filter Bank AC E or B, cues from other instruments). • B1 playback is through ground selection based on Survey data and other data sources (geophysical indices, etc.); on-board with Burst Quality allows for autonomous selection and playback, as needed (vacations, illness, ennui, etc.). • B2 survival and playback selection on-board is based on Burst Quality; playback selection includes option for forced collection (supports INT, and some possible campaign modes). • B1 and B2 support for time-tagged campaign modes available as well (e.g. BARREL support). • Inter-Instrument Burst Data • EFW message includes axial sensor status (illuminated/eclipsed), sensor sweep status (static/sweeping), and current burst-valuation algorithm ID and value. EFW INST+SOC PDR

11. EFW ConOpsCommand Generation • EFW-SOC shall generate commands by reference to UTC, as well as MOC data products (predicted ephemerides, etc.) and other data assets (e.g.. Geomagnetic indices). • EFW commands shall be validated as needed by running command load on EFW TestBed (ETU) and verifying appropriate change of state, data production, and instrument configuration. • Command validation shall occur prior to transmission of command load from EFW-SOC to RBSP-MOC. • Verification of current MET↔UTC SCLK Kernel shall occur prior to translation of EFW commands from UTC to MET. • Command receipt will be verified after transmission using standard MOC data products. EFW INST+SOC PDR

12. This page intentionally almost blank EFW INST+SOC PDR