psm31a40397-ee

CS-C1

CLG870.5-104 Software Installation Manual

n o i t a z i r n o h o t i t u a a s r i r i o o r t p u r a i e n h t o t s u s o n h t a i s w s s r e t e i r i t a s p e r d d i à h t

DIFFUSION :

CONFIDENTIELLE 

RESTREINTE 

CONTROLEE 

LIBRE 

ACCESSIBILITY

CONFIDENTIAL CONFIDENTIAL

RESTRICTED

CONTROLLED

FREE

o é t u d q i t e n a u i c m n u m o m c m o u c o r o é d i e p i o p c o , c é , s d i e l i t s u u e e r b t t ê o n s l a l a p t h s i o d n d a e n M O M T S O T L S A

L f o A t y

’ r d e p é o t r é p i r e p i v o s r l u p c t x n e e e h t m u i s c t o n d e e m u C c o d s i h T

DATE

NOM

11/02/04

NAME

ETABLI ESTABLISHED

VERIFIE CHECKED

APPROUVE APPROVED

SIGNATURE

P. EZANNO G. RAGOUILLAUX

Power Electrical and Control Systems

R. CHABANNE

REV

STAT.

P S M 3 1 A 4 0 3 9 7 D 0 0 4 A P

F°/F° FIN

Nb F°

SH/SH END N of SH

E

GFE

1/71

71

TABLE DES MODIFICATIONS / MODIFICATIONS TABLE REV

C 1 0 4 A P

ETABLI

VERIFIE

APPROUVE

ESTABLISHED

CHECKED

APPROVED

A

RAGOUILLAUX

GRAVIL

B

RAGOUILLAUX

DROUHOT

CHABANNE

C

RAGOUILL RAGOUILLAUX AUX

DROUHOT DROUHOT

D

EZANNO

E

EZANNO

21/05/02

MODIFICATIONS

STAT.

Version originale

BPE

26/12/02

Adjonction des ASDUs relatifs aux Tc doubles et TVC de type Bitstring

BPE

CHABANNE CHABANNE

17/02/03 17/02/03

Adjonctio Adjonction n de ASDUs et variables variables système système selon PID

BPE

RAGOUILLA RAGOUILLAUX UX

CHABANNE CHABANNE

18/12/03 18/12/03

English English translati translation on and Update Update for multiple multiple LRU

BPE

RAGOUILL RAGOUILLAUX AUX

CHABANNE CHABANNE

11/02/04 11/02/04

Installati Installation on procedures procedures under UNIX or Windows Windows NT/XP

BPE


ZACHARIA

DATE

PSM31A40397.2/72

TABLE OF CONTENTS 1

INTRODUCTION .................................................................................. ........................................................................................... ......... 5

1.1

GENERAL PRESENTATION ........................................................................ ............................................................................ .... 5

1.2

CONFIGURABLE CONFIGURABLE PROTOCOL ELEMENTS ....................................................... 6

1.3

DEFINITIONS................................................................................................ 7

2

RECOMMENDED CONFIGURATION.............................................................. 8

2.1

HARDWARE CONFIGURATION ..................................................................... 8

2.1.1

CLG870.5-104 application host stations..................................................... stations....................................................... 8

2.1.2

Expansion board for the TCP/IP link ........................................................... 8

2.2

CONTROCAD CONFIGURATION................................................................. 10

2.3

CONFIGURING THE APPLICATION............................................................. 11

2.3.1

Definition of the System configuration file: phkb_Sys_***_ phkb_Sys_***_ n .do .do ........... ............... .... 13

2.3.2

Definition of the application Data configuration file: phkb_Data_***_n .do .do ........................................................................ .................................................................................. .......... 28

3

INSTALLATION ............................................................................. ........................................................................................... .............. 59

3.1

PRIOR STATE................................................................................. STATE............................................................................................... .............. 59

3.2

INSTALLATION PROCEDURE UNDER UNIX ................................................ 59

3.2.1

Installation of the IEC files......................................................................... 59

3.2.2

Adding the IEC function to the system configuration ............................... 61

3.2.3

Installing the IEC function on selected stations......................................... 62

3.3

INSTALLATION PROCEDURE UNDER WINDOWS NT/XP ............................ 64

3.3.1

Hardware configuration ............................................................................ 64

3.3.2

List of software media ............................................................................... 64

3.3.3

Controcad configuration ............................................................................ 64

3.3.4

CSS-G installation ...................................................................................... 65

3.3.5

Configuration files ....................................................................... ..................................................................................... .............. 66

3.3.6

Installation of an additional CSS-G........................................................... 66


PSM31A40397.3/72

3.4

STARTING AND STOPPING THE SOFTWARE .............................................. 67

3.4.1

Under UNIX ............................................................................................... 67

3.4.2

Under NT.................................................................................................... 67

4

MAINTENANCE........................................................................................... 68

4.1

FILES MANIPULATED BY THE SOFTWARE APPLICATION ............................ 68

4.2

COUNTER MEMORIZATION FILE ................................................................ 71

4.3

TM PARAMETERS CONFIGURATION FILE ................................................... 72


PSM31A40397.4/72

1

INTRODUCTION

1.1

GENERAL PRESENTATION CLG870.5-104 (slave IEC) is a Solaris or Windows NT/XP-based software application used to establish a gateway between the Centralog and a controlling station by means of the IEC 870.5-104 communication protocol. The area of application of this protocol is wide. The CLG 870.5-104 software application implements a major part of the protocol, i.e. that part which concerns the communication of the principal Centralog variable types: TSs, TMs and counters sent from the Centralog to the controlling station; TSs, TMs, VRs, TCs and TVCs transmitted from the controlling station to the Centralog (the PID describes the specific implementation in detail). The parameters described in the present document enable operation of the CLG 870.5-104 application to be adapted to the controlling station with which it communicates. Before installing the application the following configuration points should be agreed in link with the persons responsible for the controlling station: •

parameters defining the IEC 870.5-104 protocol implementation options, size of variable identifiers, choice of transmission in delta mode or not for data transmitted in spontaneous mode, operation of the general check, etc.

•

physical characteristics of the link: parameters of the TCP/IP link.

•

data to be exchanged: identifiers and parameters of each variable .

This document describes how to configure and install the application using the ADM tool.


PSM31A40397.5/72

1.2

CONFIGURABLE PROTOCOL ELEMENTS

The table below summarizes the principal elements of the IEC 870.5-104 protocol that can be configured in this communications gateway. Description ASDU <01>: Single_Point_information - non-timetagged TS state ASDU <03>: Double_Point_Information – non-timetagged dual TS state ASDU <05>: Step_Position – non-timetagged VR value ASDU <09>: Nornalized_value –non-timetagged standardized format TM value ASDU <11>: Scaled_value – non-timetagged scaled TM value ASDU <13>: Floating_point_value – non-timetagged floating format TM value ASDU <15>: Integrated_totals – non-timetagged counter value ASDU <30>: Dated_Single_Point_information - timetagged TS state ASDU <31>: Dated_Double_Point_Information – timetagged dual TS state ASDU <32>: Dated_Step_Position – timetagged VR value ASDU <34>: Dated_Nornalized_value – timetagged standardized format TM value ASDU <35>: Dated_Scaled_value – timetagged scaled TM value ASDU <36>: Dated_Floating_point_value – timetagged floating point TM value ASDU <37>: Dated_Integrated_totals – non-timetagged counter value ASDU <45>: Single_Command - non-timetagged single TC ASDU <46>: Double_Command - non-timetagged dual TC ASDU <47>: Regulating _Step - non-timetagged TC +/ ASDU <48>: Normalised_Set_point - non-timetagged standardized TVC ASDU <49>: Scaled_Set_point - non-timetagged scaled TVC ASDU <51>: Floating_point _Set_point – non-timetagged floating point format TVC ASDU <50>: Bitstring _Set_point - TVC transported by a 32 bit bitstring ASDU <58>: Dated_Single_Command – timetagged single TC ASDU <59>: Dated_Double_Command – timetagged dual TC ASDU <60>: Dated_Regulating _Step – timetagged TC +/ ASDU <61>: Dated_Normalised_Set_point – timetagged standardized TVC ASDU <62>: Normalised_Set_point – timetagged scaled TVC ASDU <63>: Dated_Floating_point _Set_point - timetagged floating point format TVC ASDU <110>: Parameter_Normalised_value - standardized TM parameter ASDU <112>: Parameter_Floating_point _ value - floating point TM parameter Parameters applicable to single TSs Parameters applicable to dual TSs Parameters applicable to TMs Parameters applicable to VRs (Step_Position) Parameters applicable to counters Parameters applicable to single, dual and incremental TCs Parameters applicable to TVCs Parameters applicable to TSPs Parameters applicable to TMPs Parameters defining the preferred implementation of the protocol Dimensioning and timing parameters Parameters regarding bi-directional mode and multi-master redundancy


Link ASDU_01 ASDU_03 ASDU_05 ASDU_09 ASDU_11 ASDU_13 ASDU_15 ASDU_30 ASDU_31 ASDU_32 ASDU_34 ASDU_35 ASDU_36 ASDU_37 ASDU_45 ASDU_46 ASDU_47 ASDU_48 ASDU_49 ASDU_50 ASDU_51 ASDU_58 ASDU_59 ASDU_60 ASDU_61 ASDU_62 ASDU_63 ASDU_110 ASDU_112 TS parameters Dual TS parameters TM parameters VR parameters_VR Counter parameters TC parameters TVC parameters TSP parameters TMP parameters Main_Choices Size_Time Bi_direction

PSM31A40397.6/72

DEFINITIONS

1.3

•

GTW

: Gateway

•

IEC

: Communication standard from the International Electro-technical Commission

•

CIS

: Real time CENTRALOG database

•

CCC

: maintenance and setting tools station for the Centralog system

•

CVS

: Station supporting MMI functions

•

QUAD

: 4 Ethernet ports board

•

IBDD

: interface layer between MMI or gateway function and the real time database

•

BDBF

: Functional Block database

•

TCP/IP

: Ethernet transport and link layers

•

EXP

: MMI function of Centralog

•

CLOGSQL

: Centralog SQL server

•

SYSCLOG

: Centralog installation program

•

TS

: Digital point (logical input acquired in controllers)

•

TSP

: Digital point generated in Centralog station

•

TM

: Measured value (analogue input)

•

TMP

: Analogue value generated in Centralog station

•

TC

: Single / double command (logical output)

•

TVC

: Set point (analogue output)

•

DEVICE

: «DEVICE» is equivalent to RTU

•

GPT

: Generic Protocol Translator

•

RTU

: Remote Terminal Unit

•

DCS

: Digital Control System


PSM31A40397.7/72

2

RECOMMENDED CONFIGURATION

2.1

HARDWARE CONFIGURATION

2.1.1

CLG870.5-104 application host stations The CLG870.5-104 software application can be installed on the following stations: •

a Centralog 10 station,

•

a Centralog 30-50 CCC-S or CVS station

on SUN/Solaris or PC/Windows NT/XP based platforms. The installation of the CLG870.5-104 application consumes the following resources, for both types of platform: •

an Ethernet port on the QUAD board installed in the station;

•

an IBDD connection,

•

a Gateway function.

It is possible to install more than one CLG870.5-104 software application on the same station, within the limit of the resources available, given the fact that other software applications also consume these resources. For example: •

•

each EXP application (one per screen) consumes an IBDD connection, each CLOGSQL application consumes two IBDD connections and a Gateway function.

The maximum number of IBDD connections available on a station and the maximum number of Gateway functions available on a Centralog is defined in the document Centralog Capacities and Performance. 2.1.2

Expansion board for the TCP/IP link A standard station is generally equipped with two Ethernet ports. The implementation of CLG IEC-870.5-104 requires the addition of an expansion board (on condition that an expansion slot remains free in the station). The QUAD FastEthernet PCI Adapter board has been validated with the CLG IEC-870.5-104 application. This board enables 4 further Ethernet ports to be added.


PSM31A40397.8/72

The QUAD board driver is installed by SYSCLOG. The QUAD board must be located in the station before starting the full installation. The Centralog Installation and Configuration Guide describes the procedure to be followed. Installing the QUAD board after the installation of the station is more complicated as the system files must be reset by hand and the station rebooted. •

On SUN/Solaris platform : Select port qfe1. This port corresponds to file /etc/hostname.qfe1. This must contain the symbolic name IECServern. E.g. : IECServer1 The /etc/hosts file must contain the IP address corresponding to IECServern. E.g. : 199.207.36.101

IECServer1

This IP address must of course be compatible with the network to which the port is connected. •

On PC/Windows platform : The C:\WINNT\System32\drivers\etc\hosts file must contain the IP address corresponding to IECServern. E.g. : 199.207.36.101

IECServer1

This IP address must of course be compatible with the network to which the port is connected.


PSM31A40397.9/72

2.2

CONTROCAD CONFIGURATION Each slave IEC needs to be associated with a Gateway. The configuration engineer must perform the following operations: •

Declare the name(s) of the Gateway function(s) on the station hosting the slave IEC(s).

•

Declare the Gateway number(s) associated with the slave IECs.

•

Declare a one second TM output rate.

•

Declare a one second TS and VR buffer clearance time.

IMPORTANT: The CLG870.5-104 software application uses the Gateway dynamic configuration feature, which means that the declaration in CCAD of the Gateway variables used by the slave IEC is optional. However all the variables consumed must exist in the Centralog database and be defined in the data configuration file of the slave IEC (cf. phkb_Data_***_n.do in the remainder of this document).


PSM31A40397.10/72

2.3

CONFIGURING THE APPLICATION The CLG870.5-104 software application is configured by means of two configuration files located: •

•

On SUN/Solaris platform, in the directory /local/af/exe/sc on the SUN station; On PC/Windows platform, in the directory E:\P320\exe\sc on the PC.

The name of these configuration files are indexed with the Centralog identifier and the Gateway number used by the software application. In this way they cannot be confused with the configuration files of another CLG870.5-104 application installed on the same station. Their role are as follows: •

•

The system configuration file named phkb_Sys_***_n.do (*** is the identifier of the Centralog from 0 thru 3 characters, and n is the number of the Gateway) contains the following information: —

parameters of the communication layer,

—

parameters defining the choice of implementation of the IEC 870.5-104 protocol,

—

parameters used for the internal dimensioning and rates of the CLG 870.5104 application.

The data configuration file of the application named phkb_Data_***_n.do (*** is the Centralog identifier from 0 thru 3 characters, and n is the Gateway number) contains the following information: —

list of the system TSs indicating the state of the l ink,

—

list of the variable types manipulated,

—

list of variables of each type exchanged with the controlling station.

Important: Two sample configuration files are delivered with the CLG870.5-104 software application. They are located on the CCC-S respectively, in the directory /local/af/exe/sc , in case of SUN/Solaris configuration, or E:\P320\exe\sc, in case of PC/Windows configuration, and are named phkb_Sys_1_exemple.do and phkb_Data_1_exemple.do


PSM31A40397.11/72

Syntax of configuration files: Any line starting with # is a comment. E.g.

#this line is a comment

A parameter is declared as follows: =

E.g.

COUNTER_MODE=4

Most of the parameters have a default value: when a parameter is absent, its default value is used. In the remainder of this document, the default values are underlined.


PSM31A40397.12/72

2.3.1

Definition of the System configuration file: phkb_Sys_***_ n .do

2.3.1.1

Parameters defining the choice of implementation of the IEC 870.5-104 Protocol The line BASE_PERIOD= gives the value in seconds of the transmission period of variables belonging to ASDUs containing non-timetagged variables (non-timetagged TS and TM variables). The default value is 10. E.g.

BASE_PERIOD=5

The line DELTA_MODE= indicates whether the variables are transmitted systematically or in delta mode. The possible choices are: . YES: after expiry of the period of spontaneous cyclical transmissions

(BASE_PERIOD parameter), only the variables that have changed since the last transmission are sent to the controlling station. A TM has changed if its validity has changed or if its value has changed outside its Deadband. A TS has changed if its value or its validity has changed. This mode economizes the bandwidth of the link but requires a reliable line. . NO: after expiry of the period of spontaneous cyclical transmissions

(BASE_PERIOD parameter), all the variables are sent to the controlling station The default value is YES. E.g.

DELTA_MODE=YES

The line COUNTER_MODE= indicates the counter management mode. In mode A, the counter values are fixed and transmitted cyclically>. In mode C, the counter values are fixed and transmitted on instruction from the controlling station. This parameter is optional; The default value is C. E.g.

COUNTER_MODE=A

The line COUNTER_PERIOD = gives the spontaneous transmission period of the counters in mode A in number of BASE_PERIODs. This parameter is optional; it is only used if mode A is selected previously. The default value is 10. E.g.

COUNTER_PERIOD=12


PSM31A40397.13/72

The line GI_WITH_PAQ_TS= indicates whether or not the ASDU M_PS_NA_1 is used to answer to the General Interrogation message originating from the controlling station. (See PID). The possible choices are: . YES: each group of 16 TSs with consecutive addresses is sent to the controlling

station via a TS packet. TSs with addresses that are not contiguous with those of 15 other TSs are sent to the controlling station via the ASDU of the nontimetagged TSs (M_SP_NA_1). . NO: On request for a GI, the TSs are sent to the controlling station via the ASDU

of the non-timetagged TSs (M_SP_NA_1). It is advisable to set this option to NO. In fact the TS packet ASDU contains only one validity bit for a group of 16 TSs with consecutive addresses: consequently TS packets can only be used if the TSs in a single group are valid or invalid at the same time (e.g. they are located on the same acquisition board). This kind of configuration is very difficult to achieve and to maintain; consequently you are strongly advised not to use TS packets. The default value is YES. E.g.

GI_WITH_PAQ_TS=NO

The line USE_M_EI= indicates whether or not the ASDU M_EI_NA_1 is used to tell the controlling station that the CLG870.5-104 software application has terminated its initialization (see PID). The possible choices are: . YES: the M_EI message is used (at the end of startup or after a request to reset

the controlling station) . NO: the M_EI message is not used. In this case the controlling station considers

that the CLG870.5-104 software is ready as soon as the connection sequence is terminated. It is advisable to set this option to NO unless the controlling station needs to utilize the message M_EI. In effect, since this message complicates and lengthens the initialization phase it should only be used if it is indispensable for the controlling station. The default value is YES. E.g.

USE_M_EI=NO

The line INVALID_TIMETAG_DELAY= indicates the maximum delay after which a state change timetag is invalidated: during the transmission to the «controlling station» of a changement of state TS, the software calcule the time écoulé depuis the changement of state. If this is greater than the invalidation delay, the state change timetag is invalidated. The possible choices are: . 0: the timetag of the event is not invalidated even if it is very old,


PSM31A40397.14/72

. Numerical value: value of the invalidation delay in seconds.

The default value is 0. E.g. (delay of 30 minutes):

INVALID_TIMETAG_DELAY=1800

Important: Event timetags are always invalid if the Centralog fails to receive the external time signal correctly.

The line MAX_SELECT_TIME= indicates the maximum selection time of a Select Before Operate type command in seconds. If the execution request of the command arrives after the expiry of this timeout it is rejected. An integer value greater than 0 is expected. The default value is 60 (seconds). E.g.

MAX_SELECT_TIME=120

The line REMOTE_CLOCK_SYNC= indicates whether or not the CLG870.5-104 software application updates the Centralog time on the basis of the message "Clock synchronization (ASDU C_CS_NA_1)" originating from the controlling station. The possible choices are: . YES: the CLG870.5-104 software application updates the Centralog time. This

choice can only be effective if the two systems are synchronized by the same time signal. . NO: the CLG870.5-104 software application ignores time update messages.

The default value is NO. E.g.

REMOTE_CLOCK_SYNC=NO

The line CLOCK_TRANSMISSION_DELAY= indicates the maximum time allowed for transmission of the time sync message from the controlling station to the CIS. This delay is expressed in seconds. The parameter is not used if the CLG870.5-104 application does not synchronize the Centralog time on the basis of data received from the controlling station. The default value is 5 (seconds). E.g.

CLOCK_TRANSMISSION_DELAY=3

The lines OCF000,OCF001,OCF010,...,OCF111= are used to configure the output states of a dual TS as a function of the value of the single Open, Close and Fault TSs that are used in its composition. The possible values are:


PSM31A40397.15/72

. 00: maneuvering or malfunctioning, according to the controlling station, . 01: open or closed, according to the controlling station, . 10: closed or open, according to the controlling station, . 11: in malfunction, . NIL: neutral state. In this case the dual TS keeps its previous value. No new state

change is generated. The table below shows the default values used depending on the value of the single TSs that compose a dual TS: Value of the TS Open

Value of the TS Close

Value of the TS Fault

0

0

0

OCF000=NIL

0

0

1

OCF001=11

0

1

0

OCF010=10

0

1

1

OCF011=11

1

0

0

OCF100=01

1

0

1

OCF101=11

1

1

0

OCF110=NIL

1

1

1

OCF111=11

Key word of the file

E.g. OCF000=00 OCF001=11 OCF010=10 OCF011=11 OCF100=01 OCF101=11 OCF110=NIL OCF111=11

Important: The document "Centralog Gateway Dual TS Specification" describes how dual TS are produced


PSM31A40397.16/72

2.3.1.2

Parameters determining the internal dimensions and rates of the CLG 870.5-104 Application The line GPT_PERIOD= indicates the period of activation in milliseconds of the thread managing the transmission and acquisition of data in IEC 870.5-104 format. The shorter this period, the faster the polling of messages waiting in the communication layer; on the other hand, the shorter the period, the higher the consumption of the CPU by the CLG870.5-104 application. An integer value is expected. You are advised to select a value between 250ms (default value) and 500ms. E.g.

GPT_PERIOD=250

The line TS_LINK_PERIOD= indicates the time, in seconds, necessary to detect a break. The parameter is used to monitor the link between the Centralog and the controlling station. An integer value is expected. The default value is 10 seconds. E.g.

TS_LINK_PERIOD=60

The line LONG_TIME_FAULT_DETECTION= indicates the time, in seconds, before detection of a long break. When a long outage is detected the CLG870.5-104 software triggers a procedure to monitor the events awaiting extraction in the file in order to delete those that are too old. (This surveillance can be disabled or enabled via the option CYCLIC_QUEUE_CONTROL). An integer value is expected. The default value is 1800 seconds. E.g.

LONG_TIME_FAULT_DETECTION=600

The line QUEUE_SIZE= is used to dimension the chronological queue of the CLG870.5-104 application. This queue fills up most during a general check. When TS packets are not used it is necessary to allow at least one post per TS configured. When TS packets are used allow at least one p ost for every 16 TSs. An integer value is expected. The default value is 1000. E.g. (configuration with 2,000 TSs plus a 50% reserve)

QUEUE_SIZE=3000

The line EVENT_WAITING_TIME= indicates the time, in seconds, that events are kept in the queue in order to ensure their chronology. An integer value greater than or equal to 0 is expected. The default value is 2 (seconds). E.g.

EVENT_WAITING_TIME=2


PSM31A40397.17/72

The line CYCLIC_QUEUE_CONTROL= indicates whether or not the chronological queue of the CLG870.5-104 software application must be scrutinized in the event of a long break so that the oldest events can be deleted from the queue. This option is useful when the Centralog is connected to the controlling station by two independent links. But the controlling station uses only one line at a time to execute the exchanges: the option is used on switchover from one link to the other to prevent the controlling station recovering all the events that have accumulated in the application queue since the previous switchover. The possible choices are: . YES: cyclical queue control is enabled: in the event of a long break, the timetags

of the events waiting in the queue are checked every 30 seconds and outdated events are deleted. . NO: cyclical queue control is not enabled: in the event of a long break the queue

is not scrutinized. The default value is NO. E.g.

CYCLIC_QUEUE_CONTROL=YES

The line MAX_TIME_EVT_IN_QUEUE= indicates the maximum time that an event can remain in the queue awaiting extraction in the event of a long break. This parameter is only used if the CYCLIC_QUEUE_CONTROL option is enabled. The default value is 180 (seconds). E.g.

MAX_TIME_EVT_IN_QUEUE=60

The line TIME_CONTROL_COMMAND= indicates the maximum delay between the date included in a command message (TC or TVC) and the actual system time. The command is rejected (negative ACTCON) if the delay is overcome. The default value is 90 (seconds). E.g.

TIME_CONTROL_COMMAND=60

The line BUF_CMD_SIZE= indicates the maximum number of events that can be inserted in the mailbox of the communication messages from the interface thread protocol to the interface GTW thread. This mailbox is also used to store data transmitted in reverse direction. An integer value is expected. The default value is 200. E.g.

BUF_CMD_SIZE=400

The line TRACE_MODE= indicates whether or not the CLG870.5-104 software application is in trace mode or in normal mode. The possible choices are:


PSM31A40397.18/72

. YES: trace mode is actived. This means that messages designed to facilitate

debugging are displayed and that the CLG870.5-104 application can be polled by means of scenario files in order to examine the content of the local database or the chronological queue. The utilization of these scenario files is described in the DCP. . NO: trace mode is not actived; the software application is running in normal mode.


TRACE_MODE=NO

The line TRACE_COM= indicates whether or not the software traces the frames exchanged on the link . The possible choices are: . YES: trace mode is active. Communication trace messages are recorded

simultaneously in two files: - The file piko_TraceCom _n.do is placed in the /tmp directory in UNIX and in

C:/temp in NT. This file is used to save the frames exchanged on the communication level (n is the number of the gateway associated to the CLG 870.5 software application). Important: In UNIX the command tail -f /piko_TraceCom_n.do is used to monitor the frames exchanged by the IEC function. . NO: no communication message is traced.


TRACE_COM=NO

The line P1= indicates the timeout for establishment of the connection; it corresponds to parameter T0 of the IEC870.5-104 standard. Its value must be between 1 and 255 seconds. The default value is 30 (seconds). E.g.

P1=30

The line P2= indicates the timeout of send or test APDUs; it corresponds to parameter T1 of the IEC870.5-104 standard. Its value must be between 1 and 255 seconds. The default value is 15 (seconds). P2 must be smaller than P4 and greater than P3. E.g.

P2=15


PSM31A40397.19/72

The line P3= indicates the acknowledgement timeout in the case of absent data messages; it corresponds to parameter T2 of the IEC870.5-104 standard. Its value must be between 1 and 255 seconds. The default value is 10 (seconds). P3 must be smaller than P2. E.g.

P3=10

The line P4= indicates the timeout for sending test frames in case of a long idle state; it corresponds to parameter T3 of the IEC870.5-104 standard. Its value must be between 1 and 255 seconds. The default value is 30 (seconds). P4 must be greater than P2. E.g.

P4=30

The line P5= indicates the maximum difference receive sequence number to send state variable; it corresponds to parameter K of the IEC870.5-104 standard. Its value must be between 1 and 32767 APDUs. The default value is 12 (APDUs). E.g.

P5=12

The line P6= indicates the latest acknowledge after receiving w I format APDUs; it corresponds to parameter W of the IEC870.5-104 standard. Its value must be between 1 and 32767 APDUs. The default value is 8 (APDUs). (recommendation: w should not exceed 2/3 of k). E.g.

P6=8

Important notice: The parameters T0, T1, T2, T3, K and W must be configured at the same value in the master and in the slave station.


PSM31A40397.20/72

2.3.1.3

Parameters concerning bi-directional transfers, master/Centralog redundancy and command flow management The line BI_DIRECTIONAL_TRANSFER= indicates whether bidirectional transfer mode must be activated or not. In this mode the CLG870.5-104 software transmits a general check on initialization to enable reception of TSs and TMs from the controlling station. This parameter is optional; its default value is NO. E.g.

BI_DIRECTIONAL_TRANSFER=YES

The line REVERSE_GI_PERIOD= indicates the period of activation in seconds of asking GI to the remote LRU(s) of the controlling station. An integer value is expected. The default value is 300 (seconds). E.g.

REVERSE_GI_PERIOD=300

The line REVERSE_TEST_PERIOD= indicates the period of activation in seconds of making TEST check of the remote LRU(s) of the controlling station. An integer value is expected. The default value is 0 (second). E.g.

REVERSE_TEST_PERIOD=10

The line DCS_TYPE= indicates whether or not the transfer of TSs and TMs in bidirectional mode is cyclical or event-related. This parameter is optional; its default value is EVENT. E.g.

DCS_TYPE=EVENT

The line CLG_TYPE= indicates the type of Centralog used to manage the TVC_CMD and the TM_CMD in the supervision of the Centralog transmitting commands to the cell controllers. NORMAL: this value indicates a Centralog with xxxServer1 configured in the hosts file on the device. The TVC_CMD is sent with the value 2. The TM_CMD

must equal 2 for the commands to be sent to the cell controllers. BACKUP: this value indicates a Centralog with xxxServer2 configured in the hosts file on the device. The TVC_CMD is sent with the value 4. The TM_CMD

must equal 4 for the commands to be sent to the cell controllers. LOCAL: this value indicates a Centralog that it has no IEC104 link. The TVC_CMD

and the commands are not sent. STANDALONE: this value indicates the Centralog that it has an IEC104 link with a

non-redundant DCS. The TVC_CMD and the commands are not sent.


PSM31A40397.21/72

The default value is STANDALONE. This value is applied only if DCS_TYPE_REDUNDANCY is set to PARALLELE. E.g.

CLG_TYPE=STANDALONE

The line CMD_PERIOD= indicates the TVC_CMD transmission period. This is the minimum value configured by default. This value can be increased at the cost of the detection of loss of communication between the CENTRALOG and the cell controllers. If the value is set to 0: the TVC_CMD is not sent. The value is set to 1 at the cost of the bandwith of transmissions to the cell controllers. This means that the TVC_CMD will be transmitted every 5 transmissions. A value of 2 means transmission of the TVC_CMD every 10 command transmissions to the cell controllers and detection of loss of communication between the CENTRALOG transmitting the commands and the cell controllers every 4 seconds. If the value is greater than 2, the command transmission bandwith will be improved, but loss of communication between the cell controllers and the CENTRALOG transmitting the commands will only be detected at intervals equal to twice the transmission period. E.g. Transmission at 5 seconds, transmission of the TVC_CMD every 25 command transmissions but detection of loss of communication every 10 seconds. The default value is 0. This value is applied only if DCS_TYPE_REDUNDANCY is set to PARALLELE. E.g.

CMD_PERIOD=10

The line DCS_TYPE_REDUNDANCY= indicates the operating mode of DCS transmissions on the link IEC104. By default the DCS is considered as non-redundant ( NO_REDONDANT). NO_REDONDANT: DCS is non-redundant or transmits its variables on a single

Ethernet link even if 2 Centralogs are connected. In this case, the TVC_CMD and TM_CMD configurations on the Centralogs can be ignored. PARALLELE: DCS transmitting in parallel on both the Ethernet links;

consequently, an identical command can be sent by the 2 Centralogs to the cell controllers. To avoid transmitting the same command in parallel to the cell controllers, the TVC_CMDs and TM_CMDs must be configured and the Centralog type (CLG_TYPE) must be set correctly on each CENTRALOG.


PSM31A40397.22/72

ANARCHIQUE: DCS transmitting anarchically on both the Ethernet links. This case

is allowed for but is processed like NO_REDUNDANT mode. It is therefore unnecessary to configure the TVC_CMDs and TM_CMDs. In this case, the transmissions executed on the "second" link are lost. E.g.

DCS_TYPE_REDUNDANCY=NO_REDONDANT

The line INIT_TIME= indicates the time during which TC/TVC commands are blocked by the software after the opening of the session. This parameter is optional; its default value is 30 (seconds). E.g.

INIT_TIME=30

The line USED_MANAGED_COMMAND= indicates whether or not command flow management is active. Flow management enables the number of TCs and TVCs sent to cell controllers to be limited in order to avoid loss of command in case of temporary overload. This parameter is optional; its default value is NO. E.g.

USED_MANAGED_COMMAND=YES

The line SIZE_FIFO_GTW= indicates the size in terms of the number of TC/TVCs in the queue of commands to the cell controllers. This This parameter is only used if flow management is active. Its default value is 5. E.g.

SIZE_FIFO_GTW=2

The line COMMAND_PER_CYCLE= indicates the maximum number of TC/TVCs transmitted from the gateway to the cell controllers per 200 ms period; this period corresponds to the cell controller command application cycle. This parameter is only used if flow management is active. Its default value is 1. E.g.

COMMAND_PER_CYCLE=1

The line CONSUMER_NB= indicates the number of TC/TVC command consumers, which is the number of cell controllers. This parameter is only used if flow management is active. Its default value is 1. E.g.

CONSUMER_NB=5

The line MASTER_REDUNDANCY= indicates whether or not the gateway processes multi-master connections like master redundancy. In this case, several masters can establish a TCP/IP connection but variables are transferred only with the last master to have sent a STARTDT. Each new STARTDT closes the previously opened variable transfer session and opens a new session. This parameter is optional; its default value is NO.


PSM31A40397.23/72

E.g.

MASTER_REDUNDANCY=YES

The line WAIT_FOR_GI= indicates the mode of startup of the variable transfer sessions: : After a STARTDT the transfer transfer can start without without waiting for a general NEVER check. FIRST_STARTDT: The gateway awaits a general check after the first

STARTDT following the software initialization. Subsequent STARTDTs are considered as switchovers from dual/redundant masters and do not require a general check before transferring events. ALWAYS: The gateway always waits for a general check after a STARTDT

before transferring events. This parameter is optional; its default value is ALWAYS. E.g.

WAIT_FOR_GI=NEVER


PSM31A40397.24/72

2.3.1.4

Redundancy and flow management: regular regular configurations

All combinations of parameters parameters are possible; the paragraphs paragraphs below show a few cases of regular configurations of the Gateway IEC 870 104 depending on the type of DCS connected. DCS in event-related write operating mode (like the P320): DCS_TYPE = EVENT INIT_TIME=0 USED_MANAGED_COMMAND USED_MANAGED_COMMAN D = NO SIZE_FIFO_GTW=0 COMMAND_PER_CYCLE=0 CONSUMER_NB=0 CLG_TYPE= STANDALONE CMD_PERIOD=0 DCS_REDUNDANCY = NO_REDUNDANT No TS_INIT No TS_MANAGED_COMMAND No TVC_CMD of TM_CMD No PROCESS_VAR or PROCESS_VAR=NO on the TC and TVC No DEADBAND on the TVC DCS in periodic write operating mode and in parallel to both Gateways: DCS_TYPE = CYCLIC INIT_TIME = (SIZE_FIFO_TGW*0,2 s + basic value ) in seconds USED_MANAGED_COMMAND USED_MANAGED_COMMAN D = YES SIZE_FIFO_GTW = somme of the TS_IA and TM_IA (PROCESS_VAR = YES) + talon (=1) COMMAND_PER_CYCLE=1 CONSUMER_NB=1 CLG_TYPE=NORMAL or BACKUP or LOCAL CMD_PERIOD=2 DCS_REDUNDANCY = PARALLELE TS_INIT TS_MANAGED_COMMAND TVC_CMD TM_CMD PROCESS_VAR=YES for process states (TC => TS_IA and TVC => TM_IA), PROCESS_VAR=NO for all pure commands ( TC and TVC) DEADBAND on the TVC where PROCESS_VAR=YES Non-redundant DCS in periodic write operating mode: DCS_TYPE = CYCLIC INIT_TIME = (SIZE_FIFO_TGW*0,2 s + basic value ) in seconds


PSM31A40397.25/72

USED_MANAGED_COMMAND = YES SIZE_FIFO_GTW = sum of TS_IA and TM_IA (PROCESS_VAR = YES) + stub (=1) COMMAND_PER_CYCLE=1 CONSUMER_NB=1 CLG_TYPE=STANDALONE CMD_PERIOD=0 DCS_REDUNDANCY = NO_REDUNDANT TS_INIT TS_MANAGED_COMMAND No TVC_CMD of TM_CMD PROCESS_VAR=YES for process states (TC => TS_IA and TVC => TM_IA), PROCESS_VAR=NO for all pure commands ( TC and TVC) DEADBAND on the TVC where PROCESS_VAR=YES

2.3.1.5

LIMITS OF THE SYSTEM

The system cannot manage cases of chattering values: chattering appears unlikely with operator commands originating from the DCS, but may occur with process states if a sensor is badly regulated and/or if the DEADBAND of a TM_IA is badly configured. For information, the following has been observed: a "commands" FIFO dimensioned at 5 messages (minimum value by default), overflows with 2 variables chattering at 200 ms. The overflow is limited to the "Commands" FIFO and does not affect the Centralog or the S8000E. On the Centralog, when the IEC104 function traces are scrolled in the CCC message window, only a little CPU time remains available to execute consultation actions or actions on the views (opening a shell takes a lot of time). The trace modes (configured in the system file of the IEC104 software) have been removed in order to improve this behavior, and these trace modes ( TRACE_COM and TRACE_MODE at NO) must be disabled in the site configurations.


PSM31A40397.26/72

2.3.1.6

Summary of system configuration file parameters Label

Description

BASE_PERIOD DELTA_MODE COUNTER_MODE COUNTER_PERIOD GI_WITH_PAQ_TS USE_M_EI INVALID_TIMETAG_DELAY MAX_SELECT_TIME REMOTE_CLOCK_SYNC CLOCK_TRANSMISSION_DELAY OFC000 … OFC111

Period of cyclical TS and TM transmissions Transmission on value / state change Counter management mode (IEC parameter) Period of cyclical counter transmissions (in mode A only) TS grouping in response to general checks End of initialization message State change timetag invalidation timeout Maximum TC selection time Time sync by network Maximum time sync message transmission time Dual TS coding matrix

GPT_PERIOD TS_LINK_PERIOD LONG_TIME_FAULT_DETECTION QUEUE_SIZE EVENT_WAITING_TIME CYCLIC_QUEUE_CONTROL MAX_TIME_EVT_IN_QUEUE TIME_CONTROL_COMMAND BUF_CMD_SIZE TRACE_MODE TRACE_COM p1 P2 P3 P4 P5 P6

Network task activation period Network outage detection time-out Long outage time-out detection (overflow management) Size of the event file Chronological event reclassification time Long outage monitoring Maximum age of an event in the queue Maximum age of a command (Tcand TVC) before being executed Size of the internal command file Activation of trace mode Save trace messages in files Connection time-out (IEC parameter: t0) Response time-out (IEC parameter: t1) Maximum acknowledgement time (IEC parameter: t2) Maximum network silence time (IEC parameter: t3) Maximum value of sequence number offset (IEC parameter) Maximum anticipation rate for ASDU acknowledgement (IEC parameter)

BI_DIRECTIONAL_TRANSFER REVERSE_GI_PERIOD REVERSE_TEST_PERIOD DCS_TYPE CLG_TYPE CMD_PERIOD DCS_TYPE_REDUNDANCY INIT_TIME USED_MANAGED_COMMAND SIZE_FIFO_GTW COMMAND_PER_CYCLE CONSUMER_NB MASTER_REDUNDANCY WAIT_FOR_GI

In bi-directional mode: reception of TS and TM and transmission of GI In bi-directional mode: period of asking GI to the remote LRU In bi-directional mode: period of making TEST check of the remote LRU In bi-directional mode: reception of TS / TM in cyclical or on event Type of Centralog TVC_CMD transmission period in case of CLG redundancy Operating mode of DCS transmissions TC/TVC command blocking timeout after initialization Management of the command flow to the controllers Size of the command FIFO to the controllers Number of commands transmitted per 200 ms cycle Number of consumers of TC /TVC commands Redundant master takeover Standby for general check (GI) after a STARTDT


PSM31A40397.27/72

2.3.2

Definition of the application Data configuration file: phkb_Data_***_n .do The CLG870.5-104 application can now be configured with several devices (up to 32). The identifier of each device is the common ASDU for this device. The application data configuration file is structured in 3 distinct blocks: 1. At the head of the file is located the definition of the system TSs used to provide the Centralog operator with information on the state of the link. 2. The following block describes the variable types (IEC objects) manipulated. This block is delimited by the key words: DESCRIPTION_DEVICE= or DESCRIPTION_REMOTE_DEVICE=

IEC objects transmitted by the Centralog IEC objects received by the Centralog END_DEVICE DESCRIPTION_DEVICE is used to declare data transmitted in standard direction to the controlling station, while DESCRIPTION_REMOTE_DEVICE is used to declare

data transmitted in reverse direction from the controlling station. 3. The last block describes the lists of variables exchanged, classed by type. Each variable is defined with its parameters: •

•

•

Centralog key of the variable, Identifier of the variable recognized by the controlling station, used during the exchanges, Other parameters dependent on the variable type.

This block is delimited by the following key words: OBJECT_DEVICE= List of the variables of the IEC i object List of the variables of the IEC j object .... List of the variables of the IEC k object END_OBJECT_DEVICE

2.3.2.1

Definition of the Line Number used by the Master: LINE= defines the number of the line used by the master


PSM31A40397.28/72

2.3.2.2

Definition of System Variables: - The line TS_CONDUITE=

defines the key of the TS used to authorize or forbid all the commands originating from the controlling station: when the TS is valid and equal to 1 the controlling station is authorized to control the Centralog; when it is equal to 0 or is invalid, the controlling station cannot control the Centralog. This parameter is optional. When no control TS is defined, commands originating from the controlling station are authorized. The Application is responsible for setting the control TS. If the controlling station has to receive this TS, it must belong to the list of transmitted variables TSs (timetagged or not) to the controlling station. E.g.

TS_CONDUITE=PRO-TSP01

- The line TS_LIAISON_G1= defines the key of the TS

indicating whether or not the CLG870.5-104 software has established the link with the controlling station. The TS is valid and equal to 1 when the link is established, and equal to 0 otherwise. The reset to 0 period of this TS depends on the parameter TS_LINK_PERIOD defined in the system configuration file: the TS is set to 0 if no message has been received from the controlling station during a period that is at least equal to this period of time. This TS must be defined. E.g.

TS_LIAISON_G1=PRO-TSP02

- The line TS_LIAISON_CLG= defines the key of the TS that indicates the state of

the link with the real time database of the CIS. The TS is valid and equal to 1 when the CLG870.5-104 application is connected to the CIS, and equal to 0 otherwise. This TS must be defined. If the controlling station has to receive this TS, it must belong to the list of transmitted variables TSs (timetagged or not) to the controlling station. E.g.


TS_LIAISON_CLG=PRO-TSP03

PSM31A40397.29/72

- The line TS_SATURATION= defines the key of the TS that indicates whether one of the chronological queues is full or none. When one of the queues is full the TS is valid and equal to 1, otherwise it is equal to 0. This parameter can also be defined in the first device section, instead of in this first block. Important: This TS must be defined, here or in the first device section. E.g.

TS_SATURATION=PRO-TSP04

- The line TS_INIT= defines the key of the TS indicating the state of the

Gateway initialization phase. The TS is valid and equal to 1 at startup, at the establishment of communication with the DCS and following the loss of communication with the DCS. It is equal to 0 when the initialization timeout INIT_TIME is attained and steady state is established. This parameter is optional. If the controlling station receives it, the list of TSs transmitted to the controlling station must be defined. It must be configured with a CYCLIC type DCS if the INIT_TIME value is not null. In other cases, it serves no purpose: if the DCS is EVENT type, it remains at 0. E.g.

TS_INIT=PRO-TSP04

- The line TS_MANAGED_COMMAND= defines the key of the TS indicating the state of the

overflow TS regarding process command and state transmission on the S8000E network. The TS is valid and equal to 1 when the process command and state FIFO is full. It is equal to 0 on initialization and when the FIFO overflow is cleared. This variable is not reset to zero until at least one second after the FIFO is cleared. This parameter is optional. If the controlling station receives it, the list of TSs transmitted to the controlling station must be defined. It must be configured if the command flow is managed as it indicates the state of overflow of the process command and state management FIFO. If flow management is not configured (USED_MANAGED_COMMAND=NO), this variable has no purpose and remains at 0. E.g.

TS_MANAGED_COMMAND=PRO-TSP05

- The line TVC_CMD= defines the key of the TVC

used by the cell controller to determines the TM command TM_CMD in accordance with the parameter CLG_TYPE. Its value authorizes the Centralog to send the process commands or states to the cell controllers. Each Centralog type CLG_TYPE=[NORMAL or BACKUP] writes its own value in the TVC_CMD: CLG_TYPE=NORMAL => TVC_CMD=2 or CLG_TYPE=BACKUP => TVC_CMD=4.


PSM31A40397.30/72

In the initialization phase, the TVC_CMD is equal to 0. The TVC_CMD is sent if the TM_CMD=0 (this is in fact a request to transmit commands) or if the TM_CMD=TVC_CMD (to maintain the link between the Centralog and the cell controllers). The TVC_CMD is reset to 0 if the Centralog that transmits the commands has just lost the link with the DCS ( TS_LINK switches from 1 to 0). The transmission period of the TVC_CMD is CMD_PERIOD when there is no change in the state of the link with the DCS. This parameter is optional. It serves no purpose with an EVENT type DCS. E.g.

TS_MANAGED_COMMAND=PRO-TVC_CMD_06

- The line TM_CMD= defines the key of the TM

authorizing the transmission of the commands in accordance with the parameter CLG_TYPE. TM_CMD=0:

Initialization phase of the software Loss of communication between the cell controllers and the Centralog transmitting commands over the S8000E; value returned by the cell controllers following its reset to 0. Loss of communication between the DCS and the Centralog transmitting the commands; return by the cell controllers of the TVC_CMD equal to 0. TM_CMD=2:

Centralog type CLG_TYPE=NORMAL transmits the commands to the cell controllers. The Centralog type CLG_TYPE=BACKUP runs in parallel but the commands that it receives are not transmitted to the Centralog. TM_CMD=4:

Centralog type CLG_TYPE=BACKUP transmits the commands to the cell controllers. The Centralog type CLG_TYPE=NORMAL runs in parallel but the commands that it receives are not transmitted to the Centralog. The TM_CMD is not managed if the DCS is not redundant (DCS_TYPE_REDUNDANCY different from PARALLELE) or if the Centralog is standalone type ( CLG_TYPE=STANDALONE).


PSM31A40397.31/72

This parameter is optional. It serves no purpose with an EVENT type DCS E.g. 2.3.2.3

TM_CMD=PRO-TM_07

Definition of Variable Types (IEC Objects) The header of the definition block is beginning by: The line DESCRIPTION_DEVICE= , to declare data transmitted in standard direction to the controlling station, or the line DESCRIPTION_REMOTE_DEVICE= , to declare data transmitted in reverse direction from the controlling station. This identifier of device must be between 1 and 65535 (16 bits format). This line must be defined. As several devices can be defined for the IEC 870.5-104 protocol, the common ASDU address is defined for each device by the . The line END_DEVICE terminates this IEC object definition block. The parameters defined within the block are as follows: For the first device only, the parameter TS_SATURATION= could be placed here, instead of in the previous block. It defines the key of the TS that indicates whether one of the chronological queues is full or none. When one of the queues is full the TS is valid and equal to 1, otherwise it is equal to 0. This parameter could also be defined in this section because other protocols that use the same configuration files need to define several devices with one chronological queue and an associated overflow TS. Important: This TS must be defined, in the previous section or here, for the first device only. If a controlling station has to receive this TS, it must belong to the list of TSs transmitted to the controlling station. E.g.

TS_SATURATION=PRO-TSP04

Then, the declaration of the two lists of variables (transmitted or received) is done independantly of the type of concerned device (local or remote). The list of variable types transmitted by the IEC 870.5-104 Gateway (or controlling station) is declared as follows: OBJECT_DESCRIPTION_TRANSMIT > TYPE= BLOCK= POINTS=, OBJECT= , OBJECT=
....

> TYPE= BLOCK= POINTS=, OBJECT=
END_OBJECT_DESCRIPTION


PSM31A40397.32/72

It is possible to declare up to 64 objects of the same type: thus enabling the definition of several blocks of variables with contiguous addresses. The parameters of an IEC object are: . OBJECT=: indicates the object identifier. Referred to in the variable

definition block in order to define the full list of object variables, . TYPE= : defines the object variable type. Each of the possible types

corresponds to an IEC 870.5-104 standard ASDU (see PID) The possible types are: - SINGLE_POINT: non-timetagged TS type corresponding to the standard

ASDU 0x1 (M_SP_NA_1), - SINGLE_POINT_WITH_TIME: timetagged TS type corresponding to the

standard ASDU 0x1e (M_SP_TB_1), - DOUBLE_POINT: non-timetagged dual TS type corresponding to the standard

ASDU 0x3 (M_DP_NA_1) , - DOUBLE_POINT_WITH_TIME: timetagged dual TS type corresponding to the

standard ASDU 0x1f (M_DP_TB_1), - MEASURED_NORMALIZED_VALUE: normalized TM type corresponding to the

standard ASDU 0x9 (M_ME_NA_1). The value of this type of TM transmitted to the controlling station after application of the conversion formula must be between [-1, 1]. This formula is used to convert the Centralog measurement of the TM into a normalized measurement recognized by the controlling station: it is equal to Mdis=(MClog-Offset)/Coeff,

- MEASURED_NORMALIZED_VALUE_WITH_TIME: standardized TM type

corresponding to the standard ASDU 0x22 (M_ME_TD_1). The value of this type of TM transmitted to the controlling station after application of the conversion formula must be between [-1, 1]. This formula is used to convert the Centralog measurement of the TM into a normalized measurement recognized by the controlling station: it is equal to Mdis=(MClog-Offset)/Coeff,

- MEASURED_SCALED_VALUE: scaled TM type corresponding to the standard

ASDU 0xB (M_ME_NB_1). The value of this type of TM transmitted to the controlling station after application of the conversion formula is between [-32768,32767]

(The conversion formula is the same as that applied to a normalized TM) Important: The VR values of MEASURED_INTEGER_VALUE type that are defined are transmitted by the slave IEC via the standard ASDU M_ME_NB_1 .


PSM31A40397.33/72

- MEASURED_SCALED_VALUE_WITH_TIME: adjusted TM type corresponding

to the standard ASDU 0x23 (M_ME_TE_1). The value of this type of TM transmitted to the controlling station after application of the conversion formula is between [-32768,32767] (The conversion formula is the same as that applied to a normalized TM) - MEASURED_FLOAT_VALUE: short floating point TM type corresponding to the

standard ASDU 0xD (M_ME_NC_1). The value of this type of T M, transmitted to the controlling station after application of the conversion formula, is a short floating point number that conforms to standard IEEE STD 754. This formula is used to convert the Centralog measurement of the TM into a measurement understood by the controlling station: it is equal to Mdis=(MClog-Offset)/Coeff,

- MEASURED_FLOAT_VALUE_WITH_TIME: short floating point TM type

corresponding to the standard ASDU 0x24 (M_ME_TF_1). The value of this type of TM, transmitted to the controlling station after application of the conversion formula, is a short floating point number that conforms to standard IEEE STD 754. This formula is used to convert the Centralog measurement of the TM into a measurement understood by the controlling station: it is equal to Mdis=(MClog-Offset)/Coeff,

- STEP_POSITION: TM type corresponding to the standard ASDU 0x5

(M_ST_NA_1). The value of this type of TM, transmitted to the controlling station after application of the conversion formula, must be between 0,31]. This formula is used to convert the Centralog measurement of the TM into a measurement understood by the controlling station: it is equal to Mdis=(MClog-Offset)/Coeff,

- STEP_POSITION_WITH_TIME: TM type corresponding to the standard ASDU

0x20 (M_ST_TB_1). The value of this type of TM, transmitted to the controlling station after application of the conversion formula, must be between 0,31]. This formula is used to convert the Centralog measurement of the TM into a measurement understood by the controlling station: it is equal to Mdis=(MClog-Offset)/Coeff,

- INTEGRATED_TOTAL: counter type corresponding to the standard ASDU 0xF

(M_IT_NA_1). - INTEGRATED_TOTAL_WITH_TIME: counter type corresponding to the

standard ASDU 0x25 (M_IT_TB_1). Important: it is not necessary to define the TS packet object (standard ASDU 0x14 M_PS_NA_1). In fact, if used (GI_WITH_PAQ_TS=YES), it is constructed dynamically on startup by concatenating all the objects containing TSs (ASDU M_SP_NA_1 and M_SP_TA_1) . BLOCK=: defines the base number of the object variable identifiers,


PSM31A40397.34/72

. POINTS=, : gives the limits of the object variable identifiers. The low

limit is equal to: +; the high limit is equal to: + During the definition of the list of object variables, the software application checks that each variable identifier is located within these limits. The identifier is calculated with the formula: Id=+ ( is a parameter of the variable) Example 1: The base address of the objects is equal to 0, which is the same as defining the variable identifiers directly in the lists declared subsequently. OBJECT_DESCRIPTION_TRANSMIT OBJECT=1 OBJECT=2 OBJECT=31 OBJECT=32 OBJECT=3 OBJECT=4 OBJECT=5 OBJECT=6 OBJECT=7 OBJECT=10

TYPE=SINGLE_POINT BLOCK=0 TYPE=SINGLE_POINT_WITH_TIME BLOCK=0 TYPE=DOUBLE_POINT BLOCK=0 TYPE=DOUBLE_POINT_WITH_TIME BLOCK=0 TYPE=MEASURED_NORMALIZED_VALUE BLOCK=0 TYPE=MEASURED_SCALED_VALUE BLOCK=0 TYPE=MEASURED_FLOAT_VALUE_WITH_TIME BLOCK=0 TYPE=INTEGRATED_TOTAL BLOCK=0 TYPE=INTEGRATED_TOTAL_WITH_TIME BLOCK=0 TYPE=MEASURED_INTEGER_VALUE BLOCK=0

POINTS=0, 499 POINTS=500, 799 POINTS=800, 899 POINTS=900, 999 POINTS=1000,1499 POINTS=1500,1799 POINTS=1800,1999 POINTS=2000,2099 POINTS=2100,2499 POINTS=3000,3599


Example 2: The ASDU of the non-timetagged TS is composed of 3 consecutive blocks; a single TM type is used and there are no counters: OBJECT_DESCRIPTION_TRANSMIT OBJECT=1 OBJECT=11 OBJECT=12 OBJECT=2 OBJECT=4 OBJECT=6

TYPE=SINGLE_POINT TYPE=SINGLE_POINT TYPE=SINGLE_POINT TYPE=SINGLE_POINT_WITH_TIME TYPE=MEASURED_SCALED_VALUE TYPE=MEASURED_FLOAT_VALUE

BLOCK=0 BLOCK=100 BLOCK=200 BLOCK=0 BLOCK=0 BLOCK=0

POINTS=0,29 POINTS=0,9 POINTS=0,20 POINTS=500,999 POINTS=1500,1999 POINTS=2000,2099


The list of the data types received from the controlling station is declared as follows: OBJECT_DESCRIPTION_RECEIVE OBJECT= TYPE= BLOCK= POINTS=, 1 1 > , OBJECT=
....

OBJECT= TYPE= BLOCK= POINTS=, n n


It is possible to declare up to 64 object of the same type. The parameters of an IEC object are: . OBJECT=: indicates the object identifier. . TYPE= : defines the object variable type. Each of the possible types

corresponds to an IEC 870.5-104 standard ASDU (see PID) The possible types are: - SINGLE_COMMAND: direct TC and Select Before Operate TC type

corresponding to the standard ASDU 0x2D (C_SC_NA_1), - SINGLE_COMMAND_WITH_TIME: direct TC type and Select Before Operate

TC type corresponding to the standard ASDU 0x3A (C_SC_TA_1),


PSM31A40397.35/72

- DOUBLE_COMMAND: direct TC type and Select Before Operate TC type

corresponding to the standard ASDU 0x2E (C_DC_NA_1), - DOUBLE_COMMAND_WITH_TIME: direct TC type and Select Before Operate

TC type corresponding to the standard ASDU 0x3B (C_DC_TA_1), - REGULATING_STEP_COMMAND: direct TC type and Select Before Operate TC

type corresponding to the standard ASDU 0x2F (C_RC_NA_1), - REGULATING_STEP_COMMAND_WITH_TIME: direct TC type and Select Before

Operate TC type corresponding to the standard ASDU 0x3C (C_RC_TA_1), - SET_POINT_NORMALIZED_VALUE: standardized TVC type corresponding to the

standard ASDU 0x30 (C_SE_NA_1). The value of this type of TVC received from the controlling station before application of the conversion formula is located in the interval [-1, 1]. This formula is used to convert the measurement transmitted by the controlling station into a Centralog setpoint: it is equal to MClog=(MDis-Offset)/Coeff, - SET_POINT_NORMALIZED_VALUE_WITH_TIME: standardized TVC type

corresponding to the standard ASDU 0x3D (C_SE_TA_1). The value of this type of TVC received from the controlling station before application of the conversion formula is located in the interval [-1, 1]. This formula is used to convert the measurement transmitted by the controlling station into a Centralog setpoint: it is equal to MClog=(MDis-Offset)/Coeff, - SET_POINT_SCALED_VALUE: scaled TVC type corresponding to the standard

ASDU 0x31 (C_SE_NB_1). The value of this type of TVC received from the controlling station before application of the conversion formula, is located in the interval [-32768,32767]. (The conversion formula is the same as that applied to a normalized TVC). - SET_POINT_FLOAT_VALUE: short floating TVC type corresponding to the

standard ASDU 0x32 (C_SE_NC_1). The conversion formula given above is applied to the value received from the controlling station before its transmission to the Centralog. - SET_POINT_SCALED_VALUE_WITH_TIME: adjusted TVC type corresponding

to the standard ASDU 0x3E (C_SE_TB_1). The value of this type of TVC received from the controlling station before application of the conversion formula, is located in the interval [-32768,32767]. (The conversion formula is the same as that applied to a normalized TVC). - SET_POINT_FLOAT_VALUE_WITH_TIME: short floating point TVC type

corresponding to the standard ASDU 0x3F (C_SE_TC_1). The conversion formula given above is applied to the value received from the controlling station before its transmission to the Centralog.


PSM31A40397.36/72

- SET_POINT_BIT_STRING: TVC type corresponding to the standard ASDU

0x33 (C_BO_NA_1). The conversion formula given above is applied to the value received from the controlling station before its transmission to the Centralog. Important:

The SET_POINT_BIT_STRING type TVC values that are defined are transmitted by the IEC slave via the the standard ASDU M_BO_NA_1 on the least significant 16 bits.

- PARAMETER_NORMALIZED_VALUE: standardized parameter type

corresponding to the standard ASDU 0x6E (P_ME_NA_1). The value of the parameter is related to the value of the TM sent to the controlling station - not to be configured. - PARAMETER_SCALED_VALUE: ASDU 0x6F (P_ME_NB_1) - not implemented - PARAMETER_FLOAT_VALUE: standardized parameter type corresponding to

the standard ASDU 0x70 (P_ME_NC_1). The value of the parameter is related to the value of the TM sent to the controlling station - not to be configured. Note: The deadband parameter is applicable on MDis but not on Mclog.

The received objects from a remote LRU of the controlling station (in reverse direction) are distinguished by the use of distinct object variable types (suffix _FROM_MASTER): - SINGLE_POINT_FROM_MASTER: non-timetagged TS (idem transmitted

variables), - SINGLE_POINT_WITH_TIME_FROM_MASTER: timetagged TS (idem

transmitted variables), - DOUBLE_POINT_FROM_MASTER: non-timetagged dual TS (idem transmitted

variables), - DOUBLE_POINT_WITH_TIME_FROM_MASTER: timetagged dual TS (idem

transmitted variables), - MEASURED_NORMALIZED_VALUE_FROM_MASTER: standardized TM (idem

transmitted variables), - MEASURED_NORMALIZED_VALUE_WITH_TIME_FROM_MASTER: timetagged

standardized TM (idem transmitted variables), - MEASURED_SCALED_VALUE_FROM_MASTER: adjusted TM (idem transmitted

variables), - MEASURED_SCALED_VALUE_WITH_TIME_FROM_MASTER: timetagged

adjusted TM (idem transmitted variables) ,


PSM31A40397.37/72

- MEASURED_FLOAT_VALUE_FROM_MASTER: short floating point TM (idem

transmitted variables), - MEASURED_FLOAT_VALUE_WITH_TIME_FROM_MASTER: timetagged short

floating point TM (idem transmitted variables), - STEP_POSITION_FROM_MASTER: TM corresponding to ASDU 05 (idem

transmitted variables), - STEP_POSITION_WITH_TIME_FROM_MASTER: TM corresponding to ASDU

0x20 (idem transmitted variables), . BLOCK=: defines the base number of the object variable identifiers, . POINTS=, : gives the limits of the object variable identifiers. The low

limit is equal to: +; the high limit is equal to: +, E.g. the TC object is subdivided into two in order to separate the addresses of the direct TCs from those of the Select Before Operate TCs. OBJECT_DESCRIPTION_RECEIVE # Object of the direct TCs OBJECT=61 TYPE=SINGLE_COMMAND

BLOCK=0 POINTS=3000,3499

# Object of the Select Before Operate TCs OBJECT=62 TYPE=SINGLE_COMMAND


# Object of the Select Before Operate TCs OBJECT=63 TYPE=DOUBLE_COMMAND_WITH_TIME BLOCK=0 POINTS=3600,3699 OBJECT=64 TYPE=REGULATING_STEP_COMMAND_WITH_TIME BLOCK=0 POINTS=3700,3999 OBJECT=67 TYPE=SET_POINT_NORMALIZED_VALUE BLOCK=0 POINTS=4000,4199 OBJECT=68 TYPE=SET_POINT_FLOAT_VALUE_WITH_TIME BLOCK=0 POINTS=4200,4499 OBJECT=69 TYPE=SET_POINT_SCALED_VALUE BLOCK=0 POINTS=4500,4799 OBJECT=9 TYPE=SET_POINT_BIT_STRING




PSM31A40397.38/72

2.3.2.4

Definition of the Variable Lists of Each IEC Object Important: In order to optimize the bandwidth of the link the variable identifiers of each object must be consecutive: the IEC 870.5-104 protocol is much more efficient when it transmits a group of variables with consecutive addresses in an ASDU than when it transmits variables with discontinuous addresses. The line OBJECT_DEVICE= corresponds to the header of this definition block. The identifier of the device must be the same as that defined in the previous definition block (delimited by the key words DESCRIPTION_DEVICE=< Device identifier> or DESCRIPTION_REMOTE_DEVICE= ... END_DEVICE)

The line END_OBJECT_DEVICE terminates this definition block. This block must contain the variable lists of all the objects defined in the previous block. An object variable list is delimited by the following key words: DATA_OBJECT=

psm31a40397-ee

Recommend Documents