Auto-compatibility of inter-instrument interference campaign Operation Specifications

Information about the Auto-compatibility of inter-instrument interference campaign during the NECP.

General

Purpose & Objectives

An inter-instrument interference campaign is planned during the NECP to characterize the payload auto-compatibility.

Working Group Members

• Eric Lorfevre (RPW system, WG leader)
• Milan Maksimovic (RPW PI)
• Xavier Bonnin (ROC manager)
• Antonio Vecchio (RPW operations scientist)
• Diane Berard (RPW operations engineer)
• Jean-Michel Travert (RPW command/control)

Points of contact at ESA

• Sylvian Lodiot (MOC)

Deliverables

• Auto-compatibility of inter-instrument interference campaign Operation Specifications

Operation preparation

Overall timeline of the mission

Overall timeline of this campaign

The purpose of this campaign is to characterize the Solar Orbiter payload EMC in space.

RPW will run measurements covering the full frequency range for both magnetic and in electric sensors, in normal and burst mode. At the beginning of the campaign all the Solar Orbiter Instruments are OFF. Then they are successively set to ON. RPW will thus analyze the influence of each instrument on its measurements and on the background noise.

The switch on sequence is shown in table below:

Detailed timeline of the campaign 

Before A : Switch on RPW and put it in normal science mode

Between A and B : Run steps 1 to 13 (see previous table)

For each step, several configurations need to be tested : 

• LFR: 9 different configurations in SBM1 configuration
• TDS: 2 configurations in burst mode.
• THR: all modes for equal times and sweep of all HF frequencies

At B : Step 14: switch off all instruments except RPW

At C : Switch OFF RPW

Details of analyzers configurations

LFR and BIAS

LFR measurements are in SBM1 mode (SBM1 and Normal mode data simultaneously).

For each switch on sequence, 9 LFR+BIAS configurations (R0, R1 and R2 parameters, BW parameter, SP0 and SP1 parameters) are settled.

The duration of a campaign for a given LFR/BIAS configuration should be as long as possible. Indeed enough time is needed to record at least one snapshot of f3-waveform data (nominally 2 x 150 s.)

Multiplexer configurations for LFR-BIAS: 

• Conf 1: BIAS (V1_DC, V2_DC, V3_DC), SCM (SCM1, SCM2, SCM3), LFR (R0=R1=R2=1, SP0=SP1=0, BW=1)
• Conf 2: BIAS (V12_DC, V23_DC), SCM (SCM1, SCM2, SCM3), LFR (R0=R1=R2=1, SP0=SP1=0, BW=1)
• Conf 3: BIAS (V13_DC, V23_DC), SCM (SCM1, SCM2, SCM3), LFR (R0=R1=R2=1, SP0=SP1=0, BW=1)
• Conf 4: BIAS (V12_AC (gain 5), V23_AC (gain 5)), SCM (SCM1, SCM2, SCM3), LFR (R0=R1=R2=0, SP0=SP1=0, BW=1)
• Conf 5: BIAS (V13_AC (gain 5), V23_AC (gain 5)), SCM (SCM1, SCM2, SCM3), LFR (R0=R1=R2=0, SP0=SP1=0, BW=1)
• Conf 6: BIAS (V12_AC (gain 100), V23_AC (gain 100)), SCM (SCM1, SCM2, SCM3), LFR (R0=R1=R2=0, SP0=SP1=0, BW=1)
• Conf 7: BIAS (V13_AC (gain 100), V23_AC (gain 100)), SCM (SCM1, SCM2, SCM3), LFR (R0=R1=R2=0, SP0=SP1=0, BW=1)
• Conf 8: no BIAS, HF inputs, SCM (SCM1, SCM2, SCM3), LFR (R0=R1=R2=0, SP0=SP1=0, BW=0)
• Conf 9: no BIAS, HF inputs, SCM (SCM1, SCM2, SCM3), LFR (R0=R1=R2=0, SP0=SP1=1, BW=0)

We ask LFR and BIAS team to provide TC parameters (engineering value) for each of the 9 configurations during the inter-instrument interference campaign.

Open issues for LFR and BIAS team:

• K factor for LFR (distance between antennas and their orientations) à does LFR need a particular configuration to measure the K-factor or the values are already known?
• Test of saturation for BIAS when gain=100. Verify when the saturation is reached by progressively varying the gain.
  
  

LFR

BIAS

TDS

Two configurations for TDS:

• BURST mode single ended- at least 1 minute
  • Sampling rate 524 ksps.
  • High gain, single ended input configuration
  • Regular snapshot of 32k samples taken every 10 seconds.
  • MAMP (TDS maximum) product enabled at 128 sps.
  • Triggered snapshots and statistics enabled
  • Histograms disabled

At the end of the one-minute run, triggered snapshot queue dumped and 16 triggered snapshots saved.

• BURST mode dipole - at least 1 minute
  • Sampling rate 524 ksps.
  • High gain, basic dipole input configuration
  • Regular snapshot of 32k samples taken every 10 seconds.
  • MAMP (TDS maximum) product enabled at 128 sps.
  • Triggered snapshots and statistics enabled
  • Histograms disabled

At the end of the one-minute run, triggered snapshot queue dumped and 16 triggered snapshots saved.

We ask TDS team to provide the TC parameters (engineering value) for the 2 configurations during inter-instrument interference campaign.

TNR-HFR

TNR-HFR will run in all possible modes for equal times and making a sweep of all HF frequencies during each 80 minutes step. This includes the direction-finding modes, which allow testing the different antenna configurations.

ROC

• HK S/C to monitor T on ANT, SCM, MEB. How to retrieve them?
• Heaters SCM look at TM HK RPW
• Monitoring T ANT vs. heater switch on and retrieve data from ESA

OPEN ISSUES:

• For the inter instrument interference test, LFR is in SBM1 mode and TDS is in BURST mode. These modes cannot be run simultaneously. How can we deal with this? Are the LFR and TDS measurement done separately?
• Validate temperature on ANT, SCM and MED. Number of measurements to acquire? Do we need to monitor these temperatures during other phases of the mission?
• HGA vs. PA

• 300 V/m can be emitted by the HGA toward PAs
• Verify the period of the orbit when of HGA/PA conjunction
• Do we use the data measured during conjunction?

• Exact position of the moving parts for SPIS simulations (SPICE kernels). How to recover them?
• Monitoring of the activation periods of the PA and SCM heaters (HK_PDU_HEATER_CURRENT). Correlation with measured temperature to see if in these periods T really changes.
• Validation of the TDS detection algorithms and evaluation of the corresponding parameters.
• MAG synchronization. Make an internal calibration measurement for SCM and a measurement with MAG at the same time. This verifies that MAG is synchronized with SCM. MAG MUST BE turned on during the internal CAL of SCM.
• Galaxy Mode only for THR
• EMC. Excel table versus frequency: identification of known disturbances (E or B, fixed / variable / drifting, propagation through the system, etc.) → Checklist defined during ground tests, then update in flight

Orbitography

Give here the orbitography (i.e., time versus S/C orbit/attitude)

Operation Constraints

Give here the operation constraints at RPW and SOLO levels (e.g., TM rate, PW, SOOP, etc.)

Command/Control

Give here the list of flight procedures and IOR (PDOR?) required to execute this operation

Expected products

Data analysis

Expected data products

Give here the list of expected data products

Results

Give here the results of the data analysis (can be attached file, or link to references)