</Type>
</Types>
<Sources>
<Source CatLink="1" SourceID="0" SourceURL="/NCK">
<Alarms>
<Alarm AlarmID="10000">
<MSGTEXT>myNckAlarms|10000/NCK</MSGTEXT>
</Alarm>
</Alarms>
</Source>
</Sources>
</SlAeAlarmAttributes>
Registering the alarm attribute file
The alarm attribute file still has to be registered in order that the standard alarm texts are
replaced during the program runtime:
1. You can copy a sample configuration file "oem_slaesvcconf.xml" from the following
directory: /siemens/sinumerik/hmi/template/cfg
2. Save or create the file in the /oem/sinumerik/hmi/cfg or
/user/sinumerik/hmi/cfg directory.
3. Change the name to "slaesvcconf.xml".
4. Open the file and in the <DataBases> tag enter the name of the alarm attribute file, e.g.
<OEM_DataBase_01 type="QString" value="my_nck_alarms_db">
Note
The names of the <DataBases> tag can be freely selected. They must be unique in the
system and must not clash with names used by Siemens.
The <Siemens_DataBase_01> tag name is reserved for Siemens.
If you register additional alarm attribute files, i.e. you wish to include them in the
configuration file, use the names <OEM_DataBase_02>, <OEM_DataBase_03>, etc.
Restart SINUMERIK Operate
The files with the alarm texts and the attribute file still have to be converted into a binary format
in order 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 or the alarm
attribute file are located, files with the same name are created with the ".qm" and .hmi 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.
Configuring alarms
13.2 Configuring alarm and message texts via alarm text files
SINUMERIK Operate (IM9)
Commissioning Manual, 12/2017, 6FC5397-1DP40-6BA1 273
To Next Page
Loading...
Need help?
General
