scheider electric MiCOM P746, Technical Manual

Page: 396 / 530

P746/EN SC/G31 SCADA Communications
(SC) 13-
14
MiCOM P746
SC
2.4 Setting changes
(See R6512, Courier User Guide - Chapter 9)
There are three categories of settings within the relay database:
−
Control and support
−
Disturbance recorder
−
Protection settings group
Setting changes made to the control and support settings are implemented immediately and
stored in non-volatile memory. Changes made to either the disturbance recorder settings or
the protection settings groups are stored in a ‘scratchpad’ memory and are not immediately
implemented by the relay.
To action setting changes stored in the scratchpad the save changes cell in the configuration
column must be written to. This allows the changes to either be confirmed and stored in non-
volatile memory, or the setting changes to be aborted.
2.4.1 Setting transfer mode
If it is necessary to transfer all of the relay settings to or from the relay a cell within the
communication system data column can be used. This cell (location BF03) when set to 1
makes all of the relay settings visible. Any setting changes made, with the relay set in this
mode, are stored in scratchpad memory (including control and support settings). When the
value of BF03 is set back to 0 any setting changes are verified and stored in non-volatile
memory.
2.5 Event extraction
Events can be extracted either automatically (rear port only) or manually (either Courier
port). For automatic extraction all events are extracted in sequential order using the standard
Courier event mechanism, this includes fault/maintenance data if appropriate. The manual
approach allows the user to select events, faults, or maintenance data at random from the
stored records.
2.5.1 Automatic event extraction
(See Chapter 7 Courier User Guide, publication R6512)
This method is intended for continuous extraction of event and fault information as it is
produced. It is only supported via the rear Courier port.
When new event information is created the event bit is set within the status byte, this
indicates to the master device that event information is available. The oldest, unextracted
event can be extracted from the relay using the send event command. The relay will respond
with the event data, which will be either a Courier Type 0 or Type 3 event. The Type 3 event
is used for fault records and maintenance records.
Once an event has been extracted from the relay, the accept event can be used to confirm
that the event has been successfully extracted. If all events have been extracted then the
event bit will reset, if there are more events still to be extracted the next event can be
accessed using the send event command as before.