Knowledge Base /
Integration Guides
DeltaV Integration with a Turck FGEN-XSG16-5001 Utilizing the Virtual IO Module 2
By Chandler Est
Product: IOD-4117 - Profinet Driver for DeltaV VIM2

This integration guide describes the recommended settings for integrating the Turck FGEN-XSG16-5001 Module to DeltaV utilizing the Emerson Virtual IO Module 2 (VIM2) with the MYNAH IOD-4117 PROFINET Driver.


INTRODUCTION


Resources

  1. Turck FGEN-XSG16-5001 User Manual from the Turck Website
  2. Turck FGEN-XSG16-5001 Data Sheet from the Turck Website
  3. The PRONETA User Manual from the Siemens Website
  4. VIM Help Files

Hardware Requirements

  • DeltaV Virtual I/O Module 2 (VIM2) VE4026: M-Series or SE4026: S-Series
  • DeltaV Controller
  • (2) DeltaV 2-Wide
  • (2) DeltaV Power supply
  • Turck FGEN-XSG16-5001 Module and Power Cord

Software Requirements

  • DeltaV System Software (Release 10.3 or later) installed on a hardware-appropriate Windows workstation as a ProfessionalPlus Workstation for DeltaV (requires license)
  • DeltaV Explorer
  • DeltaV Diagnostics
  • DeltaV Control Studio
  • VIMNet Explorer (v9.4 or later)
  • Simulation Firmware v2.5.6 or later
  • MYNAH Technologies PROFINET Driver (IOD-4117)
  • Turck FGEN-XSG16-5001 Module GSDML file from the Turck Website
  • PRONETA from the Siemens Website

Guide Assumptions

This guide walks through the process of integrating the Turck FGEN-XSG16-5001 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 FGEN-XSG16-5001 User Manual. Lastly, it is assumed that the user has installed PRONETA and is familiar with the basic use of VIMNet Explorer and DeltaV Explorer. For PRONETA, installation may require addition of secondary Windows files and GSDML files - the user will be prompted if this information is needed.


INTEGRATION


Theory of Operation

The DeltaV VIM2 provides a native DeltaV I/O interface to the Turck FGEN-XSG16-5001 Module via an open plant PROFINET network and protocol. This firmware allows the VIM2 to behave as an IO Controller in a PROFINET network, linking IO Devices to the DeltaV system. The PROFINET devices are presented to the DeltaV controller as PROFIBUS devices. This firmware is compatible with PROFINET 2.2, published by PROFIBUS & PROFINET International. The firmware only supports Real-Time communications, and does not support Isochronous Real-Time communications.


Turck FGEN-XSG16-5001 Module Configuration

To begin the integration process, physically connect the Turck device to the desired PROFINET network via the ETH01_IN ethernet cable. The device is shipped with a default IP address, and this must be altered for the device to be available on the end-user PROFINET Network. Ensure the switches on the top of the device, beneath the clear cover, are physically turned to '500' in order to allow PRONETA to write the device name to the Turck internal memory. Open PRONETA, and select "Network Analysis" as shown below:

Figure 1. PRONETA Home Screen

In the next window, select "Online Topology" to view all devices responding to the PROFINET network requests. The Turck device should appear automatically, but with an IP address of 0.0.0.0 or some other default IP Address. Right-click the Turck icon, and select "Configure Device" to generate the following window:

Figure 2. PRONETA Configuration Screen

At this point, assign a name to the Turck device - this name will be used to identify and assign an IP Address to the Turck device. In this application note, the name "turck-fgen-xsg16-5001" was assigned. There is no need to specify an IP address, as this functionality can be handled through VIMNet Explorer. At this time, the device is properly configured and the system is ready for VIM2 configuration.


VIMNet Configuration

It is assumed the user has successfully flash upgraded a VIM2 to the MYNAH IOD-4117 PROFINET driver. As a reminder, to properly flash upgrade to IOD-4117, the user should flash the VIM2 to the latest version of Simulation firmware before flash upgrading to the PROFINET 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 a PROFINET Connection Definition for the Turck device by right-clicking "PROFINET Connection Definition" and "Add Connection Definition," as shown below:

Figure 3. VIMNet Explorer "Add Connection Definition"

A pop-up window will appear that asks the user to import a GSDML file for the device. Browse to the location where the Turck GSDML file is saved and select "Open" as shown below. 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.

Figure 4. GSDML File Import

Once the GSDML file is imported into VIMNet Explorer, the pop-up window will auto-populate with information parsed from the GSDML file. In this particular case, there are several different Turck FGEN models, so the "Access Pt" dropdown menu was adjusted to "DAP 4" in order to select the XSG16 model, as shown below. In replicating this guide, ensure that all fields in the user's file are identical to the ones displayed here.

Figure 5. GSDML Import Configuration

Now that the connection definition has been established, the user can create a VIM2 I/O Net Placeholder for the PROFINET VIM2 and "Add Connection" at the port level for the Turck device. This is shown below:

Figure 6. VIMNet Explorer "Add Connection"

A pop-up window resembling the one below will appear. In the "Name" field, copy & paste the name assigned earlier in PRONETA and press "OK." This will be used as the identifier needed to provide an IP Address to the Turck device.

Figure 7. VIMNet Explorer Device Configuration

When this window closes, a second pop-up window will appear that is similar in fashion to the first. In the "Description" field, the user may provide a unique word / phrase to help with organization, though this identifier will not be used in specifying the IP Address. However, if the user selects the "Edit" icon, the first pop-up will re-open, allowing re-configuration of the device if necessary. Press "OK," and the device should appear in the I/O Net tree. Browse all the way to the bottom layer of the device configuration, and select "Properties," as shown below:

Figure 8. VIMNet Explorer / DeltaV Device ID Match

This window governs how a PROFINET 3rd party device is mapped to one or more PROFIBUS devices for communication with DeltaV. This Device ID number must match the ID number in DeltaV, else the device will not communicate properly. By default, this number increments in VIMNet Explorer, so this entry was given Device ID 2, the next Device ID 3, etc. 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. 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.


DeltaV Configuration

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:

Figure 9. FHX Import

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:

Figure 10. Product of FHX Import

At this point, it is imperative to verify that the Device ID specified earlier in VIMNet Explorer matches that in DeltaV. To do so, right-click the PROFIBUS device that contains the Turck Device signals (C57PB2 in the image above). The following pop-up should appear, and the number listed in the "Address" drop-down must match the one in VIMNet Explorer. If they do not match, adjust the number in DeltaV.

Figure 11. DeltaV Address Check

Download the controller, and DeltaV should begin communicating with the Turck device automatically. As communications are initiated, the VIM2 assigns the configured IP Address from VIMNet Explorer to the Turck device. If PRONETA is still open on the user's machine, this can be verified in the "Online Topology" window as shown below:

Figure 12. PRONETA Check

When the Turck device begins communications with the controller, the Bus LED light on the device will change from a flashing green light to a solid green light. 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 input DI and DO blocks, and link them to the corresponding DSTs generated by the FHX import. The mapping of the physical connections of the Turck device to the signals generated in VIMNet Explorer (and therefore passed into DeltaV) can be inferred from the Turck FGEN-XSG16-5001 Product Data Sheet; for this application note, the first two signals of both the input and output tags were tested. To ensure read commands were accurately implemented, a signal was physically forced on C0 and C4 of the Turck device (refer to the Turck FGEN-XSG16-5001 Product Data Sheet for a diagram explaining this nomenclature), and the discrete values in the DI modules reflected this change, as shown below, verifying communications from DeltaV's standpoint. Additionally, LEDs on the physical device will turn green when communicating, as a verification of communications from the device's standpoint.

Figure 13. DeltaV "Read" Command Check

Verifying the Write commands is slightly simpler. In the On-line View, change the DO setpoints from 0 to 1, and the green communications LEDS mentioned above will appear on the device, and the outputs of the DO blocks will change from 0 to 1. Lastly, the user may open DeltaV Diagnostics to verify communication integrity for each of the signals in a list view, shown below:

Figure 14. DeltaV Communications Check

At this point, DeltaV has been fully integrated with the Turck-FGEN-XSG16-5001.


Please contact MYNAH Technologies for any questions about this integration at:

MYNAH Technologies
390 South Woods Mill, Suite 100
Chesterfield, MO 63017 USA
1.636.728.2000
support@mynah.com