Diagnostics and service
5.7 HMI Analyzer
HMI Advanced (IM4)
Commissioning Manual, 03/2009, 6FC5397-0DP10-3BA0
165
5.7.4 Application Examples
(1) OEM application that is linked-in does not start
Problem:
An OEM application was linked into HMI-Advanced, but it does not start after actuating the
corresponding softkey or it starts another application.
Possible cause:
Due to the hierarchical execution of the HMI directory, the entry made in the Regie.ini file
was overwritten by an entry in another regie.ini file with a higher priority and is therefore not
in effect.
For example, an entry was made in the OEM directory:
[TaskConfiguration]
Task6 = name := TestApp, Timeout := 10000, PreLoad := True
This is then overwritten in the user directory:
[TaskConfiguration]
Task6 = <empty>
Figure 5-11 Checking the start of the OEM application
HMI Analyzer:
Under Files → HMI, the regie.ini is selected. The resulting regie.ini file from all the HMI
directories is now displayed (mmc2, hmi_adv, add_on, oem, user). Now it becomes clear
whether the entry that was made is also truly active or was overwritten by another entry. In
addition, it is possible to recognize which HMI directory the entry comes from.
To Next Page
Loading...
Need help?
General
