Rockwell-automation FactoryTalk Historian SE 3.0 H2H Interface User Gu Manual de usuario

FACTORYTALK HISTORIAN TO HISTORIAN INTERFACE USER GUIDE PUBLICATION H2H-UM001A-EN-E–July 2012

Introduction 4 Feature Support Inputs to Historian: Scan-based / Unsolicited / Event Tags Scan-based Only * Supports Questionable Bit No Supports Mu

UniInt Failover Configuration 94 Figure 7: SMT application configured to import a digital state set file. The Historian Servers window shows the “l

FactoryTalk Historian To Historian Interface User Guide 95 Figure 9: The SMT application showing the UFO_State digital set created on the “localhos

UniInt Failover Configuration 96 Creating the UniInt Failover Control and Failover State Tags (Phase 2) The ICU can be used to create the UniInt Fai

FactoryTalk Historian To Historian Interface User Guide 97 Chapter 10. Interface node Clock Make sure that the time and time zone settings on the c

FactoryTalk Historian To Historian Interface User Guide 99 Chapter 11. Security The Historian Firewall Database and the Historian Proxy Database mu

Security 100 Security Configuring using Trust Editor The Trust Editor plug-in for System Management Tools 3.x may also be used to edit the Trust tab

FactoryTalk Historian To Historian Interface User Guide 101 Source System Manager 1. The file PISysDat:PIServer.dat will be used to provide overall

Security 102 E!

FactoryTalk Historian To Historian Interface User Guide 103 Chapter 12. Starting / Stopping the interface This section describes starting and stopp

FactoryTalk Historian To Historian Interface User Guide 5 Maximum Point Count While the interface does not have a hard-coded point count limit, ther

FactoryTalk Historian To Historian Interface User Guide 105 Chapter 13. Buffering Buffering refers to an interface node‟s ability to temporarily st

Buffering 106 How Buffering Works A complete technical description of PIBufss and Bufserv is beyond the scope of this document. However, the followi

FactoryTalk Historian To Historian Interface User Guide 107 However, if the Historian Server contains an interface-specific Trust entry that allows

Buffering 108 Buffering Settings There are a number of settings that affect the operation of PIBufss and Bufserv. The Buffering Settings page allow

FactoryTalk Historian To Historian Interface User Guide 109 Send rate (milliseconds) Send rate is the time in milliseconds that PIBufss waits betwee

Buffering 110 Maximum buffer file size (KB) This is the maximum size of the buffer file ([PIHOME]\DAT\APIBUF.DAT). When Bufserv cannot communicate w

FactoryTalk Historian To Historian Interface User Guide 111 The following screen shows that PIBufss is configured to write data to a Historian Coll

Buffering 112 Bufserv Bufserv buffers data to a standalone Historian Server, or to multiple standalone Historian Servers. (If you want to buffer to

FactoryTalk Historian To Historian Interface User Guide 113 Installing Buffering as a Service Both the PIBufss and Bufserv applications run as a Se

Introduction 6 SetDeviceStatus The Historian to Historian Interface is built with UniInt 4.4.4.0. New functionality has been added to support health

Buffering 114 API Buffer Server Service Use the API Buffer Server Service page to configure Bufserv as a Service. This page also allows you to sta

FactoryTalk Historian To Historian Interface User Guide 115

FactoryTalk Historian To Historian Interface User Guide 117 Chapter 14. Interface Diagnostics Configuration The Interface Point Configuration chapt

Interface Diagnostics Configuration 118 You configure one Scan Class Performance Point for each Scan Class in this Interface. From the ICU, select t

FactoryTalk Historian To Historian Interface User Guide 119 Correct / Correct All If the “Status” of a point is marked “Incorrect”, the point config

Interface Diagnostics Configuration 120 Snapshot The Snapshot column holds the snapshot value of each Performance Point that exists in Historian. Th

FactoryTalk Historian To Historian Interface User Guide 121 Click Create to create the Performance Counters Point for that particular row. Click Cr

Interface Diagnostics Configuration 122 The ICU uses a naming convention such that the tag containing “(Scan Class 1)” (for example, “sy.perf.etamp3

FactoryTalk Historian To Historian Interface User Guide 123 foreign device connections to the interface. This value will always be less than or equa

FactoryTalk Historian To Historian Interface User Guide 7 The failover scheme is described in detail in the UniInt Interface User Manual, which is a

Interface Diagnostics Configuration 124 “Historian Status” (PI_Status) The .PI_Status Performance Counters Point stores communication information ab

FactoryTalk Historian To Historian Interface User Guide 125 received a new value within the Stale Period then the point will move from the Good coun

Interface Diagnostics Configuration 126 Interface Health Monitoring Points Interface Health Monitoring Points provide information about the health o

FactoryTalk Historian To Historian Interface User Guide 127 For some of the Health Points described subsequently, the interface updates their values

Interface Diagnostics Configuration 128 [UI_SCINFO] The [UI_SCINFO] Health Point provides scan class information. The value of this point is a strin

FactoryTalk Historian To Historian Interface User Guide 129 The Interface updates this point at the same frequency as the [UI_HEARTBEAT] point. The

Interface Diagnostics Configuration 130 A particular Scan Class‟s [UI_SCBVRATE] point indicates the number System Digital State values that the inte

FactoryTalk Historian To Historian Interface User Guide 131 [UI_SCINSCANTIME] You can create a [UI_SCINSCANTIME] Health Point for each Scan Class in

Interface Diagnostics Configuration 132 As the preceding picture shows, the ICU suggests an Event Counter number and a Tagname for the I/O Rate Poi

FactoryTalk Historian To Historian Interface User Guide 133 Event Counter The Event Counter correlates a tag specified in the iorates.dat file with

Introduction 8 Figure 2: Configuration 2 PItoPI runs on the receiving Historian Server “pulling” data from the source Historian Server.

Interface Diagnostics Configuration 134 Search Allow the user to search the Historian Server for a previously defined I/O Rate tag. Interface Status

FactoryTalk Historian To Historian Interface User Guide 135 Click Create to create the ISU tag. Use the Tag Search button to select a Watchdog Tag.

FactoryTalk Historian To Historian Interface User Guide 137 Appendix A. Error and Informational Messages A string NameID is pre-pended to error mes

Error and Informational Messages 138 Scan Summary After a scan class has finished history recovery, the interface logs messages indicating the numbe

FactoryTalk Historian To Historian Interface User Guide 139 UniInt Failover Specific Error Messages Informational Message 16-May-06 10:38:00 PItoPI

Error and Informational Messages 140 Message 16-May-06 17:38:06 PItoPI 1> One of the required Failover Synchronization points was not loaded. Err

FactoryTalk Historian To Historian Interface User Guide 141 Errors (Phase 2) Unable to open synchronization file Message 27-Jun-08 17:27:17 Historia

FactoryTalk Historian To Historian Interface User Guide 143 Appendix B. PI SDK Options To access the PI SDK settings for this Interface, select thi

FactoryTalk Historian To Historian Interface User Guide 9 Figure 3: Configuration 3 PItoPI runs on a separate interface node.

FactoryTalk Historian To Historian Interface User Guide 145 Appendix C. Terminology To understand this interface manual, you should be familiar wit

Terminology 146 Historian Collective A Historian Collective is two or more replicated Historian Servers that collect data concurrently. Collectives

FactoryTalk Historian To Historian Interface User Guide 147 SMT SMT refers to System Management Tools. SMT is the program that you use for configuri

FactoryTalk Historian To Historian Interface User Guide 149 Appendix D. Technical Support and Resources Rockwell provides dedicated technical suppo

Technical Support and Resources 150 If you are not located in North America and want to contact Rockwell Automation Support, use the Worldwide Locat

FactoryTalk Historian To Historian Interface User Guide 11 Chapter 2. Principles of Operation The FactoryTalk Historian to Historian interface copi

Principles of Operation 12 How FactoryTalk Historian to Historian Finds Source Points When the FactoryTalk Historian to Historian Interface loads a

FactoryTalk Historian To Historian Interface User Guide 13 source point ID and the search ends. Otherwise, proceed to the step 4. If the search ends

iii Contact Rockwell Automation Customer Support Telephone — 1.440.646.3434 Online Support — http://www.rockwellautomation.com/support Copyright No

Principles of Operation 14 In general the interface can sustain higher data rates (events/second) when configured for exception data collection. Exc

FactoryTalk Historian To Historian Interface User Guide 15 time then exits. The times specified are relative to the machine where the interface runs

Principles of Operation 16 Archive Data Collection By default, the first scan class is used for exception data collection. Tags configured for any o

FactoryTalk Historian To Historian Interface User Guide 17 recovery nearly all data is obtained from disk reads. When the interface transitions to s

Principles of Operation 18 Int16/32 Yes Yes No Digital No Yes No String No No Yes Interface Status Events The FactoryTalk Historian to Historian

FactoryTalk Historian To Historian Interface User Guide 19 number of tag edits are made, a user may choose to restart the interface. Restarting the

Principles of Operation 20 between reconnection, and number of reconnection attempts are all user configurable parameters. Note: the default network

FactoryTalk Historian To Historian Interface User Guide 21 Failover Status When configured for server-level failover users can specify a status tag.

Principles of Operation 22 Historian to Historian is used to transfer data within a collective when the data cannot be sent directly from the inter

FactoryTalk Historian To Historian Interface User Guide 23 Example Architecture for Historian to Historian within a Historian Collective Tag attrib

FactoryTalk Historian To Historian Interface User Guide iii Table of Contents Chapter 1. Introduction ...

Principles of Operation 24 Historian to Historian between Historian Collectives The following diagram architecture depicts a typical deployment of H

FactoryTalk Historian To Historian Interface User Guide 25 After the interface is up and running, and if n-way buffering is enabled, the interface w

FactoryTalk Historian To Historian Interface User Guide 27 Chapter 3. Installation Checklist If you are familiar with running FactoryTalk Historian

Installation Checklist 28 9. Build input tags and, if desired, output tags for this Interface. Important point attributes and their use are: Locati

FactoryTalk Historian To Historian Interface User Guide 29 Advanced Interface Features Configure UniInt Failover; see that section in this document

FactoryTalk Historian To Historian Interface User Guide 31 Chapter 4. Interface Installation Rockwell Automation recommends that interfaces be inst

Interface Installation 32 Interface Directories PIHOME Directory Tree The [PIHOME] directory tree is defined by the PIHOME entry in the pipc.ini con

FactoryTalk Historian To Historian Interface User Guide 33 Installing Interface Service with Historian Interface Configuration Utility The Historian

Table of Contents iv Interface Directories ... 32 PIHOME Dire

Interface Installation 34 Log on as The Log on as text box shows the current “Log on as” Windows User Account of the interface service. If the servi

FactoryTalk Historian To Historian Interface User Guide 35  If the Auto option is selected, the service will be installed to start automatically w

Interface Installation 36 Windows Service Installation Commands on an interface node or a Historian Server Node without Bufserv implemented Manual s

FactoryTalk Historian To Historian Interface User Guide 37 Chapter 5. PointSource The PointSource is a unique, single or multi-character string tha

FactoryTalk Historian To Historian Interface User Guide 39 Chapter 6. Historian Point Configuration The Historian point is the basic building block

Historian Point Configuration 40 The Historian 2 tag name attribute LongName is used if it exists. The receiving and source tag names do not need t

FactoryTalk Historian To Historian Interface User Guide 41 Location2 Location2 specifies data timestamp adjustment. The source Historian Server supp

Historian Point Configuration 42 Location3 Value Write “I/O Timeout” Write “Access Denied” Include Snapshot Point Level Debugging 13 -- Yes Yes Y

FactoryTalk Historian To Historian Interface User Guide 43 modes. It is not possible for PI2 to have two values with the same timestamp. InstrumentT

FactoryTalk Historian To Historian Interface User Guide v Configuring Synchronization through a Shared File (Phase 2) ... 78 C

Historian Point Configuration 44 following table indicates the maximum length of this attribute for all the different combinations of PI API and His

FactoryTalk Historian To Historian Interface User Guide 45 Scan By default, the Scan attribute has a value of 1, which means that scanning is turne

Historian Point Configuration 46 Interface Configurations Data collected by the interface has already passed exception on the source Historian Serv

FactoryTalk Historian To Historian Interface User Guide 47 DataAccess, PtAccess Historian 3 nodes use these attributes to control client read/write

FactoryTalk Historian To Historian Interface User Guide 49 Chapter 7. Interface Status Tag Configuration The following procedure describes how to c

FactoryTalk Historian To Historian Interface User Guide 51 Chapter 8. Startup Command File Command-line parameters can begin with a / or with a -.

Startup Command File 52 Interface name as displayed in the ICU (optional) will have Historian- pre-pended to this name and it will be the display na

FactoryTalk Historian To Historian Interface User Guide 53 The PItoPI ICU control has 7 tabs for each scan class, plus the All Scan Classes settings

Table of Contents vi Appendix A. Error and Informational Messages ... 137 Message Logs ...

Startup Command File 54 FactoryTalk Historian to Historian Interface page Since the startup file of the FactoryTalk Historian to Historian Interface

FactoryTalk Historian To Historian Interface User Guide 55 PI2 Security File – Use PI2 security file The PI2 Security File section is used only if t

Startup Command File 56 History Recovery Tab Maximum hours of history to recover Number of hours to recover history for all points. Setting the val

FactoryTalk Historian To Historian Interface User Guide 57 Millisecond pause between history calls The number of milliseconds to pause between histo

Startup Command File 58 Debug Tab Debug Parameters The Debug Levels parameter is used to set a debug level for debug messaging per scan class. Chec

FactoryTalk Historian To Historian Interface User Guide 59 Location Tab Use the Override Tag Location Code Settings check boxes to configure the in

Startup Command File 60 Optional Tab Apply tag’s compression specifications to data retrieved during history recovery. Use compression specificatio

FactoryTalk Historian To Historian Interface User Guide 61 Specify maximum events to retrieve for a single point in each call to get history. This p

Startup Command File 62 Opt Cont Tab Source Host reconnection delay. This parameter sets the time delay for attempting to reconnect to source Histo

FactoryTalk Historian To Historian Interface User Guide 63 Source Historian Server Failover Tab Enable PItoPI Failover This check box is used to al

FactoryTalk Historian To Historian Interface User Guide 1 Chapter 1. Introduction The Rockwell FactoryTalk Historian to Historian interface copies

Startup Command File 64 Number of connection attempts to source server This parameter is used to specify the number of times to try connecting to so

FactoryTalk Historian To Historian Interface User Guide 65 General Interface Operation .BAT .INI Description /db=# Optional DebugFlags /db=1 : Max

Startup Command File 66 .BAT .INI Description the interface; the second occurrence defines the second scan class, and so on. Historian Points are as

FactoryTalk Historian To Historian Interface User Guide 67 .BAT .INI Description Previously, wall clock scheduling was possible, but not across dayl

Startup Command File 68 .BAT .INI Description /ist=tagname Optional -- Name of interface status tag. /ist=<tagname> where < tagname> is

FactoryTalk Historian To Historian Interface User Guide 69 .BAT .INI Description /stopstat or /stopatat= digstate Default: /stopstat= "Intf shu

Startup Command File 70 History Recovery and Archive Data Collection .BAT .INI Description /dc Optional -- Apply data compression to history recover

FactoryTalk Historian To Historian Interface User Guide 71 .BAT .INI Description /ns Optional -- Boundary condition for data retrieval with a time-r

Startup Command File 72 Tag Attribute Override .BAT .INI Description /c1 Optional -- Location1 tag attribute override. Load all tags configured for

FactoryTalk Historian To Historian Interface User Guide 73 .BAT .INI Description /sec_src= node :port Required -- Name or IP address of the seconda

Introduction 2 Automation recommends using n-way buffering which is supported with PI API v1.6.x and later. Please see the PI API installation manua

Startup Command File 74 Sample PItoPI.ini File ; Sample PItoPI.ini ; ;-----------------------------------------------

FactoryTalk Historian To Historian Interface User Guide 75 Chapter 9. UniInt Failover Configuration Introduction To minimize data loss during a sin

UniInt Failover Configuration 76 Quick Overview The Quick Overview below may be used to configure this Interface for failover. The failover configu

FactoryTalk Historian To Historian Interface User Guide 77 Synchronization through a Shared File (Phase 2) Business Network

UniInt Failover Configuration 78 Configuring Synchronization through a Shared File (Phase 2) Step Description 1. Verify non-failover interface opera

FactoryTalk Historian To Historian Interface User Guide 79 Step Description 5. Test the configuration. After configuring the shared file and the int

UniInt Failover Configuration 80 Step Description defined by the /UFO_ID startup command-line parameter.  The Heartbeat control tags for both copi

FactoryTalk Historian To Historian Interface User Guide 81 Configuring UniInt Failover through a Shared File (Phase 2) Start-Up Parameters Note: Th

UniInt Failover Configuration 82 Parameter Required/ Optional Description Value/Default exist, the first interface to start attempts to create the f

FactoryTalk Historian To Historian Interface User Guide 83 Parameter Required/ Optional Description Value/Default /Host=server Required Host Histori

FactoryTalk Historian To Historian Interface User Guide 3 Reference Manuals Rockwell Automation  Historian Server manuals  PI API Installation m

UniInt Failover Configuration 84 Historian Tags The following tables list the required UniInt Failover Control Historian tags, the values they will

FactoryTalk Historian To Historian Interface User Guide 85 The following table describes the extended descriptor for the above Historian tags in mor

UniInt Failover Configuration 86 Historian Tag ExDesc Required / Optional Description Value [UFO2_DEVICESTAT :#] (IF-Node1) Required Device Status

FactoryTalk Historian To Historian Interface User Guide 87 Historian Tag ExDesc Required / Optional Description Value interface is running but canno

UniInt Failover Configuration 88 Detailed Explanation of Synchronization through a Shared File (Phase 2) In a shared file failover configuration, th

FactoryTalk Historian To Historian Interface User Guide 89 points, then it cannot read any other data. There is no need for a backup communications

UniInt Failover Configuration 90 is interrupted. The updates to the Historian Server will be buffered by Bufserv or PIBufss in this case. In a hot f

FactoryTalk Historian To Historian Interface User Guide 91 Failover Configuration Using ICU The use of the ICU is the recommended and safest method

UniInt Failover Configuration 92 Configuring the UniInt Failover Startup Parameters with ICU There are three interface startup parameters that contr

FactoryTalk Historian To Historian Interface User Guide 93 Using the ICU Utility to create Digital State Set To use the UniInt Failover page to crea