1 / 14

PMOD/WRC Davos 29-30 november 2010

GETCU ( G roupe d’ E xpertise T echnique de la C harge U tile). PMOD/WRC Davos 29-30 november 2010. Présenté par : JP. Marcovici Sigle : LATMOS. SUMMARY. GETCU in the PICARD ORGANIZATION LIST OF TASKS CONTROL THE HEALTH STATUS OF THE PAYLOAD NEW PAYLOAD OPERATIONS

sybil
Download Presentation

PMOD/WRC Davos 29-30 november 2010

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. GETCU(Groupe d’Expertise Technique de la Charge Utile) PMOD/WRC Davos 29-30 november 2010 Présenté par : JP. MarcoviciSigle : LATMOS

  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. PAYLOAD HEALTH STATUS REPORT (2/3) Example of content : array about SODISM shutter

  7. PAYLOAD HEALTH STATUS REPORT (3/3) Example of graphics : PREMOS Heater Temperatures

  8. NEW PAYLOAD CONFIGURATION SODISMAdjust Thermal parameters for SODISM Adjust parameters of survey (Flight and ground) Adjust some TC parameters (duration of open shutter, etc…) SOVAP Calibration sequence PREMOS Calibration sequence Backup of detector Thermal parameters Heater 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 • LATMOS provides a description of the requested operations in simple terms • CMS-P translates it into a detailed text procedure • LATMOS validates the detailed procedure • CMS-P generates the TC groups corresponding to the valid procedure • LATMOS validates the TC groups on the LATMOS test bench (PGCU-SODISM EM, SOVAP MQ, PREMOS EM) and gives a report • If OK the new procedure is ready to be uploaded on satellite

  10. MEMBERS OF GETCU

  11. EXTERNAL SUPPORT 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…)

  12. ORGANIZATION OF THE GROUP Interface LATMOS with SOVAP and PREMOS Permanent dialog by Email, and contact Necessity to have monthly teleconferences (LATMOS, SOVAP and PREMOS) in the future The 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

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

  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

More Related