SINUMERIK Integrate Create Animated elements 1

___________________
MyHMI /3GL

SINUMERIK

SINUMERIK 840D sl
SINUMERIK Integrate Create
MyHMI /3GL

Programming Manual

Valid for:

CNC software V4.7 SP3

03/2017
Legal information
Warning notice system
This manual contains notices you have to observe in order to ensure your personal safety, as well as to prevent
damage to property. The notices referring to your personal safety are highlighted in the manual by a safety alert
symbol, notices referring only to property damage have no safety alert symbol. These notices shown below are
graded according to the degree of danger.

DANGER
indicates that death or severe personal injury will result if proper precautions are not taken.

WARNING
indicates that death or severe personal injury may result if proper precautions are not taken.

CAUTION
indicates that minor personal injury can result if proper precautions are not taken.

NOTICE
indicates that property damage can result if proper precautions are not taken.
If more than one degree of danger is present, the warning notice representing the highest degree of danger will
be used. A notice warning of injury to persons with a safety alert symbol may also include a warning relating to
property damage.
Qualified Personnel
The product/system described in this documentation may be operated only by personnel qualified for the specific
task in accordance with the relevant documentation, in particular its warning notices and safety instructions.
Qualified personnel are those who, based on their training and experience, are capable of identifying risks and
avoiding potential hazards when working with these products/systems.
Proper use of Siemens products
Note the following:

WARNING
Siemens products may only be used for the applications described in the catalog and in the relevant technical
documentation. If products and components from other manufacturers are used, these must be recommended
or approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and
maintenance are required to ensure that the products operate safely and without any problems. The permissible
ambient conditions must be complied with. The information in the relevant documentation must be observed.

Trademarks
All names identified by ® are registered trademarks of Siemens AG. The remaining trademarks in this publication
may be trademarks whose use by third parties for their own purposes could violate the rights of the owner.
Disclaimer of Liability
We have reviewed the contents of this publication to ensure consistency with the hardware and software
described. Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the
information in this publication is reviewed regularly and any necessary corrections are included in subsequent
editions.

Siemens AG Order number: 6FC5397-3FP40-0BA0 Copyright © Siemens AG 2017.

Division Digital Factory Ⓟ 12/2015 Subject to change All rights reserved
Postfach 48 48
90026 NÜRNBERG
GERMANY
Table of contents

1 Animated elements ................................................................................................................................. 5

1.1 Introduction ............................................................................................................................... 5
1.2 Modeling ................................................................................................................................... 7
1.2.1 Requirements ............................................................................................................................ 7
1.2.2 Rules for modeling .................................................................................................................... 7
1.2.3 Importing graphics (models) ...................................................................................................10
1.2.4 Modeling templates .................................................................................................................12
1.3 XML commands ......................................................................................................................13
1.3.1 Overview .................................................................................................................................13
1.3.2 Structure of the scene description file.....................................................................................13
1.3.3 Mirroring and rotations ............................................................................................................16
1.3.4 View type ................................................................................................................................17
1.4 Conversion to hmi file .............................................................................................................18
1.5 Display in Create MyHMI /3GL ...............................................................................................19
1.5.1 X3D Viewer .............................................................................................................................19
1.5.2 Class SlX3dViewerWidget ......................................................................................................19
1.5.3 Public methods .......................................................................................................................19
1.5.4 Public slots ..............................................................................................................................20
1.5.5 Libraries ..................................................................................................................................21
1.5.6 Implementation example .........................................................................................................21
1.5.7 Machine data ..........................................................................................................................21
1.5.8 Notes about use ......................................................................................................................21
1.6 Display in Run MyScreens ......................................................................................................22

SINUMERIK Integrate Create MyHMI /3GL

Programming Manual, 03/2017 3
Table of contents

SINUMERIK Integrate Create MyHMI /3GL

4 Programming Manual, 03/2017
Animated elements 1
1.1 Introduction

Introduction
The manual describes working with the X3D Viewer with which you can integrate animated
and non-animated graphical scenes (animated elements) – called help screens in the
following – into the graphical user interface of SINUMERIK Operate as of Version V4.7 SP1 .
You can show motion sequences and parameters in context-sensitive help screens. This
helps you to improve the operation of applications and make the user interface more
appealing.
Implementation of your initial idea to the final help screen is described in the steps below:
● Creation of graphical elements and 3D models for the help screens that will eventually
appear in the X3D Viewer (see Chapter Auto-Hotspot).
● Creation of the scene description file in which the model data of the graphics file will be
assigned to the scenes and animations to be displayed at particular points (see Chapter
Auto-Hotspot).
● Conversion of the X3D files and XML files into HMI files (see Chapter Conversion to hmi
file (Page 18)).
● C++ integration of the X3D Viewer into your own application (see Chapter Implementation
example (Page 21)).
● Application in Run MyScreens (see Chapter Display in Run MyScreens (Page 22)).

SINUMERIK Integrate Create MyHMI /3GL

Programming Manual, 03/2017 5
Animated elements
1.1 Introduction

Overview of the file formats

Figure 1-1 File formats

File format Description

.fxw Flux Studio (3D) graphics file
.x3d Model file in exchange format
.xml Definition file for animations and scenes
.hmi Output file for the X3D Viewer

SINUMERIK Integrate Create MyHMI /3GL

6 Programming Manual, 03/2017
 Animated elements
1.2 Modeling

1.2 Modeling

1.2.1 Requirements
The aim of the modeling is to create a file with the generated 3D models in .x3d file format,
an official standard for 3D contents.
Modeling is performed in the Flux Studio Web3D authoring tool . The Flux Studio Web3D
authoring tool is a freely available 3D modeling tool with versatile export and import options.

Requirements
● You have installed the Flux Studio Web3D authoring tool, Version 2.1.
● You are familiar with modeling and use of Flux Studio.
● File format .x3d is not described in any detail in this document, adequate knowledge of
the subject is assumed.

Note
You can download the Flux Studio Web3D authoring tool from the Internet via the following
link:
http://mediamachines.wordpress.com/flux-player-and-flux-studio

1.2.2 Rules for modeling

Observe the following rules when modeling. You will only be able to process your help
screen file if you have followed these rules correctly.

Rules for modeling

1. The time sensor must have the name "Animation".
2. All related elements must be assigned to a group.
3. All groups must be set to the following position:
x = 0, y = 0, z = 0
4. To make the groups invisible, the translation values are set as follows:
x = 1000000, y = 1000000 and z = 1000000
5. The following elements must have the same name both in the Flux Studio graphic models
and in the XML scene definitions (cf. Chapter Overview (Page 13)):
– Tool
– Cameras

SINUMERIK Integrate Create MyHMI /3GL

Programming Manual, 03/2017 7
Animated elements
1.2 Modeling

6. Before you can create a .x3d file you must make the following settings in dialog box
"Export Options":

Figure 1-2 Settings in the Export Options dialog box

7. We recommend the following settings for texts (see also the following dialog box):
– Texts must always be centered.
– The size of the text should be 0.2. This size allows you to position the text easily. The
text output by the X3D Viewer is in the font size of the user interface, irrespective of
this value.

Figure 1-3 Settings for text

SINUMERIK Integrate Create MyHMI /3GL

8 Programming Manual, 03/2017
 Animated elements
1.2 Modeling

8. To create hatching, use file schnitt.png as the texture. The lines always go from the
bottom left to the top right at an angle of 45°. You should set the scaling to 3 in both
dimensions. The rotation depends on the construction type and must be adapted
manually.

Figure 1-4 Settings for hatching

9. We recommend the following sizes/dimensions for the blanks:

– Cylinder for turning operation:
Length = 5.5 ; Radius = 1.4 (cf. template turning_blank.fxw)
– Cube for milling operation
x = 4.75 ; y = 3 ; z = 3 (cf. template milling_blank.fxw)

See also
XML commands (Page 13)

SINUMERIK Integrate Create MyHMI /3GL

Programming Manual, 03/2017 9
Animated elements
1.2 Modeling

1.2.3 Importing graphics (models)

In Flux Studio, you can import external graphics (models). You can store frequently used
models, such as tools, as .x3d or .hmi files centrally for further use as finished elements in
other help screens. You will find a list of supplied modeling templates in Chapter Modeling
templates (Page 12).
Complex objects can also be created with other modeling tools, such as Cinema4D, and
then imported.
A description of how you can reuse these models is given below.

Import as inline
Flux Studio uses the object "Inline" for importing .x3d files. It allows you to link in external
elements without multiplying the 3D data of these models.
Insert the object with menu item Create -> Create Inline. Then enter a file name in the object
properties.

Figure 1-5 Importing with object "Inline"

SINUMERIK Integrate Create MyHMI /3GL

10 Programming Manual, 03/2017
 Animated elements
1.2 Modeling

Importing 3D model data

Proceed as follows to import model data from a file.
1. Open dialog box "Flux Studio Accutrans3D Translation Utility" via menu item File ->
Import Other Format .
2. Select a format from the "File Types" list box. For example, to import a Cinema4D file,
select file type "3D Studio."
3. Then select a file with Select Files and start import.

Figure 1-6 Importing 3D model data

The model data from the Cinema4D file is inserted as a complete group. All cameras and
any other information that is additionally imported should be deleted. Only the graphics
elements of the Cinema4D file are required.

SINUMERIK Integrate Create MyHMI /3GL

Programming Manual, 03/2017 11
Animated elements
1.2 Modeling

1.2.4 Modeling templates

In this chapter, you will find a list of graphics elements on which you can base your design,
colors, and sizes. To maintain a uniform "look and feel" in the user interface, we recommend
using the style of the templates or the templates themselves for creating your own graphics.

General

Template Description
intersection_texture.png Texture for an sectioned area
rapid_traverse_line_hori.fxw Horizontal line to illustrate the tool traversing path
during rapid traverse
rapid_traverse_line_vert.fxw Vertical line to illustrate the tool traversing path
during rapid traverse
feed_traverse_line_hori.fxw Horizontal line to illustrate the tool path during
feed
feed_traverse_line_vert.fxw Vertical line to illustrate the tool path during feed
dimensioning_lines_hori.fxw Horizontal projection lines
dimensioning_lines_vert.fxw Vertical projection lines
z1_inc.fxw Horizontal dimension line with the identifier Z1
x1_inc.fxw Vertical dimension line with the identifier X1
3d_coordinate_origin.fxw 3D coordinate origin
3d_zero_point.fxw 3D zero point

Turning

Template Description
turning_blank.fxw The blank for turning technology: A simple cylin-
der
turning_centerline.fxw Center line
turning_centerpoint.fxw Coordinate origin to display the zero point in the
WCS
turning_refpoint.fxw Reference point, for example, for a machining
operation
turning_machining_area.fxw Boundary lines for the machining area

Milling

Template Description
milling_blank.fxw The blank for milling technology: A simple cube
milling_centerline.fxw Center line
milling_refpoint.fxw Reference point, for example, for a machining
operation

SINUMERIK Integrate Create MyHMI /3GL

12 Programming Manual, 03/2017
 Animated elements
1.3 XML commands

1.3 XML commands

1.3.1 Overview
The scene description file (extension .xml) is required so that the X3D Viewer can access the
graphics. In the scene description file, you assign the scene names that are called from the
configuration to the times in the .x3d file (time sensor) at which the graphics are positioned.

1.3.2 Structure of the scene description file

The structure of the scene description file is shown below together with an explanation of the
relevant XML commands:

Design and description

<!-- Treatment of the plane-dependent texts for turning -->

<TextPlane plane="G18_ZXY" />

Description

<TextPlane plane="G18_ZXY" /> Treatment of the plane-dependent texts (axis

names) specifically for turning. If, for example, a text
with the identifier "Z" is used (for G18 first geometry
axis), the corresponding geometry axis identifier of
the control will be shown in the help screen (for ex-
ample, "Z").

<!--Text alignment -->

<TextPosition center='true' />

Description

<TextPosition center='true' /> Marking that the texts are centered. This is relevant
to the display of the texts in rotated screens. We
recommend using this setting.

SINUMERIK Integrate Create MyHMI /3GL

Programming Manual, 03/2017 13
Animated elements
1.3 XML commands

<!--Adapting the tool speed -->

<ToolSpeedFactors planeSpeedFactor="0.4" rapidSpeedFactor="0.7"
reducedSpeedFac¬tor="1.0"/>

Description

<ToolSpeedFactors This entry can be added if the tool speeds are to be

modified.
planeSpeedFactor="0.4" Factor for the feedrate ( 0.4 = 40% )
rapidSpeedFactor="0.7" Factor for rapid traverse ( 0.7 = 70% )
reducedSpeedFactor="0.1" /> Factor for a third speed ( 0.1 = 10% )

<!--Definition of an animation-->
<SceneKey name='BoringAnimation' masterRotationSpeed="-64.0"
maxRotAngle="45.0" begin-Time='0.110 endTime='0.118 view='camiso'
speedMaster='boringtool' Type="VIEW_3D_TURN_CYL">

Description

<SceneKey name='BoringAnimation' Name of the animation

masterRotationSpeed="-64.0" Direction of rotation and rotation speed of the tool.
The setting is optional.
maxRotAngle="45.0" To avoid aliasing effects (tool seems to be turning in
the wrong direction). The value is usually a fourth of
the symmetry of the tool.
The setting is optional.
beginTime='0.110 Start time of the animation on the time sensor
endTime='0.118' End time of the animation on the time sensor
view='camiso' Camera to be used for the animation
speedMaster='boringtool' Name of the tool for the animation
type="VIEW_3D_TURN_CYL"> View type defines the view (see Section View type
(Page 17))

<!-- Elements -->

<Element name='1' time='0.110' feed='rapid' dwell=’2’/>
<Element name='2' time='0.112' feed='rapid'/>
<Element name='3' time='0.114' feed='rapid'/>
<Element name='4' time='0.116' feed='plane'/>
<Element name='5' time='0.118' feed='plane'/>

Description

<Element name='1' Specifies that it is the first element of the animation.

time='0.110' Time of the first element on the time sensor

SINUMERIK Integrate Create MyHMI /3GL

14 Programming Manual, 03/2017
 Animated elements
1.3 XML commands

feed='rapid' Traversing speed of the element

plane = machining feedrate
rapid = rapid traverse
reduced = reduced speed, slower than "plane"
dwell=’2’/> Pause in the traversing motion of the animation. A
rotating tool continues to rotate.

<!-- End of animation definition -->

</SceneKey>

Description

</SceneKey> End of the animation definition

<!-- Existing animation as source for a new animation -->

<SceneKey source=''BoringAnimation' name=''BoringAnimationRear' mirror='
MirrorScreenX ' />

Description

<SceneKey source=''BoringAnimation' Name of an animation that is to use another

animation as its source.
name=''BoringAnimationRear' Name of the new animation based on the
source
mirror=' MirrorScreenX ' /> Mirroring in the direction of the X axis, output
is in the new animation.

<!-- Definition of a static scene (screen), (four examples) -->

<SceneKey name='Default' time='0.026' view='camiso'
type="VIEW_3D_DRILL_CUT"/>
<SceneKey name='Cut' time='0.046' view='camside' type="VIEW_SIDE"/>
<SceneKey name='Z1ink' time='0.056' view='camside' type="VIEW_SIDE"
highLightedGroup='dad_Z1ink'/>
<SceneKey name='Z1abs' time='0.066' view='camside' type="VIEW_SIDE"
highLightedGroup='dad_Z1abs'/>

Description

<SceneKeyname=’Z1abs' Screen name

time='0.066' Time of the screen on the time sensor
view='camside' Camera to be used for the screen

SINUMERIK Integrate Create MyHMI /3GL

Programming Manual, 03/2017 15
Animated elements
1.3 XML commands

type="VIEW_SIDE" View type defines the view (see Section View

type (Page 17))
highLightedGroup='dad_Z1abs'/> Name of the group to be highlighted. The
group has been called "Z1abs" in Flux Studio.
The prefix "dad_" is automatically added by
Flux.

<!-- End of xml file –!>

1.3.3 Mirroring and rotations

Mirroring or rotation of the image or model is defined with the mirror command.

Description

mirror="RotateScreenX" The screen is rotated around the X axis

mirror="RotateScreenY" The screen is rotated around the Y axis
mirror="RotateScreenZ" The screen is rotated around the Z axis
mirror="MirrorScreenX” The screen is mirrored along the X axis
mirror="MirrorScreenY" The screen is mirrored along the Y axis
mirror="MirrorScreenZ" The screen is mirrored along the Z axis
mirror="RotatePieceX” The model is rotated around the X axis
mirror="RotatePieceY" The model is rotated around the Y axis
mirror="RotatePieceZ" The model is rotated around the Z axis
mirror="MirrorPieceX" The model is mirrored along the X axis
mirror="MirrorPieceY" The model is mirrored along the Y axis
mirror="MirrorPieceZ" The model is mirrored along the Z axis
All rotate and mirror options can be combined. A rotation angle must be defined for rotation.

Examples
mirror="RotatePieceZ=180"
mirror="RotatePieceZ=-90 MirrorScreenX"
mirror="RotateScreenY=90"
mirror="MirrorPieceX MirrorPieceY"
mirror="MirrorPieceZ RotatePieceX=-90"

SINUMERIK Integrate Create MyHMI /3GL

16 Programming Manual, 03/2017
 Animated elements
1.3 XML commands

1.3.4 View type

You define the views with the view type. The views are based on empirical values and rules
that produce a sensible representation of the objects.
This ensures that the representation of the objects matches the coordinate system settings
made in the user interface (MD52000 $MCS_DISP_COORDINATE_SYSTEM or MD52001
$MCS_DISP_COORDINATE_SYSTEM_2).

Description

"VIEW_STATIC" Direct view without conversion

"VIEW_3D_TURN_CYL" 3D view for turning operations (cylinder)
"VIEW_3D_MILL_CUBE" 3D view for milling operations (cube)
"VIEW_3D_DRILL_CUT" 3D view for drilling operations (sectional view)
"VIEW_SIDE" 2D view for drilling operations (sectional view)
"VIEW_TOP_GEO_AX_1" 2D view from the direction of the 1st geometry axis
"VIEW_TOP_GEO_AX_2" 2D view from the direction of the 2nd geometry axis
"VIEW_TOP_GEO_AX_3" 2D view from the direction of the 3rd geometry axis

SINUMERIK Integrate Create MyHMI /3GL

Programming Manual, 03/2017 17
Animated elements
1.4 Conversion to hmi file

1.4 Conversion to hmi file

Note
The X3D files and their associated XML files are converted to HMI files when the HMI is
powered up.
For each X3D file, a corresponding XML file of the same name must be created. To do this,
you store the X3D files and XML files in directory search path of HMI\ico\x3d\turning or
milling. You proceed in the same way with the .ts files.

SINUMERIK Integrate Create MyHMI /3GL

18 Programming Manual, 03/2017
 Animated elements
1.5 Display in Create MyHMI /3GL

1.5 Display in Create MyHMI /3GL

1.5.1 X3D Viewer

If you want to display particular help screens in a separate OA application you must integrate
the X3D Viewer widget into its own OA application.
The X3D Viewer widget provides interfaces, which enable X3D contents to be presented in
the HMI.
Class SlX3dViewerWidget is provided for displaying graphical scenes. The definition of the
class can be found in the corresponding slx3dviewerwidget.h header file in the global GUI
include directory \hmi_prog\gui\include.

1.5.2 Class SlX3dViewerWidget

The class provides a flexible widget that autonomously displays the contents of a model file
specified during runtime and, if required, runs the animation.
The interface of the class comprises the Constructor, Destructor, and two methods for
controlling the graphical output.
As a direct derivative of the Qt class QWidget, a much more expansive interface is available,
which will not be described in any further detail here, (for example, show(), hide() and
resize(...). For more information, please refer to the Qt documentation).

1.5.3 Public methods

SlX3dViewerWidget ( QWidget* pParent = 0 )

Constructor of the X3D Viewer widget.

Parameters Meaning
pParent The parameter is passed on to the constructor of
the Qwidget.

~SlX3dViewerWidget ( )
Destructor of the X3D Viewer widget.

Parameters Meaning
- -

SINUMERIK Integrate Create MyHMI /3GL

Programming Manual, 03/2017 19
Animated elements
1.5 Display in Create MyHMI /3GL

1.5.4 Public slots

void viewSceneSlot ( const QString& rsFileName, const QString& rsScene, const QString&
rsAnimationScene, int nChannel, int nPlane, SlStepTechnology nTechnology )
With the viewSceneSlot method, the X3D Viewer is instructed to load the rsScene static
scene and the rsAnimationSzene animated scene from the rsFileName file and display them
alternately.
The static scene and then the animated scene are repeatedly alternately displayed for a
fixed time.
If no static scene is specified, the animation will be shown immediately; an animated scene
may also not have been specified.
Channel number, plane and technology are used to rotate the scenes to the correct position
(depending on the set machine coordinate system).

Parameters Meaning
rsFileName Name of the file that contains the scenes to be
displayed
rsScene Name of the static scene.
rsAnimationScene Name of the animated scene.
nChannel Channel number
nPlane Plane
nTechnology Technology
The following constants are defined for the
SlStepTechnology enumeration type:
• SL_STEP_NO_TECHNOLOGY
• SL_STEP_MILLING
• SL_STEP_TURNING
• SL_STEP_SURFACE_GRINDING
• SL_STEP_CIRCULAR_GRINDING

void viewSceneSlot ( const QString& rsFileName, const QString& rsScene, const QString&
rsAnimationScene )
A simplified form of the viewSceneSlot method with which the X3D Viewer can be instructed
to load and display the rsScene static scene and/or the rsAnimationSzene animated scene
from the rsFileName file.

Parameters Meaning
rsFileName Name of the file that contains the scenes to be
displayed.
rsScene Name of the static scene.
rsAnimationScene Name of the animated scene.

SINUMERIK Integrate Create MyHMI /3GL

20 Programming Manual, 03/2017
 Animated elements
1.5 Display in Create MyHMI /3GL

1.5.5 Libraries
In order to be able to apply the X3D Viewer in your own projects, the list of library
dependencies must be extended by the 'slx3dviewer.lib' entry.

1.5.6 Implementation example

You will find an implementation example in the package Create MyHMI/3GL under
\examples\GUIFrameWork\SlExGuiX3D.

1.5.7 Machine data

Display MD 9104 $MM_ANIMATION_TIME_DELAY
Time delay in seconds until the animation is started for help screens. The setting does not
apply to help screens that are only animated.
The setting applies globally to all animations of SINUMERIK Operate.

1.5.8 Notes about use

● The animation is interrupted if the X3D Viewer widget is hidden. If this happens, there is
no need to choose a scene selection without animation.
● You should avoid frequent or multiple instantiation of the X3D Viewer widget as this
reduces performance and memory capacity. The use (implementation) of an X3D Viewer
Singleton is recommended in such application scenarios.
● The X3D Viewer can also be used in signal slot concepts.
● If an error occurs (for example, a file not found or unknown scene name), the X3D Viewer
widget opens a message area. This area is automatically hidden again when another
help screen is activated.

SINUMERIK Integrate Create MyHMI /3GL

Programming Manual, 03/2017 21
Animated elements
1.6 Display in Run MyScreens

1.6 Display in Run MyScreens

This section is intended for experienced "Run MyScreens" developers. Necessary
background knowledge is provided in the associated documentation.
In addition to using screens in .bmp or .png format, animated help screens can also be
displayed with the X3D Viewer.
To integrate help screens, use the Run MyScreens interface in the usual way.
To output images in .bmp or .png format, XG0 is entered in the definition of a dialog box in
the Attributes section or the parameter is left empty. To integrate X3D help screens in a
dialog, you must enter XG1 in the attributes.

//M(MASK_F_DR_O1_MAIN/$85407////52,80/XG1)

The following parameters are required to activate the individual help screens; their meaning
is described in Section 5.3 Public slots:
1. File name
2. StaticScene (optional)
3. AnimationScene (optional)
4. Technology (optional)
5. Plane (optional)
The parameters are combined into a character string in this order, separated by a comma.

Hlp = "File name,StaticScene,AnimationScene,Technology,Plane"

Examples
● The default help screen can be set with the specified variable Hlp.
In the following example, the "MyAnimation" animation is output from the
"MyDlgHelp.hmi" file. No StaticScene is specified, i.e. no static scene is output. No
specifications are made for the Technology and Plane, i. e. default values are used.
Hlp = "MyDlgHelp.hmi,,MyAnimation"

● The hlp property can be set on a specific help screen for the individual parameters of the
input screen.
In the following example, the static "MyParam" scene and the "MyAnimation" animation
are output from the "MyDlgHelp.hmi" file in the G17 plane. No specification is made for
the Technology, i.e. a default value is used.
VarMyParam.hlp = "MyDlgHelp.hmi,MyParam,MyAnimation,,G17"

SINUMERIK Integrate Create MyHMI /3GL

22 Programming Manual, 03/2017