Page History

Context

Preparation of the SVT1-A datapackage release for RPW.

• The SVT1-A campaign for RPW is expected to occur between Feb. to May 2019 (TBC)on May 2, 2019. It will be driven by MOC from ESOC site (Darmstadt, Germany).
• The RPW PFM model integrated on the S/C will be used for the test.
• No specific equipment is requested to the instrument teams (IT) to perform the test. MOC will use its own infrastructure.
• The ROC team will have to deliver the SVT1 datapackage, then support the MOC team in the preparation, execution and analysing of the test. Presence of ROC team at ESOC during test is TBD.
• All of the RPW TC will have to be tested during the SVT1 (see Summary of TC versus Sequences for the full list). Especially, the TC sequences for the commissioning and cruise phase will have to be delivered.
• Test plan and report will be written by the MOC. ROC will participate to the possible anomaly investigations related to RPW. A ROC internal test report for SVT1 will have to be written and stored in the ROC document management system (https://ged.obspm.fr/j_obspm/docbase/topic/browse_classic?topicID=T80) at the end.

Interlocutors are:

• Sylvain Lodiot at MOC

RPW SVT1 datapackage expected content overview

1. Upgraded RPW flight procedures from IGST42 datapackage
2. New RPW flight procedures related to the instrument commissioning and cruise phase operations.
3. Upgraded version of the RPW ISM
4. SVT1 timeline for RPW
5. First issue 1.0 of the RPW flight configuration description document (FCDD) (TBC)
   
   

Planning

• A first set of RPW flight procedures for SVT1 is planned to be delivered by email to Sylvain Lodiot (MOC) on mid-October 2018.
• The full SVT1 data package will have to be delivered before 14 déc. 2018.

Assumption, constraints and limits

Forbidden TCs

Jean-Michel Travert : 

Si toutes les Antennes sont correctement connectées au moment du test alors on peut jouer toutes les TC.
Si une Antenne n'est pas connecté, il y a 2 consignes :
	- Ne pas démarrer l'antenne qui n'est pas connectée donc ne pas utiliser TC_DPU_SWITCH_ON_EQUIPMENT (CP_DPU_SWITCH_ON_EQ: 	RPW_ANTi_EID, …)
	- Ne pas mettre une valeur différente de 0 en consigne du BIAS donc ne pas utiliser TC_DPU_SET_BIASi et TC_DPU_SET_BIAS_SWEEP avec 	l'argument CP_BIA_SET_SWEEP_ENAB_Pi = ENABLED
Avec i qui correspond à l'antenne qui n'est pas connectée.
C'est les mêmes contraintes que celles qui sont appliquées par ADS dans les essais qu'ils font.

Status of the data package

RPW sequences status

Routine sequences

Non-Routine sequences

Commissioning specific sequences

Cruise Phase specific sequences

SVT1 specific sequences

ISM status

Data package delivery status

Action-items related to the SVT1 datapackage

• Link to the ROC_SVT1_DATAPACK Kanban board in JIRA: https://jira-lesia.obspm.fr/secure/RapidBoard.jspa?rapidView=79