sinumerik 840d/810d hmi embedded configuring package · sinumerik 840d/810d hmi embedded...

Description of Functions 08.2001 Edition

SINUMERIK 840D/810DHMI Embedded ConfiguringPackage

Manufacturer/Service Documentation

SINUMERIK 840D/810DHMI Embedded ConfiguringPackage

Description of Functions

Valid for

Control Software VersionSINUMERIK 840D 6SINUMERIK 840DE (export version) 6SINUMERIK 840D powerline 6SINUMERIK 840DE powerline (export version) 6SINUMERIK 810D 3SINUMERIK 810DE (export version) 3SINUMERIK 810D powerline 6SINUMERIK 810DE powerline (export version) 6

08.2001 Edition

Introduction 1

Installation 2

Configuring 3

Working withMicrosoft Visual C andHMI Embedded

4

Operating HMIEmbedded

5

Appendix

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 newedition coding in the header on that page.

Edition Order No. Comment09.95 6FC5 297-2AC40-0BP0 A09.96 6FC5 297-3EA00-0BP2 C08.01 6FC5 297-6EA10-0BP0 C

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

Edition Order No. Comment09.01 6FC5298-6CA00-0BG1 C

Trademarks

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

are registered trademarks of Siemens AG. Other names in this publication might betrademarks whose use by a third party for his own purposes may violate the rights of theregistered holder.

Further information is available on the Internet under:http://www.ad.siemens.de/sinumerik

This publication was produced with WinWord V 8.0and Designer V 7.0The reproduction, transmission or use of this document or its contents is notpermitted without express written authority. Offenders will be liable for damages. Allrights, including rights created by patent grant or registration of a utility model ordesign, are reserved.

© Siemens AG 1995 - 2001. All rights reserved.

Other functions not described in this documentation might be executable in thecontrol. This does not, however, represent an obligation to supply such functionswith a new control or when servicing.

We have checked that the contents of this document correspond to the hardwareand software described. Nonetheless, differences might exist and therefore wecannot guarantee that they are completely identical. The information contained inthis document is, however, reviewed regularly and any necessary changes will beincluded in the next edition. We welcome suggestions for improvement.

Subject to change without prior notice.

Order No. 6FC5 297-6EA10-0BP0Printed in the Federal Republic of Germany

Siemens-Aktiengesellschaft.

08.01 Contents

© Siemens AG 2001. All rights reservedSINUMERIK 840D/810D HMI Embedded Configuring Package (PJE) � 08.01 Edition v

Preface

SINUMERIK documentation is organized on three levels:

General Documentation

User Documentation


This documentation is intended for manufacturers of machine tools withSINUMERIK 840D/810D .

Available from 09.2001 will be

SINUMERIK 840D powerline and

SINUMERIK 840DE powerline

with improved performance. A list of the available powerline modules can befound in the Hardware Reference Manual /PHD/ in Section 1.1

Available from 12.2001 will be

SINUMERIK 810D powerline and

SINUMERIK 810DE powerline

with improved performance. A list of the available powerline modules can befound in the Hardware Reference Manual /PHC/ in Section 1.1

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 asthe appendices:

1. List of references

2. Index

! Important

This manual is valid for: Software Release 6.

The following notes appearing in the documentation have special significance:

Structure ofdocumentation

Target readership

SINUMERIK 840Dpowerline

SINUMERIK 810Dpowerline

Objective

Search aids

Notes

Contents 08.01

© Siemens AG 2001. All rights reservedvi SINUMERIK 840D/810D HMI Embedded Configuring Package (PJE) � 08.01 Edition

Note

This symbol appears in the documentation to indicate that further informationis available.

! Important

This symbol appears in the documentation to indicate that this information isparticularly important.

The following warning notices used in the brochure are graded in significance:

! Danger

This warning notice means that death, severe physical injury or considerablematerial damage will occur if the relevant safety precautions are not taken.

! Warning

This warning notice means that death, severe physical injury or considerablematerial damage may occur if the relevant safety precautions are not taken.

! Caution

This warning notice (with a warning triangle) means that slight physical injuryor material damage may occur if the relevant safety precautions are nottaken.

Caution

This warning notice (without a warning triangle) means that material damagemay occur if the relevant safety precautions are not taken.

Important

This warning notice means that an unwelcome event or unwanted conditionmay occur if the relevant notices are not complied with.

Warning notices

08.01 Contents

© Siemens AG 2001. All rights reservedSINUMERIK 840D/810D HMI Embedded Configuring Package (PJE) � 08.01 Edition vii

Technical comments

IBM® is the registered trademark of the International Business Corporation.MS-DOS® and WINDOWS� are registered trademarks of the MicrosoftCorporation.

Trademarks

Contents 08.01

© Siemens AG 2001. All rights reservedviii SINUMERIK 840D/810D HMI Embedded Configuring Package (PJE) � 08.01 Edition

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 softwarepackage "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 ....................................................................................................................... I-123

© Siemens AG 2001. All rights reservedSINUMERIK 840D/810D HMI Embedded Configuring Package (PJE) � 08.01 Edition 1-9

Introduction

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

1

1 Introduction 08.01

© Siemens AG 2001. All rights reserved1-10 SINUMERIK 840D/810D HMI Embedded Configuring Package (PJE) � 08.01 Edition

1.1 Structure of documentation

The documents describing the functions for configuring the operator interfacefor the OP010/ OP010C/ OP010S/ OP012/ OP015 operator panels and theHT6 handheld terminal using the HMI Embedded software are organized in thefollowing structure:

SINUMERIK 840D/810DHMI Embedded Operator's GuideOperator's guide for standard scope of operating functions

SINUMERIK 840D/840Di/810D Operator's GuideHT6 Handheld TerminalOperator's guide for standard scope of operating functions of HT6

SINUMERIK 840D/810DHMI Embedded Configuring PackageDescription of Functions: Software Update, Configuration, Installation(the publication Configuring Syntax (PS) is supplied with the software as a pdffile)

SINUMERIK 840D/840Di/810DHMI/MMC Installation & Start-Up Guide

SINUMERIK 840D/810DDescription of Functions: Configuring the OP 030 Operator InterfaceSection PS: Online only: Configuring Syntax (Configuring Package)

Another option for designing the operator interface can be found in:

SINUMERIK 840/840Di/810DHMI/MMC Installation & Start-Up GuideSect. BE1: Expand the Operator Interface

08.01 1 Introduction


This documentation is intended for use by machine tool manufacturers whowish to design their own user interface for PCU20/HT6 or PCU50 hardwareusing the HMI Embedded basic software as a base.

Note

The term "HMI Embedded" as used in this document always refers to thesoftware package irrespective of the target hardware.

The software described here and the associated description of functions willenable 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 itinto operation and

� create a machine-manufacturer-specific system master disk or applicationmaster disk or text disk of the modified system for his own servicingpurposes.

The "HMI Embedded Configuring Package" used must match the relevantSINUMERIK 840D/840Di/810D version.

HMI Embedded can be configured to enable you to optimally adapt theoperator interface to the individual features of the relevant machine.

The basic system of the HMI Embedded software can be combined with avariety 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 EmbeddedScreen Kit". You can call this application in the HMI Embedded main menu(operating area key).

The structure of the configuring language is described in the online help file"Configuring Syntax" which is included with the HMI Embedded configuringpackage.

The software update is described in Section 2.

Target readership

Objective

Dependencies

Fundamentals

Configuring language

Software update

1 Introduction 08.01


The interface to the NCK control is described in

References: /LIS/ SINUMERIK 840D, 840Di/ 810D/SIMODRIVE 611DDescription of Functions Lists

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

References: /BEM/ SINUMERIK 840D/810DHMI Embedded Operator's Guide

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

References: /BAH/ SINUMERIK 840D/840Di/810DOperator's Guide for HT6 Handheld Terminal

■

Interface to NCK

Operation


Installation

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

2.2 Hardware and software requirements for the HMI Embedded softwarepackage "Screen Kit".......................................................................................2-15

2.3 Setup: Setting up the configuring environment for HMI Embedded ................2-162.3.1 Preparations for installation.............................................................................2-162.3.2 Setup routine ...................................................................................................2-162.3.3 Initialization settings for MSVC Workbench / MS Visual Studio......................2-172.3.3.1 Creating and modifying tool entries in the development

environment ....................................................................................................2-182.3.3.2 Linking in the application manager..................................................................2-192.3.3.3 Linking in the general linkage process ............................................................2-192.3.3.4 Linking in the software configuration kit (SCK) ...............................................2-192.3.3.5 Linking in the text converter ............................................................................2-202.3.3.6 Linking in the online help.................................................................................2-202.3.3.7 Other extensions to the development environment.........................................2-212.3.4 De-installing the screen kit ..............................................................................2-222.3.5 Typical Setup errors ........................................................................................2-23

2.4 Where can I find what? ...................................................................................2-252.4.1 List identities for application area - mwl_app.h ...............................................2-322.4.2 Colors and gray shades - logiccol.h, vgadef.h ................................................2-332.4.3 Layout - size definitions for characters, windows, softkeys - size.h ................2-332.4.4 Keyboard events - key.h..................................................................................2-33

2

2 Installation 08.01


2.1 Software update, fundamentals

The setup and update process comprises four main steps:

Transfer of software components from CD or diskette(s) to the hard disk ofyour PC, setup and configuring of the working environment.

Creation of a special configuration comprising applications (Machine,Parameters, Programming, Services, Diagnosis, Start-Up, System, MCU (notHT6), Higraph Diagnosis (not HT6), OEM applications) to suit yourrequirements.

Use the SCK (Software Configuration Kit) for this purpose.

Creation of one or more customer operator interfaces using the configuringmacros in development environments MSVC Workbench or MS VisualStudio 6.0.

Transfer of system software incl. applications and selected languages to theHMI Embedded hardware.

1. Setup

2. Configuration

3. Configuring

4. Installation

08.01 2 Installation


2.2 Hardware and software requirements forthe 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, PCsimulation, HMI Embedded system) on the hard disk: Approx. 50 MB.

� Windows 95 or Windows NT. (Please comply with the system requirementsspecified 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 perdefault; this has no critical memory requirements.



2.3 Setup: Setting up the configuring environment for HMIEmbedded

2.3.1 Preparations for installation

The setup operation creates a directory TargetDrive:\name on a target drive ofyour choice (C:, D:, or E:).

The default directory name is mmc100pj.

The HMI Embedded configuring package is set up in this directory.

On systems with Windows NT the configuring directories must be stored in theroot directory!

You must therefore set up the target directory before you start setup andsubstitute this on a drive letter of your choice.

You need then only specify the drive letter for "system path" and "OEMapplication path" during setup !

The use of a batch file, e.g. with the following contents, is recommended forthis purpose:

SUBST V: /D

SUBST V: TARGETDRIVE:\name

which you must execute every time before you use the HMI Embeddedconfiguring package.

Ignore the warning output by the setup program when you install it in the rootdirectory.

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

� 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 targetdrives, etc.).

Description

Windows NT only

Description



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 DOSenvironment 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 variableexplicitly, for example, in your AUTOEXEC.BAT, the correspondingextension must be made there.

� If necessary, correct your LASTDRIVE entry in CONFIG.SYS to at leastdrive "L". (LASTDRIVE=Z)

� Reboot your computer to activate the entries in the CONFIG.SYS andAUTOEXEC.BAT files.

Note

Section 2.3.3 below is relevant only if Setup was aborted as you were enteringthe Windows and MSVC paths or the entries in the toolbars of MSVCWorkbench / 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.

� Start MS Windows and the MSVC Workbench.

� Add your DOS directory or the Windows directory to the path for"EXECUTABLE FILES PATH" in menu OPTIONS DIRECTORIES .

Only then will the Make files be correctly executed.

Description



2.3.3.1 Creating and modifying tool entries in the development environment

This subsection describes how to modify and create tool entries in the MSVCWorkbench or MS Visual Studio development environment. You can use thisprocedure to retro-install screen kit tools in your development environment(e.g. because Setup cannot be executed properly). The entries you need tomake are described in the following subsections.

The MSVC Workbench offers you the option of configuring the entries in menuOPTIONS TOOLS. You must link in the tool entries here.

� Open the dialog box for modifying tools by selecting menu optionsOPTIONS 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 "UseOutput Window" and "Close Window on exiting" do not exist on theMSVC Workbench and can be ignored.

� You can adapt the tool order in the menu to suit your requirementsusing MOVE UP and MOVE DOWN.

� Close the dialog box by selecting OK.

You can configure tool entries in MS Visual Studio by selecting menu optionsTOOLS CUSTOMIZE TOOLS tab. You must link in the tool entries here.

� Open the dialog box for modifying tools by selecting menu optionsTOOLS CUSTOMIZE TOOLS tab. Select the entry you wish tochange in the "MENU CONTENTS" window or click on the NEWsymbol 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 requirementsusing the arrow symbols.

� Close the dialog box by selecting OK.

MSVC V1.xy

MSDEV V6.0



2.3.3.2 Linking in the application manager

Note

Necessary only if Setup has not been executed correctly.

You can configure your entries in the MSVC Workbench by selecting menuoptions OPTIONS TOOLS. You must link in the application manager entrieshere.

Make the following settings:

Command Line : mmc100pj\Instutil\Appman.exeMenu Text : A&pplicationmanagerArguments : No EntryInitial 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.exeMenu Text : &Generate SL.DATArguments (MSVC) : -MSVC $projArguments (Studio) : $(WkspName)Initial Directory : mmc100pj\Instutil⌧ Use Output Window" Ask for Arguments or. Prompt for Arguments" Close Window on exiting

2.3.3.4 Linking in the software configuration kit (SCK)

Note



Command Line : mmc100pj\Sck\Sck.batMenu Text : &Installation-KitArguments : No Entry Initial Directory : mmc100pj\Sck" Use Output Window" Ask for Arguments or. Prompt for Arguments⌧ Close Window on exiting



2.3.3.5 Linking in the text converter

Note



Command Line : mmc100pj\Instutil\Txt_Make.exeMenu Text : &TextconvertingArguments (MSVC) : -app $ProjDir �oNoLenWarn �fD �bGArguments (Studio) : -app $(WkspDir) �oNoLenWarn �fD �bGInitial 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 underMS Windows (with Winhelp.exe).

These files (Pj_gr.hlp, Pj_dvkit.hlp, Btss_gr.hlp) are stored in mmc100pj\Docby Setup. You can also double click them to start them from the Windows filemanager.

The file name extension .._gr stands for German (germany). If you requireonline help in English, please enter the files with extension .._uk (unitedkingdom).

In the current SW version, the English online help must be entered manually inthe toolbar (see below).

To ensure that the MSVC Workbench or MS Visual Studio can locate fileWinhelp32.exe, the Windows path must be entered in at least one of thefollowing 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. (seebelow)

If your Windows version uses only the older Help program "Winhelp.exe", allinstances of Winhlp32.exe in the tool entries (see below) must be replaced byWinhelp.exe.



Make the following 3 settings:

Command Line : C:\windowsWinhlp32.exeMenu Text : &Configuring GuideArguments : mmc100pj\Doc\Pj_gr.hlpInitial Directory : No Entry" Use Output Window" Ask Arguments or. Prompt for Arguments" Close Window on exiting

Command Line : C:\windowsWinhlp32.exeMenu Text : Screen-&Kit HelpArguments : mmc100pj\Doc\Pj_dvkit.hlpInitial Directory : No Entry" Use Output Window" Ask Arguments or. Prompt for Arguments" Close Window on exiting

Command Line : C:\windows\Winhlp32.exeMenu Text : &OPI Variables HelpArguments : mmc100pj\Doc\Btss_gr.hlpInitial Directory : No Entry" Use Output Window" Ask Arguments or. Prompt for Arguments" Close Window on exiting

The Windows installation path can be, for example: Windows, Win95, WinNT,WinNT.400.

Note

C:\windows represents the installation path of your Windows version. Othercommon paths include C:\winnt, C:\win95, C:\win.nt. For partitioning the harddisk, refer to Section 3.10.

2.3.3.7 Other extensions to the development environment

Note


� The Setup installation routine creates environment variables "RAMDISK"and "HARDWARE_NAME" ( e.g.: "PCU20" , "HT6"), variable PATH isextended. If Setup has not been executed properly, you may need to setup 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 SETVAR_NAME = /VRT to file "c:\autoexec.bat". e.g.:SET PATH = C:\WIN95; C:\PROGRAM; ....; C:\MMC100PJ\INSTUILSET RAMDISK = C:\TMP\RAMDISKSET HT6 = 1The changes do not take effect until you next restart the system !!!

Windows 95 only



To set an environment variable under Windows NT, you must open the systemsettings dialog by selecting START SETTINGS CONTROLPANEL SYSTEM . You can set the environment variables under theEnvironment tab. Enter the variable name under Variable and the value underValue. 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 color-highlighted in the development environment. For this purpose, you mustenter the vocabulary words in a "usertype.dat" file in the same folder asthe Msdev.exe program.

Setup automatically creates a file of this type containing the configuringvocabulary words and OPI variables. To ensure that entries are not lost,no pre-existing file is overwritten. In this case, you can append thecontents of file mmc100pj\Instutil\Usertype.dat to the file with the samename in the Msdev.exe folder.

2.3.4 De-installing the screen kit

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.

� 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.

� 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

Windows NT only

Description

MSVC 1.5x only

Visual Studio only

Win 95 only



statement.- Save the file and exit the editor.

- 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.

2.3.5 Typical Setup errors

Problem:

The tool menu entries do not work.

Cause:

You are probably using a Windows NT computer, but you have not installedthe HMI Embedded configuring package under a substituted drive, or havefailed 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 / MSVisual Studio)

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)

Problem:

The online help for OPI variables is aborted with an error message. The otherhelp files are ok.

Win NT only

Description

Description

Description



Cause:

You are using Winhelp.exe. OPI variables require the 32-bit versionWinhlp32.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 Windowssystem, you will unfortunately not be able to access this help function.

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 toRESTART your computer! Check the other environment variables as well.

Problem:

The PC Simulation application displays a white or a black screen. Thesimulation 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 RESTARTyour computer! Check the other environment variables as well.

Check whether the Initial Directory is correctly positioned on the toolbar(TOOLS CUSTOMIZE TOOLS tab).

Description

Description



2.4 Where can I find what?

A brief overview of relevant directories and files:

Directory for HMIEmbedded testing

Directory for configurationfiles of individual applicationconfigurations



..\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

The OEM directory

Installation path ofconfiguring package

Application directory

Application header files

Application make files(MSVC 1.xy only)

Application source files

Text files in languagedirectories

Application project files(MSDEV 6.0 only)



ApplicationName.cfg Configuration files for application configurations

..\Public

Directory for system include files. Your application configuration cannot becorrectly compiled with the application make file ApplicationName.mak (MSVC1.xy) or ApplicationName.dsp (MSVC V6.0) until the following files have beenlinked in.

The diagram only shows the directory structure, as the Include files should notbe 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 thesystem as well. Changing defines could lead to inconsistencies betweenthe system and configuration and thus to undesirable effects. Furthermore,your changes would be overwritten without warning the next time youupdate the screen kit.If you wish to make changes (e.g. because you prefer other colors orwindow 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 yourapplication source files (*.C); in this way you can be sure that all followingsystem 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 andwindows)

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



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 Linkoperation (MSVC Workbench: TOOLS GENERATE SL.DAT) copies thesefiles from directory ..\Proj\App\ApplicationName\Lib to this directory and theninterlinks them with the other application binary files configured in theInstallation 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 inevery 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, sincethe 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 filesgenerated by the text converter which must be included by the relevantapplication during the compiler operation are copied to this directory.



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 applicationmake file until the system include files have been linked in.

Proj.h Include file for linking in all system configuringinclude files

TextFileName.hApplication text include files

..\Proj\App\ApplicationName

Directory contains all the source files relevant to the applicationApplicationName. To archive your application configuration, you need onlyback 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 applicationmanager. It contains the settings of the workingarea for this application, e.g. which projectsbelong to the application and how they interact.

This file is required only if MS Visual Studio isused.

ApplicationName_Li.dsp This file is created as standard by the applicationmanager. The project controls compilation of thesource files for the application and creates theApplicationName.lib file. It is therefore equivalentto the ApplicationName.mak make file for MSVCWorkbench.


ApplicationName.dsp This file is created as standard by the applicationmanager. The project controls the link operationof this one application. A DAT file is generatedfrom the LIB file and copied to ...\Proj\Sl where itis available for access by the Installation Kit orthe general linkage process. It is thereforeequivalent to the SI_App.mak make file forMSVC Workbench.


..\Proj\App\ApplicationName\Src

Directory contains all relevant application configuring source files (*.c) for anapplication.

app_menu.c This file is generated as standard by the



application manager to allow you initial access toyour new application.

ap_l_dir.c This file contains references to the lists that areaddressed via their list IDs. It is generatedautomatically by the application manager andinitialized with all application-specific data. Youneed not make any changes to the file forconfiguring 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. itmust contain external references to all definitionblocks and lists contained in your applicationconfiguration. These entries of lists and definitionblocks used in your application must be updatedevery time you edit or supplement your lists anddefinition 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) andsoftkey object list (SOB_APP), then file ap_l_dir.hmust 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 foryour list and definition block names. A number isassigned to each definition block and list name inthis include file; the HMI Embedded basic systemcan uniquely identify every individual list on thebasis of this number.

Note

This file must be explicitly included in everyapplication source file (*.C) with entry #include"mwl_app.h" after entry #include "proj.h" so thatthe list and definition block names can be clearlyidentified.



nb_app.h This file contains all notebook number definitionsfor your applications. The notebooks arerepresented by HMI variables with which you can,for example, perform arithmetic calculations ortemporary storage operations. The variables areirretrievably lost, however, after an interruption inthe power supply. Results of arithmetic operationsshould, for example, be stored temporarily in Rparameters.

This file must be explicitly included in everyapplication source file (*.c) with entry #include"nb_app.h" after entry #include "mwl_app.h".

Definition of your ownapplication-specificinclude files

With macro configuring you can use the CDirective "#DEFINE" , allowing you, for example, todefine screen coordinates for legibility and usethem elsewhere as a textual replacement. Definesof this type should be stored in application-specificinclude files, and be included by every applicationsource file (*.c). The same applies to PLC and NCvariable defines, i.e. they should not be inserted inthe central system include files mmc100pj\Public\*.h, but stored in application-specific includefiles. This is also important as regards updates,since any entries in system include files might belost 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 ofthe application configuring sources with MSVC 1.xy. The result of this processis file ApplicationName.lib which serves as an input for the general linkageoperation.

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 linkageoperation 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.datand copies them to directory ..\Bin_sim for the PC Simulation.



This directory is not used for MS Visual Studio, because ApplicationName.datis 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 alarmtext 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 filesare stored in them. These also include file ApplicationName.lib.

2.4.1 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.

Description



2.4.2 Colors and gray shades - logiccol.h, vgadef.h

Defines for the logical colors are stored in mmc100pj\Public\logiccol.h. Onelogical color definition always includes the colors for one color screen and oneb/w screen.

For example: #DEFINE ED_WD_CCOL ORANGE|BLACK /* Cursor color inedit window */

With color screen ORANGEWith b/w screen BLACK

The combinations are devised to achieve good legibility in both screenvariants.

If you want to use other combinations, you can set up a local color table inmmc100pj\Proj\H\.

The generic basic colors are stored in filemmc100pj\Public\vgadef.h.

2.4.3 Layout - size definitions for characters, windows,softkeys - size.h

mmc100pj\Public\size.h contains defines for the sizes of windows, softkeysand characters.

If you want to define other sizes, you can set up your own include file inmmc100pj\Proj\H\.

2.4.4 Keyboard events - key.h

mmc100pj\Public\key.h contains definitions of the keyboard events which canbe configured in the reaction routines.

■

Description

Cursor color foreditor:

Description

Description


Configuring

3.1 Overview .........................................................................................................3-38

3.2 Application manager - creating an application ................................................3-393.2.1 Exiting the application manager ......................................................................3-403.2.2 Creating a new application configuration ........................................................3-403.2.3 Editing application data ...................................................................................3-443.2.4 Saving application data ...................................................................................3-443.2.5 Copying an existing application configuration .................................................3-443.2.6 Closing application data ..................................................................................3-463.2.7 Setting text converter options..........................................................................3-463.2.8 Displaying information about the HMI Embedded application manager .........3-46

3.3 Configuring a project .......................................................................................3-473.3.1 Creating a new project ....................................................................................3-473.3.2 Description of configuration files (*.cfg) ..........................................................3-49

3.4 Text converter - text principle..........................................................................3-513.4.1 Languages - multilingual texts.........................................................................3-513.4.2 Master language..............................................................................................3-523.4.3 Text source file - TextFileName.txt .................................................................3-523.4.4 Text binary files - TextFileName.sp1, TextFileName.sp2 ...............................3-523.4.5 Text include file - TextFileName.h ..................................................................3-533.4.6 Text dependencies ..........................................................................................3-533.4.7 Basic principle of text accessing .....................................................................3-533.4.8 Syntax of configuring text source files.............................................................3-543.4.9 Syntax of the HMI Embedded alarm text source file .......................................3-553.4.10 Calling the text converter.................................................................................3-55

3.5 Compiling the application configuration ..........................................................3-593.5.1 Important files for the compile operation .........................................................3-593.5.2 MSVC project - ApplicationName.mak............................................................3-603.5.3 Visual Studio Workspace - ApplicationName.dsw,

ApplicationName.dsp, ApplicationName_li.dsp...............................................3-603.5.4 Application source files - *.c ............................................................................3-613.5.5 Application list directory - ap_l_dir.h................................................................3-613.5.6 Notebook defines - nb_app.h ..........................................................................3-623.5.7 Number ranges ...............................................................................................3-623.5.8 Starting the compile operation on the MSVC Workbench...............................3-633.5.9 Starting the compile operation in MS Visual Studio 6.0 ..................................3-643.5.10 Extensions and dependencies ........................................................................3-653.5.11 Archiving the application configuring source files ...........................................3-65

3

3 Configuring 08.01


3.5.12 Description of "Example".................................................................................3-66

3.6 Linking the application areas...........................................................................3-693.6.1 Important files for the link operation ................................................................3-703.6.2 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 Installing HMI Embedded on a PCU20 ...........................................................3-713.9.1 Installing the system software .........................................................................3-723.9.2 Installing the application floppy disk ................................................................3-773.9.3 Textdisk: Updating the system software language..........................................3-813.9.4 Creating a PC card..........................................................................................3-833.9.5 Updating software via the PC card..................................................................3-83

3.10 Installing HMI Embedded Win 32 on a PCU50 ...............................................3-843.10.1 Installing via a parallel link with a FAT16 file structure....................................3-853.10.2 Installing via a parallel link with a FAT32 file structure....................................3-873.10.3 Installing via a network connection..................................................................3-88

08.01 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.) oruser applications (user interface configurations designed by the machinemanufacturer).

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 userapplications) to a horizontal softkey in the operating area menu (or to a userkey on the HT6).

Introduction

3 Configuring 08.01


3.1 Overview

The following diagram shows the sequence of operations required to configurean operating area:

Creating/copying a

newapplication

(section 3.2)

Configuringa newproject

(section 3.3)

Convertingthe

texts(section 3.4)

Compilingthe

configuredapplication

(section 3.5)

Linking theapplicationareas of the

current project(section 3.6)

Generatingsystem orapplicationdiskettes

(section 3.8)

Testingin

PC simulation(section 3.7)

Transferto hardware(sections 3.9

and 3.10)

After a change in thetexts

After achange in theproject sources

08.01 3 Configuring


3.2 Application manager - creating an application

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 notdisplayed in the tool menu)

The HMI Embedded application manager now appears on the screen.

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 activeas a task.

Remedy: Press key combination ALT TAB until the HMI Embeddedapplication manager is displayed. When you release the two keys, the activeapplication manager will appear again on your screen.

Scope of functions of the application manager

EXIT Exits the HMI Embedded applicationmanager

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 TEXT CONVERTER Sets text converter options ( not yetavailable )

HELP ABOUT APPMAN... Displays information about the HMIEmbedded application manager

Activation

Possible error

3 Configuring 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).

3.2.1 Exiting the application manager

You can close the HMI Embedded application manager by selecting menuoptions EXIT.

3.2.2 Creating a new application configuration

To create a new application, select menu options APPLICATION NEW inthe application manager. A dialog box "APPLICATION NEW" is displayed inwhich you must enter a number of parameters for the new application.

Description of entries in the "APPLICATION NEW" dialog box:

Application Name Name of the new application(max. 8 characters).

Softkey Text/

Application Text

Identifying text on the softkey via which theapplication will be activated. Once the applicationhas been selected, this text also appears at thetop left in the application header (max. 9characters).

General

application - data

08.01 3 Configuring


Text File (.txt) Name of the text file in which the application textsare stored (max. 8 characters).

Comment for Text File Comment text which must appear after the textfile name entry for the application in the [TEXT]section in filemmc100pj\sck\cfg\ApplicationName.cfg (max.200 characters).

Alarm Text File Name (.txt) Name of the alarm text file in which HMI alarmsfor the application can be stored (max. 8characters).

Comment for Alarm TextFile

Comment text which must appear after the alarmtext file name entry for the application in the[TEXT] section in filemmc100pj\sck\cfg\ApplicationName>.cfg (max.200 characters).

SCK Module Name Descriptive text in the SCK for selecting theapplication when configuring a project (max. 8characters).

Name Descriptive text to be displayed for yourapplication in the HMI Embedded version display(max. 8 characters).

Version Version identifier to be displayed for yourapplication in the HMI Embedded version display(max. 6 characters).

Date Not active

Time Not active

Length Not active

Note

When you enter an application name, the DEFAULT button is enabled. If youselect this button, all the other fields are assigned defaults containing theapplication name.

You can enter the settings for Date, Time and Length fields manually after youhave created the application by modifying the file ApplicationName.cfg in pathmmc100pj\Sck\Cfg. These entries are as follows:

Application �Version Display

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 yourapplication!

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".

Objects created

08.01 3 Configuring


See Subsection 2.4: Where can I find what?

Note

The operations you are currently performing are displayed in the dialog line ofthe application manager. If an error occurs while you are executing any of theabove actions, an appropriate error message box will appear on your screen.

Switch to the MSVC Workbench and select menu options PROJECT OPEN.... Select the application make file in folder "Obj_c800" of the createdapplication (e.g. MyApp.mak) and confirm your input by pressing the OK buttonor double click with the left mouse button.

To process yourapplication withMSVC V1.xy

Installation path ofconfiguring package

Application directory

Application header files

Application make files(MSVC 1.xy only)

Application source files

Text files in languagedirectories

Application project files(MSDEV 6.0 only)

3 Configuring 08.01


The MSVC Workbench now loads the new application and you can startconfiguring.

Switch to MS Visual Studio and select menu options FILE OPENWORKSPACE. Select ...\ApplicationName.dsw (e.g.mmc100pj\Proj\App\MyApp\MyApp.dsw) and confirm your input by pressingthe OK button or double click.

The MSVC Workbench now loads the new application and you can startconfiguring.

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 COPYin the application manager. A dialog box "APPLICATION COPY" is displayed inwhich you must enter a number of parameters for the new application.

Description of inputs in the "APPLICATION COPY" dialog box:

To process yourapplication withMSVC V6.0

08.01 3 Configuring


Application Name Name of the project to be copied. The applicationmanager now searches through directorymmc100pj\Proj\App for existing applications anddisplays them for selection in the form of a combobox.

The manager offers only those projects that havebeen created with the selected (duringinstallation) development environment.

The combo box displays only one application.You can change the selection using the arrowkeys in the combo box or with CURSOR_UP orCURSOR_DOWN.

See Subsection 3.2.2: Creating a new application configuration: Description ofentries in the "APPLICATION NEW" dialog box:

Note

When you enter an application name, the DEFAULT ...button is enabled. If youselect this button, all the other fields are assigned defaults containing theapplication name.

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 creatednew. The text files are also generated with the name specified in the dialogbox.

See Subsection 2.4: Where can I find what?

Note

The operations you are currently performing are displayed in the dialog line ofthe application manager. If an error occurs while you are executing any of theabove actions, an appropriate error message box will appear on your screen.

Proceed as described inSubsection 3.2.2 Creating a new application configuration

source

Destination Data

Copying actions

To process theapplication youhave just created

3 Configuring 08.01


3.2.6 Closing application data

(Application Close)


3.2.7 Setting text converter options

(Options Text Converter)


3.2.8 Displaying information about the HMI Embedded applicationmanager

You can display information (e.g. current version of the HMI Embeddedapplication manager) by selecting menu items HELP ABOUT APPMAN....

Close the information box again by selecting the OK button.

08.01 3 Configuring


3.3 Configuring a project

3.3.1 Creating a new project

The SCK (Software Configuration Kit) tool for configuring the system allowsyou to choose from a selection of operating functions for different targetsystems those functions that are appropriate and desirable for your particularmachine. In this way, you can individually design and adapt your operatorpanel interface.

The result of the configuration is a collection of files on the hard disk of theconfiguration PC which can be accessed directly from the SCK either forloading 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 secondlanguage in this screen; these are then installed as the foreground andbackground languages on the hardware (see also Subsection 3.4.1"Languages � Multilingual Texts"). You can switch between these twolanguages in operation. The hardware configurations are also specified inthis screen. Please set your mmc100pj as the APPLICATION_PATH. Keyin 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 applicationsTo do this, enter the number of the softkey first and press RETURN. Thenenter the module number. ( To cancel the assignment of a softkey, select0 ).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 assignmentswith H.Repeat this sequence of operations until you have assigned all softkeysand hardkeys (HT6 only) as required.

Note

You can assign each module to one softkey or hardkey only!

To configure aproject using theSCK (SoftkeyConfiguration Kit)

3 Configuring 08.01


� Confirm with <F4>.

� Use the start softkey to select the application with which the system mustboot.


� In the subsequent screen, you can define further options for texts andfiles.

<1> = Edit text files for firstl<2> = Edit text files for secondl<3> = Edit ASCII files<4> = Edit user-specific files<5> = Copy external files to the project<6> = Set options for operating area(s)

<ESC> = Cancel!

Please make your choice <F1> - Help

<F4> = Save project

<F1> = Help


� Select a project (after you have created a new project, it is automaticallyselected)

� To create a PC card image, select <I> INSTALL SYSTEM VIA RS232COR CREATE FLASH CARD in the main menu.

� To create system disks, select <S> MAKE SYSTEM DISK in the mainmenu. Using these disks, you can generate PC card images of the projectwithout an installation kit, or transfer it to the hardware via the serialinterface.

� To create application disks, select <A> MAKE APPLICATION DISK in themain menu. Using these disks, you can modify the system disks of thisproject to a certain degree. You can choose, for example, otherlanguages, or modify the bus address or text files.

� To create a PC simulation environment, select <C> CREATESIMULATION ENVIRONMENT in the main menu.

� Exit the SCK tool.

Note

The behavior of the PC simulation function can be altered only by the CREATESIMULATION ENVIRONMENT function of the installation kit. If, for example,you change the softkey assignments and create a PC card, the newassignments are operative on the card, but the old assignments still apply inthe PC simulation environment.

To generate a system

08.01 3 Configuring


3.3.2 Description of configuration files (*.cfg)

The Installation Kit (SCK) manages a configuration file in foldermmc100pj\Sck\Cfg FOR EVERY APPLICATION. The data stored in this fileincludes information about the DLLs and text files used for the application aswell as version information.

Important

You should not normally make any changes to these files yourself! Incorrectentries can have a negative impact on the functionality of your system.Nevertheless, the structure of these files is described briefly below, since somesettings can only be made by this method. You should close the SoftwareConfiguration Kit before you edit the file.

Section [DLL]:dll name = Method start, method end, start method, class name for taskcommunication, symbolic name for configuration, start menu identification,number of notebooks, text file name for standard texts, text file name for alarmtexts 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 thisapplication. However, only the section associated with the hardware isevaluated; it is possible, for example, to use different hardware versions fordifferent 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 menuselection)

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 variablesmay 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 notexplicitly specify a hardware type, it is assumed that it is suited to all hardwaretypes.

1 - Application suitable for appropriate hardware (default)

0 - Application not suitable for appropriate hardware

08.01 3 Configuring


3.4 Text converter - text principle

The following diagram illustrates the text converter processes.

Textfilename.txt

Alarm-textfilename.txt

Text converter

Textfilename.h

Textfilename.sp1

Textfilename.sp2

3.4.1 Languages - multilingual texts

You can select between 1 and 99 languages when you install the HMIEmbedded SW system. Two languages are preset per default. The first isinstalled 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 languageand *.s02 for the background language. These default settings can also bechanged via display machine data.

You can exchange the first and second languages of the HMI Embeddedsystem for other text versions or different text languages without recompilingthe 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).

Description

3 Configuring 08.01


3.4.2 Master language

The different versions of the text binary files must be compatible. For thisreason, a master language is always defined for the overall text handlingoperation. This determines the number and order of texts, their completenessand the consistency of symbol meanings. German (in path..\Proj\App\Text\D) isset as the default master language in the HMI Embedded Screen Kit. If youwant a different master language, change the default options in the SCK andcall the text conversion function using the appropriate language code in theMSVC Workbench or MS Visual Studio.See description of Installation Kit and Subsection 3.4.10: Calling the textconverter.

3.4.3 Text source file - TextFileName.txt

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 (PLCalarms, cycle alarms and compile cycle alarms).

All text source files have the *.txt extension.

3.4.4 Text binary files - TextFileName.sp1, TextFileName.sp2

Text binary files are generated by means of the tool at TOOLS TEXTCONVERTER.

Text binary files always have the *.sp1 extension for foreground language textsand *.sp2 for background language texts.

When the PC Simulation function is called, it expects to find the text binary filesin directory ..\mmc100pj\Bin_sim.

The configuring system is preconfigured such that the text conversion tool(TOOLS TEXT CONVERTER) and the SCK automatically copy the textbinary files for the foreground language (*.sp1) and those for the backgroundlanguage (*.sp2) into directory ..\mmc100pj\Bin_sim.

The language you wish to use as the foreground and/or background languagemust be specified as an argument in the call to the TOOLS TEXTCONVERTER function.

See also Subsection 3.4.10: Calling the text converter.

Description

Description

Description

08.01 3 Configuring


3.4.5 Text include file - TextFileName.h

To link the texts to the configuration, so-called text include files are generatedfrom the configuring text source files using the text conversion tool. Textinclude files are generated in the master language directory (e.g.mmc100pj\Proj\App\ApplicationName\Text\D). Text include files have theextension *.h.The text include file for your application is called TextFileName.h. This file isautomatically copied to directory \Proj\App\H by TOOLS TEXTCONVERTER.The symbolic identifiers (also referred to as Text IDs) for the configuration aredefined in the text include files.

3.4.6 Text dependencies

The application configuration must be recompiled when you edit aTextFileName.txt or AlarmTextFileName.txt.Recompilation is implemented by the relevant dependencies in make fileApplicationName.mak or project file ApplicationName_li.dsp.

3.4.7 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 runtimesystem 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.txtand the alarm text file name = AmyApp.txt, then # include "MyApp.H"is correct.

Description

Description

Description

3 Configuring 08.01


3.4.8 Syntax of configuring text source files

The relevant configuring source text file is stored in pathmmc100pj\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 informationfor the installation kit, the text converter and the runtime system.// CP=1252// IDEO=NO// ANSI=YES// UNICODE=NO// VERSION=Vxx.xx.xxThe first entry specifies the font code page used, the next line determineswhether the texts are Asiatic. "ANSI" and "UNICODE" stand for the file formatof the text file. The last entry contains a version identifier.

All configuring text source files are configured as follows:

symb_txt_id "text" [// Comment]

symb_txt_id Symbolic text identification, must start with a letter, max.length 45 characters. symb_txt_id must be uniquethroughout the configuration (standard and application).

This requirement is fulfilled within the supplied configuration version by thefollowing conventions :Text identifiers defined in file xy.txt always begin with 'T_XY_' and are uniquewithin 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 // andthe line end.

The maximum length of text that can be displayed on the screen is generallyentered as a comment.

Note

Do not use any ANSI-C comments (/*...*/), but only SingleLinecomments (//...)!

Description

Parameters

08.01 3 Configuring


3.4.9 Syntax of the HMI Embedded alarm text source file

The relevant configuring alarm text file is stored for each language in pathmmc100pj\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 configuringmacro. 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-119999range.

Notes

� Do not use any ANSI-C comments (/*...*/), but only SingleLine comments(//...)!

� The alarm text files usually begin with a number of comments containinginformation for the installation kit, the text converter and the run-time 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!

3.4.10 Calling the text converter

Fig.: Arguments for the text converter (MSVC Workbench)

The text converter is used to make the assignment between configured textfields and edited texts in different languages.

Important!

You must activate the text converter every time you edit a text file to ensurethat your change is visible, e.g. in PC Simulation.

If you are using the same text file for several different applications, you mustcall the text converter in the project in which the texts are defined !

Description

Purpose

3 Configuring 08.01


You can call the text converter by selecting menu options TOOLS TEXTCONVERTER in the MSVC Workbench or MS Visual Studio. The "ToolArguments" box then opens in which you are prompted to specify the callparameters for the text converter. The following parameters are specified perdefault:

-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 defaultparameters, you must select menu options OPTIONS TOOLS in the MSVCWorkbench TOOLS CUSTOMIZE TOOLS tab in Visual Studio, click onthe 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 directorymmc100pj\Proj\App\ApplicationName\Text\:

D German

G English

I Italian

E Spanish

F French

-f<lan> Convert foreground language only, all text files ofapplication

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

Important!

You must have generated the foreground language at least once beforehand!

-f<lan> -b<lan> Convert foreground and background languages, alltext files of application

Call

Examples ofparametercombinations

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 backgroundlanguages = <lan>, all text files of application

-all Convert all languages, foreground and backgroundlanguages from Setup settings (from Setup.cfg), alltext files of application

-app <WkspDir> This instruction notifies the text converter of theproject path. The text converter uses this todetermine 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 inpath mmc100pj\Proj\Text, incl. applicationtext files

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

Important!


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

-sys Convert foreground and background languagesfrom Setup settings (from Setup.cfg), all text files inpath mmc100pj\Proj\Text, incl. application textfiles

-all -sys Convert all languages, all text files in pathmmc100pj\Proj\Text, incl. application text files,foreground and background languages from Setupsettings (from Setup.cfg)

-all -sys -f<lan> Convert all languages, all text files in pathmmc100pj\Proj\Text, incl. application text files,foreground language = <lan>

-all -sys -b<lan> Convert all languages, all text files in pathmmc100pj\Proj\Text, incl. application text files,background language = <lan>

3 Configuring 08.01


Important!


-all -sys -f<lan>-b<lan> Convert all languages, all text files in pathmmc100pj\Proj\Text, incl. application text files,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 textfiles. This can be deactivated with -oNoLenWarn.

If you specify an f or b option, this language is treated as the foreground orbackground language and the generated language files copied to simulationdirectory mmc100pj\Bin_sim. If you do not specify one of these options, thedefaults from Setup.cfg) are used for the foreground (=master) andbackground languages.

If you specify only one of these options, then only this language file is copiedto 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 loadedto simulation directory mmc100pj\Bin_sim or directory mmc100pj\Proj\App\Hso that they are available for further configuring operations. The text sourcefiles (TextFileName.txt) themselves are copied to directorymmc100pj\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 languagedirectories in mmc100pj\Proj\App\ApplicationName\Text do not matchmmc100pj\Proj\Text!

A log file (mmc100pj\Proj\App\ApplicationName \Text\Textkonv.log) isgenerated while text is being converted.

Important!

The foreground language must have been generated at least once before textconversion can be called with option -b<lan> only!

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:

Systeminclude files

from directorymmc100pj\

Proj\

Project.h ap_l_dir.h mwl_app.h nb_app.h Textfile.h

Furtherinclude files

forapplication-

specificdefinitions

(*.h)

ap_l_dir.c app_menu.cFurther

applicationsource files

(*.c)

Application make file

ApplicationName.mak

Application project file

ApplicationName_li.dsp

Application-Name.lib

3 Configuring 08.01


3.5.2 MSVC project - ApplicationName.mak

In the MSVC Workbench V1.x, units (libraries, executables, etc.) that belongtogether are grouped as projects.

The generation convention and the dependencies for these projects arestored in mmc100pj\Proj\App\ApplicationName\Obj_c800\ApplicationName.mak files.

Note

Do not modify by hand! These ApplicationName.MAK files are maintained bythe MSVC Workbench (PROJECT EDIT, PROJECT SCAN ALLDEPENDENCIES).

3.5.3 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 ofassociated elements. (The include and source files of an application, a DLL,etc. ). A working area combines several projects of one topic (e.g. theapplication and the required DLLs ).

Even the Screen Kit applications adhere to this concept: For every applicationApplicationName there is a workspace ApplicationName.dsw. This workspacecontains the two projects ApplicationName.dsp and ApplicationName_li.dsp.

The project ApplicationName_li.dsp generates from the source files of the listconfiguration an ApplicationName.lib. You should store new configuring filesin this project.

The project ApplicationName.dsp is dependent on the other project. Itgenerates an ApplicationName.dat from the ApplicationName.lib. Only *.datfiles can be utilized by the linking operation. The project contains ap_l_dir.cas 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 andthe affected files recompiled automatically.

Description

Description

08.01 3 Configuring


3.5.4 Application source files - *.c

Your application operating area source files are stored in mmc100pj\Proj\App\ApplicationName\Src\.C.

These files must have the extension .c. Their syntax must correspond to theconfiguring syntax.

The configuration is compiled to form an application library.

This library acts as an input for the linker which uses it to generate theconfiguring binary file (ApplicationName.dat).

This library acts as an input for project ApplicationName which uses it togenerate the configuring binary file (ApplicationName.dat).

A configuring source file with the first application window and preparations forother lower-level windows is stored inL:\Proj\App\ApplicationName\Src\app_menu.c .

3.5.5 Application list directory - ap_l_dir.h

The application list directory is stored inmmc100pj\Proj\App\ApplicationName\H\ap_l_dir.h.

The application list directory ap_l_dir.h contains external definitions for all listpointers of the lists in the application operating area that are used in morethan one configuring source file.

Each list used in the configuration must be specified accordingly in this file.

EXTERN_List type (id) List external reference

id List identity

Description

MSVC 1.xx only

MS Visual Studioonly

Example

Description

Syntax

Parameter

3 Configuring 08.01


3.5.6 Notebook defines - nb_app.h

The area for notebook entries that may be used freely for configuring theapplication is stored in mmc100pj\Proj\App\ApplicationName\H\nb_app.h.

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

The number ranges for list identifiers are defined in file mmc100pj\Proj\App\ApplicationName\H\mwl_app.h.

The identities for list elements (e.g. input/output fields, actions, reactions)need only be unique in the relevant configuring source file.

The event codes specified in the elements (WATCH_EVENT,VALUE_EVENT, BIT_EVENT) of the event list must be between 10.000 and19.999.

Depending on their scope of application and validity, notebooks from differentnumber ranges are used.

The number range divisions are specified in file mmc100pj\Proj\App\ApplicationName\H\nb_app.h; symbolic defines for the notebooknumbers used can also be assigned in this file.

Local (temporary) notebook entries can be used in all ranges and overwrittenin each case with completely different contents.

Definition in mmc100pj\Proj\App\ApplicationName\H\nb_app.h

Description

List identitiesList identifiers

List elementidentities

Event codes

Notebook entries

08.01 3 Configuring


Global (application-specific) notebook entries (number 200 to (200 + no. ofNBs)) 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 otherapplications/operating areas. Local notebook entries should therefore only beused 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 samenotebook number. Application-specific notebooks retain their information afteroperating area switchovers.

3.5.8 Starting the compile operation on the MSVC Workbench

Select menu options PROJECT OPEN... on the MSVC Workbench. At"LIST FILES OF TYPE:" select type "Project (*.mak)". Click on the relevantApplicationName.mak file from the appropriate application directorymmc100pj\Proj\App\ApplicationName\Obj_c800. Select the OK button toopen the application configuration.

mmc100pj\Proj\App\Example\Obj_c800\Example.mak

Once you have opened an application configuration, you can start thecompile operation. You do this by selecting menu options PROJECT BUILD APPLICATIONNAME.LIB or PROJECT REBUILD ALLAPPLICATIONNAME.LIB in the MSVC Workbench.

Note

Before you compile, you should make sure that you have already updatedany changes to your text files using the text converter. If not, make sure youdo so before compiling the configuration, see Subsection 3.4 Text converter �Text principle.

You will know if the application has been generated correctly when thefollowing message appears in your output window:

"APPLICATIONNAME.LIB - 0 ERROR(S), 0 WARNING(S)"

Directory mmc100pj\Proj\ApplicationName\Obj_c800 must now contain a fileApplicationName.lib.

To open theapplication

Example

To compile anapplicationconfiguration

3 Configuring 08.01


3.5.9 Starting the compile operation in MS Visual Studio 6.0

Select menu options FILE OPEN WORKSPACE in MS Visual Studio. At"FILE TYPE:" select type "WORKSPACES". Click on the relevantApplicationName.DSW file from the appropriate application directorymmc100pj\Proj\App\ApplicationName. Select the OK button to open theapplication configuration.

mmc100pj\Proj\App\Example\Example.dsw

Once you have opened a working area, you can start the compile operation.To do this, select menu options BUILD BUILD ApplicationName.dat orBUILD REBUILD ALL in Visual Studio.

Note

ApplicationName must be selected as the active project; only the library iscompiled with ApplicationName_li, but not the DAT file.

Before you compile, you should make sure that you have already updatedany changes to your text files using the text converter. If not, make sure youdo so before compiling the configuration, see Subsection 3.4.10 Calling thetext converter.

You will know if the application has been generated correctly when thefollowing message appears in your output window:

"APPLICATIONNAME.DAT - 0 ERROR(S), 0 WARNING(S)"

A file ApplicationName.dat must now have been generated/modified indirectory mmc100pj\Proj\SL.

To open theapplication

Example

To compile anapplicationconfiguration

08.01 3 Configuring


3.5.10 Extensions and dependencies

If the number of displays configured for an application configurationincreases, it is advisable to configure, e.g. each window in its own applicationsource file mmc100pj\Proj\App\ApplicationName\Src\*.c).

Create a new source file in foldermmc100pj\Proj\App\ApplicationName\Src\New_File. Enter the requiredinclude statements and configuring lists in it.

You now need to register the newly created application source file with theApplicationName.mak File. In the MSVC Workbench select menu optionsPROJECT EDIT... . Now specify the path and name of the applicationsource file you have just created, register it with the ApplicationName.makfile by selecting the ADD button and then confirm your change with theCLOSE button.

Check whether the MSVC Workbench has stored the new application sourcefile by selecting the PROJECT FILES BUTTON (button on far left on toolbarmenu). The list of files displayed must now also include the file you have justgenerated. You can now continue configuring in the new application sourcefile.

Open the insert dialog by selecting PROJECT ADD TOPROJECT FILES. In the "Insert Into:" combobox, select projectApplicationName_li.dsp . Change to directorymmc100pj\Proj\App\ApplicationName\Src in the file tree and selectNEW_FILE. The file is stored in the project when you select OK.

Check that it has been properly inserted by activating the FileView in theworkspace window. The new file must be stored in folderApplicationName_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\ApplicationNamewith its subdirectories and file ..\Sck\Cfg\ApplicationName.cfg. These are theonly files needed to clearly identify and reproduce an applicationconfiguration.

Extensions toapplicationconfigurationsCreate an applicationsource file

To include source filein an MSVC project

To include source filein a Visual Studioproject

3 Configuring 08.01


3.5.12 Description of "Example"

Note

In the current version, "Example" can only be compiled with the MSVCWorkbench, but not with MS Visual Studio.

Note

This example uses a resolution of 640 x 480 pixels and is thus not suitable forHT6!

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 configuringsource 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 theapplication.

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 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 theoperating area menu.

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 canalso be made. You can direct the input focus from one input/output field tothe next using the cursor keys.

� The current value of the notebook content with number 20 from the MMCis 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 oneinput/output field to the next using the cursor keys.

� The first vertical softkey "ADD NB20 TO R10" adds the content ofinput/output field "NOTEBOOK 20" to the content of input/output field "RPARAMETER 10".

� The second vertical softkey "SUB. NB20 FROM R10" subtracts thecontent of the input/output field "NOTEBOOK 20" from the content ofinput/output field "R PARAMETER 10".

� The first horizontal softkey "GOTO WIN 2" closes the "EXAMPLE: OEMWINDOW 1" window and activates the "EXAMPLE-WINDOW 2" window.

Mode of operation

3 Configuring 08.01


Functions in the "EXAMPLE: OEM WINDOW 2" window

� The current position of the X axis from the NC is read and displayed (hotlink) in output field "ACTUAL VALUE X-AXIS". No user inputs can bemade.

� The first horizontal softkey "GOTO WIN 1" closes the "EXAMPLE: OEMWINDOW 2" window and activates window "EXAMPLE-WINDOW 1".

� The first vertical softkey "SET ALARM" outputs the HMI alarm withnumber 120000 from the alarm text file.

� The second vertical softkey "RESET ALARM" cancels the HMI alarm withnumber 120000.

08.01 3 Configuring


3.6 Linking the application areas

The following diagram illustrates the general linkage process:

Application-Name.dat

Other OEMapplications(.. Proj\Sl\

*.dat)

Sl.dat

Application-Name.lib

Standardapplications( ...\ Proj\S \

*.dat)

General linkage process

Generate Sl.dat

<Applikationsname>.dat is generated by"Generate SL.DAT" on the MSVCWorkbench only; with Visual Studio it isgenerated as part of the compilationroutine.

3 Configuring 08.01


3.6.1 Important files for the link operation

A special link operation is used to generate a file named Sl.dat from theapplications currently configured in the Installation Kit (SCK).

File SI.dat contains no texts, however, but only text references. The textsthemselves are read from text binary files (TextFileName.sp1,TextFileName.SP2 or AlarmTextFileName.sp1, AlarmTextFileName.sp2)while the HMI software is executing.

3.6.2 Starting the link operation

The open application configuration and the current application configurationtexts 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. ADOS box opens and displays status information about the operation as itproceeds.

As indicated previously, the behavior of GENERATE SL.DAT in the MSVCWorkbench differs to that in Visual Studio. With the MSVC Workbench, theApplicationName.lib file is first converted to an ApplicationName.dat filebefore the actual link operation for the applications begins. In contrast, theDAT file is generated as part of the compilation process in Visual Studio.

Notes

� A log file named APPLICATIONPATH\SL_MAKE.LOG is generatedduring the link operation.

� In the MSVC Workbench the link operation must be called for everymodified application, since this process also generates theApplicationName.dat file! A link operation out of another application usesonly 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 windowso that no DOS box is displayed.

Precondition

08.01 3 Configuring


3.7 Testing the configuration on a PC

PC simulation is described in detail in Section 5.

3.8 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 changedisks.

� Return to the main menu.

3.9 Installing HMI Embedded on a PCU20An upgrade guide is supplied with every software version. You will find it inthe first installation directory in file "siemensd.txt (German)" or "siemense.txt(English)".

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 HMIEmbedded system for English as the first language and German as thesecond. 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)

Supply method

System software

Application software

3 Configuring 08.01


3.9.1 Installing the system software

The CD contains the following software:� System software� User softwareThe HMI Embedded software is copied via an RS232C interface or PC cardto the internal EPROM.The system software contains all the files required to operate HMI Embedded.Language combinations other than English and German can be retro-installed from the application floppy disk and/or language CD.The user software area includes all system texts, PLC message texts andcycle alarm texts.

� To upgrade the system software (software version) on the PCU 20, itmust be switched to Service mode (see below).

� A PC/PG from which the new system software can be loaded is alsorequired.

� Directories requiring up to 16 MB memory are set up on the hard disk ofthe PC/PG. These directories contain the data selected for transferduring installation.

Every time software is transferred from a PC/PG to a PCU 20, the latter mustbe switched to the "ready to receive" state.

1. The PCU 20 is switched off.2. For transfer via RS232C:

- Connect the defined serial interface on the PC/PG with theinterface 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 aselection menu prompting you to choose between update from card orPCIN appears.

0: Update from PC Card1: Update with PC-IN (COM1:)2: Update with PC-IN (COM2:)

Select "PCIN" here if no PC card is available for updating the software. ThePCU 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 EXIT

PCIN Light

VERSION MMC-IN System Upload 1.1

Copyright (c) SIEMENS AG 1994

Software areas

Preconditions

Making the PCU 20ready to receive

Service mode

08.01 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. Install the system software to the hard disk (PC/PG)!With this command you can transfer the system software to severalPCs/PGs.

2. Install the system software to the hard disk (PC/PG) and transfer thecurrent configuration to the PCU 20 hardware!With this command you can transfer the system software to the harddisk (PG/PC) and install it immediately afterwards on the target PCU20 hardware.

3. Update or change the DOS/BIOS software

ESC Cancels the installation and ends the program.F1 Displays online help for the active display (available soon).

Necessary only if prescribed explicitly in a software upgrade guide.This point is omitted with normal installation.

Example:You are installing SW 6.1You 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 numberin the sub menu for transfer to the PCU 20.If you enter the number more than once, the selection togglesbetween YES and NO.

� The relevant file need not be selected for transfer to thePCU 20.

Whether you need to load one or more files specified in the table to the PCU20 will depend on which software version has been operated previously onthe PCU 20.Only the selected files should be transferred.

1.SYS_INST.EXE

2. Change theDOS/BIOS software<3> (not necessary atthe present time)

3 Configuring 08.01


Select files to install

<1> = ROMDOS20.BIN NO

<ESC> = Back to main menu


1. Select whether the DOS/BIOS area (Video BIOS, System BIOS, ROMDOS, PCIN) must be transferred

ESC Return to the installation menu and transfer the selecteddata

Select drive for installation

Drive:

ESC RETURN

Copyright (c) Siemens AG 2001, all rights reservedInstallation kit version 06.01Install system disk to hard disk

F1

Select the drive on the PC/PG to which the files from the system floppy diskmust be copied. Any hard disk drive or network drive with write authorizationcan be selected.

Select path for installation

Path:

ESC RETURN

Copyright (c) Siemens AG 2001, all rights reservedInstallation kit 06.01Install system disk to hard disk

C:\MMC100PJ.SYS

F1

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 thesuggested default path.

ImportantIf the directory already exists, it will be overwritten!

3. Enter a drive <2>

4. Specify a path

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 executionof the command and the initial menu appears again.From the hard disk (e.g. network installation) it is possible to install thesystem software on other PCs/PGs. You can then transfer the software to thehardware by opening the directory in which it has been installed and callingfile "SYS_INST.EXE". The "System installation" menu appears.To transfer the hardware configuration, continue as follows:

The transfer menu is displayed:

Transfer software to hardwareSelected COM port: COM1

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

<ESC> = Quit program


Menu option 1:Before you activate the transfer by selecting option <1>, you must ensure thatthe 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 memorycard image is generated that you can store in any directory of your choice. Ifthe directory you choose does not exist, it will be set up. If it already containsa 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 towhich you have connected the cable on the PCU 20, press <3>. In thefollowing submenu, select the digit identifying the COM interface you haveused. You will then return to the transfer menu where your port selection isdisplayed.

When you start the transfer, the following warning appears, ensuring that youare loading the software to the correct hardware:

Important advice!Please note!!!

ESC RETURN

Transfer software to hardware PCU20Selected COM port : COM1

<1> = Install system via serial line

(old MMC100.2 MLFB 6FC5210-0DA00-1AA0 or old MMC100.2 MLFB 6FC5210-0DA00-1AA1 or new HT6 MLFB 6FC5503-0AA10-0AA0 ornewest PCU20 MLFB 6FC5210-0DF00-0AA0)

<F1> - Help

Do you have the correct HMI hardware?

Please make your choice

<2> =

<3> =

<ESC> =

5. Transfer software tohardware

3 Configuring 08.01


Make the PCU20 ready to receive1. 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 aselection 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 haveconnected the cable on the PCU20 if no programmed PC card isavailable. The PCU20 is now ready to receive data via the RS232Cinterface.

Activate the transferSelect <1> in the transfer menu.The transfer operation begins and its current status is displayed both on thePC/PG and the PCU20.

Transfer is not o.k.If the transmission path is not o.k., then the PCIN screen appears on thePC/PG followed in a few seconds by the message:

WARNINGThe program PCIN-Light returned a TIMEOUT error!

Check the cable, readiness to receive on the PCU20 and the specified COMport. Once you have corrected the error, start the transfer operation again.

Series upgradeYou can update the software on several PCU units successively from thetransfer menu if you repeat the above sequence of operations in successionfor each PCU to be updated. Exit the transfer menu with <ESC> when youare finished.

FinishAfter 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 diskwere copied. You can start the installation menu again from here.

Start installation from HDThe installation menu appears again when "sys_inst.exe" is started. It nolonger contains menu option "Install system disk on hard disk" since thistransfer operation has already taken place. The other options can be selectedas described above.

08.01 3 Configuring


3.9.2 Installing the application floppy disk

The boot and system software must already have been loaded.� Compression software "ARJ.EXE" should be available.� Call file "APP_INST.EXE".

Select drive for installation

Drive:

ESC RETURN

Copyright (c) Siemens AG 2001, all rights reservedInstallation kit version 6.01Install application disk to hard disk

Select the drive to which the application software files must be extracted. Anyhard disk drive or network drive with write authorization can be selected.

Select path for installation

Path:

ESC RETURN

Copyright (c) Siemens AG 2001, all rights reservedInstallation kit 6.01Install application disk to hard disk

C:\MMC100PJ.APP

Select the path to which the application software files must be extracted. Thepath will be set up if it does not yet exist. "\mmc100pj.app" is the suggesteddefault path.The files are copied to the hard disk and extracted!

Preconditions

1. Call APP_INST.EXE

2. Specify a drive

3. Specify a path

3 Configuring 08.01


After the files have been installed on the hard disk, the following selectionmenu appears :

Install application to hardware PCU20First language: English Second language: German

<1> = Install all modules to hardware<2> = Modify configuration

<ESC> = Esc to quit!


1. Install the current configuration on the hardware!2. Change the language settings and edit selected ASCII files.ESC Cancels the installation and ends the program.F1 Displays online help for the active display (available soon).

When you select <1> the transfer languages are selected. Press the Returnkey to display more selectable languages (if available). Confirm yourselection with <F4>.

Select additional language for application disk

English

French

German

<ESC> = Cancel <Return> = Toggle<F1> = Help <F4> = Accept

X >

X >

Selected Hardware:

Install application on hardware PCU20First language: English Second language: German

<1> = Change first language<2> = Change second language<3> = Edit ASCII files<4> = Edit text file for first language<5> = Edit text file for second language<6> = Add user-specific files

<ESC> = Back to previous menu!


1. Change the language setting for the first language.2. Change the language setting for the second language.3. Edit the ASCII files of the system and applications if they contain

ASCII files.4. Edit the language files for the selected first language.5. Edit the language files for the selected second language.6. Copy PLC status files or others (Wizard) to the application image.

4. Prepare SW modulesfor transfer and install onthe hard disk

4.a. Languagesetting <1>

4.b Define theconfiguration <2>

08.01 3 Configuring


ESC Return to the installation menu.F1 Displays online help for the active display (available soon).

Install application on hardware PCU20First language: English Second language: German

<1> = Edit MPI configuration data<2> = Edit display machine data<3> = Edit AUTOEXEC.BAT<4> = Edit CONFIG.SYS<5> = Edit OEM.BAT<6> = Edit user specific files

<ESC> = Back to previous menu!


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

Correct functioning of the software cannot be guaranteed if unauthorizedchanges are made to "AUTOEXEC.BAT" and "CONFIG.SYS" files

Transfer software to hardware PCU20Selected COM port: COM1

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



If the port displayed at "Selected COM port:" is not the same as the port towhich you have connected the cable on the PCU 20, press <2>. In thefollowing submenu, select the digit identifying the COM interface you haveused. You will then return to the transfer menu where your port selection isdisplayed.Before you activate the transfer by selecting option <1>, you must ensure thatthe PCU20 is ready to receive and a cable connection to it has been made.

Activate the transferSelect <1> "Install software via serial line" in the transfer menu.The transfer operation begins and its current status is displayed both on thePC/PG and the PCU20.

4.b.1 Edit ASCIIfiles <3>

5. Transfer softwareto hardware

3 Configuring 08.01


Transfer is not o.k.If the transmission path is not o.k., then the PCIN screen appears on thePC/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 COMport. Once you have corrected the error, start the transfer operation again.

Series upgradeYou can update the software on several PCU units successively from thetransfer menu if you repeat the above sequence of operations in successionfor each PCU to be updated. Exit the transfer menu with <ESC> when youare finished.

FinishAfter you have finished transferring the software to the PCU20, close theinstallation menu with <ESC>. You are now in subdirectory "INSTUTIL" of thehard 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/PGThe configuration menu appears when you start "app_inst.exe". The selectionoptions for drive and path are omitted since the files have already beentransferred from CD to hard disk. The other options can be selected asdescribed above.

Readiness to receive on PCU201. 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 aselection menu prompting you to choose between update from card orPCIN appears. Select "PCIN" here if no PC card is available for updatingthe software. The PCU 20 is now ready to receive data via the RS232Cinterface.

Normal situationThe transfer operation begins and its current status is displayed on thePCU20.

Errors in making PCU20 ready to receiveIf no error-free connection can be established after you have taken the stepsabove, 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 transmissionExit the transfer menu by pressing <ESC>. Subdirectory "INSTUTIL" will nowbe the active directory.

Start installation from HDThe configuration menu appears when you start "app_inst.exe". The selectionoptions for drive and path are omitted since the files have already beentransferred from CD to hard disk. The other options can be selected asdescribed above.

Installation via a network (available soon)

Installation info

08.01 3 Configuring


3.9.3 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.

The configuration in the text software (selected operating areas) must matchthe 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



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).

Select the drive in which your SCK/SDK was installed

Drive:

ESC RETURN

Copyright (c) Siemens AG 2001, all rights reservedInstallation Kit version 6.01Update texts on your screen or installation kit installation

F1

Specify the drive on which the application software files have been installed

Preconditions

1. Call TXT_INST.EXE

2. Add a new languageto the screen kit

2.a Specify a drive

3 Configuring 08.01


Drive:

ESC RETURN

Copyright (c) Siemens AG 2001, all rights reservedInstallation Kit version 6.01Update texts on your application installation

Select the drive in which your application was installed

F1

Enter the path in which the Screen Kit has been installed. "\mmc100pj" is thesuggested default path.The files are copied to the hard disk and extracted!After the files have been installed on the hard disk, the update is complete.

Select the drive in which your application was installed

Drive:

ESC RETURN

Copyright (c) Siemens AG 2001, all rights reservedScreen kit version 6.01Update texts on your application installation

F1

Specify the drive on which the application software files have been installed.

Path:

ESC RETURN

Copyright (c) Siemens AG 2001, all rights reservedScreen kit version 6.01Update texts on your application installation

E:\MMC100PJ

Select the path in which your application was installed

F1

Enter the path in which the application software files are installed."\mmc100pj" is the suggested default path.The files are copied to the hard disk and extracted!After the files have been installed on the hard disk, the update is complete.

2.b Specify a path

3. Add a new languageto the applicationsoftware image

3.a Specify a drive

3.b Specify a path

08.01 3 Configuring


3.9.4 Creating a PC card

The PCMCIA cards used for the NCU and PCU20 are very similar inappearance and therefore easily confused with one another. To help youdistinguish 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. Change to the "instutil" directory in the system environment, e.g."\mmc100pj.sys\instutil" (the directory you specified when you installedthe system environment on the PC/PG).

2. Call "sys_inst".3. Select option <1> "Install system on hardware".4. Select option <2> "Create Flash Memory Card image"5. Specify the target directory in which the ABB system file must be

stored.File "pcu20.ABB" is then generated.

6. Insert the PC card in the PCMCIA slot on the PC/PG.7. Transfer the new ABB file to the PC card using "SINUCOPY-FFS".

3.9.5 Updating software via the PC card

PC card with the latest HMI Embedded software version1. Switch off the control system2. Insert the PC card with the latest HMI Embedded software version3. Switch on the control system4. 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 controloutputs a message.

Name convention forPCMCIA card

Preconditions

Precondition

3 Configuring 08.01


3.10 Installing HMI Embedded Win 32 on a PCU50

During initial start-up, Windows NT and the SINUMERIK 840D systemsoftware are loaded to the hard disk of the PCU.The hard disk of the PCU is pre-partitioned for SINUMERK 840D operationand further SINUMERIK applications on delivery and the software required fora 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.

PCU

Primary partition Primary patition Primary patitionExtended partitionwith logic driveactive

C: FAT16

DOS Tools

E NTFS

WinNT

F NTFS

840D SystemHMI, further applications

D: FAT16

TMP , Images,Install, Updates

Hard disk

Partitioning during initial start-up

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 harddisk (partitions C:, E: and F:).

The available range of versions remains stored in D:\IMAGES so that you canload them to replace the version selected during initial start-up at a later pointin 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

Principe

Select a version

08.01 3 Configuring


3.10.1 Installing via a parallel link with a FAT16 file structure

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 thePCU. It can be operated under DOS / Win3.11 / Win95 / Win98 only if thePG/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. Theactual installation is carried out by Windows NT on the next boot provided thesoftware includes an exe file, e.g. "setup.exe".

Important:

Before you attempt to install the software, make sure that there is sufficientmemory available on the partition D of the hard disk.

You must use the parallel (not the serial) interface to transfer the HMIsoftware.

1. Switch off the PCU2. 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. Copy directory HMI_Advanced from the CD to drive C:\ on the hard diskof your PG/PC and rename it "MMC2". If there is insufficient memoryspace 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 softwarecannot be installed directly from the CD.

4. The HMI software installation is started when you open the WindowsStart menu and select Run Intersvr C: (or the drive on which directoryMMC2 is stored).IMPORTANT: If your PC/PG is in this state, the PCU must be switchedoff. (If the PCU is switched on, switch it off now).

5. Switch on the PCU, select the "Service Menu" (invisible menu option) inthe boot manager.

Preconditions

Principle

Transmission

Sequence ofoperations

3 Configuring 08.01


The following menu is displayed:

PLEASE SELECT:

1 Install/Update SINUMERIK System2 SINUMERIK Tools and Options3 DOS Shell4 Start Windows NT (Service Mode)5 SINUMERIK System Check7 Backup/Restore8 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- ServiceThe following menu is displayed

PLEASE SELECT MEDIUM:

1 Install from Floppy Disk2 Install via Serial/Parallel Line3 Install from Network Drive

5 REBOOT

9 Return to Main Menu

Your Choice [Your Choice [1,2,3,5,9]?

7. Select menu option 2 Install via Serial/Parallel Line.8. The data transfer begins. The system boots to Windows NT and the

installation is started automatically.9. Select a language10. Select a technology: Milling or turning11. The system lists all the entries you have made.12. The PCU is rebooted once the installation is complete.13. End PC/PG server mode by pressing Alt + F4.

08.01 3 Configuring


3.10.2 Installing via a parallel link with a FAT32 file structure


Important:


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.

You must use the parallel (not the serial) interface to transfer the HMIsoftware installation.

This method must be used when your PC/PG has only partitions with aFAT32 file structure.

1. Copy interlnk.exe from the HMI directory on the CD toWINDOWS\COMMAND on the PC/PG. Insert the following line inconfig.sys:device=c:\windows\command\interlnk.exe/AUTO

2. Switch off the PCU.3. Using the parallel connecting cable (PC-Link cable, LapLink cable),

connect the parallel port LPT on the PC to port LPT on the PCU.4. Switch on the PCU,

select the "Service Menu" [invisible menu option] in the boot manager.

PLEASE SELECT:


9 End (Warmboot)

Your Choice[1, 2, 3, 4, 5, 7, 8, 9]?

Principe

Preconditions

Transmission

When to use


3 Configuring 08.01


5. Press key 8The system requests you to enter a password by displaying:

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 CDto directory D:\INSTALL on the PCU. When the SW has beentransferred, end INTERSVR on the PCU by pressing Alt + F4. Thesystem will boot to Windows NT.

8. In Win NT: The SW will now be installed automatically by means ofInstallShield from the PCU. You can operate the InstallShield promptboxes with TAB and the cursor keys (TAB corresponds to the END keyon the OP0xx).

9. The system powers up after the PCU has rebooted.

3.10.3 Installing via a network connection


Important:


Note

If you are using a different language version of the Windows system, theterms used in the following setting operations may be different. Thesequence of operations as specified below, however is always the same.

� 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)

Principle

Preconditions

08.01 3 Configuring


� Shared access to directoryGive 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" accessauthorization).Windows 95:Enter a share name (e.g. HMINEW).Enter access authorization.Specify a password if applicable.

� Cable connectedCable for point-to-point connection in Ethernet port: Ethernet cable of type"Converted Twisted Pair cable".

� Windows 95/98:Share-level access control selectedunder Start Settings Control Panel Network symbol: Access Controltabs "Share-level access control"

While the PCU is booting (after control is switched off and on again):

1. Select the "Service Menu" [invisible menu option] in the bootmanager.


PLEASE SELECT:


9 End (Warmboot)

Your Choice [1,2,3,4,5,7,8,9]?

2. Select option 1.

The system requests you to enter a password by displaying:

passwd:

- System- Manufacturer- Service


3 Configuring 08.01



PLEASE SELECT MEDIUM:1 Install from Floppy Disk2 Install via Serial/Parallel Line3 Install from Network Drive

5 REBOOT

9 Return to Main Menu

Your Choice [1,2,3,5,9]?

3. Select option 3.


PLEASE SELECT:

1 Connect to Network Drive2 Show connected Network Drives3 Disconnect from all Network Drives

4 Change Install Directory5 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 whenaccess to the directory was shared.

� Password entry can be confirmed.

� Enter the drive letter on the PCU via which the directory must beaccessed (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) H: (\\r3344\HMINEW)Install Directory F:\Install

Connect to networkdrive

08.01 3 Configuring


You can change the installation directory on the connected computer:

PLEASE SELECT:

1 Connect to Network Drive2 Network Drives3 Disconnect from all 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: F:\INSTALLNew Install Directory: H:\HMI_INST

You can now start the transmission:

PLEASE SELECT:


4 Change Install Directory5 Install from H:\HMI_INST


Your Choice [1,2,3,4,5,9]?

7. Select option 5.

� The system starts the transmission from the external computer to thePCU.

� 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 somecases.

The system checks whether directory D:\INSTALL already contains files.

NoteIf the SW cannot be copied to directory D:\INSTALL on the PCU, then thesystem cannot start the installation.

Change installationdirectory of theconnected drive

Install

3 Configuring 08.01


You can display all the connections to the PG/PC:

PLEASE SELECT:




Your Choice [1,2,3,4,5,9]?

8. Select option 2

The current status of the connected drives is displayed:

Status Local Name Remote NameOK H: \\r3344\HMI_INSTOK J: \\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): -none-Install Directory: H:\HMI_INST

When you exit the menu, you will be prompted to confirm whether theinitialized network parameters must be saved.

■

Show connectednetwork drives

Disconnect from allnetwork drives

Back to previousmenu

© Siemens AG 2001. All rights reservedSINUMERIK 840D/810D HMI Embedded Configuring Package (PJE) � 08.01. Edition 4-93

Working with Microsoft Visual C andHMI 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

4

4 Working with Microsoft Visual C and HMI Embedded 08.01


4.1 Using MS Visual Studio 6.0

Make only a few changes at one time.

As a result of the modeled dependencies in the make files, only edited files areregenerated. You will save only a nominal amount of time by generating newfiles at greater time intervals, but it will be more difficult to localize the causesof errors.

Reduce the risk of editing files by mistake.

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

You can change the project settings by selecting menu optionsPROJECT SETTINGS in Visual Studio. You can, for example, extend theinclude paths or set the compiler flags.

Since there are numerous options and settings for projects in Visual Studio, itwould not be sensible to list all of them here. Instead, only the most importantsettings are given below. If your application does not work when you set theproject in this way, you should compare your settings with those of a projectthat does work or with the appropriate template files stored inmmc100pj\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

General notes

Compiler and linkeroptions

08.01 4 Working with Microsoft Visual C and HMI Embedded

© Siemens AG 2001. All rights reservedSINUMERIK 840D/810D HMI Embedded Configuring Package � 08.01 Edition 4-95

For commands in configuring source files which extend over several lines, thenumber of the line containing the closing bracket or the statement end isalways specified as the line number for error or warning messages.With a configuring macro, for example, you should not assume that it is the lastparameter that is incorrectly assigned. By pressing key <F4> you can scrollthrough the messages of any error or warning list; MS Visual Studioautomatically 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.

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 ADD TOPROJECT FILES .

Select the project ApplicationName_li in the combobox "Insert Into" at the endof the dialog.

Mark the file to be inserted in the selection window and add it to the project byclicking 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 Studioscreen ). You may need to open folder ApplicationName\Source Files first.Then press the DELETE key.

Projects are saved in Visual Studio with the higher-level workspace. To do this,select menu options FILE SAVE WORKSPACE.

The best way to convert an old MSVC project to an MS Visual Studio project isas follows:

- Once you have copied the application directory to the new Screen Kit, youmust save it, mmc100pj\Proj\App\ApplicationName,

...\Proj\App\H\ApplicationName.h,

...\Proj\App\H\AApplicationName.h and

...\Sck\Cfg\ApplicationName.cfgcopy it to another directory and remove the originals.

- You must remove any copied text files so that the application manager cancreate new ones.

Delete ApplicationName.txt andAApplicationName.txt from foldersmmc100pj\Proj\Text\Language\.

Errors, warnings :Specification of linenumbers

Add to a project

Save a project

Convert an MSVCproject to VisualStudio.



- Create a new application using the Application Manager. It should have thesame name as the old MSVC application. ( Subsection 3.2.2: Creating anew 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 bedeleted.- Copy the contents of the old application folder into the new folder

mmc100pj\Proj\App\ApplicationName. The source, header and textfiles created by the Application Manager will also be overwritten at thesame time.

- Copy the text header files ApplicationName.h and AApplicationName.hto ...\Proj\App\H.

- Copy the old configuration file ApplicationName.cfg into foldermmc100pj\Sck\Cfg, overwriting the newly created file again.

Note

If you want to use any new functions of the Screen Kit, it is advisable tocompare the CFG files line by line and to insert only the lines you need into thenew CFG file.

- Open the application with Visual Studio. ( Menu options FILE OPENWORKSPACE)

- Delete the source and header files generated by the Application Managerfrom project ApplicationName_li.- Select the "File View" tab in the workspace window ( normally at left-

hand 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. Makesure that you have selected project ApplicationName_li at "Insert into" inthe Open dialog.- The source file ap_l_dir.c is not copied since it is stored in the

ApplicationName project already.

The Visual Studio editor allows you to color-highlight the different elements(source code, comments, etc.) in the text for better identification. You will findthe appropriate dialog under TOOLS OPTIONS FORMAT. To alter thecoloring of the Screen Kit keywords, for example, you must select "UserDefined Keywords" in the COLORS list.

You can assign keyboard shortcuts to menu commands in dialogTOOLS CUSTOMIZE KEYBORD tab. You will find the Screen Kit tools inthe Tools category under UserToolxx.

Tip: Color-highlightedkeywords, editorsettings

Tip: Definingkeyboard shortcuts



If you add the argument "-k $(CurText)" to the argument entries for the ScreenKit online helps IN FRONT OF the help file path underTOOLS CUSTOMIZE TOOLS, the currently selected word is automaticallysought and displayed when you open the help file (e.g. the explanation of theRECTANGLE macro is displayed if the cursor is positioned on this word whenyou open the configuring syntax help file).

Important

The program WINHLP32.EXE displays an index list if the word has not beenfound. If you end WINHLP32.EXE in this state, part of the memory will not bereleased again!!! For this reason, make sure that you always display a topicbefore you end WINHLP32.EXE.

Use the MACRO functions of Visual Studio to automate frequently repeatedoperations, e.g. it is easy to record a macro which makes the appropriate entryin ap_l_dir.h after you have created a new list. ( selectBEGIN_xxx(NEW_LIST>), copy, insert in ap_l_dir.h and replace BEGIN_ withEXTERN_.)Macro functions are stored under TOOLS MACRO..., for detailed informationplease refer to your Visual Studio guide.

If you are working "simultaneously" on several applications, you can integrateall projects into one working area by selecting menu optionsPROJECT INSERT PROJECT INTO WORKSPACE. Unfortunately, VisualStudio "forgets" the project dependencies in this case. You must thereforeenter them again under PROJECT DEPENDENCIES. ( Please note: Theproject <XXX> is always dependent on <XXX>_LI ).

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 optionalname by selecting FILE SAVE AS.

Tip: Automatic SDKhelp

Tip:Macros

Tip:One workspace forall projects

Tip:Troubleshooting



4.2 Using the MSVC Workbench

Make only a few changes at one time.

As a result of the modeled dependencies in the make files, only edited files areregenerated. You will save only a nominal amount of time by generating newfiles at greater time intervals, but it will be more difficult to localize the causesof errors.

Reduce the risk of editing files by mistake.

Select the write protection option in the File Open window of the MSVCWorkbench 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 andavailable again, but write-protected as icons, when you restart the MSVCWorkbench.

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 underOPTIONS PROJECT.

For commands in configuring source files which extend over several lines, thenumber of the line containing the closing bracket or the statement end isalways specified as the line number for error or warning messages.

With a configuring macro, for example, you should not assume that it is the lastparameter that is incorrectly assigned.

With ApplicationName.mak make files, you can press key <F4> to scrollthrough the messages of any error or warning list; in this case, the MSVCWorkbench automatically positions the cursor on the errored line in thecorresponding file.

To generate your application complete, you must always use TOOLS GENERATE SL.DAT.

General notes

Compiler and linkeroptions

Errors, warnings :Specification of linenumbers

Working efficiently



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 byclicking on ADD.

The dependencies of the files in the project are generated again.

Note

In this case, the MSVC Workbench searches through only those directoriesthat were entered under OPTIONS DIRECTORIES as the Workbench wasinitialized. If an include file is not found in any of these paths, no warning isoutput!

Generating new dependencies

As soon as you insert an additional include statement in a C file, you mustgenerate 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 exitthe MSVC Workbench.

The MSVC Workbench does not unfortunately offer an explicit 'PROJECTSAVE' 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 closingand then reopening the project.

The MSVC Workbench editor allows you to color-highlight the differentelements (source code, comments, etc.) in the text for better identification. Todo so, select menu commands OPTIONS COLOR.

The MSVC Workbench uses an output window that is overwritten when youcall 'Build' again. You can, however, save the contents of this window under anoptional name by selecting FILE SAVE AS.

Add to projects

Save a project

Editorsettings

Error documentation



4.3 Known restrictions and incompatibilities

Some ASCII editors (particularly the older versions) insert control characters inthe text to represent special characters, TABs, etc. or characters from the toparea 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 ensurethat they are integrated correctly. This is due to the fact that the Windowscharacter set deviates from the standard.

This always applies to text changes made via the Installation Kit.

■

Text editors AEDITand VI (for DOS)


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 Key assignments in PC mode .......................................................................5-1055.4.1 Mode of operation of "Dialog" keys ...............................................................5-107

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

5

5 Operating HMI Embedded 08.01


5.1 HMI Embedded - test mode on a PC

The HMI Embedded configuring package allows you to run your configurationsthrough "a quick check" on a PC. This saves you the time and work oftransferring them to the appropriate hardware when you "just" want to checkthe 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 filemmc100pj\Bin_sim\mmc0.ini:

pc_test = 0 PC MPI mode

pc_test = 1 PC simulation mode

The HMI Embedded software is started when you select menu optionsTOOLS PC-SIMULATION in the MSVC Workbench.You can now operate the software in the same way as if it were installed on thehardware.

Description

To activate

08.01 5 Operating HMI Embedded


5.2 PC simulation mode

In PC simulation mode, part of the NC or PLC data is emulated by a simulationprogram. This mode is designed solely to allow you to test the operatorinterface layout and the menu control. The data contents may deviatesignificantly from real conditions in actual operation.

You can identify PC simulation mode by the alarm 100650 "No NC/PLC found!Simulating NC/PLC!"

The configuring package has been installed properly and an executableapplication is available, i.e. the files sl.dat and mmc0conf.bin must be stored indirectory mmc100pj\Bin_sim.

Open the MSVC Workbench and start PC simulation by selecting menuoptions TOOLS PC Simulation.

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 releaseboth keys and press RETURN )

or

press the Cancel button ⌧ in window "HMI-Embedded-Win32"

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.

Description

Preconditions

To open

To close

Typical errors in PCsimulation mode



5.3 PC MPI mode

In PC MPI mode the HMI Embedded software communicates with an NC or aPLC. The logical operating characteristics correspond to real conditions on theHMI Embedded hardware.

In PC MPI mode you can connect your PC directly to an NC using an MPIcable and operate the NC using the HMI Embedded SW.

The keys of the integrated MCP interface on the HT6 cannot be operated fromthe PC. It is not safe to operate a machine because there is no emergencystop or enabling key. You cannot therefore start/stop/reset programs, moveaxes or switch operating modes from the PC.

The configuring package has been installed properly and an executableapplication is available, i.e. the files si.dat and mmc0conf.bin must be stored indirectory mmc100pj\Bin_sim.

Your PC has a functional MPI interface, e.g. a Simatic NET CP5611 MPI cardwith corresponding drivers.

Your PC is connected to the NC via an MPI cable.

Please read the MPI interface documentation for further details.

Open the MSVC Workbench and start PC simulation by selecting menuoptions TOOLS PC Simulation.

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 releaseboth keys and press RETURN )

or

press the Cancel button ⌧ in window "HMI-Embedded-Win32"

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

Description

Restriction in relationto HT6

Preconditions

To open

To close

Typical errors in PCMPI mode



5.4 Key assignments in PC mode

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.

The HMI Embedded keys are mapped onto the standard PC MFII keys asfollows:

Symbol Description Key on MFIIArea switchover key F10

Display basic menu

Machine area key Shift F10

Display machine area

Recall key F9

Return to previous menu ifsymbol 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

Restriction

Description



Description Key on MFIIAcknowledge alarm key Escape key

To acknowledge alarms with thisreset symbol

Window selection key Home

Change the active window

Select / toggle key "5" on numeric keypadwithout NumLock

Selection key for values set infields labeled with this keysymbol.

Cursor keys,paging keys,Home, End

Navigation keypadNavigation in windows and fields

Cursor keys, paging keys(Pgup, dn) Home, End

Digits, "." Numeric keypad Digits, "."Numerical inputs

Letters,specialcharacters

Alphabetic charactersAlphabetic inputs

Letters,special characters

Arrow to left, Backspace keyDeletes preceding character

Backspace

Softkey1 -Softkey8

Horizontal softkeysMenu control

F1-F8

Vert. softkey1-Vert. softkey8

Vertical softkeysMenu control

Shift F1-F8

JOG JOG mode Alt F1

MDA MDA mode Alt F2

AUTO AUTO mode Alt F3

Teach In Teach key Alt F4

Control PanelFunction

CPF keySimulated keys of MCPintegrated in HT6

Alt 7

U1- U8 User keys Ctrl F1-F8

S1- S2 Start special keys Ctrl F9-F10



5.4.1 Mode of operation of "Dialog" keys

You can normally navigate between fields using the cursor and paging keys.

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.

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.

You can terminate your field inputs correctly by pressing the Input key orexiting the field with the Cursor Up or Cursor Down key.

The inputs in your field will be discarded if your press the Edit key again in Editmode.

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 enteredin the field again automatically.

In Edit mode you can delete the character positioned immediately to the left ofthe cursor using the Backspace key.

Depending on how fields have been configured, they feature a so-called pocketcalculator function which allows you to add or subtract values in relation to thefield 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.

Navigation mode

Edit mode "Overwritefield contents"

Edit mode "Changefield contents"

Terminate an input

Undo an input

Delete individualcharacters

Pocket calculatorfunctions Additionand Subtraction



5.5 mmc0_con.cfg: Emulation of variablesBy making special entries in file mmc100pj\Bin_sim\mmc0_con.cfg you canselectively preset NC variables and HMI Embedded notebook entries to valuesfor 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 endingwith H.

e.g. 130 (decimal) --> 82 not: 0x82 or 82H

d_typ Data type (hexadecimal)3 CHAR4 UNSIGNED6 DWORD7 LONG8 FLOAT0F (Hex)DOUBLE13 (Hex)STRING (see mmc100pj\Public\Portab.h)

sy_id Syntax identification (hexadecimal)82 (Hex) NUMERIK82 (Hex) SIMODRIVE10 (Hex) PLC14 (Hex) HMI Embedded(see mmc100pj\Public\Varid_li.h)

Ar_Unit NUMERIK (area and unit (one byte) decimal):01 NCK33 ... 63 Mode group 1 to mode group 365 ... 95 Channel 1 to channel 3197 ... 127 Axis 1 to axis 31129 ... 159 TOA1 to TOA31161 ... 191 FDD1 to FDD31193 ... 223 MSD1 to MSD31

Cl Column (decimal)

(see mmc100pj\Public\Column_id.h)

Line Line (decimal)

Description

Syntax

Parameters



B_typ Block type (decimal)

(s. mmc100pj\Public\B_type.h)

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 Value0 4 '130 65 1 1 16 1' "4"#P_C_Y_numGeoAxes0 4 '130 65 2 1 16 1' "1"# " _numAuxAxes0 4 '130 65 3 1 16 1' "4"# " _numMachAxes0 4 '130 65 4 1 16 1' "4"# " _numSpindles0 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

■

Example

08.01 Appendix

© Siemens AG 2001. All rights reservedSINUMERIK 840D/810D HMI Embedded Configuring Package (PJE) � 08.01 Edition A-111

Appendix

References


/BU/ SINUMERIK 840D/840Di/810D/802S, C, DOrdering InformationCatalog NC 60Order no.: E86060-K4460-A101-A8-7600 (English)

/ST7/ SIMATICSIMATIC S7 Programmable Logic ControllersCatalog ST 70Order no.: E86060-K4670-A111-A3

/Z/ SINUMERIK, SIROTEC, SIMODRIVEAccessories and Equipment for Special-Purpose MachinesCatalog NC ZOrder no.: E86060-K4490-A001-A7-7600 (English)

Electronic Documentation

/CD8/ The SINUMERIK SystemDOC ON CD (01.02 Edition)(with all SINUMERIK 840D/840Di/810D andSIMODRIVE publications)Order no.: 6FC5 298-6CA00-0BG2

Appendix 08.01

© Siemens AG 2001. All rights reservedA-112 SINUMERIK 840D/810D HMI Embedded Configuring Package (PJE) � 08.01 Edition

User Documentation

/AUK/ SINUMERIK 840D/810DAutoTurn Operation, Short Guide (09.01 Edition)Order no.: 6FC5 298-4AA30-0BP3

/AUP/ SINUMERIK 840D/810DAutoTurn Graphic Programming System (09.01 Edition)Operator's GuideProgramming / SetupOrder no.: 6FC5 298-4AA40-0BP3

/BA/ SINUMERIK 840D/810DMMC Operator's Guide (10.00 Edition)Order no.: 6FC5 298-6AA00-0BP0

/BAD/ SINUMERIK 840D/840Di/810DOperator's Guide: HMI Advanced (09.01 Edition)Order no.: 6FC5 298-6AF00-0BP1

BEM/ SINUMERIK 840D/840Di/810DOperator's Guide: HMI Embedded (09.01 Edition)Order no.: 6FC5 298-6AC00-0BP1

/BAE/ SINUMERIK 840D/810DUnit Operator Panel Operator's Guide (04.96 Edition)Order no.: 6FC5 298-3AA60-0BP1

/BAH/ SINUMERIK 840D/810DOperator's Guide HAT 6 (new HPU) (09.01 Edition)Order no.: 6FC5 298-0AD60-0BP2

/BAK/ SINUMERIK 840D/810DOperation, Short Guide (02.01 Edition)Order no.: 6FC5 298-6AA10-0BP0

/BAM/ SINUMERIK 810D/840DManualTurn Operator's Guide (10.01 Edition)Order no.: 6FC5 298-6AD00-0BP0

/BAS/ SINUMERIK 840D/810DShopMill Operator's Guide (10.01 Edition)Order no.: 6FC5 298-6AD10-0BP0

08.01 Appendix


/BAT/ SINUMERIK 840D/810DShopTurn Operator's Guide (03.01 Edition)Order no.: 6FC5 298-6AD50-0BP0

/BAP/ SINUMERIK 840D/840Di/810DHandheld Programming Unit Operator's Guide (04.00 Edition)Order no.: 6FC5 298-5AD20-0BP1

/BNM/ SINUMERIK 840D840Di//810DMeasuring Cycles User's Guide (10.00 Edition)Order no.: 6FC5 298-6AA70-0BP0

/DA/ SINUMERIK 840D/840Di/810DDiagnostics Guide (09.01 Edition)Order no.: 6FC5 298-6AA20-0BP1

/KAM/ SINUMERIK 840D/810DManualTurn Short Guide (11.98 Edition)Order no.: 6FC5 298-2AD40-0BP0

/KAS/ SINUMERIK 840D/810DShopMill Short Guide (01.98 Edition)Order no.: 6FC5 298-2AD30-0BP0

/PG/ SINUMERIK 840D/840Di/810DFundamentals Programming Guide (09.01 Edition)Order no.: 6FC5 298-6AB00-0BP1

/PGA/ SINUMERIK 840D/840Di/810DAdvanced Programming Guide (09.01 Edition)Order no.: 6FC5 298-6AB10-0BP1

/PGK/ SINUMERIK 840D/840Di/810DProgramming, Short Guide (02.01 Edition)Order no.: 6FC5 298-6AB30-0BP1

/PGM SINUMERIK 840D/840Di/810DISO Milling Programming Guide (10.01 Edition)Order no.: 6FC5 298-6AC20-0BP1

/PGT/ SINUMERIK 840D/840Di/810DISO Turning Programming Guide (10.01 Edition)Order no.: 6FC5 298-6AC10-0BP1

Appendix 08.01


/PGZ/ SINUMERIK 840D840Di//810DCycles Programming Guide (09.01 Edition)Order no.: 6FC5 298-6AB40-0BP1

/PI/ PCIN 4.4Software for Data Transfer to/from the MMC ModuleOrder no.: 6FX2 060-4AA00-4XB0 (Ger., Eng., Fr.)Order from: WK Fürth

/SYI/ SINUMERIK 840DiSystem Overview (02.01 Edition)Order no.: 6FC5 298-6AE40-0BP0


a) Lists

/LIS/ SINUMERIK 840D/840Di/810DSIMODRIVE 611DLists (09.01 Edition)Order no.: 6FC5 297-6AB70-0BP1

b) Hardware

/BH/ SINUMERIK 840D840Di//810DOperator Components Manual (HW) (09.01 Edition)Order no.: 6FC5 297-6AA50-0BP1

/BHA/ SIMODRIVE SensorAbsolute Encoder with Profibus DPUser's Guide (HW) (02.99 Edition)Order no.: 6SN1 197-0AB10-0YP1

/EMV/ SINUMERIK, SIROTEC, SIMODRIVEEMC Installation Guideline (06.99 Edition)Planning Guide (HW)Order no.: 6FC5 297-0AD30-0BP1

08.01 Appendix


/PHC/ SINUMERIK 810DConfiguration Manual (HW) (12.01 Edition)Order no.: 6FC5 297-4AD10-0BP1

/PHD/ SINUMERIK 840DNCU 561.2-573.2 Configuration Manual (HW) (09.01 Edition)Order no.: 6FC5 297-6AC10-0BP1

/PHF/ SINUMERIK FM NCNCU 570 Configuration Manual (HW) (04.96 Edition)Order no.: 6FC5 297-3AC00-0BP0

/PMH/ SIMODRIVE SensorMeasuring System for Main Spindle DrivesConfiguration/Installation Guide, SIMAG-H (HW) (05.99 Edition)Order no.: 6SN1197-0AB30-0BP0

c) Software

/FB1 SINUMERIK 840D/840Di/810DDescription of Functions, Basic Machine (Part 1) (09.01 Edition)(the various sections are listed below)Order no.: 6FC5 297-6AC20-0BP1

A2 Various Interface SignalsA3 Axis Monitoring, Protection ZonesB1 Continuous-Path Mode, Exact Stop and Look AheadB2 AccelerationD1 Diagnostic ToolsD2 Interactive ProgrammingF1 Travel to Fixed StopG2 Velocities, Setpoint/Actual Value System, Closed-Loop ControlH2 Auxiliary Function Output to the PLCK1 Mode Group, Channel, Program OperationK2 Axes, Coordinate System, Frames,

Actual-Value System for Workpiece, Zero Offset ExternalK4 CommunicationN2 EMERGENCY STOPP1 Transverse AxesP3 Basic PLC ProgramR1 Reference Point ApproachS1 SpindlesV1 FeedratesW1 Tool Offset

/FB2/ SINUMERIK 840D/840Di/810D(CCU2)Description of Functions, Extended Functions (Part 2) (09.01 Edition)including FM NC: Turning, Stepper Motor(the varius sections are listed below)Order no.: 6FC5 297-6AC30-0BP1

A4 Digital and Analog NCK I/Os

B3 Several Operator Panels and NCUsB4 Operation via PG/PCF3 Remote DiagnosisH1 Jog with/without Handwheel

Appendix 08.01


K3 CompensationsK5 Mode Groups, Channels, Axis ReplacementL1 FM NC Local BusM1 Kinematic TransformationM5 MeasurementN3 Software Cams, Position Switching SignalsN4 Punching and NibblingP2 Positioning AxesP5 OscillationR2 Rotary AxesS3 Synchronous SpindlesS5 Synchronized Actions (up to and including SW 3 / then /FBSY/)S6 Stepper Motor ControlS7 Memory ConfigurationT1 Indexing AxesW3 Tool ChangeW4 Grinding

/FB3/ SINUMERIK 840D/840Di/810D(CCU2)Description of Functions, Special Functions (Part 3) (09.01 Edition)(the various sections are listed below)Order no.: 6FC5 297-6AC80-0BP1

F2 3 to 5-Axis TransformationG1 Gantry AxesG3 Cycle TimesK6 Contour Tunnel MonitoringM3 Coupled Motion and Master/Slave CouplingsS8 Constant Workpiece Speed for Centerless GrindingT3 Tangential ControlTE1 Clearance ControlTE2 Analog AxesTE3 Speed / Torque Coupling Master-SlaveTE4 Transformation Package HandlingTE5 Setpoint ExchangeTE6 MCS CouplingTE7 Retrace SupportTE8 Cycle-Independent Path-Synchronous Switching Signal OutputV2 PreprocessingW5 3D Tool Radius Compensation

/FBA/ SIMODRIVE 611D/SINUMERIK 840D/810DDescription of Functions, Drive Functions (09.01 Edition)(the various sections are listed below)Order no.: 6SN1 197-0AA80-0BP7

DB1 Operational Messages/Alarm ReactionsDD1 Diagnostic FunctionsDD2 Speed Control LoopDE1 Extended Drive FunctionsDF1 EnablesDG1 Encoder ParameterizationDM1 Calculating Motor / Power Section Parameters and Controller DataDS1 Current Control LoopDÜ1 Monitoring Functions/Limitations

08.01 Appendix


/FBAN/ SINUMERIK 840D/SIMODRIVE 611 DIGITALDescription of Functions ANA MODULE (02.00 Edition)Order no.: 6SN1 197-0AB80-0BP0

/FBD/ SINUMERIK 840DDescription of Functions Digitizing (07.99 Edition)Order no.: 6FC5 297-4AC50-0BP0

DI1 Installation and StartupDI2 Scanning by Tactile Sensor (scancad scan)DI3 Scanning by Laser (scancad laser)DI4 Milling Program Generation (scancad mill)

/FBDN/ CAM Integration DNC NT-2000Description of FunctionsSystem for NC Data Management and Data Distribution (05.00 Edition)Order no.: 6FC5 297-5AE50-0BP1

/FBFA/ SINUMERIK 840D/840Di/810DDescription of Functions (09.01 Edition)ISO Dialects for SINUMERIKOrder no.: 6FC5 297-6AE10-0BP1

/FBFE/ SINUMERIK 840D/810DDescription of Functions Remote Diagnosis (09.01 Edition)Order no.: 6FC5 297-0AF00-0BP1

FE1 Remote DiagnosisFE2 Alarm-Driven Notification by E-mail: @Event

/FBHLA/ SINUMERIK 840D/SIMODRIVE 611 digitalDescription of Functions HLA Module (04.00 Edition)Order no.: 6SN1 197-0AB60-0BP2

/FBMA/ SINUMERIK 840D/810DDescription of Functions ManualTurn (10.01 Edition)Order no.: 6FC5 297-6AD50-0BP0

/FBO/ SINUMERIK 840D/810DDescription of Functions (09.01 Edition)OP 030 Operator Interface Configuration(the various sections are listed below)Order no.: 6FC5 297-6AC40-0BP0

BA Operator's GuideEU Development Environment (Configuring Package)PS Online only: Configuring Syntax (Configuring Package)PSE Introduction to Configuring the Operator InterfaceIK Screen Kit: Software Update and Configuration

Appendix 08.01


/FBP/ SINUMERIK 840DDescription of Functions C PLC Programming (03.96 Edition)Order no.: 6FC5 297-3AB60-0BP0

/FBR/ SINUMERIK 840D/810DDescription of Functions SINCOM Computer Link (02.00 Edition)Order no.: 6FC5 297-5AD60-0BP0

NFL Interface to Host ComputerNPL Interface to PLC/NCK

/FBSI/ SINUMERIK 840D/SIMODRIVEDescription of Functions SINUMERIK Safety Integrated (03.01 Edition)Order no.: 6FC5 297-6AB80-0BP0

/FBSP/ SINUMERIK 840D/810DDescription of Functions ShopMill (10.01 Edition)Order no.: 6FC5 297-5AD80-0BP1

/FBST/ SIMATICDescription of Functions (11.98 Edition)FM STEPDRIVE/SIMOSTEPOrder no.: 6SN1 197-0AA70-0YP3

/FBSY/ SINUMERIK 840D/810DDescription of Functions Synchronized Actions (09.01 Edition)for Wood, Glass, Ceramics, PressesOrder no.: 6FC5 297-6AD40-0BP1

/FBT/ SINUMERIK 840D/810DDescription of Functions ShopTurn (03.01 Edition)Order no.: 6FC5 297-6AD70-0BP0

/FBTD/ SINUMERIK 840D/810DDescription of FunctionsSINTDI Tool Data Information System with Online Help (03.01 Edition)Order no.: 6FC5 297-6AE00-0BP0

/FBU/ SIMODRIVE 611 universalDescription of Functions (05.00 Edition)Closed-Loop Control Components for Speed Controland PositioningOrder no.: 6SN1 197-0AB20-0BP3

/FBW/ SINUMERIK 840D/810DDescription of Functions Tool Management (10.01 Edition)Order no.: 6FC5 297-6AC60-0BP1

08.01 Appendix


/HBI/ SINUMERIK 840DiManual (07.01 Edition)Order no.: 6FC5 297-6AE50-0BP0

/KBU/ SIMODRIVE 611 universalShort Guide (05.00 Edition)Closed-Loop Control Components for Speed ControlOrder no.: 6SN1 197-0AB40-0BP3

/PJE/ SINUMERIK 840D/810DHMI Embedded Configuring Package (08.01 Edition)Description of Functions: Software Update, Configuration,InstallationOrder no.: 6FC5 297-6EA10-0BP0(The PS Configuring Syntax publication is included with the softwareand is available as a pdf)

/PJFE/ SIMODRIVEPlanning Guide Integrated Synchronous Motors 1FE1 (08.01 Edition)Three-Phase AC Motors for Main Spindle DrivesOrder no.: 6SN1 197-0AC00-0BP1

/PJLM/ SIMODRIVEPlanning Guide Linear Motors (06.01 Edition)(on request)ALL General Information about Linear Motors

1FN1 Three-Phase AC Linear Motor 1FN11FN3 Three-Phase AC Linear Motor 1FN3CON Cables & ConnectionsOrder no.: 6SN1 197-0AB70-0BP2

/PJM/ SIMODRIVEPlanning Guide MotorsThree-Phase AC Motors for Feed and (09.00 Edition)Main Spindle DrivesOrder no.: 6SN1 197-0AA20-0BP4

/PJU/ SIMODRIVE 611Order no.: 6SN1 197-0AA00-0BP5

/POS1/ SIMODRIVE POSMO AUser's Guide (04.01 Edition)Distributed Positioning Motor on PROFIBUS DP,Order no.: 6SN2 197-0AA00-0BP2

/POS2/ SIMODRIVE POSMO AInstallation Guide (enclosed with each POSMO A) (12.98 Edition)Order no.: 462 008 0815 00

Appendix 08.01


/POS3/ SIMODRIVE POSMO SI/CD/CADistributed Servo Drive Technology, User's Guide (01.01 Edition)Order no.: 6SN2 197-0AA20-0BP0

/S7H/ SIMATIC S7-30Manual: Setup, CPU Data (hardware) (10.98 edition)Reference Manual: Module DataOrder no.: 6ES7 398-8AA03-8AA0

/S7HT/ SIMATIC S7-300STEP 7 Manual, Fundamentals, V. 3.1 (03.97 Edition)Order no.: 6ES7 810-4CA02-8AA0

/S7HR/ SIMATIC S7-300Manual (03.97 Edition)STEP 7, Reference Manuals, V. 3.1Order no.: 6ES7 810-4CA02-8AR0

/S7S/ SIMATIC S7-300FM 353 Positioning Module for Stepper Drive (04.97 Edition)Order together with the Configuring Package

/S7L/ SIMATIC S7-300FM 354 Positioning Module for Servo Drives (04.97 Edition)Order together with the Configuring Package

/S7M/ SIMATIC S7-300FM 357 Multi-Axis Module for Servo or Stepper Drives (10.99 Edition)Order together with the Configuring Package

/SHM/ SIMODRIVE 611Manual (01.98 Edition)Single-Axis Positioning Control for MCU 172AOrder no.: 6SN 1197-4MA00-0BP0

/SP/ SIMODRIVE 611-A/611-D,SimoPro 3.1Program for Configuring Machine Tool DrivesOrder no.: 6SC6 111-6PC00-0AA❏ ,Order from: WK Fürth

08.01 Appendix


d) Installationand Start-up/IAA/ SIMODRIVE 611A

Installation & Start-up Guide (10.00 Edition)(incl. description of SIMODRIVE 611Dstartup software)Order no.: 6SN 1197-0AA60-0BP6

/IAC/ SINUMERIK 810DInstallation & Start-up Guide (12.01 Edition)(incl. description of SIMODRIVE 611Dstartup software)Order no.: 6FC5 297-4AD20-0BP1

/IAD/ SINUMERIK 840D/SIMODRIVE 611DInstallation & Start-up Guide (09.01 Edition)(incl. description of SIMODRIVE 611D startup software)Order no.: 6FC5 297-6AB10-0BP1

/IAF/ SINUMERIK FM-NCInstallation & Start-up Guide (07.00 Edition)Order no.: 6FC5 297-3AB00-0BP1

/IAM/ SINUMERIK 840D/840Di/810DHMI/MMC Installation & Start-up Guide (11.01 Edition)Order no.: 6FC5 297-6AE20-0BP1

AE1 Updates/OptionsBE1 User Interface OptionsHE1 Online HelpIM2 HMI Embedded Installation and StartupIM4 HMI Advanced Installation and StartupTX1 Generating Foreign Language Texts

Appendix 08.01


08.01 Index

© Siemens AG 2001. All rights reservedSINUMERIK 840D/810D HMI Embedded Configuring Package (PJE) � 08.01 Edition I-123

Index

AAddition 5-107Application library 3-61Application list directory 3-61

CCharacter size 2-33Compiler options 4-94, 4-98Creating tool entries 2-18

DDelete 5-107Division 5-107Documentation 1-10

EEdit mode 5-107Emulation 5-108Event 2-33Event codes 3-62

GGray shades 2-33

IInsert 5-107Installation 2-16Installation on HMI Embedded 2-15Installation via parallel link with FAT16 file

structure 3-85Installation via parallel link with FAT32 file

structure 3-87Interface to NCK 1-12

Kkey.h 2-33

LLibrary 3-61Linker options 4-94, 4-98List element identities 3-62List identifiers 2-32, 3-62List identities 3-62logiccol.h 2-33

MModifying tool entries 2-18MPI mode 5-104MS-Visual C++ Workbench 2-17Multiplication 5-107mwl_app.h 2-32

NNavigation mode 5-107NCK variables 1-12Network connection: Installation 3-88Notebook entries 3-62Notebook entry 5-108Number range 2-32

OOnline 5-104On-Line-Help 2-20Operation 1-12Operator's Guide 1-10Overwrite 5-107

Pparallel link with: FAT16 file structure 3-85;

FAT32 file structure 3-87PC MPI mode 5-104PC simulation mode 5-102, 5-108Pocket calculator functions 5-107

SSCK 3-47Simulation mode 5-103, 5-108size.h 2-33Softkey size 2-33Subtraction 5-107

TTest mode on a PC 5-102Text source files 3-54, 3-55To open HMI-Embedded 5-103, 5-104Transmission via V24 2-15

UUndo 5-107

VVariables 5-108vgadef.h 2-33

Suggestions and/or corrections

ToSIEMENS AG

Suggestions

Corrections

A&D MC BMSP.O. Box 3180

For Publication/Manual:

SINUMERIK 840D/810DHMI Embedded Configuring Package

D-91050 Erlangen(Tel. +49 (0)180 / 5050 222 [Hotline]Fax: +49 (0)9131 / 98 � 2176e-mail: [email protected])


From

Name

Description of Functions

Order No.: 6FC5 297-6EA10-0BP0Edition: 08.01

Company/Dept.

Address_________________________________________________________________________________________________________________

_________________________________________________________________________________________________________________

Telephone: /_________________________________________________________________________________________________________________

Fax: /

Should you come across any printingerrors when reading this publication,please notify us on this sheet.Suggestions for improvement are alsowelcome.

SINUMERIK

840D/810D

SINUMERIK

Over vi ew of SI NUM ERI K 840D/ 840Di / 810D Docum ent at i on ( 08. 01)

Brochure CatalogOrdering InfoNC 60 *)

Description ofFunctionsDrive Functions *)

Description ofFunctions-- Basic Machine *)-- Extended Functions-- Special Functions

SINUMERIK

611D840D/810D

SINUMERIK

840D/840Di/810D

840D/840Di/810D

Accessories

CatalogAccessories NC-Z

SINUMERIKSIROTECSIMODRIVE

840D/840Di/810D611D

Lists *)Installation &Start-up Guide *)-- FM-NC-- 810D-- 840D/611D-- MMC/HMI

SINUMERIK

840D

Description ofFunctionsDigitizing

SINUMERIK

SINUMERIK

840D/810D

Configuring KitMMC 100/101-- ConfiguringSyntax

-- Development Kit

SINUMERIK

840D/810D

Screen KitMMC 100/101SW Update andConfiguration

SINUMERIK

840D/840Di/810D

SINUMERIK

840D/840Di/810D

OperatorComponents(HW) *)

840D/840Di/810D

Description ofFunctionsSINUMERIKSafety Integrated

SINUMERIKSIMODRIVE

SINUMERIK

840D/840Di/810D/611, Motors

SIMODRIVE

DOC ON CD *)The SINUMERIK System


Electronic Documentation



SINUMERIK

840D/810D/FM-NC

SINUMERIK

840D/810D

User Documentation

DiagnosticsGuide *)

Operator’s Guide-- HT 6 (+ 840Di)-- HPU-- Unit OperatorPanel

AutoTurn-- Short Guide-- Programming (1)-- Setup (2)

SINUMERIK

840D/840Di/810D

Program. Guide-- Short Guide-- Fundamentals *)-- Advanced *)-- Cycles-- Measuring Cycles-- ISO Turning/Milling

Description ofFunctions--ManualTurn-- ShopMill

Description ofFunctionsSynchronizedActions

840D/810D

SINUMERIK

Operator’s Guide--ManualTurn-- Short Guide ManualTurn-- ShopMill-- Short Guide ShopMill

840D/810D


SINUMERIK

840D/810D

Descr. of Functions-- Computer Link-- Tool DataInformationSystem

*) These documents are a minimum requirement for the control

Operator’s Guide *)-- Short Guide-- MMC 103-- HMI Embedded-- HMI Advanced

SINUMERIK

840D/840Di/810D

Configuring(HW) *)-- FM-NC-- 810D-- 840D

SINUMERIK

SINUMERIK

840D/840Di/810D

SINUMERIK

840D/810D

Description ofFunctionsOperator InterfaceOP 030

Description ofFunctionsToolManagement

SINUMERIKSIMODRIVE

SINUMERIKSIMODRIVE

SINUMERIKSIMODRIVE

SINUMERIKSIMODRIVE

SINUMERIKSIMODRIVE

840D611D

840D611D

Description ofFunctionsLinear Motor

SINUMERIKSIMODRIVESIROTEC

EMCGuidelines

Description ofFunctions-- HydraulicsModule

-- Analog Module

User Documentation

SINUMERIK

System Overview

840Di


SINUMERIK

Descr. of FunctionsISO Dialects forSINUMERIK

840D/840Di/810D

SINUMERIK

Descr. of FunctionsCAM IntegrationDNC NT-2000

SINUMERIK

Manual(HW + Installationand Start-up)

840Di

SINUMERIK

840D/810D

Descr. of FunctionsRemote Diagnosis

sinumerik 840d/810d hmi embedded configuring package · sinumerik 840d/810d hmi embedded...

Documents