You are here: ODVA EtherNet/IP > EtherNet/IP Interface Definition

EtherNet/IP Interface Definition

Connection Definitions map EtherNet/IP data to a DeltaV IO Card. All connection definitions are stored in a Connection Library. Connection definitions are assigned to a field device to create a connection instance.

The EtherNet/IP Connection Definition Properties dialog (Figure 1) is used to configure all of the different EtherNet/IP messaging modes that the VIM supports. The Connection definition dialog may be opened by selecting Add Connection Definition from the connection library context menu or by right clicking on the definition in the library and selecting Properties.   

See DeltaV Serial Card Mapping for more information on the datasets and the element mapping.

See DeltaV DeviceNet Card Mapping for more information on mapping data to DeltaV DeviceNet cards.

Figure 1 - EtherNet/IP Connection Definition Properties Dialog

Library Name

This is the name of the connection definition. This name is used to link a connection definition to a field device. The name can be a maximum of 31 characters long. The name must be unique in a given connection library.

If the name of an existing connection is changed, a copy of the connection will be created with the new name. Any connections that should use the new definition will need to be updated to point to the new name.

Version

This is the last time the connection was modified. This field is automatically updated every time the connection is saved, by clicking OK (Figure 1).

Msg Type

This is a list of all supported messaging types. When a message type is selected the Msg Details section updates to show the required parameters. Some VIM firmwares do not support all messaging types.

EtherNet/IP Messaging Types

Chassis Port ID and Slot ID

Figure 2 - EtherNet/IP Interface Definition Tab with Chassis Port and Slot Visible

Some field devices require a chassis port and slot number included with the messages. Such devices will indicate the requirement in their documentation. If a port and slot ID is required, it can be configured by selecting the Slot check box (Figure 2).

If the Port check box (Figure 2) is disabled, the VIM will use a port ID of 1. This is normally the correct port number. For example, the Allen Bradley 1756-ENBT card uses Port 2 for the Ethernet connection and Port 1 for the chassis backplane connection. If you were accessing a ControlLogix processor, Port 1 is the correct value.

When the Configurable check box (Figure 2) is enabled, the Slot ID becomes disabled. The Slot ID is no longer included with the connection definition and must be configured at the connection instance. See Chassis Slot ID for additional information.

Any path requirements beyond a chassis slot number should be configured in the Device Extended Address parameter of field device.

User Controls Mapping

This check box determines if VIMNet Explorer automatically calculates an EtherNet/IP buffer to DeltaV IO card mapping, or if the user must manually configure it. When the check box is disabled, VIMNet Explorer is automatically creating the data mapping. When the check box is enabled, the user must configure the mapping.

VIMNet Explorer automatic mapping is meant to bring all of the connection's data into DeltaV in the most convenient form. Normally, this is the easiest option. If less data than the connection provides is required in DeltaV, then the automatic mapping can be overwritten, reducing the amount of IO data DeltaV.

When automatic mapping is enabled, when a parameter, such as data type or buffer size is changed, the mapping is updated at the same time.