Emerson Deltav batch Interface
Event Journals as Data Source
Download 2.43 Mb.
|
- Navigate this page:
- SQL Batch Historian as Data Source
- SQL AlarmEvents Historian as Data Source
Event Journals as Data SourceEvent journals are files that are generated directly by a DeltaV Batch Execution System (BES). Each file represents execution of particular recipe and contains a log of batch events as well as batch related data. The interface expects that each record (row) in the event file will contain at least 15 tab-delimited columns which contain the following information in the following order: Column1: Timestamp (either LclTime or GMTTime) Column2: BatchID Column3: Recipe Column4: Descript Column5: Event Column6: Pvalue Column7: EU Column8: Area Column9: ProcCell Column10: Unit Column11: Phase Column12: PhaseDesc Column13: UserID Column14: UniqueID Column15: Comment SQL Batch Historian as Data SourceThe DeltaV Batch Execution System (BES) consists of various components and the SQL Server is one of them. The SQL Server is used to store events performed by the DeltaV BES. While the SQL Server contains multiple databases used to store realtime data and batch data, the interface requires only primary for initial connection, by default named –DVHisDB. Table 2. List of public views used for data retrieval.
If the data archiving was performed on DeltaV SQL batch historian, then the new database name containing archived batch will be referenced in the primary database – DVHisDB, allowing the interface to reconnect to the new database and retrieve archived batch data as well. Data retrieval from SQL server is scan based. Microsoft ADO driver for the Microsoft SQL is used to communicate with the SQL server databases (part of SQL Native client package). Microsoft SQL Native Client can be downloaded from the following location: http://msdn.microsoft.com/en-us/data/aa937733.aspx SQL Alarm&Events Historian as Data SourceThe DeltaV Batch Execution System (BES) 9.3+ includes the SQL Alarm&Events historian. This historian uses an independent SQL Server for its storage, which is named by default as
The SQL A&E data source(s) can be specified separately or in parallel with the SQL Batch historian data source(s). Note, the SQL AE data source is missing the ProcessCell definition. In order to properly map module hierarchy retrieved from SQL AE database onto existing DeltaV Batch equipment hierarchy, it is required to define the ProcessCell correlation to the Area or ProcessCell correlation to the Unit. It can be achieved through INI file definition: Apcmap: = And/Or
Upcmap: where apcmap stands for Area to ProcessCell map. For DeltaV default PAINT recipe, the map can be defined as: Apcmap: EXTERIOR_PAINT = PAINT_BLEND UPCmap stands for Unit to ProcessCell map. The mapping can be defined as: Upcmap: U101 = PAINT_BLEND The definition of SQL AE historian as data source is identical to specifying the DeltaV batch SQL historian with one exception – an extra parameter source[##].isAE=true has to be defined.
Source[1].sqlserver = deltav10 Source[1].database = DVHisDB
Source[1].sqlserver = deltav10 Source[1].database = DVHisDB Source[2].sqlserver = deltav10\DELTAV_CHRONICLE Source[2].database = Ejournal Source[2].isAE = true Apcmap: EXTERIOR_PAINT = PAINT_BLEND
Data retrieval from SQL server is scan based. Microsoft ADO driver for the Microsoft SQL is used to communicate with the SQL server databases (part of SQL Native client package). Microsoft SQL Native Client can be downloaded from the following location: http://msdn.microsoft.com/en-us/data/aa937733.aspx 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:
|