Dynamic Limit Text

Previous chapterNext chapter Show allShow all    Hide allHide all

The dynamic limit text allows it to include the current values of other variables in the limit text of a variable or a Reaction matrices (Rema). At that a fixed text can be linked via an index with key words generated from a language table (see also Using key words in text lists ). In the Runtime this limit text can be displayed in the Alarm Information List, Chronologic Event List and/or the alarm status bar. In the dynamic elements Link text and Status the dynamic limit text cannot be displayed.

Syntax

The following syntax is valid for the parameterization of the limit texts:

Parameters

Description

$

Denotes a dynamix limit text; this character must be on the first position in the limit text.

;

Seperator of commands Is used in order to separate the constant text from the dynamic text. When separating variables, no space must be left between the separator and the variable.

@Text

Text from the currently loaded language table

%PV

Value of another variable with the name „PV"

@Text+%PV

Composed keyword for the text from the currently loaded language table. Here the value of variable 'PV' is saved and when being displayed a text is searched in the language table which is a combination of 'text' and variable value.

This text encoding works only for the Alarm Message List or the Chronological Event List. In text elements this functionality is not available. The using of combined keywords makes it possible to create dynamic limit texts which can have more than 80 characters.

Example Example 1

Limit text = $@Text; X-Pos ;%Value1; Y-Pos ;%Value2

The following preconditions are valid:

  • @Text is a key word in the language table corresponding to „Text from table"
  • Value1 is an integer variable with the value 14
  • Value2 is an integer variable with the value 12

Output = Text from table X-Pos 14 Y-Pos 12

Example Example 2

$OFF in position ;%String1

The following preconditions are valid:

  • %String1 is a string variable with the content „ORT"

Output = OUT in position ORT

Example Example 3

$%@message_+value1
The following prerequisites apply:

  • @message_ is a part of a keyword in the language table
  • Value1 is an integer variable with the value 12

With the combined keyword, the result is the keyword „message_12" and the corresponding text from the language table

Example Example 4

$%@message_+String1
The following prerequisites apply:

  • @message_ is a part of a keyword in the language table
  • String1 is a string variable with the content „zenon".

With the combined keyword, the result is the keyword „message_zenon" and the corresponding text from the language table

Limits for dynamic limit texts

The storage of dynamic limit texts leads to a number of limits:

  1. Static text is stored in the storage area of the limit text:
    maximal 128 characters
  2. Values of the linked variables are stored in the storage area of the commentary text:
    maximal 80 character and maximal 3 variables.
  3. If dynamic limit texts are used, no commentaries can be used for these alarms.

This limits can be evaded:

Extension for long dynamic limit texts.

Variable values for dynamic limit texts can be evacuated in an own file.

Requirements: In the project properties in group Alarm Message List the property Long limit texts AML resp. in group Chronological Event List the property Long limit texts CEL is active.
Instead of the commentary field the values are stored in an own file. 264 bytes are available per limit. Per variable 8 bytes of these are used for internal structure information.

Example1 Dynamic limit with a string variable:
Of the 264 byte

Example 2 Dynamic limit with a string variable and a word variable:
Of the 264 byte

The strict limitation to three variables per limit text no longer exists.
The file names for the additional created files are Dxxx.aml bzw. Dxxx.cel.
For the ring buffer the additional information is saved in aml.bin und cel.bin.

Error texts during Runtime:

Parameters

Description

XXX

The value of a linked varieble has changed.

---

values of linked variables are not available (can happen at program start).

>3

number of linked variables is higher than 3 (so value cannot be saved).