Emerson Deltav batch Interface
Download 2.43 Mb.
|
- Navigate this page:
- DELTAV EVT (default)
- DELTAV EVT (with /ubr switch defined)
- DELTAV SQL (default: no /ubr switch)
- DELTAV SQL (with /ubr switch)
- DELTAV SQL +OPCAE (NO /ubr switch available)
- Template Example
Foreign Language SupportThe Emerson DeltaV Batch interface supports languages other than English by providing the use of a look-up table for the various event types that trigger specific actions in the interface. Note that this is not necessarily all of the events that are possible in the data source, only a selected few are required: those, which are used to trigger the start and end times of the PI Batch objects (Table 5). The language translation syntax is the following: translate: where translation is identified by the keyword – translate: followed by the native language word or phrase to be translated. The equal sign determines the end of the native language phrase or word definition and serves as a token for the start of English definition. The syntax is not case sensitive. DELTAV EVT (default)DeltaV EVT required English definitions (no /ubr switch):
DELTAV EVT (with /ubr switch defined)DeltaV EVT required English definitions (with /ubr switch)
DELTAV SQL (default: no /ubr switch)Table of DeltaV SQL required English definitions:
DELTAV SQL (with /ubr switch)DeltaV SQL required English definitions (with /ubr switch):
DELTAV SQL +OPCAE (NO /ubr switch available)DeltaV SQL +OPCAE required English definitions:
Sample German EVT required and optional event translations (when /ubr is used): // [S88 Levels] translate: “Grundrezept” = “Procedure” translate: “Teilrezept” = “Unit Procedure” translate: “Grundoperation” = “Operation” translate: “Grundfunktion” = “Phase” // [Batch Header info] translate: “Rezeptkopf” = “Recipe Header” translate: “Produktcode” = “Product Code” translate: “Formelkopf” = “Formula Header” translate: “Formelname” = “Formula Name”
translate: “Rezeptzuteilung” = “Recipe Arbitration” translate: “Betriebsmittel belegt durch Rezept” = “Resource Acquired by recipe” translate: “Betriebsmittel freigegeben durch Rezept” = “Resource Released by recipe” translate: “Teilanlage” = “Unit”
// can be converted to Comment event, and use English word in Tag Template as // trigger]
translate: “Kommentar” = “Comment” translate: “Systemmeldung” = “System Message” translate: “CHARGEN-Anfang” = “Beginning Of BATCH” translate: “CHARGEN-Ende” = “End Of BATCH” translate: “Teilrezept gestartet” = “Unit Procedure Started” translate: “Teilrezept beendet” = “Unit Procedure Finished” translate: “Grundoperation gestartet” = “Operation Started” translate: “Grundoperation beendet” = “Operation Finished”
translate: “L\C4\UFT” = “RUNNING” translate: “BEENDET” = “COMPLETE” translate: “ENTFERNT” = “REMOVED” translate: “GESTOPPT” = STOPPED” translate: “ABGEBROCHEN” = “ABORTED” // [Optional assuming /ras switch is used] translate: “Bericht” = “Report” Note: As soon as we translate word/phrase into English, we can use English Names, i.e. word – “Report” in resulting output of Template Tags and Properties. The templates must be defined using native language. Translations can be used to redefine any source word/phrase to any new word/phrase. Template Example:Based on provided translations the interface can create and populate PI Tags and PI Properties from templates in native language. For example, consider the following tag template: Tag[1].Name = [Unit] abc_[Parameter,value=”Bericht”] Tag[1].Value = [Value]:def Tag[1].type = string Tag[1].unitalias = Some Bericht Tag[1].Descriptor = Bericht for Unit: [Unit] Tag[1].EngUnits = just text
These templates are triggered by parameter – Bericht (German word for – Report) as it is found in the data source and the tag name and PI Property value will be based on native language parameter name. Assume that there is a particular row with unit field containing value: “U101” and associated Value field containing value: “testing”. In this case PI Tag name is defined as: “U101 abc_Bericht” and tag value is defined as: “testing:def”. With the use of language translations we can create tag where foreign word/phrase is replaced with translated word/phase. For example: translate: “Bericht” = “Report” translate: “testing” = “1” Then resulting Tag name would be: “U101 abc_Report” and Tag value would be “1:def” The same logic is applicable to the property template definitions. Translations are not case sensitive. Language translations don’t have to be defined prior to the tag or property template definitions, they can be defined anywhere within the INI file.
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:
|