This technical note describes the recommended settings for integrating the Allen-Bradley 193-ETN module using Class1 messaging via IOD-4104 Ethernet/IP Virtual I/O Module. This document is specifically intended for the application of the 193-ETN and the E1 Plus with a Virtual I/O module. For configuring the 193-ETN for use in other applications, see the manuals/documentation pertaining to the specific application hardware (download links in Introduction).
The procedure for interfacing the Allen-Bradley 193-ETN module with a Virtual I/O Module is comprised of three main parts: VIMNet Explorer Setup; DeltaV Explorer Setup; and Control Studio Setup. There may be cases in which specific information pertaining to the components mentioned in this document must be referenced. In the case of such an event, please refer to that part's documentation (download links are listed below). To better understand both interfaces please look over the manuals below before proceeding forward.
Allen-Bradley 193-ETN PDF
Generic Ethernet/IP Driver for DeltaV Virtual I/O Module Web Help
The following procedure assumes that the IP Address of the Allen-Bradley 193-ETN has already been configured, however, the user must keep in mind that the configured IP Address of the Allen-Bradley 193-ETN must be an address that the Virtual I/O Module can reach. One way to reconfigure the IP Address is to use the 193-ETN's web utility and enter its current IP Address into any web browser's navigation bar. The default credentials for accessing this utility are as follows:
This section provides information for configuring VIMNet Explorer to interface with the Allen-Bradley 193-ETN module. The procedure described below will create a configuration for the VIM that will eventually be downloaded to the VIM. This process is necessary to achieve I/O with the DeltaV MD/MD+ controller.
Open VIMNet Explorer. Right-click on "I/O Net" and select "New Controller."
A prompt will appear asking for the name of the controller. The value for this parameter is at the discretion of the user.
Expand "I/O Net" then right-click on the newly created controller and select "New IO VIM."
A prompt will appear asking for configuration information specific to the VIM. The "Type," "Virtual Cards," and "DeltaV version 10.x or earlier or M-Series IO" fields should be configured as shown in the image above. All of the fields under the "VIM Properties" panel are at the discretion of the user.
Expand the controller, then the newly created IO VIM, and then "C57." Right-click on "P01" under "C57" and select "Add Device."
A prompt will appear asking for configuration information specific to the new device (this device is the Allen-Bradley 193-ETN Module). The "Device Address" field as well as the fields in the "Enabled Msg Types" panel should be configured as shown in the image above. The "Description," "IP Address," and "Device Extended Address" fields are at the discretion of the user.
Right-click on "Ethernet IP Connection Library" under the root "VIMNet" and select "Add Connection Definition."
A prompt will appear asking for configuration information specific to the Ethernet IP Connection Library. The "Library Name" field is at the discretion of the user. To configure the other fields in the "Etip Buffer" panel, click the "Msg Parameters" button.
A prompt will appear asking for configuration information specific to the message parameters of the Ethernet IP Connection Library. In the "Connection" panel, set "Transport Trigger" to "Cyclic," set "Timeout Multiplier" to 4, and set "Configuration Connection" to 120. Make sure that the "Class 1" radio button is selected and that all other fields in the panel are either blank or unchecked. In the "Originator->Target" panel, set "Connection Pt" to 103, set "Priority" to "Scheduled," set "Type" to "Point to Point," set "Data Size" to 1, set "RPI" to 500, and set "Inhibition" to "Default." Make sure the "Run Idle/Header" box is checked. In the "Target->Originator" panel, set "Connection Pt" to 111, set "Priority" to "Scheduled," set "Type" to "Multicast," set "Data Size" to 22, set "RPI" to 500, and set "Inhibition" to "Default." Leave the "Run Idle/Header" box unchecked. Do NOT load the .eds file generated by the Allen-Bradley 193-ETN Webserver Utility. Click "OK" to return to the main window.
To configure the "Extended Dataset Definitions," click the "Add" button under the listbox. "Data Type" should be set to "8 bit unsigned integer" and "Data Direction" should be set to "Output."
To configure the "Ethernet IP Input Buffer Definition (Adapter to VIM)", click the "Add" button on the right side of the panel. "DataSet" should be set to "0: UINT8_WITH_STATUS," "Offset" should be set to 1, and "Bytes" should be set to 1. Leave the "Update Status" and "Unmapped Bytes" boxes unchecked. Repeat this process of adding buffer maps to the "Ethernet IP Input Buffer Definition (Adapter to VIM)" panel until 22 buffer maps are displayed, ensuring that the "Offset" parameter increments by one each time, but keeping all other fields the same as before.
To configure the "Ethernet IP Output Buffer Definition (VIM to Adapter)", click the "Add" button on the right side of the panel. "DataSet" should be set to "1: UINT8_WTIH_STATUS", "Offset" should be set to 0, and "Bytes" should be set to 1. Leave the "Update Status" and "Unmapped Bytes" boxes unchecked. After all of the parameters listed above have been configured, click on the "Msg Parameters" button on the left side of the "EtipBuffer" panel.
After all of the buffer definitions have been added, click "OK" on the main prompt window to return to VIMNet Explorer.
Right-click on "DEV01" under "P01" of "C57" and select "Add Connection."
A prompt will appear asking for configuration information specific to the new connection. In the "Ethernet Library Definition" field, select the Ethernet IP Connection Library created previously. The "Description" parameter is at the discretion of the user.
Expand the newly created connection. There will be two Datasets created under the new connection - one for the input messages and one for the output messages.
Right-click on the VIM controller created earlier and select "Commission."
Select the appropriate VIM from the list of decommissioned VIMs and click "OK."
A blue arrow will appear next to the VIM controller after commissioning - this means that the VIM still requires the configuration in VIMNet Explorer to be uploaded to the VIM hardware. Right-click on the VIM controller and select "Upload Configuration to VIM". Select "Yes" when prompted to save and select "Yes" at the dialogue warning to confirm the upload. Once the upload is finished, a dialogue will appear indicating a successful upload, and the blue arrow that was next to the VIM controller should now be gone.
Open DeltaV Explorer and continue to the next step of the procedure.
This section provides information for configuring the Allen-Bradley 193-ETN connection to the VIM by integrating a DeltaV MD/MD+ controller in DeltaV Explorer.
Right-click on "Control Network" under "Physical Network" and select "New > Controller."
A new controller will appear in the main window of DeltaV Explorer, as indicated by the red arrow in the image above. After the controller has been named, it will be displayed under "Control Network" in the explorer tree.
Expand the newly created controller, then right-click on "I/O"and select "New Card."
A prompt will appear asking for configuration information specific to the new card. Set "Card class" to "Serial Cards," set "Card type" to "2 Ports, Programmable, RS232/RS485," set "Card series" to "Series 2," and set "Slot position" to 57. Leave the "Card is redundant" box unchecked. The "Description" field is at the discretion of the user.
Repeat this process of creating cards three more times, keeping all setting the same, except for "Slot position" - this should be set to 58, 59, and 60 for each of the respective new cards.
After all the necessary cards have been created, expand "C57," then right-click on "P01" and select "Properties."
In the prompt window, make sure that the "Enabled" box is checked. You will need to repeat this process for any additional ports on any other cards in the controller that will have active I/O connections.
Expand "C57" under "I/O", then right-click on "P01" under "C57" and select "New Serial device."
A prompt will appear asking for configuration information specific to the new serial device. Set "Device Address" to 1. The "Description" field is at the discretion of the user.
Right-click on "DEV01" under "P01" and select "New Dataset."
A prompt will appear asking for configuration information specific to the new dataset. In the "General" tab, set "Data direction" to "input." In the "DeltaV" tab, set "DeltaV data type" to "8 bit uint w/status" and set "Dataset Tag" to "AB-193-E57010101". In the "PLC" tab, set "Device data type" to 36, set "Data start address" to 0, and set "Number of values" to 23. Ignore the "Special Data" tab.
Create a second new dataset in the same manner as before. A prompt will appear asking for configuration information specific to the new dataset. In the "General" tab, set "Data direction" to "output" and leave the "Output read back?" box unchecked. In the "DeltaV" tab, set "DeltaV data type" to "8 bit uint w/status" and set "Dataset Tag" to "AB-193-E57010102". In the "PLC" tab, set "Device data type" to 39, set "Data start address" to 0, and set "Number of values" to 1. Ignore the "Special Data" tab.
(If you select the datasets created in VIMNet Explorer using the Ethernet/IP Connection Library that was defined earlier, the main window of VIMNet Explorer will display the configuration parameters required for creating the datasets in DeltaV Explorer. If any changes are made to the configuration in VIMNet Explorer, check the Datasets to see if the requirements for the configuration parameters have changed - this will simplify adjustments and allow for quick setup in other applications.)
(Note that the Dataset tags listed in VIMNet Explorer and the ones used to configure the datasets in DeltaV Explorer do not match. This will not create any issues - rather, this was done intentionally because DeltaV imposes a character limit on the names of Dataset tags and the recommended Dataset tag name in VIMNet Explorer would exceed this constraint.)
After the datasets have been created, right-click on the controller placeholder and select "Commission."
Select the appropriate controller from the list of Decommissioned Nodes, then click "OK." When prompted to auto-sense DeltaV I/O cards for the controller, select "No."
After the controller has been commissioned, blue arrows will appear next to each of the elements underneath the commissioned controller - this is because the controller requires a data download. However, there is not yet anything to download to the controller. A Module must be created with function blocks in order to tell the controller what to do with the data.
To create a Module, right-click "Assigned Modules" and select "New Module."
A prompt will appear asking for configuration information specific to the new module. Set "Object type" to "Control Module or Template" and set "Algorithm type" to "Function Block Diagram." Make sure the "Create New" radio button is selected and leave the "Object is class-based" box unchecked.
Expand "Assigned Modules" under the controller placeholder, then right-click on the newly created module and select "Open > Open with Control Studio."
Open the launched Control Studio window and proceed to the next step.
This section provides information for configuring the Allen-Bradley 193-ETN connection to the VIM by creating a module for the DeltaV MD/MD+ controller in Control Studio.
The above image is an example of a module designed to read/write data to/from several of the registers used by the Allen-Bradley 193-ETN. The example module was constructed solely with Input/Output Parameter blocks and Binary Fan In/Out blocks. Based on the specific needs of the application, create a module using the function blocks available in the toolbox on the right side of the program.
The Input/Output Parameter blocks must be configured properly in order for the model to execute as desired - instructions for doing this are given below.
To configure an Input/Output Parameter Block, double-click on the block in the main window of Control Studio. Set "Parameter type" to "External Reference" and leave "Parameter category" blank. Next, click the "Browse..." button in the "Properties" panel.
In the "Object Type" drop-down menu, select "I/O Parameters." This will set Control Studio to look in the System Configuration for external references. Navigate through "Physical Network," following the hierarchy of the DeltaV controller until you find the register in the dataset you wish to reference. An example reference path would be "AB-193-ETN/IO1/C57/P01/DEV01/DS01/R1."
After the module design is finished, save the module, then click the "Download" button. At the warning prompt, select "Yes" to confirm the download. Leave any checkboxes in the prompt unchecked. A prompt may appear stating that the node has never been downloaded before. If this does appear, select "Yes" to download the entire node. A second warning prompt may appear stating that system files may be missing. Select "Download Anyway" to continue.
Once the download is complete, I/O communication will be established with the Allen-Bradley 193-ETN. You can view the current I/O information by clicking on the "Go On-Line" button in the upper left hand corner of the Control Studio application window.
At this point, the interface has been completed if you have any questions please contact MYNAH Technical Support.
MYNAH Technologies LLC
390 South Woods Mill Road, Suite 100
Chesterfield, MO 63017 USA
© MYNAH Technologies 2012 - 2020. All rights reserved.
Designs are marks of MYNAH Technologies, Emerson Process Management, DeltaV, and the DeltaV design are marks of one of the Emerson Process Management of companies. All other marks are property of their respective owners. The contents of this publication are presented for informational purposes only, and while every effort has been made to ensure their accuracy, they are not to be construed as warrantees or guarantees, expressed or implied, regarding the products or services described herein or their use or applicability. All sales are governed by our terms and conditions, which are available on request. We reserve the right to modify or improve the design or specification of such products at any time without notice.
While this information is presented in good faith and believed to be accurate, Mynah Technologies does not guarantee satisfactory results from reliance upon such information. Nothing contained herein is to be construed as a warranty or guarantee, express or implied, regarding the performance, merchantability, fitness or any other matter with respect to the products, nor as a recommendation to use any product or process in conflict with any patent. Mynah Technologies reserves the right, without notice, to alter or improve the designs or specifications of the products described herein.