Knowledge Base /
Integration Guides
DeltaV Integration with a PowerFlex 755 Utilizing the Virtual IO Module
By Jay Chard
Product: IOD-4116 - ODVA Driver for DeltaV VIM2

This integration guide describes the recommended settings for integrating the PowerFlex 755 EtherNet/IP compliant embedded interface card to DeltaV utilizing the Emerson Virtual IO Module 2 (VIM2) with the MYNAH ODVA Ethernet/IP Driver. The EtherNet/IP adapter, embedded on the main control board in PowerFlex 755 drives is used for network communication.


Introduction


Resources

  1. PowerFlex 755 Drive Embedded EtherNet/IP Adapter User Manual
  2. MYNAH Online VIM Help Files

Hardware Requirements

Software Requirements

  • DeltaV System Software (Release 10.3 or later) installed on a hardware-appropriate Windows workstation configured as a ProfessionalPlus Workstation for DeltaV (requires license)
  • DeltaV Explorer
  • DeltaV Diagnostics
  • DeltaV Control Studio
  • VIMNet Explorer

The embedded EtherNet/IP adapter stores parameters and other information in its own nonvolatile storage (NVS) memory. You must, therefore, access the adapter to view and edit its parameters. The following tools can be used to access the adapter parameters (please see the PowerFlex 755 Drive Embedded EtherNet/IP Adapater User Manual for additional information):

  • PowerFlex 20-HIM-A6 or 20-HIM-C65 HIM
  • BOOTP server
  • Connected Components Workbench software, version 1.02 or later
  • DriveExplorer software, version 6.01 or later
  • DriveExecutive software, version 5.01 or later

Guide Assumptions

The user has an installed a PowerFlex 755 with appropriate I/O connected to the system and is familiar with VIMNet Explorer, DeltaV, and the chosen PowerFlex drive configuration software.


Integration


Theory of Operation

The DeltaV VIM provides a native DeltaV I/O interface to the PowerFlex 755 embedded communication module via an open plant Ethernet network and EtherNet/IP protocol. DeltaV controllers can read and write signals to the PowerFlex 755 residing on this Ethernet network. As such, the VIM exists as a Network Gateway between DeltaV controllers and the external PowerFlex 755 nodes. This connectivity is illustrated below:

Connectivity

PowerFlex 755 Configuration

Because a generic connection between DletaV and the PowerFlex will be made, it is recommended to review the “Using the RSLogix 5000 Generic Profile, All Versions” section of the PowerFlex 755 Drive Embedded EtherNet/IP Adapter User Manual.

Because the adapter always uses the 32-bit Logic Status, 32-bit Feedback, and a 32-bit word dedicated for memory allocation of the Generic Ethernet module profile, at least three 32-bit words must be set for the Input Size. The adapter also uses the 32-bit Logic Command and 32-bit Reference, requiring at least two 32-bit words for the Output Size. If any or all of the drive’s sixteen 32-bit Datalinks are used, the Input and Output Size settings must be increased accordingly.

Input Size: Start with 3 words and add 1 word for each Datalink used to read data. For example, if 3 Datalinks—[DL To Net xx] parameters—will be used to read drive or peripheral parameters, add 3 words to the required 3 words for a total of 6 words. You can use adapter Parameter 35 - [DLs To Net Act] to check the total number of Datalinks being used. Word 0 is a pad word, Word 1 is Logic Status, Word 2 is Speed Feedback, Word 3 is DL To Net 01, and so forth.

Input Size

Output Size: Start with 2 words and add 1 word for each Datalink used to write data. For example, if 7 Datalinks—[DL From Net xx] parameters—will be used to write to drive or peripheral parameters, add 7 words to the required 2 words for a total of 9 words. You can use adapter Parameter 34 - [DLs From Net Act] to check the total number of Datalinks being used. Word 0 is Logic Command, Word 1 is Speed Reference, Word 2 is DL From Net 01, and so forth.

Output Size

In this manual, Datalinks are not used in the DeltaV and VIMNet Configuration example.

Using the I/O
The terms "input" and "output" are defined from the DeltaV controller’s point of view. Therefore, output I/O is data that is produced by the controller and consumed by the adapter. Input I/O is status data that is produced by the adapter and consumed as input by the controller.

The Logic Command is a 32-bit word of control data produced by the controller and consumed by the adapter. The Logic Status is a 32-bit word of status data produced by the adapter and consumed by the controller.

The Reference is a 32-bit REAL (floating point) word of control data produced by the controller and consumed by the adapter. The Feedback is a 32-bit REAL (floating point) word of status data produced by the adapter and consumed by the controller.

The Reference and Feedback 32-bit REAL values represent drive speed. The scaling for the speed Reference and Feedback is dependent on drive Parameter 300 - [Speed Units]. For example, if Parameter 300 is set to Hz, a 32-bit REAL Reference value of "30.0" would equal a Reference of 30.0 Hz. If Parameter 300 is set to RPM, a 32-bit REAL Reference value of "1020.5" would equal a Reference of 1020.5 RPM. Note that the commanded maximum speed can never exceed the value of drive Parameter 520 - [Max Fwd Speed]. In the DeltaV and VIMNet Configuration example below, RPM is the configured unit type.

The following showcases Parameter 545 - [Speed Ref A Sel]. By setting the Port field to "0 – PowerFlex 755" and the Parameter field to point to the port in which the embedded EtherNet/IP adapter is located (always "Port 13 Reference" – the drive port dedicated to the embedded EtherNet/IP adapter), the Reference commanded form the network can be used for Auto Ref A.

Parameter 545

A Datalink is a mechanism used by PowerFlex drives to transfer data to and from the controller. Datalinks allow a drive parameter value to be read or written to without using an Explicit Message. When enabled, each Datalink occupies one 32-bit word in a controller.

To write to any accessible drive parameter not configured in the drives I/O assemblies, Explicit Messaging is used. The MYNAH ODVA Ethernet/IP Driver supports Unconnected Explicit messaging. Each Explicit Message request requires a dedicated Connection Definition.

The example below showcases the connection required to map the Output Current of the motor to DeltaV. To request the parameter, set Service = E, Class = 9F, Instance = 7, Attribute = 9, and leave the Member = FFFF. The Output_Current is a 4 bytes floating point input so configure the response size 4.

Connection Required to Map the Output Current

Equivalently, map the DeltaV dataset portion as follows:

Mapping the DeltaV Dataset Portion

DeltaV and VIMNet Configuration

1. Use the VIMNet Explorer utility to configure the VIM card.

Open VIMNet Explorer. Expand VIMNet and Physical Network until I/O Net is displayed, as in the image below. Right-click on I/O Net and select "New Controller."

A prompt will appear asking for a controller name. The name of the controller used in this example is shown below

Expand I/O Net until the new controller (labeled “NODE1” in this example) is displayed. Right-click on the controller and select "New IO VIM."

A prompt will appear requesting specific configuration information about the new I/O VIM. For configuring the VIM to work with the PowerFlex node, enter a valid IP address on the device network and select the appropriate parameters based on the VIM type.


Expand the controller and the newly created I/O VIM, then expand C57 to show the two ports attached to Card 57. Right-click on P01 and select "Add Device."

Set the IP Address to the IP Address of the PowerFlex embedded EtherNet/IP module. Click "Add" to define the IP addresses for the embedded EtherNet/IP module

After the IP Address is selected, add a description and click "OK."

A new device should now appear under the first port of Card 57. This device is the EtherNet/IP compatible PowerFlex 755. VIMNet Explorer configures the VIM to map a DeltaV Device Address to an IP address in the field.


The TCP portion has now been mapped to DeltaV. In order to complete the EtherNet/IP connection, a properly configured connection definitions needs to be added to the configured device. To map a connection definition right-click "Serial Card EthernetIP Definition Library" and select "Add Connection Definition."

Assign a Library Name and select Class1 IO Message – Scanner (Originating Client) Msg Type. Leave Slot and User Controls Mapping unchecked.


Class1 IO Messaging is unique for every device. For this example we’ve used the default exclusive owner connection as defined below:

In the "Requested Packet Interval (RPI)" box, set the value to 200 milliseconds or greater (default is 200 milliseconds). This value determines the maximum interval that a controller should use to move data to and from the adapter. To conserve bandwidth, use higher values for communicating with low priority devices. An RPI of 500 is used for this example.

Assembly instances may consist of multiple data formats. A DeltaV dataset may only be configured as a single data type. The DeltaV Serial Card Mappings tab is used to map the data points in the assembly instances to one or many datasets. Datasets may be defined with different data types.

By default, the input assembly instance consist of a 32-bit status header, a 32-bit logic status, and a floating point speed feedback. In the example below, the first 4 header bytes of the EtIP Buf have been unmapped, and the next 4 input bytes have been mapped to the first register (offset 0) of an UINT32_WITH_STATUS (Output w/ Readback) dataset. The last 4 input bytes have been mapped to the first register (offset 0) of a FLOAT_WITH_STATUS (Output w/ Readback) dataset.

By default, the output assembly instance consist of a 32-bit logic command, and a floating point speed reference. In the example below, the first 4 output bytes of the EtIP Buf have been mapped to the second register (offset 4) of an UINT32_WITH_STATUS (Output w/ Readback) dataset. The last 4 outputs have been mapped to the second register (offset 4) of a FLOAT_WITH_STATUS (Output w/ Readback) dataset.

Next assign the Connection Definition to the device defined in VIMNet Explorer by right-clicking on the device and selecting "Add Connection."

The connection and the two defined datasets will appear under the device. The datasets will inform the user of the exact configuration parameters required for the DeltaV datasets.

Notice the Device Data Type value change for DS02.

These dataset may be manually replicated in DeltaV Explorer (See Section 2. Configuring a DeltaV Controller to Communicate to the PowerFlex 755) or exported to a FHX file from VIMNet Explorer. To export an FHX, first enable FHX exports by right-clicking on VIMNet and selecting "Properties." Proceed to enable the “FHX Export Enabled” checkbox.

Then, right-click on the VIM node and select "Export FHX File." When using FHX exports, please make sure the controller defined in VIMNet Explorer utilizes the same name of the controller defined in DeltaV.

Right-click on the VIM placeholder under the controller node and select "Commission."

Select the VIM connected to the backplane containing the DeltaV controller and click "OK."

The VIM is now ready to be uploaded to start communicating to the field. An upload is not recommended until DeltaV has been configured.

2. Configuring a DeltaV Controller to Communicate to the PowerFlex 755

Launch DeltaV Explorer. Expand System Configuration, then expand Physical Network. Right-click on Control Network and select "New->Controller."

Give the controller a name, then right-click the controller and select "Commission." Select the controller from the decommissioned nodes list. If the controller does not appear on the decommissioned nodes list, please investigate the DeltaV network.

When prompted Auto-sense the I/O cards. The I/O card may be auto-sensed because we have already configured in the VIM in the previous section. If the DeltaV is configured before VIMNet the cards will need to be manually added or auto-sense later.

Expand C57, then right-click on P01 and select "Properties."

Check the Enable box for the port, then click "OK."

Next, right-click on P01 under C57 and select "New Serial Device."

Ensure that the “Device Address” parameter is set to the same node address assigned to the device in VIMNet Explorer.

Right-click DEV01 under P01 and select "New Dataset." A dataset will be created for each dataset defined under the connection definition in VIMNet Explorer.

The dataset configuration is strictly based on the defined connection definition. Please replicate the parameters specified for the datasets in VIMNet Explorer. If there an exact match does not exist between the uploaded configuration in VIMNet Explorer and the DeltaV Explorer configuration, the user may be presented with a configuration mismatch error. A quick way to overcome this error is to import the FHX file generated from VIMNet Explorer.

For a list of VIM supported EtherNet/IP connection types, please see the following help document.

Finally, right-click on the DeltaV controller and select "Download"; choose to download the whole controller.

DeltaV is now ready to communicate to the PowerFlex 755 in the field. The Class1 IO parameters have now been fully migrated across the Ethernet network via EtherNet/IP to the VIM card and presented to the DeltaV serial dataset channels.

In this example, one module is assigned to the DeltaV controller. This landing module will read the Logic Status and Speed Feedback parameters of the drive. The landing module will write the Logic Command and Speed Reference to the drive. Landing modules should be created based on the standards of the DeltaV end-user.


Please contact MYNAH 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