ALTUS Hadron Xtorm, User Manual, Page: 138 / 351

4. Configuration
137
Code Number Name Description
0 SUCCESS Request: accepted, started or queued.
1 TIMEOUT
Request not accepted because the message
was received after the time out of the select
command.
2 NO_SELECT
Request not accepted because the select
command was not sent previously.
3 FORMAT_ERROR
Request not accepted because there was
formatting errors on control request (select,
operate or direct operate).
4 NOT_SUPPORTED
Request not accepted, because a control
operation is not supported by this point.
5 ALREADY_ACTIVE
Request not accepted because the control
queue is already full or the point is already
active.
6 HARDWARE_ERROR
Request not accepted, because of hardware
problems.
7 LOCAL
Request not accepted because the "key" Local /
Remote is in Local position.
8 TOO_MANY_OBJS
Request not accepted because many objects
are present in the same request.
9 NOT_AUTHORIZED Code not implemented.
10 AUTOMATION_INHIBIT
Request not accepted because it was prevented
or inhibited by a local automation process.
11 PROCESSING_LIMITED
Request not accepted because the device
cannot process another activity, in addition to
those in progress.
12 OUT_OF_RANGE
Request not accepted because the value is
outside the acceptable range allowed for this
point.
65 REMOTE_TIMEOUT IED remote timeout
13 a 125 RESERVED Reserved for future use.
126 NON_PARTICIPATING Code not implemented.
127 UNDEFINED
Request not accepted because of some other
undefined reason.
Table 4-91. Status Code for DNP Commands
DNP3 Ethernet Server
This protocol is available for Hadron Xtorm Series CPUs in its Ethernet channels. When you select
this option in MasterTool Xtorm, the CPU becomes DNP3 communication server, allowing
connection with up to five DNP3 client devices. For each client, the driver has a unique event queue
with the following characteristics

Size: 4.500 events

Overflow policy: keeps the most recent event
Follow the steps below in order to set this protocol:

Add the DNP3 Server protocol instance to one of the available Ethernet channels (NET 1 to NET
6).

To execute this procedure see, Inserting a Protocol Instance.

Set the Ethernet interface. See Ethernet Interfaces Configuration

Set the general parameters of the DNP3 Server protocol with the connection modes Port or IP
(for the later, set TCP port number also).

Add and set the devices, defining the requested parameters.

Add and set the DNP3 mappings, specifying the variable name, static group variation, event
group variation, index, size, range, event class, dead band and dead band type.

Set the link layer parameters, specifying the addressing and confirmation messages.