egse interface requirements specification -...

REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 1/119

EGSE INTERFACE RequirementsSpecification

H-P-1-ASPI-IS-0121

Product Code: 00000

Date Signature

Rédigé par/Writtenby

EGSE Engineer

Bernard DUBOIS

Vérifié par/Verifiedby

RAIT

J.Y. CHARNIER


AIV Manager

D. MONTET


PA Manager

C. MASSE

Approbation/Approved

Project Manager

J.J. JUILLET

Entité Emettrice: Alcatel Space - Cannes(détentrice de l’original) :

HHHEEERRRSSSCCCHHHEEELLL /// PPPLLLAAANNNCCCKKK


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 2/119

ENREGISTREMENT DES EVOLUTIONS / CHANGE RECORDS

ISSUE DATE § : DESCRIPTION DES EVOLUTIONS§ : CHANGE RECORD

REDACTEURAUTHOR

01 07/Nov/01 First issue.02 04/June/02 H-P-ASPI-CR-0123

H-P-ASPI-CR-0124B.DUBOIS

03 18/June/02 Updated version according to Minute Of Meetingn° H-P-MI-AI-0107 (11/13/June/02)n° H-P-MI-AI-0108 (13/June/02)

B.DUBOIS

§2.2 Reference document : add of “SCOS-2000 OBSMExternal InterfacesControl Document” for OBSM files format§3.1 : figure 1 and figure 2 updated[IFRQT-0040] : Add of RM link between Planck IEGSE andCCS[IFRQT-0040] : Single TCP/IP socket specified for eachconnection[IFRQT-0042] - New requirement : PIPE message priority[IFRQT-0060] : Requirement deleted[IFRQT-0080] : checking of connection by Alive RM packetevery 60 seconds[IFRQT-0103] : error raised if message transmission notcompleted within 5 seconds§4.1.3 : Byte order is big endian§4.1.4 and 4.1.6 : correction of the length of Body Message§4.1.5 PIPE Header modification :

- Deleted : data quality and sequence quality fields- Added : Request ID field and Synchro Word field- New length of PIPE Header = 10 bytes

§4.1.6.1 : Updated : Structure table Spare field§4.1.6.2 [IFRQT-0160] correction :

- Data field header = 32 bits- Ack field = ‘0001’- Spare length = 8 bits- Packet type and subtype definition : TM replace by TC

§4.1.7 : New paragraph : ‘Message ID List’§4.3.1.5 : Added RC for MAP ID selection4.3.1.3 : Correction : measuring period of nn sec[IFRQT-0520] “TM distribution is based on a table definedinside HPSDB[IFRQT-0540] : only one message ID = 0x10[IFRQT-0590] :Deleted table of Data Quality and ServiceQuality definition[IFRQT-0803] : deleted : Source data[IFRQT-0804] :MSG ID = 0x51[IFRQT-0805] :MSG ID = 0x10


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 3/119

[IFRQT-0806] :MSG ID = 0x10[IFRQT-0807] :MSG ID = 0x10[IFRQT-0808] :MSG ID = 0x10[IFRQT-0808-2] : deleted : Source data[IFRQT-0808-3] :MSG ID = 0x56[IFRQT-0886] :150 Kbps per Instrument Station is confirmed[IFRQT-0830] : NTP confirmed[IFRQT-0809-2] : Alive RM packet definition§4.12.11 Replaced [S4] by [RD13]


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 4/119

TABLE OF CONTENTS

1 SCOPE........................................................................................................................................................... 8

2 DOCUMENTS .............................................................................................................................................. 9

2.1 STANDARD DOCUMENTS............................................................................................................................. 92.2 REFERENCE DOCUMENTS............................................................................................................................ 92.3 APPLICABLE DOCUMENTS......................................................................................................................... 102.4 ACRONYMS ............................................................................................................................................... 11

3 GENERAL DESCRIPTION...................................................................................................................... 12

3.1 FUNCTIONAL DESCRIPTION ............................................................................................................. 123.2 SPECIFIC TERMS AND DEFINITION ................................................................................................. 20

4 EGSE INTERNAL INTERFACE REQUIREMENTS............................................................................ 21

4.1 PROTOCOL DEFINITION ..................................................................................................................... 214.1.1 General ............................................................................................................................................ 214.1.2 Communication Link........................................................................................................................ 244.1.3 Byte order ........................................................................................................................................ 254.1.4 Message Structure ........................................................................................................................... 254.1.5 PIPE Message HEADER ................................................................................................................. 264.1.6 Body message .................................................................................................................................. 27

4.1.6.1 Monitoring Flow message (SCOE’s/DFE/IS CCS)............................................................................274.1.6.2 Control Flow message (CCS SCOE’s/DFE/IS) .................................................................................29

4.1.7 Message ID List ............................................................................................................................... 324.2 CONTROL FLOW – TELECOMMAND PACKETS ................................................................................ 334.3 CONTROL FLOW – CCS REMOTE COMMANDING PACKETS............................................................... 34

4.3.1 COMMUNICATION VIA SCOE/DFE LAN..................................................................................... 364.3.1.1 CCS Commands......................................................................................................................................364.3.1.2 CCS → CDMU SCOE Commands.........................................................................................................364.3.1.3 CCS → ACMS SCOE Commands .........................................................................................................384.3.1.4 CCS → TT&C SCOE Commands ..........................................................................................................394.3.1.5 CCS → TM/TC DFE Commands ...........................................................................................................414.3.1.6 CCS → Umbilical I/F Module Commands .............................................................................................434.3.1.7 CCS → BATSIM SCOE Commands......................................................................................................454.3.1.8 CCS → SAS SCOE Commands .............................................................................................................464.3.1.9 CCS → BCE SCOE Commands .............................................................................................................474.3.1.10 CCS → LAUNCH POWER SUPPLY Commands.................................................................................484.3.1.11 CCS → SIS SCOE Commands ...............................................................................................................494.3.1.12 CCS → PLM SCOE Commands.............................................................................................................504.3.1.13 CCS → Herschel Cryo SCOE Commands..............................................................................................514.3.1.14 CCS → Planck PLM SCOE Commands.................................................................................................524.3.1.15 CCS → Planck Sorption SCOE Commands ...........................................................................................524.3.1.16 CCS → CDMU DFE Commands ...........................................................................................................524.3.1.17 CCS → 1553 Bus Probe Commands.......................................................................................................544.3.1.18 CCS → Quick Load Commands .............................................................................................................54

4.3.2 COMMUNICATION VIA Instrument Station LAN.......................................................................... 554.3.2.1 CCS → Instrument Stimuli SCOE Commands .......................................................................................554.3.2.2 CCS → HFI EGSE Commands...............................................................................................................554.3.2.3 CCS → LFI EGSE Commands ...............................................................................................................554.3.2.4 CCS → HCSS SCOE Commands...........................................................................................................554.3.2.5 CCS → HIFI EGSE Commands .............................................................................................................564.3.2.6 CCS → PACS EGSE Commands ...........................................................................................................564.3.2.7 CCS → SPIRE EGSE Commands ..........................................................................................................56

4.3.3 COMMUNICATION VIA www LAN................................................................................................ 564.3.3.1 CCS → www.Server Commands............................................................................................................56

4.4 MONITORING FLOW - ON-BOARD TELEMETRY PACKETS ACQUISITION.............................................. 57


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 5/119

4.5 MONITORING FLOW - TELEMETRY PACKETS DISTRIBUTION .............................................................. 584.6 MONITORING FLOW – REMOTE MESSAGE PACKETS........................................................................... 59

4.6.1 PERIODIC RM Message ................................................................................................................. 604.6.2 ASYNCHRONOUS RM Message (Event Report)............................................................................. 614.6.3 COMMUNICATION VIA SCOE/DFE LAN..................................................................................... 62

4.6.3.1 RM CDMU SCOE Definition.................................................................................................................624.6.3.2 RM ACMS SCOE Definition .................................................................................................................63

4.6.3.2.1 Quick Load.........................................................................................................................................644.6.3.2.2 Optical Stimuli ...................................................................................................................................644.6.3.2.3 Stimuli Feedback................................................................................................................................64

4.6.3.3 RM TT&C SCOE Definition ..................................................................................................................654.6.3.4 RM TM/TC DFE Definition ...................................................................................................................674.6.3.5 RM Umbilical I/F Module Definition .....................................................................................................704.6.3.6 RM BATSIM SCOE Definition..............................................................................................................724.6.3.7 RM SAS SCOE Definition .....................................................................................................................734.6.3.8 RM BCE SCOE Definition.....................................................................................................................744.6.3.9 RM LAUNCH POWER SUPPLY Definition.........................................................................................754.6.3.10 RM SIS SCOE Definition.......................................................................................................................764.6.3.11 RM PLM SCOE Definition ....................................................................................................................774.6.3.12 RM Herschel Cryo SCOE Definition......................................................................................................784.6.3.13 RM Planck PLM SCOE Definition.........................................................................................................804.6.3.14 RM Planck Sorption SCOE Definition ...................................................................................................804.6.3.15 RM CDMU DFE Definition ...................................................................................................................804.6.3.16 RM 1553 Bus Probe Definition ..............................................................................................................824.6.3.17 RM Quick Load I/F Definition ...............................................................................................................82

4.6.4 COMMUNICATION VIA IS LAN .................................................................................................... 824.6.4.1 RM Instrument Stimuli SCOE Definition...............................................................................................824.6.4.2 RM HFI EGSE Definition ......................................................................................................................824.6.4.3 RM LFI EGSE Definition.......................................................................................................................824.6.4.4 RM HCSS SCOE Definition...................................................................................................................824.6.4.5 RM HIFI EGSE Definition .....................................................................................................................824.6.4.6 RM PACS EGSE Definition ...................................................................................................................834.6.4.7 RM SPIRE EGSE Definition ..................................................................................................................83

4.6.5 COMMUNICATION VIA www LAN................................................................................................ 834.6.5.1 RM www.Server Definition....................................................................................................................83

4.7 MONITORING FLOW – ACKNOWLEDGE MESSAGE PACKETS (ACKRC).............................................. 844.7.1 Remote Command Acceptance report – Success (1,1)..................................................................... 854.7.2 Remote Command Acceptance report – Failure (1,2) ..................................................................... 864.7.3 Remote Command Execution Report - Started (1, 3)....................................................................... 884.7.4 Remote Command Execution report – Progress (1,5) ..................................................................... 894.7.5 Remote Command Execution Report - Completed (1, 7) ................................................................. 904.7.6 Remote Command Execution report – Failure (1,8)........................................................................ 91

4.8 MONITORING FLOW – ACKNOWLEDGE MESSAGE FOR TC (ACKTC) ................................................ 934.8.1 Telecommand Acceptance report – Success (1,1)............................................................................ 944.8.2 Telecommand Acceptance report – Failure (1,2) ............................................................................ 95

4.9 MONITORING FLOW – TC ECHO......................................................................................................... 974.10 MONITORING FLOW – TC REPORT................................................................................................. 984.11 MONITORING FLOW – RM ALIVE PACKET..................................................................................... 994.12 INTERFACES REQUIREMENTS...................................................................................................... 99

4.12.1 GENERIC INTERFACE NAME ................................................................................................ 1004.12.2 DATABASE ............................................................................................................................... 1014.12.3 DATE/TIME .............................................................................................................................. 1014.12.4 Quick loading function .............................................................................................................. 1014.12.5 Interface TM/TC DFE↔ NDIU ............................................................................................... 1014.12.6 Interface Instrument Stimuli SCOE ↔ Herschel Satellite ........................................................ 1024.12.7 Interface Instrument Stimuli SCOE ↔ Planck Satellite............................................................ 1024.12.8 Performance.............................................................................................................................. 1024.12.9 File transfer............................................................................................................................... 1024.12.10 Naming Convention Rules for EGSE items ............................................................................... 103


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 6/119

4.12.11 OBSM Files ............................................................................................................................... 103

5 EGSE EXTERNAL INTERFACE REQUIREMENTS TBW ......................................................... 104

5.1 EGSE TO S/C INTERFACES................................................................................................................. 1075.1.1 CDMU SCOE ................................................................................................................................ 107

5.1.1.1 Quick SW Loading I/F..........................................................................................................................1075.1.1.2 MIL-STD-1553B I/F.............................................................................................................................1075.1.1.3 Time pulse ............................................................................................................................................107

5.1.2 ACMS SCOE.................................................................................................................................. 1075.1.2.1 Optical Stimuli Commands...................................................................................................................1075.1.2.2 Stimuli Feedback Commands ...............................................................................................................107

5.1.3 TT&C SCOE RF ............................................................................................................................ 1085.1.4 POWER SCOE............................................................................................................................... 108

5.1.4.1 Power System I/F..................................................................................................................................1085.1.4.2 PCDU I/F..............................................................................................................................................1085.1.4.3 Telecommand I/F..................................................................................................................................1085.1.4.4 Telemetry I/F ........................................................................................................................................109

5.1.5 BATSIM SCOE .............................................................................................................................. 1095.1.6 SAS SCOE...................................................................................................................................... 1095.1.7 BCE SCOE..................................................................................................................................... 1105.1.8 COTE (Launch configuration)....................................................................................................... 111

5.1.8.1 Power System I/F..................................................................................................................................1115.1.8.2 PCDU I/F..............................................................................................................................................1115.1.8.3 Telecommand I/F..................................................................................................................................1115.1.8.4 Telemetry I/F ........................................................................................................................................111

5.1.9 HERSCHEL Stimuli Instrument SCOE.......................................................................................... 1125.1.10 PLM SCOE................................................................................................................................ 1125.1.11 Herschel Cryo SCOE ................................................................................................................ 1125.1.12 CDMU DFE .............................................................................................................................. 112

5.1.12.1 Internal Commands I/F .........................................................................................................................1125.1.12.2 Internal Telemetry I/F ...........................................................................................................................112

5.1.13 1553 Bus Probe ......................................................................................................................... 1125.2 EGSE TO EGSE INTERFACES............................................................................................................. 113

5.2.1 TM/TC Interface ............................................................................................................................ 1135.2.2 Launch Power Supply Interface..................................................................................................... 1135.2.3 SAFETY LOOP.............................................................................................................................. 114

6 VERIFICATION MATRIX..................................................................................................................... 115

6.1 GENERAL REQUIREMENTS.............................................................................................................. 115


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 7/119

LISTE OF FIGURES

FIGURE 1 : OVERVIEW OF THE PLANCK EGSE ARCHITECTURE........................................................................... 13FIGURE 2 : OVERVIEW OF THE HERSCHEL EGSE ARCHITECTURE ...................................................................... 14FIGURE 3 : EGSE PLANCK PLM CONFIGURATION ............................................................................................. 15FIGURE 4 : EGSE HERSCHEL PLM CONFIGURATION......................................................................................... 16FIGURE 5 : EGSE PLANCK S/C CONFIGURATION................................................................................................ 17FIGURE 6 : EGSE HERSCHEL S/C CONFIGURATION ........................................................................................... 17FIGURE 7 : HERSCHEL EGSE LAUNCH CONFIGURATION ................................................................................... 18FIGURE 8 : PLANCK EGSE LAUNCH CONFIGURATION ........................................................................................ 18FIGURE 9 : SAFETY LOOP OVERVIEW............................................................................................................... 114

LISTE OF TABLES

TABLE 1 : PIPE MESSAGE LAY-OUT ....................................................................................................................... 25TABLE 2 : PIPE MESSAGE HEADER ........................................................................................................................ 26TABLE 3 : GENERIC INTERFACE NAME................................................................................................................. 100TABLE 4 : H/P EGSE INTERFACES....................................................................................................................... 106


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 8/119

1 SCOPE

The purpose of this document is to establish, in a single document, and in an unambiguousway, the interface definitions that are used by the different EGSE constituents (Platform andInstrument), to communicate between each other.

This document is composed of two main parts :

- § 4 - EGSE INTERNAL INTERFACE REQUIREMENTS describes thecommunication protocol used between CCS and all EGSE’s item in order to emitcommands and receive data.RC and RM mean Remote Commanding/Remote Monitoring of SCOE’s and FrontEnds by the CCS, different from Satellite TC and TM.RC and RM paragraphs are split according to the LAN used to transmit data(SCOE/DFE LAN or IS LAN).

- § 5 - EGSE EXTERNAL INTERFACE REQUIREMENTS describes all electricalcharacteristics :

• between each EGSE and the UUT (SVM, PLM, Spacecraft)• between EGSE item (ex : TT&C SCOE TM/TC DFE)

Nota : All TBD’s to be defined during phase B.


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 9/119

2 DOCUMENTS

2.1 Standard Documents

Ref. Reference of document Title

S1 H-P-1-ASPI-SP-0110 Ground Support Equipment Applicability Matrix of ECSS-E-40B

S2 ESA-PSS-04-105 TM Packet Standard

S3 ESA-PSS-04-106 TC Packet Standard

S4 SCI-PT-IF-07527 Herschel/Planck Packet Structure Interface Control Document(PS-ICD)

2.2 Reference Documents


RD1 HSCDT-TN-017 Understanding of the Interfaces between the CCS and theHerschel Instrument EGSEs in the IST

RD2 H-P-SP-AI-0014 PCDU REQUIREMENT SPECIFICATION

RD3 H-P-SP-AI-0003 CDMU Hardware REQUIREMENT SPECIFICATION

RD4 H-P-SP-AI-0011 ACMS REQUIREMENT SPECIFICATION

RD5 H-P-1-SP-AI-0015 SAS REQUIREMENT SPECIFICATION

RD6 H-P-1-SP-AI-0022 Batteries REQUIREMENT SPECIFICATION

RD7 H-P-SP-AI-0012 X/X Band Transponder Specification

RD8 H-P-SP-AI-0023 RFDN Specification

RD9 H-P-SP-AI-0024 X Band LGA Specification

RD10 H-P-SP-AI-0025 X Band MGA Specification

RD11 HP-2-ASED-TN-0048 Description of the PLM-FM Cryo Control Instrumentation

RD12 ARIANE 5 User’s Manual

RD13 S2K-MCS-ICD-0014-TOS-GCI SCOS-2000 OBSM External InterfacesControl Document


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 10/119

2.3 Applicable Documents


AD1 H-P-1-ASPI-SP-0045 EGSE General Requirements SpecificationsAD2 H-P-1-ASPI-SP-0082 H-P System Database SpecificationAD3 S2K-MCS-ICD-0001-TOS-GCI SCOS-2000 Database Import ICDAD4 NDIU3-DR-0001-GSY

ROS-MOC-NDIU-0001-GSYRO-ESC-RS-5002

NDIU3 for ROSETTA SVT’s Design Report (NDIU full)NDIU3 for ROSETTA SVT’s User Manual (NDIU full)I/F ROSETTA Gateway – TM/TC FEE (NDIU lite)

AD6 H-P-1-ASPI-SP-0141 Naming conventionAD7 H-P-1-ASPI-SP-0027 General Design and Interface RequirementsAD8 SCI-PT-ICD-07418 Space/Ground Interface Control DocumentAD9 H-P-1-ASPI-TN-0127 EGSE Quick Load/Dump Interfaces


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 11/119

2.4 Acronyms

Abbreviation SignificationAIT Assembly, Integration and TestBCE Battery Charge EquipmentBER Bit Error RateBHC Bloc House ConsoleBOB Break Out BoxBPSK Bi Phase Shift KeyingCCS Central Checkout SystemCCSDS Consultative Committee for Space Data SystemsCLCW Command Link Control WordCLTU Command Link Transmission UnitCOTE Check Out Terminal EquipmentCUC CCSDS Unsegmented time CodeEGSE Electrical Ground Support EquipmentEMC ElectroMagnetic CompatibilityFEE Front End EquipmentHK House KeepingHPSDB Herschel/Planck System DataBaseIF or I/F InterFacesJU Junction UnitLAN Local Area NetworkMMI Man Machine InterfaceMTBF Mean Time Between Failure1

MTTR Mean Time To Repare2

MOC Mission Operation CenterNA Non ApplicableNDIU Network Data Interface UnitNRZ-L Non Return to Zero-LevelNRZ-M Non Return to Zero-MarkOBCP On-board Control ProceduresOBSW On Board SoftWarePIPE Packet Interface Protocol for EGSERF Radio FrequencySAS Solar Array SimulatorSCOE Specific Check Out EquipmentTAI Temps Atomique InternationalTBC To Be ConfirmedTBD To Be DefinedTM/TC Telemetry & TelecommandUTC Universal Time CoordinatedUUT Unit Under TestVC Virtual Channels

1 Average time between two breakdown of the system2 Average time before complete repair of the system


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 12/119

3 GENERAL DESCRIPTION

3.1 FUNCTIONAL DESCRIPTION

This document is applicable to each EGSE equipment used for system AIT.

This document is the interface control document which contains the interface descriptionapplicable to the EGSE constituents as designed for the Herschel/Planck Satellites.Following communication paths between the CCS and the SCOE's are defined :

- Telemetry- Telecommand- SCOE Monitoring- SCOE Commands


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 13/119

POW

ERSC

OE

SCOE DFE LAN

PLANCKInstruments

SAS

TM/TC DFE (TBC)

UMBILICAL I/F

PLANCK SVM

PCDU

TM decoder

TM source pkt

CLCWprocess

RS decoder

Frame Sync

CLCW extract

TM rebuilt

TM packets

TCencoderCLTU

Frame

NDIU

NDIU Lite

ISDN lineto ESOC

NDIU LAN

ISDN lineto ESOC

ORTM frameh

CLTUh

UMBlink

UMBlink

RFlink

RFlink

TT&CSCOE

CLTUCLTU

TM frame

Controller

TC source pkt

Transceiver

CDMU

Batteries

BATSIM

Rx1Tx1

Rx2Tx2

ACC

CDM

USC

OE

TM/TCENC/DEC

1553BC

1553BC

1553RT

1553

1553RT

ACM

S SC

OE

1553

Rx/Tx

Feed

back

Opt

Stim

ACMS Equipments

1553RT

HFI

1553RT

LFI

1553RT

HFIIS EGSE

LFIIS EGSE

IS LAN (P)ccs

SCO

E DFE LAN

WWW station

WEBarchive

printers

BCE

COTE(LaunchConfig)

Umbilicalconnectors

TM/TC DFE

Safety Loop

Packetrouter

Qui

ckLo

ad/

Dum

p

HSDB Mirror site

TM + TC echo

SCSIS EGSE

THCT

SCO

ED

ISSI

PSC

OE

TC decoderCLTU

Frame

Packet

Figure 1 : Overview of the PLANCK EGSE architecture


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 14/119

POW

ERSC

OE

Qui

ckLo

ad/

Dum

p

SCOE DFE LAN

HERSCHELInstruments

SAS UMBILICAL I/F

HERSCHEL SVM

PCDU

TT&CSCOE

Transceiver

CDMU

Batteries

BATSIM

Rx1Tx1

Rx2Tx2

ACC

CD

MU

SCO

E

TM/TCENC/DEC

1553BC

1553BC

1553RT

1553

1553RT

AC

MS

SCO

E15

53

Rx/Tx

Feed

back

Opt

Stim

ACMS Equipments

1553RT

HIFI

1553RT

PACS

1553RT

SPIRE

1553RT

HIFIIS EGSE

PACSIS EGSE

SPIREIS EGSE

IS LAN (H)ccs

SCO

E DFE

LAN

WWW station

WEBarchive

StimuliIntrument

SCOE

COTE(LaunchConfig)

Umbilicalconnectors

TM/TC DFE

Safety Loop

Packetrouter

TM + RM+ TC echo

BCE

Her

sche

lC

RYO

SCO

E

THC

TSC

OE

DIS

SIP

SCO

E

CCU

1553RT

TM/TC DFE (TBC)

TM decoder

TM source pkt

CLCWprocess

RS decoder

Frame Sync

CLCW extract

TM rebuilt

TM packets

TCencoderCLTU

Frame

NDIU

NDIU Lite

ISDN lineto ESOC

NDIU LAN

ISDN lineto ESOC

ORTM frameh

CLTUh

UMBlink

UMBlink

RFlink

RFlink

CLTUCLTU

TM frame

Controller

TC source pkt

TC decoderCLTU

Frame

Packet

Figure 2 : Overview of the HERSCHEL EGSE architecture


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 15/119

PLANCK PLM : CQM

PLM EGSE

CCS light

SCOE/DFE LAN

INSTRUMENTEGSE

IS LAN

INSTRUMENTEGSE

INSTRUMENTEGSE

CDMUDFE

PLMSCOE

PLANCK PLM : PFM

PLM EGSE

CCS

SCOE/DFE LAN

INSTRUMENTEGSE

IS LAN

INSTRUMENTEGSE

INSTRUMENTEGSE

CDMUDFE

PLMSCOE

Figure 3 : EGSE PLANCK PLM Configuration


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 16/119

HERSCHEL PLM : EQM

PLM EGSE

CCS light

SCOE/DFE LAN

INSTRUMENTEGSE

IS LAN

INSTRUMENTEGSE

INSTRUMENTEGSE

Herschel CryoSCOECDMU

DFEPLM

SCOE

HERSCHEL PLM : PFM

PLM EGSE

CCS

SCOE/DFE LAN

INSTRUMENTEGSE

IS LAN

INSTRUMENTEGSE

INSTRUMENTEGSE

Herschel CryoSCOE

CDMUDFE

PLMSCOE

Figure 4 : EGSE HERSCHEL PLM Configuration


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 17/119

PLANCK SATELLITE

CDMU SCOE

CCS

SCOE/DFE LAN

POWERSCOEACMS SCOE TM/TC DFE TT&C SCOE

NDIU LAN

NDIU

www.station

LFIINSTRUMENT

EGSE

IS LAN

HFIINSTRUMENT

EGSE

SCSINSTRUMENT

EGSE

Figure 5 : EGSE PLANCK S/C Configuration

HERSCHEL SATELLITE

CDMU SCOE

CCS

SCOE/DFE LAN

POWERSCOEACMS SCOE TM/TC DFE TT&C SCOE

NDIU LAN

NDIU

www.station

IS LAN

PACSINSTRUMENT

EGSE

HIFIINSTRUMENT

EGSE

HerschelCryo SCOE

StimuliInstrument

SCOE

SPIREINSTRUMENT

EGSE

Figure 6 : EGSE HERSCHEL S/C Configuration


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 18/119

HERSCHEL SATELLITE

CCS

SCOE/DFE LAN

COTE

TM/TC DFE

IS LAN

PACSINSTRUMENT

EGSE

HIFIINSTRUMENT

EGSE

SPIREINSTRUMENT

EGSE

HerschelCryo SCOE LPS TM/TC

apmli

Figure 7 : HERSCHEL EGSE Launch Configuration

PLANCK SATELLITE

CCS

SCOE/DFE LAN

TM/TC DFE

LFIINSTRUMENT

EGSE

IS LAN

HFIINSTRUMENT

EGSE

SCSINSTRUMENT

EGSE

COTE

LPS TM/TCapmli

Figure 8 : PLANCK EGSE Launch Configuration


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 19/119

EGSE Specification Tree

EGSE GeneralRequirements Specification

H-P-1-ASPI-SP-0045

PL PF INTERFACE

Herschel Cryo SCOERequirements Specification

CCSRequirement Specification

EGSE INTERFACERequirement Specification

HP-2-ASED-PS-0013 H-P-SP-AI-0010 H-P-1-ASPI-IS-0121

TM/TC DFERequirement Specification

H-P-SP-AI-0030

POWER SCOERequirement Specification

H-P-SP-AI-0028

TT&C SCOERequirement Specification

H-P-SP-AI-0029

ACMS SCOERequirement Specification

H-P-SP-AI-0013

CDMU SCOERequirements Specification

H-P-SP-AI-0027

PLM SCOERequirement Specification

H-P-SP-AI-0019

CDMU DFERequirement Specification

H-P-SP-AI-0020

THCT SCOE (TBC)3

Requirement SpecificationH-P-1-ASPI-SP-xxxx

DISSIP SCOE (TBC)4

Requirement SpecificationH-P-1-ASPI-SP-xxxx

3 SCOE neither specify, procure and use by Alenia4 SCOE neither specify, procure and use by Alenia


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 20/119

3.2 SPECIFIC TERMS AND DEFINITION

There are a number of concepts that have been adopted within the EGSE that have an effecton the specification of the interfaces described in this document. These can be summarised asthe following:

The CCS is solely responsible for sending telecommands and commanding the SCOE’s.

The SCOE’s are not required to support a test sequencing capability

The SCOE’s shall be able to be controlled completely from the CCS without intervention on theSCOE

The CCS is responsible for archiving all Low rate Telemetry, Telecommand Data and all otherCCS/SCOE traffic


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 21/119

4 EGSE INTERNAL INTERFACE REQUIREMENTS

4.1 PROTOCOL DEFINITION

4.1.1 General

Assuming that source packet are provided as the highest level data units for both TM and TC,typical EGSE and simulation systems would require a data routing mechanism that allowsPackets to be transferred from one system to another.The simplest solution can be found in routing the Source Packet from one location to anotherwithout any additional information or encapsulation. Analysis shows however that even in asimple environment, additional information would be required.

This solution allows PIPE protocol to adopt the following concepts:- Allow for separate TM and TC data link- Allow for dedicated command link (RC)- Allow for Acknowledge RC- Allow for Acknowledge TC- Allow for SCOE/DFE/IS monitoring link (RM)- Allow for Telemetry distribution link- Allow for TC Echo link

The main purpose of PIPE protocol is to allow Packets exchange between EGSE itemsconnected via LAN.

The protocol is structured in such a way that Packets are transferred without anychanges. This is achieved by the attachment of an information header that containadditional information required for proper routing and processing of the Packets.This complete data structure is referred to as a PIPE message.

The header contains a number of fixed fields that can be used to identify and allowfurther processing of the Packet.

Following the header, a complete (unchanged) Packet is embedded into themessage. The Packet can have a maximum length of 65542 Bytes as dictated by[S2] and [S3] although the protocol definition would allow larger data structures tobe transported.

It should be noted that the PIPE-Protocol specification allows for larger data structures to betransported. For the purpose of describing CCSDS and ESA related Packets the recommendedlength is however limited to 65542 bytes.


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 22/119

[IFRQT-0010] [Analysis]

The communication and control interface between EGSE item shall be based under 100 Mb/sETHERNET network using TCP/IP with a class B IP network addressing.

- Communication between CCS and SCOE shall be done via SCOE/DFE LAN- Communication between CCS and Instrument Station shall be done via IS LAN- Communication between CCS and www station shall be done via standard LAN and isnot covered by this specification- Communication between TM/TC DFE and NDIU shall be done via [AD4]


This control/command exchange is based on the PIPE protocol dedicated to real timecommunication.


They are two types of exchanged data:Control Flow:

- Telecommand Packets sending on-board (TC)- EGSE Remote Command (RC) (Packets sent by CCS to SCOE for commanding this SCOE

(configuration, set value, synch...))

Monitoring Flow:- On-board Telemetry Packets (TM)- EGSE Remote Message Packets (RM) (Packet generated by each SCOE (one packet per

SCOE identified by APID) sent to CCS containing its internal data like status, logging message, errorreport, data acquisition...):

• Periodic packets containing vital data acquired/measured by SCOE

• Asynchronous packets containing special SCOE/DFE/ISevent/error/warning

- Acknowledge RC packets- Acknowledge TC packets- TC Echo distribution


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 23/119

[IFRQT-0040] [Analysis]It shall be foreseen to have a single TCP/IP socket for each connection between SCOE/DFE/ISand CCS

[IFRQT-0042] [Analysis]PIPE protocol shall manage the priority of the message according to the following scheme :1. TM acquisition from TM/TC DFE2. Asynchronous messages3. Acknowledge messages4. Periodic messages

CCS

PlanckI.EGSE

SCOE'S

TM d

istrib

.

RCRM

TM/TCDFE

RMRC

NDIU

TC (A

D04

)

TCTM (HK + PL)

IS LAN

SCOE/DFE LANSCOE/DFE LAN

NDIU LAN

TM (A

D04

)

TC E

cho

TC E

cho

TC Echo TM distrib

TC Echo

TM distrib.

RM

ACKRC

ACKRC

HerschelI.EGSE

www.server

not covered by this specification

LAN

RM


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 24/119

4.1.2 Communication Link

[IFRQT-0045] [Test]

The communication links between CCS and SCOE/DFE/IS shall be managed following aClient/Server philosophy where the CCS acts as a Client and the SCOE/DFE/IS is the Serversaccepting connection and service requests.

[IFRQT-0050] [Test]

Each SCOE, DFE or Instrument Station (IS) shall automatically accept a "connection request"coming from the CCS in order to try to establish the connection after the On-line software start-up and in general every time the connection itself is dropped or failed.

[IFRQT-0060] [Test]

Deleted

[IFRQT-0070] [Analysis]The connection between the CCS and a SCOE/DFE/IS shall be considered open as soon asTCP/IP connection has been successfully established.

[IFRQT-0080] [Test]

The CCS shall expect to receive from each SCOE/DFE/IS a status packet every 60 seconds.In case packets will not be received, the connection will be dropped by the CCS.

[IFRQT-0090] [Test]

Deleted

[IFRQT-0100] [Test]

In case of logical connection broken or any problem to open/close a connection, the CCS andthe SCOE/DFE/IS concerned shall automatically raise an alarm to local operator I/F

[IFRQT-0102] [Test]

If any error is found reading data from the socket, the application software shall close theconnection immediately

[IFRQT-0103] [Test]

If the transmission of whichever message is not completed within 5 seconds (TBC), an errormessage shall be raised and managed.

[IFRQT-0104] [Test]

The CCS user shall be able to open and close the connection on explicit user command

[IFRQT-0110] [Test]


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 25/119

As soon as the connection between the CCS and a SCOE/DFE/IS is established, theSCOE/DFE/IS shall send to the CCS its own Remote Message packet (RM) whatever its mode is(Local or Remote).(See 4.6 MONITORING FLOW – Remote Message Packets)

4.1.3 Byte order

In this document the following convention is used to identify each bit in a forward-justified N-bit field.

The first bit in the field to be transmitted is defined to be ‘Bit 0’; the following bit is called ‘Bit1’ and so on, up to ‘Bit n-1’. When the field is used to express a binary value (such as aninteger), the Most Significant Bit (MSB) shall be the first transmitted bit of the field (i.e., ‘Bit 0’).

Bit 0 N-Bit data field Bit n-1MSB LSB

first bit transmitted

The byte order is ‘big endianity’

4.1.4 Message Structure

[IFRQT-0120] [Analysis]All the TCP-IP messages exchanged between the CCS, the TM/TC DFE and other SCOE start withthe PIPE Header followed by the Body.The PIPE header is added/removed by PIPE layer (it is not seen at application level)All the Integer value are under IEEE format

PIPE Header

Body message

8 bytes User defined (14 bytes< <65542 bytes)

Table 1 : PIPE message lay-out


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 26/119

4.1.5 PIPE Message HEADER

The PIPE Header consists of a fixed number of 10 bytes split up in several fields whoseminimum length is one byte.

The detailed structure of the PIPE header is depicted in the figure below:

Field Length(byte)

DESCRIPTION TYPE

Message ID 1 Identification of the message integerVCID 1 Filled only for TM message.

0x00 otherwise.integer

Remaining length 2 Length of the message excludingthe first 4 bytes

integer

Request ID 4 Filled only for TC message0x00 otherwise.

integer

Synchronisation Word 2 Synchro of PIPE message integer

Table 2 : PIPE message Header

Message IDIn order to support a number of different messages with different purpose, a PIPE message starts witha one byte message identifier. This ID can be used to make a distinction between different control,status and data messages.

VCIDThe one-byte Virtual Channel ID field indicates on which VCID are downlinked the TM source packet.This field is filled by TM/TC DFE.

Remaining Message lengthThe message length is a two-byte length field indicating the remaining length of the message includingthe remaining header fields and data.

Request IDThe 4 bytes field identifies which TC will be sent. This value will be checked with that one return by theTC Report message.This field is filled by CCS.

Synchronisation WordThe two-bytes field is used to assure the PIPE protocol management.This field will be forced to 0xFADE


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 27/119

4.1.6 Body message

The Body Message is constituted of one Header Field and of one Data Field.The Header Field have a total length of 6 bytes.The Data Fields can have a minimum length of 14 bytes and a maximum length of 65536bytes as dictated by the CCSDS & ESA packet standards [S2] and [S3].

4.1.6.1 Monitoring Flow message (SCOE’s/DFE/IS CCS)


For on-board Telemetry Packet, the complete body message shall be used to embed aPacket without any modifications to the contents or length of the Packet in question


For Remote Message (RM) Packets provided by SCOE’s, the complete body message shallbe formatted as TM source packet and shall have the following structure :

SOURCE PACKET HEADER (48 bits)

PACKET DATA FIELD(VARIABLE)

Packet Identification Packet Sequence Control PacketLength

Data FieldHeader

Source Data PacketErrorCtrl

VersionNumber

Type DataFields

HeaderFlag

ApplicationProcess ID

Segmentation Flags

SourceSequence

count

3 1 1 11 2 1416 bits 16 bits 16 bits 80 bits N x 16 bits 16 bits

Spare TM SourcePacket PUS

VersionNumber

Spare PacketType

PacketSub-Type

Spare Time

(1 bits) (3 bits) (4 bits) (8 bits) (8 bits) (8 bits) (48 bits)


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 28/119

field length VALUE TYPEVersion number 3 bits forced to ‘000‘ binaryType 1 bit forced to ‘0‘ binaryData field header flag 1 bit forced to ‘1‘ binaryApplication process ID 11 bits @ originator of TM packet integerSegmentation flags 2 bits forced to ‘11‘ binarySource sequence count 14 bits Packet count per APID binaryPacket length 16 bits length of packet data field - 1 IntegerPacket header

Spare 1 bits forced to ‘0‘ binaryPUS version number 3 bits forced to ‘000‘ binary

Spare 4 bits forced to ‘0000’ binaryPacket type 8 bits depend on the service type binary

Packet sub-type 8 bits depend on the service sub type binarySpare 8 bits forced to ‘0000 0000’ binaryTime 48 bits Packet time CUC

Source data variable SCOE/DFE/IS parameter list variablePacket error control 16 bits Not Used binary

Application process IDThe APID field indicating uniquely identifies the source of the packet.For Remote Message Packet, the APID identifies the SCOE/DFE/IS emitting the packet.

Packet lengthThe Packet Length field specifies the number of octets contained within the Packet Data Field,including the Data Field Header. The number is an unsigned integer “C” whereC = (Number of octets in Packet Data Field) - 1

Packet Type:This indicates the Service to which this telemetry source packet relates.

Packet Subtype:Together with the Packet Type, the Subtype uniquely identifies the nature of the Service constituted bythis telemetry source packet.

Time:This field represents the EGSE reference time of the packet, expressed in CUC. Details ofthe time field are given in appendix 6 of [S4]

Source Data (Variable)The source data constitutes the data element of the RM packet. It contains all internal parameter ofeach SCOE’s.

Packet Error Control (PEC) (16 bits)The Packet Error Control field shall transport an error detection code that can be used by the groundto verify the integrity of the complete telemetry source packet not used for RM


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 29/119

4.1.6.2 Control Flow message (CCS SCOE’s/DFE/IS)


For Telecommand Packets, the complete body message shall be used to embed a Packetwithout any modifications to the contents or length of the Packet in question


For Remote Command (RC) Packets sent to SCOE’s, the complete body message shall beformatted as TC packet and shall have the following structure :

SOURCE PACKET HEADER (48 bits)

PACKET DATA FIELD(VARIABLE)

Packet Identification Packet Sequence Control PacketLength

Data FieldHeader

ApplicationData

PacketErrorCtrl

VersionNumber

Type DataFields

HeaderFlag

ApplicationProcess ID

SequenceFlags

Sequencecount

3 1 1 11 2 1416 bits 16 bits 16 bits 32 bits N x 16 bits 16 bits

Seq flag Seq Count(3 bits) (11 bits)

CCSDSSecondary

Header flag

TC SourcePacket PUSVersion Nbr

Acknowledge PacketType

PacketSub-Type

Spare

(1 bit) (3 bits) (4 bits) (8 bits) (8 bits) (8 bits)


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 30/119

field length VALUE TYPEVersion number 3 bits forced to ‘000‘ binaryType 1 bit forced to ‘1‘ binaryData field header flag 1 bit forced to ‘1‘ binaryApplication process ID 11 bits SCOE/DFE/IS destination address integerSequence flags 2 bits forced to ‘11‘ binarySequence count binary

Source part 3 bits forced to ‘111‘ binarySequence part 11 bits Packet count per APID binary

Packet length 16 bits length of packet data field - 1 IntegerPacket header

CCSDS Sec Header flag 1 bits forced to ‘0‘ binaryPUS version number 3 bits forced to ‘000‘ binary

Acknowledge 4 bits forced to '0001' binaryPacket type 8 bits depend on the message type binary

Packet sub-type 8 bits depend on the service sub type binarySpare 8 bits forced to ‘0000 0000’ binary

Application data variable parameter list variablePacket error control 16 bits Not Used for RC only binary

Application process IDThe Application Process ID defines the application or unit that the Telecommand isaddressed to.For Remote Command Packet, the APID identifies the SCOE/DFE/IS receiving the packet.

Sequence Count: (14 bits):This field is provided to identify a particular Telecommand packet so that it can be traced within theend-to-end Telecommand system. The field is divided into two parts as follows:

Source part (3 most significant bits) identifies the generator or source of a certain commandas follows:

000 = Ground, all sources (maintained by ground)Sequence part (11 bits) shall be used to represent the actual Sequence Count. The SequenceCount is maintained by the Telecommand source for each Application Process ID. Thesequence count shall be incremented by 1 whenever a command is generated with thatApplication Process ID. The counter wraps around from “full-scale” to zero.When an acknowledgement of a TC-packet is required (see “Ack” field in the data field headerbelow), it is mandatory that the full Sequence Control field is included in the telemetryacknowledge packet as the identifier of the Telecommand packet being acknowledged (see§4.7). No check is to be performed by the addressed application regarding the monotony of thesequence counter, the application shall accept commands regardless of the sequencecounter.


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 31/119

Packet lengthThe Packet Length field specifies the number of octets contained within the Packet Data Field,including the Data Field Header. The number is an unsigned integer “C” whereC = (Number of octets in Packet Data Field) - 1

Packet Type:This indicates the Service to which this telecommand source packet relates.

Packet Subtype:Together with the Packet Type, the Subtype uniquely identifies the nature of the Service constituted bythis telecommand source packet.

Ack:This field is used to indicate which acknowledgements, in the form of Telecommandverification packets, are required to notify acceptance and to verify execution of thisTelecommand packet. This relates only to acknowledgement of successful acceptance andexecution, since failure reports shall be generated by default.The bit settings shall be as follows:

---1 (bit 3 of the Ack field set): mandatory, acknowledge acceptance of the packetby the Application Process

Application DataThe Telecommand application data constitute the data element of the Remote Command tobe used by the CCS to command SCOE’s.

Packet Error Control (PEC) (16 bits)The purpose of the mandatory Packet Error Control field is to transport an error detection codethat shall be used by the receiving Application Process to verify the integrity of the completeTelecommand Packet Not used for RC


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 32/119

4.1.7 Message ID List

Message ID

TYPE Description (Type,SubType

)

Source Dest. [IFRQT-]

0x80 TC TELECOMMAND Packets CCS TM/TC DFE 01700xA0 TC Echo TC Echo TM/TC DFE CCS - NDIU 0809

CCS IS station0x57 TC Report TC Report (1,1) TM/TC DFE CCS - NDIU 0809-10x44 RC CCS REMOTE

Commanding PacketsCCS SCOE/DFE 0200

0x10 RM Periodic RM Message (3,25) SCOE/DFE/IS CCS 05300x10 RM Asynch. RM Message (5,1) SCOE/DFE/IS CCS 05350x11 RM RM Alive Packet SCOE/DFE/IS CCS 0809-20x20 TM On-Board Telemetry

Packets acquisitionSCOE/DFE CCS 0500

0x21 TM Telemetry PacketsDistribution

CCS SCOE/DFE/IS 0520

0x10 ACKRC RC Execution Report -Started

(1,3) SCOE/DFE CCS 0805

0x10 ACKRC RC Execution report –Progress


0x10 ACKRC RC Execution report –Completed


0x10 ACKRC RC Execution report –Failure


0x50 ACKRC RC Acceptance report –Success


0x51 ACKRC RC Acceptance report –Failure


0x55 ACKTC TC Acceptance report –Success

(1,1) TM/TC DFE CCS 0808-2

0x56 ACKTC TC Acceptance report –Failure

(1,2) TM/TC DFE CCS 0808-3


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 33/119

4.2 CONTROL FLOW – TELECOMMAND Packets

[IFRQT-0170] [Test]

CCS shall send Telecommand Packets to TM/TC DFE without any modifications to thecontents or length of the Packet in question

Source CCSDestination TM/TC DFERate 4 kb/sLAN SCOE/DFE LAN

PIPEstructure

Field Description Size(bytes)

Values TYPE

Header Message ID 1 Forced to 0x80 integerVCID 1 Forced to 0x00 integerRemaining length 2 Variable integerRequest ID 4 Variable (filled by CCS) integerSynchronisation Word 2 Forced to 0xFADE integer

Body TC Packet variable variable


Message ID shall be forced to 0x80.


Deleted


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 34/119

4.3 CONTROL FLOW – CCS REMOTE Commanding Packets

Source CCSDestination SCOE/DFERate N/A

SCOE/DFE LANLAN


CCS shall send Remote Command (RC) Packets to SCOE’s/DFE using the following format

PIPEstructure

Field Description Size Values TYPE

Header Message ID 1 byte Forced to 0x44 integerVCID 1 byte Forced to 0x00 integerRemaining length 2 bytes Variable integerRequest ID 4 bytes Forced to 0x00000000 integerSynchronisation Word 2 bytes Forced to 0xFADE integerVersion number 3 bits forced to ‘000‘ binaryType 1 bit forced to ‘1‘ binaryData field header flag 1 bit forced to ‘1‘ binaryApplication process ID 11 bits SCOE destination address integerSequence flags 2 bits forced to ‘11‘ binarySequence flag 3 bits forced to ‘111‘ binarySequence Count 11 bits Packet count per APID binaryPacket length 2 bytes length of packet data field Integer

Body CCSDS Sec Header flag 1 bits forced to ‘0‘ binaryPUS version number 3 bits forced to ‘000‘ binaryAcknowledge 4 bits TBD binaryPacket type 1 byte TBD integerPacket sub-type 1 byte TBD integerSpare 4 bits forced to ‘0000’ binaryApplication data

RC_ID 1 byte TBD integerParameter variable TBD variable

... variableParameter variable TBD variable

Packet error control 2 bytes Not Used binary


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 35/119


Message ID shall be forced to 0x44.


Each Remote Command shall be identified by one unique mnemonic defined in HPSDB (as forTC.)


Application data shall be composed of: RC_ID field (which identify uniquely the RC) andparameters fields (optional)


HPSDB will link the RC mnemonic with all the data in order to built the RC packet message andto identify the target IP address and name:

RC Mnemo RC_ID SCOE IF Name APIDIP name IP address

Parameter Transfer functionPIPE message lengthRC Packet lengthPacket typePacket sub type

[IFRQT-0245] [Information]

The list of commands and parameters contained in Application Data field is non exhaustive; Itshall be filled by the Sub-Contractor of each SCOE.

REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 36/119

4.3.1 COMMUNICATION VIA SCOE/DFE LAN

4.3.1.1 CCS Commands

[IFRQT-0250] N/A [Analysis]

4.3.1.2 CCS → CDMU SCOE Commands

[IFRQT-0260] To Be Completed [Test]

CDMU SCOE shall accept from CCS at least the following command

ParameterRC mnemonic RC_ID

number Ack packettype

packetsub-type parameter field Name Type Transfer

functionMin

valueMaxvalue Operational description

RC mnemonic Operational description

Execute Self-testSwitch the SCOE to ON lineSwitch the SCOE to OFF lineSwitch the SCOE to LOCAL ModeSwitch the SCOE to REMOTE ModeEnable of archiveDisable of archiveStop the running Application Software (All power supply set to 0, all relays Open)


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 37/119

Switch ON the simulation of each unit (instruments, RTU)Switch OFF the simulation of each unit (instruments, RTU)Switch ON the TM packet production for each simulated unit and for each type ofpacketSwitch OFF the TM packet production for each simulated unit and for each type ofpacketSwitch ON the Bus monitoring function.Switch OFF the Bus monitoring function.Start Simulation of Experiment Telemetry as defined in the simulation files and sendthen onto the 1553 BusStop Simulation of Experiment TelemetryEnable the Telemetry End-to-End loopDisable the Telemetry End-to-End loopEnable the Telecommand End-to-End loopDisable the Telecommand End-to-End loopExecute a pre-programmed sequences of commandsSwitch between the nominal and redundant 1553 BusEnable the 1553 Bus traffic Acquisition and monitoring functionDisable the 1553 Bus traffic Acquisition and monitoring function


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 38/119

4.3.1.3 CCS → ACMS SCOE Commands

[IFRQT-0270] To Be Completed [Test]ACMS SCOE shall accept from CCS at least command to :




functionMin



Execute Self-testSwitch the SCOE to ON lineSwitch the SCOE to OFF lineSwitch the SCOE to LOCAL ModeSwitch the SCOE to REMOTE ModeEnable of archiveDisable of archiveStop the running Application Software (All power supply set to 0, all relays Open)Start/hold/suspend/terminate/kill an Application Test Program


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 39/119

4.3.1.4 CCS → TT&C SCOE Commands


TT&C SCOE shall accept from CCS at least the following command




functionMin



Execute Self-testSwitch the SCOE to ON lineSwitch the SCOE to OFF lineSwitch the SCOE to LOCAL ModeSwitch the SCOE to REMOTE ModeStop the running Application Software (All power supply set to 0, all relays Open)Switch between antenna pathsSwitch up/down link signal to measurement devicesSet up-link and down-link frequencyExecute measurements passing arguments to automated routines.Select up-link modesSelect ranging toneSweep uplink carrierSelect modulation indexSet attenuationUplink Carrier Acquisition ThresholdLock MaintenanceUplink Command Execution ThresholdUp link RF Power Measurements


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 40/119

Down link RF Power MeasurementsPhase Noise MeasurementModulation index measurementRanging Group Delay MeasurementRanging Amplitude ResponseFrequency Stability Measurement


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 41/119

4.3.1.5 CCS → TM/TC DFE Commands

[IFRQT-0290] [Test]

TM/TC DFE SCOE shall accept from CCS at least the following command




functionMin



Execute Self-testSwitch the SCOE to ON lineSwitch the SCOE to OFF lineSwitch the SCOE to LOCAL ModeSwitch the SCOE to REMOTE ModeStop the running Application Software (All power supply set to 0, all relays Open)Select Bypass TM linkSelect Nominal TM link (nominal on-board processor)Select Redundant TM link (redundant on-board processor)Select RF TM linkSelect Bypass TC linkSelect Nominal TC link (nominal on-board decoder)Select Redundant TC link (redundant on-board decoder)Select Nominal MAP IDSelect Redundant MAP IDSelect RF TC link


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 42/119

Select TC source to CCSSelect TC source to NDIUOpen TM frame link to NDIUClose TM frame link to NDIUEnable of Transfer Frame (TM and TC) archiveDisable of Transfer Frame (TM and TC) archiveEnable of Source Packets (TM and TC) archiveDisable of Source Packets (TM and TC) archiveStart Replay managementStop Replay managementStart Simulation managementStop Simulation managementEnable COP-1 managementDisable COP-1 managementEnable AD serviceEnable BC serviceEnable BD service

Start of Data distribution requestStop Data distribution request


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 43/119

4.3.1.6 CCS → Umbilical I/F Module Commands


POWER SCOE shall accept from CCS at least command to :




functionMin



Execute Self-testSwitch the SCOE to ON lineSwitch the SCOE to OFF lineSwitch the SCOE to LOCAL ModeSwitch the SCOE to REMOTE ModeStop the running Application Software (All power supply set to 0, all relays Open)Open Nominal Separation switch 1Close Nominal Separation switch 1Open Nominal Separation switch 2Close Nominal Separation switch 2Open Nominal Separation switch 3Close Nominal Separation switch 3Open Redundant Separation switch 1Close Redundant Separation switch 1Open Redundant Separation switch 2Close Redundant Separation switch 2Open Redundant Separation switch 3Close Redundant Separation switch 3Send High Priority Commands 1


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 44/119

Send High Priority Commands nSet On Line Power supply outputSet Off Line Power supply outputOpen Nominal Umbilical switchClose Nominal Umbilical switch 1Open Redundant Umbilical switchClose Redundant Umbilical switch 1Set power supply to the specific voltage valueSet power supply to the specific current value


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 45/119

4.3.1.7 CCS → BATSIM SCOE Commands

[IFRQT-0310] To Be Completed [Test]Battery Simulator SCOE shall accept from CCS at least command to :




functionMin



Execute Self-testSwitch the SCOE to ON lineSwitch the SCOE to OFF lineSwitch the SCOE to LOCAL ModeSwitch the SCOE to REMOTE ModeStop the running Application Software (All power supply set to 0, all relays Open)Set Battery Voltage characteristicsSet Battery Current characteristicsSet power supply to the specific voltage valueSet power supply to the specific current valueSet battery temperature 1 valueSet battery temperature 2 valueSet Over-Voltage valueSet Over-Current valueStart Simulation ModeStop Simulation ModeSimulate of battery nominal mode (sun presence)Simulate of battery discharge mode (eclipse)


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 46/119

Simulate of battery charge mode (sun presence after eclipse)Simulate of battery Taper mode

4.3.1.8 CCS → SAS SCOE Commands


Solar Array Simulator shall accept from CCS at least command to :




functionMin



Execute Self-testSwitch the SCOE to ON lineSwitch the SCOE to OFF lineSwitch the SCOE to LOCAL ModeSwitch the SCOE to REMOTE ModeStop the running Application Software (All power supply set to 0, all relays Open)Set all SAS section relays On-LineSet all SAS section relays Off-LineSet all SAS section relays 1 On-LineSet all SAS section relays 1 Off-Line…Set all SAS section relays 2 to 29 On-LineSet all SAS section relays 2 to 29 Off-Line…


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 47/119

Set all SAS section relays 30 On-LineSet all SAS section relays 30 Off-LineSet Voltage characteristic for SAS section 1Set Current characteristic for SAS section 1

Set Voltage characteristic for SAS section 2 to 29Set Current characteristic for SAS section 2 to 29

Set Voltage characteristic for SAS section 30Set Current characteristic for SAS section 30Start transition from Sunlit to EclipseStart transition from Eclipse to SunlitSet Section Number val1 to val2 current, with val3 seconds durationSet all power supply current to 0 AMP , with Val seconds duration

Set Over-Voltage valueSet Over-Current valueSet thermistor 1 to val1Set thermistor 1 to val2

4.3.1.9 CCS → BCE SCOE Commands

[IFRQT-0330] N/A (no interface with CCS) [Test]


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 48/119

4.3.1.10 CCS → LAUNCH POWER SUPPLY Commands





functionMin



Execute Self-testSwitch the SCOE to ON lineSwitch the SCOE to OFF lineSwitch the SCOE to LOCAL ModeSwitch the SCOE to REMOTE ModeStop the running Application Software (All power supply set to 0, all relays Open)Send High Priority Commands 1Send High Priority Commands nSet On Line Power supply outputSet Off Line Power supply outputOpen Nominal Umbilical switchClose Nominal Umbilical switch 1Open Redundant Umbilical switchClose Redundant Umbilical switch 1Set power supply to the specific voltage valueSet power supply to the specific current value


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 49/119

4.3.1.11 CCS → SIS SCOE Commands

[IFRQT-0350] [Test]

Deleted


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 50/119

4.3.1.12 CCS → PLM SCOE Commands





functionMin



Execute Self-testSwitch the SCOE to ON lineSwitch the SCOE to OFF lineSwitch the SCOE to LOCAL ModeSwitch the SCOE to REMOTE ModeStop the running Application Software (All power supply set to 0, all relays Open)Send High Priority Commands 1Send High Priority Commands nSet On Line Power supply outputSet Off Line Power supply outputSet power supply to the specific voltage valueSet power supply to the specific current valueSet ON/OFF power line LCL 1Set ON/OFF power line LCL …Set ON/OFF power line LCL nReset LCL Safety Loop


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 51/119

4.3.1.13 CCS → Herschel Cryo SCOE Commands





functionMin



Execute Self-testSwitch the SCOE to ON lineSwitch the SCOE to OFF lineSwitch the SCOE to LOCAL ModeSwitch the SCOE to REMOTE ModeEnable of archiveDisable of archiveSet arming command valve 1Switch ON to OFF valve 1Switch OFF to ON valve 1…Read sensorsSet Measuring mode to CONTNUOUSSet Measuring mode to FIX_TIME_PERIODSet Measuring period to nn SecondsSet arming command heater 1Switch ON to OFF heater 1Switch OFF to ON heater 1


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 52/119

…Switch ON current for Liquid Level measurementSwitch OFF current for Liquid Level measurement

4.3.1.14 CCS → Planck PLM SCOE Commands

[IFRQT-0380] Deleted [Test]

4.3.1.15 CCS → Planck Sorption SCOE Commands


4.3.1.16 CCS → CDMU DFE Commands





functionMin



Execute Self-test


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 53/119

Switch the SCOE to ON lineSwitch the SCOE to OFF lineSwitch the SCOE to LOCAL ModeSwitch the SCOE to REMOTE ModeEnable of archiveDisable of archiveStop the running Application Software (All power supply set to 0, all relays Open)Switch ON the simulation of each unit (instruments, RTU)Switch OFF the simulation of each unit (instruments, RTU)Switch ON the TM packet production for each simulated unit and for each type ofpacketSwitch OFF the TM packet production for each simulated unit and for each type ofpacketSwitch ON the Bus monitoring function.Switch OFF the Bus monitoring function.Start Simulation of Experiment Telemetry as defined in the simulation files and sendthen onto the 1553 BusStop Simulation of Experiment TelemetryExecute a pre-programmed sequences of commandsSwitch between the nominal and redundant 1553 BusEnable the 1553 Bus traffic Acquisition and monitoring functionDisable the 1553 Bus traffic Acquisition and monitoring functionSend High Level Command number valSend Low Level Command number valSend Memory Load Command number val


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 54/119

4.3.1.17 CCS → 1553 Bus Probe Commands

[IFRQT-0405] N/A [Test]

4.3.1.18 CCS → Quick Load Commands

[IFRQT-0410] [Test]TBD


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 55/119

4.3.2 COMMUNICATION VIA Instrument Station LAN

4.3.2.1 CCS → Instrument Stimuli SCOE Commands


4.3.2.2 CCS → HFI EGSE Commands


4.3.2.3 CCS → LFI EGSE Commands


4.3.2.4 CCS → HCSS SCOE Commands



REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 56/119

4.3.2.5 CCS → HIFI EGSE Commands


4.3.2.6 CCS → PACS EGSE Commands


4.3.2.7 CCS → SPIRE EGSE Commands


4.3.3 COMMUNICATION VIA www LAN

4.3.3.1 CCS → www.Server Commands



REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 57/119

4.4 MONITORING FLOW - On-Board Telemetry Packets acquisition

Source TM/TC DFEDestination CCSRate As soon as a valid

packet is availableLAN SCOE/DFE LAN


TM/TC DFE shall send all TM source packet received to CCS using the following format

PIPEstructure


Header Message ID 1 byte Forced to 0x20 integerVCID 1 byte Variable integerRemaining length 2 bytes Variable integerRequest ID 4 bytes Forced to 0x00000000 integerSynchronisation Word 2 bytes Forced to 0xFADE integer

Body TM Source Packet variable variable


TM/TC DFE shall transmit TM Packet as soon as a valid TM packet is available.


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 58/119

4.5 MONITORING FLOW - Telemetry Packets Distribution

Source CCSDestination SCOE/DFE/ISRate As soon as a valid

packet is availableSCOE/DFE LANLANIS LAN

[IFRQT-0520] [Analysis]The CCS shall be able to distribute all incoming Packets to the proper destination on the basis oftheir APID.The TM distribution is based oon a table define inside the HPSDB.

PIPEstructure


Header Message ID 1 byte Forced to 0x21 integerVCID 1 byte Variable integerRemaining length 2 bytes Variable integerRequest ID 4 bytes Forced to 0x00000000 integerSynchronisation Word 2 bytes Forced to 0xFADE integer

Body TM Source Packet variable variable


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 59/119

4.6 MONITORING FLOW – Remote Message Packets


Two kinds of Remote Message shall be foreseen :1. Periodic RM packets containing vital data measured/acquired by each SCOE2. Asynchronous RM packets containing special events /errors/warning notification


Message ID shall be forced to 0x10


Source data shall contain all the necessary information concerning the SCOE (status, current,voltage, temperature, alarm, etc...)The content of these fields is describe for each SCOE in the following paragraphs.The list of parameters contained in Source Data field is non exhaustive; It shall be filled by theSub-Contractor of each SCOE.


Each RM Packet shall be identified by its APID defined in HPSDB (as for TM packets.)Refer to Table 3


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 60/119

4.6.1 PERIODIC RM Message

Source SCOE/DFE/ISDestination CCSRate 1 packet/second for POWER SCOE and PLM SCOE

1 packet/10 seconds for all other SCOE/DFE/ISSCOE/DFE LANIS LAN

LAN


Each SCOE/DFE shall send its own (and unique) Remote Message (RM) Packets to the CCSusing the following format.The period of these RM Message shall be available in each SCOE/DFE configuration file andshall be modifiable.

PIPEstructure


Header Message ID 1 byte Forced to 0x10 integerVCID 1 byte Forced to 0x00 integerRemaining length 2 bytes Variable integerRequest ID 4 bytes Forced to 0x00000000 integerSynchronisation Word 2 bytes Forced to 0xFADE integer

Version number 3 bits forced to ‘000‘ binaryType 1 bit forced to ‘0‘ binaryData field header flag 1 bit forced to ‘1‘ binaryApplication process ID 11 bits @ source SCOE integerSegmentation flags 2 bits forced to ‘11‘ binarySource sequence count 14 bits Packet count per APID binaryPacket length 2 bytes length of packet data field Integer

Body Spare 1 bits forced to ‘0‘ binaryPUS version number 3 bits forced to ‘000‘ binary

Spare 4 bits forced to ‘0000’ binaryPacket type 1 byte Forced to 0x03 integer

Packet sub-type 1 byte Forced to 0x19 integerTime 48 bits Packet sending time CUC

Source data variable parameter list variablePacket error control 2 bytes Not Used integer


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 61/119

4.6.2 ASYNCHRONOUS RM Message (Event Report)

Source SCOE/DFE/ISDestination CCSRate Asynchronous

SCOE/DFE LANIS LAN

LAN


When a special event happen (error, warning, …), each SCOE/DFE shall send an Event Report tothe CCS using the following format

PIPEstructure







Source data variable parameter list variablePacket error control 2 bytes Not Used integer


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 62/119

4.6.3 COMMUNICATION VIA SCOE/DFE LAN

4.6.3.1 RM CDMU SCOE Definition


Periodic RM (3,25)

Source Data FieldOperationalmnemonic Operational description Length

(byte) TypeTBD SCOE mode

0 Local mode1 Remote mode

1 Integer

TBD Software activity :0 idle1 loading2 running3 simulation4 Self Test5 TBD

1 Integer

TBD SCOE Configuration :0 TBD

1 Integer

TBD SCOE On-line/Off-line status0 Off-line1 On-line

1 Integer

TBD 1553 Bus status0 Nominal Bus active1 Redundant Bus active

1 Integer

TBD RT address simulated 4 IntegerTBD 1553 profile trapped 4 Integer

Asynchronous RM (5,1)


(byte) TypeTBD Event ID

0 TBD1 Integer

TBD Local disk capacity0 Not OK (full)1 OK (not full)

1 Integer


1 Integer


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 63/119

4.6.3.2 RM ACMS SCOE Definition


Periodic RM (3,25)




1 Integer

TBD Software activity :0 idle1 loading2 running3 simulation4 Self test5 TBD

1 Integer

TBD SCOE Configuration :0 TBD1 TBD

1 Integer


1 Integer


1 Integer

TBD Data storage status0 started1 stopped

1 Integer

TBD Application test program status0 Started1 Held2 Suspend3 Terminated4 Killed

1 Integer

TBD




0 TBD1 Integer


1 Integer


1 Integer

TBD TC request (request for a TC to be send by CCS) 1 Integer


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 64/119

4.6.3.2.1 Quick Load

TBD

4.6.3.2.2 Optical Stimuli

TBD

4.6.3.2.3 Stimuli Feedback

TBD


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 65/119

4.6.3.3 RM TT&C SCOE Definition


Periodic RM (3,25)




1 Integer


1 Integer


1 Integer


1 Integer

TBD Antenna path0 TBD

1 Integer

TBD Up link signal switch status0 S/C1 Measurement devices

1 Integer

TBD Down link signal switch status0 S/C1 Measurement devices

1 Integer

TBD Up link frequency set-up TBD TBDTBD Down link frequency set-up TBD TBDTBD Up link mode

0 TBD1 Integer

TBD Ranging tone TBD TBDTBD Modulation Index

0 TBD1 Integer

TBD Attenuation Set-upTBD

TBD TBD

TBD Up link Carrier Acquisition Threshold TBD TBDTBD Up link Command Acquisition Threshold TBD TBDTBD Up link RF Power Measurement TBD TBDTBD Down link RF Power Measurement TBD TBDTBD Phase noise measurement TBD TBDTBD Modulation index measurement TBD TBDTBD Ranging Group Delay Measurement TBD TBDTBD Ranging Amplitude Response TBD TBDTBD Frequency Stability Measurement TBD TBDTBD


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 66/119




0 TBD1 Integer


1 Integer

TBD 1 Integer


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 67/119

4.6.3.4 RM TM/TC DFE Definition


Periodic RM (3,25)




1 Integer


1 Integer


1 Integer


1 Integer

TBD TM Link0 Bypass1 RF

1 Integer

TBD TM Selection0 Nominal1 Redundant

1 Integer

TBD TC Link0 Bypass1 RF

1 Integer

TBD TC Selection (decoder selected)0 Nominal1 Redundant

1 Integer

TBD Current Active Services0 AD mode1 BD mode2 BC mode

1 Integer

TBD MAP-ID Selection (Processor Module selected)0 Nominal1 Redundant

1 Integer

TBD Squelch TC Selection0 Nominal1 Redundant

1 Integer

TBD Squelch TC Status0 Disabled1 Enabled

1 Integer

TBD TC provider0 CCS1 NDIU

1 Integer

TBD TM to NDIU switch status0 ON

1 Integer


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 68/119


(byte) Type1 OFF

TBD TM frame Archiving status0 started1 stopped

1 Integer

TBD TC CLTU Archiving status0 started1 stopped

1 Integer

TBD TM Source Packet Archiving status0 started1 stopped

1 Integer

TBD TC Source Packet Archiving status0 started1 stopped

1 Integer

TBD COP-1 status0 Disabled1 Enabled

1 Integer

TBD CLCW – Virtual Channel ID0 Nominal1 Redundant

6 bits Binary

TBD CLCW – “No RF Available” flag0 RF physical connection is available1 RF physical connection is NOT available

1 bit Binary

TBD CLCW – “No Bit Lock” flag0 At least one of the S/C demodulation units hasachieved bit lock1 None of the S/C demodulation units has achievedbit lock

1 bit Binary

TBD CLCW – “Lockout” flag0 FARM-1 is in Lockout state1 FARM-1 is not in Lockout state

1 bit Binary

TBD CLCW – “Wait” flag0 FARM-1 is in Wait state1 FARM-1 is not in Wait state

1 bit Binary

TBD CLCW – “Retransmit” flag0 FARM-1 does not request retransmission of all typeAD transfer frame1 FARM-1 requests retransmission of type AD transferframe

1 bit Binary

TBD CLCW – FARM B counter 2 bits BinaryTBD CLCW – CR Value

= V(R)1 Integer

TBD Frame Information – S/C ID 10 bits IntegerTBD Frame Information – Virtual Channel ID

VC0 Real Time HK TelemetryVC1 Real Time Science TelemetryVC2 Dump Spacecraft and Science HK TelemetryVC3 Dump Science TelemetryVC4 Not RequiredVC5 Not RequiredVC6 Not RequiredVC7 Idle Frames

3 bits Binary

TBD Frame Information – Master Channel FrameCount

1 Integer

TBD Frame Information – Virtual Channel Frame 1 Integer


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 69/119


(byte) TypeCount

TBD Idle frame rate 1 IntegerTBD TBD TBDTBD




0 TBD1 Integer


1 Integer

TBD TC buffer0 OK (not full)1 Not OK (full)

1 Integer

TBD Reed Salomon Error number 1 IntegerTBD


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 70/119

4.6.3.5 RM Umbilical I/F Module Definition


Periodic RM (3,25)




1 Integer


1 Integer


1 Integer


1 Integer

TBD On-line relay status0 Off-line1 On-line

1 Integer

TBD Main Bus Voltage 4 IntegerTBD Main Bus Current 4 IntegerTBD Over-voltage set-up 4 IntegerTBD Over-current set-up 4 IntegerTBD Battery voltage 4 IntegerTBD Battery current 4 IntegerTBD Battery temperature 1 4 IntegerTBD Battery temperature 2 4 IntegerTBD Separation switch 1 status 1 IntegerTBD Separation switch 2 status 1 IntegerTBD Reconfiguration module switch status 1 IntegerTBD Thermistor 1 monitoring 4 IntegerTBD Thermistor 2 monitoring 4 Integer




0 TBD1 Integer

TBD Local disk capacity 1 Integer


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 71/119

0 Not OK (full)1 OK (not full)

TBD Safety Loop Status0 Disable1 Enable

1 Integer


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 72/119

4.6.3.6 RM BATSIM SCOE Definition


Periodic RM (3,25)




1 Integer


1 Integer


1 Integer


1 Integer

TBD Battery simulation mode0 nominal mode (sun presence)1 discharge mode (eclipse)2 charge mode (sun presence after eclipse)3 Taper charge

1 Integer

TBD Battery simulator voltage 4 IntegerTBD Battery simulator current 4 IntegerTBD Battery temperature 1 4 IntegerTBD Battery temperature 2 4 IntegerTBD Over-voltage set-up 4 IntegerTBD Over-current set-up 4 IntegerTBD Dynamic load voltage value 4 IntegerTBD Dynamic load current value 4 Integer




0 TBD1 Integer


1 Integer


1 Integer


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 73/119

4.6.3.7 RM SAS SCOE Definition


Periodic RM (3,25)




1 Integer


1 Integer


1 Integer


1 Integer

TBD Battery simulation mode0 nominal mode (sun presence)1 discharge mode (eclipse)2 charge mode (sun presence after eclipse)3 Taper charge

1 Integer

TBD Power supply 1 status0 Off-line1 On-line

1 Integer

TBD Power supplies 2 to 29 status IntegerTBD Power supply 30 status

0 Off-line1 On-line

1 Integer

TBD Output Voltage of power supply 1 4 IntegerTBD Output Voltage of power supplies 2 to 29 IntegerTBD Output Voltage of power supply 30 4 IntegerTBD Output Current of power supply 1 4 IntegerTBD Output Current of power supplies 2 to 29 IntegerTBD Output Current of power supply 30 4 IntegerTBD Over-voltage set-up 4 IntegerTBD Over-current set-up 4 Integer


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 74/119




0 TBD1 Integer


1 Integer


1 Integer

4.6.3.8 RM BCE SCOE Definition

[IFRQT-0630] N/A (no interface with CCS) [Test]


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 75/119

4.6.3.9 RM LAUNCH POWER SUPPLY Definition


Periodic RM (3,25)




1 Integer


1 Integer


1 Integer


1 Integer


1 Integer

TBD Main Bus Voltage 4 IntegerTBD Main Bus Current 4 IntegerTBD Over-voltage set-up 4 IntegerTBD Over-current set-up 4 IntegerTBD Battery voltage 4 IntegerTBD Battery current 4 IntegerTBD Battery temperature 1 4 IntegerTBD Battery temperature 2 4 IntegerTBD Reconfiguration module switch status 1 IntegerTBD Thermistor 1 monitoring 4 IntegerTBD Thermistor 2 monitoring 4 IntegerTBD Battery charger voltage 4 IntegerTBD Battery charger current 4 IntegerTBD Battery charger temperature 1 4 IntegerTBD Battery charger temperature 2 4 IntegerTBD Over-voltage set-up 4 IntegerTBD Over-current set-up 4 IntegerTBD Dynamic load voltage value 4 IntegerTBD Dynamic load current value 4 Integer



REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 76/119



0 TBD1 Integer


1 Integer

4.6.3.10 RM SIS SCOE Definition

[IFRQT-0650] [Test]

Deleted


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 77/119

4.6.3.11 RM PLM SCOE Definition


Periodic RM (3,25)




1 Integer


1 Integer


1 Integer


1 Integer


1 Integer

TBD Main Bus Voltage 4 IntegerTBD Main Bus Current 4 IntegerTBD Over-voltage set-up 4 IntegerTBD Over-current set-up 4 IntegerTBD LCL 1 Current set-up 4 IntegerTBD LCL 2 Current set-up 4 IntegerTBD LCL 3 Current set-up 4 IntegerTBD LCL 4 Current set-up 4 Integer




0 TBD1 Integer


1 Integer


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 78/119

4.6.3.12 RM Herschel Cryo SCOE Definition


Periodic RM (3,25)




1 Integer


1 Integer


1 Integer


1 Integer

TBD Main Bus Voltage 4 IntegerTBD Main Bus Current 4 IntegerTBD Over-voltage set-up 4 IntegerTBD Over-current set-up 4 IntegerTBD Temperature 1 C100 monitoring 4 IntegerTBD Temperature 2 C100 monitoring 4 IntegerTBD Temperature 1 Pt1000 monitoring 4 IntegerTBD Temperature 2 Pt1000 monitoring 4 IntegerTBD Pressure monitoring 4 IntegerTBD Liquid level 1 monitoring 4 IntegerTBD Liquid level 2 monitoring 4 IntegerTBD Valve 1 status monitoring 4 IntegerTBD Valve 2 status monitoring 4 IntegerTBD Valve 3 status monitoring 4 IntegerTBD Valve 4 status monitoring 4 IntegerTBD Heater status monitoring 4 IntegerTBD CVSE 1 Monitoring 4 IntegerTBD CVSE 2 to 11 Monitoring IntegerTBD CVSE 12 Monitoring 4 Integer

…


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 79/119




0 TBD1 Integer


1 Integer


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 80/119

4.6.3.13 RM Planck PLM SCOE Definition


4.6.3.14 RM Planck Sorption SCOE Definition


4.6.3.15 RM CDMU DFE Definition


Periodic RM (3,25)




1 Integer


1 Integer


1 Integer


1 Integer


1 Integer

TBD RT address simulated 4 IntegerTBD 1553 profile trapped 4 IntegerTBD Analogue input lines monitoring 4 Integer

…

TBD Thermistors input lines monitoring 4 Integer…

TBD Cryo temperature input lines monitoring 4 Integer…

TBD Digital relay status 4 Integer…

TBD Digital Bi-level status 4 Integer


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 81/119

…

TBD Status Line acquisition 4 Integer…

TBD Digital serial acquisition 4 Integer…




0 TBD1 Integer


1 Integer


1 Integer


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 82/119

4.6.3.16 RM 1553 Bus Probe Definition

[IFRQT-0710] [Test]

Definition integrated in CDMU DFE and CDMU SCOE RM definition

4.6.3.17 RM Quick Load I/F Definition

[IFRQT-0720] To Be Completed [Test]TBD

4.6.4 COMMUNICATION VIA IS LAN

4.6.4.1 RM Instrument Stimuli SCOE Definition


4.6.4.2 RM HFI EGSE Definition

[IFRQT-0740] Deleted [Test]TBD

4.6.4.3 RM LFI EGSE Definition

[IFRQT-0750] Deleted [Test]TBD

4.6.4.4 RM HCSS SCOE Definition


4.6.4.5 RM HIFI EGSE Definition



REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 83/119

4.6.4.6 RM PACS EGSE Definition


4.6.4.7 RM SPIRE EGSE Definition


4.6.5 COMMUNICATION VIA www LAN

4.6.5.1 RM www.Server Definition



REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 84/119

4.7 MONITORING FLOW – Acknowledge Message Packets (ACKRC)

Source SCOE/DFEDestination CCSRate Non periodic

SCOE/DFE LANLANIS LAN


Each SCOE/DFE shall send back to CCS an Acknowledgement message each time theSCOE/DFE received a Remote Command


Depend on the Acknowledge field in the data filed header of the RC, the SCOE shall send theAcknowledge Message to notify acceptance and execution of this command (start of execution,and completion of execution)


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 85/119

4.7.1 Remote Command Acceptance report – Success (1,1)


For all RC received by a SCOE, a Command Acceptance Report shall be generated immediatelywith the following format in case of acceptance :

PIPEstructure







Source data NonePacket error control 2 bytes Not Used integer


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 86/119

4.7.2 Remote Command Acceptance report – Failure (1,2)


For all RC received by a SCOE, a Command Acceptance Report shall be generated immediatelywith the following format in case of rejection :

PIPEstructure





Spare 4 bits forced to ‘0000’ binaryPacket type 1 byte Forced to 0x01 binary

Packet sub-type 1 byte Forced to 0x02 binaryTime 48 bits Packet sending time CUC

Source dataRC Packet Command ID 2 bytes APID of the RC received integerPacket Sequence Control 2 bytes Packet Sequence Control of RC integer

Failure code * 2 bytes Reason for failure of acceptance integerParameters ** variable Optional variable

Packet error control 2 bytes Not Used integer

*Failure code Signification

0 Illegal APID1 Incomplete or invalid length packet2 Incorrect checksum3 Illegal packet Type4 Illegal packet Subtype5 Illegal or inconsistent Application Data

16 to 255 Application specific failure of acceptance

** Parameters :


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 87/119

For the standard reasons above the illegal or incorrect parameter shall be reported.For application-specific command rejections the parameter field is to be defined by users andprovides complementary information relating to the particular value of the Failure-Code field.

In all cases the code field plus the parameter field shall have a length corresponding to oneor several 16-bit words. The maximum length for the code plus parameter fields shallnot exceed 40 octets, for a total length of the ACKRC packet message of less than 64octets.


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 88/119

4.7.3 Remote Command Execution Report - Started (1, 3)


If needed, the format of the Command Execution Report shall be as follow :

PIPEstructure










REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 89/119

4.7.4 Remote Command Execution report – Progress (1,5)


If needed, the format of the Command Execution Report shall be as follow.Note : this service is only used in case the execution of a RC consists of a significant number ofsub-steps and the overall execution takes several tens of second or more.

PIPEstructure








Step number 2 bytes Step Number of RC execution integerPacket error control 2 bytes Not Used integer


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 90/119

4.7.5 Remote Command Execution Report - Completed (1, 7)


If needed, the format of the Command Execution Report shall be as follow :

PIPEstructure










REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 91/119

4.7.6 Remote Command Execution report – Failure (1,8)


For all RC received by a SCOE, a Command Acceptance Report shall be generated immediatelywith the following format in case of rejection :

PIPEstructure








Failure code * 2 bytes Reason for failure of execution integerParameters ** variable Optional variable



TBD TBD

** Parameters :


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 92/119

For the standard reasons above the illegal or incorrect parameter shall be reported.For application-specific command rejections the parameter field is to be defined by users andprovides complementary information relating to the particular value of the Failure-Code field.



REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 93/119

4.8 MONITORING FLOW – Acknowledge Message for TC (ACKTC)

Source TM/TC DFEDestination CCSRate Non periodic

SCOE/DFE LANLAN

[IFRQT-0808-1]

[Analysis]

TM/TC DFE shall send back to CCS an Acknowledgement message each time the TM/TC DFEreceived a TC


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 94/119

4.8.1 Telecommand Acceptance report – Success (1,1)

[IFRQT-0808-2]

[Analysis]

For all TC received by a TM/TC DFE, a Command Acceptance Report shall be generatedimmediately with the following format in case of acceptance :

PIPEstructure



Version number 3 bits forced to ‘000‘ binaryType 1 bit forced to ‘0‘ binaryData field header flag 1 bit forced to ‘1‘ binaryApplication process ID 11 bits @ TM/TC DFE integerSegmentation flags 2 bits forced to ‘11‘ binarySource sequence count 14 bits Packet count per APID binaryPacket length 2 bytes length of packet data field Integer






REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 95/119

4.8.2 Telecommand Acceptance report – Failure (1,2)

[IFRQT-0808-3]

[Analysis]

For all TC received by a TM/TC DFE, a Command Acceptance Report shall be generatedimmediately with the following format in case of rejection :

PIPEstructure







Source dataRC Packet Command ID 2 bytes APID of the TC received integerPacket Sequence Control 2 bytes Packet Sequence Control of RC integer

Failure code * 2 bytes Reason for failure of acceptance integerParameters ** variable Optional variable



0 Illegal APID1 Incomplete or invalid length packet2 Incorrect checksum3 Illegal packet Type4 Illegal packet Subtype5 Illegal or inconsistent Application Data

16 to 255 Application specific failure of acceptance


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 96/119

** Parameters :For the standard reasons above the illegal or incorrect parameter shall be reported.For application-specific command rejections the parameter field is to be defined by users andprovides complementary information relating to the particular value of the Failure-Code field.



REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 97/119

4.9 MONITORING FLOW – TC Echo

Source TM/TC DFE CCSDestination CCS

NDIUIS station

Rate Non periodic Non periodicSCOE/DFE LAN IS LANLANNDIU LAN


Upon reception of a Telecommand request issued by the CCS itself and when the TC requestremotely come from the NDIU. TM/TC DFE shall deliver the TC Echo packet with the followingformat :

PIPEstructure


Message ID 1 byte Forced to 0xA0 integerVCID 1 byte Forced to 0x00 integerRemaining length 2 bytes Variable integer

Header Request ID 4 bytes Forced to 0x00000000 integerSynchronisation Word 2 bytes Forced to 0xFADE integer

Body TC Packet variable variable

Note: the same TC Echo will be sent from 0 to n times depending on TC execution.


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 98/119

4.10 MONITORING FLOW – TC Report

Source TM/TC DFEDestination CCS

NDIURate Non periodic

SCOE/DFE LANLANNDIU LAN

[IFRQT-0809-1]

[Analysis]

Upon reception of a Telecommand request issued by the CCS itself and when the TC requestremotely come from the NDIU, TM/TC DFE shall deliver the TC Report packet according to itscurrent mode :1. If TM/TC DFE in AD mode : TC Report shall be sent after CLCW check. (this means On-board

TC acceptance)2. If TM/TC DFE in BD mode, TC Report shall be sent just after TC Echo packet. (this means DFE

acceptance)

PIPEstructure







Source dataRequest ID 4 bytes To be filled by TM/TC DFE integer



REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 99/119

4.11 MONITORING FLOW – RM Alive Packet

Source SCOE/DFE/ISDestination CCSRate 1 packet/60 seconds for all SCOE/DFE/IS

SCOE/DFE LANLAN

[IFRQT-0809-2]

[Analysis]

Each SCOE/DFE/IS shall sent to the CCS one RM “Alive Packet” every 60 seconds with thefollowing format :

PIPEstructure








4.12 INTERFACES REQUIREMENTS


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 100/119

4.12.1 GENERIC INTERFACE NAME

IP address (xxx.xxx.xxx.xxx)

IPName

ALCATELxxx.xxx.xxx.

ALENIAxxx.xxx.xxx

ASTRIUMxxx.xxx.xxx

IPName

ALCATELxxx.xxx.xxx

ALENIAxxx.xxx.xxx

ASTRIUMxxx.xxx.xxx

IPName

ALCATExxx.xxx.xxx

L

ALENIAxxx.xxx.xxx

ASTRIUMxxx.xxx.xxx

EGSE APID2016

to2046

SCOE/DFE LAN IS LAN NDIU LANCCS 2016 TBD TBD TBD TBD TBD TBD TBD TBD

CDMU SCOE 2017 TBD TBD TBD TBDACMS SCOE 2018 TBD TBD TBD TBDTT&C SCOE 2019 TBD TBD TBD TBDTM/TC DFE 2020 TBD TBD TBD TBD TBD TBD TBD TBDUmbilical IF

module 2021 TBD TBD TBD TBD

SAS 2022 TBD TBD TBD TBDBATSIM 2023 TBD TBD TBD TBD

BCELPS 2024 TBD TBD TBD TBD

PLM SCOE 2025 TBD TBD TBD TBDH CRYO SCOE 2026 TBD TBD TBD

CDMU DFE 2028 TBD TBD TBD TBDQuick Load 2029 TBD TBD TBD TBD

NDIU 2030 TBD TBD TBD TBDwww server TBD TBD TBD TBD

HFI EGSE 2040 TBD TBD TBDLFI EGSE 2041 TBD TBD TBDHIFI EGSE 2042 TBD TBD TBD

PACS EGSE 2043 TBD TBD TBDSPIRE EGSE 2044 TBD TBD TBD

Table 3 : Generic Interface Name


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 101/119

4.12.2 DATABASE


The sub-contractor responsible of each SCOE/DFE shall be in charge to provide all theinformation needed to define inside HPSDB all parameters constituting RM packets andRC Packets.


The files that will be used to populate the HPSDB with SCOE/DFE parameters shall havethe following format (TBD) and shall be compatible with HPSDB [AD2](They will be used to update HPSDB)

4.12.3 DATE/TIME


The date/time synchronisation between all EGSE’s item shall be done by using standardservice providing by NTP (Network Time Protocol)

[IFRQT-0840] [Test]

In this case, CCS shall be the master and all EGSE’s item shall update and synchronisetheir local clock.

4.12.4 Quick loading function


TBW

4.12.5 Interface TM/TC DFE↔↔↔↔ NDIU

[IFRQT-0860] [Analysis]Two interfaces shall be provided compatible with the ESA provided Network Data InterconnectUnit (NDIU) for TM (frame) and TC (CLTU) interface between the satellites and the MissionOperation Centre (MOC).Refer to [AD4]


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page :02/ 9

4.12.6 Interface Instrument Stimuli SCOE ↔↔↔↔ Herschel Satellite


TBD

4.12.7 Interface Instrument Stimuli SCOE ↔↔↔↔ Planck Satellite

[IFRQT-0880] Deleted [Analysis]

4.12.8 Performance

[IFRQT-0882] [Analysis]The interface for the Telemetry packets delivery from the TM/TC DFE to the CCS shall supportthe maximum data rate of 150 Kbps (TBC) plus overhead for message header/trailer.

[IFRQT-0884] [Analysis]The interface for the Telecommand packets delivery from the CCS to the TM/TC DFE shallsupport the maximum data rate of 4Kbps plus overhead for message header/trailer.

[IFRQT-0886] [Analysis]The interface for the Telemetry packets delivery from the CCS to the Instrument Stations shallsupport the maximum data rate of up to 150 Kbps for each connected Instrument Station plusoverhead for message header/trailer.

4.12.9 File transfer

[IFRQT-0887] [Analysis]All SCOE/DFE having a controller shall support NFS (Network File System) and/or FTP (FileTransfer Protocol) to allow direct access from the CCS into the hard disk of the controller forfile transfer purposes.


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02


4.12.10 Naming Convention Rules for EGSE items

The aim of this paragraph is to fix the naming rules of all commands and parametersnecessary to fulfil the communication between EGSE items


TBD

4.12.11 OBSM Files


OBSM Files Format is define in [RD13] document (SCOS-2000 OBSM External InterfacesControl Document)


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02


5 EGSE EXTERNAL INTERFACE REQUIREMENTS TBW

This chapter will define all electrical Harness Interfaces between EGSE and SVM / PLM / S/C,and between all EGSE’s item in all the different configurations.



REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 105/119

Table below resumes all the H/P EGSE interfaces :

Internal Interface(communication protocol)

External Interface (Hardware)

EGSE NDIU Lite CCS EGSE S/CSCOE/DFE LAN

NDIULAN

www LAN CCS SCOE

(RC)SCOE CCS

(RM)

ISLAN TM/TC DFE NDIU Herschel Planck

Planck IS HFI IS EGSELFI IS EGSE

HCSS IS EGSE 4.6.4.4 (RM)Herschel ISHIFI IS EGSE 4.6.4.5 (RM)PACS IS EGSE 4.6.4.6 (RM)SPIRE IS EGSE 4.6.4.7 (RM)

Instr StimSCOE

Instr Stim 4.6.4.1 (RM) 5.1.10

TM/TC DFE* AD 4 4.3.1.54.2 (TC)

4.6.3.44.4 (TM)

5.1.4

TT&C SCOE RF 4.3.1.4 4.6.3.3 5.1.4 5.1.3 5.1.3

TT&C

* same unitTM/TC DFE* 4.3.1.5

4.2 (TC)4.6.3.44.4 (TM)

CDMU SCOE 4.3.1.2 4.6.3.1 5.1.1 5.1.1CDMU SCOECDMU QuickLoad

4.3.1.18 4.6.3.17 5.1.1.1 5.1.1.1

ACMS SCOE ACMS SCOE 4.3.1.3 4.6.3.2 5.1.2 5.1.2Optical Stim 4.3.1.3.2 4.6.3.2.2 5.1.2.1 5.1.2.1Stim Feedbk 4.3.1.3.3 4.6.3.2.3 5.1.2.2 5.1.2.2

Power SCOE Umbilical I/F 4.3.1.6 4.6.3.5 5.1.4 5.1.5 5.1.5Battery Sim 4.3.1.7 4.6.3.6 5.1.6 5.1.6SA Sim 4.3.1.8 4.6.3.7 5.1.7 5.1.7BCE SCOE 4.3.1.9 4.6.3.8 5.1.8 5.1.8


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 106/119

Internal Interface(communication protocol)

External Interface (Hardware)

EGSE NDIU Lite CCS EGSE S/CSCOE/DFE LAN

NDIULAN

www LAN CCS SCOE

(RC)SCOE CCS

(RM)

ISLAN TM/TC DFE NDIU Herschel

PlanckPlanck

LPS 4.3.1.10 4.6.3.9 5.1.4 5.1.9 5.1.9PLM PLM SCOE 5.1.10 5.1.10Herschel H-Cryo SCOE 4.3.1.13 4.6.3.12 5.1.11

CDMU DFE 4.3.1.16 4.6.3.15 5.1.12 5.1.12MIL 1553B1553 Bus prob 4.3.1.17 4.6.3.16 5.1.13 5.1.13

Table 4 : H/P EGSE Interfaces


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 107/119

5.1 EGSE to S/C INTERFACES

5.1.1 CDMU SCOE

5.1.1.1 Quick SW Loading I/F


CDMU SCOE shall interface with SVM for quick loading of the EEPROM of both CDMUProcessor Modules with the electrical characteristics according to TBD

5.1.1.2 MIL-STD-1553B I/F


Refer to [AD7] §6.8.3

5.1.1.3 Time pulse


Refer to [AD7] §6.8.1.4

5.1.2 ACMS SCOE

5.1.2.1 Optical Stimuli Commands


TBD

5.1.2.2 Stimuli Feedback Commands


TBD


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 108/119

5.1.3 TT&C SCOE RF


TT&C SCOE shall interface with SVM with the electrical characteristics according to TBD

5.1.4 POWER SCOE


Power SCOE (Umbilical I/F part) shall interface with the SVM for :

5.1.4.1 Power System I/F

Refer to [AD7] §6.7

5.1.4.2 PCDU I/F

Parameter Herschel/Planck Limit(at SVM interface)Battery support eclipse - 0 to 28 Volts

- 0 to 25 Amps- PCDU to provide protection from external s/c or supply reversal

Power bus Support inSunlight Mode

- 0 to 31 Volts- 0 to 60 Amps- PCDU to provide protection from external s/c or supply reversal

Battery monitor lines - 2 voltage monitor lines 0 to 28 volts and 2 returns- 100κΩ line protection resistors in series with the positive lines.

Bus monitor lines - 2 voltage monitor lines 0 to 28 volts and 2 returns- 100κΩ line protection resistors in series with the positive lines.

5.1.4.3 Telecommand I/F


2 TC interfaces shall be provided with the electrical characteristics according to [AD7]§6.8.1.4


Each TC Interface shall comprise the following signals :

• TC Clock : Telecommand Clock signal input

• TC Data : Telecommand Data signal input

• TC Active : Telecommand Quality signal input


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 109/119

5.1.4.4 Telemetry I/F


2 TM interfaces shall be provided with the electrical characteristics according to [AD7]§6.8.1.4


Each TM Interface shall comprise the following signals :

• TM Clock : Telemetry Clock signal output

• TM Data : Telemetry Data signal output

5.1.5 BATSIM SCOE


BATSIM SCOE shall interface with the SVM with the following electrical characteristics :

Parameter Herschel/Planck LimitMinimum EOD voltage Veodmin 15 (V)Nominal EOD voltage Veod 18 (V)Nominal EOC voltage Veoc 25.2 (V)Maximum EOC voltage Veocmax 27.7 (V) (tbc)Maximum harness voltage drop outside the PCDU,based on GDIR 1% requirement applied at EOD

0.15

Maximum harness voltage drop, based ondischarge criteria and a charge rate of 6 Amps

0.06 (V)

The maximum allowable transient current drawn bythe PCDU, under any conditions, shall not exceed

120(A) (1 ms max)35 (A) (1 minute max)

5.1.6 SAS SCOE


SAS SCOE shall interface with the SVM with the following electrical characteristics :

Positive array connection - 0 to 60 Volts (section open circuit voltage)- 0 to 3 A D.C. Max. BOL, 2A Max. EOL. (for analysispurpose a nominal section current in sunlight can beassumed to be 2 to 3A).- Redundant connector pins to guard against opencircuit failure.

Negative array connection - 0 volts (reference ground is the power bus capacitor).- Redundant connector pins to guard against opencircuit failure.

Section Capacitance Cp (mF) max 5 (tbc)


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 110/119

Section Inductance Ls (mH) max 10Section Inductance Ls (mH) min 1Effective Series Resistance Rs (W) 0.09 (tbc)Effective Parallel Resistance Rp (W) 203 (tbc)

5.1.7 BCE SCOE


BCE SCOE shall interface with the SVM with the following electrical characteristics :

Parameter Herschel/Planck LimitMinimum EOD voltage Veodmin 15 (V)Nominal EOD voltage Veod 18 (V)Nominal EOC voltage Veoc 25.2 (V)Maximum EOC voltage Veocmax 27.7 (V) (tbc)Maximum harness voltage drop outside the PCDU,based on GDIR 1% requirement applied at EOD

0.15

Maximum harness voltage drop, based ondischarge criteria and a charge rate of 6 Amps

0.06 (V)

The maximum allowable transient current drawn bythe PCDU, under any conditions, shall not exceed

120(A) (1 ms max)35 (A) (1 minute max)


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 111/119

5.1.8 COTE (Launch configuration)


COTE SCOE shall interface with the SVM with the following electrical characteristics :

5.1.8.1 Power System I/F

Refer to [AD7] §6.7

5.1.8.2 PCDU I/F

Parameter Herschel/Planck Limit(at SVM interface)Battery support eclipse - 0 to 28 Volts

- 0 to 25 Amps- PCDU to provide protection from external s/c or supply reversal

Power bus Support inSunlight Mode

- 0 to 31 Volts- 0 to 60 Amps- PCDU to provide protection from external s/c or supply reversal

Battery monitor lines - 2 voltage monitor lines 0 to 28 volts and 2 returns- 100κΩ line protection resistors in series with the positive lines.

Bus monitor lines - 2 voltage monitor lines 0 to 28 volts and 2 returns- 100κΩ line protection resistors in series with the positive lines.

5.1.8.3 Telecommand I/F


2 TC interfaces shall be provided with the electrical characteristics according to [AD7]§6.8.1.4


Each TC Interface shall comprise the following signals :

• TC Clock : Telecommand Clock signal input

• TC Data : Telecommand Data signal input

• TC Active : Telecommand Quality signal input

5.1.8.4 Telemetry I/F


2 TM interfaces shall be provided with the electrical characteristics according to [AD7]§6.8.1.4



REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 112/119

Each TM Interface shall comprise the following signals :

• TM Clock : Telemetry Clock signal output

• TM Data : Telemetry Data signal output

5.1.9 HERSCHEL Stimuli Instrument SCOE


TBD

5.1.10 PLM SCOE


TBD

5.1.11 Herschel Cryo SCOE


TBD

5.1.12 CDMU DFE

5.1.12.1 Internal Commands I/F



5.1.12.2 Internal Telemetry I/F



5.1.13 1553 Bus Probe



REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 113/119

TBD

5.2 EGSE to EGSE INTERFACES

5.2.1 TM/TC Interface


TM/TC DFE shall interface with Power SCOE (Umbilical I/F part) with the electricalcharacteristics according to [AD7] § 6.8.1.4


TM/TC DFE shall interface with TT&C SCOE RF with the electrical characteristicsaccording to [AD7] § 6.8.1.4


TM/TC DFE shall interface with NDIU with the electrical characteristics according to [AD7]§ 6.8.1.4

5.2.2 Launch Power Supply Interface


LPS (Umbilical I/F part) shall interface with CRYO SCOE with the electrical characteristicsaccording to [RD12] § 4.4.2.2


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 114/119

5.2.3 SAFETY LOOP


Safety Loop signal shall link together Power SCOE (Umbilical part), SAS SCOE andBATSIM SCOE with the electrical characteristics according to [AD5]

S/C

POWER SCOE

PCDU

Clear

Voltageref.

Comp. ReactionTime logic

(1 ms)

Driver

Safety loop module SAS(switch OFF Power Supply)

Switch OFFPowerSupply

Safety loop module BATSIM(switch OFF Power Supply)

V Bus

Umbilicalconnector

Figure 9 : SAFETY LOOP overview


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 115/119

6 VERIFICATION MATRIX

6.1 GENERAL REQUIREMENTS

The acceptance tests of the EGSE shall be distributed in 3 acceptance test levels:

- Level 1 acceptance test at equipment level.

- Level 2 acceptance test of system EGSE level.

- Level 3 acceptance test of H/P EGSE.

Requirement Test level 1 Test level 2 Test level 3IFRQT-0010 X XIFRQT-0020 X XIFRQT-0030 X XIFRQT-0040 X XIFRQT-0042 X XIFRQT-0045 X XIFRQT-0050 X XIFRQT-0060IFRQT-0070 X XIFRQT-0080 X XIFRQT-0090IFRQT-0100 X XIFRQT-0102 X XIFRQT-0103 X XIFRQT-0104 X XIFRQT-0110 X XIFRQT-0120 X XIFRQT-0130 X XIFRQT-0140 X XIFRQT-0150 X XIFRQT-0160 X XIFRQT-0170 X XIFRQT-0180 X XIFRQT-0190 X XIFRQT-0200 X XIFRQT-0210 X XIFRQT-0220 X XIFRQT-0230 X XIFRQT-0240 X XIFRQT-0245 X XIFRQT-0250 X XIFRQT-0260 X XIFRQT-0270 X XIFRQT-0280 X XIFRQT-0290 X X


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 116/119

IFRQT-0300 X XIFRQT-0310 X XIFRQT-0320 X XIFRQT-0330IFRQT-0340 X XIFRQT-0350IFRQT-0360 X XIFRQT-0370 X XIFRQT-0380IFRQT-0390IFRQT-0400 X XIFRQT-0405IFRQT-0410 X XIFRQT-0411 X XIFRQT-0420IFRQT-0430IFRQT-0440IFRQT-0450IFRQT-0460IFRQT-0470IFRQT-0480IFRQT-0490IFRQT-0500 X XIFRQT-0510 X XIFRQT-0520 X XIFRQT-0525 X XIFRQT-0530 X XIFRQT-0535 X XIFRQT-0540 X XIFRQT-0550 X XIFRQT-0560 X XIFRQT-0565 X XIFRQT-0570 X XIFRQT-0580 X XIFRQT-0590 X XIFRQT-0600 X XIFRQT-0610 X XIFRQT-0620 X XIFRQT-0630IFRQT-0640 X XIFRQT-0650IFRQT-0660 X XIFRQT-0670 X XIFRQT-0680IFRQT-0690IFRQT-0700 X XIFRQT-0710 X XIFRQT-0720 X XIFRQT-0730IFRQT-0740IFRQT-0750IFRQT-0760 X X


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 117/119

IFRQT-0770 X XIFRQT-0780 X XIFRQT-0790 X XIFRQT-0800IFRQT-0801 X XIFRQT-0802 X XIFRQT-0803 X XIFRQT-0804 X XIFRQT-0805 X XIFRQT-0806 X XIFRQT-0807 X XIFRQT-0808 X XIFRQT-0808-1 X XIFRQT-0808-2 X XIFRQT-0808-3 X XIFRQT-0809 X XIFRQT-0809-1 X XIFRQT-0809-2 X XIFRQT-0810 X XIFRQT-0820 X XIFRQT-0830 X XIFRQT-0840 X XIFRQT-0850 X XIFRQT-0860 X XIFRQT-0870 X XIFRQT-0880IFRQT-0882 X XIFRQT-0884 X XIFRQT-0886 X XIFRQT-0887 X XIFRQT-0888 X XIFRQT-0889 X XIFRQT-0890 X XIFRQT-0900 X XIFRQT-0910 X XIFRQT-0915 X XIFRQT-0920 X XIFRQT-0930 X XIFRQT-0940 X XIFRQT-0950 X XIFRQT-0960 X XIFRQT-0970 X XIFRQT-0980 X XIFRQT-0990 X XIFRQT-1000 X XIFRQT-1010 X XIFRQT-1020 X XIFRQT-1030 X XIFRQT-1040 X XIFRQT-1050 X XIFRQT-1060 X XIFRQT-1070 X X


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 118/119

IFRQT-1080 X XIFRQT-1090 X XIFRQT-1100 X XIFRQT-1110 X XIFRQT-1120 X XIFRQT-1130 X XIFRQT-1140 X XIFRQT-1150 X XIFRQT-1160 X XIFRQT-1170 X XIFRQT-1180 X XIFRQT-1190 X X


REFERENCE :

DATE :

H-P-1-ASPI-IS-0121

18/June/02

ISSUE : 03 Page : 119/119

FIN DE DOCUMENTEND OF DOCUMENT