System Interface (CGS ICD) - Astrium ST Service Portal

Space Infrasctructure
Titel:
Title:
Dokument Nr.:
Document No.:
Ausgabe Nr.:
Issue No.:
Überarbeitung:
Revision:
Klassifikations Nr.:
Class. Prod. Code:
Ausgabedatum:
Issue Date:
Überarbeitungsdatum:
Revision Date:
Liste der zu liefernden Dokumente/Dok.–Anforderungs–Beschreibung(LLD/DAB):
Document Requirements List / Doc. Requirements Description (DRL/DRD):
Bearbeitet:
Prepared by:
Geprüft:
Agreed by:
Projektmanager
Project Manager
CGS Interface Control Document
– for CGS V4.3.0 –
COL–RIBRE–ICD–0025–00
4
B
Firma:
Company:
CGS Engineering astrium–si
Firma:
Company:
P. Athmann astrium–si
J.Frank, astrium–si
Vertrags–Nr.:
Contract–No.:
8–QA
17/04/98
31/08/00
3.704
Projektmanager
Project Manager
astrium – All Rights Reserved – Copyright per DIN 34

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
DOCUMENT CHANGE RECORD
Issue/Rev. Issue date Pages/Section Remarks
Affected
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
i von/of: xii
1/– 22/03/96 all First issue of this ICD for CGS V2.2 and
V3.0.
2/– 24/03/97 all Update for CGS V3.1.3:
Incorporation of CGS V3.1.2/V3.1.3 IRNs
3/– 04/08/97 all Update for CGS V4.1:
Incorporation of CGS V3.1.3 / V3.2 / V4.0
/ V4.1 IRNs
4/– 17/04/98 all Update for CGS V4.1:
Incorporation of CGS V3.1.3 / V4.0 / V4.1
IRNs
4/A 31/03/99 all Update for CGS V4.2.0:
Incorporation of CGS V4.1/V4.2.0 IRNs
Update Applicable Documentation
astrium – All Rights Reserved – Copyright per DIN 34

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
Issue/Rev. Issue date Pages/Section Remarks
Affected
4/B 31/08/00 Update for CGS V4.3:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
ii von/of: xii
2 Update Applicable Documentation
4.1 Remove Ch 4.1 (Communication Services)
(double entry)
4.6.5 Update File Information for Error Services
Incorporation of following IRNs
7.8.1 COL–RIBRE–IRN–CGS–8003c
UCL System Library Extensions/Updates
7.8.2 COL–RIBRE–IRN–CGS–8011b
UCL Ground_Command_to_onboard modifications
6.10.3.1 COL–RIBRE–IRN–CGS–8050
Deletion of optional
7.6.5 COL–RIBRE–IRN–CGS–8051
750 Measurments in ADU: ADTs
7.8 COL–RIBRE–IRN–CGS–8057
New HK Values
7.11 COL–RIBRE–IRN–CGS–8059
DBS_DEFINITIONS
7.13 COL–RIBRE–IRN–CGS–8060
TEV_DEFINITIONS:SID/pathname list
7.14 COL–RIBRE–IRN–CGS–8061
ADT_PACKET_RESULT: SID/pathname list
7.3.5 COL–RIBRE–IRN–CGS–8069
ADT_BINARY_BUFFER:Param. length check
7.17 COL–RIBRE–IRN–CGS–8075
CSS merge with DMS–R prototype
7.11,7.13 COL–RIBRE–IRN–CGS–8078a
DBS_,TEV_DEFINIT,ADT_EVENT_RESULT
7.3.4 COL–RIBRE–IRN–CGS–8064
ADT_CCSDS_P.: Access to CCSDS Header
7.6.5 COL–RIBRE–IRN–CGS–8065
ADT_ADU_DESCR.: Access to CCSDS Header
4.6, 4.8, 4.3.3 COL–RIBRE–IRN–CGS–8068a
Commercial Baseline: Ada/DV/Oracle Patch
7.6.5 COL–RIBRE–IRN–CGS–8070
ADT_ADU: Access to CCSDS Header
7.8.1 COL–RIBRE–IRN–CGS–8076
UCL System Library Extensions/Updates
6.1.2 COL–RIBRE–IRN–CGS–8079
MPS_DEFINITIONS:new e.i. types for derived values
4.7.3, 7.2 COL–RIBRE–IRN–CGS–8082
ERROR_SERVICES,VICOS_DEF.: convert msg types
7.6.7 COL–RIBRE–IRN–CGS–8085
ADT_GDU_DESCR: TC Verification
astrium – All Rights Reserved – Copyright per DIN 34

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
iii von/of: xii
new 4.7.6 COL–RIBRE–IRN–CGS–8089
CGSI: Installation Registry
4.3.2.2.1 COL–RIBRE–IRN–CGS–8090
CGSI: SORT_AREA_SIZE in init.ora
7.2 COL–RIBRE–IRN–CGS–8094
VICOS_DEFINITIONS: Add new Log Groups
7.7 COL–RIBRE–IRN–CGS–8096
TES_API : add SUSPEND_ADU
7.13, 7.14 COL–RIBRE–IRN–CGS–8099
TEV_API and tev_definitions_.a for merge tool
7.8.2 COL–RIBRE–IRN–CGS–8101a
Length Parameter in ISSUE_SW_COMMAND
7.10.1.2, 7.10.2.2 COL–RIBRE–IRN–CGS–8102
Byte Alignment in SW Commands
7.8 COL–RIBRE–IRN–CGS–8104
HK values for limit violations
7.11 COL–RIBRE–IRN–CGS–8106
DBS_DEFINITIONS, DBS_RPI
astrium – All Rights Reserved – Copyright per DIN 34

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
TABLE OF CONTENTS
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
iv von/of: xii
CHAPTER 1 :
INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
1.1 Identification and Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.2 Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.3 Reader Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
1.4 Type of Described Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
CHAPTER 2 :
APPLICABLE AND REFERENCE DOCUMENTS . . . . . . . . . . . . . . . . . . . . . . . 4
2.1 Applicable Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2.2 Reference Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
CHAPTER 3 :
GENERAL DESCRIPTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.1 CGS Functional Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
CHAPTER 4 :
INFRASTRUCTURE INTERFACES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.1 Operating System Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.1.1 Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.1.2 File System Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.1.2.1 Home Directories for CGS Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.1.2.1.1
4.1.2.1.1.1
4.1.2.1.1.2
4.1.2.1.1.3
Sun Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
GSAF Home Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CGS Home Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Product Home Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14
14
14
14
4.1.2.1.2 HP Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.1.2.2 Subdirectories for CGS Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.1.2.2.1 Start–Up Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.1.2.2.2 Executable Images (Platform dependent) . . . . . . . . . . . . . . . . . . . . . . 15
4.1.2.2.3 Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.1.2.2.4 Utilities and Tools (Platform dependent) . . . . . . . . . . . . . . . . . . . . . . .
15
astrium – All Rights Reserved – Copyright per DIN 34

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
v von/of: xii
4.1.2.2.5 Configuration Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.1.2.2.6 Runtime Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.1.2.2.7 Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.1.2.3 Special Checkout related Directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.1.2.3.1 Test Node Directory on the HP Test Nodes . . . . . . . . . . . . . . . . . . . . . 16
4.1.2.3.2 Test Node Directories on the SUN Database Server . . . . . . . . . . . . . . 17
4.1.2.4 Home Directories For CGS Extensions And Add–Ons . . . . . . . . . . . . . . . 17
4.1.2.4.1 Special Application Software (SAS) . . . . . . . . . . . . . . . . . . . . . . . . . . 17
4.1.2.4.2 Command And Measurement Adaptation Software (CMAS) . . . . . . . 18
4.1.2.4.3 Mission Database Support Software (MDB_SS) . . . . . . . . . . . . . . . . . 18
4.1.3 Common User Environment Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4.1.3.1 Central Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
4.1.3.1.1 Central ”login” Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
4.1.3.1.2 Central ”cshrc” Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
4.1.3.1.3 Central ”logout” Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
4.2 Relational Database Management System . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
4.2.1 Functional Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
4.2.1.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
4.2.2 Database Installation and Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
4.2.2.1 Predefined Object Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
4.2.2.1.1 User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
4.2.2.1.2 Tablespaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
4.2.2.1.3 Public Synonyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
4.2.2.1.4 CRT Device Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
4.2.2.2 ORACLE Configuration Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
4.2.2.2.1 INIT.ORA Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
4.2.2.2.2 Rollback Segments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
4.2.3 Commercial Product Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
4.3 Communication Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
4.3.1 Internet Port Number Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
4.3.2 Commercial Product Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
4.4 Presentation Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
4.5 DataViews Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
4.6 CGS Top Level User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
4.6.1 Error Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
4.6.1.1 Definition of Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
4.6.1.2 Provided Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
4.6.1.3 Reporting Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
4.6.1.4 Addressing the Error Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
39
astrium – All Rights Reserved – Copyright per DIN 34

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
vi von/of: xii
4.6.1.5 Displaying and Logging the Error Message . . . . . . . . . . . . . . . . . . . . . . . 39
4.6.1.6 Central Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
4.6.1.7 Supplying a Timestamp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
4.6.1.8 Supplying Extra Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
4.6.1.9 Error Message Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
4.6.1.10 Error Message Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
4.6.1.11 Handling of Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
4.6.2 Error Report Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
4.6.3 Error Services Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
4.6.4 Timestamp Services Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
4.6.5 File Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
4.6.5.1 File Names and Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
4.6.5.1.1 Session Error Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
4.6.5.1.2 Process Response Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
4.6.6 Installation Registry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
4.7 Other Commercial Products Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
4.8 CGS_Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
4.8.1 Informal Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
4.8.2 Formal Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
CHAPTER 5 :
SOFTWARE DEVELOPMENT INTERFACES . . . . . . . . . . . . . . . . . . . . . . . . . . 59
5.1 Documentation Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
5.1.1 Format of Imported Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
5.1.1.1 Interface Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
5.1.1.2 Interface Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
5.1.1.2.1 Document Location Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
5.1.1.2.2 Document Filename Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
5.1.1.2.3 Importable DOCUMENT Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
5.2 Generic Compiler Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
5.2.1 Generic C Compiler Environment Integration Interface . . . . . . . . . . . . . . . . . 63
5.2.2 Generic Ada Compiler Environment Integration Interface . . . . . . . . . . . . . . . 63
5.3 Generic Tool Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
CHAPTER 6 :
MISSION PREPARATION INTERFACES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
6.1 Package MPS_DEFINITIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
66
astrium – All Rights Reserved – Copyright per DIN 34

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
vii von/of: xii
6.1.1 Exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
6.1.1.1 Exceptions due to internal MDB / ORACLE errors . . . . . . . . . . . . . . . . . 66
6.1.1.2 SID_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
6.1.1.3 AUTHORIZATION_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
6.1.1.4 USE_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
6.1.1.5 ENVIRONMENT_ERROR , CDU/CCU_ERROR . . . . . . . . . . . . . . . . . . 66
6.1.1.6 PARAMETER_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
6.1.1.7 CONSISTENCY_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
6.1.2 Formal Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
6.2 MDB Standard Entities and Application Programmer Interface . . . . . . . . . . 85
6.3 CLS Global . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
6.3.1 General CLS Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
6.3.2 Runtime Representation of UCL Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
6.4 Flexible Tool Invocation Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
6.5 Foreign Key Support / PUI Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
6.6 MDB Batch Data Entry Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
6.7 I–Code Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
6.7.1 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
6.7.2 I–Code Record Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
6.7.3 I–Code Record Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
6.7.4 Architecture of the Stack Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
6.7.5 I–Code Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
6.7.5.1 Instruction Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
6.7.5.2 Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
6.7.5.3 Detailed I–code Instructions Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
6.7.5.3.1 Instructions with implied parameter . . . . . . . . . . . . . . . . . . . . . . . . . . 107
6.7.5.3.2 Load Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
6.7.5.3.3 Load Address Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
6.7.5.3.4 Store Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
6.7.5.3.5 MOVE and CAT Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
6.7.5.3.6 Stack Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
6.7.5.3.7 Numerical Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
6.7.5.3.8 Comparison Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
6.7.5.3.9 BOOLEAN negation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
6.7.5.3.10 Allocation Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
6.7.5.3.11 Jump Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
6.7.5.3.12 Special Jump Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
6.7.5.3.13 Iterative Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
143
astrium – All Rights Reserved – Copyright per DIN 34

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
viii von/of: xii
6.7.5.3.14 Switch Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
6.7.5.3.15 Procedure/Function Call Instructions . . . . . . . . . . . . . . . . . . . . . . . . . 146
6.7.5.3.16 Conversion Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
6.7.5.3.17 Miscellaneous Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
6.7.5.3.18 System Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
6.7.5.3.19 No–operation Instruction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
6.7.6 Sample AP and Corresponding I–Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
6.7.7 Procedural Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
6.8 Parameter Encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
6.8.1 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
6.8.2 Parameter Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
6.8.3 Encoding Scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
6.8.3.1 External Scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
6.8.3.2 Internal Scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
6.8.4 Example (Call of a library procedure) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
6.8.5 Stack Machine Representation of AP Parameters . . . . . . . . . . . . . . . . . . . . . . 173
6.9 Flight Synoptic Display Representation Format . . . . . . . . . . . . . . . . . . . . . . . . 174
6.10 FWDU Supported Sammi API Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
6.10.1 File Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
6.10.2 Logical Server Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
6.10.3 Commands to the On–Board System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
6.10.3.1 Software Commanding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
6.10.3.2 Pre–Defined Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
6.10.3.3 Window Association Information (WAF) . . . . . . . . . . . . . . . . . . . . . . . . . 178
6.10.4 FWDU Applied Type Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
6.10.4.1 Mapping between On–board and CGS standard end item types . . . . . . . . 180
6.10.4.2 Mapping between CGS standard end item types and Sammi data types . . 180
CHAPTER 7 :
CHECKOUT AND SIMULATION INTERFACES . . . . . . . . . . . . . . . . . . . . . . . . 182
7.1 Test Setup Invocation Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
7.2 VICOS Types Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
7.3 HCI Abstract Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
7.3.1 General Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
7.3.2 Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
193
astrium – All Rights Reserved – Copyright per DIN 34

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
ix von/of: xii
7.3.2.1 SET Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
7.3.2.2 GET Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
7.3.2.3 ALTERNATIVE Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
7.3.2.4 PACK Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
7.3.2.5 UNPACK Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
7.3.2.6 PACKED_SIZE Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
7.3.2.7 ADD Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
7.3.2.8 Operations on tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
7.3.2.9 Exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
7.3.2.10 Particular Remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
7.3.2.10.1 On Synchronisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
7.3.2.10.2 On Packing/Unpacking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
7.3.3 ADT Physical Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
7.3.4 ADT CCSDS Packet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
7.3.5 Binary Buffer ADT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
7.4 Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
7.5 TES DEFINITIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
7.6 TES Abstract Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
7.6.1 General Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
7.6.2 Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
7.6.2.1 SET Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
7.6.2.1.1 GET Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
7.6.2.1.2 ALTERNATIVE Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
7.6.2.1.3 PACK Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
7.6.2.1.4 UNPACK Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
7.6.2.1.5 PACKED_SIZE Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
7.6.2.1.6 ADD Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
7.6.2.1.7 Operations on tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
7.6.2.1.8 Exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
7.6.2.1.9 Particular Remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
7.6.2.1.10 On Synchronisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
7.6.2.1.11 On Packing/Unpacking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
7.6.3 ADT Raw Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
7.6.4 ADT Engineering Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
7.6.5 ADT ADU Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267
7.6.6 ADT ADU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
7.6.7 ADT GDU Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
7.6.8 ADT GDU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
304
astrium – All Rights Reserved – Copyright per DIN 34

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
x von/of: xii
7.7 TES Application Programmer Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
7.8 VICOS Housekeeping Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
7.9 System Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
7.9.1 UCL Ground System Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
7.9.1.1 Routines Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
7.9.1.2 UCL Ground System Library Specification . . . . . . . . . . . . . . . . . . . . . . . 339
7.9.1.3 Interface Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
7.9.1.3.15 General Conversion Routines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
7.9.2 UCL GROUND_TO_OB_LIB System Library . . . . . . . . . . . . . . . . . . . . . . . 425
7.9.2.1 Routines Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425
7.9.2.2 UCL GROUND_TO_OB_LIB System Library Specification . . . . . . . . . 425
7.9.2.3 Interface Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431
7.9.3 TCL System Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447
7.9.3.1 Routines Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447
7.9.3.2 TCL_LIBRARY Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448
7.9.3.3 TCL ASCII Format Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 459
7.10 Onboard Commands and Responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461
7.10.1 Software Commands (SWOP_Command) . . . . . . . . . . . . . . . . . . . . . . . . . . . 461
7.10.1.1 CCSDS Header for Software Commands . . . . . . . . . . . . . . . . . . . . . . . . . 461
7.10.1.2 CCSDS Data Field for Software Commands . . . . . . . . . . . . . . . . . . . . . . 462
7.10.1.3 Response Packet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462
7.10.1.3.1 CCSDS Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462
7.10.1.3.2 CCSDS Data Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463
7.10.2 FLAP Execution Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464
7.10.2.1 CCSDS Header for FLAP Execution Requests . . . . . . . . . . . . . . . . . . . . 464
7.10.2.2 CCSDS Data Field for FLAP Execution Requests . . . . . . . . . . . . . . . . . . 464
7.10.2.3 Response Packet for FLAP Execution Requests . . . . . . . . . . . . . . . . . . . 465
7.10.2.3.1 CCSDS Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465
7.10.2.3.2 CCSDS Data Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465
7.11 DBS Types and Constants Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466
7.12 DBS Application Programmer Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482
7.13 TEV Types and Constants Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490
7.14 TEV Application Programmer Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510
7.15 Test Evaluation Invocation Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 567
7.15.1 TEV Invocation for Interactive Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 567
7.15.2 TEV Batch Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
567
astrium – All Rights Reserved – Copyright per DIN 34

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
xi von/of: xii
7.15.3 TEV in Office Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 568
7.16 EXCEL Representation Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569
7.17 Command and Measurement Adaptation System . . . . . . . . . . . . . . . . . . . . . . 570
7.18 Data Types supported by CGS in TES_API and CMAS_IF . . . . . . . . . . . . . . 632
7.18.1 CGS Data Types Supported
. . . . . . . .
632
7.18.2 CGS Data Types: UCL to Raw Value Conversion
. . . . . . . .
635
APPENDIX A :
ACRONYMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637
APPENDIX B :
DEFINITIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
645
astrium – All Rights Reserved – Copyright per DIN 34

Space Infrastructure
TABLE OF FIGURES
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
xii von/of: xii
Figure 1.3–1 CGS Interface Control Document Structure . . . . . . . . . . . . . . . 3
Figure 4.1.2.3.2–1 Example of Mounting Test Node Directories on the DB Server. 17
Figure 6.7–1 I–Code Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Figure 6.7–2 Stack Machine Runtime Layout . . . . . . . . . . . . . . . . . . . . . . . . . 102
Figure 6.8.3–1 External Parameter Encoding Scheme . . . . . . . . . . . . . . . . . . . . 170
Figure 6.8.3–2 Internal Parameter Enoding Scheme . . . . . . . . . . . . . . . . . . . . . 171
Figure 6.8.3–1 Encoded Parameter List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Figure 6.8.3–1 Global Data Frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
173
astrium – All Rights Reserved – Copyright per DIN 34

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
CHAPTER 1 :
INTRODUCTION
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
1 von/of: 662

Space Infrastructure
1.1 Identification and Scope
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
This is the Interface Control document for the COLUMBUS Ground System software.
The authorized abbreviation for this software is CGS.
The approved identification and nomenclature of the document is the following :
CGS Interface Control Document
– for CGS V4.3.0 –
COL–RIBRE–ICD–0025–00
The scope of this document is to cover all aspects of CGS related to external interfaces.
1.2 Purpose
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
2 von/of: 662
The purpose of this document is to describe functionally and formally how CGS interacts with the other SW
products of the Columbus Ground System (CGS) and with other external systems.
It establishes in a single document an interface agreement between the Columbus System and the CGS product
with respect to those interfaces identified in section 1.1.
Hereby it is the objective to control the interface of the CGS product such that it provides services to all interfaced
Columbus products in a manner suited to their needs.
The contents of this document are applicable to the design and the development of the CGS product.
1.3 Reader Guide
In principle, the structure of this document follows the general ICD layout, as described in the Columbus Software
Development Standards (refer to document 2.2.2.1). But the presentation of the provided and required interfaces
has been modified because it simplifies the different CGS product ICDs handling. For the CGS component,
the following structure has been adopted :

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
––1 | Introduction
––2 | Applicable and Reference Documents
––3 | General Description
––4 | ”Product Name” Provided Interfaces
––4.1 | Interface A
––4.2 | Interface B
...
––5 | ”Product Name” Required Interface of ”Product Y”
––5.1 | Interface C
...
––6 | ”Product Name” Required Interface of ”Product Z”
––6.1 | Interface D
...
––n | Language Interface (optional)
––n+1 | Representation Interface (optional)
––n+2 | Implementation Interface (optional)
––n+3 | Product Link Interface
––Appendix A | Acronyms
––Appendix B | Definitions
...
Figure 1.3–1 CGS Interface Control Document Structure
The chapter 2 provides the applicable and reference documents mentioned in this ICD.
The chapter 3 gives an overview of the role of CGS within the complete CGS component.
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
3 von/of: 662
The chapter 4 contains the interfaces provided by CGS to the rest of the system, as listed in the chapter 3.
The chapter 5 and the following ones contain the interfaces CGS requires from the rest of the system, as listed
in the chapter 3. Each component interfacing CGS is treated in a separate chapter.
The chapter n describes language conventions, if there are some defined.
The chapter n+1 describes data representation conventions, if there are some defined.
The chapter n+2 describes protocol implementation conventions, if there are some defined.
The chapter n+3 gives necessary information to set links between products.
The appendix A provides the list of the acronyms used in this ICD.
The appendix B lists the definitions of the key terms used in this ICD.
1.4 Type of Described Interfaces
This document deals with application program interface, language interface and representation interface only.
The reader will not find the description of the CGS user interface. This type of interface, if any, will be described
in detail in the CGS Architectural Design Document and/or in the CGS User Manual .

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
CHAPTER 2 :
APPLICABLE AND
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
4 von/of: 662
REFERENCE DOCUMENTS

Space Infrastructure
2.1 Applicable Documents
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
5 von/of: 662
The following documents, of the issue shown, are external documents called up in the current document and
which are considered to form part of this document, i.e. the called up section(s) of the applicable document
should be treated as if they were an integral part of the document. In case of conflict, the newer document
supersedes the older one.
2.1.1 Specifications
2.1.1.1 COLUMBUS Ground System Infrastructure (CGSI)
S/W Product Requirement Specification, SPE 1216 471 Issue 1/B 03/11/93
2.1.1.2 Software Development Environment (SDE), Reduced Operational Capability (ROC)
S/W Assembly Requirement Specification SPE 1081 716 003 Issue 1/B 08/09/93
2.1.1.3 Software Entity Software (SWES)
S/W Product Requirements Specification, SPE 1218 850 002 Issue 1/– 28/05/93
2.1.1.4 Mission Database Application (MDA)
S/W Product Requirement Specification, SPE 1216 401 002 Issue 2/C 05/11/93
2.1.1.5 COLUMBUS Language System (CLS)
S/W Product Requirement Specification, COL–RIBRE–SPE–0119 Issue 2/A 19/06/97
2.1.1.6 Ground Window Definition Utility (GWDU)
S/W Product Requirement Specification, COL–RIBRE–SPE–0035 Issue 4/– 04/07/97
2.1.1.7 Flight Window Definition Utility (FWDU)
S/W Product Requirement Specification, COL–RIBRE–SPE–0070 Issue 2/– 25/06/97
2.1.1.8 Test Setup, Configuration and Validation (TSCV)
S/W Product Requirement Specification, COL–RIBRE–SPE–0043 Issue 6/D 17/07/97
2.1.1.9 Human Comuter Interface (HCI)
S/W Product Requirement Specification, COL–RIBRE–SPE–0052
2.1.1.10 Test Execution Software (TES)
Issue 6/– 02/07/97
S/W Product Requirement Specification, COL–RIBRE–SPE–0044
2.1.1.11 Database Sevices (DBS)
Issue 6/A 01/07/97
S/W Product Requirement Specification, COL–RIBRE–SPE–0051
2.1.1.12 Test Evaluation Software (TEV)
Issue 6/A 18/02/97
S/W Product Requirement Specification, COL–RIBRE–SPE–0050
2.1.1.13 Network Software (NWSW)
Issue 6/A 18/02/97
S/W Product Requirement Specification, SPE 1216 844 001
2.1.1.14 Time Services Software (TSS)
Issue 7/– 06/05/93
S/W Product Requirement Specification, SPE 1235 055
2.1.1.15 Core Simulation Software (CSS)
Issue 1/A 19/05/93
S/W Product Requirement Specification, COL–RIBRE–SPE–0126 Issue 3/– 11/06/97
2.1.1.16 COLUMBUS Ground System (CGS)
S/W Assembly Requirement Specification, COL–RIBRE–SPE–0032 Issue 6/C 31/03/99

Space Infrastructure
2.1.2 Standards
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
6 von/of: 662
2.1.2.1 User Control Language (UCL) Reference Manual
COL–RIBRE–STD–0010 Issue 4/– 13/03/98
2.1.2.2 High Level Command Language (HLCL) Reference Manual
COL–RIBRE–STD–0009 Issue 2/A 13/03/98
2.1.2.3 Reference Manual for Crew Procedure Language (CPL) and Software Commanding
COL–RIBRE–STD–0008 Issue 1/E 18/05/98
2.1.3 Design Documents
None.
2.1.4 Technical Notes
2.1.4.1 CGS_Library Description COL_RIBRE_TN_1113; Iss. 1F; 4.8.1997
2.1.5 Manuals
2.1.5.1 Life*CODE Integrator Manual TBD TBD
2.1.5.2 Life*ADA Integrator Manual
CSD/TRJ/USM/005
Issue 1.1 July 1995
2.1.5.3 Generic Tool Integration User Manual Issue 2.0 May 1995
2.1.5.4 Interleaf 5, File Formats Manual Release 5.3
2.1.5.5 MDA Reference Manual
COL–RIBRE–MA–0031–00
and
DADI–MA Reference Manual
Issue 4/C 31/03/00
COL–RIBRE–MA–0032–00 Issue 4/– 01/09/97
2.1.5.6 Sammi Application Development Kit (ADK) Version 3.0 31/03/94
System Administrator’s Guide
2.1.6 Interface Control Documents
2.1.6.1 MDB Standard Entities and Application Programmer Interface
COL–RIBRE–ICD–0069 Issue 4/B 31/8/00
2.1.6.2 Space Station Manned Base to Columbus Attached Pressurized Module Interface Control Document.
SSP 42001 Revision K TBD

Space Infrastructure
2.2 Reference Documents
The documents specified in this section serve only as reference material.
2.2.1 Specifications
None.
2.2.2 Standards
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
7 von/of: 662
2.2.2.1 Columbus Software Development Standards,
STD 1213 800 000 Issue 5/–, 22/11/91.
2.2.3 Design Documents
None.
2.2.4 Technical Notes
None.
2.2.5 Manuals
None.
2.2.6 Other Documents
None.

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
CHAPTER 3 :
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
8 von/of: 662
GENERAL DESCRIPTION

Space Infrastructure
3.1 CGS Functional Overview
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
9 von/of: 662
CGS is the ’backbone’ assembly providing core or essential services and actually making up most of its functionality
of the various ground based Facilities within the different Space Programmes (e.g. GSRF, DMS–R, COF,
MPLM, NASA). CGS exists in several configurations each targeted at some specific operational environment
or user task. Major Facilities currently identified are:
* Software Design and Development Facility (SDDF). Used for design and development (coding,
unit test, product–level integration & partial qualification) of flight SW and data.
* Electrical Ground Support Equipment (EGSE). This facility is used for system–level integration,
verification and qualification of Flight HW and SW.
* Software, Integration and Test Equipment (SITE). Used for system–level integration, verification
and qualification of Flight SW.
A Facility is made up from CGS software configurations, standard hardware and additional hardware/software
Add Ons, e.g. Software Design and Development support services, Ground Test equipment etc. CGS is a generic
reference concept, encompassing specific CGS ’Add On’ software and CGS will be extended to establish the
Facilities. Each Facility will be different although each follow a logical model.
CGS provides software services as required for the Facilities. These services are needed for the design, development
and integration, test and qualification related activities for the Flight Configuration.
The overall functionality of CGS will support the following functions:
Design and Development Support for Ground and Flight Systems including:
Columbus Ground System Infrastructure (CGSI) provides the basic service layer to all
CGS S/W Applications, supporting Servers (SUN–4), Test Nodes (HP 9000 – 700/800
Series) and graphical Workstations (SUN–4) under the UNIX Operating System.
Software Development Environment (SDE) provides standard S/W Life Cycle support:
CGS provides interfaces to commercial SDEs, related to S/W Coding / Testing
Support including Compiler Systems and additional S/W Development Tools. Via
the MDB and the SWES component, the bridge to S/W Configuration Management
is closed, based on contractual Configuration Items and entities stored together
with data items in the MDB, .
The Software Entity Software (SWES) provides support for Ada Precompilation of
SW and Transfer of Onboard SW into the Mission Database (MDB).
The Mission Database Application (MDA) constitutes the set of utilities which support
or enable various activities typically performed during the preparation phase of a checkout
/ simulation test or mission and provides data entry and reporting, configuration management
and support to off-line generation of onboard database/flight image. MDA is
centered around the Mission Database which serves as a central repository for all test /
mission–related information.

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
10 von/of: 662
The Columbus Language System (CLS) comprises several language related software
components for UCL, HLCL and CPL:
The CLS Editor is the XView based user front–end for editing UCL, HLCL or CPL
command sequences and for the specification of SW Commands within the interactive
database environment of MDA,
The UCL Compiler translates automated procedures (APs) and libraries written
in the User Control Language (UCL) into an intermediate code (I–Code),
The HLCL Interpreter constitutes the interactive commanding interface of different
applications running on various workstations in the ground system. It interprets
and executes interactive commands and automated command sequences
written in the High Level Command Language (HLCL),
The HLCL Command Window is an XView based interactive window interface
to the HLCL Interpreter.
The Ground Window Definition Utility (GWDU) provides functionality to generate
checkout and simulation orientated ground synoptic displays. These layouts contain animated
functional drawings which will be used to display e.g. checkout, simulation, subsystem
and payload status information and to read in dedicated commands from the
human user. This product will be based on the Ground Symbol and Display Standard.
The Flight Window Definition Utility (FWDU) provides functionality to generate flight
synoptic displays. These layouts contain animated functional drawings which will be
used to display subsystem and payload status information and to read in dedicated commands
from the human user. This product will be based on the Flight Symbol and Display
Standard.

Space Infrastructure
Integration, Test and Qualification Support for Flight Systems:
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
11 von/of: 662
The Test Setup, Configuration and Verification Software (TSCV) configures a required
system configuration for a Checkout Test / Simulation. It enables the test nodes to be activated
for a given test. TSCV implements the generation of a test session in the master
archive. TSCV further supports the user to identify and control the currently used S/W
Configuration.
The Human Computer Interface (HCI) provides all services related to user input / output
on workstations during execution of a Checkout Test / Simulation Session. It provides
different interfaces to the window system and the HCI devices (keyboard,mouse,screen)
and includes services for synoptic display update, user help and user guidance through
test operations. It provides the commanding interface and the message output during online
test execution.
The Test Execution Software (TES) implements the support for test operations and automatic
testing / monitoring of the Unit under Test (UUT). It is driven by the test definitions
done by MDA and the configuration setup by TSCV. It provides a generic data and control
interface to the UUT and all services required for realtime enditem data processing.
Data Base Services (DBS) provides low level management and access to checkout test
related result data items stored in the Test Results Database or files.
Test Evaluation Software (TEV) provides all services to evaluate a.m. data generated and
stored during checkout test execution. It provides services for data selection and data
presentation. It further implements the final archiving of test results as well as the selective
exporting / importing of parts of the Test Result Database.
Network Software (NWSW) provides low level message based interprocess communication
as well as file transfer and directory services in a non NFS environment.
Timing Services Software (TSS) provides the synchronization of local computer clocks
in a distributed environment with respect to the actual (local) time. In addition, TSS also
provide low level SMT distribution, access and handling.
The Core Simulation Software (CSS) provides support for Simulation Model Development,
Simulation Preparation and Execution / Control of Models.

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
CHAPTER 4 :
INFRASTRUCTURE
INTERFACES
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
12 von/of: xii
astrium – All Rights Reserved – Copyright per DIN 34

Space Infrastructure
4.1 Operating System Services
4.1.1 Operating System
Informal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
13 von/of: 662
CGSI provides the Operating System for SUN and HP. FORCE as a third platform is used for the execution of
simulation models only.
Sun Platform
The System V option is installed and enabled.
Network Information Services (NIS) are installed and running.
Newsprint software for Postscript printers.
UUCP is installed and configured.
HP Platform
Network Information Services (NIS) are installed and running.
FORCE Platform
Network Information Services (NIS) are installed and running.
Formal Interface Description
CGSI Product Platform Commercial Product Version
OS Services SUN SOLARIS 2.6
incl. Sun recommended patches (Generic_105181–03)
HP 9000/700 HP–UX 10.20 A
+ Y2K Patch Bundle

Space Infrastructure
4.1.2 File System Structure
4.1.2.1 Home Directories for CGS Products
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
14 von/of: 662
CGSI provides to each CGS product a single home directory as defined in the following subsections.
4.1.2.1.1 Sun Platform
4.1.2.1.1.1 GSAF Home Directory
For CGS and its extensions and add–ons in the frame of GSAF, a global home directory, addressed by
means of the environment variable
$GSAF_HOME
exists. This directory is created during CGS installation. By default, the pathname
/usr/gsaf
will be used, but this is not mandatory and can be changed during installation.
The directory $GSAF_HOME and associated subdirectories and files will be owned by the user, who
is doing the installation of CGS (and its products).
4.1.2.1.1.2 CGS Home Directory
The following home directory is assigned to CGS as a common pool for SW and data:
$GSAF_HOME/cgs
The home directory is addressed by means of the environment variable CGS_HOME. This directory
will be used to store common SW and data as well as general scripts for installation / administration
etc. used by more than one CGS Product.
4.1.2.1.1.3 Product Home Directories
The following home directories are assigned to the lower level CGS Products:
$GSAF_HOME/
where is one of the following:
cgsi, sde, mps, mda, gwdu, fwdu, cls, vicos, tscv, hci, tes, dbs, tev, nwsw, tss, css.
The home directory is addressed by means of the environment variable _HOME
where is one following:
CGSI, SDE, MDA, GWDU, FWDU, CLS, TSCV, HCI, TES, DBS, TEV, NWSW, TSS,
CSS.
Note: The installation of the CGS Product SWES will be done under the directory structure of SDE.
Within CGS scripts, SW etc, the explicit usage of ~username as reference scheme has to be avoided
in any case. All references in scripts, SW etc. shall be based on the environment variables as defined
above.
It is recommended that non–CGS Products (e.g. FES, CMAS etc.) will be installed parallel to the CGS
Products directly under $GSAF_HOME with the same substructure as defined in section 4.1.2.2.
4.1.2.1.2 HP Platform
On each HP platform the GSAF top level directory (as described in section NO TAG) must be visible
and mounted into the same pathname as for the SUN platform.

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
15 von/of: 662
The ”..._HOME” variables address the specified directories in the same way as specified for SUN platform.
4.1.2.2 Subdirectories for CGS Products
Each product has its subdirectories relative to its home directory for the location of executable images,
data, utilities etc. as defined in sections 4.1.2.2.1 to 4.1.2.2.7 etc. CGSI will create these subdirectories.
Any extension in order to add another subdirectory in parallel to this level require explicit authorization
by CGS Engineering.
Note: For SDE and SWES, the directory structure already established under $SDE_HOME will be kept
without any changes!
4.1.2.2.1 Start–Up Scripts
The following directory is provided for Product related start–up scripts:
$_HOME/bin/common
where is one of the products specified in section 4.1.2.1.1.3. Product start–up scripts
will setup the necessary environment for the execution of product SW and then subsequentially call
the target dependant executable image(s) as defined in section 4.1.2.2.
Note: For the external invocation of CGS Product SW always the start–up script under
$_HOME/bin/common
shall be called and not directly the target dependant executable image !
4.1.2.2.2 Executable Images (Platform dependent)
The following directory is provided for Product related executable images:
$_HOME/bin/
where is one of the products specified in section 4.1.2.1.1.3 and is one of the
following: sun5, hp_ux8.
4.1.2.2.3 Environment
The following directory is provided for Product related environment setup (e.g. specific login, logout,
cshrc):
$_HOME/user_env
where is one of the products specified in section 4.1.2.1.1.3.
4.1.2.2.4 Utilities and Tools (Platform dependent)
The following directory is provided for executables / scripts etc of Product related utilities and tools
(e.g. installation / deinstallation of users, product SW etc.):
$_HOME/util/
where is one of the products specified in section 4.1.2.1.1.3 and is one of the
following: sun5, hp_ux8.

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
For the installation of users the following file name syntax shall be used:
install_user
Configuration data files as inputs to these scripts shall be placed under
$_HOME/config.
4.1.2.2.5 Configuration Data
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
16 von/of: 662
The following directory is provided for static configuration data of a Product (e.g. license files, product
version identification files etc, usually defined by the Product Administrator):
$_HOME/config
where is one of the products specified in section 4.1.2.1.1.3 .
4.1.2.2.6 Runtime Data
The following directory is provided for Product SW generated data files at runtime:
$_HOME/data
where is one of the products specified in section 4.1.2.1.1.3 .
4.1.2.2.7 Libraries
The following directory is provided for Product specific library code including Application Programmers
Interfaces (e.g. Ada, C, SQL etc):
$_HOME/lib/
where is one of the products specified in section 4.1.2.1.1.3 and is one of the
following: sun5, hp_ux8
Whenever library code including Application Programmers Interfaces is crossing Product boundaries
(i.e. CGS wide libraries), the location shall be:
$CGS_HOME/lib/
instead, where is one of the following: sun5, hp_ux8.
4.1.2.3 Special Checkout related Directories
4.1.2.3.1 Test Node Directory on the HP Test Nodes
Additionally, for each test node (HP platform) one directory in the local filesystem on the HP machine
will be created during CGS installation.
By default, the pathname
/test_node/‘hostname‘
will be used, but this is not mandatory and can be changed during installation.
This directory has to be created with the same ownerships as the directory tree under $GSAF_HOME
on the SUN platform.

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
17 von/of: 662
This directory will be referenced by the environment variable:
$TN_HOME
on each host (HP and SUN).
Also below this directory, two directories ”archive” and ”replay” have to be created, also owned by
the same user as for $TN_HOME. These directories will be used by the CGS products to store archive
files produced during a normal session (directory ”archive”) or used for replay purposes (directory ”replay”).
4.1.2.3.2 Test Node Directories on the SUN Database Server
Additionally for each installed HP test node, a directory in the local filesystem of the SUN Database
Server will be created during CGS installation.
The pathname for these directories needs to be exactly the same as for the test nodes (see section
4.1.2.3.1).
These directories have to be created with the same ownerships as the directory tree under
$GSAF_HOME on the SUN platform.
For all a.m. directories, the corresponding directories of the test nodes need to be mounted (see also
Figure 4.1.2.3.2–1 below).
/usr/test_node/hostn
/usr/test_node/host2
/usr/test_node/host1
DB Server
(SUN)
UNIX Mounts
/usr/test_node/host1 /usr/test_node/host2 /usr/test_node/hostn
archive archive archive
replay replay replay
Test Node 01
(HP)
Test Node 02
(HP)
Test Node xy
(HP)
Figure 4.1.2.3.2–1 Example of Mounting Test Node Directories on the Database Server.
4.1.2.4 Home Directories For CGS Extensions And Add–Ons
4.1.2.4.1 Special Application Software (SAS)
The CGS product TES is able to start special application Software (SAS).
For all SAS related data (executables, data, config files, results, etc.), CGS provides a global directory
$GSAF_HOME/sas
This directory will be owned by the owner of $GSAF_HOME.
CGS Software expects that SAS executables be stored in a directory

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
18 von/of: 662
$GSAF_HOME/sas/bin
such that they can be started from here. Therefore, the executables must either by physically present
in this directory or visible here through UNIX softlinks into other parts of the filesystem, possibly
owned by the user.
It is important that all SASes are executable for CGS, i.e. the corresponding permissions have to be
set appropriately.
CGS does not use any other directory structure below $GSAF_HOME/sas, however, it is recommended
that SASes follow the breakdown given in para. 4.1.2.2.
4.1.2.4.2 Command And Measurement Adaptation Software (CMAS)
The CGS product CSS communicates with Command And Measurement Adaptation Software
(CMAS) to facilitate hardware in the loop testing.
For all CMAS related data (executables, data, config files, results, etc.), CGS provides a global directory
$GSAF_HOME/cmas
This directory will be owned by the owner of $GSAF_HOME.
CGS Software expects that CMAS executables be stored in a directory
$GSAF_HOME/cmas/bin
such that they can be started from here. Therefore, the executable(s) must either by physically present
in this directory or visible here through UNIX softlinks into other parts of the filesystem, possibly
owned by the user.
It is important that all CMASes are executable for CGS, i.e. the corresponding permissions have to be
set appropriately.
CGS does not use any other directory structure below $GSAF_HOME/cmas, however, it is recommended
that CMASes follow the breakdown given in para. 4.1.2.2.
4.1.2.4.3 Mission Database Support Software (MDB_SS)
The CGS product MDA provides the capability for Mission Database Support Software to facilitate
mission specific database operations.
For all MDB_SS related data (executables, data, config files, results, etc.), CGS provides a global directory
$GSAF_HOME/mdb_ss
This directory will be owned by the owner of $GSAF_HOME.
CGS Software expects that MDB_SS executables be stored in a directory
$GSAF_HOME/mdb_ss/bin
such that they can be started from here. Therefore, the executable(s) must either by physically present
in this directory or visible here through UNIX softlinks into other parts of the filesystem, possibly
owned by the user.
It is important that all MDB_SSes are executable for CGS, i.e. the corresponding permissions have to
be set appropriately.

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
19 von/of: 662
CGS does not use any other directory structure below $GSAF_HOME/mdb_ss, however, it is recommended
that MDB_SSes follow the breakdown given in para. 4.1.2.2.

Space Infrastructure
4.1.3 Common User Environment Files
Informal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
20 von/of: 662
This section lists the script files which are used to set the environment of all CGS users.
The user environment files described in these sections are C–shell script files.
Through the use of the login and cshrc files CGSI initialises the CGS user environment for a CGS user on login.
The cshrc file is also executed for each subsequent shell that is invoked. CGSI uses the logout script files to tidy
up a user session on logout.
After establishing a common environment for all CGS users these script files provide the facility for a product
to provide further, product specific, tailoring of the user environment by executing the product supplied scripts.
Finally the script files provide the facility for an individual CGS User to carry out his or her own individual environment
tailoring through the use of user supplied script files.
Formal Interface Description
The CGSI provided central scripts for the supported target platforms, as defined in section 4.1.3.1, are implemented
as target–independant shell scripts. Central scripts are provided for login, cshrc and logout.

Space Infrastructure
4.1.3.1 Central Scripts
4.1.3.1.1 Central ”login” Script
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
21 von/of: 662
#####################################################################
#
# Product: CGSI CI–Number: 1216471
#
# Function: Central CGSI login file. Will be called by the users’ local .login script.
#
#####################################################################
unsetenv CGS_ERROR
set DISPLAY_MOTD = $CGSI_HOME/bin/common/display_motd
umask 022
switch ( ‘uname –s‘)
case ”SunOS”:
# Set terminal characteristics for remote terminals:
set noglob
eval ‘tset –Q –s –m ’dialup:?vt100’ –m ’network:?vt100’ –m ’su:?vt100’‘
unset noglob
set term=$TERM
# Set up cd path
set cdpath = (.. ~ )
# Skip remaining setup if not an interactive shell
if ($?USER == 0 || $?prompt == 0) exit
# Set mail characteristics
set mail = /var/mail/$user
biff y
# Set helpful environment variables
setenv MORE ’–c’
breaksw
case ”HP–UX”:
##################################################################
# Set terminal characteristics for remote terminals:
##################################################################
eval ‘tset –s –Q –m ’:vt100’‘
stty erase ”^H” kill ”^U” intr ”^C” eof ”^D” susp ”^Z” hupcl ixon ixoff tostop tabs
##################################################################
# Set up the shell environment
##################################################################
setenv TERM sun
set noclobber
breaksw
default:
setenv CGS_ERROR ”Unsupported Architecture”
endsw
#####################################################################
# Display any ”message of the day”
#####################################################################
if (–e $DISPLAY_MOTD) then
$DISPLAY_MOTD
endif
unset DISPLAY_MOTD

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
#####################################################################
# Source the SDE’s ”login” file
#####################################################################
if (–e $SDE_HOME/user_env/login) then
source $SDE_HOME/user_env/login
endif
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
22 von/of: 662

Space Infrastructure
4.1.3.1.2 Central ”cshrc” Script
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
23 von/of: 662
################################################################################
#
# Product: CGSI CI–Number: 1216471
#
# Date: 22.02.96 Version: 4.3
#
# Name: Cshrc Type: Cshell script
#
# Authors: P. Athmann, J. Hoyng, A. Ringleb, U. Hohnhorst
#
# Function: Central CGSI cshrc file. Will be called by the users’
# local .cshrc script.
# Change History:
# PIRN 8027 1/A (08.03.99): MD
# –– Added SWES_HOME
# PIRN 3094 1/B (22.02.96):
# – New architecture sun5,
# – new environment variables CMAS_HOME, SAS_HOME
# – included $CGSI_HOME/oracle/.cshrc
#
# PIRN 3086 1/A (10.11.95):
# – Execute dbs_cshrc file
# – Define TN_HOME variable
#
# PIRN 3083 1/C (10.11.95)
# – New default for GSAF_HOME
#
# COL–RIBRE–CGS–IRN–5017
# GSRF–RIBRE–CGS–SPR–2945
# – TN_HOME problems fixed
#
################################################################################
umask 022
unsetenv CGS_ERROR
set architecture = ‘uname –s‘
switch ($architecture)
case ”SunOS”:
set hardpaths
setenv OPENWINHOME /usr/openwin
setenv LD_LIBRARY_PATH $OPENWINHOME/lib
setenv XAPPLRESDIR $OPENWINHOME/lib/app–defaults
set path = ( . \
~/bin \
$OPENWINHOME/bin \
/usr/sbin \
/usr/bin \
/usr/ucb \
/usr/ccs/bin \
/usr/local/bin )
setenv REMOTE_SHELL rsh
set os_release = ‘uname –r‘
if ( $os_release =~ 4.* ) then
setenv CGS_ARCH sun4
else if ( $os_release =~ 5.* ) then
setenv CGS_ARCH sun5
else
setenv CGS_ERROR ”Unsupported Architecture”
endif

Space Infrastructure
unset os_release
breaksw
case ”HP–UX”:
set path = (. \
~/bin \
/usr/sbin \
/usr/bin \
/opt/ansic/bin \
/usr/ccs/bin \
/usr/contrib/bin \
/usr/bin/X11 \
/usr/contrib/bin/X11 )
alias rsh remsh
setenv REMOTE_SHELL remsh
setenv CGS_ARCH hp_ux8
breaksw
default:
setenv CGS_ERROR ”Unsupported Architecture $architecture”
endsw
unset architecture
# exit the script, if CGS_ERROR is set
if ($?CGS_ERROR ) then
echo ” ”
echo ” *** Error in CGSI Cshrc script ***”
echo $CGS_ERROR
echo ” ”
echo ”exit with status 1”
exit 1
endif
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
24 von/of: 662
################################################################################
# Define CGS variables
################################################################################
setenv LOGNAME ‘whoami‘
setenv USER ‘whoami‘
#############################################################################
# Define product home environment variables
#
# Note: Default Pathname will be /usr/gsaf, but can be
# ===== changed below during CGSI Installation !
#############################################################################
if ($?GSAF_HOME) then
:
else
setenv GSAF_HOME /usr/gsaf
endif
if (–d ”$GSAF_HOME”) then
setenv CGS_HOME $GSAF_HOME/cgs
setenv CGSI_HOME $GSAF_HOME/cgsi
setenv SDE_HOME $GSAF_HOME/sde
setenv SWES_HOME $SDE_HOME/swes
setenv MDA_HOME $GSAF_HOME/mda
setenv GWDU_HOME $GSAF_HOME/gwdu
setenv FWDU_HOME $GSAF_HOME/fwdu
setenv CLS_HOME $GSAF_HOME/cls
setenv TSCV_HOME $GSAF_HOME/tscv

Space Infrastructure
else
endif
setenv HCI_HOME $GSAF_HOME/hci
setenv TES_HOME $GSAF_HOME/tes
setenv DBS_HOME $GSAF_HOME/dbs
setenv TEV_HOME $GSAF_HOME/tev
setenv NWSW_HOME $GSAF_HOME/nwsw
setenv TSS_HOME $GSAF_HOME/tss
setenv CSS_HOME $GSAF_HOME/css
setenv CMAS_HOME $GSAF_HOME/cmas
setenv SAS_HOME $GSAF_HOME/sas
echo ” ”
echo ” Error in CGSI Cshrc script: ”
echo ” Directory $GSAF_HOME doesn’t exist”
echo ” Environment variables could not be set”
echo ” ”
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
#############################################################################
# setup Oracle environment
#############################################################################
setenv ORACLE_BASE ‘(cd $ORACLE_HOME/../.. && pwd)‘
setenv ORACLE_HOME ORACLE_HOME # MODIFY value during installation
setenv ORACLE_SID oracle7 # MODIFY value during installation
if ( –e $ORACLE_HOME ) then
if ($?LD_LIBRARY_PATH == 0) then
setenv LD_LIBRARY_PATH $ORACLE_HOME/lib
else
switch ($LD_LIBRARY_PATH)
case *$ORACLE_HOME/lib* :
breaksw
case ”” :
setenv LD_LIBRARY_PATH $ORACLE_HOME/lib
breaksw
default :
setenv LD_LIBRARY_PATH $ORACLE_HOME/lib:${LD_LIBRARY_PATH}
breaksw
endsw
endif
switch ($PATH)
case *$ORACLE_HOME/bin* :
breaksw
case *[:] :
setenv PATH ${PATH}$ORACLE_HOME/bin:
breaksw
case ”” :
setenv PATH $ORACLE_HOME/bin
breaksw
default :
setenv PATH ${PATH}:$ORACLE_HOME/bin
breaksw
endsw
setenv ORA_NLS33 $ORACLE_HOME/ocommon/nls/admin/datad2k
endif
#############################################################################
# setup DBS environment
#############################################################################
if ( –e $DBS_HOME/user_env/dbs_cshrc ) then
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
25 von/of: 662

Space Infrastructure
endif
source $DBS_HOME/user_env/dbs_cshrc
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
#############################################################################
# Define Test Node (dependant) home environment variable
#
# Note: Default Pathname will be /usr/test_node, but will be changed below
# ===== during CGSI Installation !
#############################################################################
setenv TN_HOME /usr/test_node/‘hostname‘
#############################################################################
# Set helpful variables
#############################################################################
set filec
set ignoreeof
set history=50
###########################################################################
# Source the SDE’s ”cshrc” file
###########################################################################
if (–e $SDE_HOME/user_env/cshrc) then
source $SDE_HOME/user_env/cshrc
endif
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
26 von/of: 662

Space Infrastructure
4.1.3.1.3 Central ”logout” Script
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
27 von/of: 662
#######################################################################################
#
# Product: CGSI CI–Number: 1216471
#
# Date: 06.02.95 Version: 1.0
#
# Name: Logout Type: Cshell script
#
# Authors: P. Athmann, J. Hoyng, A. Ringleb, U. Hohnhorst
#
# Function: Central CGSI logout file. Will be called by the users’ local .logout
script.
#
#######################################################################################
clear
###########################################################################
# Source the SDE’s ”logout” file
###########################################################################
if (–e $SDE_HOME/user_env/logout) then
source $SDE_HOME/user_env/logout
endif
echo ”‘hostname‘: ‘whoami‘ logged out at ‘date‘”
echo ”Goodbye\!”

Space Infrastructure
4.2 Relational Database Management System
Informal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
28 von/of: 662
This chapter defines the interface provided by CGSI to the CGS products for access to and use of the RDBMS
services.
A general section details the basic interface as specificed by the commercial product documentation. This is followed
by individal subsections with the specific details for each of the CGS products.
Formal Interface Description
4.2.1 Functional Interface
4.2.1.1 General
The CGSI RDBMS services are implemented by means of the ORACLE database management system.
See chapter 4.2.3 for details on product version.
4.2.2 Database Installation and Configuration
All instances of the CGSI RDBMS Services are installed and configured in accordance with the following subsections.
For each of the predefined objects names identified CGS product–specific defintions are described in the appropriate
product subsection.
4.2.2.1 Predefined Object Names
4.2.2.1.1 User Accounts
A user requiring access to an ORACLE database must have an ORACLE username and password that are valid
for a given database. This is separate from the username and password required by the operating system which
are assigned independently from ORACLE and do not provide access to an ORACLE database or programs.
4.2.2.1.2 Tablespaces
A database is divided into logical divisions called tablespaces. A database may have one or more tablespaces
and each logical tablespace corresponds to one or more physical files. Each tablespace has a set of default storage
characteristics. ORACLE users who will be creating database objects must have the right to create objects in
a given tablespace.
4.2.2.1.3 Public Synonyms
Public synonyms are used for database objects which the DBA has created for use by all ORACLE users.
4.2.2.1.4 CRT Device Names
Default terminal definitions are provided, in CRT files, for many terminals associated with the operating system
under which ORACLE runs. (A CRT file maps terminal keys to application functions, such as Clear Screen or

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
29 von/of: 662
Go To Next Field). The ORACLE distribution tape for a given operating system contains the appropriate default
terminal definition. It is possible to select an alternative CRT file.
The following CRT terminal definition file is used for CGS:
default.crt
4.2.2.2 ORACLE Configuration Parameters
4.2.2.2.1 INIT.ORA Configuration File
Informal Interface Description
When an ORACLE database instance starts, the ORACLE configuration parameters are taken into consideration.
These parameters are defined in the file INIT.ORA whereby is is the
Oracle Instance Identifier. The parameters effect memory structures, impose limits, identify files and optimize
performance. In the absence of an explicit value, ORACLE uses default values for each parameter.
Constraints on the use of parameters defined in the INIT..ORA file and applicable to the CGS
assemblies using ORACLE have been identified. To provide a precise formal interface, and since most parameter
values specificed in INIT.ORA are global (that is, are specified on a database–wide basis), the ORACLE
configuration parameters that apply across all assemblies are stated. No assembly specific configuration constraints
have been identified.
Formal Interface Description
#################################################################################
#
# Name : config/Oracle/initoracle.ora
#
# Title : Oracle RDBMS Setup parameters
#
# CI : 1216 471, CGSI
#
# Description : Customized init.ora file for Oracle Setup
#
#
# Use : Copied to directory $ORACLE_HOME/dbs by the install_cgsi
# script.
#
#
# Notes : See Oracle Documentation for contents of this file
#
#
# include database configuration parameters
ifile = /gsaf/cgsi/oracle/dbs/configoracle.ora
rollback_segments = (rs, rs_large, r01,r02,r03)
# tuning parameters
db_files = 20

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
#db_file_multiblock_read_count = 8 # SMALL
db_file_multiblock_read_count = 16 # MEDIUM
# db_file_multiblock_read_count = 32 # LARGE
#db_block_buffers = 200 # SMALL
#db_block_buffers = 550 # MEDIUM
#db_block_buffers = 3200 # LARGE
db_block_buffers = 12000 # MDB
#shared_pool_size = 3500000 # SMALL
#shared_pool_size = 6000000 # MEDIUM
#shared_pool_size = 9000000 # LARGE
shared_pool_size = 32000000 # MDB
log_checkpoint_interval = 10000
# processes = 50 # SMALL
processes = 100 # MEDIUM
# processes = 200 # LARGE
#dml_locks = 100 # SMALL
#dml_locks = 200 # MEDIUM
#dml_locks = 500 # LARGE
dml_locks = 2000 # MDB
#log_buffer = 8192 # SMALL
log_buffer = 32768 # MEDIUM
# log_buffer = 163840 # LARGE
#sequence_cache_entries = 10 # SMALL
sequence_cache_entries = 30 # MEDIUM
# sequence_cache_entries = 100 # LARGE
#sequence_cache_hash_buckets = 10 # SMALL
sequence_cache_hash_buckets = 23 # MEDIUM
# sequence_cache_hash_buckets = 89 # LARGE
# audit_trail = true # if you want auditing
# timed_statistics = true # if you want timed statistics
max_dump_file_size = 10240 # limit trace file size to 5 Meg each
# log_archive_start = true # if you want automatic archiving
# mts_dispatchers=”ipc,1”
# mts_max_dispatchers=10
# mts_servers=1
# mts_max_servers=10
# mts_service=oracle7
# mts_listener_address=”(ADDRESS=(PROTOCOL=ipc)(KEY=oracle7))”
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
30 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
OS_AUTHENT_PREFIX = ”OPS$” # required by MDB
REMOTE_OS_AUTHENT = TRUE # required by MDB
enqueue_resources = 4020 # required by MDB
open_cursors = 255 # required by MDB
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
31 von/of: 662
SORT_AREA_SIZE = 1048576 # 1 MB for sort area in memory
# The following enables a feature we need to create our tablespaces.
# The script is preconfigure_oracle.sql.
# The computations for maxextents use UNLIMITED
COMPATIBLE = 7.3.0.0.0
OPTIMIZER_MODE = rule
4.2.2.2.2 Rollback Segments
The cgsi installation script defines five rollback segments:
RS : system rollback segment
CGSI insures the minimum parameters sizes as follow:
optimal 1500K next 250k minextents 5
R01, R02, R03 : rollback segments to be used by applications performing transactions with low level
amount of data
CGSI insures the minimum parameters sizes as follow:
optimal 1500k next 250k minextents 5
RS_LARGE : rollback segment to be used by applications performing transactions with high level
amount of data
CGSI insures the minimum parameters sizes as follow:
optimal 2750K next 550K minextents 5
The application has to insure the usage of the RS_LARGE segment when performing high level amount
of data transactions.

Space Infrastructure
4.2.3 Commercial Product Versions
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
CGSI Product Platform Commercial Product Version
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
32 von/of: 662
RDBMS Services SUN ORACLE RDBMS
+ Varraw patch (DASA)
7.3.4.4 (*)(**)
SUN PRO*C 2.2.4 (*)(**)
SUN PRO*Ada 1.8.4 (*)(**)
SUN Oracle*Forms 4.5.9 (*)(***)
SUN SQL*Plus 3.3.4.0.1 (*)(**)
SUN Oracle*Reports 2.5.7 (*)(***)
SUN SQL*Net TCP/IP 2.3.4.0 (*)(**)
(*) Products so marked are covered by ESA/Oracle license contract
(**) Products so marked are an integral part of Oracle 7 Server 7.3.4.0.1 Delivery
Note: Version 7.3.4.4=7.3.4.0+Patch4
(***) Products so marked are an integral part of Oracle Developer 2000 Kit (Release 1.6)

Space Infrastructure
4.3 Communication Services
4.3.1 Internet Port Number Allocation
Informal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
33 von/of: 662
An Internet port is a logical communication channel in a host. These ports total 65535 and are accessed by port
numbers. Some of the numbers are reserved by system services such as TELNET, FTP etc. Others are reserved
for applications such as ORACLE/SQL*net.
This section defines the ports reserved for system services, etc.
Formal Interface Description
The following port numbers are reserved:
Service Portnumber/Protocol aliases and comments
System services 0–1023
ingreslock 1524/tcp
orasrv 1526/tcp ORACLE
1259/tcp Reserved for Atherton BackPlane
1259/udp Reserved for Atherton Backplane
rlb 1260/tcp # remote loopback diagnostic
nft 1536/tcp # NS network file transfer
netdist 2106/tcp # update(1m) network distribution service
rfa 4672/tcp # NS remote file access
dc_server 5000/tcp # Teamwork Data Controller Server
lanmgrx.osB 5696/tcp # LAN Manager/X for B.00.00 OfficeShare
grmd 5999/tcp # graphics resource manager
spc 6111/tcp # sub–process control
nfsd 2049/udp # NFS remote file system
CGS Applications 7000/tcp–7999/tcp VICOS Applications
CGS Applications
Notes:
8000/tcp–8999/tcp CSS Applications
# The X10_LI server for each display listens on ports 5800 + display number.
# The X10_MI server for each display listens on ports 5900 + display number.
# The X11 server for each display listens on ports 6000 + display number.
# Do not associate other services with these ports.
# Refer to the X documentation for details.

Space Infrastructure
4.3.2 Commercial Product Versions
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
CGSI Product Platform Commercial Product Version
Communication
Services SUN TCP/IP (*)
SUN NFS (*)
SUN Ethernet Software (*)
HP TCP/IP (**)
HP NFS (**)
HP Ethernet Software (**)
(*) Products so marked are an integral part of SunOS
(**) Products so marked are an integral part of HP–UX
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
34 von/of: 662

Space Infrastructure
4.4 Presentation Services
Informal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
35 von/of: 662
The CGSI Presentation Services provide an X–11 environment on all CGS workstations and servers (both Sun
and HP).
In addition on Sun platforms the CGSI Presentation Services provide both an environment for developing
OPENLOOK applications and an OPENLOOK window manager environment for executing window applications.
Formal Interface Description
CGSI Product Platform Commercial Product Version
Presentation
Services SUN X–lib Open Windows 3.6 (*)
SUN X View Toolkit Open Windows 3.6 (*)
SUN Open Look Window
Manager (OLWM) Open Windows 3.6 (*)
SUN X–Server Open Windows 3.6 (*)
(*) Products so marked, including Open Windows, are an integral part of SunOS/SOLARIS

Space Infrastructure
4.5 DataViews Services
Informal Interface Description
CGS provides Dataviews services.
Formal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
36 von/of: 662
CGSI Product Platform Commercial Product Version
SUN DataViews DV Draw 9.7a
SUN DataViews DV Tools 9.7a
SUN DataViews EO Geck 3.1
SUN DataViews Ada Bindings 9.7a
+ patch types.a: Color Threshold Table
(described in COL–RIBRE–CGS–SMD–3031)
+ patch 052
(ftp://ftp.prs.de/pub/packages/dv97/p052.solaris.tgz)

Space Infrastructure
4.6 CGS Top Level User Interface
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
37 von/of: 662
The CGS Top Level User Interface is the name given to the CGSI developed product. As such, it provides the
following:
– the user interface to the CGS system as a whole
– which integrates the CGS products through the provision of a common invocation mechanism
– which is also referred to as the CGS Desktop
– which enables the user to execute CGS level tasks (and the privileged user to perform data administration
and user administration).
[It is important to note that CGSI exercises no privilege control over users. When a user
selects and invokes a task from the CGS Desktop then that task is invoked by CGSI and
it is an product responsibility to check the user has sufficient privileges to execute that
task.]
– a set of services additional to those provided by the CGS Platform (the CGSI procured products)
– the only services provided in this version of CGSI are the Error Services
– part of the Error Services functionality [the Error Manager] is implemented as a CGS Desktop
application
– other Error Services functionality [the Error Server and Response Server] are implemented as
freestanding Unix processes
– Error Services functionality [the Error Reporter] are provided as a set of Ada libraries and C
objects.
Timestamp Services
The informal description and the formal specification of this interface are described in the Timestamp Services
section.
Error Services
The Error Services section details the interface to CGSI Error Services including a summary of the underlying
implementation. More detail concerning the Error Reporter, Error Server, Error Manager and Response Server,
mentioned above, can be found in this section. The formal specification of the provided interface is also detailed
in this section.
Not all of the services described in the subsections Calendar Services, Timestamp Services and Error Services
are required by all CGS products.

Space Infrastructure
4.6.1 Error Services
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
38 von/of: 662
The CGSI provided Error services are used for the reporting of warning/error mesages. A set of services are provided
as outlined in section 4.6.
Each CGS login starts a local Error Server. In addition, the NIS master server starts a special Error Server at
boot time.
Any CGS product which uses the Error Reporter starts a Response Server when invoked.
The CGS user may invoke the Error Manager application at any time from his Desktop.
The following sections provide an overview of the provided operations (section 4.6.1.2), the options available
(section 4.6.1.3), addressing, displaying and logging of error messages (sections 4.6.1.4, 4.6.1.5 and 4.6.1.5 respectively),
use of timestamps (section 4.6.1.7), the format of error messages (sections 4.6.1.8, 4.6.1.9, and
4.6.1.10) and, in general terms, the services should be used.
More detail concerning the actual implementation of the Error Report Package and the Error Service Package
can be found in sections 4.6.2 and 4.6.3 respectively.
Object code is made available to those products using the Error Services provided interface. This object code
implements the Error Reporter and consists of an Ada library and a number of C object files.
4.6.1.1 Definition of Terms
An error message is the complete collection of data (textual description, criticality, time of occurrence, etc.)
which describes the error which has occurred.
Certain elements of an error message may be predefined. These constitute an error message spec. This is the
form in which CGSI expects to find error messages in an assembly provided Error Message Database [section
NO TAG].
An error report is the act of invoking CGSI Error Services. The invoking process is then known as the reporting
process. The result of an error report is the broadcast of an error message on the network.
An error message mnemonic is a short text string used by the Error Reporter to index error message specs contained
in an Error Message Database [section NO TAG].
For the errors reported by a given reporting process, an error message number uniquely identifies each error
report.
4.6.1.2 Provided Operations
CGSI Error Services provides a single operation for the reporting of errors:
– report_error
This operation requires the following parameters to be supplied:
– an error message spec or an error message mnemonic, depending on the interface being used
(ad hoc or controlled) [section 4.6.1.3]
– the error message handling (log only or display and log) [section 4.6.1.5].
– the error message tags, as follows:
– the name of the assembly to which the reporting process belongs
– an assembly–specific set of parameters.
In addition, any of the following parameters may be supplied:
– the error message address (two components: user and node) [section 4.6.1.4]

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
39 von/of: 662
– an error message timestamp
– error message extra text [section 4.6.1.8].
This operation returns the following:
– the error message number [section 4.6.1.9].
CGSI Error Services provides an additional operation for determining the acknowledgement status of an error
report:
– acknowledgement_status
The invocation of this operation requires the following parameter to be supplied:
– an error message number.
This operation returns the following:
– acknowledged, not acknowledged or null status.
4.6.1.3 Reporting Options
CGSI Error Services provide a single operation for the reporting of an error message [report_error, section
4.6.1.2]. However, this operation is provided with two alternative interfaces, to provide flexibility.
The reporting process may choose to construct a complete error message spec, and pass this as a parameter.
This is known as ad hoc error reporting.
Alternatively, the reporting process can simply pass an error message mnemonic. In this case, the Error Reporter
must look up the appropriate error message spec in an Error Message Database, using the error message mnemonic
as an index. This is known as controlled error reporting.
Note: there is nominally one Error Message Database for each CGS assembly; any CGS assembly intending
to make use of controlled error reporting must provide the requisite Error Message Database
[see sections NO TAG and NO TAG].
4.6.1.4 Addressing the Error Message
The reporting process must specify who should receive the error message. The addressing parameter supplied
to the Error Reporter has two components: user and node.
The reporting process may specify a named user, a ”wild card” user or the default user. The default user is the
user logged in at the workstation on which the reporting process is executing.
The reporting process may specify a named node, a ”wild card” node or the default node. The default node is
the workstation on which the reporting process is executing.
If both the user and the node are specified, the error is reported to the specified workstation only if the specified
user is logged in at that workstation.
If a ”wild card” user is specified, the error is reported to the specified workstation regardless of who may be
logged in at that workstation.
If a ”wild card” node is specified, the error is reported to every workstation at which the specified user is logged
in.
If both user and node are specified as ”wild cards”, the error is reported to every workstation, regardless of who
may be logged in at each one.
4.6.1.5 Displaying and Logging the Error Message
The reporting process must specify how the error message is to be handled once it is received at an addressed
workstation.

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
40 von/of: 662
There are two options available. The Error Server can be instructed to simply log the error message on receipt.
Alternatively, the Error Server can be instructed to both log and display the error message on receipt. The option
is specified by a handling parameter.
Error Message Logging
At an addressed workstation, the Error Server logs a received error message by appending a line of text to a
session Error Log. The text corresponds to the constituent parts of the error message (text, severity, time of occurrence,
etc.). If the error message contains any extra text, this is also appended to the session Error Log (on
a separate line).
The session Error Log belongs to the user who is logged in at this workstation. Its name and location are specified
in section 4.6.5.1.1.
Note: a new session Error Log is opened whenever a user logs in to CGS.
Error Message Display
At an addressed workstation, CGSI displays a received error message [if appropriate] by writing a line of text
to the workstation screen. If the error message contains any extra text, this is also appended to the session Error
Log (on a separate line).
4.6.1.6 Central Logging
Every reported error message is automatically logged in a central Error Log.
There is always an Error Server present on the NIS master server. This particular Error Server ignores the addressing
and handling information contained in a broadcast error message, and simply logs every reported message.
4.6.1.7 Supplying a Timestamp
The reporting process may supply a timestamp applicable to the error being reported. If no timestamp is supplied,
CGSI generates its own timestamp from the system date and time obtained at the time that the reporting
process invokes Error Services.
If the reporting process does provide its own timestamp, then this should be obtained through the Calendar Services
interface [section NO TAG].
4.6.1.8 Supplying Extra Text
The reporting process may supply additional text applicable to the error being reported. This error message
extra text is supplied as an optional parameter.
The provision of additional text is particularly relevant to the use of the controlled interface for error reporting.
In this case, the error message spec is predefined (contained within an Error Message Database) – and consequently
the error message text is also predefined.
Extra text, on the other hand, is specified at the time the error is actually reported. Therefore the same error
message text can be reported many times, but each time with different error message extra text.
Typically, extra text will contain the text of an error message received by the reporting process from a commercial
product. The Error Message Database would then contain just one generic error message spec to cover all
errors received from this one commercial product.
4.6.1.9 Error Message Number
When CGSI Error Services are invoked for the reporting of an error, the Error Reporter returns an error message
number.

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
41 von/of: 662
In the case where the reported error requires to be acknowledged, the reporting process can then subsequently
use this number to determine the acknowledgement status of that error.
If the reported error does not require acknowledgement, this number is of no interest to the reporting process.
4.6.1.10 Error Message Components
An error message spec consists of the following components:
– an error message mnemonic
– a short text string uniquely identifying the error message spec within an Error Message Database
– by convention, the initial part of the string identifies the CGS assembly which may report the
error and the remainder of the string suffices to make the mnemonic unique within the Error
Message Database
– the error message severity
– fatal, severe, ordinary or advisory
– the error message text
– a text string containing a concise description of the error
– the error message supplementary text
– a text string containing further information about the error
An error message consists of the following components:
– the error message identifier
– consists of three components:
– the host name of the workstation on which the reporting process is executing
– the process id of the reporting process
– the error message number
– uniquely defines the error report within the network
– an error message spec
– the error message timestamp
– this can be either:
– the time that the error was detected by the CGS assembly to which the reporting process
belongs
– or:
– the time that the reporting process reported the error (by invoking CGSI Error Services)
– any error message extra text
– a text string containing information relevant to this despatch of the error message spec.
An error packet consists of the following components:
– an error message
– the error message handling
– log_only, log_and_display

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
42 von/of: 662
– the error message tag field
– the first tag specifies the CGS assembly to which the reporting process belongs
– the number and type of the remaining tags vary according to the CGS assembly specified in the
first tag (can be null)
– these tags, in conjunction with the error message severity (itself an implicit tag) are used by the
Error Manager to determine to which Error Message Windows (if any) to display the error
message
– the error message address
– consists of three components:
– the host name of the workstation to which the error is to be reported (can be a wild card)
– the user name of the CGS user to which the error is to be reported (can be a wild card).
4.6.1.11 Handling of Messages
When invoked by a reporting process, report_error performs the following actions:
– the host name of the workstation on which the reporting process is executing is retrieved from the OS
– the process id of the reporting process is retrieved from the OS
– a unique error message number is assigned to the reported error message
– this is a serial number, incremented at each error report
– the host name, process id, error message number together constitute the error message identifier, which
serves to identify the error report uniquely within the network
– if the controlled interface is being used, the error message spec corresponding to the provided error
message mnemonic is retrieved from the appropriate Error Message Database
– if the Error Message Database cannot be accessed for any reason, the exception
ERROR_MESSAGE_DATABASE_UNREADABLE is raised
– if the Error Message Database does not contain an error message spec with the mnemonic provided
by the caller, the exception NO_MATCHING_ERROR_MESSAGE_SPEC is raised
– if the ad hoc interface is being used, the error message spec is provided by the caller
– if no error message timestamp has been provided by the caller, one is constructed from the current system
time (obtained from the OS)
– an error message is constructed by combining the error message identifier and the error message spec
with the error message timestamp and any provided error message extra text
– the error message address is decomposed into a user name and a node name
– if the default user has been specified, the user name is set to the name of the owner of the reporting
process (by reference to the OS)
– if the default node has been specified, the node name is set to the name of the local host (by
reference to the OS)
– an error packet is constructed by combining the error message, the provided error message handling
(log only or log and display) and the error message address
– the error packet is broadcast on the network (using Broadcast RPC)
– if this broadcast operation fails, the exception ERROR_MESSAGE_BROADCAST_FAIL-
URE is raised
– the error message number is appended to the Response Log belonging to the reporting process

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
43 von/of: 662
– if the error message ack flag is ack required, the number is tagged with the status not acknowledged
– if the error message ack flag is ack not required, the number is tagged with the status null
status
– if this write operation fails, the exception RESPONSE_LOG_UNWRITEABLE is raised
– the error message number is returned.
Message Display
When a broadcast error packet is received by at the Message Window, the following actions are performed:
– if the user name is not a ”wild card”, it is checked, by reference to the OS, against the name of the owner
of the Error Manager (equality => success)
– if the user name is a ”wild card”, no check is made (i.e. implicit success)
– if the node name is not a ”wild card”, it is checked, by reference to the OS, against the name of the local
host (equality => success)
– if the node name is a ”wild card”, no check is made (i.e. implicit success)
– if either of the preceding checks fails, the Error Server rejects the error packet and no further processing
on it is performed
– if both the preceding checks are successful, the error message is extracted from the error packet and
the error message handling is inspected:
– if the error message handling is specified as LOG_ONLY, the error message is logged to the
user’s session Error Log
– if the error message handling is specified as LOG_AND_DISPLAY, the error message is
logged to the user’s session Error Log and displayed to the local workstation screen.
– the user may specify in the message display window a filter that specifies the various fields of an message.
Only those messages matching the filter will be displayed.
– if the severity level equals or exceeds ’severe’, or the acknowledge flag is given,
the workstation beeps
Message Logging
– the user’s name is used to locate the user’s session Error Log
– the session Error Log is located within the user’s home directory
– if the user’s home directory cannot be accessed, logging is abandoned at this point

Space Infrastructure
4.6.2 Error Report Package
Informal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
See section 4.6.1 for a general description of the TLUI provided Error Services.
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
44 von/of: 662
The functions and procedures in this package are internal to CGSI. The package is included in the CGSI ICD
because it is required by the Error Services Package (see section 4.6.3).

Space Infrastructure
Formal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
45 von/of: 662
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– err_report_.a
––
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– ABSTRACT
–– ––––––––
––
–– This file contains the body of the Ada package report_pks.ada
––
–– IDENTIFICATION
–– ––––––––––––––
––
–– Assembly Name : CGSI
–– Product Name : CGS Top Level User Interface
–– CI Number : 1234 916
–– Hood Object : Error_Reporter
––
–– CHARACTERISTICS
–– –––––––––––––––
––
–– Compiler : Alsys Ada Compiler, HP 9000 HP–UX, Version B2425A.05.25
–– Language : Ada
–– Target Machine : HP 9000
–– Target Operating System : HP–UX 9.0
–– Machine Dependencies : [NONE]
–– Compiler Dependencies : [NONE]
–– External Dependencies : [NONE]
–– Data Environment : [NONE]
–– Device Input : [NONE]
–– Device Output : [NONE]
––
–– CHANGE HISTORY
–– V3.1 at Central Repository at DASA RI (CGS V3 development)
–– creator: athmann (on host vicos2s)
–– creation date: 02.11.94 18:05:12
–– comment:
–– Remove Acknowledgement service (Response Service)
–– acc. to COL–RIBRE–CGSI–IRN–2204.
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V2.3 at ERNO ; VICOS AIV
–– creator: aivroot (on host vim_1)
–– creation date: 01.12.93 18:50:31
–– comment:
–– DERIVED FROM 2.1/cgsi_01_SRO_1234916j
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V2.2 at ERNO;CGS Central Repository (development)
–– creator: cgstest (on host vicos_4)
–– creation date: 08.09.93 17:58:09
–– comment:
–– modified for delivery to AIV (CGSI V2.0.3)
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– ––––––––––––––
––
–– END HISTORY
–– –––––––––––
––
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
with A_STRINGS;
package ERR_REPORT is

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
PROCESS_ID_MAX : constant := 99999;
ERROR_MESSAGE_NUMBER_MAX : constant := 99999;
ERROR_MESSAGE_MNEMONIC_LEN : constant := 16;
ERROR_MESSAGE_TEXT_LEN : constant := 80;
ERROR_MESSAGE_SUPP_TEXT_LEN : constant := 255;
ERROR_MESSAGE_EXTRA_TEXT_LEN : constant := 80;
ERROR_MESSAGE_TIMESTAMP_LEN : constant := 20;
subtype PROCESS_ID is INTEGER range 1..PROCESS_ID_MAX;
subtype ERROR_MESSAGE_NUMBER is INTEGER range 1..ERROR_MESSAGE_NUMBER_MAX;
subtype ERROR_MESSAGE_MNEMONIC is STRING (1..ERROR_MESSAGE_MNEMONIC_LEN);
type ERROR_MESSAGE_SEVERITY is
(FATAL,
SEVERE,
ORDINARY,
ADVISORY);
subtype ERROR_MESSAGE_TEXT is STRING (1..ERROR_MESSAGE_TEXT_LEN);
subtype ERROR_MESSAGE_SUPP_TEXT is STRING (1..ERROR_MESSAGE_SUPP_TEXT_LEN);
type CGS_ASSEMBLY is
(SDE,
CGSI,
VICOS,
MPS,
CSS,
ALL_ASSEMBLIES);
subtype VICOS_TEST_NODE is A_STRINGS.A_STRING;
subtype VICOS_GROUP_NAME is A_STRINGS.A_STRING;
type VICOS_TAG_FIELD is record
test_node : VICOS_TEST_NODE;
group_name : VICOS_GROUP_NAME;
end record;
type ERROR_MESSAGE_TAG_FIELD (assembly : CGS_ASSEMBLY) is record
case assembly is
when VICOS => vicos_tags : VICOS_TAG_FIELD;
when others => null;
end case;
end record;
–– dummy (obsolete); kept to leave interface unchanged
type ERROR_MESSAGE_ACK_FLAG is (ACK_NOT_REQUIRED,ACK_REQUIRED);
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
46 von/of: 662
subtype ERROR_MESSAGE_EXTRA_TEXT is STRING (1..ERROR_MESSAGE_EXTRA_TEXT_LEN);
subtype ERROR_MESSAGE_TIMESTAMP is STRING (1..ERROR_MESSAGE_TIMESTAMP_LEN);
type ERROR_MESSAGE_HANDLING is
(LOG_ONLY,
LOG_AND_DISPLAY);
subtype USER_NAME is A_STRINGS.A_STRING;
subtype NODE_NAME is A_STRINGS.A_STRING;
type ERROR_PACKET (assembly : CGS_ASSEMBLY) is record
source_node : NODE_NAME; –– ERROR_MESSAGE_SOURCE
source_pid : PROCESS_ID; –– ERROR_MESSAGE_SOURCE
error_number : ERROR_MESSAGE_NUMBER; –– ERROR_MESSAGE_SOURCE
error_mnemonic : ERROR_MESSAGE_MNEMONIC; –– ERROR_MESSAGE_SPEC
error_severity : ERROR_MESSAGE_SEVERITY; –– ERROR_MESSAGE_SPEC
error_text : ERROR_MESSAGE_TEXT; –– ERROR_MESSAGE_SPEC
error_supp_text : ERROR_MESSAGE_SUPP_TEXT; –– ERROR_MESSAGE_SPEC
error_handling : ERROR_MESSAGE_HANDLING; –– ERROR_MESSAGE_HANDLING
error_tag_field : ERROR_MESSAGE_TAG_FIELD (assembly); –– ERROR_MESSAGE_TAG_FIELD
error_timestamp : ERROR_MESSAGE_TIMESTAMP; –– ERROR_MESSAGE_TIMESTAMP
error_extra_text : ERROR_MESSAGE_EXTRA_TEXT; –– ERROR_MESSAGE_EXTRA_TEXT
addressed_user : USER_NAME; –– ERROR_MESSAGE_ADDRESS
addressed_node : NODE_NAME; –– ERROR_MESSAGE_ADDRESS
end record;
type ERROR_PACKET_PTR is access ERROR_PACKET;
NULL_TEXT : constant ERROR_MESSAGE_TEXT := (others => ’ ’);
NULL_SUPP_TEXT : constant ERROR_MESSAGE_SUPP_TEXT := (others => ’ ’);

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
NULL_EXTRA_TEXT : constant ERROR_MESSAGE_EXTRA_TEXT := (others => ’ ’);
NULL_MNEMONIC : constant ERROR_MESSAGE_MNEMONIC := (others => ’ ’);
NULL_TIMESTAMP : constant ERROR_MESSAGE_TIMESTAMP := (others => ’ ’);
function to_user (s : STRING) return USER_NAME renames A_STRINGS.to_a;
function to_node (s : STRING) return NODE_NAME renames A_STRINGS.to_a;
WILD_CARD_USER : constant USER_NAME := to_user (”*”);
WILD_CARD_NODE : constant NODE_NAME := to_node (”*”);
type ERROR_MESSAGE_ACK_STATUS is
(NULL_STATUS,
NOT_ACKNOWLEDGED,
ACKNOWLEDGED);
procedure despatch_error (error_pkt : ERROR_PACKET_PTR);
UNABLE_TO_DESPATCH_ERROR : exception;
end ERR_REPORT;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
47 von/of: 662

Space Infrastructure
4.6.3 Error Services Package
Informal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
See section 4.6.1 for a general description of the TLUI provided Error Services.
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
48 von/of: 662

Space Infrastructure
Formal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
49 von/of: 662
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– error_services_.a
––
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– ABSTRACT
–– ––––––––
––
–– This file contains the spec of the Ada package ERROR_SERVICES
––
–– IDENTIFICATION
–– ––––––––––––––
––
–– Assembly Name : CGSI
–– Product Name : CGS Top Level User Interface
–– CI Number : 1234 916
–– Hood Object : Error_Reporter
––
–– CHARACTERISTICS
–– –––––––––––––––
––
–– Compiler : Alsys Ada Compiler, HP 9000 HP–UX, Version B2425A.05.25
–– : SUN Ada 1.1
–– Language : Ada
–– Target Machine : HP 9000
–– Target Operating System : HP–UX A.08.02 / SUN OS 4.1.3
–– Machine Dependencies : [NONE]
–– Compiler Dependencies : [NONE]
–– External Dependencies : [NONE]
–– Data Environment : [NONE]
–– Device Input : [NONE]
–– Device Output : [NONE]
––
–– CHANGE HISTORY
–– V4.1 at Central Repository at DASA RI
–– creator: schipper (on host ada_s)
–– creation date: 05.07.96 13:49:44
–– comment:
–– Solaris Port
––
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V3.1 at Central Repository at DASA RI (CGS V3 development)
–– creator: athmann (on host vicos2s)
–– creation date: 02.11.94 18:06:13
–– comment:
–– Remove Acknowledgement service (Response Service)
–– acc. to COL–RIBRE–CGSI–IRN–2204:
–– – remove function acknowledgment_status
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V2.3 at ERNO ; VICOS AIV
–– creator: aivroot (on host vim_1)
–– creation date: 01.12.93 18:51:23
–– comment:
–– DERIVED FROM 2.1/cgsi_01_SRO_1234916j
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V2.2 at ERNO;CGS Central Repository (development)
–– creator: cgstest (on host vicos_4)
–– creation date: 08.09.93 18:00:24
–– comment:
–– modified for delivery to AIV (CGSI V2.0.3)
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– ––––––––––––––

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
50 von/of: 662
––
–– END HISTORY
–– –––––––––––
––
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
with Err_report;
package Error_services is
SPEC_VERSION : constant STRING := ”@(#) ERROR_SERVICES 4.3.1 spec”;
type Error_message_spec is record
Error_mnemonic : Err_report.Error_message_mnemonic;
Error_severity : Err_report.Error_message_severity;
Error_text : Err_report.Error_message_text;
Error_supp_text : Err_report.Error_message_supp_text;
Error_ack_flag : Err_report.Error_message_ack_flag; –– dummy (obsolete)
end record;
type Scope_of_target_user is
(Default_user,
Named_user);
type Scope_of_target_node is
(Default_node,
Named_node);
type Target_user (Scope : Scope_of_target_user := Default_user) is record
case Scope is
when Default_user => null;
when Named_user => Name : Err_report.User_name;
end case;
end record;
type Target_node (Scope : Scope_of_target_node := Default_node) is record
case Scope is
when Default_node => null;
when Named_node => Name : Err_report.Node_name;
end case;
end record;
type Error_message_source is record
Source_node : Err_report.Node_name;
Source_pid : Err_report.Process_id;
Error_number : Err_report.Error_message_number;
end record;
procedure Report_error
(Error_spec : in Error_message_spec;
Handling : in Err_report.Error_message_handling;
Tags : in Err_report.Error_message_tag_field;
User : in Target_user := (Scope => Default_user);
Node : in Target_node := (Scope => Default_node);
Timestamp : in Err_report.Error_message_timestamp :=
Err_report.Null_timestamp;
Extra_text : in Err_report.Error_message_extra_text :=
Err_report.Null_extra_text;
Error_number : out Err_report.Error_message_number);
procedure Report_error
(Error_mnemonic : in Err_report.Error_message_mnemonic;
Handling : in Err_report.Error_message_handling;
Tags : in Err_report.Error_message_tag_field;
User : in Target_user := (Scope => Default_user);
Node : in Target_node := (Scope => Default_node);
Timestamp : in Err_report.Error_message_timestamp :=
Err_report.Null_timestamp;
Extra_text : in Err_report.Error_message_extra_text :=
Err_report.Null_extra_text;
Error_number : out Err_report.Error_message_number);

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
51 von/of: 662
function Send
(User : in String := ””; –– Empty is filled with the same user, * is all
Host : in String := ””; –– Empty is filled with localhost, * is broadcast
Handling : in Boolean := TRUE; –– Display the message (not only log it).
Assembly : in Err_report.CGS_ASSEMBLY;
Source : in String := ””; –– VICOS node / application
Group : in String := ””; –– VICOS group ???
Class : in Err_report.ERROR_MESSAGE_SEVERITY := Err_report.ORDINARY;
Timestamp : in String := ””; –– Empty is filled with actual local time
Mnemonic : in String := ””; –– Look for message in a database
Text : in String; –– The message !
Extra_text : in String := ””;
Support_text : in String := ””;
Ack_flag : in Boolean := FALSE)–– Application wants acknowledge
return Integer; –– the error number, unique per UNIX process
function Acknowledgement_status
(Host : in String := ””;
error_number : in Integer)
return ERR_REPORT.ERROR_MESSAGE_ACK_STATUS;
function TO_SEVERITY (CHECKOUT_TYPE : in STRING) return ERR_REPORT.ERROR_MESSAGE_SEVERITY;
–– DESCRIPTION
–– Converts the Checkout log/error type to error services severity class.
–– The conversion is
–– VICOS_DEFINITIONS.INFO_MESSAGE_TYPE : ERR_REPORT.ADVISORY
–– VICOS_DEFINITIONS.GENERAL_MESSAGE_TYPE : ERR_REPORT.ADVISORY
–– VICOS_DEFINITIONS.ERROR_MESSAGE_TYPE : ERR_REPORT.ORDINARY
–– VICOS_DEFINITIONS.WARNING_MESSAGE_TYPE : ERR_REPORT.ADVISORY
–– VICOS_DEFINITIONS.EXCEPTION_MESSAGE_TYPE: ERR_REPORT.SEVERE
–– VICOS_DEFINITIONS.ALARM_MESSAGE_TYPE : ERR_REPORT.FATAL
–– any other string : ERR_REPORT.ADVISORY
Error_message_database_unreadable : exception;
No_matching_error_message_spec : exception;
Error_message_broadcast_failure : exception;
No_matching_error_number : exception;
end Error_services;

Space Infrastructure
4.6.4 Timestamp Services Package
Informal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
52 von/of: 662
An operation is provided which converts the current system time (obtained through a call to the operation
date_and_time_now) to a fixed length string:
– time_stamp_str
The returned string has the following format:
– YYYYMmm DD hh:mm:ss
This is the format required, for example, of a timestamp in the TLUI provided Error Services interface.
Object code is made available to those products using the Timestamp Services provided interface.

Space Infrastructure
Formal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
53 von/of: 662
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– timestamp_pks.ada
––
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– ABSTRACT
–– ––––––––
––
–– This file contains the body of the Ada package timestamp_pks.ada
––
–– IDENTIFICATION
–– ––––––––––––––
––
–– Assembly Name : CGSI
–– Product Name : CGS Top Level User Interface
–– CI Number : 1234 916
–– Hood Object : Calendar
––
–– CHARACTERISTICS
–– –––––––––––––––
––
–– Compiler : Alsys Ada Compiler, HP 9000 HP–UX, Version B2425A.05.25
–– Language : Ada
–– Target Machine : HP 9000
–– Target Operating System : HP–UX A.08.02
–– Machine Dependencies : [NONE]
–– Compiler Dependencies : [NONE]
–– External Dependencies : [NONE]
–– Data Environment : [NONE]
–– Device Input : [NONE]
–– Device Output : [NONE]
––
–– CHANGE HISTORY
–– V3.1 at Central Repository at DASA RI (CGS V3 development)
–– creator: reproot (on host vicos_4)
–– creation date: 05.07.95 21:16:50
–– comment:
–– transfered from version 2.3
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V2.3 at ERNO ; VICOS AIV
–– creator: aivroot (on host vim_1)
–– creation date: 01.12.93 18:53:22
–– comment:
–– DERIVED FROM 2.1/cgsi_01_SRO_1234916j
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V2.2 at ERNO;CGS Central Repository (development)
–– creator: cgstest (on host vicos_4)
–– creation date: 08.09.93 18:06:06
–– comment:
–– modified for delivery to AIV (CGSI V2.0.3)
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– ––––––––––––––
––
–– END HISTORY
–– –––––––––––
––
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
with CGS_CALENDAR;
package TIMESTAMP is
TIME_STAMP_LEN : constant := 20;

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
54 von/of: 662
subtype TIME_STAMP is STRING (1..TIME_STAMP_LEN);
function time_stamp_str (date_and_time : in CGS_CALENDAR.CGS_DATE_AND_TIME) return
TIME_STAMP;
end TIMESTAMP;

Space Infrastructure
4.6.5 File Information
4.6.5.1 File Names and Locations
4.6.5.1.1 Session Error Log
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
55 von/of: 662
CGSI creates a Session Error Log which is found in the directory $CGS_HOME/data/log under the following
name:
– ..log
– is the host name of the workstation at which the user is logging in
– is specified n
4.6.5.1.2 Process Response Log
CGSI creates a log of all responses (Acks) which is found in the directory $CGS_HOME/data/log under the
following name:
– ..ack
– is the host name of the workstation at which the user is logging in
– is specified n

Space Infrastructure
4.6.6 Installation Registry
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
56 von/of: 662
CGS (CGSI) provides an interface to enter or update entries in a specific registry table, called Version ID Table.
It allows for registering a software item (e.g. version of a software package, a patch or update etc)
The table is located in the $GSAF_HOME file system and is owned by the CGS Administrator user.
A program vit_manager is available under $CGSI_HOME/bin/sun5 which can be called on any SUN node
having visibility to $GSAF_HOME as the CGS Administrator user with the following parameters:
Version ID Table Manangement: List or modify the Version ID Table (VIT).
vit_manager –help | –list | –upd_item |
–add_item | –del_item |
–query {|ALL} [–format format–list]
Parameters:
–help
–– get help info
–list
–– List the contents of the VIT
–upd_item
–– update of with . Entry is tametagged with actual time.
–upd_entry
–– update of with . Entry is tametagged with actual time.
–add_item
–– Add a new entry (at the bottom) to the VIT. Entry is tametagged with actual time.
–del_item
–– Delete the entry with name = from the VIT
–query |ALL [–format format–list]
–– query the VIT for a given SW item/product or all items
–– the output can be formatted according to an optional format–list
–– format–list must be a single parameter with a comma
–– or blank separated list of format identifier
–– legal format identifier are
–– product,version,host,date,time,path
where :
: Name of SW item (max. 20 characters)
may be
’SW_ITEM’ : Name of SW item (max. 20 characters)
’VERSION’ : Version of SW item (max. 20 characters)
’HOST’ : Host where SW item is installed (max. 20 characters)
’PATH’ : Directory where SW item is installed (max. 255 characters)
: Number of entry in the VIT Table

Space Infrastructure
4.7 Other Commercial Products Version
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
57 von/of: 662
This section specifies the versions and revision levels of other commercial software products used within a CGS
version.
Note 1: The compilers used for development of CGS are listed to describe the development baseline, neglecting
the fact that the items are not included in the CGSI product.
Product Platform Commercial Product Version
Development SUN VADSself (RATIONAL) 6.2.3d
Products incl. Ada XVIEWS Bindings
XView Runtime System patch
(COL–RIBRE–SRO–119)
SUN Sun (ANSI C) Compiler 4.2
SUN VisualWorks 3.0
SUN MATRIXx 4.1
SUN SAMMI 3.0.12 (***)
HP Alsys Ada (Thompson Prod.) 5.5.4
plus patches:
0062V554–U1
0062V554–U2
0062V554–U3
0062V554–U4
0062V554–G1
HP HP C–Compiler (ANSI–C)
FORCE VADSself (RATIONAL) 6.2.3c plus
Patch 81275
FORCE SUN (ANSI–C) Compiler 3.0.1
Runtime Products SUN NTP Version 3 (*)
HP NTP Version 3 (**)
SUN TCL 7.5 (****)
SUN TCLX 7.5.2 (****)
SUN TK 4.1 (****)
SUN oratcl 2.4b3 (****)
(*) Products so marked are an integral part of SOLARIS (Solaris 2.6 Server)
(**) Products so marked are an integral part of HP–UX
(***) Products so marked require runtime licenses for RTE and FE parts
(****) Tcl/Tk is delivered as part of the CGS installation; no license is required

Space Infrastructure
4.8 CGS_Library
4.8.1 Informal Interface
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
58 von/of: 662
The CGS_Library is a set of re–usable Ada packages that provide services in the following areas:
– Abstract Data Types
Ada Type definitions and Utility packages These packages provide re–usable implementation of data
structures such as lists, stacks, maps, tables, streams, sets, queues, buffers, strings, time etc.
– Operating System Interface in Ada.
The interface to selected UNIX services is provided
– Mathematical Services
Mathematical packages providing operations on elements such as matrix and complex numbers are provided.
4.8.2 Formal Interface
For the formal definition of the packages refer to AD 2.1.4.1 .

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
CHAPTER 5 :
SOFTWARE
DEVELOPMENT
INTERFACES
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
59 von/of: 662

Space Infrastructure
5.1 Documentation Format
Informal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
60 von/of: 662
This interface defines the conventions that the external documents must follow in order for the SDE to be able
to incorporate them into its data bank and thereby put them under version control.
The conventions can be divided into three categories: format, location and filename conventions.
The format conventions contain mandatory and optional conventions. The mandatory format conventions specify
general format conventions (ie the document must be in TPS ASCII format) and, in case of book and binder
documents, the organisation of the documents. The optional format conventions specify a number of DOCT
component conventions that must be followed if the tables of contents of the target document must include items
from the imported document.
The filename conventions specifies the name and directory conventions that the document file(s) must follow.
The location conventions specify where the document files must be located.
If a document meets the above mentioned conventions, then it is possible within the SDE to incorporate it into
the SDE data bank.
Documents will be imported into the SDE database via the DOCT MMI.
Documents to be imported can be located anywhere in the file system. Via the DOCT MMI, the user can copy
these documents into the clipboard and then from the clipboard into an existing IPSE controlled book or binder
and notify the IPSE that the documents have been pasted. The IPSE will then read the contents of the book or
binder, create corresponding objects in the SDE data bank, if necessary, and read in the new document contents.
In any case, the IPSE MMI forbids the pasting of documents in a checked–in document object. This implies that
the document must be checked–out if pasting is required.
Formal Interface Description
The conventions for documents format, document location and document file names are described in applicable
document 2.1.5.4.

Space Infrastructure
5.1.1 Format of Imported Documents
5.1.1.1 Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
61 von/of: 662
This interface describes the conventions that documents must followed in order to be imported into a SDE document.
These conventions can be summarized as follows:
• Documents must comply with the Interleaf ASCII format and file naming conventions.
• In addition to this, the templates for standard SDE Interleaf documents will define (in Interleaf catalogues)
the masters for a pre–defined set of components in order to:
• comply with the lay-out style in the rest of the book, concerning for instance page headers and
footers and section headers;
• define section headers and other items that will later be inserted in the ”tables of contents” of
the Interleaf book (via the normal Interleaf facilities)
5.1.1.2 Interface Definition
5.1.1.2.1 Document Location Conventions
A document which is to be imported shall be located in an existing directory in the file system.
5.1.1.2.2 Document Filename Conventions
In this section, the following definition applies: An importable document is either an Interleaf BOOK, an Interleaf
BINDER, an Interleaf DOCUMENT or an Interleaf CATALOGUE. The BOOK, BINDER, DOCUMENT
and CATALOGUE shall have file names as described in AD [2.1.5.4].
The user must have read access to all document files which are to be imported.
The structure of importable documents must comply with the following definition:
• A document which is of Interleaf BOOK type shall contain zero or more sub–BOOKs, zero or more
BINDERs, zero or more CATALOGUEs and zero or more DOCUMENTs
• A document which is of type Interleaf type BINDER shall contain zero or more sub–BINDERs and zero
or more CATALOGUEs
• A document which is of type INTERLEAF CATALOGUE shall contain one or more COMPONENTs.
This is further described below.
• A document which is of Interleaf type DOCUMENT shall contain one or more COMPONENTs. This
is further described below.
There must not exist a cyclic containment relation between BOOKs and sub–BOOKs and between BINDERs
and sub–BINDERs. This means that a BOOK must not contain (a reference to) itself through any of its sub–
BOOKs (Interleaf permits cyclic containment, through UNIX soft links, of containers in general because a container
is implemented as a UNIX directory). A similar restriction holds for BINDERs.
5.1.1.2.3 Importable DOCUMENT Contents
The contents of DOCUMENTS and BINDERS to be imported in SDE documents shall comply to the format
defined in AD [2.1.5.4].

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
62 von/of: 662
In addition, all chapter and section header components in a DOCUMENT that are meant to be inserted in the
”table of contents” documents shall obey the following restrictions:
All appendix and sub–appendix headers that are meant to be inserted in the ”table of contents” document shall
be TPS components with one of the following names:
All figures and headers that are meant to be inserted in the ”table of figures” document shall be TPS components
with one of the following names:
All tables that are meant to be inserted in the ”table of tables” document shall be TPS components with the following
name:
The following TPS frame shall be used to establish the header and footer of the document:
Except for , each provided Interleaf master component whose name can be found in the lists above
defines a name for the associated ”table of contents” document. An instance of the predefined master component
will be written to this document upon user request (the TOC generation operation). The component’s associated
”table of contents” document is defined through the value of the component’s TOC Doc Name property field
of its Custom sheet for the component’s property sheet. For any of the predefined masters the value for the
TOC Doc Name property field is one of: contents, figures and tables.
The names of all other components which are not meant to be inserted into the above mentioned documents shall
be different from those listed above and each component’s TOC Doc Name property field shall be distinct from
any of the a.m. TOC Doc Name values.
The masters for all the components listed in this section will be provided in a catalogue within each of the standard
SDE document templates.

Space Infrastructure
5.2 Generic Compiler Interface
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
63 von/of: 662
This chapter comprises interfaces which are used if new compiler environments for Ada or C are to be integrated
into the SDE. The aim is to allow a compiler environment integrator to implement commands on top of any compiler
system to be integrated into the SDE such that an SDE user may be able to utilize these compiler systems
without being forced to leave the SDE. Thereby input as well as output data shall be version controlled on user
request.
An integrator will implement specified commands externally to the SDE such that this SDE external interface
will consist of a specific ’generic’ command protocol (language) whichs syntax and semantic is known by the
SDE.
5.2.1 Generic C Compiler Environment Integration Interface
See applicable document 2.1.5.1.
5.2.2 Generic Ada Compiler Environment Integration Interface
See applicable document 2.1.5.2.

Space Infrastructure
5.3 Generic Tool Interface
Informal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
64 von/of: 662
This section comprises interfaces which are used if new tools/commercial software are to be integrated into the
SDE. The aim is to allow a tool integrator to implement commands on top of any tool to be integrated into the
SDE such that an SDE user may be able to utilize these tools without being forced to leave the SDE. Thereby
input as well as output data shall be version controlled on user request.
An integrator will implement specified commands externally to the SDE such that this SDE external interface
will consist of a protocol (language) whichs syntax and semantic is known by the SDE.
Formal Interface Description
See applicable document 2.1.5.3.

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
CHAPTER 6 :
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
65 von/of: 662
MISSION PREPARATION
INTERFACES

Space Infrastructure
6.1 Package MPS_DEFINITIONS
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
66 von/of: 662
Please note that this package is not allowed outside CGS by other Products than CMAS !!!
6.1.1 Exceptions
6.1.1.1 Exceptions due to internal MDB / ORACLE errors
– MDB_ERROR
This exception is raised if an operation cannot be completed because of an internal error in MPS–provided
procedures
– ORACLE_ERROR
This exception is raised if an operation cannot be completed because of a malfunction of the Oracle
DBMS (e.g. database is not available)
6.1.1.2 SID_ERROR
The SID does not exist in the current context, i.e. within the scope of the currently selected CCU version. The
CCU version is specified by the procedure MDB_SESSION.SET_LOCAL_DEFAULT.
All procedures having the ‘in parameter’ SID can raise this exception.
6.1.1.3 AUTHORIZATION_ERROR
This exception is raised if an operation cannot be executed due to the fact that a user
has insufficient privilege.
In general this exception is raised if
– the user is not owner of the item specified by SID
– the status of the item is FROZEN
– the status of the item is REVIEW and the user has no configuration management privilege
6.1.1.4 USE_ERROR
This exception is raised if an operation is incorrect in the current context.
Examples:
* try to call procedures without being connected to the MDB
* try to open the MDB when it is already open
6.1.1.5 ENVIRONMENT_ERROR , CDU/CCU_ERROR
– ENVIRONMENT_ERROR
This exception is raised if an operation cannot be completed because of wrong or invalid mission–,system
tree–, flight–configuration– identifiers.
– CDU_ERROR
This exception is raised if an operation cannot be completed because of wrong or invalid CDU/ CDU–
version identifiers
– CCU_ERROR
This exception is raised if an operation cannot be completed because of wrong or invalid CCU/CCU–
version identifiers

Space Infrastructure
6.1.1.6 PARAMETER_ERROR
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
67 von/of: 662
This exception is raised if an operation cannot be completed because of wrong or invalid input parameter
(in all cases where the input parameter is not related to SID’s, CDU’s, CCU’s or Environment)
6.1.1.7 CONSISTENCY_ERROR
This exception is raised if an attempt is made to access an item that is in an ”inconsistent” state (i.e. doesn’t
satisfy the predefined integrity/consistency rules)

Space Infrastructure
6.1.2 Formal Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– MPS_DEFINITIONS
––
–– This package contains all MPS specific types and definitions used by CGS
–– in addition to the standard ADA types.
––
–– Unit : Package specification
––
–– Special features : The package NUMERIC_TYPES is directly visible
–– because the ’use’ clause is used.
––
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– History of changes
––
–– Authorizing document : COL–CGS–IRN–3020B
–– Date : May 1995
–– Change summary : – Introduction of HLCL sequences,
–– – Introduction of exception LOCKING_PROBLEM
–– – Simplification of the header
–– – Introduction of CSS specific SW type
–– definition
–– – Introduction of CGS spcific end item type
–– definitions
–– – Deletion of unused EGSE end item types
–– Author : E. Herrmann
––
–– Authorizing document : COL–RIBRE–IRN–CGS–4002
–– Date : Feb 1996
–– Change summary : CGS V3.1 Baseline definition:
–– CPL & SW Commanding
–– Authors : F.Kruse, A.Werkman, C.Seelhorst
––
–– Authorizing document : COL–RIBRE–IRN–CGS–4002a
–– Date : July 1996
–– Change summary : Use T_SW_VALUE instead of T_SW_SCALAR_VALUE
–– in T_FORMAL_PARAMETER, introduce new type
–– T_SW_VALUE_STREAM.
–– Add ASSIGN for T_SW_VALUE
–– and DEALLOCATE for T_ACCESS_SW_VALUE.
–– Add support for ADT_PACKING mechanism :
–– provide procedures PACK and UNPACK
–– and function SIZE_NEEDED.
––
–– Authorizing document : COL–RIBRE–IRN–CGS–4002b
–– Date : September 1996
–– Change summary : Initialize type T_ENGINEERING_UNIT with
–– default values
–– Authors : A. Werkman
––
–– Date : May 1997
–– Change summary : Remove Fault Management related types
–– Authors : W. St.Luce
––
––
–– Authorizing document : PIRN–7064
–– Date : 02.02.1998
–– Change summary : Procedures
–– DEALLOCATE(GARBAGE :
–– in out T_ACCESS_FORMAL_PARAMETER)
–– and
–– CLEAR(STREAM : in out T_FORMAL_PARAMETER_LIST)
–– inserted
–– Author : I. Lenz
––
–– Authorizing document : COL–RIBRE–IRN–8079
–– Date : 03.08.1999
–– Change summary : Add new end item types EGSE_XXX_DERIVED_VALUE
–– Author : I. Lenz
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
68 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
––
––
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Repository History tracking:
––
–– HISTORY
––
–– #IRN: COL–RIBRE–IRN–CGS–4002 : CGS V3.1 Baseline definition
–– #IRN: COL–RIBRE–IRN–CGS–4002a : change in T_FORMAL_PARAMETER
–– #IRN: COL–RIBRE–IRN–CGS–4002b : change in type T_ENGINEERING_UNIT
–– #IRN: COL–RIBRE–IRN–CGS–5007 : add constants for bytestream/eng. valuetype
–– #IRN: COL–RIBRE–IRN–CGS–6002 : add ASSIGN procedure for T_SW_TYPE_DESCR
–– add type EGSE_BINARY_PACKET
–– #IRN: COL–RIBRE–IRN–CGS–7005 : remove fault management related types
–– New enditem type: Response Packet
–– New domain: USER_DEF_SIDS
––
–– END HISTORY
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
with STATIC_STRINGS;
with DYNAMIC_STRINGS;
with STREAMS;
with LIMITED_STREAMS;
with STRING_POINTERS;
with UNITS;
with ADT_PACKING;
with NUMERIC_TYPES; use NUMERIC_TYPES;
––––––––––––––––––––––––––––––––––––––––––
package MPS_DEFINITIONS is
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– EXCEPTIONS
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Exceptions due to internal MDB / ORACLE errors:
ORACLE_ERROR, –– This exception is raised if an operation cannot be
–– completed because of a malfunction of the Oracle
–– DBMS (e.g. database is not available)
MDB_ERROR, –– This exception is raised if an operation cannot be
–– completed because of an internal error in
–– MDA–provided procedures
CONSISTENCY_ERROR, –– This exception is raised if an attempt is made to
–– access an item that is in an ”inconsistent” state
–– (i.e. doesn’t satisfy the predefined integrity or
–– consistency rules)
–– Exceptions due to illegal or incorrect use of provided procedures:
USE_ERROR, –– This exception is raised if an operation is
–– incorrect in the current context.
–– Examples:
–– * try to call procedures without being connected
–– to the MDB
–– * try to open the MDB when it is already open
–– * try to close the MDB without being connected
–– * try to call READ_ITEM procedure where the
–– item–type of the sid doesn’t match.
–– * try to call STORE_ITEM without calling
–– LOCK_ITEM previously
SID_ERROR, –– This exception is raised if the MDB item denoted by
–– the SID doesn’t exist in the current context,
–– i.e. within the scope of the currently selected CCU
–– version.
AUTHORIZATION_ERROR, –– This exception is raised if an operation cannot be
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
69 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–– executed because of the fact that a user has
–– insufficient privileges
–– Examples:
–– * try to lock an item for update purposes which
–– is in a frozen CDU version
–– * try to lock an item which the status REVIEW
–– without having configuration management
–– privilege.
–– * try to lock an item for update purposes which
–– belongs to another user
PARAMETER_ERROR, –– This exception is raised if an operation cannot be
–– completed because of wrong or invalid input
–– parameter (in all cases where the input parameter
–– is not related to SID’s, CDU’s, CCU’s or
–– Environment)
ENVIRONMENT_ERROR, –– wrong element, mission or systemtree version
–– identifier
CCU_ERROR, –– wrong or invalid CCU/,CCU–version identifier
CDU_ERROR, –– wrong or invalid CDU/, CDU–version identifier
LOCKING_PROBLEM –– Some procedures of the packages MDB_UCL
–– and MDB_WDU_GROUND have to re–lock the updated
–– and committed item.
–– If this lock fails because item is locked
–– by another user the exception LOCKING_PROBLEM is
–– raised.
: exception;
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Types and Constants :
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–––––––––––––––––––––––––––––––––––––––––––
–– strings
–––––––––––––––––––––––––––––––––––––––––––
type DYNAMIC_STRING is new DYNAMIC_STRINGS.DYNAMIC_STRING;
package STATIC_STRINGS80 is new STATIC_STRINGS(80);
type STATIC_STRING80 is new STATIC_STRINGS80.STATIC_STRING;
package STATIC_STRINGS256 is new STATIC_STRINGS(256);
type STATIC_STRING256 is new STATIC_STRINGS256.STATIC_STRING;
package STATIC_STRINGS1024 is new STATIC_STRINGS(1024);
type STATIC_STRING1024 is new STATIC_STRINGS1024.STATIC_STRING;
–––––––––––––––––––––––––––––––––––––––––––
–– byte stream
–––––––––––––––––––––––––––––––––––––––––––
package BYTE_STREAMS is new STREAMS (BYTE,
BYTE_ARRAY);
type T_BYTE_STREAM is new BYTE_STREAMS.STREAM;
–– using this type in other packages there must be specified
–– the average number of items(BYTE) for space allocation purposes
–– Example:
–– subtype MY_BYTE_STREAM is MPS_DEFINITIONS.T_BYTE_STREAM(20)
–––––––––––––––––––––––––––––––––––––––––––
–– character stream
–––––––––––––––––––––––––––––––––––––––––––
package CHAR_STREAMS is new STREAMS (CHARACTER,
STRING);
type T_CHAR_STREAM is new CHAR_STREAMS.STREAM;
–– using this type in other packages there must be specified
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
70 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–– the average number of items (CHARACTER) for space allocation purposes
–– Example:
–– subtype MY_CHAR_STREAM is MPS_DEFINITIONS.T_CHAR_STREAM(20)
––––––––––––––––––
–– MPS constants
––––––––––––––––––
MAX_VERSION : constant := 999; –– maximal version number
MAX_NAME_LENGTH : constant := 16;
––––––––––––––––––––––––––––
–– Operating Sytem User Name
––––––––––––––––––––––––––––
USER_NAME_LEN : constant := 30;
subtype USER_NAME_INDEX is INTEGER range 1 .. USER_NAME_LEN;
subtype USERNAME is STRING (USER_NAME_INDEX);
––––––––––––––––––––––––––––––––––––––
–– Long Identifier (Pathname) for Item
––––––––––––––––––––––––––––––––––––––
NULL_PATHNAME : constant STRING := ””;
ROOT_PATHNAME : constant STRING := ”\”;
NODE_NAME_SEPARATOR : constant STRING := ”\”;
––––––––––––––––––––––––––––––––––
–– Short Identifier (SID) for Item
––––––––––––––––––––––––––––––––––
type SID is new UNSIGNED_INTEGER32;
–– NULL_SID is set in all cases where a pathname does not exist
NULL_SID : constant SID := 0;
–– this is the parent’s sid of the element configuration (i.e. APM or MTFF)
ROOT_SID : constant SID := 1;
type T_SID_ARRAY is array (POSITIVE range ) of SID;
–––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Long Identifier (Pathname, Subitem_Name) for Subitem
–––––––––––––––––––––––––––––––––––––––––––––––––––––––
subtype T_SUBITEM_NAME is STRING (1 .. MAX_NAME_LENGTH);
NULL_SUBITEM_NAME : constant T_SUBITEM_NAME := (others => ’ ’);
–––––––––––––––––––––––––––––––––––––––––––––––––
–– Short Identifier (SID, Subitem_Id) for Subitem
–––––––––––––––––––––––––––––––––––––––––––––––––
type SUBITEM_ID is new UNSIGNED_INTEGER32;
NULL_SUBITEM_ID : constant SUBITEM_ID := 0;
––––––––
–– Names
––––––––
subtype T_NAME is STRING (1 .. MAX_NAME_LENGTH);
subtype T_ELEMENT_CONFIGURATION_NAME is T_NAME;
type T_ELEMENT_CONFIGURATION_ARRAY is array (POSITIVE range ) of
T_ELEMENT_CONFIGURATION_NAME;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
71 von/of: 662

Space Infrastructure
subtype T_MISSION_NAME is T_NAME;
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
type T_MISSION_ARRAY is array (POSITIVE range ) of T_MISSION_NAME;
subtype T_CONFIGURATION_NAME is STRING (1 .. MAX_NAME_LENGTH);
subtype T_ITEM_NAME is T_NAME;
subtype T_MDB_INSTANCE is T_NAME;
–––––––––––––––––––––––––––––––––
–– SYSTEM– / CDU– / CCU– Version
–––––––––––––––––––––––––––––––––
subtype T_VERSION_NUMBER is INTEGER range 0 .. MAX_VERSION;
type T_SYSTEMTREE_VERSION_ARRAY is array (POSITIVE range ) of
T_VERSION_NUMBER;
type T_VERSION is
record
VERSION : T_VERSION_NUMBER;
ISSUE : T_VERSION_NUMBER;
REVISION : T_VERSION_NUMBER;
end record;
NO_VERSION : constant T_VERSION := (0,0,0);
type T_CDU_VERSION(TEST : BOOLEAN := FALSE) is
record
VERSION : T_VERSION;
case TEST is
when TRUE =>
TESTVERSION : T_VERSION_NUMBER;
MDB_INSTANCE : T_MDB_INSTANCE;
when FALSE =>
null;
end case;
end record;
NO_CDU_VERSION : constant T_CDU_VERSION := (FALSE,VERSION => (0,0,0));
type T_VERSION_STATUS is (NONE,
REVIEW,
DEVELOPMENT,
FROZEN);
type T_CONSISTENCY_STATUS is (NONE,
LOCAL_INVALID,
LOCAL_VALID,
GLOBAL_VALID);
–––––––––––––
–– CDU Domain
–––––––––––––
type T_CDU_DOMAIN is (NONE,
CGS,
EGSE,
CSS,
UCL_LIBRARY,
SYMBOL_LIBRARY,
USER_DEF_SIDS,
SDDF);
–––––––––––––
–– Item Types
–––––––––––––
type T_ITEM_TYPE is (NONE,
–– EGSE specific types
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
72 von/of: 662

Space Infrastructure
–– measurements:
EGSE_INTEGER_MEASUREMENT,
EGSE_FLOAT_MEASUREMENT,
EGSE_DISCRETE_MEASUREMENT,
EGSE_BYTE_STREAM_MEASUREMENT,
EGSE_INTEGER_SW_VARIABLE,
EGSE_FLOAT_SW_VARIABLE,
EGSE_DISCRETE_SW_VARIABLE,
EGSE_BYTE_STREAM_SW_VARIABLE,
–– derived values:
EGSE_INTEGER_DERIVED_VALUE,
EGSE_FLOAT_DERIVED_VALUE,
EGSE_DISCRETE_DERIVED_VALUE,
EGSE_STRING_DERIVED_VALUE,
–– stimuli / predefined TC:
EGSE_ANALOG_STIMULUS,
EGSE_DISCRETE_STIMULUS,
EGSE_PREDEFINED_TC,
EGSE_BINARY_PACKET,
–– others:
–– CSS specific types
–– item types
EGSE_MONITOR_LIST,
GDU_DESCRIPTION_LIST,
ADU_DESCRIPTION,
SIMULATED_ADU_DESCRIPTION,
EGSE_USER_MESSAGE,
EGSE_NODE,
EGSE_TEST_CONFIGURATION,
EGSE_SOFTWARE,
TOPLEVEL_COMPOSITE_FB,
COMPOSITE_FB,
–– end item types
CONSTANT_FB,
ASYNCHRONOUS_FB,
SYNCHRONOUS_FB,
–– common types
DOUBLE_FLOAT_MEASUREMENT,
BOOLEAN_MEASUREMENT,
UNSIGNED_INTEGER_MEASUREMENT,
DOUBLE_FLOAT_SW_VARIABLE,
BOOLEAN_SW_VARIABLE,
UNSIGNED_INTEGER_SW_VARIABLE,
DOUBLE_FLOAT_STIMULUS,
BOOLEAN_STIMULUS,
UNSIGNED_INTEGER_STIMULUS,
INTEGER_STIMULUS,
PULSE_STIMULUS,
BURST_PULSE_STIMULUS,
VIRTUAL,
CDU,
GENERAL_PURPOSES,
SWEU,
SWRU,
INTEGER_CONSTANT,
REAL_CONSTANT,
STRING_CONSTANT,
UCL_AUTOMATED_PROCEDURE,
UCL_USER_LIBRARY,
UCL_SYSTEM_LIBRARY,
HLCL_COMMAND_SEQUENCE,
CPL_SCRIPT,
SWOP_COMMAND,
RESPONSE_PACKET,
APID,
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
73 von/of: 662

Space Infrastructure
CCSDS_END_POINT,
WDU_GROUND_SYMBOL,
WDU_GROUND_SYNOPTIC_DISPLAY,
OTHER);
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
type T_ITEM_TYPE_SET is array (MPS_DEFINITIONS.T_ITEM_TYPE) of BOOLEAN;
–––––––––––––––––––––––––––––––
–– Subitem Types (for CSS)
–––––––––––––––––––––––––––––––
type T_SUBITEM_TYPE is (NONE,
FB_IO_INPUT,
FB_IO_OUTPUT);
type T_SUBITEM_TYPE_SET is array (MPS_DEFINITIONS.T_SUBITEM_TYPE) of BOOLEAN;
––––––––––––––
–– State Code
––––––––––––––
type STATE_CODE is new STRING (1..8);
type T_STATE_CODE_ARRAY is array (POSITIVE range ) of STATE_CODE;
package STATE_CODE_STREAMS is new STREAMS (STATE_CODE,
T_STATE_CODE_ARRAY);
type T_STATE_CODE_LIST is new STATE_CODE_STREAMS.STREAM;
–– using this type in other packages there must be specified
–– the average number of items (STATE_CODE) for space allocation purposes.
–– Example:
–– subtype MY_STATE_CODE_LIST is MPS_DEFINITIONS.T_STATE_CODE_LIST(20)
––––––––––––––
–– Bytestream/String engineering value type
––––––––––––––
MAX_ENGINEERING_STRING_LENGTH : constant := 256;
–– sets the upper limit of a engineering string value
MAX_RAW_STRING_LENGTH: constant := 255;
–– sets the upper limit of a byte stream value
–– Please note that these two values should be equal
–– they are kept like this for historical reasons
–– They will be changed to be the same in the future
–– The redundant definition in must also be changed
–– to comply with this value
subtype T_RAW_STRING is STRING(1..MAX_RAW_STRING_LENGTH);
subtype T_ENGINEERING_STRING is STRING(1..MAX_ENGINEERING_STRING_LENGTH);
––––––––––––––––––––
–– UCL specific Time
––––––––––––––––––––
type UCL_TIME is
record
DAY : NATURAL range 0 .. 31 := 0;
MONTH : NATURAL range 0 .. 12 := 0;
YEAR : NATURAL range 0 .. 2099 := 1;
SECONDS : SINGLE_FLOAT range 0.0 .. 86_400.0 := 0.0;
end record;
for UCL_TIME use
record at mod 8;
DAY at 0*4 range 0 .. 7;
MONTH at 0*4 range 8 .. 15;
YEAR at 0*4 range 16 .. 31;
SECONDS at 1*4 range 0 .. 31;
end record;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
74 von/of: 662

Space Infrastructure
for UCL_TIME’SIZE use 64;
MIN_TIME: constant UCL_TIME := (YEAR => 1901,
MONTH => 1,
DAY => 1,
SECONDS => 0.0);
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
MAX_TIME: constant UCL_TIME := (YEAR => 2099,
MONTH => 12,
DAY => 31,
SECONDS => 86400.0 – 2#0.000_000_1#);
–– last in a day
NO_TIME: constant UCL_TIME := (YEAR => 1, –– ~.~
MONTH => 0,
DAY => 0,
SECONDS => 0.0);
–––––––––––––––––––––
–– Engineering Units
–––––––––––––––––––––
package BASE_UNITS is new UNITS(DOUBLE_FLOAT);
subtype T_UNIT is BASE_UNITS.UNIT;
type T_ENGINEERING_UNIT is
record
EXPRESSION : STATIC_STRING80 := STATIC (””);
UNIT : T_UNIT := BASE_UNITS.NO_UNIT;
end record;
–––––––––––––––––––––––––––––––––––––––––––
–– Cross Reference List
–––––––––––––––––––––––––––––––––––––––––––
type T_XREF is
record
PATH_NAME : DYNAMIC_STRING;
SHORT_ID : SID;
end record;
type T_XREF_ARRAY is array (POSITIVE range ) of T_XREF;
procedure ASSIGN (TARGET: in out T_XREF; SOURCE: T_XREF);
function ”=” (LEFT, RIGHT: T_XREF) return BOOLEAN ;
procedure DEALLOCATE (GARBAGE : in out T_XREF);
package XREF_STREAMS is new LIMITED_STREAMS (T_XREF,
T_XREF_ARRAY,
ASSIGN,
”=”);
type T_XREF_LIST is new XREF_STREAMS.STREAM;
–– using this type in other packages there must be specified
–– the average number of items (T_XREF) for space allocation purposes.
–– Example:
–– subtype MY_XREF_LIST is MPS_DEFINITIONS.T_XREF_LIST(20)
procedure DEALLOCATE (GARBAGE : in out T_XREF_LIST);
–––––––––––––––––––––––––––––––––––––
–– Software Variables Access Classes
–––––––––––––––––––––––––––––––––––––
type T_SW_ACCESS_CLASS is (NONE,
READ,
READ_WRITE,
EXECUTE,
SEND,
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
75 von/of: 662

Space Infrastructure
–––––––––––––––––––
–– Completion Code
–––––––––––––––––––
type COMPLETION_CODE is (SUCCESS,
FAILURE,
NONE);
–––––––––––––––––––––––––
–– SW_TYPE related types
–––––––––––––––––––––––––
IMPORT,
PATH_SELECT,
NODE_SELECT);
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–– The following descriptors make up a UCL type declaration.
–– They describe the software type of database items and formal parameters.
–– For a description of the UCL type concept refer to the UCL Reference
–– Manual and the HLCL Reference Manual.
––
–– Only a subset of the UCL types is supported, the following restrictions
–– apply:
––
–– enumeration types: only predefined COMPLETION_CODE
––
–– array types: max. 3 dimensions
–– index type must be INTEGER
–– lower bounds must be 1
––
–– record types: not allowed
––
–– set types: only predefined BITSET
–– 1. Type classes
––––––––––––––––––
–– These define the basic scalar type class.
–– Further information is needed for arrays, constrained and unitized types.
type T_SW_TYPE is (NONE,
STRING_TYPE,
STATE_CODE_TYPE,
INTEGER_TYPE,
REAL_TYPE,
BOOLEAN_TYPE,
BITSET_TYPE,
CHARACTER_TYPE,
WORD_TYPE,
PATHNAME_TYPE,
TIME_TYPE,
DURATION_TYPE,
COMPLETION_CODE_TYPE,
SUBITEM_PATHNAME_TYPE,
PULSE_TYPE,
BURST_PULSE_TYPE,
UNSIGNED_INTEGER_TYPE,
LONG_REAL_TYPE);
–– 2. Type constraints
––––––––––––––––––––––
–– These descriptors define constraints for various UCL types.
–– The discriminant CONSTRAINED defines whether there is a constraint
–– or not. Each descriptor is headed with an example in UCL that might
–– be represented withe the descriptor:
type T_INTEGER_RANGE (CONSTRAINED: BOOLEAN := FALSE) is
record
case CONSTRAINED is
when TRUE =>
FIRST : INTEGER32 := INTEGER32’FIRST;
LAST : INTEGER32 := INTEGER32’LAST;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
76 von/of: 662

Space Infrastructure
when FALSE =>
null;
end case;
end record;
–– Example: INTEGER (0 .. 1024)
type T_UNSIGNED_INTEGER_RANGE (CONSTRAINED: BOOLEAN := FALSE) is
record
case CONSTRAINED is
when TRUE =>
FIRST : UNSIGNED_INTEGER32 := 0;
LAST : UNSIGNED_INTEGER32 := UNSIGNED_INTEGER32’LAST;
when FALSE =>
null;
end case;
end record;
–– Example: UNSIGNED_INTEGER (0 .. 1024)
type T_REAL_RANGE (CONSTRAINED: BOOLEAN := FALSE) is
record
case CONSTRAINED is
when TRUE =>
FIRST : SINGLE_FLOAT := SINGLE_FLOAT’FIRST;
LAST : SINGLE_FLOAT := SINGLE_FLOAT’LAST;
when FALSE =>
null;
end case;
end record;
–– Example: REAL (0.0 .. 1.0)
type T_LONG_REAL_RANGE (CONSTRAINED: BOOLEAN := FALSE) is
record
case CONSTRAINED is
when TRUE =>
FIRST : DOUBLE_FLOAT := DOUBLE_FLOAT’FIRST;
LAST : DOUBLE_FLOAT := DOUBLE_FLOAT’LAST;
when FALSE =>
null;
end case;
end record;
–– Example: LONG_REAL (0.0 .. 1.0)
type T_DURATION_RANGE (CONSTRAINED: BOOLEAN := FALSE) is
record
case CONSTRAINED is
when TRUE =>
FIRST : DOUBLE_FLOAT := 0.0;
LAST : DOUBLE_FLOAT := DOUBLE_FLOAT’LAST;
when FALSE =>
null;
end case;
end record;
–– Example: DURATION (0.0 [s] .. 1.0 [s])
type T_CHARACTER_RANGE (CONSTRAINED: BOOLEAN := FALSE) is
record
case CONSTRAINED is
when TRUE =>
FIRST : CHARACTER := CHARACTER’FIRST;
LAST : CHARACTER := CHARACTER’LAST;
when FALSE =>
null;
end case;
end record;
–– Example: CHARACTER (’a’ .. ’z’)
type T_BOOLEAN_RANGE (CONSTRAINED: BOOLEAN := FALSE) is
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
77 von/of: 662

Space Infrastructure
record
case CONSTRAINED is
when TRUE =>
FIRST : BOOLEAN := BOOLEAN’FIRST;
LAST : BOOLEAN := BOOLEAN’LAST;
when FALSE =>
null;
end case;
end record;
–– Example: BOOLEAN (FALSE .. FALSE)
type T_TIME_RANGE (CONSTRAINED: BOOLEAN := FALSE) is
record
case CONSTRAINED is
when TRUE =>
FIRST : UCL_TIME := MIN_TIME;
LAST : UCL_TIME := MAX_TIME;
when FALSE =>
null;
end case;
end record;
–– Example: TIME (01.01.1990 12:00:00 .. 31.12.1995 12:00:00)
type T_COMPLETION_CODE_RANGE (CONSTRAINED: BOOLEAN := FALSE) is
record
case CONSTRAINED is
when TRUE =>
FIRST : COMPLETION_CODE := SUCCESS;
LAST : COMPLETION_CODE := FAILURE;
when FALSE =>
null;
end case;
end record;
–– Example: COMPLETION_CODE (SUCCESS .. SUCCESS)
–– 3. Array dimensions
––––––––––––––––––––––
–– These types serve to define arrays up to 3 dimensions.
type T_SW_DIMENSIONS is range 0 .. 3;
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
type T_SW_INDEX_LIST is array (T_SW_DIMENSIONS range ) of POSITIVE;
–– 4. Software type descriptor
––––––––––––––––––––––––––––––
–– This defines the type. The SW_TYPE discriminant defines the type
–– class, for arrays the type class of the element type.
–– The DIMENSION discriminant defines the array dimension.
–– DIMENSION = 0 defines a scalar type.
–– For each array dimension the BOUNDS field contains the upper bound.
–– The lower bound is understood to be 1. The index type is always INTEGER.
––
–– Each case branch is followed by a UCL example that might be represented
–– with the branch.
type T_SW_TYPE_DESCRIPTOR (SW_TYPE : T_SW_TYPE := NONE;
DIMENSION : T_SW_DIMENSIONS := 0) is
record
BOUNDS: T_SW_INDEX_LIST (1 .. DIMENSION);
case SW_TYPE is
when NONE =>
null;
when STRING_TYPE =>
STRING_SIZE : NATURAL;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
78 von/of: 662

Space Infrastructure
–– Example: X : string (80);
when STATE_CODE_TYPE =>
STATE_CODE_LIST : T_STATE_CODE_LIST (5);
–– Example: X : statecode;
–– X : statecode ($LOW, $MEDIUM, $HIGH);
when INTEGER_TYPE =>
INTEGER_RANGE : T_INTEGER_RANGE;
–– Example: X : INTEGER;
–– X : INTEGER (0 .. 255);
when REAL_TYPE =>
REAL_UNIT : T_ENGINEERING_UNIT;
REAL_RANGE : T_REAL_RANGE;
–– Example: non–unitized reals:
–– X : REAL;
–– X : REAL (0.0 .. 1.0);
–– Example: unitized reals:
–– X : REAL [m/s];
–– X : REAL (0.0 .. 1.0) [m/s];
when DURATION_TYPE =>
DURATION_RANGE : T_DURATION_RANGE;
–– Example: X : DURATION;
–– X : DURATION (0.0 [s] .. 1.0 [s]);
when BOOLEAN_TYPE =>
BOOLEAN_RANGE : T_BOOLEAN_RANGE;
–– Example: X : BOOLEAN;
–– X : BOOLEAN (FALSE .. FALSE);
when BITSET_TYPE =>
null;
–– Example: X : BITSET;
when CHARACTER_TYPE =>
CHARACTER_RANGE : T_CHARACTER_RANGE;
–– Example: X : CHARACTER;
–– X : CHARACTER (’a’ .. ’z’);
when WORD_TYPE =>
null;
–– Example: X : WORD;
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
when PATHNAME_TYPE =>
ITEM_TYPES : T_ITEM_TYPE_SET; –– predefined
OTHER_ITEM_TYPES : STRING_POINTERS.STRING_STREAM(2); –– user defined
PARAMETERIZED : BOOLEAN;
–– Example: non–parameterized pathnames:
–– X : pathname;
–– X : pathname (ANALOG_MEASUREMENT, DISCRETE_MEASUREMENT);
–– Example: parameterized pathnames:
–– X : pathname ();
–– X : pathname (ANALOG_MEASUREMENT, DISCRETE_MEASUREMENT) ();
when SUBITEM_PATHNAME_TYPE =>
SUBITEM_TYPES : T_SUBITEM_TYPE_SET;
–– Example: X : pathname.*;
–– X : pathname.* (FB_IO_INPUT);
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
79 von/of: 662

Space Infrastructure
end case;
end record;
when TIME_TYPE =>
TIME_RANGE : T_TIME_RANGE;
–– Example: X : TIME;
–– X : TIME (00:00:00 .. 12:00:00);
when COMPLETION_CODE_TYPE =>
COMPLETION_CODE_RANGE : T_COMPLETION_CODE_RANGE;
–– Example: X : COMPLETION_CODE (SUCCESS .. SUCCESS);
when PULSE_TYPE =>
null;
–– Example: X : PULSE;
when BURST_PULSE_TYPE =>
null;
–– Example: X : BURST_PULSE;
when UNSIGNED_INTEGER_TYPE =>
UNSIGNED_INTEGER_RANGE : T_UNSIGNED_INTEGER_RANGE;
–– Example: X : UNSIGNED_INTEGER;
–– X : UNSIGNED_INTEGER (0 .. 255);
when LONG_REAL_TYPE =>
LONG_REAL_UNIT : T_ENGINEERING_UNIT;
LONG_REAL_RANGE : T_LONG_REAL_RANGE;
–– Example: non–unitized long reals:
–– X : LONG_REAL;
–– X : LONG_REAL (0.0 .. 1.0);
–– Example: unitized long reals:
–– X : LONG_REAL [m/s];
–– X : LONG_REAL (0.0 .. 1.0) [m/s];
type SW_TYPE_INFO is access T_SW_TYPE_DESCRIPTOR;
procedure DEALLOCATE(GARBAGE : in out T_SW_TYPE_DESCRIPTOR) ;
procedure DEALLOCATE(GARBAGE : in out SW_TYPE_INFO) ;
procedure ASSIGN(TARGET : in out SW_TYPE_INFO;
SOURCE : in SW_TYPE_INFO) ;
procedure ASSIGN(TARGET : in out T_SW_TYPE_DESCRIPTOR;
SOURCE : in T_SW_TYPE_DESCRIPTOR) ;
function ”=” (LEFT,
RIGHT : in T_SW_TYPE_DESCRIPTOR)
return BOOLEAN ;
function EQUAL (LEFT,
RIGHT : in SW_TYPE_INFO)
return BOOLEAN ;
––––––––––––––––––
–– Software Values
––––––––––––––––––
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–– The following descriptors describe scalar or structured values.
–– Value descriptors are used to express the value of a database item
–– or the default value of a formal parameter.
–– 1. Scalar value
––––––––––––––––––
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
80 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–– A scalar value is represented by its type class (T_SW_TYPE) and a
–– value of the respective type.
type T_SW_SCALAR_VALUE (SW_TYPE: T_SW_TYPE := NONE) is
record
case SW_TYPE is
when NONE => null;
when STRING_TYPE => STRING_VALUE : STATIC_STRING256;
when STATE_CODE_TYPE => STATE_CODE_VALUE : STATE_CODE;
when INTEGER_TYPE => INTEGER_VALUE : INTEGER32;
when REAL_TYPE => REAL_VALUE : SINGLE_FLOAT;
when BOOLEAN_TYPE => BOOLEAN_VALUE : BOOLEAN;
when BITSET_TYPE => BITSET_VALUE : BITSET;
when CHARACTER_TYPE => CHARACTER_VALUE : CHARACTER;
when WORD_TYPE => WORD_VALUE : UNSIGNED_INTEGER32;
when PATHNAME_TYPE => PATHNAME_VALUE : SID;
when TIME_TYPE => TIME_VALUE : UCL_TIME;
when DURATION_TYPE => DURATION_VALUE : DOUBLE_FLOAT;
when COMPLETION_CODE_TYPE => COMPLETION_CODE_VALUE : COMPLETION_CODE;
when SUBITEM_PATHNAME_TYPE => ITEM_VALUE : SID;
SUBITEM_VALUE : SUBITEM_ID;
when PULSE_TYPE => PULSE_VALUE :BOOLEAN;
when BURST_PULSE_TYPE => BURST_PULSE_VALUE : UNSIGNED_INTEGER32;
when UNSIGNED_INTEGER_TYPE => UNSIGNED_INTEGER_VALUE : UNSIGNED_INTEGER32;
when LONG_REAL_TYPE => LONG_REAL_VALUE : DOUBLE_FLOAT;
end case;
end record;
–– Provide T_SW_SCALAR_VALUE’s own packing procedures to support the
–– ADT_PACKING mechanism.
–– They are needed to pach T_SW_VALUE below.
function SIZE_NEEDED (VALUE : T_SW_SCALAR_VALUE)
return ADT_PACKING.T_PACK_INDEX;
procedure PACK (VALUE : in T_SW_SCALAR_VALUE;
BLOCK : in out ADT_PACKING.T_BLOCK);
procedure UNPACK (BLOCK : in out ADT_PACKING.T_BLOCK;
VALUE : in out T_SW_SCALAR_VALUE);
–– 2. General value
–––––––––––––––––––
–– The descriptor T_SW_VALUE describes a value of any of the types
–– comprised by the type descriptor T_SW_TYPE_DESCRIPTOR. It covers
–– scalar values and arrays of these values up to 3 dimensions.
type T_SW_VALUE (SW_TYPE : T_SW_TYPE := NONE;
DIMENSION : T_SW_DIMENSIONS := 0) is limited private;
–– The following operations create and destroy values and access the
–– scalar components of a (possibly structured) type.
procedure CREATE (OBJECT : in out T_SW_VALUE;
SW_TYPE : in T_SW_TYPE);
procedure CREATE (OBJECT : in out T_SW_VALUE;
SW_TYPE : in T_SW_TYPE;
BOUNDS : in T_SW_INDEX_LIST);
procedure DESTROY (OBJECT : in out T_SW_VALUE);
procedure SET_VALUE (OBJECT : in out T_SW_VALUE;
VALUE : in T_SW_SCALAR_VALUE);
procedure SET_VALUE (OBJECT : in out T_SW_VALUE;
INDEX : in T_SW_INDEX_LIST;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
81 von/of: 662

Space Infrastructure
VALUE : in T_SW_SCALAR_VALUE);
procedure GET_VALUE (OBJECT : in T_SW_VALUE;
VALUE : in out T_SW_SCALAR_VALUE);
procedure GET_VALUE (OBJECT : in T_SW_VALUE;
INDEX : in T_SW_INDEX_LIST;
VALUE : in out T_SW_SCALAR_VALUE);
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
function BOUNDS_OF (OBJECT : in T_SW_VALUE) return T_SW_INDEX_LIST;
procedure ASSIGN (TARGET: in out T_SW_VALUE;
SOURCE: in T_SW_VALUE);
–– As T_SW_VALUE is private and internally uses access types, it is neces–
–– sary to provide its own packing procedures to support the ADT_PACKING
–– mechanism.
function SIZE_NEEDED (VALUE : T_SW_VALUE) return ADT_PACKING.T_PACK_INDEX;
procedure PACK (SW_VALUE : in T_SW_VALUE;
BLOCK : in out ADT_PACKING.T_BLOCK);
procedure UNPACK (BLOCK : in out ADT_PACKING.T_BLOCK;
SW_VALUE : in out T_SW_VALUE);
type T_ACCESS_SW_VALUE is access T_SW_VALUE;
procedure DEALLOCATE (GARBAGE : in out T_ACCESS_SW_VALUE);
type T_SW_VALUE_ARRAY is array (POSITIVE range ) of T_ACCESS_SW_VALUE;
package SW_VALUE_STREAMS is new
STREAMS (T_ACCESS_SW_VALUE,
T_SW_VALUE_ARRAY);
type T_SW_VALUE_STREAM is new SW_VALUE_STREAMS.STREAM;
type T_SW_SCALAR_VALUE_ARRAY is array (POSITIVE range ) of
T_SW_SCALAR_VALUE;
procedure ASSIGN (TARGET: in out T_SW_SCALAR_VALUE;
SOURCE: in T_SW_SCALAR_VALUE);
package SW_SCALAR_VALUE_STREAMS is new
LIMITED_STREAMS (T_SW_SCALAR_VALUE,
T_SW_SCALAR_VALUE_ARRAY,
ASSIGN);
type T_SW_SCALAR_VALUE_STREAM is new SW_SCALAR_VALUE_STREAMS.STREAM;
–––––––––––––––––––––––––––––––––––––––––
–– Formal Parameter List
–––––––––––––––––––––––––––––––––––––––––
–– The following descriptors describe formal parameter lists of
–– database items. For the formal parameter list concept refer to
–– the UCL Reference Manual and the HLCL Reference Manual.
–– 1. Parameter mode
––––––––––––––––––––
type T_FORMAL_PARAMETER_MODE is (NONE,
IN_MODE,
OUT_MODE,
IN_OUT_MODE);
–– 2. Single parameter
––––––––––––––––––––––
–– This describes a single parameter with its name, its mode, its type
–– and its default value, if optional.
––
–– A parameter has a name by which it can be identified in UCL/HLCL.
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
82 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–– Parameter names are identifiers as defined in UCL.
––
–– A parameter may require a single value (LIST = FALSE) or an open
–– list of values (LIST = TRUE). A list of values corresponds to an
–– open array:
–– X : array of
––
–– Parameters may be mandatory (OPTIONAL = FALSE) or optional
–– (OPTIONAL = TRUE). Optional parameters require a default value
–– described with a T_SW_VALUE descriptor.
–– A single value (LIST = FALSE) is represented with a single value
–– descriptor, a list of values (LIST = TRUE) is represented with
–– a stream of single value descriptors.
type T_FORMAL_PARAMETER
(SW_TYPE : T_SW_TYPE := NONE;
DIMENSION : T_SW_DIMENSIONS := 0;
OPTIONAL : BOOLEAN := FALSE;
LIST : BOOLEAN := FALSE)
is
record
TYPE_INFO : SW_TYPE_INFO (SW_TYPE, DIMENSION);
MODE : T_FORMAL_PARAMETER_MODE;
NAME : STATIC_STRING80;
case OPTIONAL is
when FALSE => null;
when TRUE =>
case LIST is
when FALSE => SW_VALUE : T_SW_VALUE (SW_TYPE,
DIMENSION);
when TRUE => SW_VALUE_LIST : T_SW_VALUE_STREAM(2);
end case;
end case;
end record;
type T_ACCESS_FORMAL_PARAMETER is access T_FORMAL_PARAMETER;
–– This operation deallocates memory of T_ACCESS_FORMAL_PARAMETER
–– variable and all included structures.
procedure DEALLOCATE(GARBAGE : in out T_ACCESS_FORMAL_PARAMETER);
–– 3. Parameter list
––––––––––––––––––––
–– A parameter list is represented as a stream of single parameter
–– descriptors.
type T_FORMAL_PARAMETER_ARRAY is array (POSITIVE range ) of
T_ACCESS_FORMAL_PARAMETER;
procedure ASSIGN (TARGET: in out T_ACCESS_FORMAL_PARAMETER;
SOURCE: in T_ACCESS_FORMAL_PARAMETER);
package FORMAL_PARAMETER_STREAMS is new
LIMITED_STREAMS (T_ACCESS_FORMAL_PARAMETER,
T_FORMAL_PARAMETER_ARRAY,
ASSIGN);
type T_FORMAL_PARAMETER_LIST is new FORMAL_PARAMETER_STREAMS.STREAM;
–– This operation deallocates a stream of type T_FORMAL_PARAMETER_LIST
–– and all included structures.
procedure CLEAR (STREAM : in out T_FORMAL_PARAMETER_LIST);
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– PRIVATE PART
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
private
type T_VALUE_ARRAY is array (POSITIVE range ) of T_SW_SCALAR_VALUE;
type T_ACCESS_VALUE_ARRAY is access T_VALUE_ARRAY;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
83 von/of: 662

Space Infrastructure
type T_SW_VALUE (SW_TYPE: T_SW_TYPE := NONE;
DIMENSION: T_SW_DIMENSIONS := 0) is
record
BOUNDS: T_SW_INDEX_LIST (1 .. DIMENSION);
VALUE: T_ACCESS_VALUE_ARRAY;
end record;
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
end MPS_DEFINITIONS;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
84 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
6.2 MDB Standard Entities and Application Programmer Interface
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
85 von/of: 662
The excact definition is specified in applicable document ”MDB Standard Entities and Application Programmer
Interface”, ref. 2.1.6.1.

Space Infrastructure
6.3 CLS Global
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
86 von/of: 662
The CLS Global section comprises Ada packages that contain global CLS definitions. They form the basis of
other CLS packages:
6.3.1 General CLS Definitions
The package CLS contains global declarations referenced by all CLS components, e.g. special control
characters, options, all exceptions raised by any of the CLS components.

Space Infrastructure
Formal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– CLS
––
–– Global CLS declarations:
–– Special control characters.
–– Options for all CLS components.
–– All exceptions raised by any of the CLS components.
––
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– Unit: Package specification
––
–– Author: Franz Kruse, ERNO
––
–– Document:
––
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– Version Date Author SPR Change description
–– ––––––– –––––––– –––––––––– –––– –––––––––––––––––––––––––––––––––––––––––
–– 3.0.0 11.01.94 F. Kruse First issue for V3
––
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
package CLS is
–– Source formatting characters
–––––––––––––––––––––––––––––––
TAB_CHAR: constant CHARACTER := ASCII.HT; –– Tabulator
SPACE_CHAR: constant CHARACTER := ASCII.US; –– Hard space
SYNC_CHAR: constant CHARACTER := ASCII.SYN; –– Synchronization point
LINE_CHAR: constant CHARACTER := ASCII.LF; –– End of line character
PAGE_CHAR: constant CHARACTER := ASCII.FF; –– End of page character
END_CHAR: constant CHARACTER := ASCII.NUL; –– End of text character
–– Compiler options
–––––––––––––––––––
type OPTIONS is (LIST_COMPILATION_DATE,
LIST_OWNER_NAME,
LIST_SIZE_INFORMATION,
LIST_DATABASE_ITEMS,
LIST_SIDS,
LIST_CROSS_REFERENCE,
LIST_UNCALLED_PROCEDURES,
LIST_UNUSED_VARIABLES,
OPTIMIZE);
type OPTION_LIST is array (OPTIONS) of BOOLEAN;
DEFAULT_OPTIONS: constant OPTION_LIST := (others => FALSE);
–– CLS Exceptions
–––––––––––––––––
USE_ERROR: exception; –– invalid sequence of calls
PARAMETER_ERROR: exception; –– invalid parameter constellation
DEFINITION_ERROR: exception; –– invalid definition (of commands etc.)
TYPE_ERROR: exception; –– invalid type indication
RANGE_ERROR: exception; –– range violation
FATAL_ERROR: exception; –– fatal internal error, abort
end CLS;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
87 von/of: 662

Space Infrastructure
6.3.2 Runtime Representation of UCL Types
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
88 von/of: 662
The Ada package defines the runtime representation of all UCL type classes, together with the
UCL operations on them, and conversion functions between UCL and standard Ada types where necessary or
appropriate. This representation is used in the Virtual Stack Machine (see 6.7.3) and the HLCL Interpreter (see
NO TAG).
All scalar types are represented as one or two 4–byte data words, resp., independently of the range of values
covered by the type. Structured types are represented by a sequence of as many data words as needed to cover
the complete structure. Any UCL object is allocated as a multiple of full data words, even if it occupies only
part of the last data word.
Here is a description of the type classes in detail:
1–word scalar type. Values are represented as signed numbers in 2’s complement.
1–word scalar type. Values are represented as unsigned integers. Due to implementation restrictions, only bits
0 .. 30 are used to represent a value, bit 31 is always 0.
1–word scalar type. Values are represented as contiguous unsigned integers in the order of their declaration, the
first enumeration value starting at 0.
1–word scalar type, represented as an enumeration type with two values: = 0, = 1.
1–word scalar type, represented as an enumeration type with two values: = 0, = 1.
1–word scalar type. Values are represented by unsigned integers in the range 0 .. 255, where the subrange 0 ..
127 is the ASCII character set.
1–word scalar type. Values are represented in IEEE single floating point format.
2–word sclar type. Values are represented in IEEE double floating point format.
1–word scalar type, represented like . The range is restricted to one day (–86400.0 .. 86400.0).

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
89 von/of: 662
2–word scalar type. Values are stored in a packed record. The first word stores the date, the second word stores
the seconds since midnight in DURATION format. The date is stored in the following format: the first byte is
the day in the range 1 .. 31, the second byte is the month in the range 1 .. 12, the remaining two bytes hold the
year in the range 1901 .. 2099.
Times without a date (i.e. the date is to be ignored in time operations) are represented with the complete date
word = 0.
The constant ~:~ (no time) is represented with a date word of the form: day = 0, month = 0, year = 1.
Pathname types fall in two classes:
• Non–parameterized pathnames are 1–word scalar values represented by the SID of the corresponding
database item. It is represented in format. The constant \\ (no pathname) is
represented by SID 0.
• Parameterized pathnames are structured values. Their representation is defined by the internal
encoding scheme described in chapter 4.9.3.2.
2–word scalar types. A statecode value is represented as 8 characters packed in two words, the first bytes
containing the name of the statecode literal, and the unused bytes filled with spaces.
Structured types. A set is represented by a number of bits packed in one or more words, one bit for each possible
member of the set. A member is present in the set, if its bit is set, it is absent otherwise.
1–word scalar type. is a special set with members 0 .. 31, each bit of the word representing one of the
members.
Structured types. A string is represented as one word holding the actual length of the string as an unsigned
integer, followed by zero or more words holding a byte array with 4 bytes (i.e. characters) packed in one word.
The number of bytes covers the maximum length of the string, filled up to a multiple of four.
Structured types. An array is represented as a sequence of its elements in their respective representation. Arrays
with more than one dimension store their elements in an order that for all index positions i and i+1 indices on
position i+1 vary faster than on position i.
Structured types. A record is represented as a sequence of its fields in their respective representation.
Scalar type. Values of type simply occupy a word of 32 bits, without any interpretation of the bits
themselves.

Space Infrastructure
Formal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– CLS_TYPES
––
–– Basic UCL datatypes in UCL representation
––
–– This package defines the runtime representation of all UCL/HLCL datatypes
–– with their operations.
––
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– Author: Norbert Fritsch, DASA RI
––
–– Document:
––
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Date Author Change description
–– –––––––– –––––––––––– –––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– 01.02.95 N. Fritsch #CGS: V2.2
–– 15.02.95 Franz Kruse #IRN: COL–RIBRE–IRN–CGS–3002a
–– 27.06.95 I. Semrau #IRN: COL–RIBRE–IRN–CGS–3076
–– use NUMERIC_TYPES;
–– 29.09.95 Franz Kruse #IRN: COL–RIBRE–IRN–CGS–3077
–– UCL_UNSIGNED_INTEGER constrained to 0 .. 2**31–1.
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
with CALENDAR;
with NUMERIC_TYPES; use NUMERIC_TYPES;
with MPS_DEFINITIONS;
package CLS_TYPES is
–– UCL types sizes
––––––––––––––––––
WORD_SIZE : constant := 32; –– bits per UCL storage unit
–– UCL types
––––––––––––
type UCL_BOOLEAN is new NUMERIC_TYPES.INTEGER32 range 0 .. 1;
type UCL_CHARACTER is new NUMERIC_TYPES.INTEGER32 range 0 .. 255;
subtype UCL_INTEGER is NUMERIC_TYPES.INTEGER32;
subtype UCL_UNSIGNED_INTEGER is NUMERIC_TYPES.UNSIGNED_INTEGER32
range 0 .. NUMERIC_TYPES.UNSIGNED_INTEGER32’LAST;
subtype UCL_ENUMERATION is UCL_UNSIGNED_INTEGER;
subtype UCL_REAL is NUMERIC_TYPES.SINGLE_FLOAT;
subtype UCL_LONG_REAL is NUMERIC_TYPES.DOUBLE_FLOAT;
type UCL_DURATION is new UCL_REAL range –86_400.0 .. 86_400.0;
subtype UCL_TIME is MPS_DEFINITIONS.UCL_TIME;
type UCL_WORD is new NUMERIC_TYPES.UNSIGNED_INTEGER32;
subtype UCL_PATHNAME is MPS_DEFINITIONS.SID;
type UCL_SUBITEM_PATHNAME is
record
ITEM: MPS_DEFINITIONS.SID;
SUBITEM: MPS_DEFINITIONS.SUBITEM_ID;
end record;
subtype UCL_STATECODE is MPS_DEFINITIONS.STATE_CODE;
type PACKED_BOOLEAN is new BOOLEAN;
for PACKED_BOOLEAN’SIZE use 1;
type UCL_SET is array (UCL_INTEGER range )
of PACKED_BOOLEAN;
pragma PACK (UCL_SET);
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
90 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
subtype UCL_BITSET is UCL_SET (0..31);
type PACKED_UCL_CHARACTER is new NUMERIC_TYPES.INTEGER32 range 0 .. 255;
for PACKED_UCL_CHARACTER’SIZE use NUMERIC_TYPES.BYTE’SIZE;
type PACKED_UCL_CHARACTER_ARRAY is array (UCL_INTEGER range )
of PACKED_UCL_CHARACTER;
pragma PACK (PACKED_UCL_CHARACTER_ARRAY);
type UCL_STRING (MAX_LENGTH: UCL_INTEGER) is
record
LENGTH: UCL_INTEGER := 0;
TEXT: PACKED_UCL_CHARACTER_ARRAY (1 .. MAX_LENGTH);
end record;
–– Constants
–––––––––––––––––––––––
UCL_TRUE: constant UCL_BOOLEAN := UCL_BOOLEAN (BOOLEAN’POS (TRUE));
UCL_FALSE: constant UCL_BOOLEAN := UCL_BOOLEAN (BOOLEAN’POS (FALSE));
NO_TIME: constant UCL_TIME := (DAY => 0,
MONTH => 0,
YEAR => 1,
SECONDS => 0.0);
–– Conversion functions
–––––––––––––––––––––––
function IMAGE (ITEM: UCL_BOOLEAN) return STRING;
function IMAGE (ITEM: UCL_CHARACTER) return STRING;
function IMAGE (ITEM: UCL_INTEGER) return STRING;
function IMAGE (ITEM: UCL_UNSIGNED_INTEGER) return STRING;
function IMAGE (ITEM: UCL_REAL) return STRING;
function IMAGE (ITEM: UCL_LONG_REAL) return STRING;
function IMAGE (ITEM: UCL_DURATION) return STRING;
function IMAGE (ITEM: UCL_WORD) return STRING;
function IMAGE (ITEM: UCL_TIME) return STRING;
function IMAGE (ITEM: UCL_STATECODE) return STRING;
function IMAGE (ITEM: UCL_PATHNAME) return STRING;
function IMAGE (ITEM: UCL_SUBITEM_PATHNAME) return STRING;
function IMAGE (ITEM: UCL_BITSET) return STRING;
function IMAGE (ITEM: UCL_STRING) return STRING;
–– Return the image of the given value
function VALUE (ITEM: STRING) return UCL_BOOLEAN;
function VALUE (ITEM: STRING) return UCL_CHARACTER;
function VALUE (ITEM: STRING) return UCL_INTEGER;
function VALUE (ITEM: STRING) return UCL_UNSIGNED_INTEGER;
function VALUE (ITEM: STRING) return UCL_REAL;
function VALUE (ITEM: STRING) return UCL_LONG_REAL;
function VALUE (ITEM: STRING) return UCL_DURATION;
function VALUE (ITEM: STRING) return UCL_WORD;
function VALUE (ITEM: STRING) return UCL_TIME;
function VALUE (ITEM: STRING) return UCL_STATECODE;
function VALUE (ITEM: STRING) return UCL_PATHNAME;
function VALUE (ITEM: STRING) return UCL_SUBITEM_PATHNAME;
function VALUE (ITEM: STRING) return UCL_BITSET;
function VALUE (ITEM: STRING) return UCL_STRING;
–– Return the UCL value of the given string.
–– Raise CLS.PARAMETER_ERROR if the given string is invalid.
function UCL_STRING_VALUE (ITEM: CHARACTER) return UCL_STRING;
function UCL_STRING_VALUE (ITEM: UCL_CHARACTER) return UCL_STRING;
–– Return the UCL string of the given character.
function UCL_BOOLEAN_VALUE (ITEM: BOOLEAN) return UCL_BOOLEAN;
function UCL_CHARACTER_VALUE (ITEM: CHARACTER) return UCL_CHARACTER;
function UCL_STRING_VALUE (ITEM: STRING) return UCL_STRING;
–– Return the UCL value of the given ADA value.
function BOOLEAN_VALUE (ITEM: UCL_BOOLEAN) return BOOLEAN;
function CHARACTER_VALUE (ITEM: UCL_CHARACTER) return CHARACTER;
function STRING_VALUE (ITEM: UCL_STRING) return STRING;
–– Return the ADA value of the given UCL value.
–– Raise CLS.RANGE_ERROR if a UCL character value is out of the
–– ASCII character set.
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
91 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
function UCL_TIME_VALUE (ITEM: CALENDAR.TIME) return UCL_TIME;
function TIME_VALUE (ITEM: UCL_TIME) return CALENDAR.TIME;
–– Convert UCL_TIME to TIME and vice versa.
function UCL_BITSET_VALUE (ITEM: NUMERIC_TYPES.BITSET) return UCL_BITSET;
function BITSET_VALUE (ITEM: UCL_BITSET) return NUMERIC_TYPES.
BITSET;
–– Convert UCL_BITSET to BITSET and vice versa.
–– UCL arithmetic functions on the UCL types
––––––––––––––––––––––––––––––––––––––––––––
function ”not” (ITEM: UCL_BOOLEAN) return UCL_BOOLEAN;
function ”and” (LEFT: UCL_BOOLEAN; RIGHT: UCL_BOOLEAN) return UCL_BOOLEAN;
function ”or” (LEFT: UCL_BOOLEAN; RIGHT: UCL_BOOLEAN) return UCL_BOOLEAN;
–– Operations on UCL boolean.
function POWER (LEFT: UCL_INTEGER;
RIGHT: UCL_INTEGER) return UCL_INTEGER;
function POWER (LEFT: UCL_UNSIGNED_INTEGER;
RIGHT: UCL_INTEGER) return UCL_UNSIGNED_INTEGER;
function POWER (LEFT: UCL_REAL;
RIGHT: UCL_INTEGER) return UCL_REAL;
function POWER (LEFT: UCL_LONG_REAL;
RIGHT: UCL_INTEGER) return UCL_LONG_REAL;
function POWER (LEFT: UCL_INTEGER;
RIGHT: UCL_UNSIGNED_INTEGER) return UCL_INTEGER;
function POWER (LEFT: UCL_UNSIGNED_INTEGER;
RIGHT: UCL_UNSIGNED_INTEGER) return UCL_UNSIGNED_INTEGER;
function POWER (LEFT: UCL_REAL;
RIGHT: UCL_UNSIGNED_INTEGER) return UCL_REAL;
function POWER (LEFT: UCL_LONG_REAL;
RIGHT: UCL_UNSIGNED_INTEGER) return UCL_LONG_REAL;
–– Exponentiation operations.
–– Raise CLS.PARAMETER_ERROR if RIGHT is less than 0.
–– Raise CLS.RANGE_ERROR if the required operation
–– yields an invalid result.
function ”+” (LEFT: UCL_DURATION; RIGHT: UCL_TIME) return UCL_TIME;
function ”+” (LEFT: UCL_TIME; RIGHT: UCL_DURATION) return UCL_TIME;
function ”–” (LEFT: UCL_TIME; RIGHT: UCL_DURATION) return UCL_TIME;
function ”–” (LEFT: UCL_TIME; RIGHT: UCL_TIME) return UCL_DURATION;
function ”=” (LEFT: UCL_TIME; RIGHT: UCL_TIME) return BOOLEAN;
–– Operations on time and duration.
–– Raise CLS.RANGE_ERROR if the required operation
–– yields an invalid result.
–– Raise CLS.PARAMETER_ERROR if a parameter has the value NO_TIME (~:~)
function ”+” (LEFT, RIGHT: UCL_SET) return UCL_SET;
function ”–” (LEFT, RIGHT: UCL_SET) return UCL_SET;
function ”*” (LEFT, RIGHT: UCL_SET) return UCL_SET;
function ”/” (LEFT, RIGHT: UCL_SET) return UCL_SET;
function ”

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–– Operations on string.
function ELEMENT (S: UCL_STRING; INDEX: UCL_INTEGER) return CHARACTER;
function ELEMENT (S: UCL_STRING; INDEX: UCL_INTEGER) return UCL_CHARACTER;
–– Read string components.
–– Raise CLS.RANGE_ERROR if the given index is out of bounds.
procedure ASSIGN (TARGET: in out UCL_STRING;
SOURCE: UCL_STRING);
–– Assign a UCL String.
–– Raise CLS.RANGE_ERROR if the actual length of SOURCE is greater
–– than the max. length of TARGET.
procedure ASSIGN (TARGET: in out UCL_STRING;
SOURCE: CHARACTER;
INDEX: UCL_INTEGER);
procedure ASSIGN (TARGET: in out UCL_STRING;
SOURCE: UCL_CHARACTER;
INDEX: UCL_INTEGER);
–– Assign a string component.
–– Raise CLS.RANGE_ERROR if the given index is out of bounds.
end CLS_TYPES;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
93 von/of: 662

Space Infrastructure
6.4 Flexible Tool Invocation Interface
Informal Interface Description
This service is provided to start external tools from I_MDB.
Formal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
94 von/of: 662
The detailed description of this interface is defined in the MDA Users Reference Manual, applicable document
2.1.5.5, section 4.6.

Space Infrastructure
6.5 Foreign Key Support / PUI Support
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
95 von/of: 662
The detailed description of this interface is defined in the MDA Users Reference Manual, applicable document
2.1.5.5, section 4.5.

Space Infrastructure
6.6 MDB Batch Data Entry Format
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
96 von/of: 662
The detailed description of this interface is defined in the MDA Users Reference Manual, applicable document
NO TAG, section 13.

Space Infrastructure
6.7 I–Code Definition
6.7.1 Functional Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
97 von/of: 662
I–Code (for “Intermediate Code”) is the object code produced by the UCL compiler. It has binary format and
is directly executable by the I–Code interpreters, on–board (in DMS) as well as on ground (in VICOS and CSS).
The I–Code has identical format and is interchangeable between ground and on–board.
Each I–Code instruction is an unsigned byte, possibly followed by one or two instruction specific parameters.
I–Code can be regarded as the instruction set of a Virtual Stack Machine which is implemented by the I–Code
interpreters. A stack machine is characterized by the fact that instructions do not address their operands directly
but access them via the Expression Stack. Prior to instruction execution, all operands needed must be explicitly
loaded from their memory locations onto the stack. Each instruction pops its input operands from the stack and
pushes its result operands back onto the stack where they are available as input to subsequent instructions. Dedicated
Load and Store instructions move data items from memory onto the stack and from the stack into memory,
respectively.
The architecture of the stack machine and the I–Code instructions with their parameters and semantics are described
in detail in the following sections.
Note that UCL I–Code and the underlying stack machine architecture are based on N. Wirth’s Modula–2 M–
Code and the Lilith architecture, but appropriately redesigned and extended with respect to software interpretation
and the specific needs of UCL.

Space Infrastructure
6.7.2 I–Code Record Layout
Figure 6.7–1 I–Code Record
Import list size
Code size
Global data size
Constant area size
Relocation table size
Conversion table size
Source ref. table size
Import list
Code
Constant area
Relocation table
Conversion table
Source reference table
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
WORD
WORD
WORD
WORD
WORD
WORD
WORD
WORDS
BYTES
WORDS
WORDS
WORDS
WORDS
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
98 von/of: 662
The I–Code record is generated by the UCL compiler and kept in the database. On the other hand, small
(pseudo–)APs may be generated by the HLCL interpreters in the HCI and directly sent via message over the
network.
The I–Code record, when retrieved from the database or received via message, is decomposed by the interpreter
into global data and code parts. Actual parameters delivered with an activation request are copied into the first
few global data words before start of the I–Code interpretation.
The I–Code record format shown above is mapped into a byte array. The size indications in the header, however,
count actual items, i.e. bytes in the code part, words in the other parts.

Space Infrastructure
6.7.3 I–Code Record Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
99 von/of: 662
Header
The header consists of the following 7 items. Each item is stored in one word (4 bytes). The header size is thus
7 words:
• The size of the import list in words
• The size of the code in bytes
• The size of the global data area in words
• The size of the constant area in words
• The size of the relocation table in words
• The size of the conversion table in words
• The size of the source reference table in words
Import list
The import list lists the SIDs of all imported user libraries. The user library with the external reference number
1 (i.e. the first library in the source module’s import list) is the first entry in this import list, the library 2 the
second, and so on. Each library SID occupies one word of storage.
Code
The code area is a byte–oriented stream of the I–code. It is copied into the stack machine’s code buffer at program
load time (see also code buffer description later in this document). After copying the code area into the code
buffer, all external library calls have to be relocated.
Constant area
The constant area holds long constants referenced in the I–code, e.g. strings or state codes. It may also contain
integer or real values, e.g. to reduce the storage required by often used values. Each constant will be word–
aligned.
Relocation table
The relocation table is used to relocate the references to external (i.e. imported) libraries. Each instruction referencing
user libraries references the called library using a number, the library’s SID is then found via the import
list. Different modules may use different numbers in referencing the same library, depending on the order (and/or
number) of imported libraries. The relocation step assigns then the same number for the same library to each
“external” instruction. Each entry in the relocation table is one word long and points into the code buffer, giving
the address of the library number to be relocated.
Conversion table
The conversion table is intended to support conversion of numeric values of different types in the I–Code record
to different physical representations for different target computers. It contains references to all numeric values
that are subject to such conversion.
The detailed structure of the conversion table is TBD.
Source reference table
The source reference table maps code positions (PCs) on source line numbers. It is a list of pairs (PC, line
number), where the PC defines the start of the source line. The end of the source line is given by the PC of the
next pair minus one, or by the end of the list, respectively.
6.7.4 Architecture of the Stack Machine
Module Base Table

Space Infrastructure
Code Buffer
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
100 von/of: 662
A byte structured data area that contains the I–Code of the program to be executed. The main procedure and each
imported (user) library have a separate frame in the Code Buffer, with the main procedure as frame 0 and the
library frames numbered by the order of imports. The Module Base Table contains a pointer to each global data
frame, which contains a pointer to the corresponding frame in the Code Buffer. Each frame is headed by an Entry
Table whose 2–byte entries contain the relative start addresses of the procedures and functions of that frame,
with the main program as procedure 0.
Memory (Data Stack)
The memory of the Stack Machine that stores all data processed by the machine. The memory is word structured,
data contained in the memory is represented as stated in chapter 6.3.2.
The memory is organized as a Data Stack holding “frames” of data.
• A global data frame for the main procedure (frame 0).
• A global data frame for each imported library (frames 1 .. n, numbered by the order of imports).
• A procedure frame for each active procedure/function. Each procedure call pushes a procedure frame
on the Data Stack, and each return from a procedure pops its frame from the stack.
The Module Base Table contains a pointer to each of the global data frames.
Expression Stack
A word structured stack that contains operands of I–Code operations. All arithmetic is performed on the Expression
Stack: operands are popped from the stack, and the result is pushed on the stack again.
The expression stack is organized in 4–byte words. Values on the stack are represented as stated in chapter 6.3.2.
• For one–word scalar values the value itself is pushed on the stack, occupying one word.
• For two–word scalar values the value itself is pushed on the stack, occupying two words.
• For fixed structured values an address pointing to the start of the value in memory is pushed on the stack,
occupying one word.
• For open array parameters and open string parameters first an address pointing to the data in memory
and then the upper bound are pushed on the stack, each occupying one word.

Space Infrastructure
Registers
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
101 von/of: 662
The registers contain pointers to locations in the above–mentioned data areas. They are implicitly manipulated
by I–Code instructions.
SP “Stack Pointer” –> Expression Stack
points to the value on top of the stack.
MP “Memory Pointer” –> Data Stack (Memory)
points to the first free position in the Data Stack.
GP “Global Data Pointer” –> Data Stack (Memory)
points to the start of the current global data frame.
FP “Frame pointer” –> Data Stack (Memory)
points to the procedure frame of the currently executed procedure/function.
CP “Code pointer” –> Code Buffer
points to the start of the current code frame.
PC “Program Counter” –> Code Buffer
points to the I–Code instruction currently executed.

Space Infrastructure
BASE
Module 0: Main procedure
Module 1: library 1
Module 2: library 2
Pointer to global data frame
GP
FP
MP
–3
–2
–1
0
n
–3
–2
–1
0
n
MEMORY
Global data frame 0
Global data frame 1
Initialization flag
Pointer to code frame
Pointer to constant area
AP parameters
(1 or 2 words per parameter)
Scalar: the value
Structured: the address
Global variables
(1 or 2 words for each variable)
Scalar: the value
Structured: a pointer to
the allocated data structure
Constant area
(Contents addressed via pointer
to constant area)
Global data structures
(referenced by pointers
in the global data frames)
Procedure frame
Procedure frame
Global link
(missing for local calls)
Dynamic link
Return address
Parameters
(1 or 2 words per parameter)
Scalar: value or addr. (VAR parameter)
Structured: always the address
Local variables
(1 or 2 words for each variable)
Scalar: the value
Structured: a pointer to
the allocated data structure
Allocated data structures
(referenced by pointers
in the current procedure frame)
Temporarily allocated data
free memory
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
102 von/of: 662
CODE
Code frame 0
Code frame 1
Global data frame 2 Code frame 2
Figure 6.7–2 Stack Machine Runtime Layout
6.7.5 I–Code Instructions
0
Entry list:
Offsets to start of procedures
Procedure 1
Procedure 2
...
Procedure n
Procedure 0 (global code)
LEGEND:
FP
CP
PC
General items
are marked grey
Detailed views
are outlined
In a row of items of the same
kind, the last item is always
shown in detailed view
Stack Machine
registers are shown
using inverse boxes

Space Infrastructure
6.7.5.1 Instruction Format
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
103 von/of: 662
Each I–Code instruction is one byte, possibly followed by one or two parameters. The instruction currently executed
is pointed to by the program counter register (PC). Each instruction moves the PC to the instruction that
is to be executed next, this is normally the following instruction, unless the control flow is to be explicitly altered
(jumps, procedure calls etc.).
All instructions access their input and output operands (if any) via the expression stack: operands read by the
instruction are popped off the stack, results produced by the instruction are pushed on the stack.
For some very frequent Load, Store and Call instructions with a parameter in the range 0 .. 15 additional short
forms have been introduced to avoid the explicit parameter and thus to obtain more compact code: e.g. the 1–byte
(parameterless) instructions LOAD_C.0, LOAD_C.1, LOAD_C.2 etc. have the same meaning as the 2–byte
(parameterized) instructions LOAD_C.b 0, LOAD_C.b 1, LOAD_C.b 2 etc.
The following table contains a detailed description of all I–Code instructions. For each instruction the following
details are given:
• the binary code: a value in the range 00 .. FF.
• the mnemonic: a suggestive symbolic name indicating the function performed by the instruction. Variations
of a function are denoted by different suffixes to the basic name, separated by an underscore. If
different instructions perform the same function with a difference only in the in the size of the operands,
their names consist of the basic name plus a suffix separated by a dot (”.b” for byte operands, ”.h” for
halfword operands and ”.w” for word operands). The suffix will be, by convention, written in lower
case. For instructions with implied operands, the suffix denotes the implied value, e.g. ”.0”, ”.1”, etc.
• the parameters of the instruction. Parameters may be one to four bytes long, the length is indicated with
each parameter. The parameters are interpreted signed or unsigned, depending on the instruction.
• the modes in which the instruction might be executed. The Stack Machine distinguishes between three
instruction modes:
“normal” This is the normal mode of the Stack Machine. After each instruction the Stack Machine
is reset into this mode.
“double” This mode is used to switch from single word to double word operation of the Stack
Machine. Double word I–code operations are currently supported only for 64 bit
reals.The Stack Machine is switched into this mode by prefixing the next I–code
instruction with a DOUBLE instruction.
“multi” This mode is used for multiple word operations. The Stack Machine is switched into
this mode by prefixing the next I–code instruction with a MULTI instruction.
• If an instruction is not allowed to be executed in a particular mode, then no explanation is given in the
following instruction table, as a result the instruction causes a run–time trap.
• the instruction title (a short informal description).

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
104 von/of: 662
• the effect on the expression stack (given in brackets after the title): the “=>” sign separates input items
popped off the stack (left) and output items pushed onto the stack (right):
[ x, y => z ]
states that the instruction pops x and y from the stack and, as a result, pushes z on the stack. Optional
items are enclosed in parentheses.
• a semantics specification given as a piece of Ada–like pseudo–code. These pieces of pseudo–code are
not to be understood as optimized algorithms, but rather as an easy–to–understand semantics description.
Note that a different semantic is associated with each instruction mode.
6.7.5.2 Conventions
The following conventions are applied in the I–Code description:
• Data representation of UCL runtime values is according to the conventions stated in chapter 6.3.2.
(two bullets deleted)
• The term “halfword” and “word” denote 2–byte and 4–byte values, respectively.
The term “double word” denotes an 8–byte value.
• The parameters are interpreted signed or unsigned, depending on the instruction.
• The PC is assumed to point to the code byte of the instruction currently executed. It is not explicitly
shown that each instruction implicitly advances the PC to the next instruction (PC := PC + 1 + parameter
length), if it does not explicitly alter the control flow.
• Distances used to calculate a new PC value are offsets to the current PC.
• The registers of the stack machine (SP, MP, FP, GP, PC) are used as variables.
• Auxiliary variables are used in a suggestive manner:
A denotes an address,
B denotes a boolean value,
D denotes a duration,
T denotes a time,
I, L, N stand for integer numbers,
X, Y denote arithmetic operands of the type imposed by the instruction, sets are regarded as
boolean arrays of 32 bits packed in a word
• The Module Base Table is regarded as an array of words, named BASE, pointing to the start of the global
data frame of a module.
• The Code Buffer is regarded as an array of bytes, named CODE.
• The Memory is regarded as an array of words, named MEMORY.
• The expression stack is regarded as an array of words, named STACK, where the SP points to the element
on top of the stack. Stack manipulations are indicated with calls to the procedures PUSH and
POP for words and PUSHD and POPD for double words defined as:
PUSH (X) => SP := SP + 1; STACK(SP) := X;
PUSHD (X) => SP := SP + 2; STACK(SP–1 .. SP) := X;
POP (X) => X := STACK(SP); SP := SP – 1;
POPD (X) => X := STACK(SP–1 .. SP); SP := SP – 2;
• The following functions are used to obtain control information from the Memory and the Code Buffer:
CONST_ADR (A) address of constant at offset A in constant area of current global data
frame
=> return MEMORY(GP–1) + A;

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
105 von/of: 662
PROC (N) entry point of procedure N in current code frame
=> return CP + VALUE (CODE(CP+N*2 .. CP+N*2 + 1));
SIZE (SID) size (in words) of data value associated with database object designated
by SID.

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
106 von/of: 662
• The following procedures and functions are used to denote Stack Machine system services:
SET_BYTE (i, W, X) set i–th byte in word W to value X
BYTE (i, W) extract i–th byte from word W
VALUE (bytes) compute numerical value from byte array
STRING (A) return the string stored under address A
SYSTEM (L, P) call system service P in system library L
READ (SID, TYPE, X) read end item value for SID of SW type TYPE into variable X
READD (SID, TYPE, X) read end item value for SID of SW type TYPE into double word
variable X
READM (SID, TYPE, A) read multiple–word value for SID of SW type TYPE to address A
WRITE (SID, TYPE, X) write end item value for SID of SW type TYPE from variable X
WRITED (SID, TYPE, X) write end item value for SID of SW type TYPE from double word
variable X
WRITEM (SID, TYPE, A) write multiple–word value for SID of SW type TYPE from address A
ERROR (E) abort with runtime error E
TRAP (T) abort with runtime error trap T
HALT (S) stop execution and return success code S (0 = success, 1 = failure)

Space Infrastructure
6.7.5.3 Detailed I–code Instructions Table
6.7.5.3.1 Instructions with implied parameter
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
107 von/of: 662
These instructions are special cases of the corresponding instructions with explicit parameter. They have been
introduced for optimization, since these instructions (particularly with small range parameters) cover a great
percentage of every program.
Hex | Mnemonic | Param. | Mode | Semantics
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
00 | LOAD_C.0 | | | Load constant 0 .. 15 [ => val ]
01 | LOAD_C.1 | | |
02 | LOAD_C.2 | | |–––––––––––––––––––––––––––––––––––––––––––––
03 | LOAD_C.3 | | |
04 | LOAD_C.4 | | Normal | PUSH (n); –– n = 0 .. 15
05 | LOAD_C.5 | | |
06 | LOAD_C.6 | |––––––––+–––––––––––––––––––––––––––––––––––––––––––––
07 | LOAD_C.7 | | |
08 | LOAD_C.8 | | Double | PUSHD (n); –– n = 0 .. 15
09 | LOAD_C.9 | | |
0A | LOAD_C.10 | | |
0B | LOAD_C.11 | | |
0C | LOAD_C.12 | | |
0D | LOAD_C.13 | | |
0E | LOAD_C.14 | | |
0F | LOAD_C.15 | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
10 | LOAD_L.0 | | | Load local variable [ => val ]
11 | LOAD_L.1 | | | from address 0 .. 15
12 | LOAD_L.2 | | |
13 | LOAD_L.3 | | |–––––––––––––––––––––––––––––––––––––––––––––
14 | LOAD_L.4 | | |
15 | LOAD_L.5 | | Normal | PUSH (MEMORY(FP + n));
16 | LOAD_L.6 | | |
17 | LOAD_L.7 | |––––––––+–––––––––––––––––––––––––––––––––––––––––––––
18 | LOAD_L.8 | | |
19 | LOAD_L.9 | | Double | PUSHD (MEMORY(FP + n .. FP + n + 1));
1A | LOAD_L.10 | | |
1B | LOAD_L.11 | | |
1C | LOAD_L.12 | | |
1D | LOAD_L.13 | | |
1E | LOAD_L.14 | | |
1F | LOAD_L.15 | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
108 von/of: 662
Hex | Mnemonic | Param. | Mode | Semantics
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
20 | LOAD_G.0 | | | Load global variable [ => val ]
21 | LOAD_G.1 | | | from address 0 .. 15
22 | LOAD_G.2 | | |
23 | LOAD_G.3 | | |–––––––––––––––––––––––––––––––––––––––––––––
24 | LOAD_G.4 | | |
25 | LOAD_G.5 | | Normal | PUSH (MEMORY(GP + n));
26 | LOAD_G.6 | | |
27 | LOAD_G.7 | |––––––––+–––––––––––––––––––––––––––––––––––––––––––––
28 | LOAD_G.8 | | |
29 | LOAD_G.9 | | Double | PUSHD (MEMORY(GP + n .. GP + n + 1));
2A | LOAD_G.10 | | |
2B | LOAD_G.11 | | |
2C | LOAD_G.12 | | |
2D | LOAD_G.13 | | |
2E | LOAD_G.14 | | |
2F | LOAD_G.15 | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
30 | LOAD_F.0 | | | Load offsetted variable [ adr => val ]
31 | LOAD_F.1 | | | from address 0 .. 15
32 | LOAD_F.2 | | |
33 | LOAD_F.3 | | |–––––––––––––––––––––––––––––––––––––––––––––
34 | LOAD_F.4 | | |
35 | LOAD_F.5 | | Normal | POP (A);
36 | LOAD_F.6 | | | PUSH (MEMORY(A + n));
37 | LOAD_F.7 | | |
38 | LOAD_F.8 | |––––––––+–––––––––––––––––––––––––––––––––––––––––––––
39 | LOAD_F.9 | | |
3A | LOAD_F.10 | | Double | POP (A);
3B | LOAD_F.11 | | | PUSHD (MEMORY(A + n .. A + n + 1));
3C | LOAD_F.12 | | |
3D | LOAD_F.13 | | |
3E | LOAD_F.14 | | |
3F | LOAD_F.15 | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
40 | STOR_L.0 | | | Store local variable [ val => ]
41 | STOR_L.1 | | | at address 0 .. 15
42 | STOR_L.2 | | |
43 | STOR_L.3 | | |–––––––––––––––––––––––––––––––––––––––––––––
44 | STOR_L.4 | | |
45 | STOR_L.5 | | Normal | POP (X);
46 | STOR_L.6 | | | MEMORY(FP + n) := X;
47 | STOR_L.7 | | |
48 | STOR_L.8 | |––––––––+–––––––––––––––––––––––––––––––––––––––––––––
49 | STOR_L.9 | | |
4A | STOR_L.10 | | Double | POPD (X);
4B | STOR_L.11 | | | MEMORY(FP + n .. FP + n + 1) := X;
4C | STOR_L.12 | | |
4D | STOR_L.13 | | |
4E | STOR_L.14 | | |
4F | STOR_L.15 | | |

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
109 von/of: 662
Hex | Mnemonic | Param. | Mode | Semantics
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
50 | STOR_G.0 | | | Store global variable [ val => ]
51 | STOR_G.1 | | | at address 0 .. 15
52 | STOR_G.2 | | |
53 | STOR_G.3 | | |–––––––––––––––––––––––––––––––––––––––––––––
54 | STOR_G.4 | | |
55 | STOR_G.5 | | Normal | POP (X);
56 | STOR_G.6 | | | MEMORY(GP + n) := X;
57 | STOR_G.7 | | |
58 | STOR_G.8 | |––––––––+–––––––––––––––––––––––––––––––––––––––––––––
59 | STOR_G.9 | | |
5A | STOR_G.10 | | Double | POPD (X);
5B | STOR_G.11 | | | MEMORY(GP + n .. GP + n + 1) := X;
5C | STOR_G.12 | | |
5D | STOR_G.13 | | |
5E | STOR_G.14 | | |
5F | STOR_G.15 | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
60 | STOR_F.0 | | | Store offsetted variable [ adr, val => ]
61 | STOR_F.1 | | | at address 0 .. 15
62 | STOR_F.2 | | |
63 | STOR_F.3 | | |–––––––––––––––––––––––––––––––––––––––––––––
64 | STOR_F.4 | | |
65 | STOR_F.5 | | Normal | POP (X);
66 | STOR_F.6 | | | POP (A);
67 | STOR_F.7 | | | MEMORY(A + n) := X;
68 | STOR_F.8 | | |
69 | STOR_F.9 | |––––––––+–––––––––––––––––––––––––––––––––––––––––––––
6A | STOR_F.10 | | |
6B | STOR_F.11 | | Double | POPD (X);
6C | STOR_F.12 | | | POP (A);
6D | STOR_F.13 | | | MEMORY(A + n .. A + n + 1) := X;
6E | STOR_F.14 | | |
6F | STOR_F.15 | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
70 | ––– | | |
71 | CALL.1 | | Normal | Call procedure/function 1 .. 15 [ ]
72 | CALL.2 | | |
73 | CALL.3 | | | MEMORY (MP) := FP; –– save dynamic link
74 | CALL.4 | | | MEMORY (MP+1) := PC+1; –– save return addr.
75 | CALL.5 | | |
76 | CALL.6 | | | MP := MP + 2;
77 | CALL.7 | | | FP := MP; –– mark stack frame
78 | CALL.8 | | | PC := PROC (n); –– jump
79 | CALL.9 | | | –– n = 1 .. 15
7A | CALL.10 | | |
7B | CALL.11 | | |
7C | CALL.12 | | | Note: There is no CALL.0 instruction.
7D | CALL.13 | | | A main program cannot call itself.
7E | CALL.14 | | |
7F | CALL.15 | | |

Space Infrastructure
6.7.5.3.2 Load Instructions
These instructions push data from the Memory onto the Expression Stack.
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
110 von/of: 662
Hex | Mnemonic | Param. | Mode | Semantics
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
80 | LOAD_T.b | offs 1 | | Load constant from table [ => val ]
| | unsigned| |
| | | |–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Normal | PUSH (MEMORY(CONST_ADR(offs)));
| | | |
| | |––––––––+–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Double | PUSHD (MEMORY(CONST_ADR(offs) ..
| | | | CONST_ADR(offs) + 1));
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
81 | LOAD_T.h | offs 2 | | Load constant with halfword [ => val ]
| | unsigned| | offset from table
| | | |
| | | |–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Normal | PUSH (MEMORY(CONST_ADR(offs)));
| | | |
| | |––––––––+–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Double | PUSHD (MEMORY(CONST_ADR(offs) ..
| | | | CONST_ADR(offs) + 1));
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
82 | LOAD_C.b | val 1 | | Load byte constant [ => val ]
| | signed | |
| | | |–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Normal | PUSH (val);
| | | |
| | |––––––––+–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Double | PUSHD (val);
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
111 von/of: 662
Hex | Mnemonic | Param. | Mode | Semantics
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
83 | LOAD_C.h | val 2 | | Load halfword (2–byte) constant [ => val ]
| | signed | |
| | | |–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Normal | PUSH (val);
| | | |
| | |––––––––+–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Double | PUSHD (val);
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
84 | LOAD_C.w | val 4 | | Load word (4–byte) constant [ => val ]
| | signed | |
| | | |–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Normal | PUSH (val);
| | | |
| | |––––––––+–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Double | PUSHD (val);
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
85 | LOAD_L.b | adr 1 | | Load local variable [ => val ]
| | unsigned| |
| | | |–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Normal | PUSH (MEMORY(FP + adr));
| | | |
| | |––––––––+–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Double | PUSHD (MEMORY(FP + adr .. FP + adr + 1));
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
86 | LOAD_G.b | adr 1 | | Load global variable [ => val ]
| | unsigned| |
| | | |–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Normal | PUSH (MEMORY(GP + adr));
| | | |
| | |––––––––+–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Double | PUSHD (MEMORY(GP + adr .. GP + adr + 1));
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
112 von/of: 662
Hex | Mnemonic | Param. | Mode | Semantics
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
87 | LOAD_F.b | offs 1 | | Load offsetted variable [ adr => val ]
| | unsigned| |
| | | |–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Normal | POP (A);
| | | | PUSH (MEMORY(A + offs));
| | | |
| | |––––––––+–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Double | POP (A);
| | | | PUSHD (MEMORY(A + offs .. A + offs + 1));
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
88 | LOAD_F.h | offs 2 | | Load offsetted variable [ adr => val ]
| | unsigned| | with halfword offset
| | | |
| | | |–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Normal | POP (A);
| | | | PUSH (MEMORY(A + offs));
| | | |
| | |––––––––+–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Double | POP (A);
| | | | PUSHD (MEMORY(A + offs .. A + offs + 1));
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
89 | LOAD_E | lib 1 | | Load external variable [ => val ]
| | unsigned| |
| | | |–––––––––––––––––––––––––––––––––––––––––––––
| | adr 1 | |
| | unsigned| Normal | PUSH (MEMORY(BASE(lib) + adr));
| | | |
| | |––––––––+–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Double | PUSHD (MEMORY(BASE(lib) + adr ..
| | | | BASE(lib) + adr + 1));
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
8A | LOAD_X_C | | Normal | Load indexed character [ adr, inx => val ]
| | | |
| | | | POP (I);
| | | | POP (A);
| | | | I := I – 1;
| | | | if I < 0 or I >= MEMORY(A) then
| | | | TRAP (range_error);
| | | | else
| | | | PUSH (BYTE(I mod 4, MEMORY(A + 1 + I/4)));
| | | | end if;
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
113 von/of: 662
Hex | Mnemonic | Param. | Mode | Semantics
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
8B | LOAD_X_V | | | Load indexed variable [ adr, inx => val ]
| | | |
| | | |–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Normal | POP (I);
| | | | POP (A);
| | | | PUSH (MEMORY(A + I));
| | | |
| | |––––––––+–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Double | POP (I);
| | | | POP (A);
| | | | PUSHD (MEMORY(A + I * 2) ..
| | | | MEMORY(A + I * 2 + 1));
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
8C | ––– | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––

Space Infrastructure
6.7.5.3.3 Load Address Instructions
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
These instructions push the Memory address of data on the Expression Stack.
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
114 von/of: 662
Hex | Mnemonic | Param. | Mode | Semantics
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
8D | LOAD_A_L.b | adr 1 | Normal | Load local address [ => adr ]
| | unsigned| |
| | | | PUSH (FP + adr);
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
8E | LOAD_A_G.b | adr 1 | Normal | Load global address [ => adr ]
| | unsigned| |
| | | | PUSH (GP + adr);
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
8F | LOAD_A_F.b | offs 1 | Normal | Load offsetted address [ adr => adr ]
| | unsigned| |
| | | | POP (A);
| | | | PUSH (A + offs);
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
90 | LOAD_A_F.h | offs 2 | Normal | Load offsetted address [ adr => adr ]
| | unsigned| | with halfword offset
| | | |
| | | | POP (A);
| | | | PUSH (A + offs);
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
91 | LOAD_A_E | lib 1 | Normal | Load external address [ => adr ]
| | unsigned| |
| | | | PUSH (BASE(lib) + adr);
| | adr 1 | |
| | unsigned| |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
92 | LOAD_A_T.b | offs 1 | Normal | Load address of constant in [ => adr ]
| | unsigned| | constant table
| | | |
| | | | PUSH (CONST_ADR(offs));
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
93 | LOAD_A_T.h | offs 2 | Normal | Load address of constant in [ => adr ]
| | unsigned| | constant table with halfword offset
| | | |
| | | | PUSH (CONST_ADR(offs));
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––

Space Infrastructure
6.7.5.3.4 Store Instructions
Theses instructions pop data from the Expression Stack into the Memory.
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
115 von/of: 662
Hex | Mnemonic | Param. | Mode | Semantics
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
94 | STOR_L.b | adr 1 | | Store local variable [ val => ]
| | unsigned| |
| | | |–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Normal | POP (X);
| | | | MEMORY(FP + adr) := X;
| | | |
| | |––––––––+–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Double | POPD (X);
| | | | MEMORY(FP + adr .. FP + adr + 1) := X;
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
95 | STOR_G.b | adr 1 | | Store global variable [ val => ]
| | unsigned| |
| | | |–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Normal | POP (X);
| | | | MEMORY(GP + adr) := X;
| | | |
| | |––––––––+–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Double | POPD (X);
| | | | MEMORY(GP + adr .. GP + adr + 1) := X;
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
96 | STOR_F.b | offs 1 | | Store offsetted variable [ adr, val => ]
| | unsigned| |
| | | |–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Normal | POP (X);
| | | | POP (A);
| | | | MEMORY(A + offs) := X;
| | | |
| | |––––––––+–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Double | POPD (X);
| | | | POP (A);
| | | | MEMORY(A + offs .. A + offs + 1) := X;
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
116 von/of: 662
Hex | Mnemonic | Param. | Mode | Semantics
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
97 | STOR_F.h | offs 2 | | Store offsetted variable [ adr, val => ]
| | unsigned| | with halfword offset
| | | |
| | | |–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Normal | POP (X);
| | | | POP (A);
| | | | MEMORY(A + offs) := X;
| | | |
| | |––––––––+–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Double | POPD (X);
| | | | POP (A);
| | | | MEMORY(A + offs .. A + offs + 1) := X;
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
98 | STOR_E | lib 1 | | Store external variable [ val => ]
| | unsigned| |
| | | |–––––––––––––––––––––––––––––––––––––––––––––
| | adr 1 | |
| | unsigned| Normal | POP (X);
| | | | MEMORY(BASE(lib) + adr) := X;
| | | |
| | |––––––––+–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Double | POPD (X);
| | | | MEMORY(BASE(lib) + adr ..
| | | | BASE(lib) + adr + 1) := X;
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
99 | STOR_X_C | | Normal | Store indexed character [ adr, inx, val => ]
| | | |
| | | | POP (X);
| | | | POP (I);
| | | | POP (A);
| | | | I := I – 1;
| | | | if I < 0 or I >= MEMORY(A) then
| | | | TRAP (range_error);
| | | | else
| | | | SET_BYTE (I mod 4, MEMORY(A + 1 + I/4), X);
| | | | end if;
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
117 von/of: 662
Hex | Mnemonic | Param. | Mode | Semantics
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
9A | STOR_X_V | | | Store indexed variable [ adr, inx, val => ]
| | | |
| | | |–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Normal | POP (X);
| | | | POP (I);
| | | | POP (A);
| | | | MEMORY(A + I) := X;
| | | |
| | |––––––––+–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Double | POPD (X);
| | | | POP (I);
| | | | POP (A);
| | | | MEMORY(A + I * 2 .. A + I * 2 + 1) := X;
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––

Space Infrastructure
6.7.5.3.5 MOVE and CAT Instructions
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
The MOVE instruction copies multiple–word data between Memory locations.
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
118 von/of: 662
Hex | Mnemonic | Param. | Mode | Semantics
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––––
9B | MOVE | | Normal | Move block of data [ adr, adr, len ]
| | | |
| | | | POP (L);
| | | | POP (A2);
| | | | POP (A1);
| | | | MEMORY(A1 .. A1+L–1) := MEMORY(A2 .. A2+L–1);
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––––
The CAT instruction concatenates two strings.
Hex | Mnemonic | Param. | Mode | Semantics
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––––
9C | CAT | | Normal | String concatenation [ adr, adr, size => adr ]
| | | |
| | | | POP (L);
| | | | POP (A2);
| | | | POP (A1);
| | | | PUSH (MP);
| | | |
| | | | L1 := MEMORY(A1); –– length of first string
| | | | L2 := MEMORY(A2); –– length of second string
| | | | MEMORY (MP) := L1 + L2; –– resultant length
| | | |
| | | | MEMORY (MP + 1 .. MP + L – 1) :=
| | | | STRING (A1) & STRING (A2); –– concatenation
| | | |
| | | | MP := MP + L;
| | | |
| | | | –– This instruction implicitly allocates
| | | | –– space in memory
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––––

Space Infrastructure
6.7.5.3.6 Stack Instructions
These instructions manipulate the Expression Stack only.
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
119 von/of: 662
Hex | Mnemonic | Param. | Mode | Semantics
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
9D | COPY | | | Copy top of stack [ val => val, val ]
| | | |
| | | |–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Normal | POP (X); PUSH (X); PUSH (X);
| | | |
| | |––––––––+–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Double | POPD (X); PUSHD (X); PUSHD (X);
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
9E | POP | n 1 | | Remove n items from top [ val (,...) => ]
| | unsigned| | of stack
| | | |
| | | |–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Normal | SP := SP – n;
| | | |
| | |––––––––+–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Double | SP := SP – 2 * n;
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
9F | SWAP | | | Swap data on top [ val, val => val, val ]
| | | | of stack
| | | |
| | | |–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Normal | POP (X);
| | | | POP (Y);
| | | | PUSH (X);
| | | | PUSH (Y);
| | | |
| | |––––––––+–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Double | POPD (X);
| | | | POPD (Y);
| | | | PUSHD (X);
| | | | PUSHD (Y);
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––

Space Infrastructure
6.7.5.3.7 Numerical Instructions
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
120 von/of: 662
These instructions perform different numerical operations, they usually pop their operands from the Expression
Stack and push their result back on the Expression Stack.
a) INTEGER operations
Hex | Mnemonic | Param. | Mode | Semantics
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
A0 | ADD_I | | Normal | Add integers [ val, val => val ]
| | | |
| | | | POP (Y);
| | | | POP (X);
| | | | PUSH (X + Y);
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
A1 | SUB_I | | Normal | Subtract integers [ val, val => val ]
| | | |
| | | | POP (Y);
| | | | POP (X);
| | | | PUSH (X – Y);
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
A2 | MUL_I | | Normal | Multiply integers [ val, val => val ]
| | | |
| | | | POP (Y);
| | | | POP (X);
| | | | PUSH (X * Y);
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
A3 | DIV_I | | Normal | Divide integers [ val, val => val ]
| | | |
| | | | POP (Y);
| | | | POP (X);
| | | | PUSH (X / Y);
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
A4 | EXP_I | | Normal | Exponentiate integer [ val, val => val ]
| | | |
| | | | POP (Y);
| | | | POP (X);
| | | | PUSH (X ** Y);
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
A5 | MOD_I | | Normal | Modulus [ val, val => val ]
| | | |
| | | | POP (Y);
| | | | POP (X);
| | | | PUSH (X mod Y);
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
121 von/of: 662
Hex | Mnemonic | Param. | Mode | Semantics
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
A6 | NEG_I | | Normal | Negate integer [ val => val ]
| | | |
| | | | POP (X);
| | | | PUSH (–X);
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
A7 | ABS_I | | Normal | Absolute integer value [ val => val ]
| | | |
| | | | POP (X);
| | | | PUSH (abs X);
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––

Space Infrastructure
b) UNSIGNED_INTEGER operations
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
122 von/of: 662
Hex | Mnemonic | Param. | Mode | Semantics
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
A8 | ADD_U | | Normal | Add unsigned [ val, val => val ]
| | | |
| | | | POP (Y);
| | | | POP (X);
| | | | PUSH (X + Y);
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
A9 | SUB_U | | Normal | Subtract unsigned [ val, val => val ]
| | | |
| | | | POP (Y);
| | | | POP (X);
| | | | PUSH (X – Y);
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
AA | MUL_U | | Normal | Multiply unsigned [ val, val => val ]
| | | |
| | | | POP (Y);
| | | | POP (X);
| | | | PUSH (X * Y);
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
AB | DIV_U | | Normal | Divide unsigned [ val, val => val ]
| | | |
| | | | POP (Y);
| | | | POP (X);
| | | | PUSH (X / Y);
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
AC | EXP_U | | Normal | Exponentiate unsigned [ val, val => val ]
| | | |
| | | | POP (Y);
| | | | POP (X);
| | | | PUSH (X ** Y);
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
AD | MOD_U | | Normal | Unsigned modulus [ val, val => val ]
| | | |
| | | | POP (Y);
| | | | POP (X);
| | | | PUSH (X mod Y);
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––

Space Infrastructure
c) REAL operations
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
123 von/of: 662
Hex | Mnemonic | Param. | Mode | Semantics
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
AE | ADD_R | | | Add reals [ val, val => val ]
| | | |
| | | |–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Normal | POP (Y);
| | | | POP (X);
| | | | PUSH (X + Y);
| | | |
| | |––––––––+–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Double | POPD (Y);
| | | | POPD (X);
| | | | PUSHD (X + Y);
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
AF | SUB_R | | | Subtract reals [ val, val => val ]
| | | |
| | | |–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Normal | POP (Y);
| | | | POP (X);
| | | | PUSH (X – Y);
| | | |
| | |––––––––+–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Double | POPD (Y);
| | | | POPD (X);
| | | | PUSHD (X – Y);
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
B0 | MUL_R | | | Multiply reals [ val, val => val ]
| | | |
| | | |–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Normal | POP (Y);
| | | | POP (X);
| | | | PUSH (X * Y);
| | | |
| | |––––––––+–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Double | POPD (Y);
| | | | POPD (X);
| | | | PUSHD (X * Y);
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
124 von/of: 662
Hex | Mnemonic | Param. | Mode | Semantics
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
B1 | DIV_R | | | Divide reals [ val, val => val ]
| | | |
| | | |–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Normal | POP (Y);
| | | | POP (X);
| | | | PUSH (X / Y);
| | | |
| | |––––––––+–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Double | POPD (Y);
| | | | POPD (X);
| | | | PUSHD (X / Y);
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
B2 | EXP_R | | | Exponentiate real [ val, val => val ]
| | | |
| | | |–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Normal | POP (Y);
| | | | POP (X);
| | | | PUSH (X ** Y);
| | | |
| | |––––––––+–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Double | POP (Y);
| | | | POPD (X);
| | | | PUSHD (X ** Y);
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
B3 | NEG_R | | | Negate real [ val => val ]
| | | |
| | | |–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Normal | POP (X);
| | | | PUSH (–X);
| | | |
| | |––––––––+–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Double | POPD (X);
| | | | PUSHD (–X);
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
125 von/of: 662
Hex | Mnemonic | Param. | Mode | Semantics
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
B4 | ABS_R | | | Absolute real value [ val => val ]
| | | |
| | | |–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Normal | POP (X);
| | | | PUSH (abs X);
| | | |
| | |––––––––+–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Double | POPD (X);
| | | | PUSHD (abs X);
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––

Space Infrastructure
d) TIME and DURATION operations
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
126 von/of: 662
Hex | Mnemonic | Param. | Mode | Semantics
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
B5 | ADD_D | | Normal | Add time and duration [ val, val => val ]
| | | |
| | | | POP (D);
| | | | POPD (T);
| | | | PUSHD (T + D);
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
B6 | SUB_D | | Normal | Subtract duration [ val, val => val ]
| | | | from time
| | | |
| | | | POP (D);
| | | | POPD (T);
| | | | PUSHD (T – D);
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
B7 | SUB_T | | Normal | Subtract times [ val, val => val ]
| | | |
| | | | POPD (T2);
| | | | POPD (T1);
| | | | PUSH (T1 – T2);
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
127 von/of: 662
e) SET operations
These instructions perform operations on sets. A set is regarded as a packed array of bits (BOOLEAN). A distinction
is made between 1–word and multiple–word sets: For 1–word sets the set value is directly manipulated via
the Expression Stack like any numeric value. Multiple–word sets are manipulated via their addresses on the Expression
Stack. Note that instructions that generate a multiple–word stack result implicitly allocate memory for
the result and push the address of the result on the Expression Stack.
Hex | Mnemonic | Param. | Mode | Semantics
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
B8 | ADD_S | | | Set union
| | | |
| | | |–––––––––––––––––––––––––––––––––––––––––––––
| | | | [ set, set => set ]
| | | Normal | POP (Y);
| | | | POP (X);
| | | | PUSH (X or Y);
| | | |
| | |––––––––+–––––––––––––––––––––––––––––––––––––––––––––
| | | | [ adr, adr, size => adr ]
| | | Multi | POP (L);
| | | | POP (A2);
| | | | POP (A1);
| | | | PUSH (MP);
| | | | MEMORY (MP..MP+L–1) :=
| | | | MEMORY(A1..A1+L–1) or MEMORY(A2..A2+L–1);
| | | | MP := MP + L;
| | | |
| | | | –– This instruction implicitly allocates
| | | | –– space in memory
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
128 von/of: 662
Hex | Mnemonic | Param. | Mode | Semantics
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
B9 | SUB_S | | | Set difference
| | | |
| | | |–––––––––––––––––––––––––––––––––––––––––––––
| | | | [ set, set => set ]
| | | Normal | POP (Y);
| | | | POP (X);
| | | | PUSH (X and not Y);
| | | |
| | |––––––––+–––––––––––––––––––––––––––––––––––––––––––––
| | | | [ adr, adr, size => adr ]
| | | Multi | POP (L);
| | | | POP (A2);
| | | | POP (A1);
| | | | PUSH (MP);
| | | | MEMORY (MP..MP+L–1) :=
| | | | MEMORY(A1..A1+L–1) and not
| | | | MEMORY(A2..A2+L–1);
| | | | MP := MP + L;
| | | |
| | | | –– This instruction implicitly allocates
| | | | –– space in memory
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
BA | MUL_S | | | Set intersection
| | | |
| | | |–––––––––––––––––––––––––––––––––––––––––––––
| | | | [ set, set => set ]
| | | Normal | POP (Y);
| | | | POP (X);
| | | | PUSH (X and Y);
| | | |
| | |––––––––+–––––––––––––––––––––––––––––––––––––––––––––
| | | | [ adr, adr, size => adr ]
| | | Multi | POP (L);
| | | | POP (A2);
| | | | POP (A1);
| | | | PUSH (MP);
| | | | MEMORY (MP..MP+L–1) :=
| | | | MEMORY(A1..A1+L–1) and MEMORY(A2..A2+L–1);
| | | | MP := MP + L;
| | | |
| | | | –– This instruction implicitly allocates
| | | | –– space in memory
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
129 von/of: 662
Hex | Mnemonic | Param. | Mode | Semantics
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
BB | DIV_S | | | Symmetric set difference
| | | |
| | | |–––––––––––––––––––––––––––––––––––––––––––––
| | | | [ set, set => set ]
| | | Normal | POP (Y);
| | | | POP (X);
| | | | PUSH (X xor Y);
| | | |
| | |––––––––+–––––––––––––––––––––––––––––––––––––––––––––
| | | | [ adr, adr, size => adr ]
| | | Multi | POP (L);
| | | | POP (A2);
| | | | POP (A1);
| | | | PUSH (MP);
| | | | MEMORY (MP..MP+L–1) :=
| | | | MEMORY(A1..A1+L–1) xor MEMORY(A2..A2+L–1);
| | | | MP := MP + L;
| | | |
| | | | –– This instruction implicitly allocates
| | | | –– space in memory
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
BC | INCL | | Normal | Include element in set [ adr, num => ]
| | | |
| | | | POP (N);
| | | | POP (A);
| | | | MEMORY(A + N/32)(N mod 32) := TRUE;
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
BD | EXCL | | Normal | Exclude element from set [ adr, num => ]
| | | |
| | | | POP (N);
| | | | POP (A);
| | | | MEMORY(A + N/32)(N mod 32) := FALSE;
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––

Space Infrastructure
6.7.5.3.8 Comparison Instructions
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
130 von/of: 662
These instructions perform comparisons on operands on the Expression Stack. They push a boolean value as
a result back on the Expression Stack. The multiple–word comparison instructions operate on data in the Memory
pointed by addresses on the Expression Stack.
a) GENERAL comparisons
Hex | Mnemonic | Param. | Mode | Semantics
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
BE | EQU | | | Test equal [ val, val => bool ]
| | | |
| | | |–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Normal | POP (Y);
| | | | POP (X);
| | | | PUSH (X = Y);
| | | |
| | |––––––––+–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Double | POPD (Y);
| | | | POPD (X);
| | | | PUSH (X = Y);
| | | |
| | |––––––––+–––––––––––––––––––––––––––––––––––––––––––––
| | | | [ adr, adr, size => bool ]
| | | Multi | POP (L);
| | | | POP (A2);
| | | | POP (A1);
| | | | PUSH (MEMORY(A1..A1+L–1) =
| | | | MEMORY(A2..A2+L–1));
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
131 von/of: 662
Hex | Mnemonic | Param. | Mode | Semantics
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
BF | NEQ | | | Test not equal [ val, val => bool ]
| | | |
| | | |–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Normal | POP (Y);
| | | | POP (X);
| | | | PUSH (X /= Y);
| | | |
| | |––––––––+–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Double | POPD (Y);
| | | | POPD (X);
| | | | PUSH (X /= Y);
| | | |
| | |––––––––+–––––––––––––––––––––––––––––––––––––––––––––
| | | | [ adr, adr, size => bool ]
| | | Multi | POP (L);
| | | | POP (A2);
| | | | POP (A1);
| | | | PUSH (MEMORY(A1..A1+L–1) /=
| | | | MEMORY(A2..A2+L–1));
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––

Space Infrastructure
b) INTEGER comparisons
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
132 von/of: 662
Hex | Mnemonic | Param. | Mode | Semantics
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
C0 | LES_I | | Normal | Test less (int) [ val, val => bool ]
| | | |
| | | | POP (Y);
| | | | POP (X);
| | | | PUSH (X < Y);
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
C1 | GRT_I | | Normal | Test greater (int) [ val, val => bool ]
| | | |
| | | | POP (Y);
| | | | POP (X);
| | | | PUSH (X > Y);
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
C2 | LEQ_I | | Normal | Test less/equal (int) [ val, val => bool ]
| | | |
| | | | POP (Y);
| | | | POP (X);
| | | | PUSH (X bool ]
| | | |
| | | | POP (Y);
| | | | POP (X);
| | | | PUSH (X >= Y);
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––

Space Infrastructure
c) UNSIGNED_INTEGER comparisons
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
133 von/of: 662
Hex | Mnemonic | Param. | Mode | Semantics
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
C4 | LES_U | | Normal | Test less (unsig) [ val, val => bool ]
| | | |
| | | | POP (Y);
| | | | POP (X);
| | | | PUSH (X < Y);
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
C5 | GRT_U | | Normal | Test greater (unsig) [ val, val => bool ]
| | | |
| | | | POP (Y);
| | | | POP (X);
| | | | PUSH (X > Y);
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
C6 | LEQ_U | | Normal | Test less/equal (unsig) [ val, val => bool ]
| | | |
| | | | POP (Y);
| | | | POP (X);
| | | | PUSH (X bool ]
| | | |
| | | | POP (Y);
| | | | POP (X);
| | | | PUSH (X >= Y);
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––

Space Infrastructure
d) REAL comparisons
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
134 von/of: 662
Hex | Mnemonic | Param. | Mode | Semantics
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
C8 | LES_R | | | Test less (real) [ val, val => bool ]
| | | |
| | | |–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Normal | POP (Y);
| | | | POP (X);
| | | | PUSH (X < Y);
| | | |
| | |––––––––+–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Double | POPD (Y);
| | | | POPD (X);
| | | | PUSH (X < Y);
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
C9 | GRT_R | | | Test greater (real) [ val, val => bool ]
| | | |
| | | |–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Normal | POP (Y);
| | | | POP (X);
| | | | PUSH (X > Y);
| | | |
| | |––––––––+–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Double | POPD (Y);
| | | | POPD (X);
| | | | PUSH (X > Y);
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
CA | LEQ_R | | | Test less/equal (real) [ val, val => bool ]
| | | |
| | | |–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Normal | POP (Y);
| | | | POP (X);
| | | | PUSH (X

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
135 von/of: 662
Hex | Mnemonic | Param. | Mode | Semantics
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
CB | GEQ_R | | | Test great./equ. (real) [ val, val => bool ]
| | | |
| | | |–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Normal | POP (Y);
| | | | POP (X);
| | | | PUSH (X >= Y);
| | | |
| | |––––––––+–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Double | POPD (Y);
| | | | POPD (X);
| | | | PUSH (X >= Y);
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––

Space Infrastructure
e) TIME comparisons
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
136 von/of: 662
Hex | Mnemonic | Param. | Mode | Semantics
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
CC | LES_T | | Normal | Test less (time) [ val, val => bool ]
| | | |
| | | | POPD (T2);
| | | | POPD (T1);
| | | | PUSH (T1 < T2);
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
CD | GRT_T | | Normal | Test greater (time) [ val, val => bool ]
| | | |
| | | | POPD (T2);
| | | | POPD (T1);
| | | | PUSH (T1 > T2);
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
CE | LEQ_T | | Normal | Test less/equal (time) [ val, val => bool ]
| | | |
| | | | POPD (T2);
| | | | POPD (T1);
| | | | PUSH (T1 bool ]
| | | |
| | | | POPD (T2);
| | | | POPD (T1);
| | | | PUSH (T1 >= T2);
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
137 von/of: 662
f) SET comparisons
These instructions perform comparisons on sets. 1–Word sets are manipulated directly via the Expression stack,
like any numeric value, multiple–word sets are manipulated indirectly via addresses on the Expression Stack.
Hex | Mnemonic | Param. | Mode | Semantics
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
D0 | LEQ_S | | | Test set inclusion
| | | |
| | | |–––––––––––––––––––––––––––––––––––––––––––––
| | | | [ set, set => bool ]
| | | Normal | POP (Y);
| | | | POP (X);
| | | | PUSH ((X and not Y) = (others => FALSE));
| | | |
| | |––––––––+–––––––––––––––––––––––––––––––––––––––––––––
| | | | [ adr, adr, size => bool ]
| | | Multi | POP (L);
| | | | POP (A2);
| | | | POP (A1);
| | | | PUSH ((MEMORY(A1..A1+L–1) and not
| | | | MEMORY(A2..A2+L–1))
| | | | = (others => FALSE));
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
D1 | GEQ_S | | | Test set inclusion
| | | |
| | | |–––––––––––––––––––––––––––––––––––––––––––––
| | | | [ set, set => bool ]
| | | Normal | POP (Y);
| | | | POP (X);
| | | | PUSH ((Y and not X) = (others => FALSE));
| | | |
| | |––––––––+–––––––––––––––––––––––––––––––––––––––––––––
| | | | [ adr, adr, size => bool ]
| | | Multi | POP (L);
| | | | POP (A2);
| | | | POP (A1);
| | | | PUSH ((MEMORY(A2..A2+L–1) and not
| | | | MEMORY(A1..A1+L–1))
| | | | = (others => FALSE));
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
138 von/of: 662
Hex | Mnemonic | Param. | Mode | Semantics
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
D2 | TEST | | | Test set membership
| | | |
| | | |–––––––––––––––––––––––––––––––––––––––––––––
| | | | [ num, set => bool ]
| | | Normal | POP (S);
| | | | POP (N);
| | | | IF N < 0 OR N >= 32 THEN
| | | | PUSH (FALSE);
| | | | ELSE
| | | | PUSH (S(N));
| | | | END IF;
| | | |
| | |––––––––+–––––––––––––––––––––––––––––––––––––––––––––
| | | | [ num, adr, len => bool ]
| | | Multi | POP (L);
| | | | POP (A);
| | | | POP (N);
| | | | IF N < 0 OR N >= L * 32 THEN
| | | | PUSH (FALSE);
| | | | ELSE
| | | | PUSH (MEMORY(A + N/32)(N mod 32));
| | | | END IF;
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––

Space Infrastructure
g) STRING comparisons
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
139 von/of: 662
Hex | Mnemonic | Param. | Mode | Semantics
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
D3 | LES_A | | Normal | Test less (ASCII) [ adr, adr => bool ]
| | | |
| | | | POP (A2);
| | | | POP (A1);
| | | | PUSH (STRING(A1) < STRING(A2));
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
D4 | GRT_A | | Normal | Test greater (ASCII) [ adr, adr => bool ]
| | | |
| | | | POP (A2);
| | | | POP (A1);
| | | | PUSH (STRING(A1) > STRING(A2));
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
D5 | LEQ_A | | Normal | Test less/equal (ASCII) [ adr, adr => bool ]
| | | |
| | | | POP (A2);
| | | | POP (A1);
| | | | PUSH (STRING(A1) bool ]
| | | |
| | | | POP (A2);
| | | | POP (A1);
| | | | PUSH (STRING(A1) >= STRING(A2));
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––

Space Infrastructure
6.7.5.3.9 BOOLEAN negation
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
140 von/of: 662
Hex | Mnemonic | Param. | Mode | Semantics
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––––
D7 | NEG | | Normal | Boolean NOT [ bool => bool ]
| | | |
| | | | POP (B);
| | | | PUSH (not B);
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––––
6.7.5.3.10 Allocation Instructions
These instructions allocate space in memory and free allocated space. Note that allocation and deallocation follow
strict stack semantics.
Hex | Mnemonic | Param. | Mode | Semantics
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
D8 | ALLOC | | Normal | Allocate space in memory [ size => adr ]
| | | |
| | | | POP (L);
| | | | PUSH (MP);
| | | | MP := MP + L;
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
D9 | FREE | | Normal | Free allocated space in memory [ size => ]
| | | |
| | | | POP (L);
| | | | MP := MP – L;
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––

Space Infrastructure
6.7.5.3.11 Jump Instructions
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
141 von/of: 662
These instructions perform jumps to locations in the code frame. The target location is indicated relatively as
a distance from the current PC. Conditional jumps test a condition (a boolean value) on the Expression Stack,
the jump is performed if the condition is FALSE.
Hex | Mnemonic | Param. | Mode | Semantics
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
DA | JUMP.b | dist 1 | Normal | Jump (short distance) [ ]
| | signed | |
| | | | PC := PC + dist;
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
DB | JUMP.h | dist 2 | Normal | Jump (long distance) [ ]
| | signed | |
| | | | PC := PC + dist;
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
DC | JUMP_C.b | dist 1 | Normal | Conditional jump (short dist.) [ bool => ]
| | signed | |
| | | | POP (B);
| | | | if not B then
| | | | PC := PC + dist;
| | | | else
| | | | PC := PC + 2;
| | | | end if;
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
DD | JUMP_C.h | dist 2 | Normal | Conditional jump (long distance) [ bool => ]
| | signed | |
| | | | POP (B);
| | | | if not B then
| | | | PC := PC + dist;
| | | | else
| | | | PC := PC + 3;
| | | | end if;
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––

Space Infrastructure
6.7.5.3.12 Special Jump Instructions
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
These instructions implement the UCL short–circuit OR (”|”) and AND (”&”) operations.
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
142 von/of: 662
Hex | Mnemonic | Param. | Mode | Semantics
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
DE | JUMP_T.b | dist 1 | Normal | Jump if true (OR) [ bool => (bool) ]
| | unsigned| |
| | | | POP (B);
| | | | if B then
| | | | PUSH (B);
| | | | PC := PC + dist;
| | | | else
| | | | PC := PC + 2;
| | | | end if;
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
DF | JUMP_F.b | dist 1 | Normal | Jump if false (AND) [ bool => (bool) ]
| | unsigned| |
| | | | POP (B);
| | | | if not B then
| | | | PUSH (B);
| | | | PC := PC + dist;
| | | | else
| | | | PC := PC + 2;
| | | | end if;
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––

Space Infrastructure
6.7.5.3.13 Iterative Instructions
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
143 von/of: 662
These instructions implement the UCL FOR loop. A FOR loop is bracketed by an ITER/NEXT instruction pair
that communicate via the Expression Stack.
Hex | Mnemonic | Param. | Mode | Semantics
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
E0 | ITER | dist 2 | Normal | Iterative loop prolog
| | unsigned| | [ adr, first, last, step =>
| | | | (adr, first, last, step, label) ]
| | | |
| | | | S := STACK(SP); –– step
| | | | L := STACK(SP–1); –– last loop value
| | | | F := STACK(SP–2); –– first loop value
| | | | A := STACK(SP–3); –– addr. of loop variable
| | | |
| | | | if (S > 0 and then F > L) or
| | | | (S < 0 and then F < L) then
| | | | SP := SP – 4; –– pop 4 stack items
| | | | PC := PC + dist; –– exit from loop
| | | | else
| | | | MEMORY(A) := F; –– init. loop variable
| | | | PC := PC + 3;
| | | | PUSH (PC); –– loop entry label
| | | | end if;
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
E1 | NEXT | | Normal | Iterative loop epilog
| | | | [ adr, first, last, step, label =>
| | | | (adr, first, last, step, label) ]
| | | |
| | | | S := STACK(SP–1); –– step
| | | | L := STACK(SP–2); –– last loop value
| | | | A := STACK(SP–4); –– addr. of loop variable
| | | |
| | | | MEMORY(A) := MEMORY(A) + S; –– inc. loop var
| | | |
| | | | if (S > 0 and MEMORY(A) > L)
| | | | or (S < 0 and MEMORY(A) < L) then
| | | | SP := SP – 5; –– pop 5 stack items
| | | | PC := PC + 1; –– leave loop
| | | | else
| | | | PC := STACK(SP); –– next loop cycle
| | | | end if;
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––

Space Infrastructure
6.7.5.3.14 Switch Instructions
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
144 von/of: 662
These instructions implement the UCL CASE statement. Two alternative instructions perform the jump to the
according case branch via a jump table and a search table, respectively.
Hex | Mnemonic | Param. | Mode | Semantics
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
E2 | SWITCH | n 2 | Normal | Switch to CASE branch [ val => label ]
| | unsigned| | via jump table
| | | |
| | | | Z := VALUE (CODE(PC+3..PC+4));–– exit label
| | | | E := VALUE (CODE(PC+5..PC+6));–– ELSE branch
| | | | T := PC + 7; –– Pointer to jump table
| | | |
| | | | POP (X); –– case selector
| | | | PUSH (PC + Z); –– push exit label
| | | |
| | | | if X < 0 or X > n then
| | | | PC := PC + E; –– jump to ELSE
| | | | else
| | | | I := T + 2*X; –– jump tab. index
| | | | PC := PC + VALUE (CODE(I..I+1)); –– jump
| | | | end if;
| | | |
| | | | –– SWITCH is followed by a jump table:
| | | | ––
| | | | –– halfword 1: distance to end of case
| | | | –– halfword 2: distance to ELSE part
| | | | ––
| | | | –– halfwords 3 .. 3+n:
| | | | distances to the branches
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
145 von/of: 662
Hex | Mnemonic | Param. | Mode | Semantics
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
E3 | SWITCH_X | n 2 | Normal | Switch to CASE branch [ val => label ]
| | unsigned| | via search table
| | | |
| | | | Z := VALUE (CODE(PC+3..PC+4));–– exit label
| | | | E := VALUE (CODE(PC+5..PC+6));–– ELSE branch
| | | |
| | | | POP (X); –– case selector
| | | | PUSH (PC + Z); –– push exit label
| | | |
| | | | D := {distance to branch searched in table}
| | | |
| | | | if D = 0 then –– not found
| | | | PC := PC + E; –– jump to ELSE
| | | | else
| | | | PC := PC + D; –– jump to branch
| | | | end if;
| | | |
| | | | –– SWITCH_X is followed by a search table:
| | | | ––
| | | | –– halfword: distance to end of case
| | | | –– halfword: distance to ELSE part
| | | | ––
| | | | –– range 1 .. range n
| | | | ––
| | | | –– (Each ”range” consists of:
| | | | –– o lower bound of the range (word)
| | | | –– o upper bound of the range (word)
| | | | –– o distance to branch (halfword)
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
E4 | LEAVE | | Normal | Exit from SWITCH [ label => ]
| | | |
| | | | POP (PC); –– jump to end of case statement
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––

Space Infrastructure
6.7.5.3.15 Procedure/Function Call Instructions
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
146 von/of: 662
These instructions perform procedure/function calls, entry and return operations. Note that the ENTER instruction
unstacks the actual parameters and moves them to locations in the Memory.
Hex | Mnemonic | Param. | Mode | Semantics
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
E5 | CALL.b | proc 1 | Normal | Call procedure/function [ ]
| | unsigned| |
| | | | MEMORY (MP) := FP; –– save dynamic link
| | | | MEMORY (MP+1) := PC+2; –– save return addr.
| | | | MP := MP + 2;
| | | | FP := MP; –– mark stack frame
| | | | PC := PROC (proc); –– jump
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
E6 | CALL_E | lib 1 | Normal | Call external procedure/function [ ]
| | unsigned| |
| | | | MEMORY(MP) := GP; –– save global link
| | proc 1 | | MEMORY(MP+1) := FP; –– save dynamic link
| | unsigned| | MEMORY(MP+2) := –(PC+3);–– save return addr.
| | | | MP := MP + 3;
| | | | FP := MP; –– mark stack frame
| | | | GP := BASE (lib); –– new global frame
| | | | CP := MEMORY(GP–2); –– new code frame
| | | | PC := PROC (proc); –– jump
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
E7 | INIT | | Normal | Enter library initialization part [ ]
| | | |
| | | | if not MEMORY(GP–3) then –– if not yet init.
| | | | MEMORY(GP–3) := TRUE; –– mark as init.
| | | | else –– else
| | | | PC := – MEMORY (FP–1); –– return from
| | | | MP := FP – 3; –– external call
| | | | GP := MEMORY (MP);
| | | | FP := MEMORY (MP+1);
| | | | CP := MEMORY (GP–2);
| | | | end if;
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
E8 | ENTER | par 1 | Normal | Enter procedure/funct. [ val, ..., val => ]
| | unsigned| |
| | | | –– unstack parameters:
| | dat 1 | | MEMORY(MP..MP+par–1) := STACK(SP–par+1..SP);
| | unsigned| | SP := SP – par;
| | | |
| | | | –– allocate space for local data:
| | | | MP := MP + par + dat;
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
147 von/of: 662
Hex | Mnemonic | Param. | Mode | Semantics
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
E9 | RTN | | Normal | Return from procedure/function [ ]
| | | |
| | | | PC := MEMORY (FP–1);
| | | | if PC > 0 THEN –– local call
| | | | MP := FP – 2;
| | | | FP := MEMORY(MP);
| | | | else –– external call
| | | | MP := FP – 3;
| | | | GP := MEMORY(MP);
| | | | FP := MEMORY(MP+1);
| | | | CP := MEMORY(GP–2);
| | | | PC := –PC;
| | | | end if;
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––

Space Infrastructure
6.7.5.3.16 Conversion Instructions
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
148 von/of: 662
Hex | Mnemonic | Param. | Mode | Semantics
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
EA | TRUNC | | | Truncate real to integer [ val => val ]
| | | |
| | | |–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Normal | POP (X);
| | | | PUSH (INTEGER(X));
| | | |
| | |––––––––+–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Double | POPD (X);
| | | | PUSH (INTEGER(X));
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
EB | REAL | | | Convert integer to real [ val => val ]
| | | |
| | | |–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Normal | POP (X);
| | | | PUSH (FLOAT(X));
| | | |
| | |––––––––+–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Double | POP (X);
| | | | PUSHD (FLOAT(X));
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
EC | SHORT_R | | Normal | Convert double word real [ val => val ]
| | | | to word real
| | | |
| | | | POPD (X);
| | | | PUSH (SHORT_FLOAT(X));
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
ED | LONG_R | | Normal | Convert word real [ val => val ]
| | | | to double word real
| | | |
| | | | POP (X);
| | | | PUSHD (FLOAT(X));
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
149 von/of: 662
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
EE | STR | | Normal | Convert character to string [ val => adr ]
| | | |
| | | | POP (X);
| | | | PUSH (MP);
| | | | MEMORY (MP) := 1;
| | | | MEMORY (MP+1) := X;
| | | | MP := MP + 2;
| | | |
| | | | –– This instruction implicitly allocates
| | | | –– space in memory
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
EF | –– | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––

Space Infrastructure
6.7.5.3.17 Miscellaneous Instructions
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
150 von/of: 662
Hex | Mnemonic | Param. | Mode | Semantics
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
F0 | INC_I | | Normal | Increment integer variable [ adr => ]
| | | |
| | | | POP (A);
| | | | MEMORY(A) := MEMORY(A) + 1;
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
F1 | DEC_I | | Normal | Decrement integer variable [ adr => ]
| | | |
| | | | POP (A);
| | | | MEMORY(A) := MEMORY(A) – 1;
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
F2 | INC_U | | Normal | Increment unsigned variable [ adr => ]
| | | |
| | | | POP (A);
| | | | MEMORY(A) := MEMORY(A) + 1;
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
F3 | DEC_U | | Normal | Decrement unsigned variable [ adr => ]
| | | |
| | | | POP (A);
| | | | MEMORY(A) := MEMORY(A) – 1;
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––

Space Infrastructure
6.7.5.3.18 System Instructions
These instructions perform different system specific operations.
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
151 von/of: 662
Hex | Mnemonic | Param. | Mode | Semantics
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
F4 | SYS | lib 1 | Normal | System call [ ]
| | unsigned| |
| | | | SYSTEM (lib, proc);
| | proc 1 | |
| | unsigned| |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
F5 | DOUBLE | | Normal | Interpret next instruction as double [ ]
| | | | word instruction
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
F6 | MULTI | | Normal | Interpret next instruction as multiple [ ]
| | | | word instruction
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
152 von/of: 662
Hex | Mnemonic | Param. | Mode | Semantics
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
F7 | READ | type 1 | | Read DB end item value [ sid => val ]
| | unsigned| |
| | | |–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Normal | POP (SID);
| | | | READ (SID, type, X);
| | | | PUSH (X);
| | | |
| | |––––––––+–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Double | POP (SID);
| | | | READD (SID, type, X);
| | | | PUSHD (X);
| | | |
| | |––––––––+–––––––––––––––––––––––––––––––––––––––––––––
| | | | [ sid, size => adr ]
| | | Multi | POP (L);
| | | | POP (SID);
| | | | PUSH (MP);
| | | | READM (SID, type, MP);
| | | | MP := MP + L;
| | | |
| | | | –– This instruction implicitly allocates
| | | | –– space in memory
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
F8 | WRITE | type 1 | | Write DB end item value [ sid, val => ]
| | unsigned| |
| | | |–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Normal | POP (X);
| | | | POP (SID);
| | | | WRITE (SID, type, X);
| | | |
| | |––––––––+–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Double | POPD (X);
| | | | POP (SID);
| | | | WRITED (SID, type, X);
| | | |
| | |––––––––+–––––––––––––––––––––––––––––––––––––––––––––
| | | | [ sid, adr, size => ]
| | | Multi | POP (L);
| | | | POP (A);
| | | | POP (SID);
| | | | WRITEM (SID, type, A);
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
153 von/of: 662
Hex | Mnemonic | Param. | Mode | Semantics
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
F9 | CHECK_I | | Normal | Check integer range [ val, min, max => val ]
| | | | n .. m
| | | |
| | | | POP (Y);
| | | | POP (X);
| | | | if STACK(SP) < X or STACK(SP) > Y then
| | | | TRAP (range_error);
| | | | end if;
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
FA | CHECK_0 | | Normal | Check range 0 .. m [ val, max => val ]
| | | |
| | | | POP (X);
| | | | if STACK(SP) < 0 or STACK(SP) > X then
| | | | TRAP (range_error);
| | | | end if;
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
FB | CHECK_U | | Normal | Check unsigned [ val, min, max => val ]
| | | | range n .. m
| | | |
| | | | POP (Y);
| | | | POP (X);
| | | | if STACK(SP) < X or STACK(SP) > Y then
| | | | TRAP (range_error);
| | | | end if;
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
FC | CHECK_R | | | Check real range [ val, min, max => val ]
| | | | n .. m
| | | |
| | | |–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Normal | POP (Y);
| | | | POP (X);
| | | | if STACK(SP) < X or STACK(SP) > Y then
| | | | TRAP (range_error);
| | | | end if;
| | | |
| | |––––––––+–––––––––––––––––––––––––––––––––––––––––––––
| | | |
| | | Double | POPD (Y);
| | | | POPD (X);
| | | | if STACK(SP–1..SP) < X or
| | | | STACK(SP–1..SP) > Y then
| | | | TRAP (range_error);
| | | | end if;
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
154 von/of: 662
Hex | Mnemonic | Param. | Mode | Semantics
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
FD | ERROR | err 1 | Normal | Runtime error trap [ ]
| | unsigned| |
| | | | ERROR (err);
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––
FE | HALT | | Normal | Stop program and return [ code => ]
| | | | completion code
| | | |
| | | | POP (X);
| | | | HALT (X);
| | | |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––

Space Infrastructure
6.7.5.3.19 No–operation Instruction
This instruction does not perform any operation.
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
155 von/of: 662
Hex | Mnemonic | Param. | Mode | Semantics
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––––
FF | NOP | | any | No operation [ ]
| | | mode |
––––+––––––––––––+–––––––––+––––––––+–––––––––––––––––––––––––––––––––––––––––––––––

Space Infrastructure
6.7.6 Sample AP and Corresponding I–Code
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
156 von/of: 662
This example shows the translation of the following AP into I–code. For an example of the generated Debug
Table, see the following chapter.
Source code:
1 PROCEDURE Example;
2
3 IMPORT \SYSTEM\IO_Library; –– system library (Get/Put procedures)
4
5 VARIABLE Sum: INTEGER; –– global address 0
6 VARIABLE N: INTEGER; –– global address 1
7
8
9 PROCEDURE Add (X: INTEGER); –– procedure 1
10 BEGIN
11 Sum := Sum + X;
12 INC (N);
13 END Add;
14
15
16 FUNCTION Mean (): INTEGER; –– procedure 2
17 BEGIN
18 IF N = 0 THEN
19 RETURN 0;
20 ELSE
21 RETURN Sum / N;
22 END IF;
23 END Mean;
24
25
26 BEGIN
27 Sum := 0; –– initialize counters
28 N := 0;
29
30 FOR i := 1 TO 10 DO –– i implicitly on global address 2
31 Add (i); –– local procedure call
32 END FOR;
33
34
35 Put_String (”Mean value = ”); –– procedure 6 from system library
36 Put_Integer (Mean()); –– procedure 7 from system library
37 New_Line; –– procedure 9 from system library
38
39 END Example;

Space Infrastructure
I–code in assembly language:
.PROCEDURE example
.IMPORT ; Size: 0
.DATA 3
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
157 von/of: 662
.CODE ; Size: 72 ; PC Code dump
.MAIN ; 6
JUMP.h L3 ; 34 ; 6: DB 00 22
.ENTRY P1 ; 9
ENTER 1, 0 ; 9: E8 01 00
LOAD_G.0 ; 12: 20
LOAD_L.0 ; 13: 10
ADD_I ; 14: A0
STOR_G.0 ; 15: 50
LOAD_A_G.b 1 ; 16: 8E 01
INC_I ; 18: F0
RTN ; 19: E9
.ENTRY P2 ; 20
L1:
L2:
L3:
ENTER 0, 0 ; 20: E8 00 00
LOAD_G.1 ; 23: 21
LOAD_C.0 ; 24: 00
EQU ; 25: BE
JUMP_C.h L1 ; 8 ; 26: DD 00 08
LOAD_C.0 ; 29: 00
RTN ; 30: E9
JUMP.h L2 ; 7 ; 31: DB 00 07
LOAD_G.0 ; 34: 20
LOAD_G.1 ; 35: 21
DIV_I ; 36: A3
RTN ; 37: E9
ERROR 9 ; 38: FD 09
LOAD_C.0 ; 40: 00
STOR_G.0 ; 41: 50
LOAD_C.0 ; 42: 00
STOR_G.1 ; 43: 51
LOAD_A_G.b 2 ; 44: 8E 02
LOAD_C.1 ; 46: 01
LOAD_C.10 ; 47: 0A
LOAD_C.1 ; 48: 01
ITER L4 ; 6 ; 49: E0 00 06
LOAD_G.2 ; 52: 22
CALL.1 ; 53: 71
NEXT ; 54: E1

Space Infrastructure
L4:
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
158 von/of: 662
LOAD_A_T.b D1 ; 0 ; 55: 92 00
LOAD_C.13 ; 57: 0D
LOAD_C.0 ; 58: 00
SYS 1, 6 ; 59: F4 01 06
CALL.2 ; 62: 72
LOAD_C.1 ; 63: 01
SYS 1, 7 ; 64: F4 01 07
SYS 1, 9 ; 67: F4 01 09
LOAD_C.0 ; 70: 00
HALT ; 71: FE
.CONSTANT ; Size: 4
D1: 1298489710, ; 16#4D65616E# Mean
544629100, ; 16#2076616C# val
1969561661, ; 16#7565203D# ue =
536870912 ; 16#20000000# ...
; Library relocation list: Size: 0
; Real conversion list: Size: 0
.END

Space Infrastructure
6.7.7 Procedural Interface
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
159 von/of: 662
Generation and interpretation of I–Code is supported by the Ada package . It contains
the I–Code definition as an enumeration type, together with operations to convert between textual, binary and
logical representation of I–Code.

Space Infrastructure
Formal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– I_CODE_DEFINITION
––
–– Definition of UCL I–Code
––
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– Unit: Generic package specification
––
–– Author: Ulf Schmidt, Franz Kruse, ERNO
––
–– Document: ICD 1216 404 001, CLS to System ICD
––
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Vers. Date Author Company SPR Change description
–– ––––– –––––––– ––––––––––––––– –––––––– –––– ––––––––––––––––––––––––
–– 3.0.0 22.04.94 F. Kruse ERNO First issue for V3
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
with NUMERIC_TYPES; use NUMERIC_TYPES;
package I_CODE_DEFINITION is
–– I–Code definition
––––––––––––––––––––
type I_CODE is (LOAD_C_0, –– Load constant 0 .. 15
LOAD_C_1,
LOAD_C_2,
LOAD_C_3,
LOAD_C_4,
LOAD_C_5,
LOAD_C_6,
LOAD_C_7,
LOAD_C_8,
LOAD_C_9,
LOAD_C_10,
LOAD_C_11,
LOAD_C_12,
LOAD_C_13,
LOAD_C_14,
LOAD_C_15,
LOAD_L_0, –– Load local variable from address 0 .. 15
LOAD_L_1,
LOAD_L_2,
LOAD_L_3,
LOAD_L_4,
LOAD_L_5,
LOAD_L_6,
LOAD_L_7,
LOAD_L_8,
LOAD_L_9,
LOAD_L_10,
LOAD_L_11,
LOAD_L_12,
LOAD_L_13,
LOAD_L_14,
LOAD_L_15,
LOAD_G_0, –– Load global variable from address 0 .. 15
LOAD_G_1,
LOAD_G_2,
LOAD_G_3,
LOAD_G_4,
LOAD_G_5,
LOAD_G_6,
LOAD_G_7,
LOAD_G_8,
LOAD_G_9,
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
160 von/of: 662

Space Infrastructure
LOAD_G_10,
LOAD_G_11,
LOAD_G_12,
LOAD_G_13,
LOAD_G_14,
LOAD_G_15,
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
LOAD_F_0, –– Load offsetted variable from address 0 .. 15
LOAD_F_1,
LOAD_F_2,
LOAD_F_3,
LOAD_F_4,
LOAD_F_5,
LOAD_F_6,
LOAD_F_7,
LOAD_F_8,
LOAD_F_9,
LOAD_F_10,
LOAD_F_11,
LOAD_F_12,
LOAD_F_13,
LOAD_F_14,
LOAD_F_15,
STOR_L_0, –– Store local variable at address 0 .. 15
STOR_L_1,
STOR_L_2,
STOR_L_3,
STOR_L_4,
STOR_L_5,
STOR_L_6,
STOR_L_7,
STOR_L_8,
STOR_L_9,
STOR_L_10,
STOR_L_11,
STOR_L_12,
STOR_L_13,
STOR_L_14,
STOR_L_15,
STOR_G_0, –– Store global variable at address 0 .. 15
STOR_G_1,
STOR_G_2,
STOR_G_3,
STOR_G_4,
STOR_G_5,
STOR_G_6,
STOR_G_7,
STOR_G_8,
STOR_G_9,
STOR_G_10,
STOR_G_11,
STOR_G_12,
STOR_G_13,
STOR_G_14,
STOR_G_15,
STOR_F_0, –– Store offsetted variable at address 0 .. 15
STOR_F_1,
STOR_F_2,
STOR_F_3,
STOR_F_4,
STOR_F_5,
STOR_F_6,
STOR_F_7,
STOR_F_8,
STOR_F_9,
STOR_F_10,
STOR_F_11,
STOR_F_12,
STOR_F_13,
STOR_F_14,
STOR_F_15,
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
161 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
CALL_1, –– Call local/global procedure/function 1 .. 15
CALL_2,
CALL_3,
CALL_4,
CALL_5,
CALL_6,
CALL_7,
CALL_8,
CALL_9,
CALL_10,
CALL_11,
CALL_12,
CALL_13,
CALL_14,
CALL_15,
LOAD_T_b, –– Load constant from table
LOAD_T_h,
LOAD_C_b, –– Load constant
LOAD_C_h,
LOAD_C_w,
LOAD_L_b, –– Load local variable
LOAD_G_b, –– Load global variable
LOAD_F_b, –– Load offsetted variable
LOAD_F_h,
LOAD_E, –– Load external variable
LOAD_X_C, –– Load indexed character
LOAD_X_V, –– Load indexed variable
LOAD_A_L_b, –– Load local address
LOAD_A_G_b, –– Load global address
LOAD_A_F_b, –– Load offsetted address
LOAD_A_F_h,
LOAD_A_E, –– Load external address
LOAD_A_T_b, –– Load address of constant
LOAD_A_T_h,
STOR_L_b, –– Store local variable
STOR_G_b, –– Store global variable
STOR_F_b, –– Store offsetted variable
STOR_F_h,
STOR_E, –– Store external variable
STOR_X_C, –– Store indexed character
STOR_X_V, –– Store indexed variable
MOVE, –– Move block of data
CAT, –– String catenation
COPY, –– Copy top of stack
POP, –– Remove n items from top of stack
SWAP, –– Swap data on top of stack
ADD_I, –– Add integers
SUB_I, –– Subtract integers
MUL_I, –– Multiply integers
DIV_I, –– Divide integers
EXP_I, –– Integer exponentiation
MOD_I, –– Modulus
NEG_I, –– Negate integer
ABS_I, –– Absolute integer value
ADD_U, –– Add unsigned
SUB_U, –– Subtract unsigned
MUL_U, –– Multiply unsigned
DIV_U, –– Divide unsigned
EXP_U, –– Exponentiate unsigned
MOD_U, –– Unsigned modulus
ADD_R, –– Add reals
SUB_R, –– Subtract reals
MUL_R, –– Multiply reals
DIV_R, –– Divide reals
EXP_R, –– Real exponentiation
NEG_R, –– Negate real
ABS_R, –– Absolute real value
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
162 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
ADD_D, –– Add time and duration
SUB_D, –– Subtract duration from time
SUB_T, –– Subtract times
ADD_S, –– Set union
SUB_S, –– Set difference
MUL_S, –– Set intersection
DIV_S, –– Symmetric set difference
INCL, –– Include element in set
EXCL, –– Exclude element from set
EQU, –– Test equal
NEQ, –– Test not equal
LES_I, –– Test less (integer)
GRT_I, –– Test greater (integer)
LEQ_I, –– Test less or equal (integer)
GEQ_I, –– Test greater or equal (integer)
LES_U, –– Test less (unsigned)
GRT_U, –– Test greater (unsigned)
LEQ_U, –– Test less or equal (unsigned)
GEQ_U, –– Test greater or equal (unsigned)
LES_R, –– Test less (real)
GRT_R, –– Test greater (real)
LEQ_R, –– Test less or equal (real)
GEQ_R, –– Test greater or equal (real)
LES_T, –– Test less (time)
GRT_T, –– Test greater (time)
LEQ_T, –– Test less or equal (time)
GEQ_T, –– Test greater or equal (time)
LEQ_S, –– Test set inclusion
GEQ_S, –– Test set inclusion
TEST, –– Test set membership
LES_A, –– Test less (ASCII)
GRT_A, –– Test greater (ASCII)
LEQ_A, –– Test less or equal (ASCII)
GEQ_A, –– Test greater or equal (ASCII)
NEG, –– Boolean NOT
ALLOC, –– Allocate space in memory
FREE, –– Free allocated space in memory
JUMP_b, –– Jump (short distance)
JUMP_h, –– Jump (long distance)
JUMP_C_b, –– Conditional jump (short distance)
JUMP_C_h, –– Conditional jump (long distance)
JUMP_T_b, –– Jump if true (OR)
JUMP_F_b, –– Jump if false (AND)
ITER, –– Iterative loop prolog
NEXT, –– Iterative loop epilog
SWITCH, –– Switch to CASE branch via jump table
SWITCH_X, –– Switch to CASE branch via search table
LEAVE, –– Exit from CASE branch
CALL_b, –– Call local/global procedure/function
CALL_E, –– Call external function
INIT, –– Enter library initialization part
ENTER, –– Enter procedure/function
RTN, –– Return from procedure/function
TRUNC, –– Truncate real to integer
REAL, –– Convert integer to real
SHORT_R, –– Convert double word real to word real
LONG_R, –– Convert word real to double word real
STR, –– Convert character to string
INC_I, –– Increment integer variable
DEC_I, –– Decrement integer variable
INC_U, –– Increment unsigned variable
DEC_U, –– Decrement unsigned variable
SYS, –– System call
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
163 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
D_PREFIX, –– Next instruction in Double–Mode
M_PREFIX, –– Next instruction in Multi–Mode
READ, –– Read database end item value
WRITE, –– Write database end item value
CHECK_I, –– Check integer range n .. m
CHECK_0, –– Check range 0 .. m
CHECK_U, –– Check unsigned range n .. m
CHECK_R, –– Check real range n .. m
ERROR, –– Runtime error trap
HALT, –– Stop program and return success code
NOP); –– No operation
type GENERIC_I_CODE is –– implied_____byte________halfword____word____
( LOAD_C, –– LOAD_C.# LOAD_C.b LOAD_C.h LOAD_C.w
LOAD_L, –– LOAD_L.# LOAD_L.b
LOAD_G, –– LOAD_G.# LOAD_G.b
LOAD_F, –– LOAD_F.# LOAD_F.b LOAD_F.h
LOAD_T, –– LOAD_T.b LOAD_T.h
LOAD_A_L, –– LOAD_A_L.b
LOAD_A_G, –– LOAD_A_G.b
LOAD_A_F, –– LOAD_A_F.b LOAD_A_F.h
LOAD_A_T, –– LOAD_A_T.b LOAD_A_T.h
STOR_L, –– STOR_L.# STOR_L.b
STOR_G, –– STOR_G.# STOR_G.b
STOR_F, –– STOR_F.# STOR_F.b STOR_F.h
CALL, –– CALL.# CALL.b
JUMP, –– JUMP.b JUMP.h
JUMP_C, –– JUMP_C.b JUMP_C.h
JUMP_T, –– JUMP_T.b
JUMP_F, –– JUMP_F.b
NON_GENERIC);
–– Trap numbers used for ERROR instruction
NO_RETURN_FROM_FUNCTION: constant NATURAL := 0;
STRING_ASSIGNMENT_OVERFLOW: constant NATURAL := 1;
OTHER_ERROR: constant NATURAL := 255;
type I_CODE_SET is array (I_CODE) of BOOLEAN;
type INSTRUCTION is
record
EXISTS: BOOLEAN;
VALUE: I_CODE;
end record;
type IMPLIED_INSTRUCTION is
array (0..15) of INSTRUCTION;
type I_CODE_GROUP (IS_GENERIC: BOOLEAN := FALSE) is
record
case IS_GENERIC is
when FALSE => NON_GENERIC: INSTRUCTION;
when TRUE => CLASS: GENERIC_I_CODE;
IMPLIED: IMPLIED_INSTRUCTION;
BYTE: INSTRUCTION;
HALFWORD: INSTRUCTION;
WORD: INSTRUCTION;
end case;
end record;
–– exception
––––––––––––
I_CODE_ERROR: exception;
–– conversion functions
–––––––––––––––––––––––
function VALUE (TEXT: STRING) return I_CODE;
function VALUE (TEXT: STRING) return I_CODE_GROUP;
function VALUE (CODE: BYTE) return I_CODE;
function MNEMONIC (VALUE: I_CODE) return STRING;
function MNEMONIC (CODE: BYTE) return STRING;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
164 von/of: 662

Space Infrastructure
function CODE (TEXT: STRING) return BYTE;
function CODE (VALUE: I_CODE) return BYTE;
private
for I_CODE’SIZE use 8;
for I_CODE use (LOAD_C_0 => 16#00#,
LOAD_C_1 => 16#01#,
LOAD_C_2 => 16#02#,
LOAD_C_3 => 16#03#,
LOAD_C_4 => 16#04#,
LOAD_C_5 => 16#05#,
LOAD_C_6 => 16#06#,
LOAD_C_7 => 16#07#,
LOAD_C_8 => 16#08#,
LOAD_C_9 => 16#09#,
LOAD_C_10 => 16#0A#,
LOAD_C_11 => 16#0B#,
LOAD_C_12 => 16#0C#,
LOAD_C_13 => 16#0D#,
LOAD_C_14 => 16#0E#,
LOAD_C_15 => 16#0F#,
LOAD_L_0 => 16#10#,
LOAD_L_1 => 16#11#,
LOAD_L_2 => 16#12#,
LOAD_L_3 => 16#13#,
LOAD_L_4 => 16#14#,
LOAD_L_5 => 16#15#,
LOAD_L_6 => 16#16#,
LOAD_L_7 => 16#17#,
LOAD_L_8 => 16#18#,
LOAD_L_9 => 16#19#,
LOAD_L_10 => 16#1A#,
LOAD_L_11 => 16#1B#,
LOAD_L_12 => 16#1C#,
LOAD_L_13 => 16#1D#,
LOAD_L_14 => 16#1E#,
LOAD_L_15 => 16#1F#,
LOAD_G_0 => 16#20#,
LOAD_G_1 => 16#21#,
LOAD_G_2 => 16#22#,
LOAD_G_3 => 16#23#,
LOAD_G_4 => 16#24#,
LOAD_G_5 => 16#25#,
LOAD_G_6 => 16#26#,
LOAD_G_7 => 16#27#,
LOAD_G_8 => 16#28#,
LOAD_G_9 => 16#29#,
LOAD_G_10 => 16#2A#,
LOAD_G_11 => 16#2B#,
LOAD_G_12 => 16#2C#,
LOAD_G_13 => 16#2D#,
LOAD_G_14 => 16#2E#,
LOAD_G_15 => 16#2F#,
LOAD_F_0 => 16#30#,
LOAD_F_1 => 16#31#,
LOAD_F_2 => 16#32#,
LOAD_F_3 => 16#33#,
LOAD_F_4 => 16#34#,
LOAD_F_5 => 16#35#,
LOAD_F_6 => 16#36#,
LOAD_F_7 => 16#37#,
LOAD_F_8 => 16#38#,
LOAD_F_9 => 16#39#,
LOAD_F_10 => 16#3A#,
LOAD_F_11 => 16#3B#,
LOAD_F_12 => 16#3C#,
LOAD_F_13 => 16#3D#,
LOAD_F_14 => 16#3E#,
LOAD_F_15 => 16#3F#,
STOR_L_0 => 16#40#,
STOR_L_1 => 16#41#,
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
165 von/of: 662

Space Infrastructure
STOR_L_2 => 16#42#,
STOR_L_3 => 16#43#,
STOR_L_4 => 16#44#,
STOR_L_5 => 16#45#,
STOR_L_6 => 16#46#,
STOR_L_7 => 16#47#,
STOR_L_8 => 16#48#,
STOR_L_9 => 16#49#,
STOR_L_10 => 16#4A#,
STOR_L_11 => 16#4B#,
STOR_L_12 => 16#4C#,
STOR_L_13 => 16#4D#,
STOR_L_14 => 16#4E#,
STOR_L_15 => 16#4F#,
STOR_G_0 => 16#50#,
STOR_G_1 => 16#51#,
STOR_G_2 => 16#52#,
STOR_G_3 => 16#53#,
STOR_G_4 => 16#54#,
STOR_G_5 => 16#55#,
STOR_G_6 => 16#56#,
STOR_G_7 => 16#57#,
STOR_G_8 => 16#58#,
STOR_G_9 => 16#59#,
STOR_G_10 => 16#5A#,
STOR_G_11 => 16#5B#,
STOR_G_12 => 16#5C#,
STOR_G_13 => 16#5D#,
STOR_G_14 => 16#5E#,
STOR_G_15 => 16#5F#,
STOR_F_0 => 16#60#,
STOR_F_1 => 16#61#,
STOR_F_2 => 16#62#,
STOR_F_3 => 16#63#,
STOR_F_4 => 16#64#,
STOR_F_5 => 16#65#,
STOR_F_6 => 16#66#,
STOR_F_7 => 16#67#,
STOR_F_8 => 16#68#,
STOR_F_9 => 16#69#,
STOR_F_10 => 16#6A#,
STOR_F_11 => 16#6B#,
STOR_F_12 => 16#6C#,
STOR_F_13 => 16#6D#,
STOR_F_14 => 16#6E#,
STOR_F_15 => 16#6F#,
––– => 16#70#,
CALL_1 => 16#71#,
CALL_2 => 16#72#,
CALL_3 => 16#73#,
CALL_4 => 16#74#,
CALL_5 => 16#75#,
CALL_6 => 16#76#,
CALL_7 => 16#77#,
CALL_8 => 16#78#,
CALL_9 => 16#79#,
CALL_10 => 16#7A#,
CALL_11 => 16#7B#,
CALL_12 => 16#7C#,
CALL_13 => 16#7D#,
CALL_14 => 16#7E#,
CALL_15 => 16#7F#,
LOAD_T_b => 16#80#,
LOAD_T_h => 16#81#,
LOAD_C_b => 16#82#,
LOAD_C_h => 16#83#,
LOAD_C_w => 16#84#,
LOAD_L_b => 16#85#,
LOAD_G_b => 16#86#,
LOAD_F_b => 16#87#,
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
166 von/of: 662

Space Infrastructure
LOAD_F_h => 16#88#,
LOAD_E => 16#89#,
LOAD_X_C => 16#8A#,
LOAD_X_V => 16#8B#,
––– => 16#8C#,
LOAD_A_L_b => 16#8D#,
LOAD_A_G_b => 16#8E#,
LOAD_A_F_b => 16#8F#,
LOAD_A_F_h => 16#90#,
LOAD_A_E => 16#91#,
LOAD_A_T_b => 16#92#,
LOAD_A_T_h => 16#93#,
STOR_L_b => 16#94#,
STOR_G_b => 16#95#,
STOR_F_b => 16#96#,
STOR_F_h => 16#97#,
STOR_E => 16#98#,
STOR_X_C => 16#99#,
STOR_X_V => 16#9A#,
MOVE => 16#9B#,
CAT => 16#9C#,
COPY => 16#9D#,
POP => 16#9E#,
SWAP => 16#9F#,
ADD_I => 16#A0#,
SUB_I => 16#A1#,
MUL_I => 16#A2#,
DIV_I => 16#A3#,
EXP_I => 16#A4#,
MOD_I => 16#A5#,
NEG_I => 16#A6#,
ABS_I => 16#A7#,
ADD_U => 16#A8#,
SUB_U => 16#A9#,
MUL_U => 16#AA#,
DIV_U => 16#AB#,
EXP_U => 16#AC#,
MOD_U => 16#AD#,
ADD_R => 16#AE#,
SUB_R => 16#AF#,
MUL_R => 16#B0#,
DIV_R => 16#B1#,
EXP_R => 16#B2#,
NEG_R => 16#B3#,
ABS_R => 16#B4#,
ADD_D => 16#B5#,
SUB_D => 16#B6#,
SUB_T => 16#B7#,
ADD_S => 16#B8#,
SUB_S => 16#B9#,
MUL_S => 16#BA#,
DIV_S => 16#BB#,
INCL => 16#BC#,
EXCL => 16#BD#,
EQU => 16#BE#,
NEQ => 16#BF#,
LES_I => 16#C0#,
GRT_I => 16#C1#,
LEQ_I => 16#C2#,
GEQ_I => 16#C3#,
LES_U => 16#C4#,
GRT_U => 16#C5#,
LEQ_U => 16#C6#,
GEQ_U => 16#C7#,
LES_R => 16#C8#,
GRT_R => 16#C9#,
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
167 von/of: 662

Space Infrastructure
LEQ_R => 16#CA#,
GEQ_R => 16#CB#,
LES_T => 16#CC#,
GRT_T => 16#CD#,
LEQ_T => 16#CE#,
GEQ_T => 16#CF#,
LEQ_S => 16#D0#,
GEQ_S => 16#D1#,
TEST => 16#D2#,
LES_A => 16#D3#,
GRT_A => 16#D4#,
LEQ_A => 16#D5#,
GEQ_A => 16#D6#,
NEG => 16#D7#,
ALLOC => 16#D8#,
FREE => 16#D9#,
JUMP_b => 16#DA#,
JUMP_h => 16#DB#,
JUMP_C_b => 16#DC#,
JUMP_C_h => 16#DD#,
JUMP_T_b => 16#DE#,
JUMP_F_b => 16#DF#,
ITER => 16#E0#,
NEXT => 16#E1#,
SWITCH => 16#E2#,
SWITCH_X => 16#E3#,
LEAVE => 16#E4#,
CALL_b => 16#E5#,
CALL_E => 16#E6#,
INIT => 16#E7#,
ENTER => 16#E8#,
RTN => 16#E9#,
TRUNC => 16#EA#,
REAL => 16#EB#,
SHORT_R => 16#EC#,
LONG_R => 16#ED#,
STR => 16#EE#,
––– => 16#EF#,
INC_I => 16#F0#,
DEC_I => 16#F1#,
INC_U => 16#F2#,
DEC_U => 16#F3#,
SYS => 16#F4#,
D_PREFIX => 16#F5#,
M_PREFIX => 16#F6#,
READ => 16#F7#,
WRITE => 16#F8#,
CHECK_I => 16#F9#,
CHECK_0 => 16#FA#,
CHECK_U => 16#FB#,
CHECK_R => 16#FC#,
ERROR => 16#FD#,
HALT => 16#FE#,
NOP => 16#FF#);
end I_CODE_DEFINITION;
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
168 von/of: 662

Space Infrastructure
6.8 Parameter Encoding
6.8.1 Functional Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
169 von/of: 662
When parameter lists are to be transferred via the network (e.g. for activation of an AP, or remote invocation
of a library procedure/function) they must be encoded in a serial stream of words. This is referred to as external
encoding.
When parameter lists of parameterized pathnames are kept in the memory of the stack machine, they are encoded
in an analogous form. This is referred to as internal encoding.
Both external and internal encoding are based on the same encoding scheme.
6.8.2 Parameter Classes
Parameters are classified by mode and type. This classification is coded in the parameter class word, with the
mode in the upper halfword and the type in the lower halfword.
Mode
The parameter mode defines the passing and access mechanism.
0 type
1 type
2 type
Type
IN A value is passed into the called module.
OUT A value is passed out of the called module.
IN OUT A value is passed into and out of the called module.
Parameters may belong to the following type classes.
mode
mode
mode
mode
mode
mode
mode
1
2
3
4
5
6
7
1–word scalar type (INTEGER, REAL, BOOLEAN, BITSET, WORD etc.)
Item is exactly one 32–bit word. Sets that occupy one word or less are classified here, too.
2–word scalar type (LONG_REAL, TIME, STATECODE)
Item is exactly two 32–bit words.
fixed–size string type
Item is one component consisting of one or more words representing a string.
fixed–size structured type (array, record, set)
Item is one component consisting of zero or more words representing an array, record or set.
open string type (open string parameter)
Item is one component consisting of 1 or more words representing a string.
open structured type (open array parameter)
Item is one component consisting of zero, one or more words representing an array.
parameterized pathname (pathname( ))
Item is a database end item with parameters (AP, stimulus, ...).

Space Infrastructure
6.8.3 Encoding Scheme
6.8.3.1 External Scheme
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
170 von/of: 662
The following defines the external parameter encoding scheme. The parameter stream is prefixed with the size
of the stream in words, then follow the single parameters, each encoded as shown in the picture, and a null word
terminating the stream.
The No. of words indication counts the number of data words only.
The Upper bound indication for open strings and structures is the upper bound according to the UCL view.
For scalars, the Type indication is identical to MPS_DEFINITIONS.T_SW_TYPE’POS
(BITSET_TYPE is used for all sets that occupy one word or less).
Size
in words
Parameter type class
Parameter 1 Parameter 2 . . . Parameter n
parmeterized No. of
pathname
words
open structure
open string
fixed structure
fixed string
2–word scalar
1–word scalar
mode
mode
mode
mode
mode
mode
mode
7
6
5
4
3
2
1
No. of
words
No. of
words
No. of
words
No. of
words
Type
Type
SID
Upper
bound
Upper
bound
Word
1
Word
1
Word
1
Word
1
Word
1
Word
1
Word
1
Word
2
Word
2
Word
2
Word
2
Word
2
Word
2
Word
3
Word
3
Word
3
Word
3
Word
3
data words
... Word
n
... Word
n
... Word
n
Figure 6.8.3–1 External Parameter Encoding Scheme
...
...
Word
n
Word
n
0
Words 1 .. n are the parameter
list of the pathname, encoded
according to these rules.

Space Infrastructure
6.8.3.2 Internal Scheme
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
171 von/of: 662
The following defines the representation of a parameterized pathname item in the memory of the stack machine,
including its actual parameter list. On the expression stack a parameterized item is represented by an address
pointing to the following data structure in memory.
The item is represented by its SID, the size of its actual parameter list, and the parameter list itself, which is encoded
in the internal encoding scheme. The internal encoding scheme is essentially identical to the external
scheme, with the only difference that for non–scalar parameters the actual data words are replaced by an address
pointing to the location in memory where the data words are stored, and for OUT and IN OUT parameters they
are always replaced by an address to the location in memory.
Note that the Size of list in this case denotes the true size of the encoded parameter list with addresses to structures
instead of the actual structured values while the Size in words, nevertheless, counts the data words (and
not the addresses) for the size of its following list, like in the external encoding.
pathname SID
Size
in words
Size of list Encoded list
Parameter 1 Parameter 2 . . . Parameter n
parmeterized
pathname
open structure
open string
fixed structure
fixed string
2–word scalar
IN param.
1–word scalar
IN par.
mode
mode
mode
mode
mode
mode
mode
Parameter type class
7
6
5
4
3
2
1
No. of
words
No. of
words
No. of
words
No. of
words
No. of
words
Type
Type
SID
Upper
bound
Upper
bound
Ad–
dress
Ad–
dress
Ad–
dress
Ad–
dress
Ad–
dress
2–word scalar Ad–
(IN) OUT par.
Type
dress
1–word scalar
(IN) OUT par.
mode
mode
2
1
Type
Ad–
dress
Word
1
Word
1
Word
2
data words
Figure 6.8.3–2 Internal Parameter Enoding Scheme
Address of data
instead of the data itself.
mode is OUT or IN OUT
mode is IN
0

Space Infrastructure
6.8.4 Example (Call of a library procedure)
Declaration (UCL):
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
procedure PROC (in NUMBER : INTEGER; -- 1–word scalar
in SWITCH : BOOLEAN; -- 1–word scalar
out DOUBLE : LONG_REAL; -- 2–word scalar
in STATE : statecode; -- 2–word scalar
in TEXT_1 : STRING_9; -- fix–size string
in TEXT_2 : string; -- open string
in out ARRAY_1: REAL_ARRAY_4; -- fix–size array
in ARRAY_2: array of REAL; -- open array
in PATH_1 : pathname; -- simple pathname
in PATH_2 : pathname() ); -- parameterized pathname
Call (HLCL):
PROC NUMBER : 123, -- 1–word scalar
SWITCH : TRUE, -- 1–word scalar
DOUBLE : some variable -- 2–word scalar
STATE : $MEDIUM, -- 2–word scalar
TEXT_1 : ”ABCDEFGHI”, -- fix–size string
TEXT_2 : ”ABCDEFGHI”, -- open string
ARRAY_1: some variable, -- fix–size array
ARRAY_2: (1.0, 2.0, 3.0, 4.0), -- open array
PATH_1 : \some_path\X, -- simple pathname
PATH_2 : \some_path\Y (3.14) -- parameterized pathname
Encoded parameter list:
size
of list
NUMBER
SWITCH
DOUBLE
STATE
TEXT_2
ARRAY_2
end
of list
0
0
1
0
0
52
0
INTEGER
BOOLEAN
LONG_REAL
STATECODE
4
123
true
TEXT_1 9
0
0
4 3
MEDI UM
PATH_1 PATHNAME 17535
4 ABCDEFGH I
9
9
ABCDEFGH I
ARRAY_1 2 4 4 1.0 2.0 3.0 4.0
0
0
1
1
2
2
3
5
6
1
1.0 2.0 3.0 4.0
PATH_2 0 7 5
4 1 3.14
Figure 6.8.3–1 Encoded Parameter List
0
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
172 von/of: 662
17536 REAL 0

Space Infrastructure
6.8.5 Stack Machine Representation of AP Parameters
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
Within the memory of the Stack Machine the parameters are represented as shown in the picture:
GP
MP
0
1
2
3
4
5
6
AP global data frame
1–word scalar value
2–word
scalar
fixed structure address
open
structure
...
...
value
address
contents of
fixed structure
upper bound
param. pathname address
...
contents of
open structure
contents of
parameterized pathname
data parts of
parameterized pathname
Figure 6.8.3–1 Global Data Frame
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
173 von/of: 662
AP parameters are treated
as the first n global variables.
This is analogous to local
procedure parameters.
Addresses are obtained
by allocation of space in
memory for non–scalars.
Non–scalar parameters
are allocated space in
memory and referenced
via their address.
These are the n data words
These are the n data words
This is the SID, the No. of
data words and the encoded
parameter list like defined
here, but with addresses to
structured data, instead of the
data words themselves.

Space Infrastructure
6.9 Flight Synoptic Display Representation Format
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
174 von/of: 662
The flight synoptic displays will be stored in an ASCII based format, as generated by the Sammi fmt_unload
function, which is described in applicable document 2.1.5.6, chapter 7, page 7–6 ff.
The target platform compatible binary format has to be generated from this ASCII format by the complementary
Sammi fmt_load function for the relevant target platform, which is described in the same chapter of above reference.

Space Infrastructure
6.10 FWDU Supported Sammi API Interfaces
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
175 von/of: 662
The FWDU provides an interface to the Sammi API part of the on–board systems through the formats generated
by the FWDU format editor and text editor. The conventions defined in the following sections must be followed
by the flight specific Support Software (not part of the FWDU) in order for the on–board execution to work
properly.
6.10.1 File Naming Conventions
Many of the FWDU end items (displays and other end items referenced by displays) will at run time be represented
by files. The naming convention for these files has to comply to the one applicable for the Operational
File Transfer (OFT) which is defined as:
Furthermore, the restrictions imposed by Sammi have to be observed (i.e. limitation in length, specific extension
for formats ...)
Therefore, two different file naming conventions in line with the above rule are used depending on the type of
the end item:
Synoptic Display End Items
S__.fmt
where is the decimal representation of the SID with no leading zeros (10 digits max) and is the last part of the pathname (16 characters max).
Other End Item Types
This file naming convention is used because of the limited length of the file names that can be specified in the
Sammi formats.
The file names for all other FWDU end item types referenced within display end items is derived from the SID
of the end item as follows:
S__.
where is the decimal representation of the SID with no leading zeros (10 digits max).
The depends on the end item type according the the following table:
MDB end item type Equivalent Sammi file extension / type
(see Sammi documentation for details)
FWDU_HELP_TEXT *.hlp ASCII help text, displayed in the RTE when a user
clicks the middle mouse button
FWDU_CONVERSION_TEXT *.cnv ASCII conversion table, used by Formatted Numeric
DFD types
FWDU_SYMBOL_TABLE_TEXT *.safs ASCII symbol table or text table, used by the Symbol
/ Text Table DFD types
FWDU_DYNAMIC_OBJECT_TABLE_TEXT *.dobj ASCII dynamic object table, used by the Dynamic
Object DFD type
FWDU_LIST_TEXT *.cmd ASCII standard menu or select file list, used by the
Menu and Select List DFD types
FWDU_DATA_DEF_RECORD_TEXT *.ddr ASCII Data Definition Record, used by the Tabular
DFD type
FWDU_SYMBOL_BITMAP_BINARY *.sym Binary symbol bitmap, used by Symbol Table, Object
Icon, and General Action Button DFD types

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
176 von/of: 662
FWDU_X_BITMAP_BINARY *.xbm Binary bitmap image, used as a background image
on a format; also used by Graphic Data Field and
General Action Button DFD types
FWDU_GIF_BINARY *.gif Binary GIF image, used as background image in a
format; also used by Graphic Data Field and General
Action Button DFD types
FWDU_XWD_BINARY *.xwd Binary X Window Dump image, used as background
image in a format; also used by Graphic
Data Field and General Action Button DFD types
6.10.2 Logical Server Name
The name of the logical server specified in the Sammi formats is set to FWDU_SERVER.

Space Infrastructure
6.10.3 Commands to the On–Board System
6.10.3.1 Software Commanding
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
177 von/of: 662
The FWDU shall support sending of ASCII command strings via the Sammi Run Time Environment (RTE) to
the on–board data server in accordance to the syntax as defined in the RM for CPL & SW Commanding, applicable
document 2.1.2.3, chapter 5.3.1 (Syntax description) in conjunction with section 5.3.2 (Predefined Items
for the FWDU) with the following amendments:
parameter ::= value
end_item_id ::= ”!” integer_literal
Note: Due to limitations inherent to the underlaying Sammi commercial product the overall length of such an
ASCII command string is restricted to a maximum of 80 characters.
Rule 1: For parameters of type ”system_check” as defined in applicable document 2.1.2.3, chapter 5.3.2. an
empty pathname denoted by ”\\” shall be translated to an end_item_id of ”!0”
Rule 2: The identifier has to be one of the s of the FWDU_SYNOPTIC_DISPLAY end item
containing the command string. The identifier shall comply to the rules specified in applicable document
2.1.2.3 (CPL LRM), section 4.1.2.2.1.
6.10.3.2 Pre–Defined Commands
In addition to Software Commands as defined above, the FWDU shall support sending of fixed ASCII command
strings via the Sammi Run Time Environment (RTE) to the on–board data server.
The commands can be pre–defined by the user in a dedicated list as part of the FWDU environment setup
(FWDU_EQUIPMENT_CONSTRAINTS end item type). This list is initially empty. It is user responsibility to
define the set of commands he intends to use.
During display creation time this list is presented to the user on request for selection.
The list has to comply with the following rules:
COMMAND_LIST BEGIN
{ ↵ }
END
where is any sequence printable ASCII characters (excluding quotes) enclosed in quotes (e.g
”ANNOTATE” or ”shutdown $System”). The string enclosed in quotes must not exceed 80 characters in length
(Sammi limitation).
As an example, the following list definition would serve the needs for the COF on–board system (according to
the current baseline):
COMMAND_LIST BEGIN
”Annotate”
”HELP”
”EXIT”
”MARK
”MUR”
”LIMITS”
END

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
178 von/of: 662
Note: The case of the commands is preserved, but the case is ignored when the user enters commands manually
in the FWDU, e.g. the commands ”Annotate”, ”annotate”, and ”ANNOTATE” will be interpreted
as the same command. They are sent to the on–board data server as entered by the user (i.e. no case conversion
is performed by the FWDU).
6.10.3.3 Window Association Information (WAF)
The T_FWDU_BIND_RAW aggregate is used to keep track of which data–delivering on–board end items a
DDO refers to. For historical reasons, this information is commonly referred to as ”Window Association File
(WAF)”.
Intended use on–board: When a Synoptic Display is opened the on–board data server will read the associated
WAF information in order to compose the Cyclic Acquisition Table (CAT), which in turn is used to obtain efficient
data acquisition from the DMS Services.
Although the aggregate is of type RAW the WAF information stored in it is line oriented ASCII with the following
syntax:
”H”
”D”
”S”
where denotes the ASCII Space character
denotes the ASCII New Line character (\0a hexadecimal)
Rule 1: The WAF always starts with one ”H” (header) line specifying the total number of DDOs (). If there are no DDOs in a display then = ”0” (zero).
Rule 2: For each DDO containing at least one measurement end item reference, the WAF contains one ”D” line
which specifies the DDO–name and the number of related end–item SIDs () (i.e. if there
are no measurement end items referenced by a DDO no ”D” line will be present for that specific DDO).
Note: For inconsistent / incomplete displays (which may be encountered during Synoptic Display
development time) the might be completely missing.
Rule 3: s must not contain blanks (ASCII space).
Rule 4: Each ”D” line is followed by one or more ”S” lines. Each ”S” line specifies one end–item SID ()
of the CGS standard end item types as defined in section 6.11.1 (i.e. references to other end item types
like FWDU_HELP_TEXT are not recorded here). All fields are separated by a single ASCII space character().
The following example WAF informations shall serve as illustration of the above rules:
Example 1: A Synoptic Display contains two output DDOs e.g. TEMP_PLOT, which has three end–items, and
TEMP_METER, which has one end–item. The resulting WAF information would be:
H 2
D TEMP_PLOT 3
S 111224
S 111225
S 111226
D TEMP_METER 1
S 112334
Example 2: If a Synoptic Display contains input DDOs only the resulting WAF information would be:
H 0

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
179 von/of: 662
Example 3: Assume a Synoptic Display containing three DDOs, one input and two output, of which one has no
measurement end item attached (i.e. Rule 2 above applies). Since input DDOs are not recorded the resulting
WAF information would be:
H 1
D A_PLOT 2
S 111224
S 111225
Example 4: Assume the same Synoptic Display as in example 3 with the only difference that the user did not
name the DDO containing the measurement end item references The resulting WAF information would be:
H 1
D 2

Space Infrastructure
6.10.4 FWDU Applied Type Mapping
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
6.10.4.1 Mapping between On–board and CGS standard end item types
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
180 von/of: 662
The on–board measurement end items are flight element specific and are defined by the CGS user later on.
Therefore, user defined measurement end items have to be mapped to CGS standard measurement end item types
(see chapter 3.1 of AD 2.1.6.1] (MDB ICD) for details on this mapping concept).
The FWDU allows access to user defined measurement end items by using the V_ENT_EI_TYPE view as defined
in section 7.3.5. ”Retrieval of Type Mapping Information” in conjunction with section 7.3.4.3 ”User–
Tree–Nodes View” of AD 2.1.6.1 (MDB ICD). I.e. the FWDU will only accept user defined measurement end
items that map to:
EGSE_INTEGER_MEASUREMENT EGSE_INTEGER_SW_VARIABLE
EGSE_FLOAT_MEASUREMENT EGSE_FLOAT_SW_VARIABLE
EGSE_DISCRETE_MEASUREMENT EGSE_DISCRETE_SW_VARIABLE
UNSIGNED_INTEGER_MEASUREMENT UNSIGNED_INTEGER_SW_VARIABLE
DOUBLE_FLOAT_MEASUREMENT DOUBLE_FLOAT_SW_VARIABLE
BOOLEAN_MEASUREMENT BOOLEAN_SW_VARIABLE
6.10.4.2 Mapping between CGS standard end item types and Sammi data types
The following table shows the mapping between MDB end item types and the corresponding Sammi data types.
The logical names mdb_int, mdb_uint, mdb_float, mdb_sfloat, mdb_bool, mdb_discrete are defined corresponding
to CGS standard measurement types to be used in the following tables.
MDB
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
data type
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
mdb_uint ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁ
mdb_sfloat ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁ
mdb_discrete
CGS standard measurement end item
Sammi data type
mdb_int
EGSE_INTEGER_MEASUREMENT
long
mdb_int
EGSE_INTEGER_SW_VARIABLE
long
mdb_uint UNSIGNED_INTEGER_MEASUREMENT long
UNSIGNED_INTEGER_SW_VARIABLE long
EGSE_FLOAT_MEASUREMENT float
mdb_sfloat EGSE_FLOAT_SW_VARIABLE
float
mdb_float DOUBLE_FLOAT_MEASUREMENT
double
mdb_float DOUBLE_FLOAT_SW_VARIABLE
double
mdb_discrete EGSE_DISCRETE_MEASUREMENT text, long (1)
EGSE_DISCRETE_SW_VARIABLE text
mdb_bool BOOLEAN_MEASUREMENT
text,long (1)
mdb_bool BOOLEAN_SW_VARIABLE
text
ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁ
(1) ÁÁÁ
text: ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
If linked to TEXT display type.
long: ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
If linked to DYNAMIC OBJECT, OBJECT ICON and simular display types via their raw
values (only possible for MEASUREMENTs, since SW VARIABLEs do not have raw
values).
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁ
ÁÁÁ
ÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁ ÁÁÁ ÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁ
ÁÁÁ Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
Á ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁ ÁÁÁ
ÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁ

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
181 von/of: 662
The following table shows the names of the Sammi DDOs, their internal types, and the MDB data types that can
be mapped to DDOs. The below mentioned attributes will stay the same for modified DDOs saved in a *.lib
library. For the DDOs where no corresponding MDB data type is specified no mapping is possible.
ÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
bar ÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
barchart ÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ
Sammi DDO type name
Sammi
internal
DDO type # MDB data type
alarm 5001 mdb_discrete
5011 mdb_int mdb_uint mdb_sfloat mdb_float
5036 mdb_int mdb_uint mdb_sfloat mdb_float
browser
5029
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ
button group
5026 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ
equation
ÁÁÁÁÁ
curveset
5017 mdb_sfloat
dynamic object 5021 mdb_int mdb_uint mdb_sfloat mdb_float mdb_discrete mdb_bool
5016
fix–scale meter
5031
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
mdb_int mdb_uint mdb_sfloat mdb_float
formatted numeric ÁÁÁÁÁ
ÁÁÁÁÁ
5033 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ ÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
integer
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ
mdb_int mdb_uint mdb_sfloat mdb_float
gauge
5019 mdb_int mdb_uint mdb_sfloat mdb_float
graphic date field 5034
5004 mdb_int mdb_uint
menu 5014
meter
5018
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
option ÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ
mdb_int mdb_uint mdb_sfloat mdb_float
moving scale meter 5032 mdb_int mdb_uint mdb_sfloat mdb_float
object icon 5030 mdb_int mdb_uint mdb_sfloat mdb_float mdb_discrete mdb_bool
5015
pie 5035 mdb_int mdb_uint mdb_sfloat mdb_float
plot
5008
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ
mdb_sfloat
pushbutton
5025 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ
scrollbar
ÁÁÁÁÁ
real
5005 mdb_sfloat mdb_float
region 5037 mdb_int mdb_uint
5024 mdb_int mdb_uint
select list
5027
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ
slider
5028 ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
time ÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
mdb_int mdb_uint mdb_sfloat mdb_float
symbol table
5012 mdb_int mdb_uint mdb_sfloat mdb_float mdb_discrete mdb_bool
tabular 5022 mdb_int mdb_uint mdb_sfloat mdb_float
5023
text 5003 mdb_bool, mdb_discrete
text table
5007
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
mdb_int mdb_uint mdb_sfloat mdb_float
trend
5009 mdb_sfloat
ÁÁÁÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ ÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
ÁÁÁÁÁ ÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁÁ
ÁÁÁÁÁÁÁÁ
The following table shows the Sammi data types, their internal Sammi value and their size.
typeÁÁÁÁ ÁÁÁÁÁ
ÁÁÁÁ ÁÁÁÁÁ
Sammi data Value Size in bits
short 1 16
long
2 32
float
3 32
ÁÁÁÁÁÁ
ÁÁÁÁ ÁÁÁÁÁ
ÁÁÁÁÁÁ ÁÁÁÁ
ÁÁÁÁÁÁ ÁÁÁÁÁ
ÁÁÁÁ ÁÁÁÁÁ
ÁÁÁÁÁÁ
ÁÁÁÁ
ÁÁÁÁ
ÁÁÁÁÁÁ
ÁÁÁÁÁ
ÁÁÁÁÁ

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
CHAPTER 7 :
CHECKOUT AND
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
182 von/of: 662
SIMULATION INTERFACES

Space Infrastructure
7.1 Test Setup Invocation Interface
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
183 von/of: 662
For the integration of TSCV into CGS, TSCV provides interface functions for the invocation of the product.
Two operating modes are provided by TSCV, the interactive mode and the batch mode. In interactive mode,
the test system is controlled by the user providing a graphical user interface. Whereas in batch mode, the
graphical user interface will be suppressed, and the test system is set-up and controlled automatically as
specified by the command line parameters. Depending on the parameter profile, TSCV is invoked in either
mode.
Note only one TSCV instance can be active at any time, regardless of its operating mode.
To run TSCV in interactive mode:
$TSCV_HOME/bin/common/start_tscv
[–Ws ] Initial main window size in pixels
[–Wp ] Initial main window placement in pixels
[–WG [x][++]]
[–geometry [x][++]]
Initial main window size and placement in pixels
[–WP ] Initial icon placement in pixels
[–Wi] or [+Wi] TSCV to come up closed or open (default)
To run TSCV in batch mode:
$TSCV_HOME/bin/common/start_tscv
–mn
–ec
–sv
–sn
–cn
–cv
–tc
[–ts [–fa ] ]
Enable final archiving of test data; disabled by
default
–q quit after starting master AP to provide for later
interactive control
The batch mode command line parameters have the following meaning:
mission_name name of the mission
Example: FLIGHT4711
element_configuration name of the element configuration
Example: APM
system_tree_version identification of the version of the system name tree to be used for the
given mission and element configuration
Example: 5
system_tree_node_name virtual node in the system (name) tree for the selected mission,
element configuration and version of the name tree where the given

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
184 von/of: 662
CCU is looked up
Example: ’\APM\EGSE’
CCU_name name of the CCU in MDB
Example: IF_TEST
CCU_version version identification of the given CCU. Note that a full version
identification comprises the version, issue and revision number
Example: 1.1.0
test_configuration pathname of the database enditem of type
EGSE_TEST_CONFIGURATION. This enditem describes how the
setup of the test equipment shall be done
Example: ’\APM\EGSE\SYSTEM\IF_TEST\SETUP_3’
test_session_name name of the test session to be created in TRDB for the given test
If the test session name argument ts is omitted, test data will be stored within
TRDB’s default test session. The test session name can consist of capital
letters, digits and underscores only, but starting with a capital letter. Its
length is limited to 20 characters maximum.
Example: IF_TEST_3
The final archive argument fa, i.e. store test data on final archive media, has
only meaning if a test session name argument is provided. By default, final
archiving is disabled.
Note because of backslashes, path names of MDA on the UNIX command line are to be enclosed by single
quotes.
The command will return on command line parameter errors, after starting the designated master AP when
invoked with q option, or after the test is finished, which may take up hours or even days. The final status is
indicated by following return codes:
99 success
100 invalid CCU selection
101 invalid mission name
102 invalid element configuration
103 invalid system tree version
104 invalid CCU name
105 invalid CCU version
106 invalid system tree node name
107 failed to connect to other CGS product
108 invalid test configuration
109 failed to set–up test configuration
110 failed to start test execution
111 failed to create test session
112 test configuration already active
113 a node already participates in another active test configuration
114 test session name already in use
115 no final archive device available
116 failed to start master AP
117 another TSCV instance already executing
118 invalid user profile
119 invalid command line parameter profile
120 default test session already in use
121 TSCV internal error
122 Maximum number of test configurations exceeded
123 no replay mode allowed

Space Infrastructure
7.2 VICOS Types Definition
Informal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
185 von/of: 662
A same set of data types are used in the various procedural interfaces provided by VICOS products. In order
to ensure the consistency of their definition and usage through all the interfaces, they are grouped and defined
once, in the current section.
They are ”basic” data types and constants (like numbers, strings, enumerations...) which are accessible directly.
They constitute a type pool and are grouped into a set of Ada packages, according to their nature.
The usage of the basic data types is simple. The desired variable has to be declared with the desired type in the
piece of software which will use it. The access to the content of the variable is done directly, by knowledge of
its Ada structure.
The VICOS_DEFINITIONS package contains type and constant definitions that are :
– specific of VICOS products, i.e. not used by several products of other CGS assemblies,
– common in VICOS products, i.e. used or shared by several VICOS provided services,
– of general nature, i.e. not specific to any of these services.

Space Infrastructure
Formal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
––
–– VICOS_DEFINITIONS (spec)
––
––****************************************************************************
––ABSTRACT––
––
–– This package contains type definitions and constants for VICOS global
–– use.
––
––
––*–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––IDENTIFICATION––
–– PROJECT NAME : CGS
–– PRODUCT NAME : HCI
–– CI–NUMBER : 1216 878
–– OBJECT NAME : VICOS_DEFINITIONS
––*–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––CONTENTS––
–– COMPILER : SunAda 1.1 / Alsys Ada 5.5.1
–– LANGUAGE : Ada
–– SPECIAL CONTENTS: –
–– CHANGE HISTORY
–– #IRN 6008:
–– Add GDU Alternative BINARY_PACKET
–– Author: P.Athmann
–– Date: 14.2.97
–– V3.0 at ERNO ; CGS engineering
–– creator: gehrke (on host mps2s–1)
–– creation date: 15.05.95 15:00:00
–– CGS V2 Build 2 baseline, PIRN 3023/E
–– V2.8 at ERNO ; VICOS development
–– creator: athmann (on host vicos_s)
–– creation date: 26.11.92 16:43:44
–– update representation clause for T_ERROR_MESSAGE
–– V2.7 at ERNO ; VICOS development
–– creator: athmann (on host vicos_s)
–– creation date: 26.11.92 10:27:57
–– correct representation clauses for T_NAME_STRING
–– V2.6 at ERNO ; VICOS development
–– creator: vicos (on host vicos_s)
–– creation date: 17.11.92 11:37:09
–– adts version 2.0.1: update acc. to PIRN VICOS–2020
–– V2.5 at ERNO ; VICOS development
–– creator: vicos (on host prime_1)
–– creation date: 18.09.92 12:15:22
–– modifications according to FINAL ICD REVIEW DNs (see list)
–– V2.4 at ERNO ; VICOS development
–– creator: vicos (on host vicos_8)
–– creation date: 21.07.92 12:15:05
–– Added T_FILE_NAME and NULL_FILE_NAME for several abstract data types.
–– V2.3 at ERNO ; VICOS development
–– creator: vicos (on host vicos_8)
–– creation date: 21.07.92 07:31:57
–– Naming of CGS_CALENDAR changed to VICOS_CALENDAR
–– V2.2 at ERNO ; VICOS development
–– creator: athmann (on host vicos_5)
–– creation date: 10.07.92 15:35:52
–– Update according to VCS SPADM
–– V2.1 at ERNO ; VICOS development
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
186 von/of: 662

Space Infrastructure
–– creator: vicos (on host vicos_s)
–– creation date: 30.06.92 17:38:05
–– added Standard Header by command create_file
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
––****************************************************************************
––
with NUMERIC_TYPES; use NUMERIC_TYPES;
with CGS_CALENDAR;
–– type CGS_DATE_AND_TIME
package VICOS_DEFINITIONS is
SPEC_VERSION : constant STRING := ”@(#) VICOS_DEFINITIONS 4.3.1 spec”;
––––––––––––––––––––
–– Global Constants
––––––––––––––––––––
MAX_FRAME_LENGTH : constant := 2048;
MAX_LENGTH_OF_FILE_NAME: constant := 256;
–– sets limit for filenames to be
–– stored in VICOS data structures
MAX_LENGTH_OF_DIRECTORY_NAME: constant := 256;
–– sets limit for directory names to be
–– stored in VICOS data structures
MAX_LENGTH_OF_DB_PATHNAME: constant := 256;
–– sets limit for MDB pathnames to be
–– stored in VICOS data structures
–––––––––––––––––––
–– Types for filenames
–––––––––––––––––––
type T_FILE_NAME is
record
THE_STRING : string (1..MAX_LENGTH_OF_FILE_NAME);
LENGTH : integer range 0..MAX_LENGTH_OF_FILE_NAME;
end record;
for T_FILE_NAME use
record
LENGTH at 0 range 0..31;
THE_STRING at 0 range 32..32+((MAX_LENGTH_OF_FILE_NAME*8)–1);
end record;
for T_FILE_NAME’size use MAX_LENGTH_OF_FILE_NAME*8+32;
NULL_FILE_NAME : constant T_FILE_NAME := ((others => ’ ’), 0);
–––––––––––––––––––
–– Types for Names
–––––––––––––––––––
MAX_NAME_LENGTH : constant := 20;
type T_NAME_STRING is
record
THE_STRING : string (1..MAX_NAME_LENGTH);
LENGTH : integer range 0..MAX_NAME_LENGTH;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
187 von/of: 662

Space Infrastructure
end record;
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
for T_NAME_STRING use
record
LENGTH at 0 range 0..31;
THE_STRING at 0 range 32..32+((MAX_NAME_LENGTH*8)–1);
end record;
for T_NAME_STRING’size use 32+ MAX_NAME_LENGTH*8;
type T_APPLICATION_TYPE is (
HCI,
TES,
DBS,
TEV,
TSCV,
SAS,
CSS);
–– types of VICOS application processes
subtype T_APPLICATION_NAME is T_NAME_STRING;
subtype T_TEST_SITE is T_NAME_STRING;
MAX_PROC_UNIT_NAME_LEN : constant := MAX_NAME_LENGTH;
–– The max. process unit name
subtype T_PROC_UNIT_NAME is T_NAME_STRING;
–– name of a unit inside a process
EMPTY_NAME_STRING : constant T_NAME_STRING
:= (THE_STRING => (others => ’ ’), LENGTH => 0);
subtype T_SAS_NAME is T_NAME_STRING;
–– SAS short name used in ADU and GDU descriptions
––––––––––––––
–– Identifier
––––––––––––––
type T_HK_ID is new INTEGER;
for T_HK_ID’size use 32;
–– identifier for TES housekeeping variables
subtype T_PRIVATE_ID is string(1..10);
–– ADU and GDU private identifier used by SAS’s.
NULL_PRIVATE_ID : constant T_PRIVATE_ID := (others => ’ ’);
–––––––––––––––––––
–– EGSE nodes and SW types
–––––––––––––––––––
type T_EGSE_NODE_TYPES is
(WORKSTATION,
TEST_NODE,
SIMULATOR,
DATABASE_SERVER,
FRONT_END_EQUIPMENT,
UNIT_UNDER_TEST);
type T_EGSE_NODE is record
The_Type : T_EGSE_NODE_TYPES;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
188 von/of: 662

Space Infrastructure
The_Name : T_NAME_STRING := EMPTY_NAME_STRING;
end record;
type T_EGSE_SW_TYPES is
(SAS,
EXECUTABLE,
DATA_FILE);
type T_EGSE_SW is record
The_Type : T_EGSE_SW_TYPES;
The_Full_Name : T_FILE_NAME;
The_Short_Name: T_NAME_STRING := EMPTY_NAME_STRING;
end record;
––––––––––––––––––––––––––––––––––––––––––––––––
–– VICOS Error Messages and Logging Definitions
––––––––––––––––––––––––––––––––––––––––––––––––
MAX_SHORT_TEXT_LENGTH : constant := 40;
MAX_LONG_TEXT_LENGTH : constant := 255;
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
subtype T_LOG_TEXT_SHORT is string(1.. MAX_SHORT_TEXT_LENGTH);
NULL_LOG_TEXT_SHORT : constant T_LOG_TEXT_SHORT:= (others => ’ ’);
subtype T_LOG_TEXT_LONG is string(1.. MAX_LONG_TEXT_LENGTH);
NULL_LOG_TEXT_LONG : constant T_LOG_TEXT_LONG:= (others => ’ ’);
subtype T_LOG_GROUP is STRING(1..4);
NULL_LOG_GROUP : constant T_LOG_GROUP := (others => ’ ’);
subtype T_LOG_TYPE is STRING(1..4);
NULL_LOG_TYPE : constant T_LOG_TYPE := (others => ’ ’);
type T_ERROR_MESSAGE is
record
TIME_TAG_LT : CGS_CALENDAR.CGS_DATE_AND_TIME;
TIME_TAG_SMT : CGS_CALENDAR.CGS_DATE_AND_TIME;
NODE : T_APPLICATION_NAME;
GROUP : T_LOG_GROUP;
ERROR_TYPE : T_LOG_TYPE;
MSG_NUMBER : INTEGER; –– message number
SHORT_TEXT : T_LOG_TEXT_SHORT;
LONG_TEXT : T_LOG_TEXT_LONG;
end record;
for T_ERROR_MESSAGE use
record
TIME_TAG_LT at 0 range 0..127;
TIME_TAG_SMT at 0 range 128..255;
NODE at 0 range 256..256+(MAX_NAME_LENGTH*8)+31;
GROUP at 0 range 256+MAX_NAME_LENGTH*8+32..
256+MAX_NAME_LENGTH*8+63;
ERROR_TYPE at 0 range 256+MAX_NAME_LENGTH*8+64..
256+MAX_NAME_LENGTH*8+95;
MSG_NUMBER at 0 range 256+MAX_NAME_LENGTH*8+96..
256+MAX_NAME_LENGTH*8+127;
SHORT_TEXT at 0 range
256+MAX_NAME_LENGTH*8+128..
256+MAX_NAME_LENGTH*8+128+MAX_SHORT_TEXT_LENGTH*8–1;
LONG_TEXT at 0 range
256+MAX_NAME_LENGTH*8+MAX_SHORT_TEXT_LENGTH*8+128..
256+MAX_NAME_LENGTH*8+128+MAX_SHORT_TEXT_LENGTH*8+
MAX_LONG_TEXT_LENGTH*8–1;
end record;
for T_ERROR_MESSAGE’size use 256+128+MAX_NAME_LENGTH*8+
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
189 von/of: 662

Space Infrastructure
MAX_SHORT_TEXT_LENGTH*8+
MAX_LONG_TEXT_LENGTH*8 ;
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
USER_EVENT_LOG_GROUP : constant T_LOG_GROUP := ”UEVT”;
SYSTEM_LOG_GROUP : constant string := ”SYST”;
TSCV_LOG_GROUP : constant string := ”TSCV”;
HCI_LOG_GROUP : constant string := ”HCI ”;
HLCL_LOG_GROUP : constant string := ”HLCL”;
TES_LOG_GROUP : constant string := ”TES ”;
MONITORING_LOG_GROUP : constant string := ”MON ”;
ACQUISITION_LOG_GROUP : constant string := ”DACQ”;
GENERATION_LOG_GROUP : constant string := ”DGEN”;
ARCHIVING_LOG_GROUP : constant string := ”ARCH”;
COMMAND_LOG_GROUP : constant string := ”CMD ”;
DATA_DISPATCH_LOG_GROUP : constant string := ”DDS ”;
UCL_INTERPRETER_LOG_GROUP : constant string := ”UCLI”;
UCL_CLASS1_LOG_GROUP : constant string := ”UCL1”; –– Stmnts exc the following
UCL_CLASS2_LOG_GROUP : constant string := ”UCL2”; –– Monitoring Statements
UCL_CLASS3_LOG_GROUP : constant string := ”UCL3”; –– Enditem Statements
UCL_CLASS4_LOG_GROUP : constant string := ”UCL4”; –– SAS & UCL Ctrl Statements
UCL_LOG_STMT_LOG_GROUP : constant string := ”LOG ”;
REPLAY_LOG_GROUP : constant string := ”REPL”;
CONF_DB_LOG_GROUP : constant string := ”CDB ”; –– For access to Conf DB
TRDB_LOG_GROUP : constant string := ”TRDB”; –– For access to Result DB
TST_LOG_GROUP : constant string := ”TST ”; –– For test/ debugging
UUT_LOG_GROUP : constant string := ”UUT ”; –– msg received from UUT
SAS_LOG_GROUP : constant string := ”SAS ”; –– msg received from SAS
COND_LOG_GROUP : constant string := ”COND”; –– from conditions
TC_VERIF_LOG_GROUP : constant string := ”DGVF”; –– from GDU verification
–– Remark: when modifying this log (check out) message type
–– section, the operation ERROR_SERVICES.TO_SEVERITY must be updated!
INFO_MESSAGE_TYPE : constant string := ”INFO”;
GENERAL_MESSAGE_TYPE : constant string := ”MSG ”;
ERROR_MESSAGE_TYPE : constant string := ”ERR ”;
WARNING_MESSAGE_TYPE : constant string := ”WRN ”;
EXCEPTION_MESSAGE_TYPE: constant string := ”EXC ”;
ALARM_MESSAGE_TYPE : constant string := ”ALRM”;
––––––––––––––––––––––––––
–– VICOS Mode Definitions
––––––––––––––––––––––––––
type T_VICOS_MODE is (
NONE,
NORMAL,
REPLAY,
SIMULATION,
ANY_MODE);
for T_VICOS_MODE’size use 16;
type T_VICOS_STATUS is (
IDLE,
RUNNING,
SUSPENDED,
ERROR);
for T_VICOS_STATUS’size use 16;
–––––––––––––––––––
–– raw value alternatives
–––––––––––––––––––
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
190 von/of: 662

Space Infrastructure
type T_RAW_VALUE_ALTERNATIVES is (UNDEFINED,
SINGLE_BIT,
INT,
U_INT,
FLOAT_EGSE,
BYTE_STREAM);
–– The raw value alternatives indicates if :
–– – the raw value is not set–up, so there is a bug,
–– – the raw value contains a single bit
–– – the raw value contains an integer
–– – the raw value contains an unsigned integer
–– – the raw value contains a float (32 bit)
–– – the raw value contains a byte stream
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
MAX_BYTE_STREAM_LENGTH: constant := 255;
–– sets the upper limit of a byte stream value
–––––––––––––––––––
–– adu alternatives
–––––––––––––––––––
type T_ADU_ALTERNATIVES is (
UNDEFINED,
STRUCTURED,
UNSTRUCTURED,
CCSDS_PACKET);
–– The ADU description alternatives indicates if :
–– – the ADU description is a structured adu
–– (a list of measurements sid),
–– – the ADU description is an unstructured adu
–– (a byte array),
–– – the ADU description contains a ccsds packet.
–––––––––––––––––––
–– gdu alternatives
–––––––––––––––––––
type T_GDU_ALTERNATIVES is (
UNDEFINED,
ANALOG_STIMULUS,
DISCRETE_STIMULUS,
BINARY_PACKET,
CCSDS_PACKET);
–– The GDU description alternatives indicate if :
–– – the GDU contains a REAL parameter (ANALOG_STIMULUS)
–– – the GDU contains an INTEGER parameter (DISCRETE_STIMULUS)
–– – the GDU contains a binary packet (byte array)
–– – the GDU contains a CCSDS packet (CCSDS_PACKET)
end VICOS_DEFINITIONS;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
191 von/of: 662

Space Infrastructure
7.3 HCI Abstract Data Types
7.3.1 General Concepts
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
192 von/of: 662
A same set of abstract data types related to HCI are used in the VICOS products. In order to ensure the consistency
of their definition and usage through the softwares, they are grouped and defined once, in the current
section.
An ADT specification describes a class of data structures not by an implementation, but by the list of services
available on the data structures and the formal properties of these services. Further, an ADT offers a set of services
to the outside world (other Objects, Applications etc), which is only concerned with the services offered
and not how they are implemented.
An ADT is defined by a formal specification, which is comprised of Types and Functions (Syntax part) and Preconditions
and Axioms (Semantic part).
– The Type part lists the types of the specification (which may be several types or a single type, e.g. a
’stack’).
– The Functions part lists the services available on instances of the type.
– The Axioms part describes semantics of the functions on the data to restrict and more precisely define
the specification.
– The Preconditions part provides applicability conditions for partial functions (functions that cannot be
applied to the ADT implementation in all cases (e.g., when a data type is empty, it may not be useful
to access its contents)).
An abstract data type is a type which Ada structure is hidden (private types) because of its complexity, its varying
size or its implementation dependency on compilers. Their access is possible only through associated operations.
This part of the interface allows pieces of software to manipulate data without knowledge of their Ada representation.
These types are available in the form of separate Ada packages containing at least an abstract data type,
some basic data types related to it and the operations to handle it.
The ADT services provided by HCI contain a number of services applicable to appropriate ADTs. These may
include Create services, used to create the ADT structure, Set services, which set up the data within the ADT
(e.g. for data originally held in the Mission Database or in UNIX files), Get services, which read the data set–up
in the ADT and Delete services which remove the ADT. There are also type specific services which are ADT
specific, these may include services such as Initialise, Copy, Move, Pack and Unpack. The latter Pack and Unpack,
when provided, are particularly important for data transfer to provide a method of packing and unpacking
data into Byte arrays to enable easy data communication.
The usage of the abstract data types is quite sophisticated. The desired variable is declared with the desired type
in the piece of software which will use it. The access to the content of the variable is done by using the associated
operations, because the associated Ada type is not visible. A Create/Construct operation, when provided, is the
first to be used, to instanciate the content of the variable. The Set_values operations can then be used to write
data into the instanciated variable. The Values_of/Get_values operations allow to read data from the instanciated
and filled–up variable. At last the Delete operation, when provided, will free the space allocated to ADT variables
which are not needed any more in the software.
HCI provides a set of ADTs which are used as appropriate by other products, including:
– ADT for packing/unpacking,
– ADT for Physical Address type,
– ADT for CCSDS Packet type,
– ADT for User Profile type,

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
193 von/of: 662
– ADT for User Message type,
– ADT for Version ID Table type,
– ADT for System Topology Table type (host logical names, test site name),
– ADT for SID list type.
HCI provides a method of accessing HCI data structures held in the Mission Database without causing performance
problems with continuous database access. A procedure for establishing an ADT based on MDB data is
as follows: the MDA appropriate operation will be called to read appropriate Check–out information. HCI will
provide ADT Create services (if any) to create the ADT in memory and ADT Set services will be used to put
the data from the MDB into the ADT data area. (Note, these services used by MDA) The product requiring ADT
access (maybe another Integration/Qualification product) can then use the HCI provided ADT Get services to
access the ADT data and functions. On completion of use and when provided, HCI ADT Delete services are used
to remove the ADT.
Note that the use of ADTs within CGS provides a mechanism for Memory Management, which helps to avoid
the problems of ’Garbage Collection’ that occurs with manipulating data structures within an ’Ada’ Run Time
system. This is particularly useful for tasks performed by Integration/Qualification products which need to
transfer data information between programs.
Some basic types are also defined in ADT packages. They are, most of the time, enumeration types bound to
the ADT defined in that package.
For these enumeration types, the following naming convention has been used :
– types suffixed with _TYPE are enumeration types not determining a particular structure of the ADT;
it can be considered as a normal attribute of the ADT, e.g. INTERPRETATION_TYPE in
ADT_MEASUREMENT_DESCRIPTION.
– types suffixed with _ALTERNATIVES are enumeration types which determine the set of other attributes
the corresponding ADT will contain, e.g. T_ADU_ALTERNATIVES in ADT_ADU_DE-
SCRIPTION.
7.3.2 Operations
This section describes the operations which are available on the previous types.
7.3.2.1 SET Operations
The SET operation(s) will assign the values of the attributes of an ADT. At least one SET operation has to be
provided, but in general there will be several SET operations, one for each of the attributes composing the ADT.
In case the type of the attribute exactly determines the alternative to be set, SET can be a set of overloaded SET
procedures (all having the same name) and the type of attribute to be set will be determined by the type of the
passed parameter. The type of the attribute may be defined in another package, it may be a basic type or an other
ADT. In case several attributes have the same type, different names have to be chosen for the SET operations
(e.g. SET_A, SET_B).
7.3.2.2 GET Operations
The complementary of the SET operation(s) is the GET operation(s). It follows the same rules with respect to
parameters and naming apply as for the SET operation. Most of the time, a function ATTRIBUTE is preferred
to a procedure GET_ATTRIBUTE whenever it is possible, i.e. when no limited private types are returned or
when single attribute is returned.
7.3.2.3 ALTERNATIVE Function
The function ALTERNATIVE returns the value of the alternative a variable of type T_ADT currently has. After
CREATE has been called, the default value of a variable of type T_ADT shall be UNDEFINED. It shall be poss-

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
194 von/of: 662
ible to assign values of any attribute of any alternative to the variable then. This shall, however, then change the
value of the ’discriminent’ to one of the enumeration values in T_ADT_ALTERNATIVES. All attributes belonging
to one alternative of T_ADT_ALTERNATIVES should be assign in one set operation (this is however
not a must, it is a design goal and has to be decided on a case to case basis).
7.3.2.4 PACK Operation
The pack operation packs the contents of a variable of type T_ADT into a block of type T_BLOCK by using
operations of an ADT_PACKING
7.3.2.5 UNPACK Operation
Inversely, UNPACK unpacks a T_BLOCK into a variable of type T_ADT which has been created before.
7.3.2.6 PACKED_SIZE Function
Function PACKED_SIZE returns the maximum number of bytes a packed structure of T_ADT may occupy.
7.3.2.7 ADD Operations
Some complex ADTs use other ADTs (e.g. ADT_ADU) or have a non deterministic memory usage, i.e. they
’use’ varying amounts of memory for a given alternative.
For these ADTs, there exists the possibility to maintain dynamic ’lists’ of attributes or values inside an ADT.
For this purpose, an ADD operation might be provided which then inserts exactly one element to this list.
Examples are the raw values in an ADU in the package ADT_ADU.
This procedure belongs to the specific procedures defined in the frame of a complex ADT. They depend on the
special purpose of the complex ADT and the implementer could add procedures like: get_next_element, read_at
etc.
In most of the cases, these ADD operations can be replaced by a set of SET operations, because the size of the
list is known in advance. For a type T_ADT_ITEM_LIST, the operation SET_SIZE will have to be used first,
and then the operation SET_ITEM, to fill the list at a specified index. Note that the index shall be uniformly
incremented from 1 to the chosen size, with an increment of 1.
7.3.2.8 Operations on tables
The operations defined on T_TABLE follow exactly the same logic as for the ADT itself.
7.3.2.9 Exceptions
The procedures/functions will raise the following standard exceptions :
– STORAGE_ERROR in case the CREATE operation has not sufficient memory space, independent
of the internal implementation
– NOT_CREATED if an operation is called on a variable which has not been created.
– {PARAMETER}_VALUE_ILLEGAL in case the value of the passed parameter is not legal, e.g. a
NULL_SID value for an SID parameter.
– INDEX_ERROR if the value of the passed index exceeds the size of the specified variable, e.g. it is
raised when trying to write/read the 101st element of an ADU which contains only 100 items.
– {ITEM}_NOT_FOUND when the searched item is not found in the specified list.
– {PARAMETER}_TYPE_MISMATCH when the type of the passed parameter and the expected type
of the formal parameter mismatch.

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
195 von/of: 662
On a case by case basis, the operations provided in this interface will also raise specific exceptions which are
documented in the formal interface.
7.3.2.10 Particular Remarks
7.3.2.10.1 On Synchronisation
Certain ADTs (if not all of them) will have the need of performing certain memory management internally. For
security reasons, a synchronised access to the internal memory has to be achieved, but only for the CREATE,
DESTROY, COPY, UNPACK operations since these have impact on memory management.
At present it is not finally decided, whether the ADT internally has to provide synchronisation or whether the
user should ensure synchronised access. However, this shall not have any impact on the Ada specification.
If internal synchronisation shall be provided, the use of Ada tasking and semaphores is not allowed since this
is in conflict with the current HCI design (due to X–windows !!!). Also, for performance reasons, the Ada ’new’
and ’unchecked_deallocation’ are not recommended.
7.3.2.10.2 On Packing/Unpacking
At present there exists in-house a definition of an ADT_PACKING which uses rather sophisticated techniques
to provide secure and elegant packing. However, it is also rather complex. There are investigation on a simpler
approach currently which would reduce complexity and data overheads.
When finally delivering the Ada specifications of all ADTs to the implementation teams, a version of
ADT_PACKING will be delivered also which shall then be used for implementing the PACK/UNPACK operations
of the individual ADTs.
The principals of packing will be that the ADT_ADT.PACK operation is provided with some kind of input
T_BLOCK. The inside the body of the ADT_ADT.PACK routine, other routines of ADT_PACKING shall be
used to ’add’ a packed version of T_ADT to the block. Memory management inside T_BLOCK will be accomplished
inside the ADT_PACKING provided routines. T_BLOCK is then finally returned as an out parameter
of ADT_ADT.PACK (therefore at least it has to be of mode ’in out’).

Space Infrastructure
7.3.3 ADT Physical Address
Informal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
196 von/of: 662
A Physical Address is the set of information on device physical address and used protocol for transfer of data
between an SAS and the corresponding front–end equipment or device. Each time a request for data acquisition/
generation is addressed, the SAS in charge of this data link has to interpret this information part of an ADU/GDU
Description.
A Physical Address is a composite type containing the following attributes :
– a node address;
– a device type;
– a device address;
– a device subaddress;
– a channel number;
– a function code;
– a protocol identification;
– two commands fields allowing support for addresses coding, which format is different from the
standard provided one.

Space Infrastructure
Formal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
––
–– ADT_PHYSICAL_ADDRESS specification
––
––****************************************************************************
––ABSTRACT––
––
–– This package defines and handles types related to physical address
––
––*–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––IDENTIFICATION––
–– PROJECT NAME : CGS
–– PRODUCT NAME : HCI
–– CI–NUMBER : 1216 878
–– OBJECT NAME : ADT_PHYSICAL_ADDRESS
––*–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––CONTENTS––
–– COMPILER :
–– LANGUAGE :
–– SPECIAL CONTENTS:
–– CHANGE HISTORY
–– V3.0 at ERNO ; CGS_ENGINEERING
–– creator: maron (on host vicos2–2)
–– creation date: 07.03.95 12:00:0
–– Build 2 baseline, PIRN 3050
––
–– V2.9 at ERNO ; VICOS development
–– creator: athmann (on host vicos_s)
–– creation date: 19.10.93 18:11:04
–– Initialise type T_PHYSICAL_ADDRESS
––
–– V2.8 at ERNO ; VICOS development
–– creator: athmann (on host vicos_5)
–– creation date: 03.03.93 19:56:19
–– COL–CC–VIC–SPR–009 (representation clauses)
–– V2.7 at ERNO ; VICOS development
–– creator: athmann (on host vicos_s)
–– creation date: 12.01.93 19:47:15
–– remove exception: CONSTRAINT_ERROR (not used)
–– V2.6 at ERNO ; VICOS development
–– creator: vicos (on host vicos_s)
–– creation date: 17.11.92 11:30:34
–– adts version 2.0.1: update acc. to PIRN VICOS–2022
–– V2.5 at ERNO ; VICOS development
–– creator: vicos (on host prime_1)
–– creation date: 18.09.92 12:04:12
–– modifications according to FINAL ICD REVIEW DNs (see list)
–– V2.4 at ERNO ; VICOS development
–– creator: vicos (on host vicos_s)
–– creation date: 28.07.92 09:33:21
–– Changes: editorial, exceptions
–– V2.3 at ERNO ; VICOS development
–– creator: vicos (on host vicos_8)
–– creation date: 20.07.92 08:40:40
–– General layout for ADTs acc. to TN COL_MBER_ZU1_TN_0026_92
–– V2.2 at ERNO ; VICOS development
–– creator: athmann (on host vicos_5)
–– creation date: 10.07.92 17:21:43
–– Update acc. to VCS SPADM DNs
––****************************************************************************
––
with VICOS_DEFINITIONS;
with ADT_PACKING;
package ADT_PHYSICAL_ADDRESS is
–––––––––––––––
–– public types
––––––––––––––––
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
197 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
type T_STRING_80 is
record
THE_STRING: STRING(1..80);
LENGTH: INTEGER;
end record;
for T_STRING_80 use
record
THE_STRING at 4 range 0 .. 639;
LENGTH at 0 range 0 .. 31;
end record;
–––––––––––––
–– adt types
–––––––––––––
type T_PHYSICAL_ADDRESS is private;
–– A physical address is composed of :
–– – a node address,
–– – a bus number
–– – a device type,
–– – a device address,
–– – a device subaddress,
–– – a channel number,
–– – a function code,
–– – a protocol identification,
–– – two commands.
NULL_PHYSICAL_ADDRESS : constant T_PHYSICAL_ADDRESS;
––––––––––––––––––––
–– write operations
––––––––––––––––––––
procedure SET_NODE_ADDRESS (
PHYSICAL_ADDRESS : in out T_PHYSICAL_ADDRESS;
WITH_NODE_ADDRESS : in STRING);
–– DESCRIPTION
–– This procedure sets the current node address value of
–– the specified physical address variable.
–– Empty: if string with blank characters or length 0
–– EXCEPTIONS
–– STRING_LENGTH_ERROR: the string is longer than 20 character
procedure SET_BUS_NUMBER (
PHYSICAL_ADDRESS : in out T_PHYSICAL_ADDRESS;
WITH_BUS_NUMBER : in INTEGER);
–– DESCRIPTION
–– This procedure sets the bus number of
–– the specified physical address variable.
–– Undefined if –1
–– EXCEPTIONS
–– none
procedure SET_DEVICE_TYPE (
PHYSICAL_ADDRESS : in out T_PHYSICAL_ADDRESS;
WITH_DEVICE_TYPE : in STRING);
–– DESCRIPTION
–– This procedure sets the type of the device of
–– the specified physical address variable.
–– Empty: if string with blank characters or length 0
–– EXCEPTIONS
–– STRING_LENGTH_ERROR: the string is longer than 20 character
procedure SET_DEVICE_ADDRESS (
PHYSICAL_ADDRESS : in out T_PHYSICAL_ADDRESS;
WITH_DEVICE_ADDRESS : in STRING);
–– DESCRIPTION
–– This procedure sets the address of the device of
–– the specified physical address variable.
–– Empty: if string with blank characters or length 0
–– EXCEPTIONS
–– STRING_LENGTH_ERROR: the string is longer than 20 character
procedure SET_DEVICE_SUBADDRESS (
PHYSICAL_ADDRESS : in out T_PHYSICAL_ADDRESS;
WITH_DEVICE_SUBADDRESS : in STRING);
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
198 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–– DESCRIPTION
–– This procedure sets the subaddress of the device of
–– the specified physical address variable.
–– Empty: if string with blank characters or length 0
–– EXCEPTIONS
–– STRING_LENGTH_ERROR: the string is longer than 20 character
procedure SET_CHANNEL (
PHYSICAL_ADDRESS : in out T_PHYSICAL_ADDRESS;
WITH_CHANNEL : in INTEGER);
–– DESCRIPTION
–– Set the channel number applicable for
–– the specified physical address variable.
–– Undefined if –1
–– EXCEPTIONS
–– NONE
procedure SET_FUNCTION_CODE (
PHYSICAL_ADDRESS : in out T_PHYSICAL_ADDRESS;
WITH_FUNCTION_CODE : in INTEGER);
–– DESCRIPTION
–– Set the function code applicable for
–– the specified physical address variable.
–– Undefined if –1
–– EXCEPTIONS
–– NONE
procedure SET_PROTOCOL_ID (
PHYSICAL_ADDRESS : in out T_PHYSICAL_ADDRESS;
WITH_PROTOCOL_ID : in INTEGER);
–– DESCRIPTION
–– Set the protocol id applicable for the enditem
–– the specified physical address variable.
–– Undefined if –1
–– EXCEPTIONS
–– NONE
procedure SET_CMD1 (
PHYSICAL_ADDRESS : in out T_PHYSICAL_ADDRESS;
WITH_CMD1 : in STRING);
–– DESCRIPTION
–– Set the general command strings applicable for
–– the specified physical address variable.
–– Undefined if all blank or length 0
–– EXCEPTIONS
––STRING_LENGTH_ERROR: the string is longer than 80 character
procedure SET_CMD2 (
PHYSICAL_ADDRESS : in out T_PHYSICAL_ADDRESS;
WITH_CMD2 : in STRING);
–– DESCRIPTION
–– Set the general command strings applicable for
–– the specified physical address variable.
–– Undefined if all blank or length 0
–– EXCEPTIONS
–– STRING_LENGTH_ERROR: the string is longer than 80 character
–––––––––––––––––––
–– read operations
–––––––––––––––––––
function NODE_ADDRESS (
OF_PHYSICAL_ADDRESS : T_PHYSICAL_ADDRESS)
return VICOS_DEFINITIONS.T_NAME_STRING;
–– DESCRIPTION
–– This function returns the current node address value of
–– the specified physical address variable.
–– EXCEPTIONS
–– NONE
function BUS_NUMBER (
OF_PHYSICAL_ADDRESS : T_PHYSICAL_ADDRESS)
return INTEGER;
–– DESCRIPTION
–– This function returns the bus number of
–– the specified physical address variable.
–– EXCEPTIONS
–– none
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
199 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
function DEVICE_TYPE (
OF_PHYSICAL_ADDRESS : T_PHYSICAL_ADDRESS)
return VICOS_DEFINITIONS.T_NAME_STRING;
–– DESCRIPTION
–– This function returns the current device type value of
–– the specified physical address variable.
–– EXCEPTIONS
–– NONE
function DEVICE_ADDRESS (
OF_PHYSICAL_ADDRESS : T_PHYSICAL_ADDRESS)
return VICOS_DEFINITIONS.T_NAME_STRING;
–– DESCRIPTION
–– This function returns the current device address value of
–– the specified physical address variable.
–– EXCEPTIONS
–– NONE
function DEVICE_SUBADDRESS (
OF_PHYSICAL_ADDRESS : T_PHYSICAL_ADDRESS)
return VICOS_DEFINITIONS.T_NAME_STRING;
–– DESCRIPTION
–– This function returns the current device subaddress value of
–– the specified physical address variable.
–– EXCEPTIONS
–– NONE
function CHANNEL (
OF_PHYSICAL_ADDRESS : T_PHYSICAL_ADDRESS)
return INTEGER;
–– DESCRIPTION
–– This function returns the current channel value of
–– the specified physical address variable.
–– EXCEPTIONS
–– NONE
function FUNCTION_CODE (
OF_PHYSICAL_ADDRESS : T_PHYSICAL_ADDRESS)
return INTEGER;
–– DESCRIPTION
–– This function returns the current function code value of
–– the specified physical address variable.
–– EXCEPTIONS
–– NONE
function PROTOCOL_ID (
OF_PHYSICAL_ADDRESS : T_PHYSICAL_ADDRESS)
return INTEGER;
–– DESCRIPTION
–– This function returns the current protocol id value of
–– the specified physical address variable.
–– EXCEPTIONS
–– NONE
function CMD1 (
OF_PHYSICAL_ADDRESS : T_PHYSICAL_ADDRESS)
return T_STRING_80;
–– DESCRIPTION
–– This function returns the 1st command string of
–– the specified physical address variable.
–– EXCEPTIONS
–– NONE
function CMD2 (
OF_PHYSICAL_ADDRESS : T_PHYSICAL_ADDRESS)
return T_STRING_80;
–– DESCRIPTION
–– This function returns the 2nd command string of
–– the specified physical address variable.
–– EXCEPTIONS
–– NONE
––––––––––––––––––––––
–– packing operations
––––––––––––––––––––––
procedure PACK (
PHYSICAL_ADDRESS : in T_PHYSICAL_ADDRESS;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
200 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
BLOCK : in out ADT_PACKING.T_BLOCK);
–– DESCRIPTION
–– This procedure packs the specified physical address variable into
–– a contiguous memory block.
–– EXCEPTIONS
–– NONE
procedure UNPACK (
BLOCK : in out ADT_PACKING.T_BLOCK;
PHYSICAL_ADDRESS : out T_PHYSICAL_ADDRESS);
–– DESCRIPTION
–– This procedure unpacks the specified memory block into
–– a physical address variable.
–– The variable must have been created before.
–– EXCEPTIONS
–– NONE
–––––––––––––––––––
–– exceptions
–––––––––––––––––––
STRING_LENGTH_ERROR
private
type T_PHYSICAL_ADDRESS is
record
: exception;
node_address : VICOS_DEFINITIONS.T_NAME_STRING
:= VICOS_DEFINITIONS.EMPTY_NAME_STRING;
bus_number : INTEGER := 0;
–– e.g. address on a bus
device_type : VICOS_DEFINITIONS.T_NAME_STRING
:= VICOS_DEFINITIONS.EMPTY_NAME_STRING;
device_address : VICOS_DEFINITIONS.T_NAME_STRING
:= VICOS_DEFINITIONS.EMPTY_NAME_STRING;
device_subaddress : VICOS_DEFINITIONS.T_NAME_STRING
:= VICOS_DEFINITIONS.EMPTY_NAME_STRING;
channel : INTEGER := 0;
function_code : INTEGER := 0;
protocol_id : INTEGER := 0;
command_1 : T_STRING_80
:= ((others => ’ ’),0);
–– any string value
command_2
end record;
: T_STRING_80
:= ((others => ’ ’),0);
–– any string value
–– The physical address of a measurement / stimuli / or ADU
for T_PHYSICAL_ADDRESS use
record
NODE_ADDRESS at 0 range 0 .. 191;
BUS_NUMBER at 24 range 0 .. 31;
DEVICE_TYPE at 28 range 0 .. 191;
DEVICE_ADDRESS at 52 range 0 .. 191;
DEVICE_SUBADDRESS at 76 range 0 .. 191;
CHANNEL at 100 range 0 .. 31;
FUNCTION_CODE at 104 range 0 .. 31;
PROTOCOL_ID at 108 range 0 .. 31;
COMMAND_1 at 112 range 0 .. 671;
COMMAND_2 at 196 range 0 .. 671;
end record;
for T_PHYSICAL_ADDRESS’size use 2240;
NULL_PHYSICAL_ADDRESS : constant T_PHYSICAL_ADDRESS :=
(node_address => VICOS_DEFINITIONS.EMPTY_NAME_STRING,
bus_number => 0,
device_type => VICOS_DEFINITIONS.EMPTY_NAME_STRING,
device_address => VICOS_DEFINITIONS.EMPTY_NAME_STRING,
device_subaddress => VICOS_DEFINITIONS.EMPTY_NAME_STRING,
channel => 0,
function_code => 0,
protocol_id => 0,
command_1 => ((others => ’ ’),0),
command_2 => ((others => ’ ’),0));
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
201 von/of: 662

Space Infrastructure
end ADT_PHYSICAL_ADDRESS;
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
202 von/of: 662

Space Infrastructure
7.3.4 ADT CCSDS Packet
Informal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
203 von/of: 662
A CCSDS Packet is the set of information describing the format of the data exchanged between ground and onboard
systems via operational links.
Currently, the definition of the Columbus Telemetry/Telecommand is still under discussion and is pending on
NASA / ESA interoperability meetings.
A precise description should be provided, in form of MDB end–items.
The current assumption of VICOS is that there are two types : a telemetry packet and a telecommand packet
which definition is based on CCSDS packet.
A CCSDS packet is a composite type containing the following attributes :
– a primary header containing :
– a packet id (= application id),
– a packet type,
– a version (fix),
– a secondary header flag (fix),
– a length.
– a sequence control field composed of :
– a sequence flags indicating segmentation,
– a sequence counter.
– a user data area containing :
– a data field header containing :
– a category/sub_category of packet,
– a checksum type,
– an acknowledge indication.
– user data :
– data may contain checksum at the
end (refer to utilisation std).
The checksum field is of 16 bit unsigned integer type. The checksum algorithm is a 16–bit add without carry
sum of the entire packet including primary and secondary headers exclusive of the checksum word itself.

Space Infrastructure
Formal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
––
–– ADT_CCSDS_PACKET
––
––****************************************************************************
––ABSTRACT––
––
–– Provides definition of CCSDS packets for the path service
–– (TM or TC packets).
–– Definition is based on:
–– CCSDS AOS, Blue Book CCSDS 701.0–B–2
–– and:
–– SSMB to APM ICD including IRN 41002–ES–0018E
––
––*–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––IDENTIFICATION––
–– PROJECT NAME : CGS
–– PRODUCT NAME : HCI
–– CI–NUMBER : 1216 878
–– OBJECT NAME : ADT_CCSDS_PACKET
––*–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
204 von/of: 662
––CONTENTS––
–– COMPILER : SunAda 1.1 / Alsys Ada 5.5.1
–– LANGUAGE : Ada
–– SPECIAL CONTENTS: –
–– CHANGE HISTORY
–– creator: P.Hartmann
–– creation date: 23.06.99
–– comment:
–– #IRN: COL–RIBRE–IRN–CGS–8064, Issue 1/–:
–– Add types and procedures to access header fields as normal
–– parameters
–– SPR–5864: Describe usage of Length field and checksum operation
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– creator: U. Hohnhorst RIO63
–– creation date: 18.06.98
–– comment:
–– #IRN: COL–RIBRE–IRN–CGS–8014, Issue 1/A:
–– 1) comment for checksum calculation (change implementation of
–– COMPUTED_CHECKSUM)
–– 2) type T_CCSDS_SECONDARY_HEADER spare bit added
–– 3) operations SET_SPARE_BIT, GET_SPARE_BIT added
–– 4) constants NULL_CCSDS_HEADER, NULL_CCSDS_SECONDARY_HEADER and
–– NULL_CCSDS_PACKET added
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– creator: U. Maron RIO63
–– creation date: 22.09.97
–– comment:
–– #IRN: COL–RIBRE–IRN–CGS–7023C: added support for DOUBLE_FLOAT
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– creator: Th. Kendelbacher RIO62
–– creation date: 02.06.97
–– comment:
–– #IRN: COL–RIBRE–IRN–CGS–7003: added [SECONDARY_]HEADER_FROM_BYTES

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
205 von/of: 662
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V16.2 at Central Repository at DASA RI
–– creator: hartmann (on host aiv_2)
–– creation date: 16.12.96 12:13:27
–– comment:
–– in operation GET_PARAMETER, change PARAMETER from –out– to –in out–
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V16.1 at Central Repository at DASA RI
–– creator: tommy (on host aiv_3)
–– creation date: 09.12.96 17:08:06
–– comment:
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V4.4 at CC; CGS development
–– creator: ahs (on host sde9)
–– creation date: 12.02.96 21:57:53
–– comment:
–– Patch from DASA + pack/unpack added by CC
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V4.7 at Central Repository at DASA RI (CGS V3 development)
–– creator: maron (on host vicos2–2)
–– creation date: 24.01.96 10:53:36
–– comment:
–– COL–RIBRE–IRN–3093: change Ada comments to reflect new checksum
–– algorithm and again include changes introduced by COL_RIBRE–SPR–2023
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V4.6 at Central Repository at DASA RI (CGS V3 development)
–– creator: grotheer (on host vicos2–6)
–– creation date: 15.01.96 14:41:29
–– comment: COL–RIBRE–CGS–SPR–2023, AT_OFFSET: NATURAL–>POSITIVE
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V3.2 at ERNO ; CGS engineering
–– creator: fritsch (on host ada_s)
–– creation date: 20.06.95 12:00:00
–– new constant CCSDS_SECONDARY_HEADER_SIZE
–– new functions (SECONDARY_)HEADER_BYTES, USER_DATA_LENGTH
–– Size clause in private declaration part added
–– Build 2 baseline PIRN 3046d
–– V3.1 at ERNO ; CGS engineering
–– creator: fritsch (on host ada_s)
–– creation date: 15.06.95 12:00:00
–– Build 2 baseline PIRN 3046c
–– V3.0 at ERNO ; CGS engineering
–– creator: maron (on host vicos2–2)
–– creation date: 17.05.95 16:00:00
–– Build 2 baseline PIRN 3046
–– V2.4 at ERNO ; VICOS development
–– creator: athmann (on host vicos_5)
–– creation date: 08.12.92 20:18:14
–– update comments / description
–– V2.3 at ERNO ; VICOS development
–– creator: vicos (on host vicos_s)
–– creation date: 17.11.92 11:27:50
–– adts version 2.0.1: update acc. to PIRN VICOS–2023
–– V2.2 at ERNO ; VICOS development

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–– creator: vicos (on host prime_1)
–– creation date: 18.09.92 11:58:12
–– modifications according to FINAL ICD REVIEW DNs (see list)
–– END HISTORY
––****************************************************************************
with NUMERIC_TYPES;
with ADT_PACKING;
package ADT_CCSDS_PACKET is
–––––––––––––––––––––––––––
–– ADT types and constants
–––––––––––––––––––––––––––
type T_CCSDS_HEADER is private;
type T_CCSDS_SECONDARY_HEADER is private;
type T_CCSDS_PACKET is private;
NULL_CCSDS_HEADER : constant T_CCSDS_HEADER;
NULL_CCSDS_SECONDARY_HEADER : constant T_CCSDS_SECONDARY_HEADER;
NULL_CCSDS_PACKET : constant T_CCSDS_PACKET;
type T_A_CCSDS_PACKET is access T_CCSDS_PACKET;
–––––––––––––––––––––––––––––
–– public types and constants
–––––––––––––––––––––––––––––
SPEC_VERSION : constant STRING := ”@(#) ADT_CCSDS_PACKET 4.1.1p.1 spec”;
CCSDS_HEADER_SIZE : constant INTEGER := 6;
CCSDS_SECONDARY_HEADER_SIZE : constant INTEGER := 10;
MAX_PACKET_SIZE : constant INTEGER := 4095;
–– maximum packet size excluding
–– the six header octets
–– (i.e. maximum value of the LENGTH item
–– in the primary header)
–– MUST BE AN ODD NUMBER
–– Note: The entire number of ccsds packet
–– octets is CCSDS_HEADER_SIZE
–– + MAX_PACKET_SIZE
–– + 1
MAX_PARAMETER_STRING : constant integer := 255;
subtype T_PARAMETER_STRING is STRING(1..MAX_PARAMETER_STRING);
type T_PACKET_PART is (DATA, PRIMARY_HEADER, SECONDARY_HEADER, CHECKSUM);
––––––––––––––––––––––––––––––––––––
–– Primary header items
––––––––––––––––––––––––––––––––––––
subtype T_CCSDS_VERSION is INTEGER range 0..7;
–– A three bit field
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
206 von/of: 662

Space Infrastructure
–– However, for COLUMBUS purposes only ”0” is allowed,
–– indication CCSDS version 1 packets
CCSDS_VERSION_1_PACKET : constant T_CCSDS_VERSION := 0;
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
subtype T_CCSDS_TYPE is INTEGER range 0..1;
–– A one bit field
–– For COLUMBUS purposes this shall be used for routing purposes,
–– however the field is not finally defined.
subtype T_CCSDS_SECONDARY_HEADER_FLAG is INTEGER range 0..1;
–– A one bit field
CCSDS_PACKET_HAS_SECONDARY_HEADER_FLAG :
constant T_CCSDS_SECONDARY_HEADER_FLAG := 1;
CCSDS_PACKET_HAS_NO_SECONDARY_HEADER_FLAG :
constant T_CCSDS_SECONDARY_HEADER_FLAG := 0;
subtype T_CCSDS_APPLICATION_ID is INTEGER range 0..2**11–1;
–– An 11 bit field
subtype T_CCSDS_SEQUENCE_FLAGS is INTEGER range 0..3;
–– A two bit field
–– For COLUMBUS purposes only ”3” will be allowed,
–– indicating an UNSEGMENTED packet
CCSDS_UNSEGMENTED_PACKET : constant T_CCSDS_SEQUENCE_FLAGS := 3;
subtype T_CCSDS_SEQUENCE_COUNT is INTEGER range 0..2**14–1;
–– A 14–bit field
subtype T_CCSDS_LENGTH is INTEGER range 0..MAX_PACKET_SIZE;
–– Originally a 16–bit field but restricted to the maximum length
–– allowed by the implementation of this package
HEADER_FIRST: constant INTEGER := 1;
HEADER_LAST: constant INTEGER := HEADER_FIRST + CCSDS_HEADER_SIZE – 1;
subtype T_HEADER_ARRAY is
NUMERIC_TYPES.BYTE_ARRAY (HEADER_FIRST .. HEADER_LAST);
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Secondary header items
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
subtype T_CCSDS_CHECKSUM_INDICATOR is INTEGER range 0..1;
–– A one bit field
CCSDS_PACKET_HAS_CHECKSUM : constant T_CCSDS_CHECKSUM_INDICATOR := 1;
CCSDS_PACKET_HAS_NO_CHECKSUM : constant T_CCSDS_CHECKSUM_INDICATOR := 0;
subtype T_CCSDS_TIME_ID is INTEGER range 0..3;
–– A two bit field
CCSDS_NO_TIME_FIELD : constant T_CCSDS_TIME_ID := 0;
CCSDS_REAL_TIME_COMMAND : constant T_CCSDS_TIME_ID := 1;
CCSDS_TIME_TAG : constant T_CCSDS_TIME_ID := 2;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
207 von/of: 662

Space Infrastructure
CCSDS_TIME_NOT_USED : constant T_CCSDS_TIME_ID := 3;
subtype T_CCSDS_PACKET_TYPE is INTEGER range 0..15;
–– A four bit field
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
CCSDS_DEFAULT_PACKET : constant T_CCSDS_PACKET_TYPE := 0;
CCSDS_MEMORY_DUMP_PACKET : constant T_CCSDS_PACKET_TYPE := 1;
CCSDS_DATA_SEGMENT_PACKET : constant T_CCSDS_PACKET_TYPE := 2;
CCSDS_ESSENTIAL_HK_PACKET : constant T_CCSDS_PACKET_TYPE := 3;
CCSDS_SYSTEM_HK_PACKET : constant T_CCSDS_PACKET_TYPE := 4;
CCSDS_PAYLOAD_HK_PACKET : constant T_CCSDS_PACKET_TYPE := 5;
CCSDS_SCIENCE_PACKET : constant T_CCSDS_PACKET_TYPE := 6;
CCSDS_SSMB_ANCILLIARY_PACKET : constant T_CCSDS_PACKET_TYPE := 7;
CCSDS_ESSENTIAL_COMMAND_PACKET : constant T_CCSDS_PACKET_TYPE := 8;
CCSDS_SYSTEM_COMMAND_PACKET : constant T_CCSDS_PACKET_TYPE := 9;
CCSDS_PAYLOAD_COMMAND_PACKET : constant T_CCSDS_PACKET_TYPE := 10;
CCSDS_MEMORY_LOAD_PACKET : constant T_CCSDS_PACKET_TYPE := 11;
CCSDS_RESPONSE_PACKET : constant T_CCSDS_PACKET_TYPE := 12;
CCSDS_REPORT_PACKET : constant T_CCSDS_PACKET_TYPE := 13;
CCSDS_EXCEPTION_PACKET : constant T_CCSDS_PACKET_TYPE := 14;
CCSDS_ACKNOWLEDGE_PACKET : constant T_CCSDS_PACKET_TYPE := 15;
subtype T_CCSDS_PACKET_ID is NUMERIC_TYPES.UNSIGNED_INTEGER32;
subtype T_CCSDS_COARSE_TIME is NUMERIC_TYPES.UNSIGNED_INTEGER32;
subtype T_CCSDS_FINE_TIME is INTEGER range 0..2**8–1;
type T_CCSDS_UNSEGMENTED_TIME is record
COARSE_TIME : T_CCSDS_COARSE_TIME;
FINE_TIME : T_CCSDS_FINE_TIME;
end record;
subtype T_CCSDS_CHECKSUM is INTEGER range 0..2**16–1;
–– A 16 bit field
–– Checksums are computed using the CRC16 polynomial
–– applied to the CCSDS packet:
–– x**16 + x**15 + x**2 + 1
–– since version 4.9: 16 bit add without carry
SECOND_HEADER_FIRST: constant INTEGER := HEADER_LAST + 1;
SECOND_HEADER_LAST: constant INTEGER := SECOND_HEADER_FIRST
+ CCSDS_SECONDARY_HEADER_SIZE – 1;
subtype T_SECONDARY_HEADER_ARRAY is
NUMERIC_TYPES.BYTE_ARRAY (SECOND_HEADER_FIRST .. SECOND_HEADER_LAST);
–––––––––––––––––––––––––––
–– Clear operations
–––––––––––––––––––––––––––
procedure CLEAR (PACKET: in out T_CCSDS_PACKET);
–– DESCRIPTION
–– Clears a packet, all octets are set to zero
–– Note that this does not result in a valid packet!!
–– EXCEPTIONS
–– none
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
208 von/of: 662

Space Infrastructure
––––––––––––––––––––––––––––––––––––––––––
–– Write Operations for the primary header
––––––––––––––––––––––––––––––––––––––––––
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
209 von/of: 662
procedure SET_VERSION (PACKET : in out T_CCSDS_HEADER;
TO : in T_CCSDS_VERSION := CCSDS_VERSION_1_PACKET);
–– DESCRIPTION
–– sets the packet version
–– EXCEPTIONS
–– none
procedure SET_TYPE (PACKET : in out T_CCSDS_HEADER;
TO : in T_CCSDS_TYPE);
–– DESCRIPTION
–– sets the packet type
–– EXCEPTIONS
–– none
procedure SET_SECONDARY_HEADER_FLAG
(PACKET : in out T_CCSDS_HEADER;
TO : in T_CCSDS_SECONDARY_HEADER_FLAG
:= CCSDS_PACKET_HAS_SECONDARY_HEADER_FLAG);
–– DESCRIPTION
–– sets the secondary header flag
–– EXCEPTIONS
–– none
procedure SET_APPLICATION_ID (PACKET : in out T_CCSDS_HEADER;
TO : in T_CCSDS_APPLICATION_ID);
–– DESCRIPTION
–– sets the application id in the primary header
–– EXCEPTIONS
–– none
procedure SET_SEQUENCE_FLAGS (PACKET : in out T_CCSDS_HEADER;
TO : in T_CCSDS_SEQUENCE_FLAGS
:= CCSDS_UNSEGMENTED_PACKET);
–– DESCRIPTION
–– sets the packet sequence flags in the primary header
–– EXCEPTIONS
–– none
procedure SET_SEQUENCE_COUNT (PACKET : in out T_CCSDS_HEADER;
TO : in T_CCSDS_SEQUENCE_COUNT);
–– DESCRIPTION
–– sets the packet sequence count in the primary header
–– EXCEPTIONS
–– none
procedure SET_LENGTH (PACKET : in out T_CCSDS_HEADER;
TO : in T_CCSDS_LENGTH);
–– DESCRIPTION
–– Sets the length field in the primary header of the packet.
–– The length field is really a byte count for the
–– user data field, starting with 0 (i.e. the number of bytes minus one).
–– Note: The user data field includes the secondary header (if present),
–– the user data and the checksum (if present).
–– EXCEPTIONS
–– none

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
procedure HEADER_FROM_BYTES (BYTES : in NUMERIC_TYPES.BYTE_ARRAY;
PACKET : out T_CCSDS_HEADER);
–– DESCRIPTION
–– converts the representation bytes into a primary header
–– EXCEPTIONS
–– CONSTRAINT_ERROR if BYTES is smaller than the primary header length
–––––––––––––––––––––––––––––––––––––––––
–– read operations primary header
–––––––––––––––––––––––––––––––––––––––––
function VERSION (PACKET: T_CCSDS_HEADER) return T_CCSDS_VERSION;
–– DESCRIPTION
–– returns the CCSDS version of the packet
–– EXCEPTIONS
–– none
function CCSDS_TYPE ( PACKET: T_CCSDS_HEADER) return T_CCSDS_TYPE;
–– DESCRIPTION
–– returns the type of the packet as defined in the primary header
–– EXCEPTIONS
–– none
function CCSDS_SECONDARY_HEADER_FLAG (PACKET: T_CCSDS_HEADER)
return T_CCSDS_SECONDARY_HEADER_FLAG;
–– DESCRIPTION
–– returns the secondary header flag of the packet
–– as defined in the primary header
–– EXCEPTIONS
–– none
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
210 von/of: 662
function APPLICATION_ID (PACKET: T_CCSDS_HEADER)
return T_CCSDS_APPLICATION_ID;
–– DESCRIPTION
–– returns the application id of the packet as defined in the primary header
–– EXCEPTIONS
–– none
function SEQUENCE_FLAGS (PACKET: T_CCSDS_HEADER)
return T_CCSDS_SEQUENCE_FLAGS;
–– DESCRIPTION
–– returns the packet sequence count of the packet
–– as defined in the primary header
–– EXCEPTIONS
–– none
function SEQUENCE_COUNT (PACKET: T_CCSDS_HEADER)
return T_CCSDS_SEQUENCE_COUNT;
–– DESCRIPTION
–– returns the packet sequence count of the packet
–– as defined in the primary header
–– EXCEPTIONS
–– none
function LENGTH (PACKET: T_CCSDS_HEADER) return T_CCSDS_LENGTH;
–– DESCRIPTION
–– returns the length field of the packet as defined in the primary header
–– EXCEPTIONS
–– none

Space Infrastructure
function HEADER_BYTES (PACKET: T_CCSDS_HEADER)
return NUMERIC_TYPES.BYTE_ARRAY;
–– DESCRIPTION
–– returns the representation of the primary header
–– EXCEPTIONS
–– CONSTRAINT_ERROR if
–––––––––––––––––––––––––––––––––––––––––
–– write operations secondary header
–––––––––––––––––––––––––––––––––––––––––
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
211 von/of: 662
procedure SET_CHECKSUM_INDICATOR (PACKET : in out T_CCSDS_SECONDARY_HEADER;
TO : in T_CCSDS_CHECKSUM_INDICATOR
:= CCSDS_PACKET_HAS_NO_CHECKSUM);
–– DESCRIPTION
–– sets the checksum_type in the secondary header
–– EXCEPTIONS
–– none
procedure SET_TIME_ID (PACKET : in out T_CCSDS_SECONDARY_HEADER;
TO : in T_CCSDS_TIME_ID := CCSDS_NO_TIME_FIELD);
–– DESCRIPTION
–– sets the time_id in the secondary header
–– EXCEPTIONS
–– none
procedure SET_PACKET_TYPE (PACKET : in out T_CCSDS_SECONDARY_HEADER;
TO : in T_CCSDS_PACKET_TYPE
:= CCSDS_DEFAULT_PACKET);
–– DESCRIPTION
–– sets the packet type in the secondary header
–– EXCEPTIONS
–– none
procedure SET_PACKET_ID (PACKET : in out T_CCSDS_SECONDARY_HEADER;
TO : in T_CCSDS_PACKET_ID);
–– DESCRIPTION
–– sets the packet id in the secondary header
–– EXCEPTIONS
–– none
procedure SET_SPARE_BIT (PACKET : in out T_CCSDS_SECONDARY_HEADER;
TO : in NUMERIC_TYPES.BIT := 0);
–– DESCRIPTION
–– sets the spare bit in the secondary header
–– EXCEPTIONS
–– none
procedure SET_TIME (PACKET : in out T_CCSDS_SECONDARY_HEADER;
TO : in T_CCSDS_UNSEGMENTED_TIME);
–– DESCRIPTION
–– sets the packet id in the secondary header
–– EXCEPTIONS
–– INVALID_TIME_ID
–– the secondary header time id is wrong
procedure SECONDARY_HEADER_FROM_BYTES
(BYTES : in NUMERIC_TYPES.BYTE_ARRAY;

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
PACKET : out T_CCSDS_SECONDARY_HEADER);
–– DESCRIPTION
–– converts the representation bytes into a secondary header
–– EXCEPTIONS
–– CONSTRAINT_ERROR if BYTES is smaller than the secondary header length
–––––––––––––––––––––––––––––––––––––––––
–– read operations secondary header
–––––––––––––––––––––––––––––––––––––––––
function CHECKSUM_INDICATOR (PACKET: T_CCSDS_SECONDARY_HEADER)
return T_CCSDS_CHECKSUM_INDICATOR;
–– DESCRIPTION
–– returns the checksum indicator from the secondary header
–– EXCEPTIONS
–– none
function TIME_ID (PACKET: T_CCSDS_SECONDARY_HEADER) return T_CCSDS_TIME_ID;
–– DESCRIPTION
–– returns the time id from the secondary header
–– EXCEPTIONS
–– none
function PACKET_TYPE (PACKET: T_CCSDS_SECONDARY_HEADER)
return T_CCSDS_PACKET_TYPE;
–– DESCRIPTION
–– returns the packet type from the secondary header
–– EXCEPTIONS
–– none
function PACKET_ID (PACKET: T_CCSDS_SECONDARY_HEADER)
return T_CCSDS_PACKET_ID;
–– DESCRIPTION
–– returns the packet ID from the secondary header
–– EXCEPTIONS
–– none
function SPARE_BIT (PACKET: T_CCSDS_SECONDARY_HEADER)
return NUMERIC_TYPES.BIT;
–– DESCRIPTION
–– returns the spare bit from the secondary header
–– EXCEPTIONS
–– none
function PACKET_TIME (PACKET: T_CCSDS_SECONDARY_HEADER)
return T_CCSDS_UNSEGMENTED_TIME;
–– DESCRIPTION
–– returns the time field from the secondary header
–– EXCEPTIONS
–– INVALID_TIME_ID
–– the secondary header time id is wrong
function SECONDARY_HEADER_BYTES (PACKET: T_CCSDS_SECONDARY_HEADER)
return NUMERIC_TYPES.BYTE_ARRAY;
–– DESCRIPTION
–– returns the representation of the secondary header
–– EXCEPTIONS
–– none
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
212 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– write operations to assemble a packet
–– Note : Packets must be assembled in the following order:
–– The CCSDS primary header,
–– the CCSDS secondary header (if present),
–– the length field in the primary header, if not done in first step
–– the user data,
–– the checksum (if present).
––
–– The length field in the primary header must be set
–– before the checksum is written to avoid placement of
–– the checksum at the wrong place
––––––––––––––––––––––––––––––––––––––––––––––––––––––
procedure SET_HEADER (PACKET : in out T_CCSDS_PACKET;
TO : in T_CCSDS_HEADER);
–– DESCRIPTION
–– sets the primary header
–– EXCEPTIONS
–– none
procedure SET_SECONDARY_HEADER (PACKET : in out T_CCSDS_PACKET;
TO : in T_CCSDS_SECONDARY_HEADER);
–– DESCRIPTION
–– sets the secondary header
–– EXCEPTIONS
–– NO_SECONDARY_HEADER
–– the primary header indicates that there
–– should be no secondary header
procedure SET_DATA (PACKET : in out T_CCSDS_PACKET;
TO : in NUMERIC_TYPES.BYTE_ARRAY);
–– DESCRIPTION
–– Sets the user data to the predefined static pattern
–– defined in MDB.
–– The length of the user data is constrained by the length field
–– in the primary header.
–– EXCEPTIONS
–– INVALID_SIZE
–– if the byte array is too big for the packet
procedure SUBSTITUTE_PARAMETER
(PACKET : in out T_CCSDS_PACKET;
AT_OFFSET : in POSITIVE;
TO_VALUE : in NUMERIC_TYPES.BIT);
procedure SUBSTITUTE_PARAMETER
(PACKET : in out T_CCSDS_PACKET;
AT_OFFSET : in POSITIVE;
NUMBER_OF_BITS : in NATURAL;
TO_VALUE : in NUMERIC_TYPES.BITSET);
procedure SUBSTITUTE_PARAMETER
(PACKET : in out T_CCSDS_PACKET;
AT_OFFSET : in POSITIVE;
TO_VALUE : in CHARACTER);
procedure SUBSTITUTE_PARAMETER
(PACKET : in out T_CCSDS_PACKET;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
213 von/of: 662

Space Infrastructure
AT_OFFSET : in POSITIVE;
NUMBER_OF_BITS : in NATURAL;
TO_VALUE : in NUMERIC_TYPES.INTEGER32);
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
procedure SUBSTITUTE_PARAMETER
(PACKET : in out T_CCSDS_PACKET;
AT_OFFSET : in POSITIVE;
NUMBER_OF_BITS : in NATURAL;
TO_VALUE : in NUMERIC_TYPES.UNSIGNED_INTEGER32);
procedure SUBSTITUTE_PARAMETER
(PACKET : in out T_CCSDS_PACKET;
AT_OFFSET : in POSITIVE;
TO_VALUE : in NUMERIC_TYPES.SINGLE_FLOAT);
procedure SUBSTITUTE_PARAMETER
(PACKET : in out T_CCSDS_PACKET;
AT_OFFSET : in POSITIVE;
TO_VALUE : in NUMERIC_TYPES.DOUBLE_FLOAT);
procedure SUBSTITUTE_PARAMETER
(PACKET : in out T_CCSDS_PACKET;
AT_OFFSET : in POSITIVE;
NUMBER_OF_BYTES : in NATURAL;
TO_VALUE : in NUMERIC_TYPES.BYTE_ARRAY);
–– DESCRIPTION
–– Takes TO_VALUE and substitutes the bits starting at
–– AT_OFFSET in the PACKET.
–– Note: AT_OFFSET counts the bits in the user data, starting with 1.
–– EXCEPTIONS
–– INVALID_SIZE
–– raised if the substitution of the value exceeds the length
–– of the packet
–– or for integer and unsigned integer if the actual value does
–– not fit into the NUMBER_OF_BITS
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
214 von/of: 662
function COMPUTED_CHECKSUM (PACKET: T_CCSDS_PACKET) return T_CCSDS_CHECKSUM;
–– DESCRIPTION
–– computes the checksum of the packet.
–– The checksum algorithm is a 16–bit add without carry sum of the entire packet
–– including primary and secondary headers exclusive of the checksum word itself.
–– EXCEPTIONS
–– none
procedure SET_CHECKSUM (PACKET : in out T_CCSDS_PACKET;
TO : in T_CCSDS_CHECKSUM);
–– DESCRIPTION
–– sets the checksum at the end of a paket
–– EXCEPTIONS
–– NO_CHECKSUM
–– in the secondary header no checksum is defined
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– read operations to get the packet contents
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––
function HEADER (PACKET: T_CCSDS_PACKET) return T_CCSDS_HEADER;

Space Infrastructure
–– DESCRIPTION
–– returns the primary header
–– EXCEPTIONS
–– none
function SECONDARY_HEADER (PACKET: T_CCSDS_PACKET)
return T_CCSDS_SECONDARY_HEADER;
–– DESCRIPTION
–– returns the secondary header
–– EXCEPTIONS
–– NO_SECONDARY_HEADER
–– the primary header indicates that there
–– is no secondary header
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
function USER_DATA (PACKET: T_CCSDS_PACKET) return NUMERIC_TYPES.BYTE_ARRAY;
–– DESCRIPTION
–– returns the user data (excluding secondary header and checksum)
–– from a packet
–– EXCEPTIONS
–– none
function USER_DATA_LENGTH (PACKET: T_CCSDS_PACKET) return T_CCSDS_LENGTH;
–– DESCRIPTION
–– returns the length of the user data (excluding secondary header and
–– checksum) from a packet
–– EXCEPTIONS
–– none
function CHECKSUM (PACKET: T_CCSDS_PACKET) return T_CCSDS_CHECKSUM;
–– DESCRIPTION
–– returns the checksum from a packet
–– EXCEPTIONS
–– NO_CHECKSUM
–– in the secondary header no checksum is defined
function PARAMETER (PACKET : T_CCSDS_PACKET;
AT_OFFSET : POSITIVE;
PACKET_PART : T_PACKET_PART
:= ADT_CCSDS_PACKET.DATA)
return NUMERIC_TYPES.BIT;
function PARAMETER (PACKET : T_CCSDS_PACKET;
AT_OFFSET : POSITIVE;
PACKET_PART : T_PACKET_PART
:= ADT_CCSDS_PACKET.DATA)
return CHARACTER;
function PARAMETER (PACKET : T_CCSDS_PACKET;
AT_OFFSET : POSITIVE;
NUMBER_OF_BITS : NATURAL;
PACKET_PART : T_PACKET_PART
:= ADT_CCSDS_PACKET.DATA)
return NUMERIC_TYPES.BITSET;
function PARAMETER (PACKET : T_CCSDS_PACKET;
AT_OFFSET : POSITIVE;
NUMBER_OF_BITS : NATURAL;
PACKET_PART : T_PACKET_PART
:= ADT_CCSDS_PACKET.DATA)
return NUMERIC_TYPES.INTEGER32;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
215 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
function PARAMETER (PACKET : T_CCSDS_PACKET;
AT_OFFSET : POSITIVE;
NUMBER_OF_BITS : NATURAL;
PACKET_PART : T_PACKET_PART
:= ADT_CCSDS_PACKET.DATA)
return NUMERIC_TYPES.UNSIGNED_INTEGER32;
function PARAMETER (PACKET : T_CCSDS_PACKET;
AT_OFFSET : POSITIVE;
PACKET_PART : T_PACKET_PART
:= ADT_CCSDS_PACKET.DATA)
return NUMERIC_TYPES.SINGLE_FLOAT;
function PARAMETER (PACKET : T_CCSDS_PACKET;
AT_OFFSET : POSITIVE;
PACKET_PART : T_PACKET_PART
:= ADT_CCSDS_PACKET.DATA)
return NUMERIC_TYPES.DOUBLE_FLOAT;
function PARAMETER (PACKET : T_CCSDS_PACKET;
AT_OFFSET : POSITIVE;
NUMBER_OF_BYTES: NATURAL;
PACKET_PART : T_PACKET_PART
:= ADT_CCSDS_PACKET.DATA)
return NUMERIC_TYPES.BYTE_ARRAY;
–– DESCRIPTION
–– These overloaded functions retrieve a value from a CCSDS packet
–– AT_OFFSET with the given NUMBER_OF_BITS or NUMBER_OF_BYTES.
–– Note: AT_OFFSET counts the bits in the PACKET_PART, starting with 1.
–– EXCEPTIONS
–– DATA_LENGTH_ERROR:
–– raised if the retrieval of the value exceeds the length
–– of the packet
–– using functions returning types that do not fit in a register (>32 bits)
–– causes heap access, use these equivalent procedures for speed
procedure GET_PARAMETER (PACKET : in T_CCSDS_PACKET;
AT_OFFSET : in POSITIVE;
NUMBER_OF_BYTES : in NATURAL;
PARAMETER : in out T_PARAMETER_STRING;
PACKET_PART : in T_PACKET_PART
:= ADT_CCSDS_PACKET.DATA);
–– DESCRIPTION
–– Retrieve a parameter string value from a CCSDS packet
–– AT_OFFSET with the given NUMBER_OF_BYTES.
–– Note: AT_OFFSET counts the bits in the PACKET_PART, starting with 1.
–– EXCEPTIONS
–– DATA_LENGTH_ERROR:
–– raised if the retrieval of the value exceeds the length
–– of the packet
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– operation to put a whole CCSDS packet into an ADT variable or to
–– retreive a CCSDS packet from an ADT variable into a byte array
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
216 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
procedure SET_WHOLE_PACKET (PACKET : out T_CCSDS_PACKET;
EXTERNAL_PACKET : in NUMERIC_TYPES.BYTE_ARRAY;
EXTERNAL_SIZE : in NATURAL);
–– DESCRIPTION
–– This procedure puts a byte array (containing a CCSDS packet)
–– into the ADT variable. The size of the packet (overall) in
–– bytes is given in parameter EXTERNAL_SIZE
–– EXCEPTIONS
–– INVALID_SIZE
–– The size does not fit (either to big or internally inconsistent)
procedure GET_WHOLE_PACKET (PACKET : in T_CCSDS_PACKET;
EXTERNAL_PACKET : out NUMERIC_TYPES.BYTE_ARRAY;
EXTERNAL_SIZE : out NATURAL);
–– DESCRIPTION
–– This procedure returns a byte array (containing a CCSDS packet)
–– from the ADT variable into a user provided byte array.
–– The size of the packet (overall) in bytes is provided in parameter
–– EXTERNAL_SIZE
–– EXCEPTIONS
–– DATA_LENGTH_ERROR
–– The buffer provided by the user is too small
procedure DEALLOCATE (PACKET : in out T_A_CCSDS_PACKET);
–– DESCRIPTION
–– free memory allocated by new(T_CCSDS_PACKET)
–– EXCEPTIONS
procedure PACK (PACKET : in T_CCSDS_PACKET;
BLOCK : in out ADT_PACKING.T_BLOCK);
–– DESCRIPTION
–– pack the CCSDS_PACKET into a T_BLOCK
–– only used data is packed i.e. the length field of the primary header
–– is used to determine that packed size
–– convert to machine independent format where applicable
–– EXCEPTIONS
procedure UNPACK (BLOCK : in out ADT_PACKING.T_BLOCK;
PACKET : in out T_CCSDS_PACKET);
–– DESCRIPTION
–– unpack the CCSDS from a T_BLOCK
–– convert from machine independent format where applicable
–– EXCEPTIONS
–––––––––––––––––––––––––––––––––––––
–– exceptions
–––––––––––––––––––––––––––––––––––––
NO_SECONDARY_HEADER: exception;
INVALID_TIME_ID: exception;
INVALID_SIZE: exception;
NO_CHECKSUM: exception;
DATA_LENGTH_ERROR: exception;
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
private
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
217 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
type T_CCSDS_HEADER is
record
VERSION : T_CCSDS_VERSION := CCSDS_VERSION_1_PACKET;
PTYPE : T_CCSDS_TYPE := 0;
H2FLAG : T_CCSDS_SECONDARY_HEADER_FLAG
:= CCSDS_PACKET_HAS_NO_SECONDARY_HEADER_FLAG;
APID : T_CCSDS_APPLICATION_ID := 0;
SEQFLAG : T_CCSDS_SEQUENCE_FLAGS := CCSDS_UNSEGMENTED_PACKET;
SEQCNT : T_CCSDS_SEQUENCE_COUNT := 0;
LENGTH : T_CCSDS_LENGTH := 0;
end record;
for T_CCSDS_HEADER use
record
VERSION at 0 range 0..2;
PTYPE at 0 range 3..3;
H2FLAG at 0 range 4..4;
APID at 0 range 5..15;
SEQFLAG at 2 range 0..1;
SEQCNT at 2 range 2..15;
LENGTH at 4 range 0..15;
end record;
for T_CCSDS_HEADER’SIZE use 6 * 8;
NULL_CCSDS_HEADER : constant T_CCSDS_HEADER
:= (VERSION => CCSDS_VERSION_1_PACKET,
PTYPE => 0,
H2FLAG => CCSDS_PACKET_HAS_NO_SECONDARY_HEADER_FLAG,
APID => 0,
SEQFLAG => CCSDS_UNSEGMENTED_PACKET,
SEQCNT => 0,
LENGTH => 0);
type T_CCSDS_SECONDARY_HEADER is
record
COARSE_TIME : T_CCSDS_COARSE_TIME := 0;
FINE_TIME : T_CCSDS_FINE_TIME := 0;
TIME_ID : T_CCSDS_TIME_ID := CCSDS_NO_TIME_FIELD;
CS_IND : T_CCSDS_CHECKSUM_INDICATOR := CCSDS_PACKET_HAS_NO_CHECKSUM;
SPARE : NUMERIC_TYPES.BIT := 0;
PACK_TYPE : T_CCSDS_PACKET_TYPE := CCSDS_DEFAULT_PACKET;
PACK_ID : T_CCSDS_PACKET_ID := 0;
end record;
for T_CCSDS_SECONDARY_HEADER use
record
COARSE_TIME at 0 range 0..31;
FINE_TIME at 4 range 0..7;
TIME_ID at 5 range 0..1;
CS_IND at 5 range 2..2;
SPARE at 5 range 3..3;
PACK_TYPE at 5 range 4..7;
PACK_ID at 6 range 0..31;
end record;
for T_CCSDS_SECONDARY_HEADER’SIZE use 10 * 8;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
218 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
NULL_CCSDS_SECONDARY_HEADER : constant T_CCSDS_SECONDARY_HEADER
:= (COARSE_TIME => 0,
FINE_TIME => 0,
TIME_ID => CCSDS_NO_TIME_FIELD,
CS_IND => CCSDS_PACKET_HAS_NO_CHECKSUM,
SPARE => 0,
PACK_TYPE => CCSDS_DEFAULT_PACKET,
PACK_ID => 0);
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
219 von/of: 662
type T_CCSDS_PACKET is
new NUMERIC_TYPES.BYTE_ARRAY (1 .. MAX_PACKET_SIZE + 1 + CCSDS_HEADER_SIZE);
NULL_CCSDS_PACKET : constant T_CCSDS_PACKET := (others => 0);
end ADT_CCSDS_PACKET;

Space Infrastructure
7.3.5 Binary Buffer ADT
Informal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
220 von/of: 662
The package ADT_BINARY_BUFFER has been introduced to make conversion between hexadecimal/raw values
and binary values in a safe and uniformed way.
A binary buffer is composed of :
– a length (in bytes),
– a data buffer which can be written/read as :
– raw values stored at a certain location (in bits) with a certain length (in bits) according
to a certain interpretation type;
– hexadecimal values stored at a certain location (in bits) with a certain length (in bits);
– binary values stored at a certain location (in bits).
The following conventions have been adopted :
– the least significant bit is the first on the right in a bit pattern,
– the most significant bit is the first on the left in a bit pattern,
– the bits are numbered from 1 to N*8 in a binary buffer of length n bytes, starting the numeration
with the first bit on the left,
– a value located at position P and with length L in a binary buffer means that the equivalent
bit pattern representing this value starts at bit Pth and finishes at bit (P+L–1) th ,
– in a binary buffer, unused bits are set to 0,
– a single_bit value has a 1bit long bit pattern and can be positioned at any position in the binary
buffer, the value of the single_bit (0 or 1) is simply copied in that bit,
– a bit_set value has a 1 up to 32 bits long bit pattern and can be positioned at any position in
the binary buffer where this bit pattern fits, the value of the bit_set (a list of 0 and 1) is simply
copied in that bit pattern,
– a 1s complement 12 bits integer value has a 12 bits long bit pattern and can be positioned
at any position in the binary buffer where this bit pattern fits, the value of the 1s complement
12 bits integer is converted into a binary value following the 1s complement representation,
e.g. ’2’ is encoded ’000000000010’ and ’–2’ is encoded ’111111111101,
– a 2s complement 12 bits integer value has a 12 bits long bit pattern and can be positioned
at any position in the binary buffer where this bit pattern fits, the value of the 2s complement
12 bits integer is converted into a binary value following the 2s complement representation,
e.g. ’2’ is encoded ’000000000010’ and ’–2’ is encoded ’111111111110
– a 1s complement 16 bits integer value has a 16 bits long bit pattern and can be positioned
at any position in the binary buffer where this bit pattern fits, the value of the 1s complement
16 bits integer is converted into a binary value following the 1s complement representation,
– a 2s complement 16 bits integer value has a 16 bits long bit pattern and can be positioned
at any position in the binary buffer where this bit pattern fits, the value of the 2s comple-

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
221 von/of: 662
ment 16 bits integer is converted into a binary value following the 2s complement representation,
– a 1s complement 32 bits integer value has a 32 bits long bit pattern and can be positioned
at any position in the binary buffer where this bit pattern fits, the value of the 1s complement
32 bits integer is converted into a binary value following the 1s complement representation,
– a 2s complement 32 bits integer value has a 32 bits long bit pattern and can be positioned
at any position in the binary buffer where this bit pattern fits, the value of the 2s complement
32 bits integer is converted into a binary value following the 2s complement representation,
– a float value has a 32 bits long bit pattern and can be positioned at any position in the binary
buffer where this bit pattern fits, the value of the float is converted into a binary value
following the IEEE standard for normalized single–precision–floating–point numbers,
– a byte_stream value has a 1 up to 256 bytes long bit pattern and can be positioned at any
position where this bit pattern fits, the value of the byte_stream (a list of 0 and 1) is simply
copied in that bit pattern,
– a hexadecimal value has a 1 up to 512 nibbles (half byte) long bit pattern and can be positioned
at any position where this bit pattern fits, the value of the hexadecimal number is
converted into a binary value following the standard binary representation, e.g. ’FF’ is encoded
’11111111’.

Space Infrastructure
Formal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
222 von/of: 662
––
–– ADT_BINARY_BUFFER spec
––
––****************************************************************************
––ABSTRACT
––
–– This ADT allows conversion of hexadecimal and raw values into
–– binary buffer and vice versa
––
––*–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––IDENTIFICATION––
–– PROJECT NAME : COLUMBUS VICOS
–– PRODUCT NAME : VCS
–– CI–NUMBER : 1234950
–– OBJECT NAME : ADT_BINARY_BUFFER
––*–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––CONTENTS––
–– COMPILER : SUN/Verdix Ada
–– LANGUAGE : Ada
–– SPECIAL CONTENTS: –
–– CHANGE HISTORY
––
–– #IRN 8069/B: modify comments of SUBSTITUTE_PARAMETER operations.
–– Author: P.Hartmann
–– Date: 22.06.99
––
–– #IRN 6020/B: change function PARAMETER into procedure GET_PARAMETER
–– for BYTE_ARRAY parameter and update comments.
–– Author: P.Hartmann
–– Date: 09.04.97
––
–– #IRN 6020: Add new services to store and retrieve parameter (values)
–– Author: P.Athmann
–– Date: 14.2.97
––
–– V2.3 at ERNO ; VICOS development
–– creator: grotheer (on host vicos_s)
–– creation date: 19.01.94 15:57:43
–– AT_LOCATION aligned with database (first bit=0)
––
–– V2.2 at ERNO ; VICOS development
–– creator: grotheer (on host vicos_s)
–– creation date: 24.09.93 10:38:52
–– initial version, header added
––
––****************************************************************************
with NUMERIC_TYPES;
with STATIC_STRINGS;
with ADT_RAW_VALUE;
package ADT_BINARY_BUFFER is
––––––––––––––––––––––––––––––

Space Infrastructure
–– public types and constants
––––––––––––––––––––––––––––––
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
package STATIC_STRINGS512 is new STATIC_STRINGS(512);
type T_HEXA_STRING is new STATIC_STRINGS512.STATIC_STRING;
––––––––––––––––––––
–– write operations
––––––––––––––––––––
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
223 von/of: 662
procedure SET_RAW_VALUE (
IN_BUFFER : in out NUMERIC_TYPES.BYTE_ARRAY;
WITH_RAW_VALUE : in ADT_RAW_VALUE.T_RAW_VALUE;
AT_LOCATION : in NATURAL;
WITH_LENGTH : in POSITIVE);
–– DESCRIPTION
–– This procedure sets the specified raw value in the
–– specified binary buffer at the specified location (0..n bits)
–– with the specified length (in bits). The length is specified by
–– the size of the value itself or by WITH_LENGTH (for bitsets and
integer).
–– EXCEPTIONS
–– VALUE_TYPE_MISMATCH :
–– The type of the specified raw value is not set
–– LENGTH_MISMATCH :
–– Bit location + value length exceeds the buffer size.
–– or if the length is greater than the raw value (case BYTE_STREAM)
–– or for integer and unsigned integer if the actual value does
–– not fit into the NUMBER_OF_BITS
procedure SET_HEXA_VALUE (
IN_BUFFER : in out NUMERIC_TYPES.BYTE_ARRAY;
WITH_HEXA_VALUE : in T_HEXA_STRING;
AT_LOCATION : in NATURAL;
WITH_LENGTH : in POSITIVE);
–– DESCRIPTION
–– This procedure sets the specified hexadecimal value ( text string )
–– in the specified binary buffer at the specified location (0..n bits)
–– with the specified length (in bits). Leading zeros of the hexa–
–– decimal string value are suppressed, but the specified length may
–– add leading zeros. That means: the hexadecimal string ”03” sets only
–– 2 bits (if the specified length is 2), but a given ”3” with the
–– specified length of 8 inserts the bits 00000011.
–– EXCEPTIONS
–– LENGTH_MISMATCH :
–– The specified length is not compatible with the specified
–– hexadecimal value, or the size of the binary buffer is too small.
–– VALUE_TYPE_MISMATCH :
–– The specified string is not an hexadecimal value.
–– The hexadecimal value shall be a string of the characters 0..9,
–– A..F with no blanks in between (blanks may be on either side).
procedure SET_BINARY_BUFFER (
IN_BUFFER : in out NUMERIC_TYPES.BYTE_ARRAY;
WITH_BINARY_BUFFER : in NUMERIC_TYPES.BYTE_ARRAY;
AT_LOCATION : in NATURAL);

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
224 von/of: 662
–– DESCRIPTION
–– This procedure sets the binary buffer specified as second
–– parameter into the binary buffer specified as first parameter
–– at the specified location (0..n bits). Byte alignment of the
–– specified location is not required.
–– EXCEPTIONS
–– LENGTH_MISMATCH :
–– The passed binary buffer, at the specified location, does not
–– fit into the binary buffer specified as first parameter.
procedure SUBSTITUTE_PARAMETER(
IN_BUFFER : in out NUMERIC_TYPES.BYTE_ARRAY;
AT_OFFSET : POSITIVE;
TO_VALUE : NUMERIC_TYPES.BIT);
procedure SUBSTITUTE_PARAMETER(
IN_BUFFER : in out NUMERIC_TYPES.BYTE_ARRAY;
AT_OFFSET : POSITIVE;
NUMBER_OF_BITS : NATURAL;
TO_VALUE : NUMERIC_TYPES.BITSET);
procedure SUBSTITUTE_PARAMETER(
IN_BUFFER : in out NUMERIC_TYPES.BYTE_ARRAY;
AT_OFFSET : POSITIVE;
TO_VALUE : CHARACTER);
procedure SUBSTITUTE_PARAMETER(
IN_BUFFER : in out NUMERIC_TYPES.BYTE_ARRAY;
AT_OFFSET : POSITIVE;
NUMBER_OF_BITS : NATURAL;
TO_VALUE : NUMERIC_TYPES.INTEGER32);
procedure SUBSTITUTE_PARAMETER(
IN_BUFFER : in out NUMERIC_TYPES.BYTE_ARRAY;
AT_OFFSET : POSITIVE;
NUMBER_OF_BITS : NATURAL;
TO_VALUE : NUMERIC_TYPES.UNSIGNED_INTEGER32);
procedure SUBSTITUTE_PARAMETER(
IN_BUFFER : in out NUMERIC_TYPES.BYTE_ARRAY;
AT_OFFSET : POSITIVE;
TO_VALUE : NUMERIC_TYPES.SINGLE_FLOAT);
procedure SUBSTITUTE_PARAMETER(
IN_BUFFER : in out NUMERIC_TYPES.BYTE_ARRAY;
AT_OFFSET : POSITIVE;
TO_VALUE : NUMERIC_TYPES.DOUBLE_FLOAT);
procedure SUBSTITUTE_PARAMETER(
IN_BUFFER : in out NUMERIC_TYPES.BYTE_ARRAY;
AT_OFFSET : POSITIVE;
NUMBER_OF_BYTES : NATURAL;
TO_VALUE : NUMERIC_TYPES.BYTE_ARRAY);
––DESCRIPTION
––Takes TO_VALUE and substitutes the bits starting at
––AT_OFFSET in the IN_BUFFER.
––AT_OFFSET is the offset to the beginning of the buffer,
–– counted in bits, starting with 1
––EXCEPTIONS
––LENGTH_MISMATCH
––raised if the offset + the length of the value is
––exceeding the length of the IN_BUFFER
––or if the length is greater than TO_VALUE (case BYTE_STREAM)
––or for integer and unsigned integer if the actual value does
––not fit into the NUMBER_OF_BITS

Space Infrastructure
–––––––––––––––––––
–– read operations
–––––––––––––––––––
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
function BUFFER_SIZE (
OF_BUFFER : NUMERIC_TYPES.BYTE_ARRAY)
return INTEGER;
–– DESCRIPTION
–– This function returns the size of the specified
–– binary buffer (in bytes).
–– EXCEPTIONS
–– None.
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
225 von/of: 662
procedure GET_RAW_VALUE (
FROM_BUFFER : in NUMERIC_TYPES.BYTE_ARRAY;
RAW_VALUE : in out ADT_RAW_VALUE.T_RAW_VALUE;
AT_LOCATION : in NATURAL;
WITH_LENGTH : in POSITIVE);
–– DESCRIPTION
–– This procedure returns a raw value out of the
–– specified binary buffer at the specified location (0..n bits)
–– with the specified length (in bits). The length is specified by
–– the size of the value itself or by WITH_LENGTH ( for bitsets and
–– byte streams and integer ).
–– Note that the type of the raw value variable has to be set
–– EXCEPTIONS
–– VALUE_TYPE_MISMATCH :
–– The type of the specified raw value is not set
–– LENGTH_MISMATCH :
–– 1. Bit location + value length exceeds the buffer size
–– 2. WITH_LENGTH exceeds the maximum size of a bitset or stream value
–– 3. WITH_LENGTH is not a multiple of 8 for byte stream values
function HEXA_VALUE (
FROM_BUFFER : NUMERIC_TYPES.BYTE_ARRAY;
AT_LOCATION : NATURAL;
WITH_LENGTH : POSITIVE)
return T_HEXA_STRING;
–– DESCRIPTION
–– This function returns the hexadecimal value stored in the
–– specified binary buffer at the specified location (0..n bits)
–– with the specified length (in bits). The hexadecimal string
–– is returned with a minimum of characters ( no leading zeros,
–– no hex–ID like 16#00# or 0x00, all bits 0’s = a single ”0” )
–– EXCEPTIONS
–– LENGTH_MISMATCH :
–– The area defined by the location and length is exceeding
–– the size of the binary buffer or the extracted hexadecimal value
–– exceeds the maximum no. of characters of the return value.
function BINARY_BUFFER (
FROM_BUFFER : NUMERIC_TYPES.BYTE_ARRAY;
AT_LOCATION : NATURAL;
WITH_LENGTH : POSITIVE)
return NUMERIC_TYPES.BYTE_ARRAY;
–– DESCRIPTION
–– This function returns a binary buffer stored at the
–– specified position out of the binary buffer specified

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
226 von/of: 662
–– as first parameter. Byte alignment of the specified
–– location is not required.
–– Note: A CONSTRAINT_ERROR will be raised at the level of the
–– calling program, if the specified length is not excactly
–– 8*(size of return buffer). The validity of WITH_LENGTH can’t
–– be checked in this function.
–– EXCEPTIONS
–– LENGTH_MISMATCH :
–– The area defined by the location and length is exceeding
–– the size of the binary buffer or the specified length is not
–– a multiple of 8 ( byte alignment for destination buffer ).
function PARAMETER(
FROM_BUFFER : NUMERIC_TYPES.BYTE_ARRAY;
AT_OFFSET : POSITIVE)
return NUMERIC_TYPES.BIT;
function PARAMETER(
FROM_BUFFER : NUMERIC_TYPES.BYTE_ARRAY;
AT_OFFSET : POSITIVE)
return CHARACTER;
function PARAMETER(
FROM_BUFFER : NUMERIC_TYPES.BYTE_ARRAY;
AT_OFFSET : POSITIVE;
NUMBER_OF_BITS : NATURAL)
return NUMERIC_TYPES.BITSET;
function PARAMETER(
FROM_BUFFER : NUMERIC_TYPES.BYTE_ARRAY;
AT_OFFSET : POSITIVE;
NUMBER_OF_BITS : NATURAL)
return NUMERIC_TYPES.INTEGER32;
function PARAMETER(
FROM_BUFFER : NUMERIC_TYPES.BYTE_ARRAY;
AT_OFFSET : POSITIVE;
NUMBER_OF_BITS : NATURAL)
return NUMERIC_TYPES.UNSIGNED_INTEGER32;
function PARAMETER(
FROM_BUFFER : NUMERIC_TYPES.BYTE_ARRAY;
AT_OFFSET : POSITIVE)
return NUMERIC_TYPES.SINGLE_FLOAT;
function PARAMETER(
FROM_BUFFER : NUMERIC_TYPES.BYTE_ARRAY;
AT_OFFSET : POSITIVE)
return NUMERIC_TYPES.DOUBLE_FLOAT;
procedure GET_PARAMETER(
FROM_BUFFER : in NUMERIC_TYPES.BYTE_ARRAY;
AT_OFFSET : in POSITIVE;
NUMBER_OF_BYTES : in NATURAL;
BYTE_ARRAY : in out NUMERIC_TYPES.BYTE_ARRAY);
––DESCRIPTION
––These overloaded functions retrieve a value from the buffer
––AT_OFFSET with the given NUMBER_OF_BITS or NUMBER_OF_BYTES.
––Note: AT_OFFSET counts the bits in the buffer, starting with 1.
––EXCEPTIONS
––LENGTH_MISMATCH:
––raised if the offset + the length of the value is
––exceeding the length of the buffer
––or if the length is exceeding the length of the BYTE_STREAM (procedure
––GET_PARAMETER)
–––––––––––––––––––––

Space Infrastructure
–– Exceptions
–––––––––––––––––––––
BUFFER_IS_CONSTRAINED : exception;
LENGTH_MISMATCH : exception;
VALUE_TYPE_MISMATCH : exception;
end ADT_BINARY_BUFFER;
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
227 von/of: 662

Space Infrastructure
7.4 Calibration
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
228 von/of: 662
Please note that this package is not allowed outside CGS by other Products than CMAS !!!
Informal Interface Description
The package calibration provides types to contain calibration and decalibration descriptions as well as procedures
to calibrate and decalibrate values based on these descriptions. Four types of (de)calibration mechanisms
are defined :
– conversion of analog values with a polynom (defined by coefficients);
– conversion of analog values with a curve defined by point pairs;
– conversion of discrete values into state codes, with an association table;
– conversion of byte stream values into strings, by extraction of substreams.
A Calibration Description is a composite type containing the following attributes :
– a calibration alternative,
– a list of coefficients, if the calibration is of type polynom,
– a point pairs curve description, if the calibration is of type point pairs, composed of :
– a point pair list size,
– a list of point pairs, composed of :
– a raw value point;
– a calibrated value point;
– an association table when the calibration alternative is DISCRETE, where each element is composed
of :
– a raw value,
– a corresponding state code value.
– an extraction description, if the calibration is of type string extraction, composed of :
– a position (expressed as a number of characters) in the byte stream where
the extraction has to begin,
– a length (expressed as a number of characters) corresponding to the
number of successive characters which have to be extracted from the raw
byte stream.
The calibration description has packing and unpacking operations for machine independent internal representation
and to support inter process communication.
Also, a procedure is provided to internal represent a point pair (de)calibration curve more efficient so that the
(de)calibration of data is performed quicker

Space Infrastructure
Formal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
––
–– CALIBRATION spec
––
––****************************************************************************
––ABSTRACT––
–– This package provides an abstract data type for the description of
–– how enditem data is to be converted between raw and engineering
–– values plus the procedures to do the transformation.
–– The following operations for calibration and decalibration are provided:
–– 1.) calibration: conversion of raw values –> engineering values
–– (described by point_pairs)
–– 2.) decalibration: conversion of engineering values –> raw values
–– (described by point_pairs)
–– 3.) calibration: conversion of raw values –> engineering values
–– (described by a polynominal curves)
–– 4.) decalibration: conversion of engineering values –> raw values
–– (described by a polynominal curves)
–– 5.) calibration: conversion of Integer32 –> State_Code
–– (described by discrete point pairs)
–– 6.) decalibration: conversion of State_Code –> Integer32
–– (described by discrete point pairs)
–– 7.) calibration: conversion of Dynamic_String –> Dynamic_String
–– (”substrings” argument)
–– 8.) calibration: conversion of BIT/INTEGER32 –> BOOLEAN
–– 9.) decalibration: conversion of BOOLEAN –> BIT/INTEGER32
––10.) calibration: conversion of raw values –> engineering values
–– (described by a identical mapping)
––11.) decalibration: conversion of engineering values –> raw values
–– (described by a identical mapping)
–– The package is a combination of the former VCS packages
–– ADT_CALIBRATION_DESCRIPTION and CALIBRATE. However, since this
–– version is now intended for use in the CSS product also, the data
–– types of raw and enmgineering values have been changed from
–– ADT_RAW_VALUE / ADT_ENGINEERING_VALUE to types provided by
–– NUMERIC_TYPES. Also, the exceptions have been streamlined.
––*–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––IDENTIFICATION––
–– PROJECT NAME : CGS
–– PRODUCT NAME : HCI
–– CI–NUMBER : 1216878
–– OBJECT NAME : VICOS_ADTS
––*–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
229 von/of: 662
––CONTENTS––
–– LANGUAGE : Ada
–– SPECIAL CONTENTS:
–– CHANGE HISTORY
–– V16.1 at Central Repository at DASA RI
–– creator: tommy (on host aiv_tn2)
–– creation date: 09.12.96 16:56:44
–– comment:
––
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V4.7 at Central Repository at DASA RI (CGS V3 development)
–– creator: cssproma (on host ada_s)
–– creation date: 09.01.96 16:40:03
–– comment:
–– –– introduced new functions, see PIRN COL–RIBRE–IRN–CGS–3091
–– –– adapted comments and body code, see SPR COL–RIBRE–SPR–CGS–2051

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
230 von/of: 662
––
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V4.6 at Central Repository at DASA RI (CGS V3 development)
–– creator: A.Schulz
–– creation date: 08.01.96
–– comment:
–– introduced new functions, see PIRN COL–RIBRE–IRN–CGS–3091
–– adapted comments and body code, see SPR COL–RIBRE–SPR–CGS–2051
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V4.5 at Central Repository at DASA RI (CGS V3 development)
–– creator: css_test (on host csf_1)
–– creation date: 19.12.95 09:01:11
–– comment:
–– introduced new functions, see PIRN COL–RIBRE–IRN–CGS–3091
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V4.4 at Central Repository at DASA RI (CGS V3 development)
–– creator: css_test (on host csf_1)
–– creation date: 31.08.95 16:50:52
–– comment:
–– PIRN COL–RIBRE–IRN–CGS–3032 1/H
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V4.3 at Central Repository at DASA RI (CGS V3 development)
–– creator: css_test (on host csf_1)
–– creation date: 31.08.95
–– comment:
–– new baseline according to PIRN COL–RIBRE–IRN–CGS–3032 1/H
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V4.2 at Central Repository at DASA RI (CGS V3 development)
–– creator: athmann (on host vicos_5)
–– creation date: 02.06.95 18:32:03
–– comment:
–– Constant UNDEFINED_MAPPING changed to NULL_CALIBRATION_DECALIBRATION
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V4.2 at Central Repository at DASA RI (CGS V3 development)
–– creator: css_test (on host csf_1)
–– creation date: 02.06.95 13:31:06
–– comment:
–– new baseline according to PIRN COL–RIBRE–IRN–CGS–3032 1/F
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V1.0 at Central Repository V4 (CGS build2 development)
–– creator: gehrke (on host mps2s–1)
–– creation date: 16.05.95 11:00:00
–– comment:
–– COL_RIBRE–IRN–3032/E
–– END HISTORY
––****************************************************************************
––
with MPS_DEFINITIONS;
with NUMERIC_TYPES;
with ADT_PACKING;
package CALIBRATION is
–––––––––––––––––––
–– Exceptions
–––––––––––––––––––

Space Infrastructure
––––– due to invalid runtime data –––––––––––––––––––––––
–– raised for invalid input data to (de–)calibrated:
VALUE_OUT_OF_RANGE: exception;
––––– due to invalid configuration data resp. usage –––––
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–– raised by SET_xxx_(DE–)CALIBRATION when SW types are invalid
–– for calibration alternative:
ARGUMENT_ERROR: exception;
–– raised by (DE–)CALIBRATED when calibration description was defined
–– for other direction
ILLEGAL_MAPPING_KIND: exception;
–– raised when input calibration description is incomplete
–– or parameters for SET_xx_(DE)CALIBRATION are invalid:
ILLEGAL_CALIB_DECALIB_DEFINITION: exception;
–– raised by INVERT when inversion is impossible:
NOT_INVERTABLE: exception;
–– raised when description alternative or SW type
–– is illegal for current operation:
CALIBRATION_TYPE_MISMATCH: exception;
–––––––––––––––––––––––––––––––––––––––––––––––––
–– Constants
–––––––––––––––––––––––––––––––––––––––––––––––––
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
231 von/of: 662
MAX_POLYNOM_COEFFICIENTS : constant integer := 5;
MAX_POINT_PAIRS : constant integer := 20;
MAX_STATE_CODES : constant integer := 32;
–– kept for compatibility
MAX_BYTESTREAM : constant integer := MPS_DEFINITION-
S.MAX_RAW_STRING_LENGTH;
–––––––––––––––––––
–– Types
–––––––––––––––––––
type MAPPING_KIND is (CALIBRATION, DECALIBRATION);
type CALIBRATION_ALTERNATIVES is (
UNDEFINED,
POLYNOM,
POINT_PAIRS,
DISCRETE,
BOOLEAN_CAL,
SUBSTRING,
CONSTANT_CAL);
–– The calibration alternative indicates how calibration shall be done:
–– – the curve is a polynom,
–– – the curve is a point pairs curve,
–– – a discrete association table is used,
–– – string extraction is used,
–– – default mapping used dependant on type of engineering and raw value
subtype POLYNOM_INDEX is integer range 0 .. MAX_POLYNOM_COEFFICIENTS – 1;
subtype ANALOG_POINT_PAIR_INDEX is integer range 1 .. MAX_POINT_PAIRS;
subtype DISCRETE_POINT_PAIR_INDEX is integer range 1 .. MAX_STATE_CODES;
subtype BYTESTREAM_INDEX is integer range 1 .. MAX_BYTESTREAM;

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
type POLYNOM_COEFFICIENTS is array ( POLYNOM_INDEX ) of
NUMERIC_TYPES.DOUBLE_FLOAT;
type ANALOG_POINT_PAIR is record
RAW_POINT : NUMERIC_TYPES.DOUBLE_FLOAT;
CAL_POINT : NUMERIC_TYPES.DOUBLE_FLOAT;
end record;
type ANALOG_POINT_PAIR_ARRAY is array (
ANALOG_POINT_PAIR_INDEX range ) of ANALOG_POINT_PAIR;
type DISCRETE_POINT_PAIR is record
DISCRETE_VALUE : NUMERIC_TYPES.INTEGER32;
STATECODE_VALUE : MPS_DEFINITIONS.STATE_CODE;
end record;
type DISCRETE_POINT_PAIR_ARRAY is array (
DISCRETE_POINT_PAIR_INDEX range ) of DISCRETE_POINT_PAIR;
type CALIBRATION_DECALIBRATION_TYPE is private;
–– The private type which describes how calibration as well as decalibration
–– shall be done. In favor of brevity, no separate decalibration type is
–– provided since anyhow all internals of calibration/decalibration are
–– the same.
NULL_CALIBRATION_DECALIBRATION:
constant CALIBRATION_DECALIBRATION_TYPE;
–––––––––––––––––––––––––––––––––––––––––––––––
–– write operations
–––––––––––––––––––––––––––––––––––––––––––––––
procedure SET_CONSTANT_CALIBRATION (
OF_CAL_DESCR: in out CALIBRATION_DECALIBRATION_TYPE;
RAW_VALUE_DESCRIPTOR: in MPS_DEFINITIONS.T_SW_TYPE_DESCRIPTOR;
ENG_VALUE_DESCRIPTOR: in MPS_DEFINITIONS.T_SW_TYPE_DESCRIPTOR);
–– DESCRIPTION
–– This procedure sets an identical calibration for all raw and engineering
–– values of type integer, unsigned_integer32, real and long_real :
–– calibrated value = raw value
–– The calibration alternative is set to CONSTANT_CAL internally
–– Also, the allowed ranges for the engineering and raw values as well
–– as their type are set from the input value descriptors.
–– Note that the parameters of type ”MPS_DEFINITIONS.T_SW_TYPE_DESCRIPTOR”
–– contains a component called ”engineering_unit”, which is not used here.
–– EXCEPTIONS:
–– ARGUMENT_ERROR: raised, if
–– – raw or engineering type is not legal for constant calibration
–– ILLEGAL_CALIB_DECALIB_DEFINITION: raised, if
–– – raw or engineering range is empty (first>=last)
procedure SET_POLYNOM_CALIBRATION (
OF_CAL_DESCR: in out CALIBRATION_DECALIBRATION_TYPE;
COEFFICIENTS: in POLYNOM_COEFFICIENTS;
RAW_VALUE_DESCRIPTOR: in MPS_DEFINITIONS.T_SW_TYPE_DESCRIPTOR;
ENG_VALUE_DESCRIPTOR: in MPS_DEFINITIONS.T_SW_TYPE_DESCRIPTOR);
–– DESCRIPTION
–– This procedure sets the polynom calibration coefficients of
–– the specified calibration description for all raw and engineering
–– values of type integer, unsigned_integer32, real and long_real.
–– The calibration alternative is set to POLYNOM internally
–– Also, the allowed ranges for the engineering and raw values as well
–– as their type are set from the input value descriptors.
–– Note that the parameters of type ”MPS_DEFINITIONS.T_SW_TYPE_DESCRIPTOR”
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
232 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–– contains a component called ”engineering_unit”, which is not used here.
–– EXCEPTIONS
–– ARGUMENT_ERROR: raised, if
–– – raw or engineering type is not legal for polynom calibration
–– ILLEGAL_CALIB_DECALIB_DEFINITION: raised, if
–– – raw or engineering range is empty (first>=last)
procedure SET_POINT_PAIR_CALIBRATION (
OF_CAL_DESCR: in out CALIBRATION_DECALIBRATION_TYPE;
POINT_PAIRS: in ANALOG_POINT_PAIR_ARRAY;
RAW_VALUE_DESCRIPTOR: in MPS_DEFINITIONS.T_SW_TYPE_DESCRIPTOR;
ENG_VALUE_DESCRIPTOR: in MPS_DEFINITIONS.T_SW_TYPE_DESCRIPTOR);
–– DESCRIPTION
–– This procedure sets the analog calibration point pairs of
–– the specified calibration description for all raw and engineering
–– values of type integer, unsigned_integer32, real and long_real.
–– The calibration alternative is set to POINT_PAIRS internally
–– Also, the allowed ranges for the engineering and raw values as well
–– as their type are set from the input value descriptors.
–– Note that the parameters of type ”MPS_DEFINITIONS.T_SW_TYPE_DESCRIPTOR”
–– contains a component called ”engineering_unit”, which is not used here.
–– EXCEPTIONS
–– ARGUMENT_ERROR: raised, if
–– – raw or engineering type is not legal for point pair calibration
–– ILLEGAL_CALIB_DECALIB_DEFINITION: raised, if
–– – raw or engineering range is empty (first>=last)
–– – less than 2 or more than MAX_POINT_PAIRS point pairs provided
–– – two adjacent raw or engineering values are identical
–– VALUE_OUT_OF_RANGE: raised, if
–– – any raw or engineering value is out of range
procedure SET_DISCRETE_CALIBRATION (
OF_CAL_DESCR: in out CALIBRATION_DECALIBRATION_TYPE;
POINT_PAIRS: in DISCRETE_POINT_PAIR_ARRAY;
RAW_VALUE_TYPE: in MPS_DEFINITIONS.T_SW_TYPE);
–– DESCRIPTION
–– This procedure sets the discrete calibration point pairs of
–– the specified calibration description for all raw values
–– of type integer and unsigned_integer32.
–– Note that the first entry within the list of state_codes denotes
–– the value which will be returned by the calibration operations
–– in case no valid state_code is found.
–– Internally, the following actions are performed automatically:
–– => the calibration alternative is set to DISCRETE
–– => the raw value descriptor is set dependant
–– on the RAW_VALUE_TYPE:
–– SW_TYPE := RAW_VALUE_TYPE
–– with range: SW_TYPE’FIRST..SW_TYPE’LAST
–– => the engineering value descriptor is set to
–– SW_TYPE := STATE_CODE_TYPE
–– STATE_CODE_LIST:=
–– EXCEPTIONS
–– ARGUMENT_ERROR: raised, if
–– – raw type is not legal for discrete calibration
–– ILLEGAL_CALIB_DECALIB_DEFINITION: raised, if
–– – less than 2 or more than MAX_STATE_CODES point pairs provided
–– – two raw values are identical
procedure SET_BOOLEAN_CALIBRATION (
OF_CAL_DESCR: in out CALIBRATION_DECALIBRATION_TYPE;
BY_TRUE: in NUMERIC_TYPES.BIT;
BY_FALSE: in NUMERIC_TYPES.BIT);
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
233 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–– DESCRIPTION
–– This procedure sets the bit–to–boolean mapping for calibration of
–– the specified calibration description.
–– Internally, the following actions are performed automatically:
–– => the calibration alternative is set to BOOLEAN_CAL
–– => the raw value descriptor is set to
–– SW_TYPE := INTEGER_TYPE
–– with range: 0..1
–– => the engineering value descriptor is set to
–– SW_TYPE := BOOLEAN_TYPE
–– EXCEPTIONS
–– ILLEGAL_CALIB_DECALIB_DEFINITION: raised, if
–– – BY_TRUE and BY_FALSE are identical
procedure SET_BOOLEAN_CALIBRATION (
OF_CAL_DESCR: in out CALIBRATION_DECALIBRATION_TYPE;
BY_TRUE: in NUMERIC_TYPES.INTEGER32;
BY_FALSE: in NUMERIC_TYPES.INTEGER32);
–– DESCRIPTION
–– This procedure sets the integer32–to–boolean mapping for calibration of
–– the specified calibration description.
–– Internally, the following actions are performed automatically:
–– => the calibration alternative is set to BOOLEAN_CAL
–– => the raw value descriptor is set to
–– SW_TYPE := INTEGER_TYPE
–– with range: 0..2GB
–– => the engineering value descriptor is set to
–– SW_TYPE := BOOLEAN_TYPE
–– EXCEPTIONS
–– ILLEGAL_CALIB_DECALIB_DEFINITION: raised, if
–– – BY_TRUE and BY_FALSE are identical
procedure SET_BYTESTREAM_CALIBRATION (
OF_CAL_DESCR: in out CALIBRATION_DECALIBRATION_TYPE;
START_POINT: in BYTESTREAM_INDEX;
SUBSTRING_LENGTH: in BYTESTREAM_INDEX);
–– DESCRIPTION
–– This procedure sets the substring start point and length values of
–– the specified calibration description.
–– Internally, the following actions are performed automatically:
–– => the calibration alternative is set to SUBSTRING
–– => the raw value descriptor is set to
–– SW_TYPE := STRING_TYPE
–– with STRING_SIZE: START_POINT + SUBSTRING_LENGTH – 1
–– (minimum length required for calibration)
–– => the engineering value descriptor is set to
–– SW_TYPE := STRING_TYPE
–– with STRING_SIZE: SUBSTRING_LENGTH
–– EXCEPTIONS
–– ILLEGAL_CALIB_DECALIB_DEFINITION: raised, if
–– – START_POINT + SUBSTRING_LENGTH – 1 > MAX_BYTESTREAM
procedure SET_CONSTANT_DECALIBRATION (
OF_CAL_DESCR: in out CALIBRATION_DECALIBRATION_TYPE;
RAW_VALUE_DESCRIPTOR: in MPS_DEFINITIONS.T_SW_TYPE_DESCRIPTOR;
ENG_VALUE_DESCRIPTOR: in MPS_DEFINITIONS.T_SW_TYPE_DESCRIPTOR);
–– DESCRIPTION
–– This procedure sets an identical decalibration for all raw and engineering
–– values of type integer, unsigned_integer32, real and long_real :
–– calibrated value = raw value
–– The calibration alternative is set to CONSTANT_CAL internally
–– Also, the allowed ranges for the engineering and raw values as well
–– as their type are set from the input value descriptors.
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
234 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–– Note that the parameters of type ”MPS_DEFINITIONS.T_SW_TYPE_DESCRIPTOR”
–– contains a component called ”engineering_unit”, which is not used here.
–– EXCEPTIONS:
–– ARGUMENT_ERROR: raised, if
–– – raw or engineering type is not legal for constant calibration
–– ILLEGAL_CALIB_DECALIB_DEFINITION: raised, if
–– – raw or engineering range is empty (first>=last)
procedure SET_POLYNOM_DECALIBRATION (
OF_CAL_DESCR: in out CALIBRATION_DECALIBRATION_TYPE;
COEFFICIENTS: in POLYNOM_COEFFICIENTS;
RAW_VALUE_DESCRIPTOR: in MPS_DEFINITIONS.T_SW_TYPE_DESCRIPTOR;
ENG_VALUE_DESCRIPTOR: in MPS_DEFINITIONS.T_SW_TYPE_DESCRIPTOR);
–– DESCRIPTION
–– This procedure sets the polynom decalibration coefficients of
–– the specified calibration description for all raw and engineering
–– values of type integer, unsigned_integer32, real and long_real.
–– The calibration alternative is set to POLYNOM internally
–– Also, the allowed ranges for the engineering and raw values as well
–– as their type are set from the input value descriptors.
–– Note that the parameters of type ”MPS_DEFINITIONS.T_SW_TYPE_DESCRIPTOR”
–– contains a component called ”engineering_unit”, which is not used here.
–– EXCEPTIONS
–– ARGUMENT_ERROR: raised, if
–– – raw or engineering type is not legal for polynom calibration
–– ILLEGAL_CALIB_DECALIB_DEFINITION: raised, if
–– – raw or engineering range is empty (first>=last)
procedure SET_POINT_PAIR_DECALIBRATION (
OF_CAL_DESCR: in out CALIBRATION_DECALIBRATION_TYPE;
POINT_PAIRS: in ANALOG_POINT_PAIR_ARRAY;
RAW_VALUE_DESCRIPTOR: in MPS_DEFINITIONS.T_SW_TYPE_DESCRIPTOR;
ENG_VALUE_DESCRIPTOR: in MPS_DEFINITIONS.T_SW_TYPE_DESCRIPTOR);
–– DESCRIPTION
–– This procedure sets the analog decalibration point pairs of
–– the specified calibration description for all raw and engineering
–– values of type integer, unsigned_integer32, real and long_real.
–– The calibration alternative is set to POINT_PAIRS internally
–– Also, the allowed ranges for the engineering and raw values as well
–– as their type are set from the input value descriptors.
–– Note that the parameters of type ”MPS_DEFINITIONS.T_SW_TYPE_DESCRIPTOR”
–– contains a component called ”engineering_unit”, which is not used here.
–– EXCEPTIONS
–– ARGUMENT_ERROR: raised, if
–– – raw or engineering type is not legal for point pair calibration
–– ILLEGAL_CALIB_DECALIB_DEFINITION: raised, if
–– – raw or engineering range is empty (first>=last)
–– – less than 2 or more than MAX_POINT_PAIRS point pairs provided
–– – two adjacent raw or engineering values are identical
–– VALUE_OUT_OF_RANGE: raised, if
–– – any raw or engineering value is out of range
procedure SET_DISCRETE_DECALIBRATION (
OF_CAL_DESCR: in out CALIBRATION_DECALIBRATION_TYPE;
POINT_PAIRS: in DISCRETE_POINT_PAIR_ARRAY;
RAW_VALUE_TYPE: in MPS_DEFINITIONS.T_SW_TYPE);
–– DESCRIPTION
–– This procedure sets the discrete decalibration point pairs of
–– the specified calibration description for all raw values
–– of type integer and unsigned_integer32.
–– Internally, the following actions are performed automatically:
–– => the calibration alternative is set to DISCRETE
–– => the raw value descriptor is set dependant
–– on the RAW_VALUE_TYPE:
–– SW_TYPE := RAW_VALUE_TYPE
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
235 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–– with range: SW_TYPE’FIRST..SW_TYPE’LAST
–– => the engineering value descriptor is set to
–– SW_TYPE := STATE_CODE_TYPE
–– STATE_CODE_LIST:=
–– EXCEPTIONS
–– ARGUMENT_ERROR: raised, if
–– – raw type is not legal for discrete calibration
–– ILLEGAL_CALIB_DECALIB_DEFINITION: raised, if
–– – less than 2 or more than MAX_STATE_CODES point pairs provided
–– – two state code values are identical
procedure SET_BOOLEAN_DECALIBRATION (
OF_CAL_DESCR: in out CALIBRATION_DECALIBRATION_TYPE;
BY_TRUE: in NUMERIC_TYPES.BIT;
BY_FALSE: in NUMERIC_TYPES.BIT);
–– DESCRIPTION
–– This procedure sets the bit–to–boolean mapping for decalibration of
–– the specified calibration description.
–– Internally, the following actions are performed automatically:
–– => the calibration alternative is set to BOOLEAN_CAL
–– => the raw value descriptor is set to
–– SW_TYPE := INTEGER_TYPE
–– with range: 0..1
–– => the engineering value descriptor is set to
–– SW_TYPE := BOOLEAN_TYPE
–– EXCEPTIONS
–– ILLEGAL_CALIB_DECALIB_DEFINITION: raised, if
–– – BY_TRUE and BY_FALSE are identical
procedure SET_BOOLEAN_DECALIBRATION (
OF_CAL_DESCR: in out CALIBRATION_DECALIBRATION_TYPE;
BY_TRUE: in NUMERIC_TYPES.INTEGER32;
BY_FALSE: in NUMERIC_TYPES.INTEGER32);
–– DESCRIPTION
–– This procedure sets the integer32–to–boolean mapping for decalibration of
–– the specified calibration description.
–– Internally, the following actions are performed automatically:
–– => the calibration alternative is set to BOOLEAN_CAL
–– => the raw value descriptor is set to
–– SW_TYPE := INTEGER_TYPE
–– with range: 0..2GB
–– => the engineering value descriptor is set to
–– SW_TYPE := BOOLEAN_TYPE
–– EXCEPTIONS
–– ILLEGAL_CALIB_DECALIB_DEFINITION: raised, if
–– – BY_TRUE and BY_FALSE are identical
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
236 von/of: 662
procedure DEALLOCATE_CALIB(GARBAGE: in out CALIBRATION_DECALIBRATION_TYPE);
–– DESCRIPTION
–– This procedure removes a previously defined calibration/decalibration description
–– completely.
–– EXCEPTIONS
–– none
––––––––––––––––––––––––––––––––––––––––––––––
–– read operations for calibration attributes
––––––––––––––––––––––––––––––––––––––––––––––
function GET_CALIBRATION_ALTERNATIVE (
OF_CAL_DESCR: CALIBRATION_DECALIBRATION_TYPE)
return CALIBRATION_ALTERNATIVES;
–– DESCRIPTION
–– This function returns the calibration alternative of the
–– specified (de)calibration description; UNDEFINED when empty.
–– When in doubt, call this procedure first to make sure that

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–– OF_CAL_DESCR has been defined. All other GET_xxx will raise
–– an exception when OF_CAL_DESCR is empty.
–– EXCEPTIONS
–– None.
function GET_MAPPING_KIND (
OF_CAL_DESCR: in CALIBRATION_DECALIBRATION_TYPE)
return MAPPING_KIND;
–– DESCRIPTION
–– This function returns the mapping kind of the specified (de)calibration
–– description, i.e. whether the provided description may be used for
–– calibration or decalibration
–– EXCEPTIONS
–– ILLEGAL_CALIB_DECALIB_DEFINITION: raised if
–– – the (de)calibration description is empty/undefined.
function GET_RAW_VALUE_DESCRIPTOR (
OF_CAL_DESCR: in CALIBRATION_DECALIBRATION_TYPE)
return MPS_DEFINITIONS.T_SW_TYPE_DESCRIPTOR;
–– DESCRIPTION
–– This function returns the raw value descriptor of the
–– specified (de)calibration description containing the type and ranges
–– EXCEPTIONS
–– ILLEGAL_CALIB_DECALIB_DEFINITION: raised if
–– – the (de)calibration description is empty/undefined.
–– – the raw value descriptor is empty/undefined.
function GET_ENG_VALUE_DESCRIPTOR (
OF_CAL_DESCR: in CALIBRATION_DECALIBRATION_TYPE)
return MPS_DEFINITIONS.T_SW_TYPE_DESCRIPTOR;
–– DESCRIPTION
–– This function returns the engineering value descriptor of the
–– specified (de)calibration description containing the type and ranges
–– EXCEPTIONS
–– ILLEGAL_CALIB_DECALIB_DEFINITION: raised if
–– – the (de)calibration description is empty/undefined.
–– – the engineering value descriptor is empty/undefined.
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
237 von/of: 662
function GET_POLYNOM_COEFFICIENTS (
OF_CAL_DESCR: in CALIBRATION_DECALIBRATION_TYPE)
return POLYNOM_COEFFICIENTS;
–– DESCRIPTION
–– This function returns the polynom coefficients of the
–– specified (de)calibration description.
–– EXCEPTIONS
–– CALIBRATION_TYPE_MISMATCH: raised if
–– – the calibration alternative of the specified description is not POLYNOM.
–– ILLEGAL_CALIB_DECALIB_DEFINITION: raised if
–– – the coefficients array is empty/undefined.
–– – the (de)calibration description is empty/undefined.
function GET_ANALOG_POINT_PAIRS (
OF_CAL_DESCR: in CALIBRATION_DECALIBRATION_TYPE)
return ANALOG_POINT_PAIR_ARRAY;
–– DESCRIPTION
–– This function returns the polynom coefficients of the
–– specified (de)calibration description.
–– EXCEPTIONS
–– CALIBRATION_TYPE_MISMATCH: raised if
–– – the calibration alternative of the specified description is not POINT_PAIRS.
–– ILLEGAL_CALIB_DECALIB_DEFINITION: raised if
–– – the point pair array is empty/undefined.
–– – the (de)calibration description is empty/undefined.
function GET_DISCRETE_POINT_PAIRS (

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
238 von/of: 662
OF_CAL_DESCR: in CALIBRATION_DECALIBRATION_TYPE)
return DISCRETE_POINT_PAIR_ARRAY;
–– DESCRIPTION
–– This function returns the discrete point pairs of the
–– specified (de)calibration description.
–– EXCEPTIONS
–– CALIBRATION_TYPE_MISMATCH: raised if
–– – the calibration alternative of the specified description is not DISCRETE.
–– ILLEGAL_CALIB_DECALIB_DEFINITION: raised if
–– – the point pair array is empty/undefined.
–– – the (de)calibration description is empty/undefined.
function GET_BOOLEAN_BY_TRUE_VALUE (
OF_CAL_DESCR: in CALIBRATION_DECALIBRATION_TYPE)
return NUMERIC_TYPES.BIT;
–– DESCRIPTION
–– This function returns the bit representation for ”TRUE” of the
–– specified boolean (de)calibration description.
–– EXCEPTIONS
–– CALIBRATION_TYPE_MISMATCH: raised if
–– – the calibration alternative of the specified description is not BOOLEAN_TYPE.
–– ILLEGAL_CALIB_DECALIB_DEFINITION: raised if
–– – the (de)calibration description is empty/undefined.
function GET_BOOLEAN_BY_TRUE_VALUE (
OF_CAL_DESCR: in CALIBRATION_DECALIBRATION_TYPE)
return NUMERIC_TYPES.INTEGER32;
–– DESCRIPTION
–– This function returns the integer representation for ”TRUE” of the
–– specified boolean (de)calibration description.
–– EXCEPTIONS
–– CALIBRATION_TYPE_MISMATCH: raised if
–– – the calibration alternative of the specified description is not BOOLEAN_TYPE.
–– ILLEGAL_CALIB_DECALIB_DEFINITION: raised if
–– – the (de)calibration description is empty/undefined.
function GET_BOOLEAN_BY_FALSE_VALUE (
OF_CAL_DESCR: in CALIBRATION_DECALIBRATION_TYPE)
return NUMERIC_TYPES.BIT;
–– DESCRIPTION
–– This function returns the bit representation for ”FALSE” of the
–– specified boolean (de)calibration description.
–– EXCEPTIONS
–– CALIBRATION_TYPE_MISMATCH: raised if
–– – the calibration alternative of the specified description is not BOOLEAN_TYPE.
–– ILLEGAL_CALIB_DECALIB_DEFINITION: raised if
–– – the (de)calibration description is empty/undefined.
function GET_BOOLEAN_BY_FALSE_VALUE (
OF_CAL_DESCR: in CALIBRATION_DECALIBRATION_TYPE)
return NUMERIC_TYPES.INTEGER32;
–– DESCRIPTION
–– This function returns the integer representation for ”FALSE” of the
–– specified boolean (de)calibration description.
–– EXCEPTIONS
–– CALIBRATION_TYPE_MISMATCH: raised if
–– – the calibration alternative of the specified description is not BOOLEAN_TYPE.
–– ILLEGAL_CALIB_DECALIB_DEFINITION: raised if
–– – the (de)calibration description is empty/undefined.
function GET_START_POINT (
OF_CAL_DESCR: in CALIBRATION_DECALIBRATION_TYPE)
return BYTESTREAM_INDEX;
–– DESCRIPTION
–– This function returns the start position of the

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
239 von/of: 662
–– specified bytestream (de)calibration description.
–– EXCEPTIONS
–– CALIBRATION_TYPE_MISMATCH: raised if
–– – the calibration alternative of the specified description is not SUBSTRING.
–– ILLEGAL_CALIB_DECALIB_DEFINITION: raised if
–– – the (de)calibration description is empty/undefined.
function GET_SUBSTRING_LENGTH (
OF_CAL_DESCR: in CALIBRATION_DECALIBRATION_TYPE)
return BYTESTREAM_INDEX;
–– DESCRIPTION
–– This function returns the length of the
–– specified bytestream (de)calibration description.
–– EXCEPTIONS
–– CALIBRATION_TYPE_MISMATCH: raised if
–– – the calibration alternative of the specified description is not SUBSTRING.
–– ILLEGAL_CALIB_DECALIB_DEFINITION: raised if
–– – the (de)calibration description is empty/undefined.
–––––––––––––––––––––––––––––––––––––––––
–– Pack & Unpack operations
–––––––––––––––––––––––––––––––––––––––––
procedure PACK (
VALUE: in CALIBRATION_DECALIBRATION_TYPE ;
BLOCK: in out ADT_PACKING.T_BLOCK );
–– DESCRIPTION
–– This procedure packs the specified (de)calibration description
–– variable into a contiguous memory block.
–– EXCEPTIONS
–– CONSTRAINT_ERROR: raised if
–– – any mandatory component of the (de)calibration description
–– is empty/undefined.
–– ADT_PACKING Exceptions : NOT_ENOUGH_SPACE
–– BLOCK_READ_ERROR
procedure UNPACK (
BLOCK: in out ADT_PACKING.T_BLOCK ;
VALUE: out CALIBRATION_DECALIBRATION_TYPE );
–– DESCRIPTION
–– This procedure unpacks the specified memory block into
–– a (de)calibration description variable.
–– EXCEPTIONS
–– ADT_PACKING Exceptions : NOT_ENOUGH_PACKED_DATA
–– BLOCK_WRITE_ERROR
–– ADT_ID_CHECK_FAILURE
function SIZE_NEEDED (VALUE : CALIBRATION_DECALIBRATION_TYPE)
return ADT_PACKING.T_PACK_INDEX;
–– DESCRIPTION
–– This function calculates the actual size needed for packing the
–– supplied VALUE
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– operations to calibrate and decalibrate values
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
function CALIBRATED(RAW_VALUE : NUMERIC_TYPES.DOUBLE_FLOAT;
CAL_DESCR : CALIBRATION_DECALIBRATION_TYPE)
return NUMERIC_TYPES.DOUBLE_FLOAT;
function CALIBRATED(RAW_VALUE : NUMERIC_TYPES.UNSIGNED_INTEGER32;
CAL_DESCR : CALIBRATION_DECALIBRATION_TYPE)
return NUMERIC_TYPES.DOUBLE_FLOAT;
function CALIBRATED(RAW_VALUE : NUMERIC_TYPES.INTEGER32;
CAL_DESCR : CALIBRATION_DECALIBRATION_TYPE)

Space Infrastructure
return NUMERIC_TYPES.DOUBLE_FLOAT;
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
function CALIBRATED(RAW_VALUE : NUMERIC_TYPES.SINGLE_FLOAT;
CAL_DESCR : CALIBRATION_DECALIBRATION_TYPE)
return NUMERIC_TYPES.SINGLE_FLOAT;
function CALIBRATED(RAW_VALUE : NUMERIC_TYPES.UNSIGNED_INTEGER32;
CAL_DESCR : CALIBRATION_DECALIBRATION_TYPE)
return NUMERIC_TYPES.SINGLE_FLOAT;
function CALIBRATED(RAW_VALUE : NUMERIC_TYPES.INTEGER32;
CAL_DESCR : CALIBRATION_DECALIBRATION_TYPE)
return NUMERIC_TYPES.SINGLE_FLOAT;
function CALIBRATED(RAW_VALUE : NUMERIC_TYPES.UNSIGNED_INTEGER32;
CAL_DESCR : CALIBRATION_DECALIBRATION_TYPE)
return NUMERIC_TYPES.UNSIGNED_INTEGER32;
function CALIBRATED(RAW_VALUE : NUMERIC_TYPES.INTEGER32;
CAL_DESCR : CALIBRATION_DECALIBRATION_TYPE)
return NUMERIC_TYPES.INTEGER32;
function CALIBRATED(RAW_VALUE : NUMERIC_TYPES.UNSIGNED_INTEGER32;
CAL_DESCR : CALIBRATION_DECALIBRATION_TYPE)
return NUMERIC_TYPES.INTEGER32;
function CALIBRATED(RAW_VALUE : NUMERIC_TYPES.INTEGER32;
CAL_DESCR : CALIBRATION_DECALIBRATION_TYPE)
return NUMERIC_TYPES.UNSIGNED_INTEGER32;
–– The following functions will return the first entry of the list of
–– defined state_codes in case the provided value is not found (i.e. there
–– is no corresponding state_code found for the provided raw value).
function CALIBRATED(RAW_VALUE : NUMERIC_TYPES.INTEGER32;
CAL_DESCR : CALIBRATION_DECALIBRATION_TYPE)
return MPS_DEFINITIONS.STATE_CODE;
function CALIBRATED(RAW_VALUE : NUMERIC_TYPES.UNSIGNED_INTEGER32;
CAL_DESCR : CALIBRATION_DECALIBRATION_TYPE)
return MPS_DEFINITIONS.STATE_CODE;
function CALIBRATED(RAW_VALUE : NUMERIC_TYPES.BIT;
CAL_DESCR : CALIBRATION_DECALIBRATION_TYPE)
return MPS_DEFINITIONS.STATE_CODE;
function CALIBRATED(RAW_VALUE : NUMERIC_TYPES.BIT;
CAL_DESCR : CALIBRATION_DECALIBRATION_TYPE)
return BOOLEAN;
function CALIBRATED(RAW_VALUE : NUMERIC_TYPES.INTEGER32;
CAL_DESCR : CALIBRATION_DECALIBRATION_TYPE)
return BOOLEAN;
function CALIBRATED(RAW_VALUE : STRING;
CAL_DESCR : CALIBRATION_DECALIBRATION_TYPE)
return STRING;
–– using functions returning types that do not fit in a register (>32 bits)
–– causes heap access, use these equivalent procedures for speed
–– The procedures containing a state_code as OUT–parameter will return the
–– first entry of the list of defined state_codes in case the provided value
–– is not found (i.e. there is no correspondent state_code found for the
–– provided raw value).
procedure CALIBRATE(RAW_VALUE : NUMERIC_TYPES.INTEGER32;
CAL_DESCR : CALIBRATION_DECALIBRATION_TYPE;
CAL_VALUE : out MPS_DEFINITIONS.STATE_CODE);
procedure CALIBRATE(RAW_VALUE : NUMERIC_TYPES.UNSIGNED_INTEGER32;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
240 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
CAL_DESCR : CALIBRATION_DECALIBRATION_TYPE;
CAL_VALUE : out MPS_DEFINITIONS.STATE_CODE);
procedure CALIBRATE(RAW_VALUE : in NUMERIC_TYPES.BIT;
CAL_DESCR : in CALIBRATION_DECALIBRATION_TYPE;
CAL_VALUE : out MPS_DEFINITIONS.STATE_CODE);
procedure CALIBRATE(RAW_VALUE : in MPS_DEFINITIONS.T_RAW_STRING;
RAW_LENGTH : in natural;
CAL_DESCR : in CALIBRATION_DECALIBRATION_TYPE;
CAL_VALUE : out MPS_DEFINITIONS.T_ENGINEERING_STRING;
CAL_LENGTH : out natural);
–– DESCRIPTION
–– These functions calibrate raw values into engineering values
–– according to a given calibration description:
–– – analog raw values of type FLOAT (integers have to be converted
–– to FLOATs anyhow...) are converted into analog FLOATs
–– – discrete raw values (represented by their integers) are
–– converted into state codes
–– – string raw values are ”substringed”
–– The calibration for polynom is done according to the following
–– formula:
–– Y = a(4)*X**4 + a(3)*X**3 + a(2)*X**2 + a(1)*X + a(0)
–– where X = raw value, Y = calibrated value and
–– a(0) .. a(4) = COEFFICIENTS 0 .. 4
–– For calibration via point pairs linear interpolation
–– is used.
–– EXCEPTIONS:
–– VALUE_OUT_OF_RANGE:
–– – the raw or engineering value is out of range w.r.t. the defined
–– limits of the calibration curve resp. discrete points.
–– ILLEGAL_MAPPING_KIND:
–– – the description was not created using SET_xxx_CALIBRATION
–– ILLEGAL_CALIB_DECALIB_DEFINITION:
–– – calibration description is incomplete
–– CALIBRATION_TYPE_MISMATCH:
–– – the calibration description does not match types
–– of function argument and result
function DECALIBRATED(ENG_VALUE : NUMERIC_TYPES.DOUBLE_FLOAT;
CAL_DESCR : CALIBRATION_DECALIBRATION_TYPE)
return NUMERIC_TYPES.DOUBLE_FLOAT;
function DECALIBRATED(ENG_VALUE : NUMERIC_TYPES.DOUBLE_FLOAT;
CAL_DESCR : CALIBRATION_DECALIBRATION_TYPE)
return NUMERIC_TYPES.UNSIGNED_INTEGER32;
function DECALIBRATED(ENG_VALUE : NUMERIC_TYPES.DOUBLE_FLOAT;
CAL_DESCR : CALIBRATION_DECALIBRATION_TYPE)
return NUMERIC_TYPES.INTEGER32;
function DECALIBRATED(ENG_VALUE : NUMERIC_TYPES.SINGLE_FLOAT;
CAL_DESCR : CALIBRATION_DECALIBRATION_TYPE)
return NUMERIC_TYPES.SINGLE_FLOAT;
function DECALIBRATED(ENG_VALUE : NUMERIC_TYPES.SINGLE_FLOAT;
CAL_DESCR : CALIBRATION_DECALIBRATION_TYPE)
return NUMERIC_TYPES.UNSIGNED_INTEGER32;
function DECALIBRATED(ENG_VALUE : NUMERIC_TYPES.SINGLE_FLOAT;
CAL_DESCR : CALIBRATION_DECALIBRATION_TYPE)
return NUMERIC_TYPES.INTEGER32;
function DECALIBRATED(ENG_VALUE : NUMERIC_TYPES.UNSIGNED_INTEGER32;
CAL_DESCR : CALIBRATION_DECALIBRATION_TYPE)
return NUMERIC_TYPES.UNSIGNED_INTEGER32;
function DECALIBRATED(ENG_VALUE : NUMERIC_TYPES.INTEGER32;
CAL_DESCR : CALIBRATION_DECALIBRATION_TYPE)
return NUMERIC_TYPES.INTEGER32;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
241 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
function DECALIBRATED(ENG_VALUE : NUMERIC_TYPES.UNSIGNED_INTEGER32;
CAL_DESCR : CALIBRATION_DECALIBRATION_TYPE)
return NUMERIC_TYPES.INTEGER32;
function DECALIBRATED(ENG_VALUE : NUMERIC_TYPES.INTEGER32;
CAL_DESCR : CALIBRATION_DECALIBRATION_TYPE)
return NUMERIC_TYPES.UNSIGNED_INTEGER32;
–– The following functions will raise the exception VALUE_OUT_OF_RANGE in
–– case the provided value is not found (i.e. there
–– is no correspondent raw value found for the provided state_code).
function DECALIBRATED(ENG_VALUE : MPS_DEFINITIONS.STATE_CODE;
CAL_DESCR : CALIBRATION_DECALIBRATION_TYPE)
return NUMERIC_TYPES.INTEGER32;
function DECALIBRATED(ENG_VALUE : MPS_DEFINITIONS.STATE_CODE;
CAL_DESCR : CALIBRATION_DECALIBRATION_TYPE)
return NUMERIC_TYPES.UNSIGNED_INTEGER32;
function DECALIBRATED(ENG_VALUE : MPS_DEFINITIONS.STATE_CODE;
CAL_DESCR : CALIBRATION_DECALIBRATION_TYPE)
return NUMERIC_TYPES.BIT;
function DECALIBRATED(ENG_VALUE : BOOLEAN;
CAL_DESCR : CALIBRATION_DECALIBRATION_TYPE)
return NUMERIC_TYPES.BIT;
function DECALIBRATED(ENG_VALUE : BOOLEAN;
CAL_DESCR : CALIBRATION_DECALIBRATION_TYPE)
return NUMERIC_TYPES.INTEGER32;
–– DESCRIPTION
–– These functions decalibrate engineering values into raw values
–– according to a given decalibration description:
–– – analog engineering values of type FLOAT (integers have to be converted
–– to FLOATs anyhow...) are converted into analog FLOATs
–– – state code engineering values are
–– converted into integers (representing their discrete raw value)
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
242 von/of: 662
–– The decalibration for polynom is done according to the following
–– formula:
–– Y = a(4)*X**4 + a(3)*X**3 + a(2)*X**2 + a(1)*X + a(0)
–– where X = raw value, Y = calibrated value and
–– a(0) .. a(4) = COEFFICIENTS 0 .. 4
–– For calibration via point pairs linear interpolation
–– shall be used.
–– EXCEPTIONS:
–– VALUE_OUT_OF_RANGE:
–– – the raw or engineering value is out of range w.r.t. the defined
–– limits of the calibration curve resp. discrete points.
–– ILLEGAL_MAPPING_KIND:
–– – the description was not created using SET_xxx_DECALIBRATION
–– – the calibration alternative does not match function argument and result
–– ILLEGAL_CALIB_DECALIB_DEFINITION:
–– – calibration description is incomplete
–– – software types of raw and engineering value do not match types
–– of function argument and result
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– operations to invert a calibration curve
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
function INVERT (
CAL_DESCR: CALIBRATION_DECALIBRATION_TYPE)
return CALIBRATION_DECALIBRATION_TYPE;

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–– DESCRIPTION
–– This function converts a calibration/decalibration description into
–– a decalibration/calibration description as follows:
–– point pairs to point pairs
–– discrete to discrete
–– polynom to polynom or point pairs depending
–– on the degree of the polynom
––
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
243 von/of: 662
–– EXCEPTION
–– NOT_INVERTABLE: raised if
–– the calibration alternative is set to UNDEFINED or SUBSTRING
–– the calibration alternative is set to POINT_PAIRS or POLYNOM and the
–– (de)calibration description is not strictly monotone
–– the calibration alternative is set to DISCRETE and
–– two different arguments have the same image
–– ILLEGAL_CALIB_DECALIB_DEFINITION: raised if
–– – calibration description is incomplete
function IS_INVERTABLE (
CAL_DESCR: CALIBRATION_DECALIBRATION_TYPE)
return boolean;
–– DESCRIPTION
–– This function checks if a (de)calibration mapping
–– can be inverted (i.e. is strictly monotone)
–– If the calibration description is invertable the value ”TRUE” is returned.
–– EXCEPTION
–– none
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
private
type INTERNAL_CALIB_DECALIB_TYPE
( THE_CALIBRATION_ALTERNATIVES: CALIBRATION_ALTERNATIVES);
type CALIBRATION_DECALIBRATION_TYPE is access
INTERNAL_CALIB_DECALIB_TYPE;
NULL_CALIBRATION_DECALIBRATION:
constant CALIBRATION_DECALIBRATION_TYPE := null;
end CALIBRATION;
Impact :
The modifications provide an additional pair of parameters(INTEGER32/BOOLEAN) for calibration/decalibration
as well as the changed description for de–/calibration of discrete values (state_code)
UNSIGNED_INTEGER range for STATECODE changed from 0..31 to 0..2GB.

Space Infrastructure
7.5 TES DEFINITIONS
Informal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
244 von/of: 662
A same set of data types are used in the various procedural interfaces provided by the TES product. In order to
ensure the consistency of their definition and usage through all the interfaces, they are grouped and defined once,
in the current section.
They are ”basic” data types and constants (like numbers, strings, enumerations...) which are accessible directly.
They constitute a type pool and are grouped into a set of Ada packages, according to their nature.
The usage of the basic data types is simple. The desired variable has to be declared with the desired type in the
piece of software which will use it. The access to the content of the variable is done directly, by knowledge of
its Ada structure.
This TES_DEFINITIONS package contains type and constant definitions that are :
– . specific of TES, i.e. not used or shared by several VICOS products,
– . common in TES, i.e. used or shared by several TES provided services,
– . of general nature, i.e. not specific to any of these services.

Space Infrastructure
Formal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
––
–– TES_DEFINITIONS
––
––****************************************************************************
––ABSTRACT––
––
–– This package defines types and constants for TES
––
––
––
––*–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––IDENTIFICATION––
–– PROJECT NAME : CGS
–– PRODUCT NAME : TES
–– CI–NUMBER : 1216 843
–– OBJECT NAME : TES_DEFINITIONS
––*–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––CONTENTS––
–– COMPILER : SunAda 1.1 /Alsys Ada 5.5.1
–– LANGUAGE : Ada
–– SPECIAL CONTENTS: –
–– CHANGE HISTORY
––
–– creator: U.Maron
–– creation date: 03.09.97
–– comment:
–– #PIRN: COL–RIBRE–IRN–CGS–7012 Issue 1/C:
–– New return codes for SW commanding LOAD_SCOE.
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– creator: U.Maron
–– creation date: 29.05.97
–– comment:
–– #PIRN: COL–RIBRE–IRN–CGS–7012 Issue 1/A:
–– Provide definitions for replay mode.
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V5.1.1.1 at Central Repository at DASA RI
–– creator: athmann (on host vicos_5)
–– creation date: 17.09.96 18:20:14
–– comment:
–– #PIRN: COL–RIBRE–IRN–CGS–4014 Issue 1/A:
–– Add new return codes
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V5.1.1.1 at Central Repository at DASA RI
–– creator: athmann (on host vicos_5)
–– creation date: 17.09.96 18:20:14
–– comment:
–– #PIRN: COL–RIBRE–IRN–CGS–4014 Issue 1/A:
–– Add new return codes
––
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V4.5 at CC; CGS development
–– creator: ahs (on host sde16)
–– creation date: 18.08.95 09:31:19
–– comment:
–– COL–RIBRE–IRN–CGS–3067 1/D
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
245 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V4.1.1.2 at Central Repository at DASA RI (CGS V3 development)
–– creator: gehrke (on host mps2s–1)
–– creation date: 16.08.95 14:33:38
–– comment:
–– Build 2 B/L, PIRN 3067D
–– END HISTORY added to header
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V3.0 at DASA–RI ; CGS Engineering
–– creator: maron (on vicos2–2)
–– creation date: 24.03.95
–– Build 2 baseline, PIRN 3067
–– V2.6 at ERNO ; VICOS development
–– creator: vicos (on host prime_1)
–– creation date: 18.09.92 12:11:36
–– modifications according to FINAL ICD REVIEW DNs (see list)
–– V2.5 at ERNO ; VICOS development
–– creator: vicos (on host vicos_8)
–– creation date: 22.07.92 15:29:47
–– Deleted : T_AP_ID; Added : NULL_IDENTIFIER
–– V2.4 at ERNO ; VICOS development
–– creator: vicos (on host vicos_8)
–– creation date: 21.07.92 07:33:10
–– Naming of CGS_CALENDAR changed to VICOS_CALENDAR
–– V2.3 at ERNO ; VICOS development
–– creator: maron (on host vicos_6)
–– creation date: 20.07.92 15:34:26
–– VCS–SPADM
–– V2.2 at ERNO ; VICOS development
–– creator: athmann (on host vicos_5)
–– creation date: 10.07.92 16:12:21
–– align TES_EXECUTION_MODE with VICOS_DEFINITIONS
–– V2.1 at ERNO ; VICOS development
–– creator: vicos (on host vicos_12)
–– creation date: 30.06.92 17:38:03
–– added Standard Header by command create_file
––
–– END HISTORY
––
––****************************************************************************
––
with VICOS_DEFINITIONS;
package TES_DEFINITIONS is
––––––––––––––––––––––––––––––––––––––––––––––––––
––commonly used identifiers
––––––––––––––––––––––––––––––––––––––––––––––––––
type T_APPLICATION_ID is new NATURAL;
for T_APPLICATION_ID’size use 32;
type T_IDENTIFIER is new NATURAL;
for T_IDENTIFIER’size use 32;
NULL_IDENTIFIER : constant T_IDENTIFIER := 0;
––––––––––––––––––––––––––––––––––––––––––––––––––
–– commonly used return values
––––––––––––––––––––––––––––––––––––––––––––––––––
type T_RETURN_STATUS is new NATURAL;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
246 von/of: 662

Space Infrastructure
–– Return Codes for TES_RPI and TES_API
SUCCESS : constant T_RETURN_STATUS := 0;
OTHER_ERROR : constant T_RETURN_STATUS := 1;
COMMUNICATION_ERROR : constant T_RETURN_STATUS := 2;
CURRENT_MODE_WRONG : constant T_RETURN_STATUS := 3;
INVALID_APPLICATION_ID : constant T_RETURN_STATUS := 10;
INVALID_VALUE : constant T_RETURN_STATUS := 11;
INVALID_IDENTIFIER : constant T_RETURN_STATUS := 12;
ENDITEM_UNKNOWN : constant T_RETURN_STATUS := 13;
ENDITEM_NOT_ACQUIRED : constant T_RETURN_STATUS := 14;
AP_NOT_FOUND : constant T_RETURN_STATUS := 50;
SAS_UNKNOWN : constant T_RETURN_STATUS := 51;
INVALID_COMMAND_ID : constant T_RETURN_STATUS := 60;
COMMAND_TIMEOUT : constant T_RETURN_STATUS := 61;
COMMAND_NEEDS_NO_ACK : constant T_RETURN_STATUS := 62;
NOT_A_SW_VALUE : constant T_RETURN_STATUS := 70;
TYPE_MISMATCH : constant T_RETURN_STATUS := 71;
TSS_ERROR : constant T_RETURN_STATUS := 80;
SMT_RESET : constant T_RETURN_STATUS := 81;
ADU_SERVICE_ALREADY_ANNOUNCED : constant T_RETURN_STATUS := 90;
ADU_SERVICE_NOT_ANNOUNCED : constant T_RETURN_STATUS := 91;
GDU_SERVICE_ALREADY_ANNOUNCED : constant T_RETURN_STATUS := 92;
GDU_SERVICE_NOT_ANNOUNCED : constant T_RETURN_STATUS := 93;
NO_SERVER_CONNECTION : constant T_RETURN_STATUS := 100;
TES_IS_STOPPED : constant T_RETURN_STATUS := 101;
WRONG_MODE_SELECTED : constant T_RETURN_STATUS := 102;
TES_BADLY_INITIALISED : constant T_RETURN_STATUS := 103;
REQUEST_ENDITEM_LIST_FAILED : constant T_RETURN_STATUS := 104;
DELIVERY_ID_UNKNOWN : constant T_RETURN_STATUS := 110;
INVALID_LIBRARY_NUMBER : constant T_RETURN_STATUS := 111;
INVALID_PROCEDURE_NUMBER : constant T_RETURN_STATUS := 112;
INVALID_AP_ID : constant T_RETURN_STATUS := 113;
ILLEGAL_FROM_HLCL : constant T_RETURN_STATUS := 114;
INVALID_PARAMETER : constant T_RETURN_STATUS := 115;
AP_NOT_STOPPED : constant T_RETURN_STATUS := 120;
TOO_MANY_APS : constant T_RETURN_STATUS := 121;
AP_NOT_COMPILED : constant T_RETURN_STATUS := 122;
TSS_INIT_ERROR : constant T_RETURN_STATUS := 130;
AP_TABLE_INIT_ERROR : constant T_RETURN_STATUS := 131;
GDU_TABLE_INIT_ERROR : constant T_RETURN_STATUS := 132;
MONITOR_LIST_INIT_ERROR : constant T_RETURN_STATUS := 133;
UCL_USER_LIB_INIT_ERROR : constant T_RETURN_STATUS := 134;
MEASUREMENT_INIT_ERROR : constant T_RETURN_STATUS := 135;
ERROR_MESSAGE_INIT_ERROR : constant T_RETURN_STATUS := 136;
DBS_CONNECTION_PROBLEM : constant T_RETURN_STATUS := 137;
HCI_CONNECTION_PROBLEM : constant T_RETURN_STATUS := 138;
MDB_CONNECTION_PROBLEM : constant T_RETURN_STATUS := 139;
DISTRIBUTION_TABLE_ERROR : constant T_RETURN_STATUS := 140;
TOPOLOGY_ERROR : constant T_RETURN_STATUS := 141;
RUNTIME_ERROR : constant T_RETURN_STATUS := 150;
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
247 von/of: 662

Space Infrastructure
LOAD_ADT_ERROR_MEASUREMENT_TABLE: constant T_RETURN_STATUS := 201;
LOAD_ADT_ERROR_GDU_TABLE : constant T_RETURN_STATUS := 202;
LOAD_ADT_ERROR_ADU_TABLE : constant T_RETURN_STATUS := 203;
LOAD_ADT_ERROR_MONITOR_LIST : constant T_RETURN_STATUS := 204;
LOAD_ADT_ERROR_GDU_LIST : constant T_RETURN_STATUS := 205;
LOAD_ADT_ERROR_SIM_VALUE_TABLE : constant T_RETURN_STATUS := 206;
LOAD_ADT_ERROR_AP_TABLE : constant T_RETURN_STATUS := 207;
LOAD_ADT_ERROR_USER_LIB_TABLE : constant T_RETURN_STATUS := 208;
LOAD_ADT_ERROR_NODE_LIST : constant T_RETURN_STATUS := 209;
LOAD_ADT_ERROR_SW_LIST : constant T_RETURN_STATUS := 210;
LOAD_ADT_ERROR_USR_MSG_TABLE : constant T_RETURN_STATUS := 211;
WRONG_ENVIRONMENT : constant T_RETURN_STATUS := 212;
MISSING_ENVIRONMENT : constant T_RETURN_STATUS := 213;
DIRECTORY_CREATION_ERROR : constant T_RETURN_STATUS := 214;
DIRECTORY_DOES_NOT_EXIST : constant T_RETURN_STATUS := 215;
FILE_OPEN_ERROR : constant T_RETURN_STATUS := 216;
FILE_CLOSE_ERROR : constant T_RETURN_STATUS := 217;
FILE_READ_ERROR : constant T_RETURN_STATUS := 218;
MISSING_NODE_NAME : constant T_RETURN_STATUS := 219;
MISSING_LOAD_POINT : constant T_RETURN_STATUS := 220;
REPLAY_START_TIME_WRONG : constant T_RETURN_STATUS := 250;
WRONG_REPLAY_PERIOD : constant T_RETURN_STATUS := 251;
CANNOT_READ_ARCHIVE_FILE : constant T_RETURN_STATUS := 252;
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
LOAD_ADT_ERROR_SWOP_CMD_TABLE : constant T_RETURN_STATUS := 253;
LOAD_ADT_ERROR_RESPONSE_PACKET_TABLE : constant T_RETURN_STATUS := 254;
LOAD_ADT_ERROR_APPL_ID_TABLE : constant T_RETURN_STATUS := 255;
––––––––––––––––––––––––––––––––––––––––––––––––––
–– commonly used mode and state definitions
––––––––––––––––––––––––––––––––––––––––––––––––––
subtype T_EXECUTION_MODE is VICOS_DEFINITIONS.T_VICOS_MODE
range VICOS_DEFINITIONS.NONE .. VICOS_DEFINITIONS.SIMULATION;
type T_LINK_STATUS is (RESET, INITIALISED, RUNNING, ABORTED);
for T_LINK_STATUS’size use 8;
––––––––––––––––––––––––––––––––––––––––––––––––––
–– commonly used message definitions
––––––––––––––––––––––––––––––––––––––––––––––––––
MAX_SIZE_OF_AP_MESSAGE : constant NATURAL := 80;
subtype T_AP_MESSAGE is STRING (1 .. MAX_SIZE_OF_AP_MESSAGE);
MAX_SIZE_OF_SAS_MESSAGE : constant NATURAL := 80;
subtype T_SAS_MESSAGE is STRING (1 .. MAX_SIZE_OF_SAS_MESSAGE);
MAX_SIZE_OF_SAS_PARAMETERS : constant NATURAL := 80;
subtype T_SAS_PARAMETERS is STRING (1 .. MAX_SIZE_OF_SAS_PARAMETERS);
end TES_DEFINITIONS;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
248 von/of: 662

Space Infrastructure
7.6 TES Abstract Data Types
7.6.1 General Concepts
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
249 von/of: 662
A same set of abstract data types related to TES are used in the VICOS products. In order to ensure the consistency
of their definition and usage through the softwares, they are grouped and defined once, in the current
section.
An ADT specification describes a class of data structures not by an implementation, but by the list of services
available on the data structures and the formal properties of these services. Further, an ADT offers a set of services
to the outside world (other Objects, Applications etc), which is only concerned with the services offered
and not how they are implemented.
An ADT is defined by a formal specification, which is comprised of Types and Functions (Syntax part) and Preconditions
and Axioms (Semantic part).
– The Type part lists the types of the specification (which may be several types or a single type, e.g. a
’stack’).
– The Functions part lists the services available on instances of the type.
– The Axioms part describes semantics of the functions on the data to restrict and more precisely define
the specification.
– The Preconditions part provides applicability conditions for partial functions (functions that cannot be
applied to the ADT implementation in all cases (e.g., when a data type is empty, it may not be useful
to access its contents)).
An abstract data type is a type which Ada structure is hidden (private types) because of its complexity, its varying
size or its implementation dependency on compilers. Their access is possible only through associated operations.
This part of the interface allows pieces of software to manipulate data without knowledge of their Ada representation.
These types are available in the form of separate Ada packages containing at least an abstract data type,
some basic data types related to it and the operations to handle it.
The ADT services provided by TES contain a number of services applicable to appropriate ADTs. These may
include Create services, used to create the ADT structure, Set services, which set up the data within the ADT
(e.g. for data originally held in the Mission Database or in UNIX files), Get services, which read the data set–up
in the ADT and Delete services which remove the ADT. There are also type specific services which are ADT
specific, these may include services such as Initialise, Copy, Move, Pack and Unpack. The latter Pack and Unpack,
when provided, are particularly important for data transfer to provide a method of packing and unpacking
data into Byte arrays to enable easy data communication.
The usage of the abstract data types is quite sophisticated. The desired variable is declared with the desired type
in the piece of software which will use it. The access to the content of the variable is done by using the associated
operations, because the associated Ada type is not visible. A Create/Construct operation, when provided, is the
first to be used, to instanciate the content of the variable. The Set_values operations can then be used to write
data into the instanciated variable. The Values_of/Get_values operations allow to read data from the instanciated
and filled–up variable. At last the Delete operation, when provided, will free the space allocated to ADT variables
which are not needed any more in the software.
TES provides a set of ADTs which are used as appropriate by other products, including:
– ADT for raw value type,
– ADT for engineering value type,
– ADT for ADU description type,
– ADT for ADU type,

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
250 von/of: 662
– ADT for simulated value table type,
– ADT for GDU description type,
– ADT for GDU type,
– ADT for archive file type,
– ADT for calibration description type,
– ADT for calibration services,
– ADT for monitoring description type,
– ADT for measurement description type.
TES provides a method of accessing TES data structures held in the Mission Database without causing performance
problems with continuous database access. A procedure for establishing an ADT based on MDB data is
as follows: the MDA appropriate operation will be called to read appropriate Check–out information. TES will
provide ADT Create services (if any) to create the ADT in memory and ADT Set services will be used to put
the data from the MDB into the ADT data area. (Note, these services used by MDA) The product requiring ADT
access (maybe another Integration/Qualification product) can then use the TES provided ADT Get services to
access the ADT data and functions. On completion of use and when provided, TES ADT Delete services are
used to remove the ADT.
Note that the use of ADTs within CGS provides a mechanism for Memory Management, which helps to avoid
the problems of ’Garbage Collection’ that occurs with manipulating data structures within an ’Ada’ Run Time
system. This is particularly useful for tasks performed by Integration/Qualification products which need to
transfer data information between programs.
Some basic types are also defined in ADT packages. They are, most of the time, enumeration types bound to
the ADT defined in that package.
For these enumeration types, the following naming convention has been used :
– types suffixed with _TYPE are enumeration types not determining a particular structure of the ADT;
it can be considered as a normal attribute of the ADT, e.g. INTERPRETATION_TYPE in
ADT_MEASUREMENT_DESCRIPTION.
– types suffixed with _ALTERNATIVES are enumeration types which determine the set of other attributes
the corresponding ADT will contain, e.g. T_ADU_ALTERNATIVES in ADT_ADU_DE-
SCRIPTION.
7.6.2 Operations
This section describes the operations which are available on the previous types.
7.6.2.1 SET Operations
The SET operation(s) will assign the values of the attributes of an ADT. At least one SET operation has to be
provided, but in general there will be several SET operations, one for each of the attributes composing the ADT.
In case the type of the attribute exactly determines the alternative to be set, SET can be a set of overloaded SET
procedures (all having the same name) and the type of attribute to be set will be determined by the type of the
passed parameter. The type of the attribute may be defined in another package, it may be a basic type or an other
ADT. In case several attributes have the same type, different names have to be chosen for the SET operations
(e.g. SET_A, SET_B).
7.6.2.1.1 GET Operations
The complementary of the SET operation(s) is the GET operation(s). It follows the same rules with respect to
parameters and naming apply as for the SET operation. Most of the time, a function ATTRIBUTE is preferred

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
251 von/of: 662
to a procedure GET_ATTRIBUTE whenever it is possible, i.e. when no limited private types are returned or
when single attribute is returned.
7.6.2.1.2 ALTERNATIVE Function
The function ALTERNATIVE returns the value of the alternative a variable of type T_ADT currently has. After
CREATE has been called, the default value of a variable of type T_ADT shall be UNDEFINED. It shall be possible
to assign values of any attribute of any alternative to the variable then. This shall, however, then change the
value of the ’discriminent’ to one of the enumeration values in T_ADT_ALTERNATIVES. All attributes belonging
to one alternative of T_ADT_ALTERNATIVES should be assign in one set operation (this is however
not a must, it is a design goal and has to be decided on a case to case basis).
7.6.2.1.3 PACK Operation
The pack operation packs the contents of a variable of type T_ADT into a block of type T_BLOCK by using
operations of an ADT_PACKING
7.6.2.1.4 UNPACK Operation
Inversely, UNPACK unpacks a T_BLOCK into a variable of type T_ADT which has been created before.
7.6.2.1.5 PACKED_SIZE Function
Function PACKED_SIZE returns the maximum number of bytes a packed structure of T_ADT may occupy.
7.6.2.1.6 ADD Operations
Some complex ADTs use other ADTs (e.g. ADT_ADU) or have a non deterministic memory usage, i.e. they
’use’ varying amounts of memory for a given alternative.
For these ADTs, there exists the possibility to maintain dynamic ’lists’ of attributes or values inside an ADT.
For this purpose, an ADD operation might be provided which then inserts exactly one element to this list.
Examples are the raw values in an ADU in the package ADT_ADU.
This procedure belongs to the specific procedures defined in the frame of a complex ADT. They depend on the
special purpose of the complex ADT and the implementer could add procedures like: get_next_element, read_at
etc.
In most of the cases, these ADD operations can be replaced by a set of SET operations, because the size of the
list is known in advance. For a type T_ADT_ITEM_LIST, the operation SET_SIZE will have to be used first,
and then the operation SET_ITEM, to fill the list at a specified index. Note that the index shall be uniformly
incremented from 1 to the chosen size, with an increment of 1.
7.6.2.1.7 Operations on tables
The operations defined on T_TABLE follow exactly the same logic as for the ADT itself.
7.6.2.1.8 Exceptions
The procedures/functions will raise the following standard exceptions :
– STORAGE_ERROR in case the CREATE operation has not sufficient memory space, independent
of the internal implementation
– NOT_CREATED if an operation is called on a variable which has not been created.
– {PARAMETER}_VALUE_ILLEGAL in case the value of the passed parameter is not legal, e.g. a
NULL_SID value for an SID parameter.

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
252 von/of: 662
– INDEX_ERROR if the value of the passed index exceeds the size of the specified variable, e.g. it is
raised when trying to write/read the 101st element of an ADU which contains only 100 items.
– {ITEM}_NOT_FOUND when the searched item is not found in the specified list.
– {PARAMETER}_TYPE_MISMATCH when the type of the passed parameter and the expected type
of the formal parameter mismatch.
On a case by case basis, the operations provided in this interface will also raise specific exceptions which are
documented in the formal interface.
7.6.2.1.9 Particular Remarks
7.6.2.1.10 On Synchronisation
Certain ADTs (if not all of them) will have the need of performing certain memory management internally. For
security reasons, a synchronised access to the internal memory has to be achieved, but only for the CREATE,
DESTROY, COPY, UNPACK operations since these have impact on memory management.
At present it is not finally decided, whether the ADT internally has to provide synchronisation or whether the
user should ensure synchronised access. However, this shall not have any impact on the Ada specification.
If internal synchronisation shall be provided, the use of Ada tasking and semaphores is not allowed since this
is in conflict with the current TES design (due to X–windows !!!). Also, for performance reasons, the Ada ’new’
and ’unchecked_deallocation’ are not recommended.
7.6.2.1.11 On Packing/Unpacking
At present there exists in-house a definition of an ADT_PACKING which uses rather sophisticated techniques
to provide secure and elegant packing. However, it is also rather complex. There are investigation on a simpler
approach currently which would reduce complexity and data overheads.
When finally delivering the Ada specifications of all ADTs to the implementation teams, a version of
ADT_PACKING will be delivered also which shall then be used for implementing the PACK/UNPACK operations
of the individual ADTs.
The principals of packing will be that the ADT_ADT.PACK operation is provided with some kind of input
T_BLOCK. The inside the body of the ADT_ADT.PACK routine, other routines of ADT_PACKING shall be
used to ’add’ a packed version of T_ADT to the block. Memory management inside T_BLOCK will be accomplished
inside the ADT_PACKING provided routines. T_BLOCK is then finally returned as an out parameter
of ADT_ADT.PACK (therefore at least it has to be of mode ’in out’).

Space Infrastructure
7.6.3 ADT Raw Value
Informal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
253 von/of: 662
A Raw Value is an typed objet which, depending on the alternative it is attributed, contains a value of the same
type.
A Raw Value is a composite type containing the following attributes :
– an raw value alternative type;
– a single bit, when alternative is SINGLE_BIT;
– a group of bits, when alternative is GROUP_OF_BITS;
– an integer, when alternative is INT;
– a float, when alternative is FLOAT_EGSE;
– a byte stream, when alternative is BYTE_STREAM.
A Table type is also provided, which allows to define indexed lists of this ADT.

Space Infrastructure
Formal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
254 von/of: 662
––
––
––
––****************************************************************************
––ABSTRACT––
––
–– Provides definition of a raw value of different type:
–– – INTEGER
–– – FLOAT
–– – SINGLE_BIT
–– – U_INT
–– – BYTESTREAM
––*–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––IDENTIFICATION––
–– PROJECT NAME : CGS
–– PRODUCT NAME : TES
–– CI–NUMBER : 1216 843
–– OBJECT NAME : ADT_RAW_VALUE
––*–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––CONTENTS––
–– COMPILER : SunAda 1.1/Alsys Ada 5.5.1
–– LANGUAGE : Ada
–– SPECIAL CONTENTS: –
–– CHANGE HISTORY
–– V4.4 at Central Repository at DASA RI (CGS V3 development)
–– creator: grotheer (on host vicos2–6)
–– creation date: 29.06.95 14:06:39
–– comment:
–– MAX_BYTE_STREAM_LENGTH identical to VICOS_DEFINITIONS
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V4.3 at Central Repository at DASA RI (CGS V3 development)
–– creator: grotheer (on host vicos2–6)
–– creation date: 15.06.95 17:04:13
–– comment:
–– Header correted (End History)
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V3.0 at ERNO ; VICOS development
–– creator: gehrke (on host mps2s–1)
–– creation date: 22.05.95 12:00:00
–– CGS V2 Build 2 baseline definition, PIRN 3040/A
––
–– V2.9 at ERNO ; VICOS development
–– creator: athmann (on host vicos_5)
–– creation date: 07.05.93 16:35:41
–– Define new type T_SCALAR_RAW_VALUE
––
–– V2.8 at ERNO ; VICOS development
–– creator: athmann (on host vicos_5)
–– creation date: 03.03.93 19:52:39
–– Version as delivered by SRO1216843b (IK ADTs) + COL–SPR–SBI–0043
––
–– V2.7 at ERNO ; VICOS development
–– creator: satthoff (on host vicos_4)
–– creation date: 25.11.92 10:26:30
–– corrupted header/established new from IK version.
–– V2.6 at ERNO ; VICOS development
–– creator: vicos (on host vicos_s)
–– creation date: 17.11.92 11:30:49
–– adts version 2.0.1: update acc. to PIRN VICOS–2021
–– V2.5 at ERNO ; VICOS development
–– creator: vicos (on host prime_1)
–– creation date: 18.09.92 12:05:49
–– modifications according to FINAL ICD REVIEW DNs (see list)
–– V2.4 at ERNO ; VICOS development
–– creator: vicos (on host vicos_s)
–– creation date: 28.07.92 09:35:52

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–– Changes : editorial, exceptions, operation names
–– V2.3 at ERNO ; VICOS development
–– creator: vicos (on host vicos_8)
–– creation date: 20.07.92 10:52:53
–– General layout for ADTs acc. to TN COL_MBER_ZU1_TN_0026_92
–– V2.2 at ERNO ; VICOS development
–– creator: athmann (on host vicos_5)
–– creation date: 10.07.92 17:49:28
–– Update Header
–– END HISTORY
––****************************************************************************
––
with VICOS_DEFINITIONS;
–– T_RAW_VALUE_ALTERNATIVES
with ADT_PACKING;
–– type T_BLOCK
with NUMERIC_TYPES;
–– type BYTE
–– type BIT
–– type BITSET
package ADT_RAW_VALUE is
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
255 von/of: 662
––––––––––––––––––––––––––––––
–– public types and constants
––––––––––––––––––––––––––––––
subtype T_SCALAR_RAW_VALUE_ALTERNATIVES is
VICOS_DEFINITIONS.T_RAW_VALUE_ALTERNATIVES range VICOS_DEFINITIONS.UNDEFINED ..
VICOS_DEFINITIONS.FLOAT_EGSE;
–– defines a subtype for scalar raw values (i.e. no byte streams)
MAX_BYTE_STREAM_LENGTH : constant := VICOS_DEFINITIONS.MAX_BYTE_STREAM_LENGTH;
type T_BYTE_STREAM is
record
LENGTH : NATURAL := 0;
STREAM : NUMERIC_TYPES.BYTE_ARRAY(1 .. MAX_BYTE_STREAM_LENGTH);
end record;
for T_BYTE_STREAM use
record
LENGTH at 0 range 0 .. 31;
STREAM at 4 range 0 .. MAX_BYTE_STREAM_LENGTH*8–1;
end record;
for T_BYTE_STREAM’SIZE use MAX_BYTE_STREAM_LENGTH*8+32;
–––––––––––––
–– adt types
–––––––––––––
type T_RAW_VALUE (RAW_TYPE : VICOS_DEFINITIONS.T_RAW_VALUE_ALTERNATIVES := VICOS_DE-
FINITIONS.UNDEFINED)
is private;
–– A raw value is composed of :
–– – an raw value alternative type,
–– – a single bit,
–– – an unsigned integer,
–– – an integer,
–– – a float,
–– – a byte stream.
type T_SCALAR_RAW_VALUE (RAW_TYPE : T_SCALAR_RAW_VALUE_ALTERNATIVES
:= VICOS_DEFINITIONS.UNDEFINED)
is private;
–– A scalar raw value is composed of :
–– – an raw value alternative type,
–– – a single bit,
–– – a unsigned integer,
–– – an integer,
–– – a float,
––––––––––––––––––––
–– write operations
––––––––––––––––––––

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
256 von/of: 662
procedure SET_ALTERNATIVE(VALUE : in out T_RAW_VALUE;
RAW_TYPE : in VICOS_DEFINITIONS.T_RAW_VALUE_ALTERNATIVES);
–– DESCRIPTION
–– Sets the alternative of a raw value
–– EXCEPTION
–– RAW_VALUE_IS_CONSTRAINED
–– Raised when trying to change discriminant of
–– a constrained raw value
–– DESCRIPTION (for all following write operations)
–– This procedure sets the current value of the specified
–– raw value variable.
–– EXCEPTIONS (for all following read operations)
–– RAW_VALUE_TYPE_MISMATCH :
–– the current alternative of the passed variable
–– and the type of the formal parameter mismatch.
procedure SET_BIT_VALUE
(
OF_VALUE: in out T_RAW_VALUE;
WITH_BIT: in NUMERIC_TYPES.BIT
);
procedure SET_BITSET_VALUE
(
OF_VALUE: in out T_RAW_VALUE;
WITH_BITSET: in NUMERIC_TYPES.UNSIGNED_INTEGER32
);
procedure SET_INTEGER_VALUE
(
OF_VALUE: in out T_RAW_VALUE;
WITH_INTEGER: in INTEGER
);
procedure SET_FLOAT_VALUE
(
OF_VALUE: in out T_RAW_VALUE;
WITH_FLOAT: in FLOAT
);
procedure SET_BYTE_STREAM_VALUE
(
OF_VALUE: in out T_RAW_VALUE;
WITH_BYTE_STREAM: in T_BYTE_STREAM
);
–– Overloaded Operations for scalar raw values
procedure SET_ALTERNATIVE
(VALUE : in out T_SCALAR_RAW_VALUE;
RAW_TYPE : in T_SCALAR_RAW_VALUE_ALTERNATIVES);
–– DESCRIPTION
–– Sets the alternative of a scalar raw value
–– EXCEPTION
–– RAW_VALUE_IS_CONSTRAINED
–– Raised when trying to change discriminant of
–– a constrained raw value
procedure SET_BIT_VALUE
(
OF_VALUE: in out T_SCALAR_RAW_VALUE;
WITH_BIT: in NUMERIC_TYPES.BIT
);
procedure SET_BITSET_VALUE
(
OF_VALUE: in out T_SCALAR_RAW_VALUE;
WITH_BITSET: in NUMERIC_TYPES.UNSIGNED_INTEGER32
);
procedure SET_INTEGER_VALUE
(
OF_VALUE: in out T_SCALAR_RAW_VALUE;
WITH_INTEGER: in INTEGER

Space Infrastructure
);
procedure SET_FLOAT_VALUE
(
OF_VALUE: in out T_SCALAR_RAW_VALUE;
WITH_FLOAT: in FLOAT
);
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–––––––––––––––––––
–– read operations
–––––––––––––––––––
function ALTERNATIVE
(
OF_VALUE: T_RAW_VALUE
)
return VICOS_DEFINITIONS.T_RAW_VALUE_ALTERNATIVES;
–– DESCRIPTION
–– This function returns the current alternative of
–– the specified raw value variable.
–– DESCRIPTION (for all following read operations)
–– This function returns the current value of
–– the specified raw value variable.
–– EXCEPTIONS (for all following read operations)
–– RAW_VALUE_TYPE_MISMATCH :
–– the current alternative of the passed variable
–– and the type of the formal parameter mismatch.
function BIT_VALUE
(
OF_VALUE: T_RAW_VALUE
) return NUMERIC_TYPES.BIT;
function BITSET_VALUE
(
OF_VALUE: T_RAW_VALUE
) return NUMERIC_TYPES.UNSIGNED_INTEGER32;
function INTEGER_VALUE
(
OF_VALUE: T_RAW_VALUE
) return INTEGER;
function FLOAT_VALUE
(
OF_VALUE: T_RAW_VALUE
) return FLOAT;
function BYTE_STREAM_VALUE
(
OF_VALUE: T_RAW_VALUE
) return T_BYTE_STREAM;
–– Overloaded Operations for scalar raw values
function ALTERNATIVE
(
OF_VALUE: T_SCALAR_RAW_VALUE
)
return T_SCALAR_RAW_VALUE_ALTERNATIVES;
–– DESCRIPTION
–– This function returns the current alternative of
–– the specified raw value variable.
–– DESCRIPTION (for all following read operations)
–– This function returns the current value of
–– the specified raw value variable.
–– EXCEPTIONS (for all following read operations)
–– RAW_VALUE_TYPE_MISMATCH :
–– the current alternative of the passed variable
–– and the type of the formal parameter mismatch.
function BIT_VALUE
(
OF_VALUE: T_SCALAR_RAW_VALUE
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
257 von/of: 662

Space Infrastructure
) return NUMERIC_TYPES.BIT;
function BITSET_VALUE
(
OF_VALUE: T_SCALAR_RAW_VALUE
) return NUMERIC_TYPES.UNSIGNED_INTEGER32;
function INTEGER_VALUE
(
OF_VALUE: T_SCALAR_RAW_VALUE
) return INTEGER;
function FLOAT_VALUE
(
OF_VALUE: T_SCALAR_RAW_VALUE
) return FLOAT;
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–––––––––––––––––––––––––––––––––––––––––––––
–– ’type conversion’ (assignment) operations
–––––––––––––––––––––––––––––––––––––––––––––
function ASSIGN (SCALAR_VALUE: T_SCALAR_RAW_VALUE)
return T_RAW_VALUE;
–– DESCRIPTION
–– Assign a scalar value to a value of type T_RAW_VALUE
–– EXCEPTIONS
–– none
function ASSIGN (RAW_VALUE: T_RAW_VALUE)
return T_SCALAR_RAW_VALUE;
–– DESCRIPTION
–– Assign a raw value to a value of type T_SCALAR_RAW_VALUE
–– EXCEPTIONS
–– RAW_VALUE_TYPE_MISMATCH
–– the type of the RAW_VALUE was BYTE_STREAM
––––––––––––––––––––––
–– packing operations
––––––––––––––––––––––
procedure PACK
(
VALUE: in T_RAW_VALUE;
BLOCK: in out ADT_PACKING.T_BLOCK
);
–– DESCRIPTION
–– This procedure packs the specified raw value variable into
–– a contiguous memory block.
procedure UNPACK
(
BLOCK: in out ADT_PACKING.T_BLOCK;
VALUE: out T_RAW_VALUE
);
–– DESCRIPTION
–– This procedure unpacks the specified memory block into
–– a raw value variable.
–– Overloaded Operations for scalar raw values:
procedure PACK
(
VALUE: in T_SCALAR_RAW_VALUE;
BLOCK: in out ADT_PACKING.T_BLOCK
);
–– DESCRIPTION
–– This procedure packs the specified raw value variable into
–– a contiguous memory block.
procedure UNPACK
(
BLOCK: in out ADT_PACKING.T_BLOCK;
VALUE: out T_SCALAR_RAW_VALUE
);
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
258 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–– DESCRIPTION
–– This procedure unpacks the specified memory block into
–– a raw value variable.
–––––––––––––––––––
–– exceptions
–––––––––––––––––––
RAW_VALUE_TYPE_MISMATCH : exception;
RAW_VALUE_IS_CONSTRAINED : exception;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
259 von/of: 662
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
private
type T_RAW_VALUE (RAW_TYPE : VICOS_DEFINITIONS.T_RAW_VALUE_ALTERNATIVES := VICOS_DEFINI-
TIONS.UNDEFINED) is
record
case RAW_TYPE is
when VICOS_DEFINITIONS.SINGLE_BIT =>
BIT_VALUE : NUMERIC_TYPES.BIT;
BYTE_PAD : NUMERIC_TYPES.BYTE_ARRAY(1..3);
when VICOS_DEFINITIONS. U_INT =>
BITSET_VALUE : NUMERIC_TYPES.UNSIGNED_INTEGER32;
when VICOS_DEFINITIONS.INT =>
INTEGER_VALUE : NUMERIC_TYPES.INTEGER32;
when VICOS_DEFINITIONS.FLOAT_EGSE =>
FLOAT_VALUE : NUMERIC_TYPES.SINGLE_FLOAT;
when VICOS_DEFINITIONS.BYTE_STREAM =>
BYTE_STREAM_VALUE : T_BYTE_STREAM;
when VICOS_DEFINITIONS.UNDEFINED =>
null;
end case ;
end record;
for T_RAW_VALUE use
record
RAW_TYPE at 0 range 0 .. 5;
BYTE_STREAM_VALUE at 0 range 32 .. 32+MAX_BYTE_STREAM_LENGTH*8–1+32;
BIT_VALUE at 0 range 32 .. 32;
BYTE_PAD at 0 range 40 .. 63;
BITSET_VALUE at 0 range 32 .. 63;
INTEGER_VALUE at 0 range 32 .. 63;
FLOAT_VALUE at 0 range 32 .. 63;
end record;
for T_RAW_VALUE’size use MAX_BYTE_STREAM_LENGTH*8+32+32;
–– for T_RAW_VALUE’size use 2112;
type T_SCALAR_RAW_VALUE (RAW_TYPE : T_SCALAR_RAW_VALUE_ALTERNATIVES
:= VICOS_DEFINITIONS.UNDEFINED) is
record
case RAW_TYPE is
when VICOS_DEFINITIONS.SINGLE_BIT =>
BIT_VALUE : NUMERIC_TYPES.BIT;
BYTE_PAD : NUMERIC_TYPES.BYTE_ARRAY(1..3);
when VICOS_DEFINITIONS. U_INT =>
BITSET_VALUE : NUMERIC_TYPES. UNSIGNED_INTEGER32;
when VICOS_DEFINITIONS.INT =>
INTEGER_VALUE : NUMERIC_TYPES.INTEGER32;
when VICOS_DEFINITIONS.FLOAT_EGSE =>
FLOAT_VALUE : NUMERIC_TYPES.SINGLE_FLOAT;
when VICOS_DEFINITIONS.UNDEFINED =>
null;
end case ;
end record;
for T_SCALAR_RAW_VALUE use
record
RAW_TYPE at 0 range 0 .. 5;
BIT_VALUE at 0 range 32 .. 32;
BYTE_PAD at 0 range 40 .. 63;
BITSET_VALUE at 0 range 32 .. 63;
INTEGER_VALUE at 0 range 32 .. 63;
FLOAT_VALUE at 0 range 32 .. 63;
end record;

Space Infrastructure
end ADT_RAW_VALUE;
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
260 von/of: 662

Space Infrastructure
7.6.4 ADT Engineering Value
Informal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
261 von/of: 662
A Engineering Value is an typed objet which, depending on the alternative it is attributed, contains a value of
the same type.
A Engineering Value is a composite type containing the following attributes :
– an engineering value alternative type;
– a state code, when alternative is STATE_CODE;
– an integer, when alternative is INT;
– a float, when alternative is FLT;
– a string, when alternative is STR.
A Table type is also provided, which allows to define indexed lists of this ADT.

Space Infrastructure
Formal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
––
––
––
––****************************************************************************
––ABSTRACT––
––
–– This package defines and handles types related to engineering value
––
––*–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––IDENTIFICATION––
–– PROJECT NAME : COLUMBUS VICOS
–– PRODUCT NAME : VCS
–– CI–NUMBER : 1234 950
–– OBJECT NAME : ADT_ENGINEERING_VALUE
––*–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––CONTENTS––
–– COMPILER : VADS V 6.0.3(c)
–– LANGUAGE : Ada
–– SPECIAL CONTENTS:
–– CHANGE HISTORY
–– V3.1 at Central Repository V2.2 (CGS V3 development)
–– creator: grotheer (on host vicos2s)
–– creation date: 11.07.94 17:14:56
–– comment:
–– NULL_ENGINEERING_VALUE added, COL–ERNO–CGS–SPR–1297
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V2.7 at ERNO ; VICOS development
–– creator: athmann (on host vicos_5)
–– creation date: 07.05.93 16:33:26
–– Define new type T_SCALAR_ENGINEERING_VALUE
––
–– V2.6 at ERNO ; VICOS development
–– creator: athmann (on host vicos_5)
–– creation date: 03.03.93 19:54:13
–– Version as delivered by SRO1216843b (IK ADTs)
––
–– V2.5 at ERNO ; VICOS development
–– creator: vicos (on host vicos_s)
–– creation date: 17.11.92 11:28:09
–– adts version 2.0.1: update acc. to PIRN VICOS–2028
–– V2.4 at ERNO ; VICOS development
–– creator: vicos (on host prime_1)
–– creation date: 18.09.92 11:59:08
–– modifications according to FINAL ICD REVIEW DNs (see list)
–– V2.3 at ERNO ; VICOS development
–– creator: vicos (on host vicos_s)
–– creation date: 28.07.92 09:28:51
–– Changes : editorial, exceptions, operation names
–– V2.2 at ERNO ; VICOS development
–– creator: vicos (on host vicos_8)
–– creation date: 20.07.92 10:00:21
–– General layout for ADTs acc. to TN COL_MBER_ZU1_TN_0026_92
–– END HISTORY
––****************************************************************************
––
with ADT_PACKING;
–– type T_BLOCK
with MPS_DEFINITIONS;
–– type STATE_CODE
package ADT_ENGINEERING_VALUE is
––––––––––––––––––––––––––––––
–– public types and constants
––––––––––––––––––––––––––––––
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
262 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
type T_ENGINEERING_VALUE_ALTERNATIVES is (
UNDEFINED,
STATE_CODE,
INT,
FLT,
STR);
–– The engineering value alternatives indicates if :
–– – the engineering value is not set–up
–– – the engineering value contains a state code
–– – the engineering value contains an integer
–– – the engineering value contains a float
–– – the engineering value contains a string
subtype T_SCALAR_ENGINEERING_VALUE_ALTERNATIVES is
T_ENGINEERING_VALUE_ALTERNATIVES range UNDEFINED .. FLT;
–– defines a subtype for scalar raw values (i.e. no strings)
MAX_CALIBRATED_STRING_LENGTH : constant := 256;
type T_CALIBRATED_STRING is
record
STR : STRING (1..MAX_CALIBRATED_STRING_LENGTH);
LENGTH : INTEGER range 0..MAX_CALIBRATED_STRING_LENGTH := 0;
end record;
–––––––––––––
–– adt type
–––––––––––––
type T_ENGINEERING_VALUE (
VALUE_ALTERNATIVE : T_ENGINEERING_VALUE_ALTERNATIVES := UNDEFINED) is
private;
–– A engineering value is composed of :
–– – an engineering value alternative,
–– – a state code, when alternative is STATE_CODE.
–– – an integer, when alternative is INT.
–– – a float, when alternative is FLT.
–– – a string, when alternative is STR.
NULL_ENGINEERING_VALUE : constant T_ENGINEERING_VALUE ;
type T_SCALAR_ENGINEERING_VALUE (
VALUE_ALTERNATIVE : T_SCALAR_ENGINEERING_VALUE_ALTERNATIVES := UNDEFINED)
is private;
–– A scalar engineering value is composed of :
–– – an engineering value alternative,
–– – a state code, when alternative is STATE_CODE.
–– – an integer, when alternative is INT.
–– – a float, when alternative is FLT.
––––––––––––––––––––
–– write operations
––––––––––––––––––––
procedure SET_ENGINEERING_VALUE_ALTERNATIVE (
OF_VALUE : in out T_ENGINEERING_VALUE;
WITH_ALTER : in T_ENGINEERING_VALUE_ALTERNATIVES);
–– DESCRIPTION
–– This procedure sets the engineering value alternative
–– of the given value.
–– EXCEPTIONS
–– VALUE_IS_CONSTRAINED :
–– – The provided engineering value is constrained and
–– the type can therefore not be changed.
–– DESCRIPTION (for all following write operations)
–– This procedure sets the current value of the specified
–– engineering value variable.
–– EXCEPTIONS (for all following write operations)
–– VALUE_TYPE_MISMATCH :
–– – The operation is invalid for the given value
–– of the engineering value alternative.
procedure SET_STATE_CODE_VALUE (
OF_VALUE : in out T_ENGINEERING_VALUE;
WITH_STATE_CODE : in MPS_DEFINITIONS.STATE_CODE);
procedure SET_INTEGER_VALUE (
OF_VALUE : in out T_ENGINEERING_VALUE;
WITH_INTEGER : in INTEGER);
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
263 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
procedure SET_FLOAT_VALUE (
OF_VALUE : in out T_ENGINEERING_VALUE;
WITH_FLOAT : in FLOAT);
procedure SET_STRING_VALUE (
OF_VALUE : in out T_ENGINEERING_VALUE;
WITH_STRING : in T_CALIBRATED_STRING);
––––– overloaded operations for T_SCALAR_ENGINEERING_VALUE ––––––––––––––––
procedure SET_ENGINEERING_VALUE_ALTERNATIVE (
OF_VALUE : in out T_SCALAR_ENGINEERING_VALUE;
WITH_ALTER : in T_SCALAR_ENGINEERING_VALUE_ALTERNATIVES);
–– DESCRIPTION
–– This procedure sets the engineering value alternative
–– of the given value.
–– EXCEPTIONS
–– VALUE_IS_CONSTRAINED :
–– – The provided engineering value is constrained and
–– the type can therefore not be changed.
–– DESCRIPTION (for all following write operations)
–– This procedure sets the current value of the specified
–– engineering value variable.
–– EXCEPTIONS (for all following write operations)
–– VALUE_TYPE_MISMATCH :
–– – The operation is invalid for the given value
–– of the engineering value alternative.
procedure SET_STATE_CODE_VALUE (
OF_VALUE : in out T_SCALAR_ENGINEERING_VALUE;
WITH_STATE_CODE : in MPS_DEFINITIONS.STATE_CODE);
procedure SET_INTEGER_VALUE (
OF_VALUE : in out T_SCALAR_ENGINEERING_VALUE;
WITH_INTEGER : in INTEGER);
procedure SET_FLOAT_VALUE (
OF_VALUE : in out T_SCALAR_ENGINEERING_VALUE;
WITH_FLOAT : in FLOAT);
–––––––––––––––––––
–– read operations
–––––––––––––––––––
function ALTERNATIVE (
OF_VALUE : T_ENGINEERING_VALUE)
return T_ENGINEERING_VALUE_ALTERNATIVES;
–– DESCRIPTION
–– This function returns the current alternative of
–– the specified engineering value variable.
–– EXCEPTIONS
–– None.
–– DESCRIPTION (for all following read operations)
–– This function returns the current value of
–– the specified engineering value variable.
–– EXCEPTIONS (for all following read operations)
–– VALUE_TYPE_MISMATCH :
–– the current alternative of the passed variable
–– and the type of the formal parameter mismatch.
function STATE_CODE_VALUE (
OF_VALUE : T_ENGINEERING_VALUE)
return MPS_DEFINITIONS.STATE_CODE;
function INTEGER_VALUE (
OF_VALUE : T_ENGINEERING_VALUE)
return INTEGER;
function FLOAT_VALUE (
OF_VALUE : T_ENGINEERING_VALUE)
return FLOAT;
function STRING_VALUE (
OF_VALUE : T_ENGINEERING_VALUE)
return T_CALIBRATED_STRING;
––––– overloaded operations for T_SCALAR_ENGINEERING_VALUE ––––––––––––––––
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
264 von/of: 662

Space Infrastructure
function ALTERNATIVE (
OF_VALUE : T_SCALAR_ENGINEERING_VALUE)
return T_SCALAR_ENGINEERING_VALUE_ALTERNATIVES;
–– DESCRIPTION
–– This function returns the current alternative of
–– the specified engineering value variable.
–– EXCEPTIONS
–– None.
–– DESCRIPTION (for all following read operations)
–– This function returns the current value of
–– the specified engineering value variable.
–– EXCEPTIONS (for all following read operations)
–– VALUE_TYPE_MISMATCH :
–– the current alternative of the passed variable
–– and the type of the formal parameter mismatch.
function STATE_CODE_VALUE (
OF_VALUE : T_SCALAR_ENGINEERING_VALUE)
return MPS_DEFINITIONS.STATE_CODE;
function INTEGER_VALUE (
OF_VALUE : T_SCALAR_ENGINEERING_VALUE)
return INTEGER;
function FLOAT_VALUE (
OF_VALUE : T_SCALAR_ENGINEERING_VALUE)
return FLOAT;
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–––––––––––––––––––––––––––––––––––––––––––––
–– ’type conversion’ (assignment) operations
–––––––––––––––––––––––––––––––––––––––––––––
function ASSIGN (SCALAR_VALUE: T_SCALAR_ENGINEERING_VALUE)
return T_ENGINEERING_VALUE;
–– DESCRIPTION
–– Assign a scalar value to a value of type T_ENGINEERING_VALUE
–– EXCEPTIONS
–– none
function ASSIGN (ENGINEERING_VALUE: T_ENGINEERING_VALUE)
return T_SCALAR_ENGINEERING_VALUE;
–– DESCRIPTION
–– Assign a raw value to a value of type
–– T_SCALAR_ENGINEERING_VALUE
–– EXCEPTIONS
–– VALUE_TYPE_MISMATCH
–– the type of the ENGINEERING_VALUE was STR
––––––––––––––––––––––
–– packing operations
––––––––––––––––––––––
procedure PACK (
VALUE : in T_ENGINEERING_VALUE;
BLOCK : in out ADT_PACKING.T_BLOCK);
–– DESCRIPTION
–– This procedure packs the specified engineering value variable into
–– a contiguous memory block.
–– EXCEPTIONS
–– None.
procedure UNPACK (
BLOCK : in out ADT_PACKING.T_BLOCK;
VALUE : out T_ENGINEERING_VALUE);
–– DESCRIPTION
–– This procedure unpacks the specified memory block into
–– an engineering value variable.
–– EXCEPTIONS
–– None.
––––– overloaded operations for T_SCALAR_ENGINEERING_VALUE ––––––––––––––––
procedure PACK (
VALUE : in T_SCALAR_ENGINEERING_VALUE;
BLOCK : in out ADT_PACKING.T_BLOCK);
–– DESCRIPTION
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
265 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–– This procedure packs the specified engineering value variable into
–– a contiguous memory block.
–– EXCEPTIONS
–– None.
procedure UNPACK (
BLOCK : in out ADT_PACKING.T_BLOCK;
VALUE : out T_SCALAR_ENGINEERING_VALUE);
–– DESCRIPTION
–– This procedure unpacks the specified memory block into
–– an engineering value variable.
–– EXCEPTIONS
–– None.
–––––––––––––––––––
–– exceptions
–––––––––––––––––––
VALUE_TYPE_MISMATCH : exception;
VALUE_IS_CONSTRAINED : exception;
private
type T_ENGINEERING_VALUE(
VALUE_ALTERNATIVE : T_ENGINEERING_VALUE_ALTERNATIVES := UNDEFINED) is
record
case VALUE_ALTERNATIVE is
when STATE_CODE =>
STATE_CODE_VALUE : MPS_DEFINITIONS.STATE_CODE;
when INT =>
INT_VALUE : INTEGER := 0;
when FLT =>
FLT_VALUE : FLOAT := 0.0;
when STR =>
STR_VALUE : T_CALIBRATED_STRING;
when others =>
null;
end case;
end record;
type T_SCALAR_ENGINEERING_VALUE(
VALUE_ALTERNATIVE : T_SCALAR_ENGINEERING_VALUE_ALTERNATIVES
:= UNDEFINED) is
record
case VALUE_ALTERNATIVE is
when STATE_CODE =>
STATE_CODE_VALUE : MPS_DEFINITIONS.STATE_CODE;
when INT =>
INT_VALUE : INTEGER := 0;
when FLT =>
FLT_VALUE : FLOAT := 0.0;
when others =>
null;
end case;
end record;
NULL_ENGINEERING_VALUE : constant T_ENGINEERING_VALUE :=
( VALUE_ALTERNATIVE => UNDEFINED ) ;
end ADT_ENGINEERING_VALUE;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
266 von/of: 662

Space Infrastructure
7.6.5 ADT ADU Description
Informal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
267 von/of: 662
A ADU Description is the set of information describing the format of the data acquired by VICOS. It is normally
predefined in the mission/configuration database, and loaded from the corresponding end–item, in test system
configuration and set–up phase. It is then supplied, together with the request for acquisition, by VICOS to the
dedicated SAS at test execution time.
A ADU Description is a composite type containing the following attributes :
– an ADU description alternative, which modifies the structure of this item;
– an database sid, which is the identifier allocated by the MPS when the corresponding end–item is
created;
– a private identifier, which is a identification number specific to VICOS and SASs, allowing reference
to this item without knowledge of the database sid;
– an SAS’s short name i.e. the one in charge of the data transfer (see EGSE Software);
– an acquisition rate, which indicates the frequency of reception of the corresponding ADU;
– a global address, indicating where to acquire the values (see Physical Address);
– an ADU data buffer size;
– a list of measurement references, if ADU is structured composed of :
– a mission database sid,
– a raw value alternative,
– a physical address;
– a list of item description, if ADU is unstructured composed of :
– a measurement sid,
– a location in the data buffer, in bits,
– a length in the data buffer, in bits,
– a ccsds identifier, if ADU is ccsds_packet.
A Table type is also provided, which allows to define indexed lists of this ADT.

Space Infrastructure
Formal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
––
–– ADT_ADU_DESCRIPTION
––
––****************************************************************************
––ABSTRACT––
––
–– This package is an abstract data type definition of the
–– ADU_DESCRIPTIONS
––
––*–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––IDENTIFICATION––
–– PROJECT NAME : CGS
–– PRODUCT NAME : TES
–– CI–NUMBER : 1216 843
–– OBJECT NAME : ADT_ADU_DESCRIPTION
––*–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––CONTENTS––
–– COMPILER : SunAda 1.1 /Alsys Ada 5.5.1
–– LANGUAGE : ADA
–– SPECIAL CONTENTS:
–– CHANGE HISTORY
–– PIRN 8065
–– creator: P.Hartmann
–– creation date: 23.06.99
–– comment: access to CCSDS header via measurements
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– PIRN 8051
–– creator: P.Hartmann
–– creation date: 31.03.99
–– comment: increase MAX_NBR_UNSTRUCTURED_ITEMS from 500 to 750
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– PIRN 8039
–– creator: P.Hartmann
–– creation date: 05.11.98
–– comment: add physical address flag for structured ADU’s
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– PIRN 7061
–– creator: P.Hartmann
–– creation date: 14.01.98
–– comment: increase MAX_NBR_UNSTRUCTURED_ITEMS from 250 to 500
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– PIRN 5016
–– creator: P.Hartmann
–– creation date: 17.04.97
–– comment: suppress ”pragma PACK (T__STRUCTURED_DESCRIPTION);”
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
268 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
269 von/of: 662
–– V16.1 at Central Repository at DASA RI
–– creator: tommy (on host aiv_tn2)
–– creation date: 09.12.96 16:55:59
–– comment:
–– access type added
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V4.4 at Central Repository at DASA RI (CGS V3 development)
–– creator: adt_1 (on host vicos2–3)
–– creation date: 15.06.95 14:35:29
–– comment:
–– Updated the type definition for T_ADU_DESCRIPTION to be inline with PIRN 3046
C
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V4.3 at Central Repository at DASA RI (CGS V3 development)
–– creator: adt_1 (on host vicos2–3)
–– creation date: 15.06.95 11:37:37
–– comment:
–– Build 2 baseline, PIRN 3041 1/D
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V3.0 at ERNO ; CGS engineering
–– creator: gehrke (on host mps2s–1)
–– creation date: 22.05.95 13:00:00
–– CGS V2 Build 2 baseline, PIRN 3041/C
––
–– END HISTORY
––
––****************************************************************************
––
with ADT_PACKING;
–– type T_BLOCK
with MPS_DEFINITIONS;
–– type SID
with VICOS_DEFINITIONS;
–– type T_NAME_STRING
–– type T_RAW_VALUE_ALTERNATIVES
–– type T_ADU_ALTERNATIVES
–– type T_PRIVATE_ID
with ADT_PHYSICAL_ADDRESS;
–– type T_PHYSICAL_ADDRESS
with ADT_CCSDS_PACKET;
–– MAX_PACKET_SIZE
–– CCSDS_HEADER+SIZE
package ADT_ADU_DESCRIPTION is
––––––––––––––––––––––––––––––
–– public types and constants
––––––––––––––––––––––––––––––
MAX_NBR_STRUCTURED_ITEMS : constant INTEGER := 100;

Space Infrastructure
MAX_NBR_UNSTRUCTURED_ITEMS : constant INTEGER := 750;
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
MAX_NBR_CCSDS_ITEMS : constant INTEGER := MAX_NBR_UNSTRUCTURED_ITEMS;
MAX_BINARY_BUFFER_SIZE : constant INTEGER :=
ADT_CCSDS_PACKET.MAX_PACKET_SIZE+ADT_CCSDS_PACKET.CCSDS_HEADER_SIZE+1;
–––––––––––––
–– adt types
–––––––––––––
type T_ADU_DESCRIPTION(ADU_TYPE : VICOS_DEFINITIONS.T_ADU_ALTERNATIVES :=
VICOS_DEFINITIONS.UNDEFINED) is private;
type T_A_ADU_DESCRIPTION is access T_ADU_DESCRIPTION;
––––––––––––––––––––
–– write operations
––––––––––––––––––––
procedure SET_ALTERNATIVE (
OF_ADU_DESCRIPTION : in out T_ADU_DESCRIPTION;
WITH_ALTERNATIVE : in VICOS_DEFINITIONS.T_ADU_ALTERNATIVES);
–– DESCRIPTION
–– This procedure sets the current alternative value of
–– the specified ADU description variable.
–– Setting the alternative to UNDEFINED internally clears
–– all fields as if the ADU_DESCRIPTION were empty
–– EXCEPTIONS
–– ADU_DESCRIPTION_IS_CONSTRAINED
–– Raised when trying to change the ADU description
–– in a constraint way
procedure SET_DB_SID (
OF_ADU_DESCRIPTION : in out T_ADU_DESCRIPTION;
WITH_DB_SID : in MPS_DEFINITIONS.SID);
–– DESCRIPTION
–– This procedure sets the current database sid value of
–– the specified ADU description variable.
–– EXCEPTIONS
–– SID_VALUE_ILLEGAL :
–– the passed sid has not a legal value, i.e. NULL_SID.
procedure SET_PRIVATE_ID (
OF_ADU_DESCRIPTION : in out T_ADU_DESCRIPTION;
WITH_PRIVATE_ID : in VICOS_DEFINITIONS.T_PRIVATE_ID);
–– DESCRIPTION
–– This procedure sets the current private identifier value of
–– the specified ADU description variable.
–– EXCEPTIONS
procedure SET_SAS_NAME (
OF_ADU_DESCRIPTION : in out T_ADU_DESCRIPTION;
WITH_SAS_NAME : in VICOS_DEFINITIONS.T_SAS_NAME);
–– DESCRIPTION
–– This procedure sets the current SAS short name value of
–– the specified ADU description variable.
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
270 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–– EXCEPTIONS
–– SAS_NAME_VALUE_ILLEGAL :
–– the passed name has not a legal value, i.e. EMPTY_NAME_STRING.
procedure SET_ACQUISITION_RATE (
OF_ADU_DESCRIPTION : in out T_ADU_DESCRIPTION;
WITH_ACQUISITION_RATE : in NATURAL);
–– DESCRIPTION
–– This procedure sets the current ADU acquisition rate value of
–– the specified ADU description variable.
–– EXCEPTIONS
procedure SET_GLOBAL_ADDRESS (
OF_ADU_DESCRIPTION : in out T_ADU_DESCRIPTION;
WITH_GLOBAL_ADDRESS : in out ADT_PHYSICAL_ADDRESS.T_PHYSICAL_ADDRESS);
–– DESCRIPTION
–– This procedure sets the global physical address of
–– the specified ADU description variable.
–– EXCEPTIONS
procedure SET_ITEMS_WITH_PHYSICAL_ADDRESS (
OF_ADU_DESCRIPTION : in out T_ADU_DESCRIPTION;
WITH_PYSICAL_ADDRESS : in BOOLEAN);
–– DESCRIPTION
–– This procedure sets the flag indicating for a structured ADU if
–– the items do have a physical address or not.
–– EXCEPTIONS
–– ADU_TYPE_MISMATCH
–– the ADU alternative is not a structured ADU
procedure SET_NBR_ITEMS (
OF_ADU_DESCRIPTION : in out T_ADU_DESCRIPTION;
WITH_NBR_ITEMS : in NATURAL);
–– DESCRIPTION
–– This procedure sets the current number of items of
–– the specified ADU description variable.
–– EXCEPTIONS
–– SIZE_ERROR
–– the passed number is bigger than the maximum contained items.
–– IS_UNDEFINED
–– the ADU alternative is undefined
procedure SET_ENDITEM_DESCRIPTION (
IN_ADU_DESCRIPTION : in out T_ADU_DESCRIPTION;
WITH_DB_SID : in MPS_DEFINITIONS.SID;
WITH_RAW_VALUE_TYPE : in VICOS_DEFINITIONS.
T_RAW_VALUE_ALTERNATIVES;
AT_INDEX : in POSITIVE;
WITH_PARAMETER_ADDRESS : in ADT_PHYSICAL_ADDRESS.
T_PHYSICAL_ADDRESS);
–– DESCRIPTION
–– This procedure sets the item sid in the specified
–– ADU description variable, at the specified position.
–– EXCEPTIONS
–– INDEX_ERROR :
–– – the specified position is bigger than MAX_NBR_STRUCTURED_ITEMS.
–– SID_VALUE_ILLEGAL :
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
271 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–– – the passed sid has not a legal value, i.e. NULL_SID.
–– ADU_TYPE_MISMATCH :
–– – the ADU alternative is not STRUCTURED.
–– SIZE_ERROR :
–– – the number of bytes needed to represent the values in the
–– ADU exceeds MAX_BINARY_BUFFER_SIZE
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
272 von/of: 662
procedure SET_ENDITEM_DESCRIPTION (
IN_ADU_DESCRIPTION : in out T_ADU_DESCRIPTION;
WITH_DB_SID : in MPS_DEFINITIONS.SID;
WITH_BIT_LOCATION : in NATURAL;
WITH_BIT_SIZE : in NATURAL;
WITH_PACKET_PART : in ADT_CCSDS_PACKET.T_PACKET_PART
:= ADT_CCSDS_PACKET.DATA;
AT_INDEX : in POSITIVE);
–– DESCRIPTION
–– This procedure sets the item description in the specified
–– ADU description variable, at the specified position.
–– EXCEPTIONS
–– INDEX_ERROR :
–– – the specified position is bigger than MAX_NBR_UNSTRUCTURED_ITEMS.
–– SID_VALUE_ILLEGAL :
–– – the passed sid has not a legal value, i.e. NULL_SID.
–– ADU_TYPE_MISMATCH :
–– – the ADU alternative is not UNSTRUCTURED or CCSDS_PACKET.
procedure SET_CCSDS_HEADER (
IN_ADU_DESCRIPTION : in out T_ADU_DESCRIPTION;
WITH_CCSDS_HEADER : in ADT_CCSDS_PACKET.T_CCSDS_HEADER);
–– DESCRIPTION
–– This procedure stores the ccsds primary header of the desired CCSDS
–– packet which should be put into the corresponding ADU
–– in the ADU description variable.
–– EXCEPTIONS
–– ADU_TYPE_MISMATCH :
–– the ADU alternative is not CCSDS_PACKET.
procedure SET_CCSDS_2ND_HEADER (
IN_ADU_DESCRIPTION : in out T_ADU_DESCRIPTION;
WITH_CCSDS_2ND_HEADER : in ADT_CCSDS_PACKET.T_CCSDS_SECONDARY_HEADER);
–– DESCRIPTION
–– This procedure stores the ccsds secondary header of the desired
–– CCSDS packet which should be put into the corresponding ADU
–– in the ADU description variable.
–– EXCEPTIONS
–– ADU_TYPE_MISMATCH :
–– the ADU alternative is not CCSDS_PACKET.
procedure SET_ADU_SIZE(
IN_ADU_DESCRIPTION : in out T_ADU_DESCRIPTION;
SIZE : in NATURAL);
–– DESCRIPTION
–– Set the size of the ADU in case it is unstructured
–– EXCEPTIONS
–– ADU_TYPE_MISMATCH :
–– the ADU alternative is not UNSTRUCTURED
–– SIZE_ERROR :

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–– the specified position is bigger than the maximum list size.
–––––––––––––––––––
–– read operations
–––––––––––––––––––
function DB_SID (
OF_ADU_DESCRIPTION : T_ADU_DESCRIPTION)
return MPS_DEFINITIONS.SID;
–– DESCRIPTION
–– This function returns the current database sid value of
–– the specified ADU description variable.
–– EXCEPTIONS
–– IS_UNDEFINED :
–– the alternative is UNDEFINED
function PRIVATE_ID (
OF_ADU_DESCRIPTION : T_ADU_DESCRIPTION)
return VICOS_DEFINITIONS.T_PRIVATE_ID;
–– DESCRIPTION
–– This function returns the current private identifier value of
–– the specified ADU description variable.
–– EXCEPTIONS
–– IS_UNDEFINED :
–– the alternative is UNDEFINED
function SAS_NAME (
OF_ADU_DESCRIPTION : T_ADU_DESCRIPTION)
return VICOS_DEFINITIONS.T_SAS_NAME;
–– DESCRIPTION
–– This function returns the current SAS short name value of
–– the specified ADU description variable.
–– EXCEPTIONS
–– IS_UNDEFINED :
–– the alternative is UNDEFINED
function ACQUISITION_RATE (
OF_ADU_DESCRIPTION : T_ADU_DESCRIPTION)
return NATURAL;
–– DESCRIPTION
–– This function returns the current ADU acquisition rate value of
–– the specified ADU description variable.
–– EXCEPTIONS
–– IS_UNDEFINED :
–– the alternative is UNDEFINED
function GLOBAL_ADDRESS (
OF_ADU_DESCRIPTION : in T_ADU_DESCRIPTION)
return ADT_PHYSICAL_ADDRESS.T_PHYSICAL_ADDRESS;
–– DESCRIPTION
–– This procedure returns the current global address value of
–– the specified ADU description variable.
–– EXCEPTIONS
–– IS_UNDEFINED :
–– the alternative is UNDEFINED
procedure GET_ENDITEM_DESCRIPTION (
OF_ADU_DESCRIPTION : in T_ADU_DESCRIPTION;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
273 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
DB_SID : out MPS_DEFINITIONS.SID;
RAW_VALUE_TYPE : out VICOS_DEFINITIONS.T_RAW_VALUE_ALTERNATIVES;
AT_INDEX : in POSITIVE;
PARAMETER_ADDRESS : out ADT_PHYSICAL_ADDRESS.T_PHYSICAL_ADDRESS);
–– DESCRIPTION
–– This procedure gets the enditem sid of the specified
–– ADU description variable, at the specified position.
–– EXCEPTIONS
–– INDEX_ERROR :
–– – the specified position is bigger than the list size.
–– ADU_TYPE_MISMATCH :
–– – the ADU alternative is not STRUCTURED.
–– IS_UNDEFINED :
–– – the alternative is UNDEFINED
procedure GET_ENDITEM_DESCRIPTION (
OF_ADU_DESCRIPTION : in T_ADU_DESCRIPTION;
DB_SID : out MPS_DEFINITIONS.SID;
BIT_LOCATION : out NATURAL;
BIT_SIZE : out NATURAL;
AT_INDEX : in POSITIVE);
procedure GET_ENDITEM_DESCRIPTION (
OF_ADU_DESCRIPTION : in T_ADU_DESCRIPTION;
DB_SID : out MPS_DEFINITIONS.SID;
BIT_LOCATION : out NATURAL;
BIT_SIZE : out NATURAL;
PACKET_PART : out ADT_CCSDS_PACKET.T_PACKET_PART;
AT_INDEX : in POSITIVE);
–– DESCRIPTION
–– This procedure gets the enditem description of the specified
–– ADU description variable, at the specified position.
–– the first version is kept for compatibility reason but
–– should not be used as now, measurements from CCSDS packets
–– can reference data in the headers/checksum part of the packet
–– EXCEPTIONS
–– INDEX_ERROR :
–– – the specified position is bigger than the list size.
–– ADU_TYPE_MISMATCH :
–– – the ADU alternative is not UNSTRUCTURED or CCSDS_PACKET.
–– IS_UNDEFINED :
–– – the alternative is UNDEFINED
function CCSDS_HEADER (
IN_ADU_DESCRIPTION : T_ADU_DESCRIPTION)
return ADT_CCSDS_PACKET.T_CCSDS_HEADER;
–– DESCRIPTION
–– This procedure returns the ccsds primary header of the desired
–– CCSDS packet which should be put into the corresponding ADU
–– in the ADU description variable.
–– EXCEPTIONS
–– ADU_TYPE_MISMATCH :
–– the ADU alternative is not CCSDS_PACKET.
function CCSDS_2ND_HEADER (
IN_ADU_DESCRIPTION : T_ADU_DESCRIPTION)
return ADT_CCSDS_PACKET.T_CCSDS_SECONDARY_HEADER;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
274 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–– DESCRIPTION
–– This procedure returns the ccsds secondary header of the
–– desired CCSDS
–– packet which should be put into the corresponding ADU
–– in the ADU description variable.
–– EXCEPTIONS
–– ADU_TYPE_MISMATCH :
–– the ADU alternative is not CCSDS_PACKET.
function ALTERNATIVE(ADU_DESCRIPTION : in T_ADU_DESCRIPTION)
return VICOS_DEFINITIONS.T_ADU_ALTERNATIVES;
–– DESCRIPTION
–– This function returns the current alternative of
–– the specified ADU description variable.
–– EXCEPTIONS
–– IS_UNDEFINED :
–– the alternative is UNDEFINED
function ITEMS_WITH_PHYSICAL_ADDRESS(ADU_DESCRIPTION : in T_ADU_DESCRIPTION)
return BOOLEAN;
–– DESCRIPTION
–– return the flag indicating for a structured ADU if the items do
–– have a physical address or not.
–– EXCEPTIONS :
–– ADU_TYPE_MISMATCH :
–– the ADU alternative is not a structured ADU
function NBR_ITEMS(ADU_DESCRIPTION : in T_ADU_DESCRIPTION)
return NATURAL;
–– DESCRIPTION
–– return number of items in ADU
–– EXCEPTIONS :
–– IS_UNDEFINED :
–– the alternative is UNDEFINED
function ADU_SIZE(ADU_DESCRIPTION : in T_ADU_DESCRIPTION)
return NATURAL;
–– DESCRIPTION
–– return size of the ADU
–– EXCEPTIONS :
–– ADU_TYPE_MISMATCH :
–– the ADU alternative is not UNSTRUCTURED
–– IS_UNDEFINED :
–– the alternative is UNDEFINED
function INDEX(
ADU_DESCRIPTION : in T_ADU_DESCRIPTION;
SID : in MPS_DEFINITIONS.SID)
return NATURAL;
–– DESCRIPTION
–– return the index in the ADU value list of a value with SID
–– EXCEPTIONS :
–– ADU_TYPE_MISMATCH :
–– the ADU alternative is not STRUCTURED or UNSTRUCTURED
–– ITEM_NOT_FOUND :
–– no enditem description with the given SID
–– IS_UNDEFINED :
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
275 von/of: 662

Space Infrastructure
–– the alternative is UNDEFINED
––––––––––––––––––––––
–– packing operations
––––––––––––––––––––––
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
procedure PACK (
ADU_DESCRIPTION : in T_ADU_DESCRIPTION;
BLOCK : in out ADT_PACKING.T_BLOCK);
–– DESCRIPTION
–– This procedure packs the specified ADU description variable into
–– a contiguous memory block.
–– EXCEPTIONS
procedure UNPACK (
BLOCK : in out ADT_PACKING.T_BLOCK;
ADU_DESCRIPTION : out T_ADU_DESCRIPTION);
–– DESCRIPTION
–– This procedure unpacks the specified memory block into
–– a ADU description variable.
–– EXCEPTIONS
function SIZE_NEEDED (
VALUE : T_ADU_DESCRIPTION )
return ADT_PACKING.T_PACK_INDEX;
–– DESCRIPTION
–– This function calculates the actual size needed for packing the supplied
–– VALUE
–– EXCEPTIONS
procedure DEALLOCATE(ADU_DESC : in out T_A_ADU_DESCRIPTION);
–– DESCRIPTION
–– free memory allocated by new(T_ADU_DESCRIPTION)
–– EXCEPTIONS
––
–––––––––––––––––––
–– exceptions
–––––––––––––––––––
SID_VALUE_ILLEGAL : exception;
SAS_NAME_VALUE_ILLEGAL : exception;
ADU_TYPE_MISMATCH : exception;
INDEX_ERROR : exception;
ITEM_NOT_FOUND : exception;
SIZE_ERROR : exception;
ADU_DESCRIPTION_IS_CONSTRAINED : exception;
IS_UNDEFINED : exception;
NOT_CREATED : exception;
private
type T_STRUCTURED_DESCRIPTION is
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
276 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
record
SID : MPS_DEFINITIONS.SID;
RAW_VALUE_TYPE : VICOS_DEFINITIONS.T_RAW_VALUE_ALTERNATIVES
:= VICOS_DEFINITIONS.UNDEFINED;
PHYSICAL_ADDRESS : ADT_PHYSICAL_ADDRESS.T_PHYSICAL_ADDRESS;
end record;
type T_STRUCTURED_DESCRIPTIONS is array (1 .. MAX_NBR_STRUCTURED_ITEMS)
of T_STRUCTURED_DESCRIPTION;
type T_UNSTRUCTURED_DESCRIPTION is
record
SID : MPS_DEFINITIONS.SID;
LOCATION : NATURAL;
LENGTH : NATURAL;
PACKET_PART : ADT_CCSDS_PACKET.T_PACKET_PART;
end record;
type T_UNSTRUCTURED_DESCRIPTIONS is array (1 .. MAX_NBR_UNSTRUCTURED_ITEMS)
of T_UNSTRUCTURED_DESCRIPTION;
subtype T_CCSDS_DESCRIPTION is T_UNSTRUCTURED_DESCRIPTION;
type T_CCSDS_DESCRIPTIONS is array (1..MAX_NBR_CCSDS_ITEMS)
of T_CCSDS_DESCRIPTION;
type T_ADU_DESCRIPTION(ADU_TYPE : VICOS_DEFINITIONS.T_ADU_ALTERNATIVES :=
VICOS_DEFINITIONS.UNDEFINED) is
record
DB_SID : MPS_DEFINITIONS.SID;
PRIVATE_ID : VICOS_DEFINITIONS.T_PRIVATE_ID;
SAS_NAME : VICOS_DEFINITIONS.T_SAS_NAME;
ACQUISITION_RATE : NATURAL;
GLOBAL_ADDRESS : ADT_PHYSICAL_ADDRESS.T_PHYSICAL_ADDRESS;
case ADU_TYPE is
when VICOS_DEFINITIONS.STRUCTURED =>
ITEMS_WITH_PHYSICAL_ADDRESS : BOOLEAN := TRUE;
NBR_STRUCTURED_ITEMS : NATURAL := 0;
STRUCTURED_DESCRIPTIONS : T_STRUCTURED_DESCRIPTIONS;
STRUCTURED_BUFFER_SIZE : NATURAL := 0;
when VICOS_DEFINITIONS.UNSTRUCTURED =>
NBR_UNSTRUCTURED_ITEMS : NATURAL := 0;
UNSTRUCTURED_DESCRIPTIONS: T_UNSTRUCTURED_DESCRIPTIONS;
BUFFER_SIZE : NATURAL := 0;
when VICOS_DEFINITIONS.CCSDS_PACKET =>
CCSDS_HEADER : ADT_CCSDS_PACKET.T_CCSDS_HEADER;
CCSDS_SECONDARY_HEADER : ADT_CCSDS_PACKET.T_CCSDS_SECONDARY_HEADER;
NBR_CCSDS_ITEMS : NATURAL := 0;
CCSDS_DESCRIPTIONS : T_CCSDS_DESCRIPTIONS;
when VICOS_DEFINITIONS.UNDEFINED =>
null;
end case;
end record;
end ADT_ADU_DESCRIPTION;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
277 von/of: 662

Space Infrastructure
7.6.6 ADT ADU
Informal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
278 von/of: 662
An ADU is the standardized format in which any measurement is received by VICOS. It is a packet of measurement
values which are packed according to the list given in the corresponding ADU Description. ADUs are generated
by SASs and delivered to VICOS together with an ADU header allowing to identify the initial request
for acquisition.
A ADU is a composite type containing the following attributes :
– an ADU alternative, which modifies the structure of this item;
– an database sid, which is the identifier allocated by the MPS when the corresponding ADU Description
end–item is created;
– a time tag, indicating when the values have been acquired;
– a sequence number, which indicates the number of ADUs, with this sid, already acquired, when required
cyclically;
– a data interruption flag, which means, when set to TRUE, that for some reasons, SAS could not acquire
the corresponding data, in the time between the last ADU sent to VICOS and the current one.
VICOS generates then an error message and does not apply the delta monitoring, i.e. it does not
check values against delta limits.
– an SAS’s short name i.e. the one in charge of the data transfer (see EGSE Software);
– an ADU data buffer size;
– a list of item values, if ADU is structured composed of :
– an index,
– a value (see Raw Value),
– a measurement values byte buffer, if ADU is unstructured;
– a telemetry packet, if ADU is ccsds_packet.
A Table type is also provided, which allows to define indexed lists of this ADT.

Space Infrastructure
Formal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
––
–– ADT_ADU
––
––****************************************************************************
––ABSTRACT––
––
–– This package defines an abstract data type for ADUs
––
––*–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––IDENTIFICATION––
–– PROJECT NAME : CGS
–– PRODUCT NAME : TES
–– CI–NUMBER : 1216 843
–– OBJECT NAME : VICOS_ADTS
––*–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
279 von/of: 662
––CONTENTS––
–– COMPILER : SunAda 1.1 / Alsys Ada 5.5.1
–– LANGUAGE : ADA
–– SPECIAL CONTENTS:
–– CHANGE HISTORY
–– PIRN 8070
–– creator: P.Hartmann
–– creation date: 23.06.99
–– comment: access to CCSDS header via measurements
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V16.3 at Central Repository at DASA RI
–– creator: hartmann (on host aiv_2)
–– creation date: 16.12.96 13:46:08
–– comment:
–– add comments for UNPACK2
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V16.2 at Central Repository at DASA RI
–– creator: hartmann (on host aiv_2)
–– creation date: 16.12.96 13:18:30
–– comment:
–– 1/ GET_RAW_VALUE : make the VALUE –in out– (instead of –out–) and add out
parameter LENGTH (for structured ADU)
–– 2/ remove NUMBER_OF_BITS from functions RAW_VALUE and RAW_CCSDS_VALUE
returning SINGLE_FLOAT
–– 3/ change name for RAW_VALUE and GET_RAW_VALUE to RAW_UNSTRUCTURED_VALUE and
GET_RAW_UNSTRUCTURED_VALUE (for unstructured ADU)
––
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V16.1 at Central Repository at DASA RI
–– creator: tommy (on host aiv_tn2)
–– creation date: 09.12.96 16:55:14
–– comment:
–– Fast unpack, access type , extract operation added
––

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V4.4 at Central Repository at DASA RI (CGS V3 development)
–– creator: adt_1 (on host vicos2–3)
–– creation date: 22.06.95 09:19:35
–– comment:
–– Build 2 baseline
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V3.1 at CC ;
–– creator: Tommy Jakobsen
–– creation date: 13.06.95 10:00:00
–– Build 2 baseline, PIRN 3042
–– New definition of T_ADU in private part
–– Included missing function raw_value for U_INT
–– Updated description of some functions
––
–– V3.0 at ERNO ; CGS engineering
–– creator: gehrke (on host mps2s–1)
–– creation date: 19.05.95 10:00:00
–– Build 2 baseline, PIRN 3042
––
–– V2.10 at ERNO ; VICOS development
–– creator: athmann (on host vicos_5)
–– creation date: 28.07.93 12:53:11
–– Set default values for address information for private types
––
–– V2.9 at ERNO ; VICOS development
–– creator: athmann (on host vicos_5)
–– creation date: 03.03.93 20:00:14
–– Version as delivered by SRO1216843b (IK ADTs)
––
–– V2.8 at ERNO ; VICOS development
–– creator: athmann (on host vicos_5)
–– creation date: 15.01.93 15:23:11
–– re–include ADT_type description
–– V2.7 at ERNO ; VICOS development
–– creator: athmann (on host vicos_5)
–– creation date: 08.12.92 20:01:29
–– update comments / descriptions
–– V2.6 at ERNO ; VICOS development
–– creator: vicos (on host vicos_s)
–– creation date: 17.11.92 11:20:00
–– adts version 2.0.1: update acc. to PIRN VICOS–2034
–– V2.5 at ERNO ; VICOS development
–– creator: vicos (on host prime_1)
–– creation date: 18.09.92 11:55:17
–– modifications according to FINAL ICD REVIEW DNs (see list)
–– V2.4 at ERNO ; VICOS development
–– creator: vicos (on host vicos_8)
–– creation date: 21.07.92 07:59:31
–– Naming of CGS_CALENDAR changed to VICOS_CALENDAR
–– V2.3 at ERNO ; VICOS development
–– creator: maron (on host vicos_6)
–– creation date: 20.07.92 15:31:10
–– VCS–spadm & COL–MBER–ZU1–TN–0026/92
––
–– END HISTORY
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
280 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
––
––****************************************************************************
––
with MPS_DEFINITIONS;
with VICOS_DEFINITIONS;
with CGS_CALENDAR;
with NUMERIC_TYPES;
with ADT_PACKING;
with ADT_CCSDS_PACKET;
with ADT_ADU_DESCRIPTION;
package ADT_ADU is
––––––––––––––––––––––––––––––––––––
–– public types and constants types
––––––––––––––––––––––––––––––––––––
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
281 von/of: 662
MAX_NBR_STRUCTURED_ITEMS : constant integer:=
ADT_ADU_DESCRIPTION.MAX_NBR_STRUCTURED_ITEMS;
MAX_BINARY_BUFFER_SIZE : constant integer
:= ADT_ADU_DESCRIPTION.MAX_BINARY_BUFFER_SIZE;
subtype T_BINARY_BUFFER_SIZE is INTEGER range 0 .. MAX_BINARY_BUFFER_SIZE;
subtype T_NBR_STRUCTURED_ITEMS is INTEGER range 0 .. MAX_NBR_STRUCTURED_ITEMS;
type T_BINARY_BUFFER is array (T_BINARY_BUFFER_SIZE range ) of
NUMERIC_TYPES.UNSIGNED_INTEGER8;
pragma PACK(T_BINARY_BUFFER);
–––––––––––––––––––––––
–– adt types
–––––––––––––––––––––––
type T_ADU(ALTERNATIVE : VICOS_DEFINITIONS.T_ADU_ALTERNATIVES :=
VICOS_DEFINITIONS.UNDEFINED) is private;
–– An ADU is composed of :
–– – an ADU alternative,
–– – an identifier ( MDB sid),
–– – a time–tag,
–– – a sequence counter,
–– – a data interruption flag,
–– – an SAS short name,
–– – a list of measurement sids and values if ADU is structured,
–– – an array of bytes containing meas. values if ADU is unstructured,
–– – a TM packet, if ADU is a CCSDS packet,
type T_A_ADU is access T_ADU;
–––––––––––––––––––––––
–– Construct operation
–––––––––––––––––––––––
procedure CONSTRUCT( ADU : in out T_ADU;
DESCRIPTION : in ADT_ADU_DESCRIPTION.T_ADU_DESCRIPTION);

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
282 von/of: 662
–– DESCRIPTION
–– this operation initially sets the ADU alternative
–– and the SID to the values defined in the description
–– the ADU is cleared, i.e. all datafields are set to zero
–– and the sequence count is set to zero and the
–– DATA_INTERRUPTION is reset.
–– WARNING: There is no internal check whether or not the
–– ADU is currently ”in use”.
–– EXCEPTIONS:
–– ADU_TYPE_MISMATCH : the input adu’s constraint contradicts the adu type of
description
–– SIZE_ERROR : there is not enough space in the adu for all enditems
–––––––––––––––––––––
–– Write Operations
–––––––––––––––––––––
procedure SET_ALTERNATIVE(ADU : in out T_ADU;
ALTERNATIVE : in VICOS_DEFINITIONS.T_ADU_ALTERNATIVES);
–– DESCRIPTION
–– Set the alternative of the ADU; must be set before values are
–– written to the ADU.
–– EXCEPTIONS
–– CONSTRAINT_ERROR : the alternative is already set
procedure SET_TIME_TAG(ADU : in out T_ADU;
LOCAL_TIME : in CGS_CALENDAR.CGS_DATE_AND_TIME;
SMT : in CGS_CALENDAR.CGS_DATE_AND_TIME);
–– DESCRIPTION
–– Sets the time tag of the ADU
–– EXCEPTIONS
–– none
procedure SET_SAS_NAME(ADU : in out T_ADU;
SAS_NAME : in VICOS_DEFINITIONS.T_SAS_NAME);
–– DESCRIPTION
–– This procedure sets the short name of the SAS in charge of
–– the specified ADU variable
–– EXCEPTIONS
–– None
procedure SET_SEQUENCE_NUMBER(ADU : in out T_ADU;
SEQUENCE_NUMBER : in NATURAL);
–– DESCRIPTION
–– Sets the sequence number of the ADU
–– EXCEPTIONS
–– – none
procedure SET_DATA_INTERRUPTION(ADU : in out T_ADU);
–– DESCRIPTION
–– Sets the Data Interruption flag for the ADU
–– EXCEPTIONS
–– none
procedure RESET_DATA_INTERRUPTION(ADU : in out T_ADU);
–– DESCRIPTION

Space Infrastructure
–– Resets the Data Interruption flag for the ADU
–– EXCEPTIONS
–– – none
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
procedure SET_RAW_VALUE(ADU : in out T_ADU;
INDEX : in T_NBR_STRUCTURED_ITEMS;
VALUE : in NUMERIC_TYPES.UNSIGNED_INTEGER32);
–– DESCRIPTION
–– Sets a raw value for an STRUCTURED ADU at the given index
–– with an unsigned value if the corresponding RAW_VALUE_ALTERNATIVE
–– in the ADU description was U_INT
–– EXCEPTIONS:
–– ADU_TYPE_MISMATCH
–– The ADU alternative is not STRUCTURED
–– INDEX_ERROR
–– The index is not in the range 1 .. NBR_RAW_VALUES(ADU)
–– RAW_VALUE_TYPE_MISMATCH
–– The RAW_VALUE on this index is not U_INT
procedure SET_RAW_VALUE(ADU : in out T_ADU;
INDEX : in T_NBR_STRUCTURED_ITEMS;
VALUE : in NUMERIC_TYPES.INTEGER32);
–– DESCRIPTION
–– Sets a raw value for an STRUCTURED ADU at the given index
–– with an unsigned value if the corresponding RAW_VALUE_ALTERNATIVE
–– in the ADU description was INT
–– EXCEPTIONS:
–– ADU_TYPE_MISMATCH
–– The ADU alternative is not STRUCTURED
–– INDEX_ERROR
–– The index is not in the range 1 .. NBR_RAW_VALUES(ADU)
–– RAW_VALUE_TYPE_MISMATCH
–– The RAW_VALUE on this index is not INT
procedure SET_RAW_VALUE(ADU : in out T_ADU;
INDEX : in T_NBR_STRUCTURED_ITEMS;
VALUE : in NUMERIC_TYPES.SINGLE_FLOAT);
–– DESCRIPTION
–– Sets a raw value for an STRUCTURED ADU at the given index
–– with an unsigned value if the corresponding RAW_VALUE_ALTERNATIVE
–– in the ADU description was FLOAT_EGSE
–– EXCEPTIONS:
–– ADU_TYPE_MISMATCH
–– The ADU alternative is not STRUCTURED
–– INDEX_ERROR
–– The index is not in the range 1 .. NBR_RAW_VALUES(ADU)
–– RAW_VALUE_TYPE_MISMATCH
–– The RAW_VALUE onm this index is not FLOAT_EGSE
procedure SET_RAW_VALUE(ADU : in out T_ADU;
INDEX : in T_NBR_STRUCTURED_ITEMS;
VALUE : in STRING);
–– DESCRIPTION
–– Sets a raw value for an STRUCTURED ADU at the given index
–– with an unsigned value if the corresponding RAW_VALUE_ALTERNATIVE
–– in the ADU description was BYTE_STREAM
–– EXCEPTIONS:
–– ADU_TYPE_MISMATCH
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
283 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–– The ADU alternative is not STRUCTURED
–– INDEX_ERROR
–– The index is not in the range 1 .. NBR_RAW_VALUES(ADU)
–– RAW_VALUE_TYPE_MISMATCH
–– The RAW_VALUE on this index is not BYTE_STREAM
procedure SET_BINARY_BUFFER(ADU : in out T_ADU;
BUFFER : in T_BINARY_BUFFER);
–– DESCRIPTION
–– Writes the binary data to the unstructured ADU
–– EXCEPTIONS
–– ADU_TYPE_MISMATCH
–– The ADU alternative is not UNSTRUCTURED
–– SIZE_ERROR
–– The size of the buffer differs from the binary
–– buffer size of the ADU
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
284 von/of: 662
procedure SET_CCSDS_PACKET(ADU : in out T_ADU;
PACKET : in ADT_CCSDS_PACKET.T_CCSDS_PACKET);
–– DESCRIPTION
–– Writes a complet CCSDS packet to the ADU
–– EXCEPTIONS
–– ADU_TYPE_MISMATCH
–– The ADU alternative is not CCSDS_PACKET
–––––––––––––––––––––
–– Read Operations
–––––––––––––––––––––
function IS_DATA_INTERRUPTION(ADU : in T_ADU) return BOOLEAN;
–– DESCRIPTION
–– Returns TRUE if the DATA_INTERRUPR flag is set,
–– FALSE otherwise
–– EXCEPTIONS
function ID(ADU: in T_ADU) return MPS_DEFINITIONS.SID;
–– DESCRIPTION
–– Get the Identifier of the ADU
–– EXCEPTIONS
function LOCAL_TIME_TAG(ADU: in T_ADU) return CGS_CALENDAR.CGS_DATE_AND_TIME;
function SMT_TIME_TAG(ADU: in T_ADU) return CGS_CALENDAR.CGS_DATE_AND_TIME;
–– DESCRIPTION
–– Get the time tag of the ADU
–– EXCEPTIONS
function SEQUENCE_NUMBER(ADU: in T_ADU) return NATURAL;
–– DESCRIPTION
–– Get the sequence number of the ADU
–– EXCEPTIONS
function SAS_NAME(ADU: in T_ADU) return VICOS_DEFINITIONS.T_SAS_NAME;
–– DESCRIPTION

Space Infrastructure
–– Get the SAS Name of the ADU
–– EXCEPTIONS
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
285 von/of: 662
function ALTERNATIVE(ADU : in T_ADU) return VICOS_DEFINITIONS.T_ADU_ALTERNATIVES;
–– DESCRIPTION
–– Get the alternative of the ADU
–– EXCEPTIONS
function NBR_RAW_VALUES(adu : in t_adu) return T_NBR_STRUCTURED_ITEMS;
–– DESCRIPTION
–– Get the number of raw values contained in the structured ADU
–– EXCEPTIONS
–– ADU_TYPE_MISMATCH
–– The ADU alternative is not STRUCTURED
function BINARY_BUFFER_SIZE(ADU : in T_ADU) return T_BINARY_BUFFER_SIZE;
–– DESCRIPTION
–– Get the size of the binary data from a structured ADU
–– EXCEPTIONS
–– ADU_TYPE_MISMATCH
–– The ADU alternative is not UNSTRUCTURED
function RAW_VALUE(ADU : in T_ADU;
INDEX : in T_NBR_STRUCTURED_ITEMS) return
NUMERIC_TYPES.UNSIGNED_INTEGER32;
–– DESCRIPTION
–– Get a raw value from a structured ADU
–– EXCEPTIONS
–– ADU_TYPE_MISMATCH
–– The ADU alternative is not STRUCTURED
–– INDEX_ERROR
–– The index is not in the range 1 .. NBR_RAW_VALUES(ADU)
–– RAW_VALUE_TYPE_MISMATCH
–– The RAW_VALUE is not U_INT
function RAW_VALUE(ADU : in T_ADU;
INDEX : in T_NBR_STRUCTURED_ITEMS) return NUMERIC_TYPES.INTEGER32;
–– DESCRIPTION
–– Get a raw value from a structured ADU
–– EXCEPTIONS
–– ADU_TYPE_MISMATCH
–– The ADU alternative is not STRUCTURED
–– INDEX_ERROR
–– The index is not in the range 1 .. NBR_RAW_VALUES(ADU)
–– RAW_VALUE_TYPE_MISMATCH
–– The RAW_VALUE is not INT
function RAW_VALUE(ADU : in T_ADU;
INDEX : in T_NBR_STRUCTURED_ITEMS) return
NUMERIC_TYPES.SINGLE_FLOAT;
–– DESCRIPTION
–– Get a raw value from a structured ADU
–– EXCEPTIONS
–– ADU_TYPE_MISMATCH
–– The ADU alternative is not STRUCTURED

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–– INDEX_ERROR
–– The index is not in the range 1 .. NBR_RAW_VALUES(ADU)
–– RAW_VALUE_TYPE_MISMATCH
–– The RAW_VALUE is not FLOAT_EGSE
function RAW_VALUE(ADU : in T_ADU;
INDEX : in T_NBR_STRUCTURED_ITEMS) return STRING;
–– DESCRIPTION
–– Get a raw value from a structured ADU
–– EXCEPTIONS
–– ADU_TYPE_MISMATCH
–– The ADU alternative is not STRUCTURED
–– INDEX_ERROR
–– The index is not in the range 1 .. NBR_RAW_VALUES(ADU)
–– RAW_VALUE_TYPE_MISMATCH
–– The RAW_VALUE is not BYTE_STREAM
procedure GET_RAW_VALUE(ADU : in T_ADU;
INDEX : in T_NBR_STRUCTURED_ITEMS;
LENGTH : out NATURAL;
VALUE : in out MPS_DEFINITIONS.T_RAW_STRING);
–– DESCRIPTION
–– Get a raw value from a structured ADU
–– EXCEPTIONS
–– ADU_TYPE_MISMATCH
–– The ADU alternative is not STRUCTURED
–– INDEX_ERROR
–– The index is not in the range 1 .. NBR_RAW_VALUES(ADU)
–– RAW_VALUE_TYPE_MISMATCH
–– The RAW_VALUE is not BYTE_STREAM
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
286 von/of: 662
–– new raw_value operations
function RAW_UNSTRUCTURED_VALUE
(ADU : in T_ADU;
BIT_LOCATION : in NATURAL;
NUMBER_OF_BITS : in NATURAL) return NUMERIC_TYPES.UNSIGNED_INTEGER32;
function RAW_UNSTRUCTURED_VALUE
(ADU : in T_ADU;
BIT_LOCATION : in NATURAL;
NUMBER_OF_BITS : in NATURAL) return NUMERIC_TYPES.INTEGER32;
function RAW_UNSTRUCTURED_VALUE
(ADU : in T_ADU;
BIT_LOCATION : in NATURAL) return NUMERIC_TYPES.SINGLE_FLOAT;
procedure GET_RAW_UNSTRUCTURED_VALUE
(ADU : in T_ADU;
BIT_LOCATION : in NATURAL;
NUMBER_OF_BYTES : in NATURAL;
VALUE : in out MPS_DEFINITIONS.T_RAW_STRING);
–– DESCRIPTION
–– Get a raw value from an unstructured ADU
–– EXCEPTIONS
–– ADU_TYPE_MISMATCH
–– The ADU alternative is not UNSTRUCTURED
–– DATA_LENGTH_ERROR
–– raised if the offset + the length of the value is
–– exceeding the length of the packet

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–– new raw_value operations
function RAW_CCSDS_VALUE
(ADU : in T_ADU;
BIT_LOCATION : in NATURAL;
NUMBER_OF_BITS : in NATURAL;
PACKET_PART : in ADT_CCSDS_PACKET.T_PACKET_PART
:= ADT_CCSDS_PACKET.DATA)
return NUMERIC_TYPES.UNSIGNED_INTEGER32;
function RAW_CCSDS_VALUE
(ADU : in T_ADU;
BIT_LOCATION : in NATURAL;
NUMBER_OF_BITS : in NATURAL;
PACKET_PART : in ADT_CCSDS_PACKET.T_PACKET_PART
:= ADT_CCSDS_PACKET.DATA)
return NUMERIC_TYPES.INTEGER32;
function RAW_CCSDS_VALUE
(ADU : in T_ADU;
BIT_LOCATION : in NATURAL;
PACKET_PART : in ADT_CCSDS_PACKET.T_PACKET_PART
:= ADT_CCSDS_PACKET.DATA)
return NUMERIC_TYPES.SINGLE_FLOAT;
procedure GET_RAW_CCSDS_VALUE
(ADU : in T_ADU;
BIT_LOCATION : in NATURAL;
NUMBER_OF_BYTES : in NATURAL;
VALUE : in out MPS_DEFINITIONS.T_RAW_STRING;
PACKET_PART : in ADT_CCSDS_PACKET.T_PACKET_PART
:= ADT_CCSDS_PACKET.DATA);
–– DESCRIPTION
–– Get a raw value from a CCSDS ADU
–– EXCEPTIONS
–– ADU_TYPE_MISMATCH
–– The ADU alternative is not CCSDS
–– DATA_LENGTH_ERROR
–– raised if the offset + the length of the value is
–– exceeding the length of the packet
function RAW_VALUE_TYPE(ADU : in T_ADU; INDEX : T_NBR_STRUCTURED_ITEMS)
return VICOS_DEFINITIONS.T_RAW_VALUE_ALTERNATIVES;
–– DESCRIPTION
–– Get a raw value type from a structured ADU
–– EXCEPTIONS
–– ADU_TYPE_MISMATCH
–– The ADU alternative is not STRUCTURED
–– INDEX_ERROR
–– The index is not in the range 1 .. NBR_RAW_VALUES(ADU)
procedure GET_BINARY_BUFFER(ADU : in T_ADU;
BUFFER : in out T_BINARY_BUFFER);
–– DESCRIPTION
–– Get the binary data from a structured ADU
–– EXCEPTIONS
–– ADU_TYPE_MISMATCH
–– The ADU alternative is not UNSTRUCTURED
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
287 von/of: 662

Space Infrastructure
–– SIZE_ERROR
–– The size of the buffer differs from the binary
–– buffer size of the ADU
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
288 von/of: 662
function CCSDS_PACKET(ADU : in T_ADU) return ADT_CCSDS_PACKET.T_CCSDS_PACKET;
–– DESCRIPTION
–– Get a complete CCSDS packet from a
–– structured ADU
–– EXCEPTIONS
–– ADU_TYPE_MISMATCH
–– The ADU alternative is not CCSDS_PACKET
procedure DEALLOCATE(ADU : in out T_A_ADU);
–– DESCRIPTION
–– free memory allocated by new(T_ADU)
–– EXCEPTIONS
––
–––––––––––––––––––––––
–– packing and unpacking operations
–––––––––––––––––––––––
procedure PACK(ADU : in T_ADU;
BLOCK : in out ADT_PACKING.T_BLOCK);
–– DESCRIPTION
–– Pack an ADU into a T_BLOCK; The block must have been
–– initialised before
–– EXCEPTIONS
procedure UNPACK(BLOCK : in out ADT_PACKING.T_BLOCK;
ADU : out T_ADU);
–– DESCRIPTION
–– Unpack a block into an ADU
–– EXCEPTIONS
procedure UNPACK2(BLOCK : in out ADT_PACKING.T_BLOCK;
ADU : in out T_ADU);
–– DESCRIPTION
–– Unpack a block into an ADU
–– Defining the ADU as –in out– parameter allows more efficient
–– unpacking (on HP at least: suppress additional heap usage or
–– memory copy)
–– EXCEPTIONS
–––––––––––––––––––––
–– Exceptions
–––––––––––––––––––––
INDEX_ERROR : exception;
ADU_TYPE_MISMATCH : exception;
SIZE_ERROR : exception;
RAW_VALUE_TYPE_MISMATCH : exception;
DATA_LENGTH_ERROR : exception;
–––––––––––––––––––––
–– Private Part
–––––––––––––––––––––

Space Infrastructure
private
subtype T_POSITION is NUMERIC_TYPES.INTEGER16;
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
type T_ITEM is record
POSITION : T_POSITION := 0;
BYTE_PAD1 : NUMERIC_TYPES.UNSIGNED_INTEGER8; –– pad to fill gap
RAW_TYPE : VICOS_DEFINITIONS.T_RAW_VALUE_ALTERNATIVES :=
VICOS_DEFINITIONS.UNDEFINED;
end record;
for T_ITEM use record
at mod 2;
POSITION at 0 range 0 .. 15;
BYTE_PAD1 at 2 range 0 .. 7;
RAW_TYPE at 3 range 0 .. 7;
end record;
ITEM_SIZE : constant := 4;
for T_ITEM’SIZE use ITEM_SIZE * 8;
type T_TABLE is array(T_NBR_STRUCTURED_ITEMS range ) of T_ITEM;
–– pragma PACK(T_TABLE);
MAX_RAW_VALUE_SIZE : constant INTEGER :=
VICOS_DEFINITIONS.MAX_BYTE_STREAM_LENGTH + 4;
–– length field
type T_ELEMENT is array(1 .. MAX_RAW_VALUE_SIZE) of
NUMERIC_TYPES.UNSIGNED_INTEGER8;
–– pragma PACK(T_ELEMENT);
type T_RAW_BLOCK is array(NATURAL range ) of
NUMERIC_TYPES.UNSIGNED_INTEGER8;
–– pragma PACK(T_RAW_BLOCK);
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
289 von/of: 662
type T_ADU(ALTERNATIVE : VICOS_DEFINITIONS.T_ADU_ALTERNATIVES :=
VICOS_DEFINITIONS.UNDEFINED) is record
ID : MPS_DEFINITIONS.SID;
SAS_NAME : VICOS_DEFINITIONS.T_SAS_NAME;
TIME_TAG_LT : CGS_CALENDAR.CGS_DATE_AND_TIME :=
CGS_CALENDAR.NULL_DATE_AND_TIME;
TIME_TAG_SMT : CGS_CALENDAR.CGS_DATE_AND_TIME :=
CGS_CALENDAR.NULL_DATE_AND_TIME;
SEQUENCE_NUMBER : INTEGER := 0;
INTERRUPTION_FLAG : BOOLEAN := FALSE;
BYTE_PAD1 : NUMERIC_TYPES.UNSIGNED_INTEGER8; –– pad to mod 4 address.
required on HP
BYTE_PAD2 : NUMERIC_TYPES.UNSIGNED_INTEGER8;
case ALTERNATIVE is
when VICOS_DEFINITIONS.STRUCTURED =>
BLOCK : T_RAW_BLOCK(1 .. ADT_ADU_DESCRIPTION.MAX_BINARY_BUFFER_SIZE);
BLOCK_LENGTH : INTEGER := 0;
TABLE : T_TABLE(1 .. ADT_ADU_DESCRIPTION.MAX_NBR_STRUCTURED_ITEMS);
TABLE_LENGTH : INTEGER := 0;

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
290 von/of: 662
BYTE_PAD3 : NUMERIC_TYPES.UNSIGNED_INTEGER8; –– pad to mod 4 size
BYTE_PAD4 : NUMERIC_TYPES.UNSIGNED_INTEGER8;
when VICOS_DEFINITIONS.UNSTRUCTURED =>
BYTE_BUFFER : T_BINARY_BUFFER(1 ..
ADT_ADU_DESCRIPTION.MAX_BINARY_BUFFER_SIZE);
BUFFER_LENGTH : NATURAL := 33;
when VICOS_DEFINITIONS.CCSDS_PACKET =>
PACKET : ADT_CCSDS_PACKET.T_CCSDS_PACKET;
when others =>
null;
end case;
end record;
–– removes implicit components on HP, genereates warning on SunAda compiler.
–– Ignore warning! this makes the byte pads neccessary
pragma IMPROVE(SPACE, ON => T_ADU);
for T_ADU use
record
at mod 4;
ALTERNATIVE at 64 range 0 .. 7;
ID at 0 range 0 .. 31;
SAS_NAME at 4 range 0 .. 191;
TIME_TAG_LT at 28 range 0 .. 127;
TIME_TAG_SMT at 44 range 0 .. 127;
SEQUENCE_NUMBER at 60 range 0 .. 31;
INTERRUPTION_FLAG at 65 range 0 .. 7;
BYTE_PAD1 at 66 range 0 .. 7;
BYTE_PAD2 at 67 range 0 .. 7;
–– structured
BLOCK at 476 range 0 .. 32815;
BLOCK_LENGTH at 68 range 0 .. 31;
TABLE at 76 range 0 .. 3199;
TABLE_LENGTH at 72 range 0 .. 31;
BYTE_PAD3 at 4578 range 0 .. 7;
BYTE_PAD4 at 4579 range 0 .. 7;
–– unstructured
BYTE_BUFFER at 72 range 0 .. 32815;
BUFFER_LENGTH at 68 range 0 .. 31;
–– ccsds_packet
PACKET at 68 range 0 .. 32815;
end record;
ADU_SIZE : constant := 1145 * 4;
for T_ADU’SIZE use ADU_SIZE * 8;
end ADT_ADU;

Space Infrastructure
7.6.7 ADT GDU Description
Informal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
291 von/of: 662
A GDU Description is the set of information describing the format of the data send by VICOS towards front–end
equipment or UUT. It is normally predefined in the mission/configuration database, and loaded from the corresponding
end–item, in test system configuration and set–up phase. It is then interpreted by VICOS to elaborate
a GDU to be supplied to the dedicated SAS at test execution time.
There are four different classes of GDU descriptions, depending on the target device to be triggered, which are
covered by this ADT :
– a analog stimulus description allows to send data via an analog output line;
– a discrete stimulus description allows to send data via an output line;
– a telecommand description allows to send data via the ground/onboard link;
A GDU Description is a composite type containing the following attributes :
– an GDU description alternative, which modifies the structure of this item;
– an database sid, which is the identifier allocated by the MPS when the corresponding end–item is
created;
– an SAS’s short name i.e. the one in charge of the data transfer (see EGSE Software);
– a physical address, indicating where to generate the data (see Physical Address);
– a number of retries, indicating the number of times the GDU can be resend, in case of previous
transmission failure;
– a priority indicating, if they are buffered, the order in which GDU are to be sent;
– an inhibiting flag indicating whether the GDU has to be explicitly unlocked before sending;
– a default value, if GDU description alternative is STIMULI;
– a TC packet, if GDU description alternative is PREDEFINED_TC;
– a formal parameter list, describing the authorised nature of the actual parameters, which values will
be placed in the GDU.
– a command verification, specifying a value for a TM parameter (measurement) to be verified after
sending as well as associated delays.
A Table type is also provided, which allows to define indexed lists of this ADT.

Space Infrastructure
Formal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
292 von/of: 662
––
–– ADT_GDU_DESCRIPTION spec
––
––****************************************************************************
––ABSTRACT––
––
––
–– Provides definition of a GDU description as an ADT
––
–– This ADT describes a stimulus / a packet to be generated by VICOS as a
–– general description of an Generation Data Unit (GDU)
––
–– Due to used structures from other ADTs / MPS_DEFINITIONS, the ADT structure
–– provides a dynamicly allocated datatype !
––
––*–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––IDENTIFICATION––
–– PROJECT NAME : CGS
–– PRODUCT NAME : TES
–– CI–NUMBER : 1216 843
–– OBJECT NAME : ADT_GDU_DESCRIPTION
––*–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––CONTENTS––
–– COMPILER : SunAda 1.1 /Alsys Ada 5.5.1
–– LANGUAGE : Ada
–– SPECIAL CONTENTS: –
–– CHANGE HISTORY
––
–– #IRN 8085: TC Verification
–– Author: P.Hartmann
–– Date: 25.08.99
––
–– #IRN 8038: allow for 255 parameters in CCSDS and binary packets
–– Author: P.Hartmann
–– Date: 05.11.98
––
–– #IRN 6020/B: modify bynary packet” interface and SPR 2888
–– Author: P.Hartmann
–– Date: 09.04.97
––
–– #IRN 6020: Add new GDU alternative ”binary packet”
–– Author: P.Athmann
–– Date: 8.3.97
––
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V16.1 at Central Repository at DASA RI
–– creator: tommy (on host aiv_3)
–– creation date: 09.12.96 17:13:58
–– comment:
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V5.3 at Central Repository at DASA RI
–– creator: grotheer (on host mps_s)
–– creation date: 21.11.96 16:41:26
–– comment:
–– COL–RIBRE–IRN–CGS–4013: T_ALLOWED_GDU_PARAM_TYPES extended, ENG_VALUE_UNIT
added
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
293 von/of: 662
–– V5.2 at Central Repository at DASA RI
–– creator: grotheer (on host ada_s)
–– creation date: 23.09.96 17:51:49
–– comment:
–– COL–RIBRE–IRN–CGS–4013 decalibration added
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V4.4 at Central Repository at DASA RI (CGS V3 development)
–– creator: adt_1 (on host vicos2s)
–– creation date: 15.06.95 15:48:22
–– comment:
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V4.3 at Central Repository at DASA RI (CGS V3 development)
–– creator: adt_1 (on host vicos2s)
–– creation date: 15.06.95 09:44:33
–– comment:
–– Build 2 basesline, PIRN 3043 1/D
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V4.2 at Central Repository at DASA RI (CGS V3 development)
–– creator: adt_1 (on host vicos2–3)
–– creation date: 01.06.95 11:07:52
–– comment:
–– Parameter ALTYRNATIVE in procedure SET_ALTERANTIVE renamed to ALTERNATIVE
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V3.2 at DASA CGS engineering
–– creator: maron (on host vicos2–2)
–– creation date: 22.05.95 14:00:00
–– comment:
–– Build 2 baseline, PIRN 3043
––
–– V3.1 at Central Repository V2.2 (CGS V3 development)
–– creator: grotheer (on host vicos2s)
–– creation date: 29.07.94 14:22:41
–– comment:
–– COL–ERN–VIC–IRN–2125: PACK/UNPACK added
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V2.3 at ERNO ; VICOS development
–– creator: maron (on host vicos_6)
–– creation date: 20.07.92 15:33:08
–– VCS–spadm & COL–MBER–ZU1–TN–0026/92
–– V2.2 at ERNO ; VICOS development
–– creator: athmann (on host vicos_5)
–– creation date: 10.07.92 17:27:11
–– Update ac.. to VCS SPADM DNs
–– V2.1 at ERNO ; VICOS development
–– creator: vicos (on host vicos_s)
–– creation date: 30.06.92 15:57:27
–– added Standard Header by command create_file
–– END HISTORY
––****************************************************************************
––
with NUMERIC_TYPES;
with VICOS_DEFINITIONS;
with MPS_DEFINITIONS;
with ADT_PACKING;
with ADT_PHYSICAL_ADDRESS;
with ADT_CCSDS_PACKET;
with CALIBRATION;
with ADT_ENGINEERING_VALUE;

Space Infrastructure
package ADT_GDU_DESCRIPTION is
–––––––––––––––––––––––––––––
–– public types and constants
–––––––––––––––––––––––––––––
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
294 von/of: 662
SCCSID_ADS : constant STRING := ”@(#) vcs_adt_gdu_description_.a
/main/solaris–port/cgs_4.0/cgs_4.2/cgs_4.3/3 12/08/99 14:50:38@(#)”;
MAX_GDU_PARAMETER : constant integer:= 255;
–– max number of parameters for
–– GDU of type PREDEFINED_TC
–– GDU of type BINARY_PACKET
MAX_BINARY_PACKET_SIZE : constant integer := 4096;
subtype T_ALLOWED_GDU_PARAM_TYPES is MPS_DEFINITIONS.T_SW_TYPE
range MPS_DEFINITIONS.STRING_TYPE .. MPS_DEFINITIONS.LONG_REAL_TYPE;
type T_GDU_PARAMETER
(SW_TYPE : T_ALLOWED_GDU_PARAM_TYPES := MPS_DEFINITIONS.INTEGER_TYPE;
OPTIONAL : BOOLEAN := FALSE) is private;
type T_GDU_DESCRIPTION (ALTERNATIVE : VICOS_DEFINITIONS.T_GDU_ALTERNATIVES
:= VICOS_DEFINITIONS.UNDEFINED) is private;
type T_A_GDU_DESCRIPTION is access T_GDU_DESCRIPTION;
type T_CHECK
is (EQUAL, NOT_EQUAL, LESS, GREATER, LESS_EQUAL, GREATER_EQUAL, IN_RANGE);
type T_COMMAND_VERIFICATION is
record
SID : MPS_DEFINITIONS.SID;
CHECK : T_CHECK;
VALUE_1 : ADT_ENGINEERING_VALUE.T_ENGINEERING_VALUE;
VALUE_2 : ADT_ENGINEERING_VALUE.T_SCALAR_ENGINEERING_VALUE;
end record;
–––––––––––––––––––––––––––––––––––
–– GDU Parameter: Write Operations
–––––––––––––––––––––––––––––––––––
procedure SET_PARAMETER_TYPE( GDU_PARAM : in out T_GDU_PARAMETER;
PARAM_TYPE: in T_ALLOWED_GDU_PARAM_TYPES );
–– DESCRIPTION
–– Sets the type of a GDU parameter
–– EXCEPTIONS
–– GDU_DESCRIPTION_IS_CONSTRAINED
procedure SET_OPTIONAL( GDU_PARAM: in out T_GDU_PARAMETER;
OPTIONAL : in BOOLEAN := FALSE );
–– DESCRIPTION
–– Sets the optional / mandatory flag of a GDU parameter
–– EXCEPTIONS
–– GDU_DESCRIPTION_IS_CONSTRAINED
procedure SET_BIT_LENGTH( GDU_PARAM : in out T_GDU_PARAMETER;

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
NUMBER_OF_BITS: in NATURAL );
–– DESCRIPTION
–– Sets the number of bits to be replaced by the parameter
–– (i.e. in the CCSDS packet data part)
–– EXCEPTIONS
–– none
procedure SET_BIT_OFFSET( GDU_PARAM: in out T_GDU_PARAMETER;
OFFSET : in NATURAL );
–– DESCRIPTION
–– Sets the offset to the beginning of the data fiels for bits to be
–– replaced by the parameter
–– (i.e. in the CCSDS packet data part)
–– EXCEPTIONS
–– none
procedure SET_MODE( GDU_PARAM: in out T_GDU_PARAMETER;
MODE : in MPS_DEFINITIONS.T_FORMAL_PARAMETER_MODE );
–– DESCRIPTION
–– Sets the mode (IN, IN_OUT, OUT) of the formal GDU parameter
–– EXCEPTIONS
–– none
procedure SET_NAME( GDU_PARAM: in out T_GDU_PARAMETER;
NAME : in MPS_DEFINITIONS.STATIC_STRING80 );
–– DESCRIPTION
–– Sets the name of the formal GDU parameter
–– EXCEPTIONS
–– none
procedure SET_DECALIBRATION_REQUIRED( GDU_PARAM: in out T_GDU_PARAMETER;
REQUIRED : in BOOLEAN := TRUE );
–– DESCRIPTION
–– Sets the indication, if a parameter’s actual value
–– is to be decalibrated to a raw format before replacement
–– is done
–– EXCEPTIONS
–– none
procedure SET_DECALIBRATION
(
GDU_PARAM : in out T_GDU_PARAMETER;
DECALIB_INFO: in CALIBRATION.CALIBRATION_DECALIBRATION_TYPE
);
–– DESCRIPTION
–– Sets the information, how decalibration is to be done
–– Info is to be set as expected for the CALIBRATION package
–– EXCEPTIONS
procedure SET_DEFAULT_VALUE
(GDU_PARAM: in out T_GDU_PARAMETER;
SW_VALUE: in MPS_DEFINITIONS.T_SW_SCALAR_VALUE);
–– DESCRIPTION
–– sets the default value to be applied for the parameter, if the
–– parameter is optional, and no value has been given in the command
–– EXCEPTIONS
–– INVALID_TYPE: Parameter is not optional or SW_TYPE’s not equal
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
295 von/of: 662

Space Infrastructure
–––––––––––––––––––––––––––––––––––
–– GDU Parameter: Read Operations
–––––––––––––––––––––––––––––––––––
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
function PARAMETER_TYPE (GDU_PARAM: T_GDU_PARAMETER)
return T_ALLOWED_GDU_PARAM_TYPES;
–– DESCRIPTION
–– Returns the type of a GDU parameter
–– EXCEPTIONS
function OPTIONAL (GDU_PARAM: T_GDU_PARAMETER)
return BOOLEAN;
–– DESCRIPTION
–– Returns the optional / mandatory flag of a GDU parameter
–– EXCEPTIONS
function BIT_LENGTH (GDU_PARAM: T_GDU_PARAMETER)
return NATURAL;
–– DESCRIPTION
–– Returns the number of bits to be replaced by the parameter
–– (i.e. in the CCSDS packet data part)
–– EXCEPTIONS
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
296 von/of: 662
function BIT_OFFSET (GDU_PARAM: T_GDU_PARAMETER)
return NATURAL;
–– DESCRIPTION
–– Returns the offset to the beginning of the data fiels for bits to be
–– replaced by the parameter
–– (i.e. in the CCSDS packet data part)
–– EXCEPTIONS
function MODE (GDU_PARAM: T_GDU_PARAMETER)
return MPS_DEFINITIONS.T_FORMAL_PARAMETER_MODE;
–– DESCRIPTION
–– Returns the mode (IN, IN_OUT, OUT) of the formal GDU parameter
–– EXCEPTIONS
function NAME (GDU_PARAM: T_GDU_PARAMETER)
return MPS_DEFINITIONS.STATIC_STRING80;
–– DESCRIPTION
–– Sets the name of the formal GDU parameter
–– EXCEPTIONS
function DECALIBRATION_REQUIRED (GDU_PARAM: T_GDU_PARAMETER)
return BOOLEAN;
–– DESCRIPTION
–– Returns the indication, if a parameter’s actual value
–– is to be decalibrated to a raw format before replacement
–– is done
–– EXCEPTIONS
procedure READ_DECALIBRATION
(GDU_PARAM: in T_GDU_PARAMETER;
DECALIB_INFO: out CALIBRATION.CALIBRATION_DECALIBRATION_TYPE);
–– DESCRIPTION
–– Returns the information, how decalibration is to be done
–– Info is to be set as expected for the CALIBRATION package
–– Note: DECALIB_INFO is a dynamically created structure which
–– must be destroyed after use (see CALIBRATION package)
–– EXCEPTIONS

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
function DEFAULT_VALUE
(GDU_PARAM: T_GDU_PARAMETER)
return MPS_DEFINITIONS.T_SW_SCALAR_VALUE;
–– DESCRIPTION
–– Returns the default value to be applied for the parameter, if the
–– parameter is optional, and no value has been given in the command
–– EXCEPTIONS
–– INVALID_TYPE: Parameter is not optional
––––––––––––––––––––––––––––––––––––
–– GDU Description: Write Operations
––––––––––––––––––––––––––––––––––––
procedure SET_ALTERNATIVE (
GDU_DESCRIPTION : in out T_GDU_DESCRIPTION;
ALTERNATIVE: in VICOS_DEFINITIONS.T_GDU_ALTERNATIVES);
–– DESCRIPTION
–– Sets the alternative of a GDU description
–– EXCEPTIONS
procedure SET_SID (
GDU_DESCRIPTION: in out T_GDU_DESCRIPTION;
DB_SID: in MPS_DEFINITIONS.SID);
–– DESCRIPTION
–– Sets the SID of the GDU_Description
–– EXCEPTIONS
procedure SET_SAS_NAME (
GDU_DESCRIPTION: in out T_GDU_DESCRIPTION;
SAS: in VICOS_DEFINITIONS.T_APPLICATION_NAME);
–– DESCRIPTION
–– Sets the SAS name in the GDU description
–– EXCEPTIONS
procedure SET_PHYSICAL_ADDRESS (
GDU_DESCRIPTION: in out T_GDU_DESCRIPTION;
PHYSICAL_ADDRESS: in ADT_PHYSICAL_ADDRESS.T_PHYSICAL_ADDRESS);
–– DESCRIPTION
–– Sets the physical address of the GDU
–– EXCEPTIONS
procedure SET_RETRIES (
GDU_DESCRIPTION: in out T_GDU_DESCRIPTION;
RETRIES: in NATURAL);
–– DESCRIPTION
–– Sets the number of retries applicable for the GDU
–– EXCEPTIONS
procedure SET_INHIBITED (
GDU_DESCRIPTION: in out T_GDU_DESCRIPTION);
–– DESCRIPTION
–– Sets the flag that the GDU is currently inhibited for
–– sending
–– EXCEPTIONS
procedure RESET_INHIBITED (
GDU_DESCRIPTION: in out T_GDU_DESCRIPTION);
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
297 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–– DESCRIPTION
–– Resets the flag that the GDU is currently inhibited for
–– sending
–– EXCEPTIONS
procedure SET_PRIVATE_ID (
GDU_DESCRIPTION : in out T_GDU_DESCRIPTION;
PRIVATE_ID : in VICOS_DEFINITIONS.T_PRIVATE_ID);
–– DESCRIPTION
–– Sets the private ID an SAS can use to obtain the type of
–– GDU description without knowing the SID
–– EXCEPTIONS
procedure SET_PARAMETER_GENERAL_DESCRIPTION (
GDU_DESCRIPTION: in out T_GDU_DESCRIPTION;
AT_INDEX: in POSITIVE;
PARAM: in T_GDU_PARAMETER);
–– DESCRIPTION
–– Sets the formal parameter definition at the specified position.
–– EXCEPTIONS
–– INVALID_INDEX:
–– the value AT_INDEX addresses an undefined parameter:
–– ANALOG_STIMULUS : 1
–– DISCRETE_STIMULUS : 1
–– CCSDS_PACKET : MAX_GDU_PARAMETER
–– GDU_TYPE_MISMATCH:
–– the type in the GDU_DESCRIPTION is not set to
–– CCSDS_PACKET or ANALOG_STIMULUS or DISCRETE_STIMULUS
procedure SET_CCSDS_PACKET_DESCRIPTION (
GDU_DESCRIPTION: in out T_GDU_DESCRIPTION;
CCSDS_PACKET: in ADT_CCSDS_PACKET.T_CCSDS_PACKET);
–– DESCRIPTION
–– Stores a TC packet into the GDU_DESCRIPTION
–– EXCEPTIONS
–– GDU_TYPE_MISMATCH: the type is not CCSDS_PACKET
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
298 von/of: 662
procedure SET_BINARY_PACKET_LENGTH (
GDU_DESCRIPTION: in out T_GDU_DESCRIPTION;
LENGTH : in NATURAL);
–– DESCRIPTION
–– Set the number of bytes applicable for the length of binary packet within the GDU
–– EXCEPTIONS
–– GDU_TYPE_MISMATCH
–– The GDU alternative is not BINARY_PACKET
procedure SET_BINARY_PACKET (
GDU_DESCRIPTION: in out T_GDU_DESCRIPTION;
BINARY_PACKET: in NUMERIC_TYPES.BYTE_ARRAY);
–– DESCRIPTION
–– Stores a binary packet into the GDU_DESCRIPTION
–– EXCEPTIONS
–– GDU_TYPE_MISMATCH: the alternative is not BINARY_PACKET
–––––––––––––––––––––––––––
–– TC Verification
–––––––––––––––––––––––––––

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
procedure SET_TC_VERIFICATION (
GDU_DESCRIPTION : in out T_GDU_DESCRIPTION;
ACTIVATION_DELAY : in DURATION;
VERIFICATION_TIMEOUT : in DURATION;
NUMBER_ITEMS : in NATURAL);
–– DESCRIPTION
–– Stores the timing information and the number of verifications
–– for the TC verification
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
299 von/of: 662
procedure SET_TC_VERIFICATION_ITEM (
GDU_DESCRIPTION : in out T_GDU_DESCRIPTION;
AT_INDEX : in POSITIVE;
MEASUREMENT : in MPS_DEFINITIONS.SID;
CHECK : in T_CHECK;
VALUE_1 : in ADT_ENGINEERING_VALUE.T_ENGINEERING_VALUE;
VALUE_2 : in ADT_ENGINEERING_VALUE.T_SCALAR_ENGINEERING_VALUE);
–– DESCRIPTION
–– Stores one item of the TC verification at the index AT_INDEX
–– The operation SET_TC_VERIFICATION must have been called before
–– EXCEPTIONS
–– INVALID_INDEX : AT_INDEX is bigger than the NUMBER_ITEMS specified
–– during the operation SET_TC_VERIFICATION
–––––––––––––––––––––––––––
–– Read Operations
–––––––––––––––––––––––––––
function ALTERNATIVE (GDU_DESCRIPTION : in T_GDU_DESCRIPTION)
return VICOS_DEFINITIONS.T_GDU_ALTERNATIVES;
–– DESCRIPTION
–– This function returns the GDU alternative of
–– the specified GDU description variable
–– EXCEPTION
function DB_SID (GDU_DESCRIPTION: in T_GDU_DESCRIPTION)
return MPS_DEFINITIONS.SID;
–– DESCRIPTION
–– returns the SID of the GDU_DESCRIPTION
–– EXCEPTIONS
function PRIVATE_ID (GDU_DESCRIPTION: in T_GDU_DESCRIPTION)
return VICOS_DEFINITIONS.T_PRIVATE_ID;
–– DESCRIPTION
–– returns the private ID an SAS can use to obtain the type of
–– GDU description without knowing the SID
–– EXCEPTIONS
function SAS_NAME (GDU_DESCRIPTION: in T_GDU_DESCRIPTION)
return VICOS_DEFINITIONS.T_APPLICATION_NAME;
–– DESCRIPTION
–– returns the SAS address of the GDU
–– EXCEPTIONS
function PHYSICAL_ADDRESS (GDU_DESCRIPTION: in T_GDU_DESCRIPTION)
return ADT_PHYSICAL_ADDRESS.T_PHYSICAL_ADDRESS;
–– DESCRIPTION
–– returns the physical address of the GDU
–– EXCEPTIONS
–– IS_UNDEFINED
–– – no physical address has been defined

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
function RETRIES (GDU_DESCRIPTION: in T_GDU_DESCRIPTION) return NATURAL;
–– DESCRIPTION
–– returns the number of retries of the GDU
–– EXCEPTIONS
function NUMBER_OF_PARAMETERS (GDU_DESCRIPTION: in T_GDU_DESCRIPTION)
return NATURAL;
–– DESCRIPTION
–– returns the number of parameters defined for the GDU
–– EXCEPTIONS
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
300 von/of: 662
function PARAMETER_GENERAL_DESCRIPTION (OF_GDU_DESCRIPTION: in T_GDU_DESCRIPTION;
AT_INDEX: in POSITIVE)
return T_GDU_PARAMETER;
–– DESCRIPTION
–– returns the parameter AT_INDEX from a GDU desription
–– EXCEPTIONS
–– INVALID_INDEX: the value AT_INDEX addresses an undefined parameter
–– STORAGE_ERROR: there is a heap overrun
function IS_ENABLED(GDU_DESCRIPTION : in T_GDU_DESCRIPTION)
return BOOLEAN;
–– DESCRIPTION
–– returns TRUE if the GDU is enabled for sending
–– EXCEPTIONS
function CCSDS_PACKET_DESCRIPTION (GDU_DESCRIPTION: in T_GDU_DESCRIPTION)
return ADT_CCSDS_PACKET.T_CCSDS_PACKET;
–– DESCRIPTION
–– returns the CCSDS packet description
–– EXCEPTIONS
–– GDU_TYPE_MISMATCH: the type given is not CCSDS_PACKET
procedure GET_CCSDS_PACKET_DESCRIPTION (
GDU_DESCRIPTION: in T_GDU_DESCRIPTION;
CCSDS_PACKET: in out ADT_CCSDS_PACKET.T_CCSDS_PACKET);
–– DESCRIPTION
–– returns the CCSDS packet description
–– EXCEPTIONS
–– GDU_TYPE_MISMATCH: the type given is not CCSDS_PACKET
function BINARY_PACKET_LENGTH (GDU_DESCRIPTION: in T_GDU_DESCRIPTION) return NATURAL;
–– DESCRIPTION
–– returns the number of bytes denoting the length of the binary packet
–– EXCEPTIONS
–– GDU_TYPE_MISMATCH: the alternative of the GDU Desscription is not
BINARY_PACKET
procedure GET_BINARY_PACKET (GDU_DESCRIPTION : in T_GDU_DESCRIPTION;
BINARY_PACKET : in out NUMERIC_TYPES.BYTE_ARRAY);
–– DESCRIPTION
–– returns the the contents of the binary packet
–– EXCEPTIONS
–– GDU_TYPE_MISMATCH: the type given is not BINARY_PACKET
–– CONSTRAINT_ERROR: the actual parameter BINARY_PACKET is not large enough
–––––––––––––––––––––––––––
–– TC Verification

Space Infrastructure
–––––––––––––––––––––––––––
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
function NB_TC_VERIFICATION_ITEMS (GDU_DESCRIPTION : in T_GDU_DESCRIPTION)
return NATURAL;
–– DESCRIPTION
–– returns the number of items of the TC verification
procedure GET_TC_VERIFICATION_TIME (
GDU_DESCRIPTION : in T_GDU_DESCRIPTION;
ACTIVATION_DELAY : out DURATION;
VERIFICATION_TIMEOUT : out DURATION);
–– DESCRIPTION
–– provides the timing information for the TC verification
procedure GET_TC_VERIFICATION_ITEM (
GDU_DESCRIPTION : in T_GDU_DESCRIPTION;
AT_INDEX : in POSITIVE;
TC_VERIF_ITEM : out T_COMMAND_VERIFICATION);
–– DESCRIPTION
–– provide the item of the TC verification at AT_INDEX.
–– EXCEPTIONS
–– INVALID_INDEX: the value AT_INDEX addresses an undefined item
–––––––––––––––––––––––––––––
–– pack and unpack operations
–––––––––––––––––––––––––––––
procedure PACK( VALUE : in T_GDU_DESCRIPTION ;
BLOCK : in out ADT_PACKING.T_BLOCK );
–– DESCRIPTION
–– This procedure packs the specified GDU description
–– variable into a continguous memory block.
–– EXCEPTIONS
procedure UNPACK( BLOCK : in out ADT_PACKING.T_BLOCK ;
VALUE : out T_GDU_DESCRIPTION );
–– DESCRIPTION
–– This procedure unpacks the specified memory block into
–– a GDU description variable.
–– EXCEPTIONS
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
301 von/of: 662
function SIZE_NEEDED (VALUE : T_GDU_DESCRIPTION)
return ADT_PACKING.T_PACK_INDEX;
–– DESCRIPTION
–– This function calculates the actual size needed for packing the supplied
–– VALUE
–– EXCEPTIONS
procedure DEALLOCATE(GDU_DESC : in out T_A_GDU_DESCRIPTION);
–– DESCRIPTION
–– free memory allocated for the GDU description declared as
–– an access type
–– EXCEPTIONS
––
procedure DEALLOCATE(GDU_DESC : in out T_GDU_DESCRIPTION);
–– DESCRIPTION
–– free memory allocated for the GDU description
–– EXCEPTIONS

Space Infrastructure
––
–––––––––––––
–– exceptions
–––––––––––––
GDU_TYPE_MISMATCH : exception;
INVALID_TYPE : exception;
INVALID_INDEX : exception;
GDU_DESCRIPTION_IS_CONSTRAINED : exception;
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
302 von/of: 662
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
private
type T_GDU_PARAMETER
(SW_TYPE : T_ALLOWED_GDU_PARAM_TYPES := MPS_DEFINITIONS.INTEGER_TYPE;
OPTIONAL : BOOLEAN := FALSE) is
record
BIT_LENGTH : NATURAL;
BIT_OFFSET : NATURAL;
MODE : MPS_DEFINITIONS.T_FORMAL_PARAMETER_MODE;
NAME : MPS_DEFINITIONS.STATIC_STRING80;
DECALIBRATION_REQUIRED : BOOLEAN := FALSE;
–– indicates if for this parameter decalibration is required
–– if not, the value of the actual parameter has to entered
–– without modification into the GDU/packet
DECALIBRATION : CALIBRATION.CALIBRATION_DECALIBRATION_TYPE;
–– defines the decalibration for a parameter
–– must conform to the parameter type
case OPTIONAL is
when FALSE => null;
when TRUE => SW_VALUE: MPS_DEFINITIONS.T_SW_SCALAR_VALUE(SW_TYPE);
–– holds the default value for an optional parameter
end case ;
end record;
type T_GDU_PARAMETER_ACCESS is access T_GDU_PARAMETER;
type T_GDU_PARAMETER_LIST is array (1 .. MAX_GDU_PARAMETER)
of T_GDU_PARAMETER_ACCESS;
type T_COMMAND_VERIFICATION_ARRAY
is array (INTEGER range ) of T_COMMAND_VERIFICATION;
type T_A_COMMAND_VERIFICATION_ARRAY is access T_COMMAND_VERIFICATION_ARRAY;
type T_GDU_DESCRIPTION (ALTERNATIVE : VICOS_DEFINITIONS.T_GDU_ALTERNATIVES
:= VICOS_DEFINITIONS.UNDEFINED) is
record
DB_SID : MPS_DEFINITIONS.SID;
PRIVATE_ID : VICOS_DEFINITIONS.T_PRIVATE_ID;
SAS_ADDRESS : VICOS_DEFINITIONS.T_APPLICATION_NAME;
INHIBITED : BOOLEAN; –– inhibited for sending
RETRIES : NATURAL; –– number of retries in case of failures
PHYSICAL_ADDRESS : ADT_PHYSICAL_ADDRESS.T_PHYSICAL_ADDRESS;
NUMBER_OF_PARAMETERS : NATURAL := 0;
ACTIVATION_DELAY : DURATION := 0.0;
VERIFICATION_TIMEOUT : DURATION := 0.0;
COMMAND_VERIFICATION : T_A_COMMAND_VERIFICATION_ARRAY;
case ALTERNATIVE is

Space Infrastructure
when VICOS_DEFINITIONS.ANALOG_STIMULUS =>
ANALOG_PARAMETER : T_GDU_PARAMETER;
when VICOS_DEFINITIONS.DISCRETE_STIMULUS =>
DISCRETE_PARAMETER : T_GDU_PARAMETER;
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
when VICOS_DEFINITIONS.CCSDS_PACKET =>
DEFAULT_TC : ADT_CCSDS_PACKET.T_CCSDS_PACKET;
FORMAL_PARAMETERS : T_GDU_PARAMETER_LIST := (others => null);
when VICOS_DEFINITIONS.BINARY_PACKET =>
PACKET_LENGTH : NATURAL;
–– defines length of binary packet in bytes
DEFAULT_PACKET : NUMERIC_TYPES.BYTE_ARRAY
(1..MAX_BINARY_PACKET_SIZE);
BINARY_PACKET_PARAMETERS : T_GDU_PARAMETER_LIST := (others => null);
when VICOS_DEFINITIONS.UNDEFINED =>
null;
end case ;
end record;
end ADT_GDU_DESCRIPTION;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
303 von/of: 662

Space Infrastructure
7.6.8 ADT GDU
Informal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
304 von/of: 662
An GDU is the standardized format in which any stimuli/TC is send by VICOS. It is a packet of stimulus values
which are packed according to the list given in the corresponding GDU Description. GDUs are generated by
VICOS and delivered to SASs which task is to interpret it for further propagation.
A GDU Description is a composite type containing the following attributes :
– a GDU sid,
– a GDU alternative,
– a time tag, indicating when the stimuli/TC have to be really sent;
– a sequence number, which indicates the number of GDUs, of this type, already sent;
– a priority indicating, if they are buffered, the order in which GDU are to be sent;
– a number of retries, indicating the number of times the GDU can be resend, in case of previous
transmission failure;
– an SAS short name;
– a physical address, indicating where to send the stimuli/TC (see Physical Address);
– a TC packet, if GDU description alternative is PREDEFINED_TC;
– a discrete value if GDU is of type DISCRETE_STIMULI,
– an analog value if GDU is of type ANALOG_STIMULI.
A Table type is also provided, which allows to define indexed lists of this ADT.

Space Infrastructure
Formal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
––
–– ADT_GDU
––
––****************************************************************************
––ABSTRACT––
––
–– This package is an abstract data type definition for GDUs
––
––*–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––IDENTIFICATION––
–– PROJECT NAME : CGS
–– PRODUCT NAME : TES
–– CI–NUMBER : 1216 843
–– OBJECT NAME : ADT_GDU
––*–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––CONTENTS––
–– COMPILER : SunAda 1.1 /Alsys Ada 5.5.1
–– LANGUAGE : ADA
–– SPECIAL CONTENTS:
–– CHANGE HISTORY
––
–– #IRN 7062: replacing DOUBLE_FLOAT by SINGLE_FLOAT for ANALOG_STIMULI
–– Author: P.Hartmann
–– Date: 27.01.97
––
–– #IRN 6020/B: interface for the ”bynary packet”
–– Author: P.Hartmann
–– Date: 09.04.97
––
–– #IRN 6020: Add new GDU alternative ”binary packet”
–– Author: P.Athmann
–– Date: 14.2.97
––
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V4.3 at Central Repository at DASA RI (CGS V3 development)
–– creator: adt_1 (on host vicos2–3)
–– creation date: 15.06.95 15:24:07
–– comment:
–– Build 2 baseline, PIRN 3044 1/C
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V3.0 at ERNO ; CGS engineering
–– creator: maron (on host vicos2–2)
–– creation date: 22.05.95 11:00:00
–– Build 2 baseline, PIRN 3044
––
–– V2.8 at ERNO ; VICOS development
–– creator: athmann (on host vicos_5)
–– creation date: 03.03.93 20:06:45
–– Version as delivered by SRO1216843b (IK ADTs)
––
–– END HISTORY
––
––****************************************************************************
––
with NUMERIC_TYPES;
with MPS_DEFINITIONS;
with VICOS_DEFINITIONS;
with CGS_CALENDAR;
with ADT_PACKING;
with ADT_PHYSICAL_ADDRESS;
with ADT_CCSDS_PACKET;
with ADT_GDU_DESCRIPTION;
package ADT_GDU is
–––––––––––––––––––––––––––
–– ADT Types
–––––––––––––––––––––––––––
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
305 von/of: 662

Space Infrastructure
type T_GDU(ALTERNATIVE : VICOS_DEFINITIONS.T_GDU_ALTERNATIVES :=
VICOS_DEFINITIONS.UNDEFINED) is private;
type T_PRIORITY is (HIGH,LOW);
–––––––––––––––––––––––––––
–– Write Operations
–––––––––––––––––––––––––––
procedure SET_ALTERNATIVE(
GDU : in out T_GDU;
ALTERNATIVE : in VICOS_DEFINITIONS.T_GDU_ALTERNATIVES);
–– DESCRIPTION
–– Set the alternative of the GDU; must be set before values are
–– written to the GDU.
–– EXCEPTIONS
–– GDU_IS_CONSTRAINED
–– alternative is already set
procedure SET_ID(GDU : in out T_GDU;
ID : in MPS_DEFINITIONS.SID);
–– DESCRIPTION
–– Set the identifier for the GDU
–– EXCEPTIONS
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
procedure SET_PRIVATE_ID(GDU : in out T_GDU;
ID : in VICOS_DEFINITIONS.T_PRIVATE_ID);
–– DESCRIPTION
–– Set the private identifier for the GDU
–– EXCEPTIONS
procedure SET_TIME_TAG(GDU : in out T_GDU;
TIME_TAG : in CGS_CALENDAR.CGS_DATE_AND_TIME;
TIME_TYPE : in CGS_CALENDAR.T_TIME_TYPE);
–– DESCRIPTION
–– Set the time tag of the GDU
–– EXCEPTIONS
–– none
procedure SET_SEQUENCE_COUNT(
GDU : in out T_GDU;
SEQUENCE_NUMBER : in ADT_CCSDS_PACKET.T_CCSDS_SEQUENCE_COUNT);
–– DESCRIPTION
–– Set the sequence number of a CCSDS packet if the
–– GDU is a CCSDS packet
–– EXCEPTIONS
–– GDU_TYPE_MISMATCH
–– The GDU alternative is not CCSDS_PACKET
procedure SET_PRIORITY(GDU : in out T_GDU;
PRIORITY : in T_PRIORITY);
–– DESCRIPTION
–– Set the priority of the GDU
–– EXCEPTIONS
–– none
procedure SET_RETRIES(GDU : in out T_GDU;
RETRIES : in NATURAL);
–– DESCRIPTION
–– Set the number of retries applicable for the GDU
–– EXCEPTIONS
procedure SET_SAS_NAME(GDU : in out T_GDU;
SAS_NAME : in VICOS_DEFINITIONS.T_SAS_NAME);
–– DESCRIPTION
–– This procedure sets the short name of the SAS in charge of
–– the specified GDU variable
–– EXCEPTIONS
–– None
procedure SET_PHYSICAL_ADDRESS(
GDU : in out T_GDU;
PHYSICAL_ADDRESS : in ADT_PHYSICAL_ADDRESS.T_PHYSICAL_ADDRESS);
–– DESCRIPTION
–– Set the physical address of the GDU
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
306 von/of: 662

Space Infrastructure
–– EXCEPTIONS
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
procedure SET_CCSDS_PACKET(GDU : in out T_GDU;
CCSDS_PACKET : in ADT_CCSDS_PACKET.T_CCSDS_PACKET);
–– DESCRIPTION
–– Write a complete CCSDS packet to the GDU
–– EXCEPTIONS
–– GDU_TYPE_MISMATCH
–– The GDU alternative is not CCSDS_PACKET
procedure SET_BINARY_PACKET_LENGTH (GDU : in out T_GDU;
LENGTH : in NATURAL);
–– DESCRIPTION
–– Set the number of bytes applicable for the length of binary packet within the GDU
–– EXCEPTIONS
–– GDU_TYPE_MISMATCH
–– The GDU alternative is not BINARY_PACKET
procedure SET_BINARY_PACKET(GDU : in out T_GDU;
BINARY_PACKET : in NUMERIC_TYPES.BYTE_ARRAY);
–– DESCRIPTION
–– Write a complete binary packet to the GDU
–– EXCEPTIONS
–– GDU_TYPE_MISMATCH
–– The GDU alternative is not BINARY_PACKET
––––––––––––––––––––––––––––––––––––––––
–– operations for parameter substitution
––––––––––––––––––––––––––––––––––––––––
procedure SET_VALUE(GDU : in out T_GDU;
VALUE : in NUMERIC_TYPES.SINGLE_FLOAT);
–– DESCRIPTION
–– Write an analog value of type FLOAT to the GDU if the
–– alternative is ANALOG_STIMULUS
–– EXCEPTIONS
–– GDU_TYPE_MISMATCH
–– The GDU alternative is not ANALOG_STIMULUS
procedure SET_VALUE(GDU : in out T_GDU;
VALUE : in NUMERIC_TYPES.INTEGER32);
–– DESCRIPTION
–– Write a discrete value to the GDU if the type is
–– DISCRETE_STIMULUS
–– EXCEPTIONS
–– GDU_TYPE_MISMATCH
–– The GDU alternative is not DISCRETE_STIMULUS
–––––––––––––––––––
–– read operations
–––––––––––––––––––
function ALTERNATIVE(GDU : in T_GDU) return VICOS_DEFINITIONS.T_GDU_ALTERNATIVES;
–– DESCRIPTION
–– return the alternative from a GDU
–– EXCEPTIONS
function SHORT_ID(GDU : in T_GDU) return MPS_DEFINITIONS.SID;
–– DESCRIPTION
–– return the identifier for the GDU
–– EXCEPTIONS
function PRIVATE_ID(GDU : in T_GDU) return VICOS_DEFINITIONS.T_PRIVATE_ID;
–– DESCRIPTION
–– return the identifier for the GDU
–– EXCEPTIONS
function PRIORITY(GDU: in T_GDU) return T_PRIORITY;
–– DESCRIPTION
–– return the priority of the GDU
–– EXCEPTIONS
function IS_TIME_TAGGED(GDU: in T_GDU) return boolean;
–– DESCRIPTION
–– return TRUE if a GDU has a time tag, else FALSE
–– EXCEPTIONS
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
307 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
procedure GET_TIME_TAG(GDU : in T_GDU;
TIME : out CGS_CALENDAR.CGS_DATE_AND_TIME;
TIME_TYPE : out CGS_CALENDAR.T_TIME_TYPE);
–– DESCRIPTION
–– return the time_tag from the GDU
–– EXCEPTIONS
function SEQUENCE_COUNT(GDU: in T_GDU) return ADT_CCSDS_PACKET.T_CCSDS_SEQUENCE_COUNT;
–– DESCRIPTION
–– return the sequence count from the GDU
–– EXCEPTIONS
–– GDU_TYPE_MISMATCH
–– The GDU alternative is not CCSDS_PACKET
function RETRIES(GDU: in T_GDU) return NATURAL;
–– DESCRIPTION
–– return the number of retries applicable for the GDU
–– EXCEPTIONS
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
308 von/of: 662
function PHYSICAL_ADDRESS(GDU : in T_GDU) return ADT_PHYSICAL_ADDRESS.T_PHYSICAL_ADDRESS;
–– DESCRIPTION
–– return the physical address of the GDU
–– EXCEPTIONS
function SAS_NAME(GDU : in T_GDU) return VICOS_DEFINITIONS.T_SAS_NAME;
–– DESCRIPTION
–– return the sas name of the gdu
–– EXCEPTIONS
function CCSDS_PACKET(GDU : in T_GDU) return ADT_CCSDS_PACKET.T_CCSDS_PACKET;
–– DESCRIPTION
–– return a complete CCSDS packet from the GDU
–– all parameters have been substituted
–– EXCEPTIONS
–– GDU_TYPE_MISMATCH
–– The GDU alternative is not CCSDS_PACKET
procedure GET_CCSDS_PACKET(GDU : in T_GDU;
CCSDS_PACKET: in out ADT_CCSDS_PACKET.T_CCSDS_PACKET);
–– DESCRIPTION
–– return a complete CCSDS packet from the GDU
–– all parameters have been substituted
–– EXCEPTIONS
–– GDU_TYPE_MISMATCH
–– The GDU alternative is not CCSDS_PACKET
function BINARY_PACKET_LENGTH (GDU: in T_GDU) return NATURAL;
–– DESCRIPTION
–– returns the number of bytes denoting the length of the binary packet
–– EXCEPTIONS
–– GDU_TYPE_MISMATCH: the alternative of the GDU is not BINARY_PACKET
procedure GET_BINARY_PACKET(GDU : in T_GDU;
BINARY_PACKET : in out NUMERIC_TYPES.BYTE_ARRAY);
–– DESCRIPTION
–– return a complete binary packet from the GDU
–– all parameters have been substituted
–– EXCEPTIONS
–– GDU_TYPE_MISMATCH
–– The GDU alternative is not BINARY_PACKET
–– CONSTRAINT_ERROR: the actual parameter BINARY_PACKET is not large enough
function VALUE_OF(GDU : in T_GDU) return NUMERIC_TYPES.SINGLE_FLOAT;
–– DESCRIPTION
–– Returns the analog value of type FLOAT to the GDU if the
–– alternative is ANALOG_STIMULUS
–– EXCEPTIONS
–– GDU_TYPE_MISMATCH
–– The GDU alternative is not ANALOG_STIMULUS
function VALUE_OF(GDU : in T_GDU) return NUMERIC_TYPES.DOUBLE_FLOAT;
–– DESCRIPTION
–– Analog to the previous operation. kept in this version of the ADT
–– for compatibility with the old generated softwares (e.g. SAS).

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–– The double float that is returned is a type conversion from the
–– single float data of the GDU.
–– This version will be removed in the future, so any new application
–– should not use it and applications using it should foresee to switch
–– to the single float version of the operation.
function VALUE_OF(GDU : in T_GDU) return NUMERIC_TYPES.INTEGER32;
–– DESCRIPTION
–– Returns the discrete value to the GDU if the type is
–– DISCRETE_STIMULUS
–– EXCEPTIONS
–– GDU_TYPE_MISMATCH
–– The GDU alternative is not DISCRETE_STIMULUS
––––––––––––––––––––––
–– packing operations
––––––––––––––––––––––
procedure PACK(GDU : in T_GDU;
BLOCK : in out ADT_PACKING.T_BLOCK);
–– DESCRIPTION
–– pack the GDU into a T_BLOCK
–– convert to machine independent format where applicable
–– EXCEPTIONS
procedure UNPACK(BLOCK : in out ADT_PACKING.T_BLOCK;
GDU : out T_GDU);
–– DESCRIPTION
–– unpack the GDU from a T_BLOCK
–– convert from machine independent format where applicable
–– EXCEPTIONS
procedure UNPACK2(BLOCK : in out ADT_PACKING.T_BLOCK;
GDU : in out T_GDU);
–– DESCRIPTION
–– unpack the GDU from a T_BLOCK
–– convert from machine independent format where applicable
–– EXCEPTIONS
procedure UNPACK_FROM_OLD_ARCHIVE(BLOCK : in out ADT_PACKING.T_BLOCK;
GDU : in out T_GDU);
–– DESCRIPTION
–– This operation is only to be used by the ADT archive file.
–– Its aim is to transform a GDU read from an archive file containing
–– GDU’s from former CGS versions into the current GDU structure.
–– EXCEPTIONS
–––––––––––––––––––––––––
–– Exceptions
–––––––––––––––––––––––––
GDU_TYPE_MISMATCH : exception;
GDU_IS_CONSTRAINED : exception;
–––––––––––––––––––––––––
–– Private Part
–––––––––––––––––––––––––
private
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
309 von/of: 662
type T_GDU(ALTERNATIVE : VICOS_DEFINITIONS.T_GDU_ALTERNATIVES := VICOS_DEFINITIONS.UNDEFINED) is
record
ID : MPS_DEFINITIONS.SID;
PRIVATE_ID : VICOS_DEFINITIONS.T_PRIVATE_ID;
SAS_NAME : VICOS_DEFINITIONS.T_SAS_NAME;
TIME_TAG : CGS_CALENDAR.CGS_DATE_AND_TIME := CGS_CALENDAR.NULL_DATE_AND_TIME;
TIME_TYPE : CGS_CALENDAR.T_TIME_TYPE;
RETRIES : NATURAL;
PRIORITY : T_PRIORITY;
PHYSICAL_ADDRESS : ADT_PHYSICAL_ADDRESS.T_PHYSICAL_ADDRESS;
BYTE_PAD1 : NUMERIC_TYPES.UNSIGNED_INTEGER8 := 255; –– pad to mod 4 address.
BYTE_PAD2 : NUMERIC_TYPES.UNSIGNED_INTEGER8 := 255;
BYTE_PAD3 : NUMERIC_TYPES.UNSIGNED_INTEGER8 := 255;
case ALTERNATIVE is
when VICOS_DEFINITIONS.ANALOG_STIMULUS =>

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
310 von/of: 662
ANALOG_VALUE : NUMERIC_TYPES.SINGLE_FLOAT := 0.0;
when VICOS_DEFINITIONS.DISCRETE_STIMULUS =>
DISCRETE_VALUE : NUMERIC_TYPES.INTEGER32 := 0;
when VICOS_DEFINITIONS.CCSDS_PACKET =>
CCSDS_PACKET : ADT_CCSDS_PACKET.T_CCSDS_PACKET;
BYTE_PAD4 : NUMERIC_TYPES.UNSIGNED_INTEGER8 := 255; –– pad to mod 4 size
BYTE_PAD5 : NUMERIC_TYPES.UNSIGNED_INTEGER8 := 255;
when VICOS_DEFINITIONS.BINARY_PACKET =>
PACKET_LENGTH : NATURAL := 0; –– length of binary packet in bytes
BINARY_PACKET : NUMERIC_TYPES.BYTE_ARRAY
(1..ADT_GDU_DESCRIPTION.MAX_BINARY_PACKET_SIZE);
when VICOS_DEFINITIONS.UNDEFINED =>
null;
end case;
end record;
–– removes implicit components on HP, generates warning on SunAda compiler.
–– Ignore warning! this makes the byte pads neccessary
pragma IMPROVE(SPACE, ON => T_GDU);
for T_GDU use
record at mod 4;
ALTERNATIVE at 328 range 0 .. 7;
ID at 0 range 0 .. 31;
PRIVATE_ID at 329 range 0 .. 79;
SAS_NAME at 4 range 0 .. 191;
TIME_TAG at 28 range 0 .. 127;
TIME_TYPE at 339 range 0 .. 7;
RETRIES at 44 range 0 .. 31;
PRIORITY at 340 range 0 .. 7;
PHYSICAL_ADDRESS at 48 range 0 .. 2239;
BYTE_PAD1 at 341 range 0 .. 7;
BYTE_PAD2 at 342 range 0 .. 7;
BYTE_PAD3 at 343 range 0 .. 7;
ANALOG_VALUE at 344 range 0 .. 31;
DISCRETE_VALUE at 344 range 0 .. 31;
CCSDS_PACKET at 344 range 0 .. 32815;
BYTE_PAD4 at 4446 range 0 .. 7;
BYTE_PAD5 at 4447 range 0 .. 7;
PACKET_LENGTH at 344 range 0 .. 31;
BINARY_PACKET at 348 range 0 .. ADT_GDU_DESCRIPTION.MAX_BINARY_PACKET_SIZE*8–1;
end record;
GDU_SIZE : constant := 1112 * 4;
for T_GDU’SIZE use GDU_SIZE * 8;
end ADT_GDU;

Space Infrastructure
7.7 TES Application Programmer Interface
Informal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
311 von/of: 662
The role of the TES Application Programmer Interface (TES_API) is to exchange data with TES, in the form
of ADU for data entering TES, and of GDU for data issued by TES.
It is presented as a standard interface for Special Application Software (SAS) for access to the TES kernel. (Note
that the SAS may not execute within the same operating system process).
It is implemented as a package of ’Ada’ functions which can be linked to applications requiring these services.
These procedural interfaces enable TES to be local or physically remote from the software needing to access
its services.
The TES_API concept is based on the idea that TES sends commands to a SAS through exactly one command
channel in a strictly sequential way, whenever TES wants something from the SAS, i.e. when TES takes the initiative.
The SAS itself is provided with a set of operations to read commands and parse them plus another set of
operations to issue data or requests to TES, in this case the SAS taking the initiative.
The central point in this concept is that there exists only one procedure READ_COMMAND that waits for commands
from TES and then provides these to the SAS. In the command, the various types of subcommands can
be implemented, e.g. ADU requests, GDUs etc...
With this concept, a SAS must not necessarily be designed with several tasks, though it is still allowed. As long
as the SAS in its processing of the commands is fast enough, then no tasking is needed.
Within this concept, a data interface SAS directly enters ”running” mode after the INIT_LINK command has
been received.
A number of access services are supplied, these shall be summarised.
• Connection/disconnection to TES
To enable connection to the TES kernel and to enable subsequent access, connection services are provided.
Disconnection services are also supplied.
• SAS commanding
To enable commands to be received from SAS, a procedural interface is provided for transferring CGS
commands (e.g. originating as UCL/HLCL commands) associated with test execution to TES, this interface
also provides functions to write responses from the SAS.
This service provides the handling of the basic command reception functions only. The parsing of the
command itself is not a function of this API. The necessary procedures are provided in an abstract data
type T_COMMAND in ADT_TES_TO_SAS_COMMAND package.
• Message service
Services are provided for reading messages from and passing messages to APs executing under the control
of TES.
Error message services are provided for passing Error Messages from the active SAS on to TES (and
hence on to the CGS User).
• Time service
Timing services are provided for test execution these include, reading of system time and Wait (suspend
caller until the Wake Up time).
• ADU/GDU service
During test execution, data can be acquired from different sources. Acquisition services are applied to
Acquisition Data Units (ADUs) and Generation Data Units (GDUs). ADUs are associated with End

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
312 von/of: 662
Items in the Mission Database, the definition of measurement include the calibration and monitoring
specification in addition to the raw data source (e.g. SAS for TM packet).
An ADU can contain raw measurement values which can be extracted and calibrated. An ADU can be
sent within a Delivery Packet or constructed and sent separately. ADU requests are therefore used to
trigger data and information generation e.g. from the Unit Under Test, SAS etc. GDUs provide data such
as TC packets, HW Stimuli etc to other products. These then are used to manage commanding of the
UUT. A GDU can contain Telecommands (TCs) or Stimuli.
Services provide facilities for managing such data constructs e.g.: Enable/Disable ADU Construction,
Read ADU, Enable/Disable ADU Acquisition, Enable/Disable ADU Redirection, Announce ADU/
GDU, Disconnect ADU/GDU, Issue (for End Item Command), Put GDU (ready for sending to a destination).
The extraction of an ADU description from a command itself is not a function provided by this API but
this function, as well as all the type definitions for raw values come from abstract data types
ADT_COMMAND, ADT_ADU_DESCRIPTION, ADT_ADU and ADT_RAW_VALUE.
The extraction of an GDU from a command itself is not a function provided by this API but this function
comes from abstract data types ADT_COMMAND, ADT_GDU and ADT_RAW_VALUE.
In connection with the ADU/GDU services, Exchange Services are provided for sending/receiving of
ADUs. These include: Read ADU Stream, Get/Ack GDU and Get/Ack ADU Request.
• Raw/engineering value processing
The data processing service provides the operations for raw and calibrated data exchange with TES. The
type definitions for raw and engineering values come from abstract data types ADT_RAW_VALUE and
ADT_ENGINEERING_VALUE.
Finally, services are provided to enable the active SAS to retrieve Flight SW (e.g. SWRUs) from the Mission
Database for up–link (passing onto Flight Hardware) during check–out operations.
All operations of this API are constraint because they will use operations that are protected against parallel access,
e.g. operations that check the presence of a connection or the send operation of the underlaying network
software. That means that all operations may be access in parallel without external synchronization by the client,
but the control flow of a caller may be suspended if more than one caller (task) reaches the same synchronization
point.

Space Infrastructure
Formal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
––
–– ADT_TES_TO_SAS_COMMAND spec
––
––****************************************************************************
––ABSTRACT––
––
–– This package defines and handles types related to commands exchanged
–– between VICOS TES and Special Application Software (SAS)
––
––*–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––IDENTIFICATION––
–– PROJECT NAME : CGS
–– PRODUCT NAME : TES
–– CI–NUMBER : 1216 843
–– OBJECT NAME : ADT_TES_TO_SAS_COMMAND
––*–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––CONTENTS––
–– COMPILER : SunAda 1.1 /Alsys Ada 5.5.1
–– LANGUAGE : ADA
–– SPECIAL CONTENTS:
–– CHANGE HISTORY
–– V3.0 at ERNO ; CGS engineering
–– creator: maron (on host vicos2–2)
–– creation date: 14.03.95 10:00:00
–– Build 2 baseline, PIRN 3049
–– V2.4 at ERNO ; VICOS development
–– creator: athmann (on host vicos_5)
–– creation date: 03.03.93 20:21:43
–– Version as delivered by SRO1216843b (IK ADTs)
––****************************************************************************
––
with ADT_PACKING;
–– type T_BLOCK
with VICOS_DEFINITIONS;
–– type T_APPLICATION_NAME
with ADT_ADU_DESCRIPTION;
–– type T_ADU_DESCRIPTION
with ADT_GDU;
–– type T_GDU
package ADT_TES_TO_SAS_COMMAND is
––––––––––––––––––––––––––––––
–– public types and constants
––––––––––––––––––––––––––––––
type T_DOWNLOAD_SW_TYPE is (
DATA_FILE,
EXECUTABLE);
type T_DESTINATION is (
FRONT_END_EQUIPMENT,
UNIT_UNDER_TEST);
type T_COMMAND_ALTERNATIVES is (
UNDEFINED,
INIT_APPLICATION,
START_APPLICATION,
RESET_APPLICATION,
STATUS_REQUEST,
AP_MESSAGE,
ADU_REQUEST,
GDU_REQUEST,
UNLOAD_APPLICATION,
DOWNLOAD,
NO_COMMAND);
–– The command alternatives indicates to the SAS:
–– – that the command alternative is undefined,
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
313 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–– – to put itself into an ’initiate’ state, i.e. ready to run,
–– – to start its execution,
–– – to abort the execution and to return to ’idle’ state, i.e. wait
–– for an ’initiate’ command,
–– – that a status is requested (SAS errors, statistics, ...),
–– – that the command contains a message coming from an AP,
–– – to start the data acquisition from UUT,
–– – to start the data generation to UUT,
–– – to make a complete termination, i.e. unload from memory,
–– – to support downloading of files
–– – the variable is not set–up, i.e. contains nothing.
type T_COMMAND (
COMMAND_ALTERNATIVE : T_COMMAND_ALTERNATIVES := UNDEFINED) is private;
––––––––––––––––––––
–– write operations
––––––––––––––––––––
procedure SET_COMMAND_ALTERNATIVE (
OF_COMMAND : in out T_COMMAND;
WITH_ALTERN : in T_COMMAND_ALTERNATIVES);
–– DESCRIPTION
–– This procedure sets the command alternative of the
–– given command.
–– EXCEPTIONS
–– COMMAND_IS_CONSTRAINED :
–– The provided command is constrained and the alternative
–– can therefore not be changed.
procedure SET_TIMEOUT (
OF_COMMAND : in out T_COMMAND;
WITH_TIMEOUT_MILLISECS : in POSITIVE);
–– DESCRIPTION
–– This procedure sets the timeout period in milliseconds a SAS
–– has to acknowledge the command.
–– EXCEPTIONS
–– None.
procedure SET_INIT_PARAMS (
OF_COMMAND : in out T_COMMAND;
WITH_INIT_PARAMS : in STRING);
–– DESCRIPTION
–– In case the type of command is the INIT_APPLICATION command,
–– this procedure can be used to set the parameter string
–– supplied to the UCL library procedure INIT_APPLICATION.
–– The maximum length of the string is 255 characters.
–– EXCEPTIONS
–– COMMAND_TYPE_MISMATCH :
–– the command is not an INIT_APPLICATION command
–– INIT_PARAMS_ILLEGAL :
–– the passed initialisation parameter string had a length
–– that exeeded 255 characters.
procedure SET_MESSAGE (
OF_COMMAND : in out T_COMMAND;
WITH_MESSAGE : in STRING);
–– DESCRIPTION
–– In case the type of command is the AP_MESSAGE command,
–– this procedure can be used to set the message string
–– supplied to the UCL library procedure WRITE_MESSAGE_TO_APPLICATION.
–– The maximum length of the string is 255 characters.
–– EXCEPTIONS
–– COMMAND_TYPE_MISMATCH :
–– the command is not an AP_MESSAGE command
–– MESSAGE_ILLEGAL :
–– the passed message string had a length
–– that exeeded 255 characters.
procedure SET_ADU_DESCRIPTION (
OF_COMMAND : in out T_COMMAND;
ENABLE : in BOOLEAN;
WITH_ADU_DESCRIPTION : in ADT_ADU_DESCRIPTION.T_ADU_DESCRIPTION);
–– DESCRIPTION
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
314 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–– In case the type of command is the ADU_REQUEST command,
–– this procedure can be used to set the ADU_DESCRIPTION.
–– ENABLE specifies if the ADU has to be enabled (ENABLE => true)
–– or disabled (ENABLE => false)
–– EXCEPTIONS
–– COMMAND_TYPE_MISMATCH :
–– the command is not an ADU_REQUEST command
procedure SET_GDU (
OF_COMMAND : in out T_COMMAND;
WITH_GDU : in ADT_GDU.T_GDU);
–– DESCRIPTION
–– In case the type of command is a GDU_REQUEST command,
–– this procedure can be used to set the GDU.
–– EXCEPTIONS
–– COMMAND_TYPE_MISMATCH :
–– the command is not an GDU_REQUEST command
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
315 von/of: 662
procedure SET_DOWNLOAD_PARAMS (
OF_COMMAND : in out T_COMMAND;
FILE_TYPE : in T_DOWNLOAD_SW_TYPE;
FILE_ID : in VICOS_DEFINITIONS.T_NAME_STRING;
FILE_NAME : in VICOS_DEFINITIONS.T_FILE_NAME;
DESTINATION_TYPE : in T_DESTINATION;
DESTINATION_ID : in VICOS_DEFINITIONS.T_NAME_STRING);
–– DESCRIPTION
–– In case the type of command is a DOWNLOAD command,
–– this procedure sets the parameters needed by the SAS.
–– EXCEPTIONS
–– COMMAND_TYPE_MISMATCH :
–– the command is not a DOWNLOAD command
–––––––––––––––––––
–– read operations
–––––––––––––––––––
function COMMAND_ALTERNATIVE (
COMMAND : T_COMMAND)
return T_COMMAND_ALTERNATIVES;
–– DESCRIPTION
–– This function takes a command received as an input
–– and returns the type of that command.
–– EXCEPTIONS
–– None.
function COMMAND_TIMEOUT (
COMMAND : T_COMMAND)
return POSITIVE;
–– DESCRIPTION
–– This function takes a command and
–– returns the timeout period in milliseconds an SAS has
–– to acknowledge the command.
–– EXCEPTIONS
–– None.
function NEEDS_ACKNOWLEDGE(
COMMAND : T_COMMAND)
return BOOLEAN;
–– DESCRIPTION
–– This function returns TRUE if a command needs an acknowledge by the SAS.
–– The following coomands need an acknowledge at present:
–– INIT_APPLICATION,
–– START_APPLICATION,
–– RESET_APPLICATION,
–– STATUS_REQUEST,
–– ADU_REQUEST,
–– GDU_REQUEST,
–– UNLOAD_APPLICATION,
–– DOWNLOAD,
–– EXCEPTIONS
–– None.
function STRING_LENGTH (
COMMAND : T_COMMAND)
return NATURAL;

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–– DESCRIPTION
–– In case the command provided is of type INIT_APPLICATION or
–– AP_MESSAGE this procedure returns the length of the
–– string stored by these commands.
–– EXCEPTIONS
–– COMMAND_TYPE_MISMATCH :
–– the command is not of type INIT_APPLICATION or AP_MESSAGE.
function INIT_PARAMS (
COMMAND : T_COMMAND)
return STRING;
–– DESCRIPTION
–– In case the type of command received is the INIT_APPLICATION
–– command, this procedure can be used to obtain the parameter
–– string supplied to the UCL library procedure INIT_APPLICATION.
–– EXCEPTIONS
–– COMMAND_TYPE_MISMATCH :
–– the command is not an INIT_APPLICATION command
function MESSAGE (
COMMAND : T_COMMAND)
return STRING;
–– DESCRIPTION
–– In case the type of command received is the AP_MESSAGE
–– command, this procedure can be used to obtain the message
–– string supplied to the UCL library procedure
–– WRITE_MESSAGE_TO_APPLICATION.
–– EXCEPTIONS
–– COMMAND_TYPE_MISMATCH :
–– the command is not an AP_MESSAGE command
procedure GET_ADU_DESCRIPTION (
OF_COMMAND : in T_COMMAND;
ENABLE : out BOOLEAN;
ADU_DESCRIPTION : out ADT_ADU_DESCRIPTION.T_ADU_DESCRIPTION);
–– DESCRIPTION
–– In case the type of command received is the ADU_REQUEST
–– command, this procedure can be used to obtain the
–– ADU_DESCRIPTION supplied.
–– ENABLE specifies if the ADU has to be enabled (ENABLE => true)
–– or disabled (ENABLE => false)
–– EXCEPTIONS
–– COMMAND_TYPE_MISMATCH :
–– the command is not an ADU_REQUEST command
function GDU (
COMMAND : T_COMMAND)
return ADT_GDU.T_GDU;
–– DESCRIPTION
–– In case the type of command received is the GDU_REQUEST
–– command, this procedure can be used to obtain the GDU supplied.
–– EXCEPTIONS
–– COMMAND_TYPE_MISMATCH :
–– the command is not an GDU_REQUEST command
procedure GET_DOWNLOAD_PARAMS (
OF_COMMAND : in out T_COMMAND;
FILE_TYPE : out T_DOWNLOAD_SW_TYPE;
FILE_ID : out VICOS_DEFINITIONS.T_NAME_STRING;
FILE_NAME : out VICOS_DEFINITIONS.T_FILE_NAME;
DESTINATION_TYPE : out T_DESTINATION;
DESTINATION_ID : out VICOS_DEFINITIONS.T_NAME_STRING);
–– DESCRIPTION
–– In case the type of command is a DOWNLOAD command,
–– this procedure returns the parameters needed by the SAS.
–– EXCEPTIONS
–– COMMAND_TYPE_MISMATCH :
–– the command is not a DOWNLOAD command
––––––––––––––––––––––
–– packing operations
––––––––––––––––––––––
procedure PACK (
COMMAND : in T_COMMAND;
BLOCK : in out ADT_PACKING.T_BLOCK);
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
316 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–– DESCRIPTION
–– This procedure packs the specified command variable into
–– a contiguous memory block.
–– EXCEPTIONS
–– None.
procedure UNPACK (
BLOCK : in out ADT_PACKING.T_BLOCK;
COMMAND : out T_COMMAND);
–– DESCRIPTION
–– This procedure unpacks the specified memory block into
–– a command variable.
–– EXCEPTIONS
–– None.
–––––––––––––––––––
–– exceptions
–––––––––––––––––––
COMMAND_TYPE_MISMATCH : exception;
INIT_PARAMS_ILLEGAL : exception;
MESSAGE_ILLEGAL : exception;
COMMAND_IS_CONSTRAINED : exception;
private
MAX_STRING_LENGTH : constant := 255;
type T_CALIBRATED_STRING is
record
STR : STRING (1..MAX_STRING_LENGTH) := (others => ’ ’);
LENGTH : INTEGER range 0..MAX_STRING_LENGTH := 0;
end record;
type T_COMMAND (
COMMAND_ALTERNATIVE : T_COMMAND_ALTERNATIVES := UNDEFINED) is
record
TIMEOUT_VALUE : POSITIVE;
case COMMAND_ALTERNATIVE is
when UNDEFINED =>
null;
when INIT_APPLICATION =>
INIT_STRING : T_CALIBRATED_STRING;
when START_APPLICATION =>
null;
when RESET_APPLICATION =>
null;
when STATUS_REQUEST =>
null;
when AP_MESSAGE =>
MESSAGE : T_CALIBRATED_STRING;
when ADU_REQUEST =>
DESCRIPTION : ADT_ADU_DESCRIPTION.T_ADU_DESCRIPTION;
ENABLED : BOOLEAN;
when GDU_REQUEST =>
GDU : ADT_GDU.T_GDU;
when UNLOAD_APPLICATION =>
null;
when DOWNLOAD =>
FILE_TYPE : T_DOWNLOAD_SW_TYPE;
FILE_ID : VICOS_DEFINITIONS.T_NAME_STRING;
FILE_NAME : VICOS_DEFINITIONS.T_FILE_NAME;
DESTINATION_TYPE : T_DESTINATION;
DESTINATION_ID : VICOS_DEFINITIONS.T_NAME_STRING;
when NO_COMMAND =>
null;
end case;
end record;
end ADT_TES_TO_SAS_COMMAND;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
317 von/of: 662

Space Infrastructure
Formal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
318 von/of: 662
––
–– TES_API
––
––****************************************************************************
––ABSTRACT––
–– Provides the Application Program Interface to TES on Test Nodes for
–– Specific Application Software (SAS)
––
–– Constraints:
–– The package receives internally the SIGIO Sigpoll signal for the process
–– and handles it. It ignores the Sigpipe signal.
––
––*–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––IDENTIFICATION––
–– PROJECT NAME : CGS
–– PRODUCT NAME : TES
–– CI–NUMBER : 1216 843
–– OBJECT NAME : TES_API
––*–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––CONTENTS––
–– COMPILER : SunAda 1.1 Alsys Ada 5.5.1
–– LANGUAGE : Ada
–– CHANGE HISTORY
–– V4.3 at DASA ; TES engineering
–– creator: Hartmann
–– creation date: 07.01.00
–– CGS 4.3 baseline, PIRN 8096:
–– Add operation to inform TES about ADU interruption
––
–– V4.2 at DASA ; TES engineering
–– creator: Athmann
–– creation date: 2.11.98
–– CGS 4.2 baseline, PIRN 8035:
–– Document Use of Signal Handling instead of Polling
––
–– V4.1 at DASA ; TES engineering
–– creator: hartmann
–– creation date: 29.10.97
–– CGS 4.1 baseline, PIRN 7050/A
––
–– V4.1 at DASA ; TES engineering
–– creator: maron (on host aiv–1)
–– creation date: 08.10.97 12:00:00
–– CGS 4.1 baseline, PIRN 7050
––
–– V3.0 at ERNO ; CGS emgineering
–– creator: maron (on host vicos2–2)
–– creation date: 17.03.95 12:00:00
–– Build 2 baseline, PIRN 3058
––
–– V2.5 at ERNO ; VICOS development
–– creator: athmann (on host vicos_5)
–– creation date: 03.03.93 21:02:57
–– Update acc. to COL–MBER–VIC–IRN–2047
––
–– V2.4 at ERNO ; VICOS development
–– creator: vicos (on host prime_1)
–– creation date: 18.09.92 12:12:22
–– modifications according to FINAL ICD REVIEW DNs (see list)
–– V2.3 at ERNO ; VICOS development

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–– creator: vicos (on host vicos_8)
–– creation date: 22.07.92 16:04:00
–– Alignment to SPADM and TN COL_MBER_ZU1_TN_0026_92
–– V2.1 at ERNO ; VICOS development
–– creator: vicos (on host vicos_4)
–– creation date: 25.06.92 11:09:36
–– INCREMENT_VERSION v1_0_0
–– V1.5 at ERNO ; VICOS development
–– creator: vicos (on host vicos_4)
–– creation date: 25.06.92 09:09:02
–– deleted old VICOS HEADER
–– V1.4 at ERNO ; VICOS development
–– creator: vicos (on host vicos_4)
–– creation date: 25.06.92 08:21:11
–– added new header
––****************************************************************************
––
with CGS_CALENDAR;
–– type T_DATE_AND_TIME
with NUMERIC_TYPES;
with VICOS_DEFINITIONS;
with MPS_DEFINITIONS;
–– type SID
with TES_DEFINITIONS;
–– type T_APPLICATION_ID
–– type T_RETURN_STATUS
–– type T_IDENTIFIER
–– type T_LINK_STATUS
–– type T_AP_MESSAGE
with ADT_TES_TO_SAS_COMMAND;
–– type T_COMMAND
with ADT_ADU;
–– type T_ADU
with ADT_ADU_DESCRIPTION;
–– type T_ADU_DESCRIPTION
with ADT_GDU;
–– type T_GDU
package TES_API is
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
319 von/of: 662
SCCSID_ADS : constant STRING := ”@(#) tes_api_.a /main/cgs_4.1/cgs_4.2/cgs_4.3/1
01/12/00 17:33:01@(#)”;
type T_SMT_STATUS is (NOT_INITIALISED,STOPPED,RUNNING);
procedure CONNECT (
SAS_NAME : in VICOS_DEFINITIONS.T_APPLICATION_NAME;
CGS_PARENT : in VICOS_DEFINITIONS.T_APPLICATION_NAME
:= VICOS_DEFINITIONS.EMPTY_NAME_STRING;
APPLICATION_ID : out TES_DEFINITIONS.T_APPLICATION_ID;
STATUS : out TES_DEFINITIONS.T_RETURN_STATUS);
–– DESCRIPTION
–– This procedure establishes a connection between a SAS and the CGS product

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
320 von/of: 662
–– TES.
–– It tries to connect to the TES instance locally being available on a
–– testnode if the SAS is started on a testnode. Then, the parameter
–– CGS_PARENT can be the empty name string provided by default.
–– If the SAS has been started by CGS on a workstation then the CGS_PARENT
–– has to be set explicitely by the SAS. Normally, TES should pass the
–– parent application name to the SAS via the command line interface.
–– The parameter SAS_NAME is the name of the executable image of the SAS.
–– Also, this name has to correspond exactly to the definition of this SAS
–– as a database enditem of type EGSE_SW.
–– This is required since TES needs to correlate the name of an application
–– started through a UCL library command with the ones trying to connect.The
–– Application_ID is returned by TES. It is the unique handle to be used in
–– all future calls to the TES–API for this specific instance of TES.
–– Status is the error status returned by this call
–– RETURN STATES
–– SUCCESS : the call was successfull
–– CURRENT_MODE_WRONG : TES is in idle or error mode or it is currently not
–– running
–– COMMUNICATION_ERROR : some communication problem exists, carefully look
–– into your system topology table
–– SAS_UNKNOWN : The SAS_NAME is wrong, this SAS has not been
–– started by the CGS_PARENT
–– OTHER_ERROR : an unexpected error occurred or the SAS has not
–– called READ_COMMAND in time, i.e. the time–out
–– has expired (configurable in the TES_CONFIG_FILE)
procedure DISCONNECT (
APPLICATION_ID : in TES_DEFINITIONS.T_APPLICATION_ID;
STATUS : out TES_DEFINITIONS.T_RETURN_STATUS);
–– DESCRIPTION
–– This procedure releases a connection between a SAS and TES. It tries to
–– disconnect from TES.The Application_ID is the handle provide by TES in
–– the connect operation. Status is the error status returned by this call.
–– RETURN STATES
–– SUCCESS : the call was successfull
–– NOT_CONNECTED : the SAS is not yet connected
–– COMMUNICATION_ERROR : some communication problem exists, carefully look
–– into your system topology table, maybe TES died
–– in the meantime
–– INVALID_APPLICATION_ID : The identifier is wrong, perhaps an old one is
–– used?
–– OTHER_ERROR : an unexpected error occurred or the SAS has not
–– called READ_COMMAND in time, i.e. the time–out
–– has expired (configurable in the TES_CONFIG_FILE)
procedure READ_COMMAND (
APPLICATION_ID : in TES_DEFINITIONS.T_APPLICATION_ID;
COMMAND : in out ADT_TES_TO_SAS_COMMAND.T_COMMAND;
COMMAND_ID : in out TES_DEFINITIONS.T_IDENTIFIER;
STATUS : out TES_DEFINITIONS.T_RETURN_STATUS;
BLOCK : in BOOLEAN := FALSE);
–– DESCRIPTION
–– This procedure reads a command from TES. It needs the application id
–– returned during the connect operation in order to check that this SAS
–– is properly connected to TES.
–– The command received from TES is returned in
–– ADT_TES_TO_SAS_COMMAND.T_COMMAND. The procedures and function of package
–– ADT_TES_TO_SAS_COMMAND can be used to further process the command and
–– find out what type of caommand it is. Also, the ADT provides all
–– necessary data associated with the command. Each command also comes with

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
321 von/of: 662
–– a COMMAND_ID which is lateron used to e.g. acknowledge the command.
–– The parameter BLOCK indicates whether the procedure shall block in the
–– call untilthere is a command from TES (if set to TRUE). In case it is
–– FALSE, the procedure will immediately return. The command is then either
–– a meaningful one or the NULL command.
––
–– It is important to notice that commands have to be acknowledged within a
–– given time interval which can be obtained from the command itself through
–– function ADT_COMMAND.COMMAND_TIMEOUT
–– RETURN STATES
–– SUCCESS : the call was successfull
–– CURRENT_MODE_WRONG : TES is in idle or error mode or it is currently
–– not running
–– COMMUNICATION_ERROR : some communication problem exists, carefully
–– look into your system topology table, maybe TES
–– died in the meantime
–– INVALID_APPLICATION_ID : The identifier is wrong, perhaps an old one is
–– used?
–– OTHER_ERROR : an unexpected error occurred or the SAS has not
–– called READ_COMMAND in time, i.e. the time–out
–– has expired (configurable in the TES_CONFIG_FILE)
procedure ACKNOWLEDGE_COMMAND (
APPLICATION_ID : in TES_DEFINITIONS.T_APPLICATION_ID;
COMMAND_ID : in TES_DEFINITIONS.T_IDENTIFIER;
ACKNOWLEDGED : in BOOLEAN;
STATUS : out TES_DEFINITIONS.T_RETURN_STATUS);
–– DESCRIPTION
–– This procedure acknowledges a command received from TES. Use
–– ADT_TES_TO_SAS_COMMAND to find out which commands need explicite
–– acknowledgement.
–– It needs the application id returned during the connect operation in
–– order to check that this SAS is still connected to TES.
–– The command id as received from TES during READ_COMMAND is an input
–– parameter also.
–– If SAS wants to acknowledge the command, parameter ACKNOWLEDGED is set
–– to TRUE, else to FALSE.
–– RETURN STATES
–– SUCCESS : the call was successfull
–– CURRENT_MODE_WRONG : TES is in idle or error mode or it is currently
–– not running
–– COMMUNICATION_ERROR : some communication problem exists, carefully
–– look into your system topology table, maybe TES
–– died in the meantime
–– INVALID_APPLICATION_ID : The identifier is wrong, perhaps an old one is
–– used?
–– INVALID_COMMAND_ID : The identifier is wrong, perhaps an old one is
–– used?
–– COMMAND_TIMEOUT : The acknowledge comes too late, sorry...
–– COMMAND_NEEDS_NO_ACK : The command needs no acknowledge
–– OTHER_ERROR : an unexpected error occurred or the SAS has not
–– called READ_COMMAND in time, i.e. the time–out
–– has expired (configurable in the TES_CONFIG_FILE)
procedure ACKNOWLEDGE_COMMAND_WITH_STATUS (
APPLICATION_ID : in TES_DEFINITIONS.T_APPLICATION_ID;
COMMAND_ID : in TES_DEFINITIONS.T_IDENTIFIER;
SAS_STATUS : in TES_DEFINITIONS.T_LINK_STATUS;
SAS_ERRORS : in INTEGER;
STATUS : out TES_DEFINITIONS.T_RETURN_STATUS;
SAS_LAST_ERROR : in VICOS_DEFINITIONS.T_LOG_TEXT_LONG);

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
322 von/of: 662
–– DESCRIPTION
–– This procedure is the answer to a STATUS_REQUEST command received from
–– TES. A SAS must call this procedure within the defined timeout interval,
–– otherwise TES will detect a time out.
–– The application id is the ID returned by TES during the connect operation.
–– The command id is the one returned during READ_COMMAND.
–– SAS_STATUS is the current state of the SAS. The SAS_ERRORS is the
–– accumulated number of errors detected in this SAS. It is up to the SAS
–– to decide how this counter is maintained. The SAS_LAST_ERROR is a string
–– providing more subtle information on the last error encountered.
–– RETURN STATES
–– SUCCESS : the call was successfull
–– CURRENT_MODE_WRONG : TES is in idle or error mode or it is currently
–– not running
–– COMMUNICATION_ERROR : some communication problem exists, carefully
–– look into your system topology table, maybe TES
–– died in the meantime
–– INVALID_APPLICATION_ID : The identifier is wrong, perhaps an old one is
–– used?
–– INVALID_COMMAND_ID : The identifier is wrong, perhaps an old one is
–– used?
–– COMMAND_TIMEOUT : The acknowledge comes too late, sorry...
–– COMMAND_NEEDS_NO_ACK : The command needs no acknowledge
–– OTHER_ERROR : an unexpected error occurred or the SAS has not
–– called READ_COMMAND in time, i.e. the time–out
–– has expired (configurable in the TES_CONFIG_FILE)
procedure SEND_MESSAGE_TO_AP (
APPLICATION_ID : in TES_DEFINITIONS.T_APPLICATION_ID;
AP_NAME : in STRING;
MESSAGE : in TES_DEFINITIONS.T_AP_MESSAGE;
MESSAGE_LENGTH : in POSITIVE;
STATUS : out TES_DEFINITIONS.T_RETURN_STATUS);
–– DESCRIPTION
–– This procedure sends a message to an AP’s message buffer. The application
–– id is the ID returned by TES during the connect operation.The AP name is
–– the pathname of the AP the message shall be sent to. In case several
–– instances of the AP are running, TES will put the message into all input
–– buffers.
–– The message is a string to be sent to the TES AP. The length is given in
–– parameter MESSAGE_LENGTH.
–– RETURN STATES
–– SUCCESS : the call was successfull
–– CURRENT_MODE_WRONG : TES is in idle or error mode or it is currently
–– not running
–– COMMUNICATION_ERROR : some communication problem exists, carefully
–– look into your system topology table, maybe TES
–– died in the meantime
–– INVALID_APPLICATION_ID : The identifier is wrong, perhaps an old one is
–– used?
–– AP_NOT_FOUND : The AP does not exist on the testnode
–– OTHER_ERROR : an unexpected error occurred or the SAS has not
–– called READ_COMMAND in time, i.e. the time–out
–– has expired (configurable in the TES_CONFIG_FILE)
procedure SEND_ERROR_MESSAGE (
APPLICATION_ID : in TES_DEFINITIONS.T_APPLICATION_ID;
ERROR_MESSAGE_SHORT : in VICOS_DEFINITIONS.T_LOG_TEXT_SHORT;
ERROR_MESSAGE_LONG : in VICOS_DEFINITIONS.T_LOG_TEXT_LONG;
ERROR_TYPE : in VICOS_DEFINITIONS.T_LOG_TYPE;
LOCAL_TIME_TAG : in CGS_CALENDAR.CGS_DATE_AND_TIME
:= CGS_CALENDAR.NULL_DATE_AND_TIME;

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
SMT_TIME_TAG : in CGS_CALENDAR.CGS_DATE_AND_TIME
:= CGS_CALENDAR.NULL_DATE_AND_TIME;
SHOW_IT : in BOOLEAN := TRUE;
STATUS : out TES_DEFINITIONS.T_RETURN_STATUS);
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
323 von/of: 662
–– DESCRIPTION
–– This procedure sends an error message to the CGS product TES. The error
–– message is always written into the CGS test result database. By default,
–– it is also shown to the user on workstations. Only if the parameter
–– SHOW_IT is set to FALSE, then it is not shown but only logged.
–– The APPLICATION_ID is the ID returned by TES during the connect operation.
–– ERROR_MESSAGE_SHORT and ERROR_MESSAGE_LONG are two text fields of the
–– message. The short text is always immediately shown on the screen of the
–– workstation (provided SHOW_IT is TRUE) whereas the long text is only
–– visible if the user double–clicks to the error message on the screen.
–– Thus short and long texts should be carefully chosen.
–– The ERROR_TYPE can be set by the SAS as needed. ”WRN” for warnings, ”MSG”
–– or ”INFO” for messages providing just information to the user and ”ERR”
–– for reports on error shall be used (refer to VICOS_DEFINITIONS for resp.
–– constants).
–– The group code for the error message is set by CGS to ”SAS ”.
–– Two time_tags can be provided with each error message, being local time
–– and SMT. If the NULL_DATE_AND_TIME is given, CGS will add the actual time
–– as the time tag.
–– RETURN STATES
–– SUCCESS : the call was successfull
–– CURRENT_MODE_WRONG : TES is in idle or error mode or it is currently
–– not running
–– COMMUNICATION_ERROR : some communication problem exists, carefully
–– look into your system topology table, maybe TES
–– died in the meantime
–– INVALID_APPLICATION_ID : The identifier is wrong, perhaps an old one is
–– used?
–– OTHER_ERROR : an unexpected error occurred or the SAS has not
–– called READ_COMMAND in time, i.e. the time–out
–– has expired (configurable in the TES_CONFIG_FILE)
procedure READ_TIME (
APPLICATION_ID : in TES_DEFINITIONS.T_APPLICATION_ID;
LOCAL_TIME : out CGS_CALENDAR.CGS_DATE_AND_TIME;
SMT : out CGS_CALENDAR.CGS_DATE_AND_TIME;
SMT_RUNNING : out BOOLEAN;
STATUS : out TES_DEFINITIONS.T_RETURN_STATUS);
–– DESCRIPTION
–– This procedure returns the actual local time and SMT as well as the
–– current state of the SMT, i.e. whether it is running or not.
–– The application id is the one returned by TES during the connect
–– operation.
–– RETURN STATES
–– SUCCESS : the call was successfull
–– TSS_ERROR : the time synchronisation sw could not provide timing
–– information for unknown reasons
procedure READ_SMT_DETAILS (
APPLICATION_ID : in TES_DEFINITIONS.T_APPLICATION_ID;
SMT : out CGS_CALENDAR.CGS_DATE_AND_TIME;
SYNC_SW_STATUS : out BOOLEAN;
SYNC_SW_LOCKED : out BOOLEAN;
SYNC_SW_IN_LIMIT : out BOOLEAN;
SMT_SERVER : out BOOLEAN;
MTU_PRESENT : out BOOLEAN;
SMT_STATUS : out T_SMT_STATUS;

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
SMT_OFFSET : out INTEGER;
MTU_STATUS : out INTEGER;
STATUS : out TES_DEFINITIONS.T_RETURN_STATUS);
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
324 von/of: 662
–– DESCRIPTION
–– This procedure returns the detailed status of the SMT.
–– The application id is the one returned by TES during the connect
–– operation.
–– SYNC_SW_STATUS returns, whether the NTP Status file, which is updated
–– every, minute by a crontab job if NTP is running, was read and has the
–– correct format
–– SYNC_SW_LOCKED returns, whether synchronisation source for the local NTP
–– process is considered as reliable.
–– SYNC_SW_IN_LIMIT returns, whether the time deviation between the NTP
–– client and its synchronisation source is in the allowed limit
–– SMT_SERVER returns, whether the local machine is SMT server (TRUE) or not
–– MTU_PRESENT returns, whether a MTU is present (TRUE) or not
–– SMT_STATUS returns the actual SMT status
–– SMT_OFFSET returns the actual SMT offset
–– MTU_STATUS returns the actual MTU status
–– RETURN STATES
–– SUCCESS : the call was successfull
–– TSS_ERROR : the time synchronisation sw could not provide timing
–– information for unknown reasons
procedure WAIT_UNTIL (
APPLICATION_ID : in TES_DEFINITIONS.T_APPLICATION_ID;
WAKE_UP_TIME : in CGS_CALENDAR.CGS_DATE_AND_TIME;
TIME_TYPE : in CGS_CALENDAR.T_TIME_TYPE;
STATUS : out TES_DEFINITIONS.T_RETURN_STATUS);
–– DESCRIPTION
–– This procedure waits until a given wake up time which can be either local
–– time or SMT depending on parameter Time_Type.
–– The application id is the one returned by TES during the connect
–– operation.
–– RETURN STATES
–– SUCCESS : the call was successfull
–– SMT_RESET : the SMT has been reset so the wake up time may not be correct.
–– TSS_ERROR : the time synchronisation sw could not provide timing
–– information for unknown reasons
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– ADU SERVICES
––––––––––––––––––––––––––––––––––––––––––––––––––––
procedure ANNOUNCE_ADU_SERVICE (
APPLICATION_ID : in TES_DEFINITIONS.T_APPLICATION_ID;
STATUS : out TES_DEFINITIONS.T_RETURN_STATUS);
–– DESCRIPTION
–– This procedure announces to CGS that the SAS is now able to handle ADUs
–– respectively ADU requests.The application id is the ID returned by TES
–– during the connect operation.
–– RETURN STATES
–– SUCCESS : the call was successfull
–– CURRENT_MODE_WRONG : TES is in idle or error mode or it is currently
–– not running
–– COMMUNICATION_ERROR : some communication problem exists, carefully
–– look into your system topology table, maybe TES
–– died in the meantime
–– INVALID_APPLICATION_ID : The identifier is wrong, perhaps an old one is

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
325 von/of: 662
–– used?
–– OTHER_ERROR : an unexpected error occurred or the SAS has not
–– called READ_COMMAND in time, i.e. the time–out
–– has expired (configurable in the TES_CONFIG_FILE)
procedure WITHDRAW_ADU_SERVICE (
APPLICATION_ID : in TES_DEFINITIONS.T_APPLICATION_ID;
STATUS : out TES_DEFINITIONS.T_RETURN_STATUS);
–– DESCRIPTION
–– This procedure announces to CGS that the SAS is no longer able to handle
–– ADUs respectively ADU requests.The application id is the ID returned by
–– TES during the connect operation.
–– RETURN STATES
–– SUCCESS : the call was successfull
–– CURRENT_MODE_WRONG : TES is in idle or error mode or it is currently
–– not running
–– COMMUNICATION_ERROR : some communication problem exists, carefully
–– look into your system topology table, maybe TES
–– died in the meantime
–– INVALID_APPLICATION_ID : The identifier is wrong, perhaps an old one is
–– used?
–– OTHER_ERROR : an unexpected error occurred or the SAS has not
–– called READ_COMMAND in time, i.e. the time–out
–– has expired (configurable in the TES_CONFIG_FILE)
procedure SUPPLY_ADU (
APPLICATION_ID : in TES_DEFINITIONS.T_APPLICATION_ID;
ADU : in ADT_ADU.T_ADU;
STATUS : out TES_DEFINITIONS.T_RETURN_STATUS);
–– DESCRIPTION
–– This procedure sends an ADU to TES.The application id is the ID returned
–– by TES during the connect operation.The ADU is the ADU to be sent to TES.
–– RETURN STATES
–– SUCCESS : the call was successfull
–– CURRENT_MODE_WRONG : TES is in idle or error mode or it is currently
–– not running
–– COMMUNICATION_ERROR : some communication problem exists, carefully
–– look into your system topology table, maybe TES
–– died in the meantime
–– INVALID_APPLICATION_ID : The identifier is wrong, perhaps an old one is
–– used?
–– OTHER_ERROR : an unexpected error occurred or the SAS has not
–– called READ_COMMAND in time, i.e. the time–out
–– has expired (configurable in the TES_CONFIG_FILE)
procedure SUSPEND_ADU (
APPLICATION_ID : in TES_DEFINITIONS.T_APPLICATION_ID;
ADU_SID : in MPS_DEFINITIONS.SID;
STATUS : out TES_DEFINITIONS.T_RETURN_STATUS);
–– DESCRIPTION
–– This procedure indicates to TES that the ADU is from now on suspended
–– until a new ADU is sent. The application id is the ID returned
–– by TES during the connect operation.
–– RETURN STATES
–– SUCCESS : the call was successfull
–– CURRENT_MODE_WRONG : TES is in idle or error mode or it is currently
–– not running
–– COMMUNICATION_ERROR : some communication problem exists, carefully

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
326 von/of: 662
–– look into your system topology table, maybe TES
–– died in the meantime
–– INVALID_APPLICATION_ID : The identifier is wrong, perhaps an old one is
–– used?
–– OTHER_ERROR : an unexpected error occurred or the SAS has not
–– called READ_COMMAND in time, i.e. the time–out
–– has expired (configurable in the TES_CONFIG_FILE)
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– GDU SERVICES
––––––––––––––––––––––––––––––––––––––––––––––––––––
procedure ANNOUNCE_GDU_SERVICE (
APPLICATION_ID : in TES_DEFINITIONS.T_APPLICATION_ID;
STATUS : out TES_DEFINITIONS.T_RETURN_STATUS);
–– DESCRIPTION
–– This procedure announces to CGS that the SAS is now able to handle
–– GDUs.The application id is the ID returned by TES during the connect
–– operation.
–– RETURN STATES
–– SUCCESS : the call was successfull
–– CURRENT_MODE_WRONG : TES is in idle or error mode or it is currently
–– not running
–– COMMUNICATION_ERROR : some communication problem exists, carefully
–– look into your system topology table, maybe TES
–– died in the meantime
–– INVALID_APPLICATION_ID : The identifier is wrong, perhaps an old one is
–– used?
–– OTHER_ERROR : an unexpected error occurred or the SAS has not
–– called READ_COMMAND in time, i.e. the time–out
–– has expired (configurable in the TES_CONFIG_FILE)
procedure WITHDRAW_GDU_SERVICE (
APPLICATION_ID : in TES_DEFINITIONS.T_APPLICATION_ID;
STATUS : out TES_DEFINITIONS.T_RETURN_STATUS);
–– DESCRIPTION
–– This procedure announces to TES that the SAS is no longer able to handle
–– GDUs.The application id is the ID returned by TES during the connect
–– operation.
–– RETURN STATES
–– SUCCESS : the call was successfull
–– CURRENT_MODE_WRONG : TES is in idle or error mode or it is currently
–– not running
–– COMMUNICATION_ERROR : some communication problem exists, carefully
–– look into your system topology table, maybe TES
–– died in the meantime
–– INVALID_APPLICATION_ID : The identifier is wrong, perhaps an old one is
–– used?
–– OTHER_ERROR : an unexpected error occurred or the SAS has not
–– called READ_COMMAND in time, i.e. the time–out
–– has expired (configurable in the TES_CONFIG_FILE)
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– DATA PROCESSING SERVICES
––––––––––––––––––––––––––––––––––––––––––––––––––––
procedure READ_RAW_VALUE (
APPLICATION_ID : in TES_DEFINITIONS.T_APPLICATION_ID;
ENDITEM_PATHNAME : in STRING;
VALUE_ALTERNATIVE : out VICOS_DEFINITIONS.T_RAW_VALUE_ALTERNATIVES;

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
INT_VALUE : out NUMERIC_TYPES.INTEGER32;
UINT_VALUE : out NUMERIC_TYPES.UNSIGNED_INTEGER32;
FLOAT_VALUE : out NUMERIC_TYPES.SINGLE_FLOAT;
BYTESTREAM_VALUE : in out MPS_DEFINITIONS.DYNAMIC_STRING;
STATUS : out TES_DEFINITIONS.T_RETURN_STATUS);
–– DESCRIPTION
–– This procedure read the current raw value of an enditem from CGS. Since
–– enditems can have several raw value alternatives, the procedure returns
–– the type of raw value in parameter VALUE_ALTERNATIVE. Depending on the
–– value of this parameter, the other ..._VALUE parameter will hold the
–– actual raw value returned. The other ones will be zeroed or empty.
–– APPLICATION_ID is the ID returned by TES during the connect operation.
–– The enditem is identified through its database pathname. For simplicity
–– reasons this is a string
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
327 von/of: 662
–– RETURN STATES
–– SUCCESS : the call was successfull
–– CURRENT_MODE_WRONG : TES is in idle or error mode or it is currently
–– not running
–– COMMUNICATION_ERROR : some communication problem exists, carefully
–– look into your system topology table, maybe TES
–– died in the meantime
–– INVALID_APPLICATION_ID : The identifier is wrong, perhaps an old one is
–– used?
–– ENDITEM_NOT_ACQUIRED : the enditem is currently not acquired, so there
–– is no raw value
–– ENDITEM_UNKNOWN : the enditem is unknown, so the pathname is wrong
–– or the item is maintained on another test node.
–– OTHER_ERROR : an unexpected error occurred or the SAS has not
–– called READ_COMMAND in time, i.e. the time–out
–– has expired (configurable in the TES_CONFIG_FILE)
procedure READ_ENGINEERING_VALUE (
APPLICATION_ID : in TES_DEFINITIONS.T_APPLICATION_ID;
ENDITEM_Pathname : in STRING;
VALUE_ALTERNATIVE : out MPS_DEFINITIONS.T_SW_TYPE;
INT_VALUE : out NUMERIC_TYPES.INTEGER32;
FLOAT_VALUE : out NUMERIC_TYPES.SINGLE_FLOAT;
STATECODE_VALUE : out MPS_DEFINITIONS.STATE_CODE;
BYTESTREAM_VALUE : in out MPS_DEFINITIONS.DYNAMIC_STRING;
STATUS : out TES_DEFINITIONS.T_RETURN_STATUS);
–– DESCRIPTION
–– This procedure read the current engineering value of an enditem from CGS.
–– Since enditems can have several value alternatives, the procedure returns
–– the type of value in parameter VALUE_ALTERNATIVE. Depending on the value
–– of this parameter, the other ..._VALUE parameter will hold the actual
–– engineering value returned. The other ones will be zeroed or empty.
–– Note that although MPS_DEFINITIONS.T_SW_TYPE provides many more
–– alternatives only integer, float, statecode or bytestream values can be
–– returned since these correspond to the list of allowed CGS database
–– measurement or SW variable enditems.
–– APPLICATION_ID is the ID returned by TES during the connect operation.
–– The enditem is identified through its database pathname. For simplicity
–– reasons this is a string
–– RETURN STATES
–– SUCCESS : the call was successfull
–– CURRENT_MODE_WRONG : TES is in idle or error mode or it is currently
–– not running
–– COMMUNICATION_ERROR : some communication problem exists, carefully
–– look into your system topology table, maybe TES
–– died in the meantime
–– INVALID_APPLICATION_ID : The identifier is wrong, perhaps an old one is
–– used?

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
328 von/of: 662
–– ENDITEM_NOT_ACQUIRED : the enditem is currently not acquired, so there
–– is no value
–– ENDITEM_UNKNOWN : the enditem is unknown, so the pathname is wrong
–– or the item is maintained on another test node.
–– OTHER_ERROR : an unexpected error occurred or the SAS has not
–– called READ_COMMAND in time, i.e. the time–out
–– has expired (configurable in the TES_CONFIG_FILE)
procedure WRITE_ENGINEERING_VALUE (
APPLICATION_ID : in TES_DEFINITIONS.T_APPLICATION_ID;
ENDITEM_PATHNAME : in STRING;
VALUE : in NUMERIC_TYPES.INTEGER32;
STATUS : out TES_DEFINITIONS.T_RETURN_STATUS);
procedure WRITE_ENGINEERING_VALUE (
APPLICATION_ID : in TES_DEFINITIONS.T_APPLICATION_ID;
ENDITEM_PATHNAME : in STRING;
VALUE : in NUMERIC_TYPES.UNSIGNED_INTEGER32;
STATUS : out TES_DEFINITIONS.T_RETURN_STATUS);
procedure WRITE_ENGINEERING_VALUE (
APPLICATION_ID : in TES_DEFINITIONS.T_APPLICATION_ID;
ENDITEM_PATHNAME : in STRING;
VALUE : in NUMERIC_TYPES.SINGLE_FLOAT;
STATUS : out TES_DEFINITIONS.T_RETURN_STATUS);
procedure WRITE_ENGINEERING_VALUE (
APPLICATION_ID : in TES_DEFINITIONS.T_APPLICATION_ID;
ENDITEM_PATHNAME : in STRING;
VALUE : in MPS_DEFINITIONS.STATE_CODE;
STATUS : out TES_DEFINITIONS.T_RETURN_STATUS);
procedure WRITE_ENGINEERING_VALUE (
APPLICATION_ID : in TES_DEFINITIONS.T_APPLICATION_ID;
ENDITEM_PATHNAME : in STRING;
VALUE : in MPS_DEFINITIONS.DYNAMIC_STRING;
STATUS : out TES_DEFINITIONS.T_RETURN_STATUS);
–– DESCRIPTION
–– This procedure writes an engineering value of an enditem of type
–– EGSE_...SW_VARIABLE.
–– The application id is the ID returned by TES during the connect
–– operation.
–– The pathname is the pathname of the enditem to be written. For
–– simplicity reasons this is a string.
–– The procedure comes in overloaded versions for the different types of
–– values to be written.
–– RETURN STATES
–– SUCCESS : the call was successfull
–– CURRENT_MODE_WRONG : TES is in idle or error mode or it is currently
–– not running
–– COMMUNICATION_ERROR : some communication problem exists, carefully
–– look into your system topology table, maybe TES
–– died in the meantime
–– INVALID_APPLICATION_ID : The identifier is wrong, perhaps an old one is
–– used?
–– ENDITEM_UNKNOWN : the enditem is unknown, so the pathname is wrong
–– or the item is maintained on another test node.
–– NOT_A_SW_VALUE : the enditem exists but is not a SW variable
–– TYPE_MISMATCH : the enditem’s type defined in the database and
–– the data supplied do not match.
–– OTHER_ERROR : an unexpected error occurred or the SAS has not
–– called READ_COMMAND in time, i.e. the time–out
–– has expired (configurable in the TES_CONFIG_FILE)

Space Infrastructure
––
–– OBSOLETE
––
procedure SET_POLLING_INTERVAL
(MILLI_SECONDS : in NATURAL := 10);
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
329 von/of: 662
–– DESCRIPTION
–– This procedure sets the interval at which the input of an SAS is polled
–– for incomming commands.
–– When being called in an SAS, this must occure before the call of the
–– CONNECT operation, but it is not necessary to call this procedure because
–– the default polling interval is set to 10 milliseconds.
–– If an SAS needs to respond to commands quickly (e.g. for GDUs) then the
–– intervall should be set to a value between 10 and 100 [milliseconds]. If
–– a SAS produces only ADUs or doesn’t have stringent repsonse time
–– requirements, a higher value (100 .. 300 [milliseconds]) should be
–– choosen.
–– A high value generally reduces the UNIX system load and results in better
–– overall performance of the test node.
–– EXCEPTIONS: none, any value will be accepted.
–– Note: The procedure SET_POLLING_INTERVALL is not effective anymore in
–– CGS 4.2.0 onwards. The polling mechanism of the underlying Network
–– Software has been replaced by Signal Handling to improve performance
–– The procedure has been kept, however, to guarantee upwards compatibility
––
–– END OBSOLETE
––
end TES_API;

Space Infrastructure
7.8 VICOS Housekeeping Values
Informal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
330 von/of: 662
VICOS shall internally maintain a set of housekeeping data and make these available as end–items to the user.
These housekeeping data are local state information about the current test node as well as database server node
status information (provided by exactly one test node: the MTP).
These end–items are defined in the mission data base in the subtree that is loaded into a test node with the
load_scoe operation.
When defining the database end–item the reference to a housekeeping value is made by inclusion of the housekeeping
values’ ID number in the end–item’s definition. Also, a default value has to be defined for the end–item.
In case the actual housekeeping value cannot be provided, then the default value will be provided.
Typically, housekeeping data are ”updated” when something significant or relevant happens. However, some
of the variables are ”computed” cyclically, i.e. the values 10, 90, 202, 207, 212 and so on, 1001 ... 1051. Number
12 is updated each time a record is read from the archive file. The cyclically computed HK values can in certain
instances be updated also in the middle of a cycle where they would not be updated normally.
Formal Interface Description
In the formal part of this interface (Interface Definition section), the detailed list of housekeeping values is given.

Daimler–Benz Aerospace
Raumfahrt Infrastruktur
331
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
TES shall internally maintain a set of housekeeping data and make these available to the user. These housekeeping data are local state information
about the current test node as well as database server node status information (provided by exactly one test node: the MTP).
The information maintained in housekeeping values is made available to the user by means of the S/W variable construct, i.e. for each housekeeping
value the user wants to use he has to define a Software variable of appropriate type in his/her configuration database. Thus, the user is free
to choose appropriate names for his/her values. Reference to a certain housekeeping value is made through its ID in the Software variable definition.
In the following, the list of housekeeping values is given.
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
331 von/of: 662
Daimler–Benz Aerospace – All Rights Reserved – Copyright per DIN 34

Daimler–Benz Aerospace
Raumfahrt Infrastruktur
332
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
332 von/of: 662
ID_Number
Version
Name Purpose Format Initial Value
1 Init_Path Pathname used for LOAD_SCOE, i.e. the subtree initially loaded String ”” 3.1.2
2 TES_Mode Current Test Execution Mode:
Alternatives: NONE, NORMAL, REPLAY, SIMULATE
Discrete $NONE 3.2
3 TN_Status TN Status:
Alternatives: IDLE, RUNNING, SUSPEND, ERROR
Discrete $IDLE 3.2
4 MTP_Mode The value for the MTP mode
Alternatives: SCOE, MTP
Discrete $SCOE 3.2
5 CCU internal version MDA internal identifier of the CCU version used INTEGER 0 4.2
6 Replay_Speed The replay speed INTEGER 100 4.1
7 Archive_Time The cycle time in minutes an archive file will be closed automatically INTEGER 0 3.2
8 Archive_State The current state of archiving:
Alternatives: DISABLED, ENABLED
Discrete $DISABLED 3.2
10 Local_Time Actual Local Clock Value STRING (*) 3.2
11 SMT Actual Simulated Mission Time STRING (*) 3.2
12 RLT Recorded Local Time as read from time tags of archived data STRING (*) 4.1
20 Active_APs Number of started (but not terminated) APs INTEGER 0 3.2
21 Susp._APs Number of APs explicitely suspended via system. lib. call INTEGER 0 3.2
30 RPL_Begin_Time Replay begin time selected during init String (*) 4.1
31 RPL_End_Time Replay end time selected during init String (*) 4.1
90 Free_Disk Number of free KBytes on local disk INTEGER 0 3.2
Note: RSMT is not used anylonger since in replay mode RSMT is identical to SMT.
(*) Format of the time string is as defined in package CGS_CALENDAR.CGS_DATE_STRING + 1 blank char + CGS_CALENDAR.CGS_TIME_STRING.
Initial value is CGS_CALENDAR.NULL_DATE_AND_TIME.
Daimler–Benz Aerospace – All Rights Reserved – Copyright per DIN 34

Daimler–Benz Aerospace
Raumfahrt Infrastruktur
333
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
333 von/of: 662
ID_Number
Version
Name Purpose Format Initial Value
100 SAS1_Name Name of Appl. Progr. 1 (Pathname) that has connected to TES String ”” 3.2
101 SAS1_Service The service announced by the SAS:
Alternatives: NONE, ADU_SERV, GDU_SERV, ADU+GDU
Discrete $NONE 3.2
102 SAS1_Errors The number of error messages sent by this SAS INTEGER 0 3.2
103 SAS1_Last_Err The last error message sent by this SAS String ”” 3.2
104
...
SAS1_Link_ID The Link ID for the SAS number 1 INTEGER 0 3.2
195 SAS20_Name Name of Appl. Progr. 20 (Pathname) that has connected to TES String ”” 3.2
196 SAS20_Service The service announced by the SAS (see 101) Discrete $NONE 3.2
197 SAS20_Errors The number of error messages sent by this SAS INTEGER 0 3.2
198 SAS20_Last_E. The last error message sent by this SAS String ”” 3.2
199 SAS20_Link_ID The Link ID for the SAS number 20 INTEGER 0 3.2
200 AP_1_Name Pathname of AP1 String ”” 3.2
201 AP_1_Status Status of AP 1: Discrete $NOT_RUN 3.2
Alternatives: NOT_RUN, INITIAL, RUNNING, SUSPEND, TERMINAT
202 AP_1_Stmt. Current UCL Statement of AP INTEGER 0 3.2
203 AP_1_HCI_ID The identification of the HCI that has started this AP or the parent AP STRING ”” 3.2
204 AP_1_ID The AP identifier INTEGER 0 3.2
. . .
295 AP_20_Name Pathname of AP20 String ”” 3.2
296 AP_20_Status Status of AP 20 (see 201) Discrete $NOT_RUN 3.2
297 AP_20_Stmt. Current UCL Statement of AP INTEGER 0 3.2
298 AP_20_HCI_ID The identification of the HCI that has started this AP or the parent AP STRING ”” 3.2
299 AP_20_ID The AP identifier INTEGER 0 3.2
Daimler–Benz Aerospace – All Rights Reserved – Copyright per DIN 34

Daimler–Benz Aerospace
Raumfahrt Infrastruktur
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
ID_Number Name Purpose Format Initial Value
Version
334
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
334 von/of: 662
301 Nb._Enditems Number of enditems that can be monitored (loaded from MDB) INTEGER 0 3.2
302 Nb._Enabled Number of enditems enabled for monitoring INTEGER 0 3.2
303 Nb._Discrete No. of discrete enditems that can be monitored (loaded from MDB) INTEGER 0 3.2
305 Nb._Analog No. of analog enditems that can be monitored (loaded from MDB) INTEGER 0 3.2
306 Nb._bytestream No. of bytestream enditems that can be monitored (loaded from MDB) INTEGER 0 3.2
310 Nb_Soft OOL Number of enditems currently out of soft limit (1) INTEGER 0 3.2
311 Nb_Hard OOL Number of enditems currently out of hard limit (1) INTEGER 0 3.2
312 Nb._Soft_exceptions Number of soft limit violations since last START (1) INTEGER 0 3.2
313 Nb._Hard_exceptions Number of hard limit violations since last START (1) INTEGER 0 3.2
320 Nb. Acquired Number of measurements currently acquired INTEGER 0 4.2
321 Nb. EVL Nb of acquired measurements or SW variables or derived values with EVL INTEGER 0 4.2
322 Nb. Measurements Number of meaurements defined INTEGER 0 4.3
323 Nb. SW_Variables Number of software variables defined INTEGER 0 4.3
324 Nb. Derived_Values Number of derived values defined INTEGER 0 4.3
400 Nb._stimuli Number of GDUs sent out since last START incl. erroneous ones INTEGER 0 3.2
401 Stimuli_Errors Number of GDUs with errors in SAS/FEE since last START INTEGER 0 3.2
402 Wrong_Stimulus Pathname of last stimulus that resulted in an error String ” 3.2
404 Destination Destination of last erroneous stimulus (SAS name) String ” 3.2
410 Nb._of_digital_GDUs Number of digital output GDUs (discreteStimuli) (loaded from MDB) INTEGER 0 3.2
411 Nb._of_analog_GDUs Number of analog output GDUs (analog Stimuli) (loaded from MDB) INTEGER 0 3.2
412 Nb._of_TC_GDUs Number of GDUs with CCSDS TCs (loaded from MDB) INTEGER 0 3.2
413 Nb._of_GDUs Total number of GDUs (loaded from MDB) INTEGER 0 3.2
414 Nb._of_bin.pack.GDUs Number of binary packet GDUs (loaded from MDB) INTEGER 0 4
415 Nb.GDU_Verif_Succ Number of GDUs sent with successful verification INTEGER 0 4.3
416 Nb.GDU_Verif_Fail Number of GDUs sent with failed verification INTEGER 0 4.3
420 Nb. of SW cmd. sent Number of SW commands sent INTEGER 0 4.1
421 Nb. of rtn. packets Number of return packets received for SW commands INTEGER 0 4.1
500 AP_21_Name Pathname of AP21 String ”” 4.3
501 AP_21_Status Status of AP 21 (see 201) Discrete $NOT_RUN 4.3
502 AP_21_Stmt. Current UCL Statement of AP INTEGER 0 4.3
503 AP_21_HCI_ID The identification of the HCI that has started this AP or the parent AP STRING ”” 4.3
504 AP_21_ID The AP identifier INTEGER 0 4.3
Daimler–Benz Aerospace – All Rights Reserved – Copyright per DIN 34

Daimler–Benz Aerospace
Raumfahrt Infrastruktur
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
335 von/of: 662
. . .
595 AP_40_Name Pathname of AP40 String ”” 4.3
596 AP_40_Status Status of AP 40 (see 201) Discrete $NOT_RUN 4.3
597 AP_40_Stmt. Current UCL Statement of AP INTEGER 0 4.3
598 AP_40_HCI_ID The identification of the HCI that has started this AP or the parent AP STRING ”” 4.3
599 AP_40_ID The AP identifier INTEGER 0 4.3
REMARKS:
(1) an enditem is out–of–limit if it is enabled for monitoring and its value is outside the defined range, independently from any monitoring exception and from alarm
counter, e.g. going from out of high hard limit to out of high nominal limit will set the HK value Nb._Soft_exceptions but will not lead to any monitoring exception.
335
Daimler–Benz Aerospace – All Rights Reserved – Copyright per DIN 34

Daimler–Benz Aerospace
Raumfahrt Infrastruktur
336
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
336 von/of: 662
ID_Number
Version
Name Purpose Format Initial Value
601 Served_WSs Number of connected workstations (HCI) INTEGER 0 3.2
700 Nb_COND_ENDITEMS number of conditions defined
4.1
INTEGER 0
701 Nb_CONDITIONS
4.1
Number of enditems carrying
conditions
INTEGER 0
702 Nb_TRIGGERED_COND Number of actions triggered
4.1
from conditions since last start
INTEGER 0
900 TIME_OF_EXCEPTION time (in seconds since midnight)
of detection of a monitoring exception
FLOAT 0.0 4.1
901 TIME_OF_START_AP time (in seconds since midnight)
4.1
of the last start of an AP
FLOAT 0.0
902 TIME_OF_RESUME_AP time (in seconds since midnight) FLOAT 0.0 4.1
of the last resume of an AP
Daimler–Benz Aerospace – All Rights Reserved – Copyright per DIN 34

Daimler–Benz Aerospace
Raumfahrt Infrastruktur
337
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
337 von/of: 662
ID_Number
Version
Name Purpose Format Initial Value
1001 PR1_Status The status of printer1:
Alternatives: DISABLED, ENABLED
Discrete $DISABLED 3.2
1002 PR2_Status The status of printer 2 (see 1001) Discrete $DISABLED 3.2
1003 PQ1_Status The status of print queue 1:
Alternatives: OFF, READY, PRINTING, NO_PAPER, NO_TONER
Discrete $OFF 3.2
1004 PQ2_Status The status of print queue 2 (see 1003) Discrete $OFF 3.2
1005 PQ1_Jobs The number of jobs in print queue 1 INTEGER 0 3.2
1006 PQ2_Jobs The number of jobs in print queue 2 INTEGER 0 3.2
1011 MD_Free_Spac The free disc space on the magnetic disc in kilobytes INTEGER 0 3.2
1012 FA_1_Dev_Status The device status of the long term storage medium Discrete $OK 3.2
Alternatives:OK, NOT_OK
1020 TRBD_Overall_status The overal status of the test result data base: Discrete $OK 3.2
Alternatives: OK, NOT_OK
1050 Session_Name The name of the current test execution session String ”” 3.2
1051 TRDB_Eval_U The number of evaluation users connected to TRDB INTEGER 0 3.2
1060 TRDB_Event_Usage The percentage of event table space used INTEGER 0 4.1
1061 TRDB_MA_Usage The percentage of master archive table space used INTEGER 0 4.1
1062 TRDB_Misc_Usage he percentage of miscellaneous table space used INTEGER 0 4.1
1100 T_SYNC The local clock of this machine is synchronised with the NTP server Discrete $FALSE 3.2
Alternative: TRUE, FALSE
1101 MTU_PRESENT The machine has an external master time unit (MTU) Discrete $FALSE 3.2
Alternative: TRUE, FALSE
1102 SMT_STATUS The status of the SMT Discrete $NOT_INIT 3.2
Alternative: NOT_INIT, STOPPED, RUNNING
Daimler–Benz Aerospace – All Rights Reserved – Copyright per DIN 34

Space Infrastructure
7.9 System Libraries
7.9.1 UCL Ground System Library
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
338 von/of: 662
The GROUND_LIBRARY contains all standard ground commands used for control of the ground system.
Library Id (Body_Id): 2
7.9.1.1 Routines Summary
The Ground UCL library routines are:
CLOCK REMOVE_PICTURE
CLOSE_ARCHIVE RESET_APPLICATION
DELAY RESUME_AP
DISABLE_ARCHIVING ROUTE_TO_SAS
DISABLE_CONDITIONS SEND_SIMULATED_ADU
DISABLE_ENDITEM SET_BITS_IN_SIMULATED_ADU
DISABLE_EVL SET_DELTA_LIMIT
DISABLE_MONITORING SET_EXCEPTION_COUNT
DISPLAY_PICTURE SET_EXPECTED_STATE
DOWNLOAD SET_EXPECTED_VALUE
ENABLE_ARCHIVING SET_HIGH_LIMIT
ENABLE_CONDITIONS SET_INTEGER_DELTA_LIMIT
ENABLE_ENDITEM SET_INTEGER_HIGH_LIMIT
ENABLE_EVL SET_INTEGER_LOW_LIMIT
ENABLE_MONITORING SET_LIMIT_SET
ENABLE_ON_BYTE_STREAM SET_LIMIT_SET_ON_BYTE_STREAM
ENABLE_ON_FLOAT SET_LIMIT_SET_ON_FLOAT
ENABLE_ON_INTEGER SET_LIMIT_SET_ON_INTEGER
ENABLE_ON_STATECODE SET_LIMIT_SET_ON_STATECODE
EXECUTE_AP SET_LOW_LIMIT
GET_ACQUISITION_STATUS SET_PROCESSING
GET_AP_ID SET_SIMULATED_ENDITEM_VALUE
GET_AP_STATUS START_ACQUISITION
GET_APPLICATION_ID START_AP_ON_BYTE_STREAM
GET_APPLICATION_NAME START_AP_ON_FLOAT
GET_APPLICATION_STATUS START_AP_ON_INTEGER
GET_CONDITION START_AP_ON_STATECODE
GET_CONDITION_ITEM START_APPLICATION
GET_ENDITEM_MONITOR_STATUS START_SMT
GET_FULL_ENDITEM_MONITOR_STATUS STOP_ACQUISITION
GET_PROCESSING_STATE STOP_SMT
GET_VERIFICATION_STATUS
INIT_APPLICATION SUSPEND_AP
IS_LOCAL_NODE SYNCHRONISE_WITH_AP
ISSUE
ISSUE_AND_VERIFY UCL_STATUS
LOAD_APPLICATION UNLOAD_APPLICATION
LOAD_UCL USER_EVENT
LOG
NUMBER_CONDITIONS WAIT_FOR_ADU
NUMBER_OF_CONDITION_ITEMS WAIT_UNTIL
OWN_AP_ID* WITHDRAW_CONDITION
PATHNAME_TO_STRING WRITE_MESSAGE_TO_AP*
READ_MESSAGE_FROM_AP* WRITE_MESSAGE_TO_APPLICATION*
READ_MESSAGE_FROM_APPLICATION* WRITE_MESSAGE_TO_USER*
READ_MESSAGE_FROM_USER*
READ_NUMBER_FROM_USER*

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
339 von/of: 662
NOTE: The routines marked with asterisks (*) cannot be called from HLCL, neither interactively nor
out of HLCL sequences.
7.9.1.2 UCL Ground System Library Specification
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– *******************************************
–– GROUND_LIBRARY UCL System Library
–– *******************************************
––
––ABSTRACT––
–– Defines Procedures to control the execution of CGS/VICOS
–– Must be compiled for ground and with Body Id = 2
––
––IDENTIFICATION––
–– PROJECT NAME : CGS
–– OBJECT NAME : GROUND_LIBRARY System Library
–– VERSION : ##V##CGS_4.3.0
–– Note: Changes Procedure Numbers !
–– CGS CM : ”%Z%%Z%”
––*–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––CONTENTS––
–– COMPILER : UCLC
–– LANGUAGE : UCL
––CHANGE HISTORY
–– PIRN 8076, Issue 1/– for CGS V4.3.0:
–– Add derived values to type definitions
–– Add Command Verification Status
–– Add procedures ISSUE_AND_VERIFY,GET_VERIFICATION_STATUS,ENABLE_CONDITION,
–– DISABLE_CONDITION
–– Allow virtual trees for set_limit_set operations
–– Update acquisition status
–– PIRN 8003, Issue 1/C for CGS V4.2.0.9: Add new procedures
–– Add new procedures GET_ACQUISITION_STATUS, GET_values
–– GET_APPLICATION_ID, GET_APPLICATION_NAME
–– Add CDU to all Virtual Pathname definitions
–– Add constants/array for UCL Status Text
–– Add conversion routines for pathnames to text / statecode to text
–– PIRN 8003, Issue 1/B for CGS V4.1.1.9:
–– update types and operations for the control of conditions
–– add UCL return constant NOT_OK
–– PIRN 8003, Issue 1/A for CGS V4.1.1.9:
–– Include operation ROUTE_TO_SAS
–– Include types and operations for control of conditions
–– Add additional parameter ”ADU” to commands START_ACQUISITION,
–– STOP_ACQUISITION and ENABLE_MONITORING
–– PIRN 8003, Issue 1/– for CGS V4.1.1.8:
–– Include interfaces for setting / reading integer limits
–– Provide the value of the alarm counter for all monitor end–items
–– Include operation to identify the EGSE node
–– Include operation to get the AP_ID
–– Handling of default limit set in ENABLE_MONITORING
–– PIRN 6012, Issue 1/D for CGS V4.0:
–– Include command GET_FULL_ENDITEM_MONITOR_STATUS
–– Extend ISSUE_ITEM_NAME: add EGSE_BINARY_PACKET
–– Modified AP_EXECUTION_STATE / AP_COMPLETION_STATE
––END HISTORY

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
––
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
library GROUND_LIBRARY;
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– TYPES
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
type USER_MESSAGE = STRING (255);
type VALUE_STRING = STRING (255);
type ACQUISITION_COLLECTION =
PATHNAME (EGSE_INTEGER_MEASUREMENT,
EGSE_FLOAT_MEASUREMENT,
EGSE_DISCRETE_MEASUREMENT,
EGSE_BYTE_STREAM_MEASUREMENT,
EGSE_INTEGER_SW_VARIABLE,
EGSE_FLOAT_SW_VARIABLE,
EGSE_DISCRETE_SW_VARIABLE,
EGSE_BYTE_STREAM_SW_VARIABLE,
EGSE_INTEGER_DERIVED_VALUE,
EGSE_FLOAT_DERIVED_VALUE,
EGSE_DISCRETE_DERIVED_VALUE,
EGSE_STRING_DERIVED_VALUE,
EGSE_MONITOR_LIST,
ADU_DESCRIPTION,
CDU,
VIRTUAL);
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
340 von/of: 662
type ADU_NAME = PATHNAME (ADU_DESCRIPTION);
–– ADU_DESCRIPTION covers the MDB enditem types
–– CCSDS_ADU_DESCRIPTION, UNSTRUCTURED_ADU_DESCRIPTION and
–– STRUCTURED_ADU_DESCRIPTION
–– (used with this meaning also in other type definitions)
type ANALOG_MONITOR_ITEM_NAME =
PATHNAME (EGSE_INTEGER_MEASUREMENT,
EGSE_FLOAT_MEASUREMENT,
EGSE_INTEGER_SW_VARIABLE,
EGSE_FLOAT_SW_VARIABLE,
EGSE_INTEGER_DERIVED_VALUE,
EGSE_FLOAT_DERIVED_VALUE);
type INTEGER_MONITOR_ITEM_NAME =
PATHNAME (EGSE_INTEGER_MEASUREMENT,
EGSE_INTEGER_SW_VARIABLE,
EGSE_INTEGER_DERIVED_VALUE);
type ROUTE_SAS_ITEM_NAME =
PATHNAME (GDU_DESCRIPTION_LIST,
EGSE_ANALOG_STIMULUS,
EGSE_DISCRETE_STIMULUS,
EGSE_BINARY_PACKET,
EGSE_PREDEFINED_TC,
ADU_DESCRIPTION,
CDU,
VIRTUAL);

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
341 von/of: 662
type AP_STATE =
(AP_RUNNING, AP_SUSPENDED, –– AP still exists in the system; current state
AP_UNKNOWN, –– no such AP (may be terminated)
AP_SUCCESS, AP_FAILURE, AP_ABORTED); –– result of synchronize with AP
type AP_EXECUTION_STATE =
AP_STATE (AP_RUNNING .. AP_UNKNOWN); –– see AP_STATE comment
type AP_COMPLETION_STATE =
AP_STATE (AP_UNKNOWN .. AP_ABORTED); –– see AP_STATE comment
type AP_ID = INTEGER;
type AP_ID_LIST = ARRAY (1..20) OF AP_ID;
type AP_NAME = PATHNAME (UCL_AUTOMATED_PROCEDURE);
type APPLICATION_ERROR_MESSAGE = USER_MESSAGE;
type APPLICATION_ID = INTEGER;
type APPLICATION_NAME = STRING (20);
type APPLICATION_STATE =
(SAS_UNLOADED, SAS_RESET, SAS_INIT, SAS_RUNNING, SAS_ABORTED);
type BIT_COUNT = INTEGER (1 .. 32);
type BYTE_STREAM_MONITOR_ITEM_NAME =
PATHNAME (EGSE_BYTE_STREAM_MEASUREMENT,
EGSE_BYTE_STREAM_SW_VARIABLE,
EGSE_STRING_DERIVED_VALUE);
type DISCRETE_MONITOR_ITEM_NAME =
PATHNAME (EGSE_DISCRETE_MEASUREMENT,
EGSE_DISCRETE_SW_VARIABLE,
EGSE_DISCRETE_DERIVED_VALUE);
type DOWNLOAD_ITEM_NAME = PATHNAME (EGSE_SOFTWARE);
type ISSUE_ITEM_NAME =
PATHNAME (GDU_DESCRIPTION_LIST,
EGSE_ANALOG_STIMULUS,
EGSE_DISCRETE_STIMULUS,
EGSE_BINARY_PACKET,
EGSE_PREDEFINED_TC);
type SINGLE_GDU_NAME =
PATHNAME (EGSE_ANALOG_STIMULUS,
EGSE_DISCRETE_STIMULUS,
EGSE_BINARY_PACKET,
EGSE_PREDEFINED_TC);
type LIMIT_SET_NUMBER = INTEGER (0..5);
type MONITOR_COLLECTION =
PATHNAME (EGSE_INTEGER_MEASUREMENT,
EGSE_FLOAT_MEASUREMENT,
EGSE_DISCRETE_MEASUREMENT,
EGSE_BYTE_STREAM_MEASUREMENT,
EGSE_INTEGER_SW_VARIABLE,

Space Infrastructure
EGSE_FLOAT_SW_VARIABLE,
EGSE_DISCRETE_SW_VARIABLE,
EGSE_BYTE_STREAM_SW_VARIABLE,
EGSE_INTEGER_DERIVED_VALUE,
EGSE_FLOAT_DERIVED_VALUE,
EGSE_DISCRETE_DERIVED_VALUE,
EGSE_STRING_DERIVED_VALUE,
EGSE_MONITOR_LIST,
CDU,
VIRTUAL);
type MONITOR_ITEM_NAME =
PATHNAME (EGSE_INTEGER_MEASUREMENT,
EGSE_FLOAT_MEASUREMENT,
EGSE_DISCRETE_MEASUREMENT,
EGSE_BYTE_STREAM_MEASUREMENT,
EGSE_INTEGER_SW_VARIABLE,
EGSE_FLOAT_SW_VARIABLE,
EGSE_DISCRETE_SW_VARIABLE,
EGSE_BYTE_STREAM_SW_VARIABLE,
EGSE_INTEGER_DERIVED_VALUE,
EGSE_FLOAT_DERIVED_VALUE,
EGSE_DISCRETE_DERIVED_VALUE,
EGSE_STRING_DERIVED_VALUE);
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
type MONITOR_STATUS = (MONITORING_DISABLED, IN_LIMITS, OUT_OF_LIMITS);
type EXTENDED_MONITOR_STATUS =
(DISABLED, NOT_ACQUIRED, NOMINAL,
INTERRUPTED, –– for delta limits only
NON_NOMINAL, –– for non–numeric items & delta limits
OUT_OF_HIGH_LIMIT, –– for numeric absolute limits
OUT_OF_LOW_LIMIT); –– dto.
type ACQUISITION_STATUS =
(VALID,
NOT_ACQ,
NOT_RECVD,
NOT_MAINTAINED,
DISAB,
INVALID,
STATIC);
type LIMIT_VALUE = record
case IS_INT : BOOLEAN
when TRUE : I_VALUE : INTEGER;
when FALSE : R_VALUE : REAL;
end case;
end record;
type OPTIONAL_NUMERIC_LIMIT = record
case DEFINED : BOOLEAN
when FALSE :
when TRUE : VALUE : LIMIT_VALUE;
end case;
end record;
type OPTIONAL_STATECODE = record
case DEFINED : BOOLEAN
when FALSE :
when TRUE : VALUE : STATECODE;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
342 von/of: 662

Space Infrastructure
end case;
end record;
type OPTIONAL_VALUE_STRING = record
case DEFINED : BOOLEAN
when FALSE :
when TRUE : VALUE : VALUE_STRING;
end case;
end record;
type NUMERIC_LIMITS = record
HIGH,
LOW,
DELTA : OPTIONAL_NUMERIC_LIMIT;
end record;
type MONITOR_ITEM_CLASS = (NUMERIC, DISCRETE, BYTE_STREAM);
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
type FULL_MONITOR_STATUS = record
case LIMITS_DEFINED : BOOLEAN
when FALSE :
when TRUE :
CURRENT_LIMIT_SET : INTEGER;
NOMINAL_STATUS : EXTENDED_MONITOR_STATUS;
case ITEM_CLASS : MONITOR_ITEM_CLASS
when NUMERIC : DANGER_STATUS,
DELTA_STATUS,
DELTA_DANGER_STATUS :
EXTENDED_MONITOR_STATUS;
DANGER,
NOMINAL: NUMERIC_LIMITS;
when DISCRETE : EXPECTED_STATE : OPTIONAL_STATECODE;
when BYTE_STREAM : EXPECTED_STRING : OPTIONAL_VALUE_STRING;
end case;
ALARM_COUNT : UNSIGNED_INTEGER;
end case;
end record;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
343 von/of: 662
type CMD_VERIFICATION_STATUS =
(STARTED, –– Verification is started
–– (i.e. is in Activation Delay)
IN_PROGRESS, –– Verification is in progress
–– (i.e. is in Verification Timeout)
TC_VERIF_OK, –– Verification performed with success
TC_VERIF_FAILED, –– Verification performed with no success
–– (i.e. Verification Timeout elapsed)
ERROR, –– Error during Verification Timeout
NO_VERIFICATION, –– No Verification defined for this enditem
ABORTED, –– Verification is aborted due to new issue of same
–– command or stop of remote TES
UNDEFINED); –– The verifcation status is not defined
–– (sending aborted due to error,
–– no command sent yet etc)
type NODE_NAME = PATHNAME (EGSE_NODE);
type PICTURE_ID = INTEGER;
type PICTURE_NAME = PATHNAME (WDU_GROUND_SYNOPTIC_DISPLAY);

Space Infrastructure
type PRIORITY = (LOW, HIGH);
type TIME_BASE = (GUARANTEED_LOCAL_TIME, LOCAL_TIME, SMT);
type UCL_ITEM_NAME = PATHNAME (UCL_AUTOMATED_PROCEDURE,
UCL_USER_LIBRARY);
type UCL_RETURN = INTEGER;
type UCL_STATUS_TEXT = STRING(120);
type UCL_STATUS_CODES = ARRAY (1..100) OF UCL_STATUS_TEXT;
type USER_MESSAGE_NAME = PATHNAME (EGSE_USER_MESSAGE);
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
344 von/of: 662
type CONDITION =
(EQUAL, NOT_EQUAL, LESS, GREATER, LESS_EQUAL, GREATER_EQUAL, IN_RANGE);
type DISCRETE_CONDITION = CONDITION (EQUAL .. NOT_EQUAL);
type CONDITION_TYPE =
(INTEGER_TYPE, REAL_TYPE, STATECODE_TYPE, BYTE_STREAM_TYPE);
type CONDITION_VAL = record
case COND_TYPE : CONDITION_TYPE
when INTEGER_TYPE : INTEGER_VALUE : INTEGER;
when REAL_TYPE : REAL_VALUE : REAL;
when STATECODE_TYPE : STATECODE_VALUE : STATECODE;
when BYTE_STREAM_TYPE : BYTE_STREAM_VALUE : VALUE_STRING;
end case;
end record;
type FLOAT_MONITOR_ITEM_NAME =
PATHNAME (EGSE_FLOAT_MEASUREMENT,
EGSE_FLOAT_SW_VARIABLE,
EGSE_FLOAT_DERIVED_VALUE);
type ON_OFF = (ON, OFF);
type ACTION_KIND = (PROCESSING, LIMIT, START_AP);
type ACTION_DESCRIPTION = record
case KIND : ACTION_KIND
when PROCESSING :
PROCESS_ITEM : ACQUISITION_COLLECTION;
when LIMIT :
LIMIT_ITEM : MONITOR_COLLECTION;
LIMIT_SET : LIMIT_SET_NUMBER;
when START_AP :
AP : AP_NAME;
end case;
end record;
type CONDITION_STATE = (IS_TRUE, IS_FALSE, IS_UNKNOWN);
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– CONSTANTS
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
constant NULL: CHARACTER := CHARACTER (0);

Space Infrastructure
constant NULL_APPLICATION_NAME : APPLICATION_NAME := ””;
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
constant DEFAULT_ARCH_FILE_OPEN_PERIOD: DURATION := 1800.0 [s];
constant DEFAULT_ISSUE_TIMEOUT: DURATION := 0.5 [s];
constant DEFAULT_LIMIT_SET: LIMIT_SET_NUMBER := 0;
constant DEFAULT_MESSAGE: USER_MESSAGE := ””;
constant ALL_CONDITIONS : INTEGER := 0;
constant OK: UCL_RETURN := 1;
constant AP_IS_EXECUTING: UCL_RETURN := 2;
constant INVALID_PARAMETER: UCL_RETURN := 3;
constant DISC_FULL: UCL_RETURN := 4;
constant INVALID_AP_ID: UCL_RETURN := 5;
constant INVALID_AT_TIME: UCL_RETURN := 6;
constant INVALID_CYCLE: UCL_RETURN := 7;
constant INVALID_EXC_COUNT: UCL_RETURN := 8;
constant INVALID_ITEM_NAME: UCL_RETURN := 9;
constant INVALID_LIMIT: UCL_RETURN := 10;
constant INVALID_LIMIT_SET: UCL_RETURN := 11;
constant INVALID_APPLICATION_ID: UCL_RETURN := 12;
constant INVALID_NODE_NAME: UCL_RETURN := 13;
constant INVALID_OFFSET: UCL_RETURN := 14;
constant INVALID_PICTURE_ID: UCL_RETURN := 15;
constant INVALID_PICTURE_NAME: UCL_RETURN := 16;
constant INVALID_SIZE: UCL_RETURN := 17;
constant ITEM_IS_DISABLED: UCL_RETURN := 18;
constant ITEMS_NOT_ACQUIRED: UCL_RETURN := 19;
constant MESSAGE_TOO_BIG: UCL_RETURN := 20;
constant NO_ADU_SERVICE: UCL_RETURN := 21;
constant NO_DELTA_LIMIT: UCL_RETURN := 22;
constant APPLICATION_NACK: UCL_RETURN := 23;
constant INVALID_APPLICATION_NAME: UCL_RETURN := 24;
constant APPLICATION_NOT_READY: UCL_RETURN := 25;
constant TIMEOUT: UCL_RETURN := 26;
constant TOO_MANY_SYNOPTICS: UCL_RETURN := 27;
constant TOO_MANY_APS: UCL_RETURN := 28;
constant URT_UNKNOWN: UCL_RETURN := 29;
constant INVALID_ADU_TYPE: UCL_RETURN := 30;
constant INVALID_TESTNODE_MODE: UCL_RETURN := 31;
constant ITEM_NOT_SAS_COMPATIBLE: UCL_RETURN := 32;
constant ITEM_NOT_FEE_COMPATIBLE: UCL_RETURN := 33;
constant ITEM_NOT_UUT_COMPATIBLE: UCL_RETURN := 34;
constant NO_GDU_SERVICE: UCL_RETURN := 35;
constant ITEM_IS_ENABLED: UCL_RETURN := 36;
constant INVALID_TIME: UCL_RETURN := 37;
constant TIME_SERVICE_FAILED: UCL_RETURN := 38;
constant OPERATION_ABORTED: UCL_RETURN := 39;
constant NOT_MTP: UCL_RETURN := 40;
constant ARCHIVE_FILE_ERROR: UCL_RETURN := 41;
constant AP_NOT_COMPILED: UCL_RETURN := 42;
constant AP_IS_SUSPENDED: UCL_RETURN := 43;
constant ARCHIVING_IS_DISABLED: UCL_RETURN := 44;
constant WORKSTATION_NOT_CONNECTED: UCL_RETURN := 45;
constant WORKSTATION_NOT_READY: UCL_RETURN := 46;
constant INPUT_CANCELLED: UCL_RETURN := 47;
constant PROTOCOL_ERROR: UCL_RETURN := 48;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
345 von/of: 662

Space Infrastructure
constant SYNOPTIC_RESOURCES_EXCEEDED: UCL_RETURN := 49;
constant CONNECTION_TIMEOUT: UCL_RETURN := 50;
constant CONNECTION_ABORTED: UCL_RETURN := 51;
constant APPLICATION_LOAD_FAILED: UCL_RETURN := 52;
constant APPLICATION_IS_CONNECTED: UCL_RETURN := 53;
constant COMMUNICATION_ERROR: UCL_RETURN := 54;
constant INVALID_FILE_TYPE: UCL_RETURN := 55;
constant INVALID_NODE_TYPE: UCL_RETURN := 56;
constant NOT_OK: UCL_RETURN := 57;
constant RUNTIME_ERROR: UCL_RETURN := 100;
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–– Constants to allow for easy conversion of UCL Status code to readable text
constant UCL_DEFAULT_TEXT: UCL_STATUS_TEXT := ”Undefined UCL Status Code”;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
346 von/of: 662
constant STATUS_STRING: UCL_STATUS_CODES := (
”OK”, –– 1)
”AP_IS_EXECUTING: Function could not be executed: AP is currently/already executing”, –– 2)
”INVALID_PARAMETER: A parameter is invalid or in conflict with another parameter”, –– 3)
”DISC_FULL: The disc of the test node or the DB Server is full”, –– 4)
”INVALID_AP_ID: The ID for the Automated Procedure is invalid / The addressed AP is not running (anymore)”, –– 5)
”INVALID_AT_TIME: The value given for the AT_TIME parameter is invalid”, –– 6)
”INVALID_CYCLE: The value given for the CYCLE parameter is invalid, range is 1 minute to 23 hours 59 minutes”, –– 7)
”INVALID_EXC_COUNT:The value given for the Exception Count parameter is invalid”, –– 8)
”INVALID_ITEM_NAME: The name for the item is invalid/not existing/of wrong type”, –– 9)
”INVALID_LIMIT: The value for the limit is invalid”, –– 10)
”INVALID_LIMIT_SET: The limit set number must be in range 0..5”, –– 11)
”INVALID_APPLICATION_ID: The application id is not known”, –– 12)
”INVALID_NODE_NAME: The name for the node is invalid”, –– 13)
”INVALID_OFFSET: Offset is not in valid range”, –– 14)
”INVALID_PICTURE_ID”, –– 15)
”INVALID_PICTURE_NAME”, –– 16)
”INVALID_SIZE”, –– 17)
”ITEM_IS_DISABLED: Function could not be executed, because item is disabled”, –– 18)
”ITEMS_NOT_ACQUIRED: Function could not be executed, because item is not acquired”, –– 19)
”MESSAGE_TOO_BIG: (e.g.: Parameter List for SWOPs do not fit into CCSDS packet)”, –– 20)
”NO_ADU_SERVICE: The addressed SAS has not announced its ADU service yet”, –– 21)
”NO_DELTA_LIMIT”, –– 22)
”APPLICATION_NACK: The SAS has given a negative acknowledge”, –– 23)
”INVALID_APPLICATION_NAME: SAS name not known / not related / not connected ”, –– 24)
”APPLICATION_NOT_READY: Something went wrong when preparing/sending a cmd/request to SAS or when receiving the
acknowlege”,–– 25)
”TIMEOUT: The acknowlegement of the SAS was not received in time”, –– 26)
”TOO_MANY_SYNOPTICS: The number of synoptics already loaded exceeds the allowable limit”, –– 27)
”TOO_MANY_APS: The number of APs already loaded exceeds the allowable limit”, –– 28)
”URT_UNKNOWN”, –– 29)
”INVALID_ADU_TYPE: The type of the ADU is not compatible with the called function or the ADU is not simulated/acquired”,––
30)
”INVALID_TESTNODE_MODE: The mode of the testnode (TES) does not allow for this function”, –– 31)
”ITEM_NOT_SAS_COMPATIBLE: Error when downloading file to SAS”, –– 32)
”ITEM_NOT_FEE_COMPATIBLE”, –– 33)
”ITEM_NOT_UUT_COMPATIBLE”, –– 34)
”NO_GDU_SERVICE:The addressed SAS has not announced its GDU service yet”, –– 35)
”ITEM_IS_ENABLED: Function could not be executed, because item isenabled”, –– 36)
”INVALID_TIME: Time parameter or time in CCSDS Header invalid”, –– 37)
”TIME_SERVICE_FAILED: The access to the time service failed”, –– 38)
”OPERATION_ABORTED: Operation was aborted (e.g. by forced_stop of test node or by abort_ap)”, –– 39)
”NOT_MTP: The addressed test node requires to be the MTP”, –– 40)
”ARCHIVE_FILE_ERROR: The access to an archive file failed”, –– 41)
”AP_NOT_COMPILED: The addressed AP needs to be compiled in the MDB”, –– 42)
”AP_IS_SUSPENDED: Function could not be executed, because AP is suspended”, –– 43)

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
347 von/of: 662
”ARCHIVING_IS_DISABLED: Function could not be executed, because archiving is (already) disabled”, –– 44)
”WORKSTATION_NOT_CONNECTED: Addressed workstation (HCI) is not connected to the test node”, –– 45)
”WORKSTATION_NOT_READY:Addressed workstation (HCI) is not ready”, –– 46)
”INPUT_CANCELLED”, –– 47)
”PROTOCOL_ERROR: Something went wrong when communicating with other software parts / Invalid Response Packet for
SWOP”, –– 48)
”SYNOPTIC_RESOURCES_EXCEEDED or PARAMETER_ERROR: Parameter List of SWOP has wrong data / wrong types”,
–– 49)
”CONNECTION_TIMEOUT”, –– 50)
”CONNECTION_ABORTED”, –– 51)
”APPLICATION_LOAD_FAILED: The loading of the SAS executable failed”, –– 52)
”APPLICATION_IS_CONNECTED: The SAS is already connected”, –– 53)
”COMMUNICATION_ERROR: Error on the communication channel”, –– 54)
”INVALID_FILE_TYPE”, –– 55)
”INVALID_NODE_TYPE”, –– 56)
”NOT_OK: For Operations on Lists: Some of the items could not be processed / executed”, –– 57)
”SW_COMMAND_NOT_FOUND: The addressed Software Command was not found”, –– 58)
UCL_Default_Text,–– 59)
UCL_Default_Text,UCL_Default_Text,UCL_Default_Text,UCL_Default_Text,UCL_Default_Text, –– 60..64
UCL_Default_Text,UCL_Default_Text,UCL_Default_Text,UCL_Default_Text,UCL_Default_Text,–– 65..99
UCL_Default_Text,UCL_Default_Text,UCL_Default_Text,UCL_Default_Text,UCL_Default_Text,–– 70..74
UCL_Default_Text,UCL_Default_Text,UCL_Default_Text,UCL_Default_Text,UCL_Default_Text,–– 75..79
UCL_Default_Text,UCL_Default_Text,UCL_Default_Text,UCL_Default_Text,UCL_Default_Text,–– 80..84
UCL_Default_Text,UCL_Default_Text,UCL_Default_Text,UCL_Default_Text,UCL_Default_Text,–– 85..89
UCL_Default_Text,UCL_Default_Text,UCL_Default_Text,UCL_Default_Text,UCL_Default_Text,–– 90..94
UCL_Default_Text,UCL_Default_Text,UCL_Default_Text,UCL_Default_Text,UCL_Default_Text,–– 95..99
”RUNTIME_ERROR: Something went wrong in the software”); –– 100);
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– PROCEDURES & FUNCTIONS
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Monitoring
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
procedure ENABLE_MONITORING
(in ITEM: MONITOR_COLLECTION;
in LIMIT_SET: LIMIT_SET_NUMBER := DEFAULT_LIMIT_SET;
in ADU: ADU_NAME := \\;
out STATUS: UCL_RETURN); –– #1
procedure DISABLE_MONITORING
(in ITEM: MONITOR_COLLECTION;
out STATUS: UCL_RETURN); –– #2
procedure SET_HIGH_LIMIT
(in ITEM: ANALOG_MONITOR_ITEM_NAME;
in LIMIT: REAL;
out STATUS: UCL_RETURN); –– #3
procedure SET_INTEGER_HIGH_LIMIT
(in ITEM: INTEGER_MONITOR_ITEM_NAME;
in LIMIT: INTEGER;
out STATUS: UCL_RETURN); –– #4
procedure SET_LOW_LIMIT
(in ITEM: ANALOG_MONITOR_ITEM_NAME;
in LIMIT: REAL;

Space Infrastructure
out STATUS: UCL_RETURN); –– #5
procedure SET_INTEGER_LOW_LIMIT
(in ITEM: INTEGER_MONITOR_ITEM_NAME;
in LIMIT: INTEGER;
out STATUS: UCL_RETURN); –– #6
procedure SET_DELTA_LIMIT
(in ITEM: ANALOG_MONITOR_ITEM_NAME;
in LIMIT: REAL;
out STATUS: UCL_RETURN); –– #7
procedure SET_INTEGER_DELTA_LIMIT
(in ITEM: INTEGER_MONITOR_ITEM_NAME;
in LIMIT: INTEGER;
out STATUS: UCL_RETURN); –– #8
procedure SET_EXCEPTION_COUNT
(in ITEM: MONITOR_ITEM_NAME;
in N_COUNT: INTEGER;
out STATUS: UCL_RETURN); –– #9
procedure SET_EXPECTED_STATE
(in ITEM: DISCRETE_MONITOR_ITEM_NAME;
in STATE: STATECODE;
out STATUS: UCL_RETURN); –– #10
procedure SET_EXPECTED_VALUE
(in ITEM: BYTE_STREAM_MONITOR_ITEM_NAME;
in VALUE: STRING;
out STATUS: UCL_RETURN); –– #11
procedure SET_LIMIT_SET
(in ITEM: MONITOR_COLLECTION;
in LIMIT_SET: LIMIT_SET_NUMBER;
out STATUS: UCL_RETURN); –– #12
procedure GET_ENDITEM_MONITOR_STATUS
(in ITEM: MONITOR_ITEM_NAME;
out MONITORING_STATUS: MONITOR_STATUS;
out STATUS: UCL_RETURN); –– #13
procedure GET_FULL_ENDITEM_MONITOR_STATUS
(in ITEM: MONITOR_ITEM_NAME;
out MONITORING_STATUS: FULL_MONITOR_STATUS;
out STATUS: UCL_RETURN); –– #14
procedure GET_ACQUISITION_STATUS
(in ITEM: MONITOR_ITEM_NAME;
out ENDITEM_ACQ_STATUS: ACQUISITION_STATUS;
out STATUS: UCL_RETURN); –– #15
procedure GET_INTEGER
(in ITEM: INTEGER_MONITOR_ITEM_NAME;
out VALUE: INTEGER;
out TIME_TAG: TIME;
out ENDITEM_ACQ_STATUS: ACQUISITION_STATUS;
out STATUS: UCL_RETURN); –– #16
procedure GET_FLOAT
(in ITEM: FLOAT_MONITOR_ITEM_NAME;
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
348 von/of: 662

Space Infrastructure
out VALUE: REAL;
out TIME_TAG: TIME;
out ENDITEM_ACQ_STATUS: ACQUISITION_STATUS;
out STATUS: UCL_RETURN); –– #17
procedure GET_STATECODE
(in ITEM: DISCRETE_MONITOR_ITEM_NAME;
out VALUE: STATECODE;
out TIME_TAG: TIME;
out ENDITEM_ACQ_STATUS: ACQUISITION_STATUS;
out STATUS: UCL_RETURN); –– #18
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
procedure GET_BYTE_STREAM
(in ITEM: BYTE_STREAM_MONITOR_ITEM_NAME;
out VALUE: STRING;
out TIME_TAG: TIME;
out ENDITEM_ACQ_STATUS: ACQUISITION_STATUS;
out STATUS: UCL_RETURN); –– #19
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Time Management
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
function CLOCK (in BASE: TIME_BASE := LOCAL_TIME) : TIME; –– #20
procedure DELAY
(in DELAY: DURATION;
in BASE: TIME_BASE := LOCAL_TIME); –– #21
procedure WAIT_UNTIL
(in DUE_TIME: TIME;
in BASE: TIME_BASE := LOCAL_TIME;
out STATUS: UCL_RETURN); –– #22
procedure START_SMT
(in VALUE: TIME := ~:~ ;
out STATUS: UCL_RETURN); –– #23
procedure STOP_SMT (out STATUS: UCL_RETURN); –– #24
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– AP Handling
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
procedure EXECUTE_AP
(in AP: AP_NAME ();
in PRIO: PRIORITY := LOW;
in NODE: NODE_NAME := \\;
out ID: AP_ID;
out STATUS: UCL_RETURN); –– #25
procedure SYNCHRONISE_WITH_AP
(in AP: AP_ID;
in NODE: NODE_NAME := \\;
out COMPLETION: AP_COMPLETION_STATE;
out STATUS: UCL_RETURN); –– #26
procedure SUSPEND_AP
(in AP: AP_ID;
in NODE: NODE_NAME := \\;
out STATUS: UCL_RETURN); –– #27
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
349 von/of: 662

Space Infrastructure
procedure RESUME_AP
(in AP: AP_ID;
in NODE: NODE_NAME := \\;
out STATUS: UCL_RETURN); –– #28
function OWN_AP_ID : AP_ID; –– #29
procedure GET_AP_ID
(in AP: AP_NAME;
in NODE: NODE_NAME := \\;
out NUMBER: INTEGER;
out ID_LIST: AP_ID_LIST;
out STATUS: UCL_RETURN); –– #30
procedure GET_AP_STATUS
(in AP: AP_ID;
in NODE: NODE_NAME := \\;
out EXEC_STATE: AP_EXECUTION_STATE;
out STATUS: UCL_RETURN); –– #31
procedure READ_MESSAGE_FROM_AP
(in BLOCK: BOOLEAN := TRUE;
out AP: AP_ID;
out NODE_NAME: USER_MESSAGE;
out MESSAGE : USER_MESSAGE;
out STATUS: UCL_RETURN); –– #32
procedure WRITE_MESSAGE_TO_AP
(in AP: AP_ID;
in NODE: NODE_NAME := \\;
in MESSAGE: USER_MESSAGE := DEFAULT_MESSAGE;
out STATUS: UCL_RETURN); –– #33
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Application Handling
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
procedure LOAD_APPLICATION
(in NAME: APPLICATION_NAME;
in NODE: NODE_NAME := \\;
in PARAMS: USER_MESSAGE := DEFAULT_MESSAGE;
out APPL: APPLICATION_ID;
out STATUS: UCL_RETURN); –– #34
procedure UNLOAD_APPLICATION
(in APPL: APPLICATION_ID;
out STATUS: UCL_RETURN); –– #35
procedure INIT_APPLICATION
(in APPL: APPLICATION_ID;
in MESSAGE: USER_MESSAGE := DEFAULT_MESSAGE;
out STATUS: UCL_RETURN); –– #36
procedure START_APPLICATION
(in APPL: APPLICATION_ID;
out STATUS: UCL_RETURN); –– #37
procedure RESET_APPLICATION
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
350 von/of: 662

Space Infrastructure
(in APPL: APPLICATION_ID;
out STATUS: UCL_RETURN); –– #38
procedure GET_APPLICATION_STATUS
(in APPL: APPLICATION_ID;
out STATE: APPLICATION_STATE;
out ERROR_COUNT: INTEGER;
out ERROR_MESSAGE: APPLICATION_ERROR_MESSAGE;
out STATUS: UCL_RETURN); –– #39
procedure READ_MESSAGE_FROM_APPLICATION
(in BLOCK: BOOLEAN := TRUE;
out APPL: APPLICATION_ID;
out MESSAGE: USER_MESSAGE;
out STATUS: UCL_RETURN); –– #40
procedure WRITE_MESSAGE_TO_APPLICATION
(in APPL: APPLICATION_ID;
in MESSAGE: USER_MESSAGE;
out STATUS: UCL_RETURN); –– #41
procedure GET_APPLICATION_NAME
(in APPL: APPLICATION_ID;
out NAME: APPLICATION_NAME;
out STATUS: UCL_RETURN); –– #42
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
procedure GET_APPLICATION_ID
(in NAME: APPLICATION_NAME;
out APPL: APPLICATION_ID;
out STATUS: UCL_RETURN); –– #43
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Issue of HW Stimuli & Downloading
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
procedure ISSUE
(in ITEM: ISSUE_ITEM_NAME();
in PRIO: PRIORITY := LOW;
in AT_TIME: TIME := ~:~;
in BASE: TIME_BASE := LOCAL_TIME;
in ONBOARD_EXECUTION_TIME: TIME := ~:~;
in TIMEOUT: DURATION := default_issue_timeout;
out STATUS: UCL_RETURN); –– #44
procedure ISSUE_AND_VERIFY
(in ITEM: SINGLE_GDU_NAME();
in PRIO: PRIORITY := LOW;
in AT_TIME: TIME := ~:~;
in BASE: TIME_BASE := LOCAL_TIME;
in ONBOARD_EXECUTION_TIME: TIME := ~:~;
in TIMEOUT: DURATION := default_issue_timeout;
in ACTIVATION_DELAY: DURATION := –1.0 [s];
in VERIFICATION_TIMEOUT : DURATION := –1.0 [s];
in WAIT_TIL_END: BOOLEAN := FALSE;
out VERIFICATION_STATUS: CMD_VERIFICATION_STATUS;
out STATUS: UCL_RETURN); –– #45
procedure GET_VERIFICATION_STATUS
(in ITEM: SINGLE_GDU_NAME;
out VERIFICATION_STATUS: CMD_VERIFICATION_STATUS;
out STATUS: UCL_RETURN); –– #46
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
351 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
procedure ENABLE_ENDITEM
(in ENDITEM: ISSUE_ITEM_NAME;
out STATUS: UCL_RETURN); –– #47
procedure DISABLE_ENDITEM
(in ENDITEM: ISSUE_ITEM_NAME;
out STATUS: UCL_RETURN); –– #48
procedure DOWNLOAD
(in APPL: APPLICATION_ID;
in ITEM: DOWNLOAD_ITEM_NAME;
in NODE: NODE_NAME := \\;
out STATUS: UCL_RETURN); –– #49
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Raw Data Handling
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
procedure START_ACQUISITION
(in ITEM: ACQUISITION_COLLECTION;
in ADU: ADU_NAME := \\;
out STATUS: UCL_RETURN); –– #50
procedure STOP_ACQUISITION
(in ITEM: ACQUISITION_COLLECTION;
in ADU: ADU_NAME := \\;
out STATUS: UCL_RETURN); –– #51
procedure SEND_SIMULATED_ADU
(in ADU: ADU_NAME;
out STATUS: UCL_RETURN); –– #52
procedure WAIT_FOR_ADU
(in ADU: ADU_NAME;
out TIME_TAG: TIME;
out SEQUENCE_NUMBER: INTEGER;
out STATUS: UCL_RETURN); –– #53
procedure SET_BITS_IN_SIMULATED_ADU
(in ADU: ADU_NAME;
in OFFSET: INTEGER;
in SIZE: BIT_COUNT;
in VALUE: BITSET;
out STATUS: UCL_RETURN); –– #54
procedure SET_SIMULATED_ENDITEM_VALUE
(in ITEM: MONITOR_ITEM_NAME;
in BOOL_VALUE: BOOLEAN := FALSE;
in INT_VALUE: INTEGER := 0;
in BITSET_VALUE: BITSET := {};
in REAL_VALUE: REAL := 0.0;
in STR_VALUE: USER_MESSAGE := ””;
out STATUS: UCL_RETURN); –– #55
procedure ROUTE_TO_SAS
(in ITEM: ROUTE_SAS_ITEM_NAME ;
in SAS_NAME: APPLICATION_NAME;
in OLD_SAS_NAME: APPLICATION_NAME := NULL_APPLICATION_NAME;
out STATUS: UCL_RETURN); –– #56
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
352 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Event Handling
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
procedure LOG (in MESSAGE: USER_MESSAGE;
out STATUS: UCL_RETURN); –– #57
procedure USER_EVENT
(in MESSAGE: USER_MESSAGE;
out STATUS: UCL_RETURN); –– #58
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Engineering Value Logging
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
procedure ENABLE_EVL
(in ITEM: MONITOR_COLLECTION;
out STATUS: UCL_RETURN); –– #59
procedure DISABLE_EVL
(in ITEM: MONITOR_COLLECTION;
out STATUS: UCL_RETURN); –– #60
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Archiving
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
procedure ENABLE_ARCHIVING
(in CYCLE: DURATION := DEFAULT_ARCH_FILE_OPEN_PERIOD;
out STATUS: UCL_RETURN); –– #61
procedure DISABLE_ARCHIVING; –– #62
procedure CLOSE_ARCHIVE
(out CLOSE_TIME : TIME;
out STATUS: UCL_RETURN); –– #63
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– User Input & Output
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
procedure READ_MESSAGE_FROM_USER
(in PROMPT: USER_MESSAGE;
in WORKSTATION: NODE_NAME := \\;
out USER_ENTRY: USER_MESSAGE;
out STATUS: UCL_RETURN); –– #64
procedure WRITE_MESSAGE_TO_USER
(in MESSAGE: USER_MESSAGE;
in WORKSTATION: NODE_NAME :=\\;
out STATUS: UCL_RETURN); –– #65
procedure READ_NUMBER_FROM_USER
(in PROMPT_MESSAGE: USER_MESSAGE;
in WORKSTATION: NODE_NAME := \\;
out USER_ENTRY: REAL;
out STATUS: UCL_RETURN); –– #66
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
353 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Synoptic Display Control
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
procedure DISPLAY_PICTURE
(in PICTURE: PICTURE_NAME;
in WORKSTATION: NODE_NAME := \\;
out ID: PICTURE_ID;
out STATUS: UCL_RETURN); –– #67
procedure REMOVE_PICTURE
(in ID: PICTURE_ID;
in WORKSTATION: NODE_NAME := \\;
out STATUS: UCL_RETURN); –– #68
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– UCL Code Reloading from MDB
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
procedure LOAD_UCL
(in ITEM: UCL_ITEM_NAME;
out STATUS: UCL_RETURN); –– #69
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Test Node management
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
function IS_LOCAL_NODE (in NODE : NODE_NAME) : BOOLEAN; –– #70
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Conditions
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
354 von/of: 662
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Concept :
–– –––––––––
––
–– The conditional monitoring will be defined by linking 1 measurement or
–– software variable to one or more end items.
––
–– Every link can be described by
––
–– ”when value of CONDITION_ITEM a CONDITION_VALUE”
–– ”then on an ITEM”
––
–– where can be
–– EQUAL, NOT_EQUAL, LESS, GREATER, LESS OR EQUAL, GREATER OR EQUAL
––
–– (Note: the IN_RANGE alternative is currently not supported. It is included
–– in the definition of the CONDITION type only for MDB compatibility reasons )
––
–– where can be
––
–– ”enable the processing of a measurement / a sw_variable / the
–– measurements and sw variables of a
–– monitoring list / the measurements of an
–– ADU / the measurements and sw variables

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
355 von/of: 662
–– of a subtree”
–– ”set a new limit set for a measurement / a sw_variable”
–– ”start an AP”
––
–– When processing CONDITION_ITEM, all conditions linked to that item will
–– be analysed and for those that are true, the defined action will be
–– performed.
–– It is necessary to start the acquisition of CONDITION_ITEM to allow the
–– condition to be analysed.
––
–– For performance reasons, the conditions will only be analysed when the
–– value of the CONDITION_ITEM is modified, and not everytime the
–– CONDITION_ITEM is processed.
–– However, the when defining a condition, it will be checked immediately
–– if the CONDITION_ITEM has a valid value.
––
–– Note that the order of processing of the data from one ADU is the order of
–– the definition of the items in the ADU.
–– So if an adu contains an ITEM and its CONDITION_ITEM, to ensure that the
–– CONDITION_ITEM is processed before the ITEM, it must be defined in the
–– list of items of the ADU description before the ITEM.
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– ENABLE/DISABLE CONDITION
––
–– ––––––––––––––––––––––––
–– Will enable/disable a condition or all conditions of
–– measurement(s), sw variable(s) and derived value(s).
–– PARAMETER DESCRIPTION :
–– inputs
–– ––––––
–– ITEM : measurement(s), derived values(s) or software variable(s) carrying the
–– condition.
––
–– outputs
–– –––––––
–– STATUS : the return status of the operation
–– OK : operation successfull
–– INVALID_TESTNODE_MODE : the test node is not in executing mode
–– INVALID_ITEM_NAME : ITEM is not managed locally
–– RUNTIME_ERROR : an unexpected error occurred
procedure ENABLE_CONDITIONS
(in ITEM: ACQUISITION_COLLECTION;
out STATUS: UCL_RETURN); –– #71
procedure DISABLE_CONDITIONS
(in ITEM: ACQUISITION_COLLECTION;
out STATUS: UCL_RETURN); –– #72
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– ENABLE PROCESSING OF ENDITEMS
––
–– ––––––––––––––––––––––––

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
356 von/of: 662
–– Will enable the processing of ITEM (measurement, software variable,
–– monitoring list or measurements of a subtree) when the CONDITION_CHECK
–– of the value of CONDITION_ITEM with CONDITION_VALUE is true (the
–– condition is true).
––
–– If the condition is false, this will disable the processing of ITEM.
––
–– By default, all enditems are enabled for processing. Conditions can be
–– defined to disable and re–enable the processing of given end–items.
––
–– When the processing is enabled, ITEM will be authorised for calibration
–– and monitoring. After ITEM has been enabled, it will be calibrated (if
–– its acquisition has been started) and monitored (if its monitoring has
–– been enabled) on reception of new values.
––
–– Enabling the processing of ITEM does not perform an ”initial”
–– calibration / monitoring of ITEM in the case where it has already a value.
––
–– When the processing is disabled, ITEM will not be calibrated and not be
–– monitored, even if its acquisition has been requested and if its
–– monitoring is enabled.
––
–– CONDITION_ITEM must be maintained locally otherwise an error is generated.
–– When the condition is triggered, only those measurements and SW variables
–– identified by ITEM that are maintained locally will be processed.
––
–– It is not possible to set a condition where the ITEM to enable or disable
–– is the CONDITION_ITEM.
–– If ITEM is a group of enditems (i.e. monitoring list, ADU or incomplete
–– pathname) containing CONDITION_ITEM, the condition will not apply for
–– CONDITION_ITEM.
––
–– It is not possible to enable or disable the processing of a SW variable
–– that is linked to an HK data.
––
–– PARAMETER DESCRIPTION :
–– inputs
–– ––––––
–– ITEM : item(s) to enable. It can be a measurement or software
–– variable or all measurements / sw variables contained in a
–– monitoring list or all measurements contained in an ADU or
–– all measurements / sw variables contained in a subtree.
––
–– CONDITION_ITEM : the measurement or software variable carrying the
–– condition.
––
–– CONDITION_CHECK : the check to apply on CONDITION_ITEM.
––
–– CONDITION_VALUE : the value to use in the check with CONDITION_ITEM.
––
–– SINGLE_SHOT : if true, the condition will be withdrawn after having
–– being true.
––
–– outputs
–– –––––––
–– CONDITION_REF : a unique identifier for the condition
––
–– STATUS : the return status of the operation
–– OK : operation successfull
–– INVALID_TESTNODE_MODE : the test node is not in executing mode

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
357 von/of: 662
–– INVALID_ITEM_NAME : CONDITION_ITEM is not managed locally
–– INVALID_PARAMETER : ITEM and CONDITION_ITEM are identical
–– or ITEM is a SW variable linked to an HK data.
–– or CONDITION_CHECK is IN_RANGE (not supported: see above)
–– RUNTIME_ERROR : an unexpected error occurred
procedure ENABLE_ON_INTEGER
(in ITEM : ACQUISITION_COLLECTION;
in CONDITION_ITEM : INTEGER_MONITOR_ITEM_NAME;
in CONDITION_CHECK : CONDITION;
in CONDITION_VALUE : INTEGER;
in SINGLE_SHOT : BOOLEAN;
out CONDITION_REF : INTEGER;
out STATUS : UCL_RETURN); –– #73
procedure ENABLE_ON_FLOAT
(in ITEM : ACQUISITION_COLLECTION;
in CONDITION_ITEM : FLOAT_MONITOR_ITEM_NAME;
in CONDITION_CHECK : CONDITION;
in CONDITION_VALUE : REAL;
in SINGLE_SHOT : BOOLEAN;
out CONDITION_REF : INTEGER;
out STATUS : UCL_RETURN); –– #74
procedure ENABLE_ON_STATECODE
(in ITEM : ACQUISITION_COLLECTION;
in CONDITION_ITEM : DISCRETE_MONITOR_ITEM_NAME;
in CONDITION_CHECK : DISCRETE_CONDITION;
in CONDITION_VALUE : STATECODE;
in SINGLE_SHOT : BOOLEAN;
out CONDITION_REF : INTEGER;
out STATUS : UCL_RETURN); –– #75
procedure ENABLE_ON_BYTE_STREAM
(in ITEM : ACQUISITION_COLLECTION;
in CONDITION_ITEM : BYTE_STREAM_MONITOR_ITEM_NAME;
in CONDITION_CHECK : DISCRETE_CONDITION;
in CONDITION_VALUE : STRING;
in SINGLE_SHOT : BOOLEAN;
out CONDITION_REF : INTEGER;
out STATUS : UCL_RETURN); –– #76
–– ––––––––––––––––––––––––
–– Will enable or disable the processing of ITEM. This is overwriting
–– an eventual action from a condition.
––
–– PARAMETER DESCRIPTION :
–– inputs
–– ––––––
–– ITEM : item(s) to enable or disable. It can be a measurement or
–– software variable or all measurements / sw variables contained
–– in a monitoring list or all measurements contained in an ADU or
–– all measurements / sw variables contained in a subtree.
––
–– SWITCH : ON to enable the processing and OFF to disable the processing.
––
–– outputs
–– –––––––

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
358 von/of: 662
–– STATUS : the return status of the operation
–– OK : operation successfull
–– INVALID_TESTNODE_MODE : the test node is not in executing mode
–– INVALID_ITEM_NAME : ITEM is not managed locally
–– INVALID_PARAMETER : ITEM is a SW variable linked to an HK data.
–– or CONDITION_CHECK is IN_RANGE (not supported: see above)
–– RUNTIME_ERROR : an unexpected error occurred
procedure SET_PROCESSING
(in ITEM : ACQUISITION_COLLECTION;
in SWITCH : ON_OFF;
out STATUS : UCL_RETURN); –– #77
–– ––––––––––––––––––––––––
–– Indicates if a measurement or software variabled is enabled or disabled
–– for processing (as a result of a condition or of a call to SET_PROCESSING)
––
–– PARAMETER DESCRIPTION :
–– inputs
–– ––––––
–– ITEM : item to check. It can be a single measurement or software
–– variable.
––
–– outputs
–– –––––––
–– STATE : ON if the processing is enabled and OFF if the processing is
–– disabled.
––
–– STATUS : the return status of the operation
–– OK : operation successfull
–– INVALID_TESTNODE_MODE : the test node is not in executing mode
–– INVALID_ITEM_NAME : ITEM is not managed locally
–– RUNTIME_ERROR : an unexpected error occurred
procedure GET_PROCESSING_STATE
(in ITEM : MONITOR_ITEM_NAME;
out STATE : ON_OFF;
out STATUS : UCL_RETURN); –– #78
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– SWITCH LIMIT SET
––
–– ––––––––––––––––––––––––
–– Will set the LIMIT_SET for ITEM (measurement or software variable) when
–– the CONDITION_CHECK of the value of CONDITION_ITEM with CONDITION_VALUE
–– is true (the condition is true).
––
–– This will not perform an ”initial” monitoring of ITEM in the case where
–– it has already a value. The monitoring will be performed on reception of
–– the next value (in case the monitoring has been enabled).
–– This can lead to a temporary ”inconsistent” output of the procedure
–– GET_FULL_ENDITEM_MONITOR_STATUS (result of the monitoring with the old
–– limit set with values of the new limit set might be inconsistent).

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
––
–– ITEM and CONDITION_ITEM must be maintained locally on the same node
–– otherwise an error is generated.
––
–– It is not possible to set a condition where the ITEM identical to the
–– CONDITION_ITEM.
––
–– The LIMIT_SET must be defined for ITEM, otherwise an error is generated
––
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
359 von/of: 662
–– PARAMETER DESCRIPTION :
–– inputs
–– ––––––
–– ITEM : item for which the limit set is to be switched. It can be a
–– measurement or software variable.
––
–– LIMIT_SET : the limit set number to select.
––
–– CONDITION_ITEM : the measurement or software variable carrying the
–– condition.
––
–– CONDITION_CHECK : the check to apply on CONDITION_ITEM.
––
–– CONDITION_VALUE : the value to use in the check with CONDITION_ITEM.
––
–– SINGLE_SHOT : if true, the condition will be withdrawn after having
–– being true.
––
–– outputs
–– –––––––
–– CONDITION_REF : a unique identifier for the condition
––
–– STATUS : the return status of the operation
–– OK : operation successfull
–– INVALID_TESTNODE_MODE : the test node is not in executing mode
–– INVALID_ITEM_NAME : ITEM or CONDITION_ITEM are not managed locally
–– INVALID_PARAMETER : ITEM and CONDITION_ITEM are identical
–– or CONDITION_CHECK is IN_RANGE (not supported: see above)
–– INVALID_LIMIT_SET : the limit set is not defined for ITEM
–– RUNTIME_ERROR : an unexpected error occurred
procedure SET_LIMIT_SET_ON_INTEGER
(in ITEM : MONITOR_COLLECTION;
in LIMIT_SET : LIMIT_SET_NUMBER;
in CONDITION_ITEM : INTEGER_MONITOR_ITEM_NAME;
in CONDITION_CHECK : CONDITION;
in CONDITION_VALUE : INTEGER;
in SINGLE_SHOT : BOOLEAN;
out CONDITION_REF : INTEGER;
out STATUS : UCL_RETURN); –– #79
procedure SET_LIMIT_SET_ON_FLOAT
(in ITEM : MONITOR_COLLECTION;
in LIMIT_SET : LIMIT_SET_NUMBER;
in CONDITION_ITEM : FLOAT_MONITOR_ITEM_NAME;
in CONDITION_CHECK : CONDITION;
in CONDITION_VALUE : REAL;
in SINGLE_SHOT : BOOLEAN;
out CONDITION_REF : INTEGER;
out STATUS : UCL_RETURN); –– #80

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
procedure SET_LIMIT_SET_ON_STATECODE
(in ITEM : MONITOR_COLLECTION;
in LIMIT_SET : LIMIT_SET_NUMBER;
in CONDITION_ITEM : DISCRETE_MONITOR_ITEM_NAME;
in CONDITION_CHECK : DISCRETE_CONDITION;
in CONDITION_VALUE : STATECODE;
in SINGLE_SHOT : BOOLEAN;
out CONDITION_REF : INTEGER;
out STATUS : UCL_RETURN); –– #81
procedure SET_LIMIT_SET_ON_BYTE_STREAM
(in ITEM : MONITOR_COLLECTION;
in LIMIT_SET : LIMIT_SET_NUMBER;
in CONDITION_ITEM : BYTE_STREAM_MONITOR_ITEM_NAME;
in CONDITION_CHECK : DISCRETE_CONDITION;
in CONDITION_VALUE : STRING;
in SINGLE_SHOT : BOOLEAN;
out CONDITION_REF : INTEGER;
out STATUS : UCL_RETURN); –– #82
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– START AUTOMATED PROCEDURE
––
–– ––––––––––––––––––––––––
–– Will start an automated procedure when the CONDITION_CHECK of the value
–– of CONDITION_ITEM with CONDITION_VALUE is true (the condition is true).
––
–– CONDITION_ITEM must be maintained locally on the node otherwise an
–– error is generated.
––
–– The AP to start must be an AP without parameters, otherwise an error
–– message is generated when the condition is triggered.
–– When the condition is triggered, if the AP is already running, it will
–– not be started and an error message will be generated.
––
––
–– PARAMETER DESCRIPTION :
–– inputs
–– ––––––
–– AP : the name of the automated procedure to start. This must be an AP
–– without parameter or where all parameters have default values.
––
–– CONDITION_ITEM : the measurement or software variable carrying the
–– condition.
––
–– CONDITION_CHECK : the check to apply on CONDITION_ITEM.
––
–– CONDITION_VALUE : the value to use in the check with CONDITION_ITEM.
––
–– SINGLE_SHOT : if true, the condition will be withdrawn after having
–– being true.
––
–– outputs
–– –––––––
–– CONDITION_REF : a unique identifier for the condition
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
360 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
361 von/of: 662
––
–– STATUS : the return status of the operation
–– OK : operation successfull
–– INVALID_TESTNODE_MODE : the test node is not in executing mode
–– INVALID_ITEM_NAME : CONDITION_ITEM is not managed locally
–– INVALID_PARAMETER : CONDITION_CHECK is IN_RANGE (not supported: see above)
–– RUNTIME_ERROR : an unexpected error occurred
procedure START_AP_ON_INTEGER
(in AP : AP_NAME;
in CONDITION_ITEM : INTEGER_MONITOR_ITEM_NAME;
in CONDITION_CHECK : CONDITION;
in CONDITION_VALUE : INTEGER;
in SINGLE_SHOT : BOOLEAN;
out CONDITION_REF : INTEGER;
out STATUS : UCL_RETURN); –– #83
procedure START_AP_ON_FLOAT
(in AP : AP_NAME;
in CONDITION_ITEM : FLOAT_MONITOR_ITEM_NAME;
in CONDITION_CHECK : CONDITION;
in CONDITION_VALUE : REAL;
in SINGLE_SHOT : BOOLEAN;
out CONDITION_REF : INTEGER;
out STATUS : UCL_RETURN); –– #84
procedure START_AP_ON_STATECODE
(in AP : AP_NAME;
in CONDITION_ITEM : DISCRETE_MONITOR_ITEM_NAME;
in CONDITION_CHECK : DISCRETE_CONDITION;
in CONDITION_VALUE : STATECODE;
in SINGLE_SHOT : BOOLEAN;
out CONDITION_REF : INTEGER;
out STATUS : UCL_RETURN); –– #85
procedure START_AP_ON_BYTE_STREAM
(in AP : AP_NAME;
in CONDITION_ITEM : BYTE_STREAM_MONITOR_ITEM_NAME;
in CONDITION_CHECK : DISCRETE_CONDITION;
in CONDITION_VALUE : STRING;
in SINGLE_SHOT : BOOLEAN;
out CONDITION_REF : INTEGER;
out STATUS : UCL_RETURN); –– #86
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– REMOVE CONDITION
––
–– ––––––––––––––––––––––––
–– Will remove a condition or all conditions of a CONDITION_ITEM.
–– PARAMETER DESCRIPTION :
–– inputs
–– ––––––
–– CONDITION_ITEM : the measurement or software variable carrying the
–– condition.
––
–– CONDITION_REF : the unique identifier of the condition to remove

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–– or the constant ALL_CONDITIONS to remove all conditions
–– of CONDITION_ITEM.
––
–– outputs
–– –––––––
–– STATUS : the return status of the operation
–– OK : operation successfull
–– INVALID_TESTNODE_MODE : the test node is not in executing mode
–– INVALID_ITEM_NAME : CONDITION_ITEM is not managed locally or
–– CONDITION_REF does not identify an existing
–– condition
–– RUNTIME_ERROR : an unexpected error occurred
procedure WITHDRAW_CONDITION
(in CONDITION_ITEM : MONITOR_ITEM_NAME;
in CONDITION_REF : INTEGER := ALL_CONDITIONS;
out STATUS : UCL_RETURN); –– #87
–– ––––––––––––––––––––––––
–– Will remove all conditions defined on the test node.
–– PARAMETER DESCRIPTION :
–– outputs
–– –––––––
–– STATUS : the return status of the operation
–– OK : operation successfull
–– INVALID_TESTNODE_MODE : the test node is not in executing mode
–– RUNTIME_ERROR : an unexpected error occurred
procedure WITHDRAW_ALL_CONDITIONS
(out STATUS : UCL_RETURN); –– #88
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– MANAGE CONDITIONS
––
–– ––––––––––––––––––––––––
–– Returns the number of items carrying conditions (CONDITION_ITEMS).
–– This number is as well maintained as Housekeeping variable (and can
–– be mapped to a software variable).
function NUMBER_OF_CONDITION_ITEMS : INTEGER; –– #89
–– ––––––––––––––––––––––––
–– Provide the name of the CONDITION_ITEM identified by an index.
–– To get all the CONDITION_ITEM’s, this procedure has to be called
–– with all numbers betwee 1 and the value of NUMBER_OF_CONDITION_ITEMS.
––
–– Note:
–– it can occur that between the time where NUMBER_OF_CONDITION_ITEMS has
–– been called and the time where GET_CONDITION_ITEM is called, the number
–– of items carrying condition is modified (if new conditions are created
–– or removed in parallel).
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
362 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–– PARAMETER DESCRIPTION :
–– inputs
–– ––––––
–– ITEM_NUMBER : index of the CONDITION_ITEM (between 1 and the value of
–– NUMBER_OF_CONDITION_ITEMS).
––
–– outputs
–– –––––––
–– CONDITION_ITEM : the measurement or software variable carrying the
–– condition.
––
–– STATUS : the return status of the operation
–– OK : operation successfull
–– INVALID_TESTNODE_MODE : the test node is not in executing mode
–– INVALID_PARAMETER : There is no (more) CONDITION_ITEM at the index
–– ITEM_NUMBER (see above note).
–– RUNTIME_ERROR : an unexpected error occurred
procedure GET_CONDITION_ITEM
(in ITEM_NUMBER : INTEGER;
out CONDITION_ITEM : MONITOR_ITEM_NAME;
out STATUS : UCL_RETURN); –– #90
–– ––––––––––––––––––––––––
–– Provide the number of conditions carried by a CONDITION_ITEM.
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
363 von/of: 662
–– PARAMETER DESCRIPTION :
–– inputs
–– ––––––
–– CONDITION_ITEM : the name of the item for which the number of conditions
–– is to be returned. It must be managed locally, otherwise
–– the value 0 is returned.
function NUMBER_CONDITIONS
(in CONDITION_ITEM : MONITOR_ITEM_NAME) :INTEGER; –– #91
–– ––––––––––––––––––––––––
–– Provide the description of a condition.
––
–– Note:
–– it can occur that between the time where GET_NUMBER_CONDITIONS has
–– been called and the time where GET_CONDITION is called, the number
–– of condition carried by CONDITION_ITEM is modified
–– (if new conditions are created or removed in parallel).
–– PARAMETER DESCRIPTION :
–– inputs
–– ––––––
–– CONDITION_ITEM : the name of the item carrying the condition.
––
–– CONDITION_NUMBER : the index of the condition (between 1 and the value
–– of GET_NUMBER_CONDITIONS).
––
–– outputs
–– –––––––
–– CONDITION_REF : the unique identifier of the condition.
––
–– CONDITION_CHECK : the check to apply on CONDITION_ITEM.

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
364 von/of: 662
––
–– CONDITION_VALUE : the value to use in the check with CONDITION_ITEM.
––
–– SINGLE_SHOT : indicates if the condition is to be removed after having
–– being true.
––
–– STATE : indicate the state of the condition. It can be
–– IS_TRUE : the condition is true, the associated action has been
–– triggered
–– IS_FALSE : the condition is false, the associated action has been
–– triggered (only for the enable/disable conditions)
–– IS_UNKNOWN : the condition has been set but has not yet been
–– analysed (CONDITION_ITEM has not a valid value)
––
–– ACTION : provide the description of the condition, i.e:
–– – the sid of the item(s) for which the processing is to be
–– enabled
–– – the sid of the item for which a new limit set is to be set
–– and the limit set number
–– – the sid of an AP
––
–– STATUS : the return status of the operation
–– OK : operation successfull
–– INVALID_TESTNODE_MODE : the test node is not in executing mode
–– INVALID_PARAMETER : There is no (more) condition at the index
–– CONDITION_NUMBER (see above note).
–– INVALID_ITEM_NAME : CONDITION_ITEM is not managed locally.
–– RUNTIME_ERROR : an unexpected error occurred
procedure GET_CONDITION
(in CONDITION_ITEM : MONITOR_ITEM_NAME;
in CONDITION_NUMBER : INTEGER;
out CONDITION_REF : INTEGER;
out CONDITION_CHECK : CONDITION;
out CONDITION_VALUE : CONDITION_VAL;
out SINGLE_SHOT : BOOLEAN;
out STATE : CONDITION_STATE;
out ACTION : ACTION_DESCRIPTION;
out STATUS : UCL_RETURN); –– #92
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– General Conversion
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
procedure PATHNAME_TO_STRING (in PATH : PATHNAME;
out NAME: STRING); –– #93
–– convert the pathname type into a string type
–– If PATH is not existing, an empty string is returned
–– If NAME is too short to hold resulting string, the string is truncated
function PATH(in NAME: STRING) : PATHNAME; –– #94
–– convert the string type into a pathname type
–– returns Null–Pathname in case the path is not existing

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
procedure STATECODE_TO_STRING (in CODE : STATECODE;
out CODE_TEXT: STRING); –– #95
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
365 von/of: 662
–– convert the statecode type into a string type
–– CODE_TEXT should have a length of 8
–– If CODE_TEXT is too short to hold resulting string, the string is truncated
–– If CODE_TEXT is longer than 8 characters, it is filled with blanks
function CODE(in CODE_TEXT : STRING) : STATECODE; –– #96
–– convert the string type into a statecode type
–– If CODE_TEXT is longer than 8 characters, the string is truncated
–– If CODE_TEXT is shorter than 8 characters, the STATECODE is extended by blanks
END GROUND_LIBRARY;

Space Infrastructure
7.9.1.3 Interface Description
7.9.1.3.1 Monitoring
7.9.1.3.1.1 ENABLE_MONITORING
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
Specification
procedure ENABLE_MONITORING
(in ITEM: MONITOR_COLLECTION;
in LIMIT_SET: LIMIT_SET_NUMBER : = DEFAULT_LIMIT_SET;
in ADU: ADU_NAME := \\;
out STATUS: UCL_RETURN)
Description / Parameters
Enables monitoring of enditem(s).
ITEM : The item to be enabled, which can be
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
366 von/of: 662
– a single enditem of type MEASUREMENT or SW variable;
– a incomplete pathname pointing to a virtual node, thus enabling all MEASUREMENTs or SW variables
in that subtree;
– a monitor list, thus enabling all items in that list.
LIMIT_SET (optional) : the limit set to be used. In case the value is not given or the value given is
DEFAULT_LIMIT_SET (0), the selected limit set will be the currently selected limit set. Upon loading
of the database, the selected limit set is the limit set 1. This can be changed by calling the operation
SET_LIMIT_SET.
ADU (optional) : the ADU Descriptor to be applied. If ITEM is already acquired, this parameter will
be ignored. If there is only one ADU Description defined for ITEM, the parameter may be omitted. If
more than one is defined and the parameter is omitted, the command enables monitoring by starting
acquisition for all.
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
ENABLE_MONITORING (\apm\dms, 1, stat);

Space Infrastructure
7.9.1.3.1.2 DISABLE_MONITORING
Specification
procedure DISABLE_MONITORING
(in ITEM: MONITOR_COLLECTION;
out STATUS: UCL_RETURN);
Description / Parameters
Disables monitoring of enditems.
ITEM : The item to be disabled, which can be
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
367 von/of: 662
– a single enditem of type MEASUREMENT or SW variable;
– a incomplete pathname pointing to a virtual node, thus enabling all MEASUREMENTs or SW variables
in that subtree;
– a monitor list, thus disabling all items in that list.
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
DISABLE_MONITORING (\apm\dms, stat);
7.9.1.3.1.3 SET_HIGH_LIMIT
Specification
procedure SET_HIGH_LIMIT
(in ITEM: ANALOG_MONITOR_ITEM_NAME;
in LIMIT: REAL;
out STATUS: UCL_RETURN);
Description / Parameters
Changes the soft high limit of an enditem in the currently selected limit set. If the item is an integer
measurement or integer SW variable, LIMIT is rounded to the nearest integer.
ITEM : name of item to have its limit changed.
LIMIT : value to set high limit to.
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
SET_HIGH_LIMIT (\apm\dms\cpu_load, 80.0, stat);

Space Infrastructure
7.9.1.3.1.4 SET_INTEGER_HIGH_LIMIT
Specification
;procedure SET_INTEGER_HIGH_LIMIT
(in ITEM: INTEGER_MONITOR_ITEM_NAME;
in LIMIT: INTEGER;
out STATUS: UCL_RETURN)
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
368 von/of: 662
Description / Parameters
Changes the soft high limit of an integer enditem (measurement or software variable) in the currently
selected limit set.
ITEM : name of item to have its limit changed.
LIMIT : value to set high limit to.
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
SET_INTEGER_HIGH_LIMIT (\apm\dms\counter, 80, stat);
7.9.1.3.1.5 SET_LOW_LIMIT
Specification
procedure SET_LOW_LIMIT
(in ITEM: ANALOG_MONITOR_ITEM_NAME;
in LIMIT: REAL;
out STATUS: UCL_RETURN);
Description / Parameters
Changes the soft low limit of an enditem in the currently selected limit set. If the item is an integer
measurement or integer SW variable, LIMIT is rounded to the nearest integer.
ITEM : name of item to have its limit changed.
LIMIT : value to set low limit to.
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
SET_LOW_LIMIT (\apm\dms\cpu_load, 10.0, stat);

Space Infrastructure
7.9.1.3.1.6 SET_INTEGER_LOW_LIMIT
Specification
;procedure SET_INTEGER_LOW_LIMIT
(in ITEM: INTEGER_MONITOR_ITEM_NAME;
in LIMIT: INTEGER;
out STATUS: UCL_RETURN)
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
369 von/of: 662
Description / Parameters
Changes the soft low limit of an integer enditem (measurement or software variable) in the currently
selected limit set.
ITEM : name of item to have its limit changed.
LIMIT : value to set high limit to.
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
SET_INTEGER_LOW_LIMIT (\apm\dms\counter, 20, stat);
7.9.1.3.1.7 SET_DELTA_LIMIT
Specification
procedure SET_DELTA_LIMIT
(in ITEM: ANALOG_MONITOR_ITEM_NAME;
in LIMIT: REAL;
out STATUS: UCL_RETURN);
Description / Parameters
Changes the soft delta limit of an enditem in the currently selected limit set. If the item is an integer
measurement or integer SW variable, LIMIT is rounded to the nearest integer.
ITEM : name of item to have its limit changed.
LIMIT : value to set delta limit to.
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
SET_DELTA_LIMIT (\apm\dms\cpu_load, 20.0, stat);

Space Infrastructure
7.9.1.3.1.8 SET_INTEGER_DELTA_LIMIT
Specification
;procedure SET_INTEGER_DELTA_LIMIT
(in ITEM: INTEGER_MONITOR_ITEM_NAME;
in LIMIT: INTEGER;
out STATUS: UCL_RETURN)
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
370 von/of: 662
Description / Parameters
Changes the soft delta limit of an integer enditem (measurement or software variable) in the currently
selected limit set.
ITEM : name of item to have its limit changed.
LIMIT : value to set high limit to.
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
SET_INTEGER_DELTA_LIMIT (\apm\dms\counter, 10, stat);
7.9.1.3.1.9 SET_EXCEPTION_COUNT
Specification
procedure SET_EXCEPTION_COUNT
(in ITEM: MONITOR_ITEM_NAME;
in N_COUNT: INTEGER;
out STATUS: UCL_RETURN);
Description / Parameters
Changes the exception count value of a measurement or SW variable.
ITEM : name of item to have its exception count changed.
N_COUNT : integer value to set exception count to.
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
SET_EXCEPTION_COUNT (\apm\dms\status, 5, stat);

Space Infrastructure
7.9.1.3.1.10 SET_EXPECTED_STATE
Specification
procedure SET_EXPECTED_STATE
(in ITEM: DISCRETE_MONITOR_ITEM_NAME;
in STATE: STATECODE;
out STATUS: UCL_RETURN);
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
Description / Parameters
Changes the expected state of a discrete measurement or SW variable.
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
371 von/of: 662
ITEM : name of item to have its expected state changed.
STATE : state code for desired expected state of item.
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
SET_EXPECTED_STATE (\apm\dms\status, $OFF, stat);
7.9.1.3.1.11 SET_EXPECTED_VALUE
Specification
procedure SET_EXPECTED_VALUE
(in ITEM: BYTE_STREAM_MONITOR_ITEM_NAME;
in VALUE: STRING;
out STATUS: UCL_RETURN);
Description / Parameters
Changes the expected value of a byte stream measurement or SW variable.
ITEM : name of item to have its expected value changed.
VALUE : string containing desired expected value of item.
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
SET_EXPECTED_VALUE (\apm\dms\message, ”Hallo ESA”, stat);

Space Infrastructure
7.9.1.3.1.12 SET_LIMIT_SET
Specification
procedure SET_LIMIT_SET
(in ITEM: ANALOG_MONITOR_ITEM_NAME;
in LIMIT_SET: LIMIT_SET_NUMBER;
out STATUS: UCL_RETURN);
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
372 von/of: 662
Description / Parameters
ITEM : path name of item to have its limit set changed.
LIMIT_SET : identifier of the desired limit set. Its value must be between 1 and the number of limits
defined for ITEM.
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
SET_LIMIT_SET (\apm\dms\memory_pages, 4, stat);
7.9.1.3.1.13 GET_ENDITEM_MONITOR_STATUS
Specification
procedure GET_ENDITEM_MONITOR_STATUS
(in ITEM: MONITOR_ITEM_NAME;
out MONITORING_STATUS: MONITOR_STATUS;
out STATUS: UCL_RETURN);
Description / Parameters
Returns the current monitoring status for an enditem.
ITEM : name of enditem to monitor.
MONITORING_STATUS : returns monitoring status of Item.
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
GET_ENDITEM_MONITOR_STATUS (\apm\power\consumption, enditem_status, stat);

Space Infrastructure
7.9.1.3.1.14 GET_FULL_ENDITEM_MONITOR_STATUS
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
Specification
procedure GET_FULL_ENDITEM_MONITOR_STATUS
(in ITEM: MONITOR_ITEM_NAME;
out MONITORING_STATUS: FULL_MONITOR_STATUS;
out STATUS: UCL_RETURN);
Description / Parameters
Returns the current monitoring status and monitoring values for an enditem.
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
373 von/of: 662
ITEM : pathname of enditem to monitor.
MONITOR_STATUS : returns the detailed monitoring status record of Item, containing alternative
variants depending on the item type and whether a limit set is defined (see the definition of type
FULL_MONITOR_STATUS.)
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
GET_FULL_ENDITEM MONITOR_STATUS (\apm\power\consumption, monitor_status, stat);
7.9.1.3.1.15 GET_ACQUISITION_STATUS
procedure GET_ACQUISITION_STATUS
(in ITEM: MONITOR_ITEM_NAME;
out ENDITEM_ACQ_STATUS: ACQUISITION_STATUS;
out STATUS: UCL_RETURN);
Description / Parameters
Returns the current acquisition status for an enditem. This operation can be called locally on the test
node maintaining the enditem or remotely on another test node.
ITEM : pathname of enditem (measurement or software variable).
ENDITEM_ACQ_STATUS : returns the acquisition status of item.
VALID: The enditem has been startet for acquisition and a value has been delivered
NOT_ACQ : The measurement has not been started for acquisition
NOT_RECVD : The measurement has been started for acquisition but no value has been received
up to now
NOT_MAINTAINED: The enditem is not maintained by any test node
DISAB : The measurement / sw variable has been ”disabled” by a condition
INVALID : No valid value exists for the enditem, e.g. it could not be calibrated
STATIC : The SAS has indicated that it currently cannot deliver the end–item
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
GET_ACQUISITION_STATUS (\apm\power\consumption, acq_status, stat);
IF acqu_status = VALID
then my_var := \apm\power\consumption;
END IF;

Space Infrastructure
7.9.1.3.1.16 GET_INTEGER
procedure GET_INTEGER
(in ITEM: INTEGER_MONITOR_ITEM_NAME;
out VALUE: INTEGER;
out TIME_TAG: TIME;
out ENDITEM_ACQ_STATUS: ACQUISITION_STATUS;
out STATUS: UCL_RETURN);
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
374 von/of: 662
Description / Parameters
Returns the current value for an integer enditem. This operation can be called locally on the test node
maintaining the enditem or remotely on another test node.
ITEM : pathname of an integer enditem (measurement or software variable).
VALUE : the value of the enditem. In case the value is not VALID (see ENDITEM_ACQ_STATUS),
the last valid value will be returned (or a default null value in case the value has never been set)
TIME_TAG : the time tag (local time) of the last value. In case the value is not VALID (see ENDI-
TEM_ACQ_STATUS) the time tag of the last valid value will be returned (or a default null time in case
the value has never been set)
ENDITEM_ACQ_STATUS : returns the acquisition status of item.
VALID: The enditem has been startet for acquisition and a value has been delivered
NOT_ACQ : The measurement has not been started for acquisition
NOT_RECVD : The measurement has been started for acquisition but no value has been received
up to now
NOT_MAINTAINED: The enditem is not maintained by any test node
DISAB : The measurement / sw variable has been ”disabled” by a condition
INVALID : No valid value exists for the enditem, e.g. it could not be calibrated
STATIC : The SAS has indicated that it cannot deliver any more the end–item
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
GET_INTEGER (\apm\power\counter, int_value, time_tag, acq_status, stat);

Space Infrastructure
7.9.1.3.1.17 GET_FLOAT
procedure GET_FLOAT
(in ITEM: FLOAT_MONITOR_ITEM_NAME;
out VALUE: REAL;
out TIME_TAG: TIME;
out ENDITEM_ACQ_STATUS: ACQUISITION_STATUS;
out STATUS: UCL_RETURN);
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
375 von/of: 662
Description / Parameters
Returns the current value for a float enditem. This operation can be called locally on the test node
maintaining the enditem or remotely on another test node.
ITEM : pathname of a float enditem (measurement or software variable).
VALUE : the value of the enditem. In case the value is not VALID (see ENDITEM_ACQ_STATUS),
the last valid value will be returned (or a default null value in case the value has never been set)
TIME_TAG : the time tag (local time) of the last value. In case the value is not VALID (see ENDI-
TEM_ACQ_STATUS) the time tag of the last valid value will be returned (or a default null time in case
the value has never been set)
ENDITEM_ACQ_STATUS : returns the acquisition status of item.
VALID: The enditem has been startet for acquisition and a value has been delivered
NOT_ACQ : The measurement has not been started for acquisition
NOT_RECVD : The measurement has been started for acquisition but no value has been received
up to now
NOT_MAINTAINED: The enditem is not maintained by any test node
DISAB : The measurement / sw variable has been ”disabled” by a condition
INVALID : No valid value exists for the enditem, e.g. it could not be calibrated
STATIC : The SAS has indicated that it cannot deliver any more the end–item
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
GET_float (\apm\power\consumption, flt_value, time_tag, acq_status, stat);

Space Infrastructure
7.9.1.3.1.18 GET_STATECODE
procedure GET_STATE_CODE
(in ITEM: DISCRETE_MONITOR_ITEM_NAME;
out VALUE: STATECODE;
out TIME_TAG: TIME;
out ENDITEM_ACQ_STATUS: ACQUISITION_STATUS;
out STATUS: UCL_RETURN);
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
376 von/of: 662
Description / Parameters
Returns the current value for a discrete enditem. This operation can be called locally on the test node
maintaining the enditem or remotely on another test node.
ITEM : pathname of a discrete enditem (measurement or software variable).
VALUE : the value of the enditem. In case the value is not VALID (see ENDITEM_ACQ_STATUS),
the last valid value will be returned (or a default null value in case the value has never been set)
TIME_TAG : the time tag (local time) of the last value. In case the value is not VALID (see ENDI-
TEM_ACQ_STATUS) the time tag of the last valid value will be returned (or a default null time in case
the value has never been set)
ENDITEM_ACQ_STATUS : returns the acquisition status of item.
VALID: The enditem has been startet for acquisition and a value has been delivered
NOT_ACQ : The measurement has not been started for acquisition
NOT_RECVD : The measurement has been started for acquisition but no value has been received
up to now
NOT_MAINTAINED: The enditem is not maintained by any test node
DISAB : The measurement / sw variable has been ”disabled” by a condition
INVALID : No valid value exists for the enditem, e.g. it could not be calibrated
STATIC : The SAS has indicated that it cannot deliver any more the end–item
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
GET_STATECODE (\apm\power\status, disc_value, time_tag, acq_status, stat);

Space Infrastructure
7.9.1.3.1.19 GET_BYTE_STREAM
procedure GET_BYTE_STREAM
(in ITEM: BYTE_STREAM_MONITOR_ITEM_NAME;
out VALUE: STRING;
out TIME_TAG: TIME;
out ENDITEM_ACQ_STATUS: ACQUISITION_STATUS;
out STATUS: UCL_RETURN);
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
377 von/of: 662
Description / Parameters
Returns the current value for a byte stream enditem. This operation can be called locally on the test
node maintaining the enditem or remotely on another test node.
ITEM : pathname of a byte–stream enditem (measurement or software variable).
VALUE : the value of the enditem. In case the value is not VALID (see ENDITEM_ACQ_STATUS),
the last valid value will be returned (or a default null value in case the value has never been set). If
the string given is not large enough, the value is truncated.
TIME_TAG : the time tag (local time) of the last value. In case the value is not VALID (see ENDI-
TEM_ACQ_STATUS) the time tag of the last valid value will be returned (or a default null time in case
the value has never been set)
ENDITEM_ACQ_STATUS : returns the acquisition status of item.
VALID: The enditem has been startet for acquisition and a value has been delivered
NOT_ACQ : The measurement has not been started for acquisition
NOT_RECVD : The measurement has been started for acquisition but no value has been received
up to now
NOT_MAINTAINED: The enditem is not maintained by any test node
DISAB : The measurement / sw variable has been ”disabled” by a condition
INVALID : No valid value exists for the enditem, e.g. it could not be calibrated
STATIC : The SAS has indicated that it cannot deliver any more the end–item
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
GET_BYTE_STREAM (\apm\power\message, str_value, time_tag, acq_status, stat);

Space Infrastructure
7.9.1.3.2 Time Management
7.9.1.3.2.1 CLOCK
Specification
function CLOCK
(in BASE: TIME_BASE: = LOCAL_TIME) : TIME;
Description / Parameters
Returns the actual local time or SMT
BASE (optional) : time_base to use; by default, local time.
Example
my_time_variable : = CLOCK;
7.9.1.3.2.2 DELAY
Specification
procedure DELAY
(in DELAY: DURATION;
in BASE: TIME_BASE:= LOCAL_TIME);
Description / Parameters
Waits the given time interval. Returns nothing.
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
DELAY : duration to delay, expressed as a fixed–point number in seconds.
BASE : time base to use; by default, local time.
Example
DELAY (4.6 [s]);
7.9.1.3.2.3 WAIT_UNTIL
Specification
procedure WAIT_UNTIL
(in DUE_TIME : TIME;
in BASE: TIME_BASE: = LOCAL_TIME;
out STATUS: UCL_RETURN);
Description / Parameters
Waits until the given time is reached.
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
378 von/of: 662
DUE_TIME : time to wait until.
BASE (optional) : time base to use; by default, local time.
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
WAIT_UNTIL (3:00:00.000, LOCAL_TIME, stat);

Space Infrastructure
7.9.1.3.2.4 START_SMT
Specification
procedure START_SMT
(in VALUE: TIME: ~:~ ;
out STATUS: UCL_RETURN);
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
379 von/of: 662
Description / Parameters
Starts Simulation Mean Time (SMT), and optionally sets it to a given value. If SMT is already running,
the new VALUE is immediately set, and time is incremented accordingly thereafter.
VALUE (optional) : new SMT; by default current SMT is resumed.
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
START_SMT (10.01.95 20:00:00, STATUS : stat);
7.9.1.3.2.5 STOP_SMT
Specification
procedure STOP_SMT
(out STATUS: UCL_RETURN);
Description / Parameters
Stop the running Simulation Mean Time.
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
STOP_SMT (stat);

Space Infrastructure
7.9.1.3.3 GTAP Handling
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
380 von/of: 662
In the following, the term GTAP (Ground Test Automated Procedure) is used for Automated
Procedures running in the Ground System (to differentiate from Automated Procedures running in the
Onboard System)
7.9.1.3.3.1 EXECUTE_AP
Specification
procedure EXECUTE_AP
(in AP: AP_NAME ();
in PRIO: PRIORITY: = LOW;
in NODE: NODE_NAME : = \\;
out ID: AP_ID;
out STATUS: UCL_RETURN)
Description / Parameters
Starts execution of a GTAP. If the procedure is called from within a GTAP, the called GTAP runs
asynchronously unless SYNCHRONISE_WITH_AP is also called.
AP : name of GTAP to run; optionally including its list of parameters.
PRIO (optional) : the GTAP’s priority (HIGH or LOW).
NODE (optional) : node on which the GTAP is to be executed: by default the current node.
ID : returns the new GTAP’s identifier, if it could be started; otherwise –1.
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
EXECUTE_AP
(\apm\dms\start_up(A,B,C), low_priority, \apm\dms, my_AP_ID, exec_stat);
7.9.1.3.3.2 SYNCHRONISE_WITH_AP
Specification
procedure SYNCHRONISE_WITH_AP
(in AP: AP_ID;
in NODE: NODE_NAME : = \\;
out COMPLETION: AP_COMPLETION_STATE;
out STATUS: UCL_RETURN);
Description / Parameters
Forces the calling GTAP to synchronise with the called GTAP (by default, EXECUTE_AP starts the
called GTAP asynchronously). SYNCHRONISE_WITH_AP blocks until the called GTAP has finished.
AP : internal GTAP identifier, from EXECUTE_AP.
NODE (optional) : node on which the GTAP is to be executed; by default the current node.
COMPLETION : returns the called GTAP’s completion state.
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
SYNCHRONISE_WITH_AP (my_AP_ID, \DMS\SCOE, my_completion_state, stat);

Space Infrastructure
7.9.1.3.3.3 SUSPEND_AP
Specification
procedure SUSPEND_AP
(in AP: AP_ID;
in NODE: NODE_NAME : = \\;
out STATUS: UCL_RETURN);
Description / Parameters
Suspends execution of a GTAP on a given test node.
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
381 von/of: 662
AP : internal GTAP identifier, given to it when started by EXECUTE_AP.
NODE (optional) : the node running the GTAP : by default, the current node.
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
SUSPEND_AP (power_down_AP_ID,\\, stat);
7.9.1.3.3.4 RESUME_AP
Specification
procedure RESUME_AP
(in AP: AP_ID;
in NODE: NODE_NAME : = \\;
out STATUS: UCL_RETURN);
Description / Parameters
Resumes execution of a suspended GTAP.
AP : internal GTAP identifier, given to it when started by EXECUTE_AP.
NODE (optional) : the node running the GTAP : by default the local node.
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
RESUME_AP (my_AP_reference, \\, stat);
7.9.1.3.3.5 OWN_AP_ID
Specification
;function OWN_AP_ID : AP_ID
Description / Parameters
Returns the GTAP identifier of the AP calling that function. This function is not available from HLCL as
the system library commands executed from HLCL do not have a GTAP identifier.
Example
MY_AP_ID := OWN_AP_ID;

Space Infrastructure
7.9.1.3.3.6 GET_AP_ID
Specification
procedure GET_AP_ID
(in AP: AP_NAME;
in NODE: NODE_NAME : = \\;
out NUMBER: INTEGER;
out ID_LIST: AP_ID_LIST;
out STATUS: UCL_RETURN);
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
382 von/of: 662
Description / Parameters
Returns all GTAP identifiers for a given automated procedure name on a given test node. Since
several instances of a GTAP may run in parallel on one test node, a list of GTAP identifiers is returned.
AP : name of GTAP to find.
NODE (optional) : node to search; by default, the local node.
NUMBER : returns the number of GTAP identifiers in the ID_List for this GTAP.
ID_LIST : returns list of AP_IDs found. Unused fields of the ID_List are filled with zeroes.
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
GET_AP_ID
7.9.1.3.3.7 GET_AP_STATUS
(\apm\power\control_program, \apm\dms, my_number_of_APs, my_AP_list, stat);
Specification
procedure GET_AP_STATUS
(in AP: AP_ID;
in NODE: NODE_NAME : = \\;
out EXEC_STATE: AP_EXECUTION_STATE;
out STATUS: UCL_RETURN);
Description / Parameters
Returns the current status of a GTAP.
AP : AP_ID of the GTAP whose status is required.
NODE (optional) : node to search; by default, the current node.
EXEC_STATE : returns the execution state of the GTAP.
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
GET_AP_STATUS (\apm\power\off\procedure, \apm\dms, my_AP_status, stat);

Space Infrastructure
7.9.1.3.3.8 READ_MESSAGE_FROM_AP
Specification
procedure READ_MESSAGE_FROM_AP
(in BLOCK: BOOLEAN : = TRUE;
out AP: AP_ID;
out NODE_NAME: USER_MESSAGE;
out MESSAGE : USER_MESSAGE;
out STATUS: UCL_RETURN);
Description / Parameters
Reads a message asynchronously from another GTAP.
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
BLOCK (optional) : boolean flag controlling the source of the message, as follows:
– TRUE : waits until a GTAP really sends a message (by default)
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
383 von/of: 662
– FALSE : reads the next message buffered, or if none, returns an empty string.
AP : returns identifier of the GTAP sending the message.
NODE_NAME : returns string identifying node on which other GTAP is running.
MESSAGE : returns string from the other GTAP.
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
READ_MESSAGE_FROM_AP (FALSE, the_AP_ID, the_AP_message, stat);
7.9.1.3.3.9 WRITE_MESSAGE_TO_AP
Specification
procedure WRITE_MESSAGE_TO_AP
(in AP: AP_ID;
in NODE: NODE_NAME : = \\;
in MESSAGE: USER_MESSAGE : = DEFAULT_MESSAGE;
out STATUS: UCL_RETURN);
Description / Parameters
Sends a message asynchronously from one GTAP to another, i.e. without waiting for the receiving AP
to accept the message. The caller simply sends the message and continues.
AP : AP_ID of GTAP to receive the message.
NODE (optional) : processor node running receiving GTAP; by default, the current node.
MESSAGE : string to send.
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
WRITE_MESSAGE_TO_AP
(dms_control_AP_ID, \DMS\SCOE, ”EMERGENCY STOP”, stat);

Space Infrastructure
7.9.1.3.4 Application Handling
unloaded
LOAD_APPLICATION
UNLOAD_APPLICATION
idle
INIT_APPLICATION
UNLOAD_APPLICATION
RESET_APPLICATION
initialised
START_APPLICATION
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
aborted
Figure: Relationship of Application Handling Primitives
7.9.1.3.4.1 LOAD_APPLICATION
Specification
procedure LOAD_APPLICATION
(in NAME : APPLICATION_NAME;
in NODE: NODE_NAME := \\;
in PARAMS: USER_MESSAGE : = DEFAULT_MESSAGE;
out APPL: APPLICATION_ID;
out STATUS: UCL_RETURN)
Description / Parameters
Loads an application on to the local test node or on a workstation.
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
384 von/of: 662
(crashes)
running
NAME : the name of the executable image in the predefined application directory.
NODE : the name of the node where the SAS shall execute. By default the empty pathname denotes
the local testnode. The workstations are referenced by their EGSE node entry in MDA. Starting a SAS
on another testnode is prohibited.
PARAMS (optional) : parameter string up to 255 characters to pass to the application.
APPL : returns the application’s ID to be used for subsequent control operations.
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
LOAD_APPLICATION (”exp_monitor”, ”Exp=123”, my_appl_ID, stat);

Space Infrastructure
7.9.1.3.4.2 UNLOAD_APPLICATION
Specification
procedure UNLOAD_APPLICATION
(in APPL: APPLICATION_ID;
out STATUS: UCL_RETURN);
Description / Parameters
Unloads the specified application from memory.
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
385 von/of: 662
APPL : APPLICATION_ID as returned from LOAD_APPLICATION (section 7.9.1.3.4.1).
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
UNLOAD_APPLICATION (smives_appl_ID, stat);
7.9.1.3.4.3 INIT_APPLICATION
Specification
procedure INIT_APPLICATION
(in APPL: APPLICATION_ID;
in MESSAGE: USER_MESSAGE: = DEFAULT_MESSAGE;
out STATUS: UCL_RETURN);
Description / Parameters
Initialises the specified application.
APPL : APPLICATION_ID as returned from LOAD_APPLICATION (section 7.9.1.3.4.1).
MESSAGE (optional) : string up to 255 characters to send to the application.
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
INIT_APPLICATION (my_appl_ID, ”GNC_RECEIVER_ON”, stat);
7.9.1.3.4.4 START_APPLICATION
Specification
procedure START_APPLICATION
(in APPL: APPLICATION_ID;
out STATUS: UCL_RETURN);
Description / Parameters
Starts the application running.
APPL : APPLICATION_ID as returned from LOAD_APPLICATION (section 7.9.1.3.4.1).
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
START_APPLICATION (my_appl_ID, stat);

Space Infrastructure
7.9.1.3.4.5 RESET_APPLICATION
Specification
procedure RESET_APPLICATION
(in APPL: APPLICATION_ID;
out STATUS: UCL_RETURN);
Description / Parameters
Resets the specified application.
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
386 von/of: 662
APPL : APPLICATION_ID as returned from LOAD_APPLICATION (section 7.9.1.3.4.1).
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
RESET_APPLICATION (my_appl_ID, stat);
7.9.1.3.4.6 GET_APPLICATION_STATUS
Specification
procedure GET_APPLICATION_STATUS
(in APPL: APPLICATION_ID;
out STATE: APPLICATION_STATE;
out ERROR_COUNT: INTEGER;
out ERROR_MESSAGE: APPLICATION_ERROR_MESSAGE;
out STATUS: UCL_RETURN);
Description / Parameters
Returns the status of an application, including error status and statistics.
APPL : APPLICATION_ID as returned from LOAD_APPLICATION (section 7.9.1.3.4.1).
STATE : returns state of application.
ERROR_COUNT : returns integer count of errors in the application.
ERROR_MESSAGE : returns error message from the application.
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
GET_APPLICATION_STATUS (appl_ID, appl_state, err_count, appl_error_mess, stat);

Space Infrastructure
7.9.1.3.4.7 GET_APPLICATION_ID
Specification
procedure GET_APPLICATION_ID
(in NAME: APPLICATION_NAME;
out APPL: APPLICATION_ID;
out STATUS: UCL_RETURN);
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
Description / Parameters
Returns the Application ID of an application, if the application is loaded
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
387 von/of: 662
NAME : The name of the application.
APPL : APPLICATION_ID as returned from LOAD_APPLICATION (section 7.9.1.3.4.1).
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
GET_APPLICATION_ID (appl_name, appl_id, stat);
7.9.1.3.4.8 GET_APPLICATION_NAME
Specification
procedure GET_APPLICATION_NAME
(in APPL: APPLICATION_ID;
out NAME: APPLICATION_NAME;
out STATUS: UCL_RETURN);
Description / Parameters
Returns the name of an application
APPL : APPLICATION_ID as returned from LOAD_APPLICATION (section 7.9.1.3.4.1).
NAME : returns the name of the application.
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
GET_APPLICATION_NAME (appl_ID, appl_name, stat);

Space Infrastructure
7.9.1.3.4.9 READ_MESSAGE_FROM_APPLICATION
Specification
procedure READ_MESSAGE_FROM_APPLICATION
(in BLOCK: BOOLEAN: = TRUE;
out APPL: APPLICATION_ID;
out MESSAGE : USER_MESSAGE;
out STATUS: UCL_RETURN);
Description / Parameters
Reads a message from an application.
BLOCK : boolean flag, controlling the source of the read:
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
388 von/of: 662
– TRUE, waits until an application really sends a message;
– FALSE, reads the next message buffered. If none, returns an empty string.
APPL : returns APPLICATION_ID of the application sending the message.
MESSAGE : returns a string containing the message
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
READ_MESSAGE_FROM_APPLICATION (FALSE, appl_ID, appl_message, stat)
7.9.1.3.4.10 WRITE_MESSAGE_TO_APPLICATION
Specification
procedure WRITE_MESSAGE_TO_APPLICATION
(in APPL: APPLICATION_ID;
in MESSAGE : USER_MESSAGE;
out STATUS: UCL_RETURN);
Description / Parameters
Sends a message to an application.
APPL : the APPLICATION_ID as returned from LOAD_APPLICATION.
MESSAGE : string of up to 255 characters to be sent.
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
WRITE_MESSAGE_TO_APPLICATION (smives_appl_ID, ”IEEE_BUS_1_INIT”, stat);

Space Infrastructure
7.9.1.3.5 Issue of HW Stimuli
7.9.1.3.5.1 ISSUE
Specification
procedure ISSUE
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
(in ITEM: ISSUE_ITEM_NAME();
in PRIO: PRIORITY := LOW;
in AT_TIME: TIME: = ~:~;
in BASE: TIME_BASE: = LOCAL_TIME;
in ONBOARD_EXECUTION_TIME: TIME := ~:~;
in TIMEOUT: DURATION: = DEFAULT_ISSUE_TIMEOUT ;
out STATUS: UCL_RETURN)
Description / Parameters
Issues a stimulus (or Telecommand).
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
389 von/of: 662
ITEM : the database enditem describing what has to be issued. It can denote a parameter list, as defined
for the enditem.
Note: the enditem may also be maintained by a remote node
PRIO : the priority to be used for issuing the item (HIGH or LOW)
AT_TIME (optional) : The time to issue the stimulus;
Default: ”~:~” = ”00.00.01”, i.e. the default ”no time”.
The purpose of the AT_TIME parameter shall be the same for all GDU alternatives:
For MDB enditems of type EGSE_ANALOGUE_STIMULUS, EGSE_DISCRETE_STIMULUS,
EGSE_BINARY_PACKET and EGSE_PREDEFINED_TC, the time value is written as the
TIME_TAG into the GDU generated by the command and sent to the SAS. The SAS then has to extract
the TIME_TAG from the GDU and execute the stimulus at the given time.
For MDB enditems of type GDU_DESCRIPTION_LIST the AT_TIME value will be written into the
time tasg field of the GDU header of each stimulus referenced within the GDU list.

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
390 von/of: 662
ONBOARD_EXECUTION_TIME (optional): The time to execute the telecommand onboard
Default: ”~:~” = ”00.00.01”, i.e. the default ”no time”.
For MDB Enditems of type EGSE_PREDEFINED_TC, the ONBOARD_EXECUTION _TIME value
will be written to the TIME field of the secondary header of the corresponding CCSDS packet. In this
case, the TIME_ID field of the secondary header shall be set to ’10’B, which means: a time tag is present.
No interpretation of TIME_BASE will be done by CGS in this case. The TIME_TAG of the GDU header
generated by the command will be independent from this.
If no ONBOARD_EXECUTION _TIME parameter is given, i.e. the default value is applied , the
TIME_ID and TIME field shall be set to ’10’B (= time tagged command: the execution of the command
is scheduled by the onboard system to the specified time)
For MDB enditems of type GDU_DESCRIPTION_LIST the ONBOARD_EXECUTION _TIME
value will be written into the TIME field of the secondary header of each CCSDS packet referenced
within the GDU list.
Remark: If the TIME_ID is of value ’00’B (UNDEFINED) or ’11’B (NO_TIME_TAG), the TIME field
in the secondary header shall be set to zero via the database default entry, in case no ONBOARD_EX-
ECUTION_TIME parameter is given.
BASE (optional) : specifies if AT_TIME is local time or SMT; by default, local time.
TIMEOUT : the maximum time to wait for acknowledgement of this stimulus or telecommand
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
ISSUE (\apm\ecls\main_temperature(21.1), AT_TIME : 10:00:00, STATUS : stat);

Space Infrastructure
7.9.1.3.5.2 ISSUE_AND_VERIFY
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
Specification
procedure ISSUE_AND_VERIFY
(in ITEM: SINGLE_GDU_NAME();
in PRIO: PRIORITY := LOW;
in AT_TIME: TIME := ~:~;
in BASE: TIME_BASE := LOCAL_TIME;
in ONBOARD_EXECUTION_TIME: TIME := ~:~;
in TIMEOUT: DURATION := default_issue_timeout;
in ACTIVATION_DELAY: DURATION := –1.0 [s];
in VERIFICATION_TIMEOUT : DURATION := –1.0 [s];
in WAIT_TIL_END: BOOLEAN := FALSE;
out VERIFICATION_STATUS: CMD_VERIFICATION_STATUS;
out STATUS: UCL_RETURN);
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
391 von/of: 662
Description / Parameters
Issues a stimulus (or Telecommand/Binary packet) and verifies expected values for measurements,
defined as part of the enditem definition in the MDB. The verification starts after the command has
been acknowledged and a specified time (ACTIVATION_DELAY) has elapsed. If in the
VERIFICATION_TIMEOUT period all specified expected values have been verified, the verification
status is set to OK, otherwise to FAILED. A message is generated accordingly.
If during the verification an error occurs, the verification status is set to ERROR.
If WAIT_TIL_END is set, the procedure waits until the end of the verification and the verification status is
returned in VERIFICATION_STATUS; otherwise the status can be read by the procedure GET_VERIFICA-
TION_STATUS at any time.
Send GDU
Activation_delay
Acknowledge
NACK:
Verif. Status: undefined
Verification Timeout
all values OK:
report OK
Verification Status: OK
time
min 1 value NOK:
report failure
Verification Status: FAILED
ITEM : the database enditem (GDU) describing what has to be issued. It can denote a parameter list,
as defined for the enditem.
Notes: (1) the enditem may also be maintained by a remote node
PRIO : the priority to be used for issuing the GDU (HIGH or LOW)
AT_TIME (optional) : The time to issue the GDU;
––> see procedure ISSUE
ONBOARD_EXECUTION_TIME (optional): The time to execute the telecommand onboard
––> see procedure ISSUE
BASE (optional) : specifies if AT_TIME is local time or SMT; by default, local time.

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
TIMEOUT : the maximum time to wait for acknowledgement of this GDU
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
392 von/of: 662
ACTIVATION_DELAY: the time to wait after sending of the GDU until the verification of the measurements
is started. If this value is set to 0.0, the checking is performed immediately after the command
has been acknowledged. If the default value (–1.0) is given, the activation delay is taken from the MDB
definition.
VERIFICATION_TIMEOUT: the time to wait after the ACTIVATION_DELAY has expired and before
the verification of the measurements is finished. If in this period the verification of the value(s) for
measurement(s) defined in the MDB is successful, a message is generated and the verification status
is set to OK. If VERIFICATION_TIMEOUT has elapsed and the verification of at least one measurment
is not successful, a message is generated indicating failure and the verification status is set to
FAILED.
If VERIFICATION_TIMEOUT is set to 0.0, the checking is performed immediately after the ACTIVA-
TION_DELAY and then is finished.If the default value (–1.0) is given, the activation delay is taken from
the MDB definition.
WAIT_TIL_END: If true, the procedure returns after the verification has finished. If false, the
procedure returns immediately after the GDU has been acknowledged resp. after TIMEOUT. In this
case, the VERIFICATION_STATUS is set to IN_PROGRESS.
VERIFICATION_STATUS: Status of the verification
STARTED, Verification is started, i.e. Activation Delay is currently running
IN_PROGRESS, Verification is in progress, i.e Verification Timeout is running
and not all measurements have expected values yet
TC_VERIF_OK, Verification performed with success. All measurements had expected
values.
TC_VERIF_FAILED, Verification performed with no success, i.e. Verification
Timeout elapsed and at least one measurement had no expected value
ERROR, Error during Verification Timeout. During the verification timeout
an internal error occured
NO_VERIFICATION No Verification defined for this enditem (i.e. in MDB there are no
measurements specified which to verify for this command)
ABORTED Verification aborted due to issue of same command or stop of remote
TES
UNDEFINED The verifcation status is not defined, i.e. the sending of the
command aborted due to error or negative acknowledge or timeout
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
ISSUE_AND_VERIFY(\apm\eps\power_on, VERIFICATION_TIMEOUT: 3.0[s],WAIT_TIL_END: true,
VERIFICATION_STATUS: v_stat, STATUS : stat);

Space Infrastructure
7.9.1.3.5.3 GET_VERIFICATION_STATUS
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
Specification
procedure GET_VERIFICATION_STATUS
(in ITEM: GDU_ITEM_NAME;
out VERIFICATION_STATUS: CMD_VERIFICATION_STATUS;
out STATUS: UCL_RETURN);
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
393 von/of: 662
ENDITEM : name of stimulus or telecommand for which the verification status is to be fetched.
Enditem may be defined on local or remote node.
VERIFICATION_STATUS: Status of the verification. Applies to the last command (GDU) successfully
sent or just being sent.
STARTED, Verification is started, i.e. Activation Delay is currently running
IN_PROGRESS, Verification is in progress, i.e Verification Timeout is running
and not all measurements have expected values yet
TC_VERIF_OK, Verification performed with success. All measurments had expected
values.
TC_VERIF_FAILED, Verification performed with no success, i.e. Verification
Timeout elapsed and at least one measurement had no expected value
ERROR, Error during Verification Timeout. During the verification timeout
an internal error occured
NO_VERIFICATION No Verification defined for this enditem (i.e. in MDB there are no
measurements specified which to verify for this command)
ABORTED Verification aborted due to issue of same command or stop of remote
TES
UNDEFINED The verifcation status is not defined, i.e. the sending of the
command aborted due to error or negative acknowledge or timeout
7.9.1.3.5.4 ENABLE_ENDITEM
Specification
procedure ENABLE_ENDITEM
(in ENDITEM: ISSUE_ITEM_NAME;
out STATUS: UCL_RETURN);
Description / Parameters
Enables an enditem that has been disabled, either temporarily through DISABLE_ENDITEM, or
permanently through definition in the configuration database.
ENDITEM : name of stimulus or telecommand to be enabled.
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
ENABLE_ENDITEM (\apm\power\off, stat);

Space Infrastructure
7.9.1.3.5.5 DISABLE_ENDITEM
Specification
procedure DISABLE_ENDITEM
(in ENDITEM: ISSUE_ITEM_NAME;
out STATUS: UCL_RETURN);
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
Description / Parameters
Disables an enditem that has been enabled temporarily or permanently.
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
394 von/of: 662
ENDITEM : name of stimulus or telecommand to be disabled.
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
DISABLE_ENDITEM (\apm\power\off, stat);
7.9.1.3.5.6 DOWNLOAD
Specification
procedure DOWNLOAD
(in APPL: APPLICATION_ID;
in ITEM: DOWNLOAD_ITEM_NAME;
in NODE: NODE_NAME :=\\;
out STATUS: UCL_RETURN);
Description / Parameters
Downloads a file to a SAS, the corresponding frontend equipment managed by the SAS or the unit
under test through a SAS.
APPL : name of the SAS which is doing the download
ITEM : name of the item to be downloaded
NODE : name of the node into which the item has to be downloaded. An empty pathname indicates
some kind of default for the SAS.
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
DISABLE_ENDITEM (\apm\power\off, stat);

Space Infrastructure
7.9.1.3.6 Raw Data Handling
7.9.1.3.6.1 START_ACQUISITION
Specification
procedure START_ACQUISITION
(in ITEM: ACQUISITION_COLLECTION;
in ADU: ADU_NAME := \\;
out STATUS: UCL_RETURN)
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
Description / Parameters
Starts data acquisition on the local test node for the given enditem(s).
ITEM : individual enditem or group of enditems to be acquired.
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
395 von/of: 662
ADU (optional) : the ADU Descriptor to be applied. If there is only one ADU Descriptor defined for
ITEM, the parameter may be omitted. If more than one ADU Descriptor is defined and the parameter
is omitted, the command starts acquisition for all ADUs (TBC). If ITEM is already of type ADU_DE-
SCRIPTION, the parameter is ignored.
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
START_ACQUISITION (\apm\dms\link\statistics, stat);
7.9.1.3.6.2 STOP_ACQUISITION
Specification
procedure STOP_ACQUISITION
(in ITEM: ACQUISITION_COLLECTION;
in ADU: ADU_NAME := \\;
out STATUS: UCL_RETURN)
Description / Parameters
Stops data acquisition on the local test node for the given enditems.
ITEM : individual enditem or group of enditems no longer to be acquired.
ADU (optional) : the ADU Descriptor to be applied. If only one ADU Descriptor is active for ITEM,
the parameter may be omitted. If more than one ADU Descriptor is defined and the parameter is
omitted, the command stops acquisition for all ADUs. If ITEM is already of type ADU_DESCRIPTION,
the parameter is ignored.
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
STOP_ACQUISITION (\apm\dms\link\statistics, stat);

Space Infrastructure
7.9.1.3.6.3 SEND_SIMULATED_ADU
Specification
procedure SEND_SIMULATED_ADU
(in ADU: ADU_NAME;
out STATUS: UCL_RETURN);
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
396 von/of: 662
Description / Parameters
Sends a specific ADU internally to the TES input buffers, in simulation mode. For example, triggers
sending or simulation of a non–cyclic ADU.
ADU : name of simulated packet to be sent.
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
SEND_SIMULATED_ADU (\apm\dms_scoe\ADU_3, stat);
7.9.1.3.6.4 WAIT_FOR_ADU
Specification
procedure WAIT_FOR_ADU
(in ADU: ADU_NAME;
out TIME_TAG: TIME;
out SEQUENCE_NUMBER: INTEGER;
out STATUS: UCL_RETURN);
Description / Parameters
Waits for an ADU to be supplied to this test node.
ADU : name of packet to be received.
TIME_TAG : returns the time tag from the received packet.
SEQUENCE_NUMBER : returns the current sequence number from the received packet.
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
WAIT_FOR_ADU
(\apm\dms\housekeeping\packet, the_time_tag, the_sequence_number, stat);

Space Infrastructure
7.9.1.3.6.5 SET_BITS_IN_SIMULATED_ADU
Specification
procedure SET_BITS_IN_SIMULATED_ADU
(in ADU: ADU_NAME;
in OFFSET: INTEGER;
in SIZE: BIT_COUNT;
in VALUE: BITSET;
out STATUS: UCL_RETURN);
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
397 von/of: 662
Description / Parameters
Modifies the bit–contents of a simulated ADU directly in simulation mode. The operation can only be
applied on unstructured ADUs or telemetry ADUs.
ADU : name of the ADU to be modified.
OFFSET : location in bits in this ADU where bits are to be modified.
SIZE : the number of bits to modify. The upper limit is 32 bits.
VALUE : the new value of the set of bits to be modified.
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
SET_BITS_IN_SIMULATED_ADU (\apm\dms\hk_packet_1, 1234, 3, [0,1,2], stat);
7.9.1.3.6.6 SET_SIMULATED_ENDITEM_VALUE
Specification
PROCEDURE SET_SIMULATED_ENDITEM_VALUE
(in ITEM: MONITOR_ITEM_NAME;
in BOOL_VALUE: BOOLEAN : = FALSE;
in INT_VALUE: INTEGER : = 0;
in BITSET_VALUE: BITSET : = {};
in REAL_VALUE: REAL : = 0.0;
in STR_VALUE: USER_MESSAGE : = ””;
out STATUS: UCL_RETURN);
Description / Parameters
Modifies the value of an enditem in simulated ADUs.
The operation can only be applied on measurements provided by structured ADUs.
ITEM : name of item to be modified.
Other parameters : To cope with the different data types a value can have, several parameters are
provided. By selecting the appropriate parameter, eg INT_VALUE: 7, the desired value is set. The
operation can only be applied on items provided by structured ADUs.
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
SET_SIMULATED_ENDITEM_VALUE
(\apm\dms\input_current, REAL_VALUE : 5.6, STATUS : stat);

Space Infrastructure
7.9.1.3.6.7 ROUTE_TO_SAS
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
398 von/of: 662
Specification
procedure ROUTE_TO_SAS
(in ITEM: ROUTE_SAS_ITEM_NAME ;
in SAS_NAME: APPLICATION_NAME;
in OLD_SAS_NAME: APPLICATION_NAME := NULL_APPLICATION_NAME;
out STATUS: UCL_RETURN);
Description / Parameters
Routes all items specified in ITEM which have an SAS Reference to the new SAS specified by
SAS_NAME. ITEMs must be in state ’not acquired’ if of type ADU_DESCRIPTION.
ITEM : The item to be re–defined in the local memory of the test node. ITEM can be
– a single enditem
– a incomplete pathname pointing to a virtual node, thus redefining all in that subtree of the types indicated
in the type ROUTE_SAS_ITEM_NAME;
– a GDU_DESCRIPTION_LIST list, thus enabling all items in that list.
SAS_NAME: The new short name of the SAS to be applied for ITEM.
The SAS must run on the local test node .
OLD_SAS_NAME: The old short name of the SAS.Only items specified in ITEM having a SAS Reference
matching this SAS name are changed .
If NULL_APPLICATION_NAME is given, all items specified in ITEM are changed.
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
ROUTE_TO_SAS (\apm\cc_bus1\tc, ”VTC_SAS”, ”SSMB_SAS”, stat);

Space Infrastructure
7.9.1.3.7 Event Handling
7.9.1.3.7.1 LOG
Specification
procedure LOG
(in MESSAGE: USER_MESSAGE;
out STATUS: UCL_RETURN);
Description / Parameters
Logs an event message to the test result database.
Logged events have group–code LOG and type–code MSG.
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
399 von/of: 662
MESSAGE : string of up to 255 characters containing the message to be logged.
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
LOG (”Captain’s log, stardate 1 January 2137”, stat);
7.9.1.3.7.2 USER_EVENT
Specification
procedure USER_EVENT
(in MESSAGE: USER_MESSAGE;
out STATUS: UCL_RETURN);
Description / Parameters
Logs an user event message to the test result database.
User events are special log event with the group–code UEVT and type–code MSG.
MESSAGE : string of up to 255 characters containing the message to be logged.
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
USER_EVENT (”Begin_of_Test”, stat);

Space Infrastructure
7.9.1.3.8 Engineering Value Logging
7.9.1.3.8.1 ENABLE_EVL
Specification
procedure ENABLE_EVL
(in ITEM: MONITOR_COLLECTION;
out STATUS: UCL_RETURN);
Description / Parameters
Enables engineering value logging (EVL).
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
400 von/of: 662
ITEM : name of enditem(s) to be enabled.
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
ENABLE_EVL (\apm\power_scoe\current_sensors, stat);
7.9.1.3.8.2 DISABLE_EVL
Specification
procedure DISABLE_EVL
(in ITEM: MONITOR_COLLECTION;
out STATUS: UCL_RETURN);
Description / Parameters
Disables engineering value logging. If the specified enditems are already disabled for EVL, has no
effect.
ITEM : name of enditem(s) to be enabled.
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
DISABLE_EVL (\apm\power_scoe\current_sensors, stat);

Space Infrastructure
7.9.1.3.9 Archiving
7.9.1.3.9.1 ENABLE_ARCHIVING
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
Specification
procedure ENABLE_ARCHIVING
(in CYCLE: DURATION: = DEFAULT_ARCH_FILE_OPEN_PERIOD;
out STATUS: UCL_RETURN);
Description / Parameters
Enables archiving; creates a new archive file.
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
401 von/of: 662
CYCLE : the time interval (1 minute to 24 hours exclusive) at which archive files are closed automatically.
If archiving is already enabled and the cycle time of this call differs from the cycle time specified
in the last call of this procedure, the current archive file is closed, and a new one is opened. Archiving
periodically closes the archive file using the new cycle time.
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
ENABLE_ARCHIVING( 45 [min], stat);
7.9.1.3.9.2 DISABLE_ARCHIVING
Specification
procedure DISABLE_ARCHIVING;
Description / Parameters
Stops archiving on the local test node. If archiving was enabled the current archive file is closed.
Example
DISABLE_ARCHIVING;
7.9.1.3.9.3 CLOSE_ARCHIVE
Specification
procedure CLOSE_ARCHIVE
(out CLOSE_TIME : TIME;
out STATUS: UCL_RETURN);
Description / Parameters
Closes the currently open archive file and opens a fresh one, provided archiving is enabled.
CLOSE_TIME : returns the local time the archive file was closed.
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
CLOSE_ARCHIVE (my_time_value, stat);

Space Infrastructure
7.9.1.3.10 User Input & Output
7.9.1.3.10.1 READ_MESSAGE_FROM_USER
Specification
procedure READ_MESSAGE_FROM_USER
(in PROMPT: USER_MESSAGE;
in WORKSTATION: NODE_NAME: = \\;
out USER_ENTRY: USER_MESSAGE;
out STATUS: UCL_RETURN);
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
402 von/of: 662
Description / Parameters
Reads a message from the user; issues a prompt and blocks until the user enters a message.
PROMPT : prompt string of up to 255 characters, on Workstation’s screen.
WORKSTATION (optional) : node to display the prompt; by default, the workstation that started this
GTAP.
USER_ENTRY : returns what the user enters in a 255 character string, padded with NULLs.
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
READ_MESSAGE_FROM_USER (”Continue?”, \apm\egse\test_ws\, buffer, stat);
7.9.1.3.10.2 WRITE_MESSAGE_TO_USER
Specification
procedure WRITE_MESSAGE_TO_USER
(in MESSAGE: USER_MESSAGE;
in WORKSTATION: NODE_NAME:=\\;
out STATUS: UCL_RETURN);
Description / Parameters
Sends a message to the user of a given workstation.
MESSAGE : message to be sent to user.
WORKSTATION (optional) : name of node to display message; by default the workstation where this
GTAP (or its ancestors) was started.
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
WRITE_MESSAGE_TO_USER (”STEP 3”, \apm\egse\test_ws, stat);

Space Infrastructure
7.9.1.3.10.3 READ_NUMBER_FROM_USER
Specification
procedure READ_NUMBER_FROM_USER
(in PROMPT_MESSAGE: USER_MESSAGE;
in WORKSTATION: NODE_NAME: = \\;
out USER_ENTRY: REAL;
out STATUS: UCL_RETURN);
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
403 von/of: 662
Description / Parameters
Reads a real number; issues a prompt and blocks until the user enters one at the workstation.
PROMPT : prompt string displayed on user’s screen, up to 255 characters.
WORKSTATION (optional) : the workstation to use; by default that started this GTAP (or one of its
ancestors).
USER_ENTRY : returns the number entered by the user.
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
READ_NUMBER_FROM_USER
(”Which Table ?”, \apm\egse\test_ws\, my_number, stat);

Space Infrastructure
7.9.1.3.11 Synoptic Display Control
7.9.1.3.11.1 DISPLAY_PICTURE
Specification
procedure DISPLAY_PICTURE
(in PICTURE: PICTURE_NAME;
in WORKSTATION: NODE_NAME := \\;
out ID: PICTURE_ID;
out STATUS: UCL_RETURN);
Description / Parameters
Displays a synoptic display on a specific workstation.
PICTURE : name of synoptic display.
WORKSTATION : name of node.
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
404 von/of: 662
WORKSTATION (optional): the work station to show the synoptic display: by default the work station
from which the command originates, directly or via a GTAP.
ID : returns identifier to be used by REMOVE_PICTURE when removing this synoptic display.
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
DISPLAY_PICTURE
(\apm\power\total_overview, \apm\egse\test_conductor\workstation,
my_synoptic_ID, stat);
7.9.1.3.11.2 REMOVE_PICTURE
Specification
procedure REMOVE_PICTURE
(in ID: PICTURE_ID;
in WORKSTATION: NODE_NAME := \\;
out STATUS: UCL_RETURN);
Description / Parameters
Remove a synoptic display from the screen of a specific workstation.
ID : the picture’s identifier, as returned from DISPLAY_PICTURE (section 7.9.1.3.11.1).
WORKSTATION (optional): the work station showing the synoptic display: by default the work station
from which the command originates, directly or via a GTAP.
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
REMOVE_PICTURE (my_synoptic_ID, \apm\egse\test_conductor\workstation, stat);

Space Infrastructure
7.9.1.3.12 UCL Code Reloading from MDB
7.9.1.3.12.1 LOAD_UCL
Specification
procedure LOAD_UCL
(in ITEM: UCL_ITEM_NAME;
out STATUS: UCL_RETURN);
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
405 von/of: 662
Description / Parameters
Loads the I–code of an AP or UCL User library into memory. This procedure can be used for two
purposes: Either to preload the i–code to speed up the start–up of the AP/USER_LIB or to reload an
AP/USER_LIB which has been recompiled in MDB and which has already been preloaded.
ITEM : the pathname of the item to be loaded.
RETURN_STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Example
LOAD_UCL (\apm\egse\emergency_ap, stat);
7.9.1.3.13 Test Node management
7.9.1.3.13.1 IS_LOCAL_NODE
Specification
function IS_LOCAL_NODE (in NODE : NODE_NAME) : BOOLEAN;
Description / Parameters
Returns TRUE if executed on the test node NODE, otherwise FALSE.
NODE : name of EGSE node
Example
BOOL := IS_LOCAL_NODE (\apm\egse\mtp);

Space Infrastructure
7.9.1.3.14 Conditions
7.9.1.3.14.1 ENABLE_CONDITIONS
Specification
procedure ENABLE_CONDITIONS
(in ITEM: ACQUISITION_COLLECTION;
out STATUS: UCL_RETURN);
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
406 von/of: 662
Description / Parameters
Enable condition for a specific measurement/software variable/derived value or for all enditems under
a virtual tree/CDU or for all enditems within a monitor list or for all measurements within an ADU.
Enables all conditions of the given enditems.
If acquisition is not enabled for ITEM, it will be automatically started
ITEM: The measurement(s) or software variable(s) carrying the conditions.
STATUS : the return status of the operation
–– OK : operation successfull
–– INVALID_TESTNODE_MODE : the test node is not in executing mode
–– INVALID_ITEM_NAME : ITEM is not managed locally
–– RUNTIME_ERROR : an unexpected error occurred
Example
ENABLE_CONDITIONS (\APM\mmu2, stat);
7.9.1.3.14.2 DISABLE_CONDITIONS
Specification
procedure DISABLE_CONDITIONS
(in ITEM: ACQUISITION_COLLECTION;
out STATUS: UCL_RETURN);
Description / Parameters
Disable condition(s) for a specific measurement/software variable/derived value or for all enditems
under a virtual tree/CDU or for all enditems within a monitor list or for all measurements within an ADU.
Disables all conditions of the given enditems
When disabled, the conditions are still existing, and may be re–enabled via Enable_Conditions
ITEM: The measurement(s) or software variable(s) carrying the condition.
STATUS : the return status of the operation
–– OK : operation successfull
–– INVALID_TESTNODE_MODE : the test node is not in executing mode
–– INVALID_ITEM_NAME : ITEM is not managed locally
–– RUNTIME_ERROR : an unexpected error occurred
Example
DISABLE_CONDITIONS (\APM\mmu2, stat);

Space Infrastructure
7.9.1.3.14.3 ENABLE_ON_INTEGER
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
Specification
procedure ENABLE_ON_INTEGER
(in ITEM : ACQUISITION_COLLECTION;
in CONDITION_ITEM : INTEGER_MONITOR_ITEM_NAME;
in CONDITION_CHECK : CONDITION;
in CONDITION_VALUE : INTEGER;
in SINGLE_SHOT : BOOLEAN;
out CONDITION_REF : INTEGER;
out STATUS : UCL_RETURN);
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
407 von/of: 662
Description / Parameters
Enables the processing of ITEM (measurement, software variable, monitoring list or measurements
of a subtree) when the CONDITION_CHECK of the value of CONDITION_ITEM with
CONDITION_VALUE is true (the condition is true).
If the condition is false, this will disable the processing of ITEM.
By default, all enditems are enabled for processing. Conditions can be defined to disable and
re–enable the processing of given end–items.
When the processing is enabled, ITEM will be authorised for calibration and monitoring. After ITEM
has been enabled, it will be calibrated (if its acquisition has been started) and monitored (if its
monitoring has been enabled) on reception of new values.
Enabling the processing of ITEM does not perform an ”initial” calibration / monitoring of ITEM in the
case where it has already a value.
When the processing is disabled, ITEM will not be calibrated and not be monitored, even if its
acquisition has been requested and if its monitoring is enabled.
CONDITION_ITEM must be maintained locally otherwise an error is generated.
When the condition is triggered, only those measurements and SW variables identified by ITEM that
are maintained locally will be processed.
It is not possible to set a condition where the ITEM to enable or disable is the CONDITION_ITEM. If
ITEM is a group of enditems (i.e. monitoring list, ADU or incomplete pathname) containing
CONDITION_ITEM, the condition will not apply for CONDITION_ITEM.
It is not possible to enable or disable the processing of a SW variable that is linked to an HK data.
ITEM : The item to be enabled, which can be
– a single enditem of type MEASUREMENT or SW variable;
– a incomplete pathname pointing to a virtual node, thus enabling all MEASUREMENTs or SW variables
in that subtree;

Space Infrastructure
– a monitor list, thus enabling all items in that list.
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
CONDITION_ITEM: The measurement or software variable carrying the condition
Only enditems having value type INTEGER are allowed
CONDITION_CHECK : the check to apply on CONDITION_ITEM.
CONDITION_VALUE : the value to use in the check with CONDITION_ITEM.
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
408 von/of: 662
SINGLE_SHOT : if true, the condition will be withdrawn after having been true.
CONDITION_REF : returns an unique identifier for the condition
STATUS : the return status of the operation
–– OK : operation successfull
–– INVALID_TESTNODE_MODE : the test node is not in executing mode
–– INVALID_ITEM_NAME : CONDITION_ITEM is not managed locally
–– INVALID_PARAMETER : ITEM and CONDITION_ITEM are identical
–– or ITEM is a SW variable linked to an HK data.
–– or CONDITION_CHECK is IN_RANGE (not supported)
–– RUNTIME_ERROR : an unexpected error occurred
Example
ENABLE_ON_INTEGER (\apm\dms\mmu_2, \apm\dms\mmu_number, EQUAL, 2, false, c_ref, stat);
7.9.1.3.14.4 ENABLE_ON_FLOAT
Specification
procedure ENABLE_ON_FLOAT
(in ITEM : ACQUISITION_COLLECTION;
in CONDITION_ITEM : FLOAT_MONITOR_ITEM_NAME;
in CONDITION_CHECK : CONDITION;
in CONDITION_VALUE : REAL;
in SINGLE_SHOT : BOOLEAN;
out CONDITION_REF : INTEGER;
out STATUS : UCL_RETURN);
Description / Parameters
Enables processing on conditions for float values;
Refer to analog description in ENABLE_ON_INTEGER
ITEM : Refer to analog description in ENABLE_ON_INTEGER;
CONDITION_ITEM: The measurement or software variable carrying the condition.
Only enditems having value type REAL are allowed
CONDITION_CHECK : the check to apply on CONDITION_ITEM.
CONDITION_VALUE : the value to use in the check with CONDITION_ITEM.
SINGLE_SHOT : if true, the condition will be withdrawn after having been true.
CONDITION_REF : returns an unique identifier for the condition
STATUS : the return status of the operation
–– OK : operation successfull

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
409 von/of: 662
–– INVALID_TESTNODE_MODE : the test node is not in executing mode
–– INVALID_ITEM_NAME : CONDITION_ITEM is not managed locally
–– INVALID_PARAMETER : ITEM and CONDITION_ITEM are identical
–– or ITEM is a SW variable linked to an HK data.
–– or CONDITION_CHECK is IN_RANGE (not supported)
–– RUNTIME_ERROR : an unexpected error occurred
Example
ENABLE_ON_FLOAT (\apm\dms\fire, \apm\dms\smoke_sensor, GREATER, 100.0, false, c_ref, stat);
7.9.1.3.14.5 ENABLE_ON_STATECODE
Specification
procedure ENABLE_ON_STATECODE
(in ITEM : ACQUISITION_COLLECTION;
in CONDITION_ITEM : DISCRETE_MONITOR_ITEM_NAME;
in CONDITION_CHECK : DISCRETE_CONDITION;
in CONDITION_VALUE : STATECODE;
in SINGLE_SHOT : BOOLEAN;
out CONDITION_REF : INTEGER;
out STATUS : UCL_RETURN);
Description / Parameters
Enables processing on conditions for discrete values;
Refer to analog description in ENABLE_ON_INTEGER
ITEM : Refer to analog description in ENABLE_ON_INTEGER;
CONDITION_ITEM: The measurement or software variable carrying the condition.
Only discrete enditems having value type STATECODE are allowed
CONDITION_CHECK : the check to apply on CONDITION_ITEM.
CONDITION_VALUE : the value to use in the check with CONDITION_ITEM.
SINGLE_SHOT : if true, the condition will be withdrawn after having been true.
CONDITION_REF : returns an unique identifier for the condition

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
STATUS : the return status of the operation
–– OK : operation successfull
–– INVALID_TESTNODE_MODE : the test node is not in executing mode
–– INVALID_ITEM_NAME : CONDITION_ITEM is not managed locally
–– INVALID_PARAMETER : ITEM and CONDITION_ITEM are identical
–– or ITEM is a SW variable linked to an HK data
–– RUNTIME_ERROR : an unexpected error occurred
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
410 von/of: 662
Example
ENABLE_ON_STATECODE (\apm\dms\mmu_2, \apm\dms\mmu2_state, EQUAL, ON, false, c_ref, stat);
7.9.1.3.14.6 ENABLE_ON_BYTE_STREAM
Specification
procedure ENABLE_ON_BYTE_STREAM
(in ITEM : ACQUISITION_COLLECTION;
in CONDITION_ITEM : BYTE_STREAM_MONITOR_ITEM_NAME;
in CONDITION_CHECK : DISCRETE_CONDITION;
in CONDITION_VALUE : STRING;
in SINGLE_SHOT : BOOLEAN;
out CONDITION_REF : INTEGER;
out STATUS : UCL_RETURN);
Description / Parameters
Enables processing on conditions for bytestream (string) values;
Refer to analog description in ENABLE_ON_INTEGER
ITEM : Refer to analog description in ENABLE_ON_INTEGER;
CONDITION_ITEM: The measurement or software variable carrying the condition.
Only enditems having raw value type BYTE_STREAM are allowed
CONDITION_CHECK : the check to apply on CONDITION_ITEM.
CONDITION_VALUE : the value to use in the check with CONDITION_ITEM.
SINGLE_SHOT : if true, the condition will be withdrawn after having been true.
CONDITION_REF : returns an unique identifier for the condition
STATUS : the return status of the operation
–– OK : operation successfull
–– INVALID_TESTNODE_MODE : the test node is not in executing mode
–– INVALID_ITEM_NAME : CONDITION_ITEM is not managed locally
–– INVALID_PARAMETER : ITEM and CONDITION_ITEM are identical
–– or ITEM is a SW variable linked to an HK data
–– RUNTIME_ERROR : an unexpected error occurred
Example
ENABLE_ON_BYTE_STREAM (\apm\dms\activation, \apm\dms\ap_name, equal, ”activation”, true, c_ref,
stat);

Space Infrastructure
7.9.1.3.14.7 SET_PROCESSING
Specification
procedure SET_PROCESSING
(in ITEM : ACQUISITION_COLLECTION;
in SWITCH : ON_OFF;
out STATUS : UCL_RETURN);
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
Description / Parameters
Enables or disables processing for enditems, overriding any conditions defined.
ITEM : Refer to analog description in ENABLE_ON_INTEGER;
SWITCH : ON to enable the processing and OFF to disable the processing.
STATUS : the return status of the operation
–– OK : operation successfull
–– INVALID_TESTNODE_MODE : the test node is not in executing mode
–– INVALID_ITEM_NAME : ITEM is not managed locally
–– INVALID_PARAMETER : ITEM is a SW variable linked to an HK data.
–– RUNTIME_ERROR : an unexpected error occurred
Example
SET_PROCESSING (\apm\dms\mmu_2, OFF, stat);
7.9.1.3.14.8 GET_PROCESSING
Specification
procedure GET_PROCESSING_STATE
(in ITEM : MONITOR_ITEM_NAME;
out STATE : ON_OFF;
out STATUS : UCL_RETURN);
Description / Parameters
Fetches the status of processing (enabled, disabled) for an enditem
ITEM : A single measurement or software variable
STATE : ON if enabled for processing and OFF if disabled for processing.
STATUS : the return status of the operation
–– OK : operation successfull
–– INVALID_TESTNODE_MODE : the test node is not in executing mode
–– INVALID_ITEM_NAME : ITEM is not managed locally
–– RUNTIME_ERROR : an unexpected error occurred
Example
GET_PROCESSING_STATE (\apm\dms\mmu_2, proc_state, stat);
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
411 von/of: 662

Space Infrastructure
7.9.1.3.14.9 SET_LIMIT_SET_ON_INTEGER
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
Specification
procedure SET_LIMIT_SET_ON_INTEGER
(in ITEM : MONITOR_COLLECTION;
in LIMIT_SET : LIMIT_SET_NUMBER;
in CONDITION_ITEM : INTEGER_MONITOR_ITEM_NAME;
in CONDITION_CHECK : CONDITION;
in CONDITION_VALUE : INTEGER;
in SINGLE_SHOT : BOOLEAN;
out CONDITION_REF : INTEGER;
out STATUS : UCL_RETURN);
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
412 von/of: 662
Description / Parameters
Sets the LIMIT_SET for ITEM (measurement or software variable) when the CONDITION_CHECK of
the value of CONDITION_ITEM with CONDITION_VALUE is true (the condition is true).
It will not perform an ”initial” monitoring of ITEM in the case where it has already a value. The
monitoring will be performed on reception of the next value (in case the monitoring has been enabled).
This can lead to a temporary ”inconsistent” output of the procedure GET_FULL_ENDITEM_MON-
ITOR_STATUS (result of the monitoring with the old limit set with values of the new limit set might be
inconsistent).
ITEM and CONDITION_ITEM must be maintained locally on the same node otherwise an error is
generated.It is not possible to set a condition where the ITEM identical to the CONDITION_ITEM.
In case a set of items is addressed, the limit set is switched to LIMIT_SET only, if the limit set is defined.
No error message is given for undefined sets.
ITEM : A single measurement or software variable, a monitor list or a virtual path.
LIMIT_SET : The limit set number to select.
The LIMIT_SET must be defined for ITEM, otherwise an error is generated
CONDITION_ITEM: The measurement or software variable carrying the condition.
Only enditems having value type INTEGER are allowed
CONDITION_CHECK : the check to apply on CONDITION_ITEM.
CONDITION_VALUE : the value to use in the check with CONDITION_ITEM.
SINGLE_SHOT : if true, the condition will be withdrawn after having been true.
CONDITION_REF : returns an unique identifier for the condition
STATUS : the return status of the operation
–– OK : operation successfull
–– INVALID_TESTNODE_MODE : the test node is not in executing mode
–– INVALID_ITEM_NAME : ITEM or CONDITION_ITEM are not managed locally
–– INVALID_PARAMETER : ITEM and CONDITION_ITEM are identical
–– or CONDITION_CHECK is IN_RANGE (not supported)
–– INVALID_LIMIT_SET : the limit set is not defined for ITEM
–– RUNTIME_ERROR : an unexpected error occurred
Example
SET_LIMIT_SET_ON_INTEGER (\apm\dms\mmu_status,5, \apm\dms\mmu, equal, 2, true, c_ref, stat);

Space Infrastructure
7.9.1.3.14.10 SET_LIMIT_SET_ON_FLOAT
Specification
procedure SET_LIMIT_SET_ON_FLOAT
(in ITEM : MONITOR_COLLECTION;
in LIMIT_SET : LIMIT_SET_NUMBER;
in CONDITION_ITEM : FLOAT_MONITOR_ITEM_NAME;
in CONDITION_CHECK : CONDITION;
in CONDITION_VALUE : REAL;
in SINGLE_SHOT : BOOLEAN;
out CONDITION_REF : INTEGER;
out STATUS : UCL_RETURN);
Description / Parameters
Set a limit set on conditions for float values;
Refer to analog description in SET_LIMIT_SET_ON_INTEGER
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
413 von/of: 662
ITEM : A single measurement or software variable, a monitor list or a virtual path.
In case a set of items is addressed, the limit set is switched to LIMIT_SET only
if the limit set is defined. No error message is given for undefined sets.
LIMIT_SET : The limit set number to select.
The LIMIT_SET must be defined for ITEM
CONDITION_ITEM: The measurement or software variable carrying the condition.
Only enditems having value type REAL are allowed
CONDITION_CHECK : the check to apply on CONDITION_ITEM.
CONDITION_VALUE : the value to use in the check with CONDITION_ITEM.
SINGLE_SHOT : if true, the condition will be withdrawn after having been true.
CONDITION_REF : returns an unique identifier for the condition
STATUS : the return status of the operation
–– OK : operation successfull
–– INVALID_TESTNODE_MODE : the test node is not in executing mode
–– INVALID_ITEM_NAME : ITEM or CONDITION_ITEM are not managed locally
–– INVALID_PARAMETER : ITEM and CONDITION_ITEM are identical
–– or CONDITION_CHECK is IN_RANGE (not supported)
–– INVALID_LIMIT_SET : the limit set is not defined for ITEM
–– RUNTIME_ERROR : an unexpected error occurred
Example
SET_LIMIT_SET_ON_FLOAT (\apm\dms\temp,5, \apm\dms\temp, greater, 25.0, true, c_ref, stat);

Space Infrastructure
7.9.1.3.14.11 SET_LIMIT_SET_ON_STATECODE
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
Specification
procedure SET_LIMIT_SET_ON_STATECODE
(in ITEM : MONITOR_COLLECTION;
in LIMIT_SET : LIMIT_SET_NUMBER;
in CONDITION_ITEM : DISCRETE_MONITOR_ITEM_NAME;
in CONDITION_CHECK : DISCRETE_CONDITION;
in CONDITION_VALUE : STATECODE;
in SINGLE_SHOT : BOOLEAN;
out CONDITION_REF : INTEGER;
out STATUS : UCL_RETURN);
Description / Parameters
Set a limit set on conditions for statecode values;
Refer to analog description in SET_LIMIT_SET_ON_INTEGER
ITEM : A single measurement or software variable, a monitor list or a virtual path.
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
414 von/of: 662
LIMIT_SET : The limit set number to select.
The LIMIT_SET must be defined for ITEM
CONDITION_ITEM: The measurement or software variable carrying the condition.
Only discrete enditems having value type STATECODE are allowed
CONDITION_CHECK : the check to apply on CONDITION_ITEM.
CONDITION_VALUE : the value to use in the check with CONDITION_ITEM.
SINGLE_SHOT : if true, the condition will be withdrawn after having been true.
CONDITION_REF : returns an unique identifier for the condition
STATUS : the return status of the operation
–– OK : operation successfull
–– INVALID_TESTNODE_MODE : the test node is not in executing mode
–– INVALID_ITEM_NAME : ITEM or CONDITION_ITEM are not managed locally
–– INVALID_PARAMETER : ITEM and CONDITION_ITEM are identical
–– INVALID_LIMIT_SET : the limit set is not defined for ITEM
–– RUNTIME_ERROR : an unexpected error occurred
Example
SET_LIMIT_SET_ON_STATECODE (\apm\dms\temp,5, \apm\dms\status, equal, ”heating”, true, c_ref, stat);

Space Infrastructure
7.9.1.3.14.12 SET_LIMIT_SET_ON_BYTESTREAM
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
Specification
procedure SET_LIMIT_SET_ON_BYTE_STREAM
(in ITEM : MONITOR_COLLECTION;
in LIMIT_SET : LIMIT_SET_NUMBER;
in CONDITION_ITEM : BYTE_STREAM_MONITOR_ITEM_NAME;
in CONDITION_CHECK : DISCRETE_CONDITION;
in CONDITION_VALUE : STRING;
in SINGLE_SHOT : BOOLEAN;
out CONDITION_REF : INTEGER;
out STATUS : UCL_RETURN);
Description / Parameters
Set a limit set on conditions for byte stream values;
Refer to analog description in SET_LIMIT_SET_ON_INTEGER
ITEM : A single measurement or software variable, a monitor list or a virtual path.
LIMIT_SET : The limit set number to select.
The LIMIT_SET must be defined for ITEM
CONDITION_ITEM: The measurement or software variable carrying the condition.
Only enditems having raw value type BYTE_STREAM
(engineering value type STRING) are allowed
CONDITION_CHECK : the check to apply on CONDITION_ITEM.
CONDITION_VALUE : the value to use in the check with CONDITION_ITEM.
SINGLE_SHOT : if true, the condition will be withdrawn after having been true.
CONDITION_REF : returns an unique identifier for the condition
STATUS : the return status of the operation
–– OK : operation successfull
–– INVALID_TESTNODE_MODE : the test node is not in executing mode
–– INVALID_ITEM_NAME : ITEM or CONDITION_ITEM are not managed locally
–– INVALID_PARAMETER : ITEM and CONDITION_ITEM are identical
–– INVALID_LIMIT_SET : the limit set is not defined for ITEM
–– RUNTIME_ERROR : an unexpected error occurred
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
415 von/of: 662
Example
SET_LIMIT_SET_ON_BYTE_STREAM (\apm\dms\temp,2, \apm\dms\ap_name, equal, ”deactiv”, true,
c_ref, stat);

Space Infrastructure
7.9.1.3.14.13 START_AP_ON_INTEGER
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
Specification
procedure START_AP_ON_INTEGER
(in AP : AP_NAME;
in CONDITION_ITEM : INTEGER_MONITOR_ITEM_NAME;
in CONDITION_CHECK : CONDITION;
in CONDITION_VALUE : INTEGER;
in SINGLE_SHOT : BOOLEAN;
out CONDITION_REF : INTEGER;
out STATUS : UCL_RETURN);
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
416 von/of: 662
Description / Parameters
Starts an automated procedure when the CONDITION_CHECK of the value of CONDITION_ITEM
with CONDITION_VALUE is true (the condition is true).
CONDITION_ITEM must be maintained locally on the node otherwise an error is generated.
The AP to start must be an AP without parameters, otherwise an error message is generated when the
condition is triggered.
When the condition is triggered, if the AP is already running, it will not be started and an error message
will be generated.
AP : the name of the automated procedure to start. This must be an AP without parameter
or where all parameters have default values.
CONDITION_ITEM: The measurement or software variable carrying the condition
Only enditems having value type INTEGER are allowed
CONDITION_CHECK : the check to apply on CONDITION_ITEM.
CONDITION_VALUE : the value to use in the check with CONDITION_ITEM.
SINGLE_SHOT : if true, the condition will be withdrawn after having been true.
CONDITION_REF : returns an unique identifier for the condition
STATUS : the return status of the operation
–– OK : operation successfull
–– INVALID_TESTNODE_MODE : the test node is not in executing mode
–– INVALID_ITEM_NAME : CONDITION_ITEM is not managed locally
–– INVALID_PARAMETER : CONDITION_CHECK is IN_RANGE (not supported)
–– RUNTIME_ERROR : an unexpected error occurred
Example
START_AP_ON_INTEGER (\announce_mmu_2, \apm\dms\mmu_number, EQUAL, 2, true, c_ref, stat);

Space Infrastructure
7.9.1.3.14.14 START_AP_ON_FLOAT
Specification
procedure START_AP_ON_INTEGER
(in AP : AP_NAME;
in CONDITION_ITEM : FLOAT_MONITOR_ITEM_NAME;
in CONDITION_CHECK : CONDITION;
in CONDITION_VALUE : REAL;
in SINGLE_SHOT : BOOLEAN;
out CONDITION_REF : INTEGER;
out STATUS : UCL_RETURN);
Description / Parameters
Starts an AP on conditions for float values;
Refer to analog description in START_AP_ON_INTEGER
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
417 von/of: 662
AP : the name of the automated procedure to start. This must be an AP without parameter
or where all parameters have default values.
CONDITION_ITEM: The measurement or software variable carrying the condition
Only enditems having value type REAL are allowed
CONDITION_CHECK : the check to apply on CONDITION_ITEM.
CONDITION_VALUE : the value to use in the check with CONDITION_ITEM.
SINGLE_SHOT : if true, the condition will be withdrawn after having been true.
CONDITION_REF : returns an unique identifier for the condition
STATUS : the return status of the operation
–– OK : operation successfull
–– INVALID_TESTNODE_MODE : the test node is not in executing mode
–– INVALID_ITEM_NAME : CONDITION_ITEM is not managed locally
–– INVALID_PARAMETER : CONDITION_CHECK is IN_RANGE (not supported)
–– RUNTIME_ERROR : an unexpected error occurred
Example
START_AP_ON_FLOAT (\switchoff_mmu2, \apm\dms\mmu_temp, GREATER, 35.0, false, c_ref, stat);

Space Infrastructure
7.9.1.3.14.15 START_AP_ON_STATECODE
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
Specification
procedure START_AP_ON_STATECODE
(in AP : AP_NAME;
in CONDITION_ITEM : DISCRETE_MONITOR_ITEM_NAME;
in CONDITION_CHECK : DISCRETE_CONDITION;
in CONDITION_VALUE : STATECODE;
in SINGLE_SHOT : BOOLEAN;
out CONDITION_REF : INTEGER;
out STATUS : UCL_RETURN);
Description / Parameters
Starts an AP on conditions for statecode values;
Refer to analog description in START_AP_ON_INTEGER
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
418 von/of: 662
AP : the name of the automated procedure to start. This must be an AP without parameter
or where all parameters have default values.
CONDITION_ITEM: The measurement or software variable carrying the condition
Only enditems having value type STATECODE are allowed
CONDITION_CHECK : the check to apply on CONDITION_ITEM.
CONDITION_VALUE : the value to use in the check with CONDITION_ITEM.
SINGLE_SHOT : if true, the condition will be withdrawn after having been true.
CONDITION_REF : returns an unique identifier for the condition
STATUS : the return status of the operation
–– OK : operation successfull
–– INVALID_TESTNODE_MODE : the test node is not in executing mode
–– INVALID_ITEM_NAME : CONDITION_ITEM is not managed locally
–– RUNTIME_ERROR : an unexpected error occurred
Example
START_AP_ON_STATECODE (\switchoff_mmu2, \apm\dms\power_stat, EQUAL, ”LOW”, false, c_ref,
stat);

Space Infrastructure
7.9.1.3.14.16 START_AP_ON_BYTE_STREAM
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
Specification
procedure START_AP_ON_BYTE_STREAM
(in AP : AP_NAME;
in CONDITION_ITEM : BYTE_STREAM_MONITOR_ITEM_NAME;
in CONDITION_CHECK : DISCRETE_CONDITION;
in CONDITION_VALUE : STRING;
in SINGLE_SHOT : BOOLEAN;
out CONDITION_REF : INTEGER;
out STATUS : UCL_RETURN);
Description / Parameters
Starts an AP on conditions for byte stream values;
Refer to analog description in START_AP_ON_INTEGER
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
419 von/of: 662
AP : the name of the automated procedure to start. This must be an AP without parameter
or where all parameters have default values.
CONDITION_ITEM: The measurement or software variable carrying the condition
Only enditems having value type STRING (raw type: BYTE_STREAM)
are allowed
CONDITION_CHECK : the check to apply on CONDITION_ITEM.
CONDITION_VALUE : the value to use in the check with CONDITION_ITEM.
SINGLE_SHOT : if true, the condition will be withdrawn after having been true.
CONDITION_REF : returns an unique identifier for the condition
STATUS : the return status of the operation
–– OK : operation successfull
–– INVALID_TESTNODE_MODE : the test node is not in executing mode
–– INVALID_ITEM_NAME : CONDITION_ITEM is not managed locally
–– RUNTIME_ERROR : an unexpected error occurred
Example
START_AP_ON_BYTE_STREAM (\switchoff_mmu2, \apm\dms\mmu_use, EQUAL, ”is not used”, false,
c_ref, stat);

Space Infrastructure
7.9.1.3.14.17 WITHDRAW_CONDITION
Specification
procedure WITHDRAW_CONDITION
(in CONDITION_ITEM : MONITOR_ITEM_NAME;
in CONDITION_REF : INTEGER := ALL_CONDITIONS;
out STATUS : UCL_RETURN);
Description / Parameters
Removes a condition or all conditions of a CONDITION_ITEM.
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
420 von/of: 662
CONDITION_ITEM: The measurement or software variable carrying the condition
CONDITION_REF : The unique identifier for the condition. If ALL_CONDITIONS is given, all conditions
defined for CONDITION_ITEM are removed.
STATUS : the return status of the operation
–– OK : operation successfull
–– INVALID_TESTNODE_MODE : the test node is not in executing mode
–– INVALID_ITEM_NAME : CONDITION_ITEM is not managed locally or
–– CONDITION_REF does not identify an existing condition
–– RUNTIME_ERROR : an unexpected error occurred
Example
WITHDRAW_CONDITION (\apm\dms\mmu_use, 125, stat);
7.9.1.3.14.18 WITHDRAW_ALL_CONDITIONS
Specification
procedure WITHDRAW_ALL_CONDITIONS
(out STATUS : UCL_RETURN);
Description / Parameters
Removes all conditions defined in the local test node.
STATUS : the return status of the operation
–– OK : operation successfull
–– INVALID_TESTNODE_MODE : the test node is not in executing mode
–– RUNTIME_ERROR : an unexpected error occurred
Example
WITHDRAW_ALL_CONDITIONS (stat);
7.9.1.3.14.19 NUMBER_OF_CONDITION_ITEMS
Specification
function NUMBER_OF_CONDITION_ITEMS : INTEGER;
Description / Parameters
Returns the number of items carrying conditions.
Example
NB_CONDITIONS := NUMBER_OF_CONDITION_ITEMS;

Space Infrastructure
7.9.1.3.14.20 GET_CONDITION_ITEM
Specification
procedure GET_CONDITION_ITEM
(in ITEM_NUMBER : INTEGER;
out CONDITION_ITEM : MONITOR_ITEM_NAME;
out STATUS : UCL_RETURN);
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
421 von/of: 662
Description / Parameters
Gets the name of the CONDITION_ITEM identified by an index.
To get all the CONDITION_ITEM’s, this procedure has to be called with all numbers between 1 and
the value of NUMBER_OF_CONDITION_ITEMS.
ITEM_NUMBER : index of the CONDITION_ITEM
CONDITION_ITEM : the measurement or software variable carrying the condition.
STATUS : the return status of the operation
–– OK : operation successfull
–– INVALID_TESTNODE_MODE : the test node is not in executing mode
–– INVALID_PARAMETER : There is no CONDITION_ITEM at the index ITEM_NUMBER
–– RUNTIME_ERROR : an unexpected error occurred
Example
for ITEM_NUMBER := 1 to NUMBER_OF_CONDITION_ITEMS do
GET_CONDITION_ITEM(ITEM_NUMBER, PATHNAME_ARRAY(ITEM_NUMBER),STAT);
end for;
7.9.1.3.14.21 NUMBER_CONDITIONS
Specification
function NUMBER_CONDITIONS
(in CONDITION_ITEM : MONITOR_ITEM_NAME): INTEGER;
Description / Parameters
Returns the number of conditions carried by a CONDITION_ITEM. if CONDITION_ITEM is not
maintained locally, 0 is returned
Example
NB_CONDITIONS := NUMBER_CONDITIONS(\apm\dms\mmu_2_status);

Space Infrastructure
7.9.1.3.14.22 GET_CONDITION
Specification
procedure GET_CONDITION
(in CONDITION_ITEM : MONITOR_ITEM_NAME;
in CONDITION_NUMBER : INTEGER;
out CONDITION_REF : INTEGER;
out CONDITION_CHECK : CONDITION;
out CONDITION_VALUE : CONDITION_VAL;
out SINGLE_SHOT : BOOLEAN;
out STATE : CONDITION_STATE;
out ACTION : ACTION_DESCRIPTION;
out STATUS : UCL_RETURN);
Description / Parameters
Provide the description of a condition.
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
CONDITION_ITEM : the name of the item carrying the condition.
CONDITION_NUMBER : the index of the condition (between 1 and the value
of GET_NUMBER_CONDITIONS).
CONDITION_REF : the unique identifier of the condition.
CONDITION_CHECK : the check to apply on CONDITION_ITEM.
CONDITION_VALUE : the value to use in the check with CONDITION_ITEM.
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
422 von/of: 662
SINGLE_SHOT : indicates if the condition is to be removed after having been true.
STATE : indicates the state of the condition. It can be
– IS_TRUE : the condition is true, the associated action has been triggered
– IS_FALSE : the condition is false, the associated action has been triggered (only for the enable/disable
conditions)
– IS_UNKNOWN : the condition has been set but has not yet been analysed (CONDITION_ITEM
has not a valid value)
ACTION : provide the description of the condition, i.e:
– the sid of the item(s) for which the processing is to be enabled
– the sid of the item for which a new limit set is to be set and the limit set number
– the sid of an AP
STATUS : the return status of the operation
–– OK : operation successfull
–– INVALID_TESTNODE_MODE : the test node is not in executing mode
–– INVALID_PARAMETER : There is no (more) condition at the index
–– CONDITION_NUMBER (see above note).
–– INVALID_ITEM_NAME : CONDITION_ITEM is not managed locally.
–– RUNTIME_ERROR : an unexpected error occurred
Example
GET_CONDITION(\apm\dms\mmu_stat,2,c_ref,c_check,c_value,single,action,stat);

Space Infrastructure
7.9.1.3.15 General Conversion Routines
7.9.1.3.15.1 PATHNAME_TO_STRING
Specification
procedure PATHNAME_TO_STRING
(in PATH : PATHNAME;
out NAME: STRING);
Description / Parameters
Convert the pathname type into a string type
PATH : the pathname to be converted.
NAME : the pathname returned as a string
If PATH is not existing, an empty string is returned
If NAME is too short to hold resulting string, the string is truncated
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
Example
VARIABLE NAME_STRING : STRING(255);
VARIABLE STATUS: INTEGER;
PATHNAME_TO_STRING(\EURECA\EGSE\TEST\LIBS\SAS_ITEM, NAME_STRING);
WRITE_MESSAGE_TO_APPLICATION (1234, NAME_STRING, STATUS);
7.9.1.3.15.2 PATH
Specification
function PATH(in NAME: STRING) : PATHNAME;
Description / Parameters
Convert the string type into a pathname type
NAME : the pathname as a string
returns Null–Pathname in case the path is not existing
Example
VARIABLE NAME_STRING : STRING(255);
VARIABLE SAS_PATH: PATHNAME;
VARIABLE STATUS: INTEGER;
READ_MESSAGE_FROM_APPLICATION (TRUE, 1234, NAME_STRING, STATUS);
SAS_PATH := PATH( NAME_STRING);
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
423 von/of: 662

Space Infrastructure
7.9.1.3.15.3 STATE_CODE_TO_STRING
Specification
procedure STATECODE_TO_STRING (in CODE : STATECODE;
out CODE_TEXT: STRING);
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
Description / Parameters
Convert the statecode type into a string type
CODE_TEXT should have a length of 8
If CODE_TEXT is too short to hold resulting string, the string is truncated
If CODE_TEXT is longer than the statecode, it is filled with blanks
CODE : the statecode
returns Null–Pathname in case the path is not existing
CODE_TEXT : the statecode as a string (without ”$” as prefix)
Example
VARIABLE CODE_STRING : STRING(8);
STATECODE_TO_STRING( $OFF, CODE_STRING);
7.9.1.3.15.4 CODE
Specification
function CODE(in CODE_TEXT : STRING) : STATECODE;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
424 von/of: 662
Description / Parameters
Convert the string type into a statecode type
If CODE_TEXT is longer than 8 characters, the string is truncated
If CODE_TEXT is invalid in term of a STATECODE, the statecode returned is either an ”empty”
startecode (i.e. has no characters) if the first character is invalid or a statecode corresponding to the
CODE_TEXT truncated at the first illegal character.
If CODE_TEXT is shorter than 8 characters, the STATECODE is extended by blanks
CODE_TEXT : the statecode (without ”$”) as a string;
Example
VARIABLE S_CODE : STATECODE;
S_CODE := CODE( ”OFF”);

Space Infrastructure
7.9.2 UCL GROUND_TO_OB_LIB System Library
This library contains commands sent to the COF DMS system.
Library Id (Body_Id): 4
7.9.2.1 Routines Summary
DISABLE_SW_COMMAND
ENABLE_SW_COMMAND
EXECUTE_FLAP
EXECWAIT_FLAP
ISSUE_SW_COMMAND
ROUTE_SWOP_TO_SAS
SET_CCSDS_END_POINT
SET_DEVICE_ADDRESS
GET_CCSDS_PACKET_TYPE
SET_CCSDS_PACKET_TYPE
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
7.9.2.2 UCL GROUND_TO_OB_LIB System Library Specification
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
425 von/of: 662
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
––*******************************************
–– GROUND_TO_OB_LIB System Library
––*******************************************
––ABSTRACT––
–– Defines Procedures to send commands to the onboard system
–– Must be compiled with body ID = 4
––
––IDENTIFICATION––
–– PROJECT NAME : CGS
–– OBJECT NAME : GROUND_TO_OB_LIB System Library
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––CONTENTS––
–– COMPILER : UCLC
–– LANGUAGE : UCL
––CHANGE HISTORY
–– PIRN 8101 1/A: provide max_data_length and received_data_length for
–– issue_sw_command; new UCL_RETURN RESPONSE_TOO_SHORT
–– (SPRs 7288. Cleanup of inconsistencies in return codes in
–– ISSUE_SW_COMMAND, EXECUTE_FLAP and EXECWAIT_FLAP.
–– new UCL_RETURN RESPONSE_TIMEOUT.
–– add operations to set/get the packet type.
–– change library name to GROUND_TO_OB_LIB (SPR–7826)
–– PIRN 8011 1/A: provide operation ROUTE_SWOP_TO SAS to set the SAS for an
–– SW Command or the response packet.
–– PIRN 8011 1/–: provide operation to set the DEVICE_ADDRESS for an
–– APPLICATION_ID identified by the source and destination.
–– PIRN 7004 for CGS V4.1.0: Add ENABLE/DISABLE_SW_COMMAND
–– Add Ground_Node parameter to

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
426 von/of: 662
–– ISSUE_SW_COMMAND and EXEC..._FLAP
–– Add new return stati
–– Add onboard_execution node, onb_priority,
–– time_tag
–– PIRN 6012 for CGS V4.0.0: Add SET_CCSDS_END_POINT /
–– update cmds
––END HISTORY
––
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
library GROUND_TO_OB_LIB;
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– CONSTANTS AND TYPES
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
type END_POINT = PATHNAME (CCSDS_END_POINT);
type FLAP_NAME = PATHNAME (UCL_AUTOMATED_PROCEDURE);
type SW_COMMAND = PATHNAME (SWOP_COMMAND);
type SW_COMMANDS_AND_RESPONSES = PATHNAME (SWOP_COMMAND,
RESPONSE_PACKET,
VIRTUAL);
––
–– Type and Constants defining priority
––
type PRIORITY = (LOW, HIGH);
constant ONBOARD_LOW: INTEGER := 1;
constant ONBOARD_HIGH: INTEGER := 2;
constant DEFAULT_ONBOARD_PRIORITY: INTEGER := ONBOARD_LOW;
type ONBOARD_PRIORITY = INTEGER (ONBOARD_LOW .. ONBOARD_HIGH);
––
–– Constants defining timeouts
––
constant DEFAULT_SW_COMMAND_TIMEOUT: DURATION := 10.0 [s];
constant DEFAULT_FLAP_TIMEOUT: DURATION := 30.0 [s];
––
–– Type and Constants defining the status returned for UCL procedures
––

Space Infrastructure
type UCL_RETURN = INTEGER;
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
constant OK: UCL_RETURN := 1;
constant BUSY: UCL_RETURN := 2;
constant INVALID_ITEM_NAME: UCL_RETURN := 9;
constant INVALID_APPLICATION_ID: UCL_RETURN := 12;
constant INVALID_NODE_NAME: UCL_RETURN := 13;
constant ITEM_IS_DISABLED: UCL_RETURN := 18;
constant MESSAGE_TOO_BIG: UCL_RETURN := 20;
constant NO_ADU_SERVICE: UCL_RETURN := 21;
constant APPLICATION_NACK: UCL_RETURN := 23;
constant INVALID_APPLICATION_NAME: UCL_RETURN := 24;
constant APPLICATION_NOT_READY: UCL_RETURN := 25;
constant TIMEOUT: UCL_RETURN := 26;
constant INVALID_ADU_TYPE: UCL_RETURN := 30;
constant INVALID_TESTNODE_MODE: UCL_RETURN := 31;
constant ITEM_NOT_SAS_COMPATIBLE: UCL_RETURN := 32;
constant NO_GDU_SERVICE: UCL_RETURN := 35;
constant INVALID_TIME: UCL_RETURN := 37;
constant OPERATION_ABORTED: UCL_RETURN := 39;
constant PROTOCOL_ERROR: UCL_RETURN := 48;
constant PARAMETER_ERROR: UCL_RETURN := 49;
constant COMMUNICATION_ERROR: UCL_RETURN := 54;
constant INVALID_NODE_TYPE: UCL_RETURN := 56;
constant SW_COMMAND_NOT_FOUND: UCL_RETURN := 58;
constant RESPONSE_TOO_SHORT: UCL_RETURN := 59;
constant RESPONSE_TIMEOUT: UCL_RETURN := 60;
constant RUNTIME_ERROR: UCL_RETURN := 100;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
427 von/of: 662
––
–– Types and Constants defining the status returned in the response
packet
––
type FLAP_RETURN = INTEGER;
type ONBOARD_RETURN = INTEGER;
type FLAP_ID = INTEGER;
constant ONB_RESULT_SUCCESS: ONBOARD_RETURN := 0;
constant ONB_RESULT_SEQUENCE_COUNT_ANOMALY: ONBOARD_RETURN := 1;
constant ONB_RESULT_NOT_AUTHORIZED: ONBOARD_RETURN := 2;
constant ONB_RESULT_UNKNOWN_COMMAND: ONBOARD_RETURN := 3;
constant ONB_RESULT_COMMAND_NOT_VALID: ONBOARD_RETURN := 4;
constant ONB_RESULT_PARAMETERS_INCOMPLETE: ONBOARD_RETURN := 5;
constant ONB_RESULT_PARAMETERS_NOT_VALID: ONBOARD_RETURN := 6;
constant ONB_RESULT_SEQUENCE_COUNT_REPETITION: ONBOARD_RETURN := 7;
constant ONB_RESULT_SEQUENCE_COUNT_MISMATCH: ONBOARD_RETURN := 8;
constant ONB_RESULT_CHECKSUM_ERROR: ONBOARD_RETURN := 9;
constant ONB_RESULT_TWO_STAGE_BUF_FULL: ONBOARD_RETURN := 10;
constant ONB_RESULT_TWO_STAGE_SOURCE_MISMATCH: ONBOARD_RETURN := 11;

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
428 von/of: 662
constant ONB_RESULT_OTHER: ONBOARD_RETURN := 63;
––
–– Type for setting the device address linked to an application id
––
type DEVICE_ADDRESS = STRING (20);
––
–– Type for setting the SAS name defined for SWOP and Response packets
––
type SAS_NAME = STRING (20);
constant NULL_SAS_NAME : SAS_NAME := ””;
constant NO_DATA_LENGTH_LIMIT : INTEGER := 4081;
–– maximum length of data field + 1;
type DATA_LENGTH_RANGE = INTEGER (0 .. NO_DATA_LENGTH_LIMIT);
––
–– type for setting the packet type of a swop command
––
constant CCSDS_DEFAULT_PACKET : INTEGER := 0;
constant CCSDS_MEMORY_DUMP_PACKET : INTEGER := 1;
constant CCSDS_DATA_SEGMENT_PACKET : INTEGER := 2;
constant CCSDS_ESSENTIAL_HK_PACKET : INTEGER := 3;
constant CCSDS_SYSTEM_HK_PACKET : INTEGER := 4;
constant CCSDS_PAYLOAD_HK_PACKET : INTEGER := 5;
constant CCSDS_SCIENCE_PACKET : INTEGER := 6;
constant CCSDS_SSMB_ANCILLIARY_PACKET : INTEGER := 7;
constant CCSDS_ESSENTIAL_COMMAND_PACKET : INTEGER := 8;
constant CCSDS_SYSTEM_COMMAND_PACKET : INTEGER := 9;
constant CCSDS_PAYLOAD_COMMAND_PACKET : INTEGER := 10;
constant CCSDS_MEMORY_LOAD_PACKET : INTEGER := 11;
constant CCSDS_RESPONSE_PACKET : INTEGER := 12;
constant CCSDS_REPORT_PACKET : INTEGER := 13;
constant CCSDS_EXCEPTION_PACKET : INTEGER := 14;
constant CCSDS_ACKNOWLEDGE_PACKET : INTEGER := 15;
type CCSDS_PACKET_TYPE
= INTEGER (CCSDS_DEFAULT_PACKET .. CCSDS_ACKNOWLEDGE_PACKET);
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
429 von/of: 662
–– Onboard Software Commanding / Flight Application Control
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
procedure SET_CCSDS_END_POINT
(in GROUND_NODE : END_POINT;
out STATUS : UCL_RETURN);
procedure ISSUE_SW_COMMAND
(in SW_CMD : SW_COMMAND ();
in ONBOARD_NODE : END_POINT;
in GROUND_NODE : END_POINT := \\;
in PRIO : PRIORITY := LOW;
in TIMEOUT : DURATION :=
default_sw_command_timeout;
in MAX_DATA_LENGTH : DATA_LENGTH_RANGE :=
NO_DATA_LENGTH_LIMIT;
out RECEIVED_DATA_LENGTH : DATA_LENGTH_RANGE;
out TRANSACTION_ID : INTEGER;
out RESULT : ONBOARD_RETURN;
out STATUS : UCL_RETURN);
procedure ENABLE_SW_COMMAND
(in SW_CMD : SW_COMMAND;
out STATUS : UCL_RETURN);
procedure DISABLE_SW_COMMAND
(in SW_CMD : SW_COMMAND;
out STATUS : UCL_RETURN);
procedure EXECUTE_FLAP
(in FLAP : FLAP_NAME ();
in ONBOARD_RECEPTION_NODE : END_POINT;
in ONBOARD_EXECUTION_NODE : END_POINT := \\;
in GROUND_NODE : END_POINT := \\;
in GROUND_PRIO : PRIORITY := LOW;
in ONBOARD_PRIO : ONBOARD_PRIORITY :=
default_onboard_priority;
in TIME_TAG : TIME := ~:~;
in TIMEOUT : DURATION :=
default_flap_timeout;
out TRANSACTION_ID : INTEGER;
out RESULT : ONBOARD_RETURN;
out ID : FLAP_ID;
out FLAP_EXEC_STATUS : FLAP_RETURN;
out STATUS : UCL_RETURN);
procedure EXECWAIT_FLAP
(in FLAP : FLAP_NAME ();
in ONBOARD_RECEPTION_NODE : END_POINT;
in ONBOARD_EXECUTION_NODE : END_POINT := \\;

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
in GROUND_NODE : END_POINT := \\;
in GROUND_PRIO : PRIORITY := LOW;
in ONBOARD_PRIO : ONBOARD_PRIORITY :=
default_onboard_priority;
in TIME_TAG : TIME := ~:~;
in TIMEOUT : DURATION :=
default_flap_timeout;
out TRANSACTION_ID : INTEGER;
out RESULT : ONBOARD_RETURN;
out ID : FLAP_ID;
out FLAP_EXEC_STATUS : FLAP_RETURN;
out STATUS : UCL_RETURN);
procedure SET_DEVICE_ADDRESS
(in SOURCE : END_POINT;
in DESTINATION : END_POINT;
in ADDRESS : DEVICE_ADDRESS;
out STATUS : UCL_RETURN);
procedure ROUTE_SWOP_TO_SAS
(in ITEM : SW_COMMANDS_AND_RESPONSES;
in SAS : SAS_NAME;
in OLD_SAS : SAS_NAME := NULL_SAS_NAME;
out STATUS : UCL_RETURN);
procedure GET_CCSDS_PACKET_TYPE
(in SW_CMD : SW_COMMAND;
out PACKET_TYPE : CCSDS_PACKET_TYPE;
out STATUS : UCL_RETURN);
procedure SET_CCSDS_PACKET_TYPE
(in SW_CMD : SW_COMMAND;
in PACKET_TYPE : CCSDS_PACKET_TYPE;
out STATUS : UCL_RETURN);
End GROUND_TO_OB_LIB;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
430 von/of: 662

Space Infrastructure
7.9.2.3 Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
431 von/of: 662
These procedures control the emission of CCSDS command packets (Protocol Data Units or PDUs)
from ground (e.g. AP) to onboard application (SWOP). The structure and the format of these packets
are predefined in the database.
7.9.2.3.1 Test Node Initialization
7.9.2.3.1.1 SET_CCSDS_END_POINT
Specification
procedure SET_CCSDS_END_POINT
(in GROUND_NODE: END_POINT;
out STATUS: UCL_RETURN);
Description / Parameters
Sets up the CCSDS ground destination (End Point), which is simulated by the test node. From this end
point, the addressing parameter for the CCSDS packets are derived when sending commands to
onboard (e.g. sw–commands or FLAP execution requests) and receiving responses.
GROUND_NODE: pathname of the CCSDS End Point which shall be simulated by the test node.
STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Possible Return Codes:
OK The procedure was successful
INVALID_NODE_NAME GROUND_NODE refers to an unknown item
INVALID_TESTNODE_MODE The test node is not in the right mode
(NORMAL,SIMULATION)
RUNTIME_ERROR Unexpected error

Space Infrastructure
7.9.2.3.2 Software Commanding to Onboard
7.9.2.3.2.1 ISSUE_SW_COMMAND
Specification
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
432 von/of: 662
Description / Parameters
Builds a Telecommand – CCSDS Protocol Data Unit (PDU) – and initiates the uplink of the SWOP
command. Onboard the command with the given input parameter will be executed.
NOTE: When setting the time–out to zero, only a GDU with the SW command in a CCSDS packet will
be sent to SAS using a time–out value defined in the TES_CONFIG_FILE (under $TES_HOME/config)
for the acknowledge of the GDU. The configurable value is defined under the name SW_OR-
DER.ISSUE_TIMEOUT_WHEN_NO_DELAY and has a predefined value of 5 sec (that can be configured
by the user). No response will be acquired if the timeout is set to zero.
SW_CMD : name of the SW–command to be executed onboard, followed by its list of actual
parameters (if any)
ONBOARD_NODE : Onboard node (CCSDS_End_Point) where the command is sent to.
GROUND_NODE : Ground node which is simulated by CGS and where the response has to be
returned to. If ”\\” is given, the value defined by SET_CCSDS_END_POINT
is applicable.
PRIO (optional) : indicates the priority at which the SW–Command is to be executed within the
Ground System.
TIMEOUT (optional) : the maximum time to wait for acknowledgement of this command
(i.e. the time to wait until the onboard FLAP has finished)
MAX_DATA_LENGTH (optional) : the maximum length in octets of the packet data field (without
checksum and headers). The data is truncated whenever the parameters imply a longer data field.
as follows: For INTEGER the MSB of the integer and for STRING the maximum length will be written,
string length is set accordingly to the truncated part. For other types, no data will be written.

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
433 von/of: 662
RECEIVED_DATA_LENGTH : the length in octets of the out parameter part of the resonse packet
(without checksum, headers, transaction id , onboard result). In case the received response packet
is shorter than requested by the set of out parameters the remaining out parameters shall be set to
their type respective null value (ie. INTEGER –> 0, REAL –> 0.0, TIME –>~:~, PATHNAME –> \\,
STRING –> ””, STATECODE –> $OTHER). The STATUS will be set to RESPONSE_TOO_SHORT
in this case. If a parameter cannot be filled completely then the parameter is also set to the null values
as described above, except for INTEGER the remaining bytes are used as MSB of the integer and
STRING which are truncated, ie. length is set to truncated string length.
TRANSACTION_ID: Returns the ID as received from the response packet:
the primary header of the CCSDS uplink packet without the length field
RESULT: Returns the status of the execution as received from onboard
(returned in response packet)
STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Possible Return Codes:
OK The procedure was successful
BUSY The system (test node) is currently busy
with another SW command, try again later if
necessary
INVALID_ITEM_NAME The name of the SW Command is unknown
INVALID_NODE_NAME The ID in ONBOARD_NODE or GROUND_NODE
is unknown
INVALID_TESTNODE_MODE The test node is not in the right mode
(NORMAL, SIMULATION)
ITEM_IS_DISABLED The SW command is disabled
TIMEOUT There was no response from the SAS or
from the onboard system (response packet)
NO_GDU_SERVICE The SAS did not announce the GDU Service
NO_ADU_SERVICE The SAS did not announce the ADU Service
INVALID_APPLICATION_NAME The SAS is not known
APPLICATION_NOT_READY The SAS is not connected
APPLICATION_NACK There was a negative response from
the SAS
INVALID TIME The timetag given in the GDU header or
CCSDS header was not correct
PARAMETER_ERROR When processing the parameter list of the
SW command an error occurred
COMMUNICATION_ERROR There was a problem in the communication
to the SAS
RUNTIME_ERROR There was an error during the
interpretation of the UCL Intermediate Code
RESPONSE_TOO_SHORT Response packet data length was shorter
than expected.
MESSAGE_TOO_BIG Parameter list too big.

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
434 von/of: 662
OPERATION_ABORTED Aborted (eg. through ABORT_AP, STOP_TES)
INVALID_ADU_TYPE ADU of wrong type (e.g. not CCSDS packet)
has been received as response
PROTOCOL_ERROR Incorrect length of response packet or
incorrect checksum in case when the checksum
is checked, see configuration parameters
TES.CHECK_CHECKSUM and
TES.PROCESS_ON_INCORRECT_CHECKSUM
Example Call
ISSUE_SW_COMMAND (SW_CMD: \a\b\load_mon_tab (\x\mon_tab), ONBOARD_NODE: \apm\dms_1,
GROUND_NODE: \apm\cc, TRANSACTION_ID: t_id,
RESULT: onboard_status, STATUS:stat);

Space Infrastructure
7.9.2.3.2.2 ENABLE_SW_COMMAND
Description / Parameters
Enables a SWOP Command for execution
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
435 von/of: 662
Specification
procedure ENABLE_SW_COMMAND
(in SW_CMD: SW_COMMAND;
out STATUS: UCL_RETURN);
SW_CMD : name of the SW–command to enabled.
STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Possible Return Codes:
OK The procedure was successful
This status is also returned if the item was
already enabled
INVALID_ITEM_NAME The name of the SW Command is unknown
INVALID_TESTNODE_MODE The test node is not in the right mode
(NORMAL,SIMULATION)
RUNTIME_ERROR Unexpected error
Example Call
ENABLE_SW_COMMAND (\a\b\load_mon_tab, STATUS:stat);

Space Infrastructure
7.9.2.3.2.3 DISABLE_SW_COMMAND
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
Description / Parameters
Disables a SWOP Command for execution (i.e. ISSUE command will be rejected for it)
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
436 von/of: 662
Specification
procedure DISABLE_SW_COMMAND
(in SW_CMD: SW_COMMAND;
out STATUS: UCL_RETURN);
SW_CMD : name of the SW–command to enabled.
STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Possible Return Codes:
OK The procedure was successful.
This status is also returned if the item was
already disabled
INVALID_ITEM_NAME The name of the SW Command is unknown
INVALID_TESTNODE_MODE The test node is not in the right mode
(NORMAL,SIMULATION)
RUNTIME_ERROR Unexpected error
Example Call
DISABLE_SW_COMMAND (\a\b\load_mon_tab, STATUS:stat);

Space Infrastructure
7.9.2.3.3 FLAP Execution
7.9.2.3.3.1 EXECUTE_FLAP
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
437 von/of: 662
Specification
procedure EXECUTE_FLAP
(in FLAP: FLAP_NAME ();
in ONBOARD_RECEPTION_NODE: END_POINT;
in ONBOARD_EXECUTION_NODE: END_POINT := \\;
in GROUND_NODE: END_POINT := \\;
in GROUND_PRIO: PRIORITY := LOW;
in ONBOARD_PRIO: ONBOARD_PRIORITY := default_onboard_priority;
in TIME_TAG: TIME := ~:~;
in TIMEOUT: DURATION := default_flap_timeout;
out TRANSACTION_ID: INTEGER;
out RESULT: ONBOARD_RETURN;
out ID: FLAP_ID;
out FLAP_EXEC_STATUS: FLAP_RETURN;
out STATUS: UCL_RETURN);
Description / Parameters
Builds a Telecommand – CCSDS Protocol Data Unit (PDU) – and initiates the uplink of the command.
Onboard the command instantiates and starts a flight application program (FLAP) .
Waits for the response packet and returns the parameter (packet is returned after initiation of the
FLAP)
NOTE: When setting the time–out to zero, only a GDU with the SW command in a CCSDS packet will
be sent to SAS using a time–out value defined in the TES_CONFIG_FILE (under $TES_HOME/config)
for the acknowledge of the GDU. The configurable value is defined under the name SW_OR-
DER.ISSUE_TIMEOUT_WHEN_NO_DELAY and has a predefined value of 5 sec (that can be configured
by the user). No response will be acquired if the timeout is set to zero.
FLAP : name of the FLAP to be started, followed by its list of actual parameters (if any)
ONBOARD_RECEPTION_NODE : onboard node (CCSDS End Point) to which the command is
to be sent to
ONBOARD_EXECUTION_NODE : onboard node (CCSDS End Point) on which the FLAP shall
be executed.
GROUND_NODE (optional) : Ground node which is simulated by CGS and where the response
has to be returned to. If ”\\” is given, the value defined by
SET_CCSDS_END_POINT is applicable.
GROUND_PRIO (optional) : indicates the priority at which the command is to be sent in the
Ground System
ONBOARD_PRIO (optional) : indicates the priority at which the FLAP is to be executed in the
onboard system
TIME_TAG (optional) : indicates the time when to execute the FLAP.
The default value (~:~) indicates immediate execution (timetag is set to 0
in the uplink packet). The time value is processed by the onboard system

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
438 von/of: 662
TIMEOUT (optional) : the maximum time to wait for acknowledgement of this command
(i.e. the time until the response packet has been received).
ID : returns a unique identifier of this instance of the FLAP; 0 if the FLAP could not be started.
TRANSACTION_ID: Returns the ID as received from the response packet:
the primary header of the CCSDS uplink packet without the length field
RESULT: Returns the status of the execution as received from onboard
(returned in response packet)
FLAP_EXEC_STATUS: Returns the status of the execution as received from onboard UCL
Interpreter (returned in response packet)
STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Possible Return Codes:
OK The procedure was successful
BUSY The system (test node) is currently busy
with another SW command, try again later if
necessary
INVALID_ITEM_NAME The name of the FLAP is unknown
INVALID_NODE_NAME The ID in ONBOARD_NODE or GROUND_NODE
is unknown
INVALID_TESTNODE_MODE The test node is not in the right mode
(NORMAL, SIMULATION)
ITEM_IS_DISABLED The SW command defined for EXEC_FLAP
is disabled
TIMEOUT There was no response from the SAS or
from the onboard system (response packet)
NO_GDU_SERVICE The SAS did not announce the GDU Service
NO_ADU_SERVICE The SAS did not announce the ADU Service
INVALID_APPLICATION_NAME The SAS is not known
APPLICATION_NOT_READY The SAS is not connected
APPLICATION_NACK There was a negative response from
the SAS
INVALID TIME The timetag given in the GDU header or
CCSDS header was not correct
COMMUNICATION_ERROR There was a problem in the communication
to the SAS
SW_COMMAND_NOT_FOUND The SW Command, whose name/SID is defined
in the Configuration File, is not found in
the SW Command table, or it is even
not defined in the Configuration File
PARAMETER_ERROR When processing the parameter list of the
FLAP command an error occurred
RUNTIME_ERROR There was an error during the
interpretation of the UCL Intermediate Code
MESSAGE_TOO_BIG Parameters to be put into CCSDS packet

Space Infrastructure
are too big
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
439 von/of: 662
PROTOCOL_ERROR Incorrect length of response packet or
incorrect checksum in case when the checksum
is checked, see configuration parameters
TES.CHECK_CHECKSUM and
TES.PROCESS_ON_INCORRECT_CHECKSUM
Example Call
EXECUTE_FLAP (FLAP:\ecls\fan1\start_fan (slow),
ONBOARD_RECEPTION_NODE: \apm\ node, ID: flap_id,
TRANSACTION_ID: t_id, RESULT: onboard_status,
FLAP_EXEC_STATUS: flap_stat, STATUS: stat);

Space Infrastructure
7.9.2.3.3.2 EXECWAIT_FLAP
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
440 von/of: 662
Specification
procedure EXECWAIT_FLAP
(in FLAP: FLAP_NAME ();
in ONBOARD_RECEPTION_NODE: END_POINT;
in ONBOARD_EXECUTION_NODE: END_POINT := \\;
in GROUND_NODE: END_POINT := \\;
in GROUND_PRIO: PRIORITY := LOW;
in ONBOARD_PRIO: ONBOARD_PRIORITY := default_onboard_priority;
in TIME_TAG: TIME := ~:~;
in TIMEOUT: DURATION := default_flap_timeout;
out TRANSACTION_ID: INTEGER;
out RESULT: ONBOARD_RETURN;
out ID: FLAP_ID;
out FLAP_EXEC_STATUS: FLAP_RETURN;
out STATUS: UCL_RETURN);
Description / Parameters
Builds a Telecommand – a GDU containing a CCSDS Protocol Data Unit– and initiates the uplink of the
command. Onboard the command instantiates and starts a flight application program (FLAP) . Waits
for the response packet and returns the parameter (packet is returned after completion of the FLAP).
NOTE: When setting the time–out to zero, only a GDU with the SW command in a CCSDS packet will
be sent to SAS using a time–out value defined in the TES_CONFIG_FILE (under $TES_HOME/config)
for the acknowledge of the GDU. The configurable value is defined under the name SW_OR-
DER.ISSUE_TIMEOUT_WHEN_NO_DELAY and has a predefined value of 5 sec (that can be configured
by the user). No response will be acquired if the timeout is set to zero.
FLAP : name of the FLAP to be started, optionally followed by its list of actual parameters.
ONBOARD_RECEPTION_NODE : onboard node (CCSDS End Point) to which the command is
to be sent to
ONBOARD_EXECUTION_NODE : onboard node (CCSDS End Point) on which the FLAP shall
be executed.
GROUND_NODE (optional) : Ground node which is simulated by CGS and where the response
has to be returned to. If ”\\” is given, the value defined by
SET_CCSDS_END_POINT is applicable.
GROUND_PRIO (optional) : indicates the priority at which the command is to be sent in the
Ground System
ONBOARD_PRIO (optional) : indicates the priority at which the FLAP is to be executed in the
onboard system
TIME_TAG (optional) : indicates the time when to execute the FLAP. The default value (~:~)
indicates immediate execution (timetag is set to 0 in the uplink packet).
The time value is processed by the onboard system
TIMEOUT (optional) : the maximum time to wait for acknowledgement of this command
(i.e. the time to wait until the response packet has been received)

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
441 von/of: 662
ID : returns a unique identifier of this instance of the FLAP; 0 if the FLAP could not be started.
TRANSACTION_ID: Returns the ID as received from the response packet:
the primary header of the CCSDS uplink packet without the length field
RESULT: Returns the status of the execution as received from onboard
(returned in response packet)
FLAP_EXEC_STATUS:
Returns the status of the execution as received from onboard UCL Interpreter
(returned in response packet)
STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Possible Return Codes:
OK The procedure was successful
BUSY The system (test node) is currently busy
with another SW command, try again later if
necessary
INVALID_ITEM_NAME The name of the FLAP is unknown
INVALID_NODE_NAME The ID in ONBOARD_NODE or GROUND_NODE
is unknown
INVALID_TESTNODE_MODE The test node is not in the right mode
(NORMAL, SIMULATION)
ITEM_IS_DISABLED The SW command defined for EXECWAIT_FLAP
is disabled
TIMEOUT There was no response from the SAS or
from the onboard system (response packet)
NO_GDU_SERVICE The SAS did not announce the GDU Service
NO_ADU_SERVICE The SAS did not announce the ADU Service
INVALID_APPLICATION_NAME The SAS is not known
APPLICATION_NOT_READY The SAS is not connected
APPLICATION_NACK There was a negative response from
the SAS
INVALID TIME The timetag given in the GDU header or
CCSDS header was not correct
COMMUNICATION_ERROR There was a problem in the communication
to the SAS
SW_COMMAND_NOT_FOUND The SW Command, whose name/SID is defined
in the Configuration File, is not found in
the SW Command table, or it is even
not defined in the Configuration File
PARAMETER_ERROR When processing the parameter list of the
FLAP command an error occurred
RUNTIME_ERROR There was an error during the
interpretation of the UCL Intermediate Code
MESSAGE_TOO_BIG Parameters to be put into CCSDS packet
are too big

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
442 von/of: 662
PROTOCOL_ERROR Incorrect length of response packet or
incorrect checksum in case when the checksum
is checked, see configuration parameters
TES.CHECK_CHECKSUM and
TES.PROCESS_ON_INCORRECT_CHECKSUM
Example Call
EXECWAIT_FLAP (FLAP:\ecls\fan1\start_fan (slow),
ONBOARD_RECEPTION_NODE:\apm\ node, GROUND_PRIO:low,
TRANSACTION_ID: t_id, RESULT: onboard_status, ID:flap_id,
FLAP_EXEC_STATUS: flap_return, STATUS:stat);

Space Infrastructure
7.9.2.3.3.3 SET_DEVICE_ADDRESS
Specification
procedure SET_DEVICE_ADDRESS
(in SOURCE : END_POINT;
in DESTINATION : END_POINT;
in ADDRESS : DEVICE_ADDRESS;
out STATUS : UCL_RETURN);
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
443 von/of: 662
Description / Parameters
Set a new device address for the application id identified by the source node and the destination node.
This device address will then be set in the physical address of the SWOP commands and response
packets that are generated with that application id.
SOURCE : name of the source end point for identifying the application id.
DESTINATION : name of the destination end point for identifying the application id.
ADDRESS : string (up to 20 characters) to be set in the device_address field of the physical_address.
STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Possible Return Codes:
OK The procedure was successful
INVALID_NODE_NAME There is no application id defined for
the end point pair (SOURCE, DESTINATION)
RUNTIME_ERROR There was an error during the
interpretation of the UCL Intermediate Code
Example Call
SET_DEVICE_ADDRESS (SOURCE: \apm\node,
DESTINATION: \ground\node,
ADDRESS: ”CC_BUS1”,
STATUS: stat);

Space Infrastructure
7.9.2.3.3.4 ROUTE_SWOP_TO_SAS
Specification
procedure ROUTE_SWOP_TO_SAS
(in ITEM: SW_COMMANDS_AND_RESPONSES;
in SAS: SAS_NAME;
in OLD_SAS: SAS_NAME
:= NULL_SAS_NAME;
out STATUS: UCL_RETURN)
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
444 von/of: 662
Description / Parameters
Routes all items specified in ITEM which have the OLD_SAS_NAME assigned, to the new SAS
specified by SAS_NAME.
ITEM : The item to be re–defined in the local memory of the test node. ITEM can be
– a single enditem of type SWOP_COMMAND or RESPONSE_PACKET
– an incomplete pathname pointing to a virtual node, thus redefining all SWOP_COMMAND
or RESPONSE_PACKET in that subtree;
SAS: The short name (20 character) of the SAS (Specific Application Software) to be assigned
to the ITEM. The SAS must run on the local test node .
OLD_SAS: The short name (20 character) of the SAS currently specified for item.
Only those items are taken into account for the route change, which match this SAS name. If OLD_SAS
is equal to NULL_SAS_NAME, all enditems specified in ITEM are changed, regardless of their current
SAS name.
STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Possible Return Codes:
OK The procedure was successful
INVALID_ITEM_NAME End Item is unknown
INVALID_APPLICATION_NAME A single item is provided with the
OLD_SAS_NAME specified but this does not
match the actual SAS name
RUNTIME_ERROR There was an error during the
interpretation of the UCL Intermediate Code
Example Call
ROUTE_SWOP_TO_SAS (\apm\cc_bus1\swops, ”CC_BUS_2_SAS”, ”CC_BUS_1_SAS”, stat);

Space Infrastructure
7.9.2.3.3.5 GET_CCSDS_PACKET_TYPE
Specification
procedure GET_CCSDS_PACKET_TYPE
(in SW_CMD : SW_COMMAND;
out PACKET_TYPE : CCSDS_PACKET_TYPE;
out STATUS : UCL_RETURN)
Description / Parameters
Gets the CCSDS packet type of a SW command.
SW_CMD : name of the SW–command
PACKET_TYPE: type of the CCSDS packet
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Possible Return Codes:
OK The procedure was successful
INVALID_ITEM_NAME SWOP command is unknown
RUNTIME_ERROR There was an error during the
Example Call
GET_CCSDS_PACKET_TYPE (\a\b\load_mon_tab, packet_type,stat);
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
445 von/of: 662
interpretation of the UCL Intermediate Code

Space Infrastructure
7.9.2.3.3.6 SET_CCSDS_PACKET_TYPE
Specification
procedure SET_CCSDS_PACKET_TYPE
(in SW_CMD : SW_COMMAND;
in PACKET_TYPE : CCSDS_PACKET_TYPE;
out STATUS : UCL_RETURN);
Description / Parameters
Sets the CCSDS packet type of a SW command.
SW_CMD : name of the SW–command
PACKET_TYPE: type of the packet
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
STATUS : returns an integer, the UCL return status (see definition under CONSTANTS).
Possible Return Codes:
OK The procedure was successful
INVALID_ITEM_NAME SWOP command is unknown
RUNTIME_ERROR There was an error during the
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
446 von/of: 662
interpretation of the UCL Intermediate Code
Example Call
SET_CCSDS_PACKET_TYPE (\a\b\load_mon_tab, CCSDS_Memory_Load_Packet, stat);

Space Infrastructure
7.9.3 TCL System Library
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
The TCL System Library defines commands to control the equipment within SVF.
Library Id (Body_Id): 3
The library is defined according to COL–RIBRE–TN–1169, Issue 1/E,.
7.9.3.1 Routines Summary
ASSIGN
DISPLAY_OFF_1553
DISPLAY_OFF_1553_SIGNAL
DISPLAY_ON_1553
DISPLAY_ON_1553_SIGNAL
HOLD_CURRENT
HOLD_SPECIFIED
HRDL_LOG_ON
HRDL_LOG_OFF
INIT_TCL
IOSU_LOG_ON
IOSU_LOG_ON_CARD
IOSU_LOG_ON_SIGNAL
IOSU_LOG_OFF
IOSU_LOG_OFF_CARD
IOSU_LOG_OFF_SIGNAL
IOSU_DISPLAY_ON
IOSU_DISPLAY_ON_CARD
IOSU_DISPLAY_ON_SIGNAL
IOSU_DISPLAY_OFF
IOSU_DISPLAY_OFF_CARD
IOSU_DISPLAY_OFF_SIGNAL
LOG_OFF
LOG_OFF_1553
LOG_OFF_1553_SIGNAL
LOG_ON
LOG_ON_1553
LOG_ON_1553_SIGNAL
RELEASE
SERIEL_LOG_ON
SERIEL_LOG_OFF
SERIEL_DISPLAY_ON
SERIEL_DISPLAY_OFF
START
STOP
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
447 von/of: 662

Space Infrastructure
7.9.3.2 TCL_LIBRARY Specification
library TCL_LIBRARY;
–– TYPES
type T_APPLICATION_ID = INTEGER;
type T_TCL_RETURN = (OK,
INITIALISATION_PROBLEM,
INVALID_PARAMETER,
INVALID_PATHNAME,
SAS_COMMUNICATION_ERROR,
SAS_ID_NOT_INITIALISED,
WRONG_TES_MODE);
type T_RECEIVE_TRANSMIT_1553 = INTEGER(–1..2);
type T_RECEIVE_TRANSMIT_485 = INTEGER(0..2);
type T_RT_ADDRESS = INTEGER(0..32);
type T_SUBADDRESS = INTEGER(–1..32);
type T_MODE_CODE = INTEGER(–1..32);
type T_SLOT = INTEGER(–0..16);
type T_CHANNEL = INTEGER(0..32);
type T_APID = INTEGER(0..2047);
–– Initialize TCL System library
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
448 von/of: 662
procedure INIT_TCL (in TCL_SAS_ID: T_APPLICATION_ID;
out STATUS:T_TCL_RETURN);
–– This procedure initialises the TCL system library. It delivers the Application Id of the TCL SAS, which is the destination
–– for the TCL commands after they have been processed by the TCL system library.
–– This command is processed by the TCL system library only. Nothing is sent to the TCL SAS upon this command.
–– This command is issued only once at the beginning, before any other TCL command is issued. The given TCL_SAS_ID
–– shall then be used for all subsequent TCL commands.
–– Possible return states:
–– OK
–– INITIALISATION_PROBLEM
–– Drive control comands
procedure START (in DRIVE: PATHNAME;
out STATUS: T_TCL_RETURN);
–– This procedure activates a simulation signal.
–– Functions of the TCL system library here:
–– o translate the PATHNAME of the specified parameter in its SID
–– o forward the command to the TCL SAS.
–– Possible return states:
–– OK
–– INVALID_PATHNAME
–– SAS_ID_NOT_INITIALISED,

Space Infrastructure
–– SAS_COMMUNICATION_ERROR,
–– WRONG_TES_MODE
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
procedure STOP (in DRIVE: PATHNAME;
out STATUS: T_TCL_RETURN);
–– This procedure deactivates a simulation signal.
–– Functions of the TCL system library here:
–– o translate the PATHNAME of the specified parameter in its SID
–– o forward the command to the TCL SAS
–– Possible return states:
–– OK
–– INVALID_PATHNAME
–– SAS_ID_NOT_INITIALISED,
–– SAS_COMMUNICATION_ERROR,
–– WRONG_TES_MODE
procedure ASSIGN (in DRIVE: PATHNAME;
in VALUE: REAL;
out STATUS: T_TCL_RETURN);
–– This procedure sets a simulation signal to a specified value for one simulation frame.
–– Functions of the TCL system library here:
–– o translate the PATHNAME of the specified parameter in its SID
–– o format the real value into the format ”[+/–]#.#######[E[+/–]##]” as a string
–– o forward the command to the TCL SAS
–– Possible return states:
–– OK
–– INVALID_PATHNAME
–– WRONG_TES_MODE
–– SAS_ID_NOT_INITIALISED,
–– SAS_COMMUNICATION_ERROR,
–– INVALID_PARAMETER
procedure HOLD_CURRENT (in DRIVE: PATHNAME;
out STATUS: T_TCL_RETURN);
–– This procedure holds the a simulation signal to the current value until it is released again.
–– Functions of the TCL system library here:
–– o translate the PATHNAME of the specified parameter in its SID
–– o forward the command to the TCL SAS
–– Possible return states:
–– OK
–– INVALID_PATHNAME
–– SAS_COMMUNICATION_ERROR,
–– SAS_ID_NOT_INITIALISED,
–– WRONG_TES_MODE
procedure HOLD_SPECIFIED (in DRIVE: PATHNAME;
in VALUE: REAL;
out STATUS: T_TCL_RETURN);
–– This procedure holds a simulation signal to the given value until it is released.
–– Functions of the TCL system library here:
–– o translate the PATHNAME of the specified parameter in its SID
–– o format the real value into the format ”[+/–]#.#######[E[+/–]##]” as a string
–– o forward the command to the TCL SAS
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
449 von/of: 662

Space Infrastructure
–– Possible return states:
–– OK
–– INVALID_PATHNAME
–– WRONG_TES_MODE
–– SAS_ID_NOT_INITIALISED,
–– SAS_COMMUNICATION_ERROR,
–– INVALID_PARAMETER
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
procedure RELEASE (in DRIVE: PATHNAME;
out STATUS: T_TCL_RETURN);
–– This procedure releases a preveiously held simulation signal.
–– Functions of the TCL system library here:
–– o translate the PATHNAME of the specified parameter in its SID
–– o forward the command to the TCL SAS
–– Possible return states:
–– OK
–– INVALID_PATHNAME
–– SAS_ID_NOT_INITIALISED,
–– SAS_COMMUNICATION_ERROR,
–– WRONG_TES_MODE
–– Simulation data collection commands
procedure LOG_ON (in ADU_SIM_LOG: PATHNAME;
out STATUS: T_TCL_RETURN);
–– This procedure starts the sim data collection for a specified logging session and logging frequency.
–– Functions of the TCL system library here:
–– o translate the PATHNAME of the specified parameter in its SID
–– o forward the command to the TCL SAS
–– Possible return states:
–– OK
–– SAS_ID_NOT_INITIALISED,
–– SAS_COMMUNICATION_ERROR,
–– INVALID_PATHNAME
–– WRONG_TES_MODE
procedure LOG_OFF (in ADU_SIM_LOG: PATHNAME;
out STATUS: T_TCL_RETURN);
–– This procedure stops the sim data collection for a specified logging session.
–– Functions of the TCL system library here:
–– o translate the PATHNAME of the specified parameter in its SID
–– o forward the command to the TCL SAS
–– Possible return states:
–– OK
–– SAS_ID_NOT_INITIALISED,
–– SAS_COMMUNICATION_ERROR,
–– INVALID_PATHNAME
–– WRONG_TES_MODE
–– BUS_1553 bus log and display data collection commands
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
450 von/of: 662
procedure LOG_ON_1553 (in BUS_1553: PATHNAME;
in RT_ADDRESS: T_RT_ADDRESS;
in SUB_ADDRESS: T_SUBADDRESS;

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
451 von/of: 662
in RT_TX_A: T_RECEIVE_TRANS-
MIT_1553;
in MODE: T_MODE_CODE;
in RT_TX_B: T_RECEIVE_TRANS-
MIT_1553;
out STATUS: T_TCL_RETURN);
–– This procedure turns the logging on for a given 1553 bus item.
–– Functions of the TCL system library here:
–– o translate the PATHNAME of the specified parameter in its SID
–– o forward the command to the TCL SAS
–– Possible return states:
–– OK
–– SAS_ID_NOT_INITIALISED,
–– SAS_COMMUNICATION_ERROR,
–– INVALID_PATHNAME
–– WRONG_TES_MODE
procedure LOG_ON_1553_SIGNAL (in FLIGHT_SIGNAL: PATHNAME;
out STATUS: T_TCL_RETURN);
–– This procedure turns the logging on for a given 1553 bus item.
–– Functions of the TCL system library here:
–– o translate the PATHNAME of the specified parameter in its SID
–– o forward the command to the TCL SAS
–– Possible return states:
–– OK
–– SAS_ID_NOT_INITIALISED,
–– SAS_COMMUNICATION_ERROR,
–– INVALID_PATHNAME
–– WRONG_TES_MODE
procedure LOG_OFF_1553 (in BUS_1553: PATHNAME;
in RT_ADDRESS: T_RT_ADDRESS;
in SUB_ADDRESS: T_SUBADDRESS;
in RT_TX_A: T_RECEIVE_TRANS-
MIT_1553;
in MODE: T_MODE_CODE;
in RT_TX_B: T_RECEIVE_TRANS-
MIT_1553;
out STATUS: T_TCL_RETURN);
–– This procedure turns the logging off for a given 1553 bus item.
–– Functions of the TCL system library here:
–– o translate the PATHNAME of the specified parameter in its SID
–– o forward the command to the TCL SAS
–– Possible return states:
–– OK
–– SAS_ID_NOT_INITIALISED,
–– SAS_COMMUNICATION_ERROR,
–– INVALID_PATHNAME
–– WRONG_TES_MODE
procedure LOG_OFF_1553_SIGNAL (in FLIGHT_SIGNAL: PATHNAME;
out STATUS: T_TCL_RETURN);
–– This procedure turns the logging off for a given 1553 bus item.

Space Infrastructure
–– Functions of the TCL system library here:
–– o translate the PATHNAME of the specified parameter in its SID
–– o forward the command to the TCL SAS
–– Possible return states:
–– OK
–– SAS_ID_NOT_INITIALISED,
–– SAS_COMMUNICATION_ERROR,
–– INVALID_PATHNAME
–– WRONG_TES_MODE
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
452 von/of: 662
procedure DISPLAY_ON_1553 (in BUS_1553_BUS: PATHNAME;
in RT_ADDRESS: T_RT_ADDRESS;
in SUB_ADDRESS: T_SUBADDRESS;
in RT_TX_A: T_RECEIVE_TRANS-
MIT_1553;
in MODE: T_MODE_CODE;
in RT_TX_B: T_RECEIVE_TRANS-
MIT_1553;
out STATUS: T_TCL_RETURN);
–– This procedure turns the display data collection on for a given 1553 bus item.
–– Functions of the TCL system library here:
–– o translate the PATHNAME of the specified parameter in its SID
–– o forward the command to the TCL SAS
–– Possible return states:
–– OK
–– SAS_ID_NOT_INITIALISED,
–– SAS_COMMUNICATION_ERROR,
–– INVALID_PATHNAME
–– WRONG_TES_MODE
procedure DISPLAY_ON_1553_SIGNAL (in FLIGHT_SIGNAL: PATHNAME;
out STATUS: T_TCL_RETURN);
–– This procedure turns the display data collection on for a given 1553 bus item.
–– Functions of the TCL system library here:
–– o translate the PATHNAME of the specified parameter in its SID
–– o forward the command to the TCL SAS
–– Possible return states:
–– OK
–– SAS_ID_NOT_INITIALISED,
–– INVALID_PATHNAME
–– SAS_COMMUNICATION_ERROR,
–– WRONG_TES_MODE
procedure DISPLAY_OFF_1553 (in BUS_1553_BUS: PATHNAME;
in RT_ADDRESS: T_RT_ADDRESS;
in SUB_ADDRESS: T_SUBADDRESS;
in RT_TX_A: T_RECEIVE_TRANS-
MIT_1553;
in MODE: T_MODE_CODE;
in RT_TX_B: T_RECEIVE_TRANS-
MIT_1553;
out STATUS: T_TCL_RETURN);
–– This procedure turns the display data collection off for a given 1553 bus item.

Space Infrastructure
–– Functions of the TCL system library here:
–– o translate the PATHNAME of the specified parameter in its SID
–– o forward the command to the TCL SAS
–– Possible return states:
–– OK
–– SAS_ID_NOT_INITIALISED,
–– SAS_COMMUNICATION_ERROR,
–– INVALID_PATHNAME
–– WRONG_TES_MODE
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
453 von/of: 662
procedure DISPLAY_OFF_1553_SIGNAL (in FLIGHT_SIGNAL: PATHNAME;
out STATUS: T_TCL_RETURN);
–– This procedure turns the display data collection off for a given 1553 bus item.
–– Functions of the TCL system library here:
–– o translate the PATHNAME of the specified parameter in its SID
–– o forward the command to the TCL SAS
–– Possible return states:
–– OK
–– SAS_ID_NOT_INITIALISED,
–– SAS_COMMUNICATION_ERROR,
–– INVALID_PATHNAME
–– WRONG_TES_MODE
–– SCSI bus log and display commands
procedure IOSU_LOG_ON (in MDM: PATHNAME;
in SLOT: T_SLOT;
in CHANNEL: T_CHANNEL;
out STATUS: T_TCL_RETURN);
–– This procedure turns the logging on for a given SCSI bus item.
–– Functions of the TCL system library here:
–– o translate the PATHNAME of the specified parameter in its SID
–– o forward the command to the TCL SAS
–– Possible return states:
–– OK
–– INVALID_PATHNAME
–– SAS_ID_NOT_INITIALISED,
–– SAS_COMMUNICATION_ERROR,
–– INVALID_SLOT_NUMBER,
–– INVALID_CHANNEL_NUMBER,
–– WRONG_TES_MODE
procedure IOSU_LOG_ON_CARD (in IO_CARD: PATHNAME;
out STATUS: T_TCL_RETURN);
–– This procedure turns the logging on for a given SCSI bus item.
–– Functions of the TCL system library here:
–– o translate the PATHNAME of the specified parameter in its SID
–– o forward the command to the TCL SAS
–– Possible return states:
–– OK
–– SAS_ID_NOT_INITIALISED,
–– SAS_COMMUNICATION_ERROR,

Space Infrastructure
–– INVALID_PATHNAME
–– WRONG_TES_MODE
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
procedure IOSU_LOG_ON_SIGNAL (in FLIGHT_SIGNAL: PATHNAME;
out STATUS: T_TCL_RETURN);
–– This procedure turns the logging on for a given SCSI bus item.
–– Functions of the TCL system library here:
–– o translate the PATHNAME of the specified parameter in its SID
–– o forward the command to the TCL SAS
–– Possible return states:
–– OK
–– SAS_ID_NOT_INITIALISED,
–– INVALID_PATHNAME
–– WRONG_TES_MODE
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
454 von/of: 662
procedure IOSU_LOG_OFF (in MDM: PATHNAME;
in SLOT: T_SLOT;
in CHANNEL: T_CHANNEL;
out STATUS: T_TCL_RETURN);
–– This procedure turns the logging off for a given SCSI bus item.
–– Functions of the TCL system library here:
–– o translate the PATHNAME of the specified parameter in its SID
–– o forward the command to the TCL SAS
–– Possible return states:
–– OK
–– SAS_ID_NOT_INITIALISED,
–– SAS_COMMUNICATION_ERROR,
–– INVALID_PATHNAME
–– WRONG_TES_MODE
procedure IOSU_LOG_OFF_CARD (in IO_CARD: PATHNAME;
out STATUS: T_TCL_RETURN);
–– This procedure turns the logging off for a given SCSI bus item.
–– Functions of the TCL system library here:
–– o translate the PATHNAME of the specified parameter in its SID
–– o forward the command to the TCL SAS
–– Possible return states:
–– OK
–– SAS_ID_NOT_INITIALISED,
–– SAS_COMMUNICATION_ERROR,
–– INVALID_PATHNAME
–– WRONG_TES_MODE
procedure IOSU_LOG_OFF_SIGNAL (in FLIGHT_SIGNAL: PATHNAME;
out STATUS: T_TCL_RETURN);
–– This procedure turns the logging off for a given SCSI bus item.
–– Functions of the TCL system library here:
–– o translate the PATHNAME of the specified parameter in its SID
–– o forward the command to the TCL SAS
–– Possible return states:
–– OK
–– INVALID_PATHNAME
–– SAS_ID_NOT_INITIALISED,

Space Infrastructure
–– SAS_COMMUNICATION_ERROR,
–– WRONG_TES_MODE
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
455 von/of: 662
procedure IOSU_DISPLAY_ON (in MDM: PATHNAME;
in SLOT: T_SLOT;
in CHANNEL: T_CHANNEL;
out STATUS: T_TCL_RETURN);
–– This procedure turns the display data collection on for a given SCSI bus item.
–– Functions of the TCL system library here:
–– o translate the PATHNAME of the specified parameter in its SID
–– o forward the command to the TCL SAS
–– Possible return states:
–– OK
–– INVALID_PATHNAME
–– SAS_ID_NOT_INITIALISED,
–– SAS_COMMUNICATION_ERROR,
–– WRONG_TES_MODE
procedure IOSU_DISPLAY_ON_CARD (in IO_CARD: PATHNAME;
out STATUS: T_TCL_RETURN);
–– This procedure turns the display data collection on for a given SCSI bus item.
–– Functions of the TCL system library here:
–– o translate the PATHNAME of the specified parameter in its SID
–– o forward the command to the TCL SAS
–– Possible return states:
–– OK
–– INVALID_PATHNAME
–– SAS_ID_NOT_INITIALISED,
–– WRONG_TES_MODE
procedure IOSU_DISPLAY_ON_SIGNAL (in FLIGHT_SIGNAL: PATHNAME;
out STATUS: T_TCL_RETURN);
–– This procedure turns the display data collection on for a given SCSI bus item.
–– Functions of the TCL system library here:
–– o translate the PATHNAME of the specified parameter in its SID
–– o forward the command to the TCL SAS
–– Possible return states:
–– OK
–– INVALID_PATHNAME
–– SAS_ID_NOT_INITIALISED,
–– WRONG_TES_MODE
procedure IOSU_DISPLAY_OFF (in MDM: PATHNAME;
in SLOT: T_SLOT;
in CHANNEL: T_CHANNEL;
out STATUS: T_TCL_RETURN);
–– This procedure turns the display data collection off for a given SCSI bus item.
–– Functions of the TCL system library here:
–– o translate the PATHNAME of the specified parameter in its SID
–– o forward the command to the TCL SAS
–– Possible return states:
–– OK
–– INVALID_PATHNAME

Space Infrastructure
–– SAS_ID_NOT_INITIALISED,
–– SAS_COMMUNICATION_ERROR,
–– WRONG_TES_MODE
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
456 von/of: 662
procedure IOSU_DISPLAY_OFF_CARD (in IO_CARD: PATHNAME;
out STATUS: T_TCL_RETURN);
–– This procedure turns the display data collection off for a given SCSI bus item.
–– Functions of the TCL system library here:
–– o translate the PATHNAME of the specified parameter in its SID
–– o forward the command to the TCL SAS
–– Possible return states:
–– OK
–– INVALID_PATHNAME
–– SAS_ID_NOT_INITIALISED,
–– SAS_COMMUNICATION_ERROR,
–– WRONG_TES_MODE
procedure IOSU_DISPLAY_OFF_SIGNAL (in FLIGHT_SIGNAL: PATHNAME;
out STATUS: T_TCL_RETURN);
–– This procedure turns the display data collection off for a given SCSI bus item.
–– Functions of the TCL system library here:
–– o translate the PATHNAME of the specified parameter in its SID
–– o forward the command to the TCL SAS
–– Possible return states:
–– OK
–– INVALID_PATHNAME
–– SAS_ID_NOT_INITIALISED,
–– SAS_COMMUNICATION_ERROR,
–– WRONG_TES_MODE
–– HRDL bus log and display data collection commands
procedure HRDL_LOG_ON (in MDM: PATHNAME;
in APID_A: T_APID;
in APID_B: T_APID;
out STATUS: T_TCL_RETURN);
–– This procedure turns the logging on for a given HRDL bus item.
–– Functions of the TCL system library here:
–– o translate the PATHNAME of the specified parameter in its SID
–– o forward the command to the TCL SAS
–– Possible return states:
–– OK
–– INVALID_PATHNAME
–– SAS_ID_NOT_INITIALISED,
–– SAS_COMMUNICATION_ERROR,
–– WRONG_TES_MODE
procedure HRDL_LOG_OFF (in MDM: PATHNAME;
in APID_A: T_APID;
in APID_B: T_APID;
out STATUS: T_TCL_RETURN);
–– This procedure turns the logging off for a given HRDL bus item.
–– Functions of the TCL system library here:
–– o translate the PATHNAME of the specified parameter in its SID

Space Infrastructure
–– o forward the command to the TCL SAS
–– Possible return states:
–– OK
–– INVALID_PATHNAME
–– SAS_ID_NOT_INITIALISED,
–– SAS_COMMUNICATION_ERROR,
–– WRONG_TES_MODE
–– RS485 bus log and display commands
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
457 von/of: 662
procedure SERIAL_LOG_ON (in BUS_485: PATHNAME;
in RT_TX: T_RECEIVE_TRANSMIT_485;
out STATUS: T_TCL_RETURN);
–– This procedure turns the logging on for a given RS485 bus item.
–– Functions of the TCL system library here:
–– o translate the PATHNAME of the specified parameter in its SID
–– o forward the command to the TCL SAS
–– Possible return states:
–– OK
–– INVALID_PATHNAME
–– SAS_ID_NOT_INITIALISED,
–– SAS_COMMUNICATION_ERROR,
–– WRONG_TES_MODE
procedure SERIAL_LOG_OFF (in BUS_485: PATHNAME;
in RT_TX: T_RECEIVE_TRANSMIT_485;
out STATUS: T_TCL_RETURN);
–– This procedure turns the logging off for a given RS485 bus item.
–– Functions of the TCL system library here:
–– o translate the PATHNAME of the specified parameter in its SID
–– o forward the command to the TCL SAS
–– Possible return states:
–– OK
–– INVALID_PATHNAME
–– SAS_ID_NOT_INITIALISED,
–– WRONG_TES_MODE
procedure SERIAL_DISPLAY_ON (in BUS_485: PATHNAME;
in RT_TX: T_RECEIVE_TRANSMIT_485;
out STATUS: T_TCL_RETURN);
–– This procedure turns the display data collection on for a given RS485 bus item.
–– Functions of the TCL system library here:
–– o translate the PATHNAME of the specified parameter in its SID
–– o forward the command to the TCL SAS
–– Possible return states:
–– OK
–– INVALID_PATHNAME
–– SAS_ID_NOT_INITIALISED,
–– SAS_COMMUNICATION_ERROR,
–– WRONG_TES_MODE
procedure SERIAL_DISPLAY_OFF (in BUS_485: PATHNAME;
in RT_TX: T_RECEIVE_TRANSMIT_485;
out STATUS: T_TCL_RETURN);

Space Infrastructure
–– This procedure turns the display data collection off for a given RS485 bus item.
–– Functions of the TCL system library here:
–– o translate the PATHNAME of the specified parameter in its SID
–– o forward the command to the TCL SAS
–– Possible return states:
–– OK
–– INVALID_PATHNAME
–– SAS_ID_NOT_INITIALISED,
–– SAS_COMMUNICATION_ERROR,
–– WRONG_TES_MODE
end TCL_LIBRARY;
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
458 von/of: 662

Space Infrastructure
7.9.3.3 TCL ASCII Format Specification
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
The following format shall be sent by the TCL system library.
In general the Operation Token (= command word) is to be given in upper case, the parameters
are given in lower case/numbers.
The format described in the Legend is the max. possible number of digits.
No leading or tailoring zeroes are required, because there are delimiters between the parameters.
Legend:
iiiiii SID 32bit integer in ASCII (hexadecimal presentation)
nnnnnn float value format ”[+/–]#.#######[E[+/–]##]” in ASCII
rrrrrr remote terminal number Integer range 0..32 in ASCII (decimal)
aaaaaa subaddress number Integer range –1..32 in ASCII (decimal)
dddddd mode code Integer range –1..32 in ASCII (decimal)
tttttt slot number Integer range 0..16 in ASCII (decimal)
cccccc channel number Integer range 0..32 in ASCII (decimal)
pppppp APID Integer range 0..2047 in ASCII (decimal)
xx Rec–Transmit code 1553 Integer range –1..2 in ASCII (decimal)
xx Rec–Transmit code 485 Integer range 0..2 in ASCII (decimal)
^ mandatory blank character ’ ’
Procedure Name ASCII format Example
INIT_TCL N/A
START START^iiiiii START^123FFF
STOP STOP^iiiiii STOP^12FF
ASSIGN :=^iiiiii,^nnnnnn :=^3456,^1.126E–02
HOLD_CURRENT HOLD^iiiiii HOLD^123456
HOLD_SPECIFIED HOLD^iiiiii,^nnnnnn HOLD^1234FF,^1.12
RELEASE RELEASE^iiiiii RELEASE^123456
LOG_ON SES_ON^iiiiii SES_ON^123456
LOG_OFF SES_OFF^iiiiii SES_OFF^123456
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
459 von/of: 662
LOG_ON_1553 LB_ON^iiiiii:rrrrrr:aaaaaa:xx:dddddd:xx LB_ON^1234FF:15:21:–
1:32:0
LOG_ON_1553_SIGNAL LB_ON^iiiiii LB_ON^1234FF
LOG_OFF_1553 LB_OFF^iiiiii:rrrrrr:aaaaaa:xx:dddddd:xx LB_OFF^1234FF:15:21:–1:32:0

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
LOG_OFF_1553_SIGNAL LB_OFF^iiiiii LB_OFF^1234FF
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
460 von/of: 662
DISPLAY_ON_1553 LB_DSP_ON^iiiiii:rrrrrr:aaaaaa:xx:dddddd:xx LB_DSP_ON^1234FF:15:21:–1:32:0
DISPLAY_ON_1553_SIGNAL LB_DSP_ON^iiiiii LB_DSP_ON^1234FF
DISPLAY_OFF_1553 LB_DSP_OFF^iiiiii:rrrrrr:aaaaaa:xx:dddddd:xx LB_DSP_OFF^1234FF:15:21:–1:32:0
DISPLAY_OFF_1553_SIGNAL LB_DSP_OFF^iiiiii LB_DSP_OFF^1234FF
IOSU_LOG_ON SC_ON^iiiiii:tttttt:cccccc SC_ON^1234FF:11:29
IOSU_LOG_ON_CARD SC_ON^iiiiii SC_ON^1234FF
IOSU_LOG_ON_SIGNAL SC_ON^iiiiii SC_ON^1234FF
IOSU_LOG_OFF SC_OFF^iiiiii:tttttt:cccccc SC_OFF^1234FF:11:29
IOSU_LOG_OFF_CARD SC_OFF^iiiiii SC_OFF^1234FF
IOSU_LOG_OFF_SIGNAL SC_OFF^iiiiii SC_OFF^1234FF
IOSU_DISPLAY_ON SC_DSP_ON^iiiiii:tttttt:cccccc SC_DSP_ON^1234FF:11:29
IOSU_DISPLAY_ON_CARD SC_DSP_ON^iiiiii SC_DSP_ON^1234FF
IOSU_DISPLAY_ON_SIGNAL SC_DSP_ON^iiiiii SC_DSP_ON^1234FF
IOSU_DISPLAY_OFF SC_DSP_OFF^iiiiii:tttttt:cccccc SC_DSP_OFF^1234FF:11:29
IOSU_DISPLAY_OFF_CARD SC_DSP_OFF^iiiiii SC_DSP_OFF^1234FF
IOSU_DISPLAY_OFF_SIGNAL SC_DSP_OFF^iiiiii SC_DSP_OFF^1234FF
HRDL_LOG_ON HRDL_ON^iiiiii:pppppp,^pppppp HRDL_ON^1234FF:11,^2047
HRDL_LOG_OFF HRDL_OFF^iiiiii:pppppp,^pppppp HRDL_OFF^1234FF:11,^2047
SERIAL_LOG_ON SRL_ON^iiiiii,^xx SRL_ON^1234FF,^1
SERIAL_LOG_OFF SRL_OFF^iiiiii,^xx SRL_OFF^1234FF,^1
SERIAL_DISPLAY_ON SRL_DSP_ON^iiiiii,^xx SRL_DSP_ON^1234FF,^1
SERIAL_DISPLAY_OFF SRL_DSP_OFF^iiiiii,^xx SRL_DSP_OFF^1234FF,^1

Space Infrastructure
7.10 Onboard Commands and Responses
7.10.1 Software Commands (SWOP_Command)
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
Software Commands (SWOP_Commands) are sent as CCSDS command packets.
7.10.1.1 CCSDS Header for Software Commands
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
461 von/of: 662
The CCSDS packet structure is defined in applicable document TBD (SSP42001) sections 3.6.2.2.2.2
and 3.6.3.2.1.1).
Primary Header:
CP–PDU Version: : ’000’ B
CP–PDU Type : Most Significant Bit of APID
Remark: ’0’ B for System Commands,
’1’ B for Payload Commands
CP–PDU Secondary Header Flag : ’1’ B
CP–PDU Application ID : Least significant Bits of APID as defined for Ground
CCSDS End Point to Onboard CCSDS End Point
CP–PDU Sequence Flags: : ’11’B
CP–PDU Sequence Count : 0 – 16383
CP–PDU Packet Length: : Packet Length (Number of Octets) – 7
i.e. packet length excluding primary header – 1
Secondary Header:
Time : CCSDS unsegmented time code
All 0 if Time Id = ’00’ B
Time Id : ’00’B (Time field not used) or
’01’B (Time of packet generation)
Checksum Indicator : ’1’B (Checksum Present)
Packet Type: : ’1001’B System Command or
’1000’B Essential Command or
’1010’B Payload Command
Packet ID: : SID of SWOP_Command

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
462 von/of: 662
7.10.1.2 CCSDS Data Field for Software Commands
All actual ’IN’ parameters have be encoded into the data field in the same sequence as defined by
formal specification of the software command.
The following transfer syntax rules have to be regarded:
– Most significant bit first, least significant bit last
– most significant byte first, least significant byte last
– Values of parameters shall be encoded according to the follwing mapping:
INTEGER 4 Bytes, MSB of most significant Byte is sign bit
REAL IEEE 754 format single precision
TIME CCSDS unsegmented time code (5 byte) to be
followed by byte with value 0.
String_Type 2 bytes for length followed by number of
bytes (characters) as defined by length. For odd
length byte with value 0 has to follow without
changing the length of the string.
Statecode_Type 8 bytes containing the statecode literal (ASCII)
Pathname_Type 4 bytes containing the SID of the actual enditem
For ’OUT’ parameters the same rules apply (see next section 7.10.1.3).
7.10.1.3 Response Packet
After the onboard execution of the command , exactly one response packet is returned.
The structure for response packet can be copied from higher level ICDs (SSMB to APM).
7.10.1.3.1 CCSDS Header
Primary Header:
CP–PDU Version: : ’000’ B
CP–PDU Type : Most Significant Bit of APID
Remark: ’0’ B for System Command Responses,
’1’ B for Payload CommandResponses
CP–PDU Secondary Header Flag : ’1’ B
CP–PDU Application ID : Least significant Bits of APID as defined for Onboard
CCSDS End Point to Ground CCSDS End Point
CP–PDU Sequence Flags: : ’11’B
CP–PDU Sequence Count : 0 – 16383
CP–PDU Packet Length: : Packet Length (Number of Octets) – 7
i.e. packet length excluding primary header – 1
Secondary Header:
Time : CCSDS unsegmented Time Code
All 0 if Time Id = ’00’ B
Time Id : ’00’B (time field not used)
’01’B (Time of generation i.e. Time of Acknowledge at
onboard End Point
Checksum Indicator : ’1’B (Checksum Present)
Packet Type: : ’1100’B (Command Response)
Packet ID: : SID of the response packet which is related to
the SWOP_command
in CGS: defined via response packet reference

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
463 von/of: 662
7.10.1.3.2 CCSDS Data Field
The response packet contains the following items starting at the first byte of the data field:
Transaction ID: Primary Header of uplinked command without length field (4 bytes)
Result: Enumeration (16 bit) indicating the success of the command
Success without any problems: 0
Success but sequence count anomaly: 1
No Success: Not authorized: 2
No Success: Unknown Command 3
No Success: Not valid command 4
No Success: Parameters not complete 5
No Success: Parameters not valid 6
No Success: Sequence Count repetition 7
No Success: Sequence Count Mismatch 8
No Success: Checksum Error 9
No success: Two stage buffer full 10
No success: Two stage command source mismatch 11
No Success: Other Reasons 63
No Success: specific reasons 64 .. 255
Return Parameter: Parameter returned by the onboard system.
Parameter Encoding: The transfer syntax for ’OUT’ parameters con–
tained in the response packet is the same as for the command packets.

Space Infrastructure
7.10.2 FLAP Execution Requests
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
464 von/of: 662
Execution Requests for Flight Automated Procedures (FLAP) are sent as command packets. The
structure for command packets can be copied from higher level ICDs (SSMB to APM).
7.10.2.1 CCSDS Header for FLAP Execution Requests
Primary Header:
CP–PDU Version: : ’000’ B
CP–PDU Type : Most Significant Bit of APID
Remark: ’0’ B for System Commands,
’1’ B for Payload Commands
CP–PDU Secondary Header Flag : ’1’ B
CP–PDU Application ID : Least significant Bits of APID as defined for Ground
CCSDS End Point to Onboard CCSDS End Point
CP–PDU Sequence Flags: : ’11’B
CP–PDU Sequence Count : 0 – 16383
CP–PDU Packet Length: : Packet Length (Number of Octets) – 7
i.e. packet length excluding primary header – 1
Secondary Header:
Time : CCSDS unsegmented time code
All 0 if Time Id = ’00’ B
Time Id : ’00’B (Time field not used) or
’01’B (Time of packet generation)
Checksum Indicator : ’1’B (Checksum Present)
Packet Type: : ’1001’B (System Command) or
’1010’B (Payload Command)
Packet ID: : SID of Reference to SWOP_Command defined
for FLAP execution as defined in section TBD of
the ICD TBD
Note: In CGS: defined via Configuration File
7.10.2.2 CCSDS Data Field for FLAP Execution Requests
The data field contains the following parameter in the following sequence:
1. FLAP identifier SID (4 bytes)
2. time_tag Time (CCSDS unsegemented Time Code) to be
followed by byte with value 0.
3. Priority of FLAP integer (4 bytes)
4. onboard execution node SID (4 bytes)
5. ’IN’ parameters of FLAP
All actual ’IN’ parameters of the FLAP have to be encoded into the data field as defined in section 7.16
Parameter Encoding using the external scheme.
The following transfer syntax rules have to be regarded:
– Most significant bit first, least significant bit last
– most significant byte first, least significant byte last

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
465 von/of: 662
7.10.2.3 Response Packet for FLAP Execution Requests
After the onboard execution of the FLAP command , exactly one response packet is returned.
The structure for response packet can be copied from higher level ICDs (SSMB to APM).
7.10.2.3.1 CCSDS Header
Primary Header:
CP–PDU Version: : ’000’ B
CP–PDU Type : Most Significant Bit of APID
Remark: ’0’ B for System Command Responses,
’1’ B for Payload CommandResponses
CP–PDU Secondary Header Flag : ’1’ B
CP–PDU Application ID : Least significant Bits of APID as defined for Onboard
CCSDS End Point to Ground CCSDS End Point
CP–PDU Sequence Flags: : ’11’B
CP–PDU Sequence Count : 0 – 16383
CP–PDU Packet Length: : Packet Length (Number of Octets) – 7
i.e. packet length excluding primary header – 1
Secondary Header:
Time : CCSDS unsegmented Time Code
All 0 if Time Id = ’00’ B
Time Id : ’00’B (time field not used)
’01’B (Time of generation i.e. Time of Acknowledge at
onboard End Point
Checksum Indicator : ’1’B (Checksum Present)
Packet Type: : ’1100’B (Command Response)
Packet ID: : SID of the response packet which is related to
the SWOP_command
in CGS: defined via response packet reference
7.10.2.3.2 CCSDS Data Field
The response packet contains the following items starting at the first byte of the data field:
Transaction ID: Primary Header of uplinked command without length field (4 bytes)
Result: Enumeration (16 bit) indicating the success of the command
Success without any problems: 0
Success but sequence count anomaly: 1
No Success: Not authorized: 2
No Success: Unknown Command 3
No Success: Not valid command 4
No Success: Parameters not complete 5
No Success: Parameters not valid 6
No Success: Sequence Count repetition 7
No Success: Sequence Count Mismatch 8
No Success: Checksum Error 9
No success: Two stage buffer full 10
No success: Two stage command source mismatch 11
No Success: Other Reasons 63
No Success: specific reasons 64 .. 255
FLAP_ID: Integer identifying the FLAP executed.
FLAP_status: integer indicating the success of the FLAP execution

Space Infrastructure
7.11 DBS Types and Constants Definitions
Informal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
466 von/of: 662
A same set of data types are used in the various procedural interfaces provided by the DBS product. In order
to ensure the consistency of their definition and usage through all the interfaces, they are grouped and defined
once, in the current section.
They are ”basic” data types and constants (like numbers, strings, enumerations...) which are accessible directly.
They constitute a type pool and are grouped into a set of Ada packages, according to their nature.
The usage of the basic data types is simple. The desired variable has to be declared with the desired type in the
piece of software which will use it. The access to the content of the variable is done directly, by knowledge of
its Ada structure.
The DBS_DEFINITIONS package contains type and constant definitions that are :
. specific of DBS, i.e. not used or shared by several CGS products,
. common in DBS, i.e. used or shared by several DBS provided services,
. of general nature, i.e. not specific to any of these services.
The DBS main type definitions are described hereafter.
• DBS Return Status
A type is defined for DBS return status and is used to report back to the calling application the result
of any DBS called operation.
• DBS Files
Some types are defined to manage the various files containing the test/simulation/evaluation results data
:
– raw data files contain data generated during test or simulation execution;
– result files contain data generated during evaluation activity.
• Sessions
The package DBS_DEFINITIONS provides two types of test sessions :
– test execution session, which is a collection of configuration information, files and data generated
during a particular test and limited by a time frame;
– test evaluation session, which is a collection of evaluation result files.
• Logging Events
Some types are defined to access logged events like :
– log events which are asynchronous events happening during test/simulation execution;
– user events which are additional time markers inserted by test operators during test/simulation
execution.
• Engineering Values
Some types are defined to access engineering values (calibrated data) logged in the TRDB during test/simulation
execution.
• Print Types
Several types are provided to manage printers and print queue.
• DBS Housekeeping Data

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
467 von/of: 662
A set of types represent the current state of some critical parts of DBS, like magnetic disk, database, etc.
• User Result Table
Types are provided for user result tables which are tables created by test operators, to log messages or
binary strings during test/simulation execution.
• Data Allocation
Some types are available to allow allocation of selected part of the TRDB, for further evaluation activity.
• Final Archiving (FA)
Some types are provided to support FA activities.

Space Infrastructure
Formal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
468 von/of: 662
––
–– DBS_DEFINITIONS
––
––****************************************************************************
––ABSTRACT––
––
–– This package contains the type and constant definitions provided for the
–– usage of the DBS RPI and DBS
API.––*–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––IDEN -
TIFICATION––
–– PROJECT NAME : VICOS
–– PRODUCT NAME : DBS
–– CI–NUMBER : 1216 863
–– OBJECT NAME : DBS_DEFINITIONS
––*–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––CONTENTS––
–– COMPILER : Sun / Verdix & HP / Alsys
–– LANGUAGE : Ada
–– SPECIAL CONTENTS:
–– CHANGE HISTORY
––
–– CGS V4.4 ICD Change 13.04.2000, W.Tammen:
–– introduced new values for enumeration type T_DBS_ERROR:
–– INTERRUPTED_BY_USER and CLOSE_SESSION_IN_PROGRESS
–– according to COL–RIBRE–IRN–CGS–8106
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– CGS V4.2 ICD Change 27.07.99, W.Tammen:
–– introduced new values for enumeration type T_DBS_ERROR:
–– ADT_EVENT_INVALID_NAME, ADT_EVENT_FILE_EXISTS and
–– ADT_EVENT_ERROR_ACCESSING_FILE
–– according to COL–RIBRE–IRN–CGS–8078
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– CGS V4.2 ICD Change 29.04.99, W.Tammen:
–– introduced new value END_OF_LIST for enumeration type
–– T_DBS_ERROR according to COL–RIBRE–IRN–CGS–8059
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– CGS 4.2 ICD Change (acc. COL–RIBRE–IRN–CGS–8039, 07/07/1997)
–– created by: P.Athmann, DASA
–– Include representation clauses for Printer Information Types
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– CGS V4.1 ICD Change (acc. COL–RIBRE–IRN–CGS–7009c, 07/07/1997)
–– created by: Uwe Hohnhorst, DASA, RIO63
–– comments:
–– 1) Changed T_DBS_ERROR with ref. COL–SBI–SPR–137, 18.04.1997
–– 2) Changed MAX_APPLICATION_NUMBER = 64
–– 3) Reintroduction of User Result Files in T_DATA_TYPE
–– 4) Representation clauses for T_TRDB_INFO and
–– T_TABLESPACE_RATIO’SIZE
–– 5) T_LIST_OF_CCU_INFORMATION deleted,
–– T_LIST_OF_CCU_INFORMATION_L added
–– 6) Clarification of meaning of ANY in T_MODE_SELECTION
–– 7) Added FA_SAS_ALREADY_RUNNING, CANNOT_START_FA_SAS to
–– T_DBS_ERROR
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– CGS V4.0/V4.1 ICD Change (acc. COL–RIBRE–IRN–CGS–6027b, 25/03/1997)
–– created by: Uwe Hohnhorst, DASA, RIT11
–– comments:
–– 1) FA SAS Dialog related types added,

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–– 2) Return stati in type T_DBS_ERROR adapted,
–– 3) Removal of User Result Files in T_DATA_TYPE,
–– 4) CCU Information related types added,
–– 5) T_TRDB_INFO changed (removal of FA_STATUS).
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V4.10 at Spacebel Informatique, Brussels
–– creator: bcharlie (on host asimov)
–– creation date: 15.03.96 14:31:12
–– comment:
–– USER EVENT log type replaced, SPR – 2146
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V4.5 at Spacebel Informatique, Brussels
–– creator: bcharlie (on host ariane5)
–– creation date: 25.07.95 11:56:34
–– comment:
–– Move T_EVENT definition to Vicos_definitions
–– definition, change User Event definitions.
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V4.4 at Spacebel Informatique, Brussels
–– creator: bcharlie (on host moon)
–– creation date: 24.07.95 17:44:14
–– comment:
–– Move from VICOS_CALENDAR to CGS_CALENDAR
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V4.3 at Spacebel Informatique, Brussels
–– creator: cm_admin (on host moon)
–– creation date: 06.07.95 09:44:13
–– comment:
–– Replace the Vicos_Definitions type T_VICOS_MODES_AND_STATI
–– by the new T_VICOS_MODE for selection of sessions and
–– Exec session info. (Cfr. PIRN 3023/E)
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V4.7 at Central Repository V2.0 (ariane5)
–– creator: bcharlie (on host ariane5)
–– creation date: 07.06.95 14:09:00
–– comment:
–– Add types T_TIME_TYPE and T_TIME_ORDERING,
–– modify type T_ENG_VAL_SEL_CRIT by adding
–– the fields TIME_FRAME_TYPE and LIST_ORDER.
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V4.6 at Central Repository V2.0 (ariane5)
–– creator: bcharlie (on host ariane5)
–– creation date: 10.03.95 14:02:19
–– comment:
–– Modify Eval Session Selection criteria
–– type to add array of boolean for Location.
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V4.5 at Central Repository V2.0 (ariane5)
–– creator: bcharlie (on host ariane5)
–– creation date: 10.03.95 09:18:21
–– comment:
–– Change in test execution related types.
–– Array of boolean added for Mode selection, Location
–– selection and execution state selection.
–– Type T_EXEC_SESSION_SEL_CRIT modified to include
–– these types.
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V4.4 at Central Repository V2.0 (ariane5)
–– creator: bcharlie (on host ariane5)
–– creation date: 01.02.95 16:02:49
–– comment:
–– modified by R.Smillie 1/2/95 in accordance with
–– COL–RIBRE–IRN–CGS–3023 (T_EVENT : TIME_TAG_LT, TIME_TAG_SMT).
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
469 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–– V4.3 at Central Repository V2.0 (ariane5)
–– creator: bcharlie (on host ariane5)
–– creation date: 31.01.95 14:41:49
–– comment:
–– Add the FA SAS status FA_DEVICE_NOT_ALLOCATED.
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V4.2 at Central Repository V2.0 (ariane5)
–– creator: bcharlie (on host ariane5)
–– creation date: 16.01.95 12:15:54
–– comment:
–– add FA_LIST_NOT_FOUND, FA_MMI_REQUEST_CANCELLED,
–– FA_UNIX_PROBLEM Status.
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V4.1 at SBI ; DBS development
–– creator: bcharlie (on host ariane5)
–– creation date: 08.11.94 09:43:42
–– Remove error status related to URT,
–– add status NO_PRINTER_AVAILABLE,
–– change comment for Oracle wildcard,
–– add status FA_NOT_ENOUGH_SPACE,
–– remove SYNOPTIC in Result File Types,
–– remove User Result related types,
–– add FA_RESERVED_FOR_AUTO_ARCH,
–– add User Event field values, add FA_MMI_TIME_OUT.
––
–– END HISTORY
––****************************************************************************
––
––
with VICOS_DEFINITIONS;
with CGS_CALENDAR;
with MPS_DEFINITIONS;
with ADT_RAW_VALUE;
with ADT_ENGINEERING_VALUE;
with VICOS_LIST;
package DBS_DEFINITIONS is
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Return FA SAS request for dialog
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
type T_DBS_FA_DISK_STATUS is (
SUCCESS,
FA_REQ_FOR_AUTO_ARCHIVE_DISK,
FA_REQ_FOR_MANUAL_ARCHIVE_DISK,
FA_REQ_FOR_EXPORT_DISK,
FA_REQ_FOR_IMPORT_DISK,
FA_REQ_FOR_RETRIEVE_DISK,
FA_REQ_FOR_NEW_DISK);
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
470 von/of: 662
–– SUCCESS : Appropriate disk has been already inserted
–– FA_REQ_FOR_AUTO_ARCHIVE_DISK : request from FA SAS to insert an appropriate disk
for AUTOMATIC ARCHIVING
–– FA_REQ_FOR_MANUAL_ARCHIVE_DISK : request from FA SAS to insert an appropriate disk
for MANUAL ARCHIVING
–– FA_REQ_FOR_EXPORT_DISK : request from FA SAS to insert an appropriate disk
for EXPORT
–– FA_REQ_FOR_IMPORT_DISK : request from FA SAS to insert an appropriate disk
for IMPORT
–– FA_REQ_FOR_RETRIEVE_DISK : request from FA SAS to insert an appropriate disk
for RETRIEVE
–– FA_REQ_FOR_NEW_DISK : request from FA SAS to insert a new disk for
any
–– write operations on FA (see above, e.g. Export,
Archiving)
subtype T_DBS_DEVICE_ID is positive range 1 .. 2;

Space Infrastructure
type T_DBS_FA_DIALOG is
record
DEVICE_ID : T_DBS_DEVICE_ID;
FA_DISK_STATUS : T_DBS_FA_DISK_STATUS;
end record;
–– DEVICE_ID is the allocated device for requested operation.
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Return status type
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
type T_DBS_ERROR is (
OK,
–– The operation has been successfully performed
CONNECT_PROBLEM,
–– Connection failed
INIT_PROBLEM,
–– Initialisation of communication from local to central DBS
–– failed (i.e. failed to establish connection to CGS Product).
DBS_STOPPED,
–– Local DBS is stopped, no more operation allowed.
DBS_NOT_CONNECTED,
–– Local DBS disconnected from communication services.
DISCONNECT_PROBLEM,
–– Disconnection failed.
SESSION_NOT_FOUND,
–– The session name is unknown.
INVALID_SESSION_NAME,
–– The session name is syntactically incorrect.
INVALID_APPLICATION_NAME,
–– The application TSCV_xx may not participate
–– into an Execution session.
ALREADY_PARTICIPATING,
–– Some application names already participate to open session.
AUTO_ARCH_ALREADY_USED,
–– Two sessions are already open with automatic archiving.
MAX_SESSION_REACHED,
–– Maximum of allowed open sessions is reached, init refused.
FA_DRIVE_NOT_AVAILABLE,
–– Fa drive requested for Automatic Archiving is not available.
EXISTING_SESSION,
–– The session name is not unique.
SESSION_IS_OPEN,
–– The session is open.
SESSION_NOT_OPEN,
–– No session is open.
SESSION_IS_USED,
–– The test execution or evaluation session is used for
–– an FA operation or for deleteion.
SESSION_IS_ALLOCATED,
–– The test execution or evaluation session is allocated
–– to an evaluation user.
SESSION_IS_ARCHIVED,
–– Session is archived.
SESSION_NOT_ARCHIVED,
–– Session has not been archived before.
SESSION_IS_EMPTY,
–– Session is empty, archiving/exporting is refused.
SESSION_IS_ONLINE,
–– Session is online.
RETRIEVING_NOT_AUTHORISED,
–– Session data already retrieved by another user.
DATA_ALREADY_ONLINE,
–– The selected data is already online.
DATA_PARTIALLY_ONLINE,
–– Selected data is partially online, exporting is refused.
DATA_NOT_ONLINE,
–– The selected data is not online.
INACCESSIBLE_FILES,
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
471 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
472 von/of: 662
–– Storage of files fails, files remain on local node.
EXISTING_FILE,
–– The file to store in the Test Result Database is already
–– referenced in the Test Result Database (same name, same
–– test session, and for raw data file same test node).
FILE_SYSTEM_FULL,
–– Not enough space to store the file.
FILE_NOT_FOUND,
–– The given file is not found.
NOT_CONNECTED_TO_EVAL,
–– The user is not connected as evaluation user.
DATA_NOT_FOUND,
–– The selected data is not found.
EXISTING_USER,
–– Evaluation user already connected.
BAD_SELECTION_CRITERIA,
–– Selection criteria is null.
POOL_SATURATED,
–– The event buffer pool is saturated.
TABLE_SPACE_FULL,
–– Not enough space found in the table space for loading
–– selected events.
PRINTER_ERROR,
–– Cannot perform printer operation.
–– Details are to be provided in an separate error message.
–– UNKNOWN_PRINTER,
–– The printer name is unknown.
PRINTING_REROUTED,
–– The requested print has been rerouted on the other printer.
–– FILE_NOT_PRINTABLE,
–– The format of the file is not standard
––(directory file, ..).
–– SPOOLER_DISACTIVATED,
–– The spooler is not active.
–– FILE_IS_EMPTY,
–– File to print is empty, nothing will be printed
PRINTER_NOT_DEFINED,
–– Printer environment variable not set.
NO_PRINTER_AVAILABLE,
–– No printer is available for the printing.
CANCEL_NOT_AUTHORISED,
–– Not privileged to cancel the printing job.
UNKNOWN_ERROR,
–– Detected problem is not known.
EXISTING_FA_JOB,
–– Fa jobs still in progress, stopping is refused.
JOB_CANCELLED,
–– FA job has been cancelled.
FA_MEDIUM_NOT_AVAILABLE,
–– The requested FA medium has not been mounted.
–– FA_NOT_ENOUGH_SPACE,
–– *–– The FA medium cannot receive the exported data, the free space
–– *–– left is too small.
–– This is not a error, this shall imply a dialog request with the user, for insertion
of a new disk
FA_INTERNAL_PROBLEM,
–– FA SAS reports internal error.
FA_UNIX_PROBLEM,
–– FA SAS reports Unix error.
FA_RESERVED_FOR_AUTO_ARCH,
–– The selected FA device is reserved for Automatic Archiving,
–– operations not related with Auto Arch are refused. (but read of data from
the FA for
–– the open session is possible).
FA_MMI_TIME_OUT,
–– The Final Archive Operator didn’t answer to an FA request
–– within proper delay.
FA_MMI_REQUEST_CANCELLED,
–– The Final Archive Operator cancelled an FA request
–– during the processing of the operation.
FA_LIST_NOT_FOUND,
–– The list of files (trees) to Archive, Export or Retrieve is
–– not found or not accessible.

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
473 von/of: 662
FA_DEVICE_NOT_ALLOCATED,
–– A request to Archive, Retrieve, Export or Import is
–– done as the device is not allocated for that purpose.
–– Ask for Device allocation first.
ACTIVE_FA_JOB,
–– FA job is ACTIVE and cannot be removed.
FA_SAS_NOT_RUNNING,
–– The FA SAS has to run for this request.
LIST_OVERFLOW,
–– Not enough dynamic memory space for the list.
INDEX_ERROR,
–– the index is greater than the number of elements or is null.
LIST_NULL,
–– There are no more selected logging event or engineering values.
LIST_NOT_NULL,
–– the list already contains data: the CLEAR
–– procedure shall be called before.
END_OF_LIST,
–– the end of the list has been reached
ADT_EVENT_INVALID_NAME,
–– the specified name of the adt_event_result file is too long
–– ( > 256 characters)
ADT_EVENT_FILE_EXISTS,
–– the adt_event_result file to be created already exists
ADT_EVENT_ERROR_ACCESSING_FILE,
–– general adt_event_result error
INTERRUPTED_BY_USER,
–– GENERATE_EVENT_LIST interrupted manually by user
CLOSE_SESSION_IN_PROGRESS,
–– this status is returned by DBS on command
–– DBS_RPI.CLOSE_EXECUTION_SESSION if there are remaining
–– event–/EVL– or archive–files to be handled
COMMS_TIME_OUT,
–– Communictaion time out occurs.
INSUFFICIENT_PRIVILEGE,
–– User not privileged for the requested operation.
UNKNOWN_PRIVILEGE,
–– VICOS privilege given is not defined in the file
–– dbs_privilege_file.def, impossible to map into TRDB privileges.
CANNOT_START_FA_SAS,
–– Unable to start the FA_SAS.
FA_SAS_ALREADY_RUNNING,
–– The FA SAS is already running.
DBS_ORACLE_PROBLEM,
–– Oracle problems.
DBS_UNIX_PROBLEM,
–– Unix problems (invalid access rights, directory not found, .. )
DBS_INTERNAL_PROBLEM,
–– Unexpected exception has been raised.
DBS_COMMUNICATION_PROBLEM);
–– DBS has lost communication with Central (e.g. DBS central not running).
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Time related types
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
type T_TIME_RECORD is
record
BEGIN_DATE : CGS_CALENDAR.CGS_DATE_AND_TIME;
END_DATE : CGS_CALENDAR.CGS_DATE_AND_TIME;
end record;
–– Note: variables of this type define time frames. In case the
–– content of the variables is not consistent (begin_date is older
–– than end_date), the result of functions using the variables can be
–– erroneous.
–– Note: if the BEGIN_DATE and END_DATE are CGS_CALENDAR.NULL_DATE_AND_TIME
–– for retrieving information from the Test Result Database, DBS will
–– interpret the request as ”without time constraint” (possibly with
–– other constraints like test session name, ...).

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
NULL_TIME_RECORD : constant T_TIME_RECORD
:= (BEGIN_DATE => CGS_CALENDAR.NULL_DATE_AND_TIME,
END_DATE => CGS_CALENDAR.NULL_DATE_AND_TIME);
–– This constant can be used for asking for data without time
–– constraints
type T_TIME_TYPE is (LT, SMT);
–– This type specifies kind of time used:
–– Local Time or Simulated Mission Time.
––
type T_TIME_ORDERING is (LT, SMT);
–– This type specifies kind of time used to order lists:
–– Local Time or Simulated Mission Time.
––
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Test Session Name Types
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
subtype T_TEST_SESSION_NAME is VICOS_DEFINITIONS.T_NAME_STRING;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
474 von/of: 662
–– T_TEST_SESSION_NAME: Name of the test session to be maintained in TRDB
–– for the given test. The test session name can consist of capital letters,
–– digits and underscores only, and can have a length of up to 20 characters maximum.
–– The test session name has to begin with a capital letter. Example: IF_TEST_3.
NULL_TEST_SESSION_NAME : constant T_TEST_SESSION_NAME
:= VICOS_DEFINITIONS.EMPTY_NAME_STRING;
MAX_SELECTED_SESSIONS : constant POSITIVE := 11;
subtype T_SELECTED_SESSION_RANGE is INTEGER range 1..MAX_SELECTED_SESSIONS;
type T_SELECTED_SESSIONS is
array (T_SELECTED_SESSION_RANGE range ) of T_TEST_SESSION_NAME;
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Type to describe the owner
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
MAX_USER_NAME : constant := 32;
subtype T_USER_NAME is STRING (1 .. MAX_USER_NAME);
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– File Name Types
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
subtype T_FILENAME_LENGTH is INTEGER
range 0 .. VICOS_DEFINITIONS.MAX_LENGTH_OF_FILE_NAME;
type T_FILENAME (LENGTH: T_FILENAME_LENGTH := 0) is
record
NAME : STRING (1..LENGTH);
end record;
FINAL_ARCHIVE_PATH : constant STRING := ”FINAL_ARCHIVE/”;
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Files characteristics types
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
type T_RESULT_TYPE is
(GENERAL_FILE,
DATA_SET,

Space Infrastructure
REPORT,
STATISTIC,
EVENT_LIST,
DATA_LIST,
RAW_DATA_DUMP,
GRAPH);
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
type T_RAW_DATA_FILE_INFO is
record
SESSION : T_TEST_SESSION_NAME;
FILE_NAME : T_FILENAME;
PRODUCER : VICOS_DEFINITIONS.T_APPLICATION_NAME;
DATA_TIME_LT : T_TIME_RECORD;
DATA_TIME_SMT : T_TIME_RECORD;
end record;
type T_RESULT_FILE_INFO is
record
SESSION : T_TEST_SESSION_NAME;
RESULT_TYPE : T_RESULT_TYPE;
FILE_NAME : T_FILENAME;
PRODUCER : VICOS_DEFINITIONS.T_APPLICATION_NAME;
FILE_TRANSFER_TIME: CGS_CALENDAR.CGS_DATE_AND_TIME;
end record;
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Test Execution Sessions types
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
DEFAULT_TEST_SESSION : constant T_TEST_SESSION_NAME
:= (THE_STRING => ”DEFAULT_TEST_SESSION”, LENGTH => 20);
ORACLE_WILDCARD : constant CHARACTER := ’%’;
subtype T_MODE_SELECTION is VICOS_DEFINITIONS.T_VICOS_MODE
range VICOS_DEFINITIONS.NORMAL .. VICOS_DEFINITIONS.ANY_MODE;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
475 von/of: 662
–– T_MODE_SELECTION can be either:
–– NORMAL (all test nodes in normal mode),
–– SIMULATION (all test nodes in simulation mode),
–– REPLAY (all test nodes in replay mode) or
–– ANY (test nodes are running in any mixed mode configuration).
–– For data retrieval (e.g. through TEV or TSCV):
–– NORMAL selection will retrieve all data belonging to NORMAL and ANY mode,
–– SIMULATION selection will retrieve all data belonging to SIMULATION and ANY
mode,
–– REPLAY selection will retrieve all data belonging to REPLAY and ANY mode.
–– ANY selection will retrieve all data belonging to ANY mode only.
subtype T_PATHNAME_REFERENCE_LENGTH is INTEGER
range 0 .. VICOS_DEFINITIONS.MAX_LENGTH_OF_DB_PATHNAME;
type T_PATHNAME_REFERENCE (LENGTH: T_PATHNAME_REFERENCE_LENGTH := 0) is
record
NAME : STRING (1..LENGTH);
end record;
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Return List of CCUs from default test session
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
type T_CCU_INFORMATION is
record
TIME_TAG : CGS_CALENDAR.CGS_DATE_AND_TIME;
ELEMENT_CONFIGURATION : MPS_DEFINITIONS.T_ELEMENT_CONFIGURATION_NAME;
MISSION_NAME : MPS_DEFINITIONS.T_MISSION_NAME;
SYSTEM_TREE_VERSION : MPS_DEFINITIONS.T_VERSION_NUMBER;
CCU_SYSTEM_TREE_PATHNAME : T_PATHNAME_REFERENCE;
CCU_NAME : MPS_DEFINITIONS.T_CONFIGURATION_NAME;

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
CCU_VERSION : MPS_DEFINITIONS.T_VERSION;
end record;
package P_LIST_OF_CCU_INFORMATION is new VICOS_LIST(T_CCU_INFORMATION);
subtype T_LIST_OF_CCU_INFORMATION_L is P_LIST_OF_CCU_INFORMATION.LIST;
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
type T_EXECUTION_STATE is
(OPEN,
NORMALLY_CLOSED,
ABORTED,
UNDEFINED);
type T_LOCATION is
(ONLINE_DISC,
ONLINE_FA,
FINAL_ARCHIVE,
UNDEFINED);
type T_LIST_ORDERING is
(ALPHABETICAL, CHRONOLOGICAL);
type T_SELECTED_MODE is array (T_MODE_SELECTION) of BOOLEAN;
type T_SELECTED_EXECUTION_STATE is array (T_EXECUTION_STATE) of BOOLEAN;
type T_SELECTED_LOCATION is array (T_LOCATION) of BOOLEAN;
NULL_MODE_SELECTION : constant T_SELECTED_MODE := (others => false);
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
476 von/of: 662
NULL_EXECUTION_STATE_SELECTION : constant T_SELECTED_EXECUTION_STATE := (others => false);
NULL_LOCATION_SELECTION : constant T_SELECTED_LOCATION := (others => false);
type T_EXEC_SESSION_SEL_CRIT is
record
NAME_PATTERN : T_TEST_SESSION_NAME := VICOS_DEFINITIONS.EMPTY_NAME_STRING;
SEL_MODE : T_SELECTED_MODE := NULL_MODE_SELECTION;
SEL_TIME_FRAME : T_TIME_RECORD := NULL_TIME_RECORD;
ELEMENT_CONFIGURATION : MPS_DEFINITIONS.T_ELEMENT_CONFIGURATION_NAME :=
(others => ’ ’);
MISSION_NAME : MPS_DEFINITIONS.T_MISSION_NAME := (others => ’ ’);
SYSTEM_TREE_VERSION : MPS_DEFINITIONS.T_VERSION_NUMBER := 0;
CCU_SYSTEM_TREE_PATHNAME: T_PATHNAME_REFERENCE;
CCU_NAME : MPS_DEFINITIONS.T_CONFIGURATION_NAME:= (others => ’
’);
CCU_VERSION : MPS_DEFINITIONS.T_VERSION:=
MPS_DEFINITIONS.NO_VERSION;
EXECUTION_STATE : T_SELECTED_EXECUTION_STATE :=
NULL_EXECUTION_STATE_SELECTION;
LOCATION : T_SELECTED_LOCATION := NULL_LOCATION_SELECTION;
end record;
–– Definition of session information selection.
–– Each field of the record is predefined to a null value. When a
–– field is not a part of the selection criteria, its value is thus
–– null. For the non null fields, the selection criteria is defined
–– with an AND relation between the fields. Note that the fields
–– ELEMENT_CONFIGURATION, MISSION_NAME, SYSTEM_TREE_VERSION,
–– CCU_SYSTEM_TREE_PATHNAME, CCU_NAME and CCU_VERSION will
–– be either all set to a certain value or all set to null values.
–– NAME_PATTERN field may contain several DBS_DEFINITIONS.ORACLE_WILDCARD’s.
type T_ARCHIVE_MODUS is
(NO_FINAL_ARCHIVE,
WITH_FINAL_ARCHIVE);
MAX_APPLICATION_NUMBER : constant := 64;
subtype T_APPLICATION_RANGE is POSITIVE range 1 .. MAX_APPLICATION_NUMBER;
type T_PARTICIPATING_APPLICATIONS is array (T_APPLICATION_RANGE range ) of
VICOS_DEFINITIONS.T_APPLICATION_NAME;
MAX_SESSION_INFO_TEXT : constant := 80;

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
subtype T_SESSION_INFO_TEXT is STRING (1 .. MAX_SESSION_INFO_TEXT);
type T_EXECUTION_SESSION_INFO is
record
ARCHIVE_MODUS : T_ARCHIVE_MODUS;
EXECUTION_STATE : T_EXECUTION_STATE;
LOCATION : T_LOCATION;
TEST_MODE : T_MODE_SELECTION;
NAME : T_TEST_SESSION_NAME;
BEGIN_TIME_LT : CGS_CALENDAR.CGS_DATE_AND_TIME;
END_TIME_LT : CGS_CALENDAR.CGS_DATE_AND_TIME;
ELEMENT_CONFIGURATION : MPS_DEFINITIONS.T_ELEMENT_CONFIGURATION_NAME;
MISSION_NAME : MPS_DEFINITIONS.T_MISSION_NAME;
SYSTEM_TREE_VERSION : MPS_DEFINITIONS.T_VERSION_NUMBER;
CCU_SYSTEM_TREE_PATHNAME: T_PATHNAME_REFERENCE;
CCU_NAME : MPS_DEFINITIONS.T_CONFIGURATION_NAME;
CCU_VERSION : MPS_DEFINITIONS.T_VERSION;
CREATOR : T_USER_NAME;
OWNER : T_USER_NAME;
PURPOSE : T_SESSION_INFO_TEXT;
TEST_SITE : T_SESSION_INFO_TEXT;
VERSION_ID_TABLE : T_FILENAME;
TEST_CONFIGURATION : T_FILENAME;
SYSTEM_TOPOLOGY_TABLE : T_FILENAME;
end record;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
477 von/of: 662
–– T_FILENAME for VERSION_ID_TABLE, TEST_CONFIGURATION and SYSTEM_TOPOLOGY_TABLE
–– shall always be the full UNIX pathname (ie. when calling INIT_EXECUTION_SESSION
–– or GET_EXECUTION_SESSION_INFO).
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Test Evaluation Session type
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
type T_EVALUATION_SESSION_INFO is
record
NAME : T_TEST_SESSION_NAME;
CREATION_DATE : CGS_CALENDAR.CGS_DATE_AND_TIME;
CREATOR : T_USER_NAME;
OWNER : T_USER_NAME;
LOCATION : T_LOCATION;
PURPOSE : T_SESSION_INFO_TEXT;
TEST_SITE : T_SESSION_INFO_TEXT;
end record;
type T_EVAL_SESSION_SEL_CRIT is
record
NAME_PATTERN :T_TEST_SESSION_NAME := VICOS_DEFINITIONS.EMPTY_NAME_STRING;
SEL_TIME_FRAME : T_TIME_RECORD := NULL_TIME_RECORD;
LOCATION : T_SELECTED_LOCATION := NULL_LOCATION_SELECTION;
end record;
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Logging events types
subtype T_EVENT is VICOS_DEFINITIONS.T_ERROR_MESSAGE;
–– The User Events are defined as Events with the specific field values (Cf.
VICOS_DEFINITIONS):
–– field LOG_GROUP : DBS_DEFINITIONS.USER_EVENT_LOG_GROUP,
–– field LOG_TYPE : DBS_DEFINITIONS.USER_EVENT_LOG_TYPE.
––
type T_SELECTED_EVENT is
record
EVENT : T_EVENT;
SESSION : T_TEST_SESSION_NAME;
end record;
NULL_LOG_GROUP : constant VICOS_DEFINITIONS.T_LOG_GROUP :=

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
VICOS_DEFINITIONS.NULL_LOG_GROUP;
USER_EVENT_LOG_GROUP : constant VICOS_DEFINITIONS.T_LOG_GROUP :=
VICOS_DEFINITIONS.USER_EVENT_LOG_GROUP;
NULL_LOG_TYPE : constant VICOS_DEFINITIONS.T_LOG_TYPE :=
VICOS_DEFINITIONS.NULL_LOG_TYPE;
USER_EVENT_LOG_TYPE : constant VICOS_DEFINITIONS.T_LOG_TYPE :=
VICOS_DEFINITIONS.GENERAL_MESSAGE_TYPE;
NULL_LOG_TEXT_SHORT : constant VICOS_DEFINITIONS.T_LOG_TEXT_SHORT :=
VICOS_DEFINITIONS.NULL_LOG_TEXT_SHORT;
type T_EVENT_SEL_CRIT is
record
APPLICATION : VICOS_DEFINITIONS.T_APPLICATION_NAME
:= VICOS_DEFINITIONS.EMPTY_NAME_STRING;
TIME_FRAME : T_TIME_RECORD
:= NULL_TIME_RECORD;
LOG_TYPE : VICOS_DEFINITIONS.T_LOG_TYPE
:= NULL_LOG_TYPE;
LOG_GROUP : VICOS_DEFINITIONS.T_LOG_GROUP
:= NULL_LOG_GROUP;
TEXT : VICOS_DEFINITIONS.T_LOG_TEXT_SHORT
:= NULL_LOG_TEXT_SHORT;
end record;
–– Definition of the normal event selection criteria
–– Each field of the record is predefined to a null value. When a
–– field is not a part of the selection criteria, its value is thus
–– null. For the non null fields, the selection criteria is defined
–– with an AND relation between the fields.
MAX_EVENT_CRITERIA: constant POSITIVE := 4;
subtype T_EVENT_SEL_CRIT_RANGE is integer range 1..MAX_EVENT_CRITERIA;
type T_EVENT_SEL_CRIT_COMBINED is
array (T_EVENT_SEL_CRIT_RANGE range ) of T_EVENT_SEL_CRIT;
–– Definition of the combined event selection criteria
–– There is an OR relation between the elements of the array.
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Engineering value logging types
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
type T_ENG_VALUE_LOG is
record
ENG_VALUE : ADT_ENGINEERING_VALUE.T_ENGINEERING_VALUE;
RAW_VALUE : ADT_RAW_VALUE.T_RAW_VALUE;
TIME_TAG_LT : CGS_CALENDAR.CGS_DATE_AND_TIME;
TIME_TAG_SMT : CGS_CALENDAR.CGS_DATE_AND_TIME;
END_ITEM_SID : MPS_DEFINITIONS.SID;
end record;
type T_SELECTED_ENG_VALUE_LOG is
record
ENG_VAL : T_ENG_VALUE_LOG;
PRODUCER : VICOS_DEFINITIONS.T_APPLICATION_NAME;
SESSION_NAME : T_TEST_SESSION_NAME;
end record;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
478 von/of: 662
type T_ENG_VALUE_SEL_CRIT is
record
ITEM_NAME : MPS_DEFINITIONS.SID
:= MPS_DEFINITIONS.NULL_SID;
APPLICATION : VICOS_DEFINITIONS.T_APPLICATION_NAME
:= VICOS_DEFINITIONS.EMPTY_NAME_STRING;
TIME_FRAME : T_TIME_RECORD

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
:= NULL_TIME_RECORD;
TIME_FRAME_TYPE : T_TIME_TYPE
:= LT;
LIST_ORDER : T_TIME_ORDERING
:= LT;
end record;
–– Definition of the engineering value selection criteria,
–– APPLICATION may be empty, what means any application.
–– ITEM_NAME and TIME_FRAME may also be empty what means any SID and
–– no time frame.
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Types for print services
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
type T_PRINTER is
(LASER_PRINTER1,
LASER_PRINTER2);
for T_PRINTER use
(LASER_PRINTER1 => 0,
LASER_PRINTER2 => 1);
type T_STATUS is
(DISABLED,
ENABLED);
for T_STATUS use
(DISABLED => 0,
ENABLED => 1);
type T_PRINT_QUEUE_STATUS is
(OFF,
READY,
PRINTING,
OUT_OF_PAPER,
OUT_OF_TONER);
for T_PRINT_QUEUE_STATUS use
(OFF => 0,
READY => 1,
PRINTING => 2,
OUT_OF_PAPER => 3,
OUT_OF_TONER => 4);
type T_JOB_INFORMATION is
record
IDENT : INTEGER;
OWNER : T_USER_NAME;
FILE_NAME : T_FILENAME;
FILE_SIZE_IN_BYTE : NATURAL;
end record;
type T_PRINT_INFO is
record
PRINTER_STATUS : T_STATUS;
PRINT_QUEUE_STATUS : T_PRINT_QUEUE_STATUS;
NUMBER_OF_ENTRIES : NATURAL;
end record;
–– align record to allow for machine independent network transmission
for T_PRINT_INFO use
record at mod 8;
PRINTER_STATUS at 0 range 0 .. 0;
PRINT_QUEUE_STATUS at 0 range 8 .. 10;
NUMBER_OF_ENTRIES at 0 range 32 .. 63;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
479 von/of: 662

Space Infrastructure
end record;
–– define maximum number of bits for this record
for T_PRINT_INFO’size use 64;
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
type T_GLOBAL_PRINT_INFO is array (T_PRINTER) of T_PRINT_INFO;
DEFAULT_PRINTER : constant T_PRINTER := LASER_PRINTER1;
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Types for HK data
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
type T_DISK_STATUS is
(OK,
DISK_FULL);
type T_TRDB_STATUS is (OK, NOT_OK);
type T_FA_STATUS is (OK, NOT_OK);
MAX_OPEN_SESSION : constant := 5;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
480 von/of: 662
type T_OPEN_SESSION_NAMES is array (1 .. MAX_OPEN_SESSION) of T_TEST_SESSION_NAME;
type T_TRDB_INFO is
record
NUMBER_OF_EVAL_USERS : NATURAL;
CURRENT_TEST_SESSIONS : T_OPEN_SESSION_NAMES;
OVERALL_STATUS : T_TRDB_STATUS;
end record;
for T_TRDB_INFO use
record at mod 8;
NUMBER_OF_EVAL_USERS at 0 range 0 .. 31;
CURRENT_TEST_SESSIONS at 0 range 32 .. 991;
OVERALL_STATUS at 0 range 992 .. 999;
end record;
MAX_PERCENT_VALUE : constant := 100;
subtype T_PERCENT is NATURAL range 0 .. MAX_PERCENT_VALUE;
type T_TRDB_TABLESPACE is
(MA_SPACE,
EVENT_SPACE,
MISC_SPACE);
type T_TABLESPACE_RATIO is array (T_TRDB_TABLESPACE) of T_PERCENT;
for T_TABLESPACE_RATIO’SIZE use 96;
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Types to select part of execution session
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
type T_DATA_TYPE is
(EVENT,
RAW_DATA,
ENG_VAL,
RESULT,
CONFIG);
type T_SELECTED_DATA_TYPE is array (T_DATA_TYPE) of BOOLEAN;
type T_SELECTED_DATA is array (T_DATA_TYPE) of T_TIME_RECORD;
type T_DATA_LOCATION is array (T_DATA_TYPE) of T_LOCATION;
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––

Space Infrastructure
–– Types to describe FA job
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
type T_FA_JOB_STATE is
(ACTIVE,
ALLOCATED,
PENDING);
type T_FA_ACTION is
(IMPORT,
EXPORT,
ARCHIVE,
AUTO_ARCHIVE,
RETRIEVE);
type T_FA_JOB_INFO is
record
STATE : T_FA_JOB_STATE;
JOB_ID : POSITIVE;
OWNER : VICOS_DEFINITIONS.T_APPLICATION_NAME;
ACTION : T_FA_ACTION;
PARAMETER : T_TEST_SESSION_NAME;
end record;
end DBS_DEFINITIONS;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
481 von/of: 662

Space Infrastructure
7.12 DBS Application Programmer Interface
Informal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
482 von/of: 662
The DBS product provides a package of ’Ada’ library functions to be called from ’Ada’ applications external
to CGS.
DBS application programmer interface (DBS API) services shall be provided to enable Final Archive Special
Application Software (FA SAS) to manage the final archiving of test execution/evaluation sessions in a dedicated
long term storage medium, the retrieving of archived sessions, and the import/export of complete sessions.
It makes DBS independent from any archive device, and thereby, makes possible the connection to various hardwares
e.g. Exabyte tape, DAT tape, optical disk, etc.
DBS communicates with the FA SAS through the DBS API for the transfer of data files and for identification
of the archive volumes (e.g. tape name).
The FA SAS will be in charge of the device driver, device commanding, any device specific protocol, and of
the user dialogue to operate the hardware.
The FA SAS executes as a separate OS process connected to DBS via the DBS API
A number of access services are supplied, these are summarised hereafter.
• Archive operation
• Retrieve operation
• Export operation
• Import operation

Space Infrastructure
Formal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
483 von/of: 662
––
–– DBS_API
––
––****************************************************************************
––ABSTRACT––
––
–– This package contains operation used by a FA SAS to communicate with DBS.
––
––*–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––IDENTIFICATION––
–– PROJECT NAME :VICOS
–– PRODUCT NAME :DBS
–– CI–NUMBER :1216 863
–– OBJECT NAME :DBS_API
––*–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––CONTENTS––
–– COMPILER :Sun ADA 1.1
–– LANGUAGE :ADA
–– SPECIAL CONTENTS:
–– CHANGE HISTORY
–– V5.2 at Central Repository V4.0 (moon)
–– creator: pcvicos (on host alien)
–– creation date: 20.08.97 10:31:21
–– comment:
–– DBS 4.1 development:
–– 1) New operation SUPPLY_RESPONSE added
–– 2) Scope of operation SUPPLY_ACKNOWLEDGE modified
––
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V4.1 at SBI ; DBS development
–– creator: bcharlie (on host ariane5)
–– creation date: 20.01.95 16:44:56
–– added Standard Header by command create_file
––
–– END HISTORY
––****************************************************************************
––
––
with DBS_DEFINITIONS;
with ADT_DBS_TO_SAS_COMMAND;
with DBS_COMMS_DEFINITIONS;
package DBS_API is
–– Object Description :
–– Provided operations :
procedure INIT_FA_SAS(STATUS : out DBS_DEFINITIONS.T_DBS_ERROR);
–– This operation initializes the communication services for the FA SAS
process.
–– Parameters description :
–– STATUS : informs the caller about the procedure completion :
–– – OK : the communication services have been correctly
initialized.
–– – INIT_PROBLEM : initialisation of the communication
services failed.
–– – DBS_INTERNAL_PROBLEM : unexpected exception has been
raised in the
–– procedure.
procedure READ_COMMAND(
COMMAND : out ADT_DBS_TO_SAS_COMMAND.T_COMMAND;
CHANNEL_NUMBER : out ADT_DBS_TO_SAS_COM-
MAND.T_CHANNEL_NBR;
STATUS : out DBS_DEFINITIONS.T_DBS_ERROR );
–– This operation reads the next command from DBS.
–– Parameters description :

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
484 von/of: 662
–– COMMAND : the incoming command.
–– CHANNEL_NUMBER : number of the logical channel that has initiated the
command.
–– STATUS : informs the caller about the procedure completion :
–– – OK : the message has been read correctly.
–– – DBS_COMMUNICATION_PROBLEM : the communication with
DBS is broken.
–– – DBS_INTERNAL_PROBLEM : unexpected exception has been
raised.
procedure SUPPLY_ACKNOWLEDGE(
ACK_INFO : in DBS_DEFINITIONS.T_DBS_ERROR;
CHANNEL_NUMBER : in ADT_DBS_TO_SAS_COM-
MAND.T_CHANNEL_NBR;
––
ing kind
STATUS : out DBS_DEFINITIONS.T_DBS_ERROR );
This operation sends an acknowledge to DBS in response to the follow-
–– of commands :
–– – ALLOCATE_FA_DRIVE
–– – DEALLOCATE_FA_DRIVE
–– – FREE_FA_FROM_AUTO_ARCH
–– – ARCHIVE_FILE_LIST_AA
–– Parameters description :
––
operation).
ACK_INFO : the acknowledge information to send back (status of the
––
to be sent.
CHANNEL_NUMBER : number of the logical channel to which ACK_INFO has
–– STATUS : informs the caller about the procedure completion :
–– – OK : the acknowledge has been sent correctly.
––
DBS is broken.
– DBS_COMMUNICATION_PROBLEM : the communication with
––
raised.
– DBS_INTERNAL_PROBLEM : unexpected exception has been
procedure SUPPLY_RESPONSE(
ACK_INFO
CHANNEL_NUMBER : in POSITIVE;
: in DBS_DEFINITIONS.T_DBS_ERROR;
RESPONSE_TYPE : in DBS_COMMS_DEFINITIONS.T_RESPONSE_TYPE;
RESPONSE : in DBS_COMMS_DEFINITIONS.T_RESPONSE;
STATUS : out DBS_DEFINITIONS.T_DBS_ERROR );
–– This operation sends an acknowledge and a response to DBS in response to the
–– following kind of messages:
–– – RETRIEVE_FILE_LIST
–– – ARCHIVE_FILE_LIST
–– – EXPORT_TREE_LIST
–– – IMPORT_TREE
–– – RESERVE_FA_FOR_AUTO_ARCH
–– Parameters description:
–– ACK_INFO : acknowledge to supply
–– CHANNEL_NUMBER : the addressee of the acknowledge and the response.
–– RESPONSE_TYPE : type of the response.
–– RESPONSE : the response.
––
completion :
STATUS : informs the caller about the procedure
–– – OK : the acknowledge has been correctly sent back.
––
broken.
– DBS_COMMUNICATION_PROBLEM : the communication with DBS is
––
––
– DBS_INTERNAL_PROBLEM : unexpected exception has been raised.
procedure STOP;
–– This operation stops the communication between FA SAS and DBS.
––
DBS.
This operation has to be used when receiving the stop command from
–– After execution of this operation, the communicatoin between FA SAS
––
stopped.
end DBS_API;
cannot be reinitialised as every communictaion internal tasks are

Space Infrastructure
Formal Interface Description
485
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
––
–– ADT_DBS_TO_SAS_COMMAND
––
––****************************************************************************
––ABSTRACT––
––
–– This package defines types and operations related to FA SAS commands issued
–– by DBS.
––
––*–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––IDENTIFICATION––
–– PROJECT NAME :VICOS
–– PRODUCT NAME :DBS
–– CI–NUMBER :1216 863
–– OBJECT NAME :ADT_DBS_TO_SAS_COMMAND
––*–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––CONTENTS––
–– COMPILER :Sun / Verdix
–– LANGUAGE :ADA
–– SPECIAL CONTENTS:
–– CHANGE HISTORY
–– V4.1 at SBI ; DBS development
–– creator: bcharlie (on host ariane5)
–– creation date: 18.11.94 15:23:17
–– ARCHIVE_TREE becomes ARCHIVE_LIST_OF_FILES,
–– RESERVE_FA_FOR_AUTO_ARCH + AA operations.
––****************************************************************************
––
with DBS_DEFINITIONS;
package ADT_DBS_TO_SAS_COMMAND is
–– REMARK :
–– A ’Tree’ can be either a directory structure or a file.
–––––––––––––––––––––––––––––––––
–– Provided types and constants :
–––––––––––––––––––––––––––––––––
type T_COMMAND_ALTERNATIVE is (
UNDEFINED,
ALLOCATE_FA_DRIVE,
DEALLOCATE_FA_DRIVE,
EXPORT_TREE_LIST,
IMPORT_TREE,
ARCHIVE_FILE_LIST,
RETRIEVE_FILE_LIST,
RESERVE_FA_FOR_AUTO_ARCH,
FREE_FA_FROM_AUTO_ARCH,
ARCHIVE_FILE_LIST_AA,
STOP);
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
485 von/of: 662
–– List of commands handled by the FA_SAS :
–– – request to allocate an FA drive for the following operations:
–– EXPORT_TREE_LIST, IMPORT_TREE,
–– ARCHIVE_FILE_LIST, RETRIEVE_FILE_LIST.
–– The Allocation is requested before any of these 4 operations.
–– – request to deallocate a previously allocated FA drive.
–– The deallocation is requested after any of these 4 operations.
–– – request to put a list of file trees on a single export medium.
–– – request to get a file tree from a single FA medium.
–– – request to put a list of files on multiple archive mediums.
–– – request to get a list of files from a single archive medium.
–– – request to reserve an FA device for Automatic Archiving;
–– then this device is not accessible to other operations than
–– FREE_FA_FROM_AUTO_ARCH, ARCHIVE_LIST_OF_FILES_AA,
–– STOP.
–– – request to free the FA device reserved for Automatic Archiving.
–– – request to put a list of files on the archive medium reserved for

Space Infrastructure
486
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
486 von/of: 662
–– Automatic Archiving.
––
––
– request the FA SAS to stop.
––
––
REMARK :
–– The FA services are grouped into 3 sets:
–– – the operations of import/export,
–– – the operations of archiving/retrieving,
–– – the operations of Automatic Archiving.
–– This separation allows the FA SAS to implement different labels on im/export disks
–– and archiving/retrieving disks to increase efficiency of disk utilisation
–– and to reserve a device for the automatic archiving.
–– The operations EXPORT_TREE_LIST, IMPORT_TREE and
–– RETRIEVE_FILE_LIST always access a single FA medium, but the operations
–– ARCHIVE_FILE_LIST and ARCHIVE_FILE_LIST_AA could access multiple
––
––
FA mediums if implemented by the FA–SAS.
–– EXPORT_TREE_LIST : The list of trees to export on a disk is contained in a file.
–– This is a text file composed with the file name of each item of the list,
–– one file name by line. The file name is the pathname of the tree
–– (file or directory structure) relative to $VICOS_CEN_DBS_HOME.
–– Example :
–– File containing a filename and a path to a directory structure
–– (export_tree_list):
–– /EXECUTION/SESSION_1/RAW_DATA/TES_01/Raw_data_file.01
–– /EXECUTION/SESSION_1/ENG_VAL
–– RETRIEVE_FILE_LIST : The list of files to retrieve from disk is contained in a file.
–– This is a text file composed with the file name of each item of the list,
–– one file name by line. The file name
–– is the pathname of the file relative to $VICOS_CEN_DBS_HOME.
–– Example :
–– File containing two filenames (retrieve_file_list):
–– /EXECUTION/SESSION_1/RAW_DATA/TES_01/Raw_data_file.01
–– /EXECUTION/SESSION_1/ENG_VAL/EVL_TES02_dfet1234
–– ARCHIVE_FILE_LIST (ARCHIVE_FILE_LIST_AA): The list of files to archive on
–– FA mediums, is contained in a file.
–– This is a text file composed with the file name of each item of the list,
–– one file name by line.
–– The file name is the pathname of the file relative to $VICOS_CEN_DBS_HOME.
–– The list of the FA medium labels used to archive these files is given back
–– in another file.
–– This is a text file composed with the ID of the FA mediums corresponding to
–– the files, one ID by line.
–– Example :
–– File containing a list of files and the file containing the
–– corresponding Container ID list (archive_file_list):
–– /EXECUTION/SESSION_1/RAW_DATA/TES_01/Raw_data_file.01
–– /EXECUTION/SESSION_1/ENG_VAL/TES_12_EVL_adf1234
––
––
/EXECUTION/SESSION_1/ENG_VAL/TES_04_EVL_asj4321
–– ARCH_qwerty123456
–– ARCH_qwerty123456
–– ARCH_ytrewq654321
MAX_NUMBER_OF_FA_DRIVE : constant NATURAL := 2;
–– Maximum number of FA drives.
subtype T_CHANNEL_NBR is NATURAL range 0..MAX_NUMBER_OF_FA_DRIVE;
–– Definition of a logical channel number used by DBS to communicate with the FA_SAS.
subtype T_CONTAINER_ID is DBS_DEFINITIONS.T_FILENAME;
–– Reference of the data on a FA medium.
type T_EXPORT_TREE_LIST_DATA is record
EXPORT_NAME : DBS_DEFINITIONS.T_TEST_SESSION_NAME;
LIST_OF_TREES
end record;
: DBS_DEFINITIONS.T_FILENAME;
–– Definition of the data of the EXPORT_TREE_LIST command.
–– EXPORT_NAME is the name of the exported data. This name will be used when importing.
–– LIST_OF_TREES is the name of the file containing the list of trees to export

Space Infrastructure
487
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
487 von/of: 662
––
––
(relative to $VICOS_CEN_DBS_HOME).
type T_IMPORT_TREE_DATA is record
EXPORT_NAME : DBS_DEFINITIONS.T_TEST_SESSION_NAME;
––
TARGET_DIRECTORY : DBS_DEFINITIONS.T_FILENAME;
end record;
Definition of the data of the IMPORT_TREE command.
–– EXPORT_NAME is the name of the exported data to import.
–– TARGET_DIRECTORY is the pathname where the imported data will be put
–– (relative to $VICOS_CEN_DBS_HOME).
type T_RETRIEVE_FILE_LIST_DATA is record
CONTAINER_ID : T_CONTAINER_ID;
FILE_LIST : DBS_DEFINITIONS.T_FILENAME;
––
end record;
Definition of the data of the RETRIEVE_LIST_OF_FILES command.
–– CONTAINER_ID is the reference of the FA medium.
–– FILE_LIST is the name of the file containing the list of files
–– (relative to $VICOS_CEN_DBS_HOME).
type T_ARCHIVE_FILE_LIST_DATA is record
LIST_OF_FILES : DBS_DEFINITIONS.T_FILENAME;
LIST_OF_CONTAINER_IDS : DBS_DEFINITIONS.T_FILENAME;
––
end record;
Definition of the data of the ARCHIVE_FILE_LIST command.
–– LIST_OF_FILES is the pathname of the file containing the list of files
–– to archive (relative to $VICOS_CEN_DBS_HOME).
–– LIST_OF_CONTAINER_IDS is the pathname of the file that will contain
–– the corresponding list of Container ID’s
–– (relative to $VICOS_CEN_DBS_HOME).
type T_COMMAND (COMMAND_ALTERNATIVE : T_COMMAND_ALTERNATIVE := UNDEFINED) is private;
–– Definition of the command that is sent by DBS to the FA_SAS.
NULL_CONTAINER_ID : constant T_CONTAINER_ID
:= (LENGTH => 0, NAME => (others => ’ ’));
–– Usefull null values.
––––––––––––––––––––––––
–– Provided operations :
––––––––––––––––––––––––
procedure SET_ALLOCATE_FA_DATA
(OF_COMMAND : in out T_COMMAND ;
COMMAND_DATA : in T_COMMAND_ALTERNATIVE);
–– This operation initializes the ALLOCATE_FA_DRIVE data with the kind of operation
–– for which a FA driver has to be reserved.
procedure SET_STOP_DATA
(OF_COMMAND : in out T_COMMAND);
–– This operation initializes the STOP command.
procedure SET_DEALLOCATE_FA_DATA
(OF_COMMAND : in out T_COMMAND;
COMMAND_DATA : in T_COMMAND_ALTERNATIVE);
–– This operation initializes the DEALLOCATE_FA_DRIVE data with the kind of operation
–– for which the previously reserved FA driver has to be deallocated.
procedure SET_EXPORT_TREE_LIST_DATA
(OF_COMMAND : in out T_COMMAND;
COMMAND_DATA : in T_EXPORT_TREE_LIST_DATA);
–– This operation initializes the EXPORT_TREE_LIST data with the list of directories to
–– put on the FA medium and the associated name.
procedure SET_IMPORT_TREE_DATA
(OF_COMMAND : in out T_COMMAND;
COMMAND_DATA : in T_IMPORT_TREE_DATA);
–– This operation initializes the IMPORT_TREE data with the name of the exported data
–– to get from the FA medium and the destination directory.
procedure SET_RETRIEVE_FILE_LIST_DATA
(OF_COMMAND : in out T_COMMAND;
COMMAND_DATA : in T_RETRIEVE_FILE_LIST_DATA);

Space Infrastructure
488
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
488 von/of: 662
–– This operation initializes the RETRIEVE_FILE_LIST data with the identification
–– of the file containing the list of the files to retrieve and the reference of
–– the data on the FA medium.
procedure SET_ARCHIVE_FILE_LIST_DATA
(OF_COMMAND : in out T_COMMAND ;
COMMAND_DATA : in T_ARCHIVE_FILE_LIST_DATA);
–– This operation initializes the ARCHIVE_FILE_LIST data with the pathname of the file
–– containing the list of files to archive (relative to $VICOS_CEN_DBS_HOME) and the
–– pathname of file that will contain the corresponding Container ID list.
procedure SET_RESERVE_FA_FOR_AUTO_ARCH_DATA
(OF_COMMAND : in out T_COMMAND);
–– This operation initializes the RESERVE_FA_FOR_AUTO_ARCH command.
procedure SET_FREE_FA_FROM_AUTO_ARCH_DATA
(OF_COMMAND : in out T_COMMAND);
–– This operation initializes the FREE_FA_FROM_AUTO_ARCH command.
procedure SET_ARCHIVE_FILE_LIST_AA_DATA
(OF_COMMAND : in out T_COMMAND ;
COMMAND_DATA : in T_ARCHIVE_FILE_LIST_DATA);
–– This operation initializes the ARCHIVE_FILE_LIST_AA data with the pathname of the
–– file containing the list of files to archive (relative to $VICOS_CEN_DBS_HOME) and
–– the pathname of file that will contain the corresponding Container ID list.
function COMMAND_ALTERNATIVE
(COMMAND : in T_COMMAND) return T_COMMAND_ALTERNATIVE;
–– This operation returns the type of the given command.
function GET_ALLOCATE_FA_DATA
(COMMAND : in T_COMMAND) return T_COMMAND_ALTERNATIVE;
–– This operation returns the kind of operation associated to an
–– ALLOCATE_FA_DRIVE command.
function GET_DEALLOCATE_FA_DATA
(COMMAND : in T_COMMAND) return T_COMMAND_ALTERNATIVE;
–– This operation returns the kind of operation associated to an
–– DEALLOCATE_FA_DRIVE command.
function GET_EXPORT_TREE_LIST_DATA
(COMMAND : in T_COMMAND) return T_EXPORT_TREE_LIST_DATA;
–– This operation returns the list of directories associated to an EXPORT_TREE_LIST
–– command and the name of the data to export.
function GET_IMPORT_TREE_DATA
(COMMAND : in T_COMMAND) return T_IMPORT_TREE_DATA;
–– This operation returns the name of the data to extract and the
–– destination pathname.
function GET_RETRIEVE_FILE_LIST_DATA
(COMMAND : in T_COMMAND) return T_RETRIEVE_FILE_LIST_DATA;
–– This operation returns the location on the FA medium and the name
–– of the file to extract and the destination pathname.
function GET_ARCHIVE_FILE_LIST_DATA
(COMMAND : in T_COMMAND) return T_ARCHIVE_FILE_LIST_DATA;
–– This operation returns a record with the identification of the file containing the
–– list of files to archive and the identification of the file where to write the list
–– of corresponding Container ID’s.
function GET_ARCHIVE_FILE_LIST_AA_DATA
(COMMAND : in T_COMMAND) return T_ARCHIVE_FILE_LIST_DATA;
–– This operation returns a record with the identification of the file containing the
–– list of files to archive and the identification of the file where to write the list
–– of corresponding Container ID’s.
––––––––––––––––––––––––
–– Provided exceptions :
––––––––––––––––––––––––
COMMAND_TYPE_MISMATCH : exception;

Space Infrastructure
489
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
489 von/of: 662
–– This exception is raised when an operation is called on a command that
–– does not have the correct alternative.
––
private
type T_COMMAND (COMMAND_ALTERNATIVE : T_COMMAND_ALTERNATIVE := UNDEFINED) is record
case COMMAND_ALTERNATIVE is
when ALLOCATE_FA_DRIVE => ALLOCATE_DATA : T_COMMAND_ALTERNATIVE;
when DEALLOCATE_FA_DRIVE => DEALLOCATE_DATA : T_COMMAND_ALTERNATIVE;
when EXPORT_TREE_LIST => EXPORT_TREE_LIST_DATA :
T_EXPORT_TREE_LIST_DATA;
when IMPORT_TREE => IMPORT_TREE_DATA :
T_IMPORT_TREE_DATA;
when ARCHIVE_FILE_LIST => ARCHIVE_FILE_LIST_DATA :
T_ARCHIVE_FILE_LIST_DATA;
when RETRIEVE_FILE_LIST => RETRIEVE_FILE_LIST_DATA :
T_RETRIEVE_FILE_LIST_DATA;
when RESERVE_FA_FOR_AUTO_ARCH => null;
when FREE_FA_FROM_AUTO_ARCH => null;
when ARCHIVE_FILE_LIST_AA => ARCHIVE_FILE_LIST_AA_DATA :
T_ARCHIVE_FILE_LIST_DATA;
when STOP => null;
when UNDEFINED => null;
end case;
end record;
–– Definition of the command that is sent by DBS to the FA_SAS.
end ADT_DBS_TO_SAS_COMMAND;

Space Infrastructure
7.13 TEV Types and Constants Definitions
Informal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
490 von/of: 662
A same set of data types are used in the various procedural interfaces provided by the TEV product. In order
to ensure the consistency of their definition and usage through all the interfaces, they are grouped and defined
once, in the current section.
They are ”basic” data types and constants (like numbers, strings, enumerations...) which are accessible directly.
They constitute a type pool and are grouped into a set of Ada packages, according to their nature.
The usage of the basic data types is simple. The desired variable has to be declared with the desired type in the
piece of software which will use it. The access to the content of the variable is done directly, by knowledge of
its Ada structure.
The TEV_DEFINITIONS package contains type and constant definitions that are :
. specific of TEV, i.e. not used or shared by several CGS products,
. common in TEV, i.e. used or shared by several TEV provided services,
. of general nature, i.e. not specific to any of these services.

Space Infrastructure
Formal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
491 von/of: 662
––
–– TEV_DEFINITIONS
––
––****************************************************************************
––ABSTRACT––
––
–– This object provides common types needed by
–– the evaluation definitions objects.
–– cf. COMMON SERVICES product architecture
––
––
––*–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––IDENTIFICATION––
–– PROJECT NAME : CGS
–– PRODUCT NAME : TEV
–– CI–NUMBER : 1216 858
–– OBJECT NAME : TEV_DEFINITIONS
––*–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––CONTENTS––
–– COMPILER : VERDIX ADA 6.0.3.C
–– LANGUAGE : ADA
–– SPECIAL CONTENTS:
–– CHANGE HISTORY
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V4.3 at DASA
–– creator: Bruening
–– creation date: 21.10.99
–– comment:
–– Correct mapping of MPS_DEFINITIONS.T_ITEM_TYPE to T_MEASUREMENT_ALTERNATIVES.
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V4.3 at DASA
–– creator: Bruening
–– creation date: 06.09.99
–– comment:
–– New types used for the merge ADT_DATA_SET/ADT_EVENT_RESULT tool
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– CGS V4.2 ICD Change 27.07.99, W.Tammen:
–– removed with–clauses for STRING_UTILITIES and TEV_STRING_UTILITIES
–– (simply not used)
–– according to COL–RIBRE–IRN–CGS–8078
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V4.2 at DASA
–– creator: Bruening
–– creation date: 03.05.99
–– comment:
–– New type T_SID_PATHNAME to handle working lists of SID–pathname
–– to avoid asking several times MDB for a pathname
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– END HISTORY
––****************************************************************************
––
with FILE_MANAGEMENT;
with CGS_CALENDAR;
with VICOS_LIST;
––(V3) with DBS_DEFINITIONS;
with MPS_DEFINITIONS;
with ADT_ENGINEERING_VALUE;
with VICOS_DEFINITIONS;
with ADT_RAW_VALUE;
with C_STRINGS; ––rhn Modification SPR_2886 24/01/97
with U_ENV; ––rhn Modification SPR_2886 24/01/97

Space Infrastructure
package TEV_DEFINITIONS is
–– Provided types and constants :
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
492 von/of: 662
–– RHN Begin of Modification SPR_2886 24/01/97
–– ROOT_TMP_NAME : constant string := ”/tmp/tev_tmp”;
––
TEV_HOME_ENV_NAME : constant STRING := ”TEV_HOME”;
TEV_HOME_VAR_ENV_NAME : constant STRING :=
C_STRINGS.TO_STRING(U_ENV.Getenv(C_STRINGS.To_C(TEV_HOME_ENV_NAME)));
ROOT_TMP_NAME : constant STRING := FILE_MANAGEMENT.GET_TEMP_DIRECTORY & ”/tev_tmp”;
–– End of Modification SPR_2886
–– prefix file name for temporary files
TASK_SCHEDULING_TIME : constant duration := 0.001;
–– delay needed to allow scheduling of other tasks : 1 milliseconds
–– should be used in (at least) all EXECUTE operations
subtype T_TOOL_ID is POSITIVE range 1 .. 4;
–– possible instance number of each tool
type T_PRINTER is (LASER_PRINTER1, LASER_PRINTER2);
–– defines the available printers
HEADER_SPACE : constant NATURAL := 6;
PORTRAIT_PAGE_LENGTH : constant := 60;
LANDSCAPE_PAGE_LENGTH : constant := 50;
PORTRAIT_PAGE_WIDTH : constant := 80;
LANDSCAPE_PAGE_WIDTH : constant := 140;
LEFT_MARGIN : constant := 10;
–– constants needed to fix page layout for format operation
type T_FILE_TYPE is (TRDB_RES, WD_RES, WD_DEF);
–– possible types of TEV file
subtype T_WD_FILE_TYPE is T_FILE_TYPE range WD_RES .. WD_DEF;
–– possible types of TEV WD file
subtype T_FILE_NAME_RANGE is POSITIVE range
1 .. VICOS_DEFINITIONS.MAX_NAME_LENGTH;
subtype T_FILE_NAME is STRING(T_FILE_NAME_RANGE);
–– description of a filename
subtype T_RESULT_NAME is T_FILE_NAME;
–– description of a result filename
subtype T_DEFINITION_NAME_RANGE is T_FILE_NAME_RANGE;
subtype T_DEFINITION_NAME is T_FILE_NAME;
–– description of a definition filename
type T_TIME_FRAME is
record
BEGIN_DATE_TIME : CGS_CALENDAR.CGS_DATE_AND_TIME;
END_DATE_TIME : CGS_CALENDAR.CGS_DATE_AND_TIME;
end record;
–– time frame
MAX_LENGTH_OF_ENVIRONMENT_VARIABLE_NAME : constant POSITIVE := 255;
NULL_TIME_FRAME : constant T_TIME_FRAME :=
(BEGIN_DATE_TIME => CGS_CALENDAR.NULL_DATE_AND_TIME,
END_DATE_TIME => CGS_CALENDAR.NULL_DATE_AND_TIME);
–– null time frame
subtype T_DIRECTORY is
STRING(1 .. MAX_LENGTH_OF_ENVIRONMENT_VARIABLE_NAME);
–– description of a directory name
NULL_RESULT_NAME : constant T_RESULT_NAME := (others => ’ ’);
–– null result filename
NULL_DEFINITION_NAME : constant T_DEFINITION_NAME := (others => ’ ’);
–– null definition filename

Space Infrastructure
––(V3) subtype T_TABLE_NAME is DBS_DEFINITIONS.T_TABLE_NAME;
subtype T_TABLE_NAME is string(1..20);
–– description of a user result table name
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
––(V3) NULL_TABLE_NAME : constant T_TABLE_NAME := DBS_DEFINITIONS.NULL_TABLE_NAME;
NULL_TABLE_NAME : constant T_TABLE_NAME := (others => ’ ’);
–– null table name
MAX_NUMBER_OF_TABLE_IN_DEF : constant positive := 50;
–– maximum number of table names in a user result table definition
type T_TABLE_NAME_ARRAY is array (positive range ) of T_TABLE_NAME;
–– array of table names
NULL_TABLE_NAME_ARRAY : constant T_TABLE_NAME_ARRAY :=
NULL_TABLE_NAME);
–– null array of table names
type T_RESULT_SOURCE is (WORKING_DIR, TRDB);
–– source of evaluation result file
type T_RESULT_REF is
record
RESULT_NAME : T_RESULT_NAME;
RESULT_SOURCE : T_RESULT_SOURCE;
end record;
type T_TOOL_ALTERNATIVES is (
–– types of tool managed in TEV
EVENTS_LOGGING,
RAW_DATA_DUMP,
USER_RESULT_TABLE,
DATA_SET_GENERATION,
STATISTICS_GENERATION,
DATA_LISTING,
GRAPH_DISPLAY,
REPORT_GENERATION,
SAS);
subtype T_FILE_ALTERNATIVES_IN_REPORT is
T_TOOL_ALTERNATIVES range EVENTS_LOGGING .. GRAPH_DISPLAY;
–– types of evaluation result file in a report
type T_EVALUATION_DEFINITION_ALTERNATIVES is (
type T_MEASUREMENT_ALTERNATIVES is (
–– EGSE specific types
–– measurements:
EGSE_INTEGER_MEASUREMENT,
EGSE_FLOAT_MEASUREMENT,
EGSE_DISCRETE_MEASUREMENT,
EGSE_BYTE_STREAM_MEASUREMENT,
EGSE_INTEGER_SW_VARIABLE,
EGSE_FLOAT_SW_VARIABLE,
EGSE_DISCRETE_SW_VARIABLE,
EGSE_BYTE_STREAM_SW_VARIABLE,
–– derived values:
EGSE_INTEGER_DERIVED_VALUE,
EGSE_FLOAT_DERIVED_VALUE,
EGSE_DISCRETE_DERIVED_VALUE,
EGSE_STRING_DERIVED_VALUE);
–– Possible types of parameters in the data set
type T_PARAMETER_VALUE is
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
493 von/of: 662
(1..1 =>
RAW_DATA_DEFINITION,
EVENT_DEFINITION,
DATA_SET_DEFINITION,
DATA_LISTING_DEFINITION,
STATISTICS_DEFINITION,
GRAPH_DEFINITION);

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
record
LT_TIME_TAG : CGS_CALENDAR.CGS_DATE_AND_TIME;
SMT_TIME_TAG : CGS_CALENDAR.CGS_DATE_AND_TIME;
ENGINEERING_VALUE : ADT_ENGINEERING_VALUE.T_ENGINEERING_VALUE;
RAW_VALUE : ADT_RAW_VALUE.T_RAW_VALUE;
end record;
–– definition of a value inside the data set
–– * –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– * types used for the merge ADT_DATA_SET/ADT_EVENT_RESULT tool
–– * –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
type T_TWO_TIME is
record
ORDERING_TIME : CGS_CALENDAR.CGS_DATE_AND_TIME;
SECOND_TIME : CGS_CALENDAR.CGS_DATE_AND_TIME;
end record;
–– * Pointer in the ADT_DATA_SET result file of the next value to
–– * read, for each parameter defined in the current data set
type T_POSITION_IN_LISTING is array(INTEGER range ) of NATURAL;
–– * List of engineering values for each parameter, without VICOS_LIST
type T_PARAMETER_VALUES is array(NATURAL range ) of T_PARAMETER_VALUE;
–– * –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
type T_EVALUATION_RESULT_FILE is
record
RESULT_FILE_INFO : T_RESULT_REF;
RESULT_TYPE : T_TOOL_ALTERNATIVES;
end record;
–– description and location of evaluation result file
NULL_RESULT_REF : constant T_RESULT_REF :=
(RESULT_NAME => (others => ’ ’),
RESULT_SOURCE => WORKING_DIR);
–– null result reference
MAX_NUMBER_OF_PARAMETERS_IN_DEF : constant INTEGER := 50;
–– maximum number of parameters in an evaluation definition
subtype T_PARAMETERS_RANGE is POSITIVE range 1 .. MAX_NUMBER_OF_PARAMETERS_IN_DEF;
–– number of parameters
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
494 von/of: 662
subtype T_PARAMETER_NAME_RANGE is
POSITIVE range 1 .. VICOS_DEFINITIONS.MAX_LENGTH_OF_DB_PATHNAME;
subtype T_PARAMETER_NAME is STRING(T_PARAMETER_NAME_RANGE);
–– description of a parameter name
NULL_PARAMETER_NAME : constant T_PARAMETER_NAME := (others => ’ ’);
MAX_NUMBER_OF_PARAMETERS_IN_LISTING : constant INTEGER := 10;
type T_PARAMETER_NAMES is array(POSITIVE range ) of T_PARAMETER_NAME;
type T_PARAMETER_NAME_ARRAY is array(POSITIVE range ) of T_PARAMETER_NAME;
subtype T_PRODUCER_NAME_RANGE is
POSITIVE range 1 .. VICOS_DEFINITIONS.MAX_NAME_LENGTH;
subtype T_PRODUCER_NAME is STRING(T_PRODUCER_NAME_RANGE);
–– description of producer name
NULL_LISTING_PARAMETERS : constant T_PARAMETER_NAMES(1 .. MAX_NUMBER_OF_PARAMETERS_IN_LISTING)
–– null parameters for listing
:= (others => NULL_PARAMETER_NAME);
NULL_PARAMETERS : constant T_PARAMETER_NAMES(1 .. MAX_NUMBER_OF_PARAMETERS_IN_DEF)
:= (others => NULL_PARAMETER_NAME);
–– null parameters
NULL_PRODUCER_NAME : constant T_PRODUCER_NAME := (others => ’ ’);
subtype T_COMPLETE_FILENAME_RANGE is
POSITIVE range 1 .. VICOS_DEFINITIONS.MAX_LENGTH_OF_FILE_NAME;
subtype T_COMPLETE_FILENAME is STRING(T_COMPLETE_FILENAME_RANGE);
–– description of complete filename

Space Infrastructure
subtype T_EVENT_GROUP is VICOS_DEFINITIONS.T_LOG_GROUP;
–– Type of a log event group
subtype T_EVENT_TYPE is VICOS_DEFINITIONS.T_LOG_TYPE;
–– Type of log event type
subtype T_SHORT_TEXT is VICOS_DEFINITIONS.T_LOG_TEXT_SHORT;
–– Type of short text of a log event
subtype T_LONG_TEXT is VICOS_DEFINITIONS.T_LOG_TEXT_LONG;
–– Type of short text of a log event
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
495 von/of: 662
NULL_TEV_ENGINEERING_UNIT : constant
MPS_DEFINITIONS.T_ENGINEERING_UNIT := (
EXPRESSION => MPS_DEFINITIONS.STATIC_STRING80(
MPS_DEFINITIONS.STATIC_STRINGS80.STATIC(” ”)),
UNIT => MPS_DEFINITIONS.BASE_UNITS.NO_UNIT);
–– null engineering unit record
NULL_COMPLETE_FILENAME : constant T_COMPLETE_FILENAME := (others => ’ ’);
NULL_FILENAME : constant T_COMPLETE_FILENAME := (others => ’ ’); –– (old V2 definition)
–– null complete filename
NULL_EVENT_GROUP : constant T_EVENT_GROUP := (others => ’ ’);
–– null log group for events selection criteria
NULL_LOG_TYPE : constant T_EVENT_TYPE := (others => ’ ’);
–– null log type for events selection criteria
NULL_LOG_TEXT_SHORT : constant T_SHORT_TEXT := (others => ’ ’);
–– null short text for events log
NULL_LOG_TEXT_LONG : constant T_LONG_TEXT := (others => ’ ’);
–– null long text description for events log
DEFAULT_LONG_TEXT_FLAG : constant BOOLEAN := FALSE;
–– default value of the long text flag
MAX_SELECTION_CRITERIA : constant POSITIVE := 4;
–– Maximum number of normal selection criteria to be combined.
MAX_SYSTEM_TREE_VERSION_NUMBER_STR : constant POSITIVE := 3;
–– The maximal version number (999) in string format
subtype T_SELECTION_CRITERIA_RANGE is
NATURAL range 1 .. MAX_SELECTION_CRITERIA;
–– definition of combined selection criteria range
subtype T_SESSION_NAME_RANGE is POSITIVE
range 1 .. VICOS_DEFINITIONS.MAX_NAME_LENGTH;
subtype T_SESSION_NAME is STRING(T_SESSION_NAME_RANGE);
–– description of session name
type T_SESSION_NAME_ARRAY is array (positive range ) of T_SESSION_NAME;
–– array of session names
––(V3) subtype T_SESSION_PURPOSE is DBS_DEFINITIONS.T_SESSION_INFO_TEXT;
subtype T_SESSION_PURPOSE is string(1..80);
–– Type of a purpose field related to an Execution Session Info
––(V3) subtype T_CREATOR is DBS_DEFINITIONS.T_SESSION_INFO_TEXT;
subtype T_CREATOR is string(1..80);
–– Type of a creator field related to an Execution Session Info
––(V3) subtype T_OWNER is DBS_DEFINITIONS.T_USER_NAME;
subtype T_OWNER is string(1..80);
–– Type of a owner field related to an Execution Session Info
subtype T_SYSTEM_TREE_VERSION_NUMBER_STR is
STRING(1 .. TEV_DEFINITIONS.MAX_SYSTEM_TREE_VERSION_NUMBER_STR);
–– type for the version of a system tree
subtype T_ELEMENT_CONFIGURATION_NAME is MPS_DEFINITIONS.T_ELEMENT_CONFIGURATION_NAME;

Space Infrastructure
’);
–– type for the name of an element configuration
subtype T_MISSION_NAME is MPS_DEFINITIONS.T_MISSION_NAME;
–– type for a mission name
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
496 von/of: 662
subtype T_CCU_SYSTEM_TREE_PATHNAME_STR is
STRING(1 .. VICOS_DEFINITIONS.MAX_LENGTH_OF_DB_PATHNAME);
–– type for the pathanme of CCU system tree
subtype T_CCU_CONFIGURATION_NAME is MPS_DEFINITIONS.T_CONFIGURATION_NAME;
–– type of the name of a CCU configuration
type T_CCU_VERSION_STR is
record
VERSION : T_SYSTEM_TREE_VERSION_NUMBER_STR;
ISSUE : T_SYSTEM_TREE_VERSION_NUMBER_STR;
REVISION : T_SYSTEM_TREE_VERSION_NUMBER_STR;
end record;
–– string type for the CCU version
type T_CCU_INFO_STR is
record
ELEMENT_CONFIGURATION_NAME : T_ELEMENT_CONFIGURATION_NAME;
MISSION_NAME : T_MISSION_NAME;
SYSTEM_TREE_VERSION_NUMBER : T_SYSTEM_TREE_VERSION_NUMBER_STR;
CCU_SYSTEM_TREE_PATHNAME : T_CCU_SYSTEM_TREE_PATHNAME_STR;
CCU_CONFIGURATION_NAME : T_CCU_CONFIGURATION_NAME;
CCU_VERSION : T_CCU_VERSION_STR;
end record;
–– Type of a CCU info in string format
DEFAULT_SELECTION_CRITERIA_NB : constant POSITIVE := MAX_SELECTION_CRITERIA;
NULL_SESSION_NAME : constant T_SESSION_NAME := (others => ’ ’);
MAX_NUMBER_OF_SESSIONS_IN_DEF : constant INTEGER := 10;
–– maximum number of execution sessions initialised in definition
MAX_TITLE_LENGTH : constant POSITIVE := 50;
–– maximum length of title
MAX_TEST_PLAN_LENGTH : constant POSITIVE := 50;
–– maximum length of test plan
MAX_TEV_USER_NAME : constant POSITIVE := 80;
–– maximum length of tev user name
NULL_SYSTEM_TREE_VERSION_NUMBER_STR : constant T_SYSTEM_TREE_VERSION_NUMBER_STR := ” 0”;
–– Null value of a system tree
NULL_ELEMENT_CONFIGURATION_NAME : constant T_ELEMENT_CONFIGURATION_NAME := (others => ’ ’);
–– Null value of an element configuration
NULL_MISSION_NAME : constant T_MISSION_NAME := (others => ’ ’);
–– Null value of a mission name
NULL_CCU_SYSTEM_TREE_PATHNAME_STR : constant T_CCU_SYSTEM_TREE_PATHNAME_STR := (others => ’
–– Null value of a pathanme of CCU system tree
NULL_CCU_CONFIGURATION_NAME : constant T_CCU_CONFIGURATION_NAME := (others => ’ ’);
–– Null value of a name of a CCU configuration
NULL_CCU_VERSION_STR : constant T_CCU_VERSION_STR :=
(VERSION => NULL_SYSTEM_TREE_VERSION_NUMBER_STR,
ISSUE => NULL_SYSTEM_TREE_VERSION_NUMBER_STR,
REVISION => NULL_SYSTEM_TREE_VERSION_NUMBER_STR);
–– Null value of a system tree
NULL_CCU_INFO_STR : constant T_CCU_INFO_STR :=
(ELEMENT_CONFIGURATION_NAME => NULL_ELEMENT_CONFIGURATION_NAME,
MISSION_NAME => NULL_MISSION_NAME,
SYSTEM_TREE_VERSION_NUMBER => NULL_SYSTEM_TREE_VERSION_NUMBER_STR,
CCU_SYSTEM_TREE_PATHNAME => NULL_CCU_SYSTEM_TREE_PATHNAME_STR,
CCU_CONFIGURATION_NAME => NULL_CCU_CONFIGURATION_NAME,

Space Infrastructure
CCU_VERSION => NULL_CCU_VERSION_STR);
–– Null value of a CCU Info record
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
subtype T_SESSIONS_RANGE is POSITIVE range 1 .. MAX_NUMBER_OF_SESSIONS_IN_DEF;
–– number of sessions
type T_DEFINITION_SESSION_NAMES is array(POSITIVE range ) of T_SESSION_NAME;
–– array of execution sessions used to initialise
type T_ACCESS_STATUS is (READ, WRITE);
–– access status used to open a file
type T_CURRENT_STATUS is (OPENED, CLOSED);
–– status of the file
type T_SOURCE_FILE_TYPE is (ARCHIVED_FILE, ENG_LOG_FILE);
–– type of source file
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
497 von/of: 662
–– * ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– * New strings for the merge ADT_EVENT_RESULT/ADT_DATA_SET tool
–– * ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
EVENT_DEFINITION_STR_DELIMITER : constant string := ”EVENT DEFINITION”;
EV_DEFINITION_STR_UNDERLINE : constant string :=
(EVENT_DEFINITION_STR_DELIMITER’range => ’=’);
DATA_SET_DEFINITION_STR_DELIMITER : constant string := ”DATA SET DEFINITION”;
DS_DEFINITION_STR_UNDERLINE : constant string :=
(DATA_SET_DEFINITION_STR_DELIMITER’range => ’=’);
–– * ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
DEFINITION_STR_DELIMITER : constant string := ”1) DEFINITION”;
DEFINITION_STR_UNDERLINE : constant string := (DEFINITION_STR_DELIMITER’range => ’=’);
RESULT_STR_DELIMITER : constant string := ”2) RESULT”;
RESULT_STR_UNDERLINE : constant string := (RESULT_STR_DELIMITER’range => ’=’);
–– delimiter of definition and result parts in a result file
subtype T_TITLE is string(1..PORTRAIT_PAGE_WIDTH);
–– title description
subtype T_PORTRAIT_HEADER_LINE is string(1..PORTRAIT_PAGE_WIDTH);
type T_PORTRAIT_HEADER is array(positive range ) of T_PORTRAIT_HEADER_LINE;
subtype T_LANDSCAPE_HEADER_LINE is string(1..LANDSCAPE_PAGE_WIDTH);
type T_LANDSCAPE_HEADER is array(positive range ) of T_LANDSCAPE_HEADER_LINE;
–– header descriptions
subtype T_TEST_PLAN is STRING(1 .. MAX_TEST_PLAN_LENGTH);
–– test plan
subtype T_TEV_USER is STRING(1 .. MAX_TEV_USER_NAME);
–– tev user description
subtype T_TIME_STR is STRING(1 .. 12);
–– string definition of time
subtype T_DATE_STR is STRING(1 .. 8);
–– string date definition
subtype T_DATE_TIME_STR is STRING(1 .. 21);
–– string date and time definition
type T_TIME_FRAME_STR is
record
BEGIN_DATE_TIME : T_DATE_TIME_STR;
END_DATE_TIME : T_DATE_TIME_STR;
end record;
–– string definition of time frame
NULL_TITLE : constant T_TITLE := (others => ’ ’);
–– null title string
NULL_TEST_PLAN : constant T_TEST_PLAN := (others => ’ ’);
–– null test plan string

Space Infrastructure
NULL_DATE_STR : constant T_DATE_STR := (others => ’ ’);
–– null date string definition
NULL_TIME_STR : constant T_DATE_STR := (others => ’ ’);
–– null time string definition
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
NULL_DATE_TIME_STR : constant T_DATE_TIME_STR := (others => ’ ’);
–– null date and time string definition
NULL_TIME_FRAME_STR : constant T_TIME_FRAME_STR :=
(BEGIN_DATE_TIME => NULL_DATE_TIME_STR,
END_DATE_TIME => NULL_DATE_TIME_STR);
–– null time frame string definition
subtype T_PACKET_BYTES_LINE is POSITIVE;
–– number of bytes per line for packets
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
498 von/of: 662
subtype T_PACKET_PATHNAME is STRING(1 .. VICOS_DEFINITIONS.MAX_LENGTH_OF_DB_PATHNAME);
–– packet pathname
type T_PACKET_FORMAT is (DECIMAL, HEXADECIMAL, ASCII);
–– packet format
type T_PACKET_TYPE is (ADU, GDU, ADUS, GDUS, ALL_ADUS_GDUS, NO_CHOICE);
–– characteristic of packet selection criteria
type T_PACKET_DESCRIPTOR(CHOICE : T_PACKET_TYPE := ADUS) is record
case CHOICE is
when ADU | GDU => PATH : T_PACKET_PATHNAME;
when others => null;
end case;
end record;
–– Definition of a packet descriptor
type T_SAMPLING_TYPE is (N_SAMPLING,
TIME_BASED_SAMPLING,
MERGE);
–– sampling type in data sets
type T_SAMPLING_STR(SAMPLING_TYPE : T_SAMPLING_TYPE := N_SAMPLING) is
record
case SAMPLING_TYPE is
when N_SAMPLING =>
RESOLUTION : NATURAL := 1;
when TIME_BASED_SAMPLING =>
DELTA_T : T_TIME_STR;
EPSILON : T_TIME_STR;
when others =>
null;
end case;
end record;
type T_SAMPLING(SAMPLING_TYPE : T_SAMPLING_TYPE := N_SAMPLING) is record
case SAMPLING_TYPE is
when N_SAMPLING =>
RESOLUTION : NATURAL := 1;
when TIME_BASED_SAMPLING =>
DELTA_T : CGS_CALENDAR.CGS_TIME;
EPSILON : CGS_CALENDAR.CGS_TIME;
when others =>
null;
end case;
end record;
–– definition of sampling types
NULL_PACKET_PATHNAME : T_PACKET_PATHNAME := (others => ’ ’);
–– Null pathname of a packet
NULL_PACKET_DESCRIPTOR : constant T_PACKET_DESCRIPTOR := (CHOICE => NO_CHOICE);
–– null descriptor of a packet
DEFAULT_PACKET_TYPE : constant T_PACKET_TYPE := ADU;
–– default packets type

Space Infrastructure
DEFAULT_SAMPLING_STR : constant T_SAMPLING_STR :=
(SAMPLING_TYPE => N_SAMPLING,
RESOLUTION => 1);
DEFAULT_SAMPLING : constant T_SAMPLING :=
(SAMPLING_TYPE => N_SAMPLING,
RESOLUTION => 1);
–– default sampling definitions
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
DEFAULT_PACKET_FORMAT : constant T_PACKET_FORMAT := HEXADECIMAL;
–– default format for packets
DEFAULT_BYTES_LINE : constant POSITIVE := 32;
–– default number of bytes per line
MAX_LENGTH_OF_GRAPH_NAME : constant POSITIVE := 50;
–– maximum length of graph name
MAX_LENGTH_OF_AXIS_NAME : constant POSITIVE := 50;
–– maximum length of axis name
MAX_PARMS_IN_LINE_GRAPH : constant POSITIVE := 5;
–– maximum number of parameters in a line graph
MAX_PARMS_IN_CHART : constant POSITIVE := 5;
–– maximum number of parameters in a bar or pie chart
type T_SID_PATHNAME is
record
SID : MPS_DEFINITIONS.SID := MPS_DEFINITIONS.NULL_SID;
PATHNAME : T_PACKET_PATHNAME;
end record;
NULL_SID_PATHNAME : constant T_SID_PATHNAME
:= (SID => MPS_DEFINITIONS.NULL_SID,
PATHNAME => NULL_PACKET_PATHNAME);
type T_ENTRY_RANGE is
record
FROM_ENTRY : NATURAL := NATURAL’FIRST;
TO_ENTRY : NATURAL := NATURAL’FIRST;
end record;
–– entry range selection criteria for user result tables
type T_GRAPH_TYPE is (LINE, BAR, XY, PIE, UNDEFINED);
–– description of graph types
subtype T_GRAPH_NAME_RANGE is POSITIVE range 1 .. MAX_LENGTH_OF_GRAPH_NAME;
–– range of length of graph name
subtype T_GRAPH_NAME is STRING(T_GRAPH_NAME_RANGE);
–– description of graph name
subtype T_AXIS_NAME_RANGE is POSITIVE range 1 .. MAX_LENGTH_OF_AXIS_NAME;
–– range of length of axis name
subtype T_AXIS_NAME is STRING(T_AXIS_NAME_RANGE);
–– description of axis name
NULL_AXIS_NAME : constant T_AXIS_NAME := (others => ’ ’);
–– null axis name
type T_SCALING_TYPE is (INT_SCALE, FLOAT_SCALE, UNDEFINED);
–– description of graph scaling types
type T_GRAPH_SCALING is
record
SCALING_TYPE : T_SCALING_TYPE := UNDEFINED;
INT_MAX : INTEGER := 0;
INT_MIN : INTEGER := 0;
FLOAT_MAX : FLOAT := 0.0;
FLOAT_MIN : FLOAT := 0.0;
end record;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
499 von/of: 662

Space Infrastructure
–– record giving the graph scaling ie the maximum and minimum
–– values
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
DEFAULT_SCALING : constant T_GRAPH_SCALING := (UNDEFINED, 0, 0, 0.0, 0.0);
subtype T_MAX_MIN_STR is STRING(1 .. 10);
type T_GRAPH_SCALING_STR is
record
MAX : T_MAX_MIN_STR := (others => ’ ’);
MIN : T_MAX_MIN_STR := (others => ’ ’);
end record;
–– record giving the graph scaling in string format ie the
–– maximum and minimum values
type T_COLOUR is (RED, GREEN, BLUE, YELLOW, MAGENTA,
BLACK, WHITE, BROWN, CYAN, ORANGE, GREY);
–– Definition of colours available for graphs
type T_LINE_STYLE is (SOLID, DASHED, DOTTED, DASH_DOT, LONG_DASH);
–– Definition of line styles available for graphs
type T_LINE_THICKNESS is (’0’, ’1’, ’2’, ’4’);
–– Definition of line thickness for graphs (4 is thickest)
subtype T_LINE_GRAPH_RANGE is POSITIVE range 1 .. MAX_PARMS_IN_LINE_GRAPH;
–– range of number of parameters allowed in a line graph
subtype T_CHART_RANGE is POSITIVE range 1 .. MAX_PARMS_IN_CHART;
–– range of number of parameters allowed in a bar or pie chart
type T_PARAMETER_LINE_INFO is
record
COLOUR : T_COLOUR := BLACK;
LINE_STYLE : T_LINE_STYLE := SOLID;
LINE_THICKNESS : T_LINE_THICKNESS := ’0’;
TIME_FRAME : T_TIME_FRAME := NULL_TIME_FRAME;
end record;
–– parameter information for a line graph
type T_LINE_PARAMETERS_INFO is
array(T_LINE_GRAPH_RANGE) of T_PARAMETER_LINE_INFO;
–– array of parameter information for a line graph
DEFAULT_LINE_PARAMETERS_INFO : constant T_LINE_PARAMETERS_INFO :=(
(BLACK, SOLID, ’0’, NULL_TIME_FRAME),
(BLACK, LONG_DASH, ’0’, NULL_TIME_FRAME),
(BLACK, DASHED, ’0’, NULL_TIME_FRAME),
(BLACK, DOTTED, ’0’, NULL_TIME_FRAME),
(BLACK, DASH_DOT, ’0’, NULL_TIME_FRAME) );
type T_PARAMETER_LINE_INFO_STR is
record
PARAMETER : T_PARAMETER_NAME := NULL_PARAMETER_NAME;
ENG_UNIT : MPS_DEFINITIONS.T_ENGINEERING_UNIT;
COLOUR : T_COLOUR := BLACK;
LINE_STYLE : T_LINE_STYLE := SOLID;
LINE_THICKNESS : T_LINE_THICKNESS := ’0’;
TIME_FRAME : T_TIME_FRAME_STR;
Y_SCALING : T_GRAPH_SCALING_STR;
end record;
–– parameter information for a line graph in string format
type T_LINE_PARAMETERS_INFO_STR is
array(T_LINE_GRAPH_RANGE) of T_PARAMETER_LINE_INFO_STR;
–– array of parameter information for a line graph in string
–– format
type T_XY_INFO is
record
–– X_PARAMETER : T_PARAMETER_NAME := NULL_PARAMETER_NAME;
–– Y_PARAMETER : T_PARAMETER_NAME := NULL_PARAMETER_NAME;
–– X_ENG_UNITS : MPS_DEFINITIONS.T_ENGINEERING_UNIT;
–– Y_ENG_UNITS : MPS_DEFINITIONS.T_ENGINEERING_UNIT;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
500 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
X_NAME : T_AXIS_NAME := NULL_AXIS_NAME;
Y_NAME : T_AXIS_NAME := NULL_AXIS_NAME;
X_SCALING : T_GRAPH_SCALING;
Y_SCALING : T_GRAPH_SCALING;
COLOUR : T_COLOUR := BLACK;
LINE_STYLE : T_LINE_STYLE := SOLID;
LINE_THICKNESS : T_LINE_THICKNESS := ’0’;
end record;
–– information for an xy graph
type T_XY_INFO_STR is
record
X_PARAMETER : T_PARAMETER_NAME := NULL_PARAMETER_NAME;
Y_PARAMETER : T_PARAMETER_NAME := NULL_PARAMETER_NAME;
X_ENG_UNITS : MPS_DEFINITIONS.T_ENGINEERING_UNIT;
Y_ENG_UNITS : MPS_DEFINITIONS.T_ENGINEERING_UNIT;
X_NAME : T_AXIS_NAME := NULL_AXIS_NAME;
Y_NAME : T_AXIS_NAME := NULL_AXIS_NAME;
X_SCALING : T_GRAPH_SCALING_STR;
Y_SCALING : T_GRAPH_SCALING_STR;
COLOUR : T_COLOUR := BLACK;
LINE_STYLE : T_LINE_STYLE := SOLID;
LINE_THICKNESS : T_LINE_THICKNESS := ’0’;
end record;
–– information for an xy graph in string format
type T_PARAMETER_CHART_INFO is
record
PARAMETER : T_PARAMETER_NAME := NULL_PARAMETER_NAME;
ENG_UNIT : MPS_DEFINITIONS.T_ENGINEERING_UNIT;
COLOUR : T_COLOUR := BLACK;
end record;
subtype T_CHART_GRAPH_RANGE is POSITIVE range 1 .. MAX_PARMS_IN_CHART;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
501 von/of: 662
type T_CHART_COLOURS is array (T_CHART_GRAPH_RANGE) of T_COLOUR;
type T_CHART_PARAMETERS_INFO is array(T_CHART_GRAPH_RANGE) of T_PARAMETER_CHART_INFO;
–– parameter information for a chart
NULL_GRAPH_NAME : constant T_GRAPH_NAME := (others => ’ ’);
–– null graph name
NULL_GRAPH_SCALING : constant T_GRAPH_SCALING :=
(SCALING_TYPE => UNDEFINED,
INT_MAX => 0,
INT_MIN => 0,
FLOAT_MAX => 0.0, FLOAT_MIN => 0.0);
–– null graph scaling
NULL_GRAPH_SCALING_STR : constant T_GRAPH_SCALING_STR :=
(MAX => (others => ’ ’),
MIN => (others => ’ ’));
–– null graph scaling string
MAX_SAS_COMPLETION_STRING : constant POSITIVE := 255;
–– maximum length of a SAS completion string
MAX_SAS_PARAM_STRING : constant POSITIVE := 255;
–– maximum length of a SAS parameter string
subtype T_SAS_COMPLETION is STRING(1 .. MAX_SAS_COMPLETION_STRING);
–– definition of a SAS completion string
subtype T_SAS_PARAMS is STRING(1 .. MAX_SAS_PARAM_STRING);
–– definition of a SAS parameter string
–– ===================================================
–– Instantiation of VICOS_LIST for several list types :
–– ===================================================
package P_RESULT_NAME_LIST is new VICOS_LIST(T_RESULT_NAME);
subtype T_RESULT_NAME_L is P_RESULT_NAME_LIST.LIST;
–– definition of a list of result filenames (via the vicos list)

Space Infrastructure
package P_RESULT_REF_LIST is new VICOS_LIST(T_RESULT_REF);
subtype T_RESULT_REF_L is P_RESULT_REF_LIST.LIST;
–– definition of a list of result files (via the vicos list)
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
package P_DEFINITION_NAME_LIST is new VICOS_LIST(T_DEFINITION_NAME);
subtype T_DEFINITION_NAME_L is P_DEFINITION_NAME_LIST.LIST;
–– definition of a list of definition filenames (via the vicos list)
package P_SESSION_NAME_LIST is new VICOS_LIST(T_SESSION_NAME);
subtype T_SESSION_NAME_L is P_SESSION_NAME_LIST.LIST;
–– definition of a list of execution session names (via the vicos list)
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
502 von/of: 662
––(V3)
–– package P_SESSION_LIST is new VICOS_LIST(DBS_DEFINITIONS.T_EXECUTION_SESSION_INFO);
–– subtype T_SESSION_L is P_SESSION_LIST.LIST;
–– definition of a list of execution session info (via the vicos list)
package P_TABLE_NAME_LIST is new VICOS_LIST(T_TABLE_NAME);
subtype T_TABLE_NAME_L is P_TABLE_NAME_LIST.LIST;
–– definition of a list of result table names (via the vicos list)
package P_RESULT_LIST is new VICOS_LIST(T_EVALUATION_RESULT_FILE);
subtype T_RESULT_L is P_RESULT_LIST.LIST;
–– definition of a list of result files (via the vicos list)
package P_PARAMETER_NAME_LIST is new VICOS_LIST(T_PARAMETER_NAME);
subtype T_PARAMETER_NAME_L is P_PARAMETER_NAME_LIST.LIST;
–– definition of a list of parameters (via the vicos list)
package P_FILE_NAME_LIST is new VICOS_LIST(T_FILE_NAME);
subtype T_FILE_NAME_L is P_FILE_NAME_LIST.LIST;
–– definition of a list of filenames (via the vicos list)
package P_ENGINEERING_VALUE_LIST is new
VICOS_LIST(ADT_ENGINEERING_VALUE.T_ENGINEERING_VALUE);
subtype T_ENGINEERING_VALUE_L is P_ENGINEERING_VALUE_LIST.LIST;
–– definition of a list of engineering values (via the vicos list)
package P_DATE_AND_TIME_LIST is new VICOS_LIST(CGS_CALENDAR.CGS_DATE_AND_TIME);
subtype T_DATE_AND_TIME_L is P_DATE_AND_TIME_LIST.LIST;
–– definition of a list of date and time (via the vicos list)
package P_COMPLETE_FILENAME_LIST is new VICOS_LIST(T_COMPLETE_FILENAME);
subtype T_COMPLETE_FILENAME_L is P_COMPLETE_FILENAME_LIST.LIST;
–– definition of a list of complete filenames (via the vicos list)
package P_PARAMETER_VALUE_LIST is new VICOS_LIST(T_PARAMETER_VALUE);
subtype T_PARAMETER_VALUE_L is P_PARAMETER_VALUE_LIST.LIST;
–– definition of a list of values (via the vicos list)
–– =========== List operations on T_RESULT_NAME_L ================
procedure COPY (FROM_THE_LIST : in T_RESULT_NAME_L;
TO_THE_LIST : in out T_RESULT_NAME_L) renames P_RESULT_NAME_LIST.COPY;
procedure INVERT (THE_LIST : in T_RESULT_NAME_L;
TO_THE_LIST : in out T_RESULT_NAME_L) renames P_RESULT_NAME_LIST.INVERT;
procedure CLEAR (THE_LIST : in out T_RESULT_NAME_L) renames P_RESULT_NAME_LIST.CLEAR;
procedure ASSIGN (THE_LIST : in out T_RESULT_NAME_L;
NEW_LIST : in T_RESULT_NAME_L) renames P_RESULT_NAME_LIST.ASSIGN;
procedure CONSTRUCT (RESULT_NAME : in T_RESULT_NAME;
THE_LIST : in out T_RESULT_NAME_L) renames P_RESULT_NAME_LIST.CONSTRUCT;
function LENGTH_OF (THE_LIST : in T_RESULT_NAME_L) return natural
renames P_RESULT_NAME_LIST.LENGTH_OF;
function HEAD_OF (THE_LIST : in T_RESULT_NAME_L) return T_RESULT_NAME
renames P_RESULT_NAME_LIST.HEAD_OF;

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
503 von/of: 662
function TAIL_OF (THE_LIST : in T_RESULT_NAME_L) return T_RESULT_NAME_L
renames P_RESULT_NAME_LIST.TAIL_OF;
function IS_NULL (THE_LIST : in T_RESULT_NAME_L) return boolean
renames P_RESULT_NAME_LIST.IS_NULL;
function NULL_LIST return T_RESULT_NAME_L renames P_RESULT_NAME_LIST.NULL_LIST;
–– =========== List operations on T_RESULT_REF_L ================
procedure COPY (FROM_THE_LIST : in T_RESULT_REF_L;
TO_THE_LIST : in out T_RESULT_REF_L) renames P_RESULT_REF_LIST.COPY;
procedure INVERT (THE_LIST : in T_RESULT_REF_L;
TO_THE_LIST : in out T_RESULT_REF_L) renames P_RESULT_REF_LIST.INVERT;
procedure CLEAR (THE_LIST : in out T_RESULT_REF_L) renames P_RESULT_REF_LIST.CLEAR;
procedure ASSIGN (THE_LIST : in out T_RESULT_REF_L;
NEW_LIST : in T_RESULT_REF_L) renames P_RESULT_REF_LIST.ASSIGN;
procedure CONSTRUCT (RESULT_REF : in T_RESULT_REF;
THE_LIST : in out T_RESULT_REF_L) renames P_RESULT_REF_LIST.CONSTRUCT;
function LENGTH_OF (THE_LIST : in T_RESULT_REF_L) return natural
renames P_RESULT_REF_LIST.LENGTH_OF;
function HEAD_OF (THE_LIST : in T_RESULT_REF_L) return T_RESULT_REF
renames P_RESULT_REF_LIST.HEAD_OF;
function TAIL_OF (THE_LIST : in T_RESULT_REF_L) return T_RESULT_REF_L
renames P_RESULT_REF_LIST.TAIL_OF;
function IS_NULL (THE_LIST : in T_RESULT_REF_L) return boolean
renames P_RESULT_REF_LIST.IS_NULL;
function NULL_LIST return T_RESULT_REF_L renames P_RESULT_REF_LIST.NULL_LIST;
–– =========== List operations on T_DEFINITION_NAME_L ================
procedure COPY (FROM_THE_LIST : in T_DEFINITION_NAME_L;
TO_THE_LIST : in out T_DEFINITION_NAME_L) renames P_DEFINITION_NAME_LIST.COPY;
procedure INVERT (THE_LIST : in T_DEFINITION_NAME_L;
TO_THE_LIST : in out T_DEFINITION_NAME_L) renames P_DEFINITION_NAME_LIST.INVERT;
procedure CLEAR (THE_LIST : in out T_DEFINITION_NAME_L)
renames P_DEFINITION_NAME_LIST.CLEAR;
procedure ASSIGN (THE_LIST : in out T_DEFINITION_NAME_L;
NEW_LIST : in T_DEFINITION_NAME_L) renames P_DEFINITION_NAME_LIST.ASSIGN;
procedure CONSTRUCT (DEFINITION_NAME : in T_DEFINITION_NAME;
THE_LIST : in out T_DEFINITION_NAME_L) renames P_DEFINITION_NAME_LIST.CONSTRUCT;
function LENGTH_OF (THE_LIST : in T_DEFINITION_NAME_L) return natural
renames P_DEFINITION_NAME_LIST.LENGTH_OF;
function HEAD_OF (THE_LIST : in T_DEFINITION_NAME_L) return T_DEFINITION_NAME
renames P_DEFINITION_NAME_LIST.HEAD_OF;
function TAIL_OF (THE_LIST : in T_DEFINITION_NAME_L) return T_DEFINITION_NAME_L
renames P_DEFINITION_NAME_LIST.TAIL_OF;
function IS_NULL (THE_LIST : in T_DEFINITION_NAME_L) return boolean
renames P_DEFINITION_NAME_LIST.IS_NULL;
function NULL_LIST return T_DEFINITION_NAME_L renames P_DEFINITION_NAME_LIST.NULL_LIST;
–– =========== List operations on T_SESSION_NAME_L ================
procedure COPY(FROM_THE_LIST : in T_SESSION_NAME_L;
TO_THE_LIST : in out T_SESSION_NAME_L) renames P_SESSION_NAME_LIST.COPY;

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
504 von/of: 662
procedure INVERT(THE_LIST : in T_SESSION_NAME_L;
TO_THE_LIST : in out T_SESSION_NAME_L) renames P_SESSION_NAME_LIST.INVERT;
procedure CLEAR(THE_LIST : in out T_SESSION_NAME_L)
renames P_SESSION_NAME_LIST.CLEAR;
procedure ASSIGN(THE_LIST : in out T_SESSION_NAME_L;
NEW_LIST : in T_SESSION_NAME_L) renames P_SESSION_NAME_LIST.ASSIGN;
procedure CONSTRUCT(SESSION_NAME : in T_SESSION_NAME;
THE_LIST : in out T_SESSION_NAME_L) renames P_SESSION_NAME_LIST.CONSTRUCT;
function LENGTH_OF(THE_LIST : in T_SESSION_NAME_L) return natural
renames P_SESSION_NAME_LIST.LENGTH_OF;
function HEAD_OF(THE_LIST : in T_SESSION_NAME_L) return T_SESSION_NAME
renames P_SESSION_NAME_LIST.HEAD_OF;
function TAIL_OF (THE_LIST : in T_SESSION_NAME_L) return T_SESSION_NAME_L
renames P_SESSION_NAME_LIST.TAIL_OF;
function IS_NULL(THE_LIST : in T_SESSION_NAME_L) return boolean
renames P_SESSION_NAME_LIST.IS_NULL;
function NULL_LIST return T_SESSION_NAME_L renames P_SESSION_NAME_LIST.NULL_LIST;
procedure REMOVE_ITEM(IN_THE_LIST : in out T_SESSION_NAME_L;
AT_THE_POSITION : in POSITIVE)
renames P_SESSION_NAME_LIST.REMOVE_ITEM;
–– =========== List operations on T_SESSION_L ================
––(V3)
–– procedure INVERT(THE_LIST : in T_SESSION_L;
––
––
TO_THE_LIST : in out T_SESSION_L) renames P_SESSION_LIST.INVERT;
––
––
procedure CLEAR(THE_LIST : in out T_SESSION_L) renames P_SESSION_LIST.CLEAR;
–– procedure ASSIGN(THE_LIST : in out T_SESSION_L;
––
––
NEW_LIST : in T_SESSION_L) renames P_SESSION_LIST.ASSIGN;
–– procedure CONSTRUCT(DATA_VALUE : in DBS_DEFINITIONS.T_EXECUTION_SESSION_INFO;
––
––
THE_LIST : in out T_SESSION_L) renames P_SESSION_LIST.CONSTRUCT;
––
––
function NULL_LIST RETURN T_SESSION_L renames P_SESSION_LIST.NULL_LIST;
–– function IS_NULL(THE_LIST : in T_SESSION_L) RETURN boolean
––
––
renames P_SESSION_LIST.IS_NULL;
–– function HEAD_OF(THE_LIST : in T_SESSION_L) RETURN DBS_DEFINITIONS.T_EXECUTION_SESSION_INFO
––
––
renames P_SESSION_LIST.HEAD_OF;
–– function TAIL_OF (THE_LIST : in T_SESSION_L) RETURN T_SESSION_L
––
––
renames P_SESSION_LIST.TAIL_OF;
–– function LENGTH_OF(THE_LIST : in T_SESSION_L) RETURN natural
––
––
renames P_SESSION_LIST.LENGTH_OF;
–– procedure COPY(FROM_THE_LIST : in T_SESSION_L;
–– TO_THE_LIST : in out T_SESSION_L) renames P_SESSION_LIST.COPY;
–– =========== List operations on T_TABLE_NAME_L ================
procedure INVERT(THE_LIST : in T_TABLE_NAME_L;
TO_THE_LIST : in out T_TABLE_NAME_L) renames P_TABLE_NAME_LIST.INVERT;
procedure CLEAR(THE_LIST : in out T_TABLE_NAME_L)
renames P_TABLE_NAME_LIST.CLEAR;
procedure ASSIGN(THE_LIST : in out T_TABLE_NAME_L;
NEW_LIST : in T_TABLE_NAME_L) renames P_TABLE_NAME_LIST.ASSIGN;

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
505 von/of: 662
procedure CONSTRUCT(TABLE_NAME : in T_TABLE_NAME;
THE_LIST : in out T_TABLE_NAME_L)renames P_TABLE_NAME_LIST.CONSTRUCT;
function NULL_LIST RETURN T_TABLE_NAME_L renames P_TABLE_NAME_LIST.NULL_LIST;
function IS_NULL(THE_LIST : in T_TABLE_NAME_L) RETURN boolean
renames P_TABLE_NAME_LIST.IS_NULL;
function HEAD_OF(THE_LIST : in T_TABLE_NAME_L) RETURN T_TABLE_NAME
renames P_TABLE_NAME_LIST.HEAD_OF;
function TAIL_OF (THE_LIST : in T_TABLE_NAME_L) RETURN T_TABLE_NAME_L
renames P_TABLE_NAME_LIST.TAIL_OF;
function LENGTH_OF(THE_LIST : in T_TABLE_NAME_L) RETURN natural
renames P_TABLE_NAME_LIST.LENGTH_OF;
procedure COPY(FROM_THE_LIST : in T_TABLE_NAME_L;
TO_THE_LIST : in out T_TABLE_NAME_L) renames P_TABLE_NAME_LIST.COPY;
–– =========== List operations on T_RESULT_L ================
procedure COPY (FROM_THE_LIST : in T_RESULT_L;
TO_THE_LIST : in out T_RESULT_L) renames P_RESULT_LIST.COPY;
procedure INVERT (THE_LIST : in T_RESULT_L;
TO_THE_LIST : in out T_RESULT_L) renames P_RESULT_LIST.INVERT;
procedure CLEAR (THE_LIST : in out T_RESULT_L)
renames P_RESULT_LIST.CLEAR;
procedure ASSIGN (THE_LIST : in out T_RESULT_L;
NEW_LIST : in T_RESULT_L) renames P_RESULT_LIST.ASSIGN;
procedure CONSTRUCT (RESULT_FILE : in T_EVALUATION_RESULT_FILE;
THE_LIST : in out T_RESULT_L) renames P_RESULT_LIST.CONSTRUCT;
function LENGTH_OF (THE_LIST : in T_RESULT_L) return natural
renames P_RESULT_LIST.LENGTH_OF;
function HEAD_OF (THE_LIST : in T_RESULT_L) return T_EVALUATION_RESULT_FILE
renames P_RESULT_LIST.HEAD_OF;
function TAIL_OF (THE_LIST : in T_RESULT_L) return T_RESULT_L
renames P_RESULT_LIST.TAIL_OF;
function IS_NULL (THE_LIST : in T_RESULT_L) return boolean
renames P_RESULT_LIST.IS_NULL;
function NULL_LIST return T_RESULT_L renames P_RESULT_LIST.NULL_LIST;
–– =========== List operations on T_PARAMETER_NAME_L ================
procedure COPY (FROM_THE_LIST : in T_PARAMETER_NAME_L;
TO_THE_LIST : in out T_PARAMETER_NAME_L) renames P_PARAMETER_NAME_LIST.COPY;
procedure INVERT (THE_LIST : in T_PARAMETER_NAME_L;
TO_THE_LIST : in out T_PARAMETER_NAME_L)
renames P_PARAMETER_NAME_LIST.INVERT;
procedure CLEAR (THE_LIST : in out T_PARAMETER_NAME_L)
renames P_PARAMETER_NAME_LIST.CLEAR;
procedure ASSIGN (THE_LIST : in out T_PARAMETER_NAME_L;
NEW_LIST : in T_PARAMETER_NAME_L) renames P_PARAMETER_NAME_LIST.ASSIGN;
procedure CONSTRUCT (PARAMETER_NAME : in T_PARAMETER_NAME;
THE_LIST : in out T_PARAMETER_NAME_L)
renames P_PARAMETER_NAME_LIST.CONSTRUCT;
function LENGTH_OF (THE_LIST : in T_PARAMETER_NAME_L) return natural
renames P_PARAMETER_NAME_LIST.LENGTH_OF;

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
function HEAD_OF (THE_LIST : in T_PARAMETER_NAME_L) return T_PARAMETER_NAME
renames P_PARAMETER_NAME_LIST.HEAD_OF;
function TAIL_OF (THE_LIST : in T_PARAMETER_NAME_L) return T_PARAMETER_NAME_L
renames P_PARAMETER_NAME_LIST.TAIL_OF;
function IS_NULL (THE_LIST : in T_PARAMETER_NAME_L) return boolean
renames P_PARAMETER_NAME_LIST.IS_NULL;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
506 von/of: 662
function NULL_LIST return T_PARAMETER_NAME_L renames P_PARAMETER_NAME_LIST.NULL_LIST;
–– =========== List operations on T_FILE_NAME_L ================
procedure COPY (FROM_THE_LIST : in T_FILE_NAME_L;
TO_THE_LIST : in out T_FILE_NAME_L) renames P_FILE_NAME_LIST.COPY;
procedure INVERT (THE_LIST : in T_FILE_NAME_L;
TO_THE_LIST : in out T_FILE_NAME_L) renames P_FILE_NAME_LIST.INVERT;
procedure CLEAR (THE_LIST : in out T_FILE_NAME_L)
renames P_FILE_NAME_LIST.CLEAR;
procedure ASSIGN (THE_LIST : in out T_FILE_NAME_L;
NEW_LIST : in T_FILE_NAME_L) renames P_FILE_NAME_LIST.ASSIGN;
procedure CONSTRUCT (FILE_NAME : in T_FILE_NAME;
THE_LIST : in out T_FILE_NAME_L) renames P_FILE_NAME_LIST.CONSTRUCT;
function LENGTH_OF (THE_LIST : in T_FILE_NAME_L) return natural
renames P_FILE_NAME_LIST.LENGTH_OF;
function HEAD_OF (THE_LIST : in T_FILE_NAME_L) return T_FILE_NAME
renames P_FILE_NAME_LIST.HEAD_OF;
function TAIL_OF (THE_LIST : in T_FILE_NAME_L) return T_FILE_NAME_L
renames P_FILE_NAME_LIST.TAIL_OF;
function IS_NULL (THE_LIST : in T_FILE_NAME_L) return boolean
renames P_FILE_NAME_LIST.IS_NULL;
function NULL_LIST return T_FILE_NAME_L renames P_FILE_NAME_LIST.NULL_LIST;
–– =========== List operations on T_ENGINEERING_VALUE_L ================
procedure COPY (FROM_THE_LIST : in T_ENGINEERING_VALUE_L;
TO_THE_LIST : in out T_ENGINEERING_VALUE_L)
renames P_ENGINEERING_VALUE_LIST.COPY;
procedure INVERT (THE_LIST : in T_ENGINEERING_VALUE_L;
TO_THE_LIST : in out T_ENGINEERING_VALUE_L )
renames P_ENGINEERING_VALUE_LIST.INVERT;
procedure CLEAR (THE_LIST : in out T_ENGINEERING_VALUE_L)
renames P_ENGINEERING_VALUE_LIST.CLEAR;
procedure ASSIGN (THE_LIST : in out T_ENGINEERING_VALUE_L ;
NEW_LIST : in T_ENGINEERING_VALUE_L) renames P_ENGINEERING_VALUE_LIST.ASSIGN;
procedure CONSTRUCT (ENGINEERING_VALUE : in ADT_ENGINEERING_VALUE.T_ENGINEERING_VALUE;
THE_LIST : in out T_ENGINEERING_VALUE_L) renames P_ENGINEERING_VALUE_LIST.CONSTRUCT;
function LENGTH_OF (THE_LIST : in T_ENGINEERING_VALUE_L) return natural
renames P_ENGINEERING_VALUE_LIST.LENGTH_OF;
function HEAD_OF (THE_LIST : in T_ENGINEERING_VALUE_L)
return ADT_ENGINEERING_VALUE.T_ENGINEERING_VALUE
renames P_ENGINEERING_VALUE_LIST.HEAD_OF;
function TAIL_OF (THE_LIST : in T_ENGINEERING_VALUE_L) return T_ENGINEERING_VALUE_L
renames P_ENGINEERING_VALUE_LIST.TAIL_OF;
function IS_NULL (THE_LIST : in T_ENGINEERING_VALUE_L) return boolean
renames P_ENGINEERING_VALUE_LIST.IS_NULL;

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
function NULL_LIST return T_ENGINEERING_VALUE_L
renames P_ENGINEERING_VALUE_LIST.NULL_LIST;
–– =========== List operations on T_DATE_AND_TIME_L ================
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
507 von/of: 662
procedure COPY (FROM_THE_LIST : in T_DATE_AND_TIME_L;
TO_THE_LIST : in out T_DATE_AND_TIME_L) renames P_DATE_AND_TIME_LIST.COPY;
procedure INVERT (THE_LIST : in T_DATE_AND_TIME_L;
TO_THE_LIST : in out T_DATE_AND_TIME_L )
renames P_DATE_AND_TIME_LIST.INVERT;
procedure CLEAR (THE_LIST : in out T_DATE_AND_TIME_L )
renames P_DATE_AND_TIME_LIST.CLEAR;
procedure ASSIGN (THE_LIST : in out T_DATE_AND_TIME_L ;
NEW_LIST : in T_DATE_AND_TIME_L) renames P_DATE_AND_TIME_LIST.ASSIGN;
procedure CONSTRUCT (DATE_AND_TIME : in CGS_CALENDAR.CGS_DATE_AND_TIME;
THE_LIST : in out T_DATE_AND_TIME_L) renames P_DATE_AND_TIME_LIST.CONSTRUCT;
function LENGTH_OF (THE_LIST : in T_DATE_AND_TIME_L) return natural
renames P_DATE_AND_TIME_LIST.LENGTH_OF;
function HEAD_OF (THE_LIST : in T_DATE_AND_TIME_L) return
CGS_CALENDAR.CGS_DATE_AND_TIME renames P_DATE_AND_TIME_LIST.HEAD_OF;
function TAIL_OF (THE_LIST : in T_DATE_AND_TIME_L) return T_DATE_AND_TIME_L
renames P_DATE_AND_TIME_LIST.TAIL_OF;
function IS_NULL (THE_LIST : in T_DATE_AND_TIME_L) return boolean
renames P_DATE_AND_TIME_LIST.IS_NULL;
function NULL_LIST return T_DATE_AND_TIME_L renames P_DATE_AND_TIME_LIST.NULL_LIST;
–– =========== List operations on T_COMPLETE_FILENAME_L ================
procedure COPY (FROM_THE_LIST : in T_COMPLETE_FILENAME_L;
TO_THE_LIST : in out T_COMPLETE_FILENAME_L)
renames P_COMPLETE_FILENAME_LIST.COPY;
procedure INVERT (THE_LIST : in T_COMPLETE_FILENAME_L;
TO_THE_LIST : in out T_COMPLETE_FILENAME_L )
renames P_COMPLETE_FILENAME_LIST.INVERT;
procedure CLEAR (THE_LIST : in out T_COMPLETE_FILENAME_L )
renames P_COMPLETE_FILENAME_LIST.CLEAR;
procedure ASSIGN (THE_LIST : in out T_COMPLETE_FILENAME_L ;
NEW_LIST : in T_COMPLETE_FILENAME_L) renames P_COMPLETE_FILENAME_LIST.ASSIGN;
procedure CONSTRUCT (COMPLETE_FILENAME : in T_COMPLETE_FILENAME;
THE_LIST : in out T_COMPLETE_FILENAME_L) renames P_COMPLETE_FILENAME_LIST.CONSTRUCT;
function LENGTH_OF (THE_LIST : in T_COMPLETE_FILENAME_L) return natural
renames P_COMPLETE_FILENAME_LIST.LENGTH_OF;
function HEAD_OF (THE_LIST : in T_COMPLETE_FILENAME_L) return
T_COMPLETE_FILENAME renames P_COMPLETE_FILENAME_LIST.HEAD_OF;
function TAIL_OF (THE_LIST : in T_COMPLETE_FILENAME_L) return T_COMPLETE_FILENAME_L
renames P_COMPLETE_FILENAME_LIST.TAIL_OF;
function IS_NULL (THE_LIST : in T_COMPLETE_FILENAME_L) return boolean
renames P_COMPLETE_FILENAME_LIST.IS_NULL;
function NULL_LIST return T_COMPLETE_FILENAME_L renames P_COMPLETE_FILENAME_LIST.NULL_LIST;
procedure INVERT(THE_LIST : in T_PARAMETER_VALUE_L;
TO_THE_LIST : in out T_PARAMETER_VALUE_L)
renames P_PARAMETER_VALUE_LIST.INVERT;
––

Space Infrastructure
–– Invert a list into another list
––
–– INVERT is a member of Data_Set_Opns
procedure CLEAR(THE_LIST : in out T_PARAMETER_VALUE_L)
renames P_PARAMETER_VALUE_LIST.CLEAR;
––
–– Clear a list
––
–– CLEAR is a member of Data_Set_Opns
procedure ASSIGN(THE_LIST : in out T_PARAMETER_VALUE_L;
NEW_LIST : in T_PARAMETER_VALUE_L)
renames P_PARAMETER_VALUE_LIST.ASSIGN;
––
––
–– Assign a list with a new value
––
–– ASSIGN is a member of Data_Set_Opns
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
procedure CONSTRUCT(DATA_VALUE : in T_PARAMETER_VALUE;
THE_LIST : in out T_PARAMETER_VALUE_L)
renames P_PARAMETER_VALUE_LIST.CONSTRUCT;
––
––
–– Construct a list by adding a new item
––
–– CONSTRUCT is a member of Data_Set_Opns
function NULL_LIST return T_PARAMETER_VALUE_L
renames P_PARAMETER_VALUE_LIST.NULL_LIST;
––
–– Return a null list
––
–– NULL_LIST is a member of Data_Set_Opns
function IS_NULL(THE_LIST : in T_PARAMETER_VALUE_L)
return BOOLEAN
renames P_PARAMETER_VALUE_LIST.IS_NULL;
––
–– Check if a list is null
––
–– IS_NULL is a member of Data_Set_Opns
function HEAD_OF(THE_LIST : in T_PARAMETER_VALUE_L)
return T_PARAMETER_VALUE
renames P_PARAMETER_VALUE_LIST.HEAD_OF;
––
–– Extract the head of a list
––
–– HEAD_OF is a member of Data_Set_Opns
function TAIL_OF(THE_LIST : in T_PARAMETER_VALUE_L)
return T_PARAMETER_VALUE_L
renames P_PARAMETER_VALUE_LIST.TAIL_OF;
––
–– Extract the tail of a list
––
–– TAIL_OF is a member of Data_Set_Opns
function LENGTH_OF(THE_LIST : in T_PARAMETER_VALUE_L)
return NATURAL
renames P_PARAMETER_VALUE_LIST.LENGTH_OF;
––
–– Get the length of a list
––
–– LENGTH_OF is a member of Data_Set_Opns
procedure COPY(FROM_THE_LIST : in T_PARAMETER_VALUE_L;
TO_THE_LIST : in out T_PARAMETER_VALUE_L)
renames P_PARAMETER_VALUE_LIST.COPY;
––
–– Copy a list into another list;
––
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
508 von/of: 662

Space Infrastructure
–– COPY is a member of Data_Set_Opns
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
procedure REMOVE_ITEM(IN_THE_LIST : in out T_PARAMETER_VALUE_L;
AT_THE_POSITION : in POSITIVE)
renames P_PARAMETER_VALUE_LIST.REMOVE_ITEM;
––
–– Removes an item from a list;
––
–– REMOVE_ITEM is a member of Data_Set_Opns
–– Provided exceptions :
OVERFLOW : exception;
–– Exception raised during list management
LIST_IS_NULL : exception;
–– Exception raised during list management
NOT_AT_HEAD : exception;
–– Exception raised during list management
PROTECTION_WARNING : exception;
–– Exception raised during list management
PROTECTION_VIOLATION : exception;
–– Exception raised during list management
POSITION_ERROR : exception;
–– Exception raised during list management
LEXICAL_ERROR : exception;
–– Exception raised during conversion of time from string to Ada type.
–– The syntactic format of the string is incorrect.
TIME_ERROR : exception;
–– Exception raised during conversion of time from string to Ada type.
–– The semantic format of the string is incorrect.
end TEV_DEFINITIONS;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
509 von/of: 662

Space Infrastructure
7.14 TEV Application Programmer Interface
Informal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
510 von/of: 662
The purpose of TEV_API is to give the user the possibility to extend the set of evaluation operations available
with TEV by addition of Special Application Software (SAS). When specific data processing (e.g. specific display,
specific sampling or calculation) is needed but not supported by the TEV standard tools, the user can write
additional programs that use the outputs of TEV tools as input for special processing.
Typical SAS functions may be :
– special statistic processing beyond the scope of the TEV Statistic tool,
– special mathematical processing, like Fourier Function Transfert beyond the scope of the TEV Mathematical
tool,
– data visualization beyond the scope of the TEV Graph tool,
– generation of special output formats, possibly to be included into TEV reports,
– special processing on other TRDB data types like Log Events etc,
– generation of special output formats to adapt to other commercial SW like spreadsheet or DTP...
The SAS gets selected result files to be processed from TEV and produces its own outputs.
The output of a SAS can be :
– a screen display,
– a SAS result file, which has its own internal structure not necessarily known to TEV,
– standard TEV Data Sets, which can be normally processed by standard TEV tools.
The API consists mainly in Abstract Data Types, i.e. Ada packages which describe the TEV result file types,
and which provide also the access operations to it.
The API gives the SAS programmer the freedom to write an Ada program, access the TEV result files via ADT
operations, do his special processing and deliver his result.
The control interface is simple: A SAS will be started from generic TEV together with the parameters needed
by the SAS. If the SAS is started via HLCL command, the parameter line (which is a simple string) is routed
transparently through the HLCL interpreter onto the SAS.
The SAS will become a child process of TEV. When the SAS completed the processing, it delivers the status
back and exits. It is to be seen as a one–shot operation. If an error appears, it normally will be returned with the
exit statement.
The API provides increased software security and also for software compilation and linking, (i.e. no need to reduce
software compilation on addition of a new SAS).
Formal Interface Description
In the following pages, you will find the specification of the package TEV_API written in Ada. If inconsistencies
exist with the informal description, then the formal description is superseding.

Space Infrastructure
Formal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
––
–– ADT_EVENT_RESULT
––
––****************************************************************************
––ABSTRACT––
––
–– Provides operations to access an events result file.
––
––*–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––IDENTIFICATION––
–– PROJECT NAME : CGS
–– PRODUCT NAME : TEV
–– CI–NUMBER : 1216 858
–– OBJECT NAME : HDT_TEV_API.ADT_EVENT_RESULT
––*–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––CONTENTS––
–– COMPILER : VERDIX ADA 6.0.3.C
–– LANGUAGE : ADA
–– SPECIAL CONTENTS:
–– CHANGE HISTORY
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– CGS V4.3 at DASA
–– creator: Bruening
–– creation date: 06.09.99
–– comment:
–– Define new type EVENTS_CHAIN to handle undefined number of events.
–– For the merge ADT_DATA_SET/EVENT tool
–– New procedures :
–– function POINTER_TO_FIRST_EVENT
–– procedure LIST_EVENTS_FOR_TIME_TAG
–– function RETURN_LONG_TEXT_FLAG
–– procedure CALL_FORMAT_DEFINITION
–– procedure LIST_EVENTS_AFTER_TIME_TAG
–– function GLOBAL_TIME_FRAME_OF
––
–– Procedures which where internal and now provided :
–– procedure PUT_LONG_STRING
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– CGS V4.2 ICD Change 27.07.99, W.Tammen:
–– harmonized record components (referenced types)
–– according to COL–RIBRE–IRN–CGS–8078
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– V5.2 at Central Repository V4.0 (moon)
–– creator: thvvicos (on host darkvador)
–– creation date: 20.07.97 20:54:36
–– comment:
–– Compliance with 4.1 : Tool id added
––
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V4.3 at Spacebel Informatique, Brussels
–– creator: rowena (on host moon)
–– creation date: 25.07.95 10:46:40
–– comment:
–– Move from VICOS_CALENDAR to CGS_CALENDAR
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V4.2 at Spacebel Informatique, Brussels
–– creator: rowena (on host moon)
–– creation date: 14.07.95 11:05:41
–– comment:
–– Updated with correct version of file from cm_user repository.
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
511 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–– END HISTORY
––****************************************************************************
––
––
with TEV_DEFINITIONS;
with VICOS_DEFINITIONS;
with DBS_DEFINITIONS;
with VICOS_LIST;
with CGS_CALENDAR;
with DIRECT_IO;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
512 von/of: 662
package ADT_EVENT_RESULT is
–– Provided types and constants :
subtype T_SESSIONS_RANGE_INC_DEF is POSITIVE range
TEV_DEFINITIONS.T_SESSIONS_RANGE’first..TEV_DEFINITIONS.T_SESSIONS_RANGE’last+1;
–– number of sessions including default test session
type T_EVENT is
record
PRODUCER: VICOS_DEFINITIONS.T_APPLICATION_NAME
:= VICOS_DEFINITIONS.EMPTY_NAME_STRING;
GROUP : VICOS_DEFINITIONS.T_LOG_GROUP := VICOS_DEFINITIONS.NULL_LOG_GROUP;
EVENT_TYPE : VICOS_DEFINITIONS.T_LOG_TYPE := VICOS_DEFINITIONS.NULL_LOG_TYPE;
SHORT_TEXT : VICOS_DEFINITIONS.T_LOG_TEXT_SHORT
:= VICOS_DEFINITIONS.NULL_LOG_TEXT_SHORT;
LONG_TEXT : VICOS_DEFINITIONS.T_LOG_TEXT_LONG
:= VICOS_DEFINITIONS.NULL_LOG_TEXT_LONG;
TIME_TAG_LT : CGS_CALENDAR.CGS_DATE_AND_TIME := CGS_CALENDAR.NULL_DATE_AND_TIME;
TIME_TAG_SMT : CGS_CALENDAR.CGS_DATE_AND_TIME := CGS_CALENDAR.NULL_DATE_AND_TIME;
end record;
–– definition of an event inside an event result
type EVENTS_CHAIN;
type P_EVENTS_CHAIN is access EVENTS_CHAIN;
type EVENTS_CHAIN is
record
EVENT : ADT_EVENT_RESULT.T_EVENT;
NEXT : P_EVENTS_CHAIN;
end record;
procedure FREE_EVENTS_CHAIN is new unchecked_deallocation
(OBJECT => EVENTS_CHAIN,
NAME => P_EVENTS_CHAIN);
NULL_SELECTION_CRITERIA : constant DBS_DEFINITIONS.T_EVENT_SEL_CRIT :=
(APPLICATION => VICOS_DEFINITIONS.EMPTY_NAME_STRING,
TIME_FRAME => DBS_DEFINITIONS.NULL_TIME_RECORD,
LOG_TYPE => VICOS_DEFINITIONS.NULL_LOG_TYPE,
LOG_GROUP => VICOS_DEFINITIONS.NULL_LOG_GROUP,
TEXT => VICOS_DEFINITIONS.NULL_LOG_TEXT_SHORT);
––
–– Null value of a selection criteria
––
type T_SELECTION_CRITERIA_A is array(
DBS_DEFINITIONS.T_EVENT_SEL_CRIT_RANGE) of
DBS_DEFINITIONS.T_EVENT_SEL_CRIT;
–– description of the combined selection criteria array
package P_EVENT_LIST is new VICOS_LIST(T_EVENT);
subtype T_EVENT_L is P_EVENT_LIST.LIST;
–– definition of a list of events (via the vicos list)
type T_EVENT_RESULT is limited private;
–– private adt event_result file
–– Provided operations :
procedure OPEN(EVENT_FILENAME : in STRING;
EVENT_RESULT : in out T_EVENT_RESULT;
ACCESS_STATUS : in TEV_DEFINITIONS.T_ACCESS_STATUS
:= TEV_DEFINITIONS.READ;
ALLOW_OVERWRITE : in BOOLEAN := FALSE);
–– Open an event result with read access if the file already exists,

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
513 von/of: 662
–– write access to create a new one. The EXECUTION_TIME is
–– written if it is a new file
––
–– Parameters :
–– EVENT_FILENAME : filename of the event result
–– EVENT_RESULT : private event result
–– ACCESS_STATUS : READ only to extract information from an event result
–– WRITE when generating a new event result
–– ALLOW_OVERWRITE : Required when access state is write to
–– allow generation of an event result inside an already
–– existing file.
–– Exceptions :
–– X_ERROR_ACCESSING_FILE : general error reported when
–– accessing the file
–– X_EVENT_RESULT_ALREADY_OPENED : event result is still in
–– open state
–– X_EVENT_RESULT_ALREADY_EXISTS : file exists and overwrite
–– is not allowed
–– X_INVALID_NAME : event result name is too long
––
procedure CLOSE(EVENT_RESULT : in out T_EVENT_RESULT);
–– Close a previously opened event result
––
–– Parameters :
–– EVENT_RESULT : private event result
–– Exceptions :
–– X_ERROR_ACCESSING_FILE : general error reported when
–– accessing the file
–– X_EVENT_RESULT_NOT_OPENED : event result already closed
––
procedure DEFINE(EVENT_RESULT : in out T_EVENT_RESULT;
EVENT_RESULT_NAME : in TEV_DEFINITIONS.T_RESULT_NAME;
INCLUDE_DEF_SESSION : in BOOLEAN;
SELECT_ON : in DBS_DEFINITIONS.T_TIME_TYPE;
ORDER_BY : in DBS_DEFINITIONS.T_TIME_ORDERING;
LONG_TEXT_FLAG_ON : in BOOLEAN;
SELECTION_CRITERIA : in T_SELECTION_CRITERIA_A);
–– Build and initialise the definition of an opened event result
––
–– Parameters :
–– EVENT_RESULT : private event result
–– EVENT_RESULT_NAME : name of the event result
–– INCLUDE_DEF_SESSION : include default session
–– LONG_TEXT_FLAG_ON : display long text
–– SELECTION_CRITERIA : array of event selection criteria (up to 4)
–– Exceptions :
–– X_EVENT_RESULT_NOT_OPENED : event result is not opened
–– X_NO_WRITE_ACCESS : event result not opened for write access
––
function FILENAME_OF(EVENT_RESULT : in T_EVENT_RESULT)
return STRING;
–– Return the event result file name.
––
–– Parameters :
–– EVENT_RESULT : private event result
–– Exceptions :
–– X_EVENT_RESULT_NOT_OPENED : event result is not opened
–– X_NO_READ_ACCESS : event result file not opened for read access
––
function GET_SELECTION_CRITERIA(EVENT_RESULT : in T_EVENT_RESULT;
CRITERIA_NO : in DBS_DEFINITIONS.T_EVENT_SEL_CRIT_RANGE)
return DBS_DEFINITIONS.T_EVENT_SEL_CRIT;
–– Get a given normal selection criteria
––
–– Parameters :
–– EVENT_RESULT : private event result
–– CRITERIA_NO : normal selection criteria identity
–– Exceptions:
–– X_EVENT_RESULT_NOT_OPENED : event result is not opened
–– X_NO_READ_ACCESS : event result file not opened for read access
––

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
514 von/of: 662
procedure ADD_EVENTS(EVENT_RESULT : in out T_EVENT_RESULT;
SESSION_NAME : in TEV_DEFINITIONS.T_SESSION_NAME;
EVENT : in out T_EVENT_L);
–– Add a list of events to the event result
––
–– Parameters :
–– EVENT_RESULT : private event result
–– SESSION_NAME : session owner of the events
–– EVENTS : events to be added
–– Exceptions :
–– X_EVENT_RESULT_NOT_OPENED : event result is not opened
–– X_NO_WRITE_ACCESS : result file is not opened for write access
–– X_INVALID_SESSION : the named session has already been defined
–– or there is not place for this session
–– X_ERROR_ACCESSING_FILE : general error reported when
–– accessing the file
––
function SESSIONS_NUMBER_OF(EVENT_RESULT : in T_EVENT_RESULT)
return NATURAL;
–– Return the number of sessions used to build the event result
––
–– Parameters :
–– EVENT_RESULT : private event result
–– Exceptions :
–– X_EVENT_RESULT_NOT_OPENED : event result is not opened
–– X_NO_READ_ACCESS : event result file not opened for read access
––
function SESSION_NAMES_OF(EVENT_RESULT : in T_EVENT_RESULT)
return TEV_DEFINITIONS.T_DEFINITION_SESSION_NAMES;
–– Return the names of sessions used to build the event result
––
–– Parameters :
–– EVENT_RESULT : private event result
–– Exceptions :
–– X_EVENT_RESULT_NOT_OPENED : event result is not opened
–– X_NO_READ_ACCESS : event result file not opened for read access
––
function EXECUTION_DATE_OF(EVENT_RESULT : in T_EVENT_RESULT)
return CGS_CALENDAR.CGS_DATE_AND_TIME;
–– Return the date and time of execution
––
–– Parameters :
–– EVENT_RESULT : private event result
–– Exceptions :
–– X_EVENT_RESULT_NOT_OPENED : event result is not opened
–– X_NO_READ_ACCESS : event result file not opened for read access
––
function INCLUDE_DEF_SESSION_OF(EVENT_RESULT : in T_EVENT_RESULT)
return boolean;
–– Return a flag to specify if the default session is included
––
–– Parameters :
–– EVENT_RESULT : private event result
–– Exceptions :
–– X_EVENT_RESULT_NOT_OPENED : event result is not opened
–– X_NO_READ_ACCESS : event result file not opened for read access
––
function LONG_TEXT_FLAG_OF(EVENT_RESULT : in T_EVENT_RESULT)
return boolean;
–– Return a flag to specify if the long text is displayed
––
–– Parameters :
–– EVENT_RESULT : private event result
–– Exceptions :
–– X_EVENT_RESULT_NOT_OPENED : event result is not opened
–– X_NO_READ_ACCESS : event result file not opened for read access
––
function SELECT_ON(EVENT_RESULT : in T_EVENT_RESULT)
return DBS_DEFINITIONS.T_TIME_TYPE;
–– Return the time type of the selection

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
515 von/of: 662
––
–– Parameters :
–– EVENT_RESULT : private event result
–– Exceptions :
–– X_EVENT_RESULT_NOT_OPENED : event result is not opened
–– X_NO_READ_ACCESS : event result file not opened for read access
––
function ORDER_BY(EVENT_RESULT : in T_EVENT_RESULT)
return DBS_DEFINITIONS.T_TIME_ORDERING;
–– Return the time ordering of the selection
––
–– Parameters :
–– EVENT_RESULT : private event result
–– Exceptions :
–– X_EVENT_RESULT_NOT_OPENED : event result is not opened
–– X_NO_READ_ACCESS : event result file not opened for read access
––
function POINTER_TO_FIRST_EVENT(EVENT_RESULT : in T_EVENT_RESULT) return POSITIVE;
procedure PUT_LONG_STRING(TEXT_FILE : in out TEXT_IO.FILE_TYPE;
LINE_WIDTH : in NATURAL;
MARGIN_WIDTH : in NATURAL;
TITLE_STRING : in STRING;
LONG_STRING : in STRING);
procedure EXTRACT_EVENTS(EVENT_RESULT : in T_EVENT_RESULT;
SESSION_NAME : in TEV_DEFINITIONS.T_SESSION_NAME;
EVENT : in out T_EVENT_L);
–– Return a list of events corresponding to the supplied
–– definition
––
–– Parameters :
–– EVENT_RESULT : private event result
–– SESSION_NAME : session owner of the events
–– EVENTS : extracted events
–– Exceptions :
–– X_EVENT_RESULT_NOT_OPENED : event result is not opened
–– X_NO_READ_ACCESS : event result file not opened for read access
–– X_INVALID_SESSION : the named session is not defined
––
––
X_INVALID_TIME_FRAME : the time frame is invalid
procedure FORMAT_RESULT(EVENT_RESULT : in out T_EVENT_RESULT;
FILENAME : in STRING);
–– Converts the event result to a string format for display
––
–– Parameters :
–– EVENT_RESULT : private event result
–– FILENAME : filename of formatted result
–– Exceptions :
–– X_NO_READ_ACCESS : event result file not opened for read access
–– X_EVENT_RESULT_NOT_OPENED : event result is not opened
––
––
X_ERROR_ACCESSING_FILE : general error creating formatted result
procedure FORMAT_RESULT_FILE(EVENT_RESULT_FILE : in STRING;
TO_FILENAME : in STRING;
TOOL_ID : in TEV_DEFINITIONS.T_TOOL_ID := POSITIVE’first);
–– Converts the event result to a string format for display
––
–– Parameters :
–– EVENT_RESULT_FILE : event result file to format
–– TO_FILENAME : filename of formatted result
––
–– Exceptions :
TOOL_ID : The tool id
–– X_EVENT_RESULT_NOT_OPENED : event result is not opened
–– X_ERROR_ACCESSING_FILE : general error creating formatted result
––
––
X_INVALID_NAME : event result file does not exist
procedure INVERT(THE_LIST : in T_EVENT_L;
TO_THE_LIST : in out T_EVENT_L) renames P_EVENT_LIST.INVERT;
––

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
516 von/of: 662
–– Invert a list into another list
––
procedure CLEAR(THE_LIST : in out T_EVENT_L)
renames P_EVENT_LIST.CLEAR;
––
–– Clear a list
––
procedure ASSIGN(THE_LIST : in out T_EVENT_L;
NEW_LIST : in T_EVENT_L) renames P_EVENT_LIST.ASSIGN;
––
––
–– Assign a list with a new value
––
procedure CONSTRUCT(DATA_VALUE : in T_EVENT;
THE_LIST : in out T_EVENT_L) renames P_EVENT_LIST.CONSTRUCT;
––
––
–– Construct a list by adding a new item
––
function NULL_LIST return T_EVENT_L
renames P_EVENT_LIST.NULL_LIST;
––
–– Return a null list
––
function IS_NULL(THE_LIST : in T_EVENT_L) return BOOLEAN
renames P_EVENT_LIST.IS_NULL;
––
–– Check if a list is null
––
function HEAD_OF(THE_LIST : in T_EVENT_L) return T_EVENT
renames P_EVENT_LIST.HEAD_OF;
––
–– Extract the head of a list
––
function TAIL_OF(THE_LIST : in T_EVENT_L) return T_EVENT_L
renames P_EVENT_LIST.TAIL_OF;
––
–– Extract the tail of a list
––
function LENGTH_OF(THE_LIST : in T_EVENT_L) return NATURAL
renames P_EVENT_LIST.LENGTH_OF;
––
–– Get the length of a list
––
procedure COPY(FROM_THE_LIST : in T_EVENT_L;
TO_THE_LIST : in out T_EVENT_L) renames P_EVENT_LIST.COPY;
––
–– Copy a list into another list;
––
procedure LIST_EVENTS_FOR_TIME_TAG(
EVENT_RESULT_DESC : in T_EVENT_RESULT;
ORDERING_TIME_TYPE : in DBS_DEFINITIONS.T_TIME_ORDERING;
SECOND_TIME_TYPE : in DBS_DEFINITIONS.T_TIME_ORDERING;
EARLIEST_TIMES : in TEV_DEFINITIONS.T_TWO_TIME;
LAST_TIME_TAG : in CGS_CALENDAR.CGS_DATE_AND_TIME;
FIRST_TIME_TAG : in CGS_CALENDAR.CGS_DATE_AND_TIME;
INDEX_IN_EVENT_FILE : in out NATURAL;
EVENTS_LIST : in out P_EVENTS_CHAIN;
PREVIOUS_EVENTS_LIST : in out P_EVENTS_CHAIN;
EARLIEST_LT_TIME_TAG : in out CGS_CALENDAR.CGS_DATE_AND_TIME;
EARLIEST_SMT_TIME_TAG : in out CGS_CALENDAR.CGS_DATE_AND_TIME
);
procedure LIST_EVENTS_AFTER_TIME_TAG(
EVENT_RESULT_DESC : in T_EVENT_RESULT;
LAST_TIME_TAG : in CGS_CALENDAR.CGS_DATE_AND_TIME;
FIRST_TIME_TAG : in CGS_CALENDAR.CGS_DATE_AND_TIME;

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
517 von/of: 662
ORDERING_TIME_TYPE : in DBS_DEFINITIONS.T_TIME_ORDERING;
INDEX_IN_EVENT_FILE : in out NATURAL;
EVENTS_LIST : in out P_EVENTS_CHAIN
);
procedure CALL_FORMAT_DEFINITION(
EVENT_RESULT_DESC : in T_EVENT_RESULT;
RESULT_MERGE_FD : in out TEXT_IO.FILE_TYPE);
function RETURN_LONG_TEXT_FLAG(EVENT_RESULT : in T_EVENT_RESULT) return BOOLEAN;
function GLOBAL_TIME_FRAME_OF(
EVENT_RESULT : in T_EVENT_RESULT) return TEV_DEFINITIONS.T_TIME_FRAME;
–– Provided exceptions :
X_EVENT_RESULT_NOT_OPENED,
X_ERROR_ACCESSING_FILE,
X_EVENT_RESULT_ALREADY_OPENED,
X_EVENT_RESULT_ALREADY_EXISTS,
X_INVALID_NAME,
X_NO_READ_ACCESS,
X_NO_WRITE_ACCESS,
X_INVALID_TIME_FRAME,
X_INVALID_SESSION : exception;
private
type T_EVENTS_NUMBER_A is array (natural range ) of natural;
–– Array containing number of events for each selected sessions
type T_EVENT_DEFINITION is
record
EXECUTION_DATE : CGS_CALENDAR.CGS_DATE_AND_TIME;
SELECTION_CRITERIA : T_SELECTION_CRITERIA_A;
LONG_TEXT_FLAG_ON : boolean;
SELECT_ON : DBS_DEFINITIONS.T_TIME_TYPE;
ORDER_BY : DBS_DEFINITIONS.T_TIME_ORDERING;
INCLUDE_DEF_SESSION : boolean;
EXECUTION_SESSIONS : TEV_DEFINITIONS.T_DEFINITION_SESSION_NAMES
(T_SESSIONS_RANGE_INC_DEF);
EVENTS_NUMBER : T_EVENTS_NUMBER_A(T_SESSIONS_RANGE_INC_DEF);
end record;
–– description of an event definition
package DEFINITION_IO is new DIRECT_IO(ELEMENT_TYPE => T_EVENT_DEFINITION);
–– DEFINITION_IO is used to access the event definition as the
–– header of the file
package EVENT_IO is new DIRECT_IO( ELEMENT_TYPE => T_EVENT);
–– EVENT_IO is used to access the event records inside the file,
–– the first event to access is located at position offset
–– PTR_TO_FIRST_EVENT
type T_EVENT_RESULT is
record
DEFINITION_FILE_TYPE: DEFINITION_IO.FILE_TYPE;
EVENT_FILE_TYPE : EVENT_IO.FILE_TYPE;
FILENAME : TEV_DEFINITIONS.T_COMPLETE_FILENAME;
ACCESS_STATUS : TEV_DEFINITIONS.T_ACCESS_STATUS := TEV_DEFINITIONS.READ;
CURRENT_STATUS : TEV_DEFINITIONS.T_CURRENT_STATUS := TEV_DEFINITIONS.CLOSED;
EVENT_DEFINITION : T_EVENT_DEFINITION;
RESULT_NAME : TEV_DEFINITIONS.T_RESULT_NAME
:= TEV_DEFINITIONS.NULL_RESULT_NAME;
end record;
–– description of the ADT event result record
end ADT_EVENT_RESULT;

Space Infrastructure
Formal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
518 von/of: 662
––
–– ADT_DATA_SET
––
––****************************************************************************
––ABSTRACT––
––
––
–– Provides operations to create and read a data set file.
–– The data set is seen as an ADT.
––
–– Since data are declared in the user’s code and passed as parameter,
–– there is no synchronisation constraint for parallel access.
–– Implementation constraints :
–– – the Open operation must be called before any Get/Set operations,
–– – the Close operation forces a data set in write access to end edition.
––
––*–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––IDENTIFICATION––
–– PROJECT NAME : CGS
–– PRODUCT NAME : TEV
–– CI–NUMBER : 1216 858
–– OBJECT NAME : HDT_TEV_API.ADT_DATA_SET
––*–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––CONTENTS––
–– COMPILER : VERDIX ADA 6.0.3.C
–– LANGUAGE : ADA
–– SPECIAL CONTENTS:
–– CHANGE HISTORY
–– CGS V4.3 at DASA
–– creator: Bruening
–– creation date: 21.07.99
–– comment:
–– New procedures for the merge adt_data_set / events tool :
–– procedure NEXT_VALUE_FOR_EACH_PARAM
–– procedure FORMAT_DEFINITION
–– Procedures/ functions which were previously internal
–– function GET_TIME_TAG
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– END HISTORY
––****************************************************************************
––
–– Required object : DIRECT_IO
with DIRECT_IO;
–– Required operations :
–– DIRECT_IO.CREATE
–– DIRECT_IO.CLOSE
–– DIRECT_IO.OPEN
–– Required object : CGS_CALENDAR
with CGS_CALENDAR;
–– Required object : MPS_DEFINITIONS
with DBS_DEFINITIONS;
with MPS_DEFINITIONS;
–– Required types :
–– MPS_DEFINITIONS.all_types
–– Required object : VICOS_LIST
with VICOS_LIST;
–– Required object : TEV_DEFINITIONS
with TEV_DEFINITIONS;
–– Required object : ADT_ENGINEERING_VALUE
with ADT_ENGINEERING_VALUE;
–– Required object : ADT_RAW_VALUE
with ADT_RAW_VALUE;
with ADT_ADU_DESCRIPTION;
with TEXT_IO;

Space Infrastructure
use TEV_DEFINITIONS;
package ADT_DATA_SET is
–– Provided types and constants :
type T_DATA_SET is limited private;
type T_PARAMETER_DEFINITION is private;
–– Provided operations :
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
procedure EXTERNAL_FORMAT_FILE(DATA_SET_FILE : in STRING;
TO_FILENAME : in STRING;
EXCEL_SEPARATOR : in CHARACTER := ’,’);
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
519 von/of: 662
procedure OPEN(DATA_SET_FILENAME : in STRING;
DATA_SET : in out T_DATA_SET;
ACCESS_STATUS : in TEV_DEFINITIONS.T_ACCESS_STATUS := TEV_DEFINITIONS.READ;
ALLOW_OVERWRITE : in BOOLEAN := FALSE);
–– Description :
–– Open a data set, with read access on an already existing one,
–– or with write access to create a new one. Write current
–– date and time inEXECUTION_TIME if creating a new data set.
––
–– Parameters :
–– DATA_SET_FILENAME : filename of the data set
–– DATA_SET : private data_set
–– ACCESS_STATUS : – READ only to extract information from
–– data set
–– – WRITE when generating a data set
–– ALLOW_OVERWRITE : when ACCESS_STATUS is WRITE, needed to
–– allow generation of a data set inside an already existing file
–– Exceptions :
–– X_ERROR_ACCESSING_FILE : general error reported when
–– accessing the file
–– X_DATA_SET_ALREADY_OPENED : data set has not been closed
–– and is still in open state
–– X_DATA_SET_ALREADY_EXIST : file exists and overwrite is not allowed
–– X_INVALID_NAME : data set name is too long
––
procedure CLOSE(DATA_SET : in out T_DATA_SET);
–– Description :
–– Close a previously opened data set.
––
–– Parameters :
–– DATA_SET : private data_set
–– Exceptions :
–– X_ERROR_ACCESSING_FILE : general error reported when
–– accessing the file
–– X_DATA_SET_NOT_OPENED : data set already closed
––
procedure DEFINE(DATA_SET : in out T_DATA_SET;
DATA_SET_NAME : in STRING;
TIME_FRAME : in TEV_DEFINITIONS.T_TIME_FRAME;
SAMPLING : in TEV_DEFINITIONS.T_SAMPLING;
SELECT_ON : in DBS_DEFINITIONS.T_TIME_TYPE;
ORDER_BY : in DBS_DEFINITIONS.T_TIME_ORDERING;
INCLUDE_DEF_SESSION : in BOOLEAN;
SESSIONS : in TEV_DEFINITIONS.T_SESSION_NAME_L);
–– Description :
–– Build and initialise the definition of an opened data set.
–– This updates the execution date field
––
–– Parameters :
–– DATA_SET : private data set
–– DATA_SET_NAME : name of the data set
–– TIME_FRAME : time frame of the data set
–– SAMPLING : private sampling of the data set

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–– SELECT_ON : time tag selection type ie SMT or LT
–– ORDER_BY : time order of the data set ie SMT or LT
–– INCLUDE_DEF_SESSION : include default session
–– SESSIONS : list of execution sessions
–– Exceptions :
–– X_DATA_SET_NOT_OPENED : data set is not opened
–– X_NO_WRITE_ACCESS : data set not opened for write access
––
function TIME_FRAME_OF(DATA_SET : in T_DATA_SET)
return TEV_DEFINITIONS.T_TIME_FRAME;
–– Description :
–– Return the time frame in which the current data set has been
–– built.
––
–– Parameters :
–– DATA_SET : private data_set
–– Exceptions :
–– X_NO_READ_ACCESS : data set not open with read access
–– X_DATA_SET_NOT_OPENED : data set is not opened
––
function GET_SELECTED_ON_TIME_TYPE(DATA_SET : in T_DATA_SET)
return DBS_DEFINITIONS.T_TIME_TYPE;
–– Description :
–– Return the selected on time type with which the current data set has been
–– built.
––
–– Parameters :
–– DATA_SET : private data_set
–– Exceptions :
–– X_NO_READ_ACCESS : data set not open with read access
–– X_DATA_SET_NOT_OPENED : data set is not opened
––
function GET_ORDERED_BY_TIME_TYPE(DATA_SET : in T_DATA_SET)
return DBS_DEFINITIONS.T_TIME_ORDERING;
–– Description :
–– Return the ordered by time type with which the current data set has been
–– built.
––
–– Parameters :
–– DATA_SET : private data_set
–– Exceptions :
–– X_NO_READ_ACCESS : data set not open with read access
–– X_DATA_SET_NOT_OPENED : data set is not opened
––
function EXECUTION_DATE_OF(DATA_SET : in T_DATA_SET)
–– Description :
–– Return the date and time of execution
––
–– Parameters :
–– DATA_SET : private data set
–– Exceptions :
–– X_NO_READ_ACCESS : data set not open with read access
–– X_DATA_SET_NOT_OPENED : data set is not opened
––
function FILENAME_OF(DATA_SET : in T_DATA_SET) return STRING;
–– Description :
–– Return the data set file name.
––
–– Parameters :
–– DATA_SET : private data_set
–– Exceptions :
–– X_NO_READ_ACCESS : data set not open with read access
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
520 von/of: 662
return CGS_CALENDAR.CGS_DATE_AND_TIME;

Space Infrastructure
–– X_DATA_SET_NOT_OPENED : data set is not opened
––
function SAMPLING_OF(DATA_SET : in T_DATA_SET)
return TEV_DEFINITIONS.T_SAMPLING;
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–– Description :
–– Return the sampling for the current data set.
––
–– Parameters :
–– DATA_SET : private data_set
–– Exceptions :
–– X_NO_READ_ACCESS : data set not open with read access
–– X_DATA_SET_NOT_OPENED : data set is not opened
––
function PARAMETERS_NUMBER_OF(DATA_SET : in T_DATA_SET)
return NATURAL;
–– Description :
–– Return the number of parameters used to build
–– the current data set.
––
–– Parameters :
–– DATA_SET : private data_set
–– Exceptions :
–– X_NO_READ_ACCESS : data set not open with read access
–– X_DATA_SET_NOT_OPENED : data set is not opened
––
function PARAMETER_NAME_OF(PARAMETER_DEFINITION : in T_PARAMETER_DEFINITION)
return TEV_DEFINITIONS.T_PARAMETER_NAME;
–– Description :
–– Return the name of this parameter.
––
–– Parameters :
–– DATA_SET : private data_set
–– Exceptions :
–– X_NO_READ_ACCESS : data set not open with read access
–– X_DATA_SET_NOT_OPENED : data set is not opened
––
function SESSIONS_NUMBER_OF(DATA_SET : in T_DATA_SET)
return NATURAL;
–– Description :
–– Return the number of sessions used to build
–– the current data set.
––
–– Parameters :
–– DATA_SET : private data_set
–– Exceptions :
–– X_NO_READ_ACCESS : data set not open with read access
–– X_DATA_SET_NOT_OPENED : data set is not opened
––
function SESSION_NAMES_OF(DATA_SET : in T_DATA_SET)
return TEV_DEFINITIONS.T_DEFINITION_SESSION_NAMES;
–– Description :
–– return array with session names from definition.
–– Parameters:
–– DATA_SET : private data set
–– Exception:
–– X_NO_READ_ACCESS : data set not open with read access
–– X_DATA_SET_NOT_OPENED : data set is not opened
––
function INCLUDE_DEF_SESSION_OF(DATA_SET : in T_DATA_SET)
return boolean;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
521 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–– Description :
–– Return a flag to specify if the default session is included
––
–– Parameters :
–– DATA_SET : private data_set
–– Exceptions :
–– X_NO_READ_ACCESS : data set not open with read access
–– X_DATA_SET_NOT_OPENED : data set is not opened
––
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
522 von/of: 662
function PARAMETER_DEFINITION_OF(DATA_SET : in T_DATA_SET;
PARAMETER_INDEX : in TEV_DEFINITIONS.T_PARAMETERS_RANGE)
return T_PARAMETER_DEFINITION;
–– Description :
–– Extract the definition of a given parameter in
–– the current data set by specifying its ordering number.
––
–– Parameters :
–– DATA_SET : private data_set
–– PARAMETER_INDEX : index of the parameter in the data set :
–– valid index is in range
1..PARAMETERS_NUMBER_OF()
–– Exceptions :
–– X_INVALID_PARAMETER : given parameter index is invalid
––
function PARAMETER_DEFINITION_OF_N(DATA_SET : in T_DATA_SET;
PARAMETER_NAME : in TEV_DEFINITIONS.T_PARAMETER_NAME)
return T_PARAMETER_DEFINITION;
–– Description :
–– Extract the definition of a given parameter in
–– the current data set by specifying its name.
––
–– Parameters :
–– DATA_SET : private data_set
–– PARAMETER_NAME : name of the parameter defined in the data
–– set
–– Exceptions :
–– X_INVALID_PARAMETER : given parameter name is invalid
––
function ENGINEERING_UNIT_OF(PARAMETER_DEFINITION : in T_PARAMETER_DEFINITION)
return MPS_DEFINITIONS.T_ENGINEERING_UNIT;
–– Description :
–– Return the engineering unit of this parameter.
––
–– Parameters :
–– PARAMETER_DEFINITION : private parameter definition
–– Exceptions :
––
function SOURCE_FILE_TYPE_OF(PARAMETER_DEFINITION : in T_PARAMETER_DEFINITION)
return TEV_DEFINITIONS.T_SOURCE_FILE_TYPE;
–– Description :
–– Return the type of the source files used for this parameter.
––
–– Parameters :
–– PARAMETER_DEFINITION : private parameter definition
–– Exceptions :
––
function PRODUCER_NAME_OF(PARAMETER_DEFINITION : in T_PARAMETER_DEFINITION)
return TEV_DEFINITIONS.T_PRODUCER_NAME;
–– Description :
–– Return the producer name of this parameter.
––
–– Parameters :

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–– PARAMETER_DEFINITION : private parameter definition
–– Exceptions :
––
function ITEM_TYPE_OF(PARAMETER_DEFINITION : in T_PARAMETER_DEFINITION)
return TEV_DEFINITIONS.T_MEASUREMENT_ALTERNATIVES;
–– Description :
–– Return the item type of this parameter.
––
–– Parameters :
–– PARAMETER_DEFINITION : private parameter definition
–– Exceptions :
––
function DATA_NUMBER_OF(PARAMETER_DEFINITION : in T_PARAMETER_DEFINITION)
return NATURAL;
–– Description :
–– Return the number of data stored for this parameter.
––
–– Parameters :
–– PARAMETER_DEFINITION : private parameter definition
–– Exceptions :
––
function POINTER_TO_FIRST_DATA(DATA_SET : in T_DATA_SET) return NATURAL;
procedure EXTRACT_DATA(DATA_SET : in T_DATA_SET;
PARAMETER_DEFINITION : in T_PARAMETER_DEFINITION;
PARAMETER_VALUES : in out T_PARAMETER_VALUE_L;
TIME_FRAME : in TEV_DEFINITIONS.T_TIME_FRAME
:= TEV_DEFINITIONS.NULL_TIME_FRAME);
–– Description :
–– Extract data from a data set for a given parameter in a given
–– time frame.
–– The number of data returned depends on the array size
–– supplied by the user.
––
–– Parameters :
–– DATA_SET : private data set
–– PARAMETER_DEFINITION : private parameter definition
–– PARAMETER_VALUES : array of parameter values
–– TIME_FRAME : by default the time frame of the data set
–– Exceptions :
–– X_DATA_SET_NOT_OPENED : supplied data set is not opened
–– X_NO_READ_ACCESS : data set not open with read access
–– X_INVALID_PARAMETER : invalid parameter definition
–– X_NO_DATA_AVAILABLE : data are not available
–– X_ERROR_ACCESSING_FILE : general error accessing data set
–– file
––
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
523 von/of: 662
procedure ADD_NEW_PARAMETER(DATA_SET : in out T_DATA_SET;
PARAMETER_NAME : in TEV_DEFINITIONS.T_PARAMETER_NAME;
ENGINEERING_UNIT : in MPS_DEFINITIONS.T_ENGINEERING_UNIT;
SOURCE_FILE_TYPE : in TEV_DEFINITIONS.T_SOURCE_FILE_TYPE;
PRODUCER : in TEV_DEFINITIONS.T_PRODUCER_NAME;
ITEM_TYPE : in TEV_DEFINITIONS.T_MEASUREMENT_ALTERNATIVES);
–– Description :
–– Add a new parameter in the data set definition.
––
–– Parameters :
–– DATA_SET : private data set
–– PARAMETER_NAME : name of the parameter inserted
–– ENGINEERING_UNIT : engineering unit
–– SOURCE_FILE_TYPE : type of the source file
–– PRODUCER : name of the producer
–– ITEM_TYPE : item type
–– Exceptions :
–– X_DATA_SET_NOT_OPENED : data set is not opened

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–– X_NO_WRITE_ACCESS : data set not opened for write access
–– X_TOO_MANY_PARAMETERS : maximum number of parameter reached
––
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
524 von/of: 662
procedure ADD_NEW_VALUE(DATA_SET : in out T_DATA_SET;
RAW_VALUE : in ADT_RAW_VALUE.T_RAW_VALUE;
ENGINEERING_VALUE : in ADT_ENGINEERING_VALUE.T_ENGINEERING_VALUE;
LT_TIME_TAG : in CGS_CALENDAR.CGS_DATE_AND_TIME;
SMT_TIME_TAG : in CGS_CALENDAR.CGS_DATE_AND_TIME);
–– Description :
–– Add a new value in the data set for the last defined
–– parameter.
––
–– Parameters :
–– DATA_SET : private data set
–– RAW_VALUE : raw value
–– ENGINEERING_VALUE : engineering value
–– LT_TIME_TAG : lt time tag of the data value
–– SMT_TIME_TAG : smt time tag of the data value
–– Exceptions :
–– X_DATA_SET_NOT_OPENED : data set is not opened
–– X_NO_WRITE_ACCESS : data set not opened for write access
–– X_NO_PARAMETER_AVAILABLE : no parameter created yet
–– X_ERROR_ACCESSING_FILE : general error accessing file
––
procedure ADD_NEW_VALUES(DATA_SET : in out T_DATA_SET;
VALUES : in out T_PARAMETER_VALUE_L);
–– Description :
–– Add a list of values in the data set for the last defined
–– parameter.
––
–– Parameters :
–– DATA_SET : private data set
–– VALUES : list of values
–– Exceptions :
–– X_DATA_SET_NOT_OPENED : data set is not opened
–– X_NO_WRITE_ACCESS : data set not opened for write access
–– X_NO_PARAMETER_AVAILABLE : no parameter created yet
–– X_ERROR_ACCESSING_FILE : general error accessing file
––
procedure NEXT_VALUE_FOR_EACH_PARAM(
DATA_SET_DESC : in T_DATA_SET;
NB_PARAM : in NATURAL;
LISTING_POSITION : in TEV_DEFINITIONS.T_POSITION_IN_LISTING;
LAST_POSITION : in TEV_DEFINITIONS.T_POSITION_IN_LISTING;
ORDERING_TIME_TYPE : in DBS_DEFINITIONS.T_TIME_ORDERING;
SECOND_TIME_TYPE : in DBS_DEFINITIONS.T_TIME_ORDERING;
PARAMETER_VALUES : in out TEV_DEFINITIONS.T_PARAMETER_VALUES;
EARLIEST_TIMES : in out TEV_DEFINITIONS.T_TWO_TIME;
EARLIEST_LT_TIME_TAG : in out CGS_CALENDAR.CGS_DATE_AND_TIME;
EARLIEST_SMT_TIME_TAG : in out CGS_CALENDAR.CGS_DATE_AND_TIME
);
procedure FORMAT_DEFINITION(
DATA_SET : in T_DATA_SET;
FILE_ID : in TEXT_IO.FILE_TYPE);
function GET_TIME_TAG(
PARAMETER_VALUE : in T_PARAMETER_VALUE;
TIME_TYPE : in DBS_DEFINITIONS.T_TIME_ORDERING)
return CGS_CALENDAR.CGS_DATE_AND_TIME;
X_DATA_SET_ALREADY_OPENED,
X_DATA_SET_NOT_OPENED,
X_NO_WRITE_ACCESS,
X_INVALID_NAME,
X_INVALID_PARAMETER,

Space Infrastructure
X_NO_DATA_AVAILABLE,
X_NO_READ_ACCESS,
X_NO_PARAMETER_AVAILABLE,
X_TOO_MANY_PARAMETERS,
X_ERROR_ACCESSING_FILE,
X_DATA_SET_ALREADY_EXIST : exception;
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
525 von/of: 662
private
type T_PARAMETER_DEFINITION is
record
PARAMETER_INDEX : TEV_DEFINITIONS.T_PARAMETERS_RANGE;
PARAMETER_NAME : TEV_DEFINITIONS.T_PARAMETER_NAME;
ENGINEERING_UNIT : MPS_DEFINITIONS.T_ENGINEERING_UNIT;
SOURCE_FILE_TYPE : TEV_DEFINITIONS.T_SOURCE_FILE_TYPE;
ITEM_TYPE : TEV_DEFINITIONS.T_MEASUREMENT_ALTERNATIVES;
PRODUCER : TEV_DEFINITIONS.T_PRODUCER_NAME;
DATA_NUMBER : natural := natural’first;
DATA_PTR : natural := natural’first;
end record;
–– definition of a parameter in the data set
type T_PARAMETER_DEFINITIONS_ARRAY is array(TEV_DEFINITIONS.T_PARAMETERS_RANGE) of
T_PARAMETER_DEFINITION;
–– definition of an array of a parameter definition
type T_DATA_SET_DEFINITION is
record
TIME_FRAME : TEV_DEFINITIONS.T_TIME_FRAME;
SAMPLING : TEV_DEFINITIONS.T_SAMPLING;
SELECT_ON : DBS_DEFINITIONS.T_TIME_TYPE;
ORDER_BY : DBS_DEFINITIONS.T_TIME_ORDERING;
PARAMETERS_NUMBER : NATURAL := 0;
PARAMETER_DEFINITIONS : T_PARAMETER_DEFINITIONS_ARRAY;
SESSIONS_NUMBER : NATURAL := 0;
SESSIONS : TEV_DEFINITIONS.T_DEFINITION_SESSION_NAMES(
TEV_DEFINITIONS.T_SESSIONS_RANGE
);
INCLUDE_DEF_SESSION : BOOLEAN;
EXECUTION_DATE : CGS_CALENDAR.CGS_DATE_AND_TIME;
end record;
–– Description of private types
––package definition to access data set file
package DEFINITION_IO is new DIRECT_IO( ELEMENT_TYPE => T_DATA_SET_DEFINITION);
–– DEFINITION_IO is used to access the data set definition
–– as the header of the file
package DATA_IO is new DIRECT_IO( ELEMENT_TYPE => T_PARAMETER_VALUE);
–– DATA_IO is used to access the data value records inside
–– the file,
–– the first data to access is locatec at byte offset PTR_TO_FIRST_DATA
type T_DATA_SET is
record
DEFINITION_FILE_TYPE : DEFINITION_IO.FILE_TYPE;
DATA_FILE_TYPE : DATA_IO.FILE_TYPE;
FILENAME : TEV_DEFINITIONS.T_COMPLETE_FILENAME;
ACCESS_STATUS : TEV_DEFINITIONS.T_ACCESS_STATUS
TEV_DEFINITIONS.READ;
CURRENT_STATUS : TEV_DEFINITIONS.T_CURRENT_STATUS
TEV_DEFINITIONS.CLOSED;
DATA_SET_DEFINITION : T_DATA_SET_DEFINITION;
end record;
EXCEL_LINE_MAX_SIZE : constant NATURAL := 4096;
subtype T_EXCEL_LINE is STRING(1..EXCEL_LINE_MAX_SIZE);
end ADT_DATA_SET;
:=
:=

Space Infrastructure
Formal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
––
–– ADT_LISTING_RESULT
––
––****************************************************************************
––ABSTRACT––
––
–– Provides operations to access a listing result file.
––
––*–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––IDENTIFICATION––
–– PROJECT NAME : CGS
–– PRODUCT NAME : TEV
–– CI–NUMBER : 1216 858
–– OBJECT NAME : HDT_TEV_API.ADT_LISTING_RESULT
––*–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––CONTENTS––
–– COMPILER : VERDIX ADA 6.0.3.C
–– LANGUAGE : ADA
–– SPECIAL CONTENTS:
–– CHANGE HISTORY
–– CGS V4.3 at DASA
–– creator: Bruening
–– creation date: 06.07.99
–– comment:
–– New procedure for the merge ADT_DATA_SET/ADT_EVENT_RESULT tool :
–– FORMAT_LINE
–– CREATE_HEADER_DATE_TIME
–– Procedures which were before internal and now provided
–– FORMAT_HEADER
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– END HISTORY
––****************************************************************************
––
–– Required object : DBS_DEFINITIONS
with DBS_DEFINITIONS;
–– Required object : TEV_DEFINITIONS
with TEV_DEFINITIONS;
–– Required object : DIRECT_IO
with DIRECT_IO;
–– Required object : MPS_DEFINITIONS
with MPS_DEFINITIONS;
–– Required object : VICOS_LIST
with VICOS_LIST;
–– Required object : CGS_CALENDAR
with CGS_CALENDAR;
–– Required object : ADT_ENGINEERING_VALUE
with ADT_ENGINEERING_VALUE;
with TEXT_IO;
use TEV_DEFINITIONS;
package ADT_LISTING_RESULT is
the_file : text_io.file_type;
–– Provided types and constants :
type T_LISTING_RESULT is limited private;
–– private adt listing result file
type T_PARAMETER_DEFINITION is private;
–– Provided operations :
procedure EXTERNAL_FORMAT(
LISTING_RESULT : in out T_LISTING_RESULT;
EXTRACT_LISTING_FILE : in STRING;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
526 von/of: 662

Space Infrastructure
EXCEL_SEPARATOR : in CHARACTER := ’,’);
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
procedure EXTERNAL_FORMAT_FILE(
LISTING_RESULT_FILE : in STRING;
TO_FILENAME : in STRING;
EXCEL_SEPARATOR : in CHARACTER := ’,’);
procedure FORMAT_RESULT(
LISTING_RESULT : in out T_LISTING_RESULT;
FILENAME : in STRING);
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
527 von/of: 662
–– Converts the listing result to a landscape string format
––
–– Parameters :
–– LISTING_RESULT : private listing result
–– FILENAME : filename of formatted result
–– Exceptions :
–– X_NO_READ_ACCESS : listing result file not opened for read
access
–– X_LISTING_RESULT_NOT_OPENED : listing result is not opened
–– X_ERROR_ACCESSING_FILE : general error creating formatted
result
–– X_PARMS_DO_NOT_FIT_IN_LANDSCAPE_WIDTH
procedure FORMAT_RESULT_FILE(LISTING_RESULT_FILE : in STRING;
TO_FILENAME : in STRING;
TOOL_ID : in TEV_DEFINITIONS.T_TOOL_ID := POSITIVE’first);
–– Converts the listing result to a string format for display
––
–– Parameters :
–– LISTING_RESULT_FILE : listing result file to format
–– TO_FILENAME : filename of formatted result
–– TOOL_ID : the tool id
–– Exceptions :
–– X_LISTING_RESULT_NOT_OPENED : listing result is not opened
–– X_ERROR_ACCESSING_FILE : general error creating formatted
result
–– X_INVALID_NAME : listing result file does not exist
procedure OPEN(LISTING_RESULT_FILENAME : in STRING;
LISTING_RESULT : in out T_LISTING_RESULT;
ACCESS_STATUS : in TEV_DEFINITIONS.T_ACCESS_STATUS :=
TEV_DEFINITIONS.READ;
ALLOW_OVERWRITE : in BOOLEAN := FALSE);
–– Open a listing result, with read access if it already exists,
–– or with write access to create a new one. The current date
–– and time
–– will be written in EXECUTION_TIME if creating a new listing
–– result
––
–– Parameters :
–– LISTING_RESULT_FILENAME : filename of the listing result
–– LISTING_RESULT : private listing result
–– ACCESS_STATUS : Read only to extract information from a
–– listing result
–– Write when generating a listing result
–– ALLOW_OVERWRITE : When ACCESS_STATUS is write this is
–– required to allow generation
–– of a listing result inside an already
existing file
–– Exceptions :
–– X_ERROR_ACCESSING_FILE : general error reported when
–– accessing the file
–– X_LISTING_RESULT_ALREADY_OPENED : listing result is in open
–– state
–– X_LISTING_RESULT_ALREADY_EXISTS : file exists and overwrite
–– is not allowed
–– X_INVALID_NAME : listing result name is too long
––
procedure CLOSE(LISTING_RESULT : in out T_LISTING_RESULT);

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
528 von/of: 662
–– Close a previously opened listing result
––
–– Parameters :
–– LISTING_RESULT : private listing result
–– Exceptions :
–– X_ERROR_ACCESSING_FILE : general error reported when
–– accessing the file
–– X_LISTING_RESULT_NOT_OPENED : listing result already open
––
procedure DEFINE(LISTING_RESULT : in out T_LISTING_RESULT;
LISTING_RESULT_NAME : in STRING;
DATA_SET : in TEV_DEFINITIONS.T_RESULT_REF;
TIME_FRAME : in TEV_DEFINITIONS.T_TIME_FRAME;
SELECT_ON : in DBS_DEFINITIONS.T_TIME_TYPE;
ORDER_BY : in DBS_DEFINITIONS.T_TIME_ORDERING;
SAMPLING : in TEV_DEFINITIONS.T_SAMPLING;
SESSIONS : in TEV_DEFINITIONS.T_DEFINITION_SESSION_NAMES;
INCLUDE_DEF_SESSIONS : in BOOLEAN);
–– Build and initialise the definition of an opened listing
–– result
––
–– Parameters :
–– LISTING_RESULT : private listing result
–– LISTING_RESULT_NAME : name of the listing result
–– DATA_SET : name and location of data set
–– TIME_FRAME : time frame of the listing result
–– SAMPLING : private sampling of the data set
–– SESSIONS : list of execution sessions in the data set
–– INCLUDE_DEF_SESSIONS : include default session
–– Exceptions :
–– X_LISTING_RESULT_NOT_OPENED : listing result is not opened
–– X_NO_WRITE_ACCESS : listing result not opened for write
–– access
––
function TIME_FRAME_OF(LISTING_RESULT : in T_LISTING_RESULT)
return TEV_DEFINITIONS.T_TIME_FRAME;
–– Return the time frame in which the current listing result has
–– been built.
––
–– Parameters :
–– LISTING_RESULT : private listing result
–– Exceptions :
–– X_LISTING_RESULT_ERROR : the given listing result is
–– invalid
–– X_LISTING_RESULT_NOT_OPENED : listing result is not opened
––
function FILENAME_OF(LISTING_RESULT : in T_LISTING_RESULT)
return STRING;
–– Return the listing result file name.
––
–– Parameters :
–– LISTING_RESULT : private listing result
–– Exceptions :
–– X_LISTING_RESULT_ERROR : the given listing result is
–– invalid
–– X_LISTING_RESULT_NOT_OPENED : listing result is not opened
––
function DATA_SET_OF(LISTING_RESULT : in T_LISTING_RESULT)
return TEV_DEFINITIONS.T_RESULT_REF;
–– Return the data set and location of data set with which
–– listing result was built
––
–– Parameters :
–– LISTING_RESULT : private listing result
–– Exceptions :
–– X_LISTING_RESULT_ERROR : the given listing result is
–– invalid
–– X_LISTING_RESULT_NOT_OPENED : listing result is not opened
––

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
529 von/of: 662
function TITLE_OF(LISTING_RESULT : in T_LISTING_RESULT)
return TEV_DEFINITIONS.T_TITLE;
–– Return the title of the listing result
––
–– Parameters :
–– LISTING_RESULT : private listing result
–– Exceptions :
–– X_LISTING_RESULT_ERROR : the given listing result is
–– invalid
–– X_LISTING_RESULT_NOT_OPENED : listing result is not opened
––
function SAMPLING_OF(LISTING_RESULT : in T_LISTING_RESULT)
return TEV_DEFINITIONS.T_SAMPLING;
–– Return the sampling for the data set from which the listing
–– was built.
––
–– Parameters :
–– LISTING_RESULT : private listing result
–– Exceptions :
–– X_LISTING_RESULT_ERROR : the given listing result is
–– invalid
–– X_LISTING_RESULT_NOT_OPENED : listing result is not opened
––
function PARAMETERS_NUMBER_OF(LISTING_RESULT : in T_LISTING_RESULT)
return NATURAL;
–– Return the number of parameters used to build the listing
–– result.
––
–– Parameters :
–– LISTING_RESULT : private data_set
–– Exceptions :
–– X_LISTING_RESULT_ERROR : the given listing result is
–– invalid
–– X_LISTING_RESULT_NOT_OPENED : listing result is not opened
––
function PARAMETER_NAME_OF(PARAMETER_DEFINITION : in T_PARAMETER_DEFINITION)
return TEV_DEFINITIONS.T_PARAMETER_NAME;
–– Return the name of this parameter.
––
–– Parameters :
–– PARAMETER_DEFINITION : private parameter definition
–– Exceptions :
–– X_LISTING_RESULT_ERROR : the given listing result is
–– invalid
–– X_LISTING_RESULT_NOT_OPENED : listing result is not opened
––
function SESSION_NUMBER_OF(LISTING_RESULT : in T_LISTING_RESULT)
return NATURAL;
–– Return the number of sessions used to build the data set with
–– which the listing result was created.
––
–– Parameters :
–– LISTING_RESULT : private listing result
–– Exceptions :
–– X_LISTING_RESULT_ERROR : the given listing result is
–– invalid
–– X_LISTING_RESULT_NOT_OPENED : listing result is not opened
––
function SESSION_NAMES_OF(LISTING_RESULT : in T_LISTING_RESULT)
return TEV_DEFINITIONS.T_DEFINITION_SESSION_NAMES;
–– Return the list of session names used to build the data set
–– with which the listing result was created
––
–– Parameters :
–– LISTING_RESULT : private listing result
–– Exceptions :

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
530 von/of: 662
–– X_LISTING_RESULT_ERROR : the given listing result is
–– invalid
–– X_LISTING_RESULT_NOT_OPENED : listing result is not opened
––
function INCLUDE_DEF_SESSION_OF(LISTING_RESULT : in T_LISTING_RESULT)
return boolean;
–– Return a flag to indicate the inclustion of the default test session
–– Parameters:
–– LISTING_RESULT : private listing result
–– Exceptions :
–– X_LISTING_RESULT_NOT_OPENED : listing result is not opened
–– X_NO_READ_ACCESS : listing result file not opened for
read access
––
function EXECUTION_DATE_OF(LISTING_RESULT : in T_LISTING_RESULT)
return CGS_CALENDAR.CGS_DATE_AND_TIME;
–– Return the date and time of execution
––
–– Parameters :
–– LISTING_RESULT : private listing result
–– Exceptions :
–– X_LISTING_RESULT_ERROR : the given listing result is
–– invalid
–– X_LISTING_RESULT_NOT_OPENED : listing result is not opened
––
function PARAMETER_DEFINITION_OF(LISTING_RESULT : in T_LISTING_RESULT;
PARAMETER_INDEX : in TEV_DEFINITIONS.T_PARAMETERS_RANGE)
return T_PARAMETER_DEFINITION;
–– Extract the definition of a given parameter in
–– the current listing result by specifying its ordering
–– number.
––
–– Parameters :
–– LISTING_RESULT : private listing result
–– PARAMETER_INDEX : index of the parameter in the listing
–– result :
–– valid index is in range
1..PARAMETERS_NUMBER_OF()
–– Exceptions :
–– X_LISTING_RESULT_NOT_OPENED : listing result is not opened
–– X_LISTING_RESULT_ERROR : the given listing result is
–– invalid
–– X_INVALID_PARAMETER : given parameter index is invalid
––
function PARAMETER_DEFINITION_OF_N(LISTING_RESULT : in T_LISTING_RESULT;
PARAMETER_NAME : in TEV_DEFINITIONS.T_PARAMETER_NAME)
return T_PARAMETER_DEFINITION;
–– Extract the definition of a given parameter in
–– the current listing result by specifying its name.
––
–– Parameters :
–– LISTING_RESULT : private listing result
–– PARAMETER_NAME : name of the parameter defined in the
–– listing rsult
–– Exceptions :
–– X_LISTING_RESULT_NOT_OPENED : listing result is not opened
–– X_LISTING_RESULT_ERROR : the given listing result is
–– invalid
–– X_INVALID_PARAMETER : given parameter name is invalid
––
function ENGINEERING_UNIT_OF(PARAMETER_DEFINITION : in T_PARAMETER_DEFINITION)
return MPS_DEFINITIONS.T_ENGINEERING_UNIT;
–– Return the engineering unit of this parameter.
––

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
531 von/of: 662
–– Parameters :
–– PARAMETER_DEFINITION : private parameter definition
–– Exceptions :
–– X_INVALID_PARAMETER : given parameter definition is invalid
––
function PARAMETER_INDEX_OF(PARAMETER_DEFINITION : in T_PARAMETER_DEFINITION)
return POSITIVE;
–– Return the index of this parameter.
––
–– Parameters :
–– PARAMETER_DEFINITION : private parameter definition
–– Exceptions :
–– X_INVALID_PARAMETER : given parameter definition is invalid
––
function SOURCE_FILE_TYPE_OF(PARAMETER_DEFINITION : in T_PARAMETER_DEFINITION)
return TEV_DEFINITIONS.T_SOURCE_FILE_TYPE;
–– Return the type of the source files used for this parameter.
––
–– Parameters :
–– PARAMETER_DEFINITION : private parameter definition
–– Exceptions :
–– X_INVALID_PARAMETER : given parameter definition is invalid
––
function PRODUCER_NAME_OF(PARAMETER_DEFINITION : in T_PARAMETER_DEFINITION)
return TEV_DEFINITIONS.T_PRODUCER_NAME;
–– Return the producer name of this parameter.
––
–– Parameters :
–– PARAMETER_DEFINITION : private parameter definition
–– Exceptions :
––
function DATA_NUMBER_OF(PARAMETER_DEFINITION : in T_PARAMETER_DEFINITION)
return NATURAL;
–– Return the number of data stored for this parameter.
––
–– Parameters :
–– PARAMETER_DEFINITION : private parameter definition
–– Exceptions :
–– X_INVALID_PARAMETER : given parameter definition is invalid
––
function GET_SELECTED_ON_TIME_TYPE(LISTING_RESULT : in T_LISTING_RESULT)
return DBS_DEFINITIONS.T_TIME_TYPE;
–– Return the time type of the selection
––
–– Parameters :
–– LISTING_RESULT : private listing result
–– Exceptions :
–– X_LISTING_RESULT_NOT_OPENED : listing result is not opened
–– X_NO_READ_ACCESS : listing result file not opened for
read access
––
function GET_ORDERED_BY_TIME_TYPE(LISTING_RESULT : in T_LISTING_RESULT)
return DBS_DEFINITIONS.T_TIME_ORDERING;
–– Return the time ordering of the selection
––
–– Parameters :
–– LISTING_RESULT : private listing result
–– Exceptions :
–– X_LISTING_RESULT_NOT_OPENED : listing result is not opened
–– X_NO_READ_ACCESS : listing result file not opened for
read access
––
procedure EXTRACT_DATA(
LISTING_RESULT : in T_LISTING_RESULT;
PARAMETER_DEFINITION : in T_PARAMETER_DEFINITION;
LISTING_VALUES : in out TEV_DEFINITIONS.T_PARAMETER_VALUE_L;

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
532 von/of: 662
TIME_FRAME : in TEV_DEFINITIONS.T_TIME_FRAME
:= TEV_DEFINITIONS.NULL_TIME_FRAME);
–– Extract data from a listing result for a given parameter in a
–– given time frame.
–– The number of data returned depends on the array size
–– supplied by the user.
––
–– Parameters :
–– LISTING_RESULT : private listing result
–– PARAMETER_DEFINITION : private parameter definition
–– LISTING_VALUES : array of listing values
–– TIME_FRAME : by default the time frame of the listing
–– result
–– Exceptions :
–– X_LISTING_RESULT_NOT_OPENED : supplied listing result is
–– not opened
–– X_NO_READ_ACCESS : listing result not open with read access
–– X_INVALID_PARAMETER : invalid parameter definition
–– X_NO_DATA_AVAILABLE : data are not available
–– X_ERROR_ACCESSING_FILE : general error accessing listing
–– result file
––
procedure ADD_LIST_OF_VALUES(LISTING_RESULT : in out T_LISTING_RESULT;
PARAMETER_NAME : in TEV_DEFINITIONS.T_PARAMETER_NAME;
ENGINEERING_UNIT : in MPS_DEFINITIONS.T_ENGINEERING_UNIT;
SOURCE_FILE_TYPE : in TEV_DEFINITIONS.T_SOURCE_FILE_TYPE;
PRODUCER : in TEV_DEFINITIONS.T_PRODUCER_NAME;
LIST_TO_ADD : in T_PARAMETER_VALUE_L);
–– Add a parameter and list of values in the listing result for the next
–– empty parameter
––
–– Parameters :
–– LISTING_RESULT : private listing result
–– PARAMETER_NAME : parameter name to be added
–– ENGINEERING_UNIT : engineering unit for the parameter
–– SOURCE_FILE_TYPE : source file type for the parameter
–– PRODUCER : producer of the parameter
–– LIST_TO_ADD : list of listing values
–– Exceptions :
–– X_LISTING_RESULT_NOT_OPENED : listing result is not opened
–– X_NO_WRITE_ACCESS : listing result not opened for write
–– access
–– X_NO_PARAMETER_AVAILABLE : no parameter created yet
–– X_ERROR_ACCESSING_FILE : general error accessing file
–– X_INVALID_PARAMETER : the parameter is invalid
–– X_INVALID_VALUE : the value is invalid
––
procedure FORMAT_LINE(
ORDERING_TIME_TYPE : in DBS_DEFINITIONS.T_TIME_ORDERING;
NB_PARAM : in NATURAL;
ARRAY_HEAD_OF_VALUES : in TEV_DEFINITIONS.T_PARAMETER_VALUES;
CURRENT_SMT_TIME : in CGS_CALENDAR.CGS_DATE_AND_TIME;
CURRENT_LT_TIME : in CGS_CALENDAR.CGS_DATE_AND_TIME;
FILE_ID : in TEXT_IO.FILE_TYPE;
ALL_BYTE_STREAM : in BOOLEAN;
PREVIOUS_TIME : in out CGS_CALENDAR.CGS_DATE_AND_TIME;
LISTING_POSITION : in out TEV_DEFINITIONS.T_POSITION_IN_LISTING
);
––==============================================================
––
–– Operation Name: CREATE_HEADER_DATE_TIME
–– Description:
–– Creates the header for a specific listing result :
–– Current date
–– Current time
–– LISTING RESULT:
–– –––––––––––––––––––––––––––––––––––––––––

Space Infrastructure
––
––
–– Parameters :
–– none
––
––==============================================================
procedure CREATE_HEADER_DATE_TIME;
––==============================================================
––
–– Operation Name: WRITE_HEADER_DATE_TIME
–– Description:
–– Creates the header for a specific listing result :
–– Current date
–– Current time
–– LISTING RESULT:
–– –––––––––––––––––––––––––––––––––––––––––
––
––
–– Parameters :
–– none
––
––==============================================================
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
procedure WRITE_HEADER_DATE_TIME(FILE_ID : in TEXT_IO.FILE_TYPE);
procedure FORMAT_HEADER(
NB_PARAM : in NATURAL;
FIRST_LINE : out STRING;
SECOND_LINE : out STRING;
FILE_ID : in TEXT_IO.FILE_TYPE);
–– Provided exceptions :
X_LISTING_RESULT_NOT_OPENED,
X_ERROR_ACCESSING_FILE,
X_LISTING_RESULT_ALREADY_OPENED,
X_LISTING_RESULT_ALREADY_EXISTS,
X_INVALID_NAME,
X_NO_READ_ACCESS,
X_NO_WRITE_ACCESS,
X_INVALID_TIME_FRAME,
X_INVALID_PARAMETER,
X_PARMS_DO_NOT_FIT_IN_LANDSCAPE_WIDTH,
X_INVALID_VALUE : exception;
private
type T_PARAMETER_DEFINITION is
record
PARAMETER_INDEX : TEV_DEFINITIONS.T_PARAMETERS_RANGE;
PARAMETER_NAME : TEV_DEFINITIONS.T_PARAMETER_NAME;
ENGINEERING_UNIT : MPS_DEFINITIONS.T_ENGINEERING_UNIT;
SOURCE_FILE_TYPE : TEV_DEFINITIONS.T_SOURCE_FILE_TYPE;
PRODUCER : TEV_DEFINITIONS.T_PRODUCER_NAME;
DATA_NUMBER : NATURAL := 0;
end record;
–– description of a parameter definition
subtype T_PARAMETER_RANGE_L is
NATURAL range 1 .. TEV_DEFINITIONS.MAX_NUMBER_OF_PARAMETERS_IN_LISTING;
type T_PARAMETER_DEFINITIONS_ARRAY is
array(T_PARAMETER_RANGE_L) of T_PARAMETER_DEFINITION;
–– definition of an array of a parameter definition
type T_LISTING_DEFINITION is
record
TIME_FRAME : TEV_DEFINITIONS.T_TIME_FRAME;
SELECT_ON : DBS_DEFINITIONS.T_TIME_TYPE;
ORDER_BY : DBS_DEFINITIONS.T_TIME_ORDERING;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
533 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
534 von/of: 662
DATA_SET : TEV_DEFINITIONS.T_RESULT_REF;
TITLE : TEV_DEFINITIONS.T_TITLE;
SAMPLING : TEV_DEFINITIONS.T_SAMPLING;
SESSIONS_NUMBER : NATURAL := 0;
SESSIONS :
TEV_DEFINITIONS.T_DEFINITION_SESSION_NAMES(TEV_DEFINITIONS.T_SESSIONS_RANGE);
INCLUDE_DEF_SESSIONS : BOOLEAN;
EXECUTION_TIME : CGS_CALENDAR.CGS_DATE_AND_TIME;
ASCII_DEFINED : BOOLEAN := False;
PARAMETERS_NUMBER : NATURAL := 0;
PARAMETER_DEFINITIONS : T_PARAMETER_DEFINITIONS_ARRAY;
end record;
–– description of a listing definition
package DEFINITION_IO is new DIRECT_IO( ELEMENT_TYPE => T_LISTING_DEFINITION);
–– DEFINITION_IO is used to access the listing result definition as
–– the header of the file
package LISTING_IO is new DIRECT_IO( ELEMENT_TYPE => T_PARAMETER_VALUE);
–– LISTING_IO is used to access the listing value records inside
–– the file, the first listing value to access is located at byte
–– offset
–– PTR_TO_FIRST_LISTING
type T_LISTING_RESULT is
record
DEFINITION_FILE_TYPE : DEFINITION_IO.FILE_TYPE;
LISTING_FILE_TYPE : LISTING_IO.FILE_TYPE;
FILENAME : TEV_DEFINITIONS.T_COMPLETE_FILENAME;
ACCESS_STATUS : TEV_DEFINITIONS.T_ACCESS_STATUS :=
TEV_DEFINITIONS.READ;
CURRENT_STATUS : TEV_DEFINITIONS.T_CURRENT_STATUS :=
TEV_DEFINITIONS.CLOSED;
LISTING_DEFINITION : T_LISTING_DEFINITION;
end record;
EXCEL_LINE_MAX_SIZE : constant NATURAL := 1024;
subtype T_EXCEL_LINE is STRING(1..EXCEL_LINE_MAX_SIZE);
end ADT_LISTING_RESULT;

Space Infrastructure
Formal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
––
–– ADT_STATISTIC_RESULT
––
––****************************************************************************
––ABSTRACT––
––
–– Provides operations to access a statistics result file.
––
––*–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––IDENTIFICATION––
–– PROJECT NAME : CGS
–– PRODUCT NAME : TEV
–– CI–NUMBER : 1216 858
–– OBJECT NAME : HDT_TEV_API.ADT_STATISTIC_RESULT
––*–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––CONTENTS––
–– COMPILER : VERDIX ADA 6.0.3.C
–– LANGUAGE : ADA
–– SPECIAL CONTENTS:
–– CHANGE HISTORY
–– V4.3 at Spacebel Informatique, Brussels
–– creator: jm (on host asimov)
–– creation date: 29.09.95 18:42:30
–– comment:
–– Update for SMT/LT (Req.485)
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V4.2 at Spacebel Informatique, Brussels
–– creator: rowena (on host moon)
–– creation date: 25.07.95 10:50:52
–– comment:
–– Move from VICOS_CALENDAR to CGS_CALENDAR
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– END HISTORY
––****************************************************************************
––
––
with DBS_DEFINITIONS;
with TEV_DEFINITIONS;
with VICOS_LIST;
with CGS_CALENDAR;
with DIRECT_IO;
with MPS_DEFINITIONS;
with ADT_ENGINEERING_VALUE;
use TEV_DEFINITIONS;
package ADT_STATISTICS_RESULT is
–– Provided types and constants :
type T_STATISTIC_VALUE is
record
IS_NUMERIC : BOOLEAN := TRUE;
MINIMUM : FLOAT := 0.0;
MAXIMUM : FLOAT := 0.0;
MEAN : FLOAT := 0.0;
MEDIAN : FLOAT := 0.0;
VARIANCE : FLOAT := 0.0;
NB : NATURAL := 0;
end record;
–– definition of a statistics result within the statistics result
–– file
type T_STATISTIC_RESULT is limited private;
type T_PARAMETER_DEFINITION is private;
subtype T_PARAMETERS_RANGE is POSITIVE range 1 .. 50;
MAXIMUM_NUMBER_OF_PARAMETERS : constant POSITIVE :=
T_PARAMETERS_RANGE’LAST;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
535 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
536 von/of: 662
–– maximum number of parameters allowed in the statistics result
MAX_PARAMETER_NUMBER : constant NATURAL := 10;
–– Provided operations :
procedure FORMAT_RESULT(STATISTIC_RESULT : in out T_STATISTIC_RESULT;
FILENAME : in STRING);
–– Converts the statistic result to a string format
––
–– Parameters :
–– STATISTIC_RESULT : private statistic result
–– FILENAME : filename of formatted result
–– Exceptions :
––
read access
X_NO_READ_ACCESS : statistic result file not opened for
––
opened
X_STATISTIC_RESULT_NOT_OPENED : statistic result is not
––
matted result
X_ERROR_ACCESSING_FILE : general error creating for-
procedure FORMAT_RESULT_FILE(STATISTIC_RESULT_FILE : in STRING;
TO_FILENAME : in STRING);
–– Converts the statistic result to a string format for display
––
–– Parameters :
–– STATISTIC_RESULT_FILE : statistic result file to for-
mat
–– TO_FILENAME : filename of formatted result
–– Exceptions :
–– X_STATISTIC_RESULT_NOT_OPENED : statistic result is not
opened
–– X_ERROR_ACCESSING_FILE : general error creating formatted
result
–– X_INVALID_NAME : statistic result file does not exist
procedure OPEN(STATISTIC_RESULT_FILENAME : in STRING;
STATISTIC_RESULT : in out T_STATISTIC_RESULT;
ACCESS_STATUS : in TEV_DEFINITIONS.T_ACCESS_STATUS := TEV_DE-
FINITIONS.READ;
ALLOW_OVERWRITE : in BOOLEAN := FALSE);
–– Open a statistic result, with read access if it already exists
–– or with write access to create a new one. The current date
–– and time will be written in EXECUTION_TIME if creating a new
––
––
statistic result
–– Parameters :
–– STATISTIC_RESULT_FILENAME : filename of the statistic result
–– STATISTIC_RESULT : private statistic result
–– ACCESS_STATUS : Read only to extract information from a
–– statistic result
–– Write when generating a statistic result
–– ALLOW_OVERWRITE : When ACCESS_STATUS is write this is
–– required to allow generation
–– of a statistic result inside an already existing
file
–– Exceptions :
–– X_ERROR_ACCESSING_FILE : general error reported when
–– accessing the file
––
in
X_STATISTIC_RESULT_ALREADY_OPENED : statistic result is
–– open state
–– X_STATISTIC_RESULT_ALREADY_EXISTS : file exists and
–– overwrite is not allowed
––
––
X_INVALID_NAME : statistic result name is too long
procedure CLOSE(STATISTIC_RESULT : in out T_STATISTIC_RESULT);
–– Close a previously opened statistic result
––
–– Parameters :
–– STATISTIC_RESULT : private statistic result
–– Exceptions :
–– X_ERROR_ACCESSING_FILE : general error reported when

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
537 von/of: 662
–– accessing the file
–– X_STATISTIC_RESULT_NOT_OPENED : statistic result already
–– open
––
procedure DEFINE(STATISTIC_RESULT : in out T_STATISTIC_RESULT;
STATISTIC_RESULT_NAME : in STRING;
DATA_SET : in TEV_DEFINITIONS.T_RESULT_REF;
TIME_FRAME : in TEV_DEFINITIONS.T_TIME_FRAME;
SELECT_ON : in DBS_DEFINITIONS.T_TIME_TYPE;
ORDER_BY : in DBS_DEFINITIONS.T_TIME_ORDERING;
SAMPLING : in TEV_DEFINITIONS.T_SAMPLING;
SESSIONS : in TEV_DEFINITIONS.T_DEFINITION_SESSION_NAMES;
INCLUDE_DEF_SESSION : in BOOLEAN);
–– Build and initialise the definition of an opened statistic
–– result
––
–– Parameters :
–– STATISTIC_RESULT : private statistic result
–– STATISTIC_RESULT_NAME : name of the statistic result
–– DATA_SET : name and location of data set
–– TIME_FRAME : time frame of the statistic result
–– SAMPLING : private sampling of the data set
–– SESSIONS : list of execution sessions in the data set
–– INCLUDE_DEF_SESSION : include default session
–– Exceptions :
–– X_STATISTIC_RESULT_NOT_OPENED : statistic result is not
–– opened
–– X_NO_WRITE_ACCESS : statistic result not opened for
write
–– access
––
function TIME_FRAME_OF(STATISTIC_RESULT : in T_STATISTIC_RESULT)
return TEV_DEFINITIONS.T_TIME_FRAME;
–– Return the time frame in which the current statistic result has
–– been built.
––
–– Parameters :
–– STATISTIC_RESULT : private statistic result
–– Exceptions :
–– X_STATISTIC_RESULT_ERROR : the given statistic result
is
is
–– invalid
–– X_STATISTIC_RESULT_NOT_OPENED : statistic result is not
–– opened
––
function FILENAME_OF(STATISTIC_RESULT : in T_STATISTIC_RESULT)
return STRING;
–– Return the statistic result file name.
––
–– Parameters :
–– STATISTIC_RESULT : private statistic result
–– Exceptions :
–– X_STATISTIC_RESULT_ERROR : the given statistic result
–– invalid
–– X_STATISTIC_RESULT_NOT_OPENED : statistic result is not
–– opened
––
function DATA_SET_OF(STATISTIC_RESULT : in T_STATISTIC_RESULT)
return TEV_DEFINITIONS.T_RESULT_REF;
–– Return the data set and location of data set with which
–– statistic result was built
––
–– Parameters :
–– STATISTIC_RESULT : private statistic result
–– Exceptions :
–– X_STATISTIC_RESULT_ERROR : the given statistic result

Space Infrastructure
is
is
is
is
is
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
538 von/of: 662
–– invalid
–– X_STATISTIC_RESULT_NOT_OPENED : statistic result is not
–– opened
––
function SAMPLING_OF(STATISTIC_RESULT : in T_STATISTIC_RESULT)
return TEV_DEFINITIONS.T_SAMPLING;
–– Return the sampling for the data set from which the statistic
–– was built.
––
–– Parameters :
–– STATISTIC_RESULT : private statistic result
–– Exceptions :
–– X_STATISTIC_RESULT_ERROR : the given statistic result
–– invalid
–– X_STATISTIC_RESULT_NOT_OPENED : statistic result is not
–– opened
––
function PARAMETERS_NUMBER_OF(STATISTIC_RESULT : in T_STATISTIC_RESULT)
return NATURAL;
–– Return the number of parameters used to build the statistic
–– result.
––
–– Parameters :
–– STATISTIC_RESULT : private data_set
–– Exceptions :
–– X_STATISTIC_RESULT_ERROR : the given statistic result
–– invalid
–– X_STATISTIC_RESULT_NOT_OPENED : statistic result is not
–– opened
––
function PARAMETER_NAME_OF(PARAMETER_DEFINITION : in T_PARAMETER_DEFINITION)
return TEV_DEFINITIONS.T_PARAMETER_NAME;
–– Return the name of this parameter.
––
–– Parameters :
–– PARAMETER_DEFINITION : private parameter definition
–– Exceptions :
–– X_STATISTIC_RESULT_ERROR : the given statistic result
–– invalid
–– X_STATISTIC_RESULT_NOT_OPENED : statistic result is not
–– opened
––
function SESSION_NUMBER_OF(STATISTIC_RESULT : in T_STATISTIC_RESULT)
return NATURAL;
–– Return the number of sessions used to build the data set with
–– which the statistic result was created.
––
–– Parameters :
–– STATISTIC_RESULT : private statistic result
–– Exceptions :
–– X_STATISTIC_RESULT_ERROR : the given statistic result
–– invalid
–– X_STATISTIC_RESULT_NOT_OPENED : statistic result is not
–– opened
––
function SESSION_NAMES_OF(STATISTIC_RESULT : in T_STATISTIC_RESULT)
return TEV_DEFINITIONS.T_DEFINITION_SESSION_NAMES;
–– Return the list of session names used to build the data set
–– with which the statistic result was created
––
–– Parameters :
–– STATISTIC_RESULT : private statistic result
–– Exceptions :

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
539 von/of: 662
–– X_STATISTIC_RESULT_ERROR : the given listing result is
–– invalid
–– X_STATISTIC_RESULT_NOT_OPENED : statistic result is not
–– opened
––
function INCLUDE_DEF_SESSION_OF(STATISTIC_RESULT : in T_STATISTIC_RESULT)
return boolean;
–– Return a flag to indicate the inclusion of the default test session
–– Parameters:
–– STATISTIC_RESULT : private statistic result
–– Exceptions :
–– X_STATISTIC_RESULT_NOT_OPENED : statistic result is not
opened
–– X_NO_READ_ACCESS : statistic result file not
opened for read access
––
function EXECUTION_DATE_OF(STATISTIC_RESULT : in T_STATISTIC_RESULT)
return CGS_CALENDAR.CGS_DATE_AND_TIME;
–– Return the date and time of execution
––
–– Parameters :
–– STATISTIC_RESULT : private statistic result
–– Exceptions :
–– X_STATISTIC_RESULT_ERROR : the given statistic result
is
tic
–– invalid
–– X_STATISTIC_RESULT_NOT_OPENED : statistic result is not
–– opened
––
function PARAMETER_DEFINITION_OF(STATISTIC_RESULT : in T_STATISTIC_RESULT;
PARAMETER_INDEX : in T_PARAMETERS_RANGE)
return T_PARAMETER_DEFINITION;
–– Extract the definition of a given parameter in
–– the current statistic result by specifying its ordering number.
––
–– Parameters :
–– STATISTIC_RESULT : private statistic result
–– PARAMETER_INDEX : index of the parameter in the statis-
–– result :
––
METERS_NUMBER_OF()
valid index is in range 1..PARA-
–– Exceptions :
–– X_STATISTIC_RESULT_NOT_OPENED : statistic result is not
–– opened
––
is
X_STATISTIC_RESULT_ERROR : the given statistic result
–– invalid
––
––
X_INVALID_PARAMETER : given parameter index is invalid
function PARAMETER_DEFINITION_OF_N(STATISTIC_RESULT : in T_STATISTIC_RESULT;
PARAMETER_NAME : in TEV_DEFINITIONS.T_PARAMETER_NAME)
return T_PARAMETER_DEFINITION;
–– Extract the definition of a given parameter in the current
–– statistic result by specifying its name.
––
–– Parameters :
–– STATISTIC_RESULT : private statistic result
–– PARAMETER_NAME : name of the parameter defined in the
–– statistic result
–– Exceptions :
–– X_STATISTIC_RESULT_NOT_OPENED : statistic result is not
–– opened
–– X_STATISTIC_RESULT_ERROR : the given statistic result
is
–– invalid
–– X_INVALID_PARAMETER : given parameter name is invalid
––
function ENGINEERING_UNIT_OF(PARAMETER_DEFINITION : in T_PARAMETER_DEFINITION)

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
540 von/of: 662
return MPS_DEFINITIONS.T_ENGINEERING_UNIT;
–– Return the engineering unit of this parameter.
––
–– Parameters :
–– PARAMETER_DEFINITION : private parameter definition
–– Exceptions :
–– X_INVALID_PARAMETER : given parameter definition is
invalid
––
function PARAMETER_INDEX_OF(PARAMETER_DEFINITION : in T_PARAMETER_DEFINITION)
return POSITIVE;
–– Return the index of this parameter.
––
–– Parameters :
–– PARAMETER_DEFINITION : private parameter definition
–– Exceptions :
–– X_INVALID_PARAMETER : given parameter definition is
invalid
––
function SOURCE_FILE_TYPE_OF(PARAMETER_DEFINITION : in T_PARAMETER_DEFINITION)
return TEV_DEFINITIONS.T_SOURCE_FILE_TYPE;
–– Return the type of the source files used for this parameter.
––
–– Parameters :
–– PARAMETER_DEFINITION : private parameter definition
–– Exceptions :
–– X_INVALID_PARAMETER : given parameter definition is
invalid
––
function PRODUCER_NAME_OF(PARAMETER_DEFINITION : in T_PARAMETER_DEFINITION)
return TEV_DEFINITIONS.T_PRODUCER_NAME;
–– Return the producer name of this parameter.
––
–– Parameters :
–– PARAMETER_DEFINITION : private parameter definition
–– Exceptions :
––
function TITLE_OF(STATISTIC_RESULT : in T_STATISTIC_RESULT)
return TEV_DEFINITIONS.T_TITLE;
–– Return the statistic result title.
––
–– Parameters :
–– STATISTIC_RESULT : private statistic result
–– Exceptions :
–– X_STATISTIC_RESULT_NOT_OPENED : statistic result is not
opened
–– X_NO_READ_ACCESS : statistic result file not
opened for read access
––
function GET_SELECTED_ON_TIME_TYPE(STATISTIC_RESULT : in T_STATISTIC_RESULT)
return DBS_DEFINITIONS.T_TIME_TYPE;
–– Return the time type of the selection
––
–– Parameters :
–– STATISTIC_RESULT : private statistic result
–– Exceptions :
–– X_STATISTIC_RESULT_NOT_OPENED : statistic result is not
opened
–– X_NO_READ_ACCESS : statistic result file
not opened for read access
––
function GET_ORDERED_BY_TIME_TYPE(STATISTIC_RESULT : in T_STATISTIC_RESULT)
return DBS_DEFINITIONS.T_TIME_ORDERING;
–– Return the time ordering of the selection
––
–– Parameters :
–– STATISTIC_RESULT : private statistic result
–– Exceptions :

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
541 von/of: 662
–– X_STATISTIC_RESULT_NOT_OPENED : statistic result is not
opened
–– X_NO_READ_ACCESS : statistic result file
not opened for read access
––
procedure EXTRACT_STATISTICS(STATISTIC_RESULT : in T_STATISTIC_RESULT;
PARAMETER_DEFINITION : in T_PARAMETER_DEFINITION;
STATISTIC_VALUES : in out T_STATISTIC_VALUE);
–– Extract data from a statistic result for a given parameter.
––
–– Parameters :
–– STATISTIC_RESULT : private statistic result
–– PARAMETER_DEFINITION : private parameter definition
–– STATISTIC_VALUES : statistic values
–– Exceptions :
–– X_STATISTIC_RESULT_NOT_OPENED : supplied statistic result
–– is not opened
–– X_NO_READ_ACCESS : statistic result not open with read
–– access
–– X_INVALID_PARAMETER : invalid parameter definition
–– X_NO_DATA_AVAILABLE : data are not available
–– X_ERROR_ACCESSING_FILE : general error accessing listing
–– result file
––
procedure ADD_STATISTICS(STATISTIC_RESULT : in out T_STATISTIC_RESULT;
PARAMETER_NAME : in TEV_DEFINITIONS.T_PARAMETER_NAME;
ENGINEERING_UNIT : in MPS_DEFINITIONS.T_ENGINEERING_UNIT;
SOURCE_FILE_TYPE : in TEV_DEFINITIONS.T_SOURCE_FILE_TYPE;
PRODUCER : in TEV_DEFINITIONS.T_PRODUCER_NAME;
PARAM_VALUES : in T_PARAMETER_VALUE_L);
–– Add a new value in the statistic result for the next empty
–– parameter.
––
–– Parameters :
–– STATISTIC_RESULT : private statistic result
–– PARAMETER_NAME : parameter name to be added
–– ENGINEERING_UNIT : engineering unit for the parameter
–– SOURCE_FILE_TYPE : source file type for the parameter
–– PRODUCER : producer of the parameter
–– PARAM_VALUES : list of parameter values for which to
calculate the statistics
–– Exceptions :
–– X_STATISTIC_RESULT_NOT_OPENED : statistic result is not
–– opened
–– X_NO_WRITE_ACCESS : statistic result not opened for
write
–– access
–– X_NO_PARAMETER_AVAILABLE : no parameter created yet
–– X_ERROR_ACCESSING_FILE : general error accessing file
–– X_INVALID_PARAMETER : the parameter is invalid
–– X_INVALID_VALUE : an inconsistency exists in the values
–– Provided exceptions :
X_STATISTIC_RESULT_NOT_OPENED,
X_ERROR_ACCESSING_FILE,
X_STATISTIC_RESULT_ALREADY_OPENED,
X_STATISTIC_RESULT_ALREADY_EXISTS,
X_INVALID_NAME,
X_NO_READ_ACCESS,
X_NO_WRITE_ACCESS,
X_INVALID_PARAMETER,
X_PARMS_DO_NOT_FIT_IN_PORTRAIT_WIDTH,
X_INVALID_VALUE : exception;
private
type T_PARAMETER_DEFINITION is
record
PARAMETER_INDEX : TEV_DEFINITIONS.T_PARAMETERS_RANGE;

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
542 von/of: 662
PARAMETER_NAME : TEV_DEFINITIONS.T_PARAMETER_NAME;
ENGINEERING_UNIT : MPS_DEFINITIONS.T_ENGINEERING_UNIT;
SOURCE_FILE_TYPE : TEV_DEFINITIONS.T_SOURCE_FILE_TYPE;
PRODUCER : TEV_DEFINITIONS.T_PRODUCER_NAME;
end record;
subtype T_PARAMETER_RANGE_L is
NATURAL range 1 .. TEV_DEFINITIONS.MAX_NUMBER_OF_PARAMETERS_IN_DEF;
type T_PARAMETER_DEFINITIONS_ARRAY is
array(T_PARAMETER_RANGE_L) of T_PARAMETER_DEFINITION;
–– definition of an array of a parameter definition
type T_STATISTIC_DEFINITION is
record
TIME_FRAME : TEV_DEFINITIONS.T_TIME_FRAME;
SELECT_ON : DBS_DEFINITIONS.T_TIME_TYPE;
ORDER_BY : DBS_DEFINITIONS.T_TIME_ORDERING;
DATA_SET : TEV_DEFINITIONS.T_RESULT_REF;
TITLE : TEV_DEFINITIONS.T_TITLE;
SAMPLING : TEV_DEFINITIONS.T_SAMPLING;
SESSIONS_NUMBER : NATURAL := 0;
SESSIONS :
TEV_DEFINITIONS.T_DEFINITION_SESSION_NAMES(TEV_DEFINITIONS.T_SESSIONS_RANGE);
INCLUDE_DEF_SESSION : BOOLEAN;
EXECUTION_TIME : CGS_CALENDAR.CGS_DATE_AND_TIME;
PARAMETERS_NUMBER : NATURAL := 0;
PARAMETER_DEFINITIONS : T_PARAMETER_DEFINITIONS_ARRAY;
end record;
package DEFINITION_IO is new DIRECT_IO( ELEMENT_TYPE => T_STATISTIC_DEFINITION);
–– DEFINITION_IO is used to access the listing result definition as
––
––
the header of the file
package STATISTICS_IO is new DIRECT_IO( ELEMENT_TYPE => T_STATISTIC_VALUE);
–– STATISTICS_IO is used to access the statistic value records inside
–– the file, the statistic value to access is located at byte offset
––
––
PTR_TO_STATISTIC
type T_STATISTIC_RESULT is
record
DEFINITION_FILE_TYPE : DEFINITION_IO.FILE_TYPE;
STATISTIC_FILE_TYPE : STATISTICS_IO.FILE_TYPE;
FILENAME :
TEV_DEFINITIONS.T_COMPLETE_FILENAME;
ACCESS_STATUS : TEV_DEFINITIONS.T_ACCESS_STATUS :=
TEV_DEFINITIONS.READ;
CURRENT_STATUS : TEV_DEFINITIONS.T_CURRENT_STATUS :=
TEV_DEFINITIONS.CLOSED;
STATISTIC_DEFINITION : T_STATISTIC_DEFINITION;
end record;
end ADT_STATISTICS_RESULT;

Space Infrastructure
Formal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
––
–– ADT_GRAPH_RESULT
––
––****************************************************************************
––ABSTRACT––
––
–– Provides operations to access a graphs result file.
––
––*–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––IDENTIFICATION––
–– PROJECT NAME : CGS
–– PRODUCT NAME : TEV
–– CI–NUMBER : 1216 858
–– OBJECT NAME : HDT_TEV_API.ADT_GRAPH_RESULT
––*–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––CONTENTS––
–– COMPILER : VERDIX ADA 6.0.3.C
–– LANGUAGE : ADA
–– SPECIAL CONTENTS:
–– CHANGE HISTORY
–– V5.2 at Central Repository V4.0 (moon)
–– creator: thvvicos (on host darkvador)
–– creation date: 20.07.97 20:54:52
–– comment:
–– Compliance with 4.1 : Tool id added
––
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V4.4 at Spacebel Informatique, Brussels
–– creator: jm (on host asimov)
–– creation date: 15.12.95 16:26:02
–– comment:
–– Not numeric data refused
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V4.3 at Spacebel Informatique, Brussels
–– creator: jm (on host asimov)
–– creation date: 29.09.95 18:09:42
–– comment:
–– Update for SMT/LT (Req.485)
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V4.2 at Spacebel Informatique, Brussels
–– creator: rowena (on host moon)
–– creation date: 25.07.95 10:47:44
–– comment:
–– Move from VICOS_CALENDAR to CGS_CALENDAR
––
––*––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– END HISTORY
––****************************************************************************
––
with DBS_DEFINITIONS;
with TEV_DEFINITIONS;
with MPS_DEFINITIONS;
with CGS_CALENDAR;
with ADT_ENGINEERING_VALUE;
with VICOS_LIST;
with TEXT_IO;
package ADT_GRAPH_RESULT is
type T_GRAPH_RESULT is limited private;
–– private graph result
–– Provided operations :
procedure OPEN(
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
543 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
GRAPH_RESULT_FILENAME : in STRING;
GRAPH_RESULT : in out T_GRAPH_RESULT;
ACCESS_STATUS : in TEV_DEFINITIONS.T_ACCESS_STATUS
:= TEV_DEFINITIONS.READ;
ALLOW_OVERWRITE : in BOOLEAN := FALSE);
–– Description:
–– Open a graph result with read access if it already exists,
–– or with write access to create a new one.
–– If opened with read access translate the definition into
–– T_GRAPH_RESULT and write current date and time in EXECUTION_TIME.
––
–– Parameters :
–– GRAPH_RESULT_FILENAME : filename of the graph result
–– GRAPH_RESULT : private graph result
–– ACCESS_STATUS : – READ only to extract information from
–– graph result
–– WRITE when generating a graph result
–– ALLOW_OVERWRITE : when ACCESS_STATUS is WRITE,
–– needed to allow generation of a graph result inside an already
–– existing file
–– Exceptions :
–– X_ERROR_ACCESSING_FILE : general error reported when
–– accessing the file
–– X_GRAPH_RESULT_ALREADY_OPENED : graph result has not
–– been closed
–– X_GRAPH_RESULT_ALREADY_EXISTS : file exists and
–– overwrite is not allowed
–– X_INVALID_NAME: graph result name is too long
––
procedure CLOSE(GRAPH_RESULT : in out T_GRAPH_RESULT);
–– Description:
–– if graph result opened for write access then write graph
–– result file and close, otherwise close.
––
–– Parameters :
–– GRAPH_RESULT : private graph result
–– Exceptions :
–– X_ERROR_ACCESSING_FILE : general error reported when
–– accessing the file
–– X_GRAPH_RESULT_NOT_OPENED : graph result already closed
–– X_NO_WRITE_ACCESS : graph result not opened with write
–– access
–– X_UNABLE_TO_REMOVE_FILE : unable to remove temporary
–– file
–– X_NOT_NUMERIC_DATA : graph result contains a not numeric
–– data
–– X_INVALID_PROLOG_NAME : the prolog file does not exist
–– X_NO_DATA_AVAILABLE : no parameters selected
–– X_INVALID_SCALING : the value is outside the scaling or of the
wrong type
procedure DEFINE(
GRAPH_RESULT : in out T_GRAPH_RESULT;
GRAPH_TYPE : in TEV_DEFINITIONS.T_GRAPH_TYPE;
TIME_FRAME : in TEV_DEFINITIONS.T_TIME_FRAME;
SELECT_ON : in DBS_DEFINITIONS.T_TIME_TYPE;
ORDER_BY : in DBS_DEFINITIONS.T_TIME_ORDERING;
INCLUDE_DEF_SESSION : in BOOLEAN;
SESSIONS : in TEV_DEFINITIONS.T_DEFINITION_SESSION_NAMES;
DATA_SET : in TEV_DEFINITIONS.T_RESULT_REF;
GRAPH_NAME : in TEV_DEFINITIONS.T_RESULT_NAME);
–– Description:
–– Build and initialise the definition of an opened graph result
––
–– Parameters :
–– GRAPH_RESULT : private event result
–– TIME_FRAME : time frame for the graph result
–– INCLUDE_DEF_SESSION : default session included in data set
–– SESSIONS : execution sessions included in data set
–– DATA_SET : the data set from which the graph result is
–– built
–– GRAPH_NAME : the graph name
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
544 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–– Exceptions :
–– X_GRAPH_RESULT_NOT_OPENED : graph result is not opened
–– X_NO_WRITE_ACCESS : graph result not opened for write
–– access
–– X_TOO_MANY_SESSIONS : too many sessions selected
procedure SET_LINE_CHARACTERISTICS(
GRAPH_RESULT : in out T_GRAPH_RESULT;
PARAMETERS_INFO :in
TEV_DEFINITIONS.T_LINE_PARAMETERS_INFO;
X_NAME : in TEV_DEFINITIONS.T_AXIS_NAME;
Y_NAME : in TEV_DEFINITIONS.T_AXIS_NAME;
Y_SCALING : in TEV_DEFINITIONS.T_GRAPH_SCALING;
RELATIVE_TIME : in boolean := false);
–– Set the characteristics for a line graph
––
–– Parameters :
–– GRAPH_RESULT : private graph result
–– PARAMETERS_INFO : parameter details for line graph
–– Y_NAME : name of y axis
–– RELATIVE_TIME : true if time info is relative
–– Exceptions :
–– X_GRAPH_RESULT_NOT_OPENED : graph result is not opened
–– X_NO_WRITE_ACCESS : graph result not opened for write
–– access
––
procedure SET_CHART_CHARACTERISTICS(
GRAPH_RESULT : in out T_GRAPH_RESULT;
CHART_COLOURS : in TEV_DEFINITIONS.T_CHART_COLOURS);
–– Set the pie/bar chart characteristics
––
–– Parameters :
–– GRAPH_RESULT : private graph result
–– CHART_COLOURS : allowed colours for the parameters
–– Exceptions :
–– X_GRAPH_RESULT_NOT_OPENED : graph result is not opened
–– X_NO_WRITE_ACCESS : graph result is not opened for write
–– access
–– X_INVALID_PARAMETER_NO : invalid number of parameters
–– X_INVALID_GRAPH_TYPE : not a pie or bar chart
procedure SET_XY_CHARACTERISTICS(
GRAPH_RESULT : in out T_GRAPH_RESULT;
PARAMETERS_INFO : in TEV_DEFINITIONS.T_XY_INFO);
–– Set the xy graph characteristics
––
–– Parameters :
–– GRAPH_RESULT : private graph result
–– CHARACTERISTICS : xy graph parameters info
–– Exceptions :
–– X_GRAPH_RESULT_NOT_OPENED : graph result is not opened
–– X_NO_WRITE_ACCESS : graph result is not opened for write
–– access
––
function DATA_SET_NAME_OF(GRAPH_RESULT : in T_GRAPH_RESULT)
return TEV_DEFINITIONS.T_RESULT_REF;
–– Get the name of the data set
––
–– Parameters :
–– GRAPH_RESULT : private graph result
–– Exceptions :
–– X_GRAPH_RESULT_NOT_OPENED : graph result is not open
–– X_NO_READ_ACCESS : graph result not opened for read access
function TITLE_OF(GRAPH_RESULT : in T_GRAPH_RESULT)
return TEV_DEFINITIONS.T_RESULT_NAME;
–– Get the title of the graph result
––
–– Parameters :
–– GRAPH_RESULT : private graph result
–– Exceptions :
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
545 von/of: 662

Space Infrastructure
––
––
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–– X_GRAPH_RESULT_NOT_OPENED : graph result is not open
–– X_NO_READ_ACCESS : graph result not opened for read access
function TIME_FRAME_OF(GRAPH_RESULT : in T_GRAPH_RESULT)
return TEV_DEFINITIONS.T_TIME_FRAME;
–– Get the time frame of the graph result
––
–– Parameters :
–– GRAPH_RESULT : private graph result
–– Exceptions :
–– X_GRAPH_RESULT_NOT_OPENED : graph result is not open
–– X_NO_READ_ACCESS : graph result not opened for read access
––
function GRAPH_TYPE_OF(GRAPH_RESULT : in T_GRAPH_RESULT)
return TEV_DEFINITIONS.T_GRAPH_TYPE;
–– Get the graph type of the graph result file
––
–– Parameters :
–– GRAPH_RESULT : private graph result
–– Exceptions :
–– X_GRAPH_RESULT_NOT_OPENED : graph result is not open
–– X_NO_READ_ACCESS : graph result not opened for read access
function SESSION_NUMBER_OF(GRAPH_RESULT : in T_GRAPH_RESULT)
return NATURAL;
–– Get the number of execution sessions in the data set
––
–– Parameters :
–– GRAPH_RESULT ; private graph result
–– Exceptions :
–– X_GRAPH_RESULT_NOT_OPENED : graph result is not open
–– X_NO_READ_ACCESS : graph result not opened for read access
function SESSION_NAMES_OF(GRAPH_RESULT : in T_GRAPH_RESULT)
return TEV_DEFINITIONS.T_DEFINITION_SESSION_NAMES;
–– Get the execution session names from the data set
––
–– Parameters :
–– GRAPH_RESULT : private graph result
–– Exceptions :
–– X_GRAPH_RESULT_NOT_OPENED : the graph result is not open
–– X_NO_READ_ACCESS : graph result not opened for read access
––
function NUMBER_OF_PARAMETERS(
GRAPH_RESULT : in T_GRAPH_RESULT) return NATURAL;
–– Get the number of parameters for a graph result
––
–– Parameters :
–– GRAPH_RESULT : private graph result
–– Exceptions :
–– X_GRAPH_RESULT_NOT_OPENED : the graph result is not open
–– X_NO_READ_ACCESS: graph result not opened for read acces
procedure PARAMETER_DETAILS(
GRAPH_RESULT : in T_GRAPH_RESULT;
PARAMETER_NO : in NATURAL;
PARAMETER_NAME: out
TEV_DEFINITIONS.T_PARAMETER_NAME;
ENGINEERING_UNIT: out
MPS_DEFINITIONS.T_ENGINEERING_UNIT;
SOURCE_FILE_TYPE: out
TEV_DEFINITIONS.T_SOURCE_FILE_TYPE;
ITEM_TYPE: out
TEV_DEFINITIONS.T_MEASUREMENT_ALTERNATIVES;
TEV_DEFINITIONS.T_PRODUCER_NAME);
–– Get the parameter details of a graph result
––
PRODUCER : out
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
546 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–– Parameters :
–– GRAPH_RESULT : private graph result
–– PARAMETER_NO: the number of the parameter index
–– PARAMETER_NAME: the parameter name
–– ENGINEERING_UNIT: the engineering unit
–– SOURCE_FILE_TYPE: the source file type
–– ITEM_TYPE : the item type
–– PRODUCER : the producer
–– Exceptions :
–– X_GRAPH_RESULT_NOT_OPENED : the graph result is not open
–– X_NO_READ_ACCESS: graph result not opened for read acces
–– X_INVALID_PARAMETER_INDEX : invalid parameter index
procedure GET_LINE_GRAPH_CHARACTERISTICS(
GRAPH_RESULT : in T_GRAPH_RESULT;
LINE_INFO: out
TEV_DEFINITIONS.T_LINE_PARAMETERS_INFO;
X_NAME : out TEV_DEFINITIONS.T_AXIS_NAME;
Y_NAME : out TEV_DEFINITIONS.T_AXIS_NAME;
NO_PARAMETERS : out
TEV_DEFINITIONS.T_LINE_GRAPH_RANGE;
Y_SCALING : out TEV_DEFINITIONS.T_GRAPH_SCALING;
X_REL_TIME : out BOOLEAN);
–– Get the characteristics of a line graph
––
–– Parameters :
–– GRAPH_RESULT : private graph result
–– LINE_INFO : the characteristics of a line graph
–– X_NAME : the name of the x axis
–– Y_NAME : the name of the y axis
–– Y_SCALING : the y scaling
–– X_REL_TIME : relative time on the x axis
–– Exceptions :
–– X_GRAPH_RESULT_NOT_OPENED : graph result is not open
–– X_INVALID_GRAPH_TYPE : the graph result is not of the type line
–– X_NO_READ_ACCESS : the graph result is not opened for read
–– access
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
547 von/of: 662
procedure GET_CHART_CHARACTERISTICS(GRAPH_RESULT : in T_GRAPH_RESULT;
CHART_COLOURS : out TEV_DEFINITIONS.T_CHART_COLOURS);
–– Get the characteristics of a pie/bar chart
––
–– Parameters :
–– GRAPH_RESULT : private graph result
–– CHART_COLOURS : allowed colours for the parameters
–– Exceptions :
–– X_GRAPH_RESULT_NOT_OPENED : the graph result is not open
–– X_INVALID_GRAPH_TYPE : the graph result is not of type bar
X_NO_READ_ACCESS : the graph result is not opened for read
–– access
procedure GET_XY_CHARACTERISTICS(GRAPH_RESULT : in T_GRAPH_RESULT;
XY_INFO : out TEV_DEFINITIONS.T_XY_INFO);
–– Get the characteristics of an xy graph
––
–– Parameters :
–– GRAPH_RESULT : private graph result
–– XY_INFO : the characteristics of an xy graph
–– Exceptions :
–– X_GRAPH_RESULT_NOT_OPENED : the graph result is not open
–– X_INVALID_GRAPH_TYPE : the graph result is not of type XY
X_NO_READ_ACCESS : the graph result is not opened for read
–– access
––
function EXECUTION_TIME_OF(GRAPH_RESULT : in T_GRAPH_RESULT)
return CGS_CALENDAR.CGS_DATE_AND_TIME;
–– return the execution date and time of the graph result
––
–– Parameters :
–– GRAPH_RESULT : private graph result

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–– Exceptions :
–– X_GRAPH_RESULT_NOT_OPENED : graph result is not open
X_NO_READ_ACCESS : the graph result is not opened for read
–– access
––
––
function INCLUDE_DEFAULT_SESSION(GRAPH_RESULT : in T_GRAPH_RESULT)
return BOOLEAN;
–– return true if the default session is included
––
–– Parameters :
–– GRAPH_RESULT : private graph result
–– Exceptions :
–– X_GRAPH_RESULT_NOT_OPENED : graph result is not open
X_NO_READ_ACCESS : the graph result is not opened for read
–– access
––
function GET_SELECTED_ON_TIME_TYPE(GRAPH_RESULT : in T_GRAPH_RESULT)
return DBS_DEFINITIONS.T_TIME_TYPE;
–– return the time type of the selection
––
–– Parameters :
–– GRAPH_RESULT : private graph result
–– Exceptions :
–– X_GRAPH_RESULT_NOT_OPENED : graph result is not open
X_NO_READ_ACCESS : the graph result is not opened for read
–– access
––
function GET_ORDERED_BY_TIME_TYPE(GRAPH_RESULT : in T_GRAPH_RESULT)
return DBS_DEFINITIONS.T_TIME_ORDERING;
–– return the time type of the selection
––
–– Parameters :
–– GRAPH_RESULT : private graph result
–– Exceptions :
–– X_GRAPH_RESULT_NOT_OPENED : graph result is not open
X_NO_READ_ACCESS : the graph result is not opened for read
–– access
––
procedure ADD_NEW_PARAMETER(GRAPH_RESULT : in out T_GRAPH_RESULT;
PARAMETER_NAME : in TEV_DEFINITIONS.T_PARAMETER_NAME;
ENGINEERING_UNIT : in MPS_DEFINITIONS.T_ENGINEERING_UNIT;
SOURCE_FILE_TYPE : in TEV_DEFINITIONS.T_SOURCE_FILE_TYPE;
PRODUCER : in TEV_DEFINITIONS.T_PRODUCER_NAME;
ITEM_TYPE :in TEV_DEFINITIONS.T_MEASUREMENT_ALTERNATIVES);
–– Add a new parameter in the graph result definition.
––
–– Parameters :
–– GRAPH_RESULT : private graph result
–– PARAMETER_NAME : name of the parameter inserted
–– ENGINEERING_UNIT : engineering unit
–– SOURCE_FILE_TYPE : type of the source file
–– PRODUCER : name of the producer
–– ITEM_TYPE : item type
–– Exceptions :
–– X_GRAPH_RESULT_NOT_OPENED : graph result is not opened
–– X_NO_WRITE_ACCESS : graph result not opened for write
–– access
–– X_TOO_MANY_PARAMETERS : maximum number of parameter
–– reached
–– X_DIFFERENT_ENGINEERING_UNITS_FOR_PIE_CHART :
–– parameters of a pie chart have different engineering units
––
procedure ADD_NEW_VALUES(
GRAPH_RESULT : in out T_GRAPH_RESULT;
VALUES : in out
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
548 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
TEV_DEFINITIONS.T_PARAMETER_VALUE_L);
–– Add a list of values in the graph result for the last defined
–– parameter. This operation may not be used for an XY graph.
––
–– Parameters :
–– GRAPH_RESULT : private graph result
–– VALUES : list of values
–– Exceptions :
–– X_GRAPH_RESULT_NOT_OPENED : graph result is not opened
–– X_NO_WRITE_ACCESS : graph result not opened for write
–– access
–– X_NO_PARAMETER_AVAILABLE : no parameter created yet
–– X_ERROR_ACCESSING_FILE : general error accessing file
–– X_NOT_ALLOWED_FOR_XY : operation not allowed for XY
–– graph
–– X_VALUES_ALREADY_SET : values have already been added
procedure ADD_VALUES_FOR_XY_GRAPH(
GRAPH_RESULT : in out T_GRAPH_RESULT;
X_VALUES : in out
TEV_DEFINITIONS.T_ENGINEERING_VALUE_L;
Y_VALUES : in out
TEV_DEFINITIONS.T_ENGINEERING_VALUE_L;
LT_TIME_VALUES : in out
TEV_DEFINITIONS.T_DATE_AND_TIME_L;
SMT_TIME_VALUES : in out
TEV_DEFINITIONS.T_DATE_AND_TIME_L);
–– Add the values for an XY graph. There must be the same number
–– of elements in each list.
––
–– Parameters :
–– GRAPH_RESULT : private graph result
–– X_VALUES : list of x values
–– Y_VALUES : list of corresponding y values
–– LT_TIME_VALUES : list of corresponding LT time tags
–– SMT_TIME_VALUES : list of corresponding SMT time tags
–– Exceptions :
–– X_GRAPH_RESULT_NOT_OPENED : graph result is not opened
–– X_NO_WRITE_ACCESS : graph result not opened for write access
–– X_X_AND_Y_PARAMETERS_NOT_AVAILABLE : no x and y
–– parameters created yet
–– X_ERROR_ACCESSING_FILE : general error accessing file
–– X_INVALID_GRAPH_TYPE : Graph type not XY
–– X_LISTS_DO_NOT_MATCH : the x values, y values and time
–– values do not match
––
procedure FORMAT_RESULT(FILE_TO_FORMAT : in STRING;
FORMATTED_FILE : in STRING;
TOOL_ID : in TEV_DEFINITIONS.T_TOOL_ID := POSITIVE’first);
–– Operation retained for orthogonal processing through the
–– tools. No formatting is undertaken as the file is already in
–– postscript format.
––
–– Parameters :
–– FILE_TO_FORMAT : file to format
–– FORMATTED_FILE : filename of formatted result
–– TOOL_ID : the tool id
–– Exceptions :
–– X_FILE_DOES_NOT_EXIST : the file to format does not exist
–– X_ACCESS_VIOLATION : unable to access the file to format
–– X_ERROR_READNG_FILE : general error reading file to format
–– X_ERROR_CREATING_FILE : general error creating formatted
–– result
X_GRAPH_RESULT_ALREADY_OPENED,
X_GRAPH_RESULT_ALREADY_EXISTS,
X_GRAPH_RESULT_NOT_OPENED,
X_DIFFERENT_ENGINEERING_UNITS_FOR_PIE_CHART,
X_NOT_ALLOWED_FOR_XY,
X_X_AND_Y_PARAMETERS_NOT_AVAILABLE,
X_LISTS_DO_NOT_MATCH,
X_NO_WRITE_ACCESS,
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
549 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
X_NO_READ_ACCESS,
X_ERROR_ACCESSING_FILE,
X_TOO_MANY_SESSIONS,
X_TOO_MANY_PARAMETERS,
X_NO_PARAMETER_AVAILABLE,
X_VALUES_ALREADY_SET,
–– added by JCT@SIF (dec.95) : data in graph must be numeric.
X_NOT_NUMERIC_DATA,
X_INVALID_SCALING,
X_INVALID_GRAPH_TYPE,
X_INVALID_PARAMETER_INDEX,
X_INVALID_NAME,
X_INVALID_PROLOG_NAME,
X_NO_DATA_AVAILABLE : exception;
private
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
550 von/of: 662
type T_GRAPH_CHARACTERISTIC(GRAPH_TYPE :
TEV_DEFINITIONS.T_GRAPH_TYPE := TEV_DEFINITIONS.UNDEFINED) is
record
case GRAPH_TYPE is
when TEV_DEFINITIONS.LINE =>
LINE_PARAMETER_INFO : TEV_DEFINITIONS.T_LINE_PARAMETERS_INFO;
X_NAME : TEV_DEFINITIONS.T_AXIS_NAME;
Y_NAME : TEV_DEFINITIONS.T_AXIS_NAME;
X_REL_TIME : BOOLEAN := FALSE;
Y_SCALING : TEV_DEFINITIONS.T_GRAPH_SCALING
:= TEV_DEFINI-
TIONS.DEFAULT_SCALING;
when TEV_DEFINITIONS.BAR | TEV_DEFINITIONS.PIE =>
CHART_COLOURS : TEV_DEFINITIONS.T_CHART_COLOURS;
when TEV_DEFINITIONS.XY =>
XY_PARAMETER_INFO : TEV_DEFINITIONS.T_XY_INFO;
when others =>
null;
end case;
end record;
type T_PARAMETER_DEFINITION is
record
PARAMETER_NAME : TEV_DEFINITIONS.T_PARAMETER_NAME :=
TEV_DEFINITION-
S.NULL_PARAMETER_NAME;
ENGINEERING_UNIT : MPS_DEFINITIONS.T_ENGINEERING_UNIT:=
TEV_DEFINITION-
S.NULL_TEV_ENGINEERING_UNIT;
SOURCE_FILE_TYPE : TEV_DEFINITIONS.T_SOURCE_FILE_TYPE:=
TEV_DEFINITIONS.AR-
CHIVED_FILE;
ITEM_TYPE : TEV_DEFINITIONS.T_MEASUREMENT_ALTERNATIVES:=
TEV_DEFINITIONS.EGSE_IN-
TEGER_MEASUREMENT;
PRODUCER : TEV_DEFINITIONS.T_PRODUCER_NAME:=
TEV_DEFINITIONS.NULL_PRO-
DUCER_NAME;
DATA_NUMBER : natural := natural’first;
DATA_LIST : TEV_DEFINITIONS.T_PARAMETER_VALUE_L;
end record;
–– definition of a parameter
type T_GRAPH_DEFINITION is
record
DATA_SET : TEV_DEFINITIONS.T_RESULT_REF;
TIME_FRAME : TEV_DEFINITIONS.T_TIME_FRAME;
SELECT_ON : DBS_DEFINITIONS.T_TIME_TYPE;
ORDER_BY : DBS_DEFINITIONS.T_TIME_ORDERING;
GRAPH_NAME : TEV_DEFINITIONS.T_RESULT_NAME;
GRAPH_CHARACTERISTIC : T_GRAPH_CHARACTERISTIC;
SESSIONS_NO : natural;
SESSIONS : TEV_DEFINITIONS.T_DEFINITION_SESSION_NAMES(
TEV_DEFINITION-
S.T_SESSIONS_RANGE);
INCLUDE_DEF_SESSION : BOOLEAN;

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
EXECUTION_TIME : CGS_CALENDAR.CGS_DATE_AND_TIME;
end record;
–– definition of a graph. The execution sessions are the
–– execution sessions included in the data set
type T_PARAMETER_VALUE_DETAILS is array(
T_PARAMETER_DEFINITION;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
551 von/of: 662
1..TEV_DEFINITIONS.MAX_PARMS_IN_CHART)
of
type T_GRAPH_RESULT is
record
FILE_TYPE : TEXT_IO.FILE_TYPE;
FILENAME : TEV_DEFINITIONS.T_COMPLETE_FILENAME;
ACCESS_STATUS : TEV_DEFINITIONS.T_ACCESS_STATUS
:= TEV_DEFINITIONS.READ;
CURRENT_STATUS : TEV_DEFINITIONS.T_CURRENT_STATUS
:= TEV_DEFINITION-
S.CLOSED;
GRAPH_DEFINITION : T_GRAPH_DEFINITION;
PARAMETERS_NO : natural := natural’first;
GRAPH_DATA : T_PARAMETER_VALUE_DETAILS;
end record;
end ADT_GRAPH_RESULT;

Space Infrastructure
Formal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
––
–– ADT_PACKET_RESULT
––
––****************************************************************************
––ABSTRACT––
––
–– Provides operations to access a packet result file as an ADT.
––
––*–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––IDENTIFICATION––
–– PROJECT NAME : CGS
–– PRODUCT NAME : TEV
–– CI–NUMBER : 1216 858
–– OBJECT NAME : HDT_TEV_API.ADT_PACKET_RESULT
––*–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––CONTENTS––
–– COMPILER : VERDIX ADA 6.0.3.C
–– LANGUAGE : ADA
–– SPECIAL CONTENTS:
–– CHANGE HISTORY
–– V4.3 at DASA
–– creator: Bruening
–– creation date: 01.02.00
–– comment:
–– Add CAL_STATE_CODE for a GDU in T_PACKET_RECORD. The calibrated value
–– is then stored in the ADT, to avoid calling MDB for the formatting
––*–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V4.2 at DASA
–– creator: Bruening
–– creation date: 03.05.99
–– comment:
–– The record T_PACKET_DEFINITION contains two new components :
–– ADU_SID_PATHNAME List of SID–pathname for the ADU which
–– have been dumped
–– GDU_SID_PATHNAME List of SID–pathname for the GDU which
–– have been dumped
––
–– The two new components of the record can be set up through
–– the procedure DEFINE
––*–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– V4.2 at DASA
–– creator: Bruening
–– creation date: 28.04.99
–– comment:
–– New procedure CHANGE_TIME_FRAME_WHEN_INTERRUPTION used
–– to store into the result file the end time tag as the
–– interruption time tag
––
–– END HISTORY
––****************************************************************************
with TEV_DEFINITIONS;
with DBS_DEFINITIONS;
with CGS_CALENDAR;
with VICOS_LIST;
with DIRECT_IO;
with ADT_ADU;
with ADT_GDU;
with VICOS_DEFINITIONS;
with MPS_DEFINITIONS;
package ADT_PACKET_RESULT is
–– Provided types and constants :
SPEC_SCCSID_ADS : constant STRING := ”%Z%%Z%”;
type T_PACKET_RECORD(PACKET : TEV_DEFINITIONS.T_PACKET_TYPE
:= TEV_DEFINITIONS.NO_CHOICE) is record
PACKET_ID : POSITIVE;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
552 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
553 von/of: 662
ARCHIVED_TIME : CGS_CALENDAR.CGS_DATE_AND_TIME := CGS_CALENDAR.NULL_DATE_AND_TIME;
PRODUCER : VICOS_DEFINITIONS.T_APPLICATION_NAME;
case PACKET is
when TEV_DEFINITIONS.ADU =>
ADU_PACKET : ADT_ADU.T_ADU;
when TEV_DEFINITIONS.GDU =>
GDU_PACKET : ADT_GDU.T_GDU;
CAL_STATE_CODE : MPS_DEFINITIONS.STATE_CODE := (others => ’ ’);
when others =>
null;
end case;
end record;
–– Packet record containing any kind of record : ADU or GDU
–– definition of a list of packets (via the vicos list)
package P_PACKET_LIST is new VICOS_LIST(T_PACKET_RECORD);
subtype T_PACKET_L is P_PACKET_LIST.LIST;
type T_ADU_GDU_PATHNAME_LIST is array (integer range 1..20) of
TEV_DEFINITIONS.T_PACKET_PATHNAME;
type T_SID_PATHNAME_LIST is array (integer range 1..20) of TEV_DEFINITIONS.T_SID_PATHNAME;
–– T_PACKET_RESULT_ACCESS added by RSE for SPR_2391
type T_PACKET_RESULT_ACCESS_STATUS is (READ,WRITE,UPDATE_DISPLAY_CHARACTERISTICS);
type T_PACKET_RESULT is limited private;
–– Packet result ADT record
–– Provided operations :
procedure SAFE_OPEN(PACKET_RESULT_FILENAME : in STRING;
PACKET_RESULT : in out T_PACKET_RESULT);
–– Description :
–– Open a packet result, with read access,
––
–– Parameters :
–– PACKET_RESULT_FILENAME : filename of the packet result
–– PACKET_RESULT : private packet result
––
–– Exceptions :
–– X_ERROR_ACCESSING_FILE : general error reported when
–– accessing the file
–– X_INVALID_NAME : packet result name is too long
––
procedure SAFE_CLOSE(PACKET_RESULT : in out T_PACKET_RESULT);
–– Description :
–– Close a previously opened packet result file.
––
–– Parameters :
–– PACKET_RESULT : private packet result
–– Exceptions : none
––
–– modified by RSE for SPR_2391
procedure OPEN(PACKET_RESULT_FILENAME : in STRING;
PACKET_RESULT : in out T_PACKET_RESULT;
–– ACCESS_STATUS : in TEV_DEFINITIONS.T_ACCESS_STATUS
–– := TEV_DEFINITIONS.READ;
ACCESS_STATUS : in T_PACKET_RESULT_ACCESS_STATUS := READ;
ALLOW_OVERWRITE : in BOOLEAN := FALSE);
–– Description :
–– Open a packet result, with read access on an existing one,
–– with write access to create a new one.
–– with update_display_characteristics access to modify an existing one.
–– Read definition.
–– Write current date and time in EXECUTION_TIME if creating a new
–– packet result.
–– Close file
–– Open file at offset PTR_TO_FIRST_PACKET
––
–– Parameters :
–– PACKET_RESULT_FILENAME : filename of the packet result
–– PACKET_RESULT : private packet result

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
554 von/of: 662
–– ACCESS_STATUS : – READ only to extract information from
–– packet result
–– – WRITE when generating a packet result
–– – UPDATE_DISPLAY_CHARACTERISTICS to modify an existing result
–– ALLOW_OVERWRITE : when ACCESS_STATUS is WRITE, needed to allow
–– generation of a packet result inside an already existing file
–– Exceptions :
–– X_ERROR_ACCESSING_FILE : general error reported when
–– accessing the file
–– X_PACKET_RESULT_ALREADY_OPENED : packet result is still in
–– open state
–– X_PACKET_RESULT_ALREADY_EXISTS : file exists and overwrite
–– is not allowed
–– X_INVALID_NAME : packet result name is too long
––
procedure CLOSE(PACKET_RESULT : in out T_PACKET_RESULT);
–– Description :
–– Close a previously opened packet result file.
–– Open file
–– Write definition if opened for write access
–– Close file
––
–– Parameters :
–– PACKET_RESULT : private packet result
–– Exceptions :
–– X_ERROR_ACCESSING_FILE : general error reported when
–– accessing the file
–– X_PACKET_RESULT_NOT_OPENED : packet result already closed
––
procedure DEFINE(
PACKET_RESULT : in out T_PACKET_RESULT;
PACKET_RESULT_NAME : in TEV_DEFINITIONS.T_COMPLETE_FILENAME;
TIME_FRAME : in TEV_DEFINITIONS.T_TIME_FRAME;
SELECT_ON : in DBS_DEFINITIONS.T_TIME_TYPE;
ORDER_BY : in DBS_DEFINITIONS.T_TIME_ORDERING;
PRODUCER : in TEV_DEFINITIONS.T_PRODUCER_NAME;
INCLUDE_DEF_SESSION : in boolean;
EXECUTION_SESSIONS : in TEV_DEFINITIONS.T_DEFINITION_SESSION_NAMES;
CHARACTERISTIC : in TEV_DEFINITIONS.T_PACKET_TYPE
:= TEV_DEFINITIONS.ADUS;
FORMAT : in TEV_DEFINITIONS.T_PACKET_FORMAT
:= TEV_DEFINITIONS.DEFAULT_PACKET_FORMAT;
BYTES_PER_LINE : in TEV_DEFINITIONS.T_PACKET_BYTES_LINE
:= TEV_DEFINITIONS.DEFAULT_BYTES_LINE;
PATHNAME : in TEV_DEFINITIONS.T_PACKET_PATHNAME;
SUMMARY_FORMAT : in boolean := False;
SELECTED_ADUS : in T_ADU_GDU_PATHNAME_LIST;
SELECTED_GDUS : in T_ADU_GDU_PATHNAME_LIST;
ADU_SID_PATHNAME : in T_SID_PATHNAME_LIST;
GDU_SID_PATHNAME : in T_SID_PATHNAME_LIST);
–– Description :
–– Build and initialise the definition of an opened packet
–– result. Sets the field PTR_TO_FIRST_PACKET
––
–– Parameters :
–– PACKET_RESULT : private packet result
–– PACKET_RESULT_NAME : name of the packet result
–– TIME_FRAME : time frame of the packet result
–– SELECT_ON : time tag selection type ie SMT or LT
–– ORDER_BY : time order of the data set ie SMT or LT
–– PRODUCER : producer of packet result
–– INCLUDE_DEF_SESSION : flag to include default session
–– EXECUTION_SESSIONS : list of execution session names
–– CHARACTERISTIC : specific adu/gdu, all adu’s/gdu’s
–– FORMAT : output format
–– BYTES_PER_LINE : number of bytes per line
–– PATHNAME : pathname
–– Exceptions :
–– X_PACKET_RESULT_NOT_OPENED : packet result is not opened
–– X_NO_WRITE_ACCESS : packet result not opened for write access
–– X_TOO_MANY_SESSIONS : too many sessions defined

Space Infrastructure
––
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
555 von/of: 662
procedure CHANGE_TIME_FRAME_WHEN_INTERRUPTION(
PACKET_RESULT : in out T_PACKET_RESULT;
TIME_FRAME : in TEV_DEFINITIONS.T_TIME_FRAME);
–– Parameters :
–– PACKET_RESULT : private packet result
–– TIME_FRAME : new time frame of the packet result, up to the interruption
–– Exceptions :
–– X_PACKET_RESULT_NOT_OPENED : packet result is not opened
–– X_NO_WRITE_ACCESS : packet result not opened for write access
procedure SET_DISPLAY_CHARACTERISTICS(
PACKET_RESULT : in out T_PACKET_RESULT;
FORMAT : in TEV_DEFINITIONS.T_PACKET_FORMAT
:= TEV_DEFINITIONS.DEFAULT_PACKET_FORMAT;
BYTES_PER_LINE : in TEV_DEFINITIONS.T_PACKET_BYTES_LINE
:= TEV_DEFINITIONS.DEFAULT_BYTES_LINE;
SUMMARY_FORMAT : in boolean := False);
–– Description :
–– Set formatting informations. This operation can be called at
–– any time, when writing or reading a result file.
––
–– Parameters :
–– PACKET_RESULT : private packet result
–– FORMAT : output format
–– BYTES_PER_LINE : number of bytes per line
–– Exceptions :
–– X_PACKET_RESULT_NOT_OPENED : packet result is not opened
function TIME_FRAME_OF(PACKET_RESULT : in T_PACKET_RESULT)
return TEV_DEFINITIONS.T_TIME_FRAME;
–– Description :
–– Return the time frame in which the current packet result has
–– been built.
––
–– Parameters :
–– PACKET_RESULT : private packet result
–– Exceptions :
–– X_PACKET_RESULT_NOT_OPENED : packet result is not opened
–– X_NO_READ_ACCESS : packet result not opened for read access
––
function GET_SELECTED_ON_TIME_TYPE( PACKET_RESULT : in T_PACKET_RESULT)
return DBS_DEFINITIONS.T_TIME_TYPE;
–– Description :
–– Return the selected on time type with which the current packet result has been
–– built.
––
–– Parameters :
–– PACKET_RESULT : private packet result
–– Exceptions :
–– X_NO_READ_ACCESS : packet result not open with read access
–– X_PACKET_RESULT_NOT_OPENED : packet result is not opened
––
function GET_ORDERED_BY_TIME_TYPE( PACKET_RESULT : in T_PACKET_RESULT)
return DBS_DEFINITIONS.T_TIME_ORDERING;
–– Description :
–– Return the ordered by time type with which the current packet result has been
–– built.
––
–– Parameters :
–– PACKET_RESULT : private packet result
–– Exceptions :
–– X_NO_READ_ACCESS : packet result not open with read access
–– X_DATA_SET_NOT_OPENED : packet result is not opened
function FILENAME_OF(PACKET_RESULT : in T_PACKET_RESULT)
return STRING;
–– Description :

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–– Return the packet result file name.
––
–– Parameters :
–– PACKET_RESULT : private packet result
–– Exceptions :
–– X_PACKET_RESULT_NOT_OPENED : packet result is not opened
–– X_NO_READ_ACCESS : packet result not opened for read access
––
function PRODUCER_OF(PACKET_RESULT : in T_PACKET_RESULT)
return TEV_DEFINITIONS.T_PRODUCER_NAME;
–– Description :
–– Return the packet result producer
––
–– Parameters :
–– PACKET_RESULT : private packet result
–– Exceptions :
–– X_NO_READ_ACCESS : packet result not opened for read access
–– X_PACKET_RESULT_NOT_OPENED : packet result is not opened
––
function NO_OF_PACKETS(PACKET_RESULT : in T_PACKET_RESULT)
return NATURAL;
–– Description :
–– Return the number of packets
––
–– Parameters :
–– PACKET_RESULT : private packet result
–– Exceptions :
–– X_NO_READ_ACCESS : packet result not opened for read access
–– X_PACKET_RESULT_NOT_OPENED : packet result is not opened
––
function INCLUDE_DEF_SESSION_OF(PACKET_RESULT : in T_PACKET_RESULT)
return boolean;
–– Description :
–– Return the include default session flag
––
–– Parameters :
–– PACKET_RESULT : private packet result
–– Exceptions :
–– X_NO_READ_ACCESS : packet result not opened for read access
–– X_PACKET_RESULT_NOT_OPENED : packet result is not opened
––
function SESSIONS_NUMBER_OF(PACKET_RESULT : in T_PACKET_RESULT)
return NATURAL;
–– Description :
–– Return the number of sessions used to build the current packet
–– result
––
–– Parameters :
–– PACKET_RESULT : private packet result
–– Exceptions :
–– X_NO_READ_ACCESS : packet result not opened for read access
–– X_PACKET_RESULT_NOT_OPENED : packet result is not opened
––
function SESSION_NAMES_OF(PACKET_RESULT : in T_PACKET_RESULT)
return TEV_DEFINITIONS.T_DEFINITION_SESSION_NAMES;
–– Description :
–– Extract the list of execution session names from the packet
–– result definition
––
–– Parameters :
–– PACKET_RESULT : private packet result
–– Exceptions :
–– X_NO_READ_ACCESS : packet result not opened for read access
–– X_PACKET_RESULT_NOT_OPENED : packet result is not opened
––
function EXECUTION_DATE_OF(PACKET_RESULT : in T_PACKET_RESULT)
return CGS_CALENDAR.CGS_DATE_AND_TIME;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
556 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–– Description :
–– Return the date and time of execution
––
–– Parameters :
–– PACKET_RESULT : private packet result
–– Exceptions :
–– X_NO_READ_ACCESS : packet result not opened for read access
–– X_PACKET_RESULT_NOT_OPENED : packet result is not opened
––
procedure ADD_PACKET(PACKET_RESULT : in out T_PACKET_RESULT;
PACKET : in out T_PACKET_RECORD);
–– Description :
–– Add the supplied Packet to the packet result. The Packet Id
–– is the key to access data.
––
–– Parameters :
–– PACKET_RESULT : private packet result
–– PACKET : Packet to add
–– Exceptions :
–– X_PACKET_RESULT_NOT_OPENED : packet result is not opened
–– X_NO_WRITE_ACCESS : packet result not opened for write access
–– X_ERROR_ACCESSING_FILE : general error writing the record
––
procedure GET_A_PACKET(
PACKET_RESULT : in T_PACKET_RESULT;
PACKET_ID : in positive;
PACKET : in out T_PACKET_RECORD);
–– Description :
–– Extract a given packet packet from a packet result
––
––
by specifying its Id.
–– Parameters :
–– PACKET_RESULT : private packet result
–– PACKET_ID : id of the packet to retrieve
–– PACKET : private packet record
–– Exceptions :
–– X_PACKET_RESULT_NOT_OPENED : supplied packet result file is
–– not open
–– X_NO_READ_ACCESS : packet result not open with read access
–– X_NO_PACKETS_AVAILABLE : packets are not available
–– X_ERROR_ACCESSING_FILE : general error accessing packet
––
––
result file
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
557 von/of: 662
procedure GET_A_PACKET(
PACKET_RESULT : in T_PACKET_RESULT;
TIME_TAG : in CGS_CALENDAR.CGS_DATE_AND_TIME;
PACKET_TYPE : in TEV_DEFINITIONS.T_PACKET_TYPE;
PACKET : in out T_PACKET_RECORD);
–– Description :
–– Extract a given packet packet from a packet result
––
––
by specifying its time tag and type.
–– Parameters :
–– PACKET_RESULT : private packet result
–– TIME_TAG : time tag of the packet to retrieve
–– PACKET_TYPE : type of record to retrieve
–– PACKET : private packet record
–– Exceptions :
–– X_PACKET_RESULT_NOT_OPENED : supplied packet result file is
–– not open
–– X_NO_READ_ACCESS : packet result not open with read access
–– X_NO_PACKETS_AVAILABLE : packets are not available
–– X_ERROR_ACCESSING_FILE : general error accessing packet
––
––
result file
procedure GET_PACKETS(
PACKET_RESULT : in T_PACKET_RESULT;
PACKET_LIST : in out T_PACKET_L;
PACKET_TYPE : in TEV_DEFINITIONS.T_PACKET_TYPE

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
:= TEV_DEFINITIONS.NO_CHOICE;
TIME_FRAME : in TEV_DEFINITIONS.T_TIME_FRAME
:= TEV_DEFINITIONS.NULL_TIME_FRAME;
ONLY_THE_FIRST : in boolean := false);
–– Description :
––
––
Extract packets from a packet result for a given time frame
–– Parameters :
–– PACKET_RESULT : private packet result
–– PACKET_LIST : extracted list of packets
–– PACKET_TYPE : type of record to retrieve
–– TIME_FRAME : time frame for which to make the selection
––
–– Exceptions :
ONLY_THE_FIRST : if true only the first record is returned
–– X_PACKET_RESULT_NOT_OPENED : supplied packet result file is
–– not open
–– X_NO_READ_ACCESS : packet result not open with read access
–– X_ERROR_ACCESSING_FILE : general error accessing packet
–– result file
–– X_INVALID_PACKET : a packet is invalid in the file
––
procedure FORMAT_A_PACKET(
PACKET_RESULT : in T_PACKET_RESULT;
FILENAME : in string;
PACKET_ID : in POSITIVE;
TOOL_ID : in TEV_DEFINITIONS.T_TOOL_ID);
–– Description :
–– Converts a given packet into a result file to a string format
––
–– Parameters :
–– PACKET_RESULT : private packet result
–– PACKET_ID : id of the packet to format
–– FILENAME : filename of formatted result
–– TOOL_ID : Tool id used for error logging
–– Exceptions :
–– X_PACKET_RESULT_NOT_OPENED : packet result is not opened
–– X_NO_READ_ACCESS : packet result not open with read access
–– X_ERROR_CREATING_FILE : general error creating formatted result
––
procedure FORMAT_A_PACKET(
PACKET_RESULT : in T_PACKET_RESULT;
TIME_TAG : in CGS_CALENDAR.CGS_DATE_AND_TIME;
PACKET_TYPE : in TEV_DEFINITIONS.T_PACKET_TYPE;
FILENAME : in string;
TOOL_ID : in TEV_DEFINITIONS.T_TOOL_ID);
–– Description :
–– Converts a given packet into a result file to a string format
––
–– Parameters :
–– PACKET_RESULT : private packet result
–– TIME_TAG : time tag of the packet to format
–– PACKET_TYPE : type of record to retrieve
–– FILENAME : filename of formatted result
–– TOOL_ID : Tool id used for error logging
–– Exceptions :
–– X_PACKET_RESULT_NOT_OPENED : packet result is not opened
–– X_NO_READ_ACCESS : packet result not open with read access
–– X_ERROR_CREATING_FILE : general error creating formatted result
––
procedure FORMAT_RESULT_FILE(
FILE_TO_FORMAT : in STRING;
FORMATTED_FILE : in STRING;
TOOL_ID : in TEV_DEFINITIONS.T_TOOL_ID);
–– Description :
–– Converts a packet result file to a string format for display
––
–– Parameters :
–– FILE_TO_FORMAT : filename of packet result to format
–– FORMATTED_FILE : filename of formatted result
–– PACKET_ID : the packet id
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
558 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–– Exceptions :
–– X_INVALID_NAME : packet result name is invalid
–– X_ERROR_ACCESSING_FILE : general error accessing packet
–– result file
–– X_ERROR_CREATING_FILE : general error creating formatted result
––
procedure FORMAT_RESULT_IN_SUMMARY(
FILE_TO_FORMAT : in STRING;
FORMATTED_FILE : in STRING);
–– Description :
–– Converts a packet result file to a string format for display
–– only summary info
––
–– Parameters :
–– FILE_TO_FORMAT : filename of packet result to format
–– FORMATTED_FILE : filename of formatted result
–– Exceptions :
–– X_INVALID_NAME : packet result name is invalid
–– X_ERROR_ACCESSING_FILE : general error accessing packet
–– result file
–– X_ERROR_CREATING_FILE : general error creating formatted result
––
function IS_SUMMARY(
PACKET_RESULT : in T_PACKET_RESULT) return boolean;
–– Description :
–– Return true if summary format is set
––
–– Parameters :
–– PACKET_RESULT : private packet result
–– Exceptions :
–– X_NO_READ_ACCESS : packet result not open with read access
–– X_PACKET_RESULT_NOT_OPENED : packet result is not opened
––
procedure FORMAT_PRINT_RESULT_FILE(
FILE_TO_FORMAT : in STRING;
FORMATTED_FILE : in STRING);
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
559 von/of: 662
procedure INVERT (THE_LIST : in T_PACKET_L;
TO_THE_LIST : in out T_PACKET_L) renames P_PACKET_LIST.INVERT;
–– Invert a list into another list
procedure CLEAR (THE_LIST : in out T_PACKET_L) renames P_PACKET_LIST.CLEAR;
–– Clear a list
procedure ASSIGN (THE_LIST : in out T_PACKET_L;
NEW_LIST : in T_PACKET_L) renames P_PACKET_LIST.ASSIGN;
–– Assign a list with a new value
procedure CONSTRUCT (A_PACKET : in T_PACKET_RECORD;
THE_LIST : in out T_PACKET_L) renames P_PACKET_LIST.CONSTRUCT;
–– Construct a list by adding a new item
function NULL_LIST RETURN T_PACKET_L renames P_PACKET_LIST.NULL_LIST;
–– Return a null list
function IS_NULL (THE_LIST : in T_PACKET_L) RETURN boolean
renames P_PACKET_LIST.IS_NULL;
–– Check if a list is null
function HEAD_OF (THE_LIST : in T_PACKET_L) RETURN T_PACKET_RECORD
renames P_PACKET_LIST.HEAD_OF;
–– Extract the head of a list
function TAIL_OF (THE_LIST : in T_PACKET_L) RETURN T_PACKET_L
renames P_PACKET_LIST.TAIL_OF;
–– Extract the tail of a list
function LENGTH_OF (THE_LIST : in T_PACKET_L) RETURN natural
renames P_PACKET_LIST.LENGTH_OF;
–– Get the length of a list

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
procedure COPY (FROM_THE_LIST : in T_PACKET_L;
TO_THE_LIST : in out T_PACKET_L) renames P_PACKET_LIST.COPY;
–– Copy a list into another list;
private
X_PACKET_RESULT_ALREADY_OPENED,
X_PACKET_RESULT_NOT_OPENED,
X_PACKET_RESULT_ALREADY_EXISTS,
X_INVALID_NAME,
X_INVALID_PACKET,
X_NO_PACKETS_AVAILABLE,
X_TOO_MANY_SESSIONS,
X_NO_READ_ACCESS,
X_NO_WRITE_ACCESS,
X_ERROR_CREATING_FILE,
X_ERROR_ACCESSING_FILE : exception;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
560 von/of: 662
type T_PACKET_DEFINITION is
record
EXECUTION_DATE : CGS_CALENDAR.CGS_DATE_AND_TIME;
––rhn Begin Modification for SPR 2886 07/02/97
–– RESULT_NAME : TEV_DEFINITIONS.T_RESULT_NAME;
RESULT_NAME : TEV_DEFINITIONS.T_COMPLETE_FILENAME;
––rhn End Modification for SPR 2886 07/02/97
CHARACTERISTIC : TEV_DEFINITIONS.T_PACKET_TYPE
:= TEV_DEFINITIONS.ADUS;
PATHNAME : TEV_DEFINITIONS.T_PACKET_PATHNAME;
PRODUCER : TEV_DEFINITIONS.T_PRODUCER_NAME;
FORMAT : TEV_DEFINITIONS.T_PACKET_FORMAT
:= TEV_DEFINITIONS.DEFAULT_PACKET_FORMAT;
BYTES_PER_LINE : TEV_DEFINITIONS.T_PACKET_BYTES_LINE
:= TEV_DEFINITIONS.DEFAULT_BYTES_LINE;
SUMMARY_FORMAT : BOOLEAN := FALSE;
TIME_FRAME : TEV_DEFINITIONS.T_TIME_FRAME;
SELECT_ON : DBS_DEFINITIONS.T_TIME_TYPE;
ORDER_BY : DBS_DEFINITIONS.T_TIME_ORDERING;
EXECUTION_SESSIONS : TEV_DEFINITIONS.T_DEFINITION_SESSION_NAMES(
TEV_DEFINITIONS.T_SESSIONS_RANGE);
INCLUDE_DEF_SESSION : BOOLEAN;
PACKET_NUMBER : NATURAL := natural’first;
SELECTED_ADUS : T_ADU_GDU_PATHNAME_LIST;
SELECTED_GDUS : T_ADU_GDU_PATHNAME_LIST;
ADU_SID_PATHNAME : T_SID_PATHNAME_LIST;
GDU_SID_PATHNAME : T_SID_PATHNAME_LIST;
end record;
–– package definition to access packet result file
––
package DEFINITION_IO is new DIRECT_IO(ELEMENT_TYPE => T_PACKET_DEFINITION);
–– DEFINITION_IO is used to access the packet result
–– definition as the header of the file
package PACKET_IO is new DIRECT_IO(ELEMENT_TYPE => T_PACKET_RECORD);
–– PACKET_IO is used to access the packet records inside the file.
–– The first data to access is located at position offset PTR_TO_FIRST_PACKET
type T_PACKET_RESULT is
record
DEFINITION_FILE_TYPE : DEFINITION_IO.FILE_TYPE;
PACKET_FILE_TYPE : PACKET_IO.FILE_TYPE;
FILENAME : TEV_DEFINITIONS.T_COMPLETE_FILENAME;
–– modified by RSE 12.06.96 for SPR_2391
–– ACCESS_STATUS : TEV_DEFINITIONS.T_ACCESS_STATUS
–– := TEV_DEFINITIONS.READ;
ACCESS_STATUS : T_PACKET_RESULT_ACCESS_STATUS := READ;
CURRENT_STATUS : TEV_DEFINITIONS.T_CURRENT_STATUS
:= TEV_DEFINITIONS.CLOSED;
PACKET_RESULT_DEFINITION : T_PACKET_DEFINITION;
end record;
end ADT_PACKET_RESULT;

Space Infrastructure
Formal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
––
–– TDCS_DEFINITIONS
––
––****************************************************************************
––ABSTRACT––
–– This object provides common types needed by
–– tdcs objects.
––
––
––*–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––IDENTIFICATION––
–– PROJECT NAME : CGS
–– PRODUCT NAME : TEV
–– CI–NUMBER : 1216 858
–– OBJECT NAME : TEV_DEFINITIONS
––*–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––CONTENTS––
–– COMPILER : VERDIX ADA 6.0.3.C
–– LANGUAGE : ADA
–– SPECIAL CONTENTS:
–– CHANGE HISTORY
–– V4.1 at Spacebel Informatique, Brussels
–– creator: rowena (on host moon)
–– creation date: 23.08.95 10:18:53
–– added Standard Header by command include_header
––
–– END HISTORY
––****************************************************************************
––
package TDCS_DEFINITIONS is
subtype T_TEV_TOOL_ID is NATURAL;
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Return status type
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
type T_TDCS_ERROR is (
OK,
––The operation has been successfully performed
BAD_TDCS_SELECTION_CRITERIA,
––This selection criteria cannot be fulfilled by TDCS
DATA_ONLINE_IN_30_MIN,
––The requested data is not online
––Please come back and ask again after in 30 minutes
DATA_ONLINE_IN_24_HOURS,
––The requested data is not online
––Please come back and ask again after in 24 hours
DATA_ONLINE_IN_72_HOURS,
––The requested data is not online
––Please come back and ask again after in 72 hours
TDCS_STOPPED,
––TDCS is not running
TDCS_CONNECT_PROBLEM,
––Connection to TDCS failed.
TDCS_DISCONNECT_PROBLEM,
––Disconnection from TDCS returns an error.
TDCS_INIT_PROBLEM,
––Initialisation of communication services failed.
TDCS_NOT_CONNECTED,
––TDCS connection not correctly established
LT_SELECT_NOT_SUPPORTED_BY_TDCS,
–– TDCS does not support selection according to LT timeframes
TDCS_COMMUNICATION_PROBLEM);
–– a problem in the TEV–TDCS communication occured
type T_DATA_CHARACTERISTIC is (
SELECTED_ADU_GDU,
––Selected ADU’s, GDU’s
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
561 von/of: 662

Space Infrastructure
ALL_ADUS,
––All ADU’s in the Archive File
ALL_GDUS,
––All GDU’s in the Archive File
ALL_ADUS_GDUS);
––All ADU’s, GDUS’s in the Archive File
end TDCS_DEFINITIONS;
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
562 von/of: 662

Space Infrastructure
Formal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
––
–– TDCS_RPI
––
––****************************************************************************
––ABSTRACT––
––
–– This package provides the operations of the TDCS – TEV Interface
––
––*–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––IDENTIFICATION––
–– PROJECT NAME : CGS
–– PRODUCT NAME : TEV
–– CI–NUMBER : 1216 858
–– OBJECT NAME : TDCS_RPI
––*–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––CONTENTS––
–– COMPILER : VERDIX ADA 6.0.3.C
–– LANGUAGE : ADA
–– SPECIAL CONTENTS:
–– CHANGE HISTORY
–– V4.1 at Spacebel Informatique, Brussels
–– creator: rowena (on host moon)
–– creation date: 23.08.95 10:24:18
–– added Standard Header by command include_header
––
–– END HISTORY
––****************************************************************************
––
with MPS_DEFINITIONS;
with MDB_SESSION;
with VICOS_DEFINITIONS;
with DBS_DEFINITIONS;
with DBS_LISTS;
with TDCS_DEFINITIONS;
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
package TDCS_RPI is
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Operations to control connect/disconnect activities
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
procedure CONNECT_TDCS(
SOURCE : in VICOS_DEFINITIONS.T_APPLICATION_NAME ;
STATUS : out TDCS_DEFINITIONS.T_TDCS_ERROR);
–– DESCRIPTION
–– This operation allows the evaluation user to connect to the TRDB database
–– for evaluation purposes.
–– SOURCE : Reference of the User Application Name.
–– RETURN_STATES
–– OK
–– TDCS_STOPPED
–– TDCS_CONNECT_PROBLEM
–– TDCS_INIT_PROBLEM
procedure DISCONNECT_TDCS (
STATUS : out TDCS_DEFINITIONS.T_TDCS_ERROR);
–– DESCRIPTION
–– This operation allows TEV user to disconnect from TDCS.
–– His selected sessions are automatically deallocated.
–– RETURN_STATES
–– OK
–– TDCS_NOT_CONNECTED
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
563 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
564 von/of: 662
–– TDCS_STOPPED
–– TDCS_DISCONNECT_PROBLEM
–– TDCS_COMMUNICATION_PROBLEM
procedure ALLOCATE_EXECUTION_SESSIONS (
ALLOCATED_SESSIONS : in DBS_DEFINITIONS.T_SELECTED_SESSIONS;
STATUS : out TDCS_DEFINITIONS.T_TDCS_ERROR) ;
–– DESCRIPTION
–– This operation allows the user to allocate execution sessions for
–– evaluation purposes. TDCS only returns OK. No more data is returned to TEV.
––
––
A later allocate commnand overwrite the the current allocation table.
–– ALLOCATED_SESSIONS : the list of execution sessions to allocate.
–– RETURN_STATES
–– OK
–– TDCS_NOT_CONNECTED
–– TDCS_COMMUNICATION_PROBLEM
–– TDCS_STOPPED
subtype T_RAW_DATA_FILE_INFO_LIST is DBS_LISTS.T_RAW_DATA_FILE_INFO_LIST;
procedure GET_FOREIGN_RAW_DATA_FILE_INFO_LIST_BY_ADU_GDU (
TEV_TOOL_ID : in TDCS_DEFINITIONS.T_TEV_TOOL_ID;
SESSION_NAMES : in DBS_DEFINITIONS.T_SELECTED_SESSIONS;
TIME_SELECTION : in DBS_DEFINITIONS.T_TIME_RECORD;
TIME_FRAME_TYPE : in DBS_DEFINITIONS.T_TIME_TYPE;
LIST_ORDER : in DBS_DEFINITIONS.T_TIME_ORDERING;
PRODUCER : in VICOS_DEFINITIONS.T_APPLICATION_NAME;
ADU_GDU_LIST : in MPS_DEFINITIONS.T_SID_ARRAY;
FILE_LIST : in out T_RAW_DATA_FILE_INFO_LIST;
DATA_CHARACTERISTIC : in TDCS_DEFINITIONS.T_DATA_CHARACTERISTIC;
STATUS : out TDCS_DEFINITIONS.T_TDCS_ERROR);
–– DESCRIPTION
–– This operation returns the raw data files list (Archive Files) matching
–– a selection criteria. TDCS parses a list of ADUs to obtain the session
–– name to which it applies.This supports the TEV Raw Data Dump Tool.
––
–– TEV_TOOL_ID : Identifier of the TEV user tool
–– SESSION_NAMES : Names of the test execution sessions to which
–– raw data files are related.
–– TIME_SELECTION : The selected time frame.
–– A null value is accepted.
–– TIME_FRAME_TYPE : The time type applied to the time frame (LT/SMT)
–– LIST_ORDER : The time type applied for the list ordering (LT/SMT)
–– PRODUCER : Producer Name, a null value is accepted.
–– ADU_GDU_LIST : List of ADUs, GDU’s, as additional selection criteria for raw data
–– when DATA_CHARACTERISTICS is SELECTED_ADU_GDU
–– DATA_CHARACTERISTIC : This defines the type of data to be retrieved :
–– Selected ADU’s, GDU’s
–– All ADU’s in Archive File
–– All GDU’s in Archive File
–– All ADU’s, GDU’s in Archive File
–– FILE_LIST : The selected raw data files.
–– List of Files must be in Chronological Order
––
–– RETURN_STATES
Data in each File must be in Chronological Order
–– OK
–– BAD_TDCS_SELECTION_CRITERIA
–– DATA_ONLINE_IN_30_MIN
–– DATA_ONLINE_IN_24_HOURS
–– DATA_ONLINE_IN_72_HOURS
–– TDCS_NOT_CONNECTED
–– TDCS_STOPPED
–– LT_SELECT_NOT_SUPPORTED_BY_TDCS
–– TDCS_COMMUNICATION_PROBLEM
procedure GET_FOREIGN_RAW_DATA_FILE_INFO_LIST_BY_MEASUREMENT (
TEV_TOOL_ID : in TDCS_DEFINITIONS.T_TEV_TOOL_ID;
SESSION_NAMES : in DBS_DEFINITIONS.T_SELECTED_SESSIONS;
TIME_SELECTION : in DBS_DEFINITIONS.T_TIME_RECORD;
TIME_FRAME_TYPE : in DBS_DEFINITIONS.T_TIME_TYPE;

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
565 von/of: 662
LIST_ORDER : in DBS_DEFINITIONS.T_TIME_ORDERING;
PRODUCER : in VICOS_DEFINITIONS.T_APPLICATION_NAME;
MEASUREMENT_LIST : in MPS_DEFINITIONS.T_SID_ARRAY;
FILE_LIST : in out T_RAW_DATA_FILE_INFO_LIST;
STATUS : out TDCS_DEFINITIONS.T_TDCS_ERROR);
–– DESCRIPTION
–– This operation returns the raw data files list (Archive Files) matching
–– a selection criteria. TDCS parses a list of measurements to obtain the
–– session name to which it applies.
–– Internally TDCS maps the measurements to the ADUs in which they are
–– contained and creates the required ADU list. This supports the TEV
–– Data Set Tool.
–– TEV_TOOL_ID : Identifier of the TEV user tool
–– SESSION_NAMES : Names of the test execution sessions to which
–– raw data files are related.
–– TIME_SELECTION : The selected time frame.
–– A null value is accepted.
–– PRODUCER : Producer Name, a null value is accepted.
–– TIME_FRAME_TYPE : The time type applied to the time frame (LT/SMT)
–– LIST_ORDER : The time type applied for the list ordering (LT/SMT)
–– MEASUREMENT_LIST : List of parameters as additional selection criteria
–– for raw data
–– FILE_LIST : The selected raw data files.
–– RETURN_STATES
–– OK
–– BAD_TDCS_SELECTION_CRITERIA
–– DATA_ONLINE_IN_30_MIN
–– DATA_ONLINE_IN_24_HOURS
–– DATA_ONLINE_IN_72_HOURS
–– TDCS_NOT_CONNECTED
–– TDCS_STOPPED
–– LT_SELECT_NOT_SUPPORTED_BY_TDCS
–– TDCS_COMMUNICATION_PROBLEM
procedure GET_FOREIGN_DATA_SET(
TEV_TOOL_ID : in TDCS_DEFINITIONS.T_TEV_TOOL_ID;
SESSION_NAMES : in DBS_DEFINITIONS.T_SELECTED_SESSIONS;
TIME_SELECTION : in DBS_DEFINITIONS.T_TIME_RECORD;
TIME_FRAME_TYPE : in DBS_DEFINITIONS.T_TIME_TYPE;
LIST_ORDER : in DBS_DEFINITIONS.T_TIME_ORDERING;
PRODUCER : in VICOS_DEFINITIONS.T_APPLICATION_NAME;
MEASUREMENT_LIST : in MPS_DEFINITIONS.T_SID_ARRAY;
CCU_SPECIFICATION : in MDB_SESSION.T_CCU_VERSION_IDENTIFICATION;
FILE : in out DBS_DEFINITIONS.T_FILENAME;
STATUS : out TDCS_DEFINITIONS.T_TDCS_ERROR);
–– This operation returns a Data Set generated externally matching
–– a selection criteria. TDCS processes this command exactly the same way
–– as GET_FOREIGN_RAW_DATA_FILE_INFO_LIST_BY_MEASUREMENT, excepts that it
–– passes the input data to the Data Set Formating Tool instead of the
–– Archive File Formating Tool.
–– This supports the TEV Data Set Generation Tool.
––
–– TEV_TOOL_ID : Identifier of the TEV user tool
–– SESSION_NAMES : Names of the test execution sessions to which
–– raw data files are related.
–– TIME_SELECTION : The selected time frame.
–– A null value is accepted.
–– TIME_FRAME_TYPE : The time type applied to the time frame (LT/SMT)
–– LIST_ORDER : The time type applied for the list ordering (LT/SMT)
–– PRODUCER : Producer Name, a null value is accepted.
–– MEASUREMENT_LIST : List of parameters as additional selection criteria
–– for raw data
–– CCU_SPECIFICATION : Defines the CCU to be used for calibration
–– FILE : Unix pathname for the generated Data Set.
–– RETURN_STATES
–– OK
–– BAD_TDCS_SELECTION_CRITERIA
–– DATA_ONLINE_IN_30_MIN
–– DATA_ONLINE_IN_24_HOURS
–– DATA_ONLINE_IN_72_HOURS

Space Infrastructure
–– TDCS_NOT_CONNECTED
–– TDCS_STOPPED
–– LT_SELECT_NOT_SUPPORTED_BY_TDCS
–– TDCS_COMMUNICATION_PROBLEM
end TDCS_RPI;
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
566 von/of: 662

Space Infrastructure
7.15 Test Evaluation Invocation Interface
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
567 von/of: 662
For the integration of TEV into CGS, TEV provides interface functions for the invocation of the product. Since
TEV can run interactively or in batch mode, the command line takes two alternatives.
7.15.1 TEV Invocation for Interactive Mode
If called without any parameter, TEV will run interactively and then the program expects all inputs via the
graphical user interface.
In this case TEV will be started as following:
$TEV_HOME/bin/common/start_tev
7.15.2 TEV Batch Mode
Using the TEV Command Line Interface (TEV CLI), TEV will run in batch mode and will not show up
with a graphical user interface.Thus, the command line for invoking TEV takes the following form:
$TEV_HOME/bin/common/start_tev –to \
–se \
–de \
–re
where the command parameters have the following meaning:
is the name of the tool to be executed. It can be one of the following:
LOG_EVENT: Execute the Logging Event evaluation tool
RAW_DATA: Execute the Raw Data Dump tool
DATA_SET: Execute the Data Set Generation tool
includes the sessions to be evaluated and the CCU information.
The Format of this ASCII–file is shown below. The session_file is read from the user’s working
directory $VICOS_TEV_WD/SESSIONS.
includes all tool–specific information to execute the tool.
It is to be generated either with interactive TEV or by using the appropriate procedures from
the TEV_API in Ada program. The definition_file is in binary format. It will be read from the
user’s working directory $VICOS_TEV_WD/DEFINTIONS/.
is the output of the tool.
The result_file will be put into the user’s working directory
$VICOS_TEV_WD/RESULTS/.
For logging error messages of the TEV batch mode operation there are 3 different possibilities:
1) No additional parameter given: TEV sends the error messages to the CGSI error window and to
stdout (which is the shell tool from where TEV was started).
2) The command line can be extended for output redirection with standard Unix features like
$TEV_HOME/bin/common/start_tev –to LOG_ENVET ... >logfile. In this case the output is written
to the logfile only.

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
568 von/of: 662
3) The output can be duplicated using the tee standard Unix duplicator like $TEV_HOME/bin/common/start_tev
–to LOG_EVENT ... |&tee logfile. In this case the output of error messages would also
be sent to stdout.
Session File Format:
The format for the session_file will be as follows:
SESSION:
.
.
SESSION:
DEFAULT_TEST_SESSION
CCU:
Up to 10 sessions other than the DEFAULT_TEST_SESSION can be selected.
The selection of the DEFAULT_TEST_SESSION is optional. If it is added to the selection, a total selection of
11 sessions (including the DEFAULT_TEST_SESSION) is possible.
The last record in the file must be the CCU information, which gives the CCU_PATHNAME that shall be used
for the evaluation.
The command will return after checking the parameters or after the evaluation is finished (which may take from
some minutes to some hours) with the following return codes:
–1 success
–101 invalid tool type
–102 invalid session file
–103 invalid definition file
–104 duplicate result file
–105 invalid session name
–106 invalid CCU
–107 error accessing TRDB
–108 error accessing MDB
7.15.3 TEV in Office Mode
TEV may be started in the Office Mode. In this case, It runs in a standalone configuration with TEV and DBS
only.
In the default mode (EGSE mode), DBS is started by the overall CGS startup script for a given EGSE configuration.
In Office mode, however,TEV is responsible for starting and stopping Central DBS (i.e. invoking the DBS startup
script at the beginnin and stopping the DBS processes, when the last TEV process disconnects). The Office
mode is indicated in the TEV startup command by the option ”–o”.
The following gives an example for this:
$TEV_HOME/bin/common/start_tev –o
The option does not require any further parameters.

Space Infrastructure
7.16 EXCEL Representation Format
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
569 von/of: 662
The detailed description of this format is defined in the commercial MICROSOFT EXCEL documentation.

Space Infrastructure
7.17 Command and Measurement Adaptation System
Informal Interface Description
CMAS Invocation
CMAS is started by the CSS kernel using the following command:
$CMAS_HOME/bin/common/start_cmas
with the following parameters:
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
: the value of this parameter is always ”local”
: this parameter denotes the UNIX pathname of the configuration file
containing the information about the CSS model external I/O’s,
e.g. calibration information.
: identifier of the shared memory region between CSS and CMAS
containing the values of the external I/O’s of a CSS model
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
570 von/of: 662
: identifier of the shared memory region between CSS and CMAS
containing commands and static information for communication
purposes
: denotes the name of the machine where the CSS kernel has been started.
Invocation of the CMAS Database Server
The CMAS DataBase Server is called by the CSS DB Server in case a milbus configuration file has
to be generated. The milbus configuration file contains the information about the external I/O’s of a
CSS model, e.g. CCSDS packet information, calibration/decalibration parameters. The CSS DB
Server tries to start the CMAS DB Server via the following command:
$CMAS_HOME/bin/common/start_db_server
where the parameters have the following meaning:
: This file contains the necessary information to access the database for the
currently edited model. The contents is stored in binary form and can be
retrieved by the CMAS DB Server via the procedure GET_FROM_FILE
provided by the ADA package CSS_MESSAGE_CONNECTION
(see specification).
: This ASCII file can be used by the CMAS DB Server to store any
messages produced during the generation phase of the milbus
configuration file, i.e. error messages, warning messages. The file is
displayed by the CSS MDE afterwards.
In case the start_db_server command cannot be found, the CSS DB Server will generate the milbus
configuration file. This will be done in order to keep the DB Server compatible to CMAS installations
other than SSA.

Space Infrastructure
Informal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
571 von/of: 662
The interface between CSS and the Command and Measurement Adaptation System (CMAS) is constituted by
a procedural interface and a representation interface.
The representation interface is formed by an ASCII – file generated by the DB_SERVER being a component
of CSS. The name of the ASCII – file is ’external_model_configuration’. This file contains the following information:
• 1. logical Milbus structures like:
– Bus Identification in case of multiple Milbusses,
– Remote Terminal Identification for a specific Milbus,
– Subaddress/Slot Identification for a specific Remote Terminal,
– Channel Identification (as offset) for a specific Subaddress/Slot,
– Mapping from Channel to CSS–Runtime–Identifier(RID),
– Sizing–Information:
– Number of all implemented Milbusses
– Number of all implemented Remote Terminals for a specific Milbus
– Number of all implemented Channels for a specific Remote Terminal
– Bit–Offset for all boolean values
• 2. Calibration/Decalibration:
– Identification of the RID’s to be calibrated
– Identification of the RID’s to be decalibrated
– Identification of the specific calibration/decalibration method per RID
• 3. Serial Packets:
– Mapping Serial Packets to Subaddresses
– Internal structure of a Serial Packet(length, offsets)
– Mapping internal packet items to RIDs
– Send–Interval of Serial Packets to be sent to LAN
• 4. External Model I/O:
– First External Input
– Last External Input
– First External Output
– Last External Output
– Number of all external Inputs
– Number of all external Outputs
– Physical size(for channel representation) in Bits for each I/O–Item(RID)
The CMAS receives the necessary information in order to interface with CSS in the following order:
• 1. the CSS simulator is started
• 2. CSS initializes the shared memory region
• 3. CMAS is started

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
• 4. CMAS loads external_model_configuration file
• 5. CMAS attaches to shared memory (ready to operate on dynamic region)
Formal Interface Description
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
572 von/of: 662

Space Infrastructure
Formal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– ABSTRACT –– CSS_TYPES
–– Provides the set of types defined for CSS MDE model variables.
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– KEYWORDS –– CSS_TYPES
–– Project CSS–Downsizing
––
–– HOOD object CSS_TYPES
–– MDE model variable types
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– CONTENTS –– CSS_TYPES
––
–– Type: Package Spec (+ implicit body)
––
–– Version:
–– 2.1, 10.11.93, J.Hoyng: initial version
–– 3.1, 21.07.94, J.Hoyng: the TIME type depends now on SMT_CALENDAR.TIME
–– deleted type declaration DURATION
–– 3.2, 06.04.95, J.Hoyng: implemented new types
–– 4.1, 23.08.95, J.Hoyng: build_2 version
–– 4.2, R. Lamb: added STRING_ACCESS_TYPE.
–– 5.1, 26.08.97, Th. Behrens: Replaced DB_DEFINITIONS by MPS_DEFINITIONS.
–– 5.2, 12.12.97, W. Tammen: merged DMS–R prototype with CGS V4.1.1
––
–– Purpose:
–– Provide CSS defined typeset
––
–– External:
–– From Ada system:
–– CALENDAR
––
–– From CGS:
–– MPS_DEFINITIONS
–– NUMERIC_TYPES
––
–– From CSS:
–– DB_DEFINITIONS
–– SMT_CALENDAR
––
–– Machine Dependencies:
–– none
––
–– Compiler Dependencies:
–– none
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
£
–– imports from Ada system:
with CALENDAR;
with UNCHECKED_DEALLOCATION;
–– imports from CGS:
with MPS_DEFINITIONS;
with NUMERIC_TYPES;
–– imports from CSS:
with SMT_CALENDAR;
package CSS_TYPES is
type CSS_SW_TYPES is (
NONE,
UNSIGNED_BYTE_TYPE,
SIGNED_BYTE_TYPE,
UNSIGNED_SHORT_WORD_TYPE,
SIGNED_SHORT_WORD_TYPE,
UNSIGNED_INTEGER_TYPE,
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
573 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
SIGNED_INTEGER_TYPE,
REAL_TYPE,
LONG_REAL_TYPE,
COMPLEX_TYPE,
BOOLEAN_TYPE,
TIME_TYPE,
LONG_DURATION_TYPE,
STATE_CODE_TYPE,
PULSE_TYPE,
BURST_PULSE_TYPE,
UNSIGNED_BYTE_VECTOR_TYPE,
SIGNED_BYTE_VECTOR_TYPE,
UNSIGNED_SHORT_WORD_VECTOR_TYPE,
SIGNED_SHORT_WORD_VECTOR_TYPE,
UNSIGNED_INTEGER_VECTOR_TYPE,
SIGNED_INTEGER_VECTOR_TYPE,
REAL_VECTOR_TYPE,
LONG_REAL_VECTOR_TYPE,
COMPLEX_VECTOR_TYPE,
BOOLEAN_VECTOR_TYPE,
UNSIGNED_BYTE_MATRIX_TYPE,
SIGNED_BYTE_MATRIX_TYPE,
UNSIGNED_SHORT_WORD_MATRIX_TYPE,
SIGNED_SHORT_WORD_MATRIX_TYPE,
UNSIGNED_INTEGER_MATRIX_TYPE,
SIGNED_INTEGER_MATRIX_TYPE,
REAL_MATRIX_TYPE,
LONG_REAL_MATRIX_TYPE,
COMPLEX_MATRIX_TYPE,
BOOLEAN_MATRIX_TYPE,
BYTE_STREAM_TYPE,
STRING_ACCESS_TYPE,
LAST_TYPE);
–– all CSS_SW_TYPES used during runtime
subtype CSS_RUNTIME_SW_TYPES is CSS_SW_TYPES range
CSS_SW_TYPES’SUCC(NONE) .. CSS_SW_TYPES’PRED (LAST_TYPE);
type UNSIGNED_INTEGER is new NUMERIC_TYPES.UNSIGNED_INTEGER32
range 0 .. NUMERIC_TYPES.UNSIGNED_INTEGER32’LAST;
––––––––––––––––––––––––––––––
–– SIGNED_BYTE
––––––––––––––––––––––––––––––
type SIGNED_BYTE is new NUMERIC_TYPES.INTEGER8;
SIGNED_BYTE_INITIAL_VALUE : constant SIGNED_BYTE := 0;
type SIGNED_BYTE_VECTOR is
array (UNSIGNED_INTEGER range ) of SIGNED_BYTE;
type SIGNED_BYTE_VECTOR_ACCESS is access SIGNED_BYTE_VECTOR;
type SIGNED_BYTE_MATRIX is
array (UNSIGNED_INTEGER range ,
UNSIGNED_INTEGER range ) of SIGNED_BYTE;
type SIGNED_BYTE_MATRIX_ACCESS is access SIGNED_BYTE_MATRIX;
––––––––––––––––––––––––––––––
–– UNSIGNED_BYTE
––––––––––––––––––––––––––––––
type UNSIGNED_BYTE is new NUMERIC_TYPES.BYTE;
UNSIGNED_BYTE_INITIAL_VALUE : constant UNSIGNED_BYTE := 0;
type UNSIGNED_BYTE_VECTOR is array (UNSIGNED_INTEGER range ) of UNSIGNED_BYTE;
type UNSIGNED_BYTE_VECTOR_ACCESS is access UNSIGNED_BYTE_VECTOR;
type UNSIGNED_BYTE_MATRIX is
array (UNSIGNED_INTEGER range ,
UNSIGNED_INTEGER range ) of UNSIGNED_BYTE;
type UNSIGNED_BYTE_MATRIX_ACCESS is access UNSIGNED_BYTE_MATRIX;
––––––––––––––––––––––––––––––
–– UNSIGNED_SHORT_WORD
––––––––––––––––––––––––––––––
type UNSIGNED_SHORT_WORD is new NUMERIC_TYPES.UNSIGNED_INTEGER16;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
574 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
UNSIGNED_SHORT_WORD_INITIAL_VALUE : constant UNSIGNED_SHORT_WORD := 0;
type UNSIGNED_SHORT_WORD_VECTOR is
array (UNSIGNED_INTEGER range ) of UNSIGNED_SHORT_WORD;
type UNSIGNED_SHORT_WORD_VECTOR_ACCESS is access UNSIGNED_SHORT_WORD_VECTOR;
type UNSIGNED_SHORT_WORD_MATRIX is
array (UNSIGNED_INTEGER range ,
UNSIGNED_INTEGER range ) of UNSIGNED_SHORT_WORD;
type UNSIGNED_SHORT_WORD_MATRIX_ACCESS is access UNSIGNED_SHORT_WORD_MATRIX;
––––––––––––––––––––––––––––––
–– SIGNED_SHORT_WORD
––––––––––––––––––––––––––––––
type SIGNED_SHORT_WORD is new NUMERIC_TYPES.INTEGER16;
SIGNED_SHORT_WORD_INITIAL_VALUE : constant SIGNED_SHORT_WORD := 0;
type SIGNED_SHORT_WORD_VECTOR is
array (UNSIGNED_INTEGER range ) of SIGNED_SHORT_WORD;
type SIGNED_SHORT_WORD_VECTOR_ACCESS is access SIGNED_SHORT_WORD_VECTOR;
type SIGNED_SHORT_WORD_MATRIX is
array (UNSIGNED_INTEGER range ,
UNSIGNED_INTEGER range ) of SIGNED_SHORT_WORD;
type SIGNED_SHORT_WORD_MATRIX_ACCESS is access SIGNED_SHORT_WORD_MATRIX;
––––––––––––––––––––––––––––––
–– SIGNED_INTEGER
––––––––––––––––––––––––––––––
type SIGNED_INTEGER is new NUMERIC_TYPES.INTEGER32;
SIGNED_INTEGER_INITIAL_VALUE : constant SIGNED_INTEGER := 0;
type SIGNED_INTEGER_VECTOR is
array (UNSIGNED_INTEGER range ) of SIGNED_INTEGER;
type SIGNED_INTEGER_VECTOR_ACCESS is access SIGNED_INTEGER_VECTOR;
type SIGNED_INTEGER_MATRIX is
array (UNSIGNED_INTEGER range ,
UNSIGNED_INTEGER range ) of SIGNED_INTEGER;
type SIGNED_INTEGER_MATRIX_ACCESS is access SIGNED_INTEGER_MATRIX;
––––––––––––––––––––––––––––––
–– UNSIGNED_INTEGER
––––––––––––––––––––––––––––––
UNSIGNED_INTEGER_INITIAL_VALUE : constant UNSIGNED_INTEGER := 0;
type UNSIGNED_INTEGER_VECTOR is
array (UNSIGNED_INTEGER range ) of UNSIGNED_INTEGER;
type UNSIGNED_INTEGER_VECTOR_ACCESS is access UNSIGNED_INTEGER_VECTOR;
type UNSIGNED_INTEGER_MATRIX is
array (UNSIGNED_INTEGER range ,
UNSIGNED_INTEGER range ) of UNSIGNED_INTEGER;
type UNSIGNED_INTEGER_MATRIX_ACCESS is access UNSIGNED_INTEGER_MATRIX;
––––––––––––––––––––––––––––––
–– REAL
––––––––––––––––––––––––––––––
type REAL is new NUMERIC_TYPES.SINGLE_FLOAT;
REAL_INITIAL_VALUE : constant REAL := 0.0;
type REAL_VECTOR is
array (UNSIGNED_INTEGER range ) of REAL;
type REAL_VECTOR_ACCESS is access REAL_VECTOR;
type REAL_MATRIX is
array (UNSIGNED_INTEGER range ,
UNSIGNED_INTEGER range ) of REAL;
type REAL_MATRIX_ACCESS is access REAL_MATRIX;
––––––––––––––––––––––––––––––
–– LONG_REAL
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
575 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
––––––––––––––––––––––––––––––
type LONG_REAL is new NUMERIC_TYPES.DOUBLE_FLOAT;
LONG_REAL_INITIAL_VALUE : constant LONG_REAL := 0.0;
type LONG_REAL_VECTOR is
array (UNSIGNED_INTEGER range ) of LONG_REAL;
type LONG_REAL_VECTOR_ACCESS is access LONG_REAL_VECTOR;
type LONG_REAL_MATRIX is
array (UNSIGNED_INTEGER range ,
UNSIGNED_INTEGER range ) of LONG_REAL;
type LONG_REAL_MATRIX_ACCESS is access LONG_REAL_MATRIX;
––––––––––––––––––––––––––––––
–– COMPLEX
––––––––––––––––––––––––––––––
type COMPLEX is
record
RE, IM : LONG_REAL;
end record;
COMPLEX_INITIAL_VALUE : constant COMPLEX := (0.0, 0.0);
type COMPLEX_VECTOR is
array (UNSIGNED_INTEGER range ) of COMPLEX;
type COMPLEX_VECTOR_ACCESS is access COMPLEX_VECTOR;
type COMPLEX_MATRIX is
array (UNSIGNED_INTEGER range ,
UNSIGNED_INTEGER range ) of COMPLEX;
type COMPLEX_MATRIX_ACCESS is access COMPLEX_MATRIX;
––––––––––––––––––––––––––––––
–– BOOLEAN
––––––––––––––––––––––––––––––
BOOLEAN_INITIAL_VALUE : constant BOOLEAN := TRUE;
type BOOLEAN_VECTOR is
array (UNSIGNED_INTEGER range ) of BOOLEAN;
type BOOLEAN_VECTOR_ACCESS is access BOOLEAN_VECTOR;
type BOOLEAN_MATRIX is
array (UNSIGNED_INTEGER range ,
UNSIGNED_INTEGER range ) of BOOLEAN;
type BOOLEAN_MATRIX_ACCESS is access BOOLEAN_MATRIX;
––––––––––––––––––––––––––––––
–– LONG_DURATION
––––––––––––––––––––––––––––––
subtype LONG_DURATION is SMT_CALENDAR.LONG_DURATION;
function ”+”(RIGHT: LONG_DURATION) return LONG_DURATION
renames SMT_CALENDAR.”+”;
function ”–”(RIGHT: LONG_DURATION) return LONG_DURATION
renames SMT_CALENDAR.”–”;
function ”abs”(RIGHT: LONG_DURATION) return LONG_DURATION
renames SMT_CALENDAR.”abs”;
function ”+”(LEFT: LONG_DURATION; RIGHT: LONG_DURATION) return LONG_DURATION
renames SMT_CALENDAR.”+”;
function ”–”(LEFT: LONG_DURATION; RIGHT: LONG_DURATION) return LONG_DURATION
renames SMT_CALENDAR.”–”;
function ”*”(LEFT: LONG_DURATION; RIGHT: INTEGER) return LONG_DURATION
renames SMT_CALENDAR.”*”;
–– function ”*”(LEFT: INTEGER; RIGHT: LONG_DURATION) return LONG_DURATION
–– renames SMT_CALENDAR.MUL;
function ”/”(LEFT: LONG_DURATION; RIGHT: INTEGER) return LONG_DURATION
renames SMT_CALENDAR.”/”;
function ”=”(LEFT: LONG_DURATION; RIGHT: LONG_DURATION) return BOOLEAN
renames SMT_CALENDAR.”=”;
function ”

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
renames SMT_CALENDAR.””(LEFT: LONG_DURATION; RIGHT: LONG_DURATION) return BOOLEAN
renames SMT_CALENDAR.”>”;
function ”>=”(LEFT: LONG_DURATION; RIGHT: LONG_DURATION) return BOOLEAN
renames SMT_CALENDAR.”>=”;
LONG_DURATION_INITIAL_VALUE : constant LONG_DURATION := 0.0;
––––––––––––––––––––––––––––––
–– TIME
––––––––––––––––––––––––––––––
subtype TIME is SMT_CALENDAR.TIME;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
577 von/of: 662
subtype YEAR_NUMBER is INTEGER range 1901 .. 2099;
subtype MONTH_NUMBER is INTEGER range 1 .. 12;
subtype DAY_NUMBER is INTEGER range 1 .. 31;
subtype DAY_DURATION is LONG_DURATION range 0.0 .. 86_400.0;
function CLOCK return TIME renames SMT_CALENDAR.CLOCK;
function YEAR (DATE: TIME) return YEAR_NUMBER renames SMT_CALENDAR.YEAR;
function MONTH (DATE: TIME) return MONTH_NUMBER renames SMT_CALENDAR.MONTH;
function DAY (DATE: TIME) return DAY_NUMBER renames SMT_CALENDAR.DAY;
function SECONDS(DATE: TIME) return DAY_DURATION renames SMT_CALENDAR.SECONDS;
procedure SPLIT (DATE : in TIME;
YEAR : out YEAR_NUMBER;
MONTH : out MONTH_NUMBER;
DAY : out DAY_NUMBER;
SECONDS: out DAY_DURATION) renames SMT_CALENDAR.SPLIT;
function TIME_OF(YEAR : YEAR_NUMBER;
MONTH : MONTH_NUMBER;
DAY : DAY_NUMBER;
SECONDS: DAY_DURATION := 0.0) return TIME
renames SMT_CALENDAR.TIME_OF;
function ”+” (LEFT: TIME; RIGHT: LONG_DURATION) return TIME
renames SMT_CALENDAR.”+”;
function ”+” (LEFT: LONG_DURATION; RIGHT: TIME) return TIME
renames SMT_CALENDAR.”+”;
function ”–” (LEFT: TIME; RIGHT: LONG_DURATION) return TIME
renames SMT_CALENDAR.”–”;
function ”–” (LEFT: TIME; RIGHT: TIME) return LONG_DURATION
renames SMT_CALENDAR.”–”;
function ”=” (LEFT, RIGHT: TIME) return BOOLEAN
renames SMT_CALENDAR.”=”;
function ”=”;
function GET_MINFRAME_INTERVAL return LONG_DURATION
renames SMT_CALENDAR.GET_MINFRAME_INTERVAL;
TIME_INITIAL_VALUE : constant TIME := TIME_OF (1994, 1, 1, 0.0); –– 1.1.1994 why not
––––––––––––––––––––––––––––––
–– STATE_CODE
––––––––––––––––––––––––––––––
type STATE_CODE is new MPS_DEFINITIONS.STATE_CODE;
STATE_CODE_INITIAL_VALUE : constant STATE_CODE := (others => ’ ’);
––––––––––––––––––––––––––––––
–– PULSE
––––––––––––––––––––––––––––––
type PULSE is new BOOLEAN;
PULSE_INITIAL_VALUE : constant PULSE := TRUE;
PULSE_NOT_TRIGGERED : constant PULSE := FALSE;
PULSE_TRIGGERED : constant PULSE := TRUE;
––––––––––––––––––––––––––––––
–– BURST_PULSE
––––––––––––––––––––––––––––––

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
type BURST_PULSE is new NUMERIC_TYPES.UNSIGNED_INTEGER32;
BURST_PULSE_INITIAL_VALUE : constant BURST_PULSE := 0;
BURST_PULSE_NOT_TRIGGERED : constant BURST_PULSE := 0;
––––––––––––––––––––––––––––––
–– BYTE_STREAM
––––––––––––––––––––––––––––––
type BYTE_STREAM (MAX_LENGTH : UNSIGNED_INTEGER) is
record
ACTUAL : UNSIGNED_INTEGER;
ELEMENTS: UNSIGNED_BYTE_VECTOR (1 .. MAX_LENGTH);
end record;
type BYTE_STREAM_ACCESS is access BYTE_STREAM;
–– several functions concerning BYTE_STREAM
BYTE_STREAM_INITIAL_VALUE : constant BYTE_STREAM_ACCESS := null;
–– W.Tammen: changes made for DMS–R prototype merge with CGS V4.1.1
––
–– string_access_type has to be declared redundantly here in order to
–– avoid circular compilation dependencies: css_types uses db_definitions
–– and vice versa !!
–– BOB: One day someone will have to rationalise strings.
type STRING_ACCESS is access STRING;
STRING_ACCESS_INITIAL_VALUE: constant STRING_ACCESS := null;
procedure FREE is new UNCHECKED_DEALLOCATION (STRING, STRING_ACCESS);
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
578 von/of: 662
type IO_VALUE_TYPE (SW_TYPE : CSS_SW_TYPES := NONE) is
record
case SW_TYPE is
when NONE => null;
when UNSIGNED_BYTE_TYPE =>
UNSIGNED_BYTE_VALUE: UNSIGNED_BYTE := UNSIGNED_BYTE_INITIAL_VALUE;
when SIGNED_BYTE_TYPE =>
SIGNED_BYTE_VALUE: SIGNED_BYTE := SIGNED_BYTE_INITIAL_VALUE;
when UNSIGNED_SHORT_WORD_TYPE => UNSIGNED_SHORT_WORD_VALUE:
UNSIGNED_SHORT_WORD := UNSIGNED_SHORT_WORD_INITIAL_VALUE;
when SIGNED_SHORT_WORD_TYPE => SIGNED_SHORT_WORD_VALUE:
SIGNED_SHORT_WORD := SIGNED_SHORT_WORD_INITIAL_VALUE;
when UNSIGNED_INTEGER_TYPE =>
UNSIGNED_INTEGER_VALUE: UNSIGNED_INTEGER := UNSIGNED_INTEGER_INITIAL_VALUE;
when SIGNED_INTEGER_TYPE =>
SIGNED_INTEGER_VALUE: SIGNED_INTEGER := SIGNED_INTEGER_INITIAL_VALUE;
when LONG_REAL_TYPE =>
LONG_REAL_VALUE: LONG_REAL := LONG_REAL_INITIAL_VALUE;
when COMPLEX_TYPE =>
COMPLEX_VALUE: COMPLEX := COMPLEX_INITIAL_VALUE;
when BOOLEAN_TYPE =>
BOOLEAN_VALUE: BOOLEAN := BOOLEAN_INITIAL_VALUE;
when TIME_TYPE =>
TIME_VALUE: TIME := TIME_INITIAL_VALUE;
when LONG_DURATION_TYPE =>
LONG_DURATION_VALUE: LONG_DURATION := LONG_DURATION_INITIAL_VALUE;
when UNSIGNED_BYTE_VECTOR_TYPE =>
UNSIGNED_BYTE_VECTOR_VALUE: UNSIGNED_BYTE_VECTOR_ACCESS := null;
when SIGNED_BYTE_VECTOR_TYPE => SIGNED_BYTE_VECTOR_VALUE:
SIGNED_BYTE_VECTOR_ACCESS := null;
when UNSIGNED_SHORT_WORD_VECTOR_TYPE => UNSIGNED_SHORT_WORD_VECTOR_VALUE:
UNSIGNED_SHORT_WORD_VECTOR_ACCESS := null;
when SIGNED_SHORT_WORD_VECTOR_TYPE => SIGNED_SHORT_WORD_VECTOR_VALUE:
SIGNED_SHORT_WORD_VECTOR_ACCESS := null;
when UNSIGNED_INTEGER_VECTOR_TYPE => UNSIGNED_INTEGER_VECTOR_VALUE:
UNSIGNED_INTEGER_VECTOR_ACCESS := null;
when SIGNED_INTEGER_VECTOR_TYPE => SIGNED_INTEGER_VECTOR_VALUE:
SIGNED_INTEGER_VECTOR_ACCESS := null;
when REAL_VECTOR_TYPE => REAL_VECTOR_VALUE : REAL_VECTOR_ACCESS := null;
when LONG_REAL_VECTOR_TYPE => LONG_REAL_VECTOR_VALUE:
LONG_REAL_VECTOR_ACCESS := null;
when COMPLEX_VECTOR_TYPE => COMPLEX_VECTOR_VALUE: COMPLEX_VECTOR_ACCESS := null;
when BOOLEAN_VECTOR_TYPE => BOOLEAN_VECTOR_VALUE: BOOLEAN_VECTOR_ACCESS := null;
when UNSIGNED_BYTE_MATRIX_TYPE =>
UNSIGNED_BYTE_MATRIX_VALUE: UNSIGNED_BYTE_MATRIX_ACCESS := null;
when SIGNED_BYTE_MATRIX_TYPE => SIGNED_BYTE_MATRIX_VALUE:

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
579 von/of: 662
SIGNED_BYTE_MATRIX_ACCESS := null;
when UNSIGNED_SHORT_WORD_MATRIX_TYPE => UNSIGNED_SHORT_WORD_MATRIX_VALUE:
UNSIGNED_SHORT_WORD_MATRIX_ACCESS := null;
when SIGNED_SHORT_WORD_MATRIX_TYPE => SIGNED_SHORT_WORD_MATRIX_VALUE:
SIGNED_SHORT_WORD_MATRIX_ACCESS := null;
when UNSIGNED_INTEGER_MATRIX_TYPE => UNSIGNED_INTEGER_MATRIX_VALUE:
UNSIGNED_INTEGER_MATRIX_ACCESS := null;
when SIGNED_INTEGER_MATRIX_TYPE => SIGNED_INTEGER_MATRIX_VALUE:
SIGNED_INTEGER_MATRIX_ACCESS := null;
when REAL_MATRIX_TYPE => REAL_MATRIX_VALUE : REAL_MATRIX_ACCESS := null;
when LONG_REAL_MATRIX_TYPE => LONG_REAL_MATRIX_VALUE:
LONG_REAL_MATRIX_ACCESS := null;
when COMPLEX_MATRIX_TYPE => COMPLEX_MATRIX_VALUE: COMPLEX_MATRIX_ACCESS := null;
when BOOLEAN_MATRIX_TYPE => BOOLEAN_MATRIX_VALUE: BOOLEAN_MATRIX_ACCESS := null;
when REAL_TYPE =>
REAL_VALUE : REAL := REAL_INITIAL_VALUE;
when STATE_CODE_TYPE =>
STATE_CODE_VALUE: STATE_CODE := STATE_CODE_INITIAL_VALUE;
when PULSE_TYPE =>
PULSE_VALUE: PULSE := PULSE_INITIAL_VALUE;
when BURST_PULSE_TYPE =>
BURST_PULSE_VALUE : BURST_PULSE := BURST_PULSE_INITIAL_VALUE;
when BYTE_STREAM_TYPE =>
BYTE_STREAM_VALUE : BYTE_STREAM_ACCESS := null;
when STRING_ACCESS_TYPE =>
STRING_VALUE : STRING_ACCESS := null;
when LAST_TYPE => null;
end case;
end record;
type IO_SCALAR_VALUE_TYPE (SW_TYPE : CSS_SW_TYPES := NONE) is
record
case SW_TYPE is
when NONE => null;
when UNSIGNED_BYTE_TYPE =>
UNSIGNED_BYTE_VALUE: UNSIGNED_BYTE := UNSIGNED_BYTE_INITIAL_VALUE;
when SIGNED_BYTE_TYPE =>
SIGNED_BYTE_VALUE: SIGNED_BYTE := SIGNED_BYTE_INITIAL_VALUE;
when UNSIGNED_SHORT_WORD_TYPE => UNSIGNED_SHORT_WORD_VALUE:
UNSIGNED_SHORT_WORD := UNSIGNED_SHORT_WORD_INITIAL_VALUE;
when SIGNED_SHORT_WORD_TYPE => SIGNED_SHORT_WORD_VALUE:
SIGNED_SHORT_WORD := SIGNED_SHORT_WORD_INITIAL_VALUE;
when UNSIGNED_INTEGER_TYPE =>
UNSIGNED_INTEGER_VALUE: UNSIGNED_INTEGER := UNSIGNED_INTEGER_INITIAL_VALUE;
when SIGNED_INTEGER_TYPE =>
SIGNED_INTEGER_VALUE: SIGNED_INTEGER := SIGNED_INTEGER_INITIAL_VALUE;
when LONG_REAL_TYPE =>
LONG_REAL_VALUE: LONG_REAL := LONG_REAL_INITIAL_VALUE;
when COMPLEX_TYPE =>
COMPLEX_VALUE: COMPLEX := COMPLEX_INITIAL_VALUE;
when BOOLEAN_TYPE =>
BOOLEAN_VALUE: BOOLEAN := BOOLEAN_INITIAL_VALUE;
when TIME_TYPE =>
TIME_VALUE: TIME := TIME_INITIAL_VALUE;
when LONG_DURATION_TYPE =>
LONG_DURATION_VALUE: LONG_DURATION := LONG_DURATION_INITIAL_VALUE;
when REAL_TYPE =>
REAL_VALUE : REAL := REAL_INITIAL_VALUE;
when STATE_CODE_TYPE =>
STATE_CODE_VALUE: STATE_CODE := STATE_CODE_INITIAL_VALUE;
when PULSE_TYPE =>
PULSE_VALUE: PULSE := PULSE_INITIAL_VALUE;
when BURST_PULSE_TYPE =>
BURST_PULSE_VALUE : BURST_PULSE := BURST_PULSE_INITIAL_VALUE;
when others => null;
end case;
end record;
type IO_COMPOSITE_VALUE_TYPE (SW_TYPE : CSS_SW_TYPES := NONE) is
record
case SW_TYPE is
when UNSIGNED_BYTE_VECTOR_TYPE =>
UNSIGNED_BYTE_VECTOR_VALUE: UNSIGNED_BYTE_VECTOR_ACCESS := null;
when SIGNED_BYTE_VECTOR_TYPE => SIGNED_BYTE_VECTOR_VALUE:

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
580 von/of: 662
SIGNED_BYTE_VECTOR_ACCESS := null;
when UNSIGNED_SHORT_WORD_VECTOR_TYPE => UNSIGNED_SHORT_WORD_VECTOR_VALUE:
UNSIGNED_SHORT_WORD_VECTOR_ACCESS := null;
when SIGNED_SHORT_WORD_VECTOR_TYPE => SIGNED_SHORT_WORD_VECTOR_VALUE:
SIGNED_SHORT_WORD_VECTOR_ACCESS := null;
when UNSIGNED_INTEGER_VECTOR_TYPE => UNSIGNED_INTEGER_VECTOR_VALUE:
UNSIGNED_INTEGER_VECTOR_ACCESS := null;
when SIGNED_INTEGER_VECTOR_TYPE => SIGNED_INTEGER_VECTOR_VALUE:
SIGNED_INTEGER_VECTOR_ACCESS := null;
when REAL_VECTOR_TYPE => REAL_VECTOR_VALUE : REAL_VECTOR_ACCESS := null;
when LONG_REAL_VECTOR_TYPE => LONG_REAL_VECTOR_VALUE:
LONG_REAL_VECTOR_ACCESS := null;
when COMPLEX_VECTOR_TYPE => COMPLEX_VECTOR_VALUE: COMPLEX_VECTOR_ACCESS := null;
when BOOLEAN_VECTOR_TYPE => BOOLEAN_VECTOR_VALUE: BOOLEAN_VECTOR_ACCESS := null;
when UNSIGNED_BYTE_MATRIX_TYPE =>
UNSIGNED_BYTE_MATRIX_VALUE: UNSIGNED_BYTE_MATRIX_ACCESS := null;
when SIGNED_BYTE_MATRIX_TYPE => SIGNED_BYTE_MATRIX_VALUE:
SIGNED_BYTE_MATRIX_ACCESS := null;
when UNSIGNED_SHORT_WORD_MATRIX_TYPE => UNSIGNED_SHORT_WORD_MATRIX_VALUE:
UNSIGNED_SHORT_WORD_MATRIX_ACCESS := null;
when SIGNED_SHORT_WORD_MATRIX_TYPE => SIGNED_SHORT_WORD_MATRIX_VALUE:
SIGNED_SHORT_WORD_MATRIX_ACCESS := null;
when UNSIGNED_INTEGER_MATRIX_TYPE => UNSIGNED_INTEGER_MATRIX_VALUE:
UNSIGNED_INTEGER_MATRIX_ACCESS := null;
when SIGNED_INTEGER_MATRIX_TYPE => SIGNED_INTEGER_MATRIX_VALUE:
SIGNED_INTEGER_MATRIX_ACCESS := null;
when REAL_MATRIX_TYPE => REAL_MATRIX_VALUE : REAL_MATRIX_ACCESS := null;
when LONG_REAL_MATRIX_TYPE => LONG_REAL_MATRIX_VALUE:
LONG_REAL_MATRIX_ACCESS := null;
when COMPLEX_MATRIX_TYPE => COMPLEX_MATRIX_VALUE: COMPLEX_MATRIX_ACCESS := null;
when BOOLEAN_MATRIX_TYPE => BOOLEAN_MATRIX_VALUE: BOOLEAN_MATRIX_ACCESS := null;
when BYTE_STREAM_TYPE =>
BYTE_STREAM_VALUE : BYTE_STREAM_ACCESS := null;
when STRING_ACCESS_TYPE =>
STRING_VALUE : STRING_ACCESS := null;
when others => null;
end case;
end record;
end CSS_TYPES;

Space Infrastructure
Formal Interface Description
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– ABSTRACT –– MODEL_CONNECTION
––
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– KEYWORDS –– MODEL_CONNECTION
–– Project CSS
–– ADD, section 5.2
–– HOOD object MODEL_CONNECTION
––
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– CONTENTS –– MODEL_CONNECTION
––
–– Type: Package Spec
––
–– Version:
–– 2.1, 10.11.93, : initial_version
–– 3.1, 21.07.94, J.Hoyng: build_0 version
–– 4.1, 23.08.95, N.Heyder: SW_VALUE_TYPE (record!), Byte_Stream_Value,
–– Unix–Shared_Memory, fork CMAS–Process
–– 4.2, 01.12.95, N.Heyder: added error report–list from CMAS
–– 5.1, 20.02.97, W.Tammen: merge with DMS–R Prototype
–– 5.2, 17.07.97, W.Tammen: introduced new error numbers due to IRN 7015
–– (modification in TSS initialization)
–– 5.3, 18.08.97, W.Tammen: modified error handling
–– 5.4, 11.09.97, J.Hoyng: added CMAS_SIGNAL
–– 5.5, 12.09.97, J.Hoyng: added KERNEL_SIGNAL
–– 6.1, 10.09.98, W.Tammen: added procedure RESET_ALL_OUTPUT_PULSES
–– COL–RIBRE–SPR–5260,CSS handles pulses not correctly
–– 6.2, 17.12.98, J.Hoyng: added NULL_RID, changed COMMAND_TYPE (added SV_LOADED)
––
–– Purpose:
–– To provide an abstract state machine describing the shared
–– model structure between the model software and the Adaptation System
––
–– External:
–– From Ada system:
–– none
––
–– From CGS
–– NUMERIC_TYPES
–– UNIX_INTERFACE
–– From CSS:
–– CSS_TYPES
–– CSS_DEFINITIONS
––
–– I/O:
–– –––
––
–– Machine Dependencies:
–– none
––
–– Compiler Dependencies:
–– none
––
–– UNIX signals:
–– –––
––
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
with CSS_TYPES;
with CSS_DEFINITIONS;
with NUMERIC_TYPES;
with UNIX_INTERFACE;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
581 von/of: 662

Space Infrastructure
package MODEL_CONNECTION is
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–– Unix–Signal to be sent to the CMAS–Process from the kernel process
–– (synchronization between Kernel/CMAS)
CMAS_SIGNAL : constant UNIX_INTERFACE.UNIX_SIGNAL
:= UNIX_INTERFACE.SIGUSR1;
–– Unix–Signal to be sent to the Kernel–Process from the CMAS process
–– (synchronization between Kernel/CMAS)
KERNEL_SIGNAL : constant UNIX_INTERFACE.UNIX_SIGNAL
:= UNIX_INTERFACE.SIGUSR1;
–– The following ERROR_CODE_TYPE defines all possible error situations during
–– a simulation run produced by the CMAS software. Note that this type is
–– compatible to the error_code_type as defined in the GLOBAL_DATA package
–– of the CSS Kernel software.
–– error codes will be read from file
subtype CMAS_ERROR_CODE_TYPE is Integer;
–– the following error codes will identify the messages read from the file
–– $CSS_KERNEL_MESSAGES. These error codes will build the message field
–– together with the CSS kernel messages. Therefore, the used message codes
–– have to be different from those defined in the package GLOBAL_DATA of
–– the CSS kernel software. Both identifier ranges should build a contiguous
–– range of message numbers to minimize memory utilization.
––––––––––––––––––––––––––––––––––––––––––––
–– CMAS–Errors:
––––––––––––––––––––––––––––––––––––––––––––
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
582 von/of: 662
INITIAL_STATE: constant CMAS_ERROR_CODE_TYPE := 50133;
NONE_STATE: constant CMAS_ERROR_CODE_TYPE := 50134;
OTHER_ERROR: constant CMAS_ERROR_CODE_TYPE := 50135;
CMAS_MAIN_PROC_EXCEPTION_RAISED_WHILE_STARTUP_CALIB: constant CMAS_ERROR_CODE_TYPE := 50136;
CMAS_MAIN_PROC_EXCEPTION_RAISED_WHILE_STARTUP: constant CMAS_ERROR_CODE_TYPE := 50137;
CALIB_CANNOT_SELECT_CALIBRATION_TREATMENT: constant CMAS_ERROR_CODE_TYPE := 50138;
CALIB_CANNOT_SELECT_DECALIBRATION_TREATMENT: constant CMAS_ERROR_CODE_TYPE := 50139;
CALIB_CANNOT_INITIALIZE_CALIBRATION_TREATMENT_ARRAY: constant CMAS_ERROR_CODE_TYPE := 50140;
CALIB_TOO_MANY_BITS_REQUIRED_FOR_A_TC_PACKETS_USER_DATA_ENTRY: constant CMAS_ERROR_CODE_TYPE :=
50141;
CALIB_TOO_MANY_BITS_REQUIRED_FOR_A_TM_PACKETS_USER_DATA_ENTRY: constant CMAS_ERROR_CODE_TYPE :=
50142;
CALIB_CANNOT_CALIBRATE: constant CMAS_ERROR_CODE_TYPE := 50143;
CALIB_CANNOT_DECALIBRATE: constant CMAS_ERROR_CODE_TYPE := 50144;
PACKETIZER_UNDEFINED_PACKET_RECEIVED: constant CMAS_ERROR_CODE_TYPE := 50145;
PACKETIZER_CANNOT_INIT_PACKETIZER: constant CMAS_ERROR_CODE_TYPE := 50146;
PACKETIZER_CANNOT_DEFINE_CCSDS_TM_PACKET: constant CMAS_ERROR_CODE_TYPE := 50147;
PACKETIZER_CANNOT_DEFINE_CCSDS_TC_PACKET: constant CMAS_ERROR_CODE_TYPE := 50148;
PACKETIZER_CANNOT_DE_PACKETIZE: constant CMAS_ERROR_CODE_TYPE := 50149;
PACKETIZER_CANNOT_PACKETIZE: constant CMAS_ERROR_CODE_TYPE := 50150;
PACKETIZER_CANNOT_WRITE_CCSDS_PACKET: constant CMAS_ERROR_CODE_TYPE := 50151;
PACKETIZER_CANNOT_READ_CCSDS_PACKET: constant CMAS_ERROR_CODE_TYPE := 50152;
PACKETIZER_CANNOT_GET_RT_SA_TC_FIRST_SA: constant CMAS_ERROR_CODE_TYPE := 50153;
ILLEGAL_PARAMETERS_READ_FROM_MODEL_CONFIG_FILE: constant CMAS_ERROR_CODE_TYPE := 50154;
ILLEGAL_CALIB_DECALIB_DEFINITION: constant CMAS_ERROR_CODE_TYPE := 50155;
ILLEGAL_SW_TYPE_READ_FROM_MILBUS_CONFIG_FILE: constant CMAS_ERROR_CODE_TYPE := 50156;
ILLEGAL_MILBUS_CLASS_READ_FROM_MILBUS_CONFIG_FILE: constant CMAS_ERROR_CODE_TYPE := 50157;
INVALID_OPCODE_READ_FROM_MILBUS_CONFIG_FILE: constant CMAS_ERROR_CODE_TYPE := 50158;
LAN_IF_UNDEFINED_COMMAND_RECEIVED: constant CMAS_ERROR_CODE_TYPE := 50159;
CONVERSION_ERROR_UNSIGNED_INTEGER32_TO_BYTES: constant CMAS_ERROR_CODE_TYPE := 50160;
CONVERSION_ERROR_INTEGER32_TO_BYTES: constant CMAS_ERROR_CODE_TYPE := 50161;
CONVERSION_ERROR_BIT_TO_BYTES: constant CMAS_ERROR_CODE_TYPE := 50162;
WRONG_UNSIGNED_INTEGER32_BYTE_SIZE: constant CMAS_ERROR_CODE_TYPE := 50163;
WRONG_INTEGER32_BYTE_SIZE: constant CMAS_ERROR_CODE_TYPE := 50164;
WRONG_BIT_BYTE_SIZE: constant CMAS_ERROR_CODE_TYPE := 50165;
LAN_IF_CANNOT_START_EXCEPTION: constant CMAS_ERROR_CODE_TYPE := 50166;
LAN_IF_CANNOT_SHUTDOWN_EXCEPTION: constant CMAS_ERROR_CODE_TYPE := 50167;
LAN_IF_CANNOT_OPEN_EXCEPTION: constant CMAS_ERROR_CODE_TYPE := 50168;
LAN_IF_CANNOT_CLOSE_EXCEPTION: constant CMAS_ERROR_CODE_TYPE := 50169;
LAN_IF_CANNOT_READ_EXCEPTION: constant CMAS_ERROR_CODE_TYPE := 50170;
LAN_IF_CANNOT_WRITE_EXCEPTION: constant CMAS_ERROR_CODE_TYPE := 50171;
LAN_IF_CANNOT_TERMINAL_CMD_EXCEPTION: constant CMAS_ERROR_CODE_TYPE := 50172;

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
583 von/of: 662
SHM_ACCESS_RAISED_OTHER_EXCEPTION: constant CMAS_ERROR_CODE_TYPE := 50173;
SHM_ACCESS_CANNOT_COPY_EVERYTHING_UPDATED_EXCEPTION: constant CMAS_ERROR_CODE_TYPE := 50174;
SHM_ACCESS_CANNOT_INITIALIZE_ALL_OUTPUT_PINS_EXCEPTION: constant CMAS_ERROR_CODE_TYPE := 50175;
LAN_ACCESSS_RAISED_OTHER_EXCEPTION: constant CMAS_ERROR_CODE_TYPE := 50176;
STATUS_RAISED_OTHER_EXCEPTION: constant CMAS_ERROR_CODE_TYPE := 50177;
PIN_RAISED_OTHER_EXCEPTION: constant CMAS_ERROR_CODE_TYPE := 50178;
PIN_CANNOT_CREATE_ALL_ITEMS_EXCEPTION: constant CMAS_ERROR_CODE_TYPE := 50179;
PIN_CANNOT_INPUT_RANGE_EXCEPTION: constant CMAS_ERROR_CODE_TYPE := 50180;
PIN_CANNOT_UPDATED_FLAG_EXCEPTION: constant CMAS_ERROR_CODE_TYPE := 50181;
PIN_CANNOT_WRITE_EXCEPTION: constant CMAS_ERROR_CODE_TYPE := 50182;
PIN_CANNOT_READ_EXCEPTION: constant CMAS_ERROR_CODE_TYPE := 50183;
SCHEDULER_RAISED_OTHER_EXCEPTION: constant CMAS_ERROR_CODE_TYPE := 50184;
SCHEDULER_CANNOT_BEGIN_TO_COPY_EXCEPTION: constant CMAS_ERROR_CODE_TYPE := 50185;
SCHEDULER_CANNOT_PREVENT_FROM_SHM_ACCESS_EXCEPTION: constant CMAS_ERROR_CODE_TYPE := 50186;
SCHEDULER_CANNOT_SIMULATOR_EVENT_ACTIVITIES_EXCEPTION: constant CMAS_ERROR_CODE_TYPE := 50187;
SCHEDULER_CANNOT_LAN_EVENT_ACTIVITIES_EXCEPTION: constant CMAS_ERROR_CODE_TYPE := 50188;
SCHEDULER_CANNOT_SHM_ACCESS_DONE_ACTIVITIES_EXCEPTION: constant CMAS_ERROR_CODE_TYPE := 50189;
SCHEDULER_CANNOT_LAN_ACCESS_DONE_ACTIVITIES_EXCEPTION: constant CMAS_ERROR_CODE_TYPE := 50190;
SCHEDULER_CANNOT_SHUTDOWN_ACTIVITIES_EXCEPTION: constant CMAS_ERROR_CODE_TYPE := 50191;
SCHEDULER_CANNOT_INITIALIZE_EXCEPTION: constant CMAS_ERROR_CODE_TYPE := 50192;
CANNOT_START_DMS_CONNECTION: constant CMAS_ERROR_CODE_TYPE := 50193;
CMAS_MAIN_PROCEDURE_RAISED_OTHER_EXCEPTION: constant CMAS_ERROR_CODE_TYPE := 50194;
INVALID_MODEL_OUTPUT_ID: constant CMAS_ERROR_CODE_TYPE := 50195;
UNKNOWN_EXT_SW_TYPE: constant CMAS_ERROR_CODE_TYPE := 50196;
CONVERSION_ERROR_SIGNED_INTEGER_TO_BYTES: constant CMAS_ERROR_CODE_TYPE := 50197;
CONVERSION_ERROR_UNSIGNED_INTEGER_TO_BYTES: constant CMAS_ERROR_CODE_TYPE := 50198;
CONVERSION_ERROR_LONG_REAL_TO_BYTES: constant CMAS_ERROR_CODE_TYPE := 50199;
CONVERSION_ERROR_BOOLEAN_TO_BYTES: constant CMAS_ERROR_CODE_TYPE := 50200;
CONVERSION_ERROR_STATE_CODE_TO_BYTES: constant CMAS_ERROR_CODE_TYPE := 50201;
CONVERSION_ERROR_PULSE_TO_BYTES: constant CMAS_ERROR_CODE_TYPE := 50202;
CONVERSION_ERROR_BURST_PULSE_TO_BYTES: constant CMAS_ERROR_CODE_TYPE := 50203;
CONVERSION_ERROR_BYTE_STREAM_TO_BYTES: constant CMAS_ERROR_CODE_TYPE := 50204;
CONVERSION_ERROR_UNKNOWN_EXT_SW_TYPE: constant CMAS_ERROR_CODE_TYPE := 50205;
CONVERSION_ERROR_UNSIGNED_BYTE_TO_BYTES: constant CMAS_ERROR_CODE_TYPE := 50206;
CONVERSION_ERROR_SIGNED_BYTE_TO_BYTES: constant CMAS_ERROR_CODE_TYPE := 50207;
CONVERSION_ERROR_UNSIGNED_SHORT_WORD_TO_BYTES: constant CMAS_ERROR_CODE_TYPE := 50208;
CONVERSION_ERROR_SIGNED_SHORT_WORD_TO_BYTES: constant CMAS_ERROR_CODE_TYPE := 50209;
CONVERSION_ERROR_REAL_TO_BYTES: constant CMAS_ERROR_CODE_TYPE := 50210;
INVALID_MODEL_INPUT_ID: constant CMAS_ERROR_CODE_TYPE := 50211;
WRONG_SIGNED_INTEGER_BYTE_SIZE: constant CMAS_ERROR_CODE_TYPE := 50212;
WRONG_UNSIGNED_INTEGER_BYTE_SIZE: constant CMAS_ERROR_CODE_TYPE := 50213;
WRONG_LONG_REAL_BYTE_SIZE: constant CMAS_ERROR_CODE_TYPE := 50214;
WRONG_BOOLEAN_BYTE_SIZE: constant CMAS_ERROR_CODE_TYPE := 50215;
WRONG_STATE_CODE_BYTE_SIZE: constant CMAS_ERROR_CODE_TYPE := 50216;
WRONG_PULSE_BYTE_SIZE: constant CMAS_ERROR_CODE_TYPE := 50217;
WRONG_BURST_PULSE_BYTE_SIZE: constant CMAS_ERROR_CODE_TYPE := 50218;
WRONG_BYTE_STREAM_BYTE_SIZE: constant CMAS_ERROR_CODE_TYPE := 50219;
WRONG_SIGNED_BYTE_BYTE_SIZE: constant CMAS_ERROR_CODE_TYPE := 50220;
WRONG_UNSIGNED_BYTE_BYTE_SIZE: constant CMAS_ERROR_CODE_TYPE := 50221;
WRONG_UNSIGNED_SHORT_WORD_BYTE_SIZE: constant CMAS_ERROR_CODE_TYPE := 50222;
WRONG_SIGNED_SHORT_WORD_BYTE_SIZE: constant CMAS_ERROR_CODE_TYPE := 50223;
WRONG_REAL_BYTE_SIZE: constant CMAS_ERROR_CODE_TYPE := 50224;
CANNOT_CALIBRATE: constant CMAS_ERROR_CODE_TYPE := 50225;
CANNOT_DECALIBRATE: constant CMAS_ERROR_CODE_TYPE := 50226;
MISSING_PROCESS_ARGUMENTS: constant CMAS_ERROR_CODE_TYPE := 50227;
CANNOT_START_MODEL_CONNECTION_BECAUSE_SHM_ERROR: constant CMAS_ERROR_CODE_TYPE := 50228;
CANNOT_START_MODEL_CONNECTION_BECAUSE_SHM_ATTACH_ERROR: constant CMAS_ERROR_CODE_TYPE := 50229;
CANNOT_START_MODEL_CONNECTION_BECAUSE_SHM_GET_ERROR: constant CMAS_ERROR_CODE_TYPE := 50230;
CANNOT_START_MODEL_CONNECTION_BECAUSE_SHM_CREATION_ERROR: constant CMAS_ERROR_CODE_TYPE := 50231;
CANNOT_START_MODEL_CONFIG: constant CMAS_ERROR_CODE_TYPE := 50232;
LAN_ACCESS_CANNOT_DEFINE_MY_RID_DOMAINE: constant CMAS_ERROR_CODE_TYPE := 50233;
LAN_ACCESS_CANNOT_OPEN_OUTPUT_CHANNEL: constant CMAS_ERROR_CODE_TYPE := 50234;
LAN_ACCESS_CANNOT_OPEN_INPUT_CHANNEL: constant CMAS_ERROR_CODE_TYPE := 50235;
LAN_ACCESS_CANNOT_CLOSE_OUTPUT_CHANNEL: constant CMAS_ERROR_CODE_TYPE := 50236;
LAN_ACCESS_CANNOT_CLOSE_INPUT_CHANNEL: constant CMAS_ERROR_CODE_TYPE := 50237;
LAN_ACCESS_CANNOT_COPY_MODEL_INPUT_FROM_LAN_TO_PIN: constant CMAS_ERROR_CODE_TYPE := 50238;
SHM_ACCESS_CANNOT_COPY_MODEL_INPUT_TO_SHM: constant CMAS_ERROR_CODE_TYPE := 50239;
SHM_ACCESS_CANNOT_COPY_MODEL_OUTPUT_TO_PIN: constant CMAS_ERROR_CODE_TYPE := 50240;
type IO_CLASS_TYPE is(INPUT, OUTPUT);

Space Infrastructure
type CLIENT_TYPE is (CMAS,
KERNEL,
CTG);
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
type MODE_TYPE is (NO_CMAS, –– no CMAS–Process need to be started!
WITH_CMAS); –– CMAS–Process to be started!
type SHARED_MEM_TYPE is (UNIX_SHM,
VME_SHM);
LOCAL_STR : constant string := ”local”;
REMOTE_STR : constant string := ”remote”;
type TOGGLE_FLAG_TYPE is new BOOLEAN;
type RETURN_STATUS_TYPE is (OK,
NOK);
type RETURN_STARTUP_TYPE is (OK,
CMAS_NOT_CONNECTED, –– (can only appear if Client=Kernel)
SHM_ERROR);
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
584 von/of: 662
–– Kernel–Commands to command CMAS
type COMMAND_TYPE is(INITIAL,
NOMINAL, –– only ’Static Information’ may be accessed from the
Shared Memory
IO_ACCESS_PERMISSION, –– ’Static’ and ’I/O–Variables’ may be accessed
NO_IO_ACCESS, –– do not access ’I/O–Variables’ from the Shared Memory
SHUTDOWN, –– CMAS shall Shutdown
SV_LOADED); –– the kernel has loaded the State Vector
type CMAS_STATUS_TYPE is(INITIAL,
INITIALIZING,
NORMAL_IO_OPERATION,
CURRENTLY_OVERLOAD,
FAULTY,
SHUTDOWN_IN_PROGRESS,
SHUTDOWN_COMPLETED);
type RUNTIME_ID_TYPE is new CSS_DEFINITIONS.RUNTIME_ID_TYPE;
–– invalid RID
NULL_RID : constant RUNTIME_ID_TYPE := RUNTIME_ID_TYPE(0);
type ID_RANGE_TYPE is
record
NUMBER_OF_ITEMS : NATURAL := 0;
FIRST_ID : RUNTIME_ID_TYPE := 1;
LAST_ID : RUNTIME_ID_TYPE := 0;
end record;
type ID_RANGE_PER_CSS_SW_TYPE is array(CSS_TYPES.CSS_SW_TYPES) of ID_RANGE_TYPE;
–– array for MAX. SIZE per single Byte–Stream
type SIZE_ARRAY_TYPE is array (RUNTIME_ID_TYPE range ) of CSS_TYPES.UNSIGNED_INTEGER;
type SIZE_ARRAY_ACCESS_TYPE is access SIZE_ARRAY_TYPE;
–– this specifies the overall size (Configuration) of the ext. dyn. I/O–Memory
type SH_MODEL_CONFIGURATION_TYPE is
record
–– all ext. I/Os
EXTERNAL_IOS_RANGE : ID_RANGE_TYPE;
EXTERNAL_INPUTS_RANGE : ID_RANGE_TYPE;
EXTERNAL_OUTPUTS_RANGE : ID_RANGE_TYPE;
–– Input–Array over all sw_types
EXTERNAL_INPUTS : ID_RANGE_PER_CSS_SW_TYPE;
–– Input–Array over all byte_streams
EXTERNAL_INPUTS_BSS : SIZE_ARRAY_ACCESS_TYPE;
–– Output–Array over all sw_types
EXTERNAL_OUTPUTS : ID_RANGE_PER_CSS_SW_TYPE;

Space Infrastructure
–– Output–Array over all byte_streams
EXTERNAL_OUTPUTS_BSS : SIZE_ARRAY_ACCESS_TYPE;
end record;
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
type SH_MODEL_CONFIGURATION_ACCESS_TYPE is access SH_MODEL_CONFIGURATION_TYPE;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
585 von/of: 662
type STARTUP_TYPE(CLIENT : CLIENT_TYPE := KERNEL) is
record
case CLIENT is
when KERNEL =>
MODEL_CONFIGURATION : SH_MODEL_CONFIGURATION_TYPE;
MODE : MODE_TYPE;
CMAS_HOST : css_definitions.STRING_ACCESS;
when CTG =>
SH_MODEL_CONFIGURATION : SH_MODEL_CONFIGURATION_TYPE;
when CMAS =>
SHM : SHARED_MEM_TYPE;
–– the Unix–Shared–Memory–Ids (only needed when SHM = UNIX_SHM):
SHM_ID : css_definitions.STRING_ACCESS := new STRING’(””); –– ’External State Vector’
STAT_ID : css_definitions.STRING_ACCESS := new STRING’(””); –– ’Command/Status part’
when others =>
null;
end case;
end record;
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Operations for CTG + Kernel + CMAS –––––––––––––––––––––––––––––––––––––––––––
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– START
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– If the client is CTG|KERNEL the ’Shared Memory’ will
–– be initialized(type/class/max_length).
––
–– If the client is KERNEL this function starts the CMAS–Process(via CREATE_EXT_MEMORY)!
––
–– The START operation shall create memory regions on heap or shared
–– depending on the client.
––
–– If the client is KERNEL, after successful initialization of the static–part of SHM this
–– procedure sends the NOMINAL–CMD to CMAS
––
––
–– List of exceptions:
–– – INVALID_ID
–– – SHM_ATTACH_ERROR
–– – SHMGET_ERROR
–– – SHM_CREATION_ERROR
–– – FORK_ERROR
–– – LOAD_CMAS_SHMIDS_ERROR
–– – language_predefined_exceptions
––
––
function START(
STARTUP : in STARTUP_TYPE;
MILBUS_CONFIG_UNIX_PATH : STRING := ”” –– will be needed by CMAS
) return RETURN_STARTUP_TYPE;
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– UPDATE_VALUE
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– the ’UPDATE_FLAG’ will be set to ’TRUE’
––
–– In case of Ext. Model Input: The value will be updated in the WRITE–Buffer.
––

Space Infrastructure
–– (Ext. Model Output is not toggled!)
––
––
–– List of exceptions:
–– – INVALID_ID
–– – UPDATE_VALUE_ERROR
––
––
procedure UPDATE_VALUE( IO : in RUNTIME_ID_TYPE;
VALUE : in CSS_TYPES.IO_VALUE_TYPE);
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– READ_VALUE
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– This procedure returns for both Inputs and Output the last value assigned
–– to the IO variable. If the IO has been updated in the last cycle then
–– the IS_UPDATED parameter is set.
––
–– in case of Ext.Model–Input: reading will performed from
–– the ’WRITE–Buffer’ of the requested Input
––
–– (Ext. Model Output is not toggled!)
––
–– List of exceptions:
–– – INVALID_ID
–– – READ_VALUE_ERROR
––
––
procedure READ_VALUE( IO : in RUNTIME_ID_TYPE;
IS_UPDATED : out BOOLEAN;
VALUE : in out CSS_TYPES.IO_VALUE_TYPE);
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– GET_SW_TYPE
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– returns the Software type of the specified variable
––
–– List of exceptions:
–– – INVALID_ID
–– – GET_SW_TYPE_ERROR
––
––
function GET_SW_TYPE(IO : in RUNTIME_ID_TYPE) return CSS_TYPES.CSS_SW_TYPES;
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– IS_EXTERNAL
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– returns ’TRUE’if the given SW–TYPE is an External Type
––
–– List of exceptions:
–– – INVALID_ID
–– – IS_EXTERNAL_ERROR
––
––
function IS_EXTERNAL(SW_TYPE : in css_types.CSS_SW_TYPES) return boolean;
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– RESET_OUTPUTS_UPDATED_FLAG
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– restricted to ext. Output!
–– Set the Output’s Read Updated–Flag to False
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
586 von/of: 662

Space Infrastructure
––
–– List of exceptions:
–– – RESET_OUTPUTS_UPDATED_FLAG_ERROR
––
––
procedure RESET_OUTPUTS_UPDATED_FLAG;
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– SHUTDOWN
–– – return unix system resources
–– – if called by KERNEL this terminates also the CMAS–Process by command
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– List of exceptions:
–– – SHUTDOWN_ERROR
––
––
procedure SHUTDOWN;
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Operations for CTG + Kernel ––––––––––––––––––––––––––––––––––––––––––––––––
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– INITIALIZE_VALUE
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– this procedure ’initializes’ an ext. Input/Output, but it does not set
–– the ’Updated–Flag’!
–– (might be useful for CTG!)
––
–– List of exceptions:
–– – INVALID_ID
–– – INITIALIZE_VALUE_ERROR
––
––
procedure INITIALIZE_VALUE(IO : in RUNTIME_ID_TYPE;
VALUE : in CSS_TYPES.IO_VALUE_TYPE);
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
587 von/of: 662
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– MONITOR
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– reads/monitors Input or Output always from the write–buffer
––
–– List of exceptions:
–– – INVALID_ID
–– – MONITOR_ERROR
––
––
–– in case of Ext.Model–Input: Monitoring is will performed from
–– the ’WRITE–Buffer’ of the requested Input
––
–– reading Ext. Model Input from the ’WRITE–Buffer’ is based on the concept that:
–– 1. the producer has written its value into the ’WRITE–Buffer’
–– 2. the frame is already completed
–– 3. the Toggle–Bit has not been switched between producing and
–– monitoring the requested variable
––
–– (Ext. Model Output is not toggled!)
––
procedure MONITOR( IO : in RUNTIME_ID_TYPE; –– RID
ON_CHANGE : in BOOLEAN; –– requests change–indication(––>IS_CHANGE) restricted to
Input
IS_CHANGE : out BOOLEAN; –– change–indication (restricted to Input)

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
588 von/of: 662
VALUE : in out CSS_TYPES.IO_VALUE_TYPE); –– the reported monitored value
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– INJECT
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Change the value of the IO External Input.
––
–– If not INITIALIZE then
–– change the value just in case the variable is not
–– inhibited, and set the future inhibited state according to the
–– CONNECT_FLAG parameter.
––
–– If INITIALIZE then
–– change the value without making any check and
–– without setting the UPDATED flag
––
–– Inject writes the new value into both Read– and Write–Buffer!
––
–– List of exceptions:
–– – INJECT_ERROR
––
––
procedure INJECT( IO : in RUNTIME_ID_TYPE;
VALUE : in CSS_TYPES.IO_VALUE_TYPE;
CONNECT_FLAG : in BOOLEAN := TRUE;
INITIALIZE : in BOOLEAN);
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– CONNECT (Set the ext. Input as ’writable’)
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– restricted to ext. Input!
––
–– List of exceptions:
–– – CONNECT_ERROR
––
––
procedure CONNECT(IO : in RUNTIME_ID_TYPE);
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– DISCONNECT (Set the ext. Input as ’not writable’)
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– restricted to ext. Input!
–– prevent the ext. Input from beeing written
––
–– List of exceptions:
–– – DISCONNECT_ERROR
––
––
procedure DISCONNECT(IO : in RUNTIME_ID_TYPE);
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– CMAS_PERFORMANCE
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– reads the actual ’Load–Value’ from the Shared Memory
––
–– The ’Load–Value’ is the time(in seconds) the CMAS needs to access
–– the Shared Memory for reading/writing the ext. IOs
––
–– List of exceptions:

Space Infrastructure
–– – CMAS_PERFORMANCE_ERROR
––
––
function CMAS_PERFORMANCE return duration;
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– CHECK_CMAS_STATUS
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Returns the Status of the Adaptation System
––
function CHECK_CMAS_STATUS return CMAS_STATUS_TYPE;
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– BLOCK_CMAS (prevent CMAS from accessing the Shared State Vector)
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– signalize CMAS: no further writes/reads to/from the I/O–Variables
––
–– List of exceptions:
–– – UNIX_KILL_ERROR
–– – CMAS_OUT_OF_TIME_ERROR
–– – BLOCK_CMAS_ERROR
––
––
procedure BLOCK_CMAS;
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– UNBLOCK_CMAS (allow CMAS to access the Shared State Vector)
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– signalize CMAS: writes/reads to/from Shared Memory allowed
––
–– List of exceptions:
–– – UNIX_KILL_ERROR
–– – UNBLOCK_CMAS_ERROR
––
––
procedure UNBLOCK_CMAS;
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– resets all Ext. Input–Pulses(Pulse/Burst–Pulse) within the read–buffer
–– sets the Input’s Updated–Flag(true)
–– has to be called after switching the toggling–bit!!!
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
procedure RESET_ALL_INPUT_PULSES;
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– resets all Ext. Output–Pulses(Pulse/Burst–Pulse)
–– resets the Output’s Updated–Flag(false)
–– has to be called after each frame (after monitoring)
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
procedure RESET_ALL_OUTPUT_PULSES;
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– SWITCH_TOGGLE_BIT
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
589 von/of: 662

Space Infrastructure
–– This procedure inverts the external toggle bit
–– (may only be used by the Kernel!)
––
–– List of exceptions:
–– – SWITCH_TOGGLE_BIT_ERROR
––
––
procedure SWITCH_TOGGLE_BIT;
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– RESET_INPUTS_UPDATED_FLAG
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Set the Input’s Updated–Flag to False
––
–– restricted to ext. Input!
–– Set the Input’s Updated–Flag to False
––
–– List of exceptions:
–– – RESET_INPUTS_UPDATED_FLAG_ERROR
––
––
procedure RESET_INPUTS_UPDATED_FLAG;
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– LOAD_MODEL
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Load the external shared memory: (––>SHM)
––
–– Fill the shared memory with the values previously stored in the file in
–– the PATHNAME directory.
––
–– It is provided that the needed space for storing these values has been
–– created by a previous call to the START function.
––
–– ’MODEL_CONFIGURATION’ should have been loaded by the ’START’–Function.
––
–– List of exceptions:
–– – predefined exceptions
––
––
procedure LOAD_MODEL(PATHNAME : in STRING);
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– STORE_MODEL
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Store the external shared memory: (SHM––>)
––
–– List of exceptions:
–– – predefined exceptions
––
procedure STORE_MODEL(PATHNAME : in STRING);
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– READ_ACKNOWLEDGE
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– returns the actual cmd–acknowledge–variable inside SHM
––
function READ_ACKNOWLEDGE return boolean;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
590 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– SET_TERM_CMD
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– this procedure passes a ’Remote–Terminal–Command’ to CMAS
––
–– List of exceptions:
–– – SET_TERM_CMD_ERROR
––
procedure SET_TERM_CMD(MILBUS : in natural; –– Milbus–ID
RT : in natural; –– Remote Terminal to be switched
SWITCH : in boolean); –– TRUE=ON, FALSE=OFF
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– GET_CMAS_ERROR_CODE
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Reads the actual CMAS_ERROR_CODE from Shared Memory
––
–– List of exceptions:
–– – GET_CMAS_ERROR_CODE_ERROR
––
––
function GET_CMAS_ERROR_CODE return CMAS_ERROR_CODE_TYPE;
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– SET_CMAS_CMD
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Sends a command to CMAS
––
–– Note: if SIMULATOR_HW_INTERRUPT_IMPLEMENTED = TRUE, an Interrupt/Signal
–– will be combined with the Command to be sent
function SET_CMAS_CMD(CMD : in COMMAND_TYPE) return RETURN_STATUS_TYPE;
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– PUT_KERNEL_PROCESS_ID
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– writes the CMAS Process ID into Shared–Memory
––
–– List of exceptions:
–– – PUT_KERNEL_PROCESS_ID_ERROR
––
––
procedure PUT_KERNEL_PROCESS_ID(PROCESS_ID : in numeric_types.INTEGER32);
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Operations for CMAS only –––––––––––––––––––––––––––––––––––––––––––––––––––––
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– EXT_IO_CLASS (Return the class of the given Runtime–ID)
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– Returns the class (Input or Output) of the given Runtime–ID
––
–– List of exceptions:
–– – INVALID_ID
––
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
591 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
––
function EXT_IO_CLASS(RID : in RUNTIME_ID_TYPE) return IO_CLASS_TYPE;
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– GET_COMMAND
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Get the command as set by the Kernel, give acknowledge
––
–– List of exceptions:
–– – GET_COMMAND_ERROR
––
––
function GET_COMMAND return COMMAND_TYPE;
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– SET_CMAS_STATUS
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– procedure used by the Adaptation System to inform the model about
–– its status (may be written by CMAS at any time)
––
–– List of exceptions:
–– – SET_CMAS_STATUS_ERROR
––
––
procedure SET_CMAS_STATUS(STATUS : in CMAS_STATUS_TYPE);
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– GET_TERM_CMD
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– this procedure reads a ’Remote–Terminal–Command’
––
–– List of exceptions:
–– – GET_TERM_CMD_ERROR
––
procedure GET_TERM_CMD(MILBUS : out natural; –– Milbus–Identifier
RT : out natural; –– Remote Terminal to be switched
SWITCH : out boolean; –– TRUE=ON, FALSE=OFF
FLAG : out boolean); –– CMD update flag
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– OUTPUT_UPDATED
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Returns the value of the output’s ’UPDATED_FLAG’
––
–– List of exceptions:
–– – INVALID_ID
–– – OUTPUT_UPDATED_ERROR
––
function OUTPUT_UPDATED(RID : in RUNTIME_ID_TYPE) return BOOLEAN;
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– FIRST_IO
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Returns the Runtime–ID of the first of all ext. I/O
––
–– List of exceptions:
–– – FIRST_IO_ERROR
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
592 von/of: 662

Space Infrastructure
––
––
function FIRST_IO return RUNTIME_ID_TYPE;
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– LAST_IO
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Returns the Runtime–ID of the last of all ext. I/O
––
–– List of exceptions:
–– – LAST_IO_ERROR
––
––
function LAST_IO return RUNTIME_ID_TYPE;
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– FIRST_INPUT
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Returns the Runtime–ID of the first ext. Input
––
–– List of exceptions:
–– – FIRST_INPUT_ERROR
––
––
function FIRST_INPUT return RUNTIME_ID_TYPE;
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– LAST_INPUT
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Returns the Runtime–ID of the last ext. Input
––
–– List of exceptions:
–– – LAST_INPUT_ERROR
––
––
function LAST_INPUT return RUNTIME_ID_TYPE;
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– FIRST_OUTPUT
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Returns the Runtime–ID of the first ext. Output
––
–– List of exceptions:
–– – FIRST_OUTPUT_ERROR
––
––
function FIRST_OUTPUT return RUNTIME_ID_TYPE;
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– LAST_OUTPUT
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Returns the Runtime–ID of the last ext. Output
––
–– List of exceptions:
–– – LAST_OUTPUT_ERROR
––
––
function LAST_OUTPUT return RUNTIME_ID_TYPE;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
593 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– FIRST_BYTE_STREAM_INPUT
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Returns the Runtime–ID of the first ext. Byte–Stream–Input
––
–– List of exceptions:
–– – FIRST_BYTE_STREAM_INPUT_ERROR
––
––
function FIRST_BYTE_STREAM_INPUT return RUNTIME_ID_TYPE;
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– LAST_BYTE_STREAM_INPUT
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Returns the Runtime–ID of the last ext. Byte–Stream–Input
––
–– List of exceptions:
–– – LAST_BYTE_STREAM_INPUT_ERROR
––
––
function LAST_BYTE_STREAM_INPUT return RUNTIME_ID_TYPE;
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– FIRST_BYTE_STREAM_OUTPUT
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Returns the Runtime–ID of the first ext. Byte–Stream–Output
––
–– List of exceptions:
–– – FIRST_BYTE_STREAM_OUTPUT_ERROR
––
––
function FIRST_BYTE_STREAM_OUTPUT return RUNTIME_ID_TYPE;
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– LAST_BYTE_STREAM_OUTPUT
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Returns the Runtime–ID of the last ext. Byte–Stream–Output
––
–– List of exceptions:
–– – LAST_BYTE_STREAM_OUTPUT_ERROR
––
––
function LAST_BYTE_STREAM_OUTPUT return RUNTIME_ID_TYPE;
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– MAX_LENGTH_OF_INPUT_BYTE_STREAM
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Returns the maximum length of the given ext. Byte–Stream–Input
––
–– List of exceptions:
–– – INVALID_ID
–– – MAX_LENGTH_OF_INPUT_BYTE_STREAM_ERROR
––
––
function MAX_LENGTH_OF_INPUT_BYTE_STREAM(RID : in RUNTIME_ID_TYPE)
return CSS_TYPES.UNSIGNED_INTEGER;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
594 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– MAX_LENGTH_OF_OUTPUT_BYTE_STREAM
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Returns the maximum length of the given ext. Byte–Stream–Output
––
–– List of exceptions:
–– – INVALID_ID
–– – MAX_LENGTH_OF_OUTPUT_BYTE_STREAM_ERROR
––
––
function MAX_LENGTH_OF_OUTPUT_BYTE_STREAM(RID : in RUNTIME_ID_TYPE) return
CSS_TYPES.UNSIGNED_INTEGER;
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– WRITE_CMAS_ERROR_CODE
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– writes the CMAS_ERROR_CODE into Shared–Memory
––
–– List of exceptions:
–– – WRITE_CMAS_ERROR_CODE_ERROR
––
––
procedure WRITE_CMAS_ERROR_CODE(CODE : in CMAS_ERROR_CODE_TYPE);
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– PUT_CMAS_PROCESS_ID
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– writes the CMAS Process ID into Shared–Memory
––
–– List of exceptions:
–– – PUT_CMAS_PROCESS_ID_ERROR
––
––
procedure PUT_CMAS_PROCESS_ID(PROCESS_ID : in numeric_types.INTEGER32);
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– CMAS_PROCESS_ID
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– reads the CMAS Process ID from Shared–Memory
––
––
function CMAS_PROCESS_ID return numeric_types.INTEGER32;
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– KERNEL_PROCESS_ID
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– reads the Kernel Process ID from Shared–Memory
––
––
function KERNEL_PROCESS_ID return numeric_types.INTEGER32;
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– PUT_CMAS_PERFORMANCE
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– writes the actual ’Load–Value’ into the Shared Memory
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
595 von/of: 662

Space Infrastructure
––
–– The ’Load–Value’ is the time(in seconds) the CMAS needs to access
–– the Shared Memory for reading/writing the ext. IOs
––
–– List of exceptions:
–– – PUT_CMAS_PERFORMANCE_ERROR
––
––
procedure PUT_CMAS_PERFORMANCE(DURATION_VALUE : in duration);
–––––––––––––––––––––––––––––––––––––––––––––––––––––
–– complete list of all possible specific exceptions
–– (no predefined exceptions!)
–––––––––––––––––––––––––––––––––––––––––––––––––––––
PUT_CMAS_PERFORMANCE_ERROR,
CMAS_PERFORMANCE_ERROR,
PUT_CMAS_PROCESS_ID_ERROR,
PUT_KERNEL_PROCESS_ID_ERROR,
SHM_ATTACH_ERROR,
SHMGET_ERROR,
SHM_CREATION_ERROR,
INVALID_ID,
INVALID_PIN,
SHM_DETACH_ERROR,
SHM_REMOVE_ERROR,
FORK_ERROR,
SHUTDOWN_ERROR,
UNIX_KILL_ERROR,
BLOCK_CMAS_ERROR,
UNBLOCK_CMAS_ERROR,
BYTE_STREAM_SIZE_ERROR,
CMAS_OUT_OF_TIME_ERROR,
LOAD_CMAS_SHMIDS_ERROR,
RESET_INPUTS_UPDATED_FLAG_ERROR,
RESET_OUTPUTS_UPDATED_FLAG_ERROR,
INJECT_ERROR,
CONNECT_ERROR,
DISCONNECT_ERROR,
SET_TERM_CMD_ERROR,
GET_TERM_CMD_ERROR,
SET_CMAS_STATUS_ERROR,
GET_COMMAND_ERROR,
GET_SW_TYPE_ERROR,
IS_EXTERNAL_ERROR,
SWITCH_TOGGLE_BIT_ERROR,
UPDATE_VALUE_ERROR,
INITIALIZE_VALUE_ERROR,
READ_VALUE_ERROR,
SET_PIN_INFO_ERROR,
OUTPUT_UPDATED_ERROR,
FIRST_IO_ERROR,
LAST_IO_ERROR,
FIRST_INPUT_ERROR,
LAST_INPUT_ERROR,
FIRST_OUTPUT_ERROR,
LAST_OUTPUT_ERROR,
FIRST_BYTE_STREAM_INPUT_ERROR,
LAST_BYTE_STREAM_INPUT_ERROR,
FIRST_BYTE_STREAM_OUTPUT_ERROR,
LAST_BYTE_STREAM_OUTPUT_ERROR,
MAX_LENGTH_OF_INPUT_BYTE_STREAM_ERROR,
MAX_LENGTH_OF_OUTPUT_BYTE_STREAM_ERROR,
GET_CMAS_ERROR_CODE_ERROR,
WRITE_CMAS_ERROR_CODE_ERROR,
MONITOR_ERROR,
GIVE_ACKNOWLEDGE_ERROR : exception;
end MODEL_CONNECTION;
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
596 von/of: 662

Space Infrastructure
Formal Interface Description
597
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– ABSTRACT –– SMT_CALENDAR
––
–– To provide types and operations on the Simulated Mission Time similar the Ada standard
–– package CALENDAR.
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– KEYWORDS –– SMT_CALENDAR
–– Project CSS
–– ADD, section ??
–– HOOD object SMT_CALENDAR
–– basic types, utilities
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– CONTENTS –– SMT_CALENDAR
––
–– Type: Package Specification
––
–– Version:
–– 3.1, 21.07.94, J.Hoyng: initial_version
–– 3.2, 06.04.95, J.Hoyng: new implementation
–– 4.1, 23.08.95, J.Hoyng: changed comment
––
––
–– Purpose:
–– To provide types and operations on the Simulated Mission Time
––
–– External:
–– From Ada system:
–– CALENDAR
––
––
–– From CSS:
––
––
–– I/O:
–– –––
––
–– Machine Dependencies:
–– none
––
–– Compiler Dependencies:
–– none
––
–– UNIX signals:
–– –––
––
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
£
–– imports from Ada system:
with CALENDAR;
–– imports from CGS:
–– imports from CSS:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
597 von/of: 662

Space Infrastructure
598
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
package SMT_CALENDAR is
type LONG_DURATION is new DURATION;
type TIME is private;
subtype YEAR_NUMBER is INTEGER range 1901 .. 2099;
subtype MONTH_NUMBER is INTEGER range 1 .. 12;
subtype DAY_NUMBER is INTEGER range 1 .. 31;
subtype DAY_DURATION is LONG_DURATION range 0.0 .. 86_400.0;
function CLOCK return TIME;
–– used only by the kernel
procedure SET_TIME (ITEM: TIME);
function YEAR (DATE: TIME) return YEAR_NUMBER;
function MONTH (DATE: TIME) return MONTH_NUMBER;
function DAY (DATE: TIME) return DAY_NUMBER;
function SECONDS(DATE: TIME) return DAY_DURATION;
procedure SPLIT (DATE : in TIME;
YEAR : out YEAR_NUMBER;
MONTH : out MONTH_NUMBER;
DAY : out DAY_NUMBER;
SECONDS: out DAY_DURATION);
function TIME_OF(YEAR : YEAR_NUMBER;
MONTH : MONTH_NUMBER;
DAY : DAY_NUMBER;
SECONDS: DAY_DURATION := 0.0) return TIME;
function ”+” (LEFT: TIME; RIGHT: LONG_DURATION) return TIME;
function ”+” (LEFT: LONG_DURATION; RIGHT: TIME) return TIME;
function ”–” (LEFT: TIME; RIGHT: LONG_DURATION) return TIME;
function ”–” (LEFT: TIME; RIGHT: TIME) return LONG_DURATION;
function ”=” (LEFT, RIGHT: TIME) return BOOLEAN;
function TO_CALENDAR_TIME (ITEM: TIME) return CALENDAR.TIME;
function TO_CSS_TIME (ITEM: CALENDAR.TIME) return TIME;
procedure SET_MINFRAME_INTERVAL (MINFRAME_INTERVAL : LONG_DURATION);
function GET_MINFRAME_INTERVAL return LONG_DURATION;
TIME_ERROR : exception;
private
type TIME is new CALENDAR.TIME;
end SMT_CALENDAR;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
598 von/of: 662

Space Infrastructure
Formal Interface Description
599
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– ABSTRACT –– DB_DEFINITIONS (SUN)
––
–– Definitions of types used for database structure modeling,
–– based on MPS definitions.
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– KEYWORDS –– DB_DEFINITIONS (SUN)
–– Project CSS
–– ADD, section 5.2.11 (CSS_DB)
–– HOOD Object DB_DEFINITIONS_SUN
–– database type definitions
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– CONTENTS –– DB_DEFINITIONS (SUN)
––
–– Type: Package Specification
––
–– Version:
–– 2.1, 10.11.93, : initial version
–– 3.1, 06.04.95, J.Hoyng: added GET_SV_DIR_NAME, GET_INITIAL_SV_DIR_NAME
–– GET_MAPPING_TABLE_NAME, GET_MILBUS_CONFIG_NAME,
–– changed MODEL_ID
–– A.Schulz: imported T_CDU_DOMAIN from MPS_DEFINITIONS
–– changed UNIX path access for DB version
–– 4.1, 23.08.95, A.Schulz, J.Hoyng:
–– INIT_UNIX_PATH modified : no ROOT_PATH; when
–– file system based : exception if path in ID is
–– empty
–– 4.2, 01.12.95, A.Schulz: Added procedures for improved exception message
–– handling
–– 4.3, 07.10.96, A.Schulz: Added support for CDU test versions
–– 5.1, 26.09.96, V.Schultz: SPR–2547: Improved procedures for error message
–– handling
–– 25.08.97, Th. Behrens: Added new types IO_DESCS and IO_DESCS_POINTER
–– to be able to pass information from CSS DB
–– Server to CMAS DB Server.
––
––
–– Purpose:
–– definitions of types used for database structure modeling
––
–– Function:
–– –––
––
–– External:
–– External:
–– From Ada system:
–– UNCHECKED_DEALLOCATION
––
–– From CGS:
–– NUMERIC_TYPES –– portable types with fixed representation
–– DYNAMIC_STRINGS
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
599 von/of: 662

Space Infrastructure
600
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–– MPS_DEFINITIONS –– MPS interface
––
–– I/O:
–– –––
––
–– Machine Dependencies:
–– MPS interface available for the Sun platform only.
––
–– Compiler Dependencies:
–– none
––
–– UNIX signals:
–– –––
––
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– imports from Ada system:
with UNCHECKED_DEALLOCATION;
–– imports from CGS:
with MPS_DEFINITIONS, NUMERIC_TYPES, DYNAMIC_STRINGS;
with STRING_POINTERS;
with CSS_TYPES;
package DB_DEFINITIONS is
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– TYPE DEFINITIONS PROVIDED BY THIS PACKAGE:
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– In this package, in contast to the corresponding package for the HP
–– target, most declared types are inherited from MPS as subtypes.
–– Only new types (adding semantics not present in existing MPS types)
–– use derived types.
–– Of course, with every change of the MPS interface, consistency with
–– the HP version must be checked.
–––– general types ––––
type TYPES_OF_ENVIRONMENT is (SYSTEM, USER, LIB);
type SID is new MPS_DEFINITIONS.SID;
NULL_SID : constant SID := SID(MPS_DEFINITIONS.NULL_SID);
type SID_ARRAY is new MPS_DEFINITIONS.T_SID_ARRAY;
type SUBITEM_ID is new NUMERIC_TYPES.UNSIGNED_INTEGER32;
type IO_ID is record
PARENT_SID : SID;
IO_ID : SUBITEM_ID;
end record;
type COMPLETION_CODE is new MPS_DEFINITIONS.COMPLETION_CODE;
type STATE_CODE is new MPS_DEFINITIONS.STATE_CODE;
–––– names based on fixed length STRINGs –––
type NAME is new MPS_DEFINITIONS.T_NAME;
type ELEMENT_CONFIGURATION_NAME is new
MPS_DEFINITIONS.T_ELEMENT_CONFIGURATION_NAME;
type MISSION_NAME is new MPS_DEFINITIONS.T_MISSION_NAME;
type CONFIGURATION_NAME is new MPS_DEFINITIONS.T_CONFIGURATION_NAME;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
600 von/of: 662

Space Infrastructure
601
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
601 von/of: 662
subtype FUNCTION_NAME is NAME;
–––– variable length names ––––
type DYNAMIC_STRING is new MPS_DEFINITIONS.DYNAMIC_STRING;
type NAME_TREE_PATH is new MPS_DEFINITIONS.DYNAMIC_STRING;
type LIBRARY_PATHNAME is new MPS_DEFINITIONS.DYNAMIC_STRING;
–––– string– and char constants ––––
NULL_PATHNAME : constant STRING := MPS_DEFINITIONS.NULL_PATHNAME;
SEPARATOR_CHAR : constant CHARACTER := MPS_DEFINITIONS.NODE_NAME_SEPARATOR(1);
SEPARATOR : constant STRING := MPS_DEFINITIONS.NODE_NAME_SEPARATOR;
SUBITEM_SEPARATOR : constant STRING := ”.”;
SUBITEM_SEPARATOR_CHAR : constant CHARACTER := SUBITEM_SEPARATOR(1);
PAD_CHAR : constant CHARACTER := ’ ’;
–– the character with which left–aligned fixed strings are filled
–– The directory below the user’s home directory where all
–– files related to models in the database are stored :
MODEL_ROOT_DIR : constant STRING := ”models.lib”;
–––– other variable length arrays ––––
subtype BYTE_ARRAY is NUMERIC_TYPES.BYTE_ARRAY;
type BYTE_STREAM is new MPS_DEFINITIONS.T_BYTE_STREAM;
–––– database object versions ––––
subtype VERSION_NUMBER is MPS_DEFINITIONS.T_VERSION_NUMBER;
type SYSTEM_TREE_VERSION is new VERSION_NUMBER;
type VERSION_STATUS is new MPS_DEFINITIONS.T_VERSION_STATUS;
subtype VERSION_RECORD is MPS_DEFINITIONS.T_VERSION;
function IMAGE (V: VERSION_RECORD) return STRING;
function ”=” (V1, V2: VERSION_RECORD) return BOOLEAN
renames MPS_DEFINITIONS.”=”;
subtype LIBRARY_VERSION is MPS_DEFINITIONS.T_CDU_VERSION;
function IMAGE (V: LIBRARY_VERSION) return STRING;
function NULL_LIBRARY_VERSION return LIBRARY_VERSION;
function ”=” (LIB1, LIB2: LIBRARY_VERSION) return BOOLEAN
renames MPS_DEFINITIONS.”=”;
type T_CDU_DOMAIN is new MPS_DEFINITIONS.T_CDU_DOMAIN;
–––– compound types ––––
–– Subroutines ASSIGN and = provided for use as actual parameters
–– for generic instantiations.
–– subroutines NULL_* supplied so thast input parameters can be set
–– to a default value.
type LIBRARY is record
LIBRARY_SID : SID;
PATHNAME : LIBRARY_PATHNAME;
VERSION : LIBRARY_VERSION;
end record;
function NULL_LIBRARY return LIBRARY;

Space Infrastructure
602
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
procedure ASSIGN( TARGET : in out LIBRARY; SOURCE : LIBRARY);
function ”=” (LEFT, RIGHT: LIBRARY) return BOOLEAN;
procedure DEALLOCATE (LIB : in out LIBRARY);
type SYSTEM_ENVIRONMENT is record
ELEMENT_CONFIGURATION : ELEMENT_CONFIGURATION_NAME;
MISSION : MISSION_NAME;
SYS_TREE_VERSION : SYSTEM_TREE_VERSION;
end record;
function NULL_SYSTEM_ENVIRONMENT return SYSTEM_ENVIRONMENT;
procedure ASSIGN ( TARGET : in out SYSTEM_ENVIRONMENT;
SOURCE : SYSTEM_ENVIRONMENT);
–– function ”=” (LEFT, RIGHT: SYSTEM_ENVIRONMENT) is implicit;
type USER_ENVIRONMENT is record
SYSTEM_TREE_NODE_PATHNAME : NAME_TREE_PATH;
CONFIGURATION : CONFIGURATION_NAME;
CCU_VERSION : VERSION_RECORD;
end record;
function NULL_USER_ENVIRONMENT return USER_ENVIRONMENT;
procedure ASSIGN ( TARGET : in out USER_ENVIRONMENT;
SOURCE : USER_ENVIRONMENT);
function ”=” (LEFT, RIGHT: USER_ENVIRONMENT) return BOOLEAN;
procedure DEALLOCATE (USER_ENV : in out USER_ENVIRONMENT);
type ENVIRONMENT is record
SYS_ENV : SYSTEM_ENVIRONMENT;
USER_ENV : USER_ENVIRONMENT;
LIB : LIBRARY;
end record;
procedure ASSIGN ( TARGET : in out ENVIRONMENT; SOURCE : ENVIRONMENT);
function ”=” (LEFT, RIGHT: ENVIRONMENT) return BOOLEAN;
procedure DEALLOCATE (ENV : in out ENVIRONMENT);
type TOP_LEVEL_FB_ID is record
NAME : FUNCTION_NAME;
FB_SID : SID;
PARENT_LIBRARY : LIBRARY;
end record;
procedure ASSIGN ( TARGET : in out TOP_LEVEL_FB_ID;
SOURCE : TOP_LEVEL_FB_ID);
function ”=” (LEFT, RIGHT : TOP_LEVEL_FB_ID ) return BOOLEAN;
procedure DEALLOCATE (ID : in out TOP_LEVEL_FB_ID);
type TOP_LEVEL_FB_ID_ARRAY is array ( NATURAL range ) of TOP_LEVEL_FB_ID;
procedure ASSIGN ( TARGET : in out TOP_LEVEL_FB_ID_ARRAY;
SOURCE : TOP_LEVEL_FB_ID_ARRAY);
function ”=” (LEFT, RIGHT : TOP_LEVEL_FB_ID_ARRAY ) return BOOLEAN;
procedure DEALLOCATE (ID_ARRAY : in out TOP_LEVEL_FB_ID_ARRAY);
type STORAGE_VERSION is (FILE_BASED, DB_BASED);
type STRING_ACCESS is access STRING;
procedure FREE is new UNCHECKED_DEALLOCATION (STRING, STRING_ACCESS);
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
602 von/of: 662

Space Infrastructure
603
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
type MODEL_ID( STORAGE_KIND: STORAGE_VERSION := DB_BASED) is
record
TOP_LEVEL_FB_NAME : STRING_ACCESS;
TOP_LEVEL_FB_SID : SID;
LIBRARY_NAME : STRING_ACCESS;
MODEL_UNIX_PATH : STRING_ACCESS;
ROOT : STRING_ACCESS;
case STORAGE_KIND is
when DB_BASED =>
ELEMENT_CONFIGURATION : STRING_ACCESS;
MISSION : STRING_ACCESS;
SYS_TREE_VERSION : SYSTEM_TREE_VERSION;
LIBRARY_SID : SID;
LIB_VERSION : LIBRARY_VERSION;
when FILE_BASED => null;
end case;
end record;
type MODEL_ID_ACCESS is access MODEL_ID;
procedure ASSIGN ( TARGET : in out MODEL_ID; SOURCE : MODEL_ID);
procedure DEALLOCATE (ID : in out MODEL_ID);
procedure DEALLOCATE (ID : in out MODEL_ID_ACCESS);
type OBJECT_REFERENCE is record
LIB_PATHNAME : NAME_TREE_PATH;
LIB_VERSION : LIBRARY_VERSION;
RELATIVE_NAME : NAME_TREE_PATH;
end record;
procedure ASSIGN ( TARGET : in out OBJECT_REFERENCE;
SOURCE : OBJECT_REFERENCE);
function ”=” (LEFT, RIGHT: OBJECT_REFERENCE) return BOOLEAN;
procedure DEALLOCATE (OBJECT : in out OBJECT_REFERENCE);
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Types to exchange data between CSS DB Server and CMAS DB Server
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
type IO_DESC_IO_ID is record
IO_NAME : STRING_ACCESS;
INDEX : SUBITEM_ID;
end record;
type CSS_IO_TYPES is (INPUT, OUTPUT);
type STATE_CODE_LIST is access MPS_DEFINITIONS.T_STATE_CODE_ARRAY;
type REF_DESC is record
CDU_NAME : STRING_ACCESS;
ONB_NAME : STRING_ACCESS;
REF_SID : SID;
end record;
type REF_DESC_ACCESS is access REF_DESC;
type IO_DESC is record
NAME_INDEX : IO_DESC_IO_ID;
CSS_IO_TYPE : CSS_IO_TYPES;
CSS_SW_TYPE : CSS_TYPES.CSS_SW_TYPES
:= CSS_TYPES.NONE;
–– Valid only, if CSS_SW_TYPE /= CSS_TYPES.NONE.
ENG_UNIT : STRING_ACCESS
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
603 von/of: 662

Space Infrastructure
604
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
:= null;
–– Valid only, if CSS_SW_TYPE is real type and
–– ENG_UNIT /= null.
STATE_CODES : STATE_CODE_LIST
:= null;
–– Valid only, if CSS_SW_TYPE = CSS_TYPES.STATECODE_TYPES and
–– STATE_CODES /= null.
ONB_REF : REF_DESC_ACCESS
:= null;
–– Valid only, if ONB_REF /= null.
end record;
type IO_DESC_LIST
is array (POSITIVE range )
of IO_DESC;
type IO_DESC_LIST_POINTER
is access IO_DESC_LIST;
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– UNIX PATH NAMES FOR CSS MODEL DATA:
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
EMPTY_ROOT_PATH : exception;
–– will be raised if MODEL_ID.MODEL_UNIX_PATH is empty when
–– a user tries to get a UNIX path for the model.
procedure INIT_UNIX_PATH
(MODEL : in out MODEL_ID);
–– This operation is used to determine for the db–based version
–– the unix pathname of the root directory in the UNIX file system
–– where the data of a specific version of a model is stored and stores
–– it into the corresponding field of the MODEL_ID. The full path to the
–– model is determined from the other attributes of MODEL_ID to:
––
–– $HOME/models.lib/–./
–– library_sid_–V../model_sid_
–– resp. for test versions (not yet supported) :
–– library_sid_–..––/
–– model_sid_
––
–– For the file–system based version, MODEL_ID.MODEL_UNIX_PATH has to be set
–– by the user before calling INIT_UNIX_PATH. The procedure will raise
–– EMPTY_ROOT_PATH when called and MODEL_ID.MODEL_UNIX_PATH is undefined.
––
–– Since this construction is hidden from the user, any call of
–– the following functions will raise EMPTY_ROOT_PATH whenever
–– MODEL_ID.MODEL_UNIX_PATH is undefined.
function GET_UNIX_PATH
(MODEL : in MODEL_ID;
ARCHITECTURE : in STRING := ””) return STRING;
–– This function returns the path to the UNIX root directory
–– where the architecture specific data for the specified model
–– is stored.
–– It will raise EMPTY_ROOT_PATH if the MODEL_UNIX_PATH in the
–– MODEL_ID is empty, i.e. hasn’t been initialised.
––
–– ===> See comment in HOST_SYSTEM for pathname conventions.

Space Infrastructure
605
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
605 von/of: 662
SV_NAME : in STRING;
ARCHITECTURE : in STRING) return STRING;
–– This function returns the path to the UNIX directory where
–– the architecture specific state vector for the specified model
–– is stored.
–– It will raise EMPTY_ROOT_PATH if the MODEL_UNIX_PATH in the
–– MODEL_ID is empty, i.e. hasn’t been initialised.
function GET_INITIAL_SV_NAME return STRING;
–– This function returns name the initial state vector for a model.
function GET_EXECUTABLE_NAME
(MODEL : in MODEL_ID;
ARCHITECTURE : in STRING) return STRING;
–– This function returns the path to the UNIX file where
–– the architecture specific mapping table for the specified model
–– is stored.
–– It will raise EMPTY_ROOT_PATH if the MODEL_UNIX_PATH in the
–– MODEL_ID is empty, i.e. hasn’t been initialised.
function GET_MILBUS_CONFIG_NAME
(MODEL : in MODEL_ID;
ARCHITECTURE : in STRING) return STRING;
–– This function returns the path to the UNIX file where
–– the architecture specific MIL–bus configuration data
–– for the specified model is stored.
–– It will raise EMPTY_ROOT_PATH if the MODEL_UNIX_PATH in the
–– MODEL_ID is empty, i.e. hasn’t been initialised.
–––––––––––––––––––Error handling types and procedures–––––––––––––––
–– raised in the case that HANDLE_DB_EXCEPTION fails:
EXCEPTION_HANDLING_FAILED : exception;
–– raised in the case of fatal internal errors:
CSS_DB_INTERNAL_ERROR : exception;
–– propagated MPS_DEFINITIONS (or other) exceptions :
type T_PROPAGATED_EXCEPTION is
( MDB_ERROR, AUTHORIZATION_ERROR, USE_ERROR, ORACLE_ERROR, OTHER, NONE );
–– allows any package to declare a common exception, e.g. GENERAL_ERROR
–– and an exported variable, e.g. RAISED_EXCEPTION : T_PROPAGATED_EXCEPTION,
–– which may be read by the calling procedure.
––––––––––––––––––––––RAISE_PROPAGATED_EXCEPTION–––––––––––––––––––––
procedure RAISE_PROPAGATED_EXCEPTION(
TO_RAISE : in T_PROPAGATED_EXCEPTION);
––––––––––––––––––––––––––––––––––––PREPEND––––––––––––––––––––––––––
procedure PREPEND(
ERROR_MESSAGE : in out DB_DEFINITIONS.DYNAMIC_STRING;
PREFIX : in STRING );
––––––––––––––––––––––––PROPAGATE_EXCEPTION––––––––––––––––––––––––––
procedure PROPAGATE_EXCEPTION(
MY_ERROR_MESSAGE: in out DB_DEFINITIONS.DYNAMIC_STRING;
MY_EXCEPTION : out T_PROPAGATED_EXCEPTION;
CALLER : in STRING;
CALLER_MESSAGE : in DB_DEFINITIONS.DYNAMIC_STRING;
CALLER_EXCEPTION: in T_PROPAGATED_EXCEPTION);

Space Infrastructure
606
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–––––––––––––––––––––––––––––––HANDLE_DB_EXCEPTION–––––––––––––––––––––––––
–– set standard ERROR_MESSAGE, depending on CALLER, name of raised
–– exception (from CURRENT_EXEPTION or user message) and FOR_ITEM
–– (Pathname –preferred–, SID, RID or IO_ID, depending on context)
procedure HANDLE_DB_EXCEPTION(
ERROR_MESSAGE : in out DB_DEFINITIONS.DYNAMIC_STRING;
RAISED_EXCEPTION: out T_PROPAGATED_EXCEPTION;
EXCEPTION_NAME : in STRING;
CALLER : in STRING;
FOR_ITEM : in STRING := ””);
––––––––––––––––––––––––––––HANDLE_USER_EXCEPTION–––––––––––––––––––––––––
–– set standard ERROR_MESSAGE, depending on CALLER and Caller’s
–– message
procedure HANDLE_USER_EXCEPTION(
ERROR_MESSAGE : in out DB_DEFINITIONS.DYNAMIC_STRING;
USER_MESSAGE : in STRING;
CALLER : in STRING);
end DB_DEFINITIONS;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
606 von/of: 662

Space Infrastructure
Formal Interface Description
607
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
607 von/of: 662
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– ABSTRACT –– CSS_DEFINITIONS
––
–– To provide commonly used types, utility subprogram(s) and exception(s).
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– KEYWORDS –– CSS_DEFINITIONS
–– Project CSS
–– ADD, section 5.3 (CSS Repository)
–– HOOD object CSS_DEFINITIONS
–– basic types, utilities
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– CONTENTS –– CSS_DEFINITIONS
––
–– Type: Package Specification
––
–– Version:
–– 2.1, 10.11.93, J.Hoyng: initial_version
–– 3.1, 21.07.94, J.Hoyng: change CTG_VERSION to CSS_VERSION, include type CSS_PORTS
–– moved CSS_SW_TYPES to CSS_TYPES
–– 3.2, 25.08.94, J.Hoyng: deleted MODEL_STRUCTURES_DIR_NAME,
–– added CSS_MODEL_PARENT, CSS_TEMPLATE_DIR inside
–– CSS_ENVIRONMENT_VARIABLES, included TEMPLATE_FILENAME
–– deleted KERNEL_LIBRARY_NAME
–– added CSS_SIM_DIR in CSS_ENVIRONMENT_VARIABLES
–– 3.3, 31.08.94, J.Hoyng: added CSS_EXECUTABLE in CSS_ENVIRONMENT_VARIABLES
–– 3.4, 08.09.94, J.Hoyng: changed CSS_ENVIRONMENT_VARIABLES
–– 3.5, 06.04.95, J.Hoyng: deleted GET_SV_DIR_NAME and MAPPING_TABLE_FILE
–– changed for CSS built1
–– 4.1, 23.08.95, J.Hoyng: many changes, build_2 version
–– 4.2. 25.08.95, J.Hoyng: changed CSS_ENVIRONMENT_VARIABLES, added CMAS_HOME
–– 4.3, 31.08.95, J.Hoyng: added VERBOSE
–– 4.4, 04.01.96, J.Hoyng: supporting now sun5
–– 4.5 1997–04–04 R.Lamb Added Free_String.
–– 5.0, 02.07.97, W.Tammen: introduced new environment_variable CSS_LOG_DATA_SET_DIR
–– 5.1, 15.08.97, W.Tammen: introduced new environment_variable CSS_KERNEL_MESSAGES
–– 5.2, 22.09.97, Th.Behrens: Introduced new definitions MAX_ARCHITECTURES,
–– ARCHITECTURE_RANGE, and ARCHITECTURE_ARRAY
–– (moved from HOST_SYTEM, which now contains links
–– to these objects).
–– 6.1, 17.12.98, J.Hoyng: added STRING_ACCESS_ARRAY, STRING_LIST
––
––
–– Purpose:
–– to provide commonly used types, utility subprogram(s) and exception(s)
––
–– External:
–– From Ada system:
–– UNCHECKED_DEALLOCATION
–– SYSTEM
––
–– From CGS:
–– NUMERIC_TYPES
––
–– From CSS:
–– DB_DEFINITIONS
–– CSS_TYPES
––

Space Infrastructure
608
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
608 von/of: 662
–– I/O:
–– –––
––
–– Machine Dependencies:
–– none
––
–– Compiler Dependencies:
–– none
––
–– UNIX signals:
–– –––
––
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
£
–– imports from Ada system:
with UNCHECKED_DEALLOCATION;
with SYSTEM;
–– imports from CGS:
with NUMERIC_TYPES;
–– imports from CSS:
with DB_DEFINITIONS;
with CSS_TYPES;
package CSS_DEFINITIONS is
type RUNTIME_ID_TYPE is new CSS_TYPES.UNSIGNED_INTEGER;
COPYRIGHT : constant STRING := ”(C) 1997 DASA –– Daimler–Benz Aerospace”;
type CSS_VERSION is
record
VERSION : CSS_TYPES.UNSIGNED_INTEGER;
ISSUE : CSS_TYPES.UNSIGNED_INTEGER;
–– REVISION : CSS_TYPES.UNSIGNED_INTEGER;
end record;
function CSS_VERSION_STRING (THE_CSS_VERSION : CSS_VERSION) return STRING;
function CURRENT_CSS_VERSION return CSS_VERSION;
–– string of the current (!) CSS_VERSION + date
–– ”CGS/CSS Version x.y from dd.mm.yy”
function CSS_VERSION_STRING return STRING;
function GET_DATE_STRING return STRING;
–––– basic types and utilities ––––––––––––––––––––––––––––––––––––––––––––––––
subtype BYTE_ARRAY is DB_DEFINITIONS.BYTE_ARRAY;
type BYTE_ARRAY_ACCESS is access BYTE_ARRAY;
procedure FREE is new UNCHECKED_DEALLOCATION (BYTE_ARRAY, BYTE_ARRAY_ACCESS);
type BYTE_STREAM is new DB_DEFINITIONS.BYTE_STREAM;
type DYNAMIC_STRING is new DB_DEFINITIONS.DYNAMIC_STRING;
type STRING_ACCESS is new DB_DEFINITIONS.STRING_ACCESS;
type STRING_ACCESS_ARRAY is array (NATURAL range ) of STRING_ACCESS;
type STRING_LIST is access CSS_DEFINITIONS.STRING_ACCESS_ARRAY;
––
–– The following definitions have been moved from HOST_SYTEM
––
MAX_ARCHITECTURES : constant := 20; –– this will hardly ever happen
subtype ARCHITECTURES_RANGE is POSITIVE range 1..MAX_ARCHITECTURES;
type ARCHITECTURE_ARRAY is
array (ARCHITECTURES_RANGE range ) of STRING_ACCESS;

Space Infrastructure
609
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
––
––
––
procedure Free_String is new UNCHECKED_DEALLOCATION (STRING, STRING_ACCESS);
LOWEST_PRIORITY: constant SYSTEM.PRIORITY := SYSTEM.PRIORITY’first + 3;
HIGHEST_PRIORITY: constant SYSTEM.PRIORITY := SYSTEM.PRIORITY’last – 7;
subtype EXECUTIVE_PRIORITY_RANGE is SYSTEM.PRIORITY range
LOWEST_PRIORITY .. HIGHEST_PRIORITY;
function DEBUG return BOOLEAN;
function VERBOSE return BOOLEAN;
function PARENT_OF_THE_MODEL_LIBRARY return STRING;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
609 von/of: 662
function KERNEL_COMPILATION_UNIT_NAME return STRING;
function TEMPLATE_FILENAME return STRING;
–– list of CSS environment variables used inside ”the Ada world”
type CSS_ENVIRONMENT_VARIABLES is
(COMMON_START,
ADALIB_DIR, CGS_ARCH, COMMON_SOURCES_DIR, CSS_ARCHITECTURES,
CSS_CLIBS, CSS_EXECUTABLE, CSS_HOME, CSS_LOG_DIR, CSS_LOG_DATA_SET_DIR,
CSS_KERNEL_MESSAGES, CSS_MODEL_PARENT, CSS_SIM_DIR,
CSS_TEMPLATE_DIR, HOME, TARGET_ARCH,
CMAS_HOME,
LM_LICENSE_FILE, –– needed for compilation
COMMON_END,
SUN_START,
SUN_END,
HP_START,
ALSYCOMP_DIR, –– needed for compilation
CSS_FAMILY, –– needed for compilation
HP_END,
HP_RT_START,
HPRTroot, –– needed for compilation
HP_RT_END
);
function GET_NAME(CSS_ENVIRONMENT_VARIABLE: CSS_ENVIRONMENT_VARIABLES) return STRING;
function GET_VALUE(CSS_ENVIRONMENT_VARIABLE: CSS_ENVIRONMENT_VARIABLES) return STRING;
type CSS_PORTS is new NATURAL range 8900 .. 8999;
–– utility operations needed by CSS_MESSAGE_COONECTION (to de/encode CSS_SW_TYPES
–– inside the socket protocol and by the db_server to de/encode CSS_SW_TYPES
–– inside MDE_INFO of a FB_IO –––––––––
function CSS_SW_TYPES_DECODING (VALUE: CSS_TYPES.CSS_SW_TYPES)
return CSS_TYPES.UNSIGNED_BYTE;
function CSS_SW_TYPES_ENCODING (VALUE: CSS_TYPES.UNSIGNED_BYTE)
return CSS_TYPES.CSS_SW_TYPES;
type IO_VALUE_KIND is (SCALAR, NON_SCALAR);
function IS_SCALAR (VALUE: CSS_TYPES.CSS_SW_TYPES) return BOOLEAN;
function EQUAL (LEFT, RIGHT : CSS_TYPES.IO_VALUE_TYPE) return BOOLEAN;
procedure COPY (TO : out CSS_TYPES.IO_VALUE_TYPE; FROM : CSS_TYPES.IO_VALUE_TYPE);
–– this procedure shall be calles either with a variable TO (with TO.SW_TYPE = NONE)
–– or TO (with TO.SW_TYPE = FROM.SW_TYPE and if FROM is a vector or matrix the size
–– of to must be the same, if not COPY_ERROR will be raised)
procedure COPY_INTO
(TO : in out CSS_TYPES.IO_VALUE_TYPE; FROM : CSS_TYPES.IO_VALUE_TYPE);

Space Infrastructure
610
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
610 von/of: 662
procedure FREE (VALUE : in out CSS_TYPES.IO_VALUE_TYPE);
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– NAT_IMAGE (Support function)
––
–– Description : This function returns the image of a natural number without blanks
––
–– Parameters:
––
–– N : the natural lnumer
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
function NAT_IMAGE (N: NATURAL) return STRING;
–––– exceptions: ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
INTERNAL_ERROR: exception;
MAPPING_ERROR : exception; –– raised by CSS_SW_TYPES_DECODING and CSS_SW_TYPES_ENCODING
COPY_ERROR : exception; –– raised by COPY and COPY_INTO
end CSS_DEFINITIONS;

Space Infrastructure
Formal Interface Description
611
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– ABSTRACT –– model_config
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– KEYWORDS –– model_config
–– Project CSS–Downsizing
––
–– HOOD object model_config
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– CONTENTS –– model_config
––
–– Type: Package Spec
––
–– Version:
–– 4.1, 23.08.95, N.Heyder: initial version
–– 4.2, 22.11.95, N.Heyder: introduced ’Packet–Info’ and ’Non–Standard–Class’
–– 4.3, 05.03.96, N.Heyder: editorial corrections within comment–lines
–– 4.4, 05.07.96, N.Heyder: changed comments
–– 4.5 1997–03–21 R.Lamb Add MEASUREMENT_64_BIT STIMULUS_64_BIT to SLOT_CLASS
–– Add CMD_1 CMD_2 to PUT_ENTRY, add default values.
–– Add COMMAND_1 COMMAND_2 functions.
–– 4.5a 1997–03–26 R.Lamb Commented out MEASUREMENT_64_BIT STIMULUS_64_BIT
–– to be completed for DOUBLE_FLOAT, later.
––
–– 4.6 1997–04–09 R.Lamb Changed comments to allow Remote Terminal range 0.30
–– 4.7 1997–05–16 R.Lamb Added SLOT_CLASS_TYPE 64 bit enumerated values.
––
–– 5.1, 01.10.97, A.Schulz: fixed uninitialized START_TYPE (crashes DB server)
––
–– Purpose:
–– Provide information about Milbus Configuration for CMAS
––
–– Machine Dependencies:
–– none
––
–– Compiler Dependencies:
–– none
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
with css_definitions;
with mps_definitions;
with calibration;
with numeric_types;
with ADT_CCSDS_PACKET;
package model_config is
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
611 von/of: 662
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– this package provides detailed model–specific information about:
––
–– – logical Milbus structures like:
–– * Bus Identification in case of multiple Milbusses,
–– * Remote Terminal Identification for a specific Milbus,
–– * Subaddress/Slot Identification for a specific Remote Terminal,
–– * Channel Identification (as offset) for a specific Subaddress/Slot,
–– * Mapping from Channel to CSS–Runtime–Identifier(RID),
–– * Sizing–Information like:
–– @ Number of all implemented Milbusses
–– @ Number of all implemented Remote Terminals for a specific Milbus
–– @ Number of all implemented Channels for a specific Remote Terminal
––
––
–– – Calibration/Decalibration:
–– * Identification of the RID’s to be calibrated
–– * Identification of the RID’s to be decalibrated
–– * Identification of the specific calibration/decalibration method per RID
––
––

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–– – Serial Packets:
–– * Mapping Serial Packets to Subaddresses?
–– * Internal structure of a Serial Packet(length, offsets, etc.)
–– * Mapping of internal packet items to RIDs
––
––
–– – External Model I/O:
–– * First Model Input
–– * Last Model Input
–– * First Model Output
–– * Last Model Output
–– * Amount of all ext. Inputs
–– * Amount of all ext. Outputs
––
––
––..............................................................................
––
––
–– (Milbus)–Configuration is specified by the following items:
––
––
–– n Milbusses
–– |
–– |
–– |
–– 31 Remote Terminals
–– |
–– |
–– |
–– 30 Slots/Subaddresses, Milbus Class
–– |
–– |
–– |
–– 16..512 Channels, CSS_RID,
––
–– 8 Channels to be added for non–standard DOUBLE_FLOAT
––
––
–– REMOTE TERMINAL valid range: 0 .. 30
––
–– SLOT valid range: 1 .. 30
––
–– CHANNEL–Ranges per SLOT:
––
–– Packet => 0 .. 0
–– 64–Bit => 0 .. 7
–– 32–Bit => 0 .. 15
–– 16–Bit => 0 .. 31
–– 8–Bit => 0 .. 63
–– 1–Bit => 0 .. 511
–– NON_STANDARD => 0 .. 511
––
––******************************************************************************
type CLIENT_TYPE is (API, ––> DB–SERVER
CMAS
);
type START_TYPE(CLIENT : CLIENT_TYPE := CMAS) is
record
case CLIENT is
when CMAS =>
MILBUS_CONFIG_FILE_PATHNAME : css_definitions.STRING_ACCESS := null;
when API =>
PATHNAME : css_definitions.STRING_ACCESS := null;
FIRST_MILBUS : NATURAL := 0;
LAST_MILBUS : NATURAL := 0;
FIRST_EXT_IO_ID : NATURAL := 0;
LAST_EXT_IO_ID : NATURAL := 0;
TOTAL_PACKETS : natural := 0; –– total number of packets
when others => null;
end case;
end record;
612
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
612 von/of: 662

Space Infrastructure
613
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
613 von/of: 662
–– to be returned by several operations
––
type RETURN_STATUS_TYPE is (OK, NOT_OK);
–– to be returned by the START–Function
––
type START_RETURN_STATUS_TYPE is (
OK,
INVALID_OPCODE_READ_FROM_FILE,
INVALID_SLOT_CLASS_ERROR,
OTHER_EXCEPTION_RAISED,
LOAD_EXCEPTION,
WRONG_MAPPING_DEFINITIONS);
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– types for the Milbus business –––––––––––––––––––––––––––––––––––––––––––––––
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
type SLOT_CLASS_TYPE is(
MEASUREMENT_64_BIT,
STIMULUS_64_BIT,
MEASUREMENT_32_BIT,
STIMULUS_32_BIT,
MEASUREMENT_16_BIT,
STIMULUS_16_BIT,
MEASUREMENT_8_BIT,
STIMULUS_8_BIT,
MEASUREMENT_1_BIT,
STIMULUS_1_BIT,
TM_PACKET,
TC_PACKET,
MEASUREMENT_NON_STANDARD,
STIMULUS_NON_STANDARD,
NOT_IN_USE);
––******************************************************************************
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–––
–– ’START’ must be called by DB–SERVER/CMAS before calling any other operation of this package!
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–––
––
–– exception:
–– LOAD_EXCEPTION
––
function START(START_UP : START_TYPE) return START_RETURN_STATUS_TYPE;
–– returns Bus–Media; like Milbus, Socket etc. in ”UPPER_CASE”
––
–– exceptions: predefined Ada exceptions
––
MAX_STRING_LENGTH : constant := 256;
––
function BUS_MEDIA return string;
–– returns Hostname for Bus–Counterpart(DMS)
––
type STRING_RECORD_TYPE is
record
TEXT : string(1..MAX_STRING_LENGTH) := (others => ’ ’);
CNT : natural := 0;
end record;
––
–– exceptions: predefined Ada exceptions
––
function DMS_HOSTNAME return STRING_RECORD_TYPE;
–– TRUE => STANDARD
–– FALSE => NON_STANDARD
––
–– exceptions: predefined Ada exceptions
––
function STANDARD_IF(BUS : natural) return boolean;
–– returns the socket port numbers MEAS_PORT + CMD_PORT for the given BUS
––

Space Infrastructure
614
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
614 von/of: 662
type SOCKET_PORT_NUMBER_RECORD_TYPE is
record
MEAS_PORT : natural;
CMD_PORT : natural;
end record;
––
–– exceptions: predefined Ada exceptions
––
function SOCKET_PORT_NUMBERS(BUS : in natural) return SOCKET_PORT_NUMBER_RECORD_TYPE;
–– returns the Class of a given Slot
––
–– exceptions: predefined Ada exceptions
––
function SLOT_CLASS(MILBUS : natural;
RT : natural;
SLOT : natural) return SLOT_CLASS_TYPE;
–– returns the CHANNEL for a given IO,SLOT,RT,MILBUS(except slot class TM_PACKET/TC_PACKET)
–– (TM/TC–Packets always start at Channel 0!)
––
–– exceptions:
–– INVALID_MILBUS_ID
–– INVALID_RT_ID
–– INVALID_SLOT_ID
–– INVALID_RID
–– INVALID_SLOT_CLASS
––
function CHANNEL(MILBUS : natural;
RT : natural;
SLOT : natural;
RID : natural) return natural;
–– returns the CSS–RUNTIME–ID for a given CHANNEL,SLOT,RT,MILBUS(except packet–members!)
–– As part of the NON_STANDARD changes, if there are more than one Runtime–Ids
–– for the given Channel,Slot,RT,Milbus then returns the first one found.
––
–– exceptions:
–– INVALID_MILBUS_ID
–– INVALID_RT_ID
–– INVALID_SLOT_ID
–– OTHER_EXCEPTION
––
function CSS_RID(MILBUS : natural;
RT : natural;
SLOT : natural;
CHANNEL : natural) return natural;
–– returns the ID of the first Milbus
––
–– exceptions: predefined Ada exceptions
––
function FIRST_MILBUS return natural;
–– returns the ID of the last Milbus
––
–– exceptions: predefined Ada exceptions
––
function LAST_MILBUS return natural;
–– returns the system–address for the Board supporting the given Milbus
––
–– exceptions: predefined Ada exceptions
––
function MILBUS_SYSTEM_ADDRESS(MILBUS_ID : natural) return natural;
–– returns the MILBUS–Identifier for the given IO
––
–– (This operation should be called only during initialization phase!)
––
–– exceptions:
–– INVALID_SLOT_CLASS
–– RID_ENTRY_NOT_FOUND
––
function MILBUS(RID : natural) return natural;
–– returns the Remote–Termninal–Identifier for the given IO
––

Space Infrastructure
615
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
615 von/of: 662
–– (This operation should be called only during initialization phase!)
––
–– exceptions:
–– INVALID_SLOT_CLASS
–– RID_ENTRY_NOT_FOUND
––
function RT(RID : natural) return natural;
–– returns the Slot–Identifier for the given IO
––
–– (This operation should be called only during initialization phase!)
––
–– exceptions:
–– INVALID_SLOT_CLASS
–– RID_ENTRY_NOT_FOUND
––
function SLOT(RID : natural) return natural;
–– returns the CHANNEL for the given IO
––
–– RIDs out of CCSDS–Packets are not supported (all packets always starting at channel 0!)
––
–– (This operation should be called only during initialization phase!)
––
–– exceptions:
–– INVALID_SLOT_CLASS
–– RID_ENTRY_NOT_FOUND
––
function CHANNEL(RID : natural) return natural;
–– This function returns the string COMMAND_1 for the given I/O
––
–– exceptions: predefined Ada exceptions
––
function COMMAND_1(RID : natural) return String;
–– This function returns the string COMMAND_2 for the given I/O
––
–– exceptions: predefined Ada exceptions
––
function COMMAND_2(RID : natural) return String;
–– This function returns the calibration/decalibration description for the given I/O
––
–– exceptions: predefined Ada exceptions
––
function CALIBRATION_INFO(RID : natural) return calibration.CALIBRATION_DECALIBRATION_TYPE;
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– CCSDS PACKET INFO only:
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– returns the total number of CCSDS–Packets
––
–– exceptions: predefined Ada exceptions
––
function GET_TOTAL_PACKETS return natural;
–– returns the CCSDS Packet’s Primary– and Secondary Header for the given RID
––
–– exceptions: predefined Ada exceptions
–– PACKET_HEADER_NOT_FOUND
––
procedure GET_PACKET_HEADERS(RID : in natural;
PRIMARY_HEADER : out ADT_CCSDS_PACKET.T_CCSDS_HEADER;
SECONDARY_HEADER : out ADT_CCSDS_PACKET.T_CCSDS_SECOND-
ARY_HEADER); –– valid only if secondary haeder flag is set!
–– returns the CCSDS Packet–ID for the given RID
––
–– exceptions: predefined Ada exceptions
–– PACKET_ID_NOT_FOUND
––
procedure GET_PACKET_ID(RID : in natural;
PACKET_ID : out ADT_CCSDS_PACKET.T_CCSDS_PACKET_ID);
–– returns the Bit_Offset for the given RID(required to substitute/retrieve the packets user
data)

Space Infrastructure
616
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
616 von/of: 662
––
–– exceptions: predefined Ada exceptions
–– BIT_OFFSET_NOT_FOUND
––
procedure GET_BIT_OFFSET(RID : in natural;
BIT_OFFSET : out natural);
–– returns the number of bits for the given RID(required to substitute/retrieve the packets
user data)
––
–– exceptions: predefined Ada exceptions
–– NUMBER_OF_BITS_NOT_FOUND
––
procedure GET_NUMBER_OF_BITS(RID : in natural;
NUMBER_OF_BITS : out natural);
–– returns the number RIDs for the given CCSDS–Packet–ID
––
–– exceptions: predefined Ada exceptions
–– PACKET_NOT_FOUND
––
function GET_NUMBER_OF_RIDS_PER_PACKET(PACKET_ID : ADT_CCSDS_PACKET.T_CCSDS_PACKET_ID)
return natural;
––******************************************************************************
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Operations provided exclusively for DB–SERVER:
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– set Milbus–Address
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– valid ’CHANNEL’–ranges(per SLOT) are:
––
–– CLASS | CHANNEL–Range
–– –––––––––––––––––––––––––––––
–– Packet => 0 .. 0
–– 64–Bit => 0 .. 7
–– 32–Bit => 0 .. 15
–– 16–Bit => 0 .. 31
–– 8–Bit => 0 .. 63
–– 1–Bit => 0 .. 511
–– NON_STANDARD => 0 .. 511
––
–– Notice that a CLASS primary defined for a SLOT must be kept constant for all
–– further PUT_ENTRY calls on that same SLOT!!!
––
–– Exceptions:
–– – ILLEGAL_MILBUS_CLASS_REDEFINITION
–– – INVALID_RT_ID
–– – INVALID_SLOT_ID
–– – CANNOT_PUT_ENTRY_ERROR
––
procedure PUT_ENTRY(
ID : in natural := 0; –– ext.I/O–CSS–RID or ’Packet–ID’
MILBUS : in natural := 0; –– Milbus–ID (0..n)
RT : in natural := 0; –– Remote Terminal (0..30)
SLOT : in natural := 1; –– Slot–ID (1..30)
CLASS : in slot_class_type := NOT_IN_USE;
CHANNEL : in natural := 0;
CMD_1 : in string := ””;
CMD_2 : in string := ””);
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– set CCSDS Packet Header (this must be called before setting the packet’s ”User Data”!)
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– Exceptions:
–– INVALID_SLOT_CLASS
––
procedure PUT_PACKET_HEADER(PACKET_ID : natural; –– CCSDS–Packet–ID
PRIMARY_HEADER : ADT_CCSDS_PACKET.T_CCSDS_HEADER;
SECONDARY_HEADER : ADT_CCSDS_PACKET.T_CCSDS_SECONDARY_HEADER; ––
valid only if secondary haeder flag is set!

Space Infrastructure
617
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
617 von/of: 662
MILBUS : natural; –– Milbus–ID (0..n)
RT : natural; –– Remote Terminal (0..30)
SLOT : natural; –– Slot–ID (1..30)
CLASS : slot_class_type; –– (TM or TC only!)
TOTAL_RIDS : natural);
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– set Packet User Data (”Packet Header” must have been set before!)
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– Exceptions:
–– CANNOT_PUT_ENTRY_ERROR
–– BIT_LENGTH_EXCEEDED
––
procedure PUT_PACKET_USER_DATA(PACKET_ID : natural; –– CCSDS–PACKET–ID
RID : natural; –– CSS–Runtime–Identifier
BIT_OFFSET : natural;
BIT_LENGTH : natural); –– max. 32 Bit due to CSS–Types!
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– Set the Calibration/Decalibration description for a given CSS–RID
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– sets default calibration for
–– raw/engineering types: integer32, unsigned_integer32, real, long_real
––
–– exception:
–– (language predefined exceptions)
––
procedure PUT_CONSTANT_CALIBRATION(
RID : in NATURAL;
RAW_VALUE_DESCRIPTOR : in mps_definitions.T_SW_TYPE_DESCRIPTOR;
ENG_VALUE_DESCRIPTOR : in mps_definitions.T_SW_TYPE_DESCRIPTOR);
procedure PUT_POLYNOM_CALIBRATION(
RID : in NATURAL;
COEFFICIENTS : in calibration.POLYNOM_COEFFICIENTS;
RAW_VALUE_DESCRIPTOR : in mps_definitions.T_SW_TYPE_DESCRIPTOR;
ENG_VALUE_DESCRIPTOR : in mps_definitions.T_SW_TYPE_DESCRIPTOR);
procedure PUT_POINT_PAIR_CALIBRATION(
RID : in NATURAL;
POINT_PAIRS : in calibration.ANALOG_POINT_PAIR_ARRAY;
RAW_VALUE_DESCRIPTOR : in mps_definitions.T_SW_TYPE_DESCRIPTOR;
ENG_VALUE_DESCRIPTOR : in mps_definitions.T_SW_TYPE_DESCRIPTOR);
procedure PUT_DISCRETE_CALIBRATION(
RID : in NATURAL;
POINT_PAIRS : in calibration.DISCRETE_POINT_PAIR_ARRAY;
RAW_VALUE_TYPE : in mps_definitions.T_SW_TYPE);
procedure PUT_BOOLEAN_CALIBRATION(
RID : in NATURAL;
BY_TRUE : in numeric_types.BIT;
BY_FALSE : in numeric_types.BIT);
–––––––
procedure PUT_CONSTANT_DECALIBRATION(
RID : in NATURAL;
RAW_VALUE_DESCRIPTOR : in mps_definitions.T_SW_TYPE_DESCRIPTOR;
ENG_VALUE_DESCRIPTOR : in mps_definitions.T_SW_TYPE_DESCRIPTOR);
procedure PUT_POLYNOM_DECALIBRATION(
RID : in NATURAL;
COEFFICIENTS : in calibration.POLYNOM_COEFFICIENTS;
RAW_VALUE_DESCRIPTOR : in mps_definitions.T_SW_TYPE_DESCRIPTOR;
ENG_VALUE_DESCRIPTOR : in mps_definitions.T_SW_TYPE_DESCRIPTOR);
procedure PUT_POINT_PAIR_DECALIBRATION(
RID : in NATURAL;
POINT_PAIRS : in calibration.ANALOG_POINT_PAIR_ARRAY;
RAW_VALUE_DESCRIPTOR : in mps_definitions.T_SW_TYPE_DESCRIPTOR;
ENG_VALUE_DESCRIPTOR : in mps_definitions.T_SW_TYPE_DESCRIPTOR);
procedure PUT_DISCRETE_DECALIBRATION(
RID : in NATURAL;
POINT_PAIRS : in calibration.DISCRETE_POINT_PAIR_ARRAY;
RAW_VALUE_TYPE : in mps_definitions.T_SW_TYPE);

Space Infrastructure
618
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
procedure PUT_BOOLEAN_DECALIBRATION(
RID : in NATURAL;
BY_TRUE : in numeric_types.BIT;
BY_FALSE : in numeric_types.BIT);
–– Store the complete model information into file with the Unix–Path as
–– defined by the previous START–Operation
––
–– !!!!!! This should be the final call by DB–SERVER !!!!!!!
––
function STORE return RETURN_STATUS_TYPE;
INVALID_SW_TYPE,
INVALID_RID,
INVALID_MILBUS_ID,
INVALID_RT_ID,
INVALID_SLOT_ID,
ILLEGAL_MILBUS_CLASS_REDEFINITION,
OTHER_EXCEPTION,
RID_ENTRY_NOT_FOUND,
PACKET_HEADER_NOT_FOUND,
PACKET_ID_NOT_FOUND,
BIT_OFFSET_NOT_FOUND,
NUMBER_OF_BITS_NOT_FOUND,
PACKET_NOT_FOUND,
LOAD_ERROR,
INVALID_SLOT_CLASS,
GET_SW_TYPE_ERROR,
FIRST_INPUT_ERROR,
LAST_INPUT_ERROR,
FIRST_OUTPUT_ERROR,
LAST_OUTPUT_ERROR,
CANNOT_PUT_ENTRY_ERROR,
MAX_LENGTH_OF_INPUT_BYTE_STREAM_ERROR,
BIT_LENGTH_EXCEEDED,
MAX_LENGTH_OF_OUTPUT_BYTE_STREAM_ERROR : exception;
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
end model_config;
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
618 von/of: 662

Space Infrastructure
Formal Interface Description
619
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– ABSTRACT –– MAPPING_TABLE
––
–– Purpose:
––
–– This package includes all routines for access to a model’s mapping table
–– file, i.e. the handling of the different sections and the format of the
–– entry lines.
––
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– KEYWORDS –– MAPPING_TABLE
–– Project CSS
–– DDD section 5.2.10.5
–– HOOD object MAPPING_TABLE
––
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– CONTENTS –– MAPPING_TABLE
––
–– Type: package spec
––
–– Version:
–– 4.1, 23.08.95, A.Schulz: initial version (extracted from LOGGER)
–– 5.0, 25.06.97, W.Tammen, introduced modifications used for Central Logging
–– changed parameter profile of PUT_ENTRY
–– introduced new procedure GET_ENTRY
–– introduced new procedure OPEN_TABLE
––
–– Purpose:
––
–– This package includes all routines for access to a model’s mapping table
–– file, i.e. the handling of the different sections and the format of the
–– entry lines.
––
–– External:
––
–– From CSS:
––
–– MODEL_STATE, (MODEL_ID_TYPE)
––
–– DB_DEFINITIONS, (SID,
–– SUBITEM_ID)
––
–– CSS_DEFINITIONS, (STRING_ACCESS)
––
RUNTIME_ID_TYPE)
––
––
–– I/O:
–– ––
––
–– Machine Dependencies:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
619 von/of: 662

Space Infrastructure
620
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–– none
––
–– Compiler Dependencies:
–– none
––
–– UNIX signals:
–– ––
––
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
£
–– imports from CSS
with DB_DEFINITIONS,
CSS_DEFINITIONS;
package MAPPING_TABLE is
–––––types––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– The following enumeration type is used to return to the caller of
–– GET_ENTRY the current section of the mapping table resp. to
–– specify the section for PUT_ENTRY and SELECT_SECTION.
type MAPPING_SECTION is
(NO_SECTION, –– before opened (internal use only)
SENDERS_SECTION, –– current entry is sender of a value
RECEIVERS_SECTION, –– current entry is receiver of a value
FBS_SECTION, –– current entry is function block
END_SECTION);
–– no more entries available
–––––exceptions–––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– The following exception will be raised if
–– a) OPEN_TABLE fails to open the mapping table
–– b) no table has been opened via OPEN_TABLE when calling
–– SELECT_SECTION or GET_ENTRY
NO_MAPPING_TABLE_FOUND : exception;
–– The following exception will be raised if an error occurs
–– when scanning a mapping table line
ENTRY_FORMAT_ERROR : exception;
–– support operations ––––––––––––––––––––––––––––––––––––––––––––––––––
–– This function returns the path to the UNIX file where
–– the architecture specific executable for the specified model
–– is stored.
–– It will raise DB_DEFINITIONS.EMPTY_ROOT_PATH if the
–– MODEL_UNIX_PATH in the MODEL_ID is empty, i.e. hasn’t been
–– initialised.
function GET_MAPPING_TABLE_NAME
(MODEL : in DB_DEFINITIONS.MODEL_ID;
ARCHITECTURE : in STRING) return STRING;
–– reading operations ––––––––––––––––––––––––––––––––––––––––––––––––––
–– The following procedure opens the Mapping Table File for the
–– specified model and architecture for reading.
–– A following call to GET_ENTRY will return the first entry.
–– This procedure must be called before reading the first entry via
–– GET_ENTRY or selecting a special section via SELECT_SECTION.
–– NO_MAPPING_TABLE_FOUND will be raised if no mapping table exists
–– for the specified Model and architecture.
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
620 von/of: 662

Space Infrastructure
621
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
procedure OPEN_TABLE(
MODEL_ID : in out DB_DEFINITIONS.MODEL_ID;
ARCHITECTURE : in STRING);
–– The following procedure opens the Mapping Table File in case
–– the filename is available instead of a model id (e.g. logger_be)
procedure OPEN_TABLE(MAPTAB_FILE_NAME: in STRING);
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– The following procedure positions the cursor such that the
–– next call to GET_ENTRY will return the first entry of the next
–– section of the specified type, resp. the next entry if a
–– section of the specified type is already active.
–– If no (more) such section is found, NO_SECTION is returned,
–– otherwise the specified section type.
–– NO_MAPPING_TABLE_FOUND will be raised if OPEN_TABLE hasn’t been
–– called before.
procedure GET_SELECTED_SECTION(
SECTION : in out MAPPING_SECTION );
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– The following procedure returns the next mapping table entry, i.e.
–– its SECTION, SID, IO_ID (invalid, =0 if in FBS_SECTION), RUNTIME_ID,
–– and PATHNAME. Additionally, the engineering unit, onboard reference SID
–– and the pathname of the onboard reference are returned, The latter
–– values are needed for central logging purposes. In case of model internal
–– I/O’s engineering unit is set to ””, OB_REF_SID is set to 0 and the pathname
–– of the OB reference is set to \. If NO_SECTION is returned, no more entries
–– are available and the remaining returned values are invalid.
–– NO_MAPPING_TABLE_FOUND will be raised if OPEN_TABLE hasn’t been
–– called before.
procedure GET_ENTRY(
SECTION : out MAPPING_SECTION;
SID : out DB_DEFINITIONS.SID;
IO_ID : out DB_DEFINITIONS.SUBITEM_ID;
RUNTIME_ID : out CSS_DEFINITIONS.RUNTIME_ID_TYPE;
PATHNAME : out CSS_DEFINITIONS.STRING_ACCESS;
ENGINEERING_UNIT: out CSS_DEFINITIONS.STRING_ACCESS;
OB_REF_SID : out DB_DEFINITIONS.SID;
OB_REF_PATHNAME : out CSS_DEFINITIONS.STRING_ACCESS);
procedure GET_ENTRY(
SECTION : out MAPPING_SECTION;
SID : out DB_DEFINITIONS.SID;
IO_ID : out DB_DEFINITIONS.SUBITEM_ID;
RUNTIME_ID : out CSS_DEFINITIONS.RUNTIME_ID_TYPE;
PATHNAME : out CSS_DEFINITIONS.STRING_ACCESS);
–– writing operations ––––––––––––––––––––––––––––––––––––––––––––––––––
–– The following procedure creates a new, empty Mapping Table File for
–– the specified model and architecture for writing.
–– This procedure must be called before writing the first entry via
–– PUT_ENTRY.
–– NO_MAPPING_TABLE_FOUND will be raised if no mapping table could be
–– created for the specified Model and architecture.
procedure CREATE_TABLE(
MODEL_ID : in out DB_DEFINITIONS.MODEL_ID;
ARCHITECTURE : in STRING);
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
621 von/of: 662

Space Infrastructure
622
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– The following procedure marks the beginning of a new section
–– in the mapping table file, except when SECTION is the same
–– as before.
–– NO_MAPPING_TABLE_FOUND will be raised if CREATE_TABLE hasn’t been
–– called before.
procedure PUT_NEW_SECTION(SECTION : in MAPPING_SECTION );
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– The following procedure appends a new entry, i.e. SID, IO_ID (ignored
–– if in FBS_SECTION), RUNTIME_ID and PATHNAME to the currently opened
–– (via CREATE_TABLE) mapping table file, for the currently active
–– section (via NEW_SECTION).
–– The values for engineering_unit, ob_ref_sid and ob_ref_pathname are
–– ignored, too, in case of FBS_SECTION. They are used for central logging
–– purposes.
–– NO_MAPPING_TABLE_FOUND will be raised if CREATE_TABLE hasn’t been
–– called before.
procedure PUT_ENTRY(
SID : in DB_DEFINITIONS.SID;
IO_ID : in DB_DEFINITIONS.SUBITEM_ID;
RUNTIME_ID : in CSS_DEFINITIONS.RUNTIME_ID_TYPE;
PATHNAME : in STRING;
ENGINEERING_UNIT: in STRING;
OB_REF_SID : in DB_DEFINITIONS.SID;
OB_REF_PATHNAME : in STRING);
–– closing operations ––––––––––––––––––––––––––––––––––––––––––––––––––
–– The following procedure closes any currently opened Mapping Table File.
–– No exception will be raised in the case that no file is opened.
procedure CLOSE_TABLE;
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
end MAPPING_TABLE;
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
622 von/of: 662

Space Infrastructure
Formal Interface Description
623
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– ABSTRACT –– CSS_MESSAGE_CONNECTION
––
–– This package provides socket connections for the CSS specific
–– message communication protocol.
–– Each message consists of a mandatory 12–byte header (4 byte opcode,
–– 4 byte opcode extension, 4 bytes total message length in longwords)
–– followed by an optional data field of arbitrary length (but padded
–– to a longword boundary, since the total message length (header + data)
–– is measured in longwords, see above).
–– A special case of communication is read/write from/to persistent
–– media (files), which can be characterized as ”offline” communication.
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– KEYWORDS –– CSS_MESSAGE_CONNECTION
–– Project CSS
–– ADD section 5.3.11
–– HOOD object CSS_MESSAGE_CONNECTION
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
––
–– CONTENTS –– CSS_MESSAGE_CONNECTION
––
–– Type: Package specification
––
–– Version:
–– 2.1, 10.11.93, Th. Kendelbacher: initial version
–– 3.1, 21.07.94, J. Hoyng: changed CSS_TYPES.DURATION to DURATION
–– 3.2, 06.04.95: J. Hoyng: implemented new protocol
–– 4.1, 08.10.96: A.Schulz: SPR–2713 : added support for CDU test versions
–– (added procedures to PUT/GET library versions)
–– 25.08.96: Th. Behrens: Added new procedures PUT and GET for exchange
–– of messages between CMAS DB Server and CSS DB
–– Server
–– 22.09.97: Th. Behrens: Replaced links to HOST_SYSTEM by links to
–– CSS_DEFINITIONS.
–– 03.11.97: A.Schulz : System_Environment added to GET_FROM_FILE
–– parameters
––
–– Purpose:
–– message–oriented connection of processes
––
–– Function:
–– communication via bytestream–like OS communication channels
––
–– External:
–– From Ada system:
–– SYSTEM
––
–– From CGS:
–– NUMERIC_TYPES
––
–– From CSS:
–– CSS_DEFINITIONS
–– CSS_TYPES
–– UNIX_INTERFACE
––
–– I/O:
–– either via UNIX sockets, via stdin/stdout pipes or via files,
–– depending on OPEN_CONNECTION call
––
–– Machine Dependencies:
–– –––
––
–– Compiler Dependencies:
–– –––
––
–– UNIX signals:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
623 von/of: 662

Space Infrastructure
624
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–– SIGPIPE (handler included)
–– SIGTERM only while in ACCEPT_LOOP (handler included)
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– imports from Ada system:
with SYSTEM;
–– imports from CGS:
with NUMERIC_TYPES;
–– imports from CSS:
with CSS_DEFINITIONS, CSS_TYPES;
with UNIX_INTERFACE;
with DB_DEFINITIONS;
with CSS_TYPES;
package CSS_MESSAGE_CONNECTION is
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–– CAUTION!!! ––
–– The procedures and data structures in this package are currently not ––
–– protected against concurrent accesses, so make sure that there is at ––
–– most one task using each connection. Thank you for your attention. ––
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
–––– abstract MESSAGE type for the general CSS message format –––––––––––––––––
type MESSAGE is limited private;
–– General note: The message length field as required by the protocol is
–– automatically filled by the WRITE operation depending on the current
–– data length (as set by a previous READ or PUT_xyz operation).
procedure INITIALIZE
(THE_MESSAGE: in out MESSAGE;
OPCODE: CSS_TYPES.UNSIGNED_INTEGER := 0;
DETAIL: CSS_TYPES.SIGNED_INTEGER := 0);
–– this procedure also empties the data field of MESSAGE (!)
function OPCODE (THE_MESSAGE: MESSAGE) return CSS_TYPES.UNSIGNED_INTEGER;
function DETAIL (THE_MESSAGE: MESSAGE) return CSS_TYPES.SIGNED_INTEGER;
procedure RESET_POSITION (THE_MESSAGE: in out MESSAGE);
–– reset the read–/write–position for the following procedures
–– to the initial position (start of data field).
–– The data length is set to the current write position after each
–– PUT_xyz operation.
procedure GET
(THE_MESSAGE: in out MESSAGE; VALUE: out CSS_TYPES.CSS_SW_TYPES);
–– GET operations for (scalar) CSS_TYPES:
procedure GET
(THE_MESSAGE: in out MESSAGE; VALUE: out CSS_TYPES.SIGNED_BYTE);
procedure GET
(THE_MESSAGE: in out MESSAGE; VALUE: out CSS_TYPES.UNSIGNED_BYTE);
procedure GET
(THE_MESSAGE: in out MESSAGE; VALUE: out CSS_TYPES.SIGNED_SHORT_WORD);
procedure GET
(THE_MESSAGE: in out MESSAGE; VALUE: out CSS_TYPES.UNSIGNED_SHORT_WORD);
procedure GET
(THE_MESSAGE: in out MESSAGE; VALUE: out CSS_TYPES.SIGNED_INTEGER);
procedure GET
(THE_MESSAGE: in out MESSAGE; VALUE: out CSS_TYPES.UNSIGNED_INTEGER);
procedure GET
(THE_MESSAGE: in out MESSAGE; VALUE: out CSS_TYPES.REAL);
procedure GET
(THE_MESSAGE: in out MESSAGE; VALUE: out CSS_TYPES.LONG_REAL);
procedure GET
(THE_MESSAGE: in out MESSAGE; VALUE: out CSS_TYPES.COMPLEX);
procedure GET
(THE_MESSAGE: in out MESSAGE; VALUE: out BOOLEAN);
procedure GET
(THE_MESSAGE: in out MESSAGE; VALUE: out CSS_TYPES.TIME);
procedure GET
(THE_MESSAGE: in out MESSAGE; VALUE: out CSS_TYPES.LONG_DURATION);
procedure GET
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
624 von/of: 662

Space Infrastructure
625
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
625 von/of: 662
(THE_MESSAGE: in out MESSAGE; VALUE: out CSS_TYPES.STATE_CODE);
procedure GET
(THE_MESSAGE: in out MESSAGE; VALUE: out CSS_TYPES.PULSE);
procedure GET
(THE_MESSAGE: in out MESSAGE; VALUE: out CSS_TYPES.BURST_PULSE);
–– GET operations for (composite) CSS_TYPES:
procedure GET
(THE_MESSAGE: in out MESSAGE; VALUE: out CSS_TYPES.UNSIGNED_BYTE_VECTOR);
procedure GET
(THE_MESSAGE: in out MESSAGE; VALUE: out CSS_TYPES.SIGNED_BYTE_VECTOR);
procedure GET
(THE_MESSAGE: in out MESSAGE; VALUE: out CSS_TYPES.UNSIGNED_SHORT_WORD_VECTOR);
procedure GET
(THE_MESSAGE: in out MESSAGE; VALUE: out CSS_TYPES.SIGNED_SHORT_WORD_VECTOR);
procedure GET
(THE_MESSAGE: in out MESSAGE; VALUE: out CSS_TYPES.UNSIGNED_INTEGER_VECTOR);
procedure GET
(THE_MESSAGE: in out MESSAGE; VALUE: out CSS_TYPES.SIGNED_INTEGER_VECTOR);
procedure GET
(THE_MESSAGE: in out MESSAGE; VALUE: out CSS_TYPES.REAL_VECTOR);
procedure GET
(THE_MESSAGE: in out MESSAGE; VALUE: out CSS_TYPES.LONG_REAL_VECTOR);
procedure GET
(THE_MESSAGE: in out MESSAGE; VALUE: out CSS_TYPES.COMPLEX_VECTOR);
procedure GET
(THE_MESSAGE: in out MESSAGE; VALUE: out CSS_TYPES.BOOLEAN_VECTOR);
procedure GET
(THE_MESSAGE: in out MESSAGE; VALUE: out CSS_TYPES.UNSIGNED_BYTE_MATRIX);
procedure GET
(THE_MESSAGE: in out MESSAGE; VALUE: out CSS_TYPES.SIGNED_BYTE_MATRIX);
procedure GET
(THE_MESSAGE: in out MESSAGE; VALUE: out CSS_TYPES.UNSIGNED_SHORT_WORD_MATRIX);
procedure GET
(THE_MESSAGE: in out MESSAGE; VALUE: out CSS_TYPES.SIGNED_SHORT_WORD_MATRIX);
procedure GET
(THE_MESSAGE: in out MESSAGE; VALUE: out CSS_TYPES.UNSIGNED_INTEGER_MATRIX);
procedure GET
(THE_MESSAGE: in out MESSAGE; VALUE: out CSS_TYPES.SIGNED_INTEGER_MATRIX);
procedure GET
(THE_MESSAGE: in out MESSAGE; VALUE: out CSS_TYPES.REAL_MATRIX);
procedure GET
(THE_MESSAGE: in out MESSAGE; VALUE: out CSS_TYPES.LONG_REAL_MATRIX);
procedure GET
(THE_MESSAGE: in out MESSAGE; VALUE: out CSS_TYPES.COMPLEX_MATRIX);
procedure GET
(THE_MESSAGE: in out MESSAGE; VALUE: out CSS_TYPES.BOOLEAN_MATRIX);
procedure GET
(THE_MESSAGE: in out MESSAGE; VALUE: out CSS_TYPES.BYTE_STREAM);
–– GET operations for other types:
procedure GET
(THE_MESSAGE: in out MESSAGE; VALUE: out CSS_DEFINITIONS.STRING_ACCESS);
procedure GET
(THE_MESSAGE: in out MESSAGE; VALUE: out CSS_TYPES.STRING_ACCESS);
procedure GET
(THE_MESSAGE: in out MESSAGE;
BUFFER : out STRING;
CHARS_READ : out NATURAL);
–– gets a string from MESSAGE, copies it into BUFFER and returns the
–– number of valid chars in BUFFER (rest of BUFFER is unchanged).
–– Raises BAD_LENGTH if BUFFER is insufficient.
procedure GET
(THE_MESSAGE: in out MESSAGE; VALUE: in out CSS_DEFINITIONS.DYNAMIC_STRING);
–– VALUE must be in out due to RM 7.4.4(4)
procedure GET
(THE_MESSAGE: in out MESSAGE; VALUE: out CSS_DEFINITIONS.BYTE_ARRAY_ACCESS);
procedure GET
(THE_MESSAGE: in out MESSAGE;
BUFFER : in out CSS_DEFINITIONS.BYTE_ARRAY;
CHARS_READ : out NATURAL);
–– gets a byte array from MESSAGE, copies it into BUFFER and returns the

Space Infrastructure
626
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
626 von/of: 662
–– number of valid bytes in BUFER.
–– Raises BAD_LENGTH if BUFFER is insufficient.
procedure GET
(THE_MESSAGE: in out MESSAGE; VALUE: in out CSS_DEFINITIONS.BYTE_STREAM);
–– VALUE must be in out due to RM 7.4.4(4)
–– GET operations for library version related information:
procedure GET
(THE_MESSAGE: in out CSS_MESSAGE_CONNECTION.MESSAGE;
VERSION : out DB_DEFINITIONS.VERSION_RECORD);
procedure GET
(THE_MESSAGE: in out CSS_MESSAGE_CONNECTION.MESSAGE;
LIB_VERSION: out DB_DEFINITIONS.LIBRARY_VERSION);
procedure GET
(THE_MESSAGE: in out MESSAGE; VALUE: out CSS_TYPES.IO_VALUE_TYPE);
–– This procedure shall be used, if the caller ”knows” the SW_TYPE and the size
–– of VALUE; this means if VALUE.SW_TYPE and/or the size of VALUE is wrong, if VALUE is
–– vector or matrix, then GET_INTO_ERROR will be raised
procedure GET_INTO
(THE_MESSAGE: in out MESSAGE; VALUE: in out CSS_TYPES.IO_VALUE_TYPE);
GET_INTO_ERROR: exception;
procedure PUT
(THE_MESSAGE: in out MESSAGE; VALUE: in CSS_TYPES.CSS_SW_TYPES);
–– PUT operations for (scalar) CSS_TYPES:
procedure PUT
(THE_MESSAGE: in out MESSAGE; VALUE: in CSS_TYPES.SIGNED_BYTE);
procedure PUT
(THE_MESSAGE: in out MESSAGE; VALUE: in CSS_TYPES.UNSIGNED_BYTE);
procedure PUT
(THE_MESSAGE: in out MESSAGE; VALUE: in CSS_TYPES.SIGNED_SHORT_WORD);
procedure PUT
(THE_MESSAGE: in out MESSAGE; VALUE: in CSS_TYPES.UNSIGNED_SHORT_WORD);
procedure PUT
(THE_MESSAGE: in out MESSAGE; VALUE: in CSS_TYPES.SIGNED_INTEGER);
procedure PUT
(THE_MESSAGE: in out MESSAGE; VALUE: in CSS_TYPES.UNSIGNED_INTEGER);
procedure PUT
(THE_MESSAGE: in out MESSAGE; VALUE: in CSS_TYPES.REAL);
procedure PUT
(THE_MESSAGE: in out MESSAGE; VALUE: in CSS_TYPES.LONG_REAL);
procedure PUT
(THE_MESSAGE: in out MESSAGE; VALUE: in CSS_TYPES.COMPLEX);
procedure PUT
(THE_MESSAGE: in out MESSAGE; VALUE: in BOOLEAN);
procedure PUT
(THE_MESSAGE: in out MESSAGE; VALUE: in CSS_TYPES.TIME);
procedure PUT
(THE_MESSAGE: in out MESSAGE; VALUE: in CSS_TYPES.LONG_DURATION);
procedure PUT
(THE_MESSAGE: in out MESSAGE; VALUE: in CSS_TYPES.STATE_CODE);
procedure PUT
(THE_MESSAGE: in out MESSAGE; VALUE: in CSS_TYPES.PULSE);
procedure PUT
(THE_MESSAGE: in out MESSAGE; VALUE: in CSS_TYPES.BURST_PULSE);
–– PUT operations for (composite) CSS_TYPES:
procedure PUT
(THE_MESSAGE: in out MESSAGE; VALUE: in CSS_TYPES.UNSIGNED_BYTE_VECTOR);
procedure PUT
(THE_MESSAGE: in out MESSAGE; VALUE: in CSS_TYPES.SIGNED_BYTE_VECTOR);
procedure PUT
(THE_MESSAGE: in out MESSAGE; VALUE: in CSS_TYPES.UNSIGNED_SHORT_WORD_VECTOR);
procedure PUT
(THE_MESSAGE: in out MESSAGE; VALUE: in CSS_TYPES.SIGNED_SHORT_WORD_VECTOR);
procedure PUT
(THE_MESSAGE: in out MESSAGE; VALUE: in CSS_TYPES.UNSIGNED_INTEGER_VECTOR);
procedure PUT
(THE_MESSAGE: in out MESSAGE; VALUE: in CSS_TYPES.SIGNED_INTEGER_VECTOR);
procedure PUT

Space Infrastructure
627
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
627 von/of: 662
(THE_MESSAGE: in out MESSAGE; VALUE: in CSS_TYPES.REAL_VECTOR);
procedure PUT
(THE_MESSAGE: in out MESSAGE; VALUE: in CSS_TYPES.LONG_REAL_VECTOR);
procedure PUT
(THE_MESSAGE: in out MESSAGE; VALUE: in CSS_TYPES.COMPLEX_VECTOR);
procedure PUT
(THE_MESSAGE: in out MESSAGE; VALUE: in CSS_TYPES.BOOLEAN_VECTOR);
procedure PUT
(THE_MESSAGE: in out MESSAGE; VALUE: in CSS_TYPES.UNSIGNED_BYTE_MATRIX);
procedure PUT
(THE_MESSAGE: in out MESSAGE; VALUE: in CSS_TYPES.SIGNED_BYTE_MATRIX);
procedure PUT
(THE_MESSAGE: in out MESSAGE; VALUE: in CSS_TYPES.UNSIGNED_SHORT_WORD_MATRIX);
procedure PUT
(THE_MESSAGE: in out MESSAGE; VALUE: in CSS_TYPES.SIGNED_SHORT_WORD_MATRIX);
procedure PUT
(THE_MESSAGE: in out MESSAGE; VALUE: in CSS_TYPES.UNSIGNED_INTEGER_MATRIX);
procedure PUT
(THE_MESSAGE: in out MESSAGE; VALUE: in CSS_TYPES.SIGNED_INTEGER_MATRIX);
procedure PUT
(THE_MESSAGE: in out MESSAGE; VALUE: in CSS_TYPES.REAL_MATRIX);
procedure PUT
(THE_MESSAGE: in out MESSAGE; VALUE: in CSS_TYPES.LONG_REAL_MATRIX);
procedure PUT
(THE_MESSAGE: in out MESSAGE; VALUE: in CSS_TYPES.COMPLEX_MATRIX);
procedure PUT
(THE_MESSAGE: in out MESSAGE; VALUE: in CSS_TYPES.BOOLEAN_MATRIX);
procedure PUT
(THE_MESSAGE: in out MESSAGE; VALUE: in CSS_TYPES.BYTE_STREAM);
–– PUT operations for other types:
procedure PUT
(THE_MESSAGE: in out MESSAGE; VALUE: in CSS_DEFINITIONS.STRING_ACCESS);
procedure PUT
(THE_MESSAGE: in out MESSAGE; VALUE: in STRING);
procedure PUT
(THE_MESSAGE: in out MESSAGE; VALUE: in CSS_DEFINITIONS.DYNAMIC_STRING);
procedure PUT
(THE_MESSAGE: in out MESSAGE; VALUE: in CSS_DEFINITIONS.BYTE_ARRAY_ACCESS);
procedure PUT
(THE_MESSAGE: in out MESSAGE; VALUE: in CSS_DEFINITIONS.BYTE_ARRAY);
procedure PUT
(THE_MESSAGE: in out MESSAGE; VALUE: in CSS_DEFINITIONS.BYTE_STREAM);
procedure PUT
(THE_MESSAGE: in out MESSAGE; VALUE: in CSS_TYPES.IO_VALUE_TYPE);
–– PUT operations for library version related information:
procedure PUT
(THE_MESSAGE: in out CSS_MESSAGE_CONNECTION.MESSAGE;
VERSION : in DB_DEFINITIONS.VERSION_RECORD);
procedure PUT
(THE_MESSAGE: in out CSS_MESSAGE_CONNECTION.MESSAGE;
LIB_VERSION: in DB_DEFINITIONS.LIBRARY_VERSION);
––– deallocation:
procedure FREE (THE_MESSAGE: in out MESSAGE);
–– deallocate dynamic storage space allocated for a message
–– (is automatically reallocated when this message is subsequently used
–– in PUT_xyz calls)
–– Only necessary before a MESSAGE variable becomes inaccessible,
–– not before every READ/WRITE operation!
–––– connection related types –––––––––––––––––––––––––––––––––––––––––––––––––
type CONNECTION_MODE is
(CLIENT, SERVER, –– for sockets (online)
PIPE_READER, PIPE_WRITER, –– for pipes (on/offline)
PERSISTENT_READER, PERSISTENT_WRITER); –– for files (offline)
type CONNECTION (MODE: CONNECTION_MODE) is limited private;
subtype CLIENT_CONNECTION is CONNECTION (MODE => CLIENT);
subtype SERVER_CONNECTION is CONNECTION (MODE => SERVER);

Space Infrastructure
628
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
subtype READ_PIPE is CONNECTION (MODE => PIPE_READER);
subtype WRITE_PIPE is CONNECTION (MODE => PIPE_WRITER);
subtype READ_PERSISTENT is CONNECTION (MODE => PERSISTENT_READER);
subtype WRITE_PERSISTENT is CONNECTION (MODE => PERSISTENT_WRITER);
–– Note that, in contrast to sockets, pipes and especially the
–– offline communication represented by persistents are unidirectional
–– by their very nature.
–– Hence, inappropriate operations (READ–operations on WRITERs and
–– WRITE–operations on READERs) will raise MODE_ERROR (see exceptions).
–––– connection creation ––––––––––––––––––––––––––––––––––––––––––––––––––––––
–––– socket oriented online connections –––––––––––––––––––––––––––––––––––
–––– based on symbolic service names:
procedure OPEN_SERVER_CONNECTION
(THE_CONNECTION: in out SERVER_CONNECTION; SERVICE: STRING;
BUFFERING: BOOLEAN := TRUE; NON_BLOCKING: BOOLEAN := FALSE);
procedure OPEN_CLIENT_CONNECTION
(THE_CONNECTION: in out CLIENT_CONNECTION; SERVICE, HOSTNAME: STRING;
BUFFERING: BOOLEAN := TRUE; NON_BLOCKING: BOOLEAN := FALSE);
–––– based on port numbers:
procedure OPEN_SERVER_CONNECTION
(THE_CONNECTION: in out SERVER_CONNECTION; PORT: NATURAL;
BUFFERING: BOOLEAN := TRUE; NON_BLOCKING: BOOLEAN := FALSE);
procedure OPEN_CLIENT_CONNECTION
(THE_CONNECTION: in out CLIENT_CONNECTION; PORT: NATURAL; HOSTNAME: STRING;
BUFFERING: BOOLEAN := TRUE; NON_BLOCKING: BOOLEAN := FALSE);
–– NOTES:
–– If BUFFERING = FALSE, then Flush is a no–op.
–– If BUFFERING = TRUE, then an actual transmission will only take place
–– on an explicit or implicit FLUSH (several WRITE messages may be collected
–– and transmitted in a larger block to save net transactions and overhead).
–– If NON_BLOCKING = FALSE, then READ and WRITE calls may lead to the
–– suspension of the UNIX process –– nice if you have just one client
–– at a time to serve, not so nice otherwise.
–– If NON_BLOCKING = TRUE, then no suspension of the UNIX process
–– will ever occur, so that other Ada tasks have a chance to run; on the
–– other hand, this involves polling. The decision is up to you.
–– NO MESSAGES EXCEEDING A TOTAL LENGTH OF 4096 BYTES (HEADER + DATA)
–– CAN BE READ FROM NON–BLOCKING SOCKETS!!!
–––– pipe oriented online connections –––––––––––––––––––––––––––––––––––––
procedure OPEN_READING_CONNECTION
(THE_CONNECTION: in out READ_PIPE; NON_BLOCKING: BOOLEAN := FALSE);
–– open a connection reading from the UNIX stdin channel
procedure OPEN_WRITING_CONNECTION
(THE_CONNECTION: in out WRITE_PIPE;
BUFFERING: BOOLEAN := TRUE; NON_BLOCKING: BOOLEAN := FALSE);
–– open a connection writing to the UNIX stdout channel
–––– persistent media (offline connections) –––––––––––––––––––––––––––––––
–– These operations may raise the usual IO_EXCEPTIONS for files.
procedure OPEN_READING_CONNECTION
(THE_CONNECTION: in out READ_PERSISTENT;
PERSISTENT_OBJECT: in STRING; –– the file path name
NON_BLOCKING: BOOLEAN := FALSE);
procedure OPEN_WRITING_CONNECTION
(THE_CONNECTION: in out WRITE_PERSISTENT;
PERSISTENT_OBJECT: in STRING; –– the file path name
BUFFERING: BOOLEAN := TRUE; NON_BLOCKING: BOOLEAN := FALSE);
–––– connection termination –––––––––––––––––––––––––––––––––––––––––––––––––––
procedure CLOSE (THE_CONNECTION: in out CONNECTION);
–– CAUTION: Please ENSURE that CLOSE is called at least once for each opened
–– connection! (Multiple calls won’t hurt.)
–– Otherwise, (sub–)programs might hang (not be terminated properly)
–– due to an unterminated internal task (the SIGPIPE interrupt handler).
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
628 von/of: 662

Space Infrastructure
629
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–– NOTES: This always includes an implicit flush. It never actually closes
–– pipes.
–––– connection I/O procedures ––––––––––––––––––––––––––––––––––––––––––––––––
–– NOTE: These procedures are only legal for a connected CONNECTION,
–– i.e. an un–CLOSEd CONNECTION after an OPEN_CLIENT_CONNECTION call,
–– or the CLIENT_CONNECTION returned by a successful ACCEPT_SINGLE call,
–– or the CLIENT_CONNECTION handed over to the HANDLE_CONNECTION
–– procedure parameter of an instantiated ACCEPT_LOOP.
–– In all other cases, NO_CONNECTION is raised if any of the I/O
–– procedures are called.
procedure READ
(THE_CONNECTION : in out CONNECTION;
THE_MESSAGE : in out MESSAGE);
–– this version always returns with a complete message read
–– (or NO_CONNECTION is raised if all else fails).
–– Don’t confuse this with process suspension; in the non–blocking case
–– it is actually implemented by polling.
–– READ does an implicit FLUSH before reading.
procedure READ
(THE_CONNECTION: in out CONNECTION;
THE_MESSAGE: in out MESSAGE;
SUCCESS: out BOOLEAN);
–– if SUCCESS = FALSE, then no message header was currently available
–– (even blocking connections will return immediately with the appropriate
–– SUCCESS return value).
–– READ does an implicit FLUSH before reading.
procedure WRITE
(THE_CONNECTION : in out CONNECTION;
THE_MESSAGE : in out MESSAGE);
–– when this procedure returns, the message has been completely delivered.
–– Don’t confuse this with process suspension; in the non–blocking case
–– it is actually implemented by polling.
–– For the WRITE case, no immediately–returning version is given, because
–– message delivery must be complete (or not at all).
procedure FLUSH (THE_CONNECTION: in out CONNECTION);
–– Actually sends all messages which may have been buffered by the
–– implementation. No–op if BUFFERING = FALSE (see connection creation).
–– An implicit FLUSH occurs before a socket is closed and when the
–– accumulated length of buffered messages exceeds the (UNIX–internal)
–– socket buffer length of 4096 bytes.
–––– connection testing –––––––––––––––––––––––––––––––––––––––––––––––––––––––
function IS_OPEN (THE_CONNECTION: CONNECTION) return BOOLEAN;
–– has CONNECTION successfully been opened, and is it still connected
–– to its peer?
function IS_CONNECTED (THE_CONNECTION: CONNECTION) return BOOLEAN;
–– was CONNECTION successfully connected by OPEN_CLIENT_CONNECTION,
–– OPEN_READING_CONNECTION, OPEN_WRITING_CONNECTION, ACCEPT_SINGLE or
–– ACCEPT_LOOP, and not closed yet?
–– (does NOT check if the connection is still alive!!)
function IS_BUFFERED (THE_CONNECTION: CONNECTION) return BOOLEAN;
–– was CONNECTION opened with BUFFERED => TRUE?
function IS_NON_BLOCKING (THE_CONNECTION: CONNECTION) return BOOLEAN;
–– was CONNECTION opened with NON_BLOCKING => TRUE?
function IS_READING (THE_CONNECTION: CONNECTION) return BOOLEAN;
–– can READ be applied to THE_CONNECTION (i.e. connected
–– and not a unidirectional writer)?
function IS_WRITING (THE_CONNECTION: CONNECTION) return BOOLEAN;
–– can WRITE be applied to THE_CONNECTION (i.e. connected
–– and not a unidirectional reader)?
function IS_BUFFER_EMPTY (THE_CONNECTION: CONNECTION) return BOOLEAN;
–– does CONNECTIONs buffer (if present) still contain unsent messages?
procedure IS_INPUT_READY
(THE_CONNECTION: in out CONNECTION; RESULT: out BOOLEAN);
–– has an up–to–now un–READ message arrived?
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
629 von/of: 662

Space Infrastructure
630
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
–– (i.e., would READ immediately return a message if called now?)
–– NOTE: Only the availability of a complete message header is checked,
–– assuming that in this case the contents of the message will be
–– resp. will become available immediately.
pragma INLINE –– these are really short, so make them inline
(IS_OPEN, IS_CONNECTED, IS_BUFFERED, IS_NON_BLOCKING,
IS_READING, IS_WRITING, IS_BUFFER_EMPTY, IS_INPUT_READY);
–––– server oriented procedures –––––––––––––––––––––––––––––––––––––––––––––––
procedure ACCEPT_SINGLE
(LISTENING_CONNECTION : in SERVER_CONNECTION;
CLIENT_CONNECTION : out SERVER_CONNECTION);
–– With an already opened server connection, a single connection
–– from a client can be accepted using this call.
–– If it returns normally, then a NEW_CONNECTION has been established.
–– NO_CONNECTION is raised only if something is wrong with CONNECTION.
procedure ACCEPT_SINGLE
(LISTENING_CONNECTION : in SERVER_CONNECTION;
CLIENT_CONNECTION : out SERVER_CONNECTION;
SUCCESS : out BOOLEAN);
–– this version immediately returns (if non–blocking) and flags
–– by SUCCESS if a connection was established.
–– NO_CONNECTION is raised only if something is wrong with CONNECTION.
generic
with procedure HANDLE_CONNECTION
(CLIENT_CONNECTION: in out SERVER_CONNECTION);
procedure ACCEPT_LOOP (LISTENING_CONNECTION: in out SERVER_CONNECTION);
–– With an already opened server connection, an ACCEPT_LOOP may be entered
–– which accepts connections from clients and forks UNIX child processes
–– to handle these connections. Each child, when forked successfully,
–– will call the application specific generic parameter procedure
–– HANDLE_CONNECTION and will terminate after its return.
–– Inside ACCEPT_LOOP, the LISTENING_CONNECTION will be made non–blocking,
–– but the CLIENT_CONNECTION passed to HANDLE_CONNECTION will have the
–– original blocking/non–blocking status.
–– The process which called ACCEPT_LOOP will remain in an endless loop and
–– must be KILLed by whoever started it (the user using a shell command or
–– an appliaction starting it via fork/exec). Orderly termination (by a
–– regular return from ACCEPT_LOOP) may be achieved by sending it a
–– SIGTERM signal (which is caught only while in ACCEPT_LOOP, and e.g.
–– not by the children).
procedure GET_FROM_FILE
(FROM_FILE : in STRING;
MODEL_ID : out DB_DEFINITIONS.MODEL_ID;
SYS_ENV : in out DB_DEFINITIONS.SYSTEM_ENVIRONMENT;
USER_ENV : in out DB_DEFINITIONS.USER_ENVIRONMENT;
IO_DESCS_LIST : out DB_DEFINITIONS.IO_DESC_LIST_POINTER;
NO_OF_ARCHS : out CSS_DEFINITIONS.ARCHITECTURES_RANGE;
ARCH_LIST : out CSS_DEFINITIONS.ARCHITECTURE_ARRAY);
––
–– This procedure may be used by the CMAS DB Server only to read parameters
–– written by the CSS DB Server to a file when starting the CMAS DB Server.
–– The file denoted by FROM_FILE will be deleted after reading its data.
––
procedure PUT_TO_FILE
(THE_MESSAGE : in out MESSAGE;
TO_FILE : in STRING);
––
–– This may be used the CSS DB Server only to put a message to a file when
–– passing the message to the CMAS DB Server.
–– The following items are written to the specified file:
–– * transaction ID
–– * system environment for the model
–– * current user environment for the model
–– * library pathname
–– * library SID
–– * library version
–– * relative name of the model root
–– * SID of the model root, if known (otherwise 0)
–– * flag for FILE_BASE or DB_BASED information
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
630 von/of: 662

Space Infrastructure
631
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
631 von/of: 662
–– * if FILE_BASED: name of the root of the css library (absolute UNIX path
–– without the dirname of the library an with trailing
–– slash)
–– * if FILE_BASED: name of the css library (relative UNIX path (relative
–– to ROOT (prior item)) without .lib extension and
–– without trailing slash)
–– * if FILE_BASED: name of the model (relative UNIX path (relative to
–– ROOT) incl. .mod extension but without trailing slash)
–– * the list of architectures a configuration table should be generated
–– for (only architectures for which previously a simulator kernel has
–– been configured)
–– * model (ie TLFB) interface items referencing onboard items
–––– exceptions –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
NO_CONNECTION, –– a connection couldn’t be established, broke down
–– or was disconnected during a READ, WRITE or ACCEPT call
BAD_LENGTH, –– an attempt was made to GET_xyz beyond the end of a message
–– or to GET_STRING with an insufficient BUFFER
–– an attempt was made to GET_xyz with a wrong vector or matrix size
MODE_ERROR, –– a READ operation was attempted on a PIPE– or PERSISTENT–
–– WRITER or vice versa
PROTOCOL_ERROR: –– a READ of CSS_SW_TYPE got an illegal number
exception;
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
private –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
type MESSAGE_BUFFER;
type MESSAGE_BUFFER_ACCESS is access MESSAGE_BUFFER;
MESSAGE_HEADER_LENGTH : constant := 12;
type CONNECTION (MODE: CONNECTION_MODE) is record
FD : UNIX_INTERFACE.FILE_HANDLE := UNIX_INTERFACE.FILE_HANDLE (–1);
CONNECTED : BOOLEAN := FALSE;
NON_BLOCK : BOOLEAN := FALSE;
BUFFERED : BOOLEAN := TRUE;
BUFFER : MESSAGE_BUFFER_ACCESS := null;
PEEKED : NUMERIC_TYPES.INTEGER32 range 0..MESSAGE_HEADER_LENGTH := 0;
PEEK_BUFFER: CSS_DEFINITIONS.BYTE_ARRAY (1..MESSAGE_HEADER_LENGTH);
end record;
type MESSAGE is record
OPCODE: NUMERIC_TYPES.UNSIGNED_INTEGER32 := 0;
DETAIL: NUMERIC_TYPES.INTEGER32 := 0;
LENGTH: NUMERIC_TYPES.INTEGER32 := 1;
DATA_LEN: NUMERIC_TYPES.INTEGER32 := 0;
ALLOC_LEN: NUMERIC_TYPES.INTEGER32 := 0;
POSITION: NUMERIC_TYPES.INTEGER32 := 1;
DATA: CSS_DEFINITIONS.BYTE_ARRAY_ACCESS;
end record;
LONGWORD: constant := NUMERIC_TYPES.INTEGER32’SIZE / SYSTEM.STORAGE_UNIT;
–– let’s hope there are no machines with SYSTEM.STORAGE_UNIT > INTEGER32’SIZE
–– or with (INTEGER32’SIZE mod SYSTEM.STORAGE_UNIT /= 0)
for MESSAGE use record
OPCODE at 0*LONGWORD range 0 .. 31;
DETAIL at 1*LONGWORD range 0 .. 31;
LENGTH at 2*LONGWORD range 0 .. 31;
DATA_LEN at 3*LONGWORD range 0 .. 31;
ALLOC_LEN at 4*LONGWORD range 0 .. 31;
POSITION at 5*LONGWORD range 0 .. 31;
DATA at 6*LONGWORD range 0 .. 31;
end record;
for MESSAGE’SIZE use 7*NUMERIC_TYPES.INTEGER32’SIZE;
end CSS_MESSAGE_CONNECTION;

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
7.18 Data Types supported by CGS in TES_API and CMAS_IF
7.18.1 CGS Data Types Supported
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
632 von/of: 662
The following section gives an overview on datatypes supported by CGS for usage in external interfaces
(e.g. within CCSDS Packets).
The types are described as supported at the TES_API interface, where complete CCSDS packets are
exchanged within ADUs or GDUs or where stimuli are sent within GDUs, resp. at the CSS/CMAS
interface, where values are exchanged, that can be taken by CMAS to/from CCSDS Packets or to/from
other data types on the onboard bus.
Legend:
Type in Interface.: The type of the value as it is written/read to/from the ADU or GDU
resp. the CCSDS Packet (Data Part)
TM: Telemetry Packet (received in TES inside an ADU via the TES_API)
The following types are supported at this I/F:
UNSIGNED_INTEGER
(SIGNED_)INTEGER
REAL
BYTE_STREAM (can be interpreted / displayed as STRING)
TC: Telecommand Packet (sent by CGS inside a GDU via the TES_API)
The following types are supported at this I/F:
UNSIGNED_INTEGER
SIGNED_INTEGER
STATE_CODE (bypassing decalibration)
REAL
STRING
SID (converted from PATHNAME)
TIME
SW: Software Command / Response Packets
(sent by CGS inside a GDU resp. received inside an ADU via the TES_API)
The following types are supported at this I/F:
UNSIGNED_INTEGER
SIGNED_INTEGER
STATE_CODE (bypassing decalibration)
REAL
BYTE_STREAM (STRING)
SID (converted from PATHNAME) (not in reponse packets)
TIME (not in reponse packets)
AS: Analog Stimulus (sent by CGS inside a GDU via the TES_API)
The following types are supported at this I/F:
REAL

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
DS: Discrete Stimulus (sent by CGS inside a GDU via the TES_API)
The following types are supported at this I/F:
SIGNED_INTEGER
BP: Binary Packet (sent by CGS inside a GDU via the TES_API)
The following types are supported at this I/F:
UNSIGNED_INTEGER
SIGNED_INTEGER
STATE_CODE (bypassing decalibration)
REAL
STRING
SID (converted from PATHNAME)
SIM: Simulation Measurement: A measurement given to the CMAS I/F
The following types are supported at this I/F:
UNSIGNED_BYTE, UNSIGNED_INTEGER, UNSIGNED_SHORT_WORD
SIGNED_BYTE, SIGNED_INTEGER, SIGNED_SHORT_WORD
STATE_CODE
BOOLEAN
REAL,LONG_REAL
PULSE, BURST_PULSE (currently not used by CMAS in CCSDS Packets)
SIS: Simulation Stimulus: A stimulus received from the CMAS I/F
The following types are supported at this I/F:
UNSIGNED_BYTE, UNSIGNED_INTEGER, UNSIGNED_SHORT_WORD
SIGNED_BYTE, SIGNED_INTEGER, SIGNED_SHORT_WORD
STATE_CODE
BOOLEAN
REAL, LONG_REAL
PULSE, BURST_PULSE (currently not used by CMAS in CCSDS Packets)
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
633 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
Type in Interface TM TC SW SIS SIM DS AS BP Comment
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
634 von/of: 662
Integer x x x x x x – x SIS/SIM: 8/16/32 bit
other: 1..32 bits
Unsigned Integer x x x x x x – x SIS/SIM: 8/16/32 bit
other: 1..32 bits
SID (32 bits) – x x (x) (x) – – x converted from Pathname
SIS/SIM:
as normal integer
State Code x x x x x – – x 8 Character
String x x x x x – – x Strings in CCSDS Packets:
up to 255 character
Real/Float x x x x x – x x Floating Point IEEE Std
(32 bits)
Long_Real/Float – – – x x – – Floating Point IEEE Std
(64 bits)
Single Bit x x x x x – – x SIS/SIM: converted to/
from boolean or statecode
other: converted
to/from statecode
Byte Stream x x – (x) (x) – – – Display: as String
(up to 255 bytes)
SIS/SIM:
converted by CMAS
to other types (e.g.integer)
TC: predefined in MDB
CCSDS unsegmented – x x – – – – – refer to CCSDS Standard
time code
CCSDS segmented – – – – – – – – refer to CCSDS Standard
time code

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
7.18.2 CGS Data Types: UCL to Raw Value Conversion
UCL Type TM TC SW DS AS BP Format / Comments
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
635 von/of: 662
INTEGER x x x – (1) x GDU: CCSDS: integer (1..32 bit)
GDU: Binary_Packet: integer (1..32 bit)
GDU: Analog Stimulus:
via UCL conversion to REAL (1)
ADU: CCSDS: integer (1..32 bit)
or unsigned_integer (1..32 bit)
ADU: Unstructured: integer (1..32 bit)
or unsigned_integer (1..32 bit)
ADU: Structured: integer (32 bit)
or unsigned_integer (32 bit)
UNSIGNED_INTEGERx x x – (1) x GDU: TC/SW: unsigned_integer (1..32 bit)
GDU:Bin_Pack.:unsigned_integer(1..32 bit)
GDU: Analog Stimulus:
via UCL conversion to REAL (1)
ADU: CCSDS: unsigned_integer (1..32 bit)
ADU: Unstruct: unsigned_integer (1..32 bit)
ADU: Structured: unsigned_integer (32 bit)
ENUMERATION (1) (1) (1) – (1) (1) via UCL conversion to INTEGER
BOOLEAN (2) (2) (2) – (2) (2) via UCL conversion to INTEGER
STRING x x x – – x Up to 256 character
CHARACTER *) *) *) – – *) *) A character can be interpreted as
a string of length 1 (see STRING)
COMPLETION_CODE (2) (2) (2) – (2) (2) via UCL conversion to INTEGER
REAL x x x – x x ADU,GDU (all types):
IEEE FLOATING Point format (32 bits)
or integer (1..32 bit)
or unsigned_integer(1..32 bit)
LONG REAL (1) (1) (1) – (1) (1) via UCL conversion to REAL, if value allows
DURATION (3) (3) (3) – (3) (3) via UCL conversion to REAL
TIME – x x – – – CCSDS Unsegmented Time Code

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
UCL Type TM TC SW DS AS BP Format / Comments
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
636 von/of: 662
PATHNAME – x x – – – GDU: TC/SW: SID (32 bit integer)
GDU: Binary_Packet: SID (32 bit integer)
STATECODE x x x x – x GDU: CCSDS: unsigned_integer (1..32 bit)
or STATECODE (8 byte / string)
GDU: Bin_Pack.:unsigned_integer(1..32bit)
or STATECODE (8 byte / string)
GDU: Discrete_Stimulus:
unsigned_integer (1..32 bit)
ADU: CCSDS:unsigned_integer(1..32 bit)
ADU: Unstruct: unsigned_integer (1..32 bit)
ADU: Structured: unsigned_integer (32 bit)
SETS – – – – – –
BITSET (1) (1) (1) – (1) (1) via UCL conversion to INTEGER or REAL
ARRAY – – – – – –
RECORD – – – – – –
WORD (4) (4) (4) – (4) (4) via UCL conversion to INTEGER or REAL
Notes:
(1) Conversion is supported in UCL between the following types (see UCL LRM):
– INTEGER REAL, LONG_REAL,CHARACTER, ENUMERATION, BITSET
– REAL LONG_REAL
(2) As BOOLEAN and COMPLETION_CODE are enumeration types in UCL, the conversion
BOOLEAN INTEGER and COMPLETION_CODE INTEGER apply.
(3) DURATION is defined as a unitized type. UCL supports conversion from unitized types to REAL
(4) WORD may be converted in UCL to any type which uses one storage unit (32 bits), including INTEGER
(5) The value range in UCL/CGS for unsigned integer is defined by 0 .. 2**31–1

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
APPENDIX A :
ACRONYMS
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
637 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
A
AD Applicable Document
ADD Architectural Design Document
ADT Abstract Data Type
ADU Acquisition Data Unit
AIL Atomic Implementation Language
AIV Assembly, Integration and Verification
AIT Assembly, Integration and Test
ANSI American National Standards Institute
AP Automated Procedure
API Application Programmer Interface
APM Attached Pressurized Module
AS Adaptation System
ASCII American Standard Code for Information Interchange
a.m. above mentioned
B
BNF Backus–Naur Format
BSD Berkeley Software Distribution
C
CASE Computer Aided Software Engineering
CAT Configuration Administration Tool
CCSDS Consultative Committee for Space Data Systems
CCU Configuration Control Unit
CDI Configuration Data Item
CDU Configuration Data Unit
CEGSE Core EGSE
CGS Columbus Ground System
CEGSE Core Electrical Ground Support Equipment
CGSI Columbus Ground System Infrastructure
CI Configuration Item
CLS Columbus Language System
CM Configuration Management
CPA Central Processing Assembly
CPMS Columbus Project Management System
CSS Core Simulation Software
CTG Code & Table Generator
CU Configuration Unit
C/O CheckOut
D
DADIMA Data Dictionary Maintenance Application
DB DataBase
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
638 von/of: 662

Space Infrastructure
DBA DataBase Administrator
DBMS DataBase Management System
DBS DataBase Services
DDO Dynamic Display Object
DDS Data Dispatch Service
DMS Data Management System
DN Discrepancy Notice
DNI Sun Microsystems DECnet compatible product
DOCT DOCumentation Tools
DPE Data Processing Environment
DS Directory Services
DSA DMS Simulator Assembly
E
ECA EGSE Console Assembly
EDB Engineering DataBase
EEA Error Effects Analysis tool
EGSE Electrical Ground Support Equipment
EPS Electrical Power Subsystem
ESA European Space Agency
ESE Electrical Support Equipment
EVL Engineering Value Log
F
FB Function Block
FC Flight Configuration
FDDI Fibre Distributed Data Interface
FDIR Fault Detection Isolation and Recovery
FEE Front End Equipment
FIPS Federal Information Processing Standard
FOC Final Operating Capability
FSP FTDSW Server Process
FSTP Functional Standard Target Processor
FT File Transfer
FTAM File Transfer, Access and Management
FTDS File Transfer and Directory Services
FTDSW File Transfer And Directory SoftWare
FTP File Transfer Protocol
FWDU Flight Window Definition Utility
FWDU_FE FWDU format editor
FWDU_TE FWDU text editor
G
GDE Ground DMS Equipment
GDI Ground Data Item
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
639 von/of: 662

Space Infrastructure
GDU Generation Data Unit
GMT Greenwich Mean Time
GNC Guidance, Navigation and Control
GSAF Ground Software and Avionics Facility
GSE launch site Ground Support Equipment
GWDU Ground Window Definition Utility
H
HCI Human Computer Interface software
HK HouseKeeping (data)
HLCL High Level Command Language
HOOD Hierarchical Object Oriented Design
HP Hewlett Packard
HP–UX HP UNIX
H/W HardWare
I
ICA InterCom Assembly
ICD Interface Control Document
ID IDentifier
IEEE Institute of Electrical and Electronic Engineers
IF InterFace
IP Internet Protocol
IPC InterProcess Communication
IPSE Integrated Project Support Environment
IRN Interface Revision Notice
ISO International Standards Organisation
ISS International Space Station
I/F Interface
I/O Input/Output
I–Code Interpreted Code
I_MDB Interactive Mission Database
J
K
KB Kilo Byte
Kb Kilo Bit
Kbps Kilo Bits Per Second
L
LAN Local Area Network
LOT LOcal Time
LRU Line Replaceable Unit
M
MB Mega Byte
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
640 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
Mb Mega Bit
Mbps Mega Bits Per Second
MDA Mission Database Application
MDB Mission DataBase
MDE Model Development Environment
MMI Man Machine Interface
MPS Mission Preparation Software
MRI Model Runtime Information
MTL Master TimeLine
MTP Master Test Processor
MTTC Minimum Telemetry and TeleCommand
MTU Master Timing Unit
N
N/A Not Applicable
NDT Network Diagnostic Tool
NASA National Aeronautics and Space Administration
NFS Network File System
NIS Network Information Services
NS Network Services
NTBT Not To Be Tracked
NTBT Not To Be Tested
NTP Network Timing Protocol
NW NetWork
NWSW NetWork SoftWare
O
OB OnBoard
ODS Object Description Skeleton
OLWM OpenLook Window Manager
OS Operating System
OSI Open Systems Interconnect
P
PA Product Assurance
PIRN Preliminary Interface Revision Notice
POCC Payload Operations Control Center
POSIX Portable Operating System Interface for UNIX
PROFS Professional Office Automation System
PR PRoduct level – used to indicate test level for requirements
P/L PayLoad
Q
QA Quality Assurance
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
641 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
R
RAM Random Access Memory
RCP Remote CoPy
RD Reference Document
RDBMS Relational Database Management System
REX Remote EXecution
ROD Review Of Design – a testing method
RPC Remote Procedure Call
RPI Remote Procedural Interface
RSH Remote SHell
S
SAS Special Application Software
SCA Software Criticality Analysis tool
SCOE Special Check–Out Equipment
SDDF Software Design and Development Facility
SDE Software Development Environment
SF Simulation Facility
SID Short IDentifier
SIVQ Software Integration, Verification and Qualification
SMT Simulated Mission Time
SNA System Network Architecture
SPE SPEcification document
SQL Structured Query Language
SRO Software Release Order
SS SubSystem
SSF Space Station Freedom
STAU STandard Acquisition Unit
STP Self Test Process
SunOS Sun Unix Operating System
SVID System V Interface Definition
SW SoftWare
SWES SoftWare Entity Support
SWEU SoftWare Exchangeable Unit
SWRU SoftWare Replaceable Unit
SY SYstem level – used to indicate test level for requirements
S/S SubSystem
S/W SoftWare
T
T Test – a testing method
TBC To Be Confirmed
TBD To Be Defined
TBE To Be Extended
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
642 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
TBS To Be Supplied
TC TeleCommand
TC Test Configuration
TCP Transmission Control Protocol
TE Terminal Emulation
TELNET Remote Terminal Protocol
TES Test Execution Software
TEV Test EValuation software
TLUI Top Level User Interface
TM TeleMetry
TOC Table Of Contents
TP Transport Protocol
TP4 OSI Transport Protocol Class 4
TPS Technical Publishing Software
TPS ASCII Interleaf Text Processing System ASCII output format
TRDB Test Result DataBase
TRIT Trace Requirements and ICD Tracking tool
TS Table Space
TS Transport Services
TSCV Test Set–up, Configuration and Verification software
TSP Time Services Server Process
TSS Time Services Software
U
UCL User Control Language
UCLC User Control Language Compiler
UDP User Datagram Protocol
UIL User Interface Language
UTC Universal Time Code
UTP Unshielded Twisted Pair
UUT Unit Under Test
V
VADS Verdix Ada Development System
VICOS Verification, Integration and Check–Out System
VIT Version Identification Table
VT V Terminal
W
WAN Wide Area Network
WDU Window Definition Utility
WS WorkStation
X
XDR eXternal Data Representation
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
643 von/of: 662

Space Infrastructure
Y
Z
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
644 von/of: 662

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
APPENDIX B :
DEFINITIONS
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
645 von/of: 662

Space Infrastructure
A
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
646 von/of: 662
Access rights Define what access various users or applications have to objects or
entities.
Accuracy Accuracy is the software characteristic that provides the required
precision in calculations and outputs.
Action One or more higher–level commands (from Crew, Ground, MCS, or
Master Timeline) to operate the Flight Configuration subsystems or
payloads. The Action contains all pre–checks necessary to ensure a
safe implementation of an automated operation consistent with the
actual mission phase and flight element configuration.
Ad Hoc Error Reporting An error reporting method where the application constructs the contents
of the error message.
Allowable Roles The allocated subset of roles that a particular user may perform.
Application Program or set of programs performing some specialized user–
oriented function (as opposed to general–purpose programs like a
DBMS, or an operating system).
Application Data Application data is defined, in the context of the NWSW, as data
specified by the applications using the NWSW e.g. CGS. Its content
and structure are of no importance or interest to the NWSW.
Application Home The directory location assigned to a particular application of CGS,
also called Home Directory.
Archive Refers to the process of relegating obsolete data to external backing
storage. The reverse operation (copying archived data back to active
storage) is known as restore.
Archive Files Refer to ’Archiving’
Archiving In VICOS, archiving means storage of data in raw format. All data
received or generated by a testnode is archived in OS files (archive
files). The files are managed after closure as part of the Test Result
DB and made accessable by VICOS evaluation S/W as well as by
SAS.
As–Run–Procedure In VICOS, a Test Step Sequence (or Test Instruction Sequence) is executed
by the Test Step Execution and Guidance Tool, in a dialog
with the operator. The result of each step is stored in the Test Result
DB as the ’As Run–Procedure’. The As–Run–Procedure contains the
OK/Not OK status as well as values for enditems and comments
given by the operator. Each step is timetagged when executed.
Atomic Implementation Language (AIL)
Language used for the implementation of atomic function blocks in
a model definition.
Auditing Process of examining recent transactions to determine if illegal or
fraudulent activity has occurred.
Audit Log Permanent record of important events that occur in a computer system.

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
647 von/of: 662
Authorization Permission of a command source to execute a command.
Authorized User see User
Automated Procedure
B
A program written in the User Control Language (UCL).
Baseline An SDE operation used for freezing a configuration of released SDE
objects.
Baseline A SDE operation used for freezing a configuration of SDE reviewed
constituents.
Baseline area A SDE area containing baselined constituents which are under strict
configuration control in the CM area.
Base Function The basic function underlying a function block, which is used in associated
with the function mask to provide the function block, c.f.
Base Function and Function Mask. E.g. An analogy is the invocation
of a C compiler with a set of options; the function block is the C compiler
invoked by ”cc”, the function mask is the specified set of options
”–O”, ”–target”, etc. which specify parameters particular to the invocation
(”optimisation”, ”cross–compilation”, etc.).
C
Calibration In VICOS, calibration means calculation of values for enditems according
to predefined calibration curves, from raw format (i.e. format
as received resp. acquired via devices) into calibrated format.
The result of a calibrated value is the Engineering Value, which
implies an Engineering Unit to be applied.
Check in/out SDE operations to control versions of a SDE object under development.
The check in operation freezes the contents of the checked out
version of an object such that this version can unambiguously be referenced
in the future. The check out operation creates a working copy
with an incremental version number. It is worth pointing out that not
all versions of a constituent represent formal releases: in general,
versions represent just a state of an object that the developer wants
to preserve for his/her own convenience.
Child In a hierarchical structure, denotes an immediate descendant of a
given component. A child is thus located one hierarchical level
below its parent.
CI variant version A specific version of a CI variant
Class–A–check Process of validating the syntax and format of a segment of data denoting
an Action command.
Class–B–check Process of validating and verifying the consistency of resources allocated
within an action w.r.t. the resource’s amount/availability.
Client A process or program that makes use of services provided by another
process or program (called service provider or server).
CM area The SDE CM areas consists of the baseline area and the release area

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
648 von/of: 662
Command Elementary instruction or statement from which a functionality is
called.
Command Execution Report A report provided to the command originator after command execution.
The report specifies whether the command was executed successfully
or not.
Command Status Report A report provided to ground or flight crew (on event occurrence or
on request) comprising all related commands being active at that
time and their current processing status.
Communication Session A communication session is a logical exchange of messages between
two users of the network software, such as in a response/request
scenario when a request from user A solicits one or more responses
from user B. The session can be considered to begin when the request
is sent and finished when the last response has been received. This
definition of a session is only valid when talking in terms of the network
software. It should not be confused with an OSI session because
OSI has its own widely accepted definition.
Compilation Unit Smallest unit of code that is accepted by the compiler. In UCL, there
are 3 types of Compilation Units: Automated Procedure (AP), Library
Specification, and Library Implementation (or Library body).
Completeness Completeness is the software characteristic that ensures full implementation
of the functions required.
Component Component is a generic term used to cover any item in the higher levels
of the software architecture (i.e. product, assembly and subsystem).
Configuration DB Configuration DB is the data base on EGSE site which contains all
test relevant data and configuration definitions for one specific element
(e.g. MTFF). It contains definitions for UUT (UUT specification)
and EGSE Configurations(EGSE specification).
NOTE : see appropriate definitions for UUT spec. and EGSE spec.
The Configuration DB contains several versions of definitions, each
describing a specific configuration.
Configuration DB Version A configuration data base version consists of the selection of parts
from UUT specification data and EGSE specification data relevant
for a set of specific tests.
One configuration data base may contain as many configuration data
base versions as the user wants to define.
Configuration Unit (CU) Collection of MDB items treated as a single unit for configuration
management purposes.
CUs are of two kinds:
(a) Configuration Data Units (CDU), which contain the actual data
(b) Configuration Control Units (CCU), which contain reference information
(CU name, version number, etc.) about other CUs, just like
a directory in a file system.

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
649 von/of: 662
Configuration Unit Instance see Version
Configuration Control Unit (CCU)
A Configuration Control Unit is a Configuration Unit used to define
and control other Configuration Units. It identifies which specific
combinations of CDU instances make up a particular configuration.
A Configuration Control Unit may, in turn, point to lower–level control
units, thus leading to a hierarchical configuration tree whose topmost
(root) component corresponds to an entire Columbus Flight
Configuration.
Configuration Data Unit (CDU)
Configuration Data Units are composite entities containing the
actual data items (grouped into individual units for configuration
management purposes).
Connection Matrix Refers to a matrix CM( i,j ) where the columns represent the symptom
vectors of the individual anomalies and rows each stand for a
symptom.
Consistency Consistency is the software characteristic that ensures uniform design
and implementation techniques and notations.
Constrained command see Two Stage Command
Control command A command to CSMM which allows to control the CSMM S/W
functions. It is used for enabling/disabling of automated functions
(e.g. Failure Management, Resource Management) or checking
mechanisms.
Controlled Error Reporting An error reporting method where the application selects an error
message from a pre–defined set of error messages stored in the application
Error Message Database (CGSI).
Correctness Correctness is the degree to which the software component satisfies
the specified requirements.
Current Role The role, from the subset of allowable roles, that a particular user has
currently assumed.
D
DATA_API A view based interface to the Mission Database. Provides views for
retrieval from the Mission Database, functions for setting the configuration
and functions for commit/rollback within the chosen configuration.
Data Entry / Data Maintenance
Generally refers to the process of entering and/or updating data in the
database.
In this context, the term ”maintain” refers to any operation which
alters the state of the Database, i.e. add (insert) new data, modify existing
data, or delete data.
Data Type Declarations Type declarations are done in the syntax of the Ada Programming
Language.

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
650 von/of: 662
Database A common or integrated collection of interrelated data whose purpose
is to serve one or more applications.
Database Administrator (DBA)
The person(s) responsible for the operation and maintenance of a
DBMS.
Database Integrity Refers to the state in which the database is considered to be undamaged
(both physically and logically).
Database Management System (DBMS)
The software responsible for the actual definition, storage and manipulation
of data in a Database at both the physical and logical
level.
Database Server Refers to the processor (network node) physically hosting the Database
and providing DB access services to local or remote applications
(clients).
Database Server Node In VICOS, a database server node is a logical node which provides
services to store and manage access to the Configuration DB as well
as to the Test Result DB.
A logical DB Server node has to be mapped to a physical processor
where it runs on (DB server processor).
Deadlock Situation in which two or more user processes cannot complete their
transactions because each process is holding a resource that the other
process requires in order to complete.
Default a value supplied by the system when a user does not specify a required
parameter, qualifier, or attribute.
Default Role A nominated role, from the subset of allowable roles, that a particular
user defaults to at the start of a SDE session.
Default User The user to whom an error is reported as a default. This is the CGS
user on whose workstation the error occurred.
Development area A SDE area which contains constituents under development
Diagnosis Assumption about the faults or failures of a system obtained by
examination of the symptoms.
Display (or Screen Display) In this context, refers to an area on the physical screen surface assigned
to applications for the purpose of communicating with the
human users. It may comprise one or several individual partitions
(windows) each assigned to a different application.
Distributed Database A collection of databases that can be operated and managed separately
and also share information.
E
Electronic Test Procedure Refer to ’Test Step’
End–Item see MDB item
Engineering Unit Refer to ’Calibration’
Engineering Value Refer to ’Calibration’

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
651 von/of: 662
Engineering Value Log In VICOS, enditem values may be logged (stored with a time tag) in
calibrated format in special logbooks as part of the Test Result DB.
The values may be evaluated in an offline session without need for
re–calibration.
Error Message The collection of data (textual description, attributes such as reference
number, criticality, time of occurrence, etc.) which describes
the error which has occurred (CGSI).
Error Message Mnemonic A short text string used by CGSI to index error messages.
Error Message Spec An error message spec. is the same as an error message, except that
it does not include the time of occurrence: this is the form in which
CGSI stores error messages.
Error Report The act of invoking the CGSI provided error reporting facility.
Error Reporter The invoked function block wishing to report an error.
Evaluation Application A tool within VICOS TEV or an SAS using TEV that performs a specific
evaluation task.
Evaluation Definition An end item of the Configuration Database containing a definition
used by TEV. Following types of evaluation definition are defined:
– HLCL Sequence
– Selection Criteria (for logging event evaluation)
– Statistic Definition (for statistical analysis)
– Listing Definition (for listings)
– Synoptic Display Definition
– Graph Definition
– Dump Criteria (TBC) (for raw data dump)
– Report Definition (for generation of a test report).
Evaluation Result File A file containing the output of a VICOS TEV tool for further processing
or for storage. Several types of evaluation results files are identified:
– Logging Evaluation File
(contains the result of an logging event evaluation)
– Statistic File (contains the result of a statistical analysis)
– Listing File (contains a listing)
– Synoptic Display File
(contains state of a synoptic display at a certain moment
of time of the animation –graphic)
– Graph File
(contains the state of a graph at a certain moment of time
of the animation–graphic)
– Dump File (contains the result of a raw data dump)
– Report (contains a report).
Event Log In VICOS, events (errors, out–of–limit exceptions, user input etc.)
may be logged (stored with a time tag) in special logbooks as part
of the Test Result DB. The events may be evaluated in an offline
session by producing a selected list of events, ordered according to
time tags.

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
652 von/of: 662
Exception An out–of–limits condition or a status inconsistent with the value obtained
by the monitoring function. In both cases, the current operational
state is taken into account. An exception may also be derived
from other values.
Export In the MDA context, this term refers to the process of extracting data
from a DB and preparing it for inclusion (import) into another DB.
F
Failure The termination of the ability of a functional unit to perform its required
functions (ISO). A failure may occur when a fault is encountered.
In the FDIR terminology, a failure is defined as the behavior of a
functional unit which is different from that expected.
Fault An accidental condition that causes a functional unit to fail to perform
its required functions (ISO). A fault if encountered, may cause
a failure.
Formal Language Specifications
Formal language specifications are done in extended Backus–Naur
Form (EBNF).
Function Block A component of CGS functionality which is invoked as a single entity,
c.f. Base Function and Function Mask.
Function Mask A mask which provides a map onto the functions provided by the
function block, implying the selection or non–selection of each function,
c.f. Base Function and Function Mask.
G
Ground Software All software that executes in any COLUMBUS ground computer or
in the flight configuration computers during pre–launch ground
operations.
H
Heterogeneous system Refers to a system comprising different types of processors or operating
systems.
Hierarchical Name Tree see Name Tree
High Level Command Language (HLCL)
Language used for interactive commanding in the Ground System.
HLCL Command A HLCL command is any command which can be given interactively
by the user to VICOS. HLCL commands can be given in specific
command windows. Some of them are translated to UCL interactive
commands and transfered to the UCL Interpreter running on the
EGSE test nodes (SCOE, MTP).
are a set of
– specific HLCL commands
– UCL interactive commands–
Home Directory The directory location assigned to a particular application of CGS,
also called Application Home.

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
653 von/of: 662
Homogeneous system Refers to a system in which all processors are of the same type or
family (usually from one vendor).
I
Implication Strength Entry in the connection matrix CM (i,j), in the range between zero
and unity, representing the measure of evidence which the symptom
in the i–th row bears to the anomaly in the j–th column.
Import In the MDA context, this term refers to the process of receiving or
including data from an external (possibly remote) DB into the local
DB.
Integrity Integrity is the extent to which the software component controls access
to system resources. (Resources here include database items,
functions, and software controlled hardware).
Interactive Utilities With this term, all normal UNIX programs are meant, such as ’cp’,
’ls’, ’find’,... These programs are, or can be, started from the ’shell’
through ’interaction’ with the user. Those programs report problems
through messages printed to the standard output device (the terminal’s
screen/window). The user can react accordingly. These ’interactive’
programs make use of system calls and library function to
provide their functions. These system calls and library functions are
also referred to as a ’programmatic interface’ to ’non–interactive’
utilities. Example: ’open’, ’read’, ’write’, ’stat’, ’close’, ’unlink’, ....
These ’non–interactive’ utilities report problems through a variable
called ’errno’.
Intermediate code (I–code) The binary code generated by the UCL compiler. It is interpreted at
run time.
Interoperability Interoperability is the extent of effort required to facilitate the interface
of one software component with other systems or software components.
Issue see Version
J
Journal A journal is a list of logging events in a user readable format as produced
by VICOS TEV. It is referred to also as Event Logging List
L
Level Name The name which identifies one node at a particular level in the MDB
hierarchy. A long path name is a concatenation of level names.
Library see Symbol Library, UCL Library
Local Time (LOT) The time to which the system clocks are set is the LOT. It can be e.g.
the official local time, in use at the location of the EGSE’s installation
or GMT or UTC,...The time server for LOT will be the time of
the MTP system clock. This can be set by the system administrator
using Unix shell commands.
Locking Mutual exclusion mechanism used for controlling concurrent access
by multiple users/applications to a shared resource.

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
654 von/of: 662
Logbook A logbook is a storage unit (file or may be something else if a DBMS
is used) for events and engineering values. Then there are two types
of Logbooks: the Events Logbooks and the EVL Logbooks.
Logging See ’Event Log’ and ’Engineering Value Log’
Limit In VICOS, monitoring is driven by limits defined for each enditem.
Lower and upper limits can be defined. When VICOS detects an
enditem value which is ’out–of–limits’, a message (’exception’) is
raised if a predefined ’count’ of limit violations is reached. Together
with the generation of exceptions, automatic actions (start of AP,
genertion of stimulli/TC) may be initiated. ’Limits’ for discrete or digiital
enditems are referred to as ’Expected Values’
There are two kinds of limits: ’hard limits’ and ’soft limits’. Hard limits
cannot be changed online and are checked with higher priority
than soft limits. Soft limits can be changed by the test operator in an
ongoing test (online).
Each enditem in VICOS may have a set of soft limits defined. Selection
of one applicable set is driven by conditions or switched when
TC/Stimuli are given or selected by the operator.
M
Master Archive Refer to ’Test Result DB’
MDB Item, MDB Object In the context of this document, these two terms are used interchangeably
to denote a uniquely identifiable entity that has been defined
in the Mission Database ( and corresponds to a real–world HW or SW
entity). An MDB Object or Item may be decomposed into lower–
level items according to the hierarchical nametree conventions, see
Nametree below.
An End–Item is an MDB item located at the lowest hierarchical
level (leaf or terminal node), and hence cannot be further decomposed.
MDB–Item instance An occurrence of a particular MDB item in a given CU version.
Measurement A measurement is a single (analog or digital) intput from a (measurement)
device.
Mission The performance of a coherent set of investigation or operations in
space to achieve space programme goals. A single mission may require
more than one flight, and more than one mission may be accomplished
on a single flight.
Mission Database (MDB) This a CM–controlled ground Database used as repository for all
HW / SW information required for specific Columbus missions or
test configurations. Access to the MDB is controlled and managed
by MDA.
MPS / MDA User see User
N
Nametree Hierarchical (tree) structure within the MDB which portrays the hierarchical
decomposition of Columbus Flight Configurations into

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
655 von/of: 662
systems, subsystems, equipment, etc. The topmost node of the
nametree (called the root node) designates the Flight Configuration,
whereas terminal nodes (leaf nodes) represent the items that cannot
(or need not) be further decomposed, i.e. the so–called end–items.
Each MDB object is thus identifiable by a pathname indicating the
succession of nodes to be traversed to reach that particular item in the
Nametree.
Network A group of computers (workstations) and/or terminals that are linked
together to allow the sharing of resources (data and peripherals).
Network Time Protocol (NTP)
NTP is a time synchronisation protocol used to minimise the offsets
between the system clocks of the computers in a network. In this protocol
the NTP–clients periodically request time information from the
NTP–server. Based upon this information, the NTP–clients adjust
their own clocks in order to get the offset w.r.t. the NTP–server to the
minimum.
Node Any component of a network or tree structure (e.g. LAN node,
nametree node).
O
Operating System (OS) The system software that controls the computer and its parts, performing
the basic tasks such as allocating memory, and allowing
computer components to communicate.
Operator The person who operates any system comprising software and hardware
using the provided computer input devices (e.g. keyboard,
pointing device, voice input, pushbuttons, switches etc) and/or computer
output devices (e.g. screen, printer, lamps etc).
P
Parent In a hierarchical structure, denotes an immediate ancestor of a given
component.
Parent Screen See HCI Standards
Pathname see Nametree
Physical Screen See HCI Standards
PL/SQL ORACLE procedural language extension to SQL
Pro*C ORACLE pre–C compiler with embedded SQL.
Procedural Interface A procedural interface is an interface which is implemented by a set
of procedures, usually grouped into an Ada package(s). The interface
may be included in the interfacing component without concern for
the underlying implementation, and so allow development and testing
of the underlying component.
Project A SDE project is a CI variant version (also known as a CI instantiation).
A variant exists, for example, for each different target system
of the CI. Variants are, in turn, organised into versions. A version of

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
656 von/of: 662
a variant corresponds, for example, to a major revision of the specification.
Within a version of a variant there are potentially many objects;
each of these may exist in many versions.
Protocol Rules and conventions for organizing data to be sent from one machine
to another. The protocol enables the destination machine to
recognize that the data is addressed to it, check the data to make sure
that it is valid, unpack and decode the data, etc.
Proximity Ratio A measure of the correspondence of observed pattern to predefined
pattern. For failures and faults the proximity ratio is defined as the
quotient of observed to expected symptoms.
Q
Qualification Data Data which is used to implement the qualification functionality of
CGS, e.g. test results, test procedures, test cases, trace information
etc.
R
Recovery This is the process where a Database which is damaged (or assumed
to be so) is restored to a previous state known to be consistent.
Remote Utilities A group of generally available UNIX programs providing access to
remote hosts. These programs are activated by the shell to perform
a certain function. Examples are: ’Remote Shell’ (rsh on SunOS or
remsh on HP) will execute the command given as arguments to the
’remote shell’ on the node specified by the first argument; ’Remote
Copy’ (rcp on SunOS and HP) is a copy command where the arguments
can take ’hostname:’ prefixes to indicate the indicated file
must be seen relative to that ”hostname”; ’Remote Login’ (rlogin on
SunOS and HP) will open a channel to the host specified as an argument
and allow the user a login attempt.
Report In the context of this document, a report may be defined as any
human–readable description of one or more MDB items. It is an assorted
collection of information usually presented to the user in form
of a table or itemized list (tabular format).
A report’s specification contains the instructions for generating the
report, e.g. data selection criteria, formatting instructions, and sort
order. This specification may be stored in the MDB.
On request, a report is generated, i.e. the predefined instructions are
executed, and the resulting output routed either to the workstation’s
screen (on–screen report), to the printer or to a user–selected file.
Resource Any of the component parts of the System, or the facilities that it
offers (e.g. power, communication channels, etc.).
Resource Allocation The act of making a resource (or part of it) available for use by an Action.
Resource Deallocation The act of freeing or releasing a resource previously allocated; the
resource then becomes available to other users.
Response time For interactive transactions, this refers to the time elapsing between
the ”end of input” signal (e.g. pressing the ENTER, ACCEPT, or

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
657 von/of: 662
COMMIT key) and the first character of the reply reaching the user’s
terminal.
Restore This refers to the process of copying archived data back to active
storage.
Revision see Version
S
Sammi Graphical, interactive process control software. Consists of two
parts. The format editor for creating synoptic displays and the runtime
system for executing synoptic displays.
Screen Display see Display
Semantics Refers to the set of rules dealing with the contextual meaning of the
language elements (symbols, constants, variables, etc.).
Server A process providing services to other cooperating processes.
A DB server is the processor (network node) physically hosting the
Database and providing DB access services to local or remote applications
(clients).
Short Identification A unique identification value for an end item in the Columbus Name
Tree, which may be used to access that item. The pre–compilation
stage in the SDE provides a translation, using an MPS service, of a
full path name for an end item into a short id. The short id is used to
decrease access time to the item when the software containing the
item is executed.
Simulated Mission Time Mission Time starts counting the moment space station Freedom
supplies all services to the APM and all APM circuits are powered.
In order to perform the required EGSE tests, this time has to be simulated,
and the possibility has to be there to manipulate SMT, i.e. to
set, stop and continue SMT.
SMT–domain An SMT–domain is a set of VICOS nodes having their own SMT–
server. Because in a distributed configuration more then one test configuration
can be active at the same time (one configuration in on–
line checkout and a second one in off–line simulation mode) several
SMT–domain, each with its own SMT–server, can exist simultaneously.
Software Exchangeable Unit (SWEU)
All COLUMBUS ground software is configured into SWEUs. An
SWEU is any software unit or component which can be replaced as
a single item. As such it is primarily a configuration management
item and is handled in the same way as an (onboard) SWRU for CM
purposes. ( See also SWRU).
Specific Applic. S/W (SAS) Specific Application S/W (SAS) is the S/W executed in parallel with
VICOS on the same H/W, using VICOS services. It is written in Ada
and executed under the same OS as VICOS is. It is be linked to
VICOS services using VICOS supplied interface libraries. SAS in-

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
658 von/of: 662
cludes the S/W which is written for specific purposes of the EGSE
and is standard for the EGSE. Each special application S/W product
will be produced in the SDE, in which it is identifiable via its name
and a version identification.
Stimulus A stimulus is a single (analog or digital) output to a (stimuli) device.
SWEU data set The data transferred for an SWEU which contains the following
items:
– Configuration Identifier, variant and version
– SWEU SDE name and version
– Object Code
– Object Code Size
– Date of generation of the object code
– Programming Language used for majority of
implementation
– Criticality of the SWEU
– Short identifiers cross reference list.
Software Replaceable Unit (SWRU)
All COLUMBUS flight software is configured as a set of SWRUs.
Some SWRUs can be replaced online. Otheres are replaced by reloading
the pocessor. All SWRUs are configuration management
items in the same way as SWEUs.
SWRU data set The data transferred for an SWRU which contains the following
items:
– Configuration Identifier, variant and version
– SWRU SDE name and version
– Object Code
– Object Code Size
– Date of generation of the object code
– Programming Language used for majority of
implementation
– Criticality of the SWRU
– Replacement type of the SWRU i.e. offline, online, or
embedded
– target processor type i.e. SSCU, STAU, MMC, DBC,
WSA, Equipment level processor
– compatible processors that could be used for re–allocation
– Short identifiers cross reference list.
Solicited Connection Request A solicited connection request is a connection request that a NWSW
user on a specific node makes to some other NWSW instantiation executing
in the network.

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
659 von/of: 662
Sustainable Date Rate A sustainable data rate is a rate of data traffic that can be maintained
for a relatively long period of time, where the period of time is of, at
least, the order of seconds (the number of seconds depends upon the
context).
SWRU Support Set Refers to the set of data and procedures required to control and automate
the generation and exchange of SWRUs. The SWRU Support
Set typically includes: offline generation procedure, maintenance information,
verification information, replacement procedure and
other general information (identification, version, generation date,
size, criticality, target processor type, etc.).
Symptom Indicator of faults or failures.
Synoptic Displays Synoptic Displays is a VICOS HCI window service which allow the
human user to display and manipulate Synoptic Picture within windows
at the workstation screens.
Synoptic Picture A Synoptic Picture is defined as content of a Synoptic Displays window.
It is a predefined graphical picture that represents the physical
devices and subsystems (EGSE or UUT). It contains output elements
that are dynamicly animated (to indicate status / values) as well as
input elements that allow for commanding the devices/subsystems
by direct mouse manipulation.
System Administrator A person responsible for the operation and maintenance of the operating
system of a computer.
T
Telecommand (TC) The data uplinked from the ground to a spacecraft is known as telecommands.
It contains requests to the onboard system or bulk data.
In the Columbus EGSE the data is sent to the Spacecraft via the TM/
TC Front End. The protocols used are baselined to be CCSDS path
service, and therefore TC data is uplinked in CCSDS packets.
In VICOS, a TC is always a single request. Bulk data is to be uplinked
by S/W outside VICOS (SAS) using VICOS services. TC and Stimuli
are handled in a similar way.
Telemetry (TM) The data downlinked from a spacecraft to the ground is known as telemetry
data. It contains status data of the onboard system. In the Columbus
EGSE the data is acquired from the Spacecraft via the TM/
TC Front End. The protocols used are baselined to be CCSDS path
service, and therefore TM data is downlinked in CCSDS packets.
In VICOS TM packets and measurments are handled in a similar
way.
Test Node In VICOS, a test node is a logical node which provides the data interfaces
to the UUT, either directly or via frontend equipment. Test
nodes require data from the UUT, generate data to it, process data
(calibration and monitoring) and interprete Automatic Procedures.
A logical test node has to be mapped to a physical processor where
it runs on (test processor).
Test Results In VICOS, the term test results is summarising all data produced during
a test session that are foreseen for long term storage or offline

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
660 von/of: 662
evaluation. Test Results comprise at least:
– raw data archive files
– event logging data
– engineering value logging data
– printable reports
– graphical output
– data sets produced for intermediate storage of
engineering enditems
– the ’as–run–procedure’
– other
Test Result DB In VICOS, the Test Result DB (TRDB) contains all data produced
in different test sessions, either during test execution or test evaluation
It contains an index of all data items (Master Archive), indicating
the name, the related time frame and the location of storage for
each item.
The Test Result DB is managed by VICOS DBS and consists of
Oracle Tables as well as of OS files.
The Master Archive is a sort of index that allows to retrieve data
stored on the Mass Storage according to criteria like time, test
session, evaluation session. The Master Archive is located on a Magnetic
Disc of the EGSE Database Server.
The Mass Storage contains physically all the data: Logbooks, Archive
Files, Evaluation Result Files. It is accessed thru the Master Archive.
The data will be stored temporarily on magnetic disc and then
on several storage media (Long Term Storage Medium e.g. optical
disc).
The Visible Part of the TRDB is the part that can be directly accessed
at a certain instant of time. That means, it is the Master Archive plus
the data of the Mass Storage stored on magnetic disc and on the Long
Term Storage Media actually mounted.
Test Session In VICOS, a test session is a term identifying a sequence of operations
and activities within a given time frame, related to a specific
set of test objectives, together with the generated test results and a
reference to the used configuration. A test session has a unique name,
and an index of all results produced in the test session is stored in the
Test Session Table within the Master Archive as part of the Test Result
DB.
There are two kinds of test sessions:
– the Online Test Session, which is produced during an online test
– the Evaluation Test Session, which is produced by a specific user
when data evaluation is performed offline.
Traceability Traceability is the software characteristic that provides a thread of
origin from the implementation to the requirements with respect to
the specified development envelope and operational environment.
Traceability Data Data which provides traceability information between items of a
component of components of the development process.

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
661 von/of: 662
Transaction Single thread of related activities representing a sequence of operations
initiated by the occurrence of a stimulus and ending with the
required response.
Translation Table A translation table (in the context of the NWSW) is a data structure
that contains information relating the physical network address of a
NWSW instantiation to the logical ASCII name by which it is known
to the user.
Two–stage Command A command which requires confirmation from the originator before
it is executed.
U
Unit Unit is a generic term used to cover any lower level item of breakdown
in the software architecture e.g. module, object etc.
Unit Under Test (UUT) UUT means a spacecraft or a part of a spcecraft where the EGSE is
connected to and which is foreseen to be checked out using the EGSE
and VICOS.
Unsolicited Connection Request
An unsolicited connection request is a connection request that a
NWSW user on a specific node receives without prior notice from
some other NWSW instantiation executing in the network.
User Throughout this document the term User or MPS / MDA User refers
to any person using MDA–provided services. Users are grouped into
different classes or categories and will be assigned different privileges
based on the task they perform.
User Control Language (UCL)
Columbus Test and Operations language (used for real–time control
& monitoring purposes in both the onboard and ground environment)
User Name The method used to identify the authorised users of the CGS installation.
User Working Environment A user working environment is a specific S/W environment, which
is appropriate to a human user (e.g. test conductor, test observer) and
his task. It enables the user to start automatically the applications
with the corresponding windows needed for his work (e.g. creation
of a Synoptic Displays window and start of the AP’s belonging to it).
See also ’S/W Environment (VICOS User)’.
UCL Library Encapsulation mechanism for UCL data structures and operations.
(can be viewed as a collection of functions, procedures, types, etc.)
A UCL Library corresponds to a package in Ada or a module in
Modula–2.
V
Version In the course of its life cycle, a Configuration Unit (CU) usually undergoes
several modifications due to evolving user requirements, design
changes, etc.

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
662 von/of: 662
It will thus possibly exist within the MDB in many different forms
or instances (CU occurrences) commonly referred to as versions,
e.g. DMS Version 3.2.1.
In the Configuration Management (CM) context, however, the various
CU occurrences. are classified according to the types of changes
that have been made. The terms versions, issues, and revisions are
then used to differentiate between the following 3 cases:
– Modifications due to requirements changes which result in a new
version
– Modifications due to design changes which result in a new issue.
– Modifications due to bug fixes, repairs or other corrections (affecting
neither the design nor the requirements) which result in a new
revision.
(In the above example, the CU Identifier ”DMS Version 3.2.1”,
therefore, refers to Version 3, Issue 2, Revision 1 of the DMS)
Visibility When a file is accessible by a a normal UNIX program (excluding
’remote utilities’), then the file is considered ’visible’. Without a network,
visibility is restricted to local disks, tapes and other peripherals.
When the system is integrated into a network, then some files/
directories on other devices in the network may become ’visible’ to
the local machine through the use of NFS. Another way to describe
it would be: a file is ’visible’ when its name can be specified (opened)
to the UNIX system call ”open”.
NOTE: ’Visibility’ has nothing to do with a user’s access rights to a
particular file. A file may be ’visible’ to the host program running
with ’root’ privileges but at the same time be inaccessible to a normal
user.
W
Widget An object providing a user interface abstraction (for example, a
Scrollbar widget).
X
X11 X Window System Version 11 is a library which provides functions
to write applications with a graphical user interface running on a network.
Working Directory A disc space containing the intermediate files for a specific tool and
a specific user.
Workstation Node In VICOS, a workstation node is a logical node which provides the
interface to the operator and executes operator related functions for
test execution monitoring and control, for test setup, for test preparation
and for test evaluation. It runs the VICOS HCI, the TSCV and
the TEV.
A logical workstation node has to be mapped to a physical processor
where it runs on (workstation processor).

Space Infrastructure
Dok.-Nr/Doc. No.:
Ausgabe/Issue:
Überarbtg./Rev.:
Seite/Page:
COL–RIBRE–ICD–0025–00
4 Datum/Date: 17/04/98
B Datum/Date: 31/08/00
662 von/of: 662
It will thus possibly exist within the MDB in many different forms
or instances (CU occurrences) commonly referred to as versions,
e.g. DMS Version 3.2.1.
In the Configuration Management (CM) context, however, the various
CU occurrences. are classified according to the types of changes
that have been made. The terms versions, issues, and revisions are
then used to differentiate between the following 3 cases:
– Modifications due to requirements changes which result in a new
version
– Modifications due to design changes which result in a new issue.
– Modifications due to bug fixes, repairs or other corrections (affecting
neither the design nor the requirements) which result in a new
revision.
(In the above example, the CU Identifier ”DMS Version 3.2.1”,
therefore, refers to Version 3, Issue 2, Revision 1 of the DMS)
Visibility When a file is accessible by a a normal UNIX program (excluding
’remote utilities’), then the file is considered ’visible’. Without a network,
visibility is restricted to local disks, tapes and other peripherals.
When the system is integrated into a network, then some files/
directories on other devices in the network may become ’visible’ to
the local machine through the use of NFS. Another way to describe
it would be: a file is ’visible’ when its name can be specified (opened)
to the UNIX system call ”open”.
NOTE: ’Visibility’ has nothing to do with a user’s access rights to a
particular file. A file may be ’visible’ to the host program running
with ’root’ privileges but at the same time be inaccessible to a normal
user.
W
Widget An object providing a user interface abstraction (for example, a
Scrollbar widget).
X
X11 X Window System Version 11 is a library which provides functions
to write applications with a graphical user interface running on a network.
Working Directory A disc space containing the intermediate files for a specific tool and
a specific user.
Workstation Node In VICOS, a workstation node is a logical node which provides the
interface to the operator and executes operator related functions for
test execution monitoring and control, for test setup, for test preparation
and for test evaluation. It runs the VICOS HCI, the TSCV and
the TEV.
A logical workstation node has to be mapped to a physical processor
where it runs on (workstation processor).

CHAPTER 1 :
INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1
1.1 Identification and Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2
1.2 Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2
1.3 Reader Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2
1.4 Type of Described Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3
CHAPTER 2 :
APPLICABLE AND REFERENCE DOCUMENTS . . . . . . . . . . . . . . .
4
2.1 Applicable Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5
2.2 Reference Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7
CHAPTER 3 :
GENERAL DESCRIPTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8
3.1 CGS Functional Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9
CHAPTER 4 :
INFRASTRUCTURE INTERFACES . . . . . . . . . . . . . . . . . . . . . . . . . . .
12
4.1 Operating System Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13
4.1.1 Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13
4.1.2 File System Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14
4.1.2.1 Home Directories for CGS Products . . . . . . . . . . . . . . . . . . . . .
14
4.1.2.1.1 Sun Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14

4.1.2.1.1.1 GSAF Home Directory . . . . . . . . . . . . . . . . . . . . . . . . .
14
4.1.2.1.1.2 CGS Home Directory . . . . . . . . . . . . . . . . . . . . . . . . . . .
14
4.1.2.1.1.3 Product Home Directories . . . . . . . . . . . . . . . . . . . . . . .
14
4.1.2.1.2 HP Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14
4.1.2.2 Subdirectories for CGS Products . . . . . . . . . . . . . . . . . . . . . . . .
15
4.1.2.2.1 Start–Up Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15
4.1.2.2.2 Executable Images (Platform dependent) . . . . . . . . . . . . . .
15
4.1.2.2.3 Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
15
4.1.2.2.4 Utilities and Tools (Platform dependent) . . . . . . . . . . . . . . .
15
4.1.2.2.5 Configuration Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16
4.1.2.2.6 Runtime Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16
4.1.2.2.7 Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
16
4.1.2.3 Special Checkout related Directories . . . . . . . . . . . . . . . . . . . . .
16
4.1.2.3.1 Test Node Directory on the HP Test Nodes . . . . . . . . . . . . .
16
4.1.2.3.2 Test Node Directories on the SUN Database Server . . . . . .
17
4.1.2.4 Home Directories For CGS Extensions And Add–Ons . . . . . . .
17
4.1.2.4.1 Special Application Software (SAS) . . . . . . . . . . . . . . . . . .
17
4.1.2.4.2 Command And Measurement Adaptation Software
(CMAS) . . . . . .
18
4.1.2.4.3 Mission Database Support Software (MDB_SS) . . . . . . . . .
18
4.1.3 Common User Environment Files . . . . . . . . . . . . . . . . . . . . . . . . . .
20
4.1.3.1 Central Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21
4.1.3.1.1 Central ”login” Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21
4.1.3.1.2 Central ”cshrc” Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
23
4.1.3.1.3 Central ”logout” Script . . . . . . . . . . . . . . . . . . . . . . . . . . . .
27

4.2 Relational Database Management System . . . . . . . . . . . . . . . . . . . .
28
4.2.1 Functional Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
28
4.2.1.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
28
4.2.2 Database Installation and Configuration . . . . . . . . . . . . . . . . . . . . .
28
4.2.2.1 Predefined Object Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
28
4.2.2.1.1 User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
28
4.2.2.1.2 Tablespaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
28
4.2.2.1.3 Public Synonyms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
28
4.2.2.1.4 CRT Device Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
28
4.2.2.2 ORACLE Configuration Parameters . . . . . . . . . . . . . . . . . . . . .
29
4.2.2.2.1 INIT.ORA Configuration File . . . . . . . . . . . . . . . . . . . . . . .
29
4.2.2.2.2 Rollback Segments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31
4.2.3 Commercial Product Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
32
4.3 Communication Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
33
4.3.1 Internet Port Number Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . .
33
4.3.2 Commercial Product Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
34
4.4 Presentation Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
35
4.5 DataViews Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
36
4.6 CGS Top Level User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
37
4.6.1 Error Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
38
4.6.1.1 Definition of Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
38
4.6.1.2 Provided Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
38

4.6.1.3
39
Reporting Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.1.4
39
Addressing the Error Message . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.1.5
39
Displaying and Logging the Error Message . . . . . . . . . . . . . . .
4.6.1.6
40
Central Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.1.7
40
Supplying a Timestamp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.1.8
40
Supplying Extra Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.1.9
40
Error Message Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.1.10
41
Error Message Components . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.1.11
42
Handling of Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.2
44
Error Report Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.3
48
Error Services Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.4
52
Timestamp Services Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.5
55
File Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.5.1
55
File Names and Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.5.1.1
55
Session Error Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.5.1.2
55
Process Response Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.6.6
56
Installation Registry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.7 Other Commercial Products Version . . . . . . . . . . . . . . . . . . . . . . . . .
57
4.8 CGS_Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
58
4.8.1 Informal Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
58
4.8.2 Formal Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
58

CHAPTER 5 :
SOFTWARE DEVELOPMENT INTERFACES . . . . . . . . . . . . . . . . . .
59
5.1 Documentation Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
60
5.1.1 Format of Imported Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . .
61
5.1.1.1 Interface Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
61
5.1.1.2 Interface Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
61
5.1.1.2.1 Document Location Conventions . . . . . . . . . . . . . . . . . . . .
61
5.1.1.2.2 Document Filename Conventions . . . . . . . . . . . . . . . . . . . .
61
5.1.1.2.3 Importable DOCUMENT Contents . . . . . . . . . . . . . . . . . . .
61
5.2 Generic Compiler Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
63
5.2.1 Generic C Compiler Environment Integration Interface . . . . . . . . .
63
5.2.2 Generic Ada Compiler Environment Integration Interface . . . . . . .
63
5.3 Generic Tool Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
64
CHAPTER 6 :
MISSION PREPARATION INTERFACES . . . . . . . . . . . . . . . . . . . . . .
65
6.1 Package MPS_DEFINITIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
66
6.1.1 Exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
66
6.1.1.1 Exceptions due to internal MDB / ORACLE errors . . . . . . . . .
66
6.1.1.2 SID_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
66
6.1.1.3 AUTHORIZATION_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . .
66
6.1.1.4 USE_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
66
6.1.1.5 ENVIRONMENT_ERROR , CDU/CCU_ERROR . . . . . . . . . .
66

6.1.1.6 PARAMETER_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
67
6.1.1.7 CONSISTENCY_ERROR . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
67
6.1.2 Formal Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
68
6.2 MDB Standard Entities and Application Programmer Interface . .
85
6.3 CLS Global . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
86
6.3.1 General CLS Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
86
6.3.2 Runtime Representation of UCL Types . . . . . . . . . . . . . . . . . . . . . .
88
6.4 Flexible Tool Invocation Interface . . . . . . . . . . . . . . . . . . . . . . . . . . .
94
6.5 Foreign Key Support / PUI Support . . . . . . . . . . . . . . . . . . . . . . . . .
95
6.6 MDB Batch Data Entry Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
96
6.7 I–Code Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
97
6.7.1 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
97
6.7.2 I–Code Record Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
98
6.7.3 I–Code Record Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
99
6.7.4 Architecture of the Stack Machine . . . . . . . . . . . . . . . . . . . . . . . . .
99
6.7.5 I–Code Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
102
6.7.5.1 Instruction Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
103
6.7.5.2 Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
104
6.7.5.3 Detailed I–code Instructions Table . . . . . . . . . . . . . . . . . . . . . .
107
6.7.5.3.1 Instructions with implied parameter . . . . . . . . . . . . . . . . . .
107

6.7.5.3.2 Load Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
110
6.7.5.3.3 Load Address Instructions . . . . . . . . . . . . . . . . . . . . . . . . . .
114
6.7.5.3.4 Store Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
115
6.7.5.3.5 MOVE and CAT Instructions . . . . . . . . . . . . . . . . . . . . . . .
118
6.7.5.3.6 Stack Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
119
6.7.5.3.7 Numerical Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
120
6.7.5.3.8 Comparison Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . .
130
6.7.5.3.9 BOOLEAN negation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
140
6.7.5.3.10 Allocation Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
140
6.7.5.3.11 Jump Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
141
6.7.5.3.12 Special Jump Instructions . . . . . . . . . . . . . . . . . . . . . . . . . .
142
6.7.5.3.13 Iterative Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
143
6.7.5.3.14 Switch Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
144
6.7.5.3.15 Procedure/Function Call Instructions . . . . . . . . . . . . . . . . .
146
6.7.5.3.16 Conversion Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . .
148
6.7.5.3.17 Miscellaneous Instructions . . . . . . . . . . . . . . . . . . . . . . . . . .
150
6.7.5.3.18 System Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
151
6.7.5.3.19 No–operation Instruction . . . . . . . . . . . . . . . . . . . . . . . . . . .
155
6.7.6 Sample AP and Corresponding I–Code . . . . . . . . . . . . . . . . . . . . . .
156
6.7.7 Procedural Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
159
6.8 Parameter Encoding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
169
6.8.1 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
169
6.8.2 Parameter Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
169

6.8.3 Encoding Scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
170
6.8.3.1 External Scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
170
6.8.3.2 Internal Scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
171
6.8.4 Example (Call of a library procedure) . . . . . . . . . . . . . . . . . . . . . . .
172
6.8.5 Stack Machine Representation of AP Parameters . . . . . . . . . . . . . .
173
6.9 Flight Synoptic Display Representation Format . . . . . . . . . . . . . . .
174
6.10
175
FWDU Supported Sammi API Interfaces . . . . . . . . . . . . . . . . . . . . .
6.10.1
175
File Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.10.2
176
Logical Server Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.10.3
177
Commands to the On–Board System . . . . . . . . . . . . . . . . . . . . . . . .
6.10.3.1
177
Software Commanding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.10.3.2
177
Pre–Defined Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.10.3.3
178
Window Association Information (WAF) . . . . . . . . . . . . . . . . .
6.10.4
180
FWDU Applied Type Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.10.4.1
180
Mapping between On–board and CGS standard end item types
6.10.4.2 Mapping between CGS standard end item types and Sammi
data types . .
180
CHAPTER 7 :
CHECKOUT AND SIMULATION INTERFACES . . . . . . . . . . . . . . . .
182
7.1 Test Setup Invocation Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
183
7.2 VICOS Types Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
185
7.3 HCI Abstract Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
192

7.3.1 General Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
192
7.3.2 Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
193
7.3.2.1 SET Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
193
7.3.2.2 GET Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
193
7.3.2.3 ALTERNATIVE Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
193
7.3.2.4 PACK Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
194
7.3.2.5 UNPACK Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
194
7.3.2.6 PACKED_SIZE Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
194
7.3.2.7 ADD Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
194
7.3.2.8 Operations on tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
194
7.3.2.9 Exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
194
7.3.2.10 Particular Remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
195
7.3.2.10.1 On Synchronisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
195
7.3.2.10.2 On Packing/Unpacking . . . . . . . . . . . . . . . . . . . . . . . . . . . .
195
7.3.3 ADT Physical Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
196
7.3.4 ADT CCSDS Packet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
203
7.3.5 Binary Buffer ADT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
220
7.4 Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
228
7.5 TES DEFINITIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
244
7.6 TES Abstract Data Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
249
7.6.1 General Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
249

7.6.2 Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
250
7.6.2.1 SET Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
250
7.6.2.1.1 GET Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
250
7.6.2.1.2 ALTERNATIVE Function . . . . . . . . . . . . . . . . . . . . . . . . . .
251
7.6.2.1.3 PACK Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
251
7.6.2.1.4 UNPACK Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
251
7.6.2.1.5 PACKED_SIZE Function . . . . . . . . . . . . . . . . . . . . . . . . . .
251
7.6.2.1.6 ADD Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
251
7.6.2.1.7 Operations on tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
251
7.6.2.1.8 Exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
251
7.6.2.1.9 Particular Remarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
252
7.6.2.1.10 On Synchronisation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
252
7.6.2.1.11 On Packing/Unpacking . . . . . . . . . . . . . . . . . . . . . . . . . . . .
252
7.6.3 ADT Raw Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
253
7.6.4 ADT Engineering Value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
261
7.6.5 ADT ADU Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
267
7.6.6 ADT ADU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
278
7.6.7 ADT GDU Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
291
7.6.8 ADT GDU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
304
7.7 TES Application Programmer Interface . . . . . . . . . . . . . . . . . . . . . .
311
7.8 VICOS Housekeeping Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
330
7.9 System Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
338

7.9.1 UCL Ground System Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
338
7.9.1.1 Routines Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
338
7.9.1.2 UCL Ground System Library Specification . . . . . . . . . . . . . . .
339
7.9.1.3 Interface Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
366
7.9.1.3.15 General Conversion Routines . . . . . . . . . . . . . . . . . . . . . . .
423
7.9.2 UCL GROUND_TO_OB_LIB System Library . . . . . . . . . . . . . . .
425
7.9.2.1 Routines Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
425
7.9.2.2 UCL GROUND_TO_OB_LIB System Library Specification .
425
7.9.2.3 Interface Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
431
7.9.3 TCL System Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
447
7.9.3.1 Routines Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
447
7.9.3.2 TCL_LIBRARY Specification . . . . . . . . . . . . . . . . . . . . . . . . .
448
7.9.3.3 TCL ASCII Format Specification . . . . . . . . . . . . . . . . . . . . . . .
459
7.10 Onboard Commands and Responses . . . . . . . . . . . . . . . . . . . . . . . . .
461
7.10.1 Software Commands (SWOP_Command) . . . . . . . . . . . . . . . . . . .
461
7.10.1.1 CCSDS Header for Software Commands . . . . . . . . . . . . . . . . .
461
7.10.1.2 CCSDS Data Field for Software Commands . . . . . . . . . . . . . .
462
7.10.1.3 Response Packet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
462
7.10.1.3.1 CCSDS Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
462
7.10.1.3.2 CCSDS Data Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
463
7.10.2 FLAP Execution Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
464
7.10.2.1 CCSDS Header for FLAP Execution Requests . . . . . . . . . . . .
464

7.10.2.2
464
CCSDS Data Field for FLAP Execution Requests . . . . . . . . . .
7.10.2.3
465
Response Packet for FLAP Execution Requests . . . . . . . . . . .
7.10.2.3.1
465
CCSDS Header . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.10.2.3.2
465
CCSDS Data Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.11
466
DBS Types and Constants Definitions . . . . . . . . . . . . . . . . . . . . . . . .
7.12
482
DBS Application Programmer Interface . . . . . . . . . . . . . . . . . . . . . .
7.13
490
TEV Types and Constants Definitions . . . . . . . . . . . . . . . . . . . . . . . .
7.14
510
TEV Application Programmer Interface . . . . . . . . . . . . . . . . . . . . .
7.15
567
Test Evaluation Invocation Interface . . . . . . . . . . . . . . . . . . . . . . . . .
7.15.1
567
TEV Invocation for Interactive Mode . . . . . . . . . . . . . . . . . . . . . . .
7.15.2
567
TEV Batch Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.15.3
568
TEV in Office Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.16
569
EXCEL Representation Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.17
570
Command and Measurement Adaptation System . . . . . . . . . . . . . .
7.18
632
Data Types supported by CGS in TES_API and CMAS_IF . . . . .
7.18.1 CGS Data Types Supported
. . . . . . . .
632
7.18.2 CGS Data Types: UCL to Raw Value Conversion
. . . . . . . .
635
APPENDIX A :
ACRONYMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
637
APPENDIX B :
DEFINITIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
645

Figure 1.3–1 CGS Interface Control Document Structure . . . . . . . . . . . . .
3
Figure 4.1.2.3.2–1 Example of Mounting Test Node Directories on the Database
Server. . . . . . . . . .
17
Figure 6.7–1 I–Code Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
98
Figure 6.7–2 Stack Machine Runtime Layout . . . . . . . . . . . . . . . . . . . . . . .
102
Figure 6.8.3–1 External Parameter Encoding Scheme . . . . . . . . . . . . . . . . . .
170
Figure 6.8.3–2 Internal Parameter Enoding Scheme . . . . . . . . . . . . . . . . . . .
171
Figure 6.8.3–1 Encoded Parameter List . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
172
Figure 6.8.3–1 Global Data Frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
173