PJE 0801 en

SINUMERIK 840D/810D
HMI Embedded Configuring

Package
Description of Functions
Manufacturer/Service Documentation
08.2001 Edition
SINUMERIK 840D/810D
HMI Embedded Configuring
Package
Introduction
Installation
Configuring
Working with
Microsoft Visual C and
HMI Embedded
Operating HMI
Embedded
Appendix
Valid for
Control
Software Version
SINUMERIK 840D
6
SINUMERIK 840DE (export version)
6
SINUMERIK 840D powerline
6
SINUMERIK 840DE powerline (export version)
6
SINUMERIK 810D
3
SINUMERIK 810DE (export version)
3
SINUMERIK 810D powerline
6
SINUMERIK 810DE powerline (export version)
6
08.2001 Edition
4
5
SINUMERIK Documentation
Printing history
Brief details of this edition and previous editions are listed below.
The status of each edition is shown by the code in the "Remarks" column.
Status code in the "Remarks" column:
A .... New documentation.
B .... Unrevised edition with new Order Number.
C .... Revised edition with new status.
If factual changes have been made on the page since the last edition, this is indicated by a new
edition coding in the header on that page.
Edition
Order No.
Comment
09.95
6FC5 297-2AC40-0BP0
09.96
6FC5 297-3EA00-0BP2
08.01
6FC5 297-6EA10-0BP0
This manual forms part of the documentation available on CD-ROM (DOCONCD)

Edition
Order No.
Comment
09.01
6FC5298-6CA00-0BG1
Trademarks
,
SIMATIC SIMATIC HMI, SIMATIC NET, SIROTEC, SINUMERIK and SIMODRIVE

are registered trademarks of Siemens AG. Other names in this publication might be
trademarks whose use by a third party for his own purposes may violate the rights of the
registered holder.
Further information is available on the Internet under:

http://www.ad.siemens.de/sinumerik
Other functions not described in this documentation might be executable in the

control. This does not, however, represent an obligation to supply such functions
with a new control or when servicing.
This publication was produced with WinWord V 8.0

and Designer V 7.0
The reproduction, transmission or use of this document or its contents is not
permitted without express written authority. Offenders will be liable for damages. All
rights, including rights created by patent grant or registration of a utility model or
design, are reserved.
We have checked that the contents of this document correspond to the hardware
and software described. Nonetheless, differences might exist and therefore we
cannot guarantee that they are completely identical. The information contained in
this document is, however, reviewed regularly and any necessary changes will be
included in the next edition. We welcome suggestions for improvement.
Subject to change without prior notice.
Siemens AG 1995 - 2001. All rights reserved.
Order No. 6FC5 297-6EA10-0BP0

Printed in the Federal Republic of Germany
Siemens-Aktiengesellschaft.
Contents
08.01
Preface
Structure of
documentation
SINUMERIK documentation is organized on three levels:

General Documentation
User Documentation
Target readership
This documentation is intended for manufacturers of machine tools with

SINUMERIK 840D/810D .
SINUMERIK 840D
powerline
Available from 09.2001 will be

SINUMERIK 840D powerline and
SINUMERIK 840DE powerline
with improved performance. A list of the available powerline modules can be
found in the Hardware Reference Manual /PHD/ in Section 1.1
SINUMERIK 810D
powerline
Available from 12.2001 will be

SINUMERIK 810D powerline and
SINUMERIK 810DE powerline
with improved performance. A list of the available powerline modules can be
found in the Hardware Reference Manual /PHC/ in Section 1.1
Objective
The lists serve as a reference work for installation and startup.
Search aids
To improve orientation, we have provided you with a list of contents, as well as

the appendices:
1. List of references
2. Index
Important
This manual is valid for: Software Release 6.
Notes
The following notes appearing in the documentation have special significance:
Siemens AG 2001. All rights reserved

SINUMERIK 840D/810D HMI Embedded Configuring Package (PJE) 08.01 Edition
Contents
08.01
Note
This symbol appears in the documentation to indicate that further information
is available.
Important
This symbol appears in the documentation to indicate that this information is

particularly important.
Warning notices
The following warning notices used in the brochure are graded in significance:
Danger
Warning
Caution
This warning notice means that death, severe physical injury or considerable
material damage will occur if the relevant safety precautions are not taken.
This warning notice means that death, severe physical injury or considerable
material damage may occur if the relevant safety precautions are not taken.
This warning notice (with a warning triangle) means that slight physical injury
or material damage may occur if the relevant safety precautions are not
taken.
Caution
This warning notice (without a warning triangle) means that material damage
may occur if the relevant safety precautions are not taken.
Important
This warning notice means that an unwelcome event or unwanted condition
may occur if the relevant notices are not complied with.
vi

Contents
08.01
Technical comments
Trademarks
IBM is the registered trademark of the International Business Corporation.

MS-DOS and WINDOWS are registered trademarks of the Microsoft
Corporation.

vii
Contents
08.01
Contents
Introduction ...............................................................................................................................1-9
1.1
Structure of documentation .............................................................................1-10
Installation ...............................................................................................................................2-13
2.1
Software update, fundamentals ......................................................................2-14
2.2
Hardware and software requirements for the HMI Embedded software

package "Screen Kit".......................................................................................2-15
2.3
Setup: Setting up the configuring environment for HMI Embedded ................2-16
2.4
Where can I find what? ...................................................................................2-25
Configuring..............................................................................................................................3-35
3.1
Overview .........................................................................................................3-38
3.2
Application manager - creating an application ................................................3-39
3.3
Configuring a project .......................................................................................3-47
3.4
Text converter - text principle..........................................................................3-51
3.5
Compiling the application configuration ..........................................................3-59
3.6
Linking the application areas...........................................................................3-69
3.7
Testing the configuration on a PC...................................................................3-71
3.8
Generating floppy disks...................................................................................3-71
3.9
Installing HMI Embedded on a PCU20 ...........................................................3-71
3.10
Installing HMI Embedded Win 32 on a PCU50 ...............................................3-84
Working with Microsoft Visual C and HMI Embedded .......................................................4-93

4.1
Using MS Visual Studio 6.0.............................................................................4-94
4.2
Using the MSVC Workbench ..........................................................................4-98
4.3
Known restrictions and incompatibilities .......................................................4-100
Operating HMI Embedded....................................................................................................5-101

5.1
HMI Embedded - test mode on a PC ............................................................5-102
5.2
PC simulation mode ......................................................................................5-103
5.3
PC MPI mode................................................................................................5-104
5.4
Key assignments in PC mode .......................................................................5-105
5.5
mmc0_con.cfg: Emulation of variables .........................................................5-108
Appendix............................................................................................................................... A-111
References .................................................................................................................. A-111
Index
viii
.......................................................................................................................I-123

Introduction
1.1
Structure of documentation .............................................................................1-10

1-9
1 Introduction
1.1
08.01
Structure of documentation
The documents describing the functions for configuring the operator interface
for the OP010/ OP010C/ OP010S/ OP012/ OP015 operator panels and the
HT6 handheld terminal using the HMI Embedded software are organized in the
following structure:
SINUMERIK 840D/810D
HMI Embedded Operator's Guide
Operator's guide for standard scope of operating functions
SINUMERIK 840D/840Di/810D Operator's Guide
HT6 Handheld Terminal
Operator's guide for standard scope of operating functions of HT6
SINUMERIK 840D/810D
HMI Embedded Configuring Package
Description of Functions: Software Update, Configuration, Installation
(the publication Configuring Syntax (PS) is supplied with the software as a pdf
file)
SINUMERIK 840D/840Di/810D
HMI/MMC Installation & Start-Up Guide
SINUMERIK 840D/810D
Description of Functions: Configuring the OP 030 Operator Interface
Section PS: Online only: Configuring Syntax (Configuring Package)
Another option for designing the operator interface can be found in:
SINUMERIK 840/840Di/810D
HMI/MMC Installation & Start-Up Guide
Sect. BE1: Expand the Operator Interface
1-10

08.01
Target readership
1 Introduction
This documentation is intended for use by machine tool manufacturers who

wish to design their own user interface for PCU20/HT6 or PCU50 hardware
using the HMI Embedded basic software as a base.
Note
The term "HMI Embedded" as used in this document always refers to the
software package irrespective of the target hardware.
Objective
The software described here and the associated description of functions will
enable the machine tool manufacturer to
create one or more operator interfaces of his own for HMI Embedded,
test the operator interface on a PC,
transfer the operator interface to the appropriate target hardware and put it
into operation and
create a machine-manufacturer-specific system master disk or application

master disk or text disk of the modified system for his own servicing
purposes.
Dependencies
The "HMI Embedded Configuring Package" used must match the relevant
SINUMERIK 840D/840Di/810D version.
Fundamentals
HMI Embedded can be configured to enable you to optimally adapt the

operator interface to the individual features of the relevant machine.
The basic system of the HMI Embedded software can be combined with a
variety of HMI Embedded applications (e.g. Machine, Parameters, Services,
Higraph Diagnosis (not for HT6), etc.).
You can create one or more of these applications using the "HMI Embedded
Screen Kit". You can call this application in the HMI Embedded main menu
(operating area key).
Configuring language
The structure of the configuring language is described in the online help file
"Configuring Syntax" which is included with the HMI Embedded configuring
package.
Software update
The software update is described in Section 2.

1-11
1 Introduction
08.01
The interface to the NCK control is described in

Interface to NCK
Operation
References: /LIS/
SINUMERIK 840D, 840Di/ 810D/

SIMODRIVE 611D
Description of Functions Lists
A description of how to operate HMI Embedded can be found in

References: /BEM/
SINUMERIK 840D/810D
HMI Embedded Operator's Guide
A description of how to operate the HT6 can be found in

References: /BAH/
Operator's Guide for HT6 Handheld Terminal
1-12

Installation
2.1
Software update, fundamentals ......................................................................2-14
2.2
Hardware and software requirements for the HMI Embedded software

package "Screen Kit".......................................................................................2-15
2.3
2.3.1
2.3.2
2.3.3
2.3.3.1
2.3.3.2
2.3.3.3
2.3.3.4
2.3.3.5
2.3.3.6
2.3.3.7
2.3.4
2.3.5
Setup: Setting up the configuring environment for HMI Embedded ................2-16

Preparations for installation.............................................................................2-16
Setup routine ...................................................................................................2-16
Initialization settings for MSVC Workbench / MS Visual Studio......................2-17
Creating and modifying tool entries in the development
environment ....................................................................................................2-18
Linking in the application manager..................................................................2-19
Linking in the general linkage process ............................................................2-19
Linking in the software configuration kit (SCK) ...............................................2-19
Linking in the text converter ............................................................................2-20
Linking in the online help.................................................................................2-20
Other extensions to the development environment.........................................2-21
De-installing the screen kit ..............................................................................2-22
Typical Setup errors ........................................................................................2-23
2.4
2.4.1
2.4.2
2.4.3
2.4.4
Where can I find what? ...................................................................................2-25

List identities for application area - mwl_app.h ...............................................2-32
Colors and gray shades - logiccol.h, vgadef.h ................................................2-33
Layout - size definitions for characters, windows, softkeys - size.h ................2-33
Keyboard events - key.h..................................................................................2-33

2-13
2 Installation
2.1
08.01
Software update, fundamentals

The setup and update process comprises four main steps:
1. Setup
Transfer of software components from CD or diskette(s) to the hard disk of

your PC, setup and configuring of the working environment.
2. Configuration
Creation of a special configuration comprising applications (Machine,

Parameters, Programming, Services, Diagnosis, Start-Up, System, MCU (not
HT6), Higraph Diagnosis (not HT6), OEM applications) to suit your
requirements.
Use the SCK (Software Configuration Kit) for this purpose.
3. Configuring
Creation of one or more customer operator interfaces using the configuring

macros in development environments MSVC Workbench or MS Visual
Studio 6.0.
4. Installation
Transfer of system software incl. applications and selected languages to the

HMI Embedded hardware.
2-14

08.01
2.2
2 Installation
Hardware and software requirements for

the HMI Embedded software package "Screen Kit"
Standard PC with
at least a 80386 processor (Pentium recommended),
at least 8 MB main memory,
a CD ROM drive and
a standard VGA graphics card (resolution at least 640x480 pixels)
Memory required for HMI Embedded environment (configuring, PC

simulation, HMI Embedded system) on the hard disk: Approx. 50 MB.
Windows 95 or Windows NT. (Please comply with the system requirements

specified by Microsoft).
Microsoft Visual C/C++ V1.0 ,V1.5x or Microsoft Visual Studio V6.0.
Main memory:
The Windows variant of the HMI Embedded PC Simulation is used per
default; this has no critical memory requirements.

2-15
2 Installation
08.01
2.3
Setup: Setting up the configuring environment for HMI

Embedded
2.3.1
Preparations for installation
The setup operation creates a directory TargetDrive:\name on a target drive of

your choice (C:, D:, or E:).
Description
The default directory name is mmc100pj.

The HMI Embedded configuring package is set up in this directory.
Windows NT only
On systems with Windows NT the configuring directories must be stored in the

root directory!
You must therefore set up the target directory before you start setup and
substitute this on a drive letter of your choice.
You need then only specify the drive letter for "system path" and "OEM
application path" during setup !
The use of a batch file, e.g. with the following contents, is recommended for
this purpose:
SUBST V: /D
SUBST V: TARGETDRIVE:\name
which you must execute every time before you use the HMI Embedded
configuring package.
Ignore the warning output by the setup program when you install it in the root
directory.
You can also call this batch file directly from your desktop using a link
e.g. C:\WINNT\system32\CMD.EXE /K C:\ht6_dvkit.bat
2.3.2
Setup routine
Description
2-16
Back up any configuration that may already exist.
Close MSVC and/or MS Visual Studio if it is open.
Insert the HMI Embedded SCREEN Kit CD into the CD drive.
Change to directory disk01 on the CD drive.
Start SETUP.BAT and follow the dialog (selection of source and target
drives, etc.).

08.01
2 Installation
Important
On systems with Windows NT, specify only the letter of the substituted drive!
It takes a few minutes to set up the configuring environment.
Edit file "CONFIG.SYS":
Use the SHELL command to increase the memory area for the DOS
environment to 2048 bytes (e.g. SHELL=<DOS_PATH>:\
COMMAND.COM <DOS_PATH>\ /E:2048 /P).
The SHELL command sets variable COMSPEC. If you set this variable
explicitly, for example, in your AUTOEXEC.BAT, the corresponding
extension must be made there.
If necessary, correct your LASTDRIVE entry in CONFIG.SYS to at least

drive "L". (LASTDRIVE=Z)
Reboot your computer to activate the entries in the CONFIG.SYS and

AUTOEXEC.BAT files.
Note
Section 2.3.3 below is relevant only if Setup was aborted as you were entering
the Windows and MSVC paths or the entries in the toolbars of MSVC
Workbench / MS Visual Studio were not completed!
In this case, the following entries must be made manually.
2.3.3
Initialization settings for MSVC Workbench / MS Visual Studio

Note
Necessary only if Setup has not been executed correctly.
Not required for MS Visual Studio.
Description
Start MS Windows and the MSVC Workbench.
Add your DOS directory or the Windows directory to the path for
DIRECTORIES .
"EXECUTABLE FILES PATH" in menu OPTIONS
Only then will the Make files be correctly executed.

2-17
2 Installation
2.3.3.1
08.01
Creating and modifying tool entries in the development

environment
This subsection describes how to modify and create tool entries in the MSVC
Workbench or MS Visual Studio development environment. You can use this
procedure to retro-install screen kit tools in your development environment
(e.g. because Setup cannot be executed properly). The entries you need to
make are described in the following subsections.
MSVC V1.xy
MSDEV V6.0
2-18
The MSVC Workbench offers you the option of configuring the entries in menu
OPTIONS
TOOLS. You must link in the tool entries here.
Open the dialog box for modifying tools by selecting menu options
OPTIONS
TOOLS. Select the entry you wish to change in the
"MENU CONTENTS" window or click on ADD to create a new entry.
Make your entries in the appropriate input fields. The entries "Use
Output Window" and "Close Window on exiting" do not exist on the
MSVC Workbench and can be ignored.
You can adapt the tool order in the menu to suit your requirements
using MOVE UP and MOVE DOWN.
Close the dialog box by selecting OK.
You can configure tool entries in MS Visual Studio by selecting menu options
TOOLS
CUSTOMIZE
TOOLS tab. You must link in the tool entries here.
Open the dialog box for modifying tools by selecting menu options
TOOLS
CUSTOMIZE
TOOLS tab. Select the entry you wish to
change in the "MENU CONTENTS" window or click on the NEW
symbol to create a new entry.
Make your entries in the appropriate input fields. You must enter the
"Menu Text" directly in the "MENU CONTENTS" list.
You can adapt the tool order in the menu to suit your requirements
using the arrow symbols.
Close the dialog box by selecting OK.

08.01
2.3.3.2
2 Installation
Linking in the application manager

Note
You can configure your entries in the MSVC Workbench by selecting menu
TOOLS. You must link in the application manager entries
options OPTIONS
here.
Make the following settings:
Command Line :
mmc100pj\Instutil\Appman.exe
Menu Text
:
A&pplicationmanager
Arguments
:
No Entry
Initial Directory :
mmc100pj\Instutil
Use Output Window
" Ask Arguments or. Prompt for Arguments
" Close Window on exiting
2.3.3.3
Linking in the general linkage process

Note
Command Line
:
mmc100pj\Instutil\si_make.exe
Menu Text
:
&Generate SL.DAT
Arguments (MSVC) :
-MSVC $proj
Arguments (Studio) :
$(WkspName)
Initial Directory
:
mmc100pj\Instutil
Use Output Window
" Ask for Arguments or. Prompt for Arguments
2.3.3.4
Linking in the software configuration kit (SCK)

Note
Command Line
:
mmc100pj\Sck\Sck.bat
Menu Text
:
&Installation-Kit
Arguments
:
No Entry
Initial Directory
:
mmc100pj\Sck
" Use Output Window
" Ask for Arguments or. Prompt for Arguments
Close Window on exiting

2-19
2 Installation
2.3.3.5
08.01
Linking in the text converter

Note
Command Line
:
mmc100pj\Instutil\Txt_Make.exe
Menu Text
:
&Textconverting
Arguments (MSVC) :
-app $ProjDir oNoLenWarn fD bG
Arguments (Studio) :
-app $(WkspDir) oNoLenWarn fD bG
Initial Directory
:
mmc100pj\Proj
" Use Output Window
Ask for Arguments or. Prompt for Arguments
Close Window on exiting
See also Subsection 3.4.10.
2.3.3.6
Linking in the online help

Note
The HMI Embedded Screen Kit contains three online help files for use under
MS Windows (with Winhelp.exe).
These files (Pj_gr.hlp, Pj_dvkit.hlp, Btss_gr.hlp) are stored in mmc100pj\Doc
by Setup. You can also double click them to start them from the Windows file
manager.
The file name extension .._gr stands for German (germany). If you require
online help in English, please enter the files with extension .._uk (united
kingdom).
In the current SW version, the English online help must be entered manually in
the toolbar (see below).
To ensure that the MSVC Workbench or MS Visual Studio can locate file
Winhelp32.exe, the Windows path must be entered in at least one of the
following 3 positions:
- In the environment variable PATH
- In the Executable Files path
MSVC:
Menu OPTIONS
DIRECTORIES
EXECUTABLE FILES PATH;
Visual Studio:
Menu TOOLS
OPTIONS
DIRECTORIES
EXECUTABLE FILES
In the tool entries as absolute path name in front of Winhelp32.exe. (see

below)
If your Windows version uses only the older Help program "Winhelp.exe", all
instances of Winhlp32.exe in the tool entries (see below) must be replaced by
Winhelp.exe.
2-20

08.01
2 Installation
Make the following 3 settings:

Command Line :
C:\windowsWinhlp32.exe
Menu Text
:
&Configuring Guide
Arguments
:
mmc100pj\Doc\Pj_gr.hlp
Initial Directory :
No Entry
" Use Output Window
Command Line :
C:\windowsWinhlp32.exe
Menu Text
:
Screen-&Kit Help
Arguments
:
mmc100pj\Doc\Pj_dvkit.hlp
Initial Directory :
No Entry
" Use Output Window
Command Line :
C:\windows\Winhlp32.exe
Menu Text
:
&OPI Variables Help
Arguments
:
mmc100pj\Doc\Btss_gr.hlp
Initial Directory :
No Entry
" Use Output Window
The Windows installation path can be, for example: Windows, Win95, WinNT,
WinNT.400.
Note
C:\windows represents the installation path of your Windows version. Other
common paths include C:\winnt, C:\win95, C:\win.nt. For partitioning the hard
disk, refer to Section 3.10.
2.3.3.7
Other extensions to the development environment

Note
Windows 95 only
The Setup installation routine creates environment variables "RAMDISK"

and "HARDWARE_NAME" ( e.g.: "PCU20" , "HT6"), variable PATH is
extended. If Setup has not been executed properly, you may need to set
up or extend the following environment variables manually.
PATH
:
Must contain the folder mmc100pj\Instutil .
RAMDISK
:
TEMP PATH\RAMDISK
<HW_BEZEICH>:
"1"
To set an environment variable under Windows 95, you must add SET
VAR_NAME = /VRT to file "c:\autoexec.bat". e.g.:
SET PATH = C:\WIN95; C:\PROGRAM; ....; C:\MMC100PJ\INSTUIL
SET RAMDISK = C:\TMP\RAMDISK
SET HT6 = 1
The changes do not take effect until you next restart the system !!!

2-21
2 Installation
08.01
Windows NT only
To set an environment variable under Windows NT, you must open the system
settings dialog by selecting START SETTINGS CONTROL
PANEL SYSTEM . You can set the environment variables under the
Environment tab. Enter the variable name under Variable and the value under
Value. The variable is accepted when you press the Set button.
The changes do not take effect until the next LOG ON !!!
In Visual Studio 6.0 you can define vocabulary words which are then colorhighlighted in the development environment. For this purpose, you must
enter the vocabulary words in a "usertype.dat" file in the same folder as
the Msdev.exe program.
Setup automatically creates a file of this type containing the configuring
vocabulary words and OPI variables. To ensure that entries are not lost,
no pre-existing file is overwritten. In this case, you can append the
contents of file mmc100pj\Instutil\Usertype.dat to the file with the same
name in the Msdev.exe folder.
2.3.4
De-installing the screen kit
Description
To de-install a screen kit from your computer again, proceed as follows:
Save your projects if necessary

- Save your applications in mmc100pj\Proj\App
- Save your projects in mmc100pj\Configs
- Save your configuration files in mmc100pj\Sck\Cfg
Delete the installation folder mmc100pj.
Delete the tool entries from the development environment.
- Open the dialog OPTIONS TOOLS

- Select the application manager in the Menu Contents list.
- Press the Delete button.
- Proceed in exactly the same manner for the other screen kit tools.
- Exit the dialog by selecting OK.
MSVC 1.5x only
Visual Studio only
Open the dialog TOOLS

CUSTOMIZE... TOOLS tab
- Select the application manager in the Menu Contents list.
- Press the Delete symbol.
- Proceed in exactly the same manner for the other screen kit tools.
- Exit the dialog by selecting Close.
Win 95 only
Remove the screen kit environment variables.

- Open file "C:\AUTOEXEC.BAT" using an ASCII editor.
- Delete the lines "@SET RAMDISK..." and "@SET
<HW_BEZ>...". <HW_BEZ> stands, of course, for the HW
name. (e.g. "HT6" )
- Delete section mmc100pj\Instutil from the SET PATH
2-22

08.01
2 Installation
statement.
- Save the file and exit the editor.
Win NT only
2.3.5
Description
- Open the dialog START

SETTINGS
CONTROL PANEL
SYSTEM
ENVIRONMENT tab.
- Delete the entries for RAMDISK and <HW_BEZ> by selecting
them and pressing the Delete button.
- Remove section mmc100pj\Instutil from the PATH variable.
- Confirm your settings with OK.
Typical Setup errors
Problem:
The tool menu entries do not work.
Cause:
You are probably using a Windows NT computer, but you have not installed
the HMI Embedded configuring package under a substituted drive, or have
failed to specify the substituted drive during setup.
Remedy:
Install again or change tool entries by hand
(see Subsection 2.3.3
Initialization settings for MSVC Workbench / MS
Visual Studio)
Description
Problem:
Winhlp32.exe for the online help cannot be found.
Cause:
You are probably using an older Windows system.
Remedy:
Use file Winhelp.exe instead of Winhlp32.exe.
To do this, you must alter the tool entries by hand
(see Subsection 2.3.3.6 Linking in the online help)
Description
Problem:
The online help for OPI variables is aborted with an error message. The other
help files are ok.

2-23
2 Installation
08.01
Cause:
You are using Winhelp.exe. OPI variables require the 32-bit version
Winhlp32.exe.
Remedy:
Use file Winhlp32.exe instead of Winhelp.exe if possible.
To do this, you must alter the tool entries by hand
(see Subsection 2.3.3.6 Linking in the online help)
If you cannot do this because, for example, you are using an older Windows
system, you will unfortunately not be able to access this help function.
Description
Problem:
The installation kit is aborted with error message "Cannot find arj.exe".
Cause:
The environment variable PATH has not been extended.
Remedy:
Extend the environment variable as described above. Do not forget to
RESTART your computer! Check the other environment variables as well.
Description
Problem:
The PC Simulation application displays a white or a black screen. The
simulation ends when you press a key.
Cause:
-
You have not set environment variable RAMDISK.
The PC Simulation must be called from mmc100pj\Bin_sim.
Remedy:
Set the environment variable as described above. Do not forget to RESTART
your computer! Check the other environment variables as well.
Check whether the Initial Directory is correctly positioned on the toolbar
(TOOLS
CUSTOMIZE TOOLS tab).
2-24

08.01
2.4
2 Installation
Where can I find what?

A brief overview of relevant directories and files:
Directory for HMI

Embedded testing
Directory for configuration

files of individual application
configurations

2-25
2 Installation
08.01
Installation path of
configuring package
Application directory
Application header files
Application make files

(MSVC 1.xy only)
Application source files
Text files in language

directories
Application project files

(MSDEV 6.0 only)
The OEM directory
..\Bin_sim
Directory for HMI Embedded testing (PC simulation)
Mmc0.exe
HMI Embedded PC simulation
ApplicationName.dll
Application DLLs
ApplicationName.dl_
Compressed application DLLs
*.sp*
Language files
..\Sck\Cfg
Directory for configuration files of individual application configurations
2-26

08.01
2 Installation
ApplicationName.cfg
Configuration files for application configurations
..\Public
Directory for system include files. Your application configuration cannot be
correctly compiled with the application make file ApplicationName.mak (MSVC
1.xy) or ApplicationName.dsp (MSVC V6.0) until the following files have been
linked in.
The diagram only shows the directory structure, as the Include files should not
be changed. This screen also shows the structure for ...Proj\Text\D, E, F..
Notes
You should not alter the system include files! They are utilized by the
system as well. Changing defines could lead to inconsistencies between
the system and configuration and thus to undesirable effects. Furthermore,
your changes would be overwritten without warning the next time you
update the screen kit.
If you wish to make changes (e.g. because you prefer other colors or
window sizes), then you should create your own include file under
..\Proj\App\H and enter the modified defines in this.
Always include file ..\Proj\App\H\Proj.h as the first include file in your

application source files (*.C); in this way you can be sure that all following
system include files will be linked in automatically for you.
Aclis_S.h
Definitions for standard action routines
Allg.h
Gen. definitions
Attr.h
Definitions for attribute words (V fields and

windows)
Btss_Var.h
Definitions for MPI column identifiers
Bv_Chann.h
Channel-dependent definitions
Bvdat.h
Definitions for menus and windows
Bv_Lddll.h
Configurable loading of Dlls
Charset.h
Definitions for character sets
Event.h
Definitions for event lists
Key.h
Definitions for key codes
Listen_1.h
Definitions for objects
Listen_2.h
Definitions for reaction and action lists
Localnb.h
Definitions of locally used NBs
Logiccol.h
Definitions for logical color attributes
Max_Offs.h
Maximum values for CON_TEXT_OFFSET

2-27
2 Installation
08.01
Plc_Var. h
Definitions for PLC data blocks
Polymark.h
Definitions for polymarkers
Portab.h
Gen. definitions
Size.h
Gen. Window definition
Softkey.h
Definitions for softkey menu
Vgadef.h
Definitions for colors and gray shades
Xcon.h
Definitions for data conversions
Xdi.h
Definitions for data interface
..\Proj\Sl
Directory for all applications in binary form (ApplicationName.dat). The Link
operation (MSVC Workbench: TOOLS
GENERATE SL.DAT) copies these
files from directory ..\Proj\App\ApplicationName\Lib to this directory and then
interlinks them with the other application binary files configured in the
Installation Kit (SCK). These files act as an input for the Installation Kit (SCK)
to allow, for example, the creation of system or application diskettes.
ApplicationName.dat
Applications in binary form
..\Proj\Text\D, G, ...
Directories for all application text and application alarm text source files in
every language.
These directories contain only copies of the text source files from directories
.\Proj\App\ApplicationName\Text\D, G, ...
Note
Please make your changes in the relevant text directories
..\Proj\App\ApplicationName\Text\D, G, ... and not in these directories, since
the latter are copies only and ignored by the text converter!
TextFileName.txt
Application text source files
AlarmtextFileName.txt
Application alarm text source files
..\Proj\App\H
Directory for all application text include files. All application text include files
generated by the text converter which must be included by the relevant
application during the compiler operation are copied to this directory.
2-28

08.01
2 Installation
Include file Proj.h must be included as the first in every application source file
(*.C), because it includes the main system include files from directory .. \Public.
Your application configuration cannot be correctly compiled with the application
make file until the system include files have been linked in.
Proj.h
TextFileName.h
Include file for linking in all system configuring

include files
Application text include files
..\Proj\App\ApplicationName
Directory contains all the source files relevant to the application
ApplicationName. To archive your application configuration, you need only
back up all subdirectories in this path and file ..\Sck\Cfg\ApplicationName.
This directory also contains the project and working area files for Visual Studio.
(These files are not needed when the MSVC Workbench is used.)
ApplicationName.dsw
This file is created as standard by the application

manager. It contains the settings of the working
area for this application, e.g. which projects
belong to the application and how they interact.
This file is required only if MS Visual Studio is
used.
ApplicationName_Li.dsp

manager. The project controls compilation of the
source files for the application and creates the
ApplicationName.lib file. It is therefore equivalent
to the ApplicationName.mak make file for MSVC
Workbench.
used.
ApplicationName.dsp

manager. The project controls the link operation
of this one application. A DAT file is generated
from the LIB file and copied to ...\Proj\Sl where it
is available for access by the Installation Kit or
the general linkage process. It is therefore
equivalent to the SI_App.mak make file for
MSVC Workbench.
used.
..\Proj\App\ApplicationName\Src
Directory contains all relevant application configuring source files (*.c) for an
application.
app_menu.c
This file is generated as standard by the

2-29
2 Installation
08.01
application manager to allow you initial access to

your new application.
ap_l_dir.c
This file contains references to the lists that are

addressed via their list IDs. It is generated
automatically by the application manager and
initialized with all application-specific data. You
need not make any changes to the file for
configuring purposes.
..\Proj\App\ApplicationName>\H
This directory contains all application-specific include files (*.H).
ap_l_dir.h
This file contains the application list directory, i.e. it

must contain external references to all definition
blocks and lists contained in your application
configuration. These entries of lists and definition
blocks used in your application must be updated
every time you edit or supplement your lists and
definition blocks.
e.g. if your application contains the following lists:
Menu (M_APP), Window (W_APP), Object list
(OB_APP), Softkey reaction list (SRC_APP) and
softkey object list (SOB_APP), then file ap_l_dir.h
must contain the following:
EXTERN_MENU (M_APP)
EXTERN_WINDOW (W_APP)
EXTERN_OBJECT_LIST (OB_APP)
EXTERN_SOFTKEY_REACTION_LIST
(SRC_APP)
EXTERN_SOFTKEY_OBJECT_LIST (SOB_APP)
mwl_app.h
This file contains all application number ranges for

your list and definition block names. A number is
assigned to each definition block and list name in
this include file; the HMI Embedded basic system
can uniquely identify every individual list on the
basis of this number.
Note
This file must be explicitly included in every
application source file (*.C) with entry #include
"mwl_app.h" after entry #include "proj.h" so that
the list and definition block names can be clearly
identified.
2-30

08.01
2 Installation
nb_app.h
This file contains all notebook number definitions

for your applications. The notebooks are
represented by HMI variables with which you can,
for example, perform arithmetic calculations or
temporary storage operations. The variables are
irretrievably lost, however, after an interruption in
the power supply. Results of arithmetic operations
should, for example, be stored temporarily in R
parameters.
This file must be explicitly included in every
application source file (*.c) with entry #include
"nb_app.h" after entry #include "mwl_app.h".
Definition of your own

application-specific
include files
With macro configuring you can use the C

Directive "#DEFINE" , allowing you, for example, to
define screen coordinates for legibility and use
them elsewhere as a textual replacement. Defines
of this type should be stored in application-specific
include files, and be included by every application
source file (*.c). The same applies to PLC and NC
variable defines, i.e. they should not be inserted in
the central system include files mmc100pj\
Public\*.h, but stored in application-specific include
files. This is also important as regards updates,
since any entries in system include files might be
lost when the system is updated.
These entries must then be inserted with entry
#include "Application-specific IncludeFileName.h".
..\Proj\APP\ApplicationName\Obj_c800
This directory contains the application make file which controls compilation of
the application configuring sources with MSVC 1.xy. The result of this process
is file ApplicationName.lib which serves as an input for the general linkage
operation.
This directory is not used for MS Visual Studio.
ApplicationName.mak
Application make file
..\Proj\App\ApplicationName\Lib
Directory contains the application-specific make file for the general linkage
operation which is activated when you select menu options TOOLS
GENERATE SL.DAT in MSVC Workbench. This make file generates from file
..\Proj\App\ApplicationName\Obj_c800\ApplicationName.lib the file
..\Proj\App\ApplicationName\Lib\ApplicationName.dat, copies it to ..\Proj \Sl,
links all application binary files configured in the Installation Kit into file Sl.dat
and copies them to directory ..\Bin_sim for the PC Simulation.

2-31
2 Installation
08.01
This directory is not used for MS Visual Studio, because ApplicationName.dat

is generated by project ApplicationName>.dsp.
The Lib directory is not needed to link file SI.dat.
sl_app.mak
Application make file for the Applicationdat file.

(MSVC Workbench)
..\Proj\App\ApplicationName\Text\D, G, ...
These directories contain the application text source file and application alarm
text source file for every language. You must modify or add text in these files.
TextFileName.txt
Application text source files
AlarmtextFileName.txt
Application alarm text source files
..\Proj\App\ApplicationName\Release
These directories are used by Visual Studio only. The compilation output files
are stored in them. These also include file ApplicationName.lib.
2.4.1
Description
List identities for application area - mwl_app.h
mmc100pj\Proj\App\ApplicationName\H\mwl_app.h contains all list identities

(list identifiers) of all project lists used in the application area.
The entries in this file are automatically generated via ap_l_dir.h.
The first entry in this file is normally the menu identification for the start menu.
This must also match the entry in file mmc100pj\Sck\Cfg\ApplicationName.cfg.
2-32

08.01
2.4.2
2 Installation
Colors and gray shades - logiccol.h, vgadef.h
Description
Defines for the logical colors are stored in mmc100pj\Public\logiccol.h. One

logical color definition always includes the colors for one color screen and one
b/w screen.
Cursor color for

editor:
For example: #DEFINE ED_WD_CCOL ORANGE|BLACK /* Cursor color in

edit window */
With color screen

With b/w screen
ORANGE
BLACK
The combinations are devised to achieve good legibility in both screen

variants.
If you want to use other combinations, you can set up a local color table in
mmc100pj\Proj\H\.
The generic basic colors are stored in file
mmc100pj\Public\vgadef.h.
2.4.3
Description
Layout - size definitions for characters, windows,

softkeys - size.h
mmc100pj\Public\size.h contains defines for the sizes of windows, softkeys

and characters.
If you want to define other sizes, you can set up your own include file in
mmc100pj\Proj\H\.
2.4.4
Description
Keyboard events - key.h
mmc100pj\Public\key.h contains definitions of the keyboard events which can

be configured in the reaction routines.

2-33
2 Installation
2-34
08.01

Configuring
3.1
Overview .........................................................................................................3-38
3.2
3.2.1
3.2.2
3.2.3
3.2.4
3.2.5
3.2.6
3.2.7
3.2.8
Application manager - creating an application ................................................3-39

Exiting the application manager ......................................................................3-40
Creating a new application configuration ........................................................3-40
Editing application data ...................................................................................3-44
Saving application data ...................................................................................3-44
Copying an existing application configuration .................................................3-44
Closing application data ..................................................................................3-46
Setting text converter options..........................................................................3-46
Displaying information about the HMI Embedded application manager .........3-46
3.3
3.3.1
3.3.2
Configuring a project .......................................................................................3-47

Creating a new project ....................................................................................3-47
Description of configuration files (*.cfg) ..........................................................3-49
3.4
3.4.1
3.4.2
3.4.3
3.4.4
3.4.5
3.4.6
3.4.7
3.4.8
3.4.9
3.4.10
Text converter - text principle..........................................................................3-51

Languages - multilingual texts.........................................................................3-51
Master language..............................................................................................3-52
Text source file - TextFileName.txt .................................................................3-52
Text binary files - TextFileName.sp1, TextFileName.sp2 ...............................3-52
Text include file - TextFileName.h ..................................................................3-53
Text dependencies..........................................................................................3-53
Basic principle of text accessing .....................................................................3-53
Syntax of configuring text source files.............................................................3-54
Syntax of the HMI Embedded alarm text source file .......................................3-55
Calling the text converter.................................................................................3-55
3.5
3.5.1
3.5.2
3.5.3
Compiling the application configuration ..........................................................3-59

Important files for the compile operation.........................................................3-59
MSVC project - ApplicationName.mak............................................................3-60
Visual Studio Workspace - ApplicationName.dsw,
ApplicationName.dsp, ApplicationName_li.dsp...............................................3-60
Application source files - *.c ............................................................................3-61
Application list directory - ap_l_dir.h................................................................3-61
Notebook defines - nb_app.h ..........................................................................3-62
Number ranges ...............................................................................................3-62
Starting the compile operation on the MSVC Workbench...............................3-63
Starting the compile operation in MS Visual Studio 6.0 ..................................3-64
Extensions and dependencies ........................................................................3-65
Archiving the application configuring source files ...........................................3-65
3.5.4
3.5.5
3.5.6
3.5.7
3.5.8
3.5.9
3.5.10
3.5.11

3-35
3 Configuring
08.01
3.5.12
Description of "Example".................................................................................3-66
3.6
3.6.1
3.6.2
Linking the application areas...........................................................................3-69

Important files for the link operation ................................................................3-70
Starting the link operation................................................................................3-70
3.7
Testing the configuration on a PC...................................................................3-71
3.8
Generating floppy disks...................................................................................3-71
3.9
3.9.1
3.9.2
3.9.3
3.9.4
3.9.5
Installing HMI Embedded on a PCU20 ...........................................................3-71

Installing the system software .........................................................................3-72
Installing the application floppy disk ................................................................3-77
Textdisk: Updating the system software language..........................................3-81
Creating a PC card..........................................................................................3-83
Updating software via the PC card..................................................................3-83
3.10
3.10.1
3.10.2
3.10.3
Installing HMI Embedded Win 32 on a PCU50 ...............................................3-84

Installing via a parallel link with a FAT16 file structure....................................3-85
Installing via a parallel link with a FAT32 file structure....................................3-87
Installing via a network connection..................................................................3-88
3-36

08.01
Introduction
3 Configuring
Principle of the HMI Embedded modular system

HMI Embedded comprises a basic system and a variety of applications.
A range of different applications can be combined with the basic system,
including standard applications (e.g. Machine, Parameters, Program, etc.) or
user applications (user interface configurations designed by the machine
manufacturer).
You can create user applications using the configuring package.
Applications are configured by means of the "Installation Kit" tool
(mmc100pj\Sck\sck.exe).
Using the Installation Kit, you can assign each application (including user
applications) to a horizontal softkey in the operating area menu (or to a user
key on the HT6).

3-37
3 Configuring
3.1
08.01
Overview
The following diagram shows the sequence of operations required to configure
an operating area:
Creating/
copying a
new
application
(section 3.2)
Configuring
a new
project
(section 3.3)
After a change in the

texts
After a
change in the
project sources
3-38
Converting
the
texts
(section 3.4)
Compiling
the
configured
application
(section 3.5)
Linking the
application
areas of the
current project
(section 3.6)
Testing
in
PC simulation
(section 3.7)
Generating
system or
application
diskettes
(section 3.8)
Transfer
to hardware
(sections 3.9
and 3.10)

08.01
3.2
3 Configuring
Application manager - creating an application
Activation
Open the MSVC/MSDEV Workbench and select menu options TOOLS

APPLICATION MANAGER.
(see Subsection 2.3.3.1 "Linking in the application manager" if it is not
displayed in the tool menu)
The HMI Embedded application manager now appears on the screen.
Possible error
There is no response when you select menu options TOOLS

APPLICATION MANAGER in the MSVC Workbench.
Cause: The application manager has already been started and is now active
as a task.
Remedy: Press key combination ALT
TAB until the HMI Embedded
application manager is displayed. When you release the two keys, the active
application manager will appear again on your screen.
Scope of functions of the application manager
EXIT
Exits the HMI Embedded application

manager
APPLICATION
NEW
Creates a new application configuration
APPLICATION
EDIT
Edits application data ( not yet available )
APPLICATION
SAVE
Saves application data ( not yet available )
APPLICATION
COPY
Copies an existing application configuration
APPLICATION
CLOSE
Closes editing data ( not yet available )
OPTION
HELP
TEXT CONVERTER
ABOUT APPMAN...
Sets text converter options ( not yet

available )
Displays information about the HMI
Embedded application manager

3-39
3 Configuring
General
3.2.1
08.01
Every dialog window or any action can be aborted with the Cancel button.
You can display a help text in any dialog box by selecting the Help button
(not yet functional).
Exiting the application manager

You can close the HMI Embedded application manager by selecting menu
options EXIT.
3.2.2
Creating a new application configuration

To create a new application, select menu options APPLICATION
NEW in
the application manager. A dialog box "APPLICATION NEW" is displayed in
which you must enter a number of parameters for the new application.
Description of entries in the "APPLICATION NEW" dialog box:

application - data
Application Name
Name of the new application

(max. 8 characters).
Softkey Text/
Identifying text on the softkey via which the

application will be activated. Once the application
has been selected, this text also appears at the
top left in the application header (max. 9
characters).
Application Text
3-40

08.01
Application
Version Display
3 Configuring
Text File (.txt)
Name of the text file in which the application texts

are stored (max. 8 characters).
Comment for Text File
Comment text which must appear after the text

file name entry for the application in the [TEXT]
section in file
mmc100pj\sck\cfg\ApplicationName.cfg (max.
200 characters).
Alarm Text File Name (.txt)
Name of the alarm text file in which HMI alarms

for the application can be stored (max. 8
characters).
Comment for Alarm Text

File
Comment text which must appear after the alarm

text file name entry for the application in the
[TEXT] section in file
mmc100pj\sck\cfg\ApplicationName>.cfg (max.
200 characters).
SCK Module Name
Descriptive text in the SCK for selecting the

application when configuring a project (max. 8
characters).
Name
Descriptive text to be displayed for your

application in the HMI Embedded version display
Version
Version identifier to be displayed for your

application in the HMI Embedded version display
Date
Not active
Time
Not active
Length
Not active
Note
When you enter an application name, the DEFAULT button is enabled. If you
select this button, all the other fields are assigned defaults containing the
application name.
You can enter the settings for Date, Time and Length fields manually after you
have created the application by modifying the file ApplicationName.cfg in path
mmc100pj\Sck\Cfg. These entries are as follows:

3-41
3 Configuring
08.01
[VERSION_Hardware]
Name = Application name
max. 12 characters
Version = optional entry
max. 12 characters
Date = optional entry
max. 11 characters
Time = optional entry
max. 8 characters
Length = optional entry
max. 10 characters
e.g.
[VERSION_PCU_20]
Name = Example Version = 01.01.01
Date = 28 Nov 2000
Time = 12:45
Length =
Important
Any type of change in other sections may cause execution errors in your
application!
Objects created
If you have filled out all the fields correctly, the following file structure is set up
(in our example, you entered "MyApp" for Application Name):
A configuration file for the Installation Kit has also be generated in folder
"Sck\Cfg".
3-42

08.01
3 Configuring
Installation path of
configuring package
Application directory
Application header files
Application make files

(MSVC 1.xy only)
Application source files
Text files in language

directories
Application project files

(MSDEV 6.0 only)
See Subsection 2.4: Where can I find what?
Note
The operations you are currently performing are displayed in the dialog line of
the application manager. If an error occurs while you are executing any of the
above actions, an appropriate error message box will appear on your screen.
To process your
application with
MSVC V1.xy
Switch to the MSVC Workbench and select menu options PROJECT

OPEN.... Select the application make file in folder "Obj_c800" of the created
application (e.g. MyApp.mak) and confirm your input by pressing the OK button
or double click with the left mouse button.

3-43
3 Configuring
08.01
The MSVC Workbench now loads the new application and you can start
configuring.
To process your
application with
MSVC V6.0
Switch to MS Visual Studio and select menu options FILE

OPEN
WORKSPACE. Select ...\ApplicationName.dsw (e.g.
mmc100pj\Proj\App\MyApp\MyApp.dsw) and confirm your input by pressing
the OK button or double click.
The MSVC Workbench now loads the new application and you can start
configuring.
See Subsection 3.1 Overview
3.2.3
Editing application data

(APPLICATION
EDIT)
Not functional in the current SW version.
3.2.4
Saving application data

(APPLICATION
SAVE)
3.2.5
Copying an existing application configuration

To copy an existing application, select menu options APPLICATION
COPY
in the application manager. A dialog box "APPLICATION COPY" is displayed in
which you must enter a number of parameters for the new application.
Description of inputs in the "APPLICATION COPY" dialog box:
3-44

08.01
source
3 Configuring
Application Name
Name of the project to be copied. The application

manager now searches through directory
mmc100pj\Proj\App for existing applications and
displays them for selection in the form of a combo
box.
The manager offers only those projects that have
been created with the selected (during
installation) development environment.
The combo box displays only one application.
You can change the selection using the arrow
keys in the combo box or with CURSOR_UP or
CURSOR_DOWN.
Destination Data
See Subsection 3.2.2: Creating a new application configuration: Description of

entries in the "APPLICATION NEW" dialog box:
Note
When you enter an application name, the DEFAULT ...button is enabled. If you
select this button, all the other fields are assigned defaults containing the
application name.
Copying actions
The complete application directory is copied. Only the application make files
(MSVC 1.xy) or project files (MSDEV 6.0) and the configuration file are created
new. The text files are also generated with the name specified in the dialog
box.
See Subsection 2.4: Where can I find what?
Note
The operations you are currently performing are displayed in the dialog line of
the application manager. If an error occurs while you are executing any of the
above actions, an appropriate error message box will appear on your screen.
To process the
application you
have just created
Proceed as described in
Subsection 3.2.2 Creating a new application configuration

3-45
3 Configuring
3.2.6
08.01
Closing application data

(Application
Close)
3.2.7
Setting text converter options

(Options
Text Converter)
3.2.8
Displaying information about the HMI Embedded application

manager
You can display information (e.g. current version of the HMI Embedded
application manager) by selecting menu items HELP
ABOUT APPMAN....
Close the information box again by selecting the OK button.
3-46

08.01
3 Configuring
3.3
Configuring a project
3.3.1
Creating a new project
To configure a
project using the
SCK (Softkey
Configuration Kit)
The SCK (Software Configuration Kit) tool for configuring the system allows
you to choose from a selection of operating functions for different target
systems those functions that are appropriate and desirable for your particular
machine. In this way, you can individually design and adapt your operator
panel interface.
The result of the configuration is a collection of files on the hard disk of the
configuration PC which can be accessed directly from the SCK either for
loading to the target hardware or for creating system and application diskettes.
Activate the SCK in the Workbench by selecting menu options TOOLS

Installation Kit
Open a new configuration:

P-Project Management, N-New Project.
Enter any name for your project, e.g. test_app (max. 8 Characters)
You must set the options in the next window (system configuration).
The screen kit offers languages 1 - 99. You can select the first and second
language in this screen; these are then installed as the foreground and
background languages on the hardware (see also Subsection 3.4.1
"Languages Multilingual Texts"). You can switch between these two
languages in operation. The hardware configurations are also specified in
this screen. Please set your mmc100pj as the APPLICATION_PATH. Key
in the bracketed letter to select the point you wish to change.
e.g..:
<P>ATH FOR PROJECT:
C:\MMC100PJ
<A>PPLICATION PATH:
C:
<F>IRST LANGUAGE:
GERMAN
<S>ECOND LANGUAGE:
ENGLISH
<H>ARDWARE:
PCU_20
Confirm with <F4>. The "Softkey selection" screen appears.
Program an assignment between softkeys and standard applications

(module) or OEM applications
To do this, enter the number of the softkey first and press RETURN. Then
enter the module number. ( To cancel the assignment of a softkey, select
0 ).
You can toggle between SYSTEM and OEM modules by pressing TAB.
You can assign applications to user keys by the same method on the HT6;
you can toggle between softkey assignments and hardkey assignments
with H.
Repeat this sequence of operations until you have assigned all softkeys
and hardkeys (HT6 only) as required.
Note
You can assign each module to one softkey or hardkey only!

3-47
3 Configuring
08.01
Confirm with <F4>.
Use the start softkey to select the application with which the system must
boot.
Confirm with <F4>.
In the subsequent screen, you can define further options for texts and
files.
<1>
l<2>
l<3>
<4>
<5>
<6>
= Edit text files for first

= Edit text files for second
= Edit ASCII files
= Edit user-specific files
= Copy external files to the project
= Set options for operating area(s)
<F1> = Help
<F4> = Save project
<ESC> = Cancel!
Please make your choice
To generate a system
<F1> - Help
Confirm with <F4>.
Select a project (after you have created a new project, it is automatically

selected)
To create a PC card image, select <I> INSTALL SYSTEM VIA RS232C

OR CREATE FLASH CARD in the main menu.
To create system disks, select <S> MAKE SYSTEM DISK in the main
menu. Using these disks, you can generate PC card images of the project
without an installation kit, or transfer it to the hardware via the serial
interface.
To create application disks, select <A> MAKE APPLICATION DISK in the

main menu. Using these disks, you can modify the system disks of this
project to a certain degree. You can choose, for example, other
languages, or modify the bus address or text files.
To create a PC simulation environment, select <C> CREATE

SIMULATION ENVIRONMENT in the main menu.
Exit the SCK tool.
Note
The behavior of the PC simulation function can be altered only by the CREATE
SIMULATION ENVIRONMENT function of the installation kit. If, for example,
you change the softkey assignments and create a PC card, the new
assignments are operative on the card, but the old assignments still apply in
the PC simulation environment.
3-48

08.01
3.3.2
3 Configuring
Description of configuration files (*.cfg)

The Installation Kit (SCK) manages a configuration file in folder
mmc100pj\Sck\Cfg FOR EVERY APPLICATION. The data stored in this file
includes information about the DLLs and text files used for the application as
well as version information.
Important
You should not normally make any changes to these files yourself! Incorrect
entries can have a negative impact on the functionality of your system.
Nevertheless, the structure of these files is described briefly below, since some
settings can only be made by this method. You should close the Software
Configuration Kit before you edit the file.
Section [DLL]:
dll name = Method start, method end, start method, class name for task
communication, symbolic name for configuration, start menu identification,
number of notebooks, text file name for standard texts, text file name for alarm
texts for specific operating areas
Section [INI]:
Flag for operating area with global DLL (GLOBAL) or without (NO_GLOBAL)
Section [TITLE]:
Text number for softkey text and operating area text
Section [NAME]:
Name for selection for configuration in the SCK. No blanks allowed!!!
Section [DAT]:
Configuring data for operator interface (binary)
Section [FILES]:
Contains a list of files required for the application.
Sections [HW_DESIGNATION]
Like the [FILES] section, this section contains a list of files required by this
application. However, only the section associated with the hardware is
evaluated; it is possible, for example, to use different hardware versions for
different DLLs.
Section [FONTS]:
The fonts used are entered in this section.
Section [FONTS IDEO]:
The Asiatic fonts used are entered in this section.
Section [TEXT]:
Names of required text files, detailed description of text files (e.g. for menu
selection)

3-49
3 Configuring
08.01
Section [VAR]:
In most cases, this section contains only the entry EBF_CONFIG.
EBF_CONFIG=1 is the setting required to operate an NC; no NCK variables
may be utilized with a setting of EBF_CONFIG=0.
Section [SYS]:
Application-specific, static application
Section [VERSION_<HW_BEZEICHNUNG>]:
Data for the HMI version display in different HW versions.
Section [INTERN]:
You must specify the hardware for which the application is suited. If you do not
explicitly specify a hardware type, it is assumed that it is suited to all hardware
types.
1 - Application suitable for appropriate hardware (default)
0 - Application not suitable for appropriate hardware
3-50

08.01
3.4
3 Configuring
Text converter - text principle

The following diagram illustrates the text converter processes.
Textfile
name.txt
Alarmtextfile
name.txt
Text converter
Textfile
name.h
3.4.1
Description
Textfile
name.sp1
Textfile
name.sp2
Languages - multilingual texts

You can select between 1 and 99 languages when you install the HMI
Embedded SW system. Two languages are preset per default. The first is
installed as the foreground language, the second as the background language.
You can change this default by parameterizing display machine data.
Languages are selected via the SCK.
On the hardware, the default extension is *.s01 for the foreground language
and *.s02 for the background language. These default settings can also be
changed via display machine data.
You can exchange the first and second languages of the HMI Embedded
system for other text versions or different text languages without recompiling
the configuration or basic system.
Note
You must not change the number of texts or their order of compilation.
This restriction does not apply to alarm texts (any text file that begins with "a"
alm, aln, ala, alp, alc, alz).

3-51
3 Configuring
3.4.2
Master language
Description
3.4.3
08.01
The different versions of the text binary files must be compatible. For this
reason, a master language is always defined for the overall text handling
operation. This determines the number and order of texts, their completeness
and the consistency of symbol meanings. German (in path..\Proj\App\Text\D) is
set as the default master language in the HMI Embedded Screen Kit. If you
want a different master language, change the default options in the SCK and
call the text conversion function using the appropriate language code in the
MSVC Workbench or MS Visual Studio.
See description of Installation Kit and Subsection 3.4.10: Calling the text
converter.
Text source file - TextFileName.txt
Description
Project text source files are stored in path

\Proj\App\ApplicationName\Text\D,G,... (depending on language).
Text source files starting with "A" are generally alarm text source files (PLC
alarms, cycle alarms and compile cycle alarms).
All text source files have the *.txt extension.
3.4.4
Text binary files - TextFileName.sp1, TextFileName.sp2
Description
Text binary files are generated by means of the tool at TOOLS

CONVERTER.
TEXT
Text binary files always have the *.sp1 extension for foreground language texts
and *.sp2 for background language texts.
When the PC Simulation function is called, it expects to find the text binary files
in directory ..\mmc100pj\Bin_sim.
The configuring system is preconfigured such that the text conversion tool
(TOOLS
TEXT CONVERTER) and the SCK automatically copy the text
binary files for the foreground language (*.sp1) and those for the background
language (*.sp2) into directory ..\mmc100pj\Bin_sim.
The language you wish to use as the foreground and/or background language
must be specified as an argument in the call to the TOOLS
TEXT
CONVERTER function.
See also Subsection 3.4.10: Calling the text converter.
3-52

08.01
3.4.5
Description
3.4.6
Description
3.4.7
Description
3 Configuring
Text include file - TextFileName.h

To link the texts to the configuration, so-called text include files are generated
from the configuring text source files using the text conversion tool. Text
include files are generated in the master language directory (e.g.
mmc100pj\Proj\App\ApplicationName\Text\D). Text include files have the
extension *.h.
The text include file for your application is called TextFileName.h. This file is
automatically copied to directory \Proj\App\H by TOOLS
TEXT
CONVERTER.
The symbolic identifiers (also referred to as Text IDs) for the configuration are
defined in the text include files.
Text dependencies
The application configuration must be recompiled when you edit a
TextFileName.txt or AlarmTextFileName.txt.
Recompilation is implemented by the relevant dependencies in make file
ApplicationName.mak or project file ApplicationName_li.dsp.
Basic principle of text accessing

A text symbol is assigned to a text in the configuring text source files.
The text converter uses this to generate a text binary file for the runtime
system and a text include file for the configuring kit.
Text include files must be included explicitly in each configuring source file.
Example:
If the text file name = MyApp.txt
and the alarm text file name = AmyApp.txt, then
# include "MyApp.H"
is correct.

3-53
3 Configuring
3.4.8
Description
08.01
Syntax of configuring text source files

The relevant configuring source text file is stored in path
mmc100pj\Proj\App\ApplicationName\Text\Language\ for each language.
TextFileName.txt Configuring source file for application configuration
The text files usually begin with a number of comments containing information
for the installation kit, the text converter and the runtime system.
// CP=1252
// IDEO=NO
// ANSI=YES
// UNICODE=NO
// VERSION=Vxx.xx.xx
The first entry specifies the font code page used, the next line determines
whether the texts are Asiatic. "ANSI" and "UNICODE" stand for the file format
of the text file. The last entry contains a version identifier.
All configuring text source files are configured as follows:
symb_txt_id "text" [// Comment]
Parameters
symb_txt_id
Symbolic text identification, must start with a letter, max.

length 45 characters. symb_txt_id must be unique
throughout the configuration (standard and application).
This requirement is fulfilled within the supplied configuration version by the
following conventions :
Text identifiers defined in file xy.txt always begin with 'T_XY_' and are unique
within file xy.txt (check using the Editor search function).
Recommendation:
Observe this convention when you add new text in the application!
text
Text to be displayed, character sequence in ""
A line break within the display text is denoted by the characters %n.
comment
Can be specified between the comment ID symbol // and

the line end.
The maximum length of text that can be displayed on the screen is generally
entered as a comment.
Note
Do not use any ANSI-C comments (/*...*/), but only SingleLine
comments (//...)!
3-54

08.01
3.4.9
Description
3 Configuring
Syntax of the HMI Embedded alarm text source file
The relevant configuring alarm text file is stored for each language in path
mmc100pj\Proj\App\AApplicationName\Text\
Language\.
TextFileName.txt
Alarm text file for application configuration
All alarm text source files are structured as follows:

alarm number 0 0 "text" [// comment]
The text is displayed in the dialog line by the SET_MESSAGE configuring
macro. A maximum of 62 characters (or 48 on the HT6) can be displayed.
The alarm number for OEM HMI alarms is restricted to the 119000-119999
range.
Notes
3.4.10
Do not use any ANSI-C comments (/*...*/), but only SingleLine comments
(//...)!
The alarm text files usually begin with a number of comments containing
information for the installation kit, the text converter and the runtime system. The comments are the same as those for text source files.
The first line ( excepting comment lines ) in the alarm text file
([SWITCHES]/AL) must not be deleted or changed!
Calling the text converter
Fig.: Arguments for the text converter (MSVC Workbench)

Purpose
The text converter is used to make the assignment between configured text
fields and edited texts in different languages.
Important!
You must activate the text converter every time you edit a text file to ensure
that your change is visible, e.g. in PC Simulation.
If you are using the same text file for several different applications, you must
call the text converter in the project in which the texts are defined !

3-55
3 Configuring
Call
08.01
You can call the text converter by selecting menu options TOOLS TEXT
CONVERTER in the MSVC Workbench or MS Visual Studio. The "Tool
Arguments" box then opens in which you are prompted to specify the call
parameters for the text converter. The following parameters are specified per
default:
-app $(WkspDir) oNoLenWarn -fG -bD
The meaning of these parameters is described below.
Note
If you want to make permanent changes to the text converter default
parameters, you must select menu options OPTIONS TOOLS in the MSVC
Workbench TOOLS CUSTOMIZE TOOLS tab in Visual Studio, click on
the entry "Text Converter" in the "Menu Contents:" field and then alter the
"Arguments:" setting to suit your requirements.
You must specify at least one of the first 4 text converter parameters below:
-f<lan>
...Foreground language to be converted
-b<lan>
...Background language to be converted
-all
...Convert all languages
-sys
...Convert all text files including those of the

system and standard applications (Machine,
Parameters, etc.)
-oNOCHECKDATE
...Omit current status check
<lan> stands for the selected language:

Name of text directory in directory
mmc100pj\Proj\App\ApplicationName\Text\:
Examples of
parameter
combinations
German
English
Italian
Spanish
French
-f<lan>
Convert foreground language only, all text files of

application
-b<lan>
Convert background language only, all text files of

application
Important!
You must have generated the foreground language at least once beforehand!
-f<lan> -b<lan>
3-56
Convert foreground and background languages, all

text files of application

08.01
3 Configuring
-all -f<lan>
Convert all languages, foreground language = <lan>,

all text files of application
-all -b<lan>
Convert all languages, background language

=<lan>, all text files of application
Important!
-all -f <lan>-b<lan>
Convert all languages, foreground and background

languages = <lan>, all text files of application
-all
Convert all languages, foreground and background

languages from Setup settings (from Setup.cfg), all
text files of application
-app <WkspDir>
This instruction notifies the text converter of the

project path. The text converter uses this to
determine the path of the texts to be generated.
<WkspDir> is set per default to $(WkspDir) or
$ProjDir and should not be altered!
-sys -f<lan>
Convert foreground language only, all text files in

path mmc100pj\Proj\Text, incl. application
text files
-sys -b<lan>
Convert background language only all text files in

path mmc100pj\Proj\Text, incl. application text files.
Important!
-sys -f<lan> -b<lan>
Convert foreground and background languages, all

text files in path mmc100pj\Proj\Text, incl.
application text files
-sys
Convert foreground and background languages

from Setup settings (from Setup.cfg), all text files in
path mmc100pj\Proj\Text, incl. application text
files
-all -sys
Convert all languages, all text files in path

mmc100pj\Proj\Text, incl. application text files,
foreground and background languages from Setup
settings (from Setup.cfg)
-all -sys -f<lan>

foreground language = <lan>
-all -sys -b<lan>

background language = <lan>

3-57
3 Configuring
08.01
Important!
-all -sys -f<lan>-b<lan> Convert all languages, all text files in path
foreground and background languages from <lan>
A current status check is performed per default; this is deactivated with
-oNoCheckdate.
A warning is output per default if no length comments are specified in text
files. This can be deactivated with -oNoLenWarn.
If you specify an f or b option, this language is treated as the foreground or
background language and the generated language files copied to simulation
directory mmc100pj\Bin_sim. If you do not specify one of these options, the
defaults from Setup.cfg) are used for the foreground (=master) and
background languages.
If you specify only one of these options, then only this language file is copied
to simulation directory mmc100pj\Bin_sim.
The result of a text converter run is that the individual text binary files
(TextFileName.sp1, TextFileName.sp2 or AlarmTextFileName.sp1,
AlarmTextFileName.sp2) and text include files (TextFileName.h) are loaded
to simulation directory mmc100pj\Bin_sim or directory mmc100pj\Proj\App\H
so that they are available for further configuring operations. The text source
files (TextFileName.txt) themselves are copied to directory
mmc100pj\Proj\Text\D, G, ... where the Installation Kit (SCK) can find them.
If you specify the -all option, the text conversion is aborted if the language
directories in mmc100pj\Proj\App\ApplicationName\Text do not match
mmc100pj\Proj\Text!
A log file (mmc100pj\Proj\App\ApplicationName \Text\Textkonv.log) is
generated while text is being converted.
Important!
The foreground language must have been generated at least once before text
conversion can be called with option -b<lan> only!
3-58

08.01
3 Configuring
3.5
Compiling the application configuration
3.5.1
Important files for the compile operation
The following diagram illustrates the compile operation:
System
include files
from directory
mmc100pj\
Proj\
Project.h
ap_l_dir.h
ap_l_dir.c
app_menu.c
mwl_app.h
nb_app.h
Textfile.h
Further
include files
for
applicationspecific
definitions
(*.h)
Further
application
source files
(*.c)
Application make file
Application project file
ApplicationName.mak
ApplicationName_li.dsp
ApplicationName.lib

3-59
3 Configuring
3.5.2
Description
08.01
MSVC project - ApplicationName.mak
In the MSVC Workbench V1.x, units (libraries, executables, etc.) that belong
together are grouped as projects.
The generation convention and the dependencies for these projects are
stored in mmc100pj\Proj\App\ApplicationName\Obj_c800\
ApplicationName.mak files.
Note
Do not modify by hand! These ApplicationName.MAK files are maintained by
the MSVC Workbench (PROJECT
EDIT, PROJECT
SCAN ALL
DEPENDENCIES).
3.5.3
Description
Visual Studio Workspace - ApplicationName.dsw,

ApplicationName.dsp, ApplicationName_li.dsp
A distinction is made between working areas (Workspace) and projects

(Projects) in MS Visual Studio. In this context, a project is a unit of
associated elements. (The include and source files of an application, a DLL,
etc. ). A working area combines several projects of one topic (e.g. the
application and the required DLLs ).
Even the Screen Kit applications adhere to this concept: For every application
ApplicationName there is a workspace ApplicationName.dsw. This workspace
contains the two projects ApplicationName.dsp and ApplicationName_li.dsp.
The project ApplicationName_li.dsp generates from the source files of the list
configuration an ApplicationName.lib. You should store new configuring files
in this project.
The project ApplicationName.dsp is dependent on the other project. It
generates an ApplicationName.dat from the ApplicationName.lib. Only *.dat
files can be utilized by the linking operation. The project contains ap_l_dir.c
as the only source file. You should not make any changes to this project.
Note
You should always select ApplicationName.dsp as the active project.
Changes to the configuration source files are detected by Visual Studio and
the affected files recompiled automatically.
3-60

08.01
3.5.4
3 Configuring
Application source files - *.c
Your application operating area source files are stored in mmc100pj\

Proj\App\ApplicationName\Src\.C.
Description
These files must have the extension .c. Their syntax must correspond to the
configuring syntax.
The configuration is compiled to form an application library.
MSVC 1.xx only
This library acts as an input for the linker which uses it to generate the
configuring binary file (ApplicationName.dat).
MS Visual Studio
only
This library acts as an input for project ApplicationName which uses it to

generate the configuring binary file (ApplicationName.dat).
Example
A configuring source file with the first application window and preparations for
other lower-level windows is stored in
L:\Proj\App\ApplicationName\Src\app_menu.c .
3.5.5
Description
Application list directory - ap_l_dir.h
The application list directory is stored in

mmc100pj\Proj\App\ApplicationName\H\ap_l_dir.h.
The application list directory ap_l_dir.h contains external definitions for all list
pointers of the lists in the application operating area that are used in more
than one configuring source file.
Each list used in the configuration must be specified accordingly in this file.
Syntax
EXTERN_List type (id) List external reference
Parameter
id
List identity

3-61
3 Configuring
3.5.6
08.01
Notebook defines - nb_app.h
The area for notebook entries that may be used freely for configuring the
application is stored in mmc100pj\Proj\App\ApplicationName\H\nb_app.h.
Description
Insert your defines for the notebooks used in proper order in this file.
Note
Notebook defines must not be defined as enums.
(see also the Configuring Syntax documentation)
3.5.7
Number ranges
List identities
List identifiers
The number ranges for list identifiers are defined in file mmc100pj\
Proj\App\ApplicationName\H\mwl_app.h.
List element
identities
The identities for list elements (e.g. input/output fields, actions, reactions)
need only be unique in the relevant configuring source file.
Event codes
The event codes specified in the elements (WATCH_EVENT,

VALUE_EVENT, BIT_EVENT) of the event list must be between 10.000 and
19.999.
Notebook entries
Depending on their scope of application and validity, notebooks from different

number ranges are used.
The number range divisions are specified in file mmc100pj\
Proj\App\ApplicationName\H\nb_app.h; symbolic defines for the notebook
numbers used can also be assigned in this file.
Local (temporary) notebook entries can be used in all ranges and overwritten
in each case with completely different contents.
Definition in mmc100pj\Proj\App\ApplicationName\H\nb_app.h
3-62

08.01
3 Configuring
Global (application-specific) notebook entries (number 200 to (200 + no. of

NBs)) for configuring the application :
Definition in mmc100pj\Proj\App\ApplicationName\H\nb_app.h
Important
Temporary notebook entries (numbers 1 to 99) are also used by other
applications/operating areas. Local notebook entries should therefore only be
used within temporary arithmetic operations or copyover processes.
Application-specific notebook entries are valid only within the application.
Several applications can therefore store different information under the same
notebook number. Application-specific notebooks retain their information after
operating area switchovers.
3.5.8
Starting the compile operation on the MSVC Workbench
To open the
application
Select menu options PROJECT

OPEN... on the MSVC Workbench. At
"LIST FILES OF TYPE:" select type "Project (*.mak)". Click on the relevant
ApplicationName.mak file from the appropriate application directory
mmc100pj\Proj\App\ApplicationName\Obj_c800. Select the OK button to
open the application configuration.
Example
mmc100pj\Proj\App\Example\Obj_c800\Example.mak
To compile an
application
configuration
Once you have opened an application configuration, you can start the
compile operation. You do this by selecting menu options PROJECT
BUILD APPLICATIONNAME.LIB or PROJECT
REBUILD ALL
APPLICATIONNAME.LIB in the MSVC Workbench.
Note
Before you compile, you should make sure that you have already updated
any changes to your text files using the text converter. If not, make sure you
do so before compiling the configuration, see Subsection 3.4 Text converter
Text principle.
You will know if the application has been generated correctly when the
following message appears in your output window:
"APPLICATIONNAME.LIB - 0 ERROR(S), 0 WARNING(S)"
Directory mmc100pj\Proj\ApplicationName\Obj_c800 must now contain a file
ApplicationName.lib.

3-63
3 Configuring
3.5.9
08.01
Starting the compile operation in MS Visual Studio 6.0
To open the
application
Select menu options FILE

OPEN WORKSPACE in MS Visual Studio. At
"FILE TYPE:" select type "WORKSPACES". Click on the relevant
ApplicationName.DSW file from the appropriate application directory
mmc100pj\Proj\App\ApplicationName. Select the OK button to open the
application configuration.
Example
mmc100pj\Proj\App\Example\Example.dsw
To compile an
application
configuration
Once you have opened a working area, you can start the compile operation.
To do this, select menu options BUILD
BUILD ApplicationName.dat or
BUILD
REBUILD ALL in Visual Studio.
Note
ApplicationName must be selected as the active project; only the library is
compiled with ApplicationName_li, but not the DAT file.
Before you compile, you should make sure that you have already updated
any changes to your text files using the text converter. If not, make sure you
do so before compiling the configuration, see Subsection 3.4.10 Calling the
text converter.
You will know if the application has been generated correctly when the
following message appears in your output window:
"APPLICATIONNAME.DAT - 0 ERROR(S), 0 WARNING(S)"
A file ApplicationName.dat must now have been generated/modified in
directory mmc100pj\Proj\SL.
3-64

08.01
3.5.10
3 Configuring
Extensions and dependencies
Extensions to
application
configurations
If the number of displays configured for an application configuration

increases, it is advisable to configure, e.g. each window in its own application
source file mmc100pj\Proj\App\ApplicationName\Src\*.c).
Create an application
source file
Create a new source file in folder

mmc100pj\Proj\App\ApplicationName\Src\New_File. Enter the required
include statements and configuring lists in it.
To include source file

in an MSVC project
You now need to register the newly created application source file with the
ApplicationName.mak File. In the MSVC Workbench select menu options
PROJECT
EDIT... . Now specify the path and name of the application
source file you have just created, register it with the ApplicationName.mak
file by selecting the ADD button and then confirm your change with the
CLOSE button.
Check whether the MSVC Workbench has stored the new application source
file by selecting the PROJECT FILES BUTTON (button on far left on toolbar
menu). The list of files displayed must now also include the file you have just
generated. You can now continue configuring in the new application source
file.
To include source file

in a Visual Studio
project
Open the insert dialog by selecting PROJECT ADD TO

PROJECT FILES. In the "Insert Into:" combobox, select project
ApplicationName_li.dsp . Change to directory
mmc100pj\Proj\App\ApplicationName\Src in the file tree and select
NEW_FILE. The file is stored in the project when you select OK.
Check that it has been properly inserted by activating the FileView in the
workspace window. The new file must be stored in folder
ApplicationName_li\Source Files in the file tree.
3.5.11
Archiving the application configuring source files

You only need to back up directory mmc100pj\Proj\App\ApplicationName
with its subdirectories and file ..\Sck\Cfg\ApplicationName.cfg. These are the
only files needed to clearly identify and reproduce an application
configuration.

3-65
3 Configuring
3.5.12
08.01
Description of "Example"
Note
In the current version, "Example" can only be compiled with the MSVC
Workbench, but not with MS Visual Studio.
Note
This example uses a resolution of 640 x 480 pixels and is thus not suitable for
HT6!
In directory mmc100pj\Proj\App\Example\Obj_c800
Example.mak
Make file for generating the application configuration EXAMPLE.LIB

In directory mmc100pj\Proj\App\Example\Src
app_menu.c
Configuring source file with one menu (application entry point) and one window
app_win2.c
Configuring source file with one other window
app_ctrl.c
Configuring source file with central lists that can be used by the two configuring
source files APP_MENU.C and APP_WIN2.C.
In directory mmc100pj\Proj\App\Example\H
app_inclL.h
Configuring include file with central defines (e.g. for text coordinates)
ap_l_dir.h
Application list directory with external references to all lists used in the
application.
nb_app.h
Application number ranges for notebooks

In directory mmc100pj\Proj\App\H
Example.h
Application text include file

In directory mmc100pj\Proj\App\Example\Text\D, G, ...
Example.txt
Application texts in the relevant language
Aexample.txt
HMI application alarm texts in the relevant language

In directory mmc100pj>\Sck\Cfg
Example.cfg
3-66
Configuration file of application EXAMPLE for integration in the SCK

08.01
3 Configuring
The following window is opened when you activate softkey "OEM APP." in the
operating area menu.
Mode of operation
Functions in the "EXAMPLE: OEM WINDOW 1" window
The current value of the R parameter from the NC is read and displayed
(hot link) in the "R PARAMETER 10" input/output field. User inputs can
also be made. You can direct the input focus from one input/output field to
the next using the cursor keys.
The current value of the notebook content with number 20 from the MMC
is read and displayed (hot link) in the input/output field NOTEBOOK 20".
User inputs can also be made. You can direct the input focus from one
input/output field to the next using the cursor keys.
The first vertical softkey "ADD NB20 TO R10" adds the content of
input/output field "NOTEBOOK 20" to the content of input/output field "R
PARAMETER 10".
The second vertical softkey "SUB. NB20 FROM R10" subtracts the
content of the input/output field "NOTEBOOK 20" from the content of
input/output field "R PARAMETER 10".
The first horizontal softkey "GOTO WIN 2" closes the "EXAMPLE: OEM
WINDOW 1" window and activates the "EXAMPLE-WINDOW 2" window.

3-67
3 Configuring
08.01
Functions in the "EXAMPLE: OEM WINDOW 2" window
3-68
The current position of the X axis from the NC is read and displayed (hot
link) in output field "ACTUAL VALUE X-AXIS". No user inputs can be
made.
The first horizontal softkey "GOTO WIN 1" closes the "EXAMPLE: OEM
WINDOW 2" window and activates window "EXAMPLE-WINDOW 1".
The first vertical softkey "SET ALARM" outputs the HMI alarm with
number 120000 from the alarm text file.
The second vertical softkey "RESET ALARM" cancels the HMI alarm with
number 120000.

08.01
3.6
3 Configuring
Linking the application areas

The following diagram illustrates the general linkage process:
<Applikationsname>.dat is generated by
"Generate SL.DAT" on the MSVC
Workbench only; with Visual Studio it is
generated as part of the compilation
routine.
ApplicationName.lib
Standard
applications
( ...\ Proj\S \
*.dat)
ApplicationName.dat
Other OEM
applications
(.. Proj\Sl\
*.dat)
General linkage process

Generate Sl.dat
Sl.dat

3-69
3 Configuring
3.6.1
08.01
Important files for the link operation

A special link operation is used to generate a file named Sl.dat from the
applications currently configured in the Installation Kit (SCK).
File SI.dat contains no texts, however, but only text references. The texts
themselves are read from text binary files (TextFileName.sp1,
TextFileName.SP2 or AlarmTextFileName.sp1, AlarmTextFileName.sp2)
while the HMI software is executing.
3.6.2
Precondition
Starting the link operation
The open application configuration and the current application configuration

texts must be converted.
The general linkage process is started when you select menu options TOOLS
GENERATE SL.DAT on the MSVC Workbench or in MS Visual Studio. A
DOS box opens and displays status information about the operation as it
proceeds.
As indicated previously, the behavior of GENERATE SL.DAT in the MSVC
Workbench differs to that in Visual Studio. With the MSVC Workbench, the
ApplicationName.lib file is first converted to an ApplicationName.dat file
before the actual link operation for the applications begins. In contrast, the
DAT file is generated as part of the compilation process in Visual Studio.
Notes
3-70
A log file named APPLICATIONPATH\SL_MAKE.LOG is generated

during the link operation.
In the MSVC Workbench the link operation must be called for every
modified application, since this process also generates the
ApplicationName.dat file! A link operation out of another application uses
only the DAT files of the operating areas, any newer LIB files are ignored!
In Visual Studio the output is redirected per default to the output window
so that no DOS box is displayed.

08.01
3.7
3 Configuring
Testing the configuration on a PC

PC simulation is described in detail in Section 5.
3.8
3.9
Generating floppy disks
Activate the SCK.
Go to the "Project Menu" display.
Select Select Project.
Select a project from the project list.
Select Make system masterdisk or Make application masterdisk.
Select the drive on which you want to create the system floppy disk.
If the drive is a network/disk drive, you will be prompted to enter the path.
Where more than one disk is required, you will be requested to change
disks.
Return to the main menu.
Installing HMI Embedded on a PCU20

An upgrade guide is supplied with every software version. You will find it in
the first installation directory in file "siemensd.txt (German)" or "siemense.txt
(English)".
Supply method
System software
Application software
The HMI Embedded software is supplied on CD and contains:

1.
System software (also referred to as installation software)
2.
Application software
Alarm text files (alp, alpu, alz, alzu, ...) for HMI Embedded
Configuration file (1 NCU or several NCUs) for channel switchover
User software
Language selection
By loading the system software you will obtain a functional standard HMI
Embedded system for English as the first language and German as the
second. The alarm text and message files contain Siemens texts only.
Using the application software you can:
adapt and expand alarm text files (alp, alpu, alz, alzu, ...)
select one, two or several languages (language CD)
choose special MD settings
adapt configuration parameters for 1 or several operator panels/NCUs
(netnames.ini), channel switchover
transfer user-defined screenforms for PLC status
create user displays using the software: "Expand Operator Interface
(Wizard)
-

3-71
3 Configuring
3.9.1
08.01
Installing the system software
Software areas
Preconditions
The CD contains the following software:
System software
User software
The HMI Embedded software is copied via an RS232C interface or PC card
to the internal EPROM.
The system software contains all the files required to operate HMI Embedded.
Language combinations other than English and German can be retroinstalled from the application floppy disk and/or language CD.
The user software area includes all system texts, PLC message texts and
cycle alarm texts.
Making the PCU 20

ready to receive
To upgrade the system software (software version) on the PCU 20, it

must be switched to Service mode (see below).
A PC/PG from which the new system software can be loaded is also
required.
Directories requiring up to 16 MB memory are set up on the hard disk of
the PC/PG. These directories contain the data selected for transfer
during installation.
Every time software is transferred from a PC/PG to a PCU 20, the latter must
be switched to the "ready to receive" state.
1.
2.
Service mode
The PCU 20 is switched off.

For transfer via RS232C:
Connect the defined serial interface on the PC/PG with the
interface on the PCU20 (COM1/COM2).
3. Switch on the PCU 20 and press key "6" when the serial number appears
(Service mode). Alternatively, you can press key "6" intermittently until a
selection menu prompting you to choose between update from card or
PCIN appears.
0: Update from PC Card
1: Update with PC-IN (COM1:)
2: Update with PC-IN (COM2:)
Select "PCIN" here if no PC card is available for updating the software. The
PCU 20 is now ready to receive data via the RS232C interface.
PCIN VERSION MMCIN- 1.1 (c) SIEMENS AG 1994 COM1: 19200 , EVEN,8,1 Xon/Xoff
V24 INI
DATA_IN
DATA_OUT
PCIN
EXIT
Light
VERSION MMC-IN System Upload 1.1

Copyright (c) SIEMENS AG 1994
3-72

08.01
1.SYS_INST.EXE
3 Configuring
Insert the CD
System installation HMI Embedded
<1> = Install system disk on hard disk

<2> = Install system disk on hard disk & to hardware
<3> = Select optional files for installation
<ESC> = Quit program!
1.
3.
Install the system software to the hard disk (PC/PG)!

With this command you can transfer the system software to several
PCs/PGs.
Install the system software to the hard disk (PC/PG) and transfer the
current configuration to the PCU 20 hardware!
With this command you can transfer the system software to the hard
disk (PG/PC) and install it immediately afterwards on the target PCU
20 hardware.
Update or change the DOS/BIOS software
ESC
F1
Cancels the installation and ends the program.

Displays online help for the active display (available soon).
2.
2. Change the
DOS/BIOS software
<3> (not necessary at
the present time)
<F1> - Help
Necessary only if prescribed explicitly in a software upgrade guide.

This point is omitted with normal installation.
Example:
You are installing SW 6.1
You find the following table in the upgrade instructions:
Table 0-1
Selection of basic system files
System file
Previous software version
ROMDOS20.BIN
6.1
-
5.3
-
You must select the relevant file by entering its number

in the sub menu for transfer to the PCU 20.
If you enter the number more than once, the selection toggles
between YES and NO.
The relevant file need not be selected for transfer to the
PCU 20.
Whether you need to load one or more files specified in the table to the PCU
20 will depend on which software version has been operated previously on
the PCU 20.
Only the selected files should be transferred.

3-73
3 Configuring
08.01
Select files to install
<1> = ROMDOS20.BIN
NO
<ESC> = Back to main menu

<F1> - Help
1.
ESC
Select whether the DOS/BIOS area (Video BIOS, System BIOS,

ROMDOS, PCIN) must be transferred
Return to the installation menu and transfer the selected
data
3. Enter a drive <2>

Copyright (c) Siemens AG 2001, all rights reserved
Installation kit version 06.01
Install system disk to hard disk
Select drive for installation
Drive:
ESC
F1
RETURN
Select the drive on the PC/PG to which the files from the system floppy disk
must be copied. Any hard disk drive or network drive with write authorization
can be selected.
4. Specify a path
Installation kit 06.01
Install system disk to hard disk
Select path for installation
Path:
C:\MMC100PJ.SYS
ESC
F1
RETURN
Select the path to which the files from the system floppy disk must be copied.
The path will be set up if it does not yet exist. "\mmc100pj.sys" is the
suggested default path.
Important
If the directory already exists, it will be overwritten!
3-74

08.01
3 Configuring
The files are copied to the hard disk.

If you selected command "Install system disk to hard disk" in the first menu,
installation of the system software is automatically terminated after execution
of the command and the initial menu appears again.
From the hard disk (e.g. network installation) it is possible to install the
system software on other PCs/PGs. You can then transfer the software to the
hardware by opening the directory in which it has been installed and calling
file "SYS_INST.EXE". The "System installation" menu appears.
To transfer the hardware configuration, continue as follows:
The transfer menu is displayed:
5. Transfer software to
hardware
Transfer software to hardware

Selected COM port: COM1
<1> = Install software via serial line
<2> = Create Flash Memory Card image
<3> = Select COM port
<ESC> = Quit program
<F1> - Help
Menu option 1:
Before you activate the transfer by selecting option <1>, you must ensure that
the PCU 20 is ready to receive and a cable connection to it has been made.
Menu option 2:
This option enables you to accelerate the update process. A flash memory
card image is generated that you can store in any directory of your choice. If
the directory you choose does not exist, it will be set up. If it already contains
a flash memory card image, this will be overwritten without warning.
See Subsection "Creating a PC card" for further instructions.
Menu option 3:
If the port displayed at "Selected COM port:" is not the same as the port to
which you have connected the cable on the PCU 20, press <3>. In the
following submenu, select the digit identifying the COM interface you have
used. You will then return to the transfer menu where your port selection is
displayed.
When you start the transfer, the following warning appears, ensuring that you
are loading the software to the correct hardware:
Transfer software to hardware PCU20
Selected COM port : COM1
<1> = Install system via serial line
<2> =
<3> =
<ESC> =
Important advice!
Please note!!!
Do you have the correct HMI hardware?
(old
MMC100.2 MLFB 6FC5210-0DA00-1AA0 or
old
MMC100.2 MLFB 6FC5210-0DA00-1AA1 or
new HT6
MLFB 6FC5503-0AA10-0AA0 or
newest PCU20
MLFB 6FC5210-0DF00-0AA0)
RETURN
ESC

<F1> - Help
3-75
3 Configuring
08.01
Make the PCU20 ready to receive

1.
Switch on the power supply for the PCU20.
2.
Switch on the PCU20 and press key "6" when the serial number
is displayed. Alternatively, you can press key "6" intermittently until a
selection menu appears on the screen. If a PCMCIA card is inserted,
you can choose between an update from card or the COM port for PCIN.
Otherwise you can select only one of the two COM ports. In this case,
you must select the "PCIN" with the COM port to which you have
connected the cable on the PCU20 if no programmed PC card is
available. The PCU20 is now ready to receive data via the RS232C
interface.
Activate the transfer
Select <1> in the transfer menu.
The transfer operation begins and its current status is displayed both on the
PC/PG and the PCU20.
Transfer is not o.k.
If the transmission path is not o.k., then the PCIN screen appears on the
PC/PG followed in a few seconds by the message:
WARNING
The program PCIN-Light returned a TIMEOUT error!
Check the cable, readiness to receive on the PCU20 and the specified COM
port. Once you have corrected the error, start the transfer operation again.
Series upgrade
You can update the software on several PCU units successively from the
transfer menu if you repeat the above sequence of operations in succession
for each PCU to be updated. Exit the transfer menu with <ESC> when you
are finished.
Finish
After you have finished transferring the software to the hard disk and PCU20,
close the installation menu with <ESC>. You are now in subdirectory
"INSTUTIL" of the hard disk directory to which the data from the system disk
were copied. You can start the installation menu again from here.
Start installation from HD
The installation menu appears again when "sys_inst.exe" is started. It no
longer contains menu option "Install system disk on hard disk" since this
transfer operation has already taken place. The other options can be selected
as described above.
3-76

08.01
3.9.2
3 Configuring
Installing the application floppy disk
Preconditions
The boot and system software must already have been loaded.
Compression software "ARJ.EXE" should be available.
Call file "APP_INST.EXE".
1. Call APP_INST.EXE
2. Specify a drive

Installation kit version 6.01
Install application disk to hard disk
Select drive for installation
Drive:
ESC
RETURN
Select the drive to which the application software files must be extracted. Any
hard disk drive or network drive with write authorization can be selected.
3. Specify a path
Installation kit 6.01
Install application disk to hard disk
Select path for installation
Path:
C:\MMC100PJ.APP
ESC
RETURN
Select the path to which the application software files must be extracted. The
path will be set up if it does not yet exist. "\mmc100pj.app" is the suggested
default path.
The files are copied to the hard disk and extracted!

3-77
3 Configuring
08.01
After the files have been installed on the hard disk, the following selection
menu appears :
4. Prepare SW modules
for transfer and install on
the hard disk
Install application to hardware PCU20

First language: English Second language: German
<1> = Install all modules to hardware
<2> = Modify configuration
<ESC> = Esc to quit!
1.
2.
ESC
F1
4.a. Language
setting <1>
<F1> - Help
Install the current configuration on the hardware!

Change the language settings and edit selected ASCII files.
Cancels the installation and ends the program.
When you select <1> the transfer languages are selected. Press the Return
key to display more selectable languages (if available). Confirm your
selection with <F4>.
Select additional language for application disk
Selected Hardware:
X>
English
French
X>
German
<ESC> = Cancel
4.b Define the

configuration <2>
<F1> = Help
<F4> = Accept
<Return> = Toggle
Install application on hardware PCU20

<1>
<2>
<3>
<4>
<5>
<6>
= Change first language

= Change second language
= Edit ASCII files
= Edit text file for first language
= Edit text file for second language
= Add user-specific files
<ESC> = Back to previous menu!

1.
2.
3.
4.
5.
6.
3-78
<F1> - Help
Change the language setting for the first language.

Change the language setting for the second language.
Edit the ASCII files of the system and applications if they contain
ASCII files.
Edit the language files for the selected first language.
Edit the language files for the selected second language.
Copy PLC status files or others (Wizard) to the application image.

08.01
3 Configuring
ESC
F1
4.b.1 Edit ASCII
files <3>
Return to the installation menu.

Install application on hardware PCU20

<1>
<2>
<3>
<4>
<5>
<6>
= Edit MPI configuration data

= Edit display machine data
= Edit AUTOEXEC.BAT
= Edit CONFIG.SYS
= Edit OEM.BAT
= Edit user specific files
<ESC> = Back to previous menu!

<F1> - Help
Items 1...6 start "EDIT.COM" for editing the relevant files.

Individual points are displayed only if the files exist.
ESC Exits the menu.
F1
Displays online help (available soon).
Warning
!
5. Transfer software
to hardware
Correct functioning of the software cannot be guaranteed if unauthorized

changes are made to "AUTOEXEC.BAT" and "CONFIG.SYS" files
Transfer software to hardware PCU20

Selected COM port: COM1
<1> = Install software via serial line
<2> = Create Flash Memory Card image
<3> = Select COM port

<F1> - Help
If the port displayed at "Selected COM port:" is not the same as the port to
which you have connected the cable on the PCU 20, press <2>. In the
following submenu, select the digit identifying the COM interface you have
used. You will then return to the transfer menu where your port selection is
displayed.
Before you activate the transfer by selecting option <1>, you must ensure that
the PCU20 is ready to receive and a cable connection to it has been made.
Activate the transfer
Select <1> "Install software via serial line" in the transfer menu.
The transfer operation begins and its current status is displayed both on the
PC/PG and the PCU20.

3-79
3 Configuring
08.01
Transfer is not o.k.

If the transmission path is not o.k., then the PCIN screen appears on the
PC/PG followed in a few seconds by the message:
"WARNING The program PCIN-Light returned a TIMEOUT error!"
Check the cable, readiness to receive on the PCU20 and the specified COM
port. Once you have corrected the error, start the transfer operation again.
Series upgrade
You can update the software on several PCU units successively from the
transfer menu if you repeat the above sequence of operations in succession
for each PCU to be updated. Exit the transfer menu with <ESC> when you
are finished.
Finish
After you have finished transferring the software to the PCU20, close the
installation menu with <ESC>. You are now in subdirectory "INSTUTIL" of the
hard disk directory to which the data from the application disk were copied.
You can start the installation menu again from here.
Start installation from the PC/PG
The configuration menu appears when you start "app_inst.exe". The selection
options for drive and path are omitted since the files have already been
transferred from CD to hard disk. The other options can be selected as
described above.
Readiness to receive on PCU20
1. Switch on the power supply for the PCU20.
2. Switch on the PCU20 and press key "6" when the serial number is
displayed. Alternatively, you can press key "6" intermittently until a
selection menu prompting you to choose between update from card or
PCIN appears. Select "PCIN" here if no PC card is available for updating
the software. The PCU 20 is now ready to receive data via the RS232C
interface.
Installation info
Normal situation
The transfer operation begins and its current status is displayed on the
PCU20.
Errors in making PCU20 ready to receive
If no error-free connection can be established after you have taken the steps
above, the PCU 20 waits initially or aborts on error.
Check the connecting cable, the COM port setting for the PC/PG and press
"R" for Retry after you have eliminated the fault. If you cannot clear the fault,
switch the control off and then on again. Try to establish a connection again.
End of transmission
Exit the transfer menu by pressing <ESC>. Subdirectory "INSTUTIL" will now
be the active directory.
Start installation from HD
The configuration menu appears when you start "app_inst.exe". The selection
options for drive and path are omitted since the files have already been
transferred from CD to hard disk. The other options can be selected as
described above.
Installation via a network (available soon)
3-80

08.01
3.9.3
3 Configuring
Textdisk: Updating the system software language

The "textdisk" text software is an update of the system software texts,
enabling you to do the following:
Add new languages to the screen kit.
Add new languages to the application image.
Preconditions
1. Call TXT_INST.EXE
The configuration in the text software (selected operating areas) must match
the configuration of the screen kit and the installed application software.
Insert the CD and call file "TXT_INST.EXE".
Update texts for your hardware
<1> = Update texts on your screen kit

<2> = Update texts on your application disk installation
<3> = Generating Install-Shield Image
<F1> - Help
1
Add a new language to the screen kit.
2
Add a new language to the application image.
3
Compile the install shield image.
ESC Terminates the program.
F1 displays online help for the active display (available soon).
2. Add a new language
to the screen kit
2.a Specify a drive

Installation Kit version 6.01
Update texts on your screen or installation kit installation
Select the drive in which your SCK/SDK was installed
Drive:
ESC
F1
RETURN
Specify the drive on which the application software files have been installed

3-81
3 Configuring
08.01
2.b Specify a path

Installation Kit version 6.01
Update texts on your application installation
Select the drive in which your application was installed
Drive:
ESC
F1
RETURN
Enter the path in which the Screen Kit has been installed. "\mmc100pj" is the
suggested default path.
After the files have been installed on the hard disk, the update is complete.
3. Add a new language
to the application
software image

Screen kit version 6.01
3.a Specify a drive

Select the drive in which your application was installed
Drive:
ESC
F1
RETURN
Specify the drive on which the application software files have been installed.
3.b Specify a path
Screen kit version 6.01
Select the path in which your application was installed
Path:
E:\MMC100PJ
ESC
F1
RETURN
Enter the path in which the application software files are installed.
"\mmc100pj" is the suggested default path.
After the files have been installed on the hard disk, the update is complete.
3-82

08.01
3.9.4
3 Configuring
Creating a PC card
Name convention for

PCMCIA card
Preconditions
The PCMCIA cards used for the NCU and PCU20 are very similar in
appearance and therefore easily confused with one another. To help you
distinguish between them, we refer below to the PCMCIA card
for the NCU as the "NCU card" and
for the PCU as the "PC card".

You have already installed the system environment on the PG/PC.
You have installed the "SINUCOPY_FFS" software.
1.
2.
3.
4.
5.
6.
7.
3.9.5
Precondition
Change to the "instutil" directory in the system environment, e.g.

"\mmc100pj.sys\instutil" (the directory you specified when you installed
the system environment on the PC/PG).
Call "sys_inst".
Select option <1> "Install system on hardware".
Select option <2> "Create Flash Memory Card image"
Specify the target directory in which the ABB system file must be
stored.
File "pcu20.ABB" is then generated.
Insert the PC card in the PCMCIA slot on the PC/PG.
Transfer the new ABB file to the PC card using "SINUCOPY-FFS".
Updating software via the PC card

PC card with the latest HMI Embedded software version
1.
Switch off the control system
2.
Insert the PC card with the latest HMI Embedded software version
3.
Switch on the control system
4.
When HMI Embedded is booting, press key "6" when the message
"Starting Caldera DR -DOS" appears.
5.
The following dialog appears
"0: Update from PC Card"
"1: V.24" COM1"
"2: V.24" COM2"
Select option "0: Update from PC Card"
6.
When the update is complete, the following message is displayed:
"Remove PC Card".
7.
When you remove the card, the control boots automatically.
Note
If you insert the NC card instead of the PC card or vice versa, the control
outputs a message.

3-83
3 Configuring
3.10
08.01
Installing HMI Embedded Win 32 on a PCU50
Principe
During initial start-up, Windows NT and the SINUMERIK 840D system

software are loaded to the hard disk of the PCU.
The hard disk of the PCU is pre-partitioned for SINUMERK 840D operation
and further SINUMERIK applications on delivery and the software required for
a basic start-up is installed:
The boot software and other software needed for start-up are stored
on C:
The disk image with Windows NT and the SINUMERIK 840D system
software is stored in D:\IMAGES
Partitions E: and F: are empty.
PC U
Hard disk
C:
FAT16
DOS Tools
Prim ary partition
active
D:
F AT16
TMP, Im ages,
Install, Updates
Extended partition
w ith logic drive
NTFS
W inNT
NTFS
840D System
HM I, further applications
Prim ary patition
Prim ary patition
Partitioning during initial start-up
Select a version
When the PCU boots for the first time, the following menu is displayed:
PLEASE SELECT SINUMERIK HMI Version to install:
1 SINUMERIK 840D Software <version>
......
9 Service Menu
Your Choice [1,....9]?
Select the version that you wish to install by pressing a key between "1" and
"8" and acknowledge the following prompt with "Y".
After you confirm the version, the appropriate disk image is loaded to the hard
disk (partitions C:, E: and F:).
The available range of versions remains stored in D:\IMAGES so that you can
load them to replace the version selected during initial start-up at a later point
in time using the "Restore Partitions" function.
For an exact description of installing the system software, please refer to:
/IAM/ Installation & Start-Up Guide HMI/MMC, IM4
3-84

08.01
3.10.1
3 Configuring
Installing via a parallel link with a FAT16 file structure
Preconditions
Principle
You will need a PC or a PC with a CD ROM drive.

INTERSVR is used on the external PG/PC to transfer the software to the
PCU. It can be operated under DOS / Win3.11 / Win95 / Win98 only if the
PG/PC has a hard disk partition with a FAT16 file structure (not FAT32 !).
This function transfers the HMI software to be installed to D:\INSTALL. The
actual installation is carried out by Windows NT on the next boot provided the
software includes an exe file, e.g. "setup.exe".
Important:
Before you attempt to install the software, make sure that there is sufficient
memory available on the partition D of the hard disk.
Transmission
Sequence of
operations
You must use the parallel (not the serial) interface to transfer the HMI
software.
1.
2.
Switch off the PCU

Using the parallel connecting cable (PC-Link cable, LapLink cable),
connect the parallel port LPT on the PG/PC to port LPT on the PCU.
Mode of transmission
PC/PG
PCU
parallel
LPT1
LPT (25-pin)
3.
4.
5.
Copy directory HMI_Advanced from the CD to drive C:\ on the hard disk
of your PG/PC and rename it "MMC2". If there is insufficient memory
space available on drive C:\ or it does not have a FAT16 file structure,
you may also use another local hard disk drive (e.g. D:\). The software
cannot be installed directly from the CD.
The HMI software installation is started when you open the Windows
Start menu and select Run Intersvr C: (or the drive on which directory
MMC2 is stored).
IMPORTANT: If your PC/PG is in this state, the PCU must be switched
off. (If the PCU is switched on, switch it off now).
Switch on the PCU, select the "Service Menu" (invisible menu option) in
the boot manager.

3-85
3 Configuring
08.01
The following menu is displayed:

PLEASE SELECT:
1 Install/Update SINUMERIK System
2 SINUMERIK Tools and Options
3 DOS Shell
4 Start Windows NT (Service Mode)
5 SINUMERIK System Check
7 Backup/Restore
8 Start PC Link
9 End (Warmboot)
Your Choice[1, 2, 3, 4, 5, 7, 8, 9]?
6.
Select option 1
The system requests you to enter a password by displaying:

passwd:
Enter one of the passwords for authorization levels 0 - 2
- System
- Manufacturer
- Service
The following menu is displayed
PLEASE SELECT MEDIUM:
1 Install from Floppy Disk
2 Install via Serial/Parallel Line
3 Install from Network Drive
5 REBOOT
9 Return to Main Menu
Your Choice [Your Choice [1,2,3,5,9]?
7.
8.
9.
10.
11.
12.
13.
3-86
Select menu option 2 Install via Serial/Parallel Line.

The data transfer begins. The system boots to Windows NT and the
installation is started automatically.
Select a language
Select a technology: Milling or turning
The system lists all the entries you have made.
The PCU is rebooted once the installation is complete.
End PC/PG server mode by pressing Alt + F4.

08.01
3.10.2
3 Configuring
Installing via a parallel link with a FAT32 file structure
Principe

Important:
Preconditions
You will need a PC or a PC with a CD ROM drive.

You will also need a full keyboard on the PCU.
To install the software you will required the CD ROM with the system SW.
Transmission
You must use the parallel (not the serial) interface to transfer the HMI
software installation.
When to use
This method must be used when your PC/PG has only partitions with a
FAT32 file structure.
Sequence of
operations
1.
2.
3.
4.
Copy interlnk.exe from the HMI directory on the CD to

WINDOWS\COMMAND on the PC/PG. Insert the following line in
config.sys:
device=c:\windows\command\interlnk.exe/AUTO
Switch off the PCU.
Using the parallel connecting cable (PC-Link cable, LapLink cable),
connect the parallel port LPT on the PC to port LPT on the PCU.
Switch on the PCU,
select the "Service Menu" [invisible menu option] in the boot manager.
PLEASE SELECT:
3 DOS Shell
7 Backup/Restore
8 Start PC Link
9 End (Warmboot)
Your Choice[1, 2, 3, 4, 5, 7, 8, 9]?

3-87
3 Configuring
08.01
5. Press key 8
passwd:
6.
Enter one of the passwords for authorization levels 0 - 2

- System
- Manufacturer
- Service
7.
Now copy the entire contents of the directory HMI_Advanced on the CD

to directory D:\INSTALL on the PCU. When the SW has been
transferred, end INTERSVR on the PCU by pressing Alt + F4. The
system will boot to Windows NT.
8.
In Win NT: The SW will now be installed automatically by means of

InstallShield from the PCU. You can operate the InstallShield prompt
boxes with TAB and the cursor keys (TAB corresponds to the END key
on the OP0xx).
The system powers up after the PCU has rebooted.
9.
3.10.3
Installing via a network connection
Principle

Important:
Note
If you are using a different language version of the Windows system, the
terms used in the following setting operations may be different. The
sequence of operations as specified below, however is always the same.
Preconditions
3-88
Windows NT 4.0 or Windows 95 or Windows 98

NETBBEUI is set
Set the NETBEUI protocol (load via Control Panel:
Start Settings Control Panel Network symbol Configuration tab
"Add": NETBEUI.)
Computer name of the PG/PC (look on Control Panel:
Start Settings Control Panel Network symbol Identification tab
"Computer name" e.g.: r3344)

08.01
3 Configuring
Shared access to directory

Give access to directory in which SW to be installed is stored.
Windows NT4:
Enter a share name (e.g. HMINEW).
Enter authorization (e.g. User1 [local user] or "anyone" with "read" access
authorization).
Windows 95:
Enter a share name (e.g. HMINEW).
Enter access authorization.
Specify a password if applicable.
Cable connected
Cable for point-to-point connection in Ethernet port: Ethernet cable of type
"Converted Twisted Pair cable".
Windows 95/98:
Share-level access control selected
under Start Settings Control Panel Network symbol: Access Control
tabs "Share-level access control"
Sequence of
operations
While the PCU is booting (after control is switched off and on again):
1.
Select the "Service Menu" [invisible menu option] in the boot

manager.

PLEASE SELECT:
3 DOS Shell
7 Backup/Restore
8 Start PC Link
9 End (Warmboot)
Your Choice [1,2,3,4,5,7,8,9]?
2.
Select option 1.

passwd:
-
System
- Manufacturer
- Service

3-89
3 Configuring
08.01
PLEASE SELECT MEDIUM:

1 Install from Floppy Disk
2 Install via Serial/Parallel Line
3 Install from Network Drive
5 REBOOT
9 Return to Main Menu
Your Choice [1,2,3,5,9]?
3.
Connect to network
drive
Select option 3.

PLEASE SELECT:
1 Connect to Network Drive
2 Show connected Network Drives
3 Disconnect from all Network Drives
4 Change Install Directory
5 Install from F:\INSTALL
9 Back to previous Menu
Your Choice [1,2,3,4,5,9]?
4. Select option 1.
Enter the user name and the password with which you can fetch the SW
from the shared directory on the networked PG/PC.
Windows NT4:
User name and password of a local user of the PG/PC.
Windows 95:
Optional user name, password to match the password specified when
access to the directory was shared.
Password entry can be confirmed.
Enter the drive letter on the PCU via which the directory must be
accessed (e.g. "H").
DIRECTORY TO BE MOUNTED:
Enter the computer name of the PG/PC and the name of the directory
(=share name) that you wish to access,
e.g. \\r3344\HMINEW.
Network information is displayed on the PCU:

Connected Network Drive (last)
Install Directory
3-90
H: (\\r3344\HMINEW)
F:\Install

08.01
Change installation
directory of the
connected drive
3 Configuring
You can change the installation directory on the connected computer:

PLEASE SELECT:
2 Network Drives
Your Choice [1,2,3,4,5,9]?
6.
Select option 4.
The input box appears in which you can specify the installation directory (e.g.
HMI_INST):
Old Install Directory:
New Install Directory:
F:\INSTALL
H:\HMI_INST
You can now start the transmission:

PLEASE SELECT:
5 Install from H:\HMI_INST
Your Choice [1,2,3,4,5,9]?
7.
Install
Select option 5.
The system starts the transmission from the external computer to the
PCU.
The PCU is automatically rebooted after the transmission.
Select "SINUMERIK" in the boot manager. The SW you have just
transferred is now installed under Windows NT, menu-assisted in some
cases.
The system checks whether directory D:\INSTALL already contains files.

Note
If the SW cannot be copied to directory D:\INSTALL on the PCU, then the
system cannot start the installation.

3-91
3 Configuring
08.01
You can display all the connections to the PG/PC:

Show connected
network drives
PLEASE SELECT:
Your Choice [1,2,3,4,5,9]?
8.
Select option 2
The current status of the connected drives is displayed:
Status
OK
OK
Disconnect from all

network drives
Local Name
H:
J:
Remote Name
\\r3344\HMI_INST
\\r3344\HMI_P1
You can disconnect all links to the PG/PC:

PLEASE SELECT:
Your Choice [1,2,3,4,5,9]?
9.
Select option 3.
The current status of the last connected drive is displayed:
Connected Network Drive (last):

Install Directory:
Back to previous
menu
-noneH:\HMI_INST
When you exit the menu, you will be prompted to confirm whether the
initialized network parameters must be saved.
3-92

Working with Microsoft Visual C and

HMI Embedded
4.1
Using MS Visual Studio 6.0.............................................................................4-94
4.2
Using the MSVC Workbench ..........................................................................4-98
4.3
Known restrictions and incompatibilities .......................................................4-100

SINUMERIK 840D/810D HMI Embedded Configuring Package (PJE) 08.01. Edition
4-93
4 Working with Microsoft Visual C and HMI Embedded
4.1
08.01
Using MS Visual Studio 6.0
General notes
Make only a few changes at one time.

As a result of the modeled dependencies in the make files, only edited files are
regenerated. You will save only a nominal amount of time by generating new
files at greater time intervals, but it will be more difficult to localize the causes
of errors.
Reduce the risk of editing files by mistake.

Select the write protection option in the File Open window of MS Visual Studio
for files that you only wish to read or use as a template.
Compiler and linker

options
You can change the project settings by selecting menu options

PROJECT SETTINGS in Visual Studio. You can, for example, extend the
include paths or set the compiler flags.
Since there are numerous options and settings for projects in Visual Studio, it
would not be sensible to list all of them here. Instead, only the most important
settings are given below. If your application does not work when you set the
project in this way, you should compare your settings with those of a project
that does work or with the appropriate template files stored in
mmc100pj\Instutil\Tpl.
The defaults are as follows: ( extract )
General tab
- Microsoft Foundation Classes: Not Using MFC
C/C++ tab
- C++
-
- Language
- Representation Method: Best-Case Always
Code Generation
- Processor: Blend
- Use run-time library: Multithreaded DLL
- Calling Convention: __cdecl
- struct member alignment: 1 byte
Optimizations
- Customize: Global Optimizations; Generate Intrinsic Functions,
Favor Small Code; Frame-Pointer Omission; Full Optimization
- Inline function expansion: Only inline
Preprocessor
- Preprocesser definitions:_PM
- Additional include directories: .\h,..\h,..\..\include,..\..\..\public,
..\..\..\public\headsys ........
Link tab ( for project <APPNAME> only )

General
- Output file name: ..\..\..\Proj\Sl\Appname.dat
- Object/Library modules: ...... ..\..\..\Proj\Sl\sl_glb.lib
4-94

08.01
Errors, warnings :
Specification of line
numbers
For commands in configuring source files which extend over several lines, the
number of the line containing the closing bracket or the statement end is
always specified as the line number for error or warning messages.
With a configuring macro, for example, you should not assume that it is the last
parameter that is incorrectly assigned. By pressing key <F4> you can scroll
through the messages of any error or warning list; MS Visual Studio
automatically positions the cursor on the errored line of the appropriate file.
Note
To generate your application complete, you must always use TOOLS
GENERATE SL.DAT.
Add to a project
Integrating a *.C file in the application:

Open a project OEM PATH\Proj\App\ApplicationName
\ApplicationName.dsw
To open the Insert dialog, select menu options PROJECT
PROJECT
FILES .
ADD TO
Select the project ApplicationName_li in the combobox "Insert Into" at the end
of the dialog.
Mark the file to be inserted in the selection window and add it to the project by
clicking on OK.
The dependencies of the files in the project are generated again.
To remove a file from the project again, select the file in window "Workspace"
"File View" tab ( the window is normally on the left of the Visual Studio
screen ). You may need to open folder ApplicationName\Source Files first.
Then press the DELETE key.
Save a project
Projects are saved in Visual Studio with the higher-level workspace. To do this,
select menu options FILE
SAVE WORKSPACE.
Convert an MSVC
project to Visual
Studio.
The best way to convert an old MSVC project to an MS Visual Studio project is
as follows:
Once you have copied the application directory to the new Screen Kit, you
must save it, mmc100pj\Proj\App\ApplicationName,
...\Proj\App\H\ApplicationName.h,
...\Proj\App\H\AApplicationName.h and
...\Sck\Cfg\ApplicationName.cfg
copy it to another directory and remove the originals.
-
You must remove any copied text files so that the application manager can
create new ones.
Delete ApplicationName.txt and
AApplicationName.txt from folders
mmc100pj\Proj\Text\Language\.

SINUMERIK 840D/810D HMI Embedded Configuring Package 08.01 Edition
4-95
08.01
Create a new application using the Application Manager. It should have the
same name as the old MSVC application. ( Subsection 3.2.2: Creating a
new application configuration )
Overwrite the newly created files with the files of the old MSVC application.
The project and workspace files of the new applications must not be
deleted.
- Copy the contents of the old application folder into the new folder
mmc100pj\Proj\App\ApplicationName. The source, header and text
files created by the Application Manager will also be overwritten at the
same time.
- Copy the text header files ApplicationName.h and AApplicationName.h
to ...\Proj\App\H.
- Copy the old configuration file ApplicationName.cfg into folder
mmc100pj\Sck\Cfg, overwriting the newly created file again.
Note
If you want to use any new functions of the Screen Kit, it is advisable to
compare the CFG files line by line and to insert only the lines you need into the
new CFG file.
-
Open the application with Visual Studio. ( Menu options FILE

WORKSPACE)
OPEN
Delete the source and header files generated by the Application Manager
from project ApplicationName_li.
- Select the "File View" tab in the workspace window ( normally at lefthand margin ).
- Open the folder ApplicationName_li in the file tree.
- Open the subfolder "Source Files" in the file tree and select all the files
it contains.
- Remove the files from the project by pressing the DELETE key.
- Proceed analogously for the "Header Files" subfolder.
Copy the "old" source and header files to project ApplicationName_li.

- Select menu options PROJECT ADD TO PROJECT FILES
to copy the appropriate source and header files to the project. Make
sure that you have selected project ApplicationName_li at "Insert into" in
the Open dialog.
- The source file ap_l_dir.c is not copied since it is stored in the
ApplicationName project already.
Tip: Colorhighlighted
keywords, editor
settings
The Visual Studio editor allows you to color-highlight the different elements
(source code, comments, etc.) in the text for better identification. You will find
the appropriate dialog under TOOLS OPTIONS FORMAT. To alter the
coloring of the Screen Kit keywords, for example, you must select "User
Defined Keywords" in the COLORS list.
Tip: Defining
keyboard shortcuts
You can assign keyboard shortcuts to menu commands in dialog

TOOLS CUSTOMIZE KEYBORD tab. You will find the Screen Kit tools in
the Tools category under UserToolxx.
4-96

08.01
Tip: Automatic SDK

help
If you add the argument "-k $(CurText)" to the argument entries for the Screen
Kit online helps IN FRONT OF the help file path under
TOOLS CUSTOMIZE TOOLS, the currently selected word is automatically
sought and displayed when you open the help file (e.g. the explanation of the
RECTANGLE macro is displayed if the cursor is positioned on this word when
you open the configuring syntax help file).
Important
The program WINHLP32.EXE displays an index list if the word has not been
found. If you end WINHLP32.EXE in this state, part of the memory will not be
released again!!! For this reason, make sure that you always display a topic
before you end WINHLP32.EXE.
Tip:
Macros
Use the MACRO functions of Visual Studio to automate frequently repeated

operations, e.g. it is easy to record a macro which makes the appropriate entry
in ap_l_dir.h after you have created a new list. ( select
BEGIN_xxx(NEW_LIST>), copy, insert in ap_l_dir.h and replace BEGIN_ with
EXTERN_.)
Macro functions are stored under TOOLS MACRO..., for detailed information
please refer to your Visual Studio guide.
Tip:
One workspace for
all projects
If you are working "simultaneously" on several applications, you can integrate

all projects into one working area by selecting menu options
PROJECT INSERT PROJECT INTO WORKSPACE. Unfortunately, Visual
Studio "forgets" the project dependencies in this case. You must therefore
enter them again under PROJECT DEPENDENCIES. ( Please note: The
project <XXX> is always dependent on <XXX>_LI ).
Tip:
Troubleshooting
Visual Studio uses an output window that is overwritten when you call 'Build'
again. You can, however, save the contents of this window under an optional
name by selecting FILE
SAVE AS.

4-97
4.2
08.01
Using the MSVC Workbench
General notes
Make only a few changes at one time.

As a result of the modeled dependencies in the make files, only edited files are
regenerated. You will save only a nominal amount of time by generating new
files at greater time intervals, but it will be more difficult to localize the causes
of errors.
Reduce the risk of editing files by mistake.

Select the write protection option in the File Open window of the MSVC
Workbench for files that you only wish to read or use as a template.
Change files that you do not use all the time into icons. They will be loaded and
available again, but write-protected as icons, when you restart the MSVC
Workbench.
Compiler and linker

options
The following compiler options are set in the *.mak projects:

/W4 /ALu /Gt1 /Od /ND "APP_SEG" /D "NDEBUG"
/I "::\h" /I "::\..\h"/I "\proj\h" /I "..\..\..\..\public"
For HT6:
/W4 /ALu /Gt1 /Od /ND "APP_SEG" /D "NDEBUG" /D "_HT6" /I "..\h" /I "..\..\h"
/I "..\..\..\..\public" /I "..\..\..\..\public\headsys" /I "..\..\..\include"
and the following linker options:
/NOLOGO /NOD /NOI /STACK:1 /ONERROR:NOEXE
If you change these by mistake, you can restore the right settings again under
OPTIONS
PROJECT.
Errors, warnings :
Specification of line
numbers
For commands in configuring source files which extend over several lines, the
number of the line containing the closing bracket or the statement end is
always specified as the line number for error or warning messages.
With a configuring macro, for example, you should not assume that it is the last
parameter that is incorrectly assigned.
Working efficiently
With ApplicationName.mak make files, you can press key <F4> to scroll
through the messages of any error or warning list; in this case, the MSVC
Workbench automatically positions the cursor on the errored line in the
corresponding file.
To generate your application complete, you must always use TOOLS
GENERATE SL.DAT.
4-98

08.01
Add to projects
Integrating a *.C file in the application

Open a project OEM PATH\Proj\App\ApplicationName
\Obj_c800\ApplicationName\.mak
Select PROJECT
EDIT
Mark the file to be inserted in the selection window and add it to the project by
clicking on ADD.
The dependencies of the files in the project are generated again.
Note
In this case, the MSVC Workbench searches through only those directories
that were entered under OPTIONS
DIRECTORIES as the Workbench was
initialized. If an include file is not found in any of these paths, no warning is
output!
Generating new dependencies

As soon as you insert an additional include statement in a C file, you must
generate the file dependencies again.
Open the project to which the C file belongs.
Start PROJECT
SCAN ALL DEPENDENCIES.
The dependencies are stored in the MAK file when you close the project or exit
the MSVC Workbench.
Save a project
The MSVC Workbench does not unfortunately offer an explicit 'PROJECT

SAVE' command.
When and to what extent projects are saved is not fully documented.
To save any new files, dependencies, open file windows, etc. in the project,
you should save any important editing measures (e.g. Project Edit) by closing
and then reopening the project.
Editor
settings
The MSVC Workbench editor allows you to color-highlight the different

elements (source code, comments, etc.) in the text for better identification. To
do so, select menu commands OPTIONS
COLOR.
Error documentation
The MSVC Workbench uses an output window that is overwritten when you
call 'Build' again. You can, however, save the contents of this window under an
optional name by selecting FILE
SAVE AS.

4-99
4.3
08.01
Known restrictions and incompatibilities
Text editors AEDIT

and VI (for DOS)
Some ASCII editors (particularly the older versions) insert control characters in
the text to represent special characters, TABs, etc. or characters from the top
area of the ASCII table.
These characters cause text conversion errors.
This is known to happen with AEDIT and V1 (but not XVI). As a consequence,
these editors should not be used to generate and maintain text source files
*.txt.
Important!
If the comment // ANSI = NO appears at the top of the text file, a DOS editor
(e.g. EDIT) must be used to integrate special characters in text files to ensure
that they are integrated correctly. This is due to the fact that the Windows
character set deviates from the standard.
This always applies to text changes made via the Installation Kit.
4-100

Operating HMI Embedded
5.1
HMI Embedded - test mode on a PC ............................................................5-102
5.2
PC simulation mode ......................................................................................5-103
5.3
PC MPI mode................................................................................................5-104
5.4
5.4.1
Key assignments in PC mode .......................................................................5-105

Mode of operation of "Dialog" keys ...............................................................5-107
5.5
mmc0_con.cfg: Emulation of variables .........................................................5-108

5-101
5 Operating HMI Embedded
5.1
Description
08.01
HMI Embedded - test mode on a PC

The HMI Embedded configuring package allows you to run your configurations
through "a quick check" on a PC. This saves you the time and work of
transferring them to the appropriate hardware when you "just" want to check
the layout.
You can choose between 2 different PC modes
PC MPI mode
PC simulation mode
You can select one of these modes by setting variable "pc_test" in file
mmc100pj\Bin_sim\mmc0.ini:
To activate
pc_test = 0
PC MPI mode
pc_test = 1
PC simulation mode
The HMI Embedded software is started when you select menu options
TOOLS PC-SIMULATION in the MSVC Workbench.
You can now operate the software in the same way as if it were installed on the
hardware.
5-102

08.01
5.2
PC simulation mode
Description
In PC simulation mode, part of the NC or PLC data is emulated by a simulation

program. This mode is designed solely to allow you to test the operator
interface layout and the menu control. The data contents may deviate
significantly from real conditions in actual operation.
You can identify PC simulation mode by the alarm 100650 "No NC/PLC found!
Simulating NC/PLC!"
Preconditions
The configuring package has been installed properly and an executable

application is available, i.e. the files sl.dat and mmc0conf.bin must be stored in
directory mmc100pj\Bin_sim.
To open
Open the MSVC Workbench and start PC simulation by selecting menu

options TOOLS
PC Simulation.
To close
The HMI Embedded SW is closed when you select key combination:

CTRL+X (from SW 6.2.1 CTRL+Q), then RETURN.
(Hold down the CTRL key, then press X (or Q from SW 6.2.1), then release
both keys and press RETURN )
or
press the Cancel button in window "HMI-Embedded-Win32"
Typical errors in PC
simulation mode
pc_test not set to 1.

No sl.dat.
No mmc0conf.bin.
No *.sp1,2.
No achssim.ovl.
No BD, MPF, WKS, SPF + *.DIR.
No BD_TEA.ACC, BD.TEA.

5-103
5.3
08.01
PC MPI mode
Description
In PC MPI mode the HMI Embedded software communicates with an NC or a

PLC. The logical operating characteristics correspond to real conditions on the
HMI Embedded hardware.
In PC MPI mode you can connect your PC directly to an NC using an MPI
cable and operate the NC using the HMI Embedded SW.
Restriction in relation
to HT6
The keys of the integrated MCP interface on the HT6 cannot be operated from
the PC. It is not safe to operate a machine because there is no emergency
stop or enabling key. You cannot therefore start/stop/reset programs, move
axes or switch operating modes from the PC.
Preconditions
The configuring package has been installed properly and an executable

application is available, i.e. the files si.dat and mmc0conf.bin must be stored in
directory mmc100pj\Bin_sim.
Your PC has a functional MPI interface, e.g. a Simatic NET CP5611 MPI card
with corresponding drivers.
Your PC is connected to the NC via an MPI cable.
Please read the MPI interface documentation for further details.
To open
Open the MSVC Workbench and start PC simulation by selecting menu

options TOOLS
PC Simulation.
To close
The HMI Embedded SW is closed when you select key combination:

CTRL+X (from SW 6.2.1 CTRL+Q), then RETURN.
(Hold down the CTRL key, then press X (or Q from SW 6.2.1), then release
both keys and press RETURN )
or
press the Cancel button in window "HMI-Embedded-Win32"
Typical errors in PC
MPI mode
pc_test not set to 0.

No sl.dat.
No mmc0conf.bin.
No *.sp1,2 files
MPI interface does not function (MPI card, drivers, MPI cable, bus address...)
NC not booted
5-104

08.01
5.4
Key assignments in PC mode
Restriction
Not all keys are always available on the different HMI Embedded HW options,
but most of them can be used in PC mode via the PC keyboard.
Description
The HMI Embedded keys are mapped onto the standard PC MFII keys as
follows:
Symbol
Description
Area switchover key
Key on MFII
F10
Display basic menu
Machine area key
Shift F10
Display machine area
Recall key
F9
Return to previous menu if

symbol is displayed.
Etc. key
Shift F9
Extend menu
Change channel
F11
Switch over to the next channel
Information key
F12
Display help
Edit key
Insert
To edit input fields
Input key
Return / Enter
To terminate inputs

5-105
08.01
Description
Key on MFII
Acknowledge alarm key
Escape key
To acknowledge alarms with this

reset symbol
Window selection key
Home
Change the active window
Select / toggle key
"5" on numeric keypad

without NumLock
Selection key for values set in

fields labeled with this key
symbol.
Cursor keys,
paging keys,
Home, End
Navigation keypad
Digits, "."
Numeric keypad
Navigation in windows and fields
Cursor keys, paging keys

(Pgup, dn) Home, End
Digits, "."
Numerical inputs
Letters,
special
characters
Alphabetic characters
Arrow to left,
Backspace key
Letters,special characters
Alphabetic inputs
Backspace
Deletes preceding character
5-106
Softkey1 Softkey8
Horizontal softkeys
F1-F8
Vert. softkey1Vert. softkey8
Vertical softkeys
JOG
JOG mode
Alt F1
MDA
MDA mode
Alt F2
AUTO
AUTO mode
Alt F3
Teach In
Teach key
Alt F4
Control Panel
Function
CPF key
Alt 7
U1- U8
User keys
Ctrl F1-F8
S1- S2
Start special keys
Ctrl F9-F10
Menu control
Shift F1-F8
Menu control
Simulated keys of MCP

integrated in HT6

08.01
5.4.1
Mode of operation of "Dialog" keys
Navigation mode
You can normally navigate between fields using the cursor and paging keys.
Edit mode "Overwrite

field contents"
Position the cursor on the field you wish to edit.

Simply start typing in the digits or characters.
The field content will be deleted beforehand by the system, the field is empty.
Edit mode "Change

field contents"
Position the cursor on the field you wish to edit.

Open the field with the Edit key.
The content of the field is not deleted.
Position the cursor inside the field using the cursor keys and make your input.
Terminate an input
You can terminate your field inputs correctly by pressing the Input key or
exiting the field with the Cursor Up or Cursor Down key.
Undo an input
The inputs in your field will be discarded if your press the Edit key again in Edit
mode.
The field will be closed and you will find yourself back in Navigation mode.
The value stored in the field before you switched to Edit mode will be entered
in the field again automatically.
Delete individual
characters
In Edit mode you can delete the character positioned immediately to the left of
the cursor using the Backspace key.
Pocket calculator
functions Addition
and Subtraction
Depending on how fields have been configured, they feature a so-called pocket
calculator function which allows you to add or subtract values in relation to the
field content.
Open the field for Edit mode by pressing the Edit key.
Enter +,-,*,/.
Enter your second operator (value).
Terminate your input by pressing the Input key.
The result of the calculation is then displayed in the field.

5-107
5.5
Description
Syntax
08.01
mmc0_con.cfg: Emulation of variables

By making special entries in file mmc100pj\Bin_sim\mmc0_con.cfg you can
selectively preset NC variables and HMI Embedded notebook entries to values
for PC simulation mode.
0 d_typ 'sy_id Ar_Unit Cl Line B_typ NoLines' "VALUE"

[# COMMENT]
Note
Hexadecimal numbers must not be represented beginning with 0x and ending
with H.
e.g. 130 (decimal) --> 82
Parameters
d_typ
not: 0x82 or 82H
Data type (hexadecimal)

3
CHAR
4
UNSIGNED
6
DWORD
7
LONG
8
FLOAT
0F (Hex)DOUBLE
13 (Hex)STRING
(see mmc100pj\Public\Portab.h)
sy_id
Syntax identification (hexadecimal)

82 (Hex)
NUMERIK
82 (Hex)
SIMODRIVE
10 (Hex)
PLC
14 (Hex)
HMI Embedded
(see mmc100pj\Public\Varid_li.h)
Ar_Unit
NUMERIK (area and unit (one byte) decimal):

01
NCK
33 ... 63
Mode group 1 to mode group 3
65 ... 95
Channel 1 to channel 31
97 ... 127
Axis 1 to axis 31
129 ... 159
TOA1 to TOA31
161 ... 191
FDD1 to FDD31
193 ... 223
MSD1 to MSD31
Cl
Column (decimal)
(see mmc100pj\Public\Column_id.h)
Line
5-108
Line (decimal)

08.01
B_typ
Block type (decimal)

(s. mmc100pj\Public\B_type.h)
Example
NoLines
No. of lines (decimal)
value
Value depending on data type
Comment
Any comment up to end of line
#Separator Format SyId Area Col Row BlockTyp NumCol Value

0 4 '130 65 1 1 16 1' "4"#P_C_Y_numGeoAxes
0 4 '130 65 2 1 16 1' "1"# " _numAuxAxes
0 4 '130 65 3 1 16 1' "4"# " _numMachAxes
0 4 '130 65 4 1 16 1' "4"# " _numSpindles
0 4 '130 33 3 1 127 1' "1"#B_S_opMode
For further examples, please see file mmc100pj\Bin_sim\mmc0_con.cfg
For further information about Cl, Line, B_Typ, NoLines, please see:
References:
/LIS/,
SINUMERIK 840D, Description of Functions

Lists

5-109
5-110
08.01

08.01
Appendix
Appendix
References
/BU/
/ST7/
/Z/
SINUMERIK 840D/840Di/810D/802S, C, D
Ordering Information
Catalog NC 60
Order no.: E86060-K4460-A101-A8-7600 (English)
SIMATIC
SIMATIC S7 Programmable Logic Controllers
Catalog ST 70
Order no.: E86060-K4670-A111-A3
SINUMERIK, SIROTEC, SIMODRIVE
Accessories and Equipment for Special-Purpose Machines
Catalog NC Z
Order no.: E86060-K4490-A001-A7-7600 (English)
Electronic Documentation
/CD8/
The SINUMERIK System

DOC ON CD
(with all SINUMERIK 840D/840Di/810D and
SIMODRIVE publications)
Order no.: 6FC5 298-6CA00-0BG2

(01.02 Edition)
A-111
Appendix
08.01
User Documentation
/AUK/
/AUP/
/BA/
/BAD/
BEM/
/BAE/
/BAH/
/BAK/
/BAM/
/BAS/
A-112
SINUMERIK 840D/810D
AutoTurn Operation, Short Guide
Order no.: 6FC5 298-4AA30-0BP3
SINUMERIK 840D/810D
AutoTurn Graphic Programming System
Operator's Guide
Programming / Setup
(09.01 Edition)
(09.01 Edition)
SINUMERIK 840D/810D
MMC Operator's Guide
(10.00 Edition)
Operator's Guide: HMI Advanced
Order no.: 6FC5 298-6AF00-0BP1
(09.01 Edition)
Operator's Guide: HMI Embedded
Order no.: 6FC5 298-6AC00-0BP1
(09.01 Edition)
SINUMERIK 840D/810D
Unit Operator Panel Operator's Guide
(04.96 Edition)
SINUMERIK 840D/810D
Operator's Guide HAT 6 (new HPU)
Order no.: 6FC5 298-0AD60-0BP2
(09.01 Edition)
SINUMERIK 840D/810D
Operation, Short Guide
(02.01 Edition)
SINUMERIK 810D/840D
ManualTurn Operator's Guide
(10.01 Edition)
SINUMERIK 840D/810D
ShopMill Operator's Guide
(10.01 Edition)

08.01
/BAT/
/BAP/
/BNM/
/DA/
/KAM/
/KAS/
/PG/
/PGA/
/PGK/
/PGM
/PGT/
Appendix
SINUMERIK 840D/810D
ShopTurn Operator's Guide
(03.01 Edition)
Handheld Programming Unit Operator's Guide
(04.00 Edition)
SINUMERIK 840D840Di//810D
Measuring Cycles User's Guide
(10.00 Edition)
Diagnostics Guide
(09.01 Edition)
SINUMERIK 840D/810D
ManualTurn Short Guide
(11.98 Edition)
SINUMERIK 840D/810D
ShopMill Short Guide
(01.98 Edition)
Fundamentals Programming Guide
Order no.: 6FC5 298-6AB00-0BP1
(09.01 Edition)
Advanced Programming Guide
(09.01 Edition)
Programming, Short Guide
(02.01 Edition)
ISO Milling Programming Guide
(10.01 Edition)
ISO Turning Programming Guide
(10.01 Edition)

A-113
Appendix
/PGZ/
/PI/
/SYI/
08.01
Cycles Programming Guide
(09.01 Edition)
PCIN 4.4
Software for Data Transfer to/from the MMC Module
Order no.: 6FX2 060-4AA00-4XB0 (Ger., Eng., Fr.)
Order from: WK Frth
SINUMERIK 840Di
System Overview
Order no.: 6FC5 298-6AE40-0BP0
(02.01 Edition)
a) Lists
/LIS/
SIMODRIVE 611D
Lists
(09.01 Edition)
b) Hardware
/BH/
/BHA/
/EMV/
A-114
Operator Components Manual (HW)
SIMODRIVE Sensor
Absolute Encoder with Profibus DP
User's Guide (HW)
Order no.: 6SN1 197-0AB10-0YP1
SINUMERIK, SIROTEC, SIMODRIVE
EMC Installation Guideline
Planning Guide (HW)
(09.01 Edition)
(02.99 Edition)
(06.99 Edition)

08.01
/PHC/
/PHD/
/PHF/
/PMH/
Appendix
SINUMERIK 810D
Configuration Manual (HW)
(12.01 Edition)
SINUMERIK 840D
NCU 561.2-573.2 Configuration Manual (HW)
(09.01 Edition)
SINUMERIK FM NC
NCU 570 Configuration Manual (HW)
(04.96 Edition)
SIMODRIVE Sensor
Measuring System for Main Spindle Drives
Configuration/Installation Guide, SIMAG-H (HW)
Order no.: 6SN1197-0AB30-0BP0
(05.99 Edition)
c) Software
/FB1
Description of Functions, Basic Machine (Part 1)
(the various sections are listed below)
A2
A3
B1
B2
D1
D2
F1
G2
H2
K1
K2
K4
N2
P1
P3
R1
S1
V1
W1
/FB2/
(09.01 Edition)
Various Interface Signals

Axis Monitoring, Protection Zones
Continuous-Path Mode, Exact Stop and Look Ahead
Acceleration
Diagnostic Tools
Interactive Programming
Travel to Fixed Stop
Velocities, Setpoint/Actual Value System, Closed-Loop Control
Auxiliary Function Output to the PLC
Mode Group, Channel, Program Operation
Axes, Coordinate System, Frames,
Actual-Value System for Workpiece, Zero Offset External
Communication
EMERGENCY STOP
Transverse Axes
Basic PLC Program
Reference Point Approach
Spindles
Feedrates
Tool Offset
SINUMERIK 840D/840Di/810D(CCU2)
Description of Functions, Extended Functions (Part 2)
including FM NC: Turning, Stepper Motor
(the varius sections are listed below)
A4
Digital and Analog NCK I/Os
B3
B4
F3
H1
Several Operator Panels and NCUs

Operation via PG/PC
Remote Diagnosis
Jog with/without Handwheel

(09.01 Edition)
A-115
Appendix
08.01
K3
K5
L1
M1
M5
N3
N4
P2
P5
R2
S3
S5
S6
S7
T1
W3
W4
/FB3/
Compensations
Mode Groups, Channels, Axis Replacement
FM NC Local Bus
Kinematic Transformation
Measurement
Software Cams, Position Switching Signals
Punching and Nibbling
Positioning Axes
Oscillation
Rotary Axes
Synchronous Spindles
Synchronized Actions (up to and including SW 3 / then /FBSY/)
Stepper Motor Control
Memory Configuration
Indexing Axes
Tool Change
Grinding
SINUMERIK 840D/840Di/810D(CCU2)
Description of Functions, Special Functions (Part 3)
F2
G1
G3
K6
M3
S8
T3
TE1
TE2
TE3
TE4
TE5
TE6
TE7
TE8
V2
W5
/FBA/
3 to 5-Axis Transformation
Gantry Axes
Cycle Times
Contour Tunnel Monitoring
Coupled Motion and Master/Slave Couplings
Constant Workpiece Speed for Centerless Grinding
Tangential Control
Clearance Control
Analog Axes
Speed / Torque Coupling Master-Slave
Transformation Package Handling
Setpoint Exchange
MCS Coupling
Retrace Support
Cycle-Independent Path-Synchronous Switching Signal Output
Preprocessing
3D Tool Radius Compensation
SIMODRIVE 611D/SINUMERIK 840D/810D

Description of Functions, Drive Functions
Order no.: 6SN1 197-0AA80-0BP7
DB1
DD1
DD2
DE1
DF1
DG1
DM1
DS1
D1
A-116
(09.01 Edition)
(09.01 Edition)
Operational Messages/Alarm Reactions

Diagnostic Functions
Speed Control Loop
Extended Drive Functions
Enables
Encoder Parameterization
Calculating Motor / Power Section Parameters and Controller Data
Current Control Loop
Monitoring Functions/Limitations

08.01
/FBAN/
/FBD/
Appendix
SINUMERIK 840D/SIMODRIVE 611 DIGITAL

Description of Functions ANA MODULE
Order no.: 6SN1 197-0AB80-0BP0
(02.00 Edition)
SINUMERIK 840D
Description of Functions Digitizing
(07.99 Edition)
DI1
DI2
DI3
DI4
/FBDN/
/FBFA/
/FBFE/
CAM Integration DNC NT-2000

System for NC Data Management and Data Distribution
ISO Dialects for SINUMERIK
SINUMERIK 840D/810D
Description of Functions Remote Diagnosis
Order no.: 6FC5 297-0AF00-0BP1
FE1
FE2
/FBHLA/
/FBMA/
/FBO/
Installation and Startup

Scanning by Tactile Sensor (scancad scan)
Scanning by Laser (scancad laser)
Milling Program Generation (scancad mill)
(05.00 Edition)
(09.01 Edition)
(09.01 Edition)
Remote Diagnosis
Alarm-Driven Notification by E-mail: @Event
SINUMERIK 840D/SIMODRIVE 611 digital

Description of Functions HLA Module
(04.00 Edition)
SINUMERIK 840D/810D
Description of Functions ManualTurn
(10.01 Edition)
SINUMERIK 840D/810D
OP 030 Operator Interface Configuration
BA
EU
PS
PSE
IK
(09.01 Edition)
Operator's Guide
Development Environment (Configuring Package)
Online only: Configuring Syntax (Configuring Package)
Introduction to Configuring the Operator Interface
Screen Kit: Software Update and Configuration

A-117
Appendix
/FBP/
/FBR/
08.01
SINUMERIK 840D
Description of Functions C PLC Programming
(03.96 Edition)
SINUMERIK 840D/810D
Description of Functions SINCOM Computer Link
(02.00 Edition)
NFL
NPL
/FBSI/
/FBSP/
/FBST/
/FBSY/
/FBT/
/FBTD/
/FBU/
/FBW/
A-118
Interface to Host Computer

Interface to PLC/NCK
SINUMERIK 840D/SIMODRIVE
Description of Functions SINUMERIK Safety Integrated
(03.01 Edition)
SINUMERIK 840D/810D
Description of Functions ShopMill
(10.01 Edition)
SIMATIC
FM STEPDRIVE/SIMOSTEP
Order no.: 6SN1 197-0AA70-0YP3
SINUMERIK 840D/810D
Description of Functions Synchronized Actions
for Wood, Glass, Ceramics, Presses
SINUMERIK 840D/810D
Description of Functions ShopTurn
SINUMERIK 840D/810D
SINTDI Tool Data Information System with Online Help
SIMODRIVE 611 universal
Closed-Loop Control Components for Speed Control
and Positioning
SINUMERIK 840D/810D
Description of Functions Tool Management
(11.98 Edition)
(09.01 Edition)
(03.01 Edition)
(03.01 Edition)
(05.00 Edition)
(10.01 Edition)

08.01
/HBI/
/KBU/
/PJE/
/PJFE/
/PJLM/
Appendix
SINUMERIK 840Di
Manual
SIMODRIVE 611 universal

Short Guide
Closed-Loop Control Components for Speed Control
(07.01 Edition)
(05.00 Edition)
SINUMERIK 840D/810D
(08.01 Edition)
Description of Functions: Software Update, Configuration,
Installation
Order no.: 6FC5 297-6EA10-0BP0
(The PS Configuring Syntax publication is included with the software
and is available as a pdf)
SIMODRIVE
Planning Guide Integrated Synchronous Motors 1FE1
Three-Phase AC Motors for Main Spindle Drives
Order no.: 6SN1 197-0AC00-0BP1
SIMODRIVE
Planning Guide Linear Motors
(on request)
ALL General Information about Linear Motors
(08.01 Edition)
(06.01 Edition)
1FN1 Three-Phase AC Linear Motor 1FN1

1FN3 Three-Phase AC Linear Motor 1FN3
CON Cables & Connections
/PJM/
/PJU/
/POS1/
/POS2/
SIMODRIVE
Planning Guide Motors
Three-Phase AC Motors for Feed and
Main Spindle Drives
(09.00 Edition)
SIMODRIVE 611
SIMODRIVE POSMO A
User's Guide
Distributed Positioning Motor on PROFIBUS DP,
SIMODRIVE POSMO A
Installation Guide (enclosed with each POSMO A)
Order no.: 462 008 0815 00

(04.01 Edition)
(12.98 Edition)
A-119
Appendix
/POS3/
/S7H/
/S7HT/
/S7HR/
/S7S/
/S7L/
/S7M/
/SHM/
/SP/
A-120
08.01
SIMODRIVE POSMO SI/CD/CA

Distributed Servo Drive Technology, User's Guide
SIMATIC S7-30
Manual: Setup, CPU Data (hardware)
Reference Manual: Module Data
Order no.: 6ES7 398-8AA03-8AA0
SIMATIC S7-300
STEP 7 Manual, Fundamentals, V. 3.1
Order no.: 6ES7 810-4CA02-8AA0
SIMATIC S7-300
Manual
STEP 7, Reference Manuals, V. 3.1
Order no.: 6ES7 810-4CA02-8AR0
(01.01 Edition)
(10.98 edition)
(03.97 Edition)
(03.97 Edition)
SIMATIC S7-300
FM 353 Positioning Module for Stepper Drive
Order together with the Configuring Package
(04.97 Edition)
SIMATIC S7-300
FM 354 Positioning Module for Servo Drives
(04.97 Edition)
SIMATIC S7-300
FM 357 Multi-Axis Module for Servo or Stepper Drives
(10.99 Edition)
SIMODRIVE 611
Manual
Single-Axis Positioning Control for MCU 172A
Order no.: 6SN 1197-4MA00-0BP0
(01.98 Edition)
SIMODRIVE 611-A/611-D,
SimoPro 3.1
Program for Configuring Machine Tool Drives
Order no.: 6SC6 111-6PC00-0AA,
Order from: WK Frth

08.01
d) Installation
and Start-up
/IAA/
/IAC/
/IAD/
/IAF/
/IAM/
Appendix
SIMODRIVE 611A
Installation & Start-up Guide
(incl. description of SIMODRIVE 611D
startup software)
Order no.: 6SN 1197-0AA60-0BP6
SINUMERIK 810D
startup software)
SINUMERIK 840D/SIMODRIVE 611D
startup software)
(10.00 Edition)
(12.01 Edition)
(09.01 Edition)
SINUMERIK FM-NC
(07.00 Edition)
HMI/MMC Installation & Start-up Guide
(11.01 Edition)
AE1
BE1
HE1
IM2
IM4
TX1
Updates/Options
User Interface Options
Online Help
HMI Embedded Installation and Startup
HMI Advanced Installation and Startup
Generating Foreign Language Texts

A-121
Appendix
A-122
08.01

08.01
Index
Index
A
Addition 5-107
Application library 3-61
Application list directory 3-61
Modifying tool entries 2-18

MPI mode 5-104
MS-Visual C++ Workbench 2-17
Multiplication 5-107
mwl_app.h 2-32
N
Character size 2-33

Compiler options 4-94, 4-98
Creating tool entries 2-18
Navigation mode 5-107

NCK variables 1-12
Network connection: Installation 3-88
Notebook entries 3-62
Notebook entry 5-108
Number range 2-32
Delete 5-107
Division 5-107
Documentation 1-10
Online 5-104
On-Line-Help 2-20
Operation 1-12
Operator's Guide 1-10
Overwrite 5-107
E
Edit mode 5-107
Emulation 5-108
Event 2-33
Event codes 3-62
Gray shades 2-33
parallel link with: FAT16 file structure 3-85;

FAT32 file structure 3-87
PC MPI mode 5-104
PC simulation mode 5-102, 5-108
Pocket calculator functions 5-107
Insert 5-107
Installation 2-16
Installation on HMI Embedded 2-15
Installation via parallel link with FAT16 file
structure 3-85
Installation via parallel link with FAT32 file
structure 3-87
Interface to NCK 1-12
SCK 3-47
Simulation mode 5-103, 5-108
size.h 2-33
Softkey size 2-33
Subtraction 5-107
key.h 2-33
Test mode on a PC 5-102

Text source files 3-54, 3-55
To open HMI-Embedded 5-103, 5-104
Transmission via V24 2-15
Library 3-61
Linker options 4-94, 4-98
List element identities 3-62
List identifiers 2-32, 3-62
List identities 3-62
logiccol.h 2-33
Undo 5-107
V
Variables 5-108
vgadef.h 2-33

I-123
Index
08.01
W
Window size 2-33
I-124
Siemens AG 2001 All Rights Reserved

To
SIEMENS AG
Suggestions
Corrections
For Publication/Manual:
A&D MC BMS
P.O. Box 3180
SINUMERIK 840D/810D
D-91050 Erlangen
(Tel. +49 (0)180 / 5050 222 [Hotline]
Fax: +49 (0)9131 / 98 2176
e-mail: motioncontrol@erlf.siemens.de)
From
Name
Order No.:
Edition:
Company/Dept.
Address
_________________________________________________________________________________________________________________
_________________________________________________________________________________________________________________
Telephone:
Fax:
_________________________________________________________________________________________________________________
Suggestions and/or corrections
6FC5 297-6EA10-0BP0
08.01
Should you come across any printing

errors when reading this publication,
please notify us on this sheet.
Suggestions for improvement are also
welcome.
Overview of SINUMERIK 840D/840Di/810D Documentation (08.01)

SINUMERIK
SINUMERIK
840D/810D
840D/840Di/
810D
Brochure
Catalog
Ordering Info
NC 60 *)
User Documentation
SINUMERIK
SIROTEC
SIMODRIVE
Accessories
Catalog
Accessories NC-Z
SINUMERIK
840D/840Di/
810D
840D/810D
SINUMERIK
SINUMERIK
SINUMERIK
840D/810D/
FM-NC
840D/810D
840D/840Di/
810D
840D/840Di/
810D
AutoTurn
-- Short Guide
-- Programming (1)
-- Setup (2)
Operators Guide
-- HT 6 (+ 840Di)
-- HPU
-- Unit Operator
Panel
Diagnostics
Guide *)
Operators Guide *)
-- Short Guide
-- MMC 103
-- HMI Embedded
-- HMI Advanced
User Documentation
SINUMERIK
SINUMERIK
SINUMERIK
840Di
System Overview
Operators Guide
Program. Guide
-- ManualTurn
-- Short Guide
-- Fundamentals *) -- Short Guide ManualTurn
-- ShopMill
-- Advanced *)
-- Short Guide ShopMill
-- Cycles
-- Measuring Cycles
-- ISO Turning/Milling
SINUMERIK
SINUMERIK
SINUMERIK
840D/810D
840D/840Di/
810D
840D/810D
Description of
Functions
-- ManualTurn
-- ShopMill
Description of
Functions
Synchronized
Actions
Descr. of Functions
-- Computer Link
-- Tool Data
Information
System
SINUMERIK
Configuring
(HW) *)
-- FM-NC
-- 810D
-- 840D
SINUMERIK
SINUMERIK
SIMODRIVE
SINUMERIK
SINUMERIK
SINUMERIK
SINUMERIK
SINUMERIK
840D/840Di/
810D
611D
840D/810D
840D/840Di/
810D
840D/810D
840D/810D
840D/840Di/
810D
840D/810D
Operator
Components
(HW) *)
Description of
Description of
Functions
Functions
Drive Functions *) -- Basic Machine *)
-- Extended Functions
-- Special Functions
Configuring Kit
MMC 100/101
-- Configuring
Syntax
-- Development Kit
Screen Kit
MMC 100/101
SW Update and
Configuration
Description of
Functions
Tool
Management
Description of
Functions
Operator Interface
OP 030
SINUMERIK
SIMODRIVE
SINUMERIK
SIMODRIVE
SINUMERIK
840D
Description of
Functions
SINUMERIK
Safety Integrated
Description of
Functions
Digitizing
Installation &
Start-up Guide *)
-- FM-NC
-- 810D
-- 840D/611D
-- MMC/HMI
Electronic Documentation
SINUMERIK
SIMODRIVE
840D/840Di/
810D/
611, Motors
DOC ON CD *)
The SINUMERIK System
*) These documents are a minimum requirement for the control
SINUMERIK
SIMODRIVE
840D/840Di/
810D
611D
Lists *)
SINUMERIK
SIMODRIVE
840D
611D
Description of
Functions
Linear Motor
SINUMERIK
SIMODRIVE
840D
611D
SINUMERIK
SIMODRIVE
SIROTEC
EMC
Description of
Guidelines
Functions
- Hydraulics
Module
- Analog Module
SINUMERIK
SINUMERIK
840D/840Di/
810D
Descr. of Functions
ISO Dialects for
SINUMERIK
SINUMERIK
840Di
Descr. of Functions
CAM Integration
DNC NT-2000
SINUMERIK
840D/810D
Descr. of Functions
Manual
(HW + Installation Remote Diagnosis
and Start-up)

PJE 0801 en

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

PJE 0801 en

Diunggah oleh

Hak Cipta:

Format Tersedia

SINUMERIK 840D/810D

HMI Embedded Configuring

This manual forms part of the documentation available on CD-ROM (DOCONCD)

SIMATIC SIMATIC HMI, SIMATIC NET, SIROTEC, SINUMERIK and SIMODRIVE

Further information is available on the Internet under:

Other functions not described in this documentation might be executable in the

This publication was produced with WinWord V 8.0

Siemens AG 1995 - 2001. All rights reserved.

Order No. 6FC5 297-6EA10-0BP0

SINUMERIK documentation is organized on three levels:

This documentation is intended for manufacturers of machine tools with

Available from 09.2001 will be

Available from 12.2001 will be

The lists serve as a reference work for installation and startup.

To improve orientation, we have provided you with a list of contents, as well as

The following notes appearing in the documentation have special significance:

Siemens AG 2001. All rights reserved

This symbol appears in the documentation to indicate that this information is

Siemens AG 2001. All rights reserved

IBM is the registered trademark of the International Business Corporation.

Siemens AG 2001. All rights reserved

Structure of documentation .............................................................................1-10

Software update, fundamentals ......................................................................2-14

Hardware and software requirements for the HMI Embedded software

Setup: Setting up the configuring environment for HMI Embedded ................2-16

Where can I find what? ...................................................................................2-25

Application manager - creating an application ................................................3-39

Configuring a project .......................................................................................3-47

Text converter - text principle..........................................................................3-51

Compiling the application configuration ..........................................................3-59

Linking the application areas...........................................................................3-69

Testing the configuration on a PC...................................................................3-71

Generating floppy disks...................................................................................3-71

Installing HMI Embedded on a PCU20 ...........................................................3-71

Installing HMI Embedded Win 32 on a PCU50 ...............................................3-84

Working with Microsoft Visual C and HMI Embedded .......................................................4-93

Using MS Visual Studio 6.0.............................................................................4-94

Using the MSVC Workbench ..........................................................................4-98

Known restrictions and incompatibilities .......................................................4-100

Operating HMI Embedded....................................................................................................5-101

HMI Embedded - test mode on a PC ............................................................5-102

PC simulation mode ......................................................................................5-103

Key assignments in PC mode .......................................................................5-105

mmc0_con.cfg: Emulation of variables .........................................................5-108

Siemens AG 2001. All rights reserved

Structure of documentation .............................................................................1-10

Siemens AG 2001. All rights reserved

Siemens AG 2001. All rights reserved

This documentation is intended for use by machine tool manufacturers who

test the operator interface on a PC,

create a machine-manufacturer-specific system master disk or application

HMI Embedded can be configured to enable you to optimally adapt the

The software update is described in Section 2.

Siemens AG 2001. All rights reserved

The interface to the NCK control is described in

SINUMERIK 840D, 840Di/ 810D/

A description of how to operate HMI Embedded can be found in

A description of how to operate the HT6 can be found in

Siemens AG 2001. All rights reserved

Software update, fundamentals ......................................................................2-14

Hardware and software requirements for the HMI Embedded software

Setup: Setting up the configuring environment for HMI Embedded ................2-16

Where can I find what? ...................................................................................2-25