Configuring SOE events in the IEC 61850 Configuration Tool
Original instructions
About us
Introduction
The BMENOP0300 module supports the transfer of external events originated by ERT and CRA modules to SCADA via a buffered report control block. The BMENOP0300 module cyclically detects data objects in CPU memory and includes them in a report control block with each data object's status value, quality and timestamp data.
Configuring SOE Events
To preserve memory mapping and retain the SOE timestamping that originated with the source ERT or CRA module, the BMENOP0300 module provides a single dedicated channel for the transfer of external events.
The BMENOP0300 module supports the creation and use of a single dedicated data set that can contain data objects of the single point setting (SPS) class and data object (DO) functional constraint. Each DO instance represents a single ERT/CRA channel, and includes the status value (stVal), quality (q), and timestamp (t) data attributes.
When configuring the Data Set, you need to link all DOs, and then associate a single buffered report control block (BRCB) with this Data Set. The DO instances included in the report can originate from any kind of logical node (LN). When adding a DO instance to the Data Set, you need to specify the link with the channel (Event ID), as shown below
When configuring the Data Set, you need to include all DOs. The DO instances included in the report can originate from any kind of logical node (LN). When adding a DO instance to the Data Set, you need to specify the link with the channel (Event ID), as shown below:
Next, you need to associate a single buffered report control block (BRCB) with this data set, as shown below:
After mapping the DO into PAC variables, two DDT instances are automatically created and added to the application:
NOTE: The BMENOP0300 module can add these events into a buffered report control block, according to the configuration. Because the Quantum ERT uses local time, whereas the Mx80 ERT uses UTC time, the BMENOP0300 module can manage the Quantum ERT time conversion from 60870 local time to 61850 UTC time. No such time conversion is required for Mx80 ERT/CRA.
Data Type Structure: IED_RPT
Element
Type
Description
Status
WORD
Report status:
  • bits 0...7: Report enabled/disabled. Each bit represents one report instance:
    • 0 = disabled
    • 1 = enabled
  • bits 8...15: buffer overflow:
    • 0 = no buffer overflow
    • 1 = overflow
DaChgCnt
WORD
A counter value that increments each time a report is generated.
Data Type Structure: IED_EVT_M
This structure describes the format of events used by Mx80 devices using the IEC 61850 format:
Element
Type
Description
Reserv
BYTE
<reserved>
Value
BYTE
Input value
EventID
WORD
An event identifier, which can be one of the following:
  • the channel number
  • a user-defined value
SecondSince Epoch
DWORD
The interval, in seconds, from 1970-01-01 00:00:00 UTC to the present.
FracOfSec_L
WORD
The fraction of the current second when the value element, above, has been determined. The fraction of second is calculated as:
(SUM from i = 0 to 23 of bi*2**–(i+1) s).
FracOfSec_H
BYTE
TimeQuality
BYTE
TimeQuality describes provides information regarding the sending IED, and consists of the following attributes:
Bits
Attribute
Type
Description
0...4
TimeAccuracy
CODED ENUM
The accuracy class of the time source. Only the value of 10 = 1 ms is supported.
5
ClockNotSynchronized
BOOL
When set to 1, this indicates the time source of the sending IED is not synchronized with external UTC time.
6
ClockFailure
BOOL
When set to 1, this indicates the time source of the sending IED is unreliable.
7
LeapSecondsKnown
BOOL
When set to 1, this indicates that SecondSinceEpoch value includes all leap year seconds. When set to 0, this indicates leap seconds are not included and seconds are calculated from the current date assuming a constant day length of 86400 s.
Data Type Structure: IED_EVT_Q
This structure describes the format of events used by Quantum devices using the IEC 61850 format:
Element
Type
Description
Reserv
BYTE
<reserved>
Value
BYTE
Input value
Event ID
WORD
An event identifier, which can be one of the following:
  • the channel number
  • a user-defined value
Reserved
BYTE
<reserved>
Month
BYTE
Month
Year
BYTE
Year
Ms_Lsb
BYTE
Time in milliseconds (least significant byte)
Ms_Msb
BYTE
Time in milliseconds (most significant byte)
Min
BYTE
Invalid time/minutes
Hour
BYTE
Summer time/hours
Day
BYTE
Weekday/day of the month
Data Type Structure: IED_ERT_BUF
Element
Type
Description
NewTS
BYTE
Time stamp of the new event
EvtSrc
BYTE
Event source:
  • 0 = Quantum
  • 1 = Mx80
EventEntity
WORD[6]
Event entity, which can be one of the following:
  • IED_EVT_Q
  • IED_EVT_M