Knowledge Base /
Integration Guides
DeltaV Integration with a SMC EX600-S Using ODVA EtherNet/IP VIM2
By Jay Chard
Product: IOD-4116 - ODVA Driver for DeltaV VIM2

This integration guide describes the recommended settings for integrating the SMC EX600-S EtherNet/IP compliant embedded interface to DeltaV utilizing the Emerson Virtual IO Module 2 (VIM2) with the MYNAH ODVA EtherNet/IP driver. The EtherNet/IP (bus in) M12 connector embedded on the device is used for network communication.



Hardware Requirements
DeltaV VIM2 VE4026: M-Series or SE4026: S-Series - MYNAH Technologies ODVA EtherNet/IP Driver IOD-4116
DeltaV Controller
(2) DeltaV 2-Wide
(2) DeltaV Power Supply
SMC EX600-S EtherNet/IP Compliant device
EtherNet/IP communication cable EX9-AC020EN-PSRJ Cable with M12 connector (device vendor)
Software Requirements
DeltaV System Software (Release 10.3 or later) installed on a hardware-appropriate Windows workstation as a ProfessionalPlus Workstation for DeltaV (requires license)
DeltaV Explorer
DeltaV Diagnostics
DeltaV Control Studio
VIMNet Explorer (v9.4 or later)

Guide Assumptions

  • The user has an installed a SMC EX600-S with appropriate I/O connected to the system.
  • The user is familiar with VIMNet Explorer, DeltaV, and SMC EX600-S basic operation.


Jump to SMC EX600-S Configuration
Jump to VIMNet Configuration
Jump to DeltaV Configuration

Theory of Operation

The DeltaV VIM provides a native DeltaV I/O interface to the SMC EX600-S via an open plant Ethernet network and EtherNet/IP protocol. DeltaV controllers can read and write signals to the EX600-S residing on this Ethernet network. As such, the VIM exists as a Network Gateway between DeltaV controllers and the external EX600-S nodes. This connectivity is illustrated below:


SMC EX600-S Configuration

Because a generic connection between DeltaV and the SMC EX600-S will be made, it is recommended to review the “Connecting with Allen Bradley PLC (EtherNet/IPTM master)” and “I/O Map” sections of the SMC EX600-SEN# Operation Manual.

The following section was summarized from the aforementioned manual:

  1. Configuring the I/O
    The SI unit will use a Generic Ethernet Module connection of which at least 1 byte must be set for the Input Size. If system diagnostics is used, the input size equals 4, 6, or 12 bytes based on the chosen diagnostic data dip switch settings. The SI unit also uses an output byte size based on the dip switches set for number of occupied valve outputs; thus utilizing 1, 2, 3, or 4 bytes for the Output Size. When I/O units are installed, the Input and Output Size settings must be increased according to the occupied byte size of such I/O unit.
    • Input Size: By changing the diagnosis switch, the diagnostics data shown below is assigned to the head of input data of the I/O map.
      Input Size Settings
    • Output Size: The SI unit (EX600-SEN) of the product has its own output occupied byte(s).
      Output Size Settings
  2. Using the I/O

The terms ‘input’ and ‘output’ are defined from the DeltaV controller’s point of view. Therefore, output I/O is data that is produced by the controller and consumed by the adapter. Input I/O is status data that is produced by the adapter and consumed as input by the controller.

Each unit of the product has its own I/O occupied byte(s).

I/O Map

I/O Map Occupied Bytes

I/O Map Assignment

Input data: SI unit Diagnosis bytes + Summation of Occupied Input unit bytes

Output data: Summation of Occupied Output unit bytes + SI unit Output bytes


Input data

Output data


System diagnosis bytes

Occupied Output unit byte(s)

Occupied Input unit byte(s)

SI unit Output byte(s)


For a complete detailed example, please consult the “Diagnostic” section of the SMC EX600-SEN# Operation Manual.

EtherNet/IPTM Objects
To write to additional accessible SMC parameters not configured in the I/O assemblies, Explicit Messaging is used. The MYNAH ODVA EtherNet/IP driver supports Unconnected Explicit messaging (Class Service Client). Each Explicit Message request requires an additional dedicated connection.

The following classes exist for the EX600 series:

  • System Object (Class 66h)
  • Unit/Channel Diagnosis Object (Class 67h)
  • Details of Channel Diagnosis Object (Class 77h)
  • Unit Parameter Object (Class 78h)
  • Channel Parameter Object (1) (Class: 79h to 7Fh)
  • Channel Parameter Object (2) (Class: 83h to 8Ah)

For a complete list of accessible Class Instance Attributes (CIAs), please consult the “EtherNet/IPTM Object” section of the SMC EX600-SEN# Operation Manual.

VIMNet Configuration

Use the VIMNet Explorer utility to configure the VIM card. Open VIMNet Explorer. Expand VIMNet and Physical Network until I/O Net is displayed, as in the image below. Right-click on I/O Net and select “New Controller”.

New Controller

A prompt will appear asking for a controller name. The name of the controller used in this example is shown below.

Name Controller

Expand I/O Net until the new controller (labeled “CTRL1” in this example) is displayed. Right-click on the controller and select “New IO VIM”.


A prompt will appear requesting specific configuration information about the new I/O VIM. For configuring the VIM to work with the SMC node, enter a valid IP address on the device network and select the appropriate parameters based on the VIM type.

VIM Placeholder Properties
Expand the controller and the newly created I/O VIM, then expand C57 to show the two ports attached to Card 57. Right-click on P01 and select Add Device.
Add Device

Set the IP Address to the IP Address of the SMC EX600-S IP. Click “Add” to define the IP addresses for the device.

Enter Device IP Address

After the IP Address is selected, add a description and click OK.

Device Properties

A new device should now appear under the first port of Card 57. This device is the EtherNet/IP compatible SMC EX600-S. VIMNet Explorer configures the VIM to map a DeltaV Device Address to an IP address in the field.

VIMNet Device Description

The TCP portion has now been mapped to DeltaV. In order to complete the EtherNet/IP connection, a properly configured connection definition needs to be added to the configured device. To map a connection definition right-click “Serial Card EthernetIP Definition Library” and select “Add Connection Definition”.

Add Connection Definition

Assign a Library Name and select Class1 IO Message – Scanner (Originating Client) Msg Type. Leave Slot unchecked.

EtherNet/IP Interface Definition

Class1 IO Messaging is unique for every device. For this example we have used Diagnostics Mode 1 with 4 bytes of diagnosis data. Additionally, the number Output size has also been configured with the default 4 byte setting representing the number of occupied valve outputs on the SI unit. I/O units have not been configured in this example:

EtherNet/IP Interface Settings

In the ‘Requested Packet Interval (RPI)’ box, set the value to 200 milliseconds or greater (default is 200 milliseconds). This value determines the interval that a controller will use to move data to and from the adapter. To conserve bandwidth, use higher values for communicating with low priority devices. An RPI of 200 is used for this example.

Assembly instances may consist of multiple data formats. A DeltaV dataset may only be configured as a single data type. The DeltaV Serial Card Mappings tab is used to map the data points in the assembly instances to one or many datasets. Datasets may be defined with different data types.

DeltaV Serial Card Mapping

In the example below, 4 diagnosis bytes of the EtIP Buf have been mapped to the first four registers (DS Offset 0) of an UINT8_WITH_STATUS (Output w/ Readback) dataset.

DeltaV Serial Card Mapping Inputs

In the example below, the 4 output bytes of the EtIP Buf have been mapped to registers 5-8 (DS Offset 4) of an UINT8_WITH_STATUS (Output w/ Readback) dataset.

DeltaV Serial Card Mapping Outputs

Next assign the Connection Definition to the device defined in VIMNet Explorer by right-clicking on the device and selecting “Add Connection”.

Add Connection

The connection and the single defined datasets will appear under the device. The dataset will inform the user of the exact configuration parameters required for the DeltaV datasets.

Dataset Parameters

These dataset may be manually replicated in DeltaV Explorer (See Section 2. Configuring a DeltaV Controller to Communicate to the SMC EX600-S) or exported to a FHX file from VIMNet Explorer. To export an FHX, first enable FHX exports by right-clicking on VIMNet and selecting properties. Proceed to enable the “FHX Export Enabled” checkbox.

VIMNet Properties

Then, right-click on the VIM node and select “Export FHX File”. When using FHX exports, please make sure the controller defined in VIMNet Explorer utilizes the same name of the controller defined in DeltaV.

Export FHX File

Right-click on the VIM placeholder under the controller node and select Commission.


Select the VIM connected to the backplane containing the DeltaV controller and click OK.

Commission VIM

The VIM is now ready to be uploaded to start communicating to the field. An upload is not recommended until DeltaV has been configured.

Below is a connection definition example of a Class-Instance-Attribute (CIA) request for Unit Operating Condition 1 data in the SMC’s System Object class (66h). The value returned (BYTE) is a bit mask of errors detected in units 0 – 7.

Explicit Message Example

For a list of VIM supported EtherNet/IP connection types, see EtherNet/IP Interface Definition.

DeltaV Configuration

Launch DeltaV Explorer. Expand System Configuration, then expand Physical Network. Right-click on Control Network and select New->Controller.

Add New Controller

Give the controller a name, then right-click the controller and select commission. Select the controller from the decommissioned nodes list. If the controller does not appear on the decommissioned nodes list, please investigate the DeltaV network.

Commission Controller

When prompted Auto-sense the I/O cards. The I/O card may be auto-sensed because we have already configured in the VIM in the previous section. If the DeltaV is configured before the VIM, these cards will need to be manually added or auto-sense later.

Auto-sense DeltaV I/O cards

Expand C57, then right-click on P01 and select Properties.

Port Properties

Check the Enable box for the port, then click OK.

Enable Port

Next, right-click on P01 under C57 and select New Serial Device.

Add New Serial Device

Ensure that the “Device Address” parameter is set to the same node address assigned to the device in VIMNet Explorer.

Device Properties

Right-click DEV01 under P01 and select New Dataset. A dataset will be created for each dataset defined under the connection definition in VIMNet Explorer.

DeltaV Dataset

The dataset configuration is strictly based on the defined connection definition. Please replicate the parameters specified for the datasets in VIMNet Explorer. If there an exact match does not exist between the uploaded configuration in VIMNet Explorer and the DeltaV Explorer configuration, the user may be presented with a configuration mismatch error. A quick way to overcome this error is to import the FHX file generated from VIMNet Explorer.

Finally, right-click on the DeltaV controller and select Download; choose to download the whole controller.

Download Controller

DeltaV is now ready to communicate to the SMC EX600-S in the field. The Class1 IO parameters have now been fully migrated across the Ethernet network via EtherNet/IP to the VIM card and presented to the DeltaV serial dataset channels.

Please contact MYNAH for any questions about this integration at:

MYNAH Technologies
390 South Woods Mill, Suite 100
Chesterfield, MO 63017 USA