1. Interpretation of logical node tables

The interpretation of the headings for the logical node tables is presented in Table 2.

Table 2 - Interpretation of logical node tables

Column heading

Description

Data object name

Name of the data object

Common data class

Common data class that defines the structure of the data object. See IEC 61850-7-3. For common data classes regarding the service tracking logical node (LTRK), see IEC 61850-7-2.

Explanation

Short explanation of the data object and how it is used.

T

Transient data objects - the status of data objects with this designation is momentary and must be logged or reported to provide evidence of their momentary state. Some T may be only valid on a modelling level. The TRANSIENT property of DATA OBJECTS only applies to BOOLEAN process data attributes (FC=ST) of that DATA OBJECTS. A transient DATA OBJECT is identical to normal DATA OBJECT, except that for the process state change from TRUE to FALSE no event may be generated for reporting and for logging.

For transient data objects, the falling edge is not reported if the transient attribute is set to true in the SCL-ICD file. It is recommended to report both states (TRUE to FALSE, and FALSE to TRUE), i.e. not to set the transient attribute in the SCL-ICD file for those DOs, and that the clients filter the transitions that are not "desired".

M/O/C

This column defines whether a data object is mandatory (M) or optional (O) or conditional (C) for an instance of a specific logical node. When a data object is marked mandatory (M), it shall be contained in the instance of the logical node. When a data object is marked optional (0), it may be contained in the instance of the logical node; the decision if the data object is contained or not is outside the scope of this standard. The entry C is an indication that a condition exists for this data object, given in a note under the LN table. The condition decides what conditional data objects get mandatory. C may have an index to handle multiple conditions.

NOTE1 Procurement specifications may require specific data objects marked optional to be provided for a particular project. The amount of optional information to be provided needs to be negotiated.

NOTE 2 The attributes for data objects that are instantiated may also be mandatory or optional based on the CDC (attribute type) definition in IEC 61850-7-3.



The LNName attribute is inherited from Logical-Node class (see IEC 61850-7-2). The LN class names are individually given in the logical node tables. The LN instance name shall be composed of the class name, the LN-Prefix and LN-lnstance-ID according to IEC 61850-7-2, Clause 22.

All data object names are listed alphabetically in Clause 6. Despite some overlapping, the data objects in the logical node classes are grouped for the convenience of the reader into the following categories:

  • Status information

Status information contains data object, which show either the status of the process or of the function allocated to the LN class. This information is produced locally and cannot be changed via communication for operational reasons unless substitution is applicable. Data objects such as “start” or “trip” are listed in this category. Most of these data objects are mandatory.

  • Measured and metered values

Measured values are analogue data objects measured from the process or calculated in the functions such as currents, voltages, power, etc. This information is produced locally and cannot be changed remotely unless substitution is applicable.

Metered values are analogue data objects representing quantities measured over time, for example energy. This information is produced locally and cannot be changed remotely unless substitution is applicable.

  • Controls

Controls contain data objects which are changed by commands such as switchgear state (ON/OFF), tap changer position or resettable counters. They are typically changed remotely, and are changed during operation much more often than settings.

  • Settings

Settings are data objects which configure the function for its operation. Since many settings are dependent on the implementation of the function, only a commonly agreed minimum is standardised. They may be changed from remote, but normally not very often.

  • Descriptions '

Descriptions are data objects, which give information about the LN itself or an allocated device. This information consists of identification information and general properties like configuration revision, hard and software revisions, etc.

  1. System logical nodes LN group: L

    1. LN relationships

In this subclause, the system specific information is defined. This includes common logical node information (for example logical node behaviour, nameplate information, operation counters) as well as information related to the physical device (LPHD) implementing the logical devices and logical nodes. These logical nodes (LPHD and common LN) are independent of the application domain. All other logical nodes are domain specific, but inherit mandatory and optional data objects from the common logical node.

Figure 2 - LOGICAL NODE relationships



All logical node classes defined in this document inherit their structure from the GenLogicalNodeClass (LN, see Figure 2) defined in IEC 61850-7-2. Apart from the logical node class ‘Physical Device Information’ (LPHD), all logical node classes (LLNO and domain specific LNs) defined in this document inherit at least the mandatory data objects of the common logical node (Common LN).

  1. NOTE Common logical node will never be instantiated.LN: Physical device information Name: LPHD

This LN is introduced in this part to model common issues for physical devices.

LPHD class

Data object name

Common data class

Explanation

T

М/О/ c

Data objects

Descriptions

PhyNam

DPL

Physical device name plate


M

Status information

PhyHealth

ENS

Physical device health


M

OutOv

SPS

Output communications buffer overflow


о

Proxy

SPS

Indicates if this LN is a proxy


M

InOv

SPS

Input communications buffer overflow


0

NumPwrUp

INS

Number of power-ups


о

WrmStr

INS

Number of warm starts


0

WacTrg-

INS

Number of watchdog device resets detected


о

PwrUp

SPS

Power-up detected


о

PwrDn

SPS

Power-down detected


о

PwrSupAlm

SPS

External power supply alarm


О

Controls

RsStat

SPC

Reset device statistics

T

о

Sim

SPC

Receive simulated GOOSE or simulated SV


О

Settings

Data sets (see IEC 61850-7-2)

Inherited and specialised from logical node class (see IEC 61850-7-2)

BufferedReportControlBlock (see IEC 61850-7-2)

Inherited and specialised from logical node class (see IEC 61850-7-2)

UnbufferedReportControlBlock (see IEC 61850-7-2)

Inherited and specialised from logical node class (see IEC 61850-7-2)

Services (see IEC 61850-7-2)

Inherited and specialised from logical node class (see IEC 61850-7-2)



  1. LN: common logical node Name: Common LN

The common logical node class provides data objects which are mandatory or conditional to all dedicated LN classes. It contains also data which may be used in all dedicated logical node classes, such as input references and data objects for the statistical calculation methods (refer to Annex F).

Common LN class

Data object name

Common data class

Explanation

T

MIDI C

Data objects

Mandatory and conditional logical node information (shall be inherited by ALL LN but LPHD)

Descriptions

NamPIt

LPL

Name plate


C1

Status information

Beh

ENS

Behaviour


M

Health

ENS

Health


C1

В Ik

SPS

Dynamic blocking of function described by the LN


0

Controls

Mod

ENC

Mode


C1



Common LN class

Data object name

Common data class

Explanation

T

М/О/ c

Data objects

CmdBIk

SPC

Blocking of control sequences and action triggers of controllable data objects


C2

Settings

InRefl

ORG

General input reference


0

BlkRef!

ORG

Blocking reference shows the receiving of dynamically blocking signal


0

Logical node information (statistical calculation specific - refer to Annex F)

Status information

CIcExp

SPS

Calculation period expired

T

C3

Controls

ClcStr

SPC

Enables the calculation start at time operTm from the control model (if set) or immediately


О

Settings

CIcMth

ENG

Calculation method of statistical data objects


C3

CIcMod

ENG

Calculation mode. Allowed values: TOTAL, PERIOD, SLIDING


C4

CIcIntvTyp

ENG

Calculation interval type


C4

ClcIntvPer

ING

In case CIcIntvTyp equals to MS, PER-CYCLE, CYCLE, DAY, WEEK, MONTH, YEAR, number of units to consider to calculate the calculation interval duration


C4

NumSublntv

ING

The number of sub-intervals a calculation period interval duration contains


0

CIcRfTyp

ENG

Refreshment interval type


О

CIcRfPer

ING

In case CIcIntvTyp equals to MS, PER-CYCLE, CYCLE, DAY, WEEK, MONTH, YEAR, number of units to consider to calculate the refreshment interval duration


О

CIcSrc

ORG

Object reference to source logical node


C5

CIcNxTmms

ING

Remaining time up to the end of the current calculation interval - expressed in milliseconds


О

InSyn

ORG

Object reference to the source of the external synchronization signal for the calculation interval


О

Data sets (see IEC 61850-7-2) •

Inherited and specialised from logical node class (see IEC 61850-7-2)

BufferedReportControlBlock (see IEC 61850-7-2)

Inherited and specialised from logical node class (see IEC 61850-7-2)

UhbufferedReportControlBlock (see IEC 61850-7-2)

Inherited and specialised from logical node class (see IEC 61850-7-2)

Services (see IEC 61850-7-2)

Inherited and specialised from logical node class (see IEC 61850-7-2)

Condition Cl: Mod, Health and NamPIt shall be inherited by LLN0 of the root LD of a hierarchy as mandatory and by all other LN as optional.

Condition C2: CmdBIk shall be inherited as optional data object by all LNs which contain controllable data objects additionally to Mod, if there is no BlkOpn/BlkCls available (like in XCBR).

Condition C3: This data object is optional but mandatory when considering statistical calculation, especially the MMXU, MMXN LN.

Condition C4: These data objects are mandatory, except when CIcMth equals UNSPECIFIED.

Condition C5: This data object is mandatory, if the considered LN is performing statistical calculation derived from another LN.



All dedicated LN classes shall inherit all data objects, data objects sets, control blocks and services from this common logical node class, if applicable. The data object beh shall be inherited in any case as mandatory.

  1. LN: Logical node zero Name: LLNO

This LN shall be used to address common issues for logical devices. For example, LLNO contains common information for the LD like health, mode and beh and NamPIt.

LLNO class

Data object name

Common data class

Explanation

T

MIDI C

Data objects

Status information

OpTmh

INS

Operation time


0

LocKey

SPS

Local operation for complete logical device


0

Loc

SPS

Local control behaviour


о

Controls

LocSta

SPC

Switching authority at station level


0

Diag

SPC

Run diagnostics


0

LEDRs

SPC

LED reset

T

0

Settings

GrRef

ORG

Reference to a higher level logical device


о

MltLev

SPG

Select mode of authority for local control (True - control from multiple levels is allowed, False - no other control level allowed) (see Annex B)


О

SettlngGroupControlBlock [0..1] (see IEC 61850-7-2)

Inherited and specialised from logical node class (see IEC 61850-7-2)

Log [O..n](see IEC 61850-7-2)

Inherited and specialised from logical node class (see IEC 61850-7-2)

LogControlBlock [0..n] (see IEC 61850-7-2)

Inherited and specialised from logical node class (see IEC 61850-7-2)

GOOSEControlBlock [0..n] (see IEC 61850-7-2)

Inherited and specialised from logical node class (see IEC 61850-7-2)

NIulticastSampledValueControlBlock [0..n] (see IEC 61850-7-2)

Inherited and specialised from logical node class (see IEC 61850-7-2)

UnlcastSampledValueControlBlock [0..n] (see IEC 61850-7-2)

Inherited and specialised from logical node class (see IEC 61850-7-2)



  1. LN: Physical communication channel supervision Name: LCCH

This LN is introduced in this part to model common issues for physical communication channels. It is instantiated for each physical channel or each pair of link level redundant physical channels.

LCCH class

Data object name

Common data class

Explanation

T

N1/0/ C

LNName


The name shall be composed of the class name, the LN-Prefix and LN- Instance-ID according to IEC 61850-7-2, Clause 22.



Data Objects

Status information

ChLiv

SPS

Physical channel status; true, if channel receives telegrams within a specified time interval.


M

RedChLiv

SPS

Physical channel status of redundant channel


C

OutOv

SPS

Output communications buffer overflow


0

InOv

SPS

Input communications buffer overflow


о