Knowledge Base /
Integration Guides
DeltaV Integration with Mettler-Toledo JagExtreme Using Ethernet/IP
By Geoff Nash
Product: DeltaV Virtual IO Module - VIM2

This technical note describes the recommended settings for integrating Mettler-Toledo JagExtreme scales using the Generic Device Ethernet/IP Driver for the Virtual IO Module.

Introduction

The JagExtreme allows class1 implicit, class3, and unconnected (UCMM) explicit connections via EthernetIP from the VIM (Virtual I/O Module) in a DeltaV IO rack. This TechNote details the procedure for creating a Class1 connection. For class1, the JagExtreme acts as a server, with the DeltaV controller receiving from and/or writing data to locations in the JagExtreme Assembly tables. These assembly areas are mapped in the JagExtreme to data tags that are used in its logic. There are several types of Class1 access to the data--this document describes our default definition file (vdf) for the Class1 access to the Floating Point assembly area. These assembly areas are continuously updated between the JagExtreme and the VIM. For details of the connection, see the Mettler Toledo CIP Interface Technical Manual for the JagExtreme (A16760300A 02-05). MYNAH supplies one connection definition file (vdf file) that may be imported and used as is or as a start for configuring the actual connection definition. Once this has been defined, it may be added to the configuration of any VimNet Explorer vio definition, and multiple instances of the definition may be added to the DeltaV configuration.

The size of the assembly area array that needs to be included in the communication connection message buffer is dependent on the assembly area being accessed. It is necessary to transfer the complete data table, however only those sections of the definition that are to be used need be included in the DeltaV dataset mapping. Using this method, the communications is initialized (and the size and timing of the communications messages determined) by the VIM.

Since this is a mix of data types, the connection to DeltaV is “mapped” to allow the use of several DeltaV datasets with different data types that hold values from different portions of the data buffers of the connection, depending on the type of data in the buffer. The mapped connections are used to transfer complex data structures between the two systems.

JagExtreme Configuration

The JagExtreme may be configured using any browser such as Microsoft Internet Explorer. In the address bar, type the IP address of the JagExteme HTTP server connection. When the window opens, select "Communications," ControlNet PLC Interface then specify the connection parameters your system requires. It is important you set the “Data Format” to the type you are accessing via the Class1 connection. If you do not, the unit will accept connections but not send data. This will cause continuous connection failures with the timeout dependent on the connection parameters in the VIM. You must also have a ControlNet card in the JagExtreme to communicate with. The IP address of this card the one specified in the VIM setup. The HTPP card will not accept EthernetIP connections.

VIM Configuration

This section provides information for configuring JagExtreme connections to the VIM. It assumes the user is familiar with configuring the VIM using the VimNet Explore utility.

Open the VimNet Explorer. If the appropriate configuration is not already loaded, create a configuration containing the VIM and JagExtreme Device. Right-click on the “EthernetIP Connection Library” leaf in the navigation panel on the left of the display. Select "Import Connection Definition" or “Add Connection Definition” to create a new one (see Figure below).

Next, right-click on the definition and select “Properties." This opens the “VIM_EtipBufferMapping” Utility shown in Figure below.

This is the utility that allows the configuration of the connection between the VIM and the Jag Extreme. This figure shows the definition of the JagExtreme_Class1_FP.vdf module we supply as a starting point.

If you wish, you may enter a new name in the “Library Name” field. Then edit the Etip Buffer section below. Make sure the message type radio button (Class1) is checked, and the ENBT field is unchecked.

The “Input” and “Output” fields show the selected number of bytes that will be included in the communications message buffers. The Input specifies the size of the JagExtreme to VIM (target to originator or TO), which is the assembly data in the JagExtreme that will be transmitted to the VIM, while the Output specifies the bytes transmitted from the VIM to the JagExtreme (Originator to target or OT). The defaults for the JagExtreme are 32 and 36 for the floating-point assembly area. These are fixed values for this area and should not be changed.

Next, select the “MsgParameters” button to open the “SpecialData” utility (Figure below). This utility allows you to examine, enter or modify the necessary parameters to configure the actual Ethernet/IP Class1 connection. For the JagExtreme, these are fixed for each assembly instance and should be left at or set to that value. First enter the Connection Points for the connection. Specify parameters for Originator to Target (OT) and Target to Originator (TO) connections from the Table 1.


In Table 1, the Originator (VIM) to Target (JagExtreme) is set to 4 to specify the Floating point data area. The values may be 2 or 4. Next, the Target (JagExtreme) to Originator (VIM) should be 3, to specify the floating-point area. The mapping for all the I/O area tables are shown in Table 1.

Both OT and TO connections should be set to “Scheduled” and Inhibition “Default." The OT connection should be “Point to Point” while TO should be “MultiCast." Make sure the OT connection has the “Run/Idle Header” checkbox checked and the TO does not. Now set the RPI (requested packet interval) to the required interval. This is the expected time for the JagExtreme (TO) and VIM (OT) to send data messages. The Data size for both of these was set using the “VIM_EtipBufferMapping” utility.

Finally, you need to set the overall connection parameters. These are the “Use Slot Addressing” (unchecked), Transport Trigger, “Cyclic,” and Timeout Multiplier (4). Leave the Configuration Connection at 0.

The last step in the SpecialData words is to select “OK” to save these parameters into the current connection definition, or “Cancel” to keep the last values in the VIM_EtipBufferMapping” utility.

In the VIM_EtipBufferMapping” utility, select the datasets to map these connections to. Since there is mapped data with float and non-floating point data, this will require two datasets. In Figure below, the first dataset is configured as a 16-bit unsigned integer output (with read-back). The second dataset is configured as a floating-point output dataset with read-back. This allows the connection to read discrete and unsigned integer data to one set of values and floating point to the second set. Input and output will be presented in these datasets, so they are set as output with read-back.

Next, you can see that specific registers are mapped to the transfer buffer. Each element points to a specific range of bytes in the buffer and maps these to the specific dataset registers for that type (or specifies them as unmapped). The first column show the buffer offset for the element. The second shows the datatype of the dataset which it is assigned to. The next column shows the index of the dataset (0 is the base, 1-5 is the extended set).

Double-click (or select the “edit” button) in the EthernetIP Input Buffer Definition (Adapter to VIM) to access the Input Definition.

This dialog allows the user to view and select the dataset (0: UINT16_WITH_STATUS for integer, and 1: FLOAT_WITH_STATUS for the floating-point inputs) for each section of the buffer to be used.

Selecting the “Fields” button will open a dialog (Ethernet/IP Buffer Fields) shown in Figure below that will allow the you to enter a series of field definitions. Each field may specify a JagExtreme tag definition assigned to the assembly table(s) for the connection.

Each field is added by selecting the “Add” button, then filling out the parameters (including the data type of the field), the starting byte in the field, and bit (if a bit field). Also, the size (elements) may be set if the field is an array of the data type.

Finally, select “OK” on all of the dialog boxes to accept the configured values. You are returned to the VimNet Explorer “Ethernet IP Connection Library” with the new definition added. To add this to the VIM configuration select the Node, the specific VIM, card, port and device for the connection, then, then right-click on the device and select “Add Connection.” In the dialog box, add a description and select the specific connection definition from the “Ethernet Device Definition” combo box. The connection is added to the list and the next available dataset(s) in DeltaV are assigned. You can open this connection by selecting the plus (+) in front of it, and examine the definition of each assigned dataset here. When configuring the actual DeltaV datasets (DeltaV Explorer) you may use these definitions as a reference.

DeltaV Configuration

The actual connection between the JagExtreme and DeltaV is configured in VimNet Explorer. The DeltaV dataset(s) assigned in DeltaV Explorer may be on any card (57-60) / port (1-2) and device, but they must match the definition as specified in VimNet Explorer. One or more datasets may be assigned to a connection as necessary. The first dataset defines the connection; the remaining datasets for the connection (if required) must immediately follow the first.

To start, use the DeltaV Explorer to select the device, right-click, and select “New Dataset” to open the Dataset properties dialog. Select the data direction of the connection data for this dataset. If you are assigning an output assembly instance (AO) to the data, this would be “Output.” If the assembly instance was input (AI), then use “Input." Refer to the VimNet Explorer definition of the dataset for actual requirements.

The DeltaV tab of the dataset property box is used to select the data type of the data that will be presented. This should be appropriate for the data that will be accessed in the JagExtreme. If the data in the assembly table is floating point, only a floating point dataset in DeltaV is appropriate as noted above. Mapping of datasets in the connection will allow this to be assigned separately from integer and bit registers.

On the PLC tab, the “Device data type” may be specified, but is not required. If specified, the first dataset associate with the connection is specified with a device data type of 39 (mapped EthernetIP Class1 client) on the PLC tab remaining dataset are assigned 36 (EthernetIP extension data). In addition, the number of values on this tab will determine the size of the connection data read/written from this dataset. The number of registers in the associated datasets mapping elements determines the total data in both directions, by the data direction, type, and size in each dataset.

All words on the special data tab should be 0 (any values here are ignored).

DeltaV Input Field Xreferences

These are the fields read from the JagExtreme based on the definition shown in the DeltaV Register. The JagExtreme sends these at the interval specified in the RPI (Request Packet Interval) for the connection. The values are updated to the DeltaV datasets on any change. The values in the buffer represent 4 scales (S1 to S4). Any group not required for an application may be deleted from the mapping grid in the “VIM_EtipBufferMapping” utility.

DeltaV Output Field Xreferences

These are the fields written to the JagExtreme based on the definition shown in the table below. Writing to any of these tags will be written immediately. The values in the buffer represent 4 scales (S1 to S4). Any group not required for an application may be deleted from the mapping grid in the “VIM_EtipBufferMapping” utility.

Data Access

For the JagExtreme, commands are written to the output register in the unsigned integer dataset. If a floating-point value is required for a command, it is written to the matching register in the floating point dataset. If no command is written, the JagExtreme will continuously cycle through the scale data values in the input registers. See the JagExtreme documentation for a compete description of the required commands and expected input results.