1. “DDSinterface” a software interface between Consert EGSE and Rosetta Data Delivery System (DDS)

2. DDSinterface : overview software developed for ground operations aims to extract data from the Rosetta Mission Control System (MCS) interacts with the DDS (Data Delivery System) (documentation=DDID) main features behaves in a “realtime” manner extracts and download telemetry data (APID) on the Consert EGSE handles several APID in parallel merges retrieved data within a single file takes into account temporary unavailability of data DDSinterface = Java application executed on the EGSE

3. Consert EGSE Rosetta MCS (ESOC) DDSDDS DDSinterface data analysis software (CDH ) IP network datafile Spacecraft DDS : an overview

4. requests DDS Request file (XML) Data DDS FTP server Main PI EGSE (PC) FTP transfer PI FTP server FTP transfer Data file (SFDU or raw data) Monitoring Processing Archiving … DDS : how to make requests

5. DDS : sample request (1/2)

7. TM File PI EGSE (PC) DDS 1 software thread / apid disk storage Data file Request file (XML) wait concatenate data generate request “near” realtime Request # n from Tn-1 to Tn Request # n+1 from Tn to Tnow DDSinterface : the request loop

8. PI EGSE (PC) DDS 1 software thread per APID disk storage Data file Request file (XML) wait concatenate data generate request “near” realtime Request # n from Tn-1 to Tn Request # n+1 from Tn-1 to Tnow DDSinterface : the request loop (failure) timeout Failure types : - DDS down (timeout) - Corrupted data file - Empty file

9. DDSinterface : user parameters APID number “back time” for first request realtime offset TM File Data file Request file (XML) wait concatenate data generate request “near” realtime Request # n from Tn-1 to Tn Request # n+1 from Tn to Tnow - offset

11. DDSinterface : future evolutions or improvements should use the XML acknowledgment returned by the DDS take care of evolutions (?) in the DDS system : behavior change may involve modifications in DDSinterface take care of evolutions in software technology (especially Java) and future compatibility issues take care to maintain a FTP service at the PI’s home institute, with correct configuration. Similar FTP service may become mandatory on the EGSE. no clear choice (yet) between SFDU data or raw data “standalone executable” to be built (JAR file)