Schweitzer Engineering SEL-351P, Быстрый старт

Страница: 661 / 674

H-12 Distributed Network Protocol (DNP) V3.00 Date Code 991201
SEL-351P Manual Técnico
Value Event Cause
1
Trigger command
2 Pulse command
4 Trip element
8 ER element
And the lower byte is defined as follows:
Value Fault Type
0
Indeterminate
1 A-Phase
2 B-Phase
4 C-Phase
8 Ground
The lower byte may contain any combination of the above bits (e.g., a 6 is a B to C fault and a 9
is an A to Ground fault). If Analog 105 is 0, fault information has not been read and the related
analogs (106 - 113) do not contain valid data.
Control Relay Output Blocks (object 12, variation 1) are supported. The control relays
correspond to the remote bits and other functions, as shown above. The Trip/Close bits take
precedence over the control field. The control field is interpreted as follows:
Index Close (0x4X) Trip (0x8X) Latch On (3) Latch Off (4) Pulse On (1) Pulse Off (2)
0 - 7 Set Clear Set Clear Pulse Clear
8 - 15 Pulse Do nothing Pulse Do nothing Pulse Do nothing
16 Pulse RB2 Pulse RB1 Pulse RB2 Pulse RB1 Pulse RB2 Pulse RB1
17 Pulse RB4 Pulse RB3 Pulse RB4 Pulse RB3 Pulse RB4 Pulse RB3
18 Pulse RB6 Pulse RB5 Pulse RB6 Pulse RB5 Pulse RB6 Pulse RB5
19 Pulse RB8 Pulse RB7 Pulse RB8 Pulse RB7 Pulse RB8 Pulse RB7
20 Pulse CC Pulse OC Pulse CC Pulse OC Pulse CC Pulse OC
The Status field is used exactly as defined. All other fields are ignored. A pulse operation
asserts a point for a single processing interval. Caution should be exercised with multiple remote
bit pulses in a single message (i.e., point count > 1), as this may result in some of the pulse
commands being ignored and returning an already active status.
Analog Outputs (objects 40 and 41) are supported as defined by the preceding table. Flags
returned with object 40 responses are always set to 0. The Control Status field of object 41
requests are ignored. If the value written to index 0 is outside of the range 1 through 6, the relay
will not accept the value and will return a hardware error status.
Relay Summary Event Data
Whenever there is unread relay event summary data (fault data), binary input point 1023 will be
set. In order to load the next available relay event summary, the master should pulse binary
output point 15. This will cause the event summary analogs (points 105
-
113) to be loaded with
information from next oldest relay event summary. Since the summary data is stored in a first-in,
first-out manner, loading the next event will cause the data from the previous load to be
discarded. The event summary analogs will retain this information until the next event is loaded.