Knowledge Base /
Release Notes
ODVA EtherNet/IP VIM2 Release Notes
By Nobin William
Product: DeltaV Virtual IO Module - VIM2

These notes are for the first release of the ODVA EtherNet/IP VIM2 firmware v1.0.0. The flash procedure is documented in the product manual.


The Virtual I/O Module with the ODVA EtherNet/IP Driver provides the following compatible functions using CIP (Common Industrial Protocol) as defined in the EtherNet/IP Specification from Open DeviceNet Vendor Association & ControlNet International.

DeltaV I/O space comprises a maximum of 4 Serial or DeviceNet cards. A mix of 4 Serial and DeviceNet cards are supported in Simplex mode. In Redundant mode, the configuration is forced to 4 Serial card pairs. Each Serial card has 32 datasets with user configurable data types, e.g., Boolean, Integer, etc. Each dataset is an array of 100 Integer (or 50 Floating point) values. The 32 datasets per Serial card may be user configured to 32 individual devices with one dataset per device. Or multiple datasets may be configured under a single device, thus reducing the available datasets accordingly. With 4 Serial cards, the total number of devices available is 128 (with one dataset per device).

When mapping to DeltaV DeviceNet cards, a maximum of 244 devices may be configured per card. DeviceNet cards are non-redundant, hence these are supported only in Simplex mode. Each DeviceNet device has a maximum of 255 signals of various data types. Data from field devices are mapped to DeviceNet device signals. Note that the 244 device maximum under DeviceNet emulation is a configuration limit. As a practical implementation, network performance and data throughput must dictate the number of devices connected per VIM.

The following diagram shows the DeltaV network architecture and the role of the ODVA VIM2 Network Gateway.

The DeltaV system with S-series VIM2 and Ethernet I/O integration (simplex VIM2 and DeltaV controller shown)

Release Components

IOD-4116 EtherNet/IP Driver V1.0.0
VIMNet Explorer V9.3.0
ControlLogix Browser V1.0.0

What's in this document

1. Field Communication Brief discussion of supported EtherNet/IP messaging
2. VIM Configuration Steps required to configure a VIM2 with ODVA driver
3. Add Serial Connection Adding a connection to be used under a Serial Card
4. Add DeviceNet Connection Adding a connection to be used under a DeviceNet card
5. Add Network Devices Adding field network devices user Serial and DeviceNet cards
6. Add Connections to Network Devices Adding Serial and DeviceNet connections to field devices
7. Generating DeltaV FHX file Exporting the configuration as FHX file for import into DeltaV
8. Tag Browser Brief description for the Tag Browser Application
9. Flash Procedure Describes the steps to flash the firmware into a VIM2

Field Communication

The Virtual IO Module ODVA EtherNet/IP Driver provides communications with field device as follows:

Implicit Messaging

  1. Class 1 Messages – Class 1 connections are producer/consumer connections where both sides continuously send data at a predetermined rate. This is intended for connections to IO field devices. This type requires a TCP session to be established between devices, a forward open message then establishes the Class 1 connection and data is subsequently sent via the UDP socket (2222). This includes both scanner connections (initiated by VIM) to assembly instances in IO field devices or adapter connections accepted from Logix controllers (ENBT Adapter access). RPI is assigned in VIMNet for VIM initiated connections (i.e., where the VIM is the Scanner), or in the Logix configuration when VIM is the adapter. Both read and write buffers are updated to/from the field at these intervals; writes from DeltaV are by exception and trigger an immediate write to the field. The message sent is prepended with a 16-bit sequence count value incremented only when the application updates the application production data.
    Client Transport Meaning
    Cyclic Message production is triggered by the Transmission Trigger Timer.
    Chage of State Message production is triggered when the application production data has changed and by the Transmission Trigger Timer.
    Application Object Triggered Message production is triggered when the application updates the application production data and by the Transmission Trigger Timer.

Explicit Messaging

  1. Unconnected Messages (UCMM) - Unconnected messages use a TCP session and are intended as master/slave connections to send data to field devices under the control of the master. The VIM will be the master when using UCMM messaging. Writes are by exception, reads are continuous at the interval configured for the connection. The following are supported aspects of UCMM messaging:
    1. Class/Service - Class Service messaging supports access to any EtherNet/IP device via available classes in given device.
    2. DF1 - Client DF1 messages allow VIM's to connect to SLC's, PLC5's, and other legacy Rockwell devices (in addition to ControlLogix type PLC's) via PCCC objects. Additionally, these messages are used to connect VIM's to devices on DH485 or DH+ networks via bridges or EtherNet/IP to serial converters like the 1761-NET-ENI.
    3. Tag Access - ControlLogix PLC Tag access is configurable as a client. A configuration utility is used to browse available tags in a L5X export file. This is limited to accessing global and user defined tags, and globally marked AOI tags in the PLC. Reading tags from an online processor over the network will be supported in future versions.

      All tags will be read/written at the level of tag specified for connection (a single path is enabled for a tag). For example, if the tag is an array of 100 registers, user may specify the first element of the array or start somewhere in the middle of the array. The tag data at the specified level is mapped into the input/output buffer.

      Tag access type will be read, write, or write with read-back. For write access tags the VIM (DeltaV) will be considered the master of the data, for read only the ControlLogix PLC is the master.

      Read/Write access to the following tag types is supported. Tag data type may be BOOL, SINT, INT, DINT, REAL or BOOL ARRAY.

      a. Atomic tags, i.e., tags with a single value;
      b. Lists of atomic tags configured in the VIMNet Explorer;
      c. Tags which comprise arrays in the Logix controller, or subset of array tags;
      d. Structure tags with data of different types. For example, see ComplexTag1 below.

      The following excerpts are from a RSLogix configuration showing an atomic tag, a tag array and a tag structure, respectively.
Atomic Tag
Tag Array
Tag Structure
  1. Class 3 Messages – Class 3 messages use a TCP connection to establish a link between sender and receiver, and then both sides send their data via the TCP session. Message formatting is of UCMM type as described above. Currently these messages only support DF1 communications to DH+ via the Rockwell DHRIO module.

    Note that this class of messages are available under Serial Card emulation only.

VIM Configuration

The VIMNet Explorer is used to configure the VIM2 and the ODVA driver. Launch the Explorer to see the following top level interface:

VIMNet Explorer

Click the Physical Network to select the NIC on your computer as shown. The Explorer will access the VIM network via this NIC.

VIM Network Settings

Click the Decommissioned VIMs to see the list of available, decommissioned VIM's in the LAN.

Decommissioned VIMS

Right Click I/O Net to create a Controller as follows:

New Controller

Right Click the Controller and select New IO VIM. Specify the VIM properties as follows:

VIM01 Properties

Specify the driver type as ODVA, emulated DeltaV I/O card range, VIM IP address and sub-net mask, and the mix of Serial and DeviceNet cards emulated by the VIM. Click OK to create the VIM placeholder. The Explorer will show this as follows:

VIMNet Explorer

Right Click the VIM placeholder and select Commission. Then select a decommissioned VIM from the list as follows:

Commission VIM

Click OK to complete the commissioning process. The Explorer will show the result as follows:


With the VIM commissioned, we can now configure the field devices and connections. We will configure a Serial device using Tag access and a DeviceNet device using Class 1 Scanner messages. Connection definitions are stored in VIMNet Explorer libraries, with connection instances added to the IO tree.

Add Serial Connection

To add a new Serial card connection definition, select “Add Connection Definition” from the Serial Card definition library branch of the IO tree. This connection will use the UCMM Tag Access methodology to read a Tag array called TestTag.

Add Connection Definition
Connection Definition

Specify Library name or leave it blank. If blank, the VIMNet Explorer will fill in a default name for the connection. Select the Msg Type as UCMM and Tag Access. Specify the Tag Name to be read, the tag data type and the number of values. In this case, the tag TestTag is an array of Floating Point values. Lastly, specify the Update Period as 500ms. The VIM will read the tag every 500ms. The Slot Address and Port specify the location of the Logix CPU card in the chassis. The Browse button launches the Tag Browser application which provides online and/or L5X imported file based browsing of the ControlLogix configuration. Details of the Tag Browser are documented in the user manual.

Click on the DeltaV Serial Card Mapping tab to see the following. The Tag is automatically mapped to a floating point dataset. If required, the byte order of the data may be adjusted. For this Logix data, the default is as shown.

DeltaV Serial Card Mapping

Click OK and the connection definition will be added to the Serial library and appear as follows:

VIMNet Explorer

Add DeviceNet Connection

To add a new DeviceNet card connection definition, select Add Connection Definition from the DeviceNet definition library branch of the IO tree. This is a Class 1 Scanner connection is to a Rockwell E1 Overload Relay.

Add Connection
Connection Definition

Specify Library name or leave it blank. If blank, the VIMNet Explorer will fill in a default name for the connection. Select the Msg Type as Class 1 IO Message and Scanner. The Device Type will be Generic Module, which allows definition of a Class 1 Scanner connection to any EtherNet/IP adapter field device. The Msg Details tab allows configuration of the parameters of the connection. These may be entered manually or by loading an EDS file by clicking the EDS Details button.

Click the EDS Details button to display the following dialog:

EDS Parameters

Click the Load EDS button and browse for the vendor supplied .eds file. Consult device manual to select appropriate connection points and data sizes. Data sizes depend on the configuration of the field device. The Input Type may be Multi Cast or Point-to-Point, depending on field requirements. Outputs to the field device are always Point-to-Point. Click OK to return to previous level.

EDS Parameters

When the EDS definition is complete, Input and output assembly instances (connection points) and corresponding data sizes are configured and displayed as follows:

Connection Definition

Click on the DeltaV DeviceNet Mapping tab to see the following dialog.

DeltaV DeviceNet Mapping

Under the Inputs tab, in the Input Buffer Definition section, click Add to map data received from the field device to DeviceNet Signals. Signal editing is done in a dialog as follows. Output signals are similarly defined under the Outputs tab.

DeviceNet Signal Definition

The detail display of the library definition shows details of the definition, including the prototypes of the signal names and the buffer locations.

Connection Details

Add Network Devices

Select Add Device from the Port on the Serial mapped card in the IO tree. In the Device definition dialog select the network device IP address or add a new one. Add extended addressing if required, e.g, when communicating with PLC's on DH+. Select OK to update the IO tree with the new device instance.

Add Device

This device is a ControlLogix PLC. Click Add to specify the IP address, then click OK.

Add EtherNet IP Connection
Enter IP Definition for Device
Add EtherNet IP Connection

Select Add Device from the Port on the DeviceNet mapped card in the IO tree. Add a second device placeholder to represent the E1 Overload Relay as follows:

Add Device
Aadded Devices with User Specified IP Addresses.

Add Connections to Network Devices

ControlLogix Connection under Serial card

Right Click on the C59, Port P01 and Device Dev01. Select Add Connection from the network device context menu in the IO tree. The following dialog will be displayed.

From the Ethernet Library Definition list, select the specific definition for this connection. Note that only valid connections will appear in this list. Select OK to add this to the IO tree under the network device. The VIMNet Explorer will show the following:

VIMNet Explorer

E1 Overload Relay Connection under DeviceNet card

Right Click on the C57, Port P01 and Device Dev01. Select Add Connection from the network device context menu in the IO tree. The following dialog will be displayed.

EtherNet IP Connection

From the Ethernet Library Definition list, select the specific definition for this connection. Note that only valid connections will appear in this list. Select OK to add this to the IO tree under the network device. The following dialog will be displayed. In this dialog you can edit the name and address (from 1-61 per DeviceNet card) that will be used in DeltaV to identify the device and device signals. Then click OK.

DeviceNet Device Properties

The VIMNet Explorer will show the following mapped device in the 10 list with all signals, DeltaV tags, and field 10 definitions for the connection.

VIMNet Explorer

Generating VIM Configuration as FHX file

An FHX file containing the IO definitions may be generated for import into DeltaV as follows. Various DeltaV versions up to v12.3 are supported. This FHX export functionality and subsequent import into DeltaV shortens the development cycle and eliminates reconfiguration of VIM IO cards in the DeltaV Explorer.

Export FHX File

Tag Browser

The Tag Browser is an application embedded in the VIMNet Explorer. When launched, it allows importing a RSLogix L5X export file. Once the configuration is in the Tag Browser, user can manually select Tags to be included in the VIM scan.

The following dialog shows an imported PLC configuration.

Tag Browser

Flash Procedure

The ODVA Driver v1.0 release requires a two step flash procedure as follows:

  1. Flash the VIM2 to ODVA Base line using the file: ODVA_Vim2_v100_baseline.hex
  2. Flash the VIM2 a second time using the file: ODVA_Vim2_v1.0.0.2817.hex

Who should upgrade?

Any user who wants the following functionality:

  1. Access ControlLogix Tags and other general purpose EtherNet/IP devices;
  2. Large number of field devices;
  3. Mapping of data to DeviceNet signals; and
  4. Redundancy (not supported under DeviceNet cards. Supported only as Serial cards).

What's New in This Release?

This driver is the first release.

The following defects were corrected:


The following enhancements were implemented: