Integrating an OEMFrame application into HMI sl

The Windows OEMFrame applications are used to generate and use softkeys. The required settings are described in this chapter based on an example.

You will have to modify or create the following files:

• Configuration file "systemconfiguration.ini"

• Configuring the start softkey

  In order to start an OEMFrame application from the operating software, configure a softkey on the expansion bar of the operating area.

In file "systemconfiguration.ini", save the call for Manage MyMachines /Remote Service Client accordingly. Depending on the access protection level assigned to you, you extend the "systemconfiguration.ini" file contained in the relevant directory.

<HMIInstallDir>\\hmi\oem\sinumerik\hmi\cfg

<HMIInstallDir>\\hmi\addon\sinumerik\hmi\cfg

<HMIInstallDir>\\hmi\ \user\sinumerik\hmi\oem\

Extensions

Add the following line to the [areas] section:

AREA500=name:=MMMR, process:=ProcessOEM

Add the following line to the [processes] section:

PROC500=process:=ProcessOEM, cmdline:="C:\\Program Files (x86)\\Siemens\\MMMR SC\\ManageMyMachinesRemoteServiceClientMO.exe", oemframe:=true, deferred:=true, classname:="QWidget"

Adjust the indexes of the relevant entries (PROC500, AREA500) in accordance with your HMI configuration.

The path for the executable file of the service mode client can differ from the path stated above, depending on the version installed (32 bit/64 bit) and the path selected during installation.

You can find further information about the options for integrating OEMFrame applications in the SINUMERIK Operate Commissioning Manual.