Siemens SINUMERIK 840D sl Commissioning Manual page 101

1. Open the file "slaesvcadapconf.xml" already created for the in-house alarm texts in the
2. Remove the lines "<!-- Start of comment" and "End of comment -->".
3. Enter the identifier, e.g. <Identifier type="QString" value="OEM"/>. The identifier is always
4. Enter the correct BaseName, e.g. <BaseName type="QString"
5. Enter the ContextName, e.g. <ContextName type="QString" value="oem_contextEM"/>.
Inserting several identifiers:
1. Mark and copy the definition area <OEM_IndexText_01> to </OEM_IndexText_01>.
2. Insert the area before the tag </IndexTexts>.
3. Change the names of the opening and closing tags, as well as the abovementioned fields
Restart the HMI sl
So that the "Alarm&Event Service" can read the new parameter texts, they must be
converted from the ".ts" format into binary format. Thus files with the same name with the file
extension ".qm" are created in the same folder.
Restart HMI sl. This data is only converted during startup. The result of the conversion is
written into the file "alarmtext_conversion.log". Errors that occur during the conversion, such
as syntax errors in a parameter file, are also written to the file.
HMI sl (IM9)
Commissioning Manual, 07/2007, 6FC5397-1DP10-2BA0
folder /OEM/sinumerik/hmi/cfg or /User/sinumerik/hmi/cfg
stated in pointed brackets next to the parameter specification in the alarm text, e.g.
%1<OEM>.
value="oem_indexparams"/>.
"Identifier," "BaseName," and "ContextName."
Note
To prevent overlaps, use different names for the opening and closing tags of the
definition area.
The names "IndexText_01" to "IndexText_99" are reserved for Siemens.
Configuring alarms
10.1 Creating alarm texts
95