This integration guide describes the recommended settings for integrating the Turck BL20-PG-EN-IP Module to DeltaV utilizing the Emerson Virtual IO Module 2 (VIM2) with the MYNAH IOD-4116 ODVA EtherNet/IP driver.
|DeltaV VIM2 VE4026: M-Series or SE4026: S-Series - MYNAH Technologies ODVA EtherNet/IP Driver IOD-4116|
|(2) DeltaV 2-Wide|
|(2) DeltaV Power Supply|
|Turck BL20-PG-EN-IP EtherNet/IP Compliant device|
|DeltaV System Software (Release 10.3 or later) installed on a hardware-appropriate Windows workstation as a ProfessionalPlus Workstation for DeltaV (requires license)|
|DeltaV Control Studio|
|VIMNet Explorer (v9.4 or later)|
|Simulation Firmware v2.5.6 or later|
|MYNAH Technologies ODVA EtherNet/IP Driver (IOD-4116)|
|CoDeSys from the Turck Website|
This guide walks through the process of integrating the Turck BL20-PG-EN-IP Module with the VIM2 and DeltaV. In this application note, it is assumed the user is familiar with the necessary procedure of installing / powering up the Emerson VIM2 hardware. Additionally, the guide assumes all hardware, including the Turck Module, is installed and ready for integration. For questions on how to install the VIM2 hardware, please refer to the VIM2 Help Files, and for questions on how to install the Turck Module, please refer to the Turck BL20 User Manual. Lastly, it is assumed that the user has installed CoDeSys and is familiar with the basic use of VIMNet Explorer and DeltaV Explorer. For CoDeSys, installation may require addition of secondary Windows PC.
The DeltaV VIM2 provides a native DeltaV I/O interface to the Turck BL20-PG-EN-IP Module via a plant Industrial Ethernet network and open EtherNet/IP protocol. This firmware allows the VIM2 to behave as a Class 1 IO Client on the network, linking a Class 1 IO Server to the DeltaV system. The EtherNet/IP devices are presented to the DeltaV controller as either Serial devices or DeviceNet devices. This firmware is compatible with the Open DeviceNet Vendors Association (ODVA) EtherNet/IP specification. The firmware supports both Implicit Client/Server and Explicit Client functionality.
To begin the integration process, physically connect the Turck device to the desired Ethernet network via the 10/100 Mbit Ethernet port. The IP Address is determined by setting the 3 rotary switches on the front of the Module.
Please see section 4.6 of the BL20 – User Manual Programmable Gateway for EtherNet/IP for additional information on setting the device Address. Communications between the nodes in the EtherNet/IP network can be carried out either via I/O Messages or Explicit Messages. The majority of the guide outlines the connectivity of I/O Messages which serve to exchange high priority process and application data over the network.
Section 6.0 of the BL20 – User manual programmable Gateway for EtherNet/IP to setup the BL20-PG-EN-IP with CoDeSys programming software for EtherNet/IP communications. In order to enable EtherNet/IP communication of BL20-PG-EN-IP with other EtherNet/IP nodes, the EtherNet/IP input and output words have to be added to the PG configuration. The output data coming from an external client are mapped as input data in the PG. The output data from the PG are input data on the PLC-side.
In CoDeSys, under the “Online” menu option select “Communication Parameters”. The device is defined with the following parameters:
On the resources tab, select “PLC Configuration”. The IO modules can now be defined in proper slot order. Memory addresses are auto-assigned to these I/O modules.
Add the necessary input and output words to the PG configuration under the “EtherNet/IP Words [SLOT]” section. Again, memory addresses are auto-assigned to these transmit words.
It is assumed the user has successfully flash upgraded the VIM2 to the MYNAH IOD-4116 ODVA EtherNet/IP driver. As a reminder, to properly flash upgrade to IOD-4116, the user should flash the VIM2 to the latest version of Simulation firmware before flash upgrading to the ODVA EtherNet/IP driver. If unsure as to how to flash upgrade a VIM2, MYNAH has released a guide in the online VIM help files here that can serve as a template.
In VIMNet Explorer, the user must specify either a Serial Card EthernetIP Definition or DeviceNet EthernetIP Definition. For this example, a Serial Card EthernetIP Definition will be used to form the connection between DeltaV and the VIM. Proceed to right-click on “Serial Card EthernetIP Definition Library” and “Add Connection Definition”, as shown below:
A pop-up window will appear that asks the user to configure the EtherNet/IP Interface Definition as well as the DeltaV Serial Card Mapping. This connection definition is not tied to one particular instance of a specific device, i.e. this connection definition can be used to integrate more than one Turck device of the same make and model into DeltaV.
Tab 1 represents the EtherNet/IP Interface which defines the Ethernet connection between the VIM and the device in the field.
According to the BL20 – User Manual, when configuring the Generic Ethernet Module its assembly instance parameters must be set as follows.
Tab 2 represents DeltaV Serial Card Mapping which defines the Railbus connection between the VIM and the DeltaV Controller IO.
The user has the ability to choose which bytes from the EtherNet/IP data stack they desire to map into DeltaV datasets. The example above assumes all avilable 128 input words and all avilable 128 output words are mapped backed to DeltaV. Since a DeltaV dataset is restricted to 200 bytes, two datasets were used for input values and two datasets were used for output values.
Now that the connection definition has been defined, the user can create a VIM2 I/O Net placeholder for the ODVA EtherNet/IP VIM2. First, add a device with the Turck IP Address under a desired serial card port, next “Add Connection” of the newly created connection definition to this device. This is shown below:
VIMNet auto-generates the necessary dataset configuration required to bridge the connection between the DeltaV Controller and Turck device.
At this time, the VIM2 may be commissioned and the configuration uploaded. Refer to the online VIM2 Help Files if unsure how to perform these actions. The user may now proceed to prepare the DeltaV system for communication with the Turck device. These datasets may be manually created in the DeltaV Controller’s I/O tree. Mismatched configuration errors will generate if the DeltaV configuration does not match the VIMNet configuration. VIMNet Explorer has the capability to export a DeltaV FHX file from the card level to help with generation of DSTs in DeltaV, and it is recommended the user take full advantage of this functionality. Save the FHX export file to a convenient location.
Unconnected Explicit Messaging connection definitions may also be configured to transmit low-priority configuration data, general management data, or diagnostics data between DeltaV and the device. Below showcases the configuration to get a status message from the TCP/IP Interface Object:
A full list of data available with Explicit Messaging is located in section 5 of the BL20 – User Manual Programmable Gateway for EtherNet/IP.
It is assumed that the user has already created a new DeltaV database and ProfessionalPlus station. To begin integrating the Turck device into DeltaV, create a new controller in DeltaV Explorer and provide it the same name as the Node in VIMNet Explorer. This is a strict requirement to ensure the FHX import from the VIM2 above functions properly. Once the controller has been created, proceed to commission it and autosense the DeltaV cards emulated by the VIM2. This operation may take a few minutes, but once complete, cards 57-60 (or 61-64, depending on how the user originally specified the VIM2 configuration) should appear. At this time, import the FHX file saved above by following the procedure outlined in the image below:
When the pop-up window appears, browse to the FHX file and select “Open.” The file should automatically import the Turck signals and DSTs as shown in the image below:
Download the controller. DeltaV should now begin communicating with the Turck device automatically. As communications are initiated, the VIM2 flags the controller with new data, which in turn, the controller polls from the VIM. Likewise, when data is ready to write from the assigned controller module, the controller communicates this data to the VIM registers, which in turn, the VIM sends to the device. The connection gateway is established with “Online -> Login”. Download the program to the gateway and start it with “Online -> Run”. I/O can now be observable between DeltaV and the PG.
Data can now be observed online with CoDeSys.
To verify proper communications between DeltaV and the Turck device, the user can create modules and assign them to the controller in DeltaV. In these modules, the user can create input and output blocks, and link them to the corresponding DSTs generated by the FHX import. The mapping of the physical connection of the Turck device to the signals configured in VIMNet Explorer (and therefore passed into DeltaV) can be inferred from the Turck BL20-PG-EN-IP User Manual; for this application note, the second output word is now observable in the 3rd configured register (R3) in the first input dataset (R1 is reserved or a status header).
DeltaV Diagnostics is a good tool for diagnosing status issues on bad datasets as well as quickly viewing input data with the “View Dataset Registers” right-click selection.
At this point, DeltaV has been fully integrated with the Turck BL20-PG-EN-IP.
Please contact MYNAH for any questions about this integration at:
390 South Woods Mill, Suite 100
Chesterfield, MO 63017 USA
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.