KNOWLEDGE BASE / INTEGRATION GUIDES

DeltaV Integration with

Allen-Bradley
ControlLogix across
Device Level Ring (DLR)
Network Using Class 1
EtherNet/IP Connection
By Edin Rakovic on 01.16.13
PRODUCT: DELTAV VIRTUAL IO MODULE - VIM2
This technical note describes the recommended settings for integrating the
Allen-Bradley ControlLogix across Device Level Ring (DLR) network using
Class1 messaging via IOD-4102 Ethernet/IP Virtual I/O Module. For
configuring the ControlLogix for use in other applications, see the
manuals/documentation pertaining to the specific application hardware
(download links in Introduction).

Introduction
The procedure for interfacing the Allen-Bradley ControlLogix across a Device
Level Ring (DLR) using Class 1 connection with a Virtual I/O Module is
comprised of three main parts: VIMNet Explorer Setup, DeltaV Explorer Setup,
and Control Studio Setup. There may be cases in which specific information
pertaining to the components mentioned in this document must be
referenced. In the case of such an event, please refer to that part's
documentation (download links are listed below). To better understand both
interfaces, please look over the manuals below before proceeding forward.

Allen-Bradley ControlLogix System User Manual PDF

(http://literature.rockwellautomation.com/idc/groups/literature/documents/um/1756-um001_-en-p.pdf)

Ethernet/IP Driver for DeltaV Virtual I/O Module Web Help

(http://www.mynah.com/vimnet_webhelp/Content/ethernet_ip/theory_of_operation.htm)

The following procedure assumes that the IP Address of the Allen-Bradley

E-Tap Module has already been configured. One way to reconfigure the IP
Address is to use RSLinx.

VIMNet Explorer Setup

This section provides information for configuring VIMNet Explorer to
interface with the Allen-Bradley ControlLogix module. The procedure
described below will create a configuration for the VIM that will eventually be
downloaded to the VIM. This process is necessary for the DeltaV Controller to
be able to read/write to the ControlLogix IO.

Open VIMNet Explorer. Right-click on "I/O Net" and select "New Controller."

A prompt will appear asking for the name of the controller. The value for this
parameter is at the discretion of the user, but we recommend that it matches
the configured controller name in the DeltaV Database.

Expand "I/O Net" then right-click on the newly created controller and select
"New IO VIM."

A prompt will appear asking for configuration information specific to the VIM.
The "Type," "Virtual Cards," and "DeltaV version 10.x or earlier or M-Series IO"
fields should be configured as shown in the image above. We are
communicating with S-Series Controllers on DeltaV v11.3.1 All of the fields
under the "VIM Properties" panel are at the discretion of the user. Once the

settings have been configured, the IP address availability can be confirmed by

clicking on the Ping button and the following results will appear assuming that
the address is not in use.

Next, the 1756-EN2TR interfaces will need to be configured as devices in

VIMNet Explorer.

Expand the controller, then the newly created IO VIM, and then "C57." Rightclick on "P01" under "C57" and select "Add Device."

A prompt will appear asking for configuration information specific to the new
device (this device is the 1756-EN2TR Module). The "Device Address" field will
need to match the device address in DeltaV. At this time, please record the
configured Device Address as it will be used later in the configuration of the
DeltaV Serial Device. The "Description" field is at the discretion of the user but
we recommend adding a description of the field device interface. After the
description has been provided, click "Add"to configure device specific
settings.

Configure the IP address, click "OK" to save the device IP Settings, then click
"OK" to save the overall device settings. At this point, the following
configuration should exist:

Next, the VIM will be commissioned and the configuration will be uploaded to
the VIM. Right-click on the VIM controller created earlier and select
"Commission."

Then, select the decommissioned Ethernet IP VIM. Once again, there will be
an option to Ping the IP Address and make sure it is available before assigning
the address to the VIM.

Select the appropriate VIM from the list of decommissioned VIMs and click on
"Start Flashing." At this point, please verify that the VIM intended for this
application has its lights flashing. After identification has been completed,
click on "Stop Flashing," and click "OK."

After commissioning, a blue arrow will appear next to the VIM controller. This
means that the VIM still requires the configuration in VIMNet Explorer to be
uploaded to the VIM hardware. Right-click on the VIM controller and select
"Upload Configuration to VIM."

Select "Yes" when prompted to save the configuration.

Select "Yes" at the dialogue warning to confirm the upload.

Now, the upload process will begin. Keep in mind that the term "upload
configuration" refers to the VIMNet Explorer sending the configuration to the
VIM.

Once the upload is finished, a dialogue will appear indicating a successful

upload and the blue arrow that was next to the VIM controller should now be
gone.

Open DeltaV Explorer and continue to the next step of the procedure.

DeltaV Explorer Setup

This section provides information for configuring the DeltaV MD/MD+
controller to communicate with the VIM in DeltaV Explorer. At this point, it is
assumed that an existing controller is present and the only configuration that
this article will cover includes the IO Configuration of the four programmable
serial cards emulated by the VIM. Earlier, the controller name was used in the
VIMNet Configuration. Please make sure that the same controller name is used
in the DeltaV configuration.
If the VIM is present at the time of the configuration, please use the
"Autosense IO" option in the Right-click menu of the Controller IO. Otherwise,
follow the procedure below to add the cards individually.

Right-click on "Control Network -> Physical Network -> CTRL1 -> I/O" and
select "New Card."

A new card will need to be configured with a card class of "Serial Cards" and
card type "2 Ports, Programmable, RS232/RS485". Furthermore, this process
will need to be completed for cards 57-60. Once the cards are configured under
"CTRL1" -> "I/O," there will be a configuration similar to the screenshot below.

Expand the newly created card "C57," then right-click on "P01" and select

"Properties."

A prompt will appear asking for configuration information specific to the port.
Set the port to "Enabled," then click on the Advanced Tab.

The parameters "Retry count," "Message timeout (ms)," and "Transmit delay
(ms)" are tuneable parameters.
"Retry count" = The number of attempts that the controller will make in
requesting a data point from the Programmable Serial Card.
"Message timeout (ms)" = The amount of time in milliseconds that the
controller will wait before retrying the message.
"Transmit delay (ms)" = The amount of time that the controller will delay the

request before sending it to the Programmable Serial Card.

Each one of these parameters will have an affect on communications and will
need to be tuned for proper operation. When an unreliable network is present,
then a retry count can be utilized to attempt to obtain the data multiple times
before the process is notified that the data point is not available. Under
conditions where multiple network hops might exist, a Message timeout can
be increased to have the controller wait longer for the response. When DeltaV
communications are saturating the field devices, a Port or dataset level
transmit delay can be set.

With that in mind, please consider that the controller will scan all of the
datasets and if the datapoint is not available, there will be a latency in the
communications for the total timeout T where T= (1st Attempt + Retry Count) *
Message timeout.
We recommend using the settings above as a first pass at obtaining
communications with the field device and then revisiting these settings
during the tuning of the communications.

Under the "Communications" tab, the default settings are used since the VIM
emulated Prog. Serial Cards do not use these settings.

Expand "C57" under "I/O", then right-click on "P01" under "C57" and select
"New Serial device."

A prompt will appear asking for configuration information specific to the new
serial device. Set "Device Address" to "1." The "Description" field is at the
discretion of the user.

Right-click on "DEV01" under "P01" and select "New Dataset."

A prompt will appear asking for configuration information specific to the new
dataset. In the "General" tab, set "Data direction" to "input." This defines the
direction of the data, relative to DeltaV. All input datasets will be scanned by
the VIM and output datasets will be written when a state change (i.e., a register
value changes) is detected.
The Output Mode controls how much of the dataset is written when a register
changes state. In all cases, outputs are only written when a register value
changes. The following output modes are valid:
0 - Block Output Mode = Any register changes value and all registers in the
dataset will be written out to the field device.

1 - Single Register Output Mode = A register changes value and only that
register is written to the field device. All other registers retain their current
state.
Output Read Back option controls the output dataset behavior as a bidirectional dataset. This means that the dataset is a part of the VIMs input
scan list. If the field device changes a value in this dataset, DeltaV will be able
to detect the change. When DeltaV changes register values in this dataset, they
are written to the device, according to the Output Mode setting. Note that for
Output datasets with readback, pending output changes always have
precedence over reading inputs.

In the "DeltaV" tab, set "DeltaV data type" to "16 bit uint w/status" and set
"Dataset Tag" to "CTRL1C57010101." This attribute defines how data will be
stored in the DeltaV dataset. The following table describes available options
for PLC5/XXE, and SLC 5XX and ControlLogix processors. For more
information please refer to the VIMNet Help Files (online webhelp link
(http://www.mynah.com/vimnet_webhelp/Default.htm)).

In the "PLC" tab, set "Device data type" to "15," set "Data start address" to "0,"
and set "Number of values" to "100." The Device data type parameter controls
the messaging mode of the VIM. For all of the supported messaging modes,
please refer to the VIMNet Help Files (online webhelp link
(http://www.mynah.com/vimnet_webhelp/Default.htm)).
The Start Address parameter controls the offset from the beginning of the data
file that the VIM will read from. For Device Data Type 15 (ENBT), this value
only sets the visible register number in DeltaV and it does not affect the
communications.
- When addressing registers, DeltaV PSIC register numbers are 1 based,
whereas PLC and SLC registers are 0 based.
The Number of Values parameter determines the size of the dataset. The value
is given in the number of registers based on the DeltaV Data Type. The
maximum number of registers is 100, or 50 for Floating Point.
- Floating Point file types, 32-bit Integer, and 32-bit unsigned Integer require 2
16-bit registers per value, thus reducing the registers per dataset to 50
(maximum 16-bit registers per dataset is 100).

When the PLC tab Device Data Type is specified as 15, the remote device
connects to the VIM. In this case, the "Special Tab" is not used.
Once all of the datasets have been configured, all 4 cards will need to be
downloaded at least once. This means that even if the emulated Prog. Serial
Cards are not being used, they will need to be downloaded at least once.
At this point, the interface has been completed. If you have any questions
regarding the procedures and components described in this document, please
feel free to contact MYNAH Support by creating a Support Ticket from your
MYNAH My Account.

Contact
MYNAH Technologies LLC
390 South Woods Mill Road, Suite 100
Chesterfield, MO 63017 USA
+1.636.728.2000 (International)
+1.636.728.2001 (Fax)
Email: support@mynah.com
Web: www.mynah.com

MYNAH Technologies 2012 - 2016. All rights reserved.

Designs are marks of MYNAH Technologies, Emerson Process Management, DeltaV, and the DeltaV design are marks of
one of the Emerson Process Management of companies. All other marks are property of their respective owners. The
contents of this publication are presented for informational purposes only, and while every effort has been made to
ensure their accuracy, they are not to be construed as warrantees or guarantees, expressed or implied, regarding the
products or services described herein or their use or applicability. All sales are governed by our terms and conditions,
which are available on request. We reserve the right to modify or improve the design or specification of such products at
any time without notice.
While this information is presented in good faith and believed to be accurate, Mynah Technologies does not guarantee
satisfactory results from reliance upon such information. Nothing contained herein is to be construed as a warranty or
guarantee, express or implied, regarding the performance, merchantability, fitness or any other matter with respect to the
products, nor as a recommendation to use any product or process in conflict with any patent. Mynah Technologies
reserves the right, without notice, to alter or improve the designs or specifications of the products described herein.