Download - PMOD/WRC Davos 29-30 november 2010

DAVOS, 29-30 November 2010 group GETCU (JP Marcovici)

PICARD : Consortium meeting

1

PMOD/WRC Davos 29-30 november 2010

Présenté par : JP. MarcoviciSigle : LATMOS

GETCU(Groupe d’Expertise Technique de la

Charge Utile)



2

SUMMARY

GETCU in the PICARD ORGANIZATION

LIST OF TASKS CONTROL THE HEALTH STATUS OF THE PAYLOAD NEW PAYLOAD OPERATIONS SUPPORT FOR SPECIFIC PAYLOAD OPERATIONS

MEMBERS

ORGANIZATION

ACTUAL STATUS FOR EACH TASK



3

GETCU IN THE PICARD ORGANIZATION

GETCU

LATMOSIRMBPMOD



4

LIST OF TASKS OF THE GETCU

The tasks of the GETCU concerns the 4 instruments PGCU, SODISM, SOVAP and PREMOS

The main tasks of the GETCU are :- Analyze the data periodically in order to have a

payload health status report- Define a new payload configuration after data

analysis and in order to get a more optimize configuration

- Give technical support for testing new procedures (Mission Center or Command Control Center)

- Correct and update the flight operating software



5

PAYLOAD HEALTH STATUS REPORT (1/3)

The health status report contains - an excel file with the main status for operating modes- values of housekeeping for PGCU, SODISM, PREMOS, ALIM (text and grafics) - alarms produced at CMSP- List of science TM which are missing

The study consists in examining this report in order to- alert the expert if something seems not normal- anticipate an alert an decide for instance to change the configuration (example deviation between the SES and SODISM etc…)

The report is produced each week for GPOM and each month



6

Volet 1 Volet 2

Ecart type Ecart type Boost Temps de pose Nbre ouverture Moyenne

Absolu Relatif Moyenne

Absolu Relatif

mode boost1 6900ms 7280 14.434ms 0.432 0.00006 15.896ms 0.240 0.00003










Example of content : array about SODISM shutter




7

Example of graphics : PREMOS Heater Temperatures




8

NEW PAYLOAD CONFIGURATION

SODISMAdjust Thermal parameters for SODISMAdjust parameters of survey (Flight and ground)Adjust some TC parameters (duration of open shutter, etc…)

SOVAPCalibration sequence

PREMOSCalibration sequenceBackup of detectorThermal parametersHeater configuration



9

SUPPORT FOR SPECIFIC OPERATIONS (AT CMSP)

It is necessary to separate minor procedure changes (example to test a period of 10 minute for open/close PREMOS shutters)From major procedure changes (example to have a new scientific mode)

Major changes: must be approved by GEVP at least and it must be checked that there is no significant impact on the payload (thermal, electrical) What is written in the SIO 1. LATMOS provides a description of the requested operations in

simple terms2. CMS-P translates it into a detailed text procedure3. LATMOS validates the detailed procedure4. CMS-P generates the TC groups corresponding to the valid procedure5. LATMOS validates the TC groups on the LATMOS test bench

(PGCU-SODISM EM, SOVAP MQ, PREMOS EM) and gives a report6. If OK the new procedure is ready to be uploaded on satellite



10

MEMBERS OF GETCU

Fonction Nom % Affecté

Manager of the groupFlight software, programming new proceduresAnalyze housekeeping and preliminary reportCommand control payload expert

JP Marcovici 100% (included PICARD Sol)

Expert SODISM instrument Thermal payloadElectric consumption payload

M Meftah85% (is also project manager of PICARD Sol)

Quality PlanElectronic support for mechanisms SODISM

S Abbaki 50% (included PICARD sol)

Expert Flight softwareAnalyze housekeeping and preliminary report

AJ Vieau 20% (40%31/12/2010)

Expert SOVAP (IRMB) A Chevalier

Expert PREMOS (PMOD) D. Pfiffner

Support for analyze of data and test for new procedures at LATMOS

LATMOS engineer

>=20% from 1/1/2011



11

CNES Technical support for the flight software Alimentation and thermal of the payload Manager for PICARD MIGS OPS service

GEVP Support data treatment Optical support

OTHER External expertise (electronic PGCU, expertise SODISM, flight software…)

EXTERNAL SUPPORT



12

Interface LATMOS with SOVAP and PREMOSPermanent dialog by Email, and contact

Necessity to have monthly teleconferences (LATMOS, SOVAP and PREMOS) in the futureThe next one must be organized before end of January

In the commissioning period, LATMOS had three meetings but concerning only SODISM, and CNES dialogued directly with SOVAP and PREMOS

ORGANIZATION OF THE GROUP



13

STATUS FOR EACH TASK OF THE GETCU GROUP (1/2)

Health status report

We must add a SOVAP report status and a report about the quality of SODISM images

PASS

New payload configuration

Well defined in ICD document OK

Specific operationWish to adapt GETCU (LATMOS) contribution PASS

Correct and update the flight software

Quality and validation test well defined No correction to do

OK

Dynamic of the group

It is really necessary to haveMeeting with IRMB and PMOD

PASS



14

STATUS FOR EACH TASK OF THE GETCU GROUP (2/2)

About new procedure and the flight operating software

1) The flight software was specified in order to allow a lot of possibilities (SODISM test mode for instance)

2) SODISM SOVAP and PREMOS are driven independently (except synchronization possibilities)

Even with this two facilities, it seems not easy to play new modes or new procedures due to different constraints

Download - PMOD/WRC Davos 29-30 november 2010

Top Related