ProSoft Technology MVI56E-DNPNET - Manual (Page 121)

MVI56E-DNPNET ♦ ControlLogix Platform Contents
DNPNET Ethernet Client/Server Communication Module User Manual
ProSoft Technology, Inc. Page 121 of 140
February 13, 2015
 Use CIPconnect for these applications and disconnect the module Ethernet port from the
network
DNPNET V2.00
DEVICE PROFILE DOCUMENT
Vendor Name:
ProSoft Technology, Inc.
Device Name: MVI56E-DNPNET (VERSION 2.00)
Highest DNPNET Level Supported: Device Function:
For Request: L2 Server & Client
For Responses: L2
Notable objects, functions, and/or qualifiers supported in addition to the highest DNPNET level stated above (see attached
table for complete list).
Definition of selected IIN bits:
Device Trouble - PLC data transfer operation is not taking place
Configuration Error - User specified point or event count is too high for application (can correct only by changing
configuration in PLC).
The following features are configurable on the module:
Collision avoidance, time sync before events are generated and default analog input events, Obj32V4 or O32V2, select
option. Floating-point variations are supported for analog input and output objects (both single and double floating-point
types). Support for Obj110 (octet string) available only using read function.
Events generated by IED units attached to a Client may pass their events directly to the server port. These events may
not occur in the correct time sequence. They are placed in the event buffer as the module receives them. This provides
the greatest time resolution for remote events.
Counter Freeze with reset will not zero values in the processor. Therefore, this function should only be used for the Client.
Module will not generate events until Restart IIN bit is cleared by DNPNET Client except for events passed through
module from attached IED units.
Maximum Data Link Frame Size (octets):
Maximum Application Fragment Size (octets):
Transmitted: 292 Transmitted: 2048
Received: 292 Received: 2048
Maximum Data Link Re-tries: Maximum Application Layer Re-tries:
Configurable from 0 -
255
None
Requires Data Link Layer Confirmation:
Configurable at module start-up (never, sometimes, & always)
Requires Application Layer Confirmation:
When reporting Event Data as a server unit
Time-outs while waiting for:
Data Link Confirm : Configurable at module start-up (1 to 32767 milliseconds)
Complete Application
Fragment
: Configurable at module start-up
Application Confirm : Configurable at module start-up (1 to 32767 milliseconds)