Dnp3 Configuration - GE P642 Technical Manual

Chapter 16 - Communications
Code Number Identifier Name
0 Success
1 Timeout
2 No select
3 Format error
4 Not supported
5 Already active
6 Hardware error
7 Local
8 Too many operations
9 Not authorized
127 Undefined
Note:
Code numbers 10 through to 126 are reserved for future use.
6.3.9

DNP3 CONFIGURATION

To configure the device:
1. Select the CONFIGURATION column and check that the Comms settings cell is set to Visible.
2. Select the COMMUNICATIONS column.
3. Move to the first cell down (RP1 protocol). This is a non-settable cell, which shows the chosen
communication protocol – in this case DNP3.0.
4. Move down to the next cell (RP1 Address). This cell controls the DNP3.0 address of the IED. Up to 32 IEDs can
be connected to one spur, therefore it is necessary for each IED to have a unique address so that messages
from the master control station are accepted by only one IED. DNP3.0 uses a decimal number between 1
and 65519 for the Relay Address. It is important that no two IEDs have the same address.
5. Move down to the next cell (RP1 Baud Rate). This cell controls the baud rate to be used. Six baud rates are
supported by the IED 1200 bps, 2400 bps, 4800 bps, 9600 bps, 19200 bps and 38400 bps. Make sure that
the baud rate selected on the IED is the same as that set on the master station.
348
The received request has been accepted, initiated, or queued.
The request has not been accepted because the 'operate' message was received after the
arm timer (Select Before Operate) timed out.
The arm timer was started when the select operation for the same point was received.
The request has not been accepted because no previous matching 'select' request exists. (An
'operate' message was sent to activate an output that was not previously armed with a
matching 'select' message).
The request has not been accepted because there were formatting errors in the control
request ('select', 'operate', or 'direct operate').
The request has not been accepted because a control operation is not supported for this
point.
The request has not been accepted because the control queue is full or the point is already
active.
The request has not been accepted because of control hardware problems.
The request has not been accepted because local access is in progress.
The request has not been accepted because too many operations have been requested.
The request has not been accepted because of insufficient authorization.
The request not been accepted because of some other undefined reason.
COMMUNICATIONS
RP1 Protocol
DNP3.0
COMMUNICATIONS
RP1 Address
1
Description
P64x
P64x-TM-EN-1.3