Knowledge Base /
Integration Guides
DeltaV Integration with 1769 CompactLogix Controllers Using Class 1 EtherNet/IP Connection
By Edin Rakovic
Product: DeltaV Virtual IO Module - VIM2

This technical note describes the recommended settings for integrating 1769 CompactLogix controllers using the Class 1 Generic ENBT Modules and the IOD-4102 Allen Bradley Ethernet/IP driver for the Virtual IO Module.

Introduction

Each dataset in DeltaV corresponds to a specific ENBT module in the Logix controller. Configuration of an ENBT module is described below. The Logix controller manages data updates for an ENBT dataset, i.e., the Logix is the Master in this communication. The VIM merely receives the data and sends it up to the DeltaV controller. By nature, this mechanism is very fast and suitable for highspeed data transfers from the Logix I/O sub-system into DeltaV. Please refer to the Ethernet/IP Master Driver for DeltaV Virtual IO Module manual to obtain the complete procedure on configuring the DeltaV and VIM componets of the interface.

Note

Class1 (ENBT) connections are supported only in simplex VIM configurations because of the Master/Slave relationship between VIMs and Logix controllers. For ENBT connections, the VIM behaves as a slave.

VIM Configuration

The VIM configuration involves creating the VIM placeholder, as well as adding the device configuration. For more information on this component configuration, please refer to the Ethernet/IP Master Driver for DeltaV Virtual IO Module manual.

DeltaV Configuration

The DeltaV configuration involves creating the DeltaV Serial Device placeholder, as well as adding the dataset configuration. For more information on this component configuration, please refer to the Ethernet/IP Master Driver for DeltaV Virtual IO Module manual. Below you will find the configuration information for the DeltaV Dataset which refers to Assembly Instance 1.

  1. To establish communications after the Prog. Serial Cards have been Auto Sensed, please configure the DeltaV P01 Properties. For this example we will use the configuration as shown below:
  2. Create a DeltaV Device that matches the configuration within VIMNet Explorer. In this example, the screenshot below illustrates the configuration for the 1769-L35E CompactLogix.
  3. Create the DeltaV dataset as Input. The DeltaV data type can be any supported type and should match the data type in the Logix module (Step 8 below). Note that the DeltaV data type of "Floating point with Status" is the same as the Logix module data type of "Real." In this example, we have used "Comm Format" / "DeltaV Data Type" of INT / 16 bit uint w/Status.
  4. Set the Device Data type in DeltaV to 15. Use starting address 0 and the maximum number of values as 100. The number of values should also match the Logix module size. You can use fewer values than 100. If the dataset is a type floating point, the maximum number of values is 50.

CompactLogix Configuration

This procedure will walk you through the configuration of the 1756-Generic ENBT Modules necessary for Class 1 communications with the Virtual IO Module.

  1. In the RSLogix 5000 system, right click on 1769-L35E Ethernet Port LocalENB as shown below and select "Properties."
  2. Confirm and accept the IP address part of the network configuration
  3. Now, right click on 1769-L35E Ethernet Port LocalENB again and select "New Module." A window similar to the screenshot below will appear. As it appears, expand Communications and select the "1756-ENBT 1756 10/100 Mbps Ethernet Bridge, Twisted-Pair Media."
  4. Then click "OK" to add the module. This module corresponds to the VIM card.
  5. Configure the module as shown below. The specified IP address is for the VIM card. Specify the Slot number as 0 and the Chassis size as 32. This will allow you to add a maximum of 32 ENBT connections into the VIM. Select all other parameters as shown.
  6. Next, right click the ENBT module corresponding to the VIM and select "New Module" as shown below. This is where the DeltaV dataset connections are added.
  7. From the presented list of modules, select the 1756-Module as shown below.
  8. Specify the properties of the 1756-Module. This module is equivalent to the DeltaV dataset. Specify the name corresponding to the DeltaV dataset or some other meaningful string. In the Assembly Instance column, the Input and Output parameters are the dataset index numbers. In this example, these are specified as 1. Valid range for these parameters is 1-128. This parameter is calculated based on the target card/dataset to which the ENBT is mapped. For example, if the VIM is emulating serial cards 57-60, then the following applies, where each card has 32 datasets:
    Prog. Serial Card Calculated Assembly Instance
    57 1-32
    58 33-64
    59 65-96
    60 97-128
    To map an ENBT module to Card 57, Port 2, Dataset 1, use an instance parameter of 17. To map an ENBT module to Card 59, Port 1, Dataset 5, use an instance parameter of 69.
  1. The Input and Output size parameters should match the number of values in the DeltaV dataset. Configuration parameters should always be specified as shown. Lastly, specify the Comm Format. The Comm format corresponds to the DeltaV data type. For example, INT corresponds to 16-bit unsigned int. For this example, we will use the settings shown below: *Note: Specify a value of 129 for each Generic 1756 Module's Configuration Instance.
  2. Click "Next" to specify the Packet interval. The following dialog is shown. Specify the time as 400ms. This parameter specifies how frequently the Logix will update the VIM. For few (less than 8) datasets, an RPI of 200ms may be used. For more than 16 datasets, the RPI may have to be adjusted up to the maximum (slowest) rate of 750ms. Click "Finish" to complete the module configuration. Configuring an RPI of less than 100ms is not recommended. The VIM will not be able to keep up with messages from Logix, causing datasets to have bad status.
  3. To add a new dataset connection, go back to Step 6 and add a new module.
  4. The final configuration with 4 ENBT connections will appear as follows:

At this point, the datasets in DeltaV correspond to a specific ENBT module in the Logix controller. Configuration of additional data points would follow the steps outlined above. By nature, this mechanism is very fast and suitable for highspeed data transfers from the Logix I/O sub-system into DeltaV.

Summary

In summary, we found no problems in using the 1769-L35E Compact Logix with DeltaV and the Virtual IO Module. Communication speed and performance was as expected and we had no problems with the device in setup or testing. As long as the CompactLogix interface does not change between different models, the interface using a Class 1 EtherNet/IP Connection to interface with the IOD-4102 Ethernet/IP VIM Driver will follow the procedure above.