This application note describes the process for integrating the DeltaV Virtual IO Module with an FMC722 TPU using firmware IOD-4105.
There may be times during the integration process where referencing the Virtual IO Module Manual is recommended or necessary to proceed. A link to the manual is located below:
FMC Subsea Driver for DeltaV Virtual IO Module (IOD-4105) - PDF
The following software components are required for the integration process:
This application note assumes that the user has already configured the TPU using the SmartTool software suite. For questions/information regarding the configuration of the TPU, contact FMC Technologies.
Open SmartTool KS200e. The TPU configuration file should load automatically on launch.
Select "SCU interface admin" under TPU A in the tree view. Set the IP Address and Subnet Mask of the TPU in the property fields marked by the red box on the right side of the window.
Select "SCU interface" under "SCU interface admin" in the tree view. Set the Port number of the TPU in the property field marked by the red box on the right side of the window. Save the configuration.
Right-click on the root of the tree view ("Field"), then select "Export > SCU-int-1: Export std. IO-list for branches as text file..." Save the text file and close SmartTool KS200e.
Open VIMNet Explorer.
Expand "Physical Network," then right-click on "I/O Net" and select "New Controller."
Name the contoller place holder in the dialog window, then click "OK."
Right-click on the newly created controller, then select "New IO VIM."
Configure the parameters in the dialog window as shown above. IP Address and Subnet Mask refer to the IP Address of the Virtual IO Module and the Subnet Mask of the network on which the Virtual IO Module resides. If you are running DeltaV version 10 or earlier, or you are using M-Series IO, be sure to check the checkbox in the upper-right corner of the window.
If you click "Edit" in the Configuration Version, the following dialog window will appear:
This dialog contains parameters that allow the user to keep track of the current configuration version loaded on the Virtual IO Module. The Major and Minor fields are determined manually by the user, whereas the Upload parameter is automatically incremented with each new configuration uploaded to the Virtual IO Module. This tracking system serves only as an informational tool - configuring these parameters will have no impact on the functionality of the Virtual IO Module.
When you have finished configuring the new Virtual IO Module, click "OK."
Right-click on the newly created Virtual IO Module, then select "Import FMC TPU File."
Select the text file exported from SmartTool KS200e in Step 1, then click "Open."
Expand the "Field" node in the tree view of the dialog that appears, then right-click on TPU-A and select "Assign TPU."
Configure the highlighted parameters in the dialog window to correspond to the connected TPU. The IP Address and Port parameters are not stored in the TPU configuration file used during the import procedure, so you will need to ensure that those values are entered correctly at this prompt.
After the IP Address and Port parameters are configured, click the highlighted "Create" button. This will create a Control Dataset in the VIM Configuration for the TPU time sync parameters.
After all of the parameters have been configured, click "OK" to return to the original import dialog.
Right-click on the TPU configured in the previous step, then select "Add Tags."
A dialog like the one shown above will appear. Click "OK" to close the dialog and import the tags associated with the device. Dialogs will continue to appear for every device in the TPU configuration file. Continue to click "OK" until all of the devices are configured.
Repeat the above procedure for adding tags for any other TPUs listed in the TPU configuration file.
This is what the Tag Import dialog will look like after all tags have been imported into the VIMNet configuration. Note that all of the nodes in the tree view with assigned tags are shown in bold font and that the "Assigned" parameter matches the "Count" parameter in the statistics table on the right side of the dialog.
Click "Exit" to close the dialog.
After importing all of the device tags, the VIMNet configuration should be similar to the one shown in the image above.
Right-click on the Virtual IO Module placeholder, then select "Export FHX File."
Select a save destination and a filename for the exported file, then click "Save."
After you select the save destination for the export file, a dialog will appear asking for the name of the DeltaV OPC Server. If the DeltaV OPC Server is not the local machine, you will need to specify a server name. Click "OK" when you are finished.
After you specify the DeltaV OPC Server name, a dialog will appear asking for the DeltaV version and user name of the DeltaV machine. Select the appropriate version and specify the appropriate user name in the fields shown above. If you want the names of the TPU device tags to be shown on the description fields of the DeltaV dataset registers, check the "Export Registers" box. When you are finished, click "OK."
Save the VIMNet configuration and close VIMNet Explorer.
Open DeltaV Explorer.
Right-click on "Control Network,"then select "New > Controller."
A new controller will appear in the main window of DeltaV Explorer and will be ready to be renamed. Rename the controller to the same name you gave to the controller placeholder in VIMNet Explorer.
After the controller has been renamed, right-click on the new controller in the DeltaV Explorer tree view, then select "Properties."
Under the "Model/Software Revision" panel, select the model of the DeltaV controller in use with your system, then select the major/minor revision numbers of your DeltaV software installation. When all of the parameters have been configured, click "OK."
Once the controller is properly configured, go to the "File" menu and select "Import > Standard DeltaV Format..."
(Note that if you are using DeltaV 11.3.1, you will need to migrate the 11.3 version .fhx file exported from VIMNet Explorer. To do this, go to "Start > (All) Programs > DeltaV > Engineering > Database Administration," then open the "Migrate Configuration" program from the administration panel.
Select the .fhx file you wish to import into the DeltaV database, then click "Open."
The import progress will be displayed in a window, detailing each step of the procedure and noting any errors that occur during the import process. When the import completes, click "Close."
The image above shows an example TPU configuration imported into DeltaV. Note that all of the dataset registers have their associated TPU tags listed in the Description field.
Now that the configuration is complete, you will need to commission a DeltaV controller to the placeholder in the DeltaV Explorer tree view, then download the configuration to the commissioned controller.
This concludes the FMC722 TPU integration procedure. If you have any further questions, please contact MYNAH Support by opening a support ticket from your MYNAH My Account.
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.