Introduction
Use the NOP850_EVTS
elementary function block (EFB) to:
Manage and synchronize the transfer of external events from an ERT or CRA into the memory of the 140 NOP 850 00 module.
Manage the transfer external events between a PLC and the 140 NOP 850 00.
Representation in FBD

Input Parameters
Input parameter |
Type |
Description |
---|---|---|
|
|
Start transferring. |
|
|
ERT type:
NOTE: When ERT type is:
|
|
Either: |
Event description, including value, quality, time stamp and ID. Type depends upon the platform, either Mx80 or Quantum. |
|
Report information. |
|
|
|
Time threshold in 100 ms for triggering an event. A value greater than 0. |
Output Parameters
Output parameter |
Type |
Description |
---|---|---|
|
|
A value of 1 (true) indicates the function block completed successfully. |
|
|
A value of 1 (true) indicates execution of the function block is in progress. |
|
|
A value of 1 (true) indicates the function block detects an execution error. |
|
|
Identifies the detected error:
|
|
Raw buffer containing event time stamp entities. |
Data Type Structure - IED_RPT
IED_RPT
Element |
Type |
Description |
---|---|---|
Status |
WORD |
Report status:
|
DaChgCnt |
WORD |
A counter value that increments each time a report is generated. |
Data Type Structure - IED_ERT_BUF
IED_ERT_BUF
Data Type Structure - IED_EVT_M
IED_EVT_M
: This structure
describes the format of events used by Mx80 devices using the IEC61850
format:
Element |
Type |
Description |
|||
---|---|---|---|---|---|
Rese1 |
BYTE |
<Reserved> |
|||
Value |
BYTE |
Input value. |
|||
EventID |
WORD |
An event identifier, either:
|
|||
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 |
Time Accuracy |
CODED ENUM |
The accuracy class of the time source. Only the value of 10 = 1 ms is supported. |
||
5 |
Clock Not Synchronized |
BOOL |
When set to 1, this indicates the time source of the sending IED is not synchronized with external UTC time. |
||
6 |
Clock Failure |
BOOL |
When set to 1, this indicates the time source of the sending IED is unreliable. |
||
7 |
Leap Seconds Known |
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 Structure - IED_EVT_Q
IED_EVT_Q
: This structure
describes the format of events used by Quantum devices using the IEC61850
format:
Element |
Type |
Description |
---|---|---|
Rese1 |
BYTE |
<Reserved> |
Value |
BYTE |
Input value. |
EventID |
WORD |
An event identifier, either:
|
Rese2 |
BYTE |
<Reserved> |
Month |
BYTE |
Month: 0...12 |
Year |
BYTE |
Year: 00...99 (indicating 2000 to 2099) |
Ms_Lsb |
BYTE |
Time in milliseconds: 0...59999 (least significant byte). |
Ms_Msb |
BYTE |
Time in milliseconds: 0...59999 (most significant byte). |
Min |
BYTE |
Invalid time/minutes: 0...59 |
Hour |
BYTE |
Summer time/hours: 0...23 |
Day |
BYTE |
Weekday.Day of the month: 1...31 |
Quantum ERT FBD Example

Mx80 CRA FBD Example
