Goals

  • Identify needs, open issues and action-items for the next RPW Flight Software upgrades
  • Build a preliminary schedule

Date

at 10PM (via ZOOM)

Attendees



Agenda

  1. Requirements and scope
  2. Validation process
  3. Schedule
  4. AOB

Discussion items

ItemNotesAction-Items
1.
  • Requirements and scope (introduction)
    • See slide 3 in RPW_FSW_Upgrade_Support_20201130_V01.pdf attached below
  • MOC needs and recommendation
    • See slide 4 in RPW_FSW_Upgrade_Support_20201130_V01.pdf attached below
  • DAS FSW needs and resources
    • No need to update DAS
    • LESIA DAS team will retrieve the FSW patch images from analyser teams, perform usual verifications (image size, consistency w.r.t. to budget, memory resource on EEPROMs) and provide to the ROC the FSW patch commands as TcScript files.
    • It is important the analyzer teams check memory footprint (shall remain in the budget)
  • TDS FSW needs and resources
    • See td_software_plans.pdf attached below
    • 2-3 months of work
    • No need specific funding or external human resource
    • Leads by Jan and Ludek
    • No need to update TM/TC
  • LFR FSW needs and resources
    • See LFR FSW upgrade_30 november 2020.pdf attached below
    • At least 6 montshs of work
    • No need specific funding or external human resource, except maybe for quality support. CNES may supply software quality support (Charles Dixon will be in charge of the software quality assurance from CNES in 2021)
    • Leads by Thomas and Bruno (with Alexis and Veronique in the loop)
    • No need to update TM/TC, but might require to change descriptions in the ICD (not a problem for Philippe → will no impact IDB structure)
    • May need to inject stimuli during validation tests on GSE at LESIA
  • THR FSW needs and resources
    • See THR_FS_Upgrade_30112020.pdf attached below
    • At least 3 months of work
    • Need funding for THR FSW upgrade cause K.Boughedada left the team (and quality support? → Check if possible with W.Recard from NEXEYA). Funding from LESIA RPW?
    • Leads by Milan, Pierre-Luc, Antonio and Moustapha
  • ROC needs and resources
    • No need extra funding or resources
    • Leads by Xavier and Diane
    • Will coordinate the activity (main contact with the MOC/SOC)
    • Will perform validation tests on GSE at LESIA and prepare the PDOR/MDOR for the MOC (Patching + SFT)
    • Prepare FSW patch plan and report
  • Desi - Check if CNES can supply support for FSW quality
  • Xavier - Check with Philippe about quality support at LESIA for THR FSW upgrade
  • THR Team - To supply to the Xavier the detailed needs (human and funding) for the FSW upgrading
2.
  • See slide 5 in RPW_FSW_Upgrade_Support_20201130_V01.pdf attached below
  • Validation test will be performed by the ROC with the support of the teams on the GSE at LESIA
  • LFR team - To confirm the need of stimuli for validation tests on the GSE and provide, if needed, the stimuli files
  • ROC (Xavier and Diane) - Check if stimuli can be injected in the EM2 with the GSE at LESIA
  • ROC (Xavier and Diane) - Check with Sylvian Lodiot and/or Julian Braun about verification/validation steps at MOC level (only MDOR/PDOR consistencies?)
3.
  • FSW patching should be done before the end of the Cruise phase (Nov. 2021), inside a period of low science interest and outside of any special operations activities (see https://issues.cosmos.esa.int/solarorbiterwiki/display/SOSP/LTP04+July+2021-Dec+2021 for science planning)
  • Two scenarios are envisaged:
    • A optimistic scenario (A), assuming a on-board FSW patching on June 30, 2021
    • A pessimistic scenario (B), assuming a on-board FSW patching on October 31, 2021
  • TDS team should be OK with both scenarios
  • LFR team says that the optimistic scenario (A) is too short to be ready
  • THR team says it might be OK for the two scenarios but only for three first priority FSW patches (see Milan's slides)
  • The GO/NOGO of each team w.r.t. to the scenarios A or B will have to be known by end of January 2021. The final content of the FSW datapack for each team will have to be also defined at this date (including documentation)
  • As soon as they are available FSW patches can be tested by Diane on the GSE at LESIA
  • The three analyzer FSW patches on-board may be performed separately
  • The patch operations is performed in two parts:
    • Uploading the RPW patch images in the spacecraft memory
    • Patching RPW analyzer EEPROMs
  • A SFT test must be performed after the patching on-board
  • Better to switch off all the equipments during the patching
  • Should take few hours to upload (to be refined during ground test)
  • Both old and new FSW versions can be stored on-board for safety (if a problem occurs with new software, the old one can be used in backup)
  • Main expected achievements and milestones for the two scenarios are summarized in slides 7 and 8 of RPW_FSW_Upgrade_Support_20201130_V01.pdf
  • ROC - To inform the MOC/SOC about preliminary schedules and the possibility to perform the patches around the planned dates
4.
  • A second meeting will be planned at the end of January 2021 to discuss about the FSW readiness

Action items

Attached items