7-186 F650 DIGITAL BAY CONTROLLER GEK-106310-AF
7.2 IEC 61850 PROFILE FOR F650 CHAPTER 7: IEC 61850 PROTOCOL
4 PIXIT for Reporting model
Description Value / Clarification
The supported trigger conditions are integrity Y
data change Y
quality change N
data update N
general interrogation Y
The supported optional fields are sequence-number Y
report-time-stamp Y
reason-for-inclusion Y
data-set-name Y
data-reference Y
buffer-overflow Y
entryID Y
conf-rev Y
segmentation Y
Can the server send segmented reports Y
Mechanism on second internal data change notification
of the sam
e analogue data value within buffer period
(Compare IEC 61850-7-2 $14.2.2.9)
Send report immediately
Multi client URCB approach (compare IEC 61850-7-2
$14.2
.1)
Option b) of IEC 61850-7-2 $14.2.1 is implemented
which means that each client has it's own set of URCB's.
What is the format of EntryID Signed 32 bit integer.
What is the buffer size for each BRCB or how many
r
eports can be buffered
Buffer size = 50000 bytes.
Pre-configured RCB attributes that cannot be changed
onl
ine when RptEna = FALSE
DatSet attributes are always fixed
Additional Items:
BufTm=0 behaviour When BufTm=0 multiple data can be placed in one
r
eport if changes of these data have been detected at
the same time, it means during the same scan period.
The scan period for analogues is 500 miliseconds.
Integrity period Configurable >= 500 miliseconds
EntryID EntryID is incremented only if the EntryID bit is set in
OptFl
ds.
A valid EntryID that can be written by a client should be
eq
ual or smaller than the EntryID in BRCB. This is
because the client should only request retransmission
of reports that had already been sent.
GI reports Can be triggered independently from the GI bit in
T
rgOps
Behaviour at buffer overflow When buffer overflow occurs all reports generated after
bu
ffer overflow has the BufOvfl flag set.
To stop sending reports with the BufOvfl flag, the client
should d
isable BRCB and clear the BufOvfl flag by
setting PurgeBuf=TRUE.
Sending of already buffered reports after enabling BRCB All reports that have been already buffered, after
setting the RptEna=
TRUE are sent in chronological
order, e.g. the oldest reports are sent first.