ProSoft Technology MVI69-DNPSNET - Manual (Page 91)

Reference MVI69-DNPSNET ♦ CompactLogix or MicroLogix Platform
Distributed Network Protocol Interface Module
ProSoft Technology, Inc. Page 91 of 119
November 3, 2008
5.3.2 Communication Parameters
This phase of design defines the communication parameters required for
successful communications between the module and DNP master and slave
units over the Ethernet network. Determine the IP address for the module and
the list of IP addresses that can connect to the unit if this feature is enabled.
Consult with the MIS person in charge of assigning these addresses and setting
up the network configuration. The Reference chapter contains a form to aid in
setting these parameters. Fill out this form before attempting to configure the
module. You must also determine if the UDP or the TCP protocol or both will be
used in your application. The module supports a single connection for the TCP
protocol. The UDP server supports receipt of messages from multiple clients.
Access to both servers can be limited by using the IP address list filtering.
5.3.3 Functionality
This phase of design defines the features of the DNP Level 2 Subset supported
by the module and to be utilized in the specific application. For example, will the
unit use unsolicited messaging? Coordination with the DNP master developer is
required to verify that the host will support the functionality you select. The
features that must be defined in this design step are as follows:
ƒ Will analog events be returned with or without a time value?
ƒ Will events be logged before time synchronization has occurred?
ƒ Will the module start with database values initialized by the processor?
For a complete description of the module configuration, refer to the Module
Setup section.
5.3.4 Data Transfer at Startup
The module can be configured to have the internal databases initialized with data
contained in the processor. This feature requires ladder logic. Data to be
initialized are as follows: Binary and Analog Output data. This feature can be
used to bring the module to a known state (last state set in controller) when the
module is first initialized. For example, in order to have the module startup using
the last set of binary output values and setpoint values (analog outputs), enable
this feature.
If this feature is implemented, the module will request the data from the
processor. Ladder logic must handle the blocks requested by the module (1000
to 1149) based on the modules configuration values for the write block data.
When the block is requested, the module must place the correct data in the block
and return the block to the module. The module will receive the data and initialize
the output values. Each block required by the module for initialization will be
requested.