UM_XSD_ES010006101UM11_B

UNCLASSIFIED Doc N. ES010006101UM11

Iss. B

PROGRAM:

Romania Upgrade - Phase 1

USER MANUAL

For

System Message Dispatcher

(XSD)

Program No.:

Contract Identification Code : E401

ISSUED BY :

SELEX Sistemi IntegratiVia Tiburtina km 12,4 - Roma

ITALY

The copyright in this document is the property of SELEX Sistemi

Integrati S.p.A. The document is supplied on the express

understanding that it is to be treated as confidential and that it may

not be copied, used or disclosed to others in whole or in part for any

purpose except as authorised in writing by SELEX Sistemi Integrati

S.p.A.

UNCLASSIFIED Page 1


Iss. B

The total number of pages, included the eventual Appendixes and Annexes, is 77 pages.

UNCLASSIFIED Page 2


Iss. B

SECURITY CLASSIFICATION

The following are the military classification levels for the documents from lowest to highest.

NON CLASSIFICATO CONTROLLATO UNCLASSIFIED NC

RISERVATO RESTRICTED R

RISERVATISSIMO CONFIDENTIAL RR

SEGRETO SECRET S

SEGRETISSIMO TOP SECRET SS

Editing, issue, custody, reproduction, diffusion and disposal of Classified documents must be done in conformity to the Internal Security Rules (“Regolamento Interno di Sicurezza”).

UNCLASSIFIED Page 3


Iss. B

Issue Authority

Approved by:(Project Leader) ......................................................

(Valter Ciaraffo)Date: 14/11/2008

Approved by:(Program Manager) ......................................................

(Sergio Arceri)Date: 14/11/2008

UNCLASSIFIED Page 4


Iss. B

REVISIONS RECORD SHEET

This sheet is a record of revisions to this document.

Issue Date Revised ParagraphsDocument

Change Note

Rev. A 20/05/05 First IssueRev. B 12/11/08 Revised all pages; added Annex B, C and D

UNCLASSIFIED Page 5


Iss. B

ABBREVIATIONS LIST

CODE 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

DCL Departure CLearance

DCR Departure Clearance with Re-routing

UNCLASSIFIED Page 6


Iss. B

CODE DESCRIPTION

DEP 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 list

FPLM 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

LND LANding report

LRW Landing RunWay

LSV LaSt leVel

LVA planned/cleared LeVel Assignment

MET METeorological

MIL MILitary

UNCLASSIFIED Page 7


Iss. B

CODE DESCRIPTION

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

REC RECording

REG REGistration number

REP Position REport

REV estimate REVision

RFB Radar Fall Back

RHP Radar Head Processor

RNG RaNGe scale

RWY RunWaY

SBY Stand-BY

SID Standard Instrumental Departure

UNCLASSIFIED Page 8


Iss. B

CODE DESCRIPTION

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 9


Iss. B

TABLE OF CONTENTS

1. SCOPE.................................................................................................................................12

1.1 IDENTIFICATION...............................................................................................................121.2 SYSTEM OVERVIEW.........................................................................................................121.3 DOCUMENT OVERVIEW...................................................................................................13

2. REFERENCED DOCUMENTS.............................................................................................14

3. CONVENTIONS....................................................................................................................15

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

4.1 INTERFACES TOWARD SYSTEM COMPONENTS.........................................................174.2 INTERFACES TOWARD THE OPERATOR......................................................................17

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

5.1 SETTING OF PRIVILEGES................................................................................................195.1.1 VIDEO PRESENTATIONS..............................................................................................215.1.2 ORDERS..........................................................................................................................225.1.2.1 ORDERS DESCRIPTION....................................................................................................225.1.2.1.1 SPW - Set Node Password........................................................................................225.1.2.1.2 CPW - Change Node Password................................................................................235.1.2.1.3 RPW - Reset Node Password....................................................................................245.1.2.1.4 DBR - Disable Privileges of Own Node......................................................................255.1.3 VIDEO PRESENTATIONS..............................................................................................265.1.4 ORDERS..........................................................................................................................275.1.4.1 ORDERS DESCRIPTION....................................................................................................275.1.4.1.1 MST - Set Node Role to Master.................................................................................275.1.4.1.2 SLV - Set Node Role to Slave....................................................................................285.2 SETTING OF SYSTEM TIME.............................................................................................295.2.1 VIDEO PRESENTATIONS..............................................................................................295.2.2 ORDERS..........................................................................................................................305.2.2.1 ORDERS DESCRIPTION....................................................................................................305.2.2.1.1 STT - Set System Time..............................................................................................305.2.2.2 ORDERS SEQUENCES......................................................................................................315.2.2.3 ORDER EXAMPLES ABOUT SETTING OF SYSTEM TIME.......................................................315.2.3 MASKS............................................................................................................................315.2.4 PRINTING........................................................................................................................315.2.5 EXAMPLES ABOUT SETTING OF SYSTEM TIME........................................................315.3 FILTERING AND DISPATCHING OF DIAGNOSTIC MESSAGES...................................325.3.1 VIDEO PRESENTATIONS..............................................................................................325.3.2 ORDERS..........................................................................................................................335.3.2.1 ORDERS DESCRIPTION....................................................................................................335.3.2.1.1 CDL - Change Node(s) Diagnostic Level...................................................................33

UNCLASSIFIED Page 10


Iss. B

5.3.2.1.2 DL0 - Request Node(s) Diagnostic Level 0...............................................................355.3.2.1.3 UDL - Change CSCI(s) Diagnostic Level...................................................................365.3.2.1.4 SUL - Show CSCI(s) Diagnostic Level.......................................................................375.3.2.1.5 DLD - Change Diagnostic Dissemination of RDS Node(s)........................................385.3.2.1.6 SDL - Show Diagnostic Dissemination of RDS Nodes..............................................395.3.2.2 ORDERS SEQUENCES......................................................................................................405.3.2.3 ORDER EXAMPLES ABOUT FILTERING AND DISPATCHING OF DIAGNOSTIC MESSAGES........405.3.3 MASKS............................................................................................................................415.3.4 PRINTING........................................................................................................................415.3.5 EXAMPLES ABOUT FILTERING AND DISPATCHING OF DIAGNOSTIC MESSAGES415.4 PRESENTATION OF NODE INFORMATION....................................................................425.4.1 VIDEO PRESENTATIONS..............................................................................................425.4.2 ORDERS..........................................................................................................................435.4.2.1 ORDERS DESCRIPTION....................................................................................................435.4.2.1.1 SNI - Immediately Show Node Status........................................................................435.4.2.1.2 SNR - Repeatedly Show Nodes Status.....................................................................465.4.2.1.3 VER - Show CSCI(s) Version....................................................................................475.4.2.1.4 IEP - Enable SMD Self-Diagnosis..............................................................................495.4.2.2 ORDERS SEQUENCES......................................................................................................505.4.2.3 ORDER EXAMPLES ABOUT PRESENTATION OF NODE INFORMATION...................................505.4.3 MASKS............................................................................................................................505.4.4 PRINTING........................................................................................................................505.4.5 EXAMPLES ABOUT PRESENTATION OF NODE INFORMATION...............................50

6. OPERATIVE EXAMPLES....................................................................................................51

7. ORDERS LIST......................................................................................................................52

8. GENERAL MESSAGES, ERRORS AND ALARMS............................................................53

8.1 INTRODUCTION................................................................................................................538.2 DIAGNOSTIC MESSAGES................................................................................................558.3 ERROR MESSAGES..........................................................................................................598.3.1 EXCEPTIONS..................................................................................................................598.3.2 SMD SOFTWARE ERRORS...........................................................................................618.3.3 OTHER SOFTWARE ERRORS.......................................................................................668.3.4 OPERATOR’S ERRORS.................................................................................................678.3.5 ALARM MESSAGES.......................................................................................................69

9. DEGRADED WORKING.......................................................................................................70

10. START-UP OPERATIVE PROCEDURE............................................................................70

11. APPENDIXES.....................................................................................................................71

11.1 APPENDIX A: DESCRIPTION OF SMD STATUS MESSAGE........................................7111.2 APPENDIX B: BUCHAREST SMD NODES LIST............................................................7411.3 APPENDIX C: ARAD SMD NODES LIST........................................................................75



Iss. B

11.4 APPENDIX C: CONSTANTA SMD NODES LIST.............................................................76



Iss. B

1. SCOPE

1.1 IDENTIFICATION

Within the ALENIA (former SELENIA) Air Traffic Control Automatic System (SATCAS), the identifier of the Advanced System Messages Dispatcher (ASD) Computer Software Configuration Item (CSCI) is:

E000ASD0

In this Software User Manual (SUM) the ASD CSCI will be shortly referred as System Messages Dispatcher (SMD).

1.2 SYSTEM OVERVIEW

Within the SATCAS, monitor and control messages (i.e. BITE messages) are dispatched by SMD CSCI:

locally, i.e. among (up to 256) nodes belonging to the same Radar (RDS) or Operative (OPS) site

remotely, i.e. between one or more (up to 8) RDSs and one or more (up to 8) OPSs

The nodes inside each OPS and RDS site are interconnected through Local Area Network (LAN), usually redundant; SMD CSCI supports LAN communication through standard UDP protocol or the ALENIA-proprietary Fast Data Transmission System (FDTS) protocol.

The remote RDS OPS communication is provided by serial line, usually redundant; SMD CSCI supports serial line communication through standard High-level Data Link Control (HDLC) protocol (LAP-B or Datagram) or its ALENIA-modified version (MOD-M).

When using standard HDLC protocol, SMD can use ASTERIX Category 253 for messages formatting.

Inside the SATCAS, SMD is a server CSCI whose capabilities accessible to the operator are:

1) Setting of Privileges

2) Setting of Node Role and Operative Mode

3) Setting of System Time

4) Filtering and Dispatching of Diagnostic Messages

5) Presentation of Node Information



Iss. B

1.3 DOCUMENT OVERVIEW

This document describes the operative procedures to use the SMD CSCI; it contains the following chapters:

1) Scope:it identifies the purpose and the contents of this document

2) Referenced documents:it contains the list of referenced documents

3) Conventions:it contains the alphabetical listing of all acronyms and abbreviations used in this document; the conventional orders syntax representation is described too

4) Interfaces description:it contains the list and the characteristic of interfaces toward the operator

5) Functionality:it contains the video presentation, operative orders and video masks for input information, in a detailed format

6) Operative examples:it contains some useful operative examples to use SMD CSCI

7) Orders list:it contains the alphabetical list of all SMD orders

8) General messages, error and alarms:it contains the detailed list of all messages issued by SMD CSCI to the operator, to signal error situations, alarms, and so on

9) Degraded working:it describes the possible cases of SMD degraded situations, due to external faults

10) Start-up operative procedure:it contains the procedure to start-up the SMD CSCI

11) Appendixes:they provide supplementary information



Iss. B

2. REFERENCED DOCUMENTS

The documents referred in this Software User Manual are:

[1]- AUTHOR : ALENIA S.p.A.

- DOCUMENT ID. : E000ASD0-01IRS

- TITLE : INTERFACE REQUIREMENTS SPECIFICATION for the ADVANCED SYSTEM MESSAGE DISPATCHER of SATCAS 80-M

[2]

- AUTHOR : ALENIA S.p.A.

- DOCUMENT ID. : E000ASD0-01IDD

- TITLE : INTERFACE DESIGN DOCUMENT for the ADVANCED SYSTEM MESSAGE DISPATCHER of SATCAS 80-M



Iss. B

3. CONVENTIONS

Acronyms and Abbreviations:

ASD Advanced System Message Dispatcher CSCIASTERIX All purpose STructured Eurocontrol Radar Information eXchange data formatBITE Built-In Test EquipmentCSCI Computer Software Configuration ItemCDL SMD order "Change Node(s) Diagnostic Level"CPW SMD order "Change Node Password"DBR SMD order "Disable Privileges of Own Node"DLD SMD order "Change Diagnostic Dissemination of RDS Node(s)"DL0 SMD order "Request Node(s) Diagnostic Level 0"FDTS Fast Data Transmission System protocolHDLC High-level Data Link Control protocolHWCI HardWare Configuration ItemIDD Interface Design Document IEP SMD order "Enable SMD Self-Diagnosis"IRS Interface Requirements Specification documentLAN Local Area Network HWCIMST SMD order "Set Node Role to Master"NSV Node SuperVisor CSCIOPM Operational ModeOPS OPerative SiteRDS RaDar SiteRPW SMD order "Reset Node Password"SATCAS ALENIA (former SELENIA) Air Traffic Control Automatic SystemSDL SMD order "Show Diagnostic Dissemination of RDS Nodes"SLV SMD order "Set Node Role to Slave"SMD System Message Dispatcher CSCISMR System Message Router CSCISNI SMD order "Immediately Show Node Status"SNR SMD order "Repeatedly Show Nodes Status"SPW SMD order "Set Node Password"SRS Software Requirements Specification documentSTT SMD order "Set System Time"SUL SMD order "Show CSCI(s) Diagnostic Level"SUM Software User Manual documentUDL SMD order "Change CSCI(s) Diagnostic Level"UDP User Datagram ProtocolVER SMD order "Show CSCI(s) Version"VT Video Terminal HWCI



Iss. B

Orders syntax conventions:

The syntax of each order is described using the following rules:

- The three-literal of the order and the values of the parameters are written in uppercase characters.

- The fields of the order are written in lowercase italic characters; the only exception is represented by the month identifier in the date string, which is actually written in uppercase characters (e.g. “dd/MM/yy”) to highlight its difference with respect to the minutes in the time-of-day string (e.g. “hh:mm:ss”).

- Square brackets "[ ]" mark an optional field.

- Round brackets "( )" mark a list of alternative values, separated by slashes "|".

- A sequence of a given number of identical characters is a fixed length identifier. (e.g. "yyyy" is used for a four-literal year identifier).

- A sequence of parameters of the same type is identified by the first and the last field separated by two points (e.g. num1..num3); the number of allowed parameters is shown by the digit associated to the last field.

Message syntax conventions:

The syntax of each message to the operator is described using the following rules:

- Each whole message string, with all its fields, is included in quotation marks " ".

- Italic marks variable fields.

- Square brackets "[ ]" mark fields which are optional in the message.

- Round brackets "( )" mark a list of alternative values, separated by slashes "|".

- "min-value..max-value" notation marks a variability range.

Other conventions:

- The expression "own node" means: the node the order is input from.

- The expression "own site" means: the site own node belongs to.

- A system node is called “visible” by the other nodes according to the following rules:

a node in RDS is visible by all nodes belonging to own site and by all nodes belonging to all connected Operative sites

a node in OPS is visible by all nodes belonging to own site

- A system site is called “visible” by the other nodes according to the following rules:

a radar site is visible by all nodes belonging to own site and by all nodes belonging to all connected Operative sites

an operative site is visible by all nodes belonging to own site



Iss. B

4. INTERFACES DESCRIPTION

4.1 INTERFACES TOWARD SYSTEM COMPONENTS

SMD CSCI interfaces with the following system components (refer to [1] and [2]):

CSCIs (including NSV) allocated on own node, through Path Manager service

external clock, through local serial interface

SMD CSCIs allocated on own site, through Local Area Network

SMD CSCIs allocated on another (remote) site, through remote serial interface

4.2 INTERFACES TOWARD THE OPERATOR

SMD CSCI has not direct interfaces toward the operator, but it uses the following man-machine interfaces to exchange data with him:

I/O Console interface

Interface description:

SMD CSCI has an indirect interface toward the I/O Console of own node (if any), used to input the operator’s orders and to output alphanumeric strings and presentations. The I/O Console is handled by NSV CSCI, which passes to SMD CSCI all operator’s orders which are not directly handled by itself.

Interface type:

This interface is made by a VT100-like alphanumeric video and by a standard keyboard.

Terminal input characteristics:

Each operator input is made by a characters string, always ending with a Carriage Return.

Graphic WorkStation interface

Interface description:

The indirect graphic workstation interface is handled by CMS, which performs a graphical and friendly man-machine interface, supporting SMD CSCI in the following tasks:

- alphanumeric presentation of diagnostic messages (including diagnostics, acknowledges, alarms, notifies)

- graphical presentation of the BITE Status of all the nodes of the system; through BITE Status messages, SMD CSCI notifies all changes in the system status, which is represented by CMS using graphical attributes of elements (colours, strings, shapes) on synoptic drawings

- helped input of operator’s orders

Interface type:

The graphic workstation interface is usually made by a colour graphic video, a keyboard and a buzzer.

Terminal input characteristics:

SMD CSCI uses the friendly facilities supported by CMS to input operator’s orders.

Acoustic interface:



Iss. B

SMD CSCI uses the buzzer interface supported by CMS to signal the presence of system alarms.



Iss. B

5. FUNCTIONALITY

5.1 SETTING OF PRIVILEGES

System Orders Syntax

System orders can be originated by:

a system operator, using a Graphic WorkStation

a maintenance operator, using an I/O console

a nodal CSCI, without operator’s intervention

The orders syntax accepted by SMD CSCI is:

[ site | node <blank> ] [ class <blank> ] order [ <blank> params ]

where:

site | node optional identifier of the addressed site or node; the allowed values are:sss three-literal of a visible system site (“site-addressing”)nnn three-literal of a visible system node (“node-addressing”)omitted (“no-addressing”)

class optional identifier of the addressed class of orders; the allowed values are: ccc three-literal identifier of a defined class of orders omitted the default class (3 blanks) is associated by SMD

order compulsory three-literal identifier of the order

params optional order parameter(s), usually separated by blanks

System Orders Dispatching

The way SMD dispatches each order inside the system depends on:

the way the order is addressed when produced

the way the order has been declared by the addressed CSCI (in its Order_List, refer to [2])

An order with node-addressing is dispatched only toward the addressed node (in own or other site); if on that node there are CSCIs which have declared the given order as internal, then the order is forwarded to them, otherwise the order will be declared lost by SMD.

An order with site-addressing is dispatched toward all nodes belonging to the addressed (own or other) site; if on these nodes there are CSCIs which have declared the given order as external, then the order is forwarded to them, otherwise the order will be declared lost by SMD.

When an order with no-addressing is input, firstly SMD searches whether there are CSCIs on the own node which have declared the given order as internal:

if there are such CSCIs, then the order is forwarded to them



Iss. B

otherwise the order is dispatched toward all nodes belonging to own site; if on these nodes there are CSCIs which have declared the given order as external, then the order is forwarded to them, otherwise the order will be declared lost by SMD



Iss. B

Checks on Orders

Apart some customisable exceptions, each system order must go through the following checks, before being forwarded by SMD(s) to the CSCI that will execute it:

password check

Password Check

In order to be able to send orders, the operator must request SMD to:

open a job session, entering the correct password of own node

at the end of the job session, he can request SMD to

close the job session, disabling the access privileges

The operator can request SMD to:

change / reset the password of any other node in the system; this will automatically close all open sessions (if any) on the addressed node.

It is possible to off-line customise a list of orders that can be input independently of the password setting; through Graphical WorkStation the operator can request SMD to:

change this list at run-time, defining orders to be / not to be checked by password

It is also possible to off-line customise a list of CSCIs which are enabled by default to generate orders, without opening a job session.

By default, orders can be exchanged between all CSCIs running on the same node (but NSV CSCI) without opening a job session.

5.1.1 VIDEO PRESENTATIONS

Please refer to § 5.1.2.1



Iss. B

5.1.2 ORDERS

This paragraph describes all orders executed by SMD CSCI relevant to the functionality “Setting of Privileges”.

5.1.2.1 Orders description

5.1.2.1.1 SPW - Set Node Password

Purpose:

This order allows the operator to open a job session on own node, typing the node password.

Syntax:

SPW [ <blank> password ]

where:

password current password of own node: it is an alphanumeric string long from 3 to 14 characters; it has no echo

The I/O Console operator can omit on own node the parameter password; in this case NSV CSCI will display on the I/O Console the string "PASSWORD : ", to prompt the operator to type the current password of own node.

Effect:

SMD on own node replies the following acknowledge:

"hh:mm:ss nnn SPW : ORDER ACCEPTED"

where nnn is the three-literal identifier of own node, and then:

the job session is opened, therefore the operator can input system orders from own node

Constrains:

The order is not executed by SMD if:

password is not the current password of own node



Iss. B

5.1.2.1.2 CPW - Change Node Password

Purpose:

This order allows the operator to change the current password of a visible node.

Syntax:

[ nnn <blank> ] CPW [ <blank> old_psw <blank> new_psw <blank> new_psw ]

where:

nnn optional three-literal identifier of the node whose password has to be changed (own node, if omitted)

old_psw current password of the addressed node; it is an alphanumeric string long from 3 to 14 characters: it has no echo

new_pswnew password for the addressed node; it is an alphanumeric string long from 3 to 14 characters; it has no echo and must be repeated twice for confirmation

The I/O Console operator can omit on own node the parameters old_psw and new_psw; in this case NSV CSCI will display:

once the string "OLD PASSWORD : ", to prompt the operator to type the current password of the addressed node

twice the string "NEW PASSWORD : ", to prompt the operator to enter and confirm the new password for the addressed node

Effect:

SMD on the addressed node replies the following acknowledge:

"hh:mm:ss nnn CPW : ORDER ACCEPTED"

and then:

the current password of node nnn becomes equal to the string new_psw

all open job sessions on node nnn are closed (unless enabled by default)

Constrains:


nnn is the identifier of a node not visible by own node

old_psw is not the current password of node nnn

the second instance of the string new_psw is not equal to the first one



Iss. B

5.1.2.1.3 RPW - Reset Node Password

Purpose:

This order allows the operator to close all job sessions on a visible node, disabling all system access authorisations.

Syntax:

[ nnn <blank> ] RPW

where:

nnn optional three-literal identifier of the node whose password must be reset

Effect:


"hh:mm:ss nnn RPW : ORDER ACCEPTED"

and then:

all system access authorisations on node nnn are disabled

After the execution of this order, every operator who wants to input system orders from node nnn has to set again the password of that node.

Constrains:



It is possible to customise a list of CSCIs which are enabled by default to send orders; in this case, RPW order doesn’t disable their authorisation.



Iss. B

5.1.2.1.4 DBR - Disable Privileges of Own Node

Purpose:

This order allows the operator to close his job session on own node, disabling his previous system access authorisation.

Syntax:

DBR

Effect:


"hh:mm:ss nnn DBR : ORDER ACCEPTED"


the system access authorisation on own node is reset

After the execution of this order, every operator who wants to input system orders from the node has to set again its password.

Constrains:

None.Setting of Node Role and Operative ModeThe status of each system node is defined by two attributes: its Role and its Operative Mode.

Node Role

The possible values for the Role of a node are:

SINGLE when a node is not in redundant configuration

MASTER when a node belongs to a matched pair of nodes, currently it is Master, and the partner node is available (in Slave role)

MASTER ALONE when a node belongs to a matched pair of nodes, currently it is Master and the partner node is not available

SLAVE when a node belongs to a matched pair of nodes and currently it is Slave;

SMD on whatever Slave node is not allowed to perform the following operations:

take of lock RDS

reception of time information from the external clock (except for North data)

dissemination of message from RDS to OPS(except for the messages which are produced by the Slave node itself).


change Master Slave the Role of a matched pair of nodes



Iss. B


None.



Iss. B

5.1.4 ORDERS

This paragraph describes all orders executed by SMD CSCI relevant to the functionality “Setting of Node Role and Operative Mode”.


5.1.4.1.1 MST - Set Node Role to Master

Purpose:

This order allows the operator to exchange the roles in a matched pair of nodes:

the node addressed by the order becomes Master

the partner node becomes Slave (Stand-By)

Syntax:

[ nnn <blank> ] MST

where:

nnn optional three-literal identifier of the node to become Master (own node, if omitted)

Effect:


"hh:mm:ss nnn MST : BEGIN SWITCH STANDBY -> MASTER"

and sends the order to the NSV CSCI, which is the real performer of MST order.

Therefore the operator has to wait for NSV messages, to check the complete execution of this order.

Constrains:



the addressed node has not Slave role

the addressed node is in Maintenance (Enable or Locked) mode, while the partner (Master) node is in Operational mode



Iss. B

5.1.4.1.2 SLV - Set Node Role to Slave

Purpose:

This order allows the operator to exchange the roles in a matched pair of nodes:

the node addressed by the order becomes Slave (Stand-By)

the partner node becomes Master

Syntax:

[ nnn <blank> ] SLV

where:

nnn optional three-literal identifier of the node to become Slave (own node, if omitted)

Effect:


"hh:mm:ss nnn SLV : BEGIN SWITCH MASTER -> STANDBY"

and sends the order to the NSV CSCI, which is the real performer of SLV order.

Therefore the operator has to wait for NSV messages, to check the complete execution of this order.

Constrains:



the addressed node has not Master role

the addressed node is in Operational mode, while the partner node is in Maintenance (Enable or Locked) mode



Iss. B

5.2 SETTING OF SYSTEM TIME

SMD is the system time authority; it can receive time information from an external clock, usually redundant, or from the operator; when redundant, one of the clock is considered main, the other one reserve.


set the system time (only if no clock is available and synchronised by the external radio antenna)

External Clock

An external clock can be in one of the following operative status:

synchronised (main, available, synchronised)

not synchronised (main, available)

logical off (main, available, no input)

fault (main or reserve, not available)

reserve (reserve, available)

not diagnosable (main or reserve, start-up phase)

The status of an external clock changes after:

node start-up

“logical OFF” status, i.e. no reception or wrong reception of time information from the clock

fault of the peripheral board the clock is connected to

reception of first synchronised time information from the clock

reception of first not synchronised time information from the clock

Time Information

SMD updates the system time on all nodes in the following cases:

the last time read on the external clock differs from the system time more than a customisable threshold; SMD will align asynchronously all connected nodes (sending its BITE Status message)

the time is set by the operator; SMD will align immediately all connected nodes (sending a designed message)


None.



Iss. B

5.2.2 ORDERS

This paragraph describes all orders executed by SMD CSCI relevant to the functionality “Setting of System Time”.


5.2.2.1.1 STT - Set System Time

Purpose:

This order allows the operator to set the system time and, optionally, the system date.

Syntax:

STT <blank> hh del mm del ss [ <blank> MM del dd del yy ]

where:

hh are two digits for the hours

mm are two digits for the minutes

ss are two digits for the seconds

dd are two digits for the day

MM are two digits for the month

yy are the last two figures of the year

del is one of the following delimiter characters: / - : ; ,

Effect:


"hh:mm:ss nnn STT hh del mm del ss [ MM del dd del yy] : ORDER ACCEPTED"


set the system time (and date, if necessary) on all connected nodes

Constrains:


in a node of the system there is a synchronised clock

the date has never been set before in the system, and the STT order doesn’t provide it

a (customisable) amount of time is not elapsed since previous STT order

the current time and/or the time set by the operator is around midnight



Iss. B

5.2.2.2 Orders sequences

No specific orders sequence applies to this functionality.

5.2.2.3 Order examples about Setting of System Time

STT 12:25:33 05:23:96 the operator set the system time and date

STT 09:14:00 the operator set only the system time

5.2.3 MASKS

Not applicable.

5.2.4 PRINTING

The SMD messages scrolling on I/O console can be printed in hard-copy.

5.2.5 EXAMPLES ABOUT SETTING OF SYSTEM TIME

The operator is allowed to set the system time only when no clock is available and synchronised by the external radio antenna.



Iss. B

5.3 FILTERING AND DISPATCHING OF DIAGNOSTIC MESSAGES

Diagnostic Messages

Diagnostic messages are ASCII strings produced by the CSCIs (including SMD itself) to notify a meaningful event (e.g. an anomaly) to the operator.

In order to allow diagnostics selection, the producer CSCI must associate to each diagnostic message a severity level in the range [0 , 7]; while the level 0 is usually used for non-operational diagnostics (e.g. notifications for internal testing of CSCIs), the levels from 1 to 7 are hierarchical (1 = heaviest severity).

SMD receives the diagnostic messages from the producer CSCIs running on own node and dispatch them, through other SMDs, to all diagnostic users CSCIs running on whatever visible node.


select the diagnostic levels to display, in order to filter out all undesired messages

select the highest diagnostic level to be produced by one / all CSCI(s) on a node

show the highest diagnostic level to be produced by each CSCI of a node

select the highest diagnostic level to be sent from an RDS node towards an OPS

show the highest diagnostic level sent from all nodes of an RDS towards a connected OPS

Alarm Messages

Each producer CSCIs can associate to a diagnostic message the acoustic attribute, to signal through buzzer activation the occurrence of an alarm in the system.


Please refer to § 5.4.2.1.4 and § 5.4.2.1.6 .



Iss. B

5.3.2 ORDERS

This paragraph describes all orders executed by SMD CSCI relevant to the functionality “Filtering and Dispatching of Diagnostic Messages”.


5.3.2.1.1 CDL - Change Node(s) Diagnostic Level

Purpose:

This order allows the operator to define up to which level the diagnostic messages produced by one / all visible node(s) have to be displayed on own node.

The CDL order provides a diagnostic filtering on presentation, not on production; it acts on the diagnostic messages having level between 1 and 7.

Syntax:

CDL <blank> lev [ <blank> nnn ]

where:

lev highest level of diagnostic messages the operator wants to display on own node from the addressed node(s); its allowed values are:

1.. 7 if diagnostic messages up to the given level 1..7 have to be displayed

“I” if no diagnostic messages and broadcast notifies have to be displayed at all

nnn optional three-literal identifier of the addressed node(s) (own node, if omitted); its allowed values are:

“ALL” if the order applies to all visible nodes

“LOC” if the order applies to all nodes of own site

“nnn” if the order applies to the node nnn

Effect:


"hh:mm:ss ooo CDL lev [ nnn] : ORDER ACCEPTED"

where ooo is the three-literal identifier of own node, and then:

if lev is in the range from 1 to 7, all diagnostic messages produced by the addressed node(s) having level greater than lev will not be displayed on own node

if lev is equal to "I", no diagnostic and broadcast notify messages produced by the addressed node(s) will be displayed at all on own node

Constrains:



Iss. B





Iss. B

5.3.2.1.2 DL0 - Request Node(s) Diagnostic Level 0

Purpose:

This order allows the operator to request the presentation on own node of all diagnostic messages having level 0 produced by one / all visible node(s).

The DL0 order provides a diagnostic filtering on presentation, not on production; it acts on the diagnostic messages having level equal to 0 (non operational diagnostics).

Syntax:

DL0 <blank> flag [ <blank> nnn ]

where:

flag flag indicating whether the diagnostic level 0 presentation must be enabled; its allowed values are:

"ON" if the presentation of diagnostic level 0 must be enabled

"OFF" if the presentation of diagnostic level 0 must be disabled

nnn optional three-literal identifier of the addressed node(s) (own node, if omitted); its allowed values are:

“ALL” if the order applies to all visible nodes

“LOC” if the order applies to all nodes of own site

“nnn” if the order applies to the node nnn

Effect:


"hh:mm:ss ooo DL0 flag [ nnn] : ORDER ACCEPTED"


if flag is equal to “ON”, all diagnostic messages having level 0 produced by the addressed node(s) will be displayed on own node

if flag is equal to “OFF”, no diagnostic messages having level 0 produced by the addressed node(s) will be displayed on own node

Constrains:





Iss. B

5.3.2.1.3 UDL - Change CSCI(s) Diagnostic Level

Purpose:

This order allows the operator to define up to which level the diagnostic messages from one / all CSCI(s) on a visible node have to be produced toward the system.

The UDL order provides a filtering on production, not on presentation; it acts on diagnostic messages having level included between 0 and 7.

Syntax:

[ nnn <blank> ] UDL <blank> lev <blank> ccc

where:

nnn optional three-literal identifier of the addressed node (own node, if omitted)

lev highest level of diagnostic messages the addressed CSCI(s) is / are allowed to produce toward the system; its allowed values are:

0.. 7 if diagnostic messages up to the given level 0..7 have to be produced

“I” if no diagnostic messages have to be produced at all

ccc three-literal identifier of the addressed CSCI(s); its allowed values are:

“ALL” if the order applies to all CSCIs in the addressed node

“ccc” if the order applies to the CSCI ccc

Effect:

SMD on node nnn replies the following acknowledge:

"hh:mm:ss nnn UDL lev ccc : ORDER ACCEPTED"

and then:

if lev is in the range from 0 to 7, all diagnostic messages having level greater than lev will not be produced by the addressed CSCI(s) toward the system

if lev is equal to "I", no diagnostic messages at all will be produced by the addressed CSCI(s) toward the system

Constrains:



ccc is the identifier of a CSCI which is unknown by SMD on the addressed node



Iss. B

5.3.2.1.4 SUL - Show CSCI(s) Diagnostic Level

Purpose:

This order allows the operator to display which is / are the maximum diagnostic level(s) to be produced by one / all CSCIs on a visible node.

Syntax:

[ nnn <blank> ] SUL <blank> ccc

where:





Effect:

SMD on node nnn (own node, if omitted) replies the following acknowledge:

"hh:mm:ss nnn SUL ccc : ORDER ACCEPTED"

and then shows to the operator, in a table like the following one, the maximum level of diagnostic to be produced by the addressed CSCI(s) on the given node:

USERS LEVEL

Func Level

ccc

.

.

.

ccc

lev

.

.

.

lev

where:

ccc name of the CSCI on the addressed node

lev maximum diagnostic level to be produced by the CSCI ccc; it can assume a value from 0 to 7, or the value “no level” if no diagnostic at all have to be produced by it

Constrains:






Iss. B

5.3.2.1.5 DLD - Change Diagnostic Dissemination of RDS Node(s)

Purpose:

This order allows the operator to limit the diagnostic to be sent by the nodes in a visible radar site toward own operative site.

The DLD order provides a diagnostic filtering on production, not on presentation; it acts on diagnostic messages having level included between 0 and 7.

Syntax:

rrr <blank> DLD <blank> lev <blank> nnn

where:

rrr compulsory three-literal of the addressed radar site

lev highest level of diagnostic messages the addressed node(s) must send toward own operative site; its allowed values are:

0.. 7 if diagnostic messages up to the given level 0..7 have to be produced

“I” if no diagnostic messages have to be produced at all

nnn three-literal identifier of the addressed node(s) in the radar site rrr; its allowed values are:

“ALL” if the order applies to all nodes in the radar site rrr

“nnn” if the order applies to the node nnn in the radar site rrr

Effect:

SMD on the bridge node of the radar site rrr replies the following acknowledge:

"hh:mm:ss hhh rrr DLD lev nnn: ORDER ACCEPTED"

where hhh is the three-literal identifier of the bridge node of the radar site rrr, and then:

if lev is in the range from 0 to 7, all diagnostic messages having level greater than lev will not be produced by the addressed node(s) toward own operative site

if lev is equal to "I", no diagnostic messages at all will be produced by the addressed node(s) toward own operative site

Constrains:


rrr is the identifier of a radar site not visible by own node

nnn is the identifier of a node not belonging to the radar site rrr

own site is not an operative site



Iss. B

5.3.2.1.6 SDL - Show Diagnostic Dissemination of RDS Nodes

Purpose:

This order allows the operator to display which is the maximum diagnostic level to be produced by each node of a visible radar site toward a connected operative site.

Syntax:

rrr <blank> SUL <blank> ooowhere:

rrr compulsory three-literal of the addressed radar site

ooo compulsory three-literal of the operative site the order refers to

Effect:

SMD on the bridge node of the radar site rrr replies the following acknowledge:

"hh:mm:ss hhh rrr SDL ooo : ORDER ACCEPTED"

where hhh is the three-literal identifier of the bridge node of the radar site rrr, and then shows to the operator, in a table like the following one, the maximum level of diagnostic to be produced by each node of radar site rrr toward the operative site ooo:

DIAGNOSTIC LEVEL

Node Level

nnn

.

.

.

nnn

lev

.

.

.

lev

where:

nnn name of each node belonging to the radar site rrr

lev maximum diagnostic level which can be produced by the node nnn; it can assume a value from 0 to 7, or the value “no level” if no diagnostic at all have to be produced toward the operative site ooo

Constrains:


rrr is the identifier of a radar site not visible by own node

ooo is the identifier of an operative site not connected to radar site rrr



Iss. B



5.3.2.3 Order examples about Filtering and Dispatching of Diagnostic Messages

CDL 7 ALL the operator requests to display all diagnostic messages produced by all visible system nodes (excluding diagnostic messages with level 0)

CDL 3 LOC the operator requests to display all diagnostic messages having level equal to 1, 2 or 3 produced by all nodes of own site

CDL 4 OT1 the operator requests to display all diagnostic messages having level from 1 to 4 produced by the node OT1

CDL I the operator requests to stop the presentation of all the diagnostic messages produced by own node (excluding diagnostic messages with level 0)

CDL I ALL the operator requests to stop the presentation of all the diagnostic messages produced by all visible system nodes (excluding diagnostic messages with level 0)

DL0 ON the operator requests to display all diagnostic messages having level equal to 0 produced by own node

DL0 ON ALL the operator requests to display all diagnostic messages having level equal to 0 produced by all visible system nodes

DL0 ON OT1 the operator requests to display all diagnostic messages having level equal to 0 produced by the node OT1

DL0 OFF LOC the operator requests to stop the presentation of the diagnostic messages having level equal to 0 produced by all nodes of own site

DL0 OFF OT2 the operator requests to stop the presentation of the diagnostic messages having level equal to 0 produced by the node OT2

UDL 5 ALL the operator requests to limit all CSCI on own node to produce diagnostic messages up to level 5.

OT1 UDL 2 TTM the operator requests to inhibit TTM CSCI on OT1 node to produce diagnostic messages having level greater than 2.

OT2 UDL I TRH the operator requests to inhibit TRH CSCI on OT2 node to produce any diagnostic messages.

UDL I ALL the operator requests to inhibit all CSCI of own node to produce any diagnostic messages



Iss. B

OT1 SUL TRH the operator requests to display the diagnostic level produced by TRH CSCI on OT1 node

OT2 SUL ALL the operator requests to display the diagnostic level produced by all CSCI on OT2 node

OTR DLD 3 OT1 the operator requests to the of site OTR to disseminate toward own site diagnostic messages produced by the node OT1 up to level 3

OTR DLD 5 ALL the operator requests to the of site OTR to disseminate toward own site diagnostic messages produced by all OTR nodes up to level 5

OTR SDL LBO the operator requests to display the diagnostic level disseminates by the radar site OTR towards the operative site LBO

5.3.3 MASKS

Not applicable.

5.3.4 PRINTING


5.3.5 EXAMPLES ABOUT FILTERING AND DISPATCHING OF DIAGNOSTIC MESSAGES

The Diagnostics with Level 0 are mainly used for internal testing of SMD and other CSCIs.

The Diagnostic Dissemination is used to limit on OPS LAN the traffic of RDS diagnostic.



Iss. B

5.4 PRESENTATION OF NODE INFORMATION

BITE Status of Nodes

SMD produces the BITE Status of own node using the information sent from the CSCIs running on the same node:

NSV CSCI sends information about the status of the peripherals and devices of the node

the other CSCIs send information about their logical status

SMD collects these data in order to send the whole BITE Status message of the node, periodically only or at each variation too, toward all visible system nodes.

The operator on the I/O console can request SMD to:

dump immediately the Status message of a visible node

dump repeatedly each Status message of all nodes

Version of CSCIs

SMD memorises the version of a CSCI every time:

the CSCI opens a Path with SMD (start-up)

the CSCI sends a version message (run-time)

Please refer to [2] for more information; the operator can request SMD to:

display the version of one / all CSCI(s) of a visible node

Self-Diagnosis of SMD

In case of recoverable software error (refer to § 8), SMD CSCI can produce a diagnostic message, to inform the operator about the occurrence of an internal software error.


enable / disable SMD self-diagnosis on own node


Please refer to § 5.4.2.1.1 and § 5.4.2.1.3 .



Iss. B

5.4.2 ORDERS

This paragraph describes all orders executed by SMD CSCI relevant to the functionality “Presentation of Node Information”.


5.4.2.1.1 SNI - Immediately Show Node Status

Purpose:

This order allows the operator to immediately display on the I/O console of own node the BITE Status of a visible node.

Syntax:

SNI [ <blank> nnn ]

where:


Effect:


"hh:mm:ss ooo SNI [ nnn] : ORDER ACCEPTED"


shows on own I/O Console the BITE Status of the addressed node, in an hexadecimal dump like the following one:



Iss. B


Status message from nnn Time hh:mm:ss Date dd/mm/yyyy

FUNCTION SMD ID XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX

FUNCTION NSV Status status Node role role ID XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX

FUNCTION ccc ID XX XX XX XX XX XX XX XX XX XX XX XX XX . . .FUNCTION ccc ID XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX


Iss. B

where:

nnn three-literal identifier of the node whose BITE Status is dumped

hh:mm:ss hours, minutes and seconds of time as set on node nnn

dd/mm/yyyy day, month and year of date as set on node nnn

ccc three-literal identifier of the CSCI (here called “function”) on node nnn whose logical status is dumped in the following bytes set

ID hexadecimal value of the system unique identifier of the CSCI on node nnn whose logical status is dumped in the following bytes set

XX hexadecimal value of a byte belonging to a bytes set containing codified information relative to the logical status of the given CSCI ccc; please refer to Appendix A for detailed information about SMD logical status

status node status according to NSV CSCI; this field can assume the following values:

ON

FAULT

DEGRADED

role node role according to NSV CSCI; this field can assume the following values:

MASTER

STANDBY (i.e. SLAVE)

MASTER ALONE

SINGLE

Constrains:



This order is meaningful only when input on I/O console.



Iss. B

5.4.2.1.2 SNR - Repeatedly Show Nodes Status

Purpose:

This order allows the operator to repeatedly display on the I/O console of own node the BITE Status sent by all nodes visible by own node.

Syntax:

SNR [ <blank> END ]

Effect:


"hh:mm:ss nnn SNR [ END] : ORDER ACCEPTED"


if the parameter "END" is omitted, all BITE Status messages sent by all visible nodes will be displayed on own I/O Console, with the same format as described in § 5.4.2.1.1

if the parameter "END" is present, BITE Status messages sent by all visible nodes will be no more displayed on own I/O Console

Constrains:

This order is meaningful only when input on I/O console.



Iss. B

5.4.2.1.3 VER - Show CSCI(s) Version

Purpose:

This order allows the operator to display the software version of one / all CSCI(s) allocated on a visible node.

Syntax:

[ nnn <blank> ] VER <blank> ccc

where:





Effect:

SMD on node nnn (own node, if omitted) replies the following acknowledge:

"hh:mm:ss nnn VER ccc : ORDER ACCEPTED"

and then shows to the operator, in a table like the following one, the software version of the addressed CSCI(s) on the given node:

FUNCTIONS RELEASES

FUN VERSION

ccc

.

.

.

ccc

VV.rr dd-MMM-yyyy [site]

.

.

.

VV.rr dd-MMM-yyyy [site]

where:

ccc three-literal of the CSCI (here called “function”)

VV.rr software version and release numbers of the CSCI ccc

dd-MMM-yyyy software date of the CSCI ccc

site optional site identifier of CSCI ccc

Constrains:



Iss. B






Iss. B

5.4.2.1.4 IEP - Enable SMD Self-Diagnosis

Purpose:

This order allows the operator to enable or disable the self-diagnosis of SMD CSCI on own node, i.e. the presentation of all occurrences of SMD internal software errors (refer to § 8.3).

Syntax:

IEP <blank> flag

where:

flag flag indicating whether the SMD self-diagnosis must be enabled; its allowed values are:

"ON" if the presentation of SMD internal errors must be enabled

"OFF" if the presentation of SMD internal errors must be disabled

Effect:


"hh:mm:ss nnn IEP flag : ORDER ACCEPTED"

where nnn is three-literal identifier of own node, and then:

if flag is equal to “ON”, enable the presentation of SMD self-diagnosis

if flag is equal to “OFF” (default), disable the presentation of SMD self-diagnosis

Constrains:

None.



Iss. B



5.4.2.3 Order examples about Presentation of Node Information

SNI the operator requests to display immediately on the I/O console the status message of own node

SNI OT2 the operator requests to display immediately on the I/O console the status message of node OT2

SNR the operator requests to enable the periodical display on the I/O console all status messages of visible nodes, including own node

SNR END the operator requests to disable the periodical display on the I/O console of all status message

OT2 VER ALL the operator requests to display the software versions of all CSCIs allocated on the node OT2

VER SMD the operator requests on own node to display the software version of SMD CSCI

IEP ON the operator requests SMD CSCI to display its self-diagnosis messages

IEP OFF the operator requests SMD CSCI not to display its self-diagnosis messages

5.4.3 MASKS

Not applicable.

5.4.4 PRINTING


5.4.5 EXAMPLES ABOUT PRESENTATION OF NODE INFORMATION

The Immediate Presentation of Node status on I/O console and SMD self-diagnosis are used mainly for internal testing of SMD and other CSCIs; please refer to:

Appendix A for the description of SMD status message

§ 8.3.2 for the list of internal error messages

The Repeated Presentation of Node status is used mainly by internal CSCIs, e.g. to graphically represent the present status information.



Iss. B

6. OPERATIVE EXAMPLES

The following orders sequence shows a typical working session of the operator:

1) "SPW OT2" typed on OT2 node:

the operator sets the password on own node

2) "CDL 4 OT1" typed on OT2 node:

the operator requests SMD to display on own node (OT2) all diagnostic messages produced by OT1 node having level greater then 0 and less or equal than 4

3) "VER ALL" typed on OT2 node:

the operator requests to display the software versions of all CSCIs on own node (OT2)

4) "DBR "typed on OT2 node:

the operator closes his job session



Iss. B

7. ORDERS LIST

The following table provides, for each order executed by SMD CSCI:

its three-literal mnemonic

its syntax

its possible restrictions

order

syntax restrictions

CDL CDL lev [nnn] -

CPW [nnn] CPW [old_psw new_psw new_psw]

-

DBR DBR only on own node

DL0 DL0 flag [nnn] -

DLD rrr DLD lev nnn -

IEP IEP flag only on own node

MST [nnn] MST -

RPW [nnn] RPW -

SDL rrr SDL ooo -

SLV [nnn] SLV -

SNI SNI [nnn] meaningful only from I/O console

SNR SNR [END] meaningful only from I/O console

SPW SPW password only on own node

SUL [nnn] SUL ccc -

STT STT hh del mm del ss [MM del dd del yy]

-

UDL [nnn] UDL lev ccc -

VER [nnn] VER ccc -



Iss. B

8. GENERAL MESSAGES, ERRORS AND ALARMS

8.1 INTRODUCTION

The general messages produced by SMD toward the operator are:

diagnostic messages (including alarms and software errors)

acknowledges to orders

All diagnostic messages produced by SMD have the following pattern:

"hh:mm:ss nnn l SMD : diagnostic_text"

where:

hh:mm:ss time when SMD has produced the diagnostic

nnn three-literal identifier of the node which has produced the diagnostic

l diagnostic level in the range 0..7

diagnostic_text text which informs about the event to be notified to the operator

Please refer to § 8.2 for the list of all diagnostic messages which can be produced by SMD CSCI, and to § 8.4 for the list of all SMD alarm messages.

SMD also produces a particular diagnostic message with level one, whose diagnostic_text has the following pattern:

"INTERNAL ERROR xxxxH : yyyyH"

where:

xxxx code associated to the routine in which the software error has been detected

yyyy sub-code which differentiates software errors inside the same routine

Please refer to § 8.3.2 for the list of all internal error messages which can be produced by SMD CSCI.

All acknowledges to orders produced by SMD have the following pattern:

"hh:mm:ss nnn ord [params] : ack_text"

where:

hh:mm:ss time when SMD has produced the acknowledge

nnn three-literal identifier of the node which has produced the acknowledge

ord three-literal identifier of the acknowledged order

params optional order parameters



Iss. B

ack_text text which informs about the result of order execution; it is equal to the string “ORDER ACCEPTED” if the order has been correctly executed by SMD CSCI



Iss. B

8.2 DIAGNOSTIC MESSAGES

SMD CSCI produces diagnostic messages whose diagnostic_text, with relative level and explanations, are the following:

“BUFFER BOUNCED FROM XXXX RESULTCODE YYYY” (lev. = 1)SMD has received a buffer bounced from the communication path XXXX

“BUFFER LOST CAUSED BY DETACH PATH WITH EXTERNAL CLOCK X” (lev. = 1)SMD received a detach path message from the external clock, therefore the buffer used for the read operation is lost

“CREATE$PATH FROM FUNCTION UNKNOWN” (lev. = 1)an unknown CSCI requested to open the communication path with SMD

“DISS. NOTIFY MSG NOT EXECUTABLE” (lev. = 1)SMD received a dissemination request which cannot be executed

“DISS. NOTIFY MSG WITH ILLEGAL PARAMETER” (lev. = 1)SMD received a dissemination request containing incorrect parameters

“END DISS. NOTIFY MSG WITH ILLEGAL PARAMETER” (lev. = 1)SMD received an end dissemination request containing incorrect parameters

“END OF DISPATCHING SITE XXX” (lev. = 1)SMD stopped to dispatch messages from the site XXX

“ERROR IN CONFIGURATION OF NETWORKS” (lev. = 1)SMD detected a difference on own node name between NSV and LAN driver information

“GETPATHSTATUS FROM XXXX : DRIVER NOT READY” (lev. = 1)the status of LAN peripheral XXXX is not OK

“MY LINE AND PARTNER NODE LINE NOT OK” (lev. = 1)SMD couldn’t switch the role between two nodes because both lines of slave node are faulted

“NO BUFFER AVAILABLE FOR STATUS DECODING” (lev. = 1)SMD had no more buffers to send the BITE Status message of own node

“NODE XXX STATUS VARIATION ON YYYY - STATUS WWWWWWWWWW” (lev. = 1)SMD notified a change in the status of a node on the LAN

“NOT MODM IN SMD CONFIGURATION” (lev. = 1)



Iss. B

SMD received a request to dispatch messages through lines which aren't in SMD PU_List

“OPEN$PATH REPLY NOT OK FROM MASTER CLOCK” (lev. = 1)SMD failed to open the communication path with the external clock

“READ FROM EXTERNAL CLOCK X : WRONG DATA RECEIVED” (lev. = 1)the read operation on the external clock X returned to SMD with wrong data

“RESPONDPATH FROM XXXX WITH RESULTCODE YYYY” (lev. = 1)SMD failed (with resultcode YYYY) to open the communication path with the peripheral XXXX

“SELECT REPLY FROM XXXX WITH RESULTCODE YYYY” (lev. = 1)SMD failed (with resultcode YYYY) to perform the messages selection from the peripheral XXXX



Iss. B

“SMD TO XXX PATH OVERFLOW RECOVERY” (lev. = 1)the number of messages sent to CSCI XXX and not replied by it is now below a customisable limit

“SMD TO XXX: PATH OVERFLOW” (lev. = 1)the number of messages sent to CSCI XXX and not replied by it has exceeded a customisable limit

“START DISPATCHING SITE XXX PU MAIN YYYY” (lev. = 1)SMD begun to dispatch messages from the site XXX by means of the line YYYY

“THE STARTUP PHASE IS FINISHED : THE NODE IS OPERATIVE” (lev. = 1)SMD notified that its start-up phase has finished

“UNKNOWN MSG: OPCODE XXXX STATUS YYYY USERREF ZZZZ DATADISP WWWW MSGTYPE HHHH FUNCTION FFF” (lev. = 1)SMD received from the CSCI FFF an unknown message whose code is HHHH

“XXXXX --> FAULT: EXTERNAL CLOCK X IS IN FAULT” (lev. = 1)SMD notified that the external clock X is in fault

“XXXXX --> LO_OF: BUFFER BOUNCED FROM EXTERNAL CLOCK X” (lev. = 1)SMD received a buffer bounced from the external clock X

“XXXXX --> LO_OF: EXTERNAL CLOCK X IS IN LOGICAL OFF” (lev. = 1)SMD notified that the external clock X is in logical off (no messages received)

“XXXXX --> NT_SY: EXTERNAL CLOCK X IS NOT SYNCHRONIZED” (lev. = 1)SMD notified that the external clock X is not synchronised

“XXXXX --> NT_SY: EXTERNAL CLOCK X IS ON AND NOT SYNCHRONIZED” (lev. = 1)SMD has notified that the external clock X is ON and not synchronised

“XXXXX --> NT_SY: READ FROM EXTERNAL CLOCK X : WRONG DATA RECEIVED” (lev. = 1)the read operation on the external clock X returned to SMD with wrong data

“XXXXX --> RECOV: EXTERNAL CLOCK X HAS BEEN RECOVERED” (lev. = 1)SMD has notified that the external clock X has been recovered.

“XXXXX --> RECOV: READ FROM EXTERNAL CLOCK X NOT OK” (lev. = 1)the read operation on external clock X returned with a negative result

“XXXXX --> SYNCR: EXTERNAL CLOCK X HAS RECOVERED THE SYNCHRONISM” (lev. = 1)SMD has notified that the external clock X has recovered the synchronism

“XXXXX --> SYNCR: EXTERNAL CLOCK X IS ON AND SYNCHRONIZED” (lev. = 1)SMD has notified that the external clock X is ON and synchronised

“XXXXX --> SYNCR: EXTERNAL CLOCK X IS SYNCHRONIZED” (lev. = 1)SMD notified that the external clock X is synchronised

“XXXXX --> WA_SY: EXTERNAL CLOCK X HAS LOST THE SYNCHRONISM” (lev. = 1)



Iss. B

SMD notified that the external clock X has lost the synchronism



Iss. B

8.3 ERROR MESSAGES

SMD can detect the following four types of errors, ordered by their severity:

1) Exceptions (Fatal Errors) with consequent HALT of the node

2) SMD Software Errors caused by SMD CSCI itself

3) Other Software Errors caused by other interfacing CSCIs

4) Operator’s Errors caused by wrong operator’s requests

8.3.1 EXCEPTIONS

The Exceptions that can be raised by SMD are the following:

hex code

explanation of the fatal error

0101 SMD has requested a mailbox creation to Operating System but this service was not successful

0102 during SMD pool creation the Operating System has rejected a buffer request

0103 SMD has requested a path creation towards NSV but Operating System has rejected the request

0104 SMD has requested a path creation towards NSV but this CSCI has rejected the request

0105 SMD has requested a Timer creation to Operating System but this service was not successful

0106 SMD is not present in the table which describes the nodal CSCIs

0107 NSV is not present in the table which describes the nodal CSCIs

0108 the Go Message does not contain own node name

0109 SMD cannot open the path with a peripheral because the UCB List is full

010A SMD has requested a path creation with a device but Operating System has rejected this service

010B SMD has on-line requested a data segment to Operating System but the service was not successful

010C SMD has to use too many devices than maximum number of handled devices

010D NSV has assigned a peripheral type to SMD that does not handle it

010E SMD cannot open the path with a peripheral because the Devices Table is full

010F the Go Message assigns a peripheral to SMD that does not find it into own configuration

0110 the Go Message assigns too many LANs to SMD than maximum number of handled LANs

0111 the Go Message assigns too many Lines to SMD than maximum number of handled Lines



Iss. B

0112 the Operating System has rejected an on-line SMD buffer request due to end of memory

0113 the Go Message assigns too many Clocks to SMD than maximum number of handled Clocks

0114 SMD has requested a Process creation to Operating System but this service was not successful

0115 SMD has requested a Semaphore creation to Operating System but the service was not successful

0116 SMD has requested a do case operation to Operating System but an error occurs

0117 SMD has requested a data copy operation to Operating System but an overflow occurs



Iss. B

8.3.2 SMD SOFTWARE ERRORS

All SMD Software Errors are signalled by SMD with a diagnostic message with level one, whose diagnostic_text has the following pattern:

"INTERNAL ERROR xxxxH : yyyyH"

The Software Errors that can be issued by SMD are the following:

xxxx yyyy procedure explanation of the internal error0014 yyyy diag_disp the Diag module received an unexpected message001E yyyy level_modify_fun the origin and/or the operation code of a Level Modify message is erroneous0037 0064 dispatch_this_messa

geSMD cannot elaborate the message because it cannot have the needful buffer

003C 000A diag_notify_fun the pointer of the message coming from a nodal CSCI or from NSV is NIL003C yyyy diag_notify_fun the origin and/or the operation code of a Diagnostic Notify message is erroneous0041 yyyy diag_msg_fun the origin and/or the operation code of a Diagnostic Message is erroneous0046 yyyy diag_req_fun the origin and/or the operation code of a CDL order is erroneous005A 000A cons_table_fun the site name received in a message coming from network isn't equal to own site

name005A 0014 cons_table_fun the site name received is not present into the table005A 001E cons_table_fun the site name received in a message coming from line isn't equal to own site

name005A 0028 cons_table_fun the site name received is not present in the table005A yyyy cons_table_fun the origin and/or the operation code of a user table is erroneous0064 yyyy prod_table_fun the origin and/or the operation code of a producer table is erroneous006E yyyy diag_req_pas_fun the origin and/or the operation code of a CDP order is erroneous0078 0001 smista_diag_msg SMD received a Diagnostic Message from a node belonging to an unknown site0082 0014 order_msg_fun SMD received a wrong message from network0082 0064 order_msg_fun SMD received a wrong message from line0082 yyyy order_msg_fun the origin and/or the operation code of a Order Message is erroneous008C yyyy order_req_fun the origin and/or the operation code of a Order Request Message is erroneous00A0 yyyy ack_to_function_fun the origin and/or the operation code of a Ack to Function Message is erroneous00AA 0028 ack_from_executor_f

unSMD received an Acknowledge from CSCI with Ack Type field = 0 (erroneous)

00AA 0032 ack_from_executor_fun

SMD received an Acknowledge from CSCI with Ack Type field > 3 (erroneous)


SMD received from LAN an Acknowledge From Executor with Ack Type field = 0


SMD received from LAN an Acknowledge From with Ack Type field > 3

00AA 006E ack_from_executor_fun

SMD received from Line an Acknowledge From Executor with Ack Type field = 0


SMD received from Line an Acknowledge From Executor with Ack Type field > 3

00AA yyyy ack_from_executor_fun

the origin and/or the operation code of an Acknowledge From Executor is erroneous

00B4 yyyy order_disp the Order module received an unexpected message00BE yyyy notify_ack_fun the origin and/or the operation code of a Notify Ack Message is erroneous00CA yyyy notify_lan_message_fun the origin and/or the operation code of a Notify LAN Message is erroneous00CB yyyy lan_msg_request_fun the origin and/or the operation code of a LAN Message Request is erroneous



Iss. B

00CC 0001 insert_maint_node the node is already present into the Maintenance Nodes table00CD 0005 receive_lan_status_f

unthe text length is wrong

00CD 0006 receive_lan_status_fun

the text length is wrong

00CD yyyy receive_lan_status_fun

the origin and/or the operation code of a Receive LAN Status is erroneous

00D2 0001 smd_order_disp the order has been refused, then it will not be sent toward the other CSCIs which uses it

00D2 0002 smd_order_disp SMD received an irregular Order to be executed by SMD itself00DC yyyy clock_disp the Clock module received an unexpected message00DE yyyy settime_msg_fun the origin and/or the operation code of a SetTime message is erroneous00E0 yyyy time_reass_fun the origin and/or the operation code of a TimeReassigned message is erroneous00E4 yyyy time_sync_msg_fun the origin and/or the operation code of a TimeSynchronism message is

erroneous00F0 yyyy visual_ver_fun the origin and/or the operation code of a VER order is erroneous00FA yyyy dis_order_fun the origin and/or the operation code of a DIS order is erroneous ( ref. to [2] )0104 0005 ack_to_pass_cons_fu

nsite number not found into the table

0104 0046 ack_to_pass_cons_fun

SMD received Acknowledge to diagnostic passive users from LAN with Ack Type = 0


SMD received Acknowledge to diagnostic passive users from LAN with Ack Type > 3

0104 006E ack_to_pass_cons_fun

SMD received Acknowledge to diagnostic passive users from Line with Ack Type = 0


SMD received Acknowledge to diagnostic passive users from Line with Ack Type > 3

0104 yyyy ack_to_pass_cons_fun

the origin and/or the op. code of Acknowledge to diagnostic passive users is erroneous

010E yyyy lok_ord_fun the origin and/or the operation code of a RDS Lock order is erroneous0118 0007 receive_lok_tab_fun the LOK order is requested but own node isn't in lock enable0118 yyyy receive_lok_tab_fun the origin and/or the operation code of the Table of RDS lock owners is

erroneous011D 000A node_mode SMD received an Operative Mode Notify which contains an erroneous field mode011D 0014 node_mode the node is already present into the Maintenance Nodes Table011E 0014 notify_request_fun SMD received a Notify Ack Request from CSCI with Ack Type = 0011E 0032 notify_request_fun SMD received a Notify Ack Request from CSCI with Ack Type > 3011E yyyy notify_request_fun the origin and/or the operation code of a Notify Ack Request Message is

erroneous011F 0005 notify_ack_pass_fun site number not found into the table011F 0064 notify_ack_pass_fun SMD received a Notify Ack to diagnostic passive users from LAN with Ack Type =

0011F 000A notify_ack_pass_fun SMD received a Notify Ack to diagnostic passive users from LAN with Ack Type =

3011F 005A notify_ack_pass_fun SMD received a Notify Ack to diagnostic passive users from LAN with Ack Type >

3011F 0050 notify_ack_pass_fun SMD received a Notify Ack to diagnostic passive users from Line with Ack Type =

0011F 0028 notify_ack_pass_fun SMD received a Notify Ack to diagnostic passive users from Line with Ack Type >

3011F yyyy notify_ack_pass_fun the origin and/or the op code of a Notify Ack to diagnostic passive users is

erroneous0120 yyyy mst_order_fun the origin and/or the operation code of a MST order is erroneous



Iss. B

0121 yyyy slv_order_fun the origin and/or the operation code of a SLV order is erroneous0123 0064 lok_ord_disp lock request refused because the sender node is not present into the lock priority

table0123 006E lok_ord_disp site number not found into the table0123 0078 lok_ord_disp site number not found into the table012C yyyy mem_order_fun the origin and/or the operation code of a MEM order is erroneous0136 yyyy mlm_order_fun the origin and/or the operation code of a MLM order is erroneous014A 0064 put_pool the value of the pointer that must be released to the internal pool is NIL014F 012C lff_order_fun the syntax of the input order isn't correct015F 0064 sul_diag_fun the syntax of the requested command isn't correct0160 012C iep_diag_fun the syntax of the requested command isn't correct0161 yyyy dld_tbl_management_fu

nthe origin and/or the operation code of a DLD Table Management is erroneous

0162 yyyy global_prod_tab_fun the origin and/or the operation code of Global Production Table is erroneous0168 yyyy diag_pass_cons_fun the origin and/or the operation code of a Diagnostic To Passive Message is

erroneous0172 000A alarm_msg_fun the pointer of the message coming from a nodal CSCI or from NSV is NIL0172 yyyy alarm_msg_fun the origin and/or the operation code of a Alarm Message is erroneous018B yyyy level_zero_req_fun the origin and/or the operation code of a DL0 order is erroneous018D yyyy udl_order_fun the origin and/or the operation code of a UDL order is erroneous018E 00C8 dld_diag_fun apparatus not present into the table018E 0064 dld_diag_fun site name not present into the table018E 012C dld_diag_fun the message coming from a RDS node018F 0064 sdl_diag_fun the message isn't of line type0190 yyyy init_disp the Init module received an unexpected message019A 0001 create_path_fun SMD received a path request from a CSCI which already has the path with SMD019A 0002 create_path_fun SMD cannot open a path with a user because the UCB List is full019A 0003 create_path_fun SMD cannot open a path with a user because the Version Table is full019A 0004 create_path_fun A CSCI has already sent to SMD its version by means of a Version Notify

Message and therefore the version included in the present Path Request cannot be used

01A4 000A diss_notify_fun SMD received a Dissemination Notify not congruent with SMD configuration data01A4 yyyy diss_notify_fun the origin and/or the operation code of a Dissemination Notify message is

erroneous01AE yyyy end_diss_fun the origin and/or the operation code of an End Dissemination Notify is erroneous01B8 yyyy select_main_fun the origin and/or the operation code of a Selection of Main LAN message is

erroneous01C2 yyyy iosp_select_fun the origin and/or the operation code of a Selection Reply message is erroneous01C2 000A iosp_select_fun SMD received a Selection Reply but doesn't find the item of UCB List of the

peripheral01C2 000B iosp_select_fun SMD received a Selection Reply but doesn't find the item of Devices Table of

peripheral01C2 000C iosp_select_fun SMD received a Selection Reply message but the operation is failed01CC yyyy path_status_fun the origin and/or the operation code of a Get Path Status Reply message is

erroneous01D6 yyyy lan_status_fun the origin and/or the operation code of a LAN Status message is erroneous01E0 yyyy him_fault_fun the origin and/or the operation code of a HIM Fault message is erroneous01F4 yyyy go_message_fun the origin and/or the operation code of a Go Message is erroneous01FE yyyy terminate_msg_fun the origin and/or the operation code of a Node Terminate message is erroneous0208 yyyy console_message_fu

nthe origin and/or the operation code of a Console Message is erroneous

0212 yyyy disable_request_fun the origin and/or the operation code of a DBR order is erroneous



Iss. B

021C yyyy enable_request_fun the origin and/or the operation code of a SPW order is erroneous0226 0001 disp_open_path SMD received a Create Path Reply but doesn't find the item of UCB List of

peripheral0226 0002 disp_open_path SMD received a Create Path Reply but doesn't find the item of Devices Table0230 0000 open_path_fun the origin and/or the operation code of a Open Reply from external clock is

erroneous0244 yyyy resetta_password_fu

nthe origin and/or the operation code of a RPW order is erroneous

024E yyyy cambia_password_fun

the origin and/or the operation code of a CPW order is erroneous

0253 000A pu_status_fun the information length about the node status isn't correct0253 yyyy pu_status_fun the origin and/or the operation code of a PU Status Message is erroneous0254 yyyy status_pl_fun the origin and/or the operation code of a Status PL Message is erroneous0255 yyyy version_msg_fun the origin and/or the operation code of a Version Notify Message is erroneous0255 000A version_msg_fun the Versions Table is full and therefore SMD must reject the received Version

Notify0255 0014 version_msg_fun a CSCI already sent its version to SMD therefore the Version Notify cannot be

used0256 0064 syntax_control the syntax of SLO order isn't correct0258 yyyy stat_disp SMD error, the Stat module received an unexpected message0262 yyyy status_msg_fun the origin and/or the operation code of a Status Message is erroneous026C 0014 status_notify_fun the buffer containing the node status is full026C 001E status_notify_fun a CSCI has sent to SMD a Status Message whose length is different from

previous Status026C yyyy status_notify_fun the origin and/or the operation code of a Status Notify Message is erroneous0276 000A status_immediate_fu

nsite number not present into the table

0276 yyyy status_immediate_fun

the origin and/or the operation code of a SNI order is erroneous

0280 yyyy status_repeated_fun the origin and/or the operation code of a SNR order is erroneous028A 000A node_status_msg_fu

nsite number not present into the table

028A yyyy node_status_msg_fun

the origin and/or the operation code of a Node Status Message is erroneous

0294 yyyy status_reset_fun the origin and/or the operation code of a Status Reset is erroneous 02BC 000A dispatcher SMD received an unexpected reply without corresponding SMD send operation02C1 0001 bounce$main SMD received an unexpected reply without corresponding SMD send operation02C1 0002 bounce$main number of message = 0 (send operation without incrementing the counter

NUM$MG)0320 yyyy interface_disp the Interface module received an unexpected message032A yyyy rebuild_msg_fun the origin and/or the operation code of a message subdivided in packets is

erroneous0334 yyyy service_dispatching_fun the origin and/or the operation of the service messages is erroneous033E 0001 line_commutation the message is addressed to own node but the sender is not the twin node033E 0002 line_commutation own node is not a node of a matched pair0348 0001 prepare_question SMD received the question about his line, but it isn't the twin node of the sender

node0384 yyyy nonstand_disp the Nonstand module received an unexpected message038E 000A nonstand_msg_fun SMD received a Non Standard Message from LAN with Ack Type = 0038E 0014 nonstand_msg_fun SMD received a Non Standard Message from LAN with Ack Type = 0

or the Message Type of a Non Standard Message is not in the range of the types A, B

038E 001E nonstand_msg_fun SMD received a Non Standard Message from Line with Ack Type = 0



Iss. B

038E 0028 nonstand_msg_fun SMD received a Non Standard Message from with Ack Type > 2or the Message Type of a Non Standard Message is not in the range of the types A, B

038E 0032 nonstand_msg_fun SMD received a Non Standard Message from CSCI with Ack Type = 0038E 003C nonstand_msg_fun SMD received a Non Standard Message from with Ack Type > 2

or the Message Type of a Non Standard Message is not in the range of the types A, B

038E yyyy nonstand_msg_fun the origin and/or the operation code of a Non Standard Message is erroneous0398 yyyy tcr_order_fun the origin and/or the operation code of a TCR order is erroneous ( ref. to [2] )03A2 yyyy functional_north_msg_f

unthe origin and/or the operation code of a North Message is erroneous

03AC yyyy clock_status_variation_fun

the origin and/or the operation code of a Clock Status Variation is erroneous

03B6 yyyy clock_handler the origin and/or the operation code of a Clock Handler is erroneous03E8 0001 invia_msg SMD doesn't find the pointer of the UCB item of output message addressee03E8 0002 invia_msg SMD, during the output of a message, finds erroneous the field UCB05DD yyyy slo_order_fun the origin and/or the operation code of a SLO order is erroneous



Iss. B

8.3.3 OTHER SOFTWARE ERRORS

The negative Result-Codes that can be returned by SMD to the other CSCIs are the following:

hex. code

explanation of the error

1 SMD produced a codified diagnostic of Internal Error type2 a CSCI sent to SMD an order with wrong syntax, and therefore the order was rejected3 a CSCI sent an Order List to SMD but the number of orders class exceeds its

maximum value4 a CSCI has notified own Logical Status to SMD but the Node Status buffer is already

full5 a CSCI has sent a request to SMD but this cannot be executed6 SMD has received an order to be dispatched to user CSCIs, but the order time-out

expired7 a CSCI already sent its version to SMD, therefore the received Version Notify cannot

be used8 the CSCI Versions Table is full, therefore SMD must reject the received Version

Notify0A an SMD order is in progress and only at its end SMD will be able to execute other

orders0B SMD has received an order to dispatch to user CSCIs but the order got lost0C a CSCI has attempted to enter in the system without setting the password0D a CSCI has attempted to send an order towards RDS but own node is not the lock

owner11 SMD has received an unknown message12 SMD has received a request before receiving the Go Message from NSV13 SMD has received a notify ack having a size greater than the size of SMD buffers14 SMD has received the lock request for an unknown radar site15 SMD has received the request to send out a local order16 SMD has received an order inconsistent with the role of the node17 the typed string is not correct



Iss. B

8.3.4 OPERATOR’S ERRORS

The negative acknowledges that can be returned by SMD after operator’s orders are the following:

“EXECUTOR NOT FOUND”the operator has typed an order but SMD does not find any executor CSCI

“ILLEGAL PARAMETER”the operator has typed an SMD order using a wrong syntax, therefore the order is rejected by SMD

“ILLEGAL PASSWORD”the operator has attempted to enter a wrong password

“IMPOSSIBLE TO SWITCH”SMD has received a MST or SLV order, but the role of the node is master alone

“INCONSISTENCE ORDER WITH MASTER STATUS OF NODE”SMD has received a MST order, but the role of the node is already master

“INCONSISTENCE ORDER WITH STANDBY STATUS OF NODE”SMD has received a SLV order but the role of the node is already slave

“LOCK BELONGS TO ANOTHER NODE”the operator requested own node to become the RDS lock owner, but another node already owns the lock

“MAINTENANCE ENABLED MODE : ORDER NOT ACCEPTED”the operator has produced an order which cannot be accepted by SMD, because it would set the matched pair of nodes in an inconsistent status

“MAINTENANCE LOCKED MODE : ORDER NOT ACCEPTED”the operator has produced an order which cannot be accepted by SMD, because it would set the matched pair of nodes in an inconsistent status

“NO ORDERS CLASS IS LOCKED”the order can't be executed because no orders class is locked

“NODE NAME NOT IN MATCHED PAIRS TABLE”SMD does not find the name of the own node into the table of matched pair nodes, therefore cannot know the name of the partner node

“NODE WITHOUT LOCK : ORDER NOT EXECUTED”the operator has attempted to send an order towards an RDS, or he has attempted to release the RDS lock, but own node is not the lock owner

“OPERATIONAL MODE: ORDER NOT ACCEPTED”the operator has produced an order which cannot be accepted by SMD, because it would set the matched pair of nodes in an inconsistent status

“ORDER ALREADY IN PROGRESS”a previous order is in progress, thus only after its completion SMD will be able to execute next order

“ORDER NOT ACCEPTED: AN STT ORDER IS ALREADY IN EXECUTION”the operator has requested an STT order, but the execution of previous STT order is still in progress

“ORDER NOT ACCEPTED: NODE IN STARTUP PHASE”the operator has requested an order that the node in start-up phase can't accept



Iss. B

“ORDER NOT ACCEPTED: SYSTEM ALREADY SYNCHRONIZED”the operator has requested the STT order, but the system is already synchronised by external clock

“ORDER NOT ACCEPTED: THE INHIBITION TIME IS ACTIVE”the operator requested an STT order with the hour near midnight, or the system time is near midnight

“ORDER NOT ACCEPTED: THE STATUS OF XXX SITE NODES IS UNKNOWN”the lock order is refused because the nodes status of the referred site is not OK

“ORDER NOT ACCEPTED: UNKNOWN SITE”the operator has request the lock of an unknown radar site

“ORDER NOT ACCEPTED: WRONG INFORMATION ABOUT SENDER NODEthe lock request is refused because the sender node is not present into the lock-priority table

“ORDER NOT EXECUTED: UNKNOWN FUNCTION”the typed order is referred to an unknown CSCI

“ORDER NOT SENT: NODE DISCONNECTED”the typed order is refused because the node is not connected on LAN or it is in fault

“ORDER NOT SENT: XXX SITE DISCONNECTED”the typed order is refused because the addressed site is not connected with own site

“ORDER TIMEOUT EXPIRED”the operator has typed an order but no CSCI has executed it within a customisable time-out

“RDS LOCK IS NOT ENABLED ON THIS NODE”the RDS lock request is refused because lock service is not enabled on the addressed node

“THE OBJECT NODE HAS THE LOCK : ORDER NOT ACCEPTED”the node addressed by the request is the RDS lock owner, therefore cannot go to an operative status which is not congruent with lock possession

“THE OBJECT NODE IS NOT ENABLED TO MAINTENANCE MODE”MEM order cannot be accepted because the maintenance service is not enabled on the addressed node

“THE OBJECT SITE IS OPS: LOCK NOT ACCEPTED”the operator has requested the lock of an Operative Site instead of a Radar Site

“THE RECEIVED ORDER IS LOCAL FOR XXX NODE: ORDER NOT ACCEPTED”the typed order is local for another node

“THE STT ORDER IS REFUSED BECAUSE IT NOT CONTAINS THE DATE”the date has never been set before in the system, and the STT order doesn’t provide it

“THE TYPED ORDER IS LOCAL FOR XXX NODE: ORDER NOT ACCEPTED”the operator has attempted to send out an order, but this order is local for own node XXX

“YOUR NODE ALREADY OWNS RDS LOCK : ORDER NOT ACCEPTED”the LOK order is useless because own node is already the RDS lock owner

“YOUR NODE HAS NOT NEEDFUL PRIORITY : ORDER NOT ACCEPTED”another node has higher lock-priority than own node, which therefore cannot become RDS lock owner

“YOUR NODE ROLE IS SINGLE: ORDER NOT ACCEPTED”the operator has requested a masterslave commutation, but the role of own node is single

“YOUR NODE ROLE IS SLAVE : ORDER NOT ACCEPTED”the role of own node is slave, therefore own node cannot become RDS lock owner



Iss. B

8.3.5 ALARM MESSAGES

The format of the SMD alarm messages is the same of SMD diagnostic messages (refer to § 8.1); the only alarm that can be issued by SMD is the following:

"THE COMMUNICATION WITH LOCK HANDLER WAS INTERRUPT - THE LOCK IS LOST" (lev. 2)

the lock owner node is no more connected with the lock handler node, and therefore it releases the RDS lock; this can happen only if the lock owner was an OPS node, otherwise in this case the lock owner becomes itself lock handler



Iss. B

9. DEGRADED WORKING

During its operation SMD uses the following devices:

LAN, usually redundant, for the communication among nodes in own site (RDS and OPS)

serial line, usually redundant, for the communication between radar and operative sites

external clock, usually redundant, for system time alignment

The possible degraded situations for SMD are consequently the following:

one of the two LANs of a site are faulted:SMD transmits and receives data to / from both LANs, therefore this degraded situation does not cause any loss of messages for SMD

all the LANs of a site are faulted:the SMDs on own site can no more communicate each other, therefore the operator can not obtain on a node information about the other nodes of own site, and can not send orders towards them; moreover, if the LANs fault occurs in a radar site, the communication between the given RDS and the connected OPS(s) is stopped, with the exception of the RDS bridge nodes

the serial line between a (bridge) node of an RDS and a connected OPS is faulted:SMD on the given bridge node is no more able to use its line to send messages to the given OPS, therefore it will send them, through the RDS LAN, to the partner bridge node, which will forward them, through its undamaged line, to the given OPS; the node in OPS which is in charge of the SMD dissemination of the given RDS will detect the line fault, and will switch, if necessary, the role MAINRESERVE of the RDS lines;therefore, this degraded situation does not cause any loss of messages for SMD

both serial lines between the (bridge) nodes of an RDS and a connected OPS are faulted:the SMDs on all nodes of the given RDS can no more communicate with the SMDs on the nodes of the given OPS, therefore the operator on whatever node of the given OPS can no more send orders / receive information to / from all nodes of the given RDS

one external clock is faulted or no more synchronised:SMD is able to receive time information from both external clocks, therefore this degraded situation does not cause any loss of messages for SMD

both external clocks are faulted or no more synchronised:SMD can no more receive synchronised time information from the external clocks, therefore the system time is extrapolated by the internal clock of the computer having higher priority in the system; the nodal CSCIs are no more able to perform Time Stamping operations

10. START-UP OPERATIVE PROCEDURE

When a node starts, there is a period of time during which SMD does not know the status of the other connected nodes which are already started; during this start-up phase, SMD cannot perform the following critical activities, because they require the knowledge of the status of the connected nodes:

receiving orders from other nodes

sending orders towards other nodes

executing the orders STT, MST, SLV

performing the bridge node service between RDS and OPS

SMD carries out its start-up phase when it has received at least one BITE Status message from each LAN of own site (or after a customisable period of time).



Iss. B

11. APPENDIXES

11.1 APPENDIX A: DESCRIPTION OF SMD STATUS MESSAGE

1 byte Identifier of the sender CSCI 00 = SMD CSCI

1 byte Operative Mode of sender node 07 = operational 04 = maintenance (enabled or locked)

1 byte Lock property 03 = sender node is lock owner of an RDS in the system 07 = sender node is not lock owner of any RDS

1 byte Lock owner site (meaningful only for lock handler node in RDS) 0 = RDS not locked <> 0 = number of the site locking the RDS FFH = information not available to the sender node

2 bytes spare

1 byte for every node connected to first LAN of sender site (if any) 03 = the given node is present on first LAN 02 = the given node is absent on first LAN FFH = information not available to the sender node

1 byte for every node connected to second LAN of sender site (if any) 03 = the given node is present on second LAN 02 = the given node is absent on second LAN FFH = information not available to the sender node

4 bytes for every serial line connected to the sender node (if any, and if to be diagnosed by SMD):

1 byte Line Identifier 1 byte Line Tx Status 01 = RESERVE (no logical connection) 02 = FAULT (no physical connection) 03 = ON (last message correctly transmitted) 04 = OFF (last message not correctly transmitted) 06 = UNKNOWN (no messages ever transmitted)

1 byte Line Rx Status 01 = RESERVE (no logical connection) 02 = FAULT (no physical connection) 03 = ON (messages are continuously received by SMD) 04 = OFF (messages are no more received by SMD) 06 = UNKNOWN (no messages ever received)

1 byte Line role 00 = main 01 = reserve



Iss. B

FFH = information not available (“dummy” line)



Iss. B

5 bytes for every external clock connected to sender node (if any):

1 byte Clock Identifier 1 byte Clock Status 00 = START-UP 02 = FAULT 03 = SYNCHRONISED (synchronised messages received by SMD) 04 = LOGICAL OFF (no messages received by SMD) 05 = NOT SYNCHRONISED (unsynchr. messages received by SMD)

2 bytes spare set to FFH

1 byte Clock Role 00 = main 01 = reserve FFH = information not available

1 byte Clocks Synthesis (if any clock is connected to sender node) 03 = at least one clock is SYNCHRONISED 04 = both clocks are OFF or FAULTED 05 = no clock is SYNCHRONISED but at least one clock is NOT SYNCHRONISED (i.e. it is neither OFF nor FAULTED)

4 bytes for every serial line connected to the sender node and handled by SMR CSCI(if present on the sender node); same fields and values as for SMD lines

1 byte for SMR status on first LAN (if SMR is present on the sender node) 02 = the connection of the sender node on first LAN is OK 03 = the connection of the sender node on first LAN is NOT OK FFH = information not available

If the SMD status message is sent to a “phase 1” site, the format of the message remains almost the same except for:

the field “Lock property” is replaced by the field “Diag_Level”, which represents the maximum diagnostic level to be produced by the sender node, plus one

the field “Lock owner site” and the two subsequent spare bytes are missing



Iss. B

11.2 APPENDIX B: BUCHAREST SMD NODES LIST

"RD1", "RD2", "RD3", "RD4", "RP1", "RP2", "FP1", "FP2", /* 01..08 */ "RF1", "RF2", "RF3", "RF4", "CM1", "CM2", "MT1", "MT2", /* 09..16 */ "MN1", "MN2", "D11", "D12", "D13", "D14", "D15", "D16", /* 17..24 */ "D17", "D18", "D19", "D21", "D22", "D23", "D24", "D25", /* 25..32 */ "D26", "D27", "D28", "D29", "D31", "D32", "D33", "D34", /* 33..40*/ "D35", "D36", "D37", "D38", "D39", "D41", "D42", "D43", /* 41..48 */ "D44", "D45", "D46", "D47", "D48", "D49", "D51", "D52", /* 49..56 */ "D53", "D54", "D55", "D56", "D57", "D58", "D60", "D61", /* 57..64 */ "D62", "D63", "D64", "D65", "D66", "D67", "D68", "D69", /* 65..72 */ "D71", "D72", "D73", "D74", "D75", "D76", "D77", "D78", /* 73..80 */ "D79", "D80", "L29", "T01", "T02", "T03", "T04", "T05", /* 81..88 */ "T06", "T07", "T08", "L01", "L02", "L03", "L04", "L05", /* 89..96 */ "L06", "L07", "L08", "L09", "L10", "L11", "L12", "L13", /* 97..104 */ "L14", "L15", "L16", "L17", "L18", "L19", "L20", "L21", /* 105..112 */ "L22", "L23", "L24", "L25", "L26", "L27", "L28" /* 113..119 */



Iss. B

11.3 APPENDIX C: ARAD SMD NODES LIST

"RD1", "RD2", "FP1", "FP2", "RF1", "RF2", "CM1", "MT1", /* 01..08 */"MT2", "MN1", "MN2", "D01", "D02", "D03", "D04", "D05", /* 09..16 */"D06", "D07", "D08", "D09", "D10", "D11", "D12", "D13", /* 17..24 */"D14", "D15", "D16", "D17", "D21", "D22", "D23", "D24", /* 25..32 */"L13", "L14", "L15", "L16", "L17", "L18", "D31", "D32", /* 33..40 */"D33", "D34", "L19", "L20", "L21", "L22", "L23", "L24", /* 41..48 */"D41", "D42", "D43", "D44", "L25", "L26", "L27", "L28", /* 49..56 */"L29", "L30", "D51", "D52", "D53", "D54", "L31", "L32", /* 57..64 */"L33", "L34", "L01", "L02", "L03", "L04", "L05", "L06", /* 65..72 */"L07", "L08", "L09", "L10", "L11", "L12" /* 73..78 */



Iss. B

11.4 APPENDIX C: CONSTANTA SMD NODES LIST

"RD1", "RD2", "FP1", "FP2", "RF1", "RF2", "CM1", "MT1", /* 01..08 */"MT2", "MN1", "MN2", "D01", "D02", "D03", "D04", "D05", /* 09..16 */"D06", "D07", "D08", "D09", "D10", "D11", "D12", "D25", /* 17..24 */"D26", "D27", "D28", "D29", "D30", "L01", "L02", "L03", /* 25..32 */"L04", "L05", "L06", "L07", "L08", "L09", "L10", "L11", /* 33..40 */"L12", "D43", "D44", "D45", "D46"


Documents

UM_XSD_ES010006101UM11_B