Knowledge Base /
Integration Guides
DeltaV/Eaton 9000x AF Drive Configuration
By Geoff Nash
Product: IOD-4114 - Generic Device Ethernet IP Scanner Driver for DeltaV VIM2

This technical note describes the configuration of the VIM with Generic Ethernet/IP Firmware for access of the drive from DeltaV. Other parameters may be accessed using UCMM messaging, not discussed in the document.

The Eaton 9000x series AF Drives have Ethernet/IP support with the OPTCK option board. This board supports Class1 access to assembly points and Explicit message (UCMM) support for access to class attributes.

VIM Configuration

This section describes the configuration of a VIM connection to a 9000x series drive. It assumes the user is familiar with configuring the VIM and using the VimNet Explorer Utility.

This device requires one Class1 connection to be configured. To create a connection definition, right-click on the "EthernetIP Connection Library" in the VimNet IO tree. Select "Add Connection Definition".

Add A Connection

This opens the definition properties dialog.

Definition Properties Dialog


In this dialog you may create a name for the connection definition. If no name is specified, a default name will be generated on exit. Make sure the connection message type is “Class1”, and select the "Msg Properties" button to open the Special Data dialog for configuring the Class1 connection access parameters.

The Class1 connection in this example is from the Eaton “Ethernet/IP Option Board OPTCK for 9000X Drives” User Manual (September 2010) figure C4 (Logix5000 Generic Module Properties) and tables 4-19 (Assembly 101) and 4-28 (Assembly 107). The VIM functions the same as does the Rockwell Generic Ethernet Module, so this specifies an appropriate configuration for the connection.

This control connection uses Originator to Target (DeltaV to Drive) connection point (assembly instance) of 101, with 8 bytes of data and the Run/Idle header added to the message. The drive return data is from connection point 107, is also 8 bytes (including the header bytes) and no run/idle header. For this connection the default RPI was used, this might need tuning if may other connections are in use.

Special Class1 Connection Properties

The Configuration Connection instance should be set to 1, and the connection is cyclic. When the definition is completed, select "OK" to return to the connection definition dialog.

Note that now the input and output defined registers are set to 8 bytes each.

Connection Properties with data

This connection need only use one dataset in DeltaV, so the base dataset is configured as a 16-bit unsigned integer output dataset with read-back. As there are 8 bytes of input and 8 bytes of output data, the 16-bit dataset will use 8 registers. No extension datasets are required.

DeltaV Dataset Configuration

Now you need to map the Ethernet/IP buffers to the DeltaV dataset. The right side of the properties dialog has two grids, one for input (Drive to DeltaV) and one output (DeltaV to Drive) mapping. You may map either side first; each grid maps sequential elements in the Ethernet/IP buffer to the registers in DeltaV. For this example, we will map the outputs first. This results in the outputs being in the first registers in the DeltaV dataset. For this, add one mapping element. Select "Add" in the Output Buffer Definition (VIM to Adapter).

Data Mapping Section
This opens the element dialog. This opens with the next available offset byte into the buffer selected (0 in this case) and the base dataset (the only one available). Select all 8 bytes here and "OK" to add this to the list. Once added this may also be accessed by selecting the "Edit" button with the element highlighted or double clicking on the element. While the element properties dialog is open, an option here is to add field names. Select "Fields" button.
Element Map Fields Select

The "Ethernet/IP Buffer Fields" dialog opens. In here you may add all fields that are in the mapped buffer area for the element. Each field may have a data type appropriate for the field. Here there are discrete bits added to the first and second bytes, and three unsigned integers to the remaining bytes:

Mapping Element Fields Dialog

These values are not transferred to the VIM but are present in VimNet Explorer as an aid in configuring DeltaV.

This is repeated for the Input Buffer Definition (Adapter to VIM). Once completed, the Connection properties dialog is complete:

Connection Configuration

Select "OK" to complete the editing of the definition and to add it to the Ethernet/IP Connection Library in VimNet Explorer.

You will now see the connection:

Ethernet Library Definition Listing

Now add a device to represent the 9000X series drive to the IO tree. Right-click on the desired port an select "Add Device."

Add A Device to the Port

This opens the "Device Properties" dialog. Add an IP address and specify the device address. This is important as the device IP address in the VIM is determined by this address. If the address does not correspond, there will be issues in communications to the field. You may limit available connection definitions in this dialog. And also add an extended address, if required.

Device Properties Dialog

Next, add the connection definition to the Device. Right-click on the device and select "Add Connection."

Devices Add Connection Menu

In the Connection dialog select the appropriate library definition form the "Ethernet Library Definition" combo box and "OK" to save the new instance in the IO tree under the device. It is possible to assign a description of this connection instance.

Ethernet Connection Instance Properties

The detailed view of the connection in the IO tree shows the parameters, as configured in the library definition, including the fields assigned in the mapping elements, names, and DeltaV addresses.

Connection Detail View

FHX File Export

The IO card definition may be exported using the VIM context menu. Right-click on the VIM and select "Export FHX File." Select the location (and name) for saving the FHX file. If there is a DeltaV OPC server available (other than the local machine), enter the name in the "Select ProPlus" dialog. If this is the ProPlus, then this may not be necessary. If no OPC server is available, you will be prompted for the DeltaV version profile file.

VIM Context Menu Export FHX File Item and Export Version Selection Dialog

Select "OK" and the file is created.

DeltaV Configuration

In DeltaV, import the FHX file from VimNet. Select "File," "Import," and "Standard DeltaV Format…" Browse to the location of the FHX file and select. This will process the FHX file and create the four VIM cards in the DeltaV controller IO tree. For this to work, the DeltaV controller name must match that in VimNet Explorer. You may also manually enter the cards. If done manually, make sure the DeltaV tree definitions match those in VimNet, including device and dataset order. Also make sure all four cards (57-60, or 61-64) are defined, even if no IO is assigned to some.

The Eaton 9000X series connection was tested in DeltaV using the a module for reads and writes. The input parameters are detailed in figures below.

DeltaV Module Input and Output Landing Parameters

Please contact us for any questions about this technical note at:

MYNAH Technologies
390 South Woods Mill Road, Suite 100
Chesterfield, MO 63017 USA
+1 636 728 2000 (voice)
+1 636 728 2001 (fax)
email: support@mynah.com