Siemens SINUMERIK 840D sl Commissioning Manual page 637

Fundamentals
3.1 Structure of configuration file
Introduction
The defining data for new user interfaces are stored in configuration files. These files are
automatically interpreted and the result displayed on the screen. Configuration files are not
stored in the software supplied and must be set up by the user.
An ASCII editor (e.g. notepad or the integrated editor of the user interface) is used to create
configuration files. The description can also be explained using comments. A ";" is inserted
as comment character before every explanation.
Note
COM files can also always be saved as ASCII files.
If texts, e.g. for softkey labels are entered into the configuration directly and not via the text
ID (for reading from the language files), then the COM files must be saved as UTF-8,
otherwise the text will not be correctly displayed.
However, keywords - also in an UTF8-coded COM file - may only comprise characters that
are contained in the ASCII character set. Otherwise the interpretation and therefore the
display of the screen forms/dialogs cannot be guaranteed.
Language files are always saved as UTF-8, as they only contain text.
Note
When using HMI Operate in the NCU, note that all file names are written in lower case letters
(com, png, txt) on the CF card. This is required because of Linux.
On the PCU, you can write file names either in upper case or lower case letters.
Configuration
Each HMI application has permanent start softkeys, which can be used to access newly
generated dialogs.
In the event of "Load a screen form" (LM) or a "Load softkey menu" (LS) call in a
configuration file, a new file name containing the object called can be specified. This makes
it possible to structure the configuration, e.g., all functions in one operating level in a
separate configuration file.
SINUMERIK Integrate Run MyScreens (BE2)
Programming Manual, 03/2013, 6FC5397-1DP40-3BA1
3
19