DeltaV Smart Connector - OSIsoftcdn.osisoft.com/interfaces/2702/PI_DeltaV… · Web view ·...

DeltaV Smart Connector

DeltaV Versions 10.3. or greater

Version 2.0.0.xRevision C

OSIsoft, LLC 777 Davis St., Suite 250San Leandro, CA 94577 USATel: (01) 510-297-5800Fax: (01) 510-357-8136Web: http://www.osisoft.com

OSIsoft Australia • Perth, AustraliaOSIsoft Europe GmbH • Frankfurt, GermanyOSIsoft Asia Pte Ltd. • Singapore OSIsoft Canada ULC • Montreal & Calgary, CanadaOSIsoft, LLC Representative Office • Shanghai, People’s Republic of ChinaOSIsoft Japan KK • Tokyo, JapanOSIsoft Mexico S. De R.L. De C.V. • Mexico City, MexicoOSIsoft do Brasil Sistemas Ltda. • Sao Paulo, Brazil

DeltaV Smart ConnectorCopyright: © 2008-2023 OSIsoft, LLC. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, mechanical, photocopying, recording, or otherwise, without the prior written permission of OSIsoft, LLC.

OSIsoft, the OSIsoft logo and logotype, PI Analytics, PI ProcessBook, PI DataLink, ProcessPoint, PI Asset Framework(PI-AF), IT Monitor, MCN Health Monitor, PI System, PI ActiveView, PI ACE, PI AlarmView, PI BatchView, PI Data Services, PI Manual Logger, PI ProfileView, PI WebParts, ProTRAQ, RLINK, RtAnalytics, RtBaseline, RtPortal, RtPM, RtReports and RtWebParts are all trademarks of OSIsoft, LLC. All other trademarks or trade names used herein are the property of their respective owners.

U.S. GOVERNMENT RIGHTSUse, duplication or disclosure by the U.S. Government is subject to restrictions set forth in the OSIsoft, LLC license agreement and as provided in DFARS 227.7202, DFARS 252.227-7013, FAR 12.212, FAR 52.227, as applicable. OSIsoft, LLC.

Published: 01/2011

http://www.osisoft.com/

Table of Contents

Chapter 1. Introduction...................................................................................................1Reference Manuals............................................................................................1Supported Features...........................................................................................2System Diagram................................................................................................5

Chapter 2. Overview of a Smart Connector..................................................................6Installation..........................................................................................................6Principles of Operation.......................................................................................6DeltaV Configuration Data.................................................................................6

DeltaV Asset Connector Installation Directory.........................................7

Chapter 3. AF 2.0 Object Creation and Configuration.................................................9AF Categories....................................................................................................9AF Element Templates.....................................................................................10AF Elements....................................................................................................10AF Attributes....................................................................................................10

Chapter 4. Installation Checklist..................................................................................11

Chapter 5. Smart Connector Installation.....................................................................13

Chapter 6. Buffering......................................................................................................15

Appendix A. Error and Informational Messages......................................................17Message Logs..................................................................................................17System Errors and PI Errors............................................................................17

Error Descriptions on Windows..............................................................17

Appendix B. Revision History....................................................................................19

DeltaV Smart Connector iii

Chapter 1. Introduction

The DeltaV Smart Connector for the Emerson DeltaV system is a term used to relate all the components needed to allow the new “embedded” option of an Enterprise PI Server and DeltaV Smart Connector on a DeltaV v10.3 Application Station. The Enterprise PI Server is installed separately and integrated into the DeltaV engineering and operations environments much like the DeltaV Continuous Historian. Integration of the embedded Enterprise PI historian is accomplished through the use of a new DeltaV interface known as the DeltaV Smart Connector which includes the: PI AF Client, PI OPC Data Access (DA) interface and the DeltaV Asset Connector. There are three main tasks of the DeltaV Smart Connector:

Create PI Points automatically.

Collect time-series data and send it to the PI System through the PI OPC DA Interface.

Create AF Objects automatically.

Reference Manuals

OSIsoft DeltaV Asset Connector

PI Server manuals

AF manuals

PI OPC DA Interface Manual

PI OPC DA Interface Failover Manual

Emerson Process Management DeltaV Users Guide v10.3

DeltaV Smart Connector 1

Supported Features

Feature Support

Part Number PI-SC-EM-DV-NTI

* Platforms 32-bit Interface 64-bit Interface

Windows XP

32-bit OS Yes No

64-bit OS No (Emulation Mode) No

Windows 2003 Server

32-bit OS Yes No


Windows Vista

32-bit OS Yes No


Windows 2008

32-bit OS Yes No

Windows 2008 R2


Windows 7

32-bit OS Yes No


* Auto Creates PI Points Smart Connector

* Automatic Creation of AF Objects Yes

Point Builder Utility No

ICU Control Yes

PI Point Types Int16 / Int32 / Float16 / Float3 / Digital/ String

Sub-second Timestamps Yes

Sub-second Scan Classes Yes

Automatically Incorporates PI Point Attribute Changes

Yes

Exception Reporting Yes

Outputs from PI No

Inputs to PI Scan / Unsolicited

Supports Questionable Bit Yes

Supports Multi-character PointSource Yes

Maximum Point Count Unlimited

* Uses PI SDK Yes

PINet String Support No

* Source of Timestamps DeltaV / PI

History Recovery No


Feature Support

* UniInt-based* Disconnected Startup* SetDeviceStatus

YesYesYes

* Failover Server-level Failover; Interface-Level Failover Using UniInt Phase 1; Interface-Level Failover Using Microsoft Clustering

* Vendor Software Required on PI Smart Connector Node

No

* Vendor Software Required on Foreign Device

Yes

* Vendor Hardware Required Yes

Additional PI Software Included with Interface

No

Device Point Types Int16, int32, float16, float32, String, Digital

Serial-Based Interface No

* See paragraphs below for further explanation.

PlatformsThe DeltaV Asset Connector is designed to run on the above listed Microsoft Windows operating systems. The DeltaV Smart Connector also requires Microsoft .NET 3.0. Because it is dependent on vendor software, newer platforms may not yet be supported. Please contact OSIsoft Technical Support for more information.

Automatic Creation of PI PointsThe DeltaV Smart Connector creates and configures all PI Points needed for collection of time-series data. PI Points are created if the enterprise historian configuration file, (Enthist.xml) is present on startup and each time the file is updated.

Automatic Creation of AF ObjectsThe DeltaV Smart Connector creates AF objects such as Element Templates, Attribute Templates, Elements, and Attributes based on the asset information received from the DeltaV system contained in the DeltaV equipment hierarchy file (equiphier.xml). The DeltaV equipment hierarchy file is exported manually from the DeltaV Explorer. Assets are initially created after the initial creation of PI points.

Uses PI SDKThe PI SDK and the PI API are bundled together and will be installed on each PI Smart Connector node. This Smart Connector specifically makes PI SDK calls to create and edit PI Points.

Source of TimestampsTimestamps are received from the foreign system or the PI Server depending the how the OPC interface is configured.

UniInt-basedUniInt stands for Universal Interface. UniInt is not a separate product or file; it is an OSIsoft-developed template used by developers and is integrated into many interfaces and Smart


Introduction

Connectors, including this Smart Connector. The purpose of UniInt is to keep a consistent feature set and behavior across as many of OSIsoft’s interfaces and Smart Connectors as possible. It also allows for the very rapid development of new interfaces and Smart Connectors. In any UniInt-based Smart Connector, the Smart Connector uses some of the UniInt-supplied configuration parameters and some Smart Connector –specific parameters. UniInt is constantly being upgraded with new options and features.

The UniInt Interface User Manual is a supplement to this manual.

Failover Server-Level Failover

The interface supports server-level failover that allows collecting data from either primary or backup OPC Servers. This feature is built into the interface and does not require any additional hardware or software. See OPC DA Interface Failover Manual for more details

Interface-Level Failover using UniInt

This interface supports Interface-Level Failover using UniInt, as well as Interface-Level Failover using Microsoft Clustering.

UniInt provides support for a hot failover configuration which results in a no data loss solution for bi-directional data transfer between the PI Server and the Data Source given a single point of failure in the system architecture. This failover solution requires that two copies of the interface be installed on different interface nodes collecting data simultaneously from a single data source. Failover operation is automatic and operates with no user interaction. Each interface participating in failover has the ability to monitor and determine liveliness and failover status. To assist in administering system operations, the ability to manually trigger failover to a desired interface is also supported by the failover scheme. This type of failover does not require a special type of hardware or software (e.g. a Microsoft Cluster).

The failover scheme is described in detail in the UniInt Interface User Manual, which is a supplement to this manual. Details for configuring this Interface to use failover are described in the “UniInt Failover Configuration” section of the OPC DA Interface Failover Manual.

Interface-Level Failover using Microsoft Clustering

This type of failover allows two copies of the interface to run on two clustered machines, with only one copy actually collecting data at any given time. This failover option can be combined with the Server-Level Failover, so that the user can have redundancy for both the OPC server and the interface. Details of configuring the failover are documented in the OPC DA Interface Failover Manual.

Vendor Software Required on Smart Connector NodeThe Asset Connector is required to run on a DeltaV Application Station.

Vendor Software Required on Foreign DeviceDeltaV version 10.3 or later

Vendor Hardware RequiredDeltaV Application Station.


Device Point TypesInt16, Int32, Float16, Float32, String, and Digital device point types are supported in the DeltaV System.

System Diagram


Chapter 2. Overview of a Smart Connector

The DeltaV Smart Connector handles all actions necessary to connect to and mine data from the DeltaV 10.3 system in order to populate and send data to both a PI Server and an AF 2.x Server. The DeltaV Smart Connector automatically creates and configures PI Points, stores time-series data in PI through the PI OPC DA Interface, and creates AF objects.

Installation

The standard installation has the Enterprise PI Server, the PI OPC DA Interfaces and the DeltaV OPC DA server on the same DeltaV Application Station. During the DeltaV_Actr set-up program, the user is prompted to enter configuration information regarding the location of the DeltaV OPC DA server, PI Server, and AF Server. Defaults are provided for each selection, but the user may change these settings during the installation procedure. The Smart Connector creates and starts the DeltaV Asset Connector as a Windows service. See the Smart Connector Installation section of this manual for more information. For more information see the DeltaV Asset Connector to the PI System.

Principles of Operation

The DeltaV Smart Connector provides the following functionality:

Stores DeltaV data in a PI System.

Automatically creates and configures PI Points based on DeltaV historicized parameters.

Automatically creates and configures AF objects based on DeltaV equipment hierarchy after a manual export operation.

DeltaV Configuration Data

DeltaV history collection configuration data is retrieved from the enterprise historian configuration XML file that is generated by a download of the Continuous Historian subsystem on the Application Station where the DeltaV Asset Connector is installed. On the initial download PI tags will be created for each DeltaV parameter in the file, and with each additional download, the file timestamp changes, causing the Asset Connector to check the file for updates and reflect those updates in PI. The “Use embedded Enterprise Historian” option must be chosen in the DeltaV Continuous Historian Properties before the DeltaV Smart Connector can be used.


To choose the embedded Enterprise PI Historian option, follow these steps:

1. Open DeltaV Explorer.

2. Right click the Continuous Historian subsystem on the proper Application Station and choose Properties.

3. Click the Enabled checkbox and choose the Use embedded Enterprise Historian option.

Note: The PI Enterprise Server should be version 3.4.375.80 or greater. It is

DeltaV Asset Connector Installation Directory

The DeltaV_Actr is installed to the following location:PIHOME\Asset Connectors\DeltaV\

where PIHOME is replaced with the corresponding entry in the pipc.ini file.


Chapter 3. AF 2.0 Object Creation and Configuration

The DeltaV Asset Connector automatically creates and configures AF objects when the DeltaV equipment hierarchy export is executed and the equipment hierarchy file, equiphier.xml, exists in the directory specified during the installation of the asset connector. During installation, the user is prompted to enter the AF node name and the AF Database name. If this AF Database already exists, it is updated with the information received from the DeltaV system. If this AF Database does not exist, a new AF Database with the specified name is created.

To export the equipment hierarchy XML file for the asset connector follow these steps.

1. Open DeltaV Explorer

2. Click, File Export Equipment Hierarchy,

AF Categories

The DeltaV Asset Connector creates a ‘DeltaV’ AF Element Category in AF 2.x and assigns all AF Element Templates and AF Elements created by the DeltaV Asset Connector to this category. The AF Category represents a user-defined value used to group objects in AF. Objects may be grouped by categories for generation of reports or to run queries.


AF Element Templates

One AF Element Template is created for each type of DeltaV object contained in the exported DeltaV equipment hierarchy file. DeltaV object types may include Control Modules, Units, Process Cells, Areas, etc. The AF Element Template name is set to the type name, and the Element Template is assigned to the ‘DeltaV’ Element Category described above.

AF Elements

The DeltaV Asset Connector creates one ‘root’ AF Element in order to group all AF Elements that it creates. The default name for this AF Element is “DeltaV_Actr” but a different root name may be chosen during installation of the DeltaV Asset Connector. Once the initial synchronization is completed, and this root element exists in AF, it is recommended that the name not be changed in PI System Explorer. If it is necessary to change the name, the AFRoot argument in the PIDeltaV_Actr.exe.config file must also be changed to match the new name, and the DeltaV Asset Connector must then be restarted.

One AF Element is created for each unique DeltaV object in the exported DeltaV equipment hierarchy file. The object position in the equipment hierarchy file is used to determine the appropriate position in the PI AF hierarchy. The AF Element is created under the ‘root’ element and is assigned to the ‘DeltaV’ AF Element Category described above. The AF Element Template corresponding to the DeltaV object type describing this object is used when the AF Element is created.

AF Attributes

When an AF Element is created, the DeltaV Asset Connector searches for all PI Points matching the AF Element’s name. A new AF Attribute is created for each PI Point configured for history collection that is found. The AF Attribute has the same name as its corresponding PI point and its ValueType is set according to the pointtype of the PI point associated with it. A PI Point Data Reference is configured in order to tie the AF Attribute to its corresponding PI Point. When the AF Attribute value is requested, the data reference returns the value of the associated PI Point.


Chapter 4. Installation Checklist

For those users who are familiar with running PI data collection interface and Smart Connector programs, this checklist helps get the Smart Connector running. If not familiar with PI Smart Connector, return to this section after reading the rest of the manual in detail.

1. Verify proper licensing for Emerson DeltaV and the Enterprise PI Server.

2. Install the Enterprise PI Server (v3.4.375.80 or later) on DeltaV Application station.

3. Install PI AF Server on PI AF node (optional).

4. Configure DCOM for PI OPC DA interface connection to the DeltaV OPC Server (see the PI OPC DA Interface manual for help in configuring DCOM)

5. Run the PI DeltaV Smart Connector installation that will install the AF Client, PI OPC DA Interface, PI OPC DA Interface ICU Control and the DeltaV Asset Connector.

6. Verify that PI points are correctly configured and that data collection is correct.


Chapter 5. Smart Connector Installation

The DeltaV Smart Connector installation includes the DeltaV Asset Connector and the PI OPC DA Interface. Each of these components will be installed as an automatically starting windows service on the DeltaV Application Station where the embedded PI Server is installed. There are several dialog boxes that prompt the user for information. Some entries are required while other information may be optional, based on the requirements of the project. The installation program for the DeltaV Asset Connector sets up the PI OPC DA Interface bat files automatically. (Please see the DeltaV Asset Connector to the PI Server manual for comprehensive instructions).

Note: The PI OPC DA Interface service is not removed when the DeltaV Asset Connector is uninstalled. The removal of the service must be done manually before the OPC interface is uninstalled. To remove the service run: OPCint_SCx –remove for each OPC interface service installed.

Note: There are significant changes in the install since 1.0. It is very important to review the Installation chapter of the DeltaV Asset Connector user manual.


Chapter 6. Buffering

PI Buffering is not recommended on the DeltaV Application Station.


Appendix A.Error and Informational Messages

A string DV_Actr is pre-pended to error messages written to the pipc log. Please see the DeltaV Asset Connector to the PI System manual for a comprehensive list of errors. PI OPC DA Interface error messages will be pre-pended with the string OPCpi. For more information see the PI OPC DA Interface manual.

Message Logs

The location of the message log depends upon the platform on which the Smart Connector is running. See the UniInt Interface User Manual for more information.

Messages are written to PIHOME\dat\pipc.log at the following times.

When the Smart Connector starts many informational messages are written to the log. These include the version of the Smart Connector, the version of UniInt, the command-line parameters used, and the number of points.

As the Smart Connector retrieves points, messages are sent to the log if there are any problems with the configuration of the points.

If the /db is used on the command-line, then various informational messages are written to the log file.

System Errors and PI Errors

System errors are associated with positive error numbers. Errors related to PI are associated with negative error numbers.

Error Descriptions on Windows

On Windows, descriptions of system and PI errors can be obtained with the pidiag utility:PI\adm\pidiag –e error_number


Appendix B.Technical Support and Resources

You can read complete information about technical support options, and access all of the following resources at the OSIsoft Technical Support Web site:

http://techsupport.osisoft.com (http://techsupport.osisoft.com)

Before You Call or Write for Help

When you contact OSIsoft Technical Support, please provide:

Product name, version, and/or build numbers

Computer platform (CPU type, operating system, and version number)

The time that the difficulty started

The log file(s) at that time

Help Desk and Telephone Support

You can contact OSIsoft Technical Support 24 hours a day. Use the numbers in the table below to find the most appropriate number for your area. Dialing any of these numbers will route your call into our global support queue to be answered by engineers stationed around the world.

Office Location Access Number Local Language OptionsSan Leandro, CA, USA 1 510 297 5828 English

Philadelphia, PA, USA 1 215 606 0705 English

Johnson City, TN, USA 1 423 610 3800 English

Montreal, QC, Canada 1 514 493 0663 English, French

Sao Paulo, Brazil 55 11 3053 5040 English, Portuguese

Frankfurt, Germany 49 6047 989 333 English, German

Manama, Bahrain 973 1758 4429 English, Arabic

Singapore 65 6391 181186 021 2327 8686

English, MandarinMandarin

Perth, WA, Australia 61 8 9282 9220 English


http://techsupport.osisoft.com/

Support may be provided in languages other than English in certain centers (listed above) based on availability of attendants. If you select a local language option, we will make best efforts to connect you with an available Technical Support Engineer (TSE) with that language skill. If no local language TSE is available to assist you, you will be routed to the first available attendant.

If all available TSEs are busy assisting other customers when you call, you will be prompted to remain on the line to wait for the next available TSE or else leave a voicemail message. If you choose to leave a message, you will not lose your place in the queue. Your voicemail will be treated as a regular phone call and will be directed to the first TSE who becomes available.

If you are calling about an ongoing case, be sure to reference your case number when you call so we can connect you to the engineer currently assigned to your case. If that engineer is not available, another engineer will attempt to assist you.

Search Support

From the OSIsoft Technical Support Web site, click Search Support.

Quickly and easily search the OSIsoft Technical Support Web site’s Support Solutions, Documentation, and Support Bulletins using the advanced MS SharePoint search engine.

Email-based Technical Support

[email protected]

When contacting OSIsoft Technical Support by email, it is helpful to send the following information:

Description of issue: Short description of issue, symptoms, informational or error messages, history of issue

Log files: See the product documentation for information on obtaining logs pertinent to the situation.

Online Technical Support

From the OSIsoft Technical Support Web site, click Contact us > My Support > My Calls.

Using OSIsoft’s Online Technical Support, you can:

Enter a new call directly into OSIsoft’s database (monitored 24 hours a day)

View or edit existing OSIsoft calls that you entered

View any of the calls entered by your organization or site, if enabled

See your licensed software and dates of your Service Reliance Program agreements


mailto:[email protected]

Technical Support and Resources

Remote Access

From the OSIsoft Technical Support Web site, click Contact Us > Remote Support Options.

OSIsoft Support Engineers may remotely access your server in order to provide hands-on troubleshooting and assistance. See the Remote Access page for details on the various methods you can use.

On-site Service

From the OSIsoft Technical Support Web site, click Contact Us > On-site Field Service Visit.

OSIsoft provides on-site service for a fee. Visit our On-site Field Service Visit page for more information.

Knowledge Center

From the OSIsoft Technical Support Web site, click Knowledge Center.

The Knowledge Center provides a searchable library of documentation and technical data, as well as a special collection of resources for system managers. For these options, click Knowledge Center on the Technical Support Web site.

The Search feature allows you to search Support Solutions, Bulletins, Support Pages, Known Issues, Enhancements, and Documentation (including user manuals, release notes, and white papers).

System Manager Resources include tools and instructions that help you manage: Archive sizing, backup scripts, daily health checks, daylight savings time configuration, PI Server security, PI System sizing and configuration, PI trusts for Interface Nodes, and more.

Upgrades

From the OSIsoft Technical Support Web site, click Contact Us > Obtaining Upgrades.

You are eligible to download or order any available version of a product for which you have an active Service Reliance Program (SRP), formerly known as Tech Support Agreement (TSA). To verify or change your SRP status, contact your Sales Representative or Technical Support (http://techsupport.osisoft.com / ) for assistance.

OSIsoft Virtual Campus (vCampus)

The OSIsoft Virtual Campus (vCampus) Web site offers a community-oriented program that focuses on PI System development and integration. The Web site's annual online subscriptions provide customers with software downloads, resources that include a personal development PI System, online library, technical webinars, online training, and community-oriented features such as blogs and discussion forums.

OSIsoft vCampus is intended to facilitate and encourage communication around PI programming and integration between OSIsoft partners, customers and employees. See the


http://techsupport.osisoft.com/

Technical Support and Resources

OSIsoft vCampus Web site, http://vCampus.osisoft.com (http://vCampus.osisoft.com) or contact the OSIsoft vCampus team at [email protected] for more information.


http://vCampus.osisoft.com/

Appendix C.Revision History

Date Author Comments

14-Feb-2008 Bpayne Initial version

03-Apr-2008 Mmoore Updates, added PI AF information

21-Apr-2008 Bpayne Updates, more concise information about synchronization parameters

28-May-2008 Bpayne Updates found from preliminary testing

26-Jun-2008 Bpayne Updates for AFRoot, Part Number, and cleanup

14-Jul-2008 Bpayne Updates include screen shots

31-Jul-2008 Bpayne Updates based on Mkelly review

04-Aug-2008 Bpayne Updates based on Mkelly’s 2nd review

06-Aug-2008 Bpayne Updates from Sbranscomb review

05-Sep-2008 Mmoore Updates from Jzeilenga review

16-Sep-2008 Bpayne Added Note below the OPC interface dialog for explaining the distribution of tags across multiple instances of the interface.

06-Oct-2008 Mkelly Fixed headers, footers and page numbers

09-Oct-2008 Bpayne Replaced screen capture for “Required Server Data” and removed comments and set to FINAL

09-Oct-2008 Mmoore Updates from Emerson review; updated screenshots

10-Nov-2008 Mkelly Version 1.0.0.0, Revision A, Changed all references of OPC Interface to PI OPC DA Interface, Added OPCInt ICU Control to the installation checklist, fixed headers and footers.

24-Nov-2008 Bpayne Corrections made from Mike Kelly’s release review.

03-Dec-2008 Bpayne Version 1.0.0.0, Revision B, Added Buffering section.

21-Apr-2009 Mmoore Version 1.0.1.x Documented point type mapping and error tag .csv file

19-May-2009 Mkelly Version 1.0.1.x, Revision A; Changed title and contact page. Fixed headers and footer and section breaks. Updated copyright date. Corrected Title in file properties.

26-Aug-2009 Mmoore Version 1.0.2.x, Revision A; Updated for [UC] keyword in descriptor

17-Aug-2010 Bpayne Version 1.1.0.x Revision A: Updated Digital State section for the new method of storing DeltaV Named Sets.

10-Dec-2010 Bpayne Version 2.0.0.x Revision A: Updated Installation section for new Named Set behavior for creating PI Tags.


11-Jan-2011 MKelly Version 2.0.0.x Revision B; Updated title page and copyright page. Saved as Final.

25-Jan-2011 MKelly Version 2.0.0.x Revision C; Added missing appendix for Technical Support and Resources.


DeltaV Smart Connector - OSIsoftcdn.osisoft.com/interfaces/2702/PI_DeltaV… · Web view ·...

Documents

Transcript of DeltaV Smart Connector - OSIsoftcdn.osisoft.com/interfaces/2702/PI_DeltaV… · Web view ·...