---

Annex A

(normative)

Interpretation of mode and behaviour

Switching between the modes (Mod.stVal) should only happen as a result of an operator command to the data object Mod. Mod and Beh are always accessible by the services. The communication services for the data object Mod do not care about the status of the Beh of the LN. Possible values of Mod and Beh are given in Table A.1.

Table A.1 - Values of mode and behaviour

Table A.2 gives an overview over the definition of mode and behaviour.

In the lower lines is given the functional processing of the LNs in different behaviour states. Logical nodes should process receiving data according to their quality information:

• “Processed as valid” means that the application should react according to the quality and the behaviour of the LN.

• "Processes as invalid” means the application should react as if the quality of the data had been invalid. ,

• “Processed as blocked” means that the application should decide how to react, besides no process-related action based on the value is performed.

Table A.2 - Definition of mode and behaviour

NOTE A precondition of the use of different modes (Mod/Beh) is the processing of the quality status (q) of the receiving information.

61850-7-4 © IEC:2010(E) - 157

Annex В

(normative)

Local I Remote concept

The data object LocKey represents the status of a physical key switch and allows to taking over the control authority.

The data object Loc shows the control behaviour of the logical node.

The data object LocSta shows the switching authority at station level. If LocSta=false control, commands are allowed from remote, e.g. network control center (NCC).

The data object MltLev shall be modelled in LLNO only. It shows if more than one source of control commands is accepted at a certain level at the same time.

Example:

1. If MltLev=false, CSWI.Loc=false and CSW1.LocSta=true, only a control command with a station level originator is allowed, what means only one level has the switching authority.

2. If MltLev=true, CSWI.Loc=false and CSWI.LocSta=true, additionally to the allowed command from the station level, also commands from the bay level are allowed, which means that the station level and the bay level have the switching authority. So the final reaction on control commands regarding the different sources of the commands (specified by the originator of the control command) is defined by data objects Loc, LocSta and MltLev.

The concept is illustrated in Table B.1 and shall be applied.

Table В.1 - Relationship between Loc/Rem data objects and control authority

Annex С
(informative)

Deprecated logical node classes

C.1 General

In this annex, those logical nodes are listed that are obsolete (no longer needed because of technical progress since the publication of the first edition (2003). They will be kept in the standard for backward compatibility with namespace indication of edition 1 (IEC 61850-7-4:2003).

C.2 LN: Metering statistics Name: MSTA

The metered values are not always used directly, but as average values, minima and maxima over a given evaluation period. The reporting may be started after the end of this period.

Annex D
(informative)

Relationship between this standard and IEC 61850-5

The logical nodes listed in IEC 61850-5 define requirements; the logical nodes listed in this standard define the modelling. Some requirements of the LNs from IEC 61850-5 are modelled by LNs which are not explicitly referred to in this standard. Its functionality is provided by the services or by the communication stack. Some system support functions are too dependent on implementation to be standardized in this standard. Examples are listed in Table C.1.

Table D.1 - Relationship between IEC 61850-5 and this standard
for some miscellaneous LNs

Annex Е
(informative)

Algorithms used in logical nodes for automatic control

E.1 General

A number of logical nodes for control functions are based on the algorithms used rather than the allocation in a functional structure. This annex provides more detailed information on the functional content behind the formal logical node definitions.

The following logical nodes are described in this annex:

• FCSD - Curve shape description function

• FPID - PID regulator function

• FFIL - Filter function

• FRMP - Set-point ramping function

• FSPT - Set-point control function

E.2 Logical node FCSD (curve shape description)

The logical node is used to adapt an incoming value to a specific curve function. As an example, it can be used to adjust non-linear transmitters to the correct physical values. The curve is two-dimensional in nature, however a three-dimensional curve can be achieved by using several instances of the LN FCSD.

In Figure E.1, we can see an example of a two-dimensional curve used for shaping a flow value based on the gate position. The values entered in the table are based on statistical data obtained following a series of index tests.

FCSD.Crv.crvPtsI .xVal

FCSD.Crv.crvPts1.yVal

FCSD.Crv.crvPts2.xVal

FCSD.Crv.crvPts2.yVal

FCSD.Crv.crvPts3.xVal

FCSD.Crv.crvPts3.yVal

FCSD.Crv.crvPts4.xVal

FCSD.Crv.crvPts4.yVal

INPUT:

Gate Position

FCSD.Crv.crvPts10.xVal

FCSD.Crv.crvPtsI O.yVal

> Interpolated Water Flow FCSD.Output.mag

IEC 435/10

Figure E.1 - Example of curve based on an indexed gate position
providing water flow

E.3 Logical node FCSV (curve shape group)

The logical node is used to adapt an incoming value to a specific curve function. As an example, it can be used to adjust non-linear transmitters to the correct physical values. The

curve is two-dimensional in nature, however a three-dimensional curve can be achieved by using several instances of the FCSG LN. The logical node is similar to FCSD with the exception that they are modifiable online.

In Figure E.2, we can see an example of a three-dimensional curve used for defining a runner blade position based on two variables: net head and guide vane position. To achieve such a function, five logical nodes are required.

FCSGS.Crv.crvPls1.xVal I

FpSG4.Crv.crvPts1.xVal I

FCSG3.Crv.crvPts1.xVal I

F

IEC 436/10

CSG2.Crv.crvPts1.xVal

_c FCSG1.Crv.crvPts1.xVal

FCSG1.Crv.crvPts1.yVal

FCSG1.Crv.crvPts2.xVal

FCSG1.Crv.crvPts2.yVal

F

p FCSG1.Crv.crvPts3.yVal

CSG1.Crv.crvPts3.xVal

— p FCSG1.Crv.crvPts4.xVal

F ^F — FCSG1.Crv.crvPts4.yVal

F F —

F_^

<— p FCSG1.Crv.crvPts10.xVal

FCSG1.Crv.crvPts10.yVal

Figure E.2 - Example of curve based on an indexed guide vane position (x axis) vs. net
head (y axis) giving an interpolated runner blade position (Z axis)