Softkey menus or dialogs that are possibly included are ignored. If a softkey has a command
without
file information, e.g. LM ("test"), as the required softkey menu or dialog is contained in
the same file, then the corresponding file name is supplemented in the internal merge version
so that in this case, no changes are required. The merge configuration contained is then
subsequently displayed.
3.4 Troubleshooting (log book)
Overview
If "Run MyScreens" detects errors when interpreting the configuration files, these errors will
be written to the easyscreen_log.txt text file. Only errors of the currently selected dialog are
entered. Error entries from previously selected dialogs are deleted.
The file indicates:
● The action during which an error occurred
● The line and column number of the first faulty character
● The entire faulty line of the configuration file
● The entries made by the DEBUG function
Note
Each entry has a prefix with the current time stamp in square brackets. This can be helpful,
for example, when analyzing time-critical configurations.
Saving easyscreen-log.txt
The file easyscreen_log.txt is saved in the following directory:
[System user directory]
/log
Syntax
The system does not start to interpret the syntax until the start softkey has been defined and
a dialog with start and end identifiers as well as a definition line has been configured.
//S(Start)
HS6=("1st screen")
PRESS(HS6)
LM("Maske1")
END_PRESS
//END
//M(Maske1)
Fundamentals
3.4 Troubleshooting (log book)
SINUMERIK Integrate Run MyScreens
Programming Manual, 10/2015, 6FC5397-3DP40-5BA3 31
To Next Page
Loading...
Need help?
General
