Specifications

Gaia
GAIA.ASU.SP.ESM.00007
Issue 2.00
Page 51 of 79
Astrium Ltd owns the copyright of this document which is supplied in confidence and which shall not be used for any purpose other than that for which it is supplied and shall not in
whole or in part be reproduced, copied, or communicated to any person without written permission from the owner.
GAIA.ASU.SP.ESM.00007 (Avionics SCOE Req Iss 2).doc
3.7 CCS Interface Requirements
AVI-1575/CREATED/T
The Avionics SCOE interface to the CCS shall be via the Network Interface (LAN) Card using TCP-IP
protocols.
AVI-3365/GSE-SYS-770/T
Three distinct interface types shall be provided for Avionics SCOE to CCS data transfers, as defined
in the following sections:
• Standard SCOE HK TM / Command & Control interface
• SCET/H
REF
data pair transfer
• Transport Sample Protocol (TSP) interface for data logging to CCS Processing and
Central Archive.
3.7.1 HK TM / Command & Control Interface
AVI-1576/CREATED/T
Standard HK TM messages sent to the CCS shall utilize the EGSE Internal Housekeeping TM Source
Packet structure defined in Section 3.4.3 of the EGSE ICD [AD01].
AVI-2805/CREATED/T
Command & Control messages sent by the CCS shall utilize the EGSE Command and Control
Source Packet structure defined in Section 3.4.4 of the EGSE ICD [AD01].
AVI-2804/CREATED/T
HK TM and Command & Control messages from/to the CCS shall contain the Application ID as given
in Appendix 2 of the EGSE ICD [AD01] for the Avionics SCOE.
AVI-2803/CREATED/T
Where applicable, message protocols shall conform to (but not be restricted to) the Keyword List
identified in Section 3.4.4.2 of the EGSE ICD [AD01].
AVI-1577/CREATED/T
All data received from the CCS shall be acknowledged by ACK/NAK reply in accordance with Section
3.4.4 of the EGSE ICD [AD01].