Emerson Deltav batch Interface
Download 2.43 Mb.
|
- Navigate this page:
- Interface Node
- PI Server Node
- Tag (Input Tag and Output Tag)
|
Emerson DeltaV Batch Interface Version 1.0.2.0 - 1.0.2.1
Table of Contents Chapter 1. Introduction 1 Reference Manuals 2 Supported Features 2 Diagram of Hardware Connection 6 Chapter 2. Principles of Operation 9 Interface Modes 9 Source Template 10 Event Journals as Data Source 13 SQL Batch Historian as Data Source 13 SQL Alarm&Events Historian as Data Source 14 OPC Alarm&Events Server as Data Source 15 Recipe Model vs. Equipment Model 15 Methodology 16 PIBatch 17 PIUnitBatch 20 PISubBatches 24 Operation 24 Phase 26
Phase State 28 Phase Step 28 Arbitration Events Unavailable 29 Template Placeholders 30 PIBatch and PIUnitBatch Product Property 31 PIModule Creation 33 Foreign Language Support 36 Event Logging 41 Advanced Parsing Parameters 42 Property Templates 43 Tag Templates 46 Tag Templates – PI Batch Database Activity Logging 58 Alarm Tag Templates 60 PI Tag as Placeholder 64 Recipe Templates 65 Merging Multiple Source batches into a Single PIBatch 67 Using /BIDM Parameter 67 Lost Connections to PI Server and PI Archive Backup Issues 68 Data Preprocessing 68 Data Recovery 70 Data Analysis 71 PI Data Deletion 72 EVT Source – Event Based Time Ordered Processing 72 Dealing with Irrelevant Recipes 73 Dealing with Irrelevant Units 74 Dealing with Irrelevant Phases 75 Dealing with Irrelevant Phase States 75 Initialization File 76 EVT Source – Example Event File Journal 78
Data Collection Steps 81 Interface Diagnostics 82
Naming Conventions and Requirements 87 Interface Directories 88 PIHOME Directory Tree 88 Interface Installation Directory 88 Interface Installation Procedure 88 Installing the Interface as a Windows Service 88 Installing the Interface Service with the PI ICU 88 Installing the Interface Service Manually 91
Interface-specific Points 97 Chapter 8. Startup Command File 99 Configuring the Interface with PI ICU 99 PIEMDVB Configuration 101 Configure INI File Form 109 Source Template Tab 109 Tag Template Tab 111 Alarm Tag Template Tab 113 Property Template Tab 115 Recipe Template Tab 116 General Template Tab 117 Translation Tab 119 Mappings Tab 120 Configuring Interface Startup Files 122 Command-line Parameters 122 Sample PIEMDVB.bat File 132 Initialization File Parameters 133 Sample INI file – Multiple EVT Sources 136 Sample INI file – DeltaV German EVT Source 137 Sample INI file – DeltaV SQL 139 Sample INI file – DeltaV SQL, OPCAE 140 Chapter 9. Interface Node Clock 141 Chapter 10. Security 143 Chapter 11. Starting and Stopping the Interface 145 Starting Interface as a Service 145 Stopping the Interface Running as a Service 145
Message Logs 149 Messages 149 System Errors and PI Errors 156 Appendix B. PI SDK Options 157 Appendix C. Batch Executive System – Configuration Requirements 159 Introduction 159 Background 159 Objectives 159 Principles of Operation 159 Principles of the PI Server Batch Database 159 Principles of the PI DeltaV Batch Interface 160 Recommendations for BES Recipes and Equipment Models 161 Appendix D. Event File Directory Sync Utility 165 Introduction 165 Principles of Operation 165 Utility Installation Procedure 165 Installing the Utility as a Windows Service 166 Startup Command File 166 Command-line Parameters 166 Sample EVTSync.bat File 166 Starting and Stopping the Utility 167 Starting the Utility Service 167 Stopping the Utility Service 167 Conclusions 167 Appendix E. Technical Support and Resources 169 Before You Call or Write for Help 169 Help Desk and Telephone Support 169 Search Support 170 Email-based Technical Support 170 Online Technical Support 170 Remote Access 171 On-site Service 171 Knowledge Center 171 Upgrades 171 Appendix F. Revision History 173 Terminology To understand this interface, you should be familiar with the terminology used in this manual. ICUICU is the PI Interface Configuration Utility. The ICU is the primary application that you use to configure and run PI interface programs. You must install the ICU on the same computer on which an interface runs. A single copy of the ICU manages all the interfaces on that particular computer. OSIsoft strongly recommends that you use the ICU for interface management tasks. While, you can configure and run an interface by editing a startup command file, OSIsoft discourages this approach. ICU ControlAn ICU Control is a plug-in to the ICU. Whereas the ICU handles functionality common to all interfaces, an ICU Control implements interface-specific behavior. Most PI interfaces have an associated ICU Control. Interface NodeAn Interface Node is a computer on which the PI API, the PI SDK, or both are installed, and PI Server programs are not installed. PI APIThe PI API is a library of functions that allow applications to communicate and to exchange data with the PI Server. PI CollectiveA PI Collective is two or more replicated PI Servers that collect data concurrently. Collectives are part of the High Availability environment. When the primary PI Server in a collective becomes unavailable, a secondary collective member node seamlessly continues to collect and provide data access to your PI clients. PIHOMEPIHOME refers to the directory that is the common location for PI 32-bit client applications. On a 32-bit operating system A typical PIHOME is C:\Program Files\PIPC. On a 64-bit operating system A typical PIHOME is C:\Program Files (x86)\PIPC. PI interfaces reside in a subdirectory of the Interfaces directory under PIHOME. For example, files for the Modbus Ethernet Interface are in [PIHOME]\PIPC\Interfaces\ModbusE. This document uses [PIHOME] as an abbreviation for the complete PIHOME or PIHOME64 directory. For example, ICU files in [PIHOME]\ICU.
PIHOME64PIHOME64 will be found only on a 64-bit operating system and refers to the directory that is the common location for PI 64-bit client applications. A typical PIHOME64 is C:\Program Files\PIPC. PI interfaces reside in a subdirectory of the Interfaces directory under PIHOME64. For example, files for a 64-bit Modbus Ethernet Interface would be found in C:\Program Files\PIPC\Interfaces\ModbusE. This document uses [PIHOME] as an abbreviation for the complete PIHOME or PIHOME64 directory. For example, ICU files in [PIHOME]\ICU. PI SDKThe PI SDK is a library of functions that allow applications to communicate and to exchange data with the PI Server. Some PI interfaces, in addition to using the PI API, require the PI SDK. PI Server NodeA PI Server Node is a computer on which PI Server programs are installed. The PI Server runs on the PI Server Node. PI SMTPI SMT refers to PI System Management Tools. PI SMT is the program you use for configuring PI Servers. A single copy of PI SMT manages multiple PI Servers. PI SMT runs on either a PI Server Node or a PI Interface Node. Pipc.logThe pipc.log file is the file to which OSIsoft applications write informational and error messages. While a PI interface runs, it writes to the pipc.log file. The ICU provides easy access to the pipc.log. PointThe PI point is the basic building block for controlling data flow to and from the PI Server. For a given timestamp, a PI point holds a single value. A PI point does not necessarily correspond to a “data collection point” on the foreign device. For example, a single “point” on the foreign device can consist of a set point, a process value, an alarm limit, and a discrete value. These four pieces of information require four separate PI points. ServiceA Service is a Windows program that runs without user interaction. A Service continues to run after you have logged off as a Windows user. A Service has the ability to start up when the computer itself starts up. The ICU allows you to configure a PI interface to run as a Service. Tag (Input Tag and Output Tag)The tag attribute of a PI point is the name of the PI point. There is a one-to-one correspondence between the name of a point and the point itself. Because of this relationship, PI System documentation uses the terms “tag” and “point” interchangeably. Interfaces read values from a device and write these values to an Input Tag. Interfaces use an Output Tag to write a value to the device. Directory: interfaces interfaces -> Pi interface for Siemens Spectrum Power tg (Linux) interfaces -> Interface to the pi system Version 37 and Greater interfaces -> Citect Interface interfaces -> Interface to the pi system interfaces -> How to Contact Us interfaces -> How to Contact Us Download 2.43 Mb. Share with your friends:
|