GEK-106310AB F650 Digital Bay Controller 7-55
7 IEC 61850 PROTOCOL 7.2 IEC 61850 PROFILE FOR F650
7
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 same 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
reports can be buffered
Buffer size = 50000 bytes.
Pre-configured RCB attributes that cannot be changed
online when RptEna = FALSE
DatSet attributes are always fixed
Additional Items:
BufTm=0 behaviour When BufTm=0 multiple data can be placed in one
report 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
OptFlds.
A valid EntryID that can be written by a client should be
equal 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
TrgOps
Behaviour at buffer overflow When buffer overflow occurs all reports generated after
buffer overflow will have the BufOvfl flag set.
To stop sending reports with the BufOvfl flag, the client
should disable 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 will be sent in chronological order,
e.g. the oldest reports will be sent first.
Multi client access to BCRB It is possible to access and configure the same BRCB
from different clients. However it is strongly
recommeded that each BRCB should be accessed and
configured by only one client.
There is a restriction that the first client which enables
BRCB for the first time will establish the “minimum MMS
PDU size” required for this BRCB. After realsing the
BRCB by the first client, this BRCB can be enabled by
any client which has the MMS PDU size at least as big
as the established “minimum MMS PDU size” for that
BRCB.
The explanation of this restriction is that after enabling
BRCB for the first time and disabling it the reports can
be buffered in it. For the segmentation of the reports in a
buffer the device uses the “minimum MMS PDU size”
that was stored by the first client which enabled BRCB. If
any other client with MMS PDU size lower than the MMS
PDU size used by BRCB for segmentation would enable
the BRCB then the reports stored in a buffer could not
be sent to this client as their size would be too big.
To Next Page
Loading...
