Goals

  • Discuss about the configurations chosen by each sub-system teams for each step of the commissioning. Those configurations have to be delivered to MOC before  

Date

Attendees



Agenda

The discussion is based on the attached presentation detailing the different issues.

  1. State of reception of documents detailing configuration for each step and each sub-system
  2. Discussion on each commissioning step and validation by each team
  3. Discussion of cruise phase configuration : low rate config
  4. Action-items, organization and planning

Global remark :

  • SBM1 is requested for each commissioning operation but is not mandatory. To be checked with MOC to be sure that SBM1 data can be downlinked on ground. If not, Normal mode will be used for each sub-system.

Discussion items

Item

Notes

Actions-items

  1. State of reception of documents detailing configuration for each step and each sub-system
Every team sent to ROC all the documents before the meeting. The config for reaction wheels filtering is missing
  • LFR team needs to provide the inputs for reaction wheels filtering test before   ROCOPE-223 - Getting issue details... STATUS

2. First RPW switch-on and in-flight SFT (RPW-1)

  • based on standard SFT as for ground 
  • tools : ROC tools as I/F with MOC
  • SFT configuration description can be found in C-SGSE script and run doc. only  


  • Action JMT : to provide any input for this operation. Especially send the last version of the SFT C-SGSE script and doc. ROCOPE-224 - Getting issue details... STATUS

2. I-Boom deployment (RPW-2)

  • LFR — 1 config over all the operation 
  • TDS — 1 config.  over all the operation (mag. data only)
  • THR — 2 config.  = 1 before/after (10 min.) + 1 during deployment.
  • BIAS — OFF

→ THR will lead the overall timeline of the deployment

- THR requests to have 3 PA HF ON? (EL: ADS nous a confirmé que l'impact thermique d'avoir le PA (d'une antenne gerbée) ON est négligeable)
- ANT PZ might be deployed before the I-boom in the current scenario 

  • Action EL —> check if there is no risk when ANT are stowed (PA heating) ROCOPE-222 - Getting issue details... STATUS

2. ANT deployment (RPW-3)

We asked for 3h duration : 3 rotations of 1h

  • LFR - 1 config. over all the operation 
  • TDS - 1 config. over all the operation (elec. data only)
  • BIAS ON - single-ended signal on each antenna. Biasing disabled
  • THR — 2 config.  = 1 before/after (10 min.) + 1 during deployment.

→ THR will lead the overall timeline of the deployment

THR requests to have 3 PA HF ON

  • Action XB : send an email to Sylvain Lodiot to ask if SBM event data can be downlinked during NECP ROCOPE-225 - Getting issue details... STATUS

2. ANT calibration rolls (RPW-4)

  • SBM_DETECTION submode for all
  • BIAS ON with biasing disabled 
  • All sub-systems with 1 config. overall the operation
  • May be run during first E-GAM (end of CP) instead of NECP

2. SCM calibration operation (RPW-5)

  • No specific request SBM_DETECTION or NORMAL mode ok for all the teams → SBM_DETECTION has been chosen
  • All sub-systems with 1 config. overall the operation
  • Might be run during first E-GAM (end of CP) instead of NECP

2. In-flight inter-instrument interference campaign (RPW-6)

  • RW filtering at this step ? - probably when EMC with platform
  • Instead of 80 min per inter-instrument step, only need for ~5 min

2. RPW PAS filtering tune campaign (RPW-7)
  • LFR 2 config. : ENABLE then DISABLE PAS-filtering
  • PAS ON 
Action EL : Organize a telecon with PAS team about RPW-7 ROCOPE-226 - Getting issue details... STATUS
3. Discussion of cruise phase configuration : low rate config

ROC will keep the two first configurations. if SBM1 data can be retrieve, config 2 will be chosen. Else config 1.

No time left to discuss galaxy and default configuration


4. Action-items, organization and planning
  • First draft of Commissioning procedures will be sent to MOC before  
  • A overview document will be written by ROC summarizing all the configurations (commissioning + CP) for each step and each subsystem. Approval by each lead CoI will be requested

Action DB+AV : prepare the configuration document ROCOPE-227 - Getting issue details... STATUS

Action Items

Key Summary T Created Updated Due Assignee Reporter P Status Resolution
Refresh

Attached items

  • No labels