Emerson Deltav batch Interface
Download 2.43 Mb.
|
- Navigate this page:
- Reference Manuals
- Supported Features
- Source of Timestamps
- History Recovery
- SetDeviceStatus
- Vendor Software Required
- Device Point Types
IntroductionThis manual describes the operation of the Emerson DeltaV Batch Interface to the PI System. In this manual, we refer to the Emerson DeltaV Batch interface as the Batch Interface. The primary objective of the Batch Interface is to collect batch processing events from the DeltaV System and store them in the PI Batch Database. In addition to collecting batch data, the interface collects associated batch data to PI Tags and PI Batch properties. The Batch Interface is the first dedicated interface for collecting batch data from the DeltaV System. The interface collects batch events in real-time through the DeltaV OPC Alarm & Events Server (A&E Server). Associated batch data, such as operator comments, report parameters, and recipe parameters, are retrieved by querying the DeltaV Batch Historian during each interface scan. If you lose the connection to the DeltaV OPC A&E Server, the interface retrieves batch data and associated batch data from the DeltaV Batch Historian during each interface scan. The interface automatically tries to re-establish the connection to the DeltaV OPC A&E Server; once the connection has been re-established, the interface returns to collecting batch data in real-time through the DeltaV OPC A&E Server. This interface is primarily designed to be used for DeltaV 10.3 and later systems utilizing the DeltaV OPC A&E Server and the DeltaV Batch Historian; however, it can run against earlier systems utilizing different data sources.
For DeltaV 9.3 systems this interface can utilize the DeltaV Batch Historian or DeltaV event files as the primary data source. For DeltaV 8.4 systems this interface can only use DeltaV event files as the primary data source. NOTE: The use of DeltaV event files as a public interface for the DeltaV System is not recommended by Emerson. The flow of data in the interface is unidirectional—that is, data can only be read from the specified data source and written to the PI Server. This interface can read data from multiple batch data sources simultaneously. By design, the interface does not edit or delete source data. The Batch Interface is a scan-based interface that populates the PI Batch Database and PI Module Database. In addition to batch data, the interface can populate the PI Point Database. PI Point creation, commonly known as tag creation and event population, is controlled by using tag templates. All modules, tags, tag aliases, and health tags are automatically created on the PI server. The Interface does not use the PI API Buffering Service because batch and tag data is already buffered by the source historian databases. To maximize performance, the interface writes events to PI tags in bulk—that is, it writes all events per interface scan. NOTE: The Emerson DeltaV Batch Interface is not an upgrade to the Batch Event File Monitor Interface. OSI plans to provide a migration path for those customers who want to migrate from the Batch Event File Monitor Interface to the Emerson DeltaV Batch Interface. This migration plan and best practices will be posted to the OSI Technical Support website. Reference ManualsOSIsoftPI Data Archive Manual PI Server System Management Guide PI SDK User Manual VendorYou should review the pertinent documentation regarding the particular Batch Executive System (BES) at your facility. You should also maintain familiarity with the contents and format of the source data so that you can choose appropriate options and features for the interface. Supported Features
*See paragraphs below for further explanation. PlatformsThe Interface is designed to run on the above mentioned Microsoft Windows operating systems. Because it is dependent on vendor software, newer platforms may not yet be supported. Please contact OSIsoft Technical Support for more information. PI SDKThe PI SDK and the PI API are bundled and must be installed on each PI Interface node. The PI DeltaV Batch Interface makes PI SDK calls to access the PI Module Database and PI Batch Database. The Interface requires PI SDK version 1.3.4.333 or higher to be installed. The Interface uses PI API to log messages in the local pipc.log file. It does not require a PI API connection to the PI Server. Source of TimestampsSince each record in the source contains a timestamp and the interface itself is solely scan-based, use of the time at record processing could introduce inherent latency with respect to establishing the event time. Thus, the timestamp accompanying the record is used as the source of the timestamp for the data to be placed into the PI system. For the health tags, the Interface uses local system time at the time the value is being recorded. History RecoveryThe operation of the Batch Interface may be interrupted without loss of data. While the Interface is offline, the data is being buffered by the data sources such as SQL Server (DeltaV 9.3+), Event Journal files (DeltaV 8.4+). The Interface can recover data provided it is still available in the data sources. If the data interruption occurred while the interface was running, then the data is recovered automatically without user intervention. To perform historical data recovery, the Interface must be run in Recovery mode. In this mode, the Interface can recover data for any time period specified by the user. The recovery mode is enabled by specifying the recovery time period through the command line parameters /rst= SetDeviceStatusThe Health PIPoint with the attribute ExDesc = [UI_DEVSTAT], is used to represent the status of the source devices. This tag is automatically created and configured if missing by the interface on startup. The following events can be written into the tag: “Good” – the interface is properly communicating and reading data from the data sources. The following events represent proper communication with the data sources. This message is displayed on successful connection to each source. “2 | Connected/No Data | EVT Directory Monitor: “2 | Connected/No Data | Source SQL Server: The following list of events represents the failure to communicate with either the Event Journal file directory or Position directory, or failure to read data from the Event Journal File: “3 | 1 device(s) in error | Error monitoring directory (onError): “3 | 1 device(s) in error | Error monitoring directory: “3 | 1 device(s) in error | Failed to start directory monitoring thread: “3 | 1 device(s) in error | Error in scanning directory: “3 | 1 device(s) in error | Error obtaining EVT files EOF.” “3 | 1 device(s) in error | Error getting current EVT file timestamp.” “3 | 1 device(s) in error | Error reading EVT file: “3 | 1 device(s) in error | Error while reading EVT file.” “3 | 1 device(s) in error | Error reading SQL Server: When DeltaV SQL server is selected as data source, the SQL Native Client must be installed on the interface node. Device Point TypesSince the interface receives data from source as string type, it attempts to coerce the string data into numerical equivalents according to Tag Templates if defined. 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:
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||