Creating Texts For Indexed Alarm Parameters - Siemens SINUMERIK 840D sl Commissioning Manual

Configuring alarms
13.2 Configuring alarm and message texts via alarm text files
Example:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<!-- Configuration of the Solutionline Alarm & Event Service Adapter -->
<CONFIGURATION>
</CONFIGURATION>
Restart SINUMERIK Operate
The files must still be converted into a binary format so that the alarm texts can be displayed
during the program runtime. This data is only converted during power up.
To do this, restart SINUMERIK Operate. In the same directory where the .ts files are located,
files with the same name are created with the ".qm" file extension.
The result of the conversion is written to the "alarmtext_conversion.log" or
"oem_text_conversion.log" file. Errors that occur during the conversion, such as syntax
errors in a parameter file, are also written to the file.
This file is located in the "/user/sinumerik/hmi/log" directory.
Note
The conversion is only made if the .ts file is newer than the associated .qm file.
13.2.2

Creating texts for indexed alarm parameters

If a string, the so-called "Index identifier", is specified in the alarm text in pointed brackets
after a space holder (e.g. "%1&lt;OEM&gt;"), the parameter itself is not inserted in the alarm
text, but a text from another alarm text file, a so-called index text file. In this case, the alarm
parameter value serves as index in order to select the text in the index file. The index text
can, in turn, include parameters, also index parameters.
Note
Explanation for the "Index identifier" string
• "&lt;" ≙ opening pointed bracket "<"
• "&gt;" ≙ closing pointed bracket ">"
202
<AlarmTexts>
<BaseNames>
<OEM_BaseName_01 type="QString" value="my_alarms"/>
</BaseNames>
</AlarmTexts>
...
Commissioning Manual, 03/2013, 6FC5397-1DP40-3BA1
SINUMERIK Operate (IM9)