UM_REC_ES010006101UM03_C.doc

7/29/2019 UM_REC_ES010006101UM03_C.doc

1/61

ATMAS Division UNCLASSIFIED ES010006101UM03E184

Issue C

Date: 28/01/2005

Modernization Project of Romanian ATM System

USER MANUAL

for

RECORDING

CDRL No. :

ISSUED BY :

Alenia Marconi Systems S.p.A.Via Tiburtina Km 12.400 - Roma

ITALY

The copyright in this document is the property ofAlenia

Marconi Systems S.p.A.The document is supplied on theexpress understanding that it is to be treated as confidential

and that it may not be copied, used or disclosed to others inwhole or in part for any purpose except as authorized in

writing byAlenia Marconi Systems S.p.A .

This document contains a total of 62 pages

UNCLASSIFIED Page 1

TEMP-UK (ATC-Km 12.400) rev 6

7/29/2019 UM_REC_ES010006101UM03_C.doc

2/61


Issue C

Date: 28/01/2005

DOCUMENT SECURITY CLASSIFICATION:

This document is intended for the use of the recipient only, and for communication to such persons as may be

required to be acquainted with its contents in the course of their duties.

The recipient, and any other person to whom the recipient has communicated the contents of this document,

shall threat this document in accordance with the requirements of Alenia document "Security Instructions", 15

February 1992.

Any person others the authorised holder upon obtaining possession of this document, by finding or otherwise,should forward it by registered post, together with his name and address, in a sealed envelope to:

Ufficio Sicurezza

Alenia Marconi Systems S.p.A.

Via Tiburtina 12.400

00131 Roma

ITALY

Any questions arising from this document should be addressed to:

Maurizio MANZO

Alenia Marconi Systems S.p.A.

Air Traffic Management & Airports Systems

Via Tiburtina, Km 12.400 - 00131 Roma

ITALY

Telephone +39-06 4150-3689

Fax +39-06 4150-3729

UNCLASSIFIED Page 2

7/29/2019 UM_REC_ES010006101UM03_C.doc

3/61


Issue C

Date: 28/01/2005

Issue Authority

Prepared by :

(SWSM)......................................................

(Maurizio MANZO)

Date:

Approved by:

(Project Leader) ......................................................

(Fabio MORIGGI)

Date:

UNCLASSIFIED Page 3

7/29/2019 UM_REC_ES010006101UM03_C.doc

4/61


Issue C

Date: 28/01/2005

REVISIONS RECORD SHEET

This sheet is a record of revisions to this document.

Issue/AL Date Revised Pages Document Change Note

(DCN)

A 22/11/01 MRT_RPB_TCA UM

B 27/03/03 First Issue

C 28/01/05 Page 13, Page 20

UNCLASSIFIED Page 4

7/29/2019 UM_REC_ES010006101UM03_C.doc

5/61


Issue C

Date: 28/01/2005

LIST OF ABBREVIATIONS

ABBR. DESCRIPTION

ACC Area Control Centre

ACD Advanced Common Database

ACK Acknowledge

ACL Arrival CLearance

ACR Arrival Clearance with Re-routing

AFTN Aeronautical Fixed Traffic Network

AIS Aeronautical Information Service

ALV Authorization LeVel

APP APProach control

ARR ARRival

ASF Assistant function

ASQ Arrival SeQuencing

ASS Assistant Controller

ATA Actual Time of Arrival

ATC Air Traffic Control

ATD Actual Time of Departure

ATI Actual Time of Inbound

ATM Air Traffic Management

ATO Actual Time Over

ATS Air Traffic Service

ATW Auxiliary Working Position

BRW BroWse

CNL CaNceL

CoMap Coordination Maps display

CSCI Computer Software Configuration Item

CWP Controller Working Position

DAIW Danger Area Infringement Warning

DARD Direct Access Radar Data

UNCLASSIFIED Page 5

7/29/2019 UM_REC_ES010006101UM03_C.doc

6/61


Issue C

Date: 28/01/2005

DCL Departure CLearance

DCR Departure Clearance with Re-routingDEP DEParture list

DIS DISabled

DLA DeLAy departure

DMD Dangerous area Map Display

EMG EmerGency

EST ESTimate

ETA Estimated Time of Arrival / Estimated Exit Time from the feeding fix (in

ACL order)

ETD Estimated Time of Departure

ETI Estimated Time of Inbound

ETL Estimated Time of Landing

ETO Estimated Time Over

EXE EXEcutive function

FCK Formality ChecK

FCN Flight data CaNcellation

FDM Flight Data Management

FDP Flight Data Processing

FIR Flight Information Region

FL Flight Level

FLD FLDA Displaying

FLDA FLight DAta page list

FLDI FLight DIrectory listFPLM Flight Plan Message list

FTR File TeRmination

GlobMap Global Mps display

I/O Input/Output

ICAO International Civil Aviation Organization

INBFIX INBound (entry) FIX

INI INItialize

UNCLASSIFIED Page 6

7/29/2019 UM_REC_ES010006101UM03_C.doc

7/61


Issue C

Date: 28/01/2005

LND LANding reportLRW Landing RunWay

LSV LaSt leVel

LVA planned/cleared LeVel Assignment

MET METeorological

MIL MILitary

MNG MaNaGement

MPG Map Generation System

MRT Multi Radar Tracking

MSAW Minimum Safe Altitude Warning

NAVAID NAVigational AID

NM Nautical Miles

NOTAM NOtice to AirMan

NVS NaVigator aid

OBT Off Block Time

ODS Operator input and Display System

ONL ON Line

OP Operational

OPRSUP OpeRational SUPervisor

PCN Planning Cancellation

PEN PENding tracks

PKB ParKing Bay allocation

PLB PlayBack

PLC Planning Controller

PLN PlaNning function

QNH Barometric pressure / enter QNH

RCL en-Route CLearance

RCR en-Route Clearance with Re-routing

RDP Radar Data Processing

UNCLASSIFIED Page 7

7/29/2019 UM_REC_ES010006101UM03_C.doc

8/61


Issue C

Date: 28/01/2005

REC RECording

REG REGistration numberREP Position REport

REV estimate REVision

RHP Radar Head Processor

RNG RaNGe scale

RWY RunWaY

SBY Stand-BY

SID Standard Instrumental Departure

SIG fir SIGmet

SMD System Messages Dispatching (CSCI)

SRL SSR code ReLease

SSR Secondary Surveillance Radar / SSR code assignment

STAR STandard Approaching Route

SUM Software User Manual

SUP SuPerVisor

SW SoftWare

TAS True Air Speed / change True Air Speed

TBD To Be Defined

TCA Traffic Conflict Alert

TKF TaKe-oFf report

TMA TerMinal Area

TMS Terminal Area management

TRW departure RunWay

TXT free TeXT

TWR control ToWeR

VDU Video Display Unit

VFR Visual Flight Rule

WTC WaTCher

UNCLASSIFIED Page 8

7/29/2019 UM_REC_ES010006101UM03_C.doc

9/61


Issue C

Date: 28/01/2005

TABLE OF CONTENTS

1. SCOPE .......................................................................................................................................................11

1.1 IDENTIFICATION......................................................................................................................................11

1.2 SYSTEM OVERVIEW.................................................................................................................................12

1.3 DOCUMENT OVERVIEW...........................................................................................................................14

2. REFERENCED DOCUMENTS ..............................................................................................................15

3. CONVENTIONS ......................................................................................................................................16

4. THE INTERFACES DESCRIPTION ....................................................................................................17

4.1 INTERFACESTOWARDSSYSTEMCOMPONENTS ..............................................................................................17

4.2 OPERATORINTERFACES ...........................................................................................................................18

5. FUNCTIONALITY ..................................................................................................................................19

5.1 CONFIGURATIONANDINITIALIZATIONCOMMANDS........................................................................................21

5.1.1 ORDERS.............................................................................................................................................22

5.1.1.1 Orders Description.............................................................................................................................23

5.1.1.2 Orders sequence.................................................................................................................................35

5.1.1.3 Example of Configuration orders....................................................................................................36

5.1.2 MASKS..............................................................................................................................................37

5.1.3 PRINTS ..............................................................................................................................................37

5.2 START/STOPRECORDINGCOMMANDS..........................................................................................................38

5.2.1 ORDERS.............................................................................................................................................385.2.1.1 Orders Description.............................................................................................................................39

5.2.1.2 Orders sequence.................................................................................................................................41

5.2.1.3 Examples of Recording orders........................................................................................................42

5.2.2 MASKS..............................................................................................................................................43

5.2.3 PRINTS ..............................................................................................................................................43

5.3 INFORMATIONPRESENTATIONCOMMANDS...................................................................................................44

5.3.1 ORDERS.............................................................................................................................................44

5.3.1.1 Orders Description.............................................................................................................................45

5.3.1.2 Orders sequence.................................................................................................................................53

5.3.1.3 Examples of Informations presentation orders................................................................................53

UNCLASSIFIED Page 9

7/29/2019 UM_REC_ES010006101UM03_C.doc

10/61


Issue C

Date: 28/01/2005

5.3.2 MASKS...............................................................................................................................................53

5.3.3 PRINTS ..............................................................................................................................................53

6. OPERATIVE EXAMPLES .....................................................................................................................54

7. ORDERS LIST .........................................................................................................................................54

8. ERRORS AND ALARMS MESSAGE ...................................................................................................55

8.1 GENERALITY.........................................................................................................................................558.2 MESSAGES............................................................................................................................................55

8.3 ERRORS................................................................................................................................................57

8.4 ALARMS...............................................................................................................................................58

9. DEGRADED EXECUTION ....................................................................................................................60

10. OPERATIVE STARTING .....................................................................................................................61

UNCLASSIFIED Page 10

7/29/2019 UM_REC_ES010006101UM03_C.doc

11/61


Issue C

Date: 28/01/2005

1. SCOPE

1.1 IDENTIFICATION

This document is related to the package CSCI Recording

Identification number : 3 Title : Software User Manual for the advanced CSCI Recording Abbreviation : REC


7/29/2019 UM_REC_ES010006101UM03_C.doc

12/61


Issue C

Date: 28/01/2005

1.2 SYSTEM OVERVIEW

The Recording Function records all the selected messages passing through the duplicated Local Area Network

(LAN).

The recorded data are stored in a duplicated Hard Disk (dedicated to Recording-playback) , in order to store a

large quantity of information.

In addition, the last 30 minutes are recorded on a separate area of the Hard Disk, to permit the Fast View

facility.

This function permits to immediately view what happened during the last 30 minutes, without affecting the

Operative recording.

In addition, the capacity of the streamer tape and of the voice recorder guarantees a 24 recording without

operator intervention.

In detail, the following messages are recorded:

- System tracks, coming from MRT processing (RDP or RFB node)

- Local tracks (mono-radar/DARD tracks)

- Weather data

- Orders from controllers

- Orders of supervision coming from certain

(central processors, workstation, Monitoring system)

- Diagnostic messages coming from displays,

central processor,RHPs

- Control messages (time,date,etc.)

- Auxialiary data

- Flight data

In summary, the recording function is able to store all the messages which are directly addressed to it through

the LANs.

Recording uses a system service function which constantly refreshes system data and display configurations,

to maintain the configuration aligned.


7/29/2019 UM_REC_ES010006101UM03_C.doc

13/61


Issue C

Date: 28/01/2005

The complete system configuration is stored at the start of H/D-Tape and then changes are recorded, to enable

the correct reconstruction of the situation.

In addition to real data, time marks are stored every minute and all the recorded messages are time stamped.

To sum up, the recording function provided for MATSMP guarantees the recording of all data required to

reproduce the live presentation of all CWP equipped position.


7/29/2019 UM_REC_ES010006101UM03_C.doc

14/61


Issue C

Date: 28/01/2005

1.3 DOCUMENT OVERVIEW

This document describes the procedures to be followed for the execution of the XRE CSCI.

The paragraph 1 supplies a brief description of the SATCAS system and of the content of thisdocument.

The paragraph 2 supplies a list of referenced documents.

The paragraph 3 supplies a glossary.

The paragraph 4 contains the description of XRE interfaces with external world.

The paragraph 5 provides informations about :

Recording CSCI brief functional description. Operator commands description.

The paragraph 8 provides the list of messages and errors notifications issued from XRE CSCI.


7/29/2019 UM_REC_ES010006101UM03_C.doc

15/61


Issue C

Date: 28/01/2005

2. REFERENCED DOCUMENTS

Software Requirement Specification E000XRE0-D01SRS. DoD_2167A_DI-MCCR-80019A.


7/29/2019 UM_REC_ES010006101UM03_C.doc

16/61


Issue C

Date: 28/01/2005

3. CONVENTIONS

CPU-M : Central Processor Unit - Master. It is the Master Node.

CPU-S : Central Processor Unit - Slave. It is the Slave Node.

LAN : Local Area Network. Comunication Line among the nodesMT : Monitoring Tecnico. It is a system function.XPL : Play-Back functionSP : Serial Printer.

TOM : Tecnical Monitoring.DAT : Dat Unit. It is the digital data recording unit. Each unit is supplied of a Tape.

FL : File Unit. It is the digital data recording unit. Each unit is supplied of a File


7/29/2019 UM_REC_ES010006101UM03_C.doc

17/61


Issue C

Date: 28/01/2005

4. THE INTERFACES DESCRIPTION

4.1 INTERFACES TOWARDS SYSTEM COMPONENTS

The interfaces between Recording and the external world are :

Identificator : NSV_Message

Description : They are all the messages exchanged with NSV CSCI and the informations about theoperations on the peripherals.

Informations type : To Degrade-To Restore the peripherals performance

Characteristic of exchange : Via Path

Referenced Documents : Interface Requirements Specification XRE

Identificator : NSV_Change_State

Description : It is the message that contains the XRE activation according to node role.

Informations type : XRE activation (Master/Stand_by); To Degrade-To Restore the peripherals

performance



Identificator : SMD_Command_To_XRE,XRE_Message_To_SMD, Run_Pause_OrderDescription : They are operator orders and other kind of messages exchanged with SMD function

Informations type : These are that informations that correspond to the orders sent from the operatorand the diagnostic messages




7/29/2019 UM_REC_ES010006101UM03_C.doc

18/61


Issue C

Date: 28/01/2005

Identificator : XRE_XPL_Message

Description : These are the requests and the answers sent from XPL to XRE (and viceversa) for theperipherals handling

Informations type : These are the informations regarding to the peripherals used

Characteristic of exchange : Via Lan


4.2 OPERATOR INTERFACES

The interface with operator is represented by possible operator commands.


7/29/2019 UM_REC_ES010006101UM03_C.doc

19/61


Issue C

Date: 28/01/2005

5. FUNCTIONALITY

The main purpose of XRE CSCI is to record data and events occurred in system.The recording functionalities are controlled by:1. The operator orders messages coming from SMD. They are the messages that contain the

recording operator orders receveid from the enabled terminals or consoles and dispatchedtowards RECording by SMD.

By means these messages an operator can drive the RECording CSCI: about the operations to do on disk files, to select the kind of messages to record, to start or to stop the storing of data messages on the recording supports.

2. NSV messages. These message contain informations about:

The role changing of the node (from Master to Stand-by and viceversa). The status changing (ON or OFF) of the streamer peripherals.

RECording CSCI can handle two streamer devices and a mirrored disk.When it is resident on a node of a couple of computers, it is able to drive these devices only when it

is on the master node of the couple.The RECording CSCI on the stand-by node is always updated about the changing of the content ofthe main tables and variables by the RECording CSCI on the master node by means proper messagesvia Lan and an alignment file on disk.In this way, after a commutation master->stand-by, the RECording activities can continue.

Files on disk is a support where it is possible to store digital data.

The five files on disk handled by RECording CSCI are identificated in two different way.

The first one is the physical number of the file. It is a number which value is 1, 2, 3, 4 or 5 and it isalways associated to a specific file unit.

The second one is the logical name of the file unit. The logical name can be: FLA, FLB, FLC.FLA is always the main unit and FLB is always the continuation unit. FLC is used as the reserve filein the event of fault of FLA OR FLB or when the operator orders a change of the main file with FLC(see CHF command).

Normally the data are stored both on tape and on disk file. In the event of fault of disk the data arestored only on tape.

The RECording activities start on the FLA unit; when FLA file is near at the end (eof), RECordingCSCI changes file and starts to store the data on the FLB file, if it is assigned.Otherwise, RECording CSCI uses FLA file again, it starts to store the from the beginning of FLA fileand overwrites the data just stored.


7/29/2019 UM_REC_ES010006101UM03_C.doc

20/61


Issue C

Date: 28/01/2005

The SMD CSCI receives system orders from the enabled terminals and consoles, searches thedestination CSCI, and then dispatches the orders towards it.

A CSCI that receives and executes a system order has to send towards SMD an acknowledgemessage. SMD dispatches this acknowledge towards the enabled terminals and consoles.

In this way an operator can give (and receive answers) commands towards RECording CSCI fromthe enabled terminals and consoles.

The commands for XRE have the following format :

REC CCC A...A A...A A...A

where :REC : REC threeliteral for SMD to understand that the command is for Recording.

CCC : It is the generic command

A...A : It is the parameter(s) of the command and it is different from command to command

The RECording CSCI answers to an order with a message that contains the string of the order plusthe result of the execution of the order itself. If the syntax of the order is not correct the answer is

the string of the order plus the string SYNTAX ERROR.

The commands towards RECording may be divided into three categories: Configuration and initialization: To configure and to initialize the streamer devices and the

parameters of selection of the data to record. Start/stop recording : To start or stop the storing of the selected data on the recording supports.

Information presentation : to show some informations about the status of the peripherals, thesetting of the parameters, etc.

The RECording CSCI doesnt record any information if REAL and OPERATIVE are in different

LAN (see REL LAS order on XCD user manual).


7/29/2019 UM_REC_ES010006101UM03_C.doc

21/61


Issue C

Date: 28/01/2005

5.1 CONFIGURATION AND INITIALIZATION COMMANDS

Before starting the recording of data the operator has to give to RECording CSCI the informationabout which is the main file unit (ASF command).

If the operator wants to record some data not selected for default, he has to give the SEL and MOVcommands.

Naturally, there are also the commands to deassign a file.In the same way if operator wants that the recording of data continues on the continuation file at theend of the main file and to avoid the overwriting of the main file, he has to provide the informationabout which is the continuation file unit (ASF command).


7/29/2019 UM_REC_ES010006101UM03_C.doc

22/61


Issue C

Date: 28/01/2005

5.1.1 ORDERS

The list of the commands that allows the things said before is:

REC SEL LAN [NOT] [rrrc] [xxx, xxx,..,xxx] Selection parameters (optional)REC MOV ACT PRV Puts the active table into the temporary table (optional)

REC MOV ALL PRV Selection of all the data in the temporary table (optional)

REC MOV DEF PRV Puts the default table into the temporary table (optional)

REC MOV NIL PRV Clears out the temporary table (optional)

REC MOV ACT PRV Puts the temporary table into the active table (optional)

REC ASF {FLA,FLB,FLC} n Assigned phisycal-logical File Unit

REC DAF {FLA,FLB,FLC} Deassigned phisycal-logical File Unit

REC CHF {FLB,FLC} Change phisycal-logical File Unit

REC LAN { A , B } Select main LAN on which to send messages


7/29/2019 UM_REC_ES010006101UM03_C.doc

23/61


Issue C

Date: 28/01/2005

5.1.1.1 Orders Description

5.1.1.1.1 . REC MOV ALL PRV (OPTIONAL)

Description: This command is part of the selection OPS orders.It fills up the temporary tablewith all the selection parameters in the their max configuration.

Controls: No;

Result: The command is executed. If after this command it enables the parameters by MOVPRV ACT, the recording will record all the data coming from LAN and RHP.


7/29/2019 UM_REC_ES010006101UM03_C.doc

24/61


Issue C

Date: 28/01/2005

5.1.1.1.2 . REC MOV ACT PRV (OPTIONAL) Description: This command is part of the selection OPS orders.It puts the selection

parameters of the active table into the temporary table. Controls: No;

Result: From this time the active parameters are removed in the temporary table.


7/29/2019 UM_REC_ES010006101UM03_C.doc

25/61


Issue C

Date: 28/01/2005

5.1.1.1.3 . REC MOV DEF PRV (OPTIONAL) Description: This command is part of the selection OPS orders. It puts the selection

parameters of default in the temporary table.

Controls: No;

Result: The command is executed.


7/29/2019 UM_REC_ES010006101UM03_C.doc

26/61


Issue C

Date: 28/01/2005

5.1.1.1.4 . REC MOV NIL PRV (OPTIONAL)

Description: This command is part of the selection OPS orders.It clears out the temporary

table.This command nullifyes all the SEL commands used to modify the temporary table. Controls: No;

Result: The command is executed. If after this command it enables the parameters by MOVPRV ACT, the recording will record no message suitable for the selection.


7/29/2019 UM_REC_ES010006101UM03_C.doc

27/61


Issue C

Date: 28/01/2005

5.1.1.1.5 . REC MOV PRV ACT (OPTIONAL)

Description: This command is part of the selection OPS orders. It puts the selectionparameters of the temporarytable in the active table.

Controls: No;

Result: From this time the temporary parameters are become effective for the selection of thedata in input to the Recording. If it is operative the command will immediately be effective,otherwise it will be effective after the RUN command. If the XRE is operative,the selection

parameters will be recorded on the TU.


7/29/2019 UM_REC_ES010006101UM03_C.doc

28/61


Issue C

Date: 28/01/2005

5.1.1.1.6 . REC SEL LAN [NOT] [rrrc] [xxxxx, xxxxx,...,xxxxx] (OPTIONAL)

Description:

where:

NOT = It means that the data selected by the parameters xxxxx will not be processed. If thereisnt NOT,it means that the data selected by the parameters xxxxx will be processed.

rrr = This treeliteral indicates the code of sender or addressee according to the field xxxxx. It

can be a function or an apparatus. The codes rrr are defined at system level. Thethreeliteral _ indicates all those already defined.

c = 0,1,- Radar channel If there is the radar channel, the code rrr must be present too.0 = channel 0 , 1 = canale 1 , - = all the channels.

In the case rrr is an apparatus different from radar channel or a function, c must bepresent but it dont have to be considered.

xxxxx = messages to select. If it is present, the fields rrr and c must be present too.

= RHP is as to select TDA+MET+JAM

= TDA Track data: local tracks and the plots of all the radar channels + the tracks ofthe system.

The fields rrr and c must be but they wont be used for the selection.

= MET the meteo messages.= JAM the jammer strobe messages.= TCO answeres to the telcommands. The fields rrr and c indicate the function

or the addressed apparatus. In the case of function the code c is present but ithas no sense.

= TSI as TCO.

= CDLnn nn = -1, 00, 01, 02,..,07 nn = the diagnostic level. Diagnostic coming fromthe apparatus rrr , channel c . It is valid the note of the PLB SEL RHP


7/29/2019 UM_REC_ES010006101UM03_C.doc

29/61


Issue C

Date: 28/01/2005

This command is a part of the selection OPS orders. It executes by this command the selection ofdata coming from LAN line or internal path (SMD commands, diagnostic).

Controls:

the message SYNTAX ERROR as follws:

1. if rrr is not a valid code of function or radar apparatus for the system;2. if rrr is a code of radar apparatus and c is not a valid code for radar channel;

3. in all the other cases of syntax error.

Result: it modifies the temporary table.


7/29/2019 UM_REC_ES010006101UM03_C.doc

30/61


Issue C

Date: 28/01/2005

SELECTED MESSAGES

REC SEL LAN COMMAND

Parameter selection

xxxx rrr c

Selected

messages

Field of selected

in the message

NOTE

TDA no control BDTMG

MTKMGSLLMG

DES it cannot select by

sender or addressee

MET no control MMSMG DES see note (*)

JAM no control JSSMG DES see note (*)

TSI it control it theapparatus rrr

is present

ACk$TO$FUNCTION

coming fromSMD

DESthreeliteral sender

the selection bythreeliteral is executed

if it is present in thefirst 3 bytes of text part

TCO it control it theapparatus rrris present

ACk$TO$FUNCTIONcoming fromSMD

DESthreeliteral sender

the selection bythreeliteral is executedif it is present in thefirst 3 bytes of text part

CDLnn it control it theapparatus rrris present

DIAGNOSTIC$NOTIFYcoming fromSMD

DESthreeliteral senderand diagnostic level

(*) Without the selection of radar or channel


7/29/2019 UM_REC_ES010006101UM03_C.doc

31/61


Issue C

Date: 28/01/2005

5.1.1.1.7 . REC ASF {FLA, FLB, FLC} n

Where: n = 1,2,3,4 (file physical number);

Description: This command assigns the logical name FLA (to indicate that it is the main unit)or the logical name FLB (to indicate that it is the continuation unit) or the logical name FLC(to indicate that is the reserve unit) to the file which physical number is n. By means thiscommand the file which physical number is n is dedicated to RECording CSCI (andPLayBack CSCI cannot use it).

Controls: If the command has been written correctly, the string ORDER ACCEPTED isdisplayed. Otherwise,the string SYNTAX ERROR is displayed.

Result: If the order is executed, the following string is displayed: FILE ASSIGNED.Otherwise,

1. The string FILE ALREADY ASSIGNED is diplayed, if the file device with physicalnumber n is already assigned to XPL or to XRE;

2. The string FILE ROLE ALREADY ASSIGNED is diplayed, if the logical name(role) is already assigned to XRE;

3. The string FMS ERROR is diplayed, if there is error on opening or on closing and soon

4. The string FILE IN BACKUP is diplayed, if the file n is used by Backup.


7/29/2019 UM_REC_ES010006101UM03_C.doc

32/61


Issue C

Date: 28/01/2005

5.1.1.1.8 . REC DAF FLx

Where: x = A, B, C (A to indicate the main unit; B to indicate the continuation unit; C toindicate the reserve unit);

Description: This command deassigns the file device with the logical name FLx.

Controls:

1. If the command has not been written correctly, the string SYNTAX ERROR isdisplayed.

2. If the file referred to the command DAF is the main unit and the RECording is in pause orthe file referred to the command DAF is not the main unit,the string ORDERACCEPTED is displayed.

3. Otherwise, the string ERROR REC NOT IN PAUSE is displayed.

Result: If the order is executed, the following string is displayed: FILE DEASSIGNED .

Otherwise,

1. The string FILE NOT ASSIGNED TO REC is diplayed, if the file with physical numbern is not assigned to XRE;

2. The string FILE ROLE NOT ASSIGNED TO REC is diplayed, if the logic name (role) isnot assigned to XRE;3. The string FILE LOCKED BY CHANGE COMMAND is diplayed,if there is in

progress the command CHF FLx,where x is the same of the command DAF FLx;4. The string FMS ERROR is diplayed, if there is error on opening or on closing and so

on.


7/29/2019 UM_REC_ES010006101UM03_C.doc

33/61


Issue C

Date: 28/01/2005

5.1.1.1.9 . REC CHF FLx

Where: x = B, C (B to indicate the continuation unit; C to indicate the reserve unit);

Description: This command exchanges the role of the continuation file (logical name FLB) orthe reserve file (logical name FLC) with the current main file.

Controls:

1. If the command has not been written correctly, the string SYNTAX ERROR isdisplayed.

2. If there isnt a file with logical name FLA assigned to XRE, the string COMMANDNOT IN SEQUENCE is displayed.

Otherwise, the string ORDER ACCEPTED is displayed.

Result: If the order is executed, the following string is displayed: FILE CHANGED .Otherwise,

1. If there is already a command CHF in progress, the string FILES SWITCHING IN

PROGRESS is diplayed.2. If the file role referred to the command CHF is not assigned to RECording, the string

REQUESTED FILE NOT ALLOCATED is diplayed.3. The string FMS ERROR is diplayed, if there is error on opening or on closing and so

on.


7/29/2019 UM_REC_ES010006101UM03_C.doc

34/61


Issue C

Date: 28/01/2005

5.1.1.1.10 REC LAN m

where m = A or B ( A is the first LAN configurated , B is the second one )

Description: This command allows to select the preferred LAN (main LAN) on which RECording sends

the messages (at the start the default LAN is A). In any case, if the LAN selected is in fault, the messages

are sent on the other LAN (reserve LAN).

Controls:

1. If RECording is in startup phase, the string COMMAND NOT EXECUTABLE

YET is shown

2. If the command has been written incorrectly, the string SINTAX ERROR in shown

3. If the selected LAN has already the main role, the string LAN ALREADY MAIN

is shown

Otherwise the command can be executed.

Results: If the command can be executed, at the end, the string COMMAND EXECUTED is shown


7/29/2019 UM_REC_ES010006101UM03_C.doc

35/61


Issue C

Date: 28/01/2005

5.1.1.2 Orders sequence

To execute some commands (ASF, DAF, RUN, PAU), the operator has to respect a determinatesequence, otherwise the string COMMAND NOT IN SEQUENCE (or other diagnostic message,see orders description) is displayed to indicate a not correct sequence of commands.Other commands, on the contrary, could be requested in any case.


7/29/2019 UM_REC_ES010006101UM03_C.doc

36/61


Issue C

Date: 28/01/2005

5.1.1.3 Example of Configuration orders

The more significant sequence of orders to execute to obtain a correct Configuration is thefollowing :

REC ASF {FLA,FLB,FLC} n Logical - Phisycal File Unit assigned

If you wants to deassign the FLA or FLB or FLC it must to execute the following order : REC DAF

{FLA,FLB,FLC} Deassigned File Unit

If you wants to know the status of the file units it executes the following order: REC SHO FLDisplaying FL status


7/29/2019 UM_REC_ES010006101UM03_C.doc

37/61


Issue C

Date: 28/01/2005

5.1.2 MASKS

Not applicable

5.1.3 PRINTS

Not applicable


7/29/2019 UM_REC_ES010006101UM03_C.doc

38/61


Issue C

Date: 28/01/2005

5.2 START/STOP RECORDING COMMANDS

To start recording functionality XRE CSCI needs a proper command (RUN command), only afterthis command XRE begins to record radard data and diagnostic messages..

Recording may be interrupted by proper command (PAU command).

5.2.1 ORDERS

There are two orders that allows to start and to stop the recording of data. They are:

REC RUN Run Recording

REC PAU Pause Recording


7/29/2019 UM_REC_ES010006101UM03_C.doc

39/61


Issue C

Date: 28/01/2005


5.2.1.1.1 REC RUN

Description: This command starts (or restarts after the PAU command) the recording of dataon streamer tape and on disk file.

Controls: The command is not accepted:

1. If the main file (FLA) is not assigned to XRE (ASF FLA n command), the stringCOMMAND NOT IN SEQUENCE is displayed.

2. If RECording is already in run. The string RECORDING ALREADY IN RUN is

displayed.

Results: If the order is accepted the string RECORDING IN RUN is displayed and therecording of data on disk file starts.


7/29/2019 UM_REC_ES010006101UM03_C.doc

40/61


Issue C

Date: 28/01/2005

5.2.1.1.2 REC PAU

Description: This command stops the recording of data on streamer tape and on disk file.

Controls: The command is not accepted:

If XRE is not running (RUN command). The string RECORDING ALREADY INPAUSE is displayed.

Results: if the command is accepted the string RECORDING IN PAUSE is displayed and

data recording stops. Data recording can be restarted by means RUN command.


7/29/2019 UM_REC_ES010006101UM03_C.doc

41/61


Issue C

Date: 28/01/2005

5.2.1.2 Orders sequence

To execute some commands (ASF, DAF, RUN, PAU), the operator has to respect a determinatesequence, otherwise the string COMMAND NOT IN SEQUENCE (or other diagnostic message,see orders description) is displayed to indicate a not correct sequence of commands.Other commands, on the contrary, could be requested in any case.


7/29/2019 UM_REC_ES010006101UM03_C.doc

42/61


Issue C

Date: 28/01/2005

5.2.1.3 Examples of Recording orders

The more significant sequence of orders to execute to obtain a correct Recording is the following :

REC ASF {FLA,FLB,FLC} n Assigned phisycal-logical File Unit


If you wants to break the recording it executes the following order :

REC PAU Pause Recording


7/29/2019 UM_REC_ES010006101UM03_C.doc

43/61


Issue C

Date: 28/01/2005

5.2.2 MASKS

Not applicable

5.2.3 PRINTS

Not applicable


7/29/2019 UM_REC_ES010006101UM03_C.doc

44/61


Issue C

Date: 28/01/2005

5.3 INFORMATION PRESENTATION COMMANDS

5.3.1 ORDERS

This set of commands allows to show some informations about the status of the peripherals handledby the RECording CSCI and the setting of the parameters.

These commands are:

REC SHO DIA Displaying diagnostic levelREC SHO REC Displaying Recording statusREC SHO FL Displaying FL statusREC SHO ACT Displaying active table status (optional)

REC SHO DEF Displaying default table status (optional)

REC SHO LAN Displaying LAN status

REC SHO SEL Displaying temporary table status (optional)

REC SHO VR Displaying VR status

REC MON FLn It shows the recorded informations on the File (Identification number of theFile, Initial Date and hour of recording, End Date and hour of recording)


7/29/2019 UM_REC_ES010006101UM03_C.doc

45/61


Issue C

Date: 28/01/2005


5.3.1.1.1 REC SHO LAN

Description: This command shows the LAN status.

Controls: nothing;

Results: The following string is displayed

LAN STATUS : xxx

where:

xxx = ON LAN on (default)= OFF LAN off


7/29/2019 UM_REC_ES010006101UM03_C.doc

46/61


Issue C

Date: 28/01/2005

5.3.1.1.2 REC SHO REC

Description: This command shows the status of Recording CSCI.

Controls: nothing;


REC STATUS : xxx

R1 STATUS : WORK R2 STATUS : OPERATIVE

R4 STATUS : START

where:

xxx = ON The data recording is activated.= OFF The data recording is not activated.

R1, R2, and R4 are internal recording function tasks.

R1 is the Operator interface task.

R2 is the Message Dispatcher task.

R4 is the Disk Writing handler task.

Each of them can assume the following status:

R1: It is always presented in work status (running), since the transitions in other status

are too fast to be presented.

R2: It is always presented in a OPERATIVE status (running), or in PAUSE status if the

recording has been paused by the operator.

R4: It is always presented in OPERATIVE status (running), or in PAUSE status if the

recording has been paused because the main file is completed.

The transitions in other status are too fast to be presented.

Other status are:

CONFIGURATION (during start-up phase)

CHANGE FILE (during the file commutation)

COMMUTATION (during the MST/SLV commutation)


7/29/2019 UM_REC_ES010006101UM03_C.doc

47/61


Issue C

Date: 28/01/2005

5.3.1.1.3 REC SHO DIA

Description: This command shows the maximum level allowed for the diagnostic messagesgenerated by XRE CSCI (see order CDL on SMD Software User Manual).

Controls: nothing;


DIAGNOSTIC LEVEL : nwhere: n = -1,0,1,2,...,7 is the diagnostic level.1 = not diagnostic0 = diagnostic level higher

....

7 = diagnostic level lower


7/29/2019 UM_REC_ES010006101UM03_C.doc

48/61


Issue C

Date: 28/01/2005

5.3.1.1.4 REC SHO SEL (OPTIONAL)

Description : Shows the selection parameters of the temporary table.

Controls: No

Result:

For example it displayes:

TEMPORARY PARAMETERS :

CDLnn MET JAM TDA TSI TCOLANABC - : CDL00BCD M : --- MET JAM --- --- ---

where: ABC,BCD are threeliterals that indicate the sender or addresee code.They can be a function or an apparatus defined at system level.


7/29/2019 UM_REC_ES010006101UM03_C.doc

49/61


Issue C

Date: 28/01/2005

5.3.1.1.5 REC SHO ACT (OPTIONAL)

Description : Shows the selection active parameters, that is, the commands that execute theselection of the data in input during the operative Recording.

Controls: No

Result:


ACTIVE PARAMETERS :

CDLnn MET JAM TDA TSI TCOLANABC - : CDL00BCD M : --- MET JAM --- --- ---

where: ABC,BCD are threeliterals that indicate the sender or addresee code.They can be a function or an apparatus defined at system level.


7/29/2019 UM_REC_ES010006101UM03_C.doc

50/61


Issue C

Date: 28/01/2005

5.3.1.1.6 REC SHO DEF (OPTIONAL)

Description : Shows the default selection parameters.

Controls: No

Result:


DEFAULT PARAMETERS :

CDLnn MET JAM TDA TSI TCOLAN ALL

It supposes to select, as the default parameters, all the data coming from LAN.This selection can be subjected to possible modifications.


7/29/2019 UM_REC_ES010006101UM03_C.doc

51/61


Issue C

Date: 28/01/2005

5.3.1.1.7 REC SHO VR (OPTIONAL)

Description : Shows the status of the Voice Recorders.

Controls: No

Result:

For example it displayes:(the VR can be 4 and the Decks can be 2 for each VR)

VR1 : DECK1 xxx yyyy zzz

VR1 : DECK2 xxx yyyy zzzVR2 : DECK1 xxx yyyy zzzVR2 : DECK2 xxx yyyy zzz

where :xxx = REC tape assigned to the XRE= PLB tape assigned to the APL= --- tape not assigned

yyyy = MAIN main tape(RES reserve tape) (NOT INCLUDED)

zzz = ON tape operating (default)= OFF the link with VR is OFF


7/29/2019 UM_REC_ES010006101UM03_C.doc

52/61


Issue C

Date: 28/01/2005

5.3.1.1.8 REC SHO FL

Description: This command shows the File Units status.

Controls:

It checks the syntax of the command.1. If the command has been written correctly ORDER ACCEPTED is displayed.

2. If the command has not been written correctly SYNTAX ERROR is displayed.

Result: If the order is executed, it is displayed as follows:

If the access to the file is not possible,the following string is displayed: FILE NOT ACCESSIBLE

Otherwise, the following table is displayed:FL1 xxx yyyy xx%FL2 xxx yyyy xx%...

FLn xxx yyyy xx%

where: n = 4 maxxxx = REC file assigned to XRE= PLB file assigned to XPL= --- file not assigned

yyyy = MAIN principal file (for FLA)= RES continuation file (for FLB)= RESR reserve file (for FLC)= --- file not assigned

xx = 0,1,2,...,99 (the percentage of used file for main file only)


7/29/2019 UM_REC_ES010006101UM03_C.doc

53/61


Issue C

Date: 28/01/2005

5.3.1.2 Orders sequenceThe commands to display informations may be executed in any moment, without order of

sequence.

5.3.1.3 Examples of Informations presentation orders

REC SHO REC

REC SHO FL

5.3.2 MASKS

Not applicable

5.3.3 PRINTS

Not applicable


7/29/2019 UM_REC_ES010006101UM03_C.doc

54/61


Issue C

Date: 28/01/2005

6. OPERATIVE EXAMPLES

See examples relative to the different functionalities.

7. ORDERS LIST

1. REC PAU Pause Recording2. REC RUN Run Recording3. REC SEL LAN [NOT] [rrrc] [xxx, xxx,..,xxx] Selection parameters (optional)4. REC MOV ACT PRV Puts the active table into the temporary table (optional)

5. REC MOV ALL PRV Selection of all the data in the temporary table (optional)

6. REC MOV DEF PRV Puts the default table into the temporary table (optional)

7. REC MOV NIL PRV Clears out the temporary table (optional)

8. REC MOV ACT PRV Puts the temporary table into the active table (optional)

9. REC SHO DIA Displaying Diagnostic state10. REC SHO REC Displaying Recording status

11. REC SHO ACT Displaying active table status (optional)

12. REC SHO DEF Displaying default table status (optional)

13.REC SHO LAN Displaying LAN status

14. REC SHO SEL Displaying temporary table status (optional)

15.REC SHO VR Displaying VR status

16. REC ASF {FLA,FLB,FLC} n Logical-phisycal File Unit assignment

17. REC DAF {FLA,FLB,FLC} File Unit deassignment18. REC CHF {FLB,FLC} File Unit changement19. REC SHO FL Displaying FL status

20. REC MON FLn Showing recorded information on the File (Identification number of the File,Initial Date and hour of recording, End Date and hour of recording)


7/29/2019 UM_REC_ES010006101UM03_C.doc

55/61


Issue C

Date: 28/01/2005

8. ERRORS AND ALARMS MESSAGE

8.1 GENERALITY

The messages introduction, errors, alarms, are shown by the messages on I/O console and on spoolerif it is configured.

8.2 MESSAGES

The following messages are displayed on I/O console:

CHANNEL ALREADY SELECTED: channel is already selected, therefore the selectioncommand it must be referenced to another already existent;

COMMAND ABORTED: the command is refused by the operator.

COMMAND ERROR: logical error in the command. The error regards the compilation rules. COMMAND NOT IN SEQUENCE: the command do not respect the sequence of the

commmands (see paragraphs Commands Sequence). ERROR IN EXECUTION: the operation is finished with error. To control the peripherals

status, their assignation or the possible others diagnostic messages to send. RECORDING IN PAUSE: positive result of the PAU command.

RECORDING IN RUN: positive result of the RUN command.

RECORDING ALREADY IN PAUSE: negative result of the PAU command because XRE isalready in pause.

RECORDING ALREADY IN RUN: negative result of the RUN command because XRE isalready in run.

FILE ASSIGNED: positive result of the ASF command. FILE NAME ALREADY ASSIGNED: negative result of the ASF command, because the

device is already assigned to the XRE CSCI or the APL CSCI. FILE ROLE ALREADY ASSIGNED: negative result of the ASF command, because the role

of the file is already assigned. ERROR REC NOT IN PAUSE: negative result of the DAF command, because the RECording

was not in pause. FILE DEASSIGNED: positive result of the DAF command. FILE NAME NOT ASSIGNED TO REC: negative result of the DAF command, because the

file had not been assigned to RECording. FILE ROLE NOT ASSIGNED TO REC: negative result of the DAF command, because the

role had not been assigned to RECording. FILE LOCKED BY CHANGE COMMAND: negative result of the DAF command, because

there was a CHF command in progress. FILE IN BACKUP: negative result of the ASF command, because there was a backup in

progress. FILE CHANGED: positive result of the CHF command.


7/29/2019 UM_REC_ES010006101UM03_C.doc

56/61


Issue C

Date: 28/01/2005

FILES SWITCHING IN PROGRESS: negative result of the CHF command, because therewas a CHF command in progress.

REQUESTED FILE NOT ALLOCATED: negative result of the CHF command, becausethe file was assigned to XRE CSCI.

NO DATA: negative result of the SHO DAT command, because the RECording was not inrun.

EMPTY FILE : NO DATA: negative result of the MON FLn command, because the file is notassigned or the file is assigned but there is no data EMPTY FILE : NO DATA is displayed.

ORDER ACCEPTED: no syntax error in the command. The command had been writtencorrectly. SYNTAX ERROR: syntax error in the command. The command must be written correctly.


7/29/2019 UM_REC_ES010006101UM03_C.doc

57/61


Issue C

Date: 28/01/2005

8.3 ERRORS

The errors messages sent out by XRE have the following format :

REC CODE:RmPRSWppRESxxxxH ASCII STRING that contains the errors explanation.el.

Where:

m= module index where the error is occurred; pp= procedure index internal to the module in which the error is occurred,represented decimal format; xxxx= hexadecimal code of the MARA error represented in hexadecimal format;

Module codes are:

1 : R1 process 2 : R2 process 4 : R4 process

The procedure codes are defined in the high level documents..

When in a procedure an anomalous situation occurs not dependent from MARA error directly, theinternal error is setted. The possible explanation string of internal error codes for the RecordingCSCI, are:

CONVERSION ERROR CREATE PATH ERROR BUFFER BOUNCED FATAL ERROR GET WORK AREA ERROR PATH DETACHED RELEASE WORK AREA ERROR REPLY WITH NOK RESULTCODE INVALID PU INDEX INVALID MESSAGE RECEIVED UNKNOWN MESSAGE RECEIVED

The following internal errors are specified in according to the module in which it occurred.

R1 (1) PROCESS:

INVALID POINTER


7/29/2019 UM_REC_ES010006101UM03_C.doc

58/61


Issue C

Date: 28/01/2005

R2 (2) PROCESS:

BUFFER NOT RELEASED UNEXPECTED MESSAGE FROM RCD INVALID LAN STATUS CREATE BUFFER ERROR ATTACH PATH ERROR ERROR ON VOICE RECORDER OPERATION WRONG SELECTION LAN NUMBER FROM RCD INCONGRUENT RCD MEX WITH REC STATUS

R4 (1) PROCESS:

BUFFER WITH STATUS NOK INCONGRUENT MSG WITH R4 STATUS DISK DEASSIGNED INVALID COMMAND RECEIVED INVALID MESSAGE RECEIVED) RESTART R4 FILE FULL : DATA BASE NOT RECEIVED FILE MAIN FATAL ERROR FILE MAIN ERROR)

RECOVERY ON FILE RES/RES CREATE FILE ERROR

The external error is the result of a Mara error. (See the Mara manual).

STOP of the Recording

The stopping event for XRE are:

impossibility to open a path with RCD;

impossibility to open a path with the LAN;

If one of these path was not opened correctly the XRE CSCI in a undetermined status is stopped. Torestart CSCI XRE is necessary to restart the node.

Diagnostic messages are provided.

8.4 ALARMS

An acustic alarm message is generated by the CSCI in the following events:


7/29/2019 UM_REC_ES010006101UM03_C.doc

59/61


Issue C

Date: 28/01/2005

error on voice recorder operation fault on main Lan

fault on tape or hard disk


7/29/2019 UM_REC_ES010006101UM03_C.doc

60/61


Issue C

Date: 28/01/2005

9. DEGRADED EXECUTION

The XRE CSCI must handle the following failure conditions:

Peripherals failure (Disk Unit);

Peripherals Failure

The Failure of PUs handled by XRE, is managed according to the informations that the function has.

.

I/O console:

Even if the application task takes information about failure on I/O console, it continues to workwithout testing.

Node Supervisor will have to send a stopping comunication to the application tasks that use it.

Dual Port (Lan) Peripherical Commutation

The application task will be able to notify to NS some particular conditions regarding to peripheralunits known by it.NS can decide what to and can ask to the application task to carry out it.


7/29/2019 UM_REC_ES010006101UM03_C.doc

61/61


Issue C

Date: 28/01/2005

10. OPERATIVE STARTING

When system is loaded for the operative starting the following operations are executed:

REC ASF {FLA,FLB,FLC} n Logical - Phisycal File Unit assignment
