
Gaia
GAIA.ASU.SP.ESM.00007
Issue 2.00
Page 55 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.8.2 Real-Time Network Definition & Responsibility
This Section defines the general principles controlling the definition of the RTS to Avionics SCOE interfaces.
The detail and performance are to be agreed with the RTS supplier as part of the co-engineering activity
defined in Section 4.
Operation of the Real-Time Network requires definition of the following processes:
Mapping of RTS Model discrete I/O variables to the RTN Reflective Memory (for Avionics SCOE, Dynamic
FPA Simulator and Star Tracker SCOE)
Calibration of discrete data output from RTS Models to real values required at the Spacecraft Interfaces
Calibration of discrete data input to RTS Model from real values acquired at the Spacecraft Interfaces
As the RTS provides data to all other EGSE on the RTN, Reflective Memory mapping will be the
responsibility of the RTS supplier.
The RTS supplier will provide a Memory Map file (in a format to be determined by them) which will
determine Reflective Memory address locations, data size and data type for all discrete data passed across
the RTN.
The Memory Map file will refer to data by Symbolic Name and reference RFM locations by offset from the
RFM base address.
The RFM Memory Map file will be one input to an overall Real Time Network ICD to be developed between
The Avionics SCOE and RTS suppliers (see Section 4).
AVI-1454/CREATED/T
The Avionics SCOE shall utilize the memory Map file to determine its transfer of data between RFM
and the Spacecraft Interfaces.
AVI-1455/CREATED/R
Any data conversion and/or calibration requirements between RFM data types and those required for
Spacecraft I/O shall be the joint responsibility of the Avionics SCOE and RTS supplier, and be
determined as part of a co-engineering task between the Avionics SCOE and RTS suppliers (see
Section 4).
AVI-3025/CREATED/R
Any interface requirements between the Avionics SCOE and the RTS (such as asynchronous
operation for BUS transfers, high-level configuration requirements, calibration, for example) shall be
determined as part of a co-engineering task between the Avionics SCOE and RTS suppliers (see
Section 4).
The interface between the RTS and the Avionics SCOE is critical to the operation of the Avionics SCOE as
one component of a real-time closed-loop system. Section 4 defines the processes to be undertaken by the
Avionics SCOE subcontractor to ensure correct operation of this interface.
Comentarios a estos manuales