IAM 0304 en PDF
IAM 0304 en PDF
IAM 0304 en PDF
sinumerik
SINUMERIK 840D/840Di/810D
HMI
Updates/ AE1
Supplements
Appendix A
Valid for
03.04 Edition
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" columns.
12.98 6FC5297-5AE20-0BP0 A
08.99 6FC5297-5AE20-0BP1 C
02.01 6FC5297-6AE20-0BP0 C
11.01 6FC5297-6AE20-0BP1 C
11.02 6FC5297-6AE20-0BP2 C
03.04 6FC5297-6AE20-0BP3 C
The reproduction, transmission or use of this document or its contents We have checked that the contents of this document correspond to the
is not permitted without express written authority. Offenders will be hardware and software described. Nevertheless, differences might
liable for damages. All rights, including rights created by patent grant or exist and therefore we cannot guarantee that they are completely
registration or a utility model or design, are reserved. identical. The information given in this publication is reviewed at
regular intervals and any corrections that might be necessary are
made in subsequent editions. We welcome all recommendations and
suggestions.
© Siemens AG, 2004. All rights reserved Subject to change without prior notice
Preface
Target group
This documentation is intended for manufacturers of machine tools with the
SINUMERIK 840D/840Di/810D control.
Hotline
If you have any queries, please contact the following hotline:
Fax form: See the feedback page at the end of the document.
Internet address
http://www.siemens.com/motioncontrol
Objectives
• To support the machine manufacturer in the commissioning and
parameterization of the HMI.
• To inform the machine manufacturer / end user of the various ways of
expanding the standard help system.
• The instructions explain how the HMI user interface provided by Siemens / the
machine manufacturer, can be modified easily by the machine manufacturer /
end user to meet their specific requirements. No other additional software tools
are required to do this.
Standard scope
The printed version consists of the following manuals:
• /AE1/ Updates/Supplements
• /BE1/ Expanding the Operator Interface
• /HE1/ Help in the Editor
• /IM2/ Starting Up HMI Embedded
• /IM4/ Starting Up HMI Advanced
• /TX1/ Creating Foreign Language Texts with Windows 95/NT
• /TX2/ Creating Foreign Language Texts with Windows 2000/XP
Search aids
To help you find your way around, there is a full list of contents together with a list
of chapter contents for each part as well as the following aids in the appendix:
1. References
2. List of abbreviations
3. Index per manual
! Important
This Installation and Start-Up Guide is valid for HMI Embedded, HMI Advanced
and HT 6.
! Danger
Indicates an imminently hazardous situation which, if not avoided, will result in
death or serious injury or in substantial property damage.
! Warning
Indicates a potentially hazardous situation which, if not avoided, could result in
death or serious injury or in substantial property damage.
! Caution
Used with the safety alert symbol indicates a potentially hazardous situation
which, if not avoided, may result in minor or moderate injury or in property
damage.
Caution
Used without safety alert symbol indicates a potentially hazardous situation
which, if not avoided, may result in property damage.
Notice
Used without the safety alert symbol indicates a potential situation which, if not
avoided, may result in an undesirable result or state.
Other information
! Important
Appears in the documentation wherever an important fact has to be taken into
account.
Note
Appears in the documentation wherever further references are made.
Machine Manufacturer
This symbol appears in this documentation whenever the machine manufacturer
can influence or modify the described functional behavior. Please observe
the information provided by the machine manufacturer.
Trademarks
IBM is a registered trademark of the International Business Corporation.
MS-DOS and WINDOWSTM are registered trademarks of the Microsoft
Corporation.
SINUMERIK 840D/840Di/810D
Updates/Supplements (AE1)
2 Changes from NC-SW 6.1 (10.00) to SW 6.3 (11.01) and from HMI-SW 6.1 to SW 6.2 ....... AE1/2-9
3 Changes from NC-SW 6.3 (09.01) to SW 6.4 (11.02) and from HMI-SW 6.2 to SW 6.3 ..... AE1/3-13
Introduction
The abbreviations listed below in column "Target document" are listed and
explained in the list of references in the appendix.
61_05 NCU573.3. tech. data update PHD: Configuring Manual NCU 561.2-573.2
61_08 NCU 572.3: tech. data update PHD: Configuring Manual NCU 561.2-573.2
61_09 NCU link, Profibus: Expansion PHD: Configuring Manual NCU 561.2-573.2
61_12 Functionality of the NCUs 571-573 PHD: Configuring Manual NCU 561.2-573.2
updated IAD: SINUMERIK 840D/SIMODRIVE 611D
Installation and Start-Up Guide
61_13 Block search via program test FB1/K1: Mode group, channel, program operation
Supplements in (ASUBs in all mode
modes and travel to fixed stop)
61_18 Lead link axis ("reading" axis) FB2/B3: Several Operator Panels and NCUs
61_19 Sequence control system for the FB2/B3: Several Operator Panels and NCUs
NCU link FB1/G2: Velocities, …,
BA: MMC Operator's Guide
61_20 Drive status for synchronized FB2/B3 Several Operator Panels and NCUs
actions PGA: Programming Guide Advanced
61_22 Block search extensions FB1/K1: Mode group, channel, program operation
mode
61_23 ISO dialects: Extensions FBFA: ISO Dialects for SINUMERIK Description of
Functions
61_41 Accelerated external block search BA: MMC Operator's Guide, Chapter 4
61_44 Additional states of skip levels BA: MMC Operator's Guide, Section 4.6
61_45 Rapid traverse override in the BA: Operator's Guide, Section 4.4
display
61_46 Tool management: code carrier FBW: Description of Functions Tool Management
with OEM data and new tool data
61_48 Access protection for basic softkey IAM/IM3: Installation and Start-Up MMC103,
offset Section 12.4
61_49 Tool management: filtered BA: MMC Operator's Guide, Section 5.3
lists/order processing
61_50 Extensions for MMC Wizard IAM/BE1: Expand the Operator Interface
61_51 Simulation: Match data with NC BA: MMC Operator's Guide, Section 6.7
61_53 Finishing m:n: distributed concept FB2/B3: Several Operator Panels and NCUs
(server)
61_54 NCU-specific alarm texts for IAM/IM3: Installation and Start-Up MMC103,
m:n Section 4.5
61_55 Changing the Alarm Help and MD IAM/HE1: Online help, Chapter 4
Help to pdf Help
61_57 Accelerated external block search BAD: Operator's Guide, HMI Advanced, Section 4.6
61_59 Automatic master spindle display BAD: Operator's Guide, HMI Advanced, Section 4.2
61_60 Additional states of skip levels BAD: Operator's Guide, HMI Advanced, Section 4.6
61_61 Rapid traverse override in the BAD: Operator's Guide, HMI Advanced, Section 4.4
display
61_63 Access protection for basic softkey IAM/IM4: Installing HMI Advanced, Chapter 5
offset
61_65 Tool management: order of BAD: Operator's Guide, HMI Advanced, Section 5.3
replacement tools FBW: Description of Functions Tool Management
61_66 Simulation: Match data with NC IAM/IM4: Installing HMI Advanced, Chapter 5
61_67 Change-language softkey, BAD: Operator's Guide, HMI Advanced, Section 9.5
independent of the language
61_68 NCU-specific alarm texts for IAM/IM4: Installing HMI Advanced, Section 6.2
m:n
61_70 Automatic master spindle display BEM: Operator's Guide, HMI Embedded,
Section 4.4
61_71 Tool and magazine list from BEM: Operator's Guide, HMI Embedded,
ShopMill Section 5.4
61_72 Extensions for MMC Wizard IAM/BE1: Expand the Operator Interface
61_73 Editing and activating GUDs and BEM: Operator's Guide, HMI Embedded,
MACs Section 6.4
61_74 Utilization display for Non-Win in BEM: Operator's Guide, HMI Embedded,
percent Section 8.6
61_76 Original condition via NC card BEM: Operator's Guide, HMI Embedded,
Section 7.5
61_77 Screen position configuring IAM/IM2: Installing HMI Embedded: Chapter 5
61_82 Changing the language with BEM: Operator's Guide, HMI Embedded,
"Change language" independent Section 9.4
of the language
The abbreviations listed below in column "Target document" are listed and
explained in the list of references in the appendix.
Note
Reference is made only to those functions and components that are not included
in Chapter 1 and that have been updated.
The abbreviations listed below in column "Target document" are listed and
explained in the list of references in the appendix.
Note
Reference is made only to those functions and components that are not included
in Chapter 2 and that have been updated.
64_16 Functionality of the NCUs 571-573 PHD: Configuring Manual NCU 561.2-573.4
IAD: Installation & Start-up Guide
64_17 Global measurement FB2, M5: Measuring
64_18 DRAM file system for cycle storage IAD: Installation & Start-up Guide
64_19 Wait mark for REPOS FB1, K1: Mode group, channel, program
operation mode
64_20 System variable SP_SEARCH_S FB1, K1: Mode group, channel, program
operation mode
64_21 Block search via program test FB1, K1: Mode group, channel, program
Supplements in (ASUBs in all operation mode
modes and travel to fixed stop) FB1, F1: Traversing to fixed stop
64_22 Single axes and spindle logic FB2, S3: Synchronous spindles
FB2, R2: Rotary axes, P2: Positioning axes
FB1, P3: PLC basic program
FB1, S1: Spindles, W1: Tool compensation
FB1, K1: Mode group, channel, program
operation mode,
VDI Interface Lists
64_23 Overlaid movements FB1, K1: Mode group, channel, program
operation mode, W1: Tool compensation
FB2, S5: Synchronized actions (up to SW 3)
FBSY: Description of Functions, Synchronized
Actions
PG: Programming Guide Fundamentals
64_24 Block change FB2, P2: Positioning axles
FB1, S1: Spindle
FBSY: Descr. of Functions, Synchr. Actions
PG: Programming Guide Fundamentals
64_25 Display of handwheels in the VDI FB2, H1: Manual travel, handwheel travel
interface
64_26 Contour handwheel FB2, H1: Manual travel, handwheel travel
64_27 Rotary table, 2 methods of FB2, H1: Manual travel, handwheel travel
operation
64_28 Expansions to SW cams FB2, N3: Software cams, position switching
signals
64_29 Spindle extensions FB1, S1: Spindles
FBSY: Description of Functions
64_30 No gear change during dry run FB1, S1: Spindles
FB1, K1: Mode gr, channel, prog. oper. mode
64_31 Automatic gantry synchronization
64_32 Electronic stop and retraction FB3, M3: Coupled axes and ESR
(NC-ESR): Extensions
64_33 EGON w. curve tables PLU V0015
64_34 Non-linear coupling in the ELG FB3, M3: Coupled axes and ESR
64_35 Drive signal dir. from the VDI FB2, B3: Several operator panels and NCUs
64_36 Drive status for synchronized FB2, B3: Several operator panels and NCUs
actions PGA: Programming Guide Advanced
64_37 Lead link axis FB2, B3: Several operator panels and NCUs
64_38 Sequence control system for the FB2, B3: Several Operator Panels and NCUs
NCU link FB1, G2: Velocities, setpoint/actual value
systems, closed-loop control
BA: MMC Operator's Guide
64_39 NC language P6 FB1, K1: Mode group, channel, program
operation mode
FB1, S1: Spindles
FBSY: Description of Functions, Synchronized
Actions
PGA: Programming Guide Advanced
64_40 Ext. f. block search P6 FB1, K1: Mode group, channel, program
operation mode
64_41 Synchronized actions extensions FBSY: Description of Functions
IAD: Installation & Start-up Guide
64_42 Synchr. action for indexed access FBSY: Description of Functions
64_43 Polynomial, 5th degree FB1, K1: Mode Group, Channels, Program
Operation
PGA: Programming Guide Advanced,
HW in FB2, B3: Several operator panels and
NCUs
64_44 Autom. change of exact stop FB1, B1: Continuous-path mode, exact stop and
operation Look Ahead
64_45 Smoothing with contour tolerance FB1, B1: Continuous-path mode, exact stop and
Look Ahead
64_46 Path acceleration by SYNACT FB1, B1: Continuous-path mode, exact stop and
Look Ahead
FBSY: Descr. of Functions Synchronized Actions
64_47 Tool path velocity smoothing FB1, B1: Continuous-path mode, exact stop and
Look Ahead
64_48 Dynamic response adaptation FB1, B1: Continuous-path mode, exact stop and
Look Ahead
64_49 Compressor COMPCAD: PGA: Programming Guide Advanced
Extensions
64_50 Non-circular turning FB2, B3: Several operator panels and NCUs
64_51 Frame extensions FB1, K2: Axes, coordinate systems, frames,
actual value system for workpiece, external work
offset,
FB1, S1: Spindles, W1: Tool Compensation
FB2, M5: Measuring,
FBSY: Description of Functions, Synchronized
Actions
PGA: Programming Guide Advanced
64_52 System frame for cycles FB1, K2: Axes, coordinate systems, frames,
actual value system for workpiece, external work
offset
64_53 3D measurement of inclined FB2, M5: Measuring
surfaces
64_54 Generic 5-axis transformation FB3, F2: 3 to 5-axis transformation
64_55 Using compr. better for orient. tool FB3, F2: 3 to 5-axis transformation
64_101 TCP functionality with 3+2 axes FB1, W1: Tool Compensation
FB3, F2: 3 to 5-axis transformation
FBSY: Descr. of Functions Synchronized Actions
PGA: Programming Guide, Advanced
PG: Programming Guide Fundamentals
64_102 Online tool length offset TRAGEN, FB1, W1: Tool Compensation
TRAORI, TCARR FB3, F2: 3 to 5-axis transformation,
FBSY: Descr. of Functions Synchronized Actions
PGA: Programming Guide, Advanced
PG: Programming Guide Fundamentals
64_103 Referencing in follow-up mode FB1, R1: Reference point approach
64_104 Motor change on spindle drives FB1 G2: Velocities, setpoint/actual value
systems, closed-loop control
64_105 Referencing with Distance-Coded FB1, R1: Reference point approach
Encoders
64_106 611 Digital Performance 2 FBA: Description of Functions, Drive Functions
IAD: Installation & Start-up Guide
64_107 Identification def. 611D modules FB1, D1: Diagnostic tools
64_108 Position control with PI controller FB1, G2: Velocities, setpoint/actual value
systems, closed-loop control
FB3, M3: Coupled axes and ESR,
ELG -> FB1, G2: Velocities, setpoint/actual value
systems, closed-loop control
64_109 Gauging of the HLA valve
characteristic
64_110 Coupling and uncoupling of rotating FB3, TE3: Speed/torque coupling, master-slave
spindles
64_111 Measuring functions on the FB2, M5: Measuring, only MD 13210 expanded
PROFIBUS-DP HBI: Manual
64_112 SPL-EA_Timing FBSI: Description of Functions SINUMERIK
Safety Integrated
64_113 SI, Step 3 Gen. FBSI: Description of Functions SINUMERIK
Safety Integrated
64_114 SPL function blocks FBSI: Description of Functions SINUMERIK
Safety Integrated
64_115 Series installation and start-up IAD: Installation & Start-up Guide
64_116 SINUMERIK HT6 IAM, IM2: Installing HMI Embedded
BAH: Operator's Guide HT6 (HPU New)
64_117 Retrofittable SM/MT FBMA: Description of Functions, ManualTurn
FBSP: Description of Functions ShopMill
64_118 NCK shutdown path FBSI: Description of Functions SINUMERIK
Safety Integrated
64_119 Ext. safe braking FBSI: Description of Functions SINUMERIK
Safety Integrated
FB1, P3: PLC basic program
64_120 SI I/O on Profibus FBSI: Description of Functions SINUMERIK
Safety Integrated
64_121 SI, Step 3 Diagnosis FBSI: Description of Functions SINUMERIK
Safety Integrated
64_122 Acceptance test FBSI: Description of Functions SINUMERIK
Safety Integrated
64_123 SI combined with ESR FBSI: Description of Functions SINUMERIK
Safety Integrated
64_150 Block search when executing IAM, IM2: Start-Up HMI Embedded
from network IAM, IM4: Installing HMI Advanced
64_151 Selective program protection BEM: HMI Embedded Operator's Guide
64_152 Hidden lines in the editor BEM: HMI Embedded Operator's Guide
64_153 Double editor BEM: HMI Embedded Operator's Guide
64_154 Copying programs in the BEM: HMI Embedded Operator's Guide
background
64_155 Multiple selection of files BEM: HMI Embedded Operator's Guide
64_156 Editing on the network drive BEM: HMI Embedded Operator's Guide
64_157 Geometry processor and C950: BEM: HMI Embedded Operator's Guide
Grinding stock allowances
64_158 System resource display of IAM, IM2: Start-Up HMI Embedded
SRAM, DRAM
64_159 Entry of fits BEM: HMI Embedded Operator's Guide
The abbreviations listed below in column "Target document" are listed and
explained in the list of references in the appendix.
Note
Reference is made only to those functions and components that are not included
in Chapter 3 and that have been updated.
I Index
I
I.1 Subject index
Changes from SW 5.3 (04.00) to SW 6.1/6.2
(10.00) ............................................... AE1/1-3
C Changes from SW 6.1 (NC) (10.00) to SW 6.3
(11.01) and from HMI-SW 6.1 to SW 6.2
Changes from NC-SW 6.3 (09.01) to SW 6.4 ............................................................ AE1/2-9
(11.02) and from HMI SW 6.2 to SW 6.3 Changes from the 11.02 Edition to the 03.04
......................................................... AE1/3-13 Edition .............................................. AE1/4-21
SINUMERIK 840D/840Di/810D
2.3 Display selection from the PLC (SW 5.3 and higher) ...........................................................BE1/2-20
5.2 Selecting screens created with "Expanding the Operator Interface" ..................................BE1/5-128
5.2.1 INI files and sections......................................................................................................BE1/5-129
5.2.2 Configuration .................................................................................................................BE1/5-130
5.12 Terms...............................................................................................................................BE1/5-148
7.4 HMI Embedded WIN32 and HMI Advanced together on one hardware platform ...............BE1/7-175
7.4.1 General information about searches..............................................................................BE1/7-175
7.4.2 Search strategy for common.com ..................................................................................BE1/7-179
7.4.3 Search sequence for images .........................................................................................BE1/7-180
8.1 Terms.................................................................................................................................BE1/8-184
1 Introduction
1
1.1 Aims and objectives................................................................... BE1/1-6
Note
SW version 6 redefines the designations for the operating software packages
running on PCU 20, PCU 50 and PC with WinNT.
HMI Embedded WIN32 on PCU 50 and PC can be combined with WinNT and
HMI Advanced on a single hardware platform. More detailed information can be
found in Chapter 7.
The tools package for "Expanding the Operator Interface" enables you to create
operator interfaces which display functional expansions designed by the machine
manufacturer or end user, or simply to implement your own screen form layout.
Preconfigured interfaces supplied by Siemens or the machine manufacturer can be
modified or replaced.
These configuration files which contain the description of the operator interface as
a whole are created using the ASCII Editor.
The syntax that must be applied in creating these files is described in the following
sections.
Note
The programming support functions described in Chapter 4 and the operator
interfaces for Siemens cycles in software version 5 and higher have been created
with the system tools for expanding the operator interface. As a result, they can
be modified as required by the machine manufacturer or end user within the
scope described in this chapter.
• It is only possible to switch between screen forms within one MMC operating
area.
• User, setting and machine data are initialized on request on the MMC 103.
• User variables may not have the same names as system or PLC variables.
• The screen forms activated by the PLC form a separate operating area for the
MMC 103 (similar to measuring cycle displays).
The entire memory space for all configuration files including texts amounts to
256KB, of which approx. 128KB are occupied by the system; therefore, 128 KB
remain for the user.
For PCU 20
256 kB are available to the user.
Functionality
The following functions are not available:
Search functions:
- SB (search forwards)
- SF (search backwards)
File names
All file names must follow DOS conventions (xxxxxxxx.eee).
Note
When an ID parameter is modified during operation, it is not necessary to specify
the parameter if it is unambiguous:
xy = value
Note
If the square parentheses are in bold ([...]), then the entry is not optional syntax,
but square parentheses which form part of the syntax, i.e. square parentheses in
bold must be configured.
//M(Identifier/[Header]/[Graphic]/[Dimension]/[System
or user variable]/[Graphic position]/[Attributes])
//M(Mask1/"CYC83"/"c83.bmp"/,,300,200//10)
;Name of identifier: Form1
;Header: CYC83
;Graphics: c83.bmp
;Dimension: Distance from left and top: Standard positions are
system-dependent, width 300 pixels, height 200 pixels
;System or user variables: None
;x-position of Help display: 10 pixels
;Attribute: None
Note
All possible values which can be assumed by a parameter are listed for some positional
parameters. Only one of the specified values can be assigned.
Identifier=(Text[,Status][,Access level])
with status se0
se1
se2
se3
HS2=("thread",se1)
If alternative parameters are possible, the separator | is placed between the
alternatives in the syntax description.
Note
The positions and size of image parameters are specified in pixels with reference
to standard displays with 640x480 pixels. In displays with higher resolutions,
these positions are converted automatically.
The reference point for positions is the top left corner of the main section of the
screen form.
The display of the HT6 has a resolution of 320x240. The values are understood
1:1, i.e. they are not converted.
Note
Commands which have not yet been implemented are specified at a number of
places in this document. Please refer to the Index for the corresponding
command with page reference.
Notes
2 First Steps
2
2.1 Creating configuration files ...................................................... BE1/2-14
2.1.1 Principle of the screen form tree........................................... BE1/2-17
2.1.2 Reverting to the standard application................................... BE1/2-17
2.3 Display selection from the PLC (SW 5.3 and higher) .............. BE1/2-20
Editor
An ASCII editor (e.g. Notepad or the MMC Editor) is used to create configuration
files.
Files
The defining data for new operator interfaces are stored in configuration files.
These files are automatically interpreted and displayed as screen forms.
Configuration files are not stored in the software supplied and must be set up by
the user.
Access
Every application uses permanent (MMC100.2, HT6, ShopMill, ManualTurn) or
default (MMC 103) start softkeys which can be selected to open newly configured
screen forms. Additional start softkeys can be configured on the MMC 103.
MMC 100.2/103
ShopMill
ManualTurn
HT6
Softkey Configuration File
Main screen Machine JOG, horizontal H_MA_JOG.COM
softkey 1
Main screen Machine MDA, horizontal H_MA_MDA.COM
softkey 1
Main screen Machine Automatic, horizontal H_MA_AUT.COM
softkey 2
Main screen Parameters, horizontal H_PARAM.COM
softkey 7
Main screen Parameters, horizontal H_PARAM.COM
softkey 8
Main screen Programming, horizontal H_PROG.COM
softkey 8
Main screen Services, horizontal softkey 7 H_SERVIC.COM
Main screen Start-up, horizontal softkey 7 H_STRTUP.COM
Main screen editor, horizontal softkeys 2-3 H_EDITOR.COM
Main screen correction editor, horizontal H_C_EDIT.COM
softkeys 2-4
MMC 100.2/HT6
On the MMC 100.2, HT6, ShopMill and ManualTurn, the system first seeks to
access the configuration files in the user cycles directory (NC memory), then in the
standard cycles directory and finally in a special DOS directory (Flash File System).
The Flash File System is the preferable option for performance-related reasons.
MMC 103
On the MMC 103, the system first seeks to access the configuration files in the
user cycles directory and then the standard cycles directory. The search is also
made in the manufacturer cycles directory in SW 6.2 and higher.
Access
softkey
You can use the "RECALL" key to close the new user interfaces if you have not
configured this key for any other task.
EXIT function
See Subsections 2.6.4 "Screen-form-independent softkeys" and 3.2.1 "Displaying
another screen form or softkey".
In order to access the start screen or a start softkey menu, the start softkey must
be defined. The definition block for a start softkey is structured as follows:
Start identifier of start softkey //S(Start)
MMC 100.2/HT6
Note
The information required to implement a softkey is to be found in
Subsection 7.2.1, keyword "Start softkeys".
Screen-form-independent softkeys are keys that are not called from a screen form,
i.e. they are start softkeys and softkey menus, which are configured before the first
new screen form. These functions are configured using the following method:
PRESS method
The PRESS method is executed when the corresponding softkey is pressed.
PRESS(Identifier)
...
END_PRESS
where:
Identifier Name of softkey: HS1-HS8, VS1-VS8
or RECALL
2.3 Display selection from the PLC (SW 5.3 and higher)
Displays can also be selected from the PLC. An interface is available for signal
exchange between the PLC and MMC/HT6.
Interface description
The interface contains:
• The display number
• Control bits from the PLC to the MMC
• Control bits from the MMC to the PLC
As each NCU can be addressed by up to two MMCs/HT6s at the same time in
systems with "several operator panel fronts and NCUs", this interface can exist in
duplicate.
References: /FB/, B3 "Several Operator Panels and NCUs"
The interface is located in the operator panel front interface (DB19). The interface
requires a total of 8 bytes in DB19, 4 bytes for each MMC/HT6.
These PLC displays offer the same means of display and functions as for the
displays selected via the softkeys.
For more information about display selection from the PLC, see Chapter 5, "PLC
interface".
Header
Form
element
8 vertical
softkeys
Graphic
Dialog line
8 horizontal softkeys
Within the screen form definition block, various variables that appear as form
elements in the screen form, as well as horizontal and vertical softkeys, are defined
first.
Different types of actions are then configured in methods.
Table 2-2
Entry Search in ...
Example
A new screen form is called via start softkey "Example" from the Parameters
operating area.
//S(Start)
HS7=("Example", ac7, se1)
PRESS(HS7)
LM("Form1")
END_PRESS
//END
//M(Form1/"Cycles")
HS1=("")
HS2=("")
HS3=("")
HS4=("")
HS5=("")
HS6=("")
HS7=("")
HS8=("")
VS1=("")
VS2=("")
VS3=("")
VS4=("")
VS5=("")
VS6=("")
VS7=("")
VS8=("")
... ;Methods
//END
Header
Main body
of screen
form
Graphic
The properties of the screen form are defined in the start identifier line of the form
screen:
//M(Identifier/[Header]/[Graphic]/[Dimension]/[System or user variable]/[Graphic
position]/[Attributes])
where:
Identifier Name of the screen form
Header Screen form header as text or call for text
(e.g. $85011) from a language-specific text file
(see Section 7.1 General information about the
configuring environment).
Graphics Graphics file (with path) in double quotation marks.
See also Chapter 3 "Displays".
Dimension Position and sized of main body of screen form in
pixels (distance from left, distance from top, width,
height), measured from the top left corner of the
screen. The measurements are separated by commas.
System or System or user variable to which current cursor
user variable position is assigned. The cursor position can be sent to
the NC/PLC via the system or user variable.
The first variable has the index 1.
The sequence matches the configuring sequence
of the variables.
Graphic position Position of graphic (distance from left, distance from
top) in pixels, measured from the top left corner of the
main body of the screen form. The minimum clearance
from the top is 18 pixels.
The data is separated by commas.
//M(Form1/"CYCLE83"/"c83.bmp"/,,300,200/"$R[2]"/10,20/CM1)
The properties Header, Graphic and System or User Variable can be changed in
the methods when the application is running:
Hd = Header
Hlp = Graphic
Var = System or user variable
See above for explanation of parameters.
Hd = "CYCLE83 changed"
Hlp = "c83_b.bmp"
Var = $R[19]
The screen form property System can be read during the runtime:
Values: 0 HMI_Embedded is being used
1 HMI_Advanced is being used
Example
//S(Start)
HS7=("Example", se1, ac7)
PRESS(HS7)
LM("Form1")
END_PRESS
//END
//M(Screen form1/"Example 2 : Display graphics"/"MST.BMP")
HS1=("")
HS2=("")
HS3=("")
HS4=("")
HS5=("")
HS6=("")
HS7=("")
HS8=("")
VS1=("")
VS2=("")
VS3=("")
VS4=("")
VS5=("")
VS6=("")
VS7=("")
VS8=("")
...
//END
Methods PRESS(HSx)
Actions LM...
End of method END_PRESS
Note
A carriage return in the softkey designation is created with %n. A maximum of 2
lines of 10 characters are available in HMI Advanced and 2 lines of 9 characters
in HMI Embedded. Two lines of 6 characters each are available to the HT6.
Access level
ac0
...
ac7
Meaning, refer to Table 2-3.
Default setting: AC7
Status
se1 visible
se2 cannot be used (grayed-out)
se3 displayed (last softkey used)
Default setting: se1
The properties Text, Access Level and Status can be changed in the methods
when the application is running:
SK.st = Text "Abort" ;Softkey e.g. the text "Abort"
SK.ac = Access level ;Softkey e.g. with access level 4
SK.se = Status ;Softkey e.g. with Status 2
where:
Access Level
0
...
7
Meaning, refer to Table 2-3.
Status
1 visible
2 cannot be used (grayed-out)
3 displayed (last softkey used)
See above for explanation of parameters.
Access level
The meanings of the different protection levels are as follows:
Table 2-3
Protection Locked by Range
level
ac0 is the highest protection level and ac7 the lowest. The operator can only
access information on the level for which he is authorized and all lower levels.
Example
//S(Start)
HS7=("Example", ac7, se1)
PRESS(HS7)
LM("Form3")
END_PRESS
//END
In addition to the horizontal and vertical softkeys, a RECALL key is also available.
In contrast to the softkeys, the RECALL key does not need to be defined. The
properties Status and Access Level can be assigned to it during operation (see
Subsection 2.6.2 "Define softkey").
PRESS(RECALL)
RECALL.ac = 1
LM("Form5")
END_PRESS
Note
More information about defining variables for one or more screen form elements
and all relevant information about creating displays appears in Chapter 3 "Syntax
for screen form definition".
Notes
3.1 Methods
Various types of event (exit input field, actuate softkey) can initiate particular
actions in screen forms and screen-form-dependent softkey menus (softkey
menus, which are called from a newly configured screen form). These actions are
configured in methods.
The following table shows the basic principle used to configure a method:
Method PRESS(HS1)
Actions:
- Functions, LM...
see Section 3.2 "Functions" LS...
PRESS method
The PRESS method is executed when the corresponding softkey is pressed. See
PRESS methods, softkey bars.
PRESS(SK)
...
END_PRESS
where:
SK Name of softkey: HS1-HS8, VS1-VS8,
or RECALL plus the following keys:
Keys
PU PageUP Screen up
PD PageDown Screen down
SL ScrollLeft Cursor key Left
SR ScrollRight " Right
SU ScrollUp " Up
SD ScrollDown " Down
END_PRESS
PRESS (HS2)
END_PRESS
PRESS(PU)
INDEX = INDEX -7
CALL("UP1")
END_PRESS
LOAD method
The LOAD method is executed after the variable and softkey definitions (DEF
Var1= ..., HS1= ...) have been interpreted. At this time, the screen form is not yet
displayed.
LOAD
...
END_LOAD
LOAD ;Start identifier of Load method
Form1.Hd = $85111 ;Assign text from language
;file as screen form header
VAR1.Min = 0 ;Assign Limit Value variable MIN
VAR1.Max = 1000 ;Assign Limit Value variable MAX
END_LOAD ;End identifier
UNLOAD method
The UNLOAD method is executed before a screen form is unloaded.
UNLOAD
...
END_UNLOAD
UNLOAD
REG[1] = VAR1 ;Place variable in register
END_UNLOAD
CHANGE method
CHANGE methods are executed if a variable value changes, i.e. variable
calculations that are performed as soon as a variable value changes are
configured within a CHANGE method.
There are two types of CHANGE method, i.e. element-specific and global.
The element-specific CHANGE method is executed if the value of a specified
variable changes.
CHANGE(identifier)
...
END_CHANGE
where:
Identifier Name of variable
If a system or user variable is assigned to a variable, cyclic updating of the variable
value can be configured in a CHANGE method.
The global CHANGE method is executed if the value of any variable changes and
no element-specific CHANGE method has been configured.
CHANGE()
...
END_CHANGE
CHANGE()
EXIT ;If any variable value changes,
;the screen form is closed
END_CHANGE
FOCUS method
The FOCUS method is executed if the focus (cursor) is positioned on another field
in the screen form.
FOCUS
...
END_FOCUS
FOCUS
DLGL("The focus has been placed on variable"<< FOC <<)
END_FOCUS
The FOC function may not be initiated as a result of navigation event. The cursor
may only be moved in softkey press blocks, change blocks, …
The response to cursor left, right, up, down as well as PGUP, PGDN are
permanently pre-defined.
Note
Within the focus block, it is not possible to select a different variable, nor can a
new screen form be loaded.
OUTPUT method
The OUTPUT method is executed if the GC function is called.
OUTPUT(Identifier)
...
END_OUTPUT
where:
Identifier Name of OUTPUT method
OUTPUT(CODE1)
"CYCLE82(" Var1.val "," Var2.val "," Var3.val ","
Var4.val "," Var5.val "," Var6.val ")"
END_OUTPUT
Condition Procedure
Number of blocks remains unchanged Block numbers are retained
Number of blocks is reduced The highest block numbers are
canceled
Number of blocks is increased New blocks are not numbered
Note
The NC code can be generated in an extra file by means of file functions and
transferred to the NC. For more information about NC code generation, see
Subsection 3.2.6 "File functions".
Example:
DEF var100=(R//1) ;Original, corresponds to Version 0
DEF var101(1)=(S//"Hello") ;Extension with effect from Version 1
When writing the OUTPUT block, you can specify which variables are written, with
reference to a particular version identifier.
Example:
OUTPUT(NC1) ;Only the variables of the original are available
;in the OUTPUT block
The OUTPUT block for the original version does not need a version identifier,
however you can specify it with 0. OUTPUT(NC1) is equivalent to
OUTPUT(NC1,0). Version identifier n in the OUTPUT block includes all variables of
the originals 0, 1, 2, ... up to and including n.
The code is automatically generated with the newest version, even if the code was
previously recompiled with an older version.
The newest screen form with all its variables is always displayed.
; Version 0 (default)
//M(XXX)
DEF var100=(R//1)
DEF var101=(S//"Hello")
DEF TMP
VS8=("GC")
PRESS(VS8)
GC("NC1")
END_PRESS
OUTPUT(NC1)
var100",,"var101
END_OUTPUT
//M(XXX)
DEF var100=(R//1)
DEF var101=(S//"Hello")
DEF var102(1)=(V//"HUGO")
DEF TMP
VS8=("GC")
PRESS(VS8)
GC("NC1")
END_PRESS
...
;Original
OUTPUT(NC1)
var100","var101
END_OUTPUT
...
; and the new version in addition
;Version 1
OUTPUT(NC1,1)
var100","var101"," var102
END_OUTPUT
Display line
with
long text
Form
Main body element
of the form
Screen form elements fill lines in the main body of the form. One or several screen
form elements can be defined in each line (see also "Multi-column screen forms").
The term "screen form element" refers to the visible part of a variable, i.e. short
text, graphics text, input/output field (I/O field) and unit text.
Defining variables
DEF Identifier = 1
(Variable type
2
/[limit values or toggle field or table identifier]
3
/[Default]
4
/[Texts (Long text, Short text|Display, Graphics text, Units text)]
5
/[Attributes]
6
/[Help display]
7
/[System or user variable]
8
/[Position of short text]
9
/[Position I/O field(Left, Top, Width, Height)]
10
/[Colors]
11
/[Help]*)
* MMC103 only
Note
The small figures above "(" and "/" are only an aid to assigning the parameter
groups. They are not part of the syntax. The single parameters to be separated
by commas are enclosed in round parentheses.
where:
Identifier Name of variable
Variable type Variable type:
R[x] Real (+ digit for the decimal place)
I Integer
Also refer below
"Integer extensions".
S[x] String (+ digit for string length)
C Single character
B Bool
V Version (See also "Variable type, variant")
The variable type must be specified.
Toggle field Toggle field: List with predefined entries in the I/O field.
The list is initiated by a * ; the entries are separated
by commas.
The entries can be assigned a value
(see "Examples").
The entry for the limit value is interpreted as a list
for the toggle field.
Entering only a * generates a variable
toggle field (see "Variable toggle fields").
Default setting: No default
or
Texts Texts: Long text, short text, graphics text, unit text
where:
Long text: Text in the display line
Short text: Name of the screen form element
Graphics text: Text refers to the terms in the graphics.
Unit text: Unit of screen form element
(see graphic above). See also Sections 1.4 and 5.1.
The sequence is specified.
Default setting: Empty
In SW 6 and higher, instead of the short text, a diagram can also be displayed.
Access level
Empty Can always be written
ac0...ac7 Protection levels (see Subsection 2.6.2
Defining a softkey)
If the access level is not adequate, then the first line is
displayed grayed-out.
Default setting: ac7
Font size
fs1 Default font size (8 pt.)
fs2 Double font size
Default setting: fs1
The clearances between the lines is defined.
For the default font size, 16 lines can fit into the screen form.
Graphics and unit text can only be configured in the default
font size.
li0 No check
li1 Check with respect to min.
li2 Check with respect to max.
li3 Check with respect to min. and max.
Default setting: Determined by specified limit values
Position of I/O Position of I/O field (distance from left, distance top, width,
field height).
The positions are specified in pixels and are measured from
the top left corner of the main body of the screen form.
Data is separated by a comma.
See also "Positions".
If this position changes, the positions of the short text,
the graphics text and the unit text also change.
Colors Colors:
Foreground color, background color
Value range: 1...10
For colors, see Section 8.2 "Color table".
The colors are separated by a comma.
Default setting: Foreground color: Black
Background color: White
Identical PDF and text files must have the same name.
The name of the PDF file must be written in uppercase letters
in the txt file.
See also "Help"
ISNUM (VAR)
where:
VAR Name of the variable whose data type must be checked
The result of the scan can be:
FALSE = not a numerical variable (data type = String)
TRUE = numerical variable (data type = Real)
or
ISSTR (VAR)
where:
VAR Name of the variable whose data type must be checked
The result of the scan can be:
FALSE = numerical variable (data type = Real)
TRUE = not a numerical variable (data type = String)
The field type "Variant" is mainly suited to write either variable names or numerical
values into the NC code.
IF ISNUM(VAR1) == TRUE
IF ISSTR(REG[4]+2) == TRUE
Integer extensions
The following extensions for determining the display in the I/O field and the
memory utilization are possible for Integer types:
Examples
Example 1:
Assign properties Variable Type, Texts, Help, Colors:
DEF Var1 = (R///,"Actual value",,"mm"//"Var1.bmp"////8,2)
Variable type: Real
Limit values or toggle field entries: None
Default: None
Texts:
Long text: None
Short text: Actual value
Graphics text: None
Unit text: mm
Attributes: None
Help display: Var1.bmp
System or user variable: None
Position of short text: No data, i.e. a default position
Position I/O field: No data, i.e. default position
Colors:
Foreground color: 8
Background color: 2
Help: None
Example 2:
Assign properties Variable Type, Limit Values, Attributes, Short Text Position:
DEF Var2 = (I/0,10///wr1,al1///,,300)
Variable type: Integer
Limit values: MIN: 0; MAX: 10
Default: None
Texts: None
Attributes:
Input mode: Is read only
Alignment of short text: Right-justified
Help display: None
System or user variable: None
Position of short text:
Distance from left: None
Distance from the top: None, i.e. default distance
from the top left
Width: 300
Position I/O field: No data, i.e. default position
Colors: No data, i.e. a default setting
Help: None
Example 3:
Assign properties Variable Type, Default, System or User Variable, I/O Field
Position:
DEF Var3 =(R//10////"$R[1]"//300,10,200//
"Help.pdf",1,"Help1")
Variable type: String
Limit values or toggle field entries: None
Default: 10
Texts: None
Attributes: None
Help display: None
System or user variable: $R[1] (R-Parameter 1)
Position, short text: Default position relative to the
I/O field
Position of the I/O field:
Distance from left: 300
Distance from the top: 10
Width: 200
Colors: No data, i.e. a default setting
Help: In the Help.pdf file, the Help with the Help text
"Help1" is called on the page with index 1
when the Help key is pressed.
Example 4:
Various entries in toggle field:
DEF Var1 = (I/* 0,1,2,3)
DEF Var2 = (S/* "In", "Out")
DEF Var3 = (B/* 1="In", 0="Out")
;1 and 0 are values, "In" and "Out"
;are displayed
DEF Var4 = (R/* ARR1) ;ARR1 is the name of an array
Example 5:
Several Help calls per form element (MMC 103 only):
DEF Var1 = (R//////////"Help1.pdf",1,"Help1",
,2,"Help2","Help3.pdf",3,)
;1. Entry in the Help loop
Help file: HELP1.PDF
Index: 1
Help text: Help1
2. Entry in the Help loop
Help file: HELP1.PDF
Index: 2
Help text: Help2
3. Entry in the Help loop
Help file: HELP3.PDF
Index: 3
Help text: Help2
In SW 6 and higher, the display mode can be changed for the type property of a
variable.
For integer variables this is display type:
B = binary
D = decimal with sign
H = hexadecimal
without sign
+ U for unsigned
For Real, only the number of places after the decimal point can be changed.
Changing the basic type is illegal and generates an error message in the file
error.com.
Parameterization example:
Var1.typ = "IBW"
Var2.typ = "R3"
Default
A variable can assume various states depending on whether a default value, or a
system or user variable, or both, is assigned to the variable field (I/O field or toggle
field).
Table 3-3
If... Then...
Field Default System or Reaction of field type
type user variable
Not calculated: Toggling is not possible until a valid value is assigned to the
variable
Positions
The short text and graphics text and the I/O field and unit text are each treated like
a unit, i.e. position settings for short text apply to the graphic text and settings for
the I/O field and to the unit text.
The configured position entry overwrites the default value, i.e. only one value can
be changed.
If no position data is configured for following screen form elements, then the
position settings for the preceding screen form element are applied.
If no positions have been specified for any element, then default positions are
applied. The column width for the short text and I/O field is calculated as standard
for each row from the number of columns and maximum row width, i.e.
column width = maximum row width/number of columns.
The width of the graphics and unit text is predefined and optimized to suit the
requirements of programming support. If graphics or unit text has been configured,
the width of the short text or I/O field is reduced accordingly.
The order of short text and I/O field can be reversed by position settings.
Help
The Help loop for a screen form element can be extended or deleted during
runtime. These functions are available only with MMC 103.
Extending the Help loop:
where:
Identifier Name of the variable whose Help loop will be extended
Help file Path specification of the file (PDF format)
Index Index in the Help file to the Help text
Help text Help text for display in the Help text file
The Help loop can be extended as required by calling the function repeatedly.
ADDHTX(VAR1, ”C:\OEM\HLP\MYHLP.PDF”, 15, ”Machine data”)
DEF Identifier =
(Variable type
/+ $Text number |
* value= "\\display"[,value="\\bild2.bmp"][, ...]
/[Default]
/[Texts(Long text, Short text, Graphics text, Units text)]
/[Attributes]
/[Help display]
/[System or user variable]
/[Position of short text]
/[Position I/O field(Left, Top, Width, Height)]
/[Colors]
/[Help])
where:
Variable type Type of variables specified in the system or user
variable
Text number Number (basis) of the language-specific texts valid as the
basis number
System or System or user variable (offset)
user variable used to form the final text number (basis + offset)
For explanation of other parameters, see "Defining variables".
When the screen form is opened, the contents of text number $85015 are
displayed in the I/O field. Default value 15 is entered in system variable
DB90.DBB5. If the value saved in system variable DB90.DBB5 changes, then the
displayed text number $(85000 + <DB90.DBB5>) is recalculated in response to
every change.
DEF VAR1=(IDB/*1="\\bild1.bmp",
2="\\bild2.bmp"//,"$85000"/wr1//"MB[0]"//160,40,50,50)
To make individual variables in the configuration file more legible, the definition
lines can be wrapped after every variable definition and following comma.
The key word "DEF" always indicates the beginning of a new line.
Variable value
The default property of a variable is its value. When a variable is defined, a value is
allocated to it in the form of a default setting, a system or user variable or
programmed in the methods, as described below.
Identifier.val = Variable value
or
Identifier = Variable value
where:
Identifier Name of variable
Variable value Value of variable
Variable status
The "Variable status" property can be scanned during runtime to find out whether a
variable has a valid value. This property can be read and written with the FALSE =
0 setting.
Identifier.vld
where:
Identifier Name of variable
The result of the scan can be:
FALSE = invalid value
TRUE = valid value
IF VAR1.VLD == FALSE
VAR1 = 84
ENDIF
where:
Input mode: wr 0 Invisible, exception: Short text
1 Read (the line appears grayed-out)
2 Read and write (the line appears grayed-out)
3 wr1 with focus
4 All elements of the variables are invisible,
no focus possible
5 The value entered is saved immediately
whenever the key is pressed
(unlike wr2 - here, a save is only performed
on exiting the field, or when RETURN
is pressed).
The text/value entered is saved immediately.
Variable remains in the edit mode.
Input mode on the PCU 20: Only relevant for the I/O field
wr 4 Only all elements of the variable are affected.
PRESS(HS1)
AXIS=AXIS+1
WEG.VAR="$AA_DTBW["<<AXIS<<"]"
;Address axis address via
variable
END_PRESS
Help variables
Help variables are internal arithmetic variables.
Arithmetic variables are defined like other variables, but have no other properties
apart from variable value and status, i.e. Help variables are not visible in the screen
form. Help variables are of the Variant type.
DEF Identifier
where:
Identifier Name of Help variables
DEF OTTO ;Definition of a Help variable
where:
Identifier Name of the Help variables
Help variable value Contents of the Help variables
LOAD
OTTO = "Test" ;Assign Help variable Otto the value "Test"
END_LOAD
LOAD
OTTO = REG[9].VAL ;Assign value of register to
;Help variable
END_LOAD
The Status property can be used to scan the Help variable to find out whether its
value is valid. Status is a read only property.
Identifier.vld
where:
Identifier Name of Help variables
The result of the scan can be:
FALSE = invalid value
TRUE = valid value
IF OTTO.VLD == FALSE
OTTO = 84
ENDIF
The variable status (see Variable status) can be used to scan a variable to find out
whether its value is valid or not.
3.1.4 Displays
Displays
Maximum size: 560 * 326 pixels (MMC 100.2 and MMC 103)
312 * 139 pixels (HT6)
688 * 376 pixels (PCU20 and PCU50 with OP012)
Creating displays on
MMC100.2/HT6
To configure displays, please proceed as follows:
• Create the displays using, for example, the Windows 95 Paint application.
• Convert the displays into PCX format with 16 colors (e.g. with PaintShopPro).
• Convert the PCX file where the supplied program pcxconv.exe is executed.
Explanation of parameters:
The parameters Xpos, Ypos, Width, Height define the display section to be
converted from the generated display.
I.a. Start with 0 0, that is, in the upper left corner.
The conversion program BMP2BIN (on the application floppy disk) should be used
with software version 6.2 and higher. It supports 256 colors and faster display
building.
Explanation of parameters:
The described procedure for conversion and archiving is applicable for all
displays in the MMC 100.2/HT6.
With MMC 100/WIN32, partial binary or BMP files (packed or compressed) can be
processed. MMC 100.2 can process packed or unpacked BMP files. The colors are
converted online. For this the files containing the color table (syscol.col,
sysbw.col,...) have been extended to include Section [BMP]. This section allocates
a color of a BMP pixel to a color of an MMC.
Preconditions
The screens must have previously been stored in 16-color mode.
Bitmaps with 256 colors are supported in software version 6.2. and higher. You will
find the corresponding color table in Section 8.2. "Color table"
Storage locations
The following storage locations are possible (SW 5.3):
- Bitmap unpacked on Flash (WIN32 (MMC103, HMI) unpacked on
hard disk)
- In each case one bitmap packed in xxx.bm_, where xxx.bm_ contains file
xxx.bmp
As of SW 6:
- Bitmap packed in CST.ARJ (for standard cycle images)
- Bitmap packed in CUS.ARJ (for customer cycle images)
- Bitmap packed in CMA.ARJ (for manufacturer cycle images)
Procedure
Examples:
Alternative 1: Several files per archive:
arj a cus.arj my_file1.bmp my_file2.bmp my_file3.bmp my_file4.bmp
Alternative 2: One file per archive:
arj a my_file1.bm_ my_file1.bmp
Limit
Archiving is optional. However you must ensure that the sum of customer screens
does not exceed 128KB for the MMC 100.2 hardware.
Archiving individual files (.bm_) has runtime advantages over archiving in a large
archive (cus.arj) if you have a large number of customer screens.
If you are working in a WIN32 environment we recommend that you DO NOT
archive the BMP files but store them directly in the BIN directory. This therefore
eliminates the runtime when extracting.
Add the archive cus.arj, or the individual archive .bm_ using the MMC100.2
application environment (menu item ADD FILES)
This point no longer applies in the WIN32 environment.
Further, from SW 5.3, it is possible to assign any softkey a bitmap by starting the
softkey text with 2 backslashes. The text behind the backslashes is then
interpreted as the name of the file that contains the bitmap.
Notice !
From SW 6.2 onwards, the widths of the bitmaps (No. of pixels) can be specified
with any number. There is no longer any requirement for it to be possible to divide
them by 8.
Note
The display colors might be shown differently on the MMC 100.2/HT6 than in
PaintShopPro. For more information about handling (e.g. search strategies in
general and search sequence for displays), see Chapter 7, Chapter 8 "Color
table".
Creating displays on
the MMC 103
Graphics/displays and Help images can have the following format:
• Bitmap (BMP),
• Metafile (WMF) or
• Icon (ICO).
Graphic programs can be freely selected provided that they are capable of creating
the prescribed formats.
You can insert further screens in the background (Help screen). Even as a function
of the values of the variables.
Like for softkeys you can assign a graphics file to a display field. The height of the
displayed graphic (of the I/O field) is specified as the fourth parameter of the
positions.
You can define bitmaps in fields (short text, I/O field).
The definition is made with the notation used in "Defining variables" (see
Subsection 3.1.2 Screen form elements).
Example:
Short text field is overlaid with graphics
DEF VAR1=(S///,"\\bild1.bmp" ////160,40,50,50) ; Type S irrelevant
Toggle field overlaid with graphics, the graphic being selected with a PLC flag byte.
DEF VAR1=(IDB/*1="\\bild1.bmp",
2="\\bild2.bmp"//,"$85000"/wr1//"MB[0]"//160,40,50,50)
3.1.6 Arrays
Definition
Arrays have start identifier //A and end identifier //END. The number of rows and
columns is optional. An array is structured in the following way:
//A(Identifier)
(a/b...)
(c/d...)
...
//END
where:
Identifier Name of array
a, b, c, d Values of array
Note
Values of the String type must be enclosed in quotation marks.
//A(Thread)
; Size / Pitch / Core diameter
(0.3 / 0.075 / 0.202)
(0.4 / 0.1 / 0.270)
(0.5 / 0.125 / 0.338)
(0.6 / 0.15 / 0.406)
(0.8 / 0.2 / 0.540)
(1.0 / 0.25 / 0.676)
(1.2 / 0.25 / 0.676)
(1.4 / 0.3 / 1.010)
(1.7 / 0.35 / 1.246)
//END
Load
The LA (Load Array) function can be used to load an array from another file.
LA(Identifier [, File])
where:
Identifier Name of array to be loaded
File File in which the array is defined
Note
If an array in the current configuration file must be replaced by an array from
another configuration file, then both arrays must have the same name.
Note
Please note that a valid value must be assigned to a variable after the LA function
has been used to assign another array to the toggle field of the variable.
Access
The value of an array access operation can be transferred with property Value
(identifier.val).
Access to one-dimensional array with only one column:
Identifier [Z,[M[,C]]] or Identifier [Z,[M[,C]]].val
The row index (row number of the array) or column index (column number of the
array) each start at 0.
If a row index or column index points to outside the array, the value 0 or a blank
string is output and error variable ERR set to TRUE.
Error variable ERR is also set to TRUE if a search key cannot be found.
Compare mode
When compare mode C = 0 is used, the contents of the search row or search
column must be sorted in ascending sequence. If the search key is smaller than
the first element or greater than the last, a value of 0 or blank string is output and
error variable ERR is set to TRUE.
When compare mode C = 1 is used, the search key must be present in the search
row or search column. If the key cannot be found, a value of 0 or a blank string is
output and error variable ERR is set to TRUE.
Access mode
Table 3-4
Mode Row value Z Column value S Output value
M
Example
Two arrays are defined below. These are the basis for the following examples.
//A(Thread)
(0.3 / 0.075 / 0.202)
(0.4 / 0.1 / 0.270)
(0.5 / 0.125 / 0.338)
(0.6 / 0.15 / 0.406)
(0.8 / 0.2 / 0.540)
(1.0 / 0.25 / 0.676)
(1.2 / 0.25 / 0.676)
(1.4 / 0.3 / 1.010)
(1.7 / 0.35 / 1.246)
//END
//A(Array2)
("DES" "PTCH" / "CDM" )
/
(0.3 / 0.075 / 0.202 )
(0.4 / 0.1 / 0.270 )
(0.5 / 0.125 / 0.338 )
(0.6 / 0.15 / 0.406 )
(0.8 / 0.2 / 0.540 )
(1.0 / 0.25 / 0.676 )
(1.2 / 0.25 / 0.676 )
(1.4 / 0.3 / 1.010 )
(1.7 / 0.35 / 1.246 )
//END
Explanation: Search for value 0.5 in column 0 of "Thread" array and output the
value found in column 1 of the same row.
Explanation: Search for the row with the contents 0.6 in column 0 of array "Array2",
search for the column with the contents "STG" in row 0. Transfer the value from the
row and column found to VAR1.
Explanation: Search for value 0.125 in column 1 of array "Thread" and transfer the
row index of the value found to VAR1.
Explanation: Search in row 4 of the "Thread" array for the value 0.2 and transfer
the column index of the value found to VAR1. Comparison mode 1 was selected
because the values of row 4 are not sorted in an increasing sequence.
Array status
The Status property can be used to scan a configuration file to find out whether an
array access operation is supplying a valid value. Status is a read only property.
Identifier [Z, S, [M[,C]]].vld
where:
Identifier Name of array
The result of the scan can be:
FALSE = invalid value
TRUE = valid value
Contrary to the array, that displays status data saved in cables which can then be
selected, the values of a table element (grid) are continually updated. This involves
a tabular representation of values of system variables that can be addressed using
one block in one channel.
Assignment
The table element definition is assigned to a variable definition via a table identifier
in accordance with Subsection 3.1.2 "Screen form elements".
The variable definition determines the values to be displayed and the table element
definition determines the appearance and the assignment in the screen window.
The grid uses the I/O field-specific properties from the variable definition line.
Screen window
The visible area of the grid is determined by the width and height of the I/O field.
Any rows or columns than cannot be seen can be displayed by scrolling
horizontally and vertically.
Table description
The variable description will contain a reference to a table description:
DEF Identifier = 1
(Variable type
2
/[limit values or toggle field or table identifier]
3
/[Default]
4
/[Texts (Long text, Short text|Display, Graphics text, Units text)]
5
/[Attributes]
6
/[Help display]
7
/[System or user variable]
....
The other parameters correspond to those described in Subsection 3.1.2 "Screen
form elements".
Note
The small figures above "(" and "/" are only intended to enhance legibility.
Table identifiers
Identifiers of a table containing NCK/PLC values of the
same type, which can be addressed via a channel
block. The table identifier is differentiated from limit
values or toggle fields by the addition of a % sign in
front of it. The file containing the table description can
be specified by adding a comma after the identifier and
then inserting the name of the file.
Load Grid
LG (identifier, table identifier [,file name])
The identifier is the variable identifier to which the table identifier is to be assigned.
The file name can be inserted at this point. It identifies the file in which the table
description (table block) is stored.
Header
//G(Table identifier/Table type/Number of rows/[Fixed row attribute], [Fixed column
attribute])
Table identifier:
The table identifier is used without a leading % sign. It can only be used once in
each screen form.
Table type:
0 (default value) Standard table for PLC or user data
(NCK and channel-specific data)
1 (and others, reserved)
No. of rows:
Number of rows including header
1 Active
0 Not active
0 Active
1 Not active
The fixed row or fixed column is not scrolled.
Column definitions
Column definition row:
For PLC or NC variables, the index number is of significance with one or several
indices. Only those variables with index are sensibly represented as grid.
Column properties are modified via the variable identifier in the definition list or via
the column index (starting at 1).
Example:
Var1[1].st="Column 1"
String variable
If the variable is a string type variable, the string length must be specified in Type.
The next three examples show the assignment between cells and PLC variables in
a standard table (table type=0).
The first row shows the column headers.
Example 1:
//G(MB_TAB/0/4/,1)
(I///,"MB 1 to MB 3"///"MB1"/100/1)
(I///,"MB 4 to MB 6"///"MB4"/100/1)
MB 1 to MB 3 MB 4 to MB 6
Value(MB1) Value(MB4)
Value(MB2) Value(MB5)
Value(MB3) Value(MB6)
//G(MB_TAB/0/4/,1)
(I///," MB1, MB3, MB5"///"MB1"/100/2)
(I///," MB2, MB4, MB6"/// "MB2"/100/2)
Rows and columns are assigned as follows:
In each row, the index of the variable was increased by the offset (=2).
//G(MB_TAB/0/4/,1)
(IB///,"M1.1, M2.1, M3.1"/// "M1.1"/100/1)
(IB///,"M1.1, M2.1, M3.1"/// "M1.1"/100/0.1)
In the first column, the first variable index for each row was increased by 1.
(Offset1 = 1)
In the second column, the second variable index for each row was increased by 1.
(Offset2 = 1)
Example: (I///,"Rows"///"0"/60/1)
• Consecutive texts from the language files can be entered in the first column.
Example: (S///,"Rows"///"$80000"/60/1)
Identifier.Row
Identifier.Col
Row properties:
Each cell in a table has the Val and Vld properties.
In order to read and write cell properties, a row and column index must be specified
in addition to the variable identifiers from the definition list.
Example:
Var1[2,3].val=1.203
If a row or column index is not specified, the indices of the focused cell apply.
Example:
Var1[2,3].val=1.203
Is equivalent to:
Var1.Row =2
Var1.Col=3
Var1.val=1.203
3.2 Functions
LM function
The LM function can be used to load another screen form.
Note
Parameter VARx transfers only the value of the variable in each case, i.e.
variables can be read and written in the sub-screen form, but are not visible in it.
Variables can be returned from the sub-screen form to the master screen form by
means of the EXIT function.
PRESS(HS1)
LM("MASKE2",”C:\CFI\CFI.COM”,1, POSX, POSY,
DIAMETER)
;Interrupt screen form1 and open screen form2. At the same
;time, transfer variables POSX, POSY and DIAMETER.
DLGL("Form2 ended")
;On return from screen form2, the following text appears in the
;dialog line of screen form1: Screen form2 ended.
END_PRESS
LS function
The LS function can be used to display another softkey menu.
LS("Identifier"[, "File"][, Merge])
where:
Identifier Name of softkey menu
File Path name (MMC file system or NC file system)
of configuration file
Default setting: Actual configuration file
Merge 0: All currently displayed softkeys are deleted - the
newly configured softkeys are entered
1: Merge, i.e. only newly configured softkeys overwrite
existing softkeys, other softkeys remain unchanged
and retain their function and text
Default setting: 1
Note
Even MMC, ShopMill or ManualTurn standard softkeys can be retained with their
existing functionality.
Default setting: 0
PRESS(HS4)
LS("Menu2",,0) ;Menu2 overwrites existing menu,
;all existing softkeys are deleted
END_PRESS
Note
As long as the interpreter has not displayed a screen form, i.e. no LM function
has yet been processed, only one LS or one LM command, but no other action,
can be configured in the PRESS methods of the definition blocks for the start
softkey and softkey menus.
Note
The LS and LM functions may only be called within a softkey PRESS block and
will not react if navigation keys are pressed (PU, PD, SL, SR, SU,SD)
EXIT function
The EXIT function is used to search for master forms.
If it finds a master screen form, the currently displayed form is closed and you
return to the master screen form. If no master screen form is found, you exit from
the newly configured operator interfaces and return to the standard application.
EXIT
PRESS(HS1)
EXIT
END_PRESS
If the current screen form has been called as a sub-screen form with transfer
variables, the variables in the sub-screen form can be changed and transferred
back to the master screen form.
EXIT[(VARx)]
where:
VARx List of variables or variable values which are
transferred from the sub-screen form to the master form.
The variable contents/values are assigned to the variables
transferred to the sub-screen form the master screen form via
the LM function.
Up to 20 variables/variable values, each separated by a
comma, can be transferred.
Note
The sequence of variables/variable values must be the same as the sequence of
transfer values programmed for the LM function to preclude assignment errors.
Any unspecified variable values will not be changed when the transfer is made.
The modified transfer variables are immediately valid in the master screen form
on execution of the LM function.
//M(Form1)
...
PRESS(HS1)
LM("Form2",”C:\CFI\CFI.COM”,1, POSX, POSY,
DIAMETER)
;Interrupt screen form1 and open screen form2. At the same
;time, transfer variables POSX, POSY and DIAMETER.
DLGL("Form2 ended")
;On return from screen form2, the following text appears in the
;dialog line of screen form1: Screen form2 ended.
END_PRESS
...
//END
//M(Form2)
...
PRESS(HS1)
EXIT(5, , CALCULATED_DIAMETER)
;Exit screen form2 and return to screen form1 in the row after
;LM. At the same time, assign value 5 to variable
;Assign the value of the CALCULATED_DIAMETER variables to the
;DIAMETER variables. The variable POSY retains its current value.
END_PRESS
...
//END
EXITLS function
You can use the EXITLS function to exit the current operator interfaces and load a
defined softkey menu.
where:
Softkey menu Name of the softkey menu to be loaded
Path name Directory path of the softkey menu to be loaded
Action Instruction to a softkey of the new menu
(function is still not available in SW 5.2)
PRESS(HS1)
EXITLS( "Bar1", "COM.DIR\AEDITOR.COM" )
END_PRESS
EXE function
The EXE function can be used on the MMC 103 to call a program created as an
application with the OEM package of the MMC 103 or to start the Free Contour
Programming application.
On the MMC 100.2, EXE can only be used to start the Free Contour Programming
application.
Note
The EXE function GPROC is only available within the parts program editor.
Note (MMC103)
In order to start EXE, the task index of the EXE function must be entered under
[CHILDS] in the application INI file as it is stored in the REGIE.INI file (see OEM
documentation).
PRESS(VS3)
EXE(GPROC) ;Start GPROC.EXE (free
;contour programming)
END_PRESS
Read
RNP ("System or user variable")
where:
System or user variable Name of NC or PLC variable
VAR2=RNP("$AA_IN[2]") ;Read NC variable
Write
WNP ("System or user variable", value)
where:
System or user variable Name of NC or PLC variable
Value Value that should be written
into the system or user variable.
If the value is a String type, it must
be enclosed in quotation marks.
Note
User variables may not have the same names as system or PLC variables.
Table 3-5
Machine data
Table 3-6
Setting data
Table 3-7
System variables
R parameter 1 $R[1]
PLC variable
All PLC data are available.
Table 3-8
PLC data
In the variable names, "*" is the separator. The values are transferred to register
REG[Register index] and those following in the order that the variable names
appear in the command.
The following therefore applies:
The value of the first variable is located in REG[Register index]
The value of the second variable is located in REG[Register index + 1],
etc., see General screen form variables, "Register" section.
Notice
Please note that the list of variables must not contain more than 500 rows and not
exceed the value for registers in Section 3.4 General screen form variables.
Example:
MRNP("$R[0]*$R[1]*$R[2]*$R[3]",1)
In the previous example, REG[1] to REG[4] are described with the value of
variables $R[0] to$R[3].
It may be useful to check if variables contain a valid value before an NC code with
the GC function.
IF CVAR == TRUE ;Check all variables
VS8.SE = 1 ;If all variables are correct, softkey VS8
;will be visible
ELSE
VS8.SE = 2 ;If one variable contains
;an invalid value, softkey VS8
;cannot be used
ENDIF
DLGL ("String")
where:
String Text which is displayed in the dialog line
(notated according to 1.4)
EVAL(exp)
where:
exp ;Logical expression to be evaluated
VAR1=(S)
VAR2=(S)
VAR3=(S)
VAR4=(S)
CHANGE()
REG[7] = EVAL("VAR"<<REG[5]) ;The expression in parentheses
;is the value of VAR3 if the value of
;REG[5] equals 3. REG[7] is
;assigned the value of VAR3.
;(See Section 3.3)
END_CHANGE
3.2.4 Subroutines
Repeatedly used configuring instructions or others which define the process for a
particular operation can be configured in subroutines. Subroutines can be loaded
into the main program or other subroutines at any time and executed as often as
necessary, i.e. the instructions they contain do not need to be configured
repeatedly. In this case, the screen form and softkey menu definition blocks act as
the main program.
Defining a
subroutine
Subroutines are identified by the block identifier //B and terminated with //END in a
configuration file. Several subroutines can be defined under each block identifier. A
block is structured in the following way:
//B(Block name)
SUB (identifier)
...
END_SUB
[SUB(identifier)
...
END_SUB]
...
//END
where:
Block name Name of block identifier
Identifier Name of subroutine
Note
Variables programmed in subroutines must be defined in the screen form in
which these subroutines are called.
LOAD
LB("PROG1") ;Block "PROG1" is located in the current configuration file
;and then loaded
LB("PROG2","C:\TMP\XY.COM")
;Block "PROG2" is located in configuration file XY.COM in the
;C:\TMP directory and then loaded
END_LOAD
Note
Subroutines can also be defined directly in a screen form so that they do not have
to be loaded.
Calling a
subroutine (CALL)
The CALL function can be used to call a loaded subroutine from any point in a
method.
Subroutine nesting is supported, i.e. you can call a subroutine from another
subroutine.
CALL("Identifier")
where:
Identifier Name of subroutine
//M(FORM1)
VAR1 = ...
VAR2 = ...
LOAD
...
LB("PROG1") ;Load block
...
END_LOAD
CHANGE()
...
CALL("UP1") ;Call the subroutine and execute
...
END_CHANGE
...
//END
RETURN
//B(PROG1) ;Block start
SUB(UP2) ;Subroutine start
IF VAR1.val=="Otto"
VAR1.val="Hans"
RETURN ;If the variable value = Otto,
;the value Hans is assigned to the
;variable and the subroutine
;is terminated at this point
ENDIF
VAR1.val="Otto" ;If the variable value ≠ Otto,
;the value Otto is assigned to the
;variable
END_SUB ;Subroutine end
//END ;Block end
Effect
1. All active variable contents (input/output fields) in the display range are output
again with the background and foreground.
2. All active and visible short description texts, graphic texts and unit texts are
output again without clearing the text background first.
Generating
NC code
The GC (Generate Code) function generates NC code from the OUTPUT method.
GC("Identifier"[,"Target file"][,Opt])
where:
Identifier Name of OUTPUT block from which code is
to be generated
Target file Path name of target file for MMC or NC file system
Opt Option for generating comments:
1: Do not create comments in the generated code
CAUTION: This code cannot be recompiled.
0: Default, generate code with comment for
recompilability
Note
Invalid variables generate a blank string in generated NC code and an error
message in the log book when they are read.
Note
The GC function cannot be called in sub-forms because variables originating from
master forms can be used in sub-forms. These variables would not, however, be
available in response to a direct call.
When generated code is processed manually with the Editor, the number of
characters for values created by the code generation routine must not be
changed. Changing these values would make it impossible to recompile the code.
Remedy:
Recompile,
enter changes using the configured screen form (e.g. 99 Æ 101)
GC
//M(TestGC/"Code generation:")
DEF VAR1 = (R//1)
DEF VAR2 = (R//2)
DEF D_NAME
LOAD
VAR1 = 123
VAR2 = -6
END_LOAD
OUTPUT(CODE1)
"Cycle123(" VAR1 "," VAR2 ")"
"M30"
END_OUTPUT
PRESS(VS1)
D_NAME = "C:\TMP\MESSEN.MPF"
GC("CODE1",D_NAME) ;NC code:
Cycle123(123, -6)
M30
Write from OUTPUT method in file
C:\TMP\MESSEN.MPF
END_PRESS
Note
To store the NC code from the OUTPUT method directly in the NC, the path must
be defined as follows:
"/_N_MPF_DIR/_N_MESSEN_MPF"
Note
With the following functions, both with MMC 100.2 and with MMC 103, DOS
paths (e.g. \MPF.DIR\TEST.MPF) are used.
//M(TestGC/"Code generation:")
DEF VAR1 = (R//1)
DEF VAR2 = (R//2)
DEF D_NAME
LOAD
VAR1 = 123
VAR2 = -6
END_LOAD
OUTPUT(CODE1)
"Cycle123(" VAR1 "," VAR2 ")"
"M30"
END_OUTPUT
PRESS(VS1)
D_NAME = "C:\TMP\MESSEN.MPF"
GC("CODE1",D_NAME) ;Write code from OUTPUT method in
;file C:\TMP\MESSEN.MPF
END_PRESS
PRESS(HS8)
D_NAME = "\MPF.DIR\MESSEN.MPF"
AP(D_NAME) ;Load file into NC
END_PRESS
With MMC100.2/HT6 this function has the same effect as Delete enable.
PP("File")
where:
File Complete path name of NC file to be
NC file
PP("\MPF.DIR\MESSEN.MPF")
//M(TestGC/"Code generation:")
DEF VAR1 = (R//1)
DEF VAR2 = (R//2)
DEF D_NAME
LOAD
VAR1 = 123
VAR2 = -6
END_LOAD
OUTPUT(CODE1)
"Cycle123(" VAR1 "," VAR2 ")"
"M30"
END_OUTPUT
PRESS(VS1)
D_NAME = "C:\TMP\MESSEN.MPF"
GC("CODE1",D_NAME) ;Write code from OUTPUT method in
;file C:\TMP\MESSEN.MPF
END_PRESS
PRESS(HS8)
AP("\MPF.DIR\MESSEN.MPF") ;Load the file into the NC
SP("\MPF.DIR\MESSEN.MPF") ;Select file
END_PRESS
DP("\MPF.DIR\CFI.MPF")
Note
Channel-dependent PI Services always refer to the current channel.
PI Services which require the TO area (PI Services of tool functions) always refer
to the TO area allocated to the current channel.
Note
An external function must have at least one return parameter.
//M(FORM1)
DEF VAR1 = (R)
DEF VAR2 = (I)
DEF RET = (I)
FCT InitConnection = ("c:\user\mydll.dll"/I/R,I,S/I,S)
Note
When codes are generated with the GC function, only numerical values in
decimal or exponential notation are evaluated, but not those in binary or
hexadecimal notation.
Binary: ‘B01110110‘
Decimal: 123.45
Hexadecimal: ‘HF1A9‘
Exponential: ‘-1.23EX-3‘
Note
Numerical values in binary, hexadecimal and exponential notation must be
enclosed in apostrophes.
VAR1 = ‘HF1A9‘
REG[0]= ‘B01110110‘
DEF VAR7 = (R//‘-1.23EX-3‘)
+ Addition
- Subtraction
* Multiplication
/ Division
MOD Modulo operation
() Parentheses
AND AND operator
OR OR operator
NOT NOT operator
Example:
VAR1.VAL = 45 * (4 + 3)
Bit-serial operators
BOR Bit-serial OR
BXOR Bit-serial XOR
BAND Bit-serial AND
BNOT Bit-serial NOT
SHL Shift bits to left
SHR Shift bits to right
SHL operator
Syntax:
variable = value SHL increment
Function:
Bits are shifted to the left using the function SHL. You can specify both the value to
be shifted and the number of shift increments directly or via a variable.
If the limit of the data format is reached, the bits are shifted beyond the limit without
displaying an error message.
Example:
PRESS(VS1)
VAR01 = 16 SHL 2 ;Result = 64
VAR02 = VAR02 SHL VAR04 ;Convert contents of VAR02 to 32-bit unsigned
;and shift contents to left by number of bits
;specified in VAR04. Then convert
;32-bit value back to format of
;variable VAR02.
END_PRESS
SHR operator
Syntax:
variable = value SHL increment
Function:
Bits are shifted to the right using the function SHR. You can specify both the value
to be shifted and the number of shift increments directly or via a variable.
If the limit of the data format is reached, the bits are shifted beyond the limit without
displaying an error message.
Example:
PRESS(VS1)
VAR01 = 16 SHR 2 ;Result = 4
VAR02 = VAR02 SHR VAR04 ;Same effect as SHL but shift to right
Table 3-10
Mathematical functions
SIN(x) Sine of x
COS(x) Cosine of x
TAN(x) Tangent of x
ATAN(x, y) Arc tangent of x/y
SQRT(x) Square root of x
Mathematical functions
Note
The functions operate with radian measure. The functions SDEG() and SRAD()
can be used for conversion.
VAR1.VAL = SQRT(2)
Table 3-11
Constants
PI 3.14159265358979323846
FALSE 0
TRUE 1
VAR1.VAL = PI
Table 3-12
Comparison operators
== Equal to
<> Not equal to
> Greater than
< Less than
>= Greater than or equal to
<= Less than or equal to
IF VAR1.VAL == 1
VAR2.VAL = TRUE
ENDIF
3.3.3 Conditions
Condition with a command:
IF
...
ENDIF
String concatenation
Strings can be processed as part of the configuration. These allow text to be
displayed dynamically or different texts to be chained for the purpose of code
generation.
The following rules must be observed with regard to string variables:
Logic operations are processed from left to right.
Nested expressions are solved from the inside outwards.
No distinction is made between uppercase and lowercase type.
Strings can be deleted simply by assigning a blank string.
Strings can be attached after the equal sign using the operator "<<".
Quotation marks (") in the string are represented by two successive quotation mark
symbols.
Strings can be checked for equality in IF instructions.
Examples
Default settings for the following examples:
VAR1.VAL = "This is an"
VAR8.VAL = 4
VAR14.VAL = 15
VAR2.VAL = "error"
$85001 = "This is an"
$85002 = "alarm text"
Chaining of strings:
VAR12.VAL = VAR1 << " Error."
;Result: "This is an error"
Deleting a variable:
VAR10.VAL = "" ;Result: Blank string
String length
Syntax:
LEN(string | varname)
Parameter:
string Every valid string expression. NULL is output if string is empty
Function:
Determine the number of characters in a string.
Note:
Only one of the two parameters is allowed.
Example:
DEF VAR01
DEF VAR02
LOAD
VAR01="HELLO"
VAR02=LEN(VAR01) ;Result = 5
END_LOAD
Find a character
Syntax:
INSTR(start, string1, string2 [,direction])
Parameter:
start Number, position from which string1 is searched for in string2.
This parameter defines the start position for the search. Enter 0
to start searching at the beginning of string2.
Function:
INSTR returns the position of the first occurrence of a specified character in a
string.
Note:
0 is returned if string1 does not occur in string2.
Example:
DEF VAR01
DEF VAR02
LOAD
VAR01="HELLO/WORLD"
VAR02=INST(1,"/",VAR01) ;Result = 6
END_LOAD
Parameter:
string Character string or variable with the string to be
processed
length Number of characters that are to be read out
Function:
LEFT returns a string containing the specified number of characters starting from
the left side of a string.
Example:
DEF VAR01
DEF VAR02
LOAD
VAR01="HELLO/WORLD"
VAR02=LEFT(VAR01,5) ;Result = "HELLO"
END_LOAD
Parameter:
string Character string or variable with the string to be
processed
length Number of characters that are to be read out
Function:
RIGHT returns a string containing the specified number of characters starting from
the right side of a string.
Example:
DEF VAR01
DEF VAR02
LOAD
VAR01="HELLO/WORLD"
VAR02=RIGHT(VAR01,4) ;Result = "WORLD"
END_LOAD
Parameter:
string Character string or variable with the string to be
processed
Example:
DEF VAR01
DEF VAR02
LOAD
VAR01="HELLO/WORLD"
VAR02=MIDS(VAR01,4,4) ;Result = "LO/W"
END_LOAD
Replacing characters
Syntax
REPLACE ( String, FindString, ReplaceString [, Start [, Count ] ] )
Parameter:
String , in which the FinString is to be replaced by the
String
ReplaceString
FindString String to be replaced
ReplaceString Replacement string (is used instead of the FindString)
Start position from which a search is made or replacement
Start
made
Number of characters that are to be searched from the Start
Count
position after the FindString
Function:
The REPLACE function replaces a character/string in a string by another
character/string. It is similar to the basic function of the same name.
Return values:
Registers
Registers are needed to be able to exchange data between different screen forms.
Registers are assigned to a screen form. They are loaded when the first screen
form is generated and assigned the value 0 or a blank string.
REG [x]
where:
x Number of register with x = 0...19
Real or String type = Variant
Registers with x ≥ 20 are used by Siemens.
Note
Registers may not be used directly in OUTPUT blocks for generating NC code.
Register value
The assignment of values to registers is configured in a method.
Identifier.val = Register value
or
Identifier = Register value
where:
Identifier Name of register
Register value Value of register
UNLOAD
REG[0] = VAR1 ;Assign value of variable 1 to
register 0
END_UNLOAD
UNLOAD
These registers can then be assigned to local variables again in the next screen
form.
LOAD
VAR2 = REG[0]
END_LOAD
Note
If a new form is generated from an existing form by means of the LM function, the
contents of registers are automatically transferred to the new screen form at the
same time and so are available for further calculations in the second screen form.
Register status
The Status property can be used to scan a register for valid contents. Status is a
read-only property.
Identifier.vld
where:
Identifier Name of register
The result of the scan can be:
FALSE = invalid value
TRUE = valid value
One possible use for the register scan function is to ensure that a value is written to
a register only if the relevant screen form is a "master screen form".
IF REG[15].VLD == FALSE ;Scan validity of register
REG[15] = 84
ENDIF
VAR1 = REG[9].VLD ;Assign Var1 the value of the status scan
;of REG[9]
Note
The FOC function cannot be applied to variables with input mode wr = 0 and
wr = 4 or to Help variables.
Entry
The ENTRY variable can be used to check by what method a screen form has
been called.
ENTRY
The result of the scan can be:
0 = No programming support
1 = Programming support (the screen form was called under
programming)
2 = Programming support + default from
previous screen form (sub-screen form)
3 = Program support + recompilation
4 = Programming support + recompilation with generated
comments and # characters
5 = Programming support + recompilation with generated
comments but no # characters
S_CHAN
In SW 6.1 and higher, variable S_CHAN can be used to determine the number of
the current channel for display or any evaluation purposes.
CURPOS
Using the CURPOS variable, it is possible to call or manipulate the position of the
cursor in the active input field of the current screen form. The variable indicates
how many characters are located in front of the cursor. If the cursor is located at
the start of the input field, then CURPOS assumes the value of 0. If the value of
CURPOS is changed, then the cursor is positioned at the appropriate location in
the input field.
In order to be able to respond to changes in the variable value, it is possible to
monitor for changes using a CHANGE block. If the value of CURPOS changes,
then a jump is made to the CHANGE block and the instructions contained there are
executed.
The log book is a file (Error.com) to which error messages generated by syntax
interpretation are written.
The operator himself must set up the file in the comment directory (MMC 103).
DEF VAR1 = (R)
DEF VAR2 = (R)
LOAD
VAR1 = VAR2 + 1 ;Error message in log book because
;VAR2 has no value
The system does not start to interpret syntax until the start softkey has been
defined and a screen form with start and end identifiers and a definition line has
been configured.
//S(Start)
HS6=("1st screen form")
PRESS(HS6)
LM("Screen form1")
END_PRESS
//END
//M(Form1)
DEF Var1=(R)
//END
If "Expanding the Operator Interface" detects any errors when interpreting the
screen form configuration files, these will be stored in the file ERROR.COM
- with MMC 100.2 and HT6 on the RAM drive,
- with MMC 103, in the directory \DH\COM.DIR\.
This file is deleted before every new screen form. It details
- which action was affected by an error,
- the row and column number of the first defective character and
- the whole defective line in the configuration file.
If the screen form was created using the PC test environment, then the error file
will be stored in the directory referenced by environment variable RAMDISK
(MMC 100.2/HT6). It can be read together with the communication error log in the
"Services" operating area by means of PCIN via the R-232 interface.
Editing in
ERROR.COM
MMC 103:
Call the editor in the "Services" or "Start-Up" area.
MMC 100.2/HT6
Operating area "Start-Up", Access mode "Manufacturer", MMC, EDIT, New,
E:\ERROR.COM.
Notes
Note
For the sake of compatibility, the cycles support (//C...) function is still supported
by the description language used in earlier versions and not by the syntax of the
"Expanding the Operator Interface" system.
Configuration file
The definition of new screen forms for programming support is stored in
configuration file AEDITOR.COM.
Newly configured screen forms can be displayed in the Editor main screen through
selection of 5 start softkeys (horizontal softkeys 2, 3, 4, 5 and 6).
The default labels for softkeys 2 to 5 are "Contour", "Drilling", "Milling" and
"Turning".
In SW 6.1 and higher, horizontal softkeys 14 and 15 (softkeys 6 and 7 in the
expanded menu) are assigned the "Gauge turning" and "Gauge milling" functions.
5 access softkeys
Find Text
The "Find text" function is used to search for a string from the current cursor
position in the NC program currently selected in the Editor and to output its value.
Search backwards from the current cursor position:
SB ("String")
Search forwards from the current cursor position:
SF ("String")
where:
String Text to be found
• A blank must be inserted before and after the search key unit, consisting of
search string and its value, in the currently selected NC program.
• The system does not search for keys within comment text or other strings.
• The value to be output must be a numerical expression. Expressions in the form
of "X1=4+5" are not detected.
• The system recognizes hexadecimal constants in the form of X1='HFFFF',
binary constants in the form of X1='B10010' and exponential components in the
form of X1='-.5EX-4'.
Note
The value of a string can be output if it contains the following between string and
value:
• Nothing
• Blank space
• Equality sign
X100 Y200
Abc=SB("Y") ;The variable Abc contains the value 200
or
X100 Y 200
Abc=SB("Y") ;The variable Abc contains the value 200
or
X100 Y=200
Abc=SB("Y") ;The variable Abc contains the value 200
Recompile
In the Programming support system, it is possible to recompile NC code that has
been generated with the GC function and to display the variable values in the I/O
field of the screen form again.
Variables from the NC code are transferred to the screen form.
At the same time, the variable values from the NC code are compared with the
calculated variable values from the configuration file. If the values do not coincide,
an error message is written to the log book because values have been changed
during NC code generation.
If the NC code contains the same variable several times, it is evaluated at the point
where it last occurs during recompilation.
A warning is also written to the log book.
Variables which are not utilized in NC code during code generation are stored as
user comment. The term "user comment" refers to all information required to
recompile codes. User comment must not be altered.
Note
The block consisting of NC code and user comment can be recompiled only if it
starts at the beginning of a line.
The following value is displayed for VAR1 in the input screen form:
VAR1=222
Introduction
When using the cycle support in the part program, in front of and behind the cycle
call, additional comment lines are generated that are used for re-compilation.
These lines start with ;# ... .
When cycles are called, that were directly noted using the editor (also "old" cycles),
then this information is missing. A description is provided in the following text as to
how the information for cycles, contained in the lines in ;# can be provided by
configuring INI files. This means, that after re-compilation, it will be possible to work
with the following using the screen form support:
For Siemens cycles, the required configuration files are included in the scope of
supply.
For screen forms, generated with expand operator interface, which are used to
support user cycles, then the information in the screen form descriptive files can be
used for this technique.
In order to define whether cycles with ;# lines are to be processed in the part
program, or re-compiled via the configuration files, can be defined for each cycle in
the configuration itself.
Using this technique, for the directly noted "old" cycles (SW 4.x), the
expansion by ;# lines, required for screen form support, can be optimally
generated in the part program.
Requirement:
For these cycles, a configuration generated using "expand operator
interface" resources must exist/be generated.
Configuration
The wizard.ini file can be stored in the following directories:
..-\user
..-\oem
..-\hmi_adv
..-\mmc2
A search is made in the specified directories in this sequence and the information
of the section
Cycle-specific entries with the following form are located in the particular paket.ini
files
[cycleName] Name of the cycle' as section entry
Mname= mandatory, screen form name
Dir= mandatory, directory of the file with the screen form information
Dname= mandatory, file with screen form information
Output mandatory, name of the OUTPUT block
Anzp= mandatory, number of parameters (defined variables)
Version= optional, cycle version, without data 0
Code_typ= optional, output with = 0 or without = 1 ;# lines
Example
[CYCLE83]
Mname=CYC83
Dir=cst.dir
Output=bohren.ini
Anzp=17
Version=3
Code_typ=0
Details
A differentiation is made between various versions of cycles with the same name
using the version number.
Main block/secondary block and block numbers in front of the cycle call are kept
unchanged.
;NCG#CYC94#\CST.DIR\DREHEN.COM#NC1#1#*NCG;*RO*;*HD*
;##########*NCG;*RO*;*HD*
/1234 :44 CYCLE94(,,"",)
;#END#*NCG;*RO*;*HD*
Notes
5.1 Introduction
This Section involves the configuring of
• a group of 6 hotkeys on the OP 010 and OP 010C or Sinumerik keyboards with
hotkey blocks
• the optional reconfiguration of the "Machine" and "Menu Select" keys
• keys (e.g. machine console keys) and events evaluated by the PLC, which, as
PLC keys or "virtual keys", can initiate configured sequences of operations in
the HMI system.
Overview
MCP
The 6 OP hotkeys can be used to display any HMI operating area directly. This
shortens the usual selection process via the main menu. The standard assignment
of the 6 hotkeys can be reconfigured.
The interface between the PLC and the HMI enables a PLC key to be transferred
from the PLC to the HMI. The operations initiated on the HMI system in this way
can be configured. Key numbers 50 to 254 are available for use by the PLC.
As an option, the "Machine" and "Menu Select" keys can be configured in the same
way as the 6 OP hotkeys. They are assigned to HK7 and HK8.
Configuration is carried out using the "Expanding the Operator Interface" system
functions described in the previous sections.
Applications
• Selection of operating areas (e.g. Machine, Parameters, etc.)
• Selection of specific submenus (e.g. selection of the alarm screen in the
Diagnosis area)
• Initiation of actions (e.g. selection of the tool list in the Parameters area and
pressing of softkey HS3)
• Specific selection of menus created using the "Expanding the Operator
Interface" system
• Selection of additional screens, depending on the current operating situation, in
screens created using the "Expanding the Operator Interface" system.
5.1.1 OP hotkeys
Standard layout
The 6 OP hotkeys are laid out in 2 lines, each of which contains 3 keys:
Line 1
Label Depends on OP
(no symbol)
OP10 Machine Program Offset
OP10C Machine
OP10S Position
Configured as HK1 HK2 HK3
Line 2
Label Prg. Manager Alarm Custom
(no symbol)
Details about HK7 and HK8 can be found in 5.1.3 Configuring the M key and
Menu Select as HK7, HK8.
Note
Hot keys 1 and 7 (M key) cannot be determined by the hardware on the OP10S
(position of labeling). Hot key 7 is always triggered when one of the keys is
pressed. If HK1 is configured, this event can only be triggered by an external
(MFII) keyboard.
Directories
For HMI Advanced, the file can exist in various directories. These are:
• user
• oem
• add_on *)
• mmc0w32 *)
• mmc2 *)
• hmi_adv *)
The files are executed in the above sequence. Entries in the directory which
appears at the beginning of the sequence will disable existing entries in directories
which appear later in the sequence.
*) These directories are reserved for Siemens.
The assignments for HK1 to HK6 are supplied, saved as follows in Keys.ini in
directory mmc2 for the standard system:
Key Function
HK1 Position Machine operating area, last screen
HK2 Program Program operating area, last screen
HK3 Offset Parameters operating area, last screen
HK4 Prg. manager Main screen programming
HK5 Alarm Diagnosis operating area, alarm screen
HK6 Custom Default Custom operating area, last
screen
(user-configured operator interface)
Key Function
HK1 Position Machine operating area, last screen
HK2 Program Program editor, last status
HK3 Offset Offset area, last status
HK4 Prg. manager Program directory last status
HK5 Alarm Diagnosis operating area, alarm screen
HK6 Custom Default Custom operating area, last
screen
(user-configured operator interface)
In HMI Embedded, the data in Keys.ini can be adapted using the Software
Configuration Kit (SCK):
Entry format
Details about the input format can be found in the "Hotkey event" subsection
below. To enable a better understanding of the input format, multiple keypresses
will be described first.
Multiple keypress
A function extension determines the sequence when the hotkey is pressed
repeatedly:
1. The number "n" in the key data in file Keys.ini represents the number of
keypress repeats, thus allowing a separate task/state/action combination to be
assigned each time the hotkey is pressed. This means that each time the key
is pressed, a change of state can take place and a screen and a softkey can
be selected.
2. When the user changes to another operating area, the repeat status of the
hotkey is cleared. In the new area, the hotkey is considered not to have been
pressed.
It does not matter how the user changed to the other operating area (operating
area menu, etc.). In addition, each time a function key is pressed (e.g. softkey,
area switchover key, channel switchover key, etc.), the status is reset.
3. Inputting data into fields in the current screen form does not interrupt the
repetition sequence. Pressing a softkey in the current screen form interrupts
the repetition sequence with the softkey which was used to call the current
screen form.
Note
Multiple keypress is possible for HK1–HK8 and for keys HK9–HK49, which are
reserved for Siemens.
The keys.ini configuration file has a dedicated section for assigning the ini files for
PLC keys. Without this entry, the ini files will not be detected. The default settings
are as follows:
[HMI_INI_FILES]
Task0=machine.ini
Task1=paramet.ini
Task2=program.ini
Task3=services.ini
Task4=diagnosis.ini
Task5=startup.ini
Task6 = shopmill.ini alternative Task6 = shopturn.ini depending on the system,
mandatory!
Task11=custom.ini
Hotkey-Event
Design:
The maximum number of attributes which can be assigned to a hotkey event are
the 4 attributes in bold print above.
The KEY key attribute identifies the event and must always come first. All other
attributes are optional, but at least one other attribute must be specified. These
attributes can appear in any sequence in the line.
• Attribute key (hotkey)
The value x.n contains the hotkey number x and a discrete event n
corresponding to the nth activation of the key (when the key is pressed several
times in succession).
For example, Key 3.5 addresses the hotkey event for HK3, 6th activation.
The range of values of the hotkey numbers is from 1 - 254.
The range of values for the event n is from 0 - 9 (10 keystrokes).
Hotkeys 1 - 8 are assigned to the keys of the Ops (refer to 5.1.1 OP hotkeys).
Hotkeys 9 - 49 are reserved for Siemens. PLC-specific keys from 50 - 254 are
also available. These keys are not actual hotkeys, but are used for selecting
screen forms via the PLC (virtual keys ). Keys 50 - 254 can also be configured
without a task. In this case, the event is always assigned to the current task.
• Attribute Task (operating area)
A hotkey is assigned to an operating area (task) via a task number. The task
number also defines the horizontal softkey to which the operating area is
assigned in the area switchover menu. This creates a permanent connection
between the task number and the corresponding softkey. In the HMI system,
there are three softkey menus (two in HMI Embedded) which are reserved for
the area switchover function. The default assignments are as follows:
Pressing the ETC key again accesses softkey menu 3 (only possible in HMI
Advanced):
SK1 → Task16
...
SK8 → Task23
In HMI Advanced, the range of values for the task numbers is between 0 and
23. In HMI Embedded it is between 0 and 15.
If no task is specified, the event is assigned to the current task (current operating
area).
• Attribute State:
The State attribute can be used to select a specific screen within a task. The range
of values depends on the individual application and is limited to between 0 and
65534 (65535 is used by the system). A list of available states is stored in
• Attribute Action:
The Action attribute can be used to select a specific softkey within a task. In
order to be effective, the attribute must be set from a defined state, e.g. the
main menu.
The range of values depends on the individual application and is limited to
between 0 and 17 (see below). The Action attribute of particular importance.
With a value of ≥ 100, it activates a display selection via the "Expanding the
Operator Interface" system mechanism.
Actions in the value range 0 - 99 are not executed for ShopMill/ShopTurn.
Note
A power ON is required in order for the changes to keys.ini to take effect.
Configuring example
[KeyConfiguration]
KEY1.0 = Task:=0, State:=10, Action:=2 ;Hotkey 1, 1st activation
KEY1.1 = State:=10, Action:=3 ;Hotkey 1, 2nd activation
KEY1.2 = Action:=4 ;Hotkey 1, 3rd activation
RECALL key 16
ETC key (only for HMI 17
Embedded)
Hotkey assignment:
MF II keyboard Hotkey
M key (Machine) SHIFT+F10 HK7
Menu Select (area F10 HK8
switchover)
If there is no entry in the Keys.ini configuration file for hotkey 7, the key will not be
mapped as a hotkey but will retain its original function (compatible mode). A key
definition without a response will be assigned the <empty> attribute (see example).
Examples
[KeyConfiguration]
; Activate mapping of the M key to hotkey 7 and set new
; key reaction
Key7.0 = Task:= 3, State := 10
\user and
\oem
searched earlier during processing. Only deviations in the settings must be stored,
not the complete block.
HMI Advanced
The ETC key, Action 17, has no effect.
An Action value >= 100 automatically switches the HMI software to "Expanding the
Operator Interface" operational sequences.
If Action >= 100, the configuration of the INI files determines which softkey menu
or screen form should be displayed and in which state.
Machine:
machine.ini
[KeyConfigurationAuto]
[KeyConfigurationMDA]
[KeyConfigurationJOG]
Parameter:
paramet.ini
[KeyConfiguration]
Programming:
program.ini
[KeyConfiguration]
Services:
services.ini
[KeyConfiguration]
Diagnostics:
diagnosis.ini
[KeyConfiguration]
Start-up:
startup.ini
[KeyConfiguration]
Custom
custom.ini
[KeyConfiguration]
JobShop
The INI files for the JobShop products ShopMill and ShopTurn are called
shopmill.ini and shopturn.ini.
Both files contain the following sections, in which 5.2.2 Configuration "Expanding
the Operator Interface" functions can be configured as described in
[MachineManual]
...
[MachineAutomatic]
...
[ProgramManager]
...
[Program]
...
[MessagesAlarms]
...
[ToolsZeroOffset]
...
[MachineMDI]
5.2.2 Configuration
One or more states (according to the State list) can be configured for each action
(≥ 100) and you can also specify which "Expanding the Operator Interface" function
is to be initiated.
If nothing is configured in these INI files, no screen forms or softkey menus will
appear.
General notation:
Action.State=Screen form/softkey menu to be loaded, configuration file
Examples
[KeyConfiguration]
100.10=LS("Softkey1","param.com")
100.30=LM("Form1","param.com")
101.10=LS("Softkey1","param.com")
101.30=LM("Form2","param.com")
102=LM("Form2","param1.com")
If an Action 100 is initiated in state (status/screen) 10, the softkey menu configured
in file param.com will be displayed with the name softkey1.
If Action 102 is initiated, the screen form with the name screen form2 will be called
in the actual screen. This screen form is configured in file param1.com.
Note
In M:N mode, the area for the 2nd HMI interface is DB19.Byte60
See also: Description of Functions B3 "Interfaces in DB19 for M:N".
Acknowledgment
An HMI system acknowledgment is divided into two steps:
1. In the first step, the HMI software transfers the control information 255 to
DB19.Byte10.
2. In the second step, the actual acknowledgment takes place on the PLC in
which DB19.Byte10 is cleared.
This is necessary in order that, despite the lack of synchronism between the HMI
and the PLC, the same key code transferred twice in immediate succession can be
detected by the HMI. This defined virtual key activation enables the HMI to identify
every PLC key sequence uniquely. The control information is of no significance to
the PLC program (transparent) and must not be changed.
Error
If the task switchover cannot be executed, the operator interface will send a
message to indicate this.
There is an interface between the PLC and the MMC/HT6 to select the displays.
These PLC displays offer the same means of display and functions as for the
displays selected via the softkeys.
MMC 1:
DB19.DBW28: Display number
DB19.DBB30: PLC control bits Æ MMC, PLC byte
DB19.DBB31: Control bits MMC Æ PLC, MMC byte
MMC 2:
DB19.DBW28: Display number
DB19.DBB80: Control bits PLC Æ MMC, PLC byte
DB19.DBB81: Control bits MMC Æ PLC, MMC byte
PLC byte:
Bit0 Display selection
Bit1 Display deselection
MMC byte:
Bit0 Display selection/deselection accepted
Bit1 Display is selected/deselected
Bit2 Display is selected
Bit3 Display is deselected
Bit4 Error, display selection not possible
Bit7 Inactive bit
Two bytes are used for the display number to be transferred by the PLC, one byte
respectively (PLC byte and MMC byte) for coordinating the display selection.
The interface is operated by the PLC OEM program with the following functions:
Display selection
The relations with the individual steps are shown in the above table by the numbers
in brackets (step numbers).
Display deselection
1. The PLC sets bit1 for display deselection in the PLC byte if bit1 and bit2 are set
in the MMC byte and bit7 is reset.
2. The MMC/HT6 acknowledges to the PLC that it has accepted display
deselection by setting bit0 in the MMC byte. At the same time, the value zero is
written to bit3 and bit4 in the MMC byte.
3. The MMC/HT6 acknowledges the display deselection to the PLC by setting bit3
and resetting bit0, bit1 and bit2 in the MMC byte if the interpreter is terminated.
4. The PLC resets bit1 in the PLC byte.
After display deselection by the PLC or the EXIT command, the MMC/HT6
switches back to the last selected MMC display.
Operating areas
With the MMC 103, the displays are shown in a separate operating area similar to
the measuring cycle displays. This operating area can be selected manually by
means of the sixth softkey (PLC displays) on the second operating area menu. If
no PLC display is active when the area is selected, the text "Currently no PLC
display active" is displayed in the header. The PLC is informed when the area is
selected/deselected manually via bit2 of the MMC byte.
It is also possible to change to other operating areas via the MMC 103's operating
area after a display has been selected by the PLC.
Examples
Example in accordance with Subsection 5.1.2 Assigning functions to keys:
[KeyConfiguration]
HK50.0 = Action:=100
The configuration shown here does not execute a change of task or state and
therefore remains in the current task and screen. An Action 100 is forwarded.
A change of task and state could be configured here in exactly the same way.
HK50.0 = Task:=1, State:=10, Action:=100
2.) The main actual value screens for each mode (softkey vertical 6)
Switching between the WCS and MCS is possible via the PLC.
State Function
10 Alarms
20 Messages
30 Alarm log
40 Service displays
50 PLC status
State Function
0 NC axes and drives
10 Machine data
40 PLC status
50 Drive/servo
60 MMC
50 Measure Tool
16 Length manual *)
17 Diameter manual *)
13 Length auto *)
14 Diameter auto *)
51 *)
15 Calibration probe *)
52 *)
20 MDA
4 Positioning
18 Face milling
1 Settings
5.7.4 Program
State Function
400 Program listing
Simulation:
412 Top view
413 3-level view
414 Volume model
5.8.4 Program
State Function
400 Program listing
Simulation:
412 3-window view
413 Side view
414 Front view
415 Volume model
Note
Screens marked *) may also have been configured using the "Expanding the
Operator Interface" system. In this case, the screen configured by the user is
addressed.
In ShopMill and ShopTurn, the active states in DB82 DBW44 are sent to the PLC.
5.10 Examples
Possible entries for Keys.ini
1
...
6 Hardkeys OP
7
Optional hardkeys OP
8
9
...
Reserved for Siemens
49
50
... OEM applications
81
82
... General applications
254
Definitions of applications:
[KeyConfigurationAuto]
[KeyConfigurationMDA]
[KeyConfigurationJOG] [KeyConfiguration]
//S(Toolbar1)
...
5.12 Terms
Hotkeys
6 keys on OP010, OP010C and Sinumerik keyboards with hotkey blocks. Pressing
the keys selects an operating area directly.
As an option, 2 additional keys can be configured as hotkeys.
PLC keys
PLC keys are provided as hotkeys via the PLC interface of the HMI software. Their
reactions can be configured in the HMI. They are set up as:
- Keys of the machine control panel
- Signal logical interconnections of the PLC that are evaluated
These are also known as "virtual keys".
SK
Softkey
Virtual keys
See PLC keys.
6.1 Introduction
The operating areas described thus far can be extended and modified using
"Expanding the Operator Interface" tools. Extensions can only be applied to
softkeys which have not been used previously. With the resources described in the
following, it is possible both in
The Custom operating area can be accessed directly (on OPs with hotkey blocks:
OP 010, OP 010C) with:
HMI Advanced
The CUSTOM operating area is available as standard and can be reset via an
entry in file regie.ini (control.ini) or assigned to any other horizontal softkey.
HMI Embedded
The CUSTOM operating area is available as standard. It is supplied with the
application diskette and can be assigned to any horizontal softkey by the customer
using the Software Configuration Kit (SCK.exe).
Details for integrating the Custom operating area into the system can be found in
6.1.5 Integrating the Custom operating area.
HMI Advanced
See Integrating the Custom operating area 6.1.5 b).
HMI Embedded
Using the display machine data MD 9016: MM_SWITCH_TO_AREA, you can
define in which operator area HMI-Embedded should run-up; whereby, the
CUSTOM operating are can be specified.
The value in the MD provides the number of the softkey for the required operating
area.
Horizontal softkeys 1 – 8: 1–8
Softkeys of the 1st continue bar after pressing ETC: 9 – 16
The standard default setting is 12.
With hotkey
The CUSTOM hotkey on the OP 010 and OP 010C always activates this operating
area (default). Other additional configurations are possible.
The CUSTOM operating area also permits a configurable text in the operating area
display field in the global menu.
All softkeys are empty and can be assigned as required by the customer using the
"Expanding the Operator Interface" definition and provided with "Expanding the
Operator Interface" functionality.
When switching from and back to the CUSTOM area, the configured screen which
was active before exiting the CUSTOM operating area is active.
HMI Advanced
The operating area is enabled in the regie.ini file and is assigned to a softkey.
Example:
Activation via horizontal softkey 4 in the 1st step softkey menu
(standard assignment).
b) In file control.ini this operating area can also be selected as the standard start-
up area. The entry must be made in section [Miscellaneous]:
PoweronTaskIndex = 11
The corresponding lines can be deactivated by adding a ";" comment line at the
beginning of the line if the Custom area is not to be selected or should not be
activated on start-up.
The area can be assigned to a different softkey by changing the task number.
HMI Embedded
The HMI software for the CUSTOM application evaluates file custom.ini and
decides whether the area should be displayed. The file contains a section for this
purpose (HMI Embedded only):
[Activate]
Activate=True
The operating area is assigned to a horizontal softkey by the customer using the
Software Configuration Kit (SCK.EXE), menu option "Modify configuration".
In order for the Custom operating area to be activated by default on start-up, the
softkey numbers must be entered in display machine data MD 9016:
MM_SWITCH_TO_AREA.
If this display MD has the value -1, HMI Embedded will start up in the operating
area specified as the start-up area with the SCK. (When delivered, softkey 1 in the
main menu Æarea MACHINE).
All Custom area elements which are used to access other elements, e.g.
• softkey menus
• I/O fields
and their associated functions must be configured using "Expanding the Operator
Interface" tools.
In the CUSTOM application, all softkeys are available as "Expanding the Operator
Interface" softkeys.
These softkeys are configured in file custom.com (like the standard version of
aeditor.com) as described below.
JobShop products
The JobShop products ManualTurn, ShopMill and ShopTurn are based on HMI
Embedded.
HMI Embedded WIN32 and HMI Advanced can be combined on a single hardware
platform. Thus, the JobShop products operating systems are available as
alternatives to HMI Advanced on a single hardware platform. The special
considerations for configuration and search strategies for this case are described in
Section 7.4 HMI Embedded and HMI Advanced on a shared hardware platform.
Creating displays
If the configured screen forms are to include graphics, then a suitable graphics
program will be required. The following subsections contain relevant system-
specific information.
Language-dependent texts
Texts used in screen forms can be specified explicitly in configuration files or,
particularly in cases where screen forms are to be displayed in different languages,
stored separately in text files. The syntax for texts in screen forms and alarm texts
is identical. You can choose between:
The selected method must be defined by means of further control file entries on the
MMC 100.2, HMI Embedded, HT6.
• Softkey labels
• Headings
• Help texts
• Any other texts
The names of the language files can be defined by the user and are specified in
COMMON.COM.
For more information, see "Structure of the COMMON.COM control file".
8xxxx 0 0 "text"
where:
xxxx 5000 to 9899 (text identification number range reserved for users).
The numbers must only be assigned once.
Text Text that appears in the screen form, enclosed in quotation marks
Examples:
85000 0 0 "Retraction level"
85001 0 0 "Drilling depth"
85002 0 0 "Thread pitch"
85003 0 0 "Pocket radius"
Parameters 2 and 3 are separated by blanks and act as control characters for
alarm text output. To ensure that the text format is identical to that of the alarm
texts, these two parameters must always be set to 0.
%n Line break
Details of how to make the appropriate entries in file COMMON.COM for the
MMC 100.2, HMI Embedded, HT6 can be found in the next subsection.
Storage location
The central control file COMMON.COM must be stored in one of the following NC
directories:
1. \CUS ; User cycles directory
2. \CST ; Standard cycles directory
3. \COM ; Comment directory
The system searches through the directories for COMMON.COM in the following
order. The first file with this name is evaluated.
In SW 6.2 or higher, PCU 20 and PCU 50 .bmp images and their conversions with
up to 256 colors can also be used (PCX2BIN application).
Performance
If screen form configuration files are executed from the Flash memory, screen
forms are displayed and processed significantly faster. This option should therefore
be chosen where possible.
Note
The file is supplied together with the cycles. It must always be set up on the NC.
Syntax of COMMON.COM
Comments:
All characters contained within a line after a semicolon ";" are treated as comment
and are not evaluated.
Parameter:
The general notation is:
Possible parameters:
SCxxx=file or HCyyy=file
SCxxx Softkey Connection (connection between softkey and configuration
file). xxx represents an internal softkey identity of the start softkey
See Chapter 2 "Defining a start softkey".
The softkey identity must be entered directly after SC.
Softkeys will not be displayed unless a softkey connection is defined
for them.
File The configuration file which contains the desired softkey and screen
form definitions.
MMC and HMI file names may only be 8 characters in length. The file
extension is added with a dot.
Examples:
SC101= my_file.com ; (my_file.com on MMC, HMI, NC)
HCyyy Hotkey connection (a connection between real key and configuration
file). yyy represents an internal hotkey identity of the start hotkey
(see Subsection "Start softkeys"). The hotkey identity must be entered
directly after HC.
Only hotkeys for which a hotkey connection has been defined have an
effect.
Note
The files names listed in Table 2-1 are already stored as defaults. The matching
files must however be set up on the NC or MMC, HMI, HT6 by the user.
LAN1=File
File Language-dependent file which contains the foreground
language
(1st language) of all configured texts.
LAN2=File
File Language-dependent file which contains the background
language
(2nd language) of all configured texts.
If parameters LAN1/LAN2 are assigned, then the system looks for language-
dependent texts in these files first before searching through the cycle alarm texts.
The contents of the files specified by LAN1/LAN2 matches the format of the alarm
texts (see Section 7.1 General information about configuring environment). The file
names can be freely assigned as part of the secondary conditions according to
Section 1.3. COM is the file extension. These text files allow texts to be created
directly in online operation which can then be displayed directly in screen forms
created online.
CHK_FILE_EXIST=ram
ram This control flag: specifies whether configuration files must be copied
each time by the NC or whether a check must be made as to whether the
files are already stored on the RAM drive of the MMC 100.2, HMI, HT6.
Possible values:
0:
A check whether the file already exists on the RAM drive is not carried
out. A search is first carried out in
- the NC user cycles directory, then in
- the NC manufacturer cycles directory, then in
- the NC standard cycles directory, then in
- the NC comments directory and finally in
- the Flash File System on the MMC 100.2, HMI Embedded, HT6
This mode is only set while the configuration files are being set up online
on the NC. Changes to configuration files in the NC then become
operative immediately on the MMC 100.2, HMI, HT6, slowing down the
display building process.
1:
Default setting (if CHK_FILE_EXIST has not been set):
The configuration files are read once into the RAM and executed
thereafter from there. (This means:
an improved runtime, but no reaction to changes in the configuration files
in the NC).
LOGSIZE=kB
KB Size of the LOG file in KB (max. size = 64 KB). A LOG file named
ERROR.COM is set up on the RAM disk of the MMC/HT6; its size is
determined by this parameter setting.
CHK_FILE_EXIST = tf
tf 0:
The files are always copied into RAMDISK, even if they are already
there. Existing files are overwritten.
1:
The files are only copied into RAMDISK, even if they are not already
there.
Default setting:
If CHK_FILE_EXIST is not specified, then 1 is assumed. This means that
the files are only copied if they are not already there.
RAMDISK_SIZE = kBrd
kBrd Size of the available RAMDISK spacing in KB for expanding the wizard
directory.
RAMDISK_SIZE can be located at any position - within or outside the
sections. If the element occurs several times, then the first occurrence is
relevant.
Example:
RAMDISK_SIZE=200 ; 200 KB
The standard value (if the element RAMDISK_SIZE was not specified) is
100 KB.
In SW 6.5 and higher, the default value is 300 KB
If, after copying, the selected size has been exceeded, all of the COM
files in the directory for expanding the operator interface on the
RAMDISK are deleted before the next copying operation. (Files for
screen forms in the background (for operating area change) are still
kept.)
Example of COMMON.COM
%_N_COMMON_COM
[MMC_DOS]
sc101=tooth.com ; MACHINE
; Files are located in the
; Flash memory of the MMC
sc111=mda.com
sc122=auto.com
sc207=param.com ; PARAMETER
sc314=aeditor.com ; PROGRAM, Editor
sc315=aeditor.com
sc316=aeditor.com
sc407=dienste.com ; SERVICES
sc507=diagnose.com ; DIAGNOSTICS
sc607=inbetrn.com ; Start-up
sc826=cmm.com ; ShopMill, Machine, AUTO
sc857=cmm.com ; Messages/
sc858=cmm.com ; alarms
sc867=cmm.com ; Tools, ZO
LAN1=stdlan1.com ; Configured form texts
; are in stdlan1.com in the
; Flash memory
LAN2=_N_stdlan2_com ; Background language on NC
CHK_COMMON.COM=1 ; faster processing
; from MMC
LOGSIZE=30 ; 30 kB for LOG of errors in
: the screen forms
[PLC_SELECT] ; declaration of
; displays that can be called from
; the PLC, see below.
PC1= CYC82, drilling.com ; display 1
PC2= CYCLE90, millthre.com ; display 2
This section is for assigning the display numbers to the configured displays. In
general, the syntax of an assignment line is:
Example:
[PLC_SELECT] ;Fixed section introduction
PC1= CYC82, drilling.com ;assignment line
PC2= CYCLE90, millthre.com
PC3=...etc.
In the complete example shown above, the section [PLC_SELECT] is at the end of
Common.com.
Notice:
This mechanism is not compatible with the HMI language concept. It is merely
used for the online creation of language-dependent texts (text phase). As soon as
the user screens have been created their contents must be copied to the relevant
(ALUC.TXT).
The file names can be freely assigned as part of the secondary conditions
according to Section 1.3. COM is the file name extension.
The text files are defined with DOS notation (e.g. LAN1=my_text.com).
If LAN1/LAN2 is not specified, the search is performed in the user cycle alarm texts
(ALUC) and in the standard cycle alarm texts (ALSC) only.
Once the screens have been created the text files specified in LAN1/LAN2 must be
read out of the NC and integrated in ALUC.TXT/ALSC.TXT. Before normal
operation starts entries LAN1/LAN2 must either be removed or marked as a
comment.
Note
To simplify the configuring process on the MMC 100.2, HMI, HT6, a further text
file named SPT.COM (temporary alarm text file) is provided, allowing texts to be
loaded for $8xxxx. This file is needed to avoid having to create file
ALUC_xx.COM in the EPROM during trial runs.
(xx language code as specified in Table 5-1)
Start softkeys
The start softkeys named here can be used to activate the associated configuration
files.
The possible start softkeys for screen forms are predefined. Additional start
softkeys are not possible. Access points are specific to operating areas.
SCxxx=File
SCxxx Softkey Connection (link between softkey and configuration file). xxx
represents one of the internal softkey identities for start softkeys listed
below
File Name of configuration file
The possible start hotkeys for screen forms are pre-defined. No additional start
hotkeys can be configured. Access points are specific to operating areas.
HCyyy=File
HCyyy hotkey connection (connecting the hotkey with the configuration file). yyy
stands for one of the internal hotkey identities listed below for the start hotkeys; file
is the name of the configuration file identities for start hotkeys:
HCyyy Key:
HC1 User key U1
HC2 User key U2
HC3 User key U3
HC4 User key U4
HC5 User key U5
HC6 User key U6
HC7 User key U7
HC8 User key U8
HC11 Special key S1
HC12 Special key S2
HC21 TEACH key
Introduction
While form configuration files are being created or tested, it is useful to store them
on the NC so that they can be edited with the program editor and the result
checked immediately.
Since configuration files have to be copied to the RAM of the MMC, HMI every time
they are accessed by the NC, the resulting access times are long.
For this reason, tested configuration files (except for the control file
COMMON.COM) should be transferred to the Flash File System of the MMC and
executed from there to achieve the best possible performance.
Configuration files are write-protected once they are stored in the Flash File
System.
Displays can only be inserted in screen forms from the Flash File System.
The following sections describe the steps needed to transfer configuration files and
displays to the Flash File System on the MMC 100.2, HMI using a PCMCIA card.
Preconditions, tools
You will need a PC with programmer for PCMCIA cards or a PG with integrated
programming device for PCMCIA cards.
Software requirements:
PCMCIA CARD
Programming
Editor
NC
PCMCIA CARD
replugging for
PRJ1 PRJ2 PRJ3 Common. booting
com
PC or PG
PCMCIA CARD
System environment
Application environment
PCIN/SinuCom PCIN
Sinucopy FFS
Fig. 7-1 Procedure for generating a PCMCIA card with screen form configuration files
Prepare files
1. Install the system environment on your PC/PG
2. Install the application environment on your PC/PG
3. Archive your display data and screen form configuration files as follows using
the ARJ program supplied:
Examples:
abc.com is stored in abc.co_.
my_pic.bin is stored in my_pic.bi_.
4. Check whether the total size of your files meet the requirements outlined in
Section 7.2 in terms of definition and size. If not, you must reduce the space
required by your display images by the following methods:
- Smaller formats
- Less complexity
- Fewer colors
- Fewer display images
- etc.
- Removing texts
Enter your files in the same way as you did for previous entries.
Alternative:
If you wish to integrate the texts for configuring forms into alarm texts, copy them
using an ASCII editor into file
ALUC.TXT in the application environment in the appropriate language-specific
directories.
proj\text\lan
under the directory in which you have installed the application environment. lan
identifies the language:
proj\text\d = German
proj\text\e = Spanish
proj\text\f = French
proj\text\g = English
proj\text\i = Italian
Preconditions
You have installed the PC version of the MMC 100.2, HMI or HT6 software on your
PC/PG.
Procedure
Create COMMON.COM in the directory in which you have installed the PC version
of the MMC100.2, HMI-Embedded or HT6 SW. The data search takes place
according to the search sequence.
Set up the form configuration files and text files in the directory in which you have
installed the PC version of the MMC 100.2, HMI.
Start the PC version of the MMC 100.2, HMI or HT6 software.
The file ERROR.COM, which contains messages about errors in the screen form
configuration files, is stored in the directory to which the environment variable
RAMDISK refers.
7.3.2 Saving configuration files on the hard disk of the MMC 103, HMI
Directories
\DH\CUS.DIR\
\DH\CMA.DIR\
\DH\CST.DIR\
\DH\COM.DIR\
File names
Configuration files with the names listed in Table 2-1 are searched for in directories
in the specified order. If files of the same name are stored in different directories,
then the first file detected according to the search strategy is interpreted.
File sizes
The sizes of configuration files are not subject to any particular restrictions. It
should be noted, however, that large files are processed more slowly.
7.3.3 Saving alarm text files on the hard disk of the MMC 103, PCU50
Directory
\DH\MB.DIR\
File names
ALUC_xx.COM
Table 7-1
Code Language
xx
gr German
uk English
fr French
it Italian
sp Spanish
nl Dutch
fi Finnish
sw Swedish
pl Polish
tr Turkish
ch Chinese
tw Taiwan Chinese
ko Korean
hu Hungarian
po Portuguese
ru Cyrillic
cz Czech
Preconditions
You have installed the PC version of the MMC 103, HMI Advanced software on
your PC/PG.
Directories
The directory structure is the same as on the MMC 103, see above. The error log is
generated in:
\DH\COM.DIR\ERROR.COM
Supplementary conditions
HMI Embedded WIN32 evaluates the mmchome property of section [DHSTART]
in configuration file DH.INI which contains the root directory for the data
management path.
DH.INI must be stored in the BIN directory on which MMC0.EXE is started.
The maximum length for the data management root directory entry is 100
characters.
Booting
On start-up, HMI Embedded WIN32 uses the entries in the Windows Registry to
ascertain where HMI Advanced is installed.
In the directory indicated in the registry, a search is made for file DH.INI in the
subdirectories ..\user, ..\oem, ..\add_on, ..\mmc2 in the sequence specified. If
DH.INI cannot be found there, a search is carried out for the file in the current
directory of HMI Embedded WIN32.
Example:
If HMI-Advanced was found on f:\HMI\HMI-Advanced, then a search for dh.ini is
made in the following sequence:
f:\HMI\HMI-Advanced\user
f:\HMI\HMI-Advanced\oem
f:\HMI\HMI-Advanced\add_on
f:\HMI\HMI-Advanced\mmc2
If the definition for CHK_FILE_EXIST has not been commented out in file
Common.com, CHK_FILE_EXIST 1 is used.
If mmc0.ini cannot be located, the default value is from pc_test 0 (default status on
installation).
The files for the "Expanding the Wizard directory" are searched in the following
sequence. A hit in the above directory disables the corresponding entries in
directories located further down the sequence.
Note
File Common.com is handled differently. See below.
PC system
A connection to the NC is not established.
CUS directory in the data management directory specified in dh.ini
CMA directory in the data management directory specified in dh.ini
CST directory in the data management directory specified in dh.ini
COM directory in the data management directory specified in dh.ini
Current directory in HMI Embedded WIN32
Current directory in HMI Embedded WIN32 packed in *.co_
"Expanding the Wizard directory" directory on the RAM disk
The new search mechanism also includes the directories of the data management
path, relevant for "Expanding the Wizard directory" and the possible archives for
images (cus.arj, cma.arj, cst.arj).
53. Filename.bin in archive CST ARJ in the CUS directory of the data
management path
....
64. Filename.bmp in archive CUS.ARJ in the CST\resolution directory of the data
management path
No PC system
A connection to the NC is established.
PC system
A connection to the NC is not established.
The new search mechanism also includes the directories of the data management
path, relevant for "Expanding the Wizard directory" and the possible archives for
images (cus.arj, cma.arj, cst.arj).
The search mechanism always processes the loop displays first before searching
possible archives. This results in the following search sequence for images:
• Individual image before archive (.bin files are searched for before .bmp files).
Once the search of the unpacked files has been completed, the archives
containing a single file (.bi_, then .bm_) are searched.
• Bitmap name with followed by bitmap name without path
For more information about the search sequence for bitmaps with the various
formats, see "General information about searches".
Softkey expansion
In addition to the horizontal softkeys (HS1-8) already configured, HT6-specific keys
can also be defined. As the HT6 has no vertical softkeys (VS1-8), they cannot be
configured.
Extensions common.com
Section [HT6] has been introduced into the file common.com. The connections for
the special HC keys can be entered here.
HC (Hotkey Connection) represents any one of the keys: UKi, SKi, TEACH
Note
If user keys U1–U8, S1 or S2 are operated on the HT6, any open screen created
with "expand Wizard directory" is closed. This also applies if no response has
been configured for the user key (e.g. with the software development kit or
"expand Wizard directory")!
Notes
8.1 Terms
Table 8-1
Term Explanation
Action Anything that is configured within a → method: → Functions,
→ Calculating variables, → Changing properties, ...
Access level Graduated system of authorization, which makes the accessibility
and utilization of functions on the → operator interface dependent
on the authorization rights of the user.
Array Table or list of data
Attribute Characteristic that assigns an object (→ screen form or → variable)
specific, detailed → properties.
Block Reload unit for → configuration file
Column index Column number of an array
Configuration file File or files, which contain definitions and instructions that deter-
mine the appearance of → Screen forms and their → Functions.
Definition lines Program section in which → variables and → softkeys are defined.
Editor ASCII Editor which with characters can be entered in a file and
edited.
Event Any action, which initiates execution of a → Method: Input of
characters, actuation of → Softkeys, ...
Focus Highlighting on screen which identifies the → Screen form element
that is currently selected for editing/monitoring. Screen form
element marked by the cursor.
Form-independent Softkeys, which are not called from a screen form, i.e. start softkey
softkeys and softkey menus, which the user configures before the first, new
screen form.
Function Sequence of operations programmed in → Methods as a function
of → Parameters.
Graphics Graphic which is displayed when a screen form is opened.
Help display Display, which is opened context-sensitively in relation to screen
form elements.
Help loop Several help references can be configured in a loop for each →
Screen form element, i.e. the references are called up in
succession and when the last reference closes, the first is
displayed again.
Help variable Internal arithmetic variable to which no → Properties can be
assigned, i.e. it is not visible in the → Screen form.
HSx Horizontal → Softkey x
I/O field Input/output field for displaying and modifying values of variables.
Interpreter The interpreter automatically converts the defined code from the →
Configuration File into a → Screen form and controls its use.
Machine data Settings of properties of the SINUMERIK system made by
Siemens/machine manufacturer/end user and stored in the system.
A differentiation is made between:
$MN_... General NC machine data
$MC_... Channel-specific machine data
$MA_... Axis-specific machine data
$MM_... Machine data for operator panel
In addition to these, the system also uses → Setting data and
Drive machine data.
Term Explanation
Main body of screen Header, long text, graphics and → Screen form elements
form
ManualTurn Optimized SINUMERIK application and operator interface for
simple turning machines.
Master screen form → Screen form, which calls another screen form but remains open
when a second screen is displayed.
Method Programmed sequence of operations which is executed when a
corresponding → Event occurs.
MMC 100.2 Computer unit of operator panel front without hard disk
MMC 103 Computer unit of operator panel front with hard disk
NC Numerical Control: System component of a SINUMERIK system
which controls the motional sequences of axes on the basis of →
Parts programs.
NC code Permissible language elements used to write → Parts programs of
the SINUMERIK system
NC function →PI service
Operator interface The term "operator interface" refers in this document to the
information displayed on the screen, including allocated softkeys
and some special operator panel front keys.
Parameters Parameters are variable elements of the programming syntax and
replaced by other words/symbols in the → Configuration file.
Parts programs A program formulated in the NC language, which specifies motion
sequences for axes and various special actions.
PI service → Function, which, on an → NC, executes a clearly defined
operation. PI services can be called from the → PLC and → MMC
100.2/103.
PLC Programmable Logic Control: Programmable controller, which
performs mainly logic operations in the SINUMERIK system.
Programming support Provision of → Screen forms to assist programmers in writing →
system Parts programs with "higher-level" components
Free contour programming
Cycle support
Blueprint programming
→ Recompilation
→ Simulation
directly from the → Editor.
Properties Characteristics of an object (e.g. of a → variable)
RECALL key Standard key on front of operator panel
Recompilation Sections of → NC code can be generated in a → Parts program
from input fields in → Screen forms of the → Programming support
system. Recompilation is the reverse operation. The input fields,
which have created a selected section of NC code, are retrieved
from the NC code and displayed in the original screen form.
Register Memory for data exchange between → Screen forms.
Row index Row number of an array
Screen form Screen display of → Operator interface
Screen form definition Program section from //M..........//END for defining a → Screen form
block
Screen form element Visible component of a → Variable: Short text, graphics text, → I/O
field and unit text
Screen form tree A group of interlinked → Screen forms
Term Explanation
Screen-form-dependent Softkey menu, which is called from a newly configured screen
softkey menu form.
Setting data Data that communicates properties of the machine tool to the NC
control in a way defined by the system software. In contrast to →
Machine data, setting data can be altered immediately by the
operator.
ShopMill Optimized SINUMERIK application and operator interface for 2½D
milling operations.
Simulation Simulation of a → Parts program run (e.g. graphically) without
movement of the actual machine axes.
Softkey Key on front of operator panel, which activates a function displayed
on the assigned area of the screen.
Softkey label Text/image on the screen area, which is assigned to a → Softkey.
Softkey menu All horizontal or all vertical → softkeys
Softkey menu definition Program section from //S..........//END for defining a → Softkey
block menu
Standard application → Operator interfaces that are integrated in standard software.
Start softkey → Softkey, with which the first newly created → screen form is
started.
Start softkey definition Program section from //S(Start)..........//END in which a → Start
block softkey is defined
Sub-screen form → Screen form that is called from another screen form (master
screen form) without the → Master screen form being closed.
System variables NC variable providing the NC states for parts program accesses
and accesses from → MMC.
Toggle field A list of values in the → I/O Field; check with toggle field: The
value input in a field must be the same as one of the listed values.
User comment Comment, which is automatically created during → NC code
generation.
User variable The user can declare user-defined variables for optional use in the
→ parts program or data block.
Variable Designation of a memory location, which can be displayed in a →
Screen form by assigning → Properties and in which input data
and the results of arithmetic operations can be entered.
VSx Vertical → Softkey x
The following color table for screen form configuring is available for the MMC 100.2
and MMC 103 (subset of each standard color table):
1 Black
2 Red/brown
3 Dark green
4 Light gray
5 Dark gray
6 Blue
7 Red
8 Brown
9 Yellow
10 White
Colors for
MMC 103
MMC 100.2
ManualTurn
ShopMill
may be displayed with slight differences.
On the HT6 gray scales exist.
Bitmap color table
Note
With software version 6.3 and higher, HMI Embedded supports the "New Fashion" option.
Some colors in the color palette have changed in this context.
You will find more details below.
HMI Advanced
The following color table in the drawing program must be used for bitmaps in HMI
Advanced.
HMI Embedded
The following color table in the drawing program must be used for bitmaps in HMI
Advanced.
- HMI_EMB_OLD_FASHION.PAL :
This color palette should be used for HMI Embedded SW 6.2 and SW 6.3 with Old
Fashion
Color indices 160 to 231 are available
- HMI_EMB_NEW_FASHION.PAL :
This color palette should be used for HMI Embedded SW 6.3 with New Fashion
Color indices 160 to 231 are available
- HMI_EMB_OLD_AND_NEW_FASHION.PAL :
This color palette should be used for HMI Embedded SW 6.2 and SW 6.3
independent of Old and New Fashion; the bitmaps generated with this color palette
are identical in appearance for Old and New Fashion.
Color indices 160, 163, 184, 187, 196, 199, 204, 205, 207, 217, 219, 220, 221,
223, 226 and 228 are available
Only colors 160 through 231 can be used. This is the only way to ensure that
images look the same on HMI Embedded and HMI Advanced.
Activating a color table from PaintShopPro
File → Open → ...\*.bmp
Colors → Open picture palette → ...\*.PAL
Apply palette with Color Indices "Open"
System colors
One of 10 colors can be selected for one screen form element (text, input field,
screen form background, etc.). In SW 6.4 and higher, the system colors have been
expanded - and there is a difference between the old and new designs (refer to
e.g. the header color in the table below). In order to achieve a demarcation
between unique and design-dependent colors, it has been defined that the unique
colors are found between 0 and 128. The design-dependent colors that have been
newly introduced as part of this expansion, are defined from index 128. This
means, that also when the unique colors are expanded (up to 128), it is prevented
that both color types are mixed.
$AC_FCTUL[x] x = polynomial no. Upper limit value after polynomial for synchro. action
Name Index Description
$AC_FIFOx[y] x = FIFONo (1-10) FIFO variables for synchronous actions
y = ParameterNo
$AC_MARKER[x] x = MarkerNo Marker var, counter for motion-synchronous actions
$AC_MEA Probe has responded
$AC_OVR Path override for synchronous actions
$AC_PARAM[x] x = ParameterNo Dyn. parameter for motion synchronization
$AC_PATHN Normalized path parameter
$AC_PLTBB Path travel from block beg. in basic coordin. system
$AC_PLTEB Path travel from block end in basic coordin. system
$AC_PRESET[x] x = Axis PRESET value
$AC_PROG Program status
$AC_RETPOINT[x] x = Axis Return position on contour for repositioning
$AC_SDIR[x] x = SpindleNo Rotat. status
$AC_SMODE[x] x = SpindleNo Spindle mode
$AC_STAT Channel status
$AC_TIME Time from the start of the block in seconds
(including the times for the internally generated
intermediate blocks)
$AC_TIMES Time from the start of the block in seconds (without
the times for the internally generated intermediate
blocks)
$AC_TIMEC Time from the start of the block in interpolation clock
cycles (including clock cycles for the internally
generated intermediate blocks)
$AC_TIMESC Time from the start of the block in interpolation clock
cycles (without the clock cycles for internally
generated intermediate blocks)
$AC_TIMER[x] x = TimerNo Timer location in seconds
$AC_VACTB Interpolation feedrate, setpoint
$AC_VACTW Path velocity in workpiece coordinate system
$AC_VC Add. path feed override for synchronous actions
$AN_AXCTAS[n] Actual axis container address (rotary position)
$AN_AXCTSWA CTn = axis container Axis container rotation active
[CTn] no.
$AN_ESR_TRIGGER ESR start signal
$AN_MARKER[x] x = MarkerNo Marker variable for motion synchronous actions
$MC_DISPLAY_AXIS Bits 16-31 Machine axis identifier
$MC_DISPLAY_AXIS Bits 0-15 Identifier for geometry/auxiliary axis
$MC_MM_NUM_ Number of base frames in channel
BASE_FRAMES
$MN_EXTERN_ CNC system language
LANGUAGE and
$MN_EXTERN_CNC_
SYSTEM
$MN_MAX_CUTTING Maximum value D number
_EDGE_NO
$MN_MAX_CUTTING Max. number of edges per tool
_EDGE_PER_TOOL
$MN_MAX_ Max. number of total offsets per tool
SUMCORR_PERCUT
TING_EDGE
PI_SERVICE(service, n parameter)
where:
Service Identifier of PI service
n parameter List of PI service parameters. The
parameters are separated by a comma.
Table 8-3
Service Explanation
Parameters
Example
Service Explanation
Parameters
Example
_N_CRCEDN Create tool edge by specifying the cutting edge number. If the T number of
an existing tool is entered in parameter "T Number" of this service, then a
tool edge for the existing tool is created (in this case, the parameter "D
number", i.e. the number of the edge to be created, has a value range of 1-
9). If a positive T number is specified as a parameter and the tool for the T
number entered does not exist, then the PI service is aborted.
If a value of 0 is entered as the T number (model of absolute D numbers),
then the D number values can range from 1 - 31999. The new cutting edge
is set up with the specified D number.
If the specified cutting edge already exists, then the PI service is aborted in
both cases.
Par1 T number
Par2 D number
T number == 0 ==> 1–31999
T number > 0 ==> 1–9
A tool edge with number 3 is created for the tool with number 17 in the
current TO area.
PI_SERVICE("_N_CRCEDN“,17,3)
_N_CREACE Create a new tool edge for a specified tool. The next-higher available D
number is automatically set up. The following blocks in the active file system
are affected by this PI service:
Tool offsets TO: The relevant tool edge (with ZERO content) is set up
Monitoring data TS: (If available) the relevant tool edge (with ZERO content)
is set up
User edge data TUE: (if available) the respective tool edge is created (with
content ZERO)
(NCK software versions < 10.x)
Par1 Tool number 1 to 31999
After the tool with number 55 has been set up in T area 1, a further 2 edges
are created for it. The tool therefore now possesses a total of 3 edges.
PI_SERVICE("_N_CREATO“,55)
PI_SERVICE("_N_CREACE“,55)
PI_SERVICE("_N_CREACE“,55)
Service Explanation
Parameters
Example
_N_CREATO Create a tool with a specific T number. The following blocks in the active file
system are affected by this PI service:
Tool directory TV: The tool is entered as an existing tool
Tool offsets TO: The first tool edge D1 (with ZERO content) is set up
User edge data TUE: (If available) the first tool edge D1 (with ZERO
content) is set up
User tool data TU: (If available) an empty data block is made available for
the tool
Par1 Tool number 1 to 31999
After the tool with number 55 has been set up in T area 1, a further 2 edges
are created for it. The tool therefore now possesses a total of 3 edges.
PI_SERVICE("_N_CREATO“,55)
PI_SERVICE("_N_CREACE“,55)
PI_SERVICE("_N_CREACE“,55)
_N_DELECE Delete a tool edge. If the T number of an existing tool is entered in
parameter "T Number" of this PI service, then the tool edge for the relevant
tool is deleted (in this case, the parameter "D number, i.e. the number of
edge to be deleted, has a value range of 1-9). If a positive T number is
specified as a parameter and the tool for the T number entered does not
exist, then the PI service is aborted.
If a value of 0 is entered as the T number (model of absolute D numbers),
then the D number values can range from 1-31999.
If the specified cutting edge does not exist, then the PI service is aborted in
both cases.
Par1 T number of the tool for which the associated tool cutting edge is to
be deleted.
A setting of 0 indicates that there is no reference to a specific tool (absolute
D number).
Par2 Cutting edge number of tool cutting edge that should be deleted.
Value range:
T number == 0 ==> 1–31999
T number > 0 ==> 1–9
The tool edge with number 3 for the tool with number 17 in the current TO
area is deleted.
PI_SERVICE("_N_DELECE“,17,3)
Service Explanation
Parameters
Example
_N_DELETO Deletes the tool with all tool edges in all data blocks in which it is stored. The
tool is also deleted in the following blocks (if available): TO, TU, TUE, TV,
TG (type 400), TD, TS.
Par1 Tool number 1 to 31999
Deletion of tool with T number 21 in the current T area.
PI_SERVICE("_N_DELETO“,21)
Par1 ID for the search mode
1: Search without calculation
2: Search with calculation
3: Search including the main block analysis
Start search with calculation in current channel.
To start the PI service in a meaningful manner, the data structure for the
block search (block SPRAF ; addressing on MMC102 with variable services
via /Channel/Search/..) must be filled in beforehand.
PI_SERVICE("_N_FINDBL“,2)
_N_LOGIN_ A password which sets the current access level is sent to the NCK.
Par1 Password (precisely 8 characters, for less than 8 characters, blanks
must be added)
Transfers a password to the NCK, thus setting another access level.
PI_SERVICE("_N_LOGIN_“,"TESTWORD“)
_N_LOGOUT The current access level is reset.
---
The current access level is reset.
PI_SERVICE("_N_LOGOUT“)
_N_SETUFR The SYSTEM OR USER variables 'linShift', 'mirrorImgActive', 'rotation' and
'scaleFact' in channel-specific data block FU can be used to define up to 8
zero offsets per channel. PI service _N_SETUFR must be called in order to
activate these user-defined zero offsets.
---
Activation of a user frame.
PI_SERVICE("_N_SETUFR“)
8.5 Examples
//S(Start)
HS7=("Example", se1, ac7)
PRESS(HS7)
LM("Form4")
END_PRESS
//END
LOAD
By1=1
By2=2
By3=3
By6=6
By7=7
END_LOAD
PRESS(HS1)
Byte.wr=2
END_PRESS
CHANGE(Byte)
By1=byte+1
By2=byte+2
By3=byte+3
By6=byte+6
By7=byte+7
Feed.VAR="EB"<<By3
Spin.VAR="EB"<<Byte
Custom1.VAR="EB"<<By6
Custom2.VAR="EB"<<By7
Axistop.VAR="E"<<By2<<".2"
Spinstop.VAR="E"<<By2<<".4"
Byte.wr=1
END_CHANGE
CHANGE(Axistop)
IF Axistop==0
Axistop.BC=9
ELSE
Axistop.BC=11
ENDIF
END_CHANGE
CHANGE(Spinstop)
IF Spinstop==0
Spinstop.BC=9
ELSE
Spinstop.BC=11
ENDIF
END_CHANGE
PRESS(VS8)
EXIT
END_PRESS
Figure 8-1
Note
You will find further examples in the supplied tool box.
I Index
/ C
NC code S
Generating .................................BE1/3-88
NC functions .................................BE1/3-92 SB ............................................... BE1/4-112
NC variable Scope of supply
Read...........................................BE1/3-80 Expanding the operator
Write ...........................................BE1/3-80 interface................................ BE1/7-156
NC variable....................................BE1/3-80 Scope.............................................. BE1/1-7
Screen form .................................. BE1/2-21
Screen form
O Multi-column .............................. BE1/3-54
Screen form change mode ........... BE1/3-76
Operating area Screen form definition block ......... BE1/2-21
Custom .....................................BE1/6-150 Screen form elements................... BE1/3-41
Operating area change................BE1/6-154 Screen form properties ................. BE1/2-24
Operating areas...........................BE1/5-134 Screen form tree ........................... BE1/2-17
Operator interface .........................BE1/2-21 se .................................................. BE1/2-31
OUTPUT........................................BE1/3-39 SF................................................ BE1/4-112
Short text
P As image.................................... BE1/3-49
Short text....................................... BE1/3-43
Parameter........................................BE1/1-9 SINUCOPY_FFS ........................ BE1/7-171
PCMCIA card image....................BE1/7-171 Size
PI services ....................................BE1/3-92 Configuration file...................... BE1/7-159
Picture file ................................ BE1/7-159
SINUMERIK 840D/840Di/810D
1 Programming Help
1
1.1 Overview of Programming Help................................................. HE1/1-4
Hardware
The pdf Help is available for PCU 50/PCU 70 with the HMI Advanced or HMI
Embedded Win 32 software.
Software
• HMI Advanced or HMI Embedded Win 32, SW 6.1 or higher
• Adobe Acrobat Reader 4.x (obtainable free in the Internet/in bookshops)
The Adobe Acrobat Reader 4.x software is installed in the SINUMERIK 840D
control from SW 5.x as standard.
• Adobe Acrobat 4.x
You will require Adobe Acrobat Distiller 4.x software for converting documents to
pdf and editing the pdf documents.
Note
• Adobe Acrobat 4 is available from your local software dealer
• Cost: around DM 600, with discounts for bulk quantities
• Adobe Reader 4 is free.
Alarm/MD Help F:\ MMC2\HLP (contains any hlp, pdf and txt files)
OPI Help F:\ HMI_ADV\HLP (contains any hlp, pdf and txt files)
Procedure:
1. Define and generate the jumps in the Help document (e.g. using the standard
index function of DTP systems)
2. Save the jump file as a text file
3. For Programming Help only: Assign ID numbers to the programming
commands
4. Generate the pdf file
Result:
• A call file (text file) with the parameters
<pdf file name> <ID> <search string> for each call
• One or more associated pdf file(s)
Note
For multiple jumps to a topic, each page reference must be written
on a new line.
Example: 840d_pg_gr.pdf 44 155
840d_pg_gr.pdf 45 180
840d_pg_gr.pdf 46 199
Tip:
In cases where the index is large, the call file can be generated automatically using
Microsoft Excel:
• Insert "index file" (*.txt) in Excel
• Insert a column
• Enter the name of the PDF file in the first line.
• Execute "Edit - Fill".
• Copy data and
• Save the file as "txt".
The following syntax should remain:
<pdf file name> <ID> <search string>
840d_pg_gr.pdf 44 155
Note
If the search terms were not found, it can be due to the following:
• Error during input
• The texts were incorrectly converted at PDF generation, therefore they could
not be found by the search function.
Analysis: Highlight a search term in the Adobe Acrobat, copy it and insert it
into a Word document.
Remedy:
• Generate pdf again.
Search order
The search order for the Help function is as follows:
1. F:\ USER\HLP
2. F:\ OEM\HLP
3. F:\ ADD_ON\HLP
4. F:\ MMC2\HLP
5. F:\ HMI_ADV\HLP
6. F:\ DH\CUS.DIR\HLP.DIR (User directory)
7. F:\ DH\CMA.DIR\HLP.DIR (Manufacturer directory)
8. F:\ DH\CST.DIR\HLP.DIR (Siemens directory)
9. F:\ DH\COM.DIR\HLP.DIR
Certain text files to which the help function accesses can be expanded (see
Section 1.4 "Expanding the Text Files").
The paths of the generated ASCII text files must be entered in the "IF.INI"
initialization file or configured under "Settings" (user file name).
TECHNOLOGY section
The relevant technology category of the connected machine can be entered in the
[TECHNOLOGY] section so as to limit the display of instruction texts to relevant
technology entries, i.e. only entries pertinent to the relevant technology are
displayed.
"m" = milling
"t" = turning
"g" = grinding
"s" = nibbling
"p" = punching
"a" = display all technologies
TEXTFILES section
The paths (path\name) used for the Short Help text files on which the help function
is based are parameterized in the section [TEXTFILES].
The help function accesses the following text files:
• Siemens "DH\CST.DIR\IFS_GR.COM"
• Machine manufacturer "DH\CMA.DIR\IFM_GR.COM" (any file name)
• End user "DH\CUS.DIR\USER_GR.COM" (any file name)
(is also entered via "Settings")
! Important
The path for the Siemens text file "DH\CST.DIR\LFS_GR.COM" must exist
otherwise an error message is output.
There are different parameterization options for the names of the text files when
assigning the text path.
The following table lists the parameterization options and their interpretation by the
Help function.
Table 1-1
Example: ENDUSER=CUS.DIR\IFM_.COM
First of all, the language-independent text file "IFM.COM" is opened in the path
"C:\DH\CUS.DIR\" by default or, if the language-independent text file does not
exist, the relevant language-dependent text file (e.g. "IFM.COM") is opened.
CONTEXT section
An increased context sensitivity of the Help function can be selected in the
[CONTEXT] section. This setting is activated with "1" and deactivated with "0".
If the increased context sensitivity is activated and the cursor is positioned to the
left of or on an instruction text, then all instructions with the same initial letters are
displayed when Help is called.
For example, if the programmer has selected instruction "G1", then all instructions
beginning with "G1" (e.g. "G1", "G17", "G18", "G19") are displayed.
If increased context sensitivity has been deactivated with "0", then only the
instruction actually selected (if available) is displayed.
TEXTSEARCH section
The text search type can be specified in the [TEXTSEARCH] section. The following
search methods can be parameterized:
File IF.INI
[TECHNOLOGY]
"m" = milling
"t" = turning
"g" = grinding
"s" = nibbling
"p" = punching
"a" = display all technologies
[TEXTFILES]
Siemens = DH\CST.DIR\IFS_GR.COM
Machine manufacturer = DH\CMA.DIR\IFM_GR.COM
Machine manufacturer = DH\CMA.DIR\IFI_GR.COM
End user = DH\CUS.DIR\USER_GR.COM
[CONTEXT]
=0 Context sensitivity not active
=1 Context sensitivity active
[TEXTSEARCH]
=1 Text search only according in instruction texts
=2 Text search only according in description texts
=3 Text search in instruction and description texts
The following functions can be added to the text files (*.com) of the Help according
to the following pattern:
• General categories, i.e. "groups" of instructions
• Instructions with descriptive texts
• Instructions with Extended Help call
• Editor Help "pdf" or
• Cycle Help for input fields in the cycle screens in which the instruction
parameters are entered
• Instructions with alarm text variables as descriptive texts.
Instruction definition
Technology/Category ID/Extended Help
/Instruction text/Descriptive text
Note
1. With reference to the individual text files, first the Siemens and then the
machine manufacturer and last the final user general category are displayed.
2. The order specified above appears only if the categories are defined first,
followed by the instruction declarations in the text file.
3. To provide correct sorting of the standard, machine manufacturer and final
user instructions, the instructions in the text files must be stored in the
alphabetical order.
Category definition
Technology code "r"/Category ID/Category name
In this case, the text file could contain the following line:
r/2/Travel commands
r is a predefined setting for category declarations.
2 is the category ID used to assign instructions to the
category.
Travel commands category name.
The "/" character separates the parameters and may only be used as a text
character in the last parameter.
The length of the category name is limited by the display and may not, for example,
exceed 40 characters with a standard type size of 8pt.
The following category IDs are reserved:
Category ID User
0...49 Siemens
50...99 Machine manufacturer
100 and over End user
The following category IDs are provided in the Siemens text file as standard:
Categ. Categ.
Expanding an instruction
An instruction contains description texts, e.g. "G0/linear interpolation with rapid
traverse". The category ID is used to assign instructions to the category.
After the above line has been entered in one of the user text files, the user cycle
"CYCLExx" is supported within the Help system. It is displayed if either of the
following are entered in the "If.ini" initialization file:
• The technology-independent identifier "a"
• The specific milling machine identifier "m"
The cycle is assigned to "Standard cycles" via category ID "14", i.e. it can also be
found by making the appropriate entry in the category search.
The last parameter of the definition contains the descriptive text that is displayed in
the corresponding column of the Help system to provide the user with basic
information about the function of the cycle.
The "/" character separates the parameters and may only be used as a text
character in the last parameter.
Technology
The following characters are used to assign the instruction to a technology type:
"m" = milling
"t" = turning
"g" = grinding
"s" = nibbling
"p" = punching
"a" = display for all technologies
Note
If you wish to assign instructions to several technologies and different categories,
the relevant ID codes must be separated by a "comma".
Category ID
The category ID is programmed to assign instructions to a particular category of
the category definition and display them under the relevant category heading.
Extended Help
The following entries are possible in the "Extended Help" parameter:
• Editor Help
/"Pdf file name", Help ID, "search string"/
• Cycle Help
/"Pdf file name", Help ID, "search string" (file name,
Help display)/
Two commas must be placed in the "Extended Help" parameter, even if no entry is
made.
Example:
The declaration line requires, e.g. the following parameters:
m,t/14/"Pdf file name", Help ID, "search string" (file name,
Help display)/CYCLE82/drilling cycle, drilling, counterboring
The entries for the "Extended Help" parameter have the following meaning:
Pdf file name
= file from which the descriptive text is to be displayed
Help ID
= unique assignment to term for which Help is to be displayed
search string
= search string in the pdf file to be displayed in the Help text.
CYCLE82
= instruction text
Drilling cycle, boring, counterbore
= description text
Sample call:
m,t/14/"PGZ.pdf",1,"RTP"(drilling,CYC82)/CYCLE82/drilling
cycle, drilling, counterboring
Note
If you wish to access only the Pdf file, only these parameters are permissible in
the "Extended Help" section.
If you wish to display only the Help display, only these parameters are
permissible in the "Extended Help" section.
Instruction text
"G17" is one example of an instruction text. This text is transferred to the part
program that you are editing when you select "Transfer to the Editor".
Instruction texts can be about 12 characters in length.
Descriptive text
The descriptive text is the Help text that describes the instruction more in detail.
The length of the descriptive text is limited by the display and must not, for
example, exceed 40 characters with a standard type size of 8pt.
Multiple jumps
Multiple Help references can be stored per Help text as a ring (i.e. after the last
Help reference, the first Help reference is displayed again).
E.g.: m,t/14/"Hlp.pdf",1,"Hilfe1",,2,"Hilfe2","Help3.pdf",3,,/
CYCLE82/drilling cycle, drilling, counterboring
I.e.:
1. Entry in the Help text ring
File: HLP.PDF
Index: 1
Text: Help1
2. Entry in the Help text ring
File: HLP.PDF
Index: 2
Text: Help2
3. Entry in the Help text ring
File: HELP3.PDF
Index: 3
Text: Help2
To avoid repetitions, the components of the previous block are stored, as shown in
the example. Only whole blocks are transferred.
Note
• How the pdf files and Help files are embedded in the system is described in
Section 2.2 "Embedding PDF files in the Help system".
• Two commas must be placed in the "Extended Help" parameter, even if no
entry is made.
E.g. m/14//CYCLExx/$888888
Instead of entering the descriptive text directly into the Help text file, it is stored
directly, e.g. under the alarm text variable "$888888".
The declaration of the descriptive text is thus relocated to a user-specific alarm text
file.
"Extended Help":
The following entries are possible in the "Extended Help" parameter:
• Editor Help
/"Pdf file name", Help ID, "search string"/
Example: a/20/"PGA.PDF",2,"="/=/Assignment operator
• Cycle Help
/"Pdf file name", Help ID, "search string" (file name,
help display)/
Example: a/3/"PG.PDF",17,"ANG"/ANG/Contour angle (s)
Configuring the Long Help pdf: see Subsection 1.4.3 "Expanding the Long Help
"pdf""
Required files
• IFM_GR.COM text file with program commands and brief description
• *.pdf Help file e.g. 840d_pg_gr.pdf
• *.txt Jump file e.g. 840d_pg_gr.txt
1
Define jump labels in the document
The jumps must be marked with index entry in the document (e.g. WinWord) of
which excerpts are to be displayed on the control as pdf.
and a single-column index list (page numbers right-justified) produced.
If multiple jumps are required for command, assign the appropriate number of
index markers first.
2
Create text file
Copy the single-column index created above (page number right-justified) and save
it as a txt file (*.txt).
The text file for the pdf call has the following syntax:
<pdf file name> <ID> <page>
Add the name of the pdf file for each line (without language code).
3
Define ID numbers
Define unambiguous ID numbers (e.g. 1...n) for the search terms in each
document: The ID numbers correspond to the list of instructions of the Short Help
"ASCII", since the detailed description is to be displayed for the brief descriptions.
Now delete the column "search terms", so that the following syntax remains:
Result: <pdf file name> <ID> <page>
840d_pg_gr.pdf 44 155
4
Generate a pdf file
Print your document as a postscript file and convert it to "pdf" using the Adobe
Acrobat Distiller.
5
Reading files to the control
The generated files (*.pdf and *.txt) must be copied onto the control, e.g. to
directory F:\DH\CUS.DIR\HLP.
Note
In cases where the index is large, the call file can be generated automatically
using Microsoft Excel:
• Insert text file (*.txt) in Excel
• Insert a column
• Enter the name of the PDF file in the first line.
• Execute "Edit - Fill".
• Now delete the column "search terms", so that the following syntax remains:
<pdf file name> <ID> <page>
840d_pg_gr.pdf 44 155
• Copy data and
• save the file as "txt".
If "ISO dialect 0" Help functions are to be displayed, the data to be displayed must
be distinguished, since the same commands can have different meanings, for
example.
To do this, the "IF.INI" file has been expanded in the [TEXTFILES] section to
include the entry SiemensI=Cst.dir\ifit_.com (turning technology) or
SiemensI=Cst.dir\ifim_.com (milling technology), under which the path (Cst.dir)
and name (ifit_.com or ifim_.com) are specified for the ISO Mode Short Help
"ASCII".
The relevant Long Help "pdf" can then be called from the Short Help "ASCII".
IF.INI[TEXTFILES]
[TEXTFILES]
;text files containing the information shown in the Help
system
Siemens=Cst.dir\Ifs_.com
SiemensI=Cst.dir\ifit_.com or ifim_.com
Manufacturer=
Enduser=
Required files
• List of "ISO-dialect 0" commands with associated brief description (see
Chapter 1)
• TXT file for jump to PDF file
• PDF file to be displayed in the Help
Program sequence
The Help function checks the following machine data during start-up:
• MD 18800 MM_EXTERN_LANGUAGE
If this MD is activated, the control switches to ISO Dialect 0 mode.
If MD 18800 = 1, MD 20150 is evaluated.
• MD 10880 MM_EXTERN_CNC_LANGUAGE
MD 10880 specifies whether the control must be set for turning or milling in ISO
mode.
If additional descriptions are to be displayed in the ISO mode Help function, they
must be added in the form of
• a list of ISO-mode commands with brief description in the file ifit_.com or
ifim_.com file in the SiemensI=Cst.dir\ directory (see Section 1.4 "Expanding the
text files"),
• a Help description (pdf file) and a text file with the same name in the directory
F:\USER\HLP.
"Extended Help":
The following entries are possible in the "Extended Help" parameter:
• Editor Help
/"Pdf file name", Help ID, "page number"/
• Cycle Help
/"Pdf file name", Help ID, "page number" (file name, Help
display)/
Configuring the Long Help pdf: see Subsection 1.4.3 "Expanding the Long Help
"pdf""
Required files
• Ifit_.com or Ifim_.com text file with ISO-mode commands and brief
description
• *.pdf e.g. 840d_pgit_gr.pdf
• *.txt e.g. 840d_pgit_gr.txt
1
Define jump labels in the document
The jump labels must be marked with an index entry in the document (e.g.
WinWord) to be displayed at the control as pdf
and a single-column index list (page numbers right-justified) produced.
2
Generate a text file
Copy the single-column index created above (page number right-justified) and save
it as a txt file.
Example: G65 155
<search term> <page>
The text file requires the following syntax to call the pdf file:
<pdf file name> <search term> <page>
Add the name of the pdf file for each line (without language code).
3
Define ID numbers
Define unambiguous ID numbers (e.g. 1...n) for the search terms in each
document: The ID numbers correspond to the list of instructions of the Short Help
"ASCII", since the detailed description is to be displayed for the brief descriptions.
Now delete the column "search terms", so that the following syntax remains:
Result: <pdf file name> <ID> <page>
840d_pgit.pdf 44 155
4
Generate a pdf file
Print your document as a postscript file and convert it to "pdf" using the Adobe
Acrobat Distiller.
5
Reading files to the control
The files created (*.pdf and *.txt) must be read to the control from the
F:\USER\HLP directory.
Note
In cases where the index is large, the call file can be generated automatically
using Microsoft Excel:
• Insert text file (*.txt) in Excel
• Insert a column
• Enter the name of the PDF file in the first line.
• Execute "Edit - Fill".
• Now delete the column "search terms", so that the following syntax remains:
<pdf file name> <ID> <page>
840d_pg.pdf 44 155
• Copy data and
• save the file as "txt".
2.1 Overview
The following expandable Help systems are available on the control:
1. Programming Help
• Short Help "ASCII"
• Long Help "pdf"
• Additional Help (PDF file) from Short Help "ASCII".
• Additional Help for input fields of cycle parameterization screens
• ISO Mode Help
2. Alarm Help
3. Machine Data Help
Hardware
The pdf Help is available for PCU 50/PCU 70 with the HMI Advanced or HMI
Embedded Win 32 software.
Software
• HMI Advanced or HMI Embedded Win 32, SW 6.1 or higher
• Adobe Acrobat Reader 4.x (obtainable free in the Internet/in bookshops)
The Adobe Acrobat Reader 4.x software is installed in the SINUMERIK 840D
control from SW 5.x as standard.
• Adobe Acrobat 4.x
You will require Adobe Acrobat Distiller 4.x software for converting documents
to pdf and editing the pdf documents.
Note
• Adobe Acrobat 4 is available from your local software dealer
• Cost: around DM 600, with discounts for bulk quantities
• Adobe Reader 4 is free.
Alarm/MD Help F:\ MMC2\HLP (contains any hlp, pdf and txt files)
OPI Help F:\ HMI_ADV\HLP (contains any hlp, pdf and txt files)
Procedure:
1. Define and generate the jumps in the Help document (e.g. using the standard
index function of DTP systems)
2. Save the jump file as a text file
3. For Programming Help only: Assign ID numbers to the programming
commands
4. Generate the pdf file
Result:
• A call file (text file) with the parameters
<pdf file name> <ID> <search string> for each call
• One or more associated pdf file(s)
Note
For multiple jumps to one topic, each page reference must be
written on a new line.
Example: 840d_pg_gr.pdf 44 155
840d_pg_gr.pdf 45 180
840d_pg_gr.pdf 46 199
Tip:
In cases where the index is large, the call file can be generated automatically
using Microsoft Excel:
• Insert "index file" (*.txt) in Excel
• Insert a column
• Enter the name of the PDF file in the first line.
• Execute "Edit - Fill".
• Copy data and
• save the file as "txt".
The following syntax should remain:
<pdf file name> <ID> <search string>
840d_pg_gr.pdf 44 155
Note
If the search terms were not found, it can be due to the following:
• Error during input
• The texts were incorrectly converted at PDF generation, therefore they could
not be found by the search function.
Analysis: Highlight a search term in the Adobe Acrobat, copy it and insert it
into a Word document.
Remedy:
• Generate pdf again.
Search order
The files containing the alarms data are stored in the following directories:
• Siemens alarms F:\HMI_ADV\HLP,
• Manufacturer alarms F:\DH\CMA.DIR\HLP
• User alarms F:\DH\USER\HLP
File names
The following file names must be used, also for additional user alarms (i.e. must
not be changed):
• ALARM_GR.PDF [German alarms]
• ALARM_UK.PDF [English alarms]
• ALARM_FR.PDF [French alarms]
• ALARM_IT.PDF [Italian alarms]
• ALARM_SP.PDF [Spanish alarms]
The names of the associated txt files (containing the jump list) must correspond as
follows:
• ALARM_GR.TXT [German txt file]
• ALARM_UK.TXT [English txt file]
• ALARM_FR.TXT [French txt file]
• ALARM_IT.TXT [Italian txt file]
• ALARM_SP.TXT [Spanish txt file]
Further languages
The alarm texts are available in the following languages:
CH: Simplified Chinese
TW: Standard Chinese
KO: Korean
JA: Japanese
SW: Swedish
HU: Hungarian
PO: Portuguese
CZ: Czech
TR: Turkish
RU: Russian
PL: Polish
NL: Dutch
The language codes for the file names of the user alarms must be used in
accordance with the naming conventions specified above (must not be changed).
Required files
• *.pdf e.g. alarm_gr.pdf
• *.txt e.g. alarm_gr.txt
1
Define jump labels in the document
The jump labels must be marked with an index entry in the document (e.g.
WinWord) to be displayed at the control as pdf single-colum index list (page
numbers right-justified) produced.
2
Create text file
Copy the single-column index created above (page number right-justified) and save
it as a txt file.
Example: 10702 90
<ID> <page>
The search word (alarm number) is the same as the ID No. in this case.
The text file requires the following syntax to call the pdf file:
<pdf file name> <ID> <page>
3
Generate pdf file
Print your document as a postscript file and convert it to "pdf" using the Adobe
Acrobat Distiller.
4
Incorporate the files to the control
The generated files (*.pdf and *.txt) must be copied onto the control, e.g. to
directory F:\DH\USER\HLP.
F:\USER\RH
Note
Alarm-specific texts can be stored by pressing the key [i] if the MMC Help
function was invoked from the alarm overview or alarm log for the respective
alarm. It does not work if you select the alarm from the directory.
2. Create text file: Copy the single-colum index created above (page numbers
right justified) and save it in a "txt" file.
The text file for the pdf call has the following syntax:
<pdf file name> <ID> <page>
The search word (alarm number) is the same as the ID No. in this case.
Add the name of the pdf file before each line.
Example: ALARM_GR.PDF 10702 90
ALARM_GR.PDF 10703 90
ALARM_GR.PDF 10704 91
<pdf name> <ID> <page>
3. Print out the file containing the alarm texts as a Postscript file (this works on
all common platforms). For example, the file extensions are ".prn" for WinWord
and ".ps" for Interleaf.
4. Convert the Postscript file to pdf with adobe Acrobat 4 using the Distiller.
5. Copy the files (*.pdf and *.txt) onto the control to directory
F:\DH\USER\HLP.DIR.
Note
• If additional user alarms are to be displayed in the Alarm Help, these must be
added in the form of a pdf file and in a txt file of the same name in the
F:\USER\HLP directory.
• Please observe the naming conventions stated in Section 4.1.
File names
The following file names must be used, also for additional user MDs (i.e. must not
be changed):
The names of the associated txt files (containing the jump list) must correspond as
follows:
Explanation of names
Name Significance
N_NCK_GR.PDF General MDs
C_NCK_GR.PDF Channel-specific MDs
A_NCK_GR.PDF Axis-specific MDs
S_NCK_GR.PDF Setting Data
DISPL_GR.PDF Display MDs
DROT_GR.PDF Drive MDs, rotary
DLIN_GR.PDF Drive MDs, linear
HYDRM_GR.PDF Drive MDs, hydraulics module
Required files
• *.pdf e.g. n_nck_gr.pdf
• *.txt e.g. n_nck_gr.txt
1
Define jump labels in the document
The jump labels must be marked with an index entry in the document (e.g.
WinWord) to be displayed at the control as pdf and a single-column index list (page
numbers right-justified) produced.
2
Create text file
Copy the single-column index created above (page number right-justified) and save
it as a txt file.
Example: 10000 170
<ID> <page>
3
Generate pdf file
Print your document as a postscript file and convert it to "pdf" using the Adobe
Acrobat Distiller.
4
Incorporate the files to the control
The files created (*.pdf and *.txt) must be read to the control from the
F:\USER\HLP directory.
I Index
I
I.1 Subject index
Help references
Multiple ........................................HE/1-16
A
Search order
D Help .............................................HE/2-28
Descriptive text ............................... HE/1-16
T
H Technology .....................................HE/1-14
Help function...................HE/1-7, 1-17, 2-26
SINUMERIK 840D/840Di/810D
3.4 Network operation with HMI Embedded (SW 6.2 and higher).............................................. IM2/3-31
3.4.1 Network configuration data ........................................................................................... IM2/3-32
3.4.2 HMI system settings...................................................................................................... IM2/3-32
3.4.3 Examples: Network configuration ................................................................................. IM2/3-33
5.11 Define machine position and rotary axis position ............................................................... IM2/5-72
5.17 Remote diagnostics "RCS Host PCU 20 / RCS Viewer PCU 20"....................................... IM2/5-78
5.17.1 Configure "RCS Host PCU 20" ..................................................................................... IM2/5-81
5.17.2 Installing and configuring "RCS Viewer PCU 20".......................................................... IM2/5-83
5.17.3 Start "RCS Host PCU 20" ............................................................................................. IM2/5-86
8.5 Data backup for HMI Embedded WIN32 with PCU 50/70 .................................................. IM2/8-160
9 Diagnostics........................................................................................................................... IM2/9-161
10.4 Sample program 2: Hold time and optional text variables .............................................. IM2/10-172
10.5 Sample program 3: MMC command with synchronous acknowledgment mode ............ IM2/10-173
10.6 Sample program 4: Positioning the input and output field .............................................. IM2/10-174
10.9 List of files for the dialog screen files ............................................................................. IM2/10-179
11.6 Loading the image from the PC card to the HT 6........................................................... IM2/11-202
1 General Preparations
1
1.1 Hardware/software requirements................................................ IM2/1-8
Introduction
This Installation and Start-Up Guide describes the procedures for installing the
PCU 20 with the software HMI Embedded.
For further reading on special NCK, MMC, PLC, or drive functions, please consult
the Descriptions of Functions/Manuals (see Section: Documentation).
Names of HMI/MMC:
Up to SW 5: HW and SW: MMC100.2
Hardware
The hardware base for the HMI software (Human Machine Interface) is
• a PCU computer unit together with an
• OP display unit (operator panel)
Software
As standard, the HMI Embedded software is installed on the supplied PCU 20 and
contains all files required for the operation of the PCU.
If you want to change the configuration of the installed software or install a new
software version, then you must replace the software.
In this case, you can choose whether the replacement software has the standard
configuration or a modified configuration.
1.2 Documentation
You require the following documentation for the installation and start-up of
SINUMERIK 840D:
3. Lists /LIS/
Exception:
If non-Siemens devices are connected (printers, programming devices, etc.), you
can also use standard shielding cables which are connected at one end.
These external devices may not be connected to the control during normal
operation. However, if the system cannot be operated without them, then the cable
shields must be connected at both ends. Furthermore, the external device must be
connected to the control via an equipotential bonding cable.
Pulse-carrying HC/HV cables must always be laid completely separately from all
other cables.
The distance (interference injection area) between the following cables must be as
close as possible:
Signal line and signal line
Signal line and associated equipotential bonding conductor
Equipotential bonding conductor and PE conductor (routed together)
! Important
For further information about suppression measures and the connection of
shielded cables see
References: /EMC/, EMC Directive
! Important
Handling of modules containing devices sensitive to electrostatic discharge:
• When handling electrostatically sensitive devices, make sure that operator,
workplace and packing material are properly grounded.
• Modules must never be brought into contact with statically chargeable and
highly insulating materials, such as plastic sheeting, insulating table tops,
clothing made of synthetic fibers.
You can find a detailed description of the PCU as well as the current descriptions
of the other components in:
References: /BH/Operator Components, Manual
The PCU 20/50/70 computer unit can be used together with the following operator
panel fronts.
OP, operator panel: OP 010, OP 010C, OP 010S,
OP 012, OP 015, OP 015A
TP, touch panel: TP 012, TP015A: Can only be used with customized
HMI software.
2.1.2 Accessories
Depth = 56
53
PS/2 keyboard COM1/RS-232 COM2/RS-232 USB Ethernet MPI/L2-DP Memory card slot
Reset
24 V power connection
Note
You will notice that the electromagnetic compatibility of commercially available
peripheral devices is usually rated for office use only.
For industrial use, components with a higher degree of certificate are
recommended.
Memory cards
The following memory cards can be used for operation on the operator
components:
Compact Flash card 32 MB Order no.: 6FC5313-1AG00-0AA0
Compact Flash card 64 MB Order no.: 6FC5313-2AG00-0AA0
Card reader
You require a commercially available card reader for the above memory cards, a
USB card reader which supports the CF cards.
You can find information on how to adapt and set your interface and which
connection cable you require in the description of the corresponding device.
3 Communication/Initial Requirements
3
3.1 Communication within the system ............................................ IM2/3-18
! Important
Only two terminations are permitted.
Bus terminating resistors are integral components of HHU and HPU units.
! Important
The NC control must be located at the end of the connection*).
3. Drop cables (feeder cable from bus segment to node) should be as short as
possible.
! Important
Any unassigned spur lines should be removed if possible.
5. Either one HHU and one HPU, or two HHUs or two HPUs can be connected to
each bus segment. No bus terminators must be inserted in the distributor boxes
of an HHU or an HPU.
If more than one HHU/HPU are connected to a bus segment, this can be done
with an intermediate repeater.
6. The following cables lengths for MPI or OPI for standard use without repeater
may not be exceeded:
MPI (187.5 kbaud): Max. cable length 1000 m in total
OPI (1.5 Mbaud): Max. cable length 200 m in total
Example A
on
HHU
Terminating resisitor
inserted in connector
on PCU
Distribu-
MCP on
tor box
Terminating resisitor
integrated
OPI on
840D control
MPI on
Distribu-
tor box
PG
on
HPU
Example B
on
Terminating resisitor
inserted in connector
PCU
OP030
MCP on
Terminating resisitor
on
integrated
on
OPI
840D control
Standard application
SINUMERIK 840D with PCU and one machine control panel (MCP) or interface
customer operator panel on the OPI
Hardware requirements
At least firmware release V 03_01_01 for
• MCP
• Customer operator panel / PP031
Bus addresses
Each node on the MPI/OPI bus must have a bus address (0...31).
1 OPI
1.5 MBaud
6
SINUMERIK 840D
MCP/interface
X101
13 customer operator
NCK panel
PG/ 0
setup tool X122 PLC
2
MPI
187.5 kBaud
! Important
The logical addressing of components in the PLC basic program is performed by
means of the bus address parameter setting (for the machine control panel) or
the GD circuit (for the handheld operator unit). The GD circuits are always used
for physical addressing on the OPI/MPI. Every machine control panel, interface
customer operator panel etc. must be addressed with a GD circuit.
In the control, the conversion of the bus address in the associated GD circuit is
performed via the PLC program.
The bus address, and therefore the setting of the associated GD circuits, are set on
the machine control panel by means of DIP-FIX switches.
On the MPI, however, the same GD circuits are set for different bus addresses for
the components machine control panel, interface customer operator panel, PP031
and HPU. Allowance should be made for this when using more than one machine
control panel, etc.
The table below shows the relationship between bus addresses and GD circuit.
Table 3-1 Relationship between bus address and GD circuit
Bus addresses on MPI GD circuit
15,14,13 1
12,11 2
10, 9 3
8, 7 4
6 8
5, 4 5
Example:
Two machine control panels (MCPs) on the MPI are to be connected to one
control. The first MCP can be connected to bus address 15 (GD circuit 1), the
second to bus address 12 (GD circuit 2).
Note
If PLC lateral communication is to be configured on the MPI with the STEP 7 tool
"Communication Configuration", for example, and one or several MCPs is/are to
be connected to the MPI, it is important to ensure that the GD circles are uniquely
assigned. The STEP 7 tool "Communication Configuration" allocates the GD
circuits, starting at GD circuit 1, in ascending order. If the MCPs on the OPI are
connected, the PLC-PLC communication on the MPI is not affected.
Example:
"Communication Configuration" allocates GD circuits 1 and 2 for PLC-PLC lateral
communication. The first MCP on the MPI can be assigned to GD circuit 3 (bus
address 9 or 10), and a second MCP can be assigned to GD circuit 4 (bus address
7 or 8).
USB keyboard
If a USB keyboard is connected, a reset must be performed on the PCU: Key
combination Ctrl + Q + Input or, if this key combination is not available: "Power
OFF“.
Delivery
The Network Manager software is supplied on the CD
"Administer SINUMERIK 810D/840D network/diskette drive on the PCU 20"
with the order number 6FC5253-0AE01-0AA0.
Precondition
The Network Manager is available for the operating systems Windows95/ 98/ ME
and WindowsNT/ 2000/ XP.
The PCU and HMI Embedded Network Manager communicate with one another
via TCP/IP sockets.
Client
(HMI Embedded Server
System) (Server
computer)
For the connection to be secure, a password and user name must be set on the
client and on the server. These are defined on the client as part of the network
startup process.
Any users who need access to the server must be registered in the Network
Manager with their name and password.
If no user names have been defined, the system uses a standard user name
(PCU20_USER).
3.3.1 Installation/deinstallation
Installation
The HMI Embedded Network Manager is installed by running the "setup.exe"
program.
Deinstallation
The deinstallation of the HMI Embedded Network Manager is performed under:
"/Start/Settings/Control Panel/Software". Select the HMI Embedded Network
Manager and click "Add/Remove..." to deinstall.
Start
Start the Network Manager under "Start/Programs/<name selected during the
installation>/HMI Embedded Network Manager".
When you start the Network Manager, an icon is displayed in the status line of the
taskbar (Windows) to signal that the manager is active on this particular computer.
Right-click the icon to open the shortcut menu which contains the following entries:
Help...: Displays the main Help menu for the Network Manager
Message window... In this dialog box you can check the status
of the current connection.
Activate detailed trace file... A trace file is activated which logs all
telegrams with their contents. The icon in the
status line changes.
The status data of the Network Manager are displayed in the upper part of the
window.
The following data must be entered in the lower part of the screen:
The user name need not correspond to the current user, but the "permanent
connection" must be authorized to access the directories of the entered user.
See section: User administration
Note
Setting up or clearing a permanent connection can take several seconds.
Simple network
Each PCU is shipped with a standard user name "PCU20_USER"; this name is
also entered in each Network Manager as soon as it is installed. However, this user
name should be used only in a simple point-to-point connection because the data
on the server can be accessed within a larger network and secure communication
between the PCU and the server cannot be guaranteed if the standard user name
is used.
Large network
If you wish to share selected directories with a particular PCU, you must assign
appropriate rights to the relevant PCU user in the Network Manager.
You can make the following entries within the "User management..." dialog box:
- New: Create new user.
In the top section of the screen, enter the user name (max. 40
characters) and its password (max. 40 characters). Repeat the
password in the "Confirm Password" field.
In the central area of the screen, you assign access (operating system
shares and HMI-specific shares) to the shared drives on the server
computer of the relevant user.
The left-hand field (List of visible shared folders) contains all folders to
which the user can be granted access.
The right-hand field (List of shared folders) contains all shared folders
to which the Windows user who started the Network Manager has
access and all HMI-specific shared folders that have been set up within
the Network Manager.
By clicking "Å Add" you can add a folder selected in the right-hand field
to the left-hand list and thus make it accessible to the user.
By selecting "Æ Remove" you can delete a visible folder (on the left-
hand side) again.
You can enter hidden shared folders manually in the "Add hidden
shared folder" field and click "Å Add hidden" to add them to the "List of
visible shared folders ..." field.
The abbreviation at the start of the status line has the following
meaning:
- OS: Operating system share
- HMI: HMI-specific share
Clicking "OK" will confirm these settings and the dialog box is exited.
Clicking "Cancel" will reject these settings and the dialog box is exited.
Clicking "Help" calls the help function.
- Edit: In this box you can edit an existing user who you have selected. The
"Edit..." dialog operates on the same principle as the "New..."
dialog.
- Delete: An existing user who you have selected can be deleted. A prompt
appears with which you must confirm the actual deletion with "YES".
With "NO", you can reject the deletion.
To enable a folder for sharing, click it in the Windows Explorer with the right-
hand mouse button:
• Select the item "Share...".
• Select "Share as".
• Enter the share name. You can also assign the rights to the shared folders.
When you select menu option "Config HMI specific shared folders..." the
following dialog appears:
Fig. 3-10
Fig. 3-11
Precondition
The following programs must be installed on the system:
• Microsoft Internet Explorer 4.0 or higher,
• Microsoft Help HTML Viewer
If the Help HTML Viewer is not available on your computer, the "hhupd.exe"
installation routine is started to install the viewer.
The Help HTML Viewer is integrated as standard in WindowsNT/ 2000/ XP and
must not be installed again.
3.3.7 Troubleshooting
There is an error in communication between the PCU and the HMI Embedded
Network Manager. Check the ports.
Remedy
1. The following ports must be available:
- pcu20_ftp1 6743/tcp
- pcu20_ftp2 6744/tcp
- pcu20_ftp3 6745/tcp
- pcu20_ftp4 6746/tcp
- pcu20_ftp5 6747/tcp
- pcu20_ftp6 6748/tcp
- pcu20_ftp7 6749/tcp
- pcu20_ftp8 6750/tcp
- pcu20_ftp9 6751/tcp
- pcu20_ftp10 6752/tcp
- pcu20_ftp11 6753/tcp
- pcu20_ftp12 6754/tcp
- pcu20_ftp13 6755/tcp
- pcu20_ftp14 6756/tcp
- pcu20_ftp15 6757/tcp
If necessary, these ports are entered in the "services" file every time the HMI
Embedded Network Manager is started. If a port is already being used by another
program, the program must be uninstalled so that the port can be made available
to the Network Manager.
2. Check the software versions
You must use the correct Network Manager software version in each case for the
HMI Embedded software version installed.
3.4 Network operation with HMI Embedded (SW 6.2 and higher)
This function is the option "Administer SINUMERIK 810D/840D network/diskette
drive on the PCU 20".
The PCU hardware has its own network card and can be integrated in an existing
network. If the appropriate option is set, additional horizontal keys are integrated in
the Program Manager of the "Machine" and "Program" standard applications; these
soft keys symbolize a linked drive or a local drive.
Precondition:
The Network Manager must be installed on the PC to be connected,
see Section "Network Manager on the server".
Possible connections
The number of possible connections between the HMI Embedded system and
different servers or local drives is limited to four.
The following machine data are available for authorizing the use of the drives that
are set up:
MD 9510 MM_USER_CLASS_DIRECTORY1_P
MD 9511 MM_USER_CLASS_DIRECTORY2_P
MD 9512 MM_USER_CLASS_DIRECTORY3_P
MD 9513 MM_USER_CLASS_DIRECTORY4_P
(value 0...7)
TCP/IP protocol
The only protocol supported for configuration within the network startup masks is
TCP/IP.
Section "Examples: Network Configuration" describes two possible configuration
options:
1. A small self-contained network whose sole purpose is to network the PCU with
one or more servers.
2. A large company network.
In the first example, both the HMI Embedded configuration and the Windows
configuration are explained in detail. The second example provides an explanation
of the HMI Embedded system configuration only, as the company network is
already in existence and the company has network administrators to perform the
Windows tasks.
2. Subnet mask:
You need to select a subnet mask that is unique within the entire network.
3. Computer name:
The computer name is optional, as it is only a symbolic identifier and can be
replaced by the IP address at any time.
4. User name/password:
The user name and password are used to protect communication between the
HMI Embedded system and the associated Network Manager on the server. If
you assign a user name and a password, you need to specify them in the
Network Manager as well. This means that the HMI embedded system will be
recognized as an authorized user. If you don't assign a user name and
password, the system enters a standard user (PCU20_USER) and standard
password so that the Network Manager can decide whether the request comes
from an authorized user or not and refuse it if appropriate.
See Section: User management
! Important
As no "hub" is used, you will need a special twisted-pair cable for the point-to-
point connection.
Crossed
twisted pair cable
IP address: 192.168.0.1
Subnet mask: 255.255.0.0
Computer name: PCU20_1
User name: PCU20_USER1
Password: ********
IP address: 192.168.0.4
Subnet mask: 255.255.0.0
Computer name: SERVER_1
IP address: 192.168.0.2
Subnet mask: 255.255.0.0
Computer name: PCU20_2
User name: PCU20_USER1
Password: ********
IP address: 192.168.0.5
Subnet mask: 255.255.0.0
Computer name: SERVER_2
IP address: 192.168.0.3
Subnet mask: 255.255.0.0
Computer name: PCU20_3
User name: PCU20_USER1
Password: ********
As in this case the same user name was chosen for all three HMI Embedded
systems, the same password must be entered on each system too.
You can also, however, enter a different user on each HMI Embedded system. The
respective users must then be entered in the Network Manager on the servers
whose drives are to be displayed.
Company network
A fixed IP address is used to address the company network. You will need to ask
your administrator for an IP address for each PCU. The computer name is also
provided by the network administrator and corresponds to the IP address that is
set. Further, it is necessary to have the correct subnet mask for the network and a
default gateway (router). If you intend to use a DNS server, you will also need its IP
address and the DNS domain. The data must be entered in the "Startup" operating
area under "Logical drives" "Network configuration".
You can select any user name you want, as long as it is known within the Network
Manager so that a secure connection can be established.
Network configuration
The network is switched off when the HMI Embedded system starts for the first
time.
There are three options:
HMI boot without network
• A network is not started when the HMI Embedded system is booted, therefore
no network drives are available. This setting is the default setting at initial
system startup. After the first start, the user can specify network data if
required.
If the network is to be set up, first the setting "HMI boot:" must be set to either "with
network" or "with network if confirmed". The remaining fields can now be edited
and the following settings entered:
The remaining fields must not be filled in as this small network does not have a
DNS server or a default gateway.
With external drives (network connections) you need to specify the full network
path (\\Computer name\Share name\Path specification), whereby the path name is
optional:
\\R4711\Workpieces\Template
\\R4812\Workpieces
The names you specify must be available on the network computer.\\R1234 refers
to the network computer in our example. The share name WORKPIECES must be
specified on any hard disk drive on this computer.
Server name
In order to assign symbolic names to the computers, the relevant nodes to be
addressed within the network must be entered so that their names can be resolved:
Example
Server name:
192.168.0.20 R2345
192.168.0.21 R2346
With these settings computers R2345 and R2346 can be addressed by means of
their symbolic names.
Operation:
The first entry in the line is the IP address. The second entry is the computer name.
The data already specified appears in the upper section of the screen. By selecting
soft keys "New" and "Edit" you can go to the lower half of the screen where you
can edit entries.
You can change back to the upper section by pressing the "Cancel" soft key (data
is not saved) or the "Save" soft key (data is saved).
File types
File types must be set up as required. These types are evaluated and displayed
by the PCU.
The Program Manager will use the file extensions to filter which files to display and
which to hide. This filter function can be set as follows:
If soft keys "New" or "Edit" are selected, then like with the dialog box "Enter server
name", you change to the lower section of the screen and make additional entries
or edit existing ones. To exit, press "Cancel" (without changes) or "Save" (with
changes).
Example:
Computer name: SERVER_1
Work group: GROUP1
3.5 EXTCALL
During execution the first file is transferred via a quick download operation. For this
reason, time-critical reload sections should always be included in the first execution
file.
The program to be called must be specified in a unique manner and with the full
path and file name.
A prefix part of the path name can be predefined via the channel-specific setting
data 42700 SC_EXT_PROG_PATH.
Example:
Full path name in NC program:
N10 EXTCALL ("C:\Workpieces\Template.mpf")
- with prefix part in setting data:
SC_EXT_PROG_PATH = C:\Workpieces\
N10 EXTCALL("Template.mpf")
Note
It is not advisable to execute a program directly from a network drive as there is
no guarantee that the network performance will be stable or sufficiently dynamic.
We recommend that you transfer programs via the network to an optional plug-in
Compact Flash card.
The drive letter of this external storage medium always begins with C:\
The storage media must always be plugged in before the computer boots. They
cannot be hot-swapped.
Backup option
A complete system data image is downloaded to an external device.
In a selection menu you can choose the following back-up options:
• Transmission via RS-232-C to an external device,
• to diskette.
If you have installed a floppy drive on your PCU 20 press 'F' to save
exception data to floppy disk
Make sure you use the correct com port and the same baud rate as the
receiving station. Then press 'T' to transfer data via serial line.
You can also press 'R' to reboot immediately but we recommend you
save the data first.
Transfer to diskette
When you select key "F" you start transmission of the exception trace to diskette.
The following status message appears:
Abort transfer
If errors occur in the transmission, or you have set the baud rate incorrectly, you
can stop the transmission again by pressing key "S". The following message
appears about 2 to 5 seconds after you press key "S":
Transmission finished
Once all the data have been transferred successfully, the following message
appears:
When using serial transmission please check the number of saved bytes
with the number of bytes received by the remote device.
If there is any difference please return to the save menu by pressing
the 'S' key and retry the transmission with a lower baud rate.
Note
When you use the serial link, the number of transmitted bytes is also displayed
and must match the number of bytes received. If the two numbers are not the
same, abort the transmission by pressing key "S", select a lower baud rate and
start the transmission again.
3.6.1 Restart
The exception handler attempts an automatic restart in Restart mode.
Try
Try rebooting
rebooting -- in
in the
the event
event of
of no
no reaction
reaction after
after 11 minute,
minute,
please switch Off/On
please switch off/on
If the PCU has not reacted after 60 seconds, you must restart it manually by
switching the power supply to the system or the operator panel front off and then
on again.
Note
These times apply on condition that the external device can receive the set baud
rate without blocking.
4 Switching On/Power Up
4
4.1 Establish readiness for operation ............................................. IM2/4-48
Information on how to adapt and set the interface and which connection cable is
required, is to be found in the manual of your I/O device.
Note
When connecting I/O devices, please make sure that the components are
designed for use in industry!
! Caution
When plugging in / unplugging I/O connections (keyboard, mouse, printer, etc.),
make sure that the I/O devices and the PCU are disconnected from the power
supply. Otherwise they may be damaged.
This does not apply to USB connections.
4.2 Ramp-up
As soon as the power supply is switched on the PCU ramps up automatically and
displays a start screen if NC-PLC data communication has been established. If
there is no NC-PLC data communication, the following message appears: "Waiting
for communication" (black screen).
Powerline
Since software version 6.2, the Siemens ramp-up screens for the NCU/CCU types
with "powerline" are specially marked. The control detects the "powerline" module
automatically and the name is displayed in the ramp-up screen.
5 Functions/Parameterization
5
5.1 Access protection via password and keyswitch........................ IM2/5-51
5.1.1 Password ............................................................................ IM2/5-52
5.1.2 Keyswitch ............................................................................ IM2/5-53
5.11 Define machine position and rotary axis position ................... IM2/5-72
Access rights
• 0 to 3 are locked by means of a password and
• 4 to 7 by means of keyswitch positions.
Access features
• Protection level 0 provides the greatest number of access rights,
protection level 7 the least.
• Access rights can be set by querying the current keyswitch positions and
comparing the passwords entered. When a password is entered it
overwrites the access rights of the keyswitch position.
• Access rights for protection levels 4 to 7 are only suggestions and can be
altered by the machine tool manufacturer or end user.
5.1.1 Password
Set/reset password
The passwords for the 4 available password levels with their respective access
authorization can be entered in the "Diagnostics" operating area through selection
of soft key "Set password".
References: /BEM/ Operator's Guide HMI Embedded
A password remains valid until the access authorization is reset with the soft key
"Delete password".
Access authorization is therefore not automatically deleted by Power On!
Permitted characters
Up to eight characters can be used in the password. We recommend that you
restrict yourself to the character set of the operator panel in selecting a password.
Where a password consists of less than eight characters, the additional characters
are interpreted as blanks.
Default passwords
The following default passwords are defined for protection levels 1 to 3:
Protection level 1 SUNRISE
Protection level 2 EVENING
Protection level 3 CUSTOMER
Note
The passwords are entered as the defaults on system ramp-up in start-up mode
(NCK start-up switch in position 1).
The default passwords should be changed in order to guarantee reliable access
protection.
5.1.2 Keyswitch
Protection levels 4 to 7 require a corresponding keyswitch position on the machine
control panel. Three keys of different colors are provided for this purpose. Each of
these keys provides access only to certain areas. The keyswitch positions are
transferred at the PLC interfaces. The associated interface signals are in the DB10,
DBB56 and can be evaluated by the PLC user program.
Keyswitch application
The keyswitch can be used to inhibit access to certain data areas. In this way, for
example, unintentional changes by the operator in the geometry data (e.g. work
offsets) can be excluded.
Keyswitch position 0 has access rights of the lowest priority and position 3 access
rights of the highest priority.
Example:
%_N_SGUD_DEF ; File for global variables
; $PATH=/_N_DEF_DIR
REDEF $MA_CTRLOUT_SEGMENT_NR APR 2 APW 2
; (APR ... read access)
REDEF $MA_ENC_SEGMENT_NR APR 2 APW 2
; (APW ... write access)
REDEF $SN_JOG_CONT_MODE_LEVELTRIGGRD APR 2 APW 2
M30
The file becomes active when the next _N_INITIAL_INI is read in. Different
protection levels are specified for writing (changing) or reading (parts program or
PLC).
Example:
MD 10000 has protection levels 2/7, i.e. writing requires protection level 2
(corresponding to password) and reading requires protection level 7. In order to
access the machine data area, key switch position 3 or more is required.
Example:
%_N_SGUD_DEF ; File for global variables
; $PATH=/_N_DEF_DIR
REDEF $MA_CTRLOUT_SEGMENT_NR APR 7 APW 2
; (APR ... read access)
REDEF $MA_ENC_SEGMENT_NR APR 0 APW 0
; (APW ... write access)
REDEF $SN_JOG_CONT_MODE_LEVELTRIGGRD APR 7 APW 7
M30
5.2 Functions
In MD 9006, the function "Screen dark from HMI Embedded" can be started using
the following entry:
MD 9006 = 1 < time in minutes, e.g. 1 >
MD 9006 = 60 < time in minutes, e.g. 60 >
MD 9006 = 0 Deactivation of the function (default setting)
Caution
If a high contrast picture is displayed on the TFT display for more than an hour,
there is a danger of irreversible display damage due to the so-called "burn-in
effect".
In order to avoid this undesired effect, the screen saver must always be active.
Two of these languages can be selected during the installation. During operation,
the switchover between the first and the second language is performed via the soft
key "Change Language".
In addition to these standard languages, further languages can be loaded via the
language CD.
After the installation, the text for the selected machine data item is displayed below
the machine data list in the Set-up operating area.
Syntax
Plaintext number
Number: Number of the machine data item
Plaintext: Plaintext of the machine data item, maximum 62 characters
(The plaintext cannot be enclosed by inverted comas.)
Note
If a machine data item has different indices and you do not specify an index for
the plaintext, the same plaintext appears for all the indices of the machine data
item.
Examples:
14504 Number of user data (INT)
14510[0] First user data item (INT)
14510[1] Second user data item (INT)
Note
Changes can only be made to the PLC operands with the appropriate password.
The settings in the PROGRAM operating area are retained after a reset.
If a valid display duration is set, each alarm is displayed for this time before being
replaced by the next alarm.
Procedure
Before installation (see Chapter 7), you must copy the desired screen
"Logo_oem.bmp" into each directory with the appropriate resolution.
Copy the batch file "oem_bmp.bat" from the "tool\oem_bmp" directory on the
supplied CD into the BIN\640, BIN\800 and BIN\1024 directories and start the
batch file in each of these three directories.
MD 10260 CONVERT_SCALING_SYSTEM ≠ 0
Function
Using the user interface, you can establish a connection between the HMI
Embedded unit and the connected NCU/PLC units in each operating area.
Channell13
Channel14
Channel15
Mill 1 Mill 2
Channel switchover
You can switch to other channels by means of the vertically arranged soft keys.
Group switchover
Use the horizontal soft keys to switch over to a different group; the channels of the
current group are now displayed on the vertical soft keys. Switchover to another
channel (and if necessary to another NC) only takes place upon activation of a
vertical soft key.
Note
The soft keys only offer the connections that are really assigned and whose
channels are active in the respective NC.
Note
The NC writes the channel number of HMI Embedded in DB19, DBB22 or DB19,
DBB72 (2nd interface).
The names in the file NETNAMES.INI are limited to five characters.
NETNAMES.INI
[own]
owner= HMI_1
; Description of possible connections
[conn HMI_1]
conn_1= NCU_1
; Description of significant net parameters
[param network]
bus= opi; the mpi interface must be used on the SINUMERIK 810D
[param HMI_1]
mmc_typ = 0x20
mmc_bustyp = OPI
mmc_address = 1
mstt_address = 6
name = HMI1
start_mode = ONLINE
[param NCU_1]
nck_address = 12
plc_address = 12
name= NCU1
; Description of a standard channel configuration
[chan HMI_1]
ShowChanMenu = TRUE ; FALSE -> deactivate the channel menu
DEFAULT_logChanSet = Mill_1
DEFAULT_logChan = Channel11
logChanSetList = Mill_1, Mill_2
[Mill_1]
[chan HMI_1]
ShowChanMenu = TRUE ; FALSE -> deactivate the channel menu
DEFAULT_logChanSet = Mill_1
DEFAULT_logChan = Channel11
logChanSetList = Mill_1, Mill_2
[Mill_1]
logChanList = Channel11, Channel12, Channel13, Channel14, Channel15,
[Channel11]
logNCName = NCU_1
ChanNum =1
[Channel12]
logNCName = NCU_1
ChanNum =2
[Channel13]
logNCName = NCU_1
ChanNum =3
[Channel14]
logNCName = NCU_1
ChanNum =4
[Channel15]
logNCName = NCU_1
ChanNum =5
[Mill_2]
logChanList = Channel21, Channel22, Channel23, Channel24,
[Channel21]
logNCName = NCU_1
ChanNum =6
[Channel22]
logNCName = NCU_1
ChanNum =7
[Channel23]
logNCName = NCU_1
ChanNum =8
[Channel24]
logNCName = NCU_1
ChanNum =9
Example:
File with OEM name specifications for channel-areas and channels
//* text definitions for soft keys in channel switch menu *///* name of channel area 1
and names of channels of channel area 1 */
The OEM user can enter texts by inserting them in the blank character strings (see
above ")! 8 characters are possible per soft key bar; the carriage return is created
with characters "%n": e.g. "NC3Turn%nChann1".
The MMC 100.2 is described in the above document which corresponds exactly to
the functionality of HMI Embedded.
Note
This functionality requires NCK software version 4 and later.
If you use the function in the reset state, machine data MD 20110
RESET_MODE_MASK bit 0 = reset mode must be set accordingly. Then the tool
offset is not reset on a reset.
A D number can be assigned just once per tool, i.e. each D number stands for one
and no more than one offset data set.
Example:
Suppose you want to create a workpiece template with the content "Daten.ini" and
"TEST.MPF":
Workpiece: _TEMPL_
_TEMPL_.MPF
DATEN.INI
TEST.MPF
Operating sequence:
1. Press soft key "New"
2. Name: Define "ACHSE"
3. The new workpiece "ACHSE" is created with the following files:
ACHSE.MPF
DATEN.INI
TEST.MPF
Note
The functions of HMI Embedded can be altered in the INI files, display MD or the
user interface.
Another column for the fine offset is inserted alongside the column for entering the
offsets.
The inputs are checked against the display machine data
• MD 9203: USER_CLASS_WRITE_FINE
• MD 9451: MM_WRITE_ZOA_FINE_LIMIT
The first data describes the protection level, and the second data the amount of a
possible value that can be entered.
The base work offset (base WO) is displayed like a settable work offset and can be
selected and modified using the soft key "Base WO" in the screen form "Overview
of work offsets".
Introduction
The behavior of the scratching and preset actual value memory, PRESET
functions is influenced by a number of machine data. The selected settings also
affect operation. (Display of soft keys and values, saving of input values).
With the introduction of system frames in software version 6, two variants are
available for the functions. The variants are differentiated by a channel-specific
MD:
MD 28082: MM_SYSTEM_FRAME_MASK
Bit: 0 Preset, scratching
1 External work offset
2 TCARR, PAROT
3 TOROT, TOFRAME
4 Workpiece reference points (SW 6.3 and higher)
5 Cycles (SW 6.3 and higher)
6 Frame transformation (SW 6.4 and higher)
3: Preset actual value memory: NCK with/without system frame: Setting possible
in the currently active frame.
Note
To hide the PRESET, preset actual value memory and scratching soft keys, MD
9220: MM_USER_CLASS_PRESET can be set.
Scratching
Scratching with system frame
G500 active
- The values are written to the system frame
G500 not active
- The values are written in the currently active frame
You cannot choose any tool other than the one in the spindle.
If there is no tool in the spindle, you can choose any tool you want.
Function
Channel-specific MD 20098 DISPLAY_AXIS can be used to hide axes in the
Machine operating area.
All axes are displayed by default.
In this way you can specify separately for the view in the machine or workpiece
coordinate system whether or not the axis is displayed:
20098 DISPLAY_AXIS
MD number Display or hide axis on MMC/HMI
Default setting: 0xFFFFFFFF Minimum input limit: 0 Maximum input limit:
0xFFFFFFFF
Changes effective after POWER ON Protection level: 2/7 Unit: -
Data type: DWORD Applies from SW: 4.4
Meaning: Bits 0 to 15: WCS
Bit 0= 1 Show geometrical axis in actual-value windows
0 Hide geometrical axis in actual-value windows
Bit 1 1 Show geometrical axis in reference point
windows
0 Hide geometrical axis in actual-value windows
Bit 2= 1 Show geometrical axis in preset/base
offset/scratching/work offset window
0 Hide geometrical axis in preset/base offset/
scratching window
Bit 3= 1 Show geometrical axis in handwheel selection window
0 Hide geometrical axis in handwheel selection
window.
Special cases
• Reference point approach and Safety Integrated
MD 20098 DISPLAY_AXIS is not evaluated in the displays for referencing
mode, i.e. in the axis reference point and acknowledge safe position display. All
machine axes are always displayed.
Therefore the operator cannot change the values for the base work offset without
the appropriate access authorization.
These settings apply to both the actual-value window and the editor window.
Example
In the NC program the movement of axes from X120 Y20 Z-50 to X200 Y200 Z-120
looks like this in binary display:
You can choose whether or not to show the STAT and TU values by setting the
following display machine data:
To be able to simulate certain operations during a dry run even though the
axis/controller pulses have been disabled, the transfer of status "ext. pulse disable
active, terminal 663 open" to the NC must be inhibited.
The machine manufacturer can achieve this by evaluating the above-mentioned
PLC signal and activating the dry run simultaneously with NC Start.
If the drive MD 1012 FUNC_SWITCH, Bit 2 = 0 is also set, the status "ext. pulse
disable active, terminal 663 open" is not transferred to the NC.
When the option is set, you can select the function via the "3D Simulation" softkey.
The contour elements of the contour chain are displayed by symbols or text.
Via the MD 9020 TECHNOLOGY, you define the basic configuration for the free
contour programming of turning/milling.
In HMI Embedded you can integrate screen forms which provide support for
programming measuring cycles into the G code editor. These cycles can then be
recompiled automatically.
The "measuring cycles" function is a software option with order no. 6FC520-
0BX00-0AB0.
For further information about measuring cycle support, please refer to:
References: /BNM/ User's Guide Measuring Cycles
In this way, you establish the connection between the soft keys, with which
you call the measuring cycle support, and the configuration file of these
support screens.
In this way, you can change the properties of the measuring cycle support in
the Start-up operating area.
Change the properties of the measuring cycle support in the "Start-up" " >"
"Measuring Cycles" menu.
Note
You can set the position of the coordinate system for turning in MD 9610
CTM_POS_COORDINATE_SYSTEM.
+Y +Z +X
+Z
+Y
+X +Y
+X +Z
0 +X 1 +Z 2 +Y 3
+Z +Z
+Y +Y +X
+X
+X +X
+Y +Z
4 5 +Z 6 +Y 7
+X +Y
+Z +X
+Z +Z
+Y
+Y
8 +Y 9 +X 10 +Z 11 +X
+X
+X +Z
+Z +Y +Y
+Y +Y
14 +Z
12 13 +X +Z 15 +X
+Y +X +Y +Z
+X +Z +X
+Z +Y
16 17 +Y 18 +X 19
+Z
+Y +Y +Z
+X +X
+Z
+Z
+Z
20 23 +X
21 +Y 22 +X +Y
+Y +Z +X
+Y
+Z
+X +Z
+X
+Y
24 +X 25 +Y 26 +Z 27
+Y +Y
+Z +Z +X
+X
+X +X
+Z +Y
28 29 +Y 30 +Z 31
+X +Y +X +Z
+Y +Y
+Z
+Z
32 +Z 33 +X 34 +Y 35 +X
+X
+X +Y
+Y +Z +Z
+Z +Z
+Y
36 37 +X 38 +Y 39 +X
+Z +X +Z +Y
+X +Y +X
+Y +Z
40 +Y 41 +Z 42 +X 43
+Z +Z +Y
+X +Y +X
+Y
+Y
+X
44 45 +Z 46 +X 47 +Z
The PC card with the remote diagnostics software must be inserted when the
PCU 20 is switched on. The card must be started up during the initial ramp-up.
(Press key 6 during ramp-up, modem on COM1 or COM2...)
The remote diagnostics software only supports graphics mode 12 (640 x 480, 16
colors). With higher resolution displays, a small centered screen is displayed.
You can find a detailed description of the installation, configuration and operation
of the remote diagnostics in
Remote diagnostics "RCS Host PCU 20 / RCS Viewer PCU 20" as of HMI SW 6.5
See following section: "Remote diagnostics RCS Host PCU 20 / RCS Viewer
PCU 20"
The remote diagnostics software "RCS Host PCU 20" is already installed on the
PCU 20.
For the PC, the remote diagnostics software "RCS Viewer PCU 20 V1.0" is
supplied on the remote diagnostics CD
"RCS Viewer (Edition 01/2004)" with the order no.: 6FC6000-6DC01-1BA0.
It is then possible for a service engineer to monitor and influence a controller via its
PCU 20 from a remote PC (remote PC = viewer), i.e. the same display is shown on
the remote PC as on the PCU 20.
Precondition
The following hardware and software is required:
• Establish a tunnel connection between the PCU 20 (machine) and the remote
PC (viewer), e.g. via hardware router with so-called VPN (Vitual Private
Network) functionality, e.g. Cisco 803
• Windows PC (NT4/95/98) with network connection
• "Viewer" application (mmcR.exe) from the remote diagnostics CD (remote PC)
• Ethernet cable
• Network Manager (on the remote PC)
- Set up logical drive for the data exchange (file transfer)
• "Ping" server application (optional, but recommended) which accepts and
manages incoming service requests from the PCU 20. This SW is not part of
the scope of delivery!
Connection structure
The example shows the connection via the ISDN network (64 kbit/s). This
telephone network provides the capability of connecting to remote LANs via a
tunnel using the point-to-point protocol (PPP). The PCU 20 is connected to the
ISDN network via the Ethernet interface with a hardware router (with VPN
functionality).
172.1.1.2
Host: PCU 20 (HMI Embedded)
IP 192.168.254.4 Ethernet BRIO Interface BRIO Interface Ethernet Host: IP 192.168.12.238
174.1.1.1 192.168.254.1 192.168.12.237 172.1.1.1
Process: UDP Ping (Server) Process: UDP Ping (Client)
on Port 9999 Target: 192.168.254.4:9999
Tunnel Connection
Host: Remote PC (VPN) Process: "RCS Host PCU 20"
IP 192.168.254.129 (Server) on Port 5800
Process: "RCS Viewer PCU 20" (Client) Process: File transfer (Client)
Target: 192.168.12.238:5800
Usually the remote PC should have a "Ping" server application in its LAN for the
log-on and monitoring of the remote diagnostics session. This server has the task
of accepting the incoming "Ping" data (e.g. serial number) of the requesting
machine and registering the IP address of the requesting PCU 20. This can be
implemented, for example, with a simple server application based on the UDP. The
IP address, the port and the protocol used for this Ping server is specified by the
service provider and must be set on the PCU 20.
The remote diagnostics is intiated by the PCU 20. The PCU 20 is connected to the
appropriately configured router via an Ethernet cable and starts the remote
diagnostics via the "Diagnostics" operating area and the "Remote diagnostics" soft
key.
The PCU 20 then sends cyclical preset "Ping" data to the remote PC and waits for
its response. The sending of the "Ping" causes the router to establish the
connection (e.g. ISDN switched communication).
When the response is received from the remote PC, the PCU 20 is ready for the
data communication for the remote diagnostics. For this, a server process is
started on the PCU 20 which is responsible for the exchange of graphic information
to the remote PC and the keyboard inputs from the remote PC.
The exchange is performed via the TCP/IP protocol and a "permanently" agreed
port, the so-called "RCS Host PCU 20 port". A so-called "Viewer" application
(mmcR.exe) is installed on a remote PC as communication partner. As of now, all
further activites initiate from the remote PC.
With the arrival of the "Ping" on the PC, the IP address of the requesting PCU 20 is
known and the "Viewer" application (mmcR.exe) with this destination IP address
can be started on a PC. This application runs as client. The PCU 20 can be
monitored and controlled via this remote PC.
The transfer of files between the remote PC and the PCU 20 is handled in the
same way as the access to logical drives - so-called Share Folders. A folder (Share
Folder), which accepts the transferred files, only has to be selected on the remote
PC.
The appropriate settings are automatically made by the system on the PCU 20.
The file transfer is performed via a separate communication process ("HMI
Network Manager"). This process runs on the remote PC as server. The port used
for this is called "Port for share folder" in the following. This server application is
automatically called with the start of the "Viewer" application.
The entries
• IP address
• Subnet mask
• Gateway
are already specified by the router configuration and are only used as examples
here.
When you press the "Save" soft key, the PCU 20 is restarted.
The port number, default 5800, is entered in the "Port for remote diagnostics
(default 5800)" input field for the server process (remote diagnostics). The same
port number must be entered in the "Viewer" application on the remote PC.
Pressing the "Save" soft key terminates the configuration of the server.
If, from the four possible "logical drives", no connection is available, the message
"Caution: No configurable share available!" appears.
Deactivate the remote diagnostics by pressing the "Exit" soft key.
Switch to the "Start-up" operating area, press the soft key "Connections" and
delete a connection entry.
When you restart the remote diagnostics "RCS Host PCU 20", the connection
"REMOTE_FOLDER" is automatically set up and the soft key with the same name
generated.
Precondition
• Remote diagnostics CD with the "RCS Viewer PCU 20" software
• HMI Network Manager (for data exchange, the file transfer)
Installation
The "RCS Viewer PCU 20" is installed by running the "setup.exe" setup program.
The installation path should be noted for the later "Network Manager" installation.
Note
"Network Manager" and "RCS Viewer PCU 20" must be in the same path.
You must then, if you have not already done so, install the Network Manager in the
same directory as the "RCS-Viewer PCU 20" application.
Also, during the installation of the Network Manager option, you must click the "No"
button twice in the "Select Components" window.
Configuration
Start the "Viewer" application "mmcR.exe" on the remote PC. When starting the
"mmcR.exe" for the first time, you must select a folder (share folder) on the PC.
Data is transferred to and from the PCU 20 via this common folder (file transfer).
This folder is managed under the permanent name "REMOTE_FOLDER". The file
transfer uses this name only for the identification of the source or the target.
When you click the "Yes" button, the dialog box for the selection of the storage
path appears. Either enter the path in the "Config HMI-specific shared folders..."
field or click "Browse..." so that the path can be selected in the Explorer view.
Confirm the selection with "OK".
You return to the following window and the selected storage path is displayed:
Click the "Add" button and then "OK" to conclude the configuration for the file
transfer.
Note
The name "REMOTE_FOLDER" cannot be changed as only this name is used as
reference on the PCU 20.
If this port (e.g. 1902) is after the service entry "pcu20_remote diagnostics 1902/tcp
#Siemens..." in the "Services" file, the entire line must be deleted.
PCU 20 (host)
Activate the "RCS Host PCU 20" in the "Diagnostics" operating area via the
"Remote diagnostics" and "Start" soft keys.
Status messages provide information on the current state.
When the connection to the remote PC is established, the PCU 20 waits for the
"Viewer“ application (mmcR.exe) to be started on the remote PC and the
communication for the data exchange to be activated.
The message: "Ping server responds" appears.
This communication is performed via the "RCS Host PCU 20 port" which, per
default, is applied to port number 5800.
When the message "Communication running" appears, operation of the PCU 20
from the remote PC is possible.
Remote PC (viewer)
When you start the "mmcR.exe", the "RCS Viewer PCU 20" window opens.
If a "Ping" server is operated, then the IP address of the PCU 20 is known on the
remote PC after the first "Ping" has been received and can be transferred with the
call of the "Viewer" application or entered directly in the dialog field:
e.g.: 192.168.12.238
When you click the "Connect" button, the connection with the PCU 20 via the "RCS
Host PCU 20 port" is activated. The corresponding status messages are output in
the field below. When these are completed, the dialog is reduced and the HMI
Embedded interface appears.
File transfer
The file transfer is performed in the "Program" operating area. When you press the
"REMOTE FOLDER" soft key, the contents of the selected folder are displayed.
The transfer can be performed using the vertical soft keys.
Place the cursor on the icon. Right-click the icon to open a menu and select the
"Config HMI-specific shared folders..." dialog.
The procedure is the same as in Section: Installing and configuring RCS Viewer
PCU 20.
Precondition
As different protection levels are assigned to machine data per default, the set
access authorization for the editing of machine data must be sufficiently high.
Depending on the authorization level, it will be possible to edit data such as cycles
and machine data.
Procedure
A soft key menu is displayed when you select the ETC key ">" in the Start-up
operating area.
When you select the "NC memory" soft key, the memory overview screen appears,
showing the amount of NC user memory currently available for programs and data.
The "SRAM" and "DRAM" areas have been provided to enable you to examine or
edit those machine data which configure the memory. These areas in turn are
divided into further groups.
The memory-configuring machine data are divided into the following groups:
- Tool management
- Global user data
- Curve tables
- Compensation
- File system / program memory
- Protection zones
Detailed view
Click the area of interest with the cursor and select the "Details" soft key. The
current data for the relevant machine data are then displayed.
The block header contains the number and name of the machine data. The
currently set values are output on the lines below.
You can change the memory setting in the gray field after "New value" or "New
number" to the right of the field containing the actual value.
This new setting is entered temporarily. Your entry is automatically checked for
limits and an appropriate message output in the dialog line if you make a mistake.
The total available memory, taking into account any modified values, is displayed in
the lower half of the screen.
Soft keys "Axis+" and "Axis-" are displayed for axis-specific machine data.
Soft keys "Channel+" and "Channel-" are displayed for channel-specific machine
data.
When you select soft key "Accept", the temporary values of the displayed machine
data are transferred to the NC.
You can exit the detail view by selecting the "Cancel" soft key or the Recall key "^".
Note
Once you have pressed soft key "Accept", the "Cancel" soft key is no longer
operative, i.e. any changes you have made cannot be undone.
Data backup
When you change the allocation of a memory, alarm 4400 "Machine data alteration
will cause reorganization of buffered memory (data loss)" appears.
Since data are not backed up automatically, to avoid data loss you must back up
the data yourself by way of an NCK Reset before you transfer the MD change.
By selecting the horizontal soft keys, you can view or edit the machine data
memory values of other subgroups.
Operating instructions: See Section "Static user memory (SRAM), Detail view"
Filter:
H01 ShopMill
H02 ShopTurn
H03 ManualTurn
H04 Access levels
H05 Standard machine
Description
The installation operation of the HMI Embedded software (see Chapter 7) transfers
the following data from the Update directory on your PC/PG to the PCU:
- Configuration settings,
- Texts,
- The configured user interface,
- The user software
The ways in which the alarm text files can be adapted beforehand are described
here.
Preconditions
RS 232C (V.24) cable between the COM1 interface of the PCU 20 and the COM1
or COM2 interface of your PC.
The following description assumes that you have already transferred the software
from the HMI Embedded software as described in Chapter 7.
Files
Depending on the selected language, one of the following letters stands for
<LANGUAGE DIRECTORY>:
D for German
G for English
F for French
E for Spanish
I for Italian
The alarm file names start with a and end in the extension .txt:
ALZU.TXT Cycle texts
ALUC.TXT Cycle alarm and tool management texts
ALC.TXT Compile cycle alarm texts
ALPU.TXT PLC alarm/message texts
ALSI.TXT Alarm texts for Safety Integrated
Editor
For editing you can use the DOS editor "edit" (OEM code page) or under Windows
"Notepad" or "Wordpad" (ANSI code page, see Table 6.5). The standard texts
contained in the text files can be overwritten by user-specific texts. An ASCII editor,
e.g. DOS editor, must be used for this purpose. New entries can be added to alarm
text files.
The installation allows you to choose any combination of two of these languages
as the foreground and background language.
Master language
The master language is by definition German. It defines the number and order of
the alarm/message texts for the languages selected by the user.
The number and sequence of the alarm/message texts of the chosen languages
and the master language must match.
Note
For the user up to 256 Kbytes are available (e.g. for additional text files, images,
PLC user alarms).
Alarm numbers
The following alarm numbers are available for the cycle, compile cycle and PLC
alarms:
Table 6-1 Alarm numbers for cycle, compile cycle, and PLC alarms
Number range Description Effect Deletion Name
The structure of the text file for cycle and compile cycle alarms is as follows:
Table 6-2 Structure of the text file for cycle alarm texts
Alarm number Display Help ID Text or alarm number
60100 1 0 "No D number %1 is
programmed"
60101 1 0 60100
... ... ... ...
65202 0 1 "Axis %2 in channel %1 is still
moving"
// Alarm text file for cycles in German
Alarm number
List of alarm numbers
Display
This number defines the alarm display type:
0: Display in alarm line
1: Display in a dialog box
Help ID
(in preparation)
Table 6-3 Structure of the text file for PLC alarm texts
Alarm Display Help ID Text Text on HMI
no.
510000 1 0 "Channel %K FDDIS all" Channel 1 FDDIS all
600124 1 0 "Feed disable axis %A" Feed disable axis 1
600224 0 0 600124 Feed disable axis 2
600324 1 0 600224 Feed disable axis 3
Help ID
(in preparation)
Note
The alarm number is transferred from the PLC via basic program module FC 10
(this uses PLC system function SFC 52 to send alarms to the HMI).
Supplementary information is not supported.
However, the alarm number can also be transferred to the HMI by means of PLC
system function SFC 17, SFC 18 (ALARM S, ALARM SQ). The mechanisms are
used, for example, by the PDIAG configuring tool.
The alarm number displayed on the HMI is transferred via SFC parameter EV_ID.
The supplementary information for the alarm number is transferred via SFC
parameter SD.
Indexed alarms
Indexed alarms can be used to display additional comments in the alarm line, e.g.
an explanation for "action =%"
Load, combine and save new text file, supplied with SW 6, and converted old text
file in the Windows Editor.
Replace the TXT file supplied with software version 6 with the created text file in
the corresponding language catalog.
Mixed code pages within a file are not supported.
No conversion is required for Asian languages as the ANSI and OEM code pages
are identical in this case.
OEM code pages are not supported for languages not listed.
7 Software Installation
7
7.1 Software installation on PCU 20 ............................................. IM2/7-124
7.1.1 Installation software............................................................. IM2/7-124
7.1.2 Software replacement with standard configuration ............. IM2/7-126
7.1.3 Software replacement with modified configuration.............. IM2/7-128
7.1.4 Creating an image ............................................................... IM2/7-139
7.1.5 Uploading an image to the PC card .................................... IM2/7-141
7.1.6 Copying image from PC card to PCU.................................. IM2/7-142
If you want to change the configuration of the installed software or install a new
software version, then you must replace the software.
In this case, you can choose whether the replacement software has the standard
configuration or a modified configuration.
Software on CD
The complete HMI Embedded software package is supplied on one CD:
A folder named e.g. "sw_6_x" containing the following is stored on the CD:
• Documentation:
Upgrade instructions in English "siemene.txt" and German "siemend.txt".
• pcu20 8 MB:
Creates an 8 MB flash image for the update of a PCU 20 / 8 MB.
Two languages are available, as standard, these are German and English.
• pcu20 16 MB:
Creates a 16 MB flash image for the update of a PCU 20 / 16 MB.
Up to six languages are available, as standard, these are: English, German,
French, Italian, Spanish and simplified Chinese.
• tools:
In this directory, you can store your own screens, e.g. in the folder:
"oem_bmp"/"wizard", and the Network Manager in the folder "net server".
Additional languages
A separate language add-on CD is available which allows you to both install
additional languages and to replace the existing standard languages.
Precondition
The software can run on a PC or PG under the following operating systems:
• Windows NT (version 4.0 and later)
• Windows 2000
• Windows XP
To store the data on the installation CD and create a flash image for the PC card,
there must be at least 30 to 40 MB of free memory available on the PC or PG (a
great deal more memory is required for logographic languages such as Korean,
Chinese etc.!).
2. Creating an image
In the first screen you can choose between English and German as the language
for the installation preparation menus.
Select your chosen language and click "OK".
The next screen will display a default installation path and name for the software
package, e.g. "D:\HMI_0_2".
The installation path (standard path or selected path) is then displayed and you
can preset it by clicking the "Accept" button.
If you want to replace your selected path with the standard path, click the "Restore
original status" button. You are prompted as to whether you want to restore the
original status (click "OK"), or whether the current status should be retained (click
"Cancel").
You return to this screen (see Fig.: Installation directory), in which the installation
path is displayed. When you click "Accept", the next screen for the procedure is
displayed.
If you click "OK", the installation will continue and the files will be overwritten.
The current status of the installation preparation process is displayed in the next
screen.
Data compilation
Once the preparation is complete, you have the following two options:
1. Install the software at a later time:
Click the "Finish" button to end the installation preparation phase.
All data have now been downloaded from the data medium (CD) to your local
hard disk which means that you do not need the CD to continue the
installation.
To resume the installation at a later time, simply go to the directory that you
specified during the preparation phase and start the "Setup.Exe"
routine again.
Confirm these settings with "OK". The data compilation process then commences.
The installation path (standard path or selected path) is then displayed and you
can preset it by clicking the "Accept" button.
If you want to replace your selected path with the standard path, click the "Restore
original status" button. You are prompted as to whether you want to restore the
original status (click "OK"), or whether the current status should be retained (click
"Cancel").
You return to this screen (see Fig.: Installation directory), in which the installation
path is displayed. To continue the installation, click "OK".
If the software is already installed, a prompt will be displayed confirming that the
directory already exists and that existing files will be deleted.
If you click the "Cancel" button, you will return to the previous screen.
If you click "OK", the installation will continue and the files will be overwritten.
The current status of the installation preparation process is displayed in the next
screen.
Data compilation
Once the preparation is complete, you have the following two options:
1. Install the software at a later time:
Click the "Finish" button to end the installation preparation phase.
All data have now been downloaded from the data medium (CD) to your local
hard disk which means that you do not need the CD to continue the
installation.
To resume the installation at a later time, simply go to the directory that you
specified during the preparation phase and start the "Setup.Exe"
routine again.
You can view, edit or add to the user settings listed below. Furthermore, you can
also install your own or manufacturer-specific files.
• Language setting
• Modified configuration files
• Your own files
• Boot screen
• Supported displays
If you click the "Change selection" button, you will be able to view further areas and
files in which you can make your own settings.
Clicking "OK" will confirm these settings and initiate data compilation.
Note
Some buttons are displayed in all screens and have the following function:
• "Back" takes you back to the previous screen.
• "Cancel program" allows you to close and exit the program after a
confirmation prompt.
• "Help" displays a dialog box containing a help text.
• "Restore defaults" is activated only if you have entered your own settings.
When you select this button, the defaults defined by Siemens AG are
restored again.
When this button is clicked, a prompt appears asking you to confirm
restoration of the default settings with "OK" or allowing you to retain your own
settings with "Cancel". The button is deactivated again once the original
status has been restored.
• "Reject" enables you to cancel the last setting entered.
• "Accept" confirms the settings you have made and returns you to the
"Selected configuration" screen.
Language selection
You are in the "Selected configuration" screen.
If you select the "Change selection" button in the language selection line, you will
open the "Select language" screen.
German, English, French, Italian, Spanish and simplified Chinese are available for
the PCU 20. All available languages are displayed in a table.
The following selections can be made in the checkboxes in front of the languages:
• 1st and 2nd language, or
• "No 2nd language", and
• "Additional"
Place the CD in the CD drive of the PC or PG and click the "Add new languages"
button.
If languages are already installed, the message "Overwrite language" will appear.
If you have loaded a new language to the installation directory, you will return to
the "Select language" screen. This will now show the new language for you to
select.
Reset selection:
If you have selected a directory and want to remove it, click the "Reject" button.
The Explorer is then closed. You can click the "Back" button to return to the "Select
language" screen.
Clicking the "Change" button starts the editor in which you can view, modify or add
to the values and settings in the opened files. Clicking "Change" in the last two
lines opens screens displaying further subcategories of files.
If you want to link a file of your own into the installation environment, click the
"Replace" button. The Explorer will then open and you can select this file, e.g. one
containing data specific to your own requirements.
MPI configuration
The information needed to set up the links between the PCU and NCU/PLC units
and to define their properties is stored in the NETNAMES.INI configuration file.
For example, you want to link a PCU to two NCs. You use the channel switchover
key and the channel menu to switch from one NC to the other. The softkey
assignments must be configured in file NETNAMES.INI.
Click the "Change" button after "MPI configuration" in the "Data manipulation"
screen. The NETNAMES.INI file opens. You can view the settings and modify or
add to them if required.
Click the "Replace" button if you want to install your own file.
The Explorer then opens. Select the appropriate file and click the "Select" button.
This is then accessed as the installation file.
Note
You cannot change the display machine data available for PCU 20 in the NC in
the BD.TEA file! You can only alter the default settings for these machine data.
Any changes are activated only if the display machine data does not exist in the
NC.
If you possess the required access authorization, you can also change the default
settings in the "Start-up" operating area while the system is operating.
References: /BEM/Operator's Guide HMI Embedded, Chapter: Start-up
Note
Any default settings for display machine data altered in this menu cannot,
however, be changed after the software has been installed!
Select "Replace" to link a file containing user-defined display machine data into the
installation environment. Choose the relevant file in the Explorer view and confirm
by clicking "Select".
Hardkey configuration
If you click the "Change" button in the "Hardkey configuration" line, the following
selections will appear:
These hardkey configuration files (.ini files) are displayed for selection per default.
The configuration file contains the following files.
machine.ini
paramet.ini
program.ini
services.ini
diagnosis.ini
startup.ini
Configuration file:
The ini. files for hardkeys are assigned in configuration file KEYS.INI. Without this
entry, the ini files will not be detected.
If you want to change the names and settings of files contained in the configuration
file, click the "Change" button.
The editor is then started and the KEYS.INI file opens. You can change, add or
delete hardkey names in this file.
Save your change and close the editor.
You will return again to the overview where the current hardkey files are displayed.
If you want to link your own KEYS.INI file into the software environment, click the
"Replace" button. Choose the relevant file in the Explorer view and confirm by
clicking "Select".
.ini files
The individual hardkeys/softkeys are configured in the .ini files.
If the .ini files do not yet contain any settings, click the "Create" button. A file
containing only header data will be opened; you can enter your configuration
settings here.
If you have your own ini files, you can link them into the installation environment by
clicking "Replace", choosing the relevant file and confirming with "Select".
If an ini file has already been set up, the "Create" button is replaced by the
"Change" button which you can use to open the file.
Confirm the file settings by clicking the "Accept" button.
Caution
If you click the "Reject" button in the "Change hardkey configuration" screen, all
settings made in the .ini files and the configuration file are discarded and you then
return to the "Data manipulation" screen.
Language:
You can select the language for the files to be changed in this box.
The box contains every installed language.
Now click the "Browse…" button. The "INSTUTIL" directory is opened and you can
select the appropriate files (see below). Confirm your selection with the "Select"
button.
! Important
An error message will appear if you attempt to add files with names that do not
comply with the DOS convention (max. 8 characters for name and 3 characters
for file extension).
All files you select are displayed with their size and date. At the same time, a
"Delete" button is displayed after every file so that you have the option of removing
it again after a confirmation prompt.
Supported displays
The following operator panels with the appropriate resolution are available for
selection:
OP 010 (640 x 480)
OP 012 (800 x 600)
OP 015 (1024 x 768)
Select the appropriate operator panel.
You can monitor the progress of this task in the "Data preparation" screen.
To stop the preparation run and return to the "Selected configuration" screen, click
the "Interrupt" button.
When the data compilation is completed, you are prompted to specify the
installation type and the storage path for the flash image.
The following screen appears for the PCU 20:
In the input box enter the storage path on your PC for the flash image or
open the Explorer by clicking the "Browse .." button and select the path in the
Explorer view.
Finally, click the "OK" button to start the flash image creation process itself.
Once the data have been installed, the following messages appear:
On the PCU 20 with 8 MB flash:
"The flash card image for PCU 20 has been successfully created.
It is in F:\0605440a\flash
Please use SINUCOPY to transfer this image to a Flash Memory card or copy this
onto a Compact Flash card".
If you click the "Back" button, you will return to the previous screen. You can close
the installation program by clicking "Exit program".
Card selection
The following memory cards are available:
• For a PCU 20 with 8 MB internal flash:
Linear Flash memory card (8 MB)
Compact Flash card (as of 16 MB) with adapter
Preconditions
• If you want to copy the image to a Linear Flash Memory Card, the
"SINUCOPY_FFS" software must be installed on your PC.
• If you use a Compact Flash Card, the software is copied and inserted with
the Windows Explorer.
You require the appropriate adapter for the Compact Flash card.
The "SINUCOPY_FFS" software is no longer required.
Procedure
With a Linear Flash Memory Card:
1. Insert the PC card in the card drive on the PC or PG.
2. Start the SINUCOPY-FFS program.
3. Select: "Save system from hard disk to PC card".
4. Select the path and the ABB.file on the PC.
5. Start the upload.
Software on PC card
Precondition:
• PC card with new image.
• The controller is switched off.
Procedure:
1. Before switching on the PCU, insert the PC card into the PCMCIA memory
card slot of the PCU.
Important
If the network settings were made on another PCU, network access is disabled. A
network address must not be assigned more than once.
Note
If you insert the wrong card in the PCU by mistake, e.g. NC card or an empty
card, the following message appears:
"No PCU system software on PC card".
The transfer operation begins and its progress is displayed on the PCU.
Precondition
• The Network Manager is installed.
• Compact Flash Memory Card inserted in the PCU.
• The connection to the internal drive, the PCMCIA memory card interface, is
already set up.
See Section: Connections, logical drives
Procedure
1. Insert the PC card with the new HMI Embedded software version in the
PCMCIA memory card slot of the PCU.
2. In the "Program" or "Services" operating area, select the ETC key or the
"Additional..." softkey to get to the second vertical bar.
3. When you press the "Compact Flash Card" softkey, the Explorer with the
files of the external drive appears on the screen.
8 Data Backup
8
8.1 Data backup............................................................................ IM2/8-146
8.1.1 General ................................................................................ IM2/8-146
8.5 Data backup for HMI Embedded WIN32 with PCU 50/70 ...... IM2/8-160
NCK/PLC/HMI
The entire data backup with the SINUMERIK 840D is divided into
1. Data backup for NCK, drive and operator panel front settings
2. Data backup for PLC
Series start-up
The following methods can be used to back up data, each serving a different
purpose.
1. Series start-up
In order to be able to transfer as simply as possible a particular configuration to
further controls of the same software version that are e.g. operated on the same
machine type, you can create what are called series start-up files. This type of
file cannot be modified externally using an ASCII editor.
Series start-up files contain all relevant settings (except for compensation data).
Series start-up files must be created for NCK, PLC,
PCU 20 for HMI Embedded, and
PCU 50/70 for HMI Embedded Win32.
3. Software upgrade
4. Area-specific archiving
PLC and HMI Embedded data are not subdivided any further.
Required accessories
You will require the following accessories in order to save data:
• PCIN data transmission program for PG/PC
• RS232C (V24) cable 6FX2002–1AA01–0BF0
• The unit defines the channel, the axis or the TOA area. No unit has to be
specified if the entire area is selected.
• The type determines the data type. During a data backup, the file names are
created and output automatically.
Areas
NC General NC-specific data
CH Channel-specific data (unit corresponds to the channel
number)
AX Axis-specific data (unit corresponds to the number of the
machine axis)
TO Tool data
COMPLETE All data of an area
INITIAL Data for all areas (_N_INITIAL_INI)
Types
TEA Machine data
SEA Setting data
OPT Option data
TOA Tool data
UFR User input frames: Settable Work offset, rotations, etc.
EEC Measuring system error compensation
CEC Sag/angularity compensation
QEC Quadrant error compensation
PRO Protection zone
RPA R parameters
GUD Global user data
INI General initialization program (all data in the active file system)
Via RS-232
Data can be backed up in the following way via the RS232C (V.24) interface:
• Series start-up: With selection option for areas
- NCK (complete)
- PLC (complete)
Data backup
1. Connect the PG/PC to the COM1/COM2 interface of the PCU.
5. On the PCU select "start-up data" (PCU 20 operating area "Services", data
output "Data Out"); after pressing the Enter key, the NCK and PLC areas are
offered.
6. First select NCK ("NCK" is offered as the name of the archive file)
and start the read-out procedure with the softkey "Start". Proceed in the same
way for the "PLC" data record.
b. Area-wide archiving
3. PCU interface configuration (see above, select punched tape format for all data
except for drive data).
4. Start PCIN data transmission program ("Data In") on the PC/PG and enter a file
name.
5. On the PCU 20, select the data area to be output (operating area "Services",
data output "Data out").
6. Press the "Data selection" softkey and select the areas to be read out. The area
"NC active data", for example, contains the following data:
Machine data
- Setting data
- Option data
- Global and local user data
- Tool and magazine data
- Protection zones
- R parameters
- Work offsets
- Drive data
- Compensation data
- Display machine data
- Workpieces, global part programs / subroutines
- Standard and user cycles
- Definitions and macros
When the areas are being output, the internal identifier used in each case
appears in the top line of the display.
7. Start the read-out procedure with the softkey "Start" and answer the prompts
on the operator panel front.
Note
For the PLC, data backup can be executed with the SIMATIC tools HiGraph.
Note filter setting for SDBs!
3. Select the "Services" operating area on the PCU. Continue with steps listed
under "Reading in series start-up" or "Reading in area-specific archive data".
a. Series start-up
4. Select the PCU 20 interface configuration "RS 232-PG/PC" as above,
(punched tape format deselected).
5. Start the PCIN data transmission program on the PG/PC by selecting the
NCK series start-up file to be read into the control under "Data Out" for
transmission.
Select the operating area "Services", "Data In" and start the read-in procedure
with the softkey "Start". Acknowledge the input prompts on the PCU 20.
6. Follow the same procedure for the PLC series start-up file after executing an
NCK reset and a PLC general reset.
7. After another NCK reset, the control powers up with the imported data sets.
Note
The NCK series start-up file must always be imported before the PLC series start-
up file.
b. Area-wide archiving
4. Select the PCU 20 interface configuration "V24-PG/PC" as above and set
"punched tape format" (except for drive data).
- Start the PCIN data transmission program on the PG/PC. Selection
of the archive file to be read into the control under "Data Out" for
transmission.
- On the PCU 20, select area "Services", "Data In" and start
the read-in procedure with the softkey "Start". The file is
automatically detected and loaded accordingly.
6. Load the machine data file and actuate "NCK RESET". If you then receive
messages about a reconfiguration of the memory or restandardization of
machine data, then you must read in the machine data file again and RESET
the control. Usually, this procedure will have to be performed two or three
times.
7. If you want to activate global user data, read out the "N_INITIAL_INI" file
(Table 8-2). Read out starts when you select "All data" as for area-wide
archiving.
9. Read the save "N_INITIAL_INI" file back in to activate the global user data.
11. The PLC area must be loaded last after a PLC general reset.
Note
• When you are loading drive data, deselect the punched tape format as well
as all special functions on the right of the display of interface settings. Do
not actuate softkey "Back up boot file" in the drive data menu until you have
reset the control once after loading the drive archive data.
Transmission errors
If transmission is aborted with an error, check the following:
• The password has been entered for the correct protection level
• The interface parameters (RS-232-C-PG/PC) are correct
• If LEC data are being read in, MD32700 ENC_COMP_ENABLE must be
initially set to 0.
• MD11220 INI_FILE_MODE set to 1 or 2 see:
11210 UPLOAD_MD_CHANGES_ONLY
MD number MD backup of changed MD only
Default setting: 0 Minimum input limit: 0 Maximum input limit: 255
Change effective: Immediately Protection level: 2/4 Unit: –
Data type: BYTE Valid as of SW release: 1 or 4
Meaning: Up to SW 3.x
Bit 0 Scope of the differential upload with TEA files
(area-specific archiving)
0: All data are output
1: Only data which deviate from the standard are output
(not valid for INITIAL_INI)
If a value of a data item, which is stored as an array, is
changed, the complete MD array is output
(e.g. MD 10000: AXCONF_MACHAX_NAME_TAB).
As of SW 4
Bit 1 Scope of the differential upload with INI files
0: All data are output
1: Only data which deviate from the standard are
output
(e.g. INITIAL_INI)
Bit 2 Changes of a field element
0: Complete array is output
1: Only modified elements of an array are output
Bit 3 R parameters (only for INITIAL_INI)
0: All R parameters are output
1: Only R parameters not equal to zero are output
Bit 4 Frames (only for INITIAL_INI)
0: All frames are output
1: Only frames not equal to zero are output
Bit 5 Tool data, cutting edge parameters (only for INITIAL_INI)
0: All tool data are output
1: Only tool data not equal to zero are output
Related to ....
Note
It might be sensible to back up only altered machine data before a software
update if changes have been made to the default machine data settings in the
new software version. This applies particularly to machine data which are
assigned SIEMENS protection level 0.
Note
MD 11210 UPLOAD_MD_CHANGES_ONLY should be set to "1" or the
corresponding bits set to "1". With this setting, the transferred files contain only
those data which deviate from the default. This is of advantage with respect to
future SW upgrades.
Specify file:
HMI Embedded acknowledgment byte to PLC for current status of V.24 (RS-232-C)
interface:
Job processing
A PLC job is processed according to the following scheme:
1. The PLC may initiate a job only if the acknowledgment byte is 0.
3. Once the operation is finished (OK or Error), the PLC must respond again and
delete the job byte. The PLC receives a "job active" signal for an unfinished
job.
N18 _N_CH%d_UFR
N19 _N_COMPLETE_GUD
N20 _N_NC_GUD
N21 _N_NC_GD1
N22 _N_NC_GD2
N23 _N_NC_GD3
N24 _N_NC_GD4
N25 _N_NC_GD5
N26 _N_NC_GD6
N27 _N_NC_GD7
N28 _N_NC_GD8
N29 _N_NC_GD9
N30 _N_CH%d_GUD
N31 _N_CH%d_GD1
N32 _N_CH%d_GD2
N33 _N_CH%d_GD3
N34 _N_CH%d_GD4
N35 _N_CH%d_GD5
N36 _N_CH%d_GD6
N37 _N_CH%d_GD7
N38 _N_CH%d_GD8
N39 _N_CH%d_GD9
N40 _N_TO%d_INI
N41 _N_TO%d_TOA
N42 _N_TO%d_TMA
N43 _N_NC_CEC
N44 _N_AX%d_QEC
N45 _N_AX%d_EEC
In the case of files with identifier "%d", the channel, axis or tool area number is
specified via the PLC (DB19, DBB14).
The standard list cannot be edited.
• Axis and channel numbers can be specified via the PLC (DB19, DBB14).
• Another index (0, 1 - 255) for defining text (file name) can be specified as a line
offset within this file. HMI Embedded uses this information to identify the name
of the transfer file or job list to be started.
• HMI Embedded signals to the PLC: Reading out control file DB19.DBB24,6 = 1
If index 0 is specified, all files listed in the control file will be output.
The line numbers (N1 to N255) must be generated starting at 1 and incremented
by 1 for each line.
Machine manufacturer
See machine manufacturer's specifications.
ISO programs can be read in and out of HMI Embedded in punched tape format.
The punched tape format for ISO programs (ISO punched tape format) is not the
same as Siemens HMI Embedded punched tape format.
The new ISO format settings are activated in display machine data
"MM_ISO_ACTIVE" (9390) ("MM_ISO_ACTIVE" = 1).
Memory cards
The following commercially available SANDISK cards are recommended:
SDP3B- 32-101
SDP3B-128-101
Cards available from Siemens:
- STRATA PC CARD with the card driver SINUCOPY FFS or
SinuCom FFS
- Compact Flash Card with adapter
Procedure:
• Insert the card in the deactivated PCU 20.
! Important
If the network settings were made on another PCU, network access is disabled. A
network address must not be assigned more than once.
8.5 Data backup for HMI Embedded WIN32 with PCU 50/70
Data backup including hard disk backup is described in:
9
9 Diagnostics
Note
The precondition for the Action Log function is that the "Start-up" operating area
is installed.
9012 ACTION_LOG_MODE
MD number Action log settings
Default: 255 Min. input value: 0 Max. input value: 0xffff
Changes effective after POWER ON Protection level (R/W) 2/2 Unit: -
Data type: DWORD
Meaning This MD can be used to enable/disable the action log and to
define a choice of the data to be logged.
If the action log is enabled, the files that can be logged are logged by default. The
following events can be logged:
Alarm status
All displayed NC/PLC and HMI Embedded alarms and messages can be logged.
Key actuation
All operator panel front and MF2 key actuations can be logged.
Window ID
The identification number of a screen is logged when it is opened or closed.
File structure
The log file is divided into 4 columns:
• Date
• Time
• NCU name
• Event
For older software versions, you can find an assignment of the window IDs to the
window names in the "Documentation \ Window Lists" directory on the software
CD.
For each software version, there is an assignment file which contains the version
ID in the file name (e.g. 060507.txt for the software version P06.05.07).
You can see which software version is installed on the PCU at the start of the log
file.
The current log file is displayed on the screen of the operator panel front in the
"Diagnostics" operating area in the "Service Displays" -> Action Log menu in the
"Action Log File" screen.
If a crash file exists, the softkey "Crash Data" is also displayed, with which the
crash file can be displayed.
The vertical softkey "Data Out -> RS-232-C (V.24)" can be used to output and
archive the log file.
If the bit is already set when HMI Embedded is booted, HMI Embedded does not
respond to the value of the bit (only after it has been reset and set again).
• The log file _AC_LOGP.TXT is read out either during the boot process or can
be read out in the Diagnosis operating area until the system is next switched
off. The file is then deleted.
• If you acknowledge this question with "Yes", the log will be read out via RS
232 C (V.24).
Note
A latency must be observed between two signals to make sure that the second
signal can be processed.
You can display the version data of the following areas via the horizontal softkeys:
• Version data of the NCU
• Version data of the HMI
• Version data of the cycles (user, manufacturer, standard cycles)
10.9 List of files for the dialog screen files ................................ IM2/10-179
Introduction
With software version 4.4 and higher, you can configure your own dialog windows
(dialog screens) and display them on HMI Embedded.
The appearance of the dialog windows is configured purely by text (COM file in the
cycles directory). The dialog window is opened and closed by function calls from
the parts program.
User-configured dialog windows do not modify the HMI system software (operator
interface).
You cannot call user-defined dialog windows simultaneously in different channels,
i.e. you can only use the MMC command with a 1:1 link.
The "Configure Windows in the NC Program" function is also referred to as the
"command channel".
Application
One possible application of user dialog windows is, for example, to selectively
assign current values to particular user variables (GUD) prior to a parts program
run.
Operating area
Name of softkey with which the configured user dialogs can be called. Default
entry: "CYCLES", appears as "Cycles" on softkey 7 (with Win32: Softkey 14) and
can be reached via the "ETC" key.
Command
Picture_on select screen
Picture_off deselect screen
Com file
Name of the dialog box file (max. 8 characters, in the user cycles or standard
cycles directory CST.DIR). The dialog screen design is defined here. The dialog
screen is used to display user variables and/or comment texts.
Graphics file
File name of a BMP graphic to be inserted.
See Operator Interface book, BE1: Chapter, Screen elements, pictures
Text variables
Screen header or comment text from a text variable in the COM file.
Acknowledgment mode
"S" Synchronous, acknowledgment via "OK" softkey
O perating area
Com m and Picture on/off
Com file nam e*) in the
cycle directory
*) On the MMC103 / PCU 50, the file is named T_SK_GR.COM for example, but is
called here without language identifier "GR".
%_N_UGUD_DEF
;$PATH=/_N_DEF_DIR
DEF CHAN REAL TEST_1
Reference para-
meter for MMC
command
Data type
Name of the user variable
//C3(Bild3)
R/ 15 75 5/ COMMENT;%1,%2,%3/ W,RJ TEST_1/ ...)
Variable type
Real Integer String
User variable
Input limits:
min. 15, max. 75
(not HMI Embedded)
Default value
for user VAR
Comment text with
optional text variables
Access type:
W = Read/write
R= Read only
W, rj = Read/write with comment
No j: Left-justified to input/output field
j: Right-justified to input/output field
(not HMI Embedded)
Note
For variable names, text variables and cycle names, capital letters must be used.
Text variables
[TEXTVARIABLES ]
A1 =Example2: MMC command without ack.
Reference para-
meter for MMC
command
Text variable
TEXT VARIABLES]
A1 =............Example1: MMC command without acknowledgment………
Sequence
The user variable TEST_1 from GUD4.DEF with header A1 is displayed for a short
time.
Text variable
[TEXT VARIABLES]
The 7th parameter is interpreted as the display time for the mode without
acknowledgment (10 seconds).
The contents of the table are then deleted. The screen form remains on the screen
until Picture_off is selected.
The 8th parameter (T1) is the text variable for the screen header. If there is no
entry, the operating area name (cycles) is displayed.
The parameters 9 to 23 are optional text variables (in this case "G1=optional text
variable").
In this COM file, the optional text variables must be loaded with default values in
the "[Text variables]" section.
Sequence
The comment text from the COM file (USER VAR TEST_1) is expanded in this
example at the position of the first wild card (%1) by the contents of the text
variable "G1optional text variable". By calling the text variables contained in the
MMC command (9th to 23rd parameters), messages or names can be "composed"
in this way.
Text variable
F1 = ...Example3: MMC command with synchronous acknowledgment mode…
OK
Sequence
The user variable Test_1 is displayed until the "OK" softkey is pressed.
The user variable has also been overwritten with the value 5 here.
Without STOPRE, this assignment would be carried out before the keyboard input
(after it with STOPRE!).
(R///Var.Name/R/TEST_3/6000,2800,8000/ 200,3000,7500)
The two parameters each consist of three numerical values; these specify the
position and length of the field. The values are specified in Twips, with 15 Twips
roughly corresponding to one pixel.
The field height is defined as being 250 Twips.
Meaning of values:
(./6000,2800,8000/....)
ANW.VAR TEST_2
1.000000
OK
To ensure that the cursor control works seamlessly, the configured fields must
overlap one another (see below):
1.000000
1.000000
1.000000
1.000000
OK
A comment text for the picture can also be preassigned via the Com file. You can
position this comment text by specifying position parameters.
Note
You can only move the picture itself by repositioning it in the graphics program.
Part program
N10 MMC("CYCLES,PICTURE_ON,T_SK.COM,SCREEN8,GUD4.DEF,
GRA.BMP,,M1","S")
N20 MMC("CYCLES,PICTURE_OFF","N")
N30 M30
Text variable
M1 = ......Example5: Insert picture…..
Pictures are created, e.g. with the drawing tool "Paintbrush".
Picture size: 300X500 pixels, you can only change the picture size in Paintbrush.
OK
(*.COM)
//C3(Screen3)
(S/// USER VAR QUIT_1/W/QUIT_1//)
[TEXT VARIABLES]
K1 = ..Example8: MMC command with asynchronous acknowledgment mode
N1 = ..Example8: Screen2
Text variable
[SCREEN3]
SK1 = END
SK2 = Screen2
Softkey 8
Softkey 9
Example 8: MMC command with asynchronous acknowledgement mode
Softkey 10
ANW.VAR TEST_1 START
Softkey 11
Softkey 12
Softkey 13
Softkey 14
OK Softkey 15
END Screen2
Sequence
The screen called via the asynchronous MMC command continues to be displayed
until one of the two configured softkeys is actuated:
With softkey "END", the user dialog is immediately exited.
With softkey "Screen2", a further screen is then displayed for 10s.
Program
• The acknowledgment variable is defined as a string.
Length of the string: >= 20
(Values < 20 are evaluated internally only, SK0 ... SK15 are entered at position
17...20 on actuation of the softkey).
• The string is assigned a value in the parts program and any old softkey
information is deleted.
Example 8: Screen 2
OK
%_N_MMC_EXAMPLE2_MPF
N10 MMC("CYCLES,PICTURE_ON,T_SK.COM,SCREEN6,GUD4.DEF,,10,
T1,G1","N")
N15 G4 F15
N20 MMC("CYCLES,PICTURE_OFF","N")
N25 M30
%_N_MMC_EXAMPLE3_MPF
N15 MMC("CYCLES,PICTURE_ON,T_SK.COM,SCREEN1,GUD4.DEF,,,F1",
"S")
N20 TEST_1 = 5
N30 MMC("CYCLES,PICTURE_OFF","N")
N40 M30
%_N_MMC_EXAMPLE4_MPF
N15 MMC("CYCLES,PICTURE_ON,T_SK.COM,SCREEN2,GUD4.DEF,,,C1",
"S")
N20 TEST_3 = 5
N30 MMC("CYCLES,PICTURE_OFF","N")
N40 M30
%_N_MMC_EXAMPLE5_MPF
N15 MMC("CYCLES,PICTURE_ON,T_SK.COM,SCREEN8,GUD4.DEF,
GRA.BMP,,M1","S")
N30 MMC("CYCLES,PICTURE_OFF","N")
N40 M30
%_N_MMC_EXAMPLE8_MPF
N10 QUIT_1 = "START"
N20 MMC("CYCLES, PICTURE_ON,T_SK.COM,SCREEN3,GUD4.DEF,,
QUIT_1,K1","A")
N30 LABEL0:
N40 STOPRE
N50 IF MATCH (QUIT_1,"SK1") >= 0 GOTOF LABEL1
N60 IF MATCH (QUIT_1,"SK2") >= 0 GOTOF LABEL2
N70 GOTOB LABEL0
N80 LABEL2:
N90 MMC("CYCLES, PICTURE_ON,T_SK.COM,SCREEN1,GUD4.DEF,,,
N1","N")
N100 G4 F10
N110 LABEL1:
N120 MMC("CYCLES, PICTURE_OFF","N")
N130 M30
11.6 Loading the image from the PC card to the HT 6 ............... IM2/11-202
Introduction
This chapter describes how to install and start up the HT 6.
For further reading on special NCK, MMC, PLC or drive functions, please consult
the Descriptions of Functions/Manuals (see Section: Documentation)
11.1.2 Software
The software used to install the HT 6 software is pre-installed on the HT 6 when it
is shipped.
If you want to change the configuration of the installed software or install a new
software version, then you must replace the software.
In this case, you can choose whether the replacement software has the standard
configuration or a modified configuration.
The five available interface languages are English, German, French, Spanish and
Italian.
Additional languages
A separate language add-on CD is available which allows you to both install
additional languages and to replace the existing standard languages.
Precondition
The software can run on a PC or PG under the following operating systems:
• Windows 98
• Windows Me
• Windows NT (version 4.0 and later)
• Windows 2000
• Windows XP
To store the data of the installation CD and create a flash image (8 MB) for the PC
card, there must be at least 30 to 40 MB of free memory available on the PC or
PG.
If you wish to install pictographic languages such as Korean or Chinese, you will
need significantly more memory.
2. Create an image
11.1.3 Documentation
You will require the following documentation to install and start up the HT 6:
− /BH/ Operator Components Manual, Section: Handheld Terminal HT 6
− /BH/ SINUMERIK 840Di Manual, Section: Handheld Terminal HT 6
− /FB1/ P3/ Description of Functions Basic Machine, Section: HT 6
Signals to Interfaces
− /FB2/ B3/ Description of Functions Extension Functions, Section:
Several Operator Panel Fronts
− /IAC/Installation & Start-Up Guide, Section: Handheld Terminal HT 6
− Lists /LIS/
− Diagnostics Guide /DA/
− Installation & Start-Up Guide, HMI Option Package /IAM/BE1/
− Operator's Guide HT 6 /BAH/
The next screen will display a default installation path and name for the software
package, e.g. "E:\HMI_HT6".
If you want to specify a different path, select the "Change" button and the following
screen will appear:
You can enter the path and name directly in the input field or
open the Explorer by clicking the "Find directory.." button.
Choose the installation path by clicking the "Select" button. The installation path is
then displayed and you can preset it by clicking the "Accept" button.
You then return to the previous screen (see screenshot above) where the
installation path will be displayed.
Click the "OK" button to continue the installation.
If the software is already installed, a prompt will be displayed confirming that the
directory already exists and that existing data will be deleted.
If you click the "Cancel" button, you will return to the previous screen.
If you click "OK", the installation will continue and the files will be overwritten.
The current status of the installation preparation process is displayed in the next
screen.
Once the preparation is complete, you have the following two options:
1. Install the software at a later time:
Click the "Finished" button to end the preparation phase and continue the
installation at a later point in time. All data have now been downloaded from
the data medium (CD) to your local hard disk which means that you do not
need the CD to continue the installation.
To resume the installation at a later time, simply go to the directory that you
specified during the preparation phase and start the "Setup.Exe"
routine again.
The next screen will display a default installation path and name for the software
package, e.g. "E:\HMI_HT6".
If you want to specify a different path, select the "Change" button and the following
screen will appear:
You can enter the path and name directly in the input field or
open the Explorer by clicking the "Find directory.." button.
If the software is already installed, a prompt will be displayed confirming that the
directory already exists and that existing files will be deleted.
If you click the "Cancel" button, you will return to the previous screen.
If you click "OK", the installation will continue and the files will be overwritten.
The current status of the installation preparation process is displayed in the next
screen.
Once the preparation is complete, you have the following two options:
1. Install the software at a later time:
Click the "Finish" button to end the installation preparation phase.
All data have now been downloaded from the data medium (CD) to your local
hard disk which means that you do not need the CD to continue the
installation.
To resume the installation at a later time, simply go to the directory that you
specified during the preparation phase and start the "Setup.Exe"
routine again.
Selected configuration
The "Configuration selected" screen displays an overview of the current user
settings.
You can view, edit or add to the user settings listed below. Furthermore, you can
also install your own or manufacturer-specific files.
• Language setting
• Modified configuration files
• Your own files
• Boot screen (HT 6 does not have a boot screen)
• Supported displays
If you click the "Change selection" button, you will be able to view further areas and
files in which you can make your own settings.
Clicking "OK" will confirm these settings and initiate data compilation.
Note
Some buttons are displayed in all screens and have the following function:
• "Back" takes you back to the previous screen.
• "Cancel program" allows you to close and exit the program after a
confirmation prompt.
• "Help" displays a dialog box containing a help text.
• "Restore defaults" is activated only if you have entered your own settings.
When you select this button, the defaults defined by Siemens AG are
restored again.
When this button is clicked, a prompt appears asking you to confirm
restoration of the default settings with "OK" or allowing you to retain your own
settings with "Cancel". The button is deactivated again once the defaults
have been restored.
• "Reject" enables you to cancel the last setting entered.
• "Accept" confirms the settings you have made and returns you to the
"Selected configuration" screen.
Select language
You are in the "Selected configuration" screen.
If you select the "Change selection" button in the language selection line, you will
open the "Select language" screen.
A table of available languages is displayed: You can make your selections for the
1st and 2nd languages, or choose "No 2nd language", by activating the
corresponding checkboxes.
Place the CD in the CD drive of the PC or PG and click the "Add new languages"
button.
If languages are already installed, the message "Overwrite language" will appear.
If you have loaded a new language to the installation directory, you will return to
the "Select language" screen. This will now show the new language for you to
select.
Reset selection:
If you have selected a directory and want to remove it, click the "Reject" button.
The Explorer is then closed. You can click the "Back" button to return to the "Select
language" screen.
Clicking the "Change" button starts the editor in which you can view, modify or add
to the values and settings in the opened files. Clicking "Change" in the last two
lines opens screens displaying further subcategories of files.
If you want to link a file of your own into the installation environment, click the
"Replace" button. The Explorer will then open and you can select this file, e.g. one
containing data specific to your own requirements.
MPI configuration
The information needed to set up the links between the HT 6 and NCU/PLC units
and to define their properties is stored in the NETNAMES.INI configuration file.
For example, you want to link an HT 6 to two NCs. You use the channel switchover
key and the channel menu to switch from one NC to the other. The softkey
assignments must be configured in file NETNAMES.INI.
Click the "Change" button after "MPI configuration" in the "Adapt configuration files"
screen. The NETNAMES.INI file opens. You can view the settings and modify or
add to them if required.
Click the "Replace" button if you want to install your own file. The Explorer then
opens. Select the appropriate file and click the "Select" button.
This is then accessed as the installation file.
Note
You cannot change the display machine data for HT 6 in file BD.TEA! You can
only alter the default settings for these machine data.
Any changes are activated only if the display machine data does not exist in the
NC.
If you possess the required access authorization, you can also change the default
settings in the "Start-up" operating area while the system is operating.
References: /BAH/HT 6 Operator's Guide, Section: Start-up
Note
Any default settings for display machine data altered in this menu cannot,
however, be changed after the software has been installed!
Select "Replace" to link a file containing user-defined display machine data into the
installation environment. Choose the relevant file in the Explorer view and confirm
by clicking "Select".
Hardkey configuration
If you click the "Change" button in the "Hardkey configuration" line, the following
selections will appear:
These hardkey configuration files (.ini files) are displayed for selection per default.
The configuration file contains the following files.
machine.ini
paramet.ini
program.ini
services.ini
diagnosis.ini
startup.ini
Configuration file:
The .ini files for hardkeys are assigned in configuration file KEYS.INI. Without this
entry, the ini files will not be detected.
If you want to change the names and settings of files contained in the configuration
file, click the "Change" button.
The editor is then started and the KEYS.INI file opens. You can change, add or
delete hardkey names in this file.
Save your change and close the editor.
You will return again to the overview where the current hardkey files are displayed.
If you want to link your own KEYS.INI file into the software environment, click the
"Replace" button. Choose the relevant file in the Explorer view and confirm by
clicking "Select".
.ini files
The individual hardkeys/softkeys are configured in the .ini files.
If the .ini files do not yet contain any settings, click the "Create" button. A file
containing only header data will be opened; you can enter your configuration
settings here.
If you have your own ini files, you can link them into the installation environment by
clicking "Replace", choosing the relevant file and confirming with "Select".
If an ini file has already been set up, the "Create" button is replaced by the
"Change" button which you can use to open the file.
Confirm the file settings by clicking the "Accept" button.
Caution
If you click the "Reject" button in the "Change the hardkey configuration" screen,
all settings made in the .ini files and the configuration file are discarded and you
then return to the "Adapt configuration files" screen.
If you click the "Change" button in the "Alarm and user texts" line, a screen
displaying different categories of user text will appear:
Language:
You can select the language for the files to be changed in this box.
The box contains every installed language.
The file is selected on the basis of a file type filter. You can enter the file type
directly in the first input box or
use the arrow to open the drop-down list of the following file types:
After you have selected a file type, click the "Browse" button. Choose the
corresponding file in the Explorer view and confirm by clicking "Select".
! Important
An error message will appear if you attempt to add files with names that do not
comply with the DOS convention (max. 8 characters for name and 3 characters
for file extension).
All files you select are displayed with their size and date. At the same time, a
"Delete" button is displayed after every file so that you have the option of removing
it again after a confirmation prompt.
Boot screen
A boot screen cannot be selected for the HT 6.
Supported displays
The only resolution available for the HT 6 is 320 x 240; no alternative resolutions
can be selected.
Once the data have been compiled, the following screen appears:
In the input box, enter the storage path on your PC for the flash image or
open the Explorer by clicking the "Find directory.." button and select the path in the
Explorer view.
Finally, click the "OK" button to start the flash image creation process itself.
Once the data have been installed, the following message appears:
If you click the "Back" button, you will return to the previous screen. You can close
the installation program by clicking "Finish program".
Procedure
With a Linear Flash memory card:
1. Insert the PC card in the card drive on the PC or PG.
2. Press the Reset key on the HT 6 and wait for the software version and
serial number to appear.
Note
With software version 6.4 or later, an error message will appear if you select
"0:Update from PC card" and have inserted by mistake the wrong card, e.g. the
NC card, or an empty card, in the HT 6.
Editor
You should use the editor (Notepad) called by the installation software to make any
changes to files.
If you use a different editor to edit text files, make sure that you store them in ASCII
format afterwards.
Example:
File with OEM name specifications for channel-areas and channels.
//* text definitions for softkeys in channel switch menu *///* name of channel area 1
and names of channels of channel area 1 */
T_CHAN_AREA_1 "Milling1"
T_CHAN_AREA_1_CHANNEL_1 "Channel11"
T_CHAN_AREA_1_CHANNEL_2 "Channel12"
T_CHAN_AREA_1_CHANNEL_3 "Channel13"
T_CHAN_AREA_1_CHANNEL_4 "Channel14"
T_CHAN_AREA_1_CHANNEL_5 "Channel15"
T_CHAN_AREA_1_CHANNEL_6 ""
T_CHAN_AREA_1_CHANNEL_7 ""
T_CHAN_AREA_1_CHANNEL_8 ""
The OEM user can enter texts by inserting them in the blank character strings (see
above)!
Six characters are possible per softkey bar; the carriage return is created with
characters "%n": e.g. "NC3%nChann1".
Table 11-2 Structure of the text file for cycle alarm texts
Alarm number Display Help ID Text or alarm number
60100 1 0 "No D number %1 is
programmed"
60101 1 0 60100
... ... ... ...
65202 0 1 "Axis %2 in channel %1 is still
moving"
// Alarm text file for cycles in German
Alarm number
List of alarm numbers
Display
This number defines the alarm display type:
0: Display in alarm line
1: Display in a dialog box
Help ID
(in preparation)
Table 11-3 Structure of the text file for PLC alarm texts
Alarm Display Help ID Text Text on HT 6
no.
510000 1 0 "Channel %K FDDIS all" Channel 1 FDDIS all
600124 1 0 "Feed disable axis %A" Feed disable axis 1
600224 1 0 600124 Feed disable axis 2
600324 1 0 600224 Feed disable axis 3
703210 1 1 "User text" User Text
...
703211 1 1 "User text%A ..." User Text
Axis 1 ...
// Alarm text file for PLC alarm
Display
This number defines the alarm display type:
0: Display in alarm line
1: Display in a dialog box
Help ID
(in preparation)
Note
The alarm number is transferred from the PLC via basic program module FC 10
(this uses PLC system function SFC 52 to send alarms to the HMI).
Supplementary information is not supported. However, the alarm number can
also be transferred to the HMI by means of PLC system function SFC 17, SFC 18
(ALARM S, ALARM SQ). The mechanisms are used, for example, by the PDIAG
configuring tool. The alarm number displayed on the HMI is transferred via SFC
parameter EV_ID. The supplementary information for the alarm number is
transferred via SFC parameter SD.
Indexed alarms
Indexed alarms can be used to display additional comments in the alarm line, e.g.
an explanation for "action =%"
Example:
You want to assign the text "SampleText" to alarm number 700007
(DB2.DBX180.7).
Procedure:
1. a. Set up an RS-232-C link between the HT 6 and your PC,
b. Boot the HT 6 and PC,
c. In the "Services" operating area on the HT 6, select menu "Data Out",
menu "Texts" [in our case "Language 1" (German),
d. In the working window which then opens, select a menu line
[in our case "PLC alarm texts (user)"],
e. Start a data transfer program (e.g. PCIN) on the PC, at the same
time specifying the storage path and name for the file to be edited,
(e.g. "Alarm1.txt")
f. Activate the "Start" softkey in the HT 6 working window.
The alarm text file is then transferred to the PC where it is saved under the name
you selected.
2. a. Edit the file on the PC. Each line contains an alarm text number
with associated explanatory text.
b. Generate a new line at the end of the file by pressing the <RETURN>
key,
c. Type in a new entry: 700007 0 0 "SampleText",
d. Save and close the file.
3. a. Activate the data transfer from the PC (see 1.e) with "Send Data",
b. As for 1.c, but select menu "Data In",
c. In the working window which then opens, keeping the default
settings, start the data transfer to the HT 6 by selecting softkeys
"Start" and "OK".
The HT 6 boots automatically when the data have been transferred. The modified
alarm text file is then operative.
On 1:1 systems, switchover is not performed via the channel menu, but with the
softkey "channel".
Note
The NETNAMES.INI file cannot be loaded via the RS-232-C interface!
Using the user interface, you can establish a connection between the HT 6 unit and
the connected NCU/PLC units in each operating area.
Note
The softkeys only offer the connections that are really assigned and whose
channels are active in the respective NC.
In the case of "m:n systems" all PLC communications tasks are mapped onto
single variable accesses to keep the PLC resources required to a minimum.
Note
The NC writes the channel number of the HT 6 in DB19, DBB22 or DB19, DBB72
(2nd interface).
The names in the file NETNAMES.INI are limited to five characters.
Example:
NETNAMES.INI
[own]
owner = HT6_1
mmc_bustyp = OPI
mmc_address = 14
mstt_address = 14
name = HT6
start_mode = OFFLINE
[param NCU_1]
type = NCU_573
nck_address = 12
plc_address = 12
name = NCU1
[param NCU_2]
type = NCU_573
nck_address = 14
plc_address = 14
name = NCU2
[chan HT6_1]
DEFAULT_logChanSet = Milling1
DEFAULT_logChan = Channel13
ShowChanMenu = TRUE
logChanSetList = Milling1, Milling2
[Milling1]
logChanList = Channel11, Channel12, Channel13, Channel14, Channel15
[Channel11]
logNCName = NCU_1
ChanNum = 1
[Channel12]
logNCName = NCU_1
ChanNum = 2
[Channel13]
logNCName = NCU_1
ChanNum = 3
[Channel14]
logNCName = NCU_1
ChanNum = 4
[Channel14]
logNCName = NCU_1
ChanNum = 5
[Fräsen2]
logChanList = Channel21, Channel22, Channel23
[Channel21]
logNCName = NCU_2
ChanNum = 1
[Channel22]
logNCName = NCU_2
ChanNum = 2
[Channel23]
logNCName = NCU_2
ChanNum = 3
11.9 PLC
The task of the PLC is to control functional sequences specific to the machine. It is
implemented as a software PLC.
This function is accessed via the "Start-up" operating area in the "PLC" screen by
activating the softkey "Date%nTime".
If any changes are made to the time and date, the time and date of the HT 6 are
transferred to the PLC.
You can check the synchronization in the "Current time:" output field.
Cyclical synchronization of the time:
• The time duration with active "autom. ON" is specified in the field
"Synchronization time".
• "Sync. manual" synchronizes the PLC and HT 6 immediately.
Note
Changes can only be made to the PLC operands with the appropriate password.
Note
If you operate the HT 6 via the MPI card of the PC, the system time of the PC is
altered when the two devices are synchronized.
11.10 Diagnostics
11.10.1 Action log
Function
The Action log function can be used to log operating sequences.
The following functions are provided:
• Logging of alarms
• Logging of key actuation
• Output of log file via RS 232 C (V.24)
Note
The precondition for the Action Log function is that the "Start-up" operating area
is installed.
9012 ACTION_LOG_MODE
MD number Action log settings
Default: 255 Min. input value: 0 Max. input value: 0xffff
Changes effective after POWER ON Protection level (R/W) 2/2 Unit: -
Data type: DWORD Applies as of SW 5.2
Meaning This MD can be used to enable/disable the action log and to
define a choice of the data to be logged.
Bit 0 =1 Action log ON (default)
=0 Action log OFF
If the action log is enabled, the files that can be logged are logged by default. The
following events can be logged:
Alarm status
All displayed NC/PLC and HT 6 alarms and messages can be logged.
Key actuation
All operator panel front and MF2 key actuations can be logged.
Window ID
The identification number of a screen is logged when it is opened or closed.
Log file
The log file is output in English.
The log file is divided into four columns:
File structure
• Date
• Time
• NCU name
• Event
On the HT 6 the log file is not flashed, i.e. after every power off/on or reset the old
contents are erased.
The current log file is displayed on the screen of the operator panel front in the
"Diagnostics" operating area when you select softkey "Service Displays" -> "Action
log" in the "Action log log file" screen.
If a crash file exists, the softkey "Crash Data" is also displayed, with which the
crash file can be displayed.
The screen "Action log settings" is displayed in the screen "HMI" -> "Action log" in
the Start-up operating area.
The selected setting must be confirmed by pressing the softkey "Save Settings".
If the bit is already present when the HT 6 boots, the HMI will not react to the value
of the bit (only after resetting and setting).
• The log file _AC_LOGP.TXT is read out either during the boot process
or can be read out in the Diagnostics operating area within the time
when the MMC is switched off. The file is then deleted.
• Reboot the control system.
• Prompt: "Crash Log found! Read out V24? ([Y]/N)"
• If you acknowledge this question with "Yes", the log will be read out
via RS 232 C (V.24).
Note
A latency must be observed between two signals to make sure that the second
signal can be processed.
Backup option
A complete system data image is downloaded to an external device.
The data are backed up via the RS-232-C interface to an external medium.
Additional information:
XXXXXXXX:XXXXXXXX XXXXXXXX:XXXXXXXX
...
XXXXXXXX:XXXXXXXX
CODE = XX XX XX XX XX XX XX XX XX XX
EIP: XX XX XX XX XX XX XX XX XX XX
STACK= XXXXXXXX XXXXXXXX XXXXXXXX
XXXXXXXX XXXXXXXX XXXXXXXX
XXXXXXXX XXXXXXXX XXXXXXXX
Press ‘1’ to save data or press ‘9’ to
reboot immediately
choose the baud rate and the interface for the serial transmission.
Press key "3" to set the baud rate selected on the external receiving device
(PG/PC).
Set the external receiving device to "Receive" and start.
Start the transmission by pressing key "2".
You can stop the transmission by pressing "1" (in the event of transmission error or
incorrect baud rate)
The following message appears about 2 to 5 seconds after you press key "1":
Once all the data have been transferred successfully, the following message
appears:
Transmission finished
XXXXXX bytes saved.
Note
When you use the serial link, the number of transmitted bytes is also displayed
and must match the number of bytes received. If the two numbers are not the
same, abort the transmission by pressing key "1", select a lower baud rate and
start the upload again.
Restart
The exception handler attempts an automatic restart in Restart mode.
If the HT 6 has not reacted after 60 seconds, you must restart it manually by
switching the power supply to the system or the operator panel front off and then
on again.
11.11 Miscellaneous
11.11.1 NCK reset
It is possible to initiate an NCK Power-On Reset from the HT 6.
Operating sequence
Select the operating area "Start-up" and press the softkey
"NC"
"Start-up NC"
You can choose between:
- "Normal mode"
- "Start-up mode"
- "Software update"
This setting ensures that the program halts after the first machine function block
when a part program is started from reset with SBL active and not immediately
after the initialization sequence (Init. block).
Deactivation of function
MD 9006 = 0 Deactivation of function
2. You can adjust the brightness via softkeys in the "Start-up" operating area.
Select softkey "System" in the "Start-up" operating area. Then select softkey
"Brightness". The softkey menu changes and you can adjust the backlighting
by selecting softkeys "brighter" or "darker".
If the traversing keys are to control 6 axes or less, it is not necessary to create any
axis system groups.
To set up a number of axis systems, proceed as follows:
• Set the number of axis systems in machine data 9027.
• In the PLC user program, specify which axes are to be controlled by the
traversing keys and the axis system to which the axes belong.
• Set signal Abn+2 Bit6 (AXSEL0) to transfer the selected axis system from
the PLC to the HT 6. The selected axis system is displayed to the right of the
override in the status display (ASY2/ASY3/ASY4).
No text is displayed for axis system 1 (i.e. ASY1 is not shown).
You can choose whether or not to show the STAT and TU values by setting the
following display machine data:
I Index
I
I.1 Subject index
Change language...........................IM2/5-56
Channel switchover example.........IM2/5-61
A CMM_DIRECTORY_SOFTKEY_PATH1
MD 9676 ...................................IM2/5-112
Access rights ................................. IM2/5-51 CMM_DIRECTORY_SOFTKEY_PATH2
Accessories for PCU20 ................. IM2/2-13 MD 9677 ...................................IM2/5-113
Accessories ..................................... IM2/1-8 CMM_DIRECTORY_SOFTKEY_PATH3
Action log MD 9678 ...................................IM2/5-113
HT 6........................................ IM2/11-213 CMM_DIRECTORY_SOFTKEY_PATH4
Read out log file, MD 9679 ...................................IM2/5-113
HMI Emdedded ..................... IM2/9-165 CMM_ENABLE_CUSTOMER_M_CODES
Reading out the log file, HT6.. IM2/11-215 MD 9661 ...................................IM2/5-112
Set, HT 6 ................................ IM2/11-215 CMM_ENABLE_TOOL_MAGAZINE
ACTION_LOG_MODE MD 9674 ...................................IM2/5-112
9012 ....................................... IM2/11-213 CMM_FIXED_TOOL_PLACE
ACTION_LOG_MODE MD 9672 ...................................IM2/5-112
MD 9012..................................... IM2/5-97 CMM_POS_COORDINATE_SYSTEM
ACTION_LOG_MODE MD 9650 ...................................IM2/5-112
MD9012.................................... IM2/9-162 CMM_TOOL_DISPLAY_IN_DIAM
Activate tool offset immediately..... IM2/5-65 MD 9663 ...................................IM2/5-112
ACTIVATE_SEL_USER_DATA CMM_TOOL_LIFE_CONTROL
MD 9440................................... IM2/5-108 MD 9652 ...................................IM2/5-112
Alarm display ................................. IM2/5-58 CMM_TOOL_LOAD_STATION
Alarm text files for HT 6............. IM2/11-203 MD 9673 ...................................IM2/5-112
Alarm texts................................... IM2/6-116 CMM_TOOL_MANAGEMENT
ALARM_ROTATION_CYCLE MD 9651 ...................................IM2/5-112
MD 9056..................................... IM2/5-99 Communication .............................IM2/3-18
Altered MD, Data backup ............ IM2/8-153 Compact Flash card ......................IM2/3-36
Analog spindles ............................. IM2/5-66 Compact Flash card with
Articulated position STAT.............. IM2/5-72 adapter....................................IM2/7-142
Components of the PCU................IM2/2-12
B Configuration
Alarm and user texts.................IM2/7-136
Base offset..................................... IM2/5-67 Changing the language ............IM2/7-131
Blue screen, HT 6...................... IM2/11-216 ini files.......................................IM2/7-135
Blue screen.................................... IM2/3-42 Modifying the files .....................IM2/7-132
Bus address................................... IM2/3-20 Configure CAPSLOCK...................IM2/5-55
Configuring text files in foreign
languages ...............................IM2/6-121
C Connection mode
Network Manager ......................IM2/3-25
Card reader ................................... IM2/2-15
D File transfer
RCS Viewer PCU 20 .................IM2/5-87
D number....................................... IM2/5-66 File transfer between RCS Host PCU 20
DARKTIME_TO_PLC and RCS Viewer PCU 20..........IM2/5-83
MD 9015..................................... IM2/5-97 Fine offset of tools for wear ...........IM2/5-65
Data backup FIRST_LANGUAGE
For HMI Embedded WIN32 with the MD 9003 .....................................IM2/5-96
PCU 50 ................................. IM2/8-160 Free contour programming ...........IM2/5-74
General..................................... IM2/8-146
Transmission errors ................. IM2/8-152 G
Data backup on PC card ............. IM2/8-159
Data transfer via PLC .................. IM2/8-154 G code editor .................................IM2/5-75
Display axes .................................. IM2/5-71
Display axis systems, HT 6 ....... IM2/11-221
Display log file, HMI Embedded .. IM2/9-165 H
Display machine data .................... IM2/5-96
Display user list Hardware
Network Manager....................... IM2/3-27 Requirements .............................IM2/3-20
DISPLAY_BACKLIGHT HMI boot with network ..................IM2/3-35
MD 9025..................................... IM2/5-98
MD_DRV_TEA_IDX_LIMIT O
MD 9957................................... IM2/5-113
MD_NC_TEA_FILTER Online help
MD 9950................................... IM2/5-113 Network Manager .......................IM2/3-30
MD_NC_TEA_IDX_LIMIT OP 010 operator panel fronts ........IM2/2-14
MD 9951................................... IM2/5-113 OP 010...........................................IM2/2-14
MD_TEXT_SWITCH OP 012 operator panel front .........IM2/2-14
MD 9900................................... IM2/5-113 OP 012...........................................IM2/2-14
Measuring cycles........................... IM2/5-75 OP 015 operator panel fronts .......IM2/2-15
Mechanical and electrical installation OP 015...........................................IM2/2-15
PCU............................................ IM2/2-12 Operating system share.................IM2/3-29
Memory allocation Operation of the Network
Tool management ...................... IM2/5-91 Manager ...................................IM2/3-23
User data.................................... IM2/5-94
Memory cards................................ IM2/2-15
Metric/inch switchover ................... IM2/5-59 P
Milling simulation 3D graphics....... IM2/5-73
Modifying the configuration PA_ZOA_MODE
HT 6 software replacement .... IM2/11-191 MD 9459 ...................................IM2/5-108
Software replacement .............. IM2/7-130 Password
MPI/OPI netiquette ....................... IM2/3-18 Default password ........................IM2/5-52
Permitted characters ..................IM2/5-52
PC card ........................................IM2/7-141
N PCMCIA card ...............................IM2/7-141
PCU
NC card ....................................... IM2/7-141 Components ...............................IM2/2-12
NC_PROPERTIES Mechanical and electrical
MD 9500................................... IM2/5-109 installation................................IM2/2-12
NETNAMES.INI PCU ................................................ IM2/1-8
File extension ............................. IM2/5-61 PCU20
Netork Accesories ..................................IM2/2-13
Configuration data...................... IM2/3-32 Interfaces ....................................IM2/2-14
Network configuration examples Permanent connection
Company network ...................... IM2/3-35 Network Manager ......................IM2/3-26
One embedded / one server PLC alarm acknowledgement
computer ................................. IM2/3-33 icon ...........................................IM2/5-58
Three embedded / two server PLC start-up
computers ............................... IM2/3-34 HT 6 ........................................IM2/11-212
Network Manager PLC_ALARM_PICTURE
Deinstallation.............................. IM2/3-23 MD 9055 .....................................IM2/5-99
Network Manager PLC_HOTKEY
Connection mode ....................... IM2/3-25 MD 9017 .....................................IM2/5-97
Installation .................................. IM2/3-23 PLC_SYMBOL_FILTER
Operation.................................... IM2/3-23 MD 9054 .....................................IM2/5-99
Network Manager ......................... IM2/3-22 PLC_SYMBOL_SORT
Network operation MD 9053 .....................................IM2/5-98
HMI Embedded, TCP/IP PLC-MD
protocol ................................... IM2/3-32 Assign texts ................................IM2/5-56
Network operation with HMI Powerline ramp-up screen.............IM2/4-48
Embedded ............................... IM2/3-31 Preset actual value memory ..........IM2/5-68
NUM_AX_SEL Preset.............................................IM2/5-68
MD 9027..................................... IM2/5-98 PRG_DEFAULT_DIR
MD 9005 .....................................IM2/5-96
Program simulation ........................IM2/5-73
PROGRAM_SETTINGS Turning........................................IM2/5-73
MD 9460................................... IM2/5-109 SINUMERIK HT6 .......................IM2/11-184
Protection level change ................ IM2/5-53 Software installation ....................IM2/7-124
Software replacement
Modifying the configuration.......IM2/7-130
R Operator panel..........................IM2/7-139
Preparing for installation...........IM2/7-128
Ramp-up of the PCU ..................... IM2/4-48 Software replacement with modified
RCS Host PCU 20 configuration ...........................IM2/7-128
Adapt to PC ................................ IM2/5-82 Software replacement with standard
Change port ............................... IM2/5-85 configuration ...........................IM2/7-126
Configure.................................... IM2/5-81 Software version display..............IM2/9-166
Connection structure .................. IM2/5-79 Software via Network Manager....IM2/7-144
File transfer ................................ IM2/5-83 Standard configuration...................IM2/3-20
Sequence ................................... IM2/5-80 Standard control file
Start............................................ IM2/5-86 HMI Embedded.........................IM2/8-155
RCS Host PCU 20 ........................ IM2/5-78 STARTUP_LOGO
RCS Viewer PCU 20 MD 9050 .....................................IM2/5-98
Configuration.............................. IM2/5-84 STAT ..........................IM2/5-72, IM2/11-222
Connection structure .................. IM2/5-79 Static user memory (SRAM) .........IM2/5-89
File transfer ................................ IM2/5-83 Status (STAT)
Installation .................................. IM2/5-83 Hide, HMI Embedded ................IM2/5-73
Sequence ................................... IM2/5-80 Hide, HT 6...............................IM2/11-222
RCS Viewer PCU 20 .................... IM2/5-78 Show, HMI Embedded................IM2/5-73
Reading ISO programs in/out...... IM2/8-158 Show, HT 6 .............................IM2/11-222
Remote diagnostics of the Suppression measures ................... IM2/1-9
PCU 20 .................................... IM2/5-78 SW_OPTIONS
Replace ramp-up screen ............... IM2/5-59 MD 9990 ...................................IM2/5-114
Reset password............................. IM2/5-52 Switch channel
Rotary axis position ....................... IM2/5-72 Foreign language texts ...............IM2/5-64
Switch channel / control units
S SINUMERIK HT6 ....................IM2/11-209
Switch channels on one NCU ........IM2/5-60
Scratching...................................... IM2/5-68 Switch pocket calculator on/off ......IM2/5-56
Screen SWITCH_TO_AREA
Activate screen darkening, MD 9016 .....................................IM2/5-97
HT 6 .................................... IM2/11-220 Switching the work offset display...IM2/5-67
Screen darkening via PLC ........ IM2/5-55 SYS_CLOCK_SYNC_TIME
Set brightness, HT 6 .............. IM2/11-221 MD 9013 .....................................IM2/5-97
Screen saver ................................. IM2/5-55
Select language HT 6 T
Modifying the configuration .... IM2/11-192
Selecting tools via a D number TABULATOR_SIZE
(flat D no.) ................................ IM2/5-66 MD 9007 .....................................IM2/5-97
Series start-up ............................. IM2/8-146 TCP/IP protocol
Set action log, HMI Emdedded.... IM2/9-165 Configuring under Win95/98/ME IM2/3-40
Set date ......................................... IM2/5-57 Configuring under WinNT/
Set editor ....................................... IM2/5-57 2000/XP...................................IM2/3-39
Set password................................. IM2/5-52 Install/configure under HMI
Set time ......................................... IM2/5-57 Embedded ...............................IM2/3-32
Shared folder for PCU ................... IM2/3-29 Installing under Win95/98/ME.....IM2/3-40
SHOW_CHANNEL_SPANNING_STATE Installing under WinNT/
MD 9052..................................... IM2/5-98 2000/XP...................................IM2/3-39
Simulation
Milling ......................................... IM2/5-73
USER_CLASS_DIRECTORY4_P USER_CLASS_TM_SKMGNEXT
MD 9513................................... IM2/5-110 MD 9263 ...................................IM2/5-103
USER_CLASS_INCH_METRIC USER_CLASS_TM_SKNCDELTOOL
MD 9182..................................... IM2/5-99 MD 9259 ...................................IM2/5-103
USER_CLASS_OVERSTORE_HIGH USER_CLASS_TM_SKNCNEWTOOLE
MD 9213................................... IM2/5-100 MD 9258 ...................................IM2/5-102
USER_CLASS_PRESET USER_CLASS_TM_SKTLLIST
MD 9220................................... IM2/5-101 MD 9251 ...................................IM2/5-102
USER_CLASS_READ_BD USER_CLASS_TM_SKTLLREPR1
MD 9230................................... IM2/5-101 MD 9265 ...................................IM2/5-103
USER_CLASS_READ_CST USER_CLASS_TM_SKTLLREPR2
MD 9225................................... IM2/5-101 MD 9266 ...................................IM2/5-103
USER_CLASS_READ_CUS USER_CLASS_TM_SKTLLREPR3
MD 9226................................... IM2/5-101 MD 9267 ...................................IM2/5-103
USER_CLASS_READ_DEF USER_CLASS_TM_SKTLNEWTOOL
MD 9229................................... IM2/5-101 MD 9264 ...................................IM2/5-103
USER_CLASS_READ_GUD_LUD USER_CLASS_TM_SKTOOLLOAD
MD 9211................................... IM2/5-100 MD 9252 ...................................IM2/5-102
USER_CLASS_READ_IN USER_CLASS_TM_SKTOOLMOVE
MD 9224................................... IM2/5-101 MD 9254 ...................................IM2/5-102
USER_CLASS_READ_PROGRAM USER_CLASS_TM_SKTOOLUNLOAD
MD 9216................................... IM2/5-100 MD 9253 ...................................IM2/5-102
USER_CLASS_READ_SYF USER_CLASS_VERT_MODE_SK
MD 9228................................... IM2/5-101 MD 9249 ...................................IM2/5-102
USER_CLASS_READ_TCARR USER_CLASS_WRITE_FINE
MD 9180..................................... IM2/5-99 MD 9203 ...................................IM2/5-100
USER_CLASS_READ_TOA USER_CLASS_WRITE_GUD_LUD
MD 9200................................... IM2/5-100 MD 9212 ...................................IM2/5-100
USER_CLASS_SELECT_PROGRAM USER_CLASS_WRITE_PRG_CONDIT
MD 9218................................... IM2/5-101 MD 9214 ...................................IM2/5-100
USER_CLASS_SET_V24 USER_CLASS_WRITE_PROGRAM
MD 9223................................... IM2/5-101 MD 9217 ...................................IM2/5-100
USER_CLASS_SHOW_SBL2 USER_CLASS_WRITE_RPA
MD 9227................................... IM2/5-101 MD 9222 ...................................IM2/5-101
USER_CLASS_SYS_ZERO_OFF USER_CLASS_WRITE_SEA
MD 9246................................... IM2/5-102 MD 9215 ...................................IM2/5-100
USER_CLASS_TEACH_IN USER_CLASS_WRITE_TCARR
MD 9219................................... IM2/5-101 MD 9181 .....................................IM2/5-99
USER_CLASS_TM_SKACTPLACE USER_CLASS_WRITE_TOA_ADAPT
MD 9270................................... IM2/5-103 MD 9209 ...................................IM2/5-100
USER_CLASS_TM_SKFINDPLACE USER_CLASS_WRITE_TOA_GEO
MD 9269................................... IM2/5-103 MD 9201 ...................................IM2/5-100
USER_CLASS_TM_SKLDTOOLDAT USER_CLASS_WRITE_TOA_WEAR
MD 9271................................... IM2/5-103 MD 9202 ...................................IM2/5-100
USER_CLASS_TM_SKMGBUFFER USER_CLASS_WRITE_ZOA
MD 9260................................... IM2/5-103 MD 9210 ...................................IM2/5-100
USER_CLASS_TM_SKMGFIND USER_WRITE_CYCFRAME
MD 9261................................... IM2/5-103 MD 9186 .....................................IM2/5-99
USER_CLASS_TM_SKMGLISTPOS USER_WRITE_EXTFRAME
MD 9262................................... IM2/5-103 MD 9188 .....................................IM2/5-99
USER_CLASS_TM_SKMGLREPR2 USER_WRITE_PARTFRAME
MD 9256................................... IM2/5-102 MD 9184 .....................................IM2/5-99
USER_CLASS_TM_SKMGLREPR3 USER_WRITE_TOOLFRAME
MD 9257................................... IM2/5-102 MD 9183 .....................................IM2/5-99
SINUMERIK 840D/840Di/810D
6.3.6 NCU-specific alarm texts with multiple operator panels/NCUs ...................................... IM4/6-175
8 Diagnostics........................................................................................................................... IM4/8-241
10.5 Example program 2: Display time and optional text variables........................................ IM4/10-263
10.6 Example program 3: MMC command with synchronous acknowledgment mode .......... IM4/10-265
10.7 Example program 4: Positioning the input and output field ............................................ IM4/10-266
10.10 Example program 8: Asynchronous acknowledgment mode with softkeys .................. IM4/10-270
10.11 List of files for the dialog screen files ........................................................................... IM4/10-272
1 General Preparations
1
1.1 Hardware/software requirements................................................ IM4/1-8
Introduction
This Installation and Start-Up Guide describes the procedures for commissioning
the PCU 50/70 with the HMI Advanced software. For further reading on special
NCK, MMC, PLC, or drive functions, please consult the Descriptions of
Functions/Manuals (see "Required documentation").
Note
The HMI Advanced software can also run on the MMC 103 with Windows NT4.0,
order number 6FC5 2110-0DB21-3AA1. (Intel Pentium 200 MHz, 64 MB RAM).
The HMI Advanced software, which must be ordered separately, should be
loaded using the pre-installed basic software, as described for the PCU50.
1.2 Documentation
You require the following documentation for the installation and start-up of
SINUMERIK 840D:
1. Operator Components Manual /BH/
Order number: 6FC5 297-6AA50-0AP0
2. Description of Functions, Basic Machine /FB/ (Part 1)
Order number: 6FC5 297-6AC20–0AP0
3. Lists /LIS/
Order number: 6FC5 297-6AB70-0AP0
4. Diagnostics Guide /DA/
Order number: 6FC5 297-6AA20-0AP0
5. Operator's Guide HMI Advanced /BAD/
Order number: 6FC5 298-6AF00-0AP0
Operator's Guide HMI Advanced
Exception:
• If non-Siemens devices are connected (printers, programming devices, etc.),
you can also use standard shielding cables which are connected at one end.
These external devices may not be connected to the control during normal
operation. However, if the system cannot be operated without them, then the
cable shields must be connected at both ends. Furthermore, the external
device must be connected to the control via an equipotential bonding lead.
• Signal cables and load cables must be routed at the greatest possible distance
from one another.
• Only use SIEMENS signal cables for connecting to and from the NC or PLC.
• Signal cables must not be laid in the close vicinity of strong external magnetic
fields (e.g. motors and transformers).
! Important
For more information about interference suppression measures and connection of
shielded cables, please refer to
References: /EMC/, EMC Installation Guidelines
! Important
Handling of modules containing devices sensitive to electrostatic discharge:
• When handling electrostatically sensitive devices, make sure that operator,
workplace and packing material are properly grounded.
• As a general principle, avoid touching electronic components unless the work
to be performed makes this unavoidable. Therefore, when handling PCBs,
make sure that you never touch any submodule pins or conducting paths.
• Components must only be touched if
- You are permanently grounded with an ESD arm band,
- You are wearing ESD shoes or ESD shoe grounding strips that are
in contact with an ESD floor.
• Modules must be placed on a conductive surface (table with ESD surface,
conductive ESD foam plastic, ESD packing bag, ESD transport container).
• Never place modules in the vicinity of display units, monitors, or television sets
(minimum distance < 10 cm).
• Modules must never be brought into contact with statically chargeable and
highly insulating materials, such as plastic sheeting, insulating table tops,
clothing made of synthetic fibers.
• Measurements of the module must only be performed if
- The measuring instrument is grounded (e.g. via protective conductor) or
- Before measuring with a potential-free measuring device the measuring
head is discharged briefly (e.g. touch unpainted metal on the control
housing).
The HMI Advanced software runs with the following SINUMERIK operator panel
fronts for use with the PCU 50/70: OP 010, OP 010S, OP 010C, OP 012, TP012,
TP015A, OP 015 and OP015A.
When it is used with an operator panel front, the PCU 50/70 is first screwed to the
panel front and then secured to the mounting panel with fixing devices.
Control key
Softkeys block
Hotkey
block
Cursor
block
USB
front
interface
Recall Machine Area Etc key Area switchover
*) When TEMP LED responds, expect higher wear
Fig. 2-1
Notes
IP address input
To do this, select
Start-> Settings-> Control Panel-> Network, "Protocols" tab, and set Properties to
TCP/IP Protocol.
3.3.1 Hardware
Hardware
The operating basis for HMI software is
• a computer unit together with an
• OP… operator panel
"PCU" is the term used for the computer unit on which the HMI (human-machine
interface) software runs from HMI software release 6.0 onwards.
Note
Details of how to replace PCU and OP/TP components can also be found in the
Operator Components Manual. Please refer to the latest /BU/ NC 60 order
catalog for available component combinations.
Note
Instructions on how to use the basic software can be found in the file
C:\Siemensd.rtf
For the versions of the Service menu (and Windows NT) system components
contained in the basic software, please refer to the file C:\BaseVers.txt.
The expansion is carried out from a Service menu, which comes with the basic
software.
Service menu
The Service menu is written in DOS.
Software installations and updates are started from the Service menu and (after
rebooting the system) executed by Windows NT/XP.
Data backup functions (backup/restore) are also carried out using the Service
menu.
The boot manager allows you to choose between booting a Sinumerik system and
the Service menu.
• 3 primary partitions and 1 expanded partition are created. (Hard disks below 4.8
GB in size are not supported).
• As well as Windows NT 4.0 or Windows XP (with the HMI system software),
DOS (with the Service menu) can also be booted (dual booting).
• Depending on the order details, the HMI system software may be pre-loaded on
delivery. It is installed subsequently by the customer the first time the system is
booted.
• For data security reasons, the HMI system software, the Windows NT system
software and DOS are distributed by the Service menu to different partitions.
The following illustration shows how partitioning is used in the installation of the
HMI system software (the partition names are shown in italics).
PCU
H a rd d is k
Partition C
Partition C contains DOS 6.2 together with the tools and scripts created by the
Service menu (e.g. Ghost tools).
Partition D
Partition D is used for Ghost images, i.e. stored images (e.g. those supplied with
the system) and local backup images. The Windows NT system software, which
can be copied for installing drivers or as an update, for example, is also stored
there. Partition D also contains the installation directory to which the software to be
installed is copied from a remote PG/PC before the actual installation process.
Partition E
Partition E is reserved for the Windows NT/XP system software.
Partition F
Partition F is the applications partition. Applications such as the HMI system
software (including data management and temporary data), HMI-OEM applications,
STEP7 and customer-specific applications (e.g. Protool) run here.
Note
The size of the partitions shown in Figure 3-1 depends on the size of the hard
disk and the type of Windows operating system.
Note
We strongly recommend that you install all applications in Partition F only.
Free areas
The following hard disk memory space is available on the PCU 50 and PCU 70:
Drive D: 1.8 GB reserved for local backups
Drive F: 3 GB in addition to the pre-installed 5-language HMI Advanced
which is reserved for user data (programs, applications, languages,
data, etc.).
High memory allocation in drive F: can mean that a local partition backup becomes
so big that it can no longer be stored locally on drive D:. If that happens, the
GHOST image (hard disk backup) must be stored on an external device.
The Service menu is used for software installation and data backup.
Here you can:
- Transfer/expand HMI system software
- Install HMI system software from a network
- Save data to the hard disk (backup/restore)
The basic functions of the Service menu are described in section 3.4. It can be
activated when the system is booted. See 3.3.6.
Main Function
menu
2 SINUMERIK Tools and Options: Load additional tools and enable options.
1 Activate STEP7 for PCU, see notes below
9 Return to Main Menu: Back to main menu
3 DOS Shell: call the DOS command interpreter, drive C:\ is displayed, type
"exit" to leave the DOS shell.
4 Start Windows: The Windows functions can be used here
1 Standard Windows (without starting SINUMERIK HMI)
4 Original SINUMERIK HMI Environment, started next time the system
is booted
5 Current SINUMERIK HMI Environment, started next time the system
is booted
9 Return to Main Menu: Back to main menu
5 SINUMERIK System Check: test the file system for consistency, restore
consistency with SCANDISK if necessary.
7 Backup/Restore:
1 Hard disk Backup/Restore with GHOST
1 Configure GHOST Parameters: Set parameters (interface, path,
network connection) for Norton Ghost
1 Set Connection Mode PARALLEL (LPT:)
2 Set Connection Mode LOCAL/NETWORK
3 Change Backup Image File Name
4 Change Restore Image File Name
5 Change Machine Name (for Windows and DOS net)
1 Input Machine Name MANUALLY
2 Generate Machine Name RANDOMLY
9 Back to previous menu
6 Manage Network Drives (see above)
7 Change Split Mode
1 NO Splitting
2 Splitting
9 Back to previous menu
2 Harddisk Backup: back up hard disk
3 Harddisk Restore: copy data to hard disk
1 Windows XP
1 Standard Partitioning (default)
2 User-defined Partitioning
3 Image-defined Partitioning
2 Windows NT/2000 (submenu same as for Windows XP)
3 Windows 95 (submenu same as for Windows XP)
4 WfW3.11 (submenu same as for Windows XP)
5 DOS (spare part) (submenu same as for Windows XP)
9 Back to previous menu
4 Switch to other version of GHOST
9 Back to previous menu: return to previous menu
Main Function
menu
7 4 Partition Backup/Restore with GHOST: Save partition contents from
C:, E:, F: to D: or copy back from D: to C:, E:, F:.
1 Configure Ghost Parameters
1 Change Maximum Backup Images
2 Define Emergency Backup Image
9 Back to previous menu
2 Partition Backup, LOCAL Mode
3 Partition Restore, LOCAL Mode
4 Partition E (Windows) Restore, Mode LOCAL
8 Delete Image
9 Back to previous menu
9 Return to Main Menu: Back to main menu
8 Start PC Link: install software from a CD-ROM (Interlink/Interserve)
9 Reboot: restart the system
To configure the Service menu, create the file envparam.bat in the Tools directory
in partition C: and enter the following commands:
String entries:
Preconditions
The SIMATIC Step7 software V5.x for SINUMERIK hardware is already installed.
Operator action
While the PCU is booting (after switching the control off and then on again):
1. Select the Service menu [hidden menu option] in the boot manager
The following menu is displayed:
PLEASE SELECT
9 Reboot (Warmboot)
2. Select option 2
PLEASE SELECT
Authorizing
4. Select option 1
Booting
The system will then reboot automatically.
The actual authorization takes place next time Windows NT/XP is booted, before
the HMI system software is started.
Note
Authorization can also be performed on the SINUMERIK desktop by starting the
function "STEP7 Authorizing".
- ADD_ON
- USER
- OEM
are saved. The directories are then cleared.
Operator action
While the PCU is booting (after switching the control off and then on again):
1. Select the Service menu [hidden menu option] in the boot manager
9 Reboot (Warmboot)
2. Select option 4
passwd:
Note
The original settings for the HMI environment can also be restored on the
SINUMERIK desktop by starting the function "Original SINUMERIK HMI Environ".
Operator action
While the PCU is booting (after switching the control off and then on again):
1. Select the Service menu [hidden menu option] in the boot manager
9 Reboot (Warmboot)
2. Select option 4
passwd:
Booting
The system will then reboot automatically.
The function is actually executed next time Windows is booted, before the HMI
software is started.
Note
Restoration of the original settings for the HMI environment can also be canceled
on the SINUMERIK desktop by starting the function "Current SINUMERIK HMI
Environ".
Operator action
While the PCU is booting (after switching the control off and then on again):
1. Select the Service menu [hidden menu option] in the boot manager
9 Reboot (Warmboot)
passwd:
Operator action
While the PCU is booting (after switching the control off and then on again):
1. Select the Service menu [hidden menu option] in the boot manager
PLEASE SELECT
9 Reboot (Warmboot)
Note
The SINUMERIK desktop can also be started while the system is booting by
pressing 3 when the version number of the basic software appears in the
background display (within a 3-second time frame).
1. Select the Service menu [hidden menu option] in the boot manager
9 Reboot (Warmboot)
The function is actually executed next time Windows NT/XP is booted, before the
HMI system software is started.
Note
The hard disk can also be checked on the SINUMERIK desktop by starting the
function "Check SINUMERIK System".
Booting
In the boot screen the version of the basic PCU software appears in the bottom
right of the display.
Note
Installing/updating the HMI system software via the Service menu (DOS) is
described in 7.2.
Note
The function can also be initiated in the Service menu (DOS), see 3.4.2 Setting
the original SINUMERIK HMI environment.
It is then executed when Windows NT is started (before the HMI system software
starts), without the need to open the SINUMERIK desktop.
Note
The function can also be initiated in the Service menu (DOS) as described in
3.4.3 Setting the current SINUMERIK HMI environment. It is then
executed when Windows is started (before the HMI system software starts),
without the need to open the SINUMERIK desktop.
Note
The function can also be initiated in the Service menu (DOS) as described in
3.4.1 Authorizing SIMATIC Step7 for SINUMERIK hardware. It is then
executed when Windows is started (before the HMI system software starts),
without the need to open the SINUMERIK desktop.
Note
A PS/2 mouse will not work with this setting.
Note
The function can also be initiated in the Service menu (DOS) as described in
3.4.6 Checking the hard disk. It is then executed when Windows is
started (before the HMI system software starts), without the need to open the
SINUMERIK desktop.
HMI Explorer
In some cases HMI applications can be started and uninstalled individually from
HMI Explorer.
Log file
Whenever the system is booted, information is written to a block in the file
D:\$$Base.log, which contains the date, time and nature of administrative
interventions.
3.5.7 Configuration
In addition to programs, data files can also be placed in the subdirectories. They
are then opened according to their file type. For example, ".txt" files are opened
with Notepad, ".htm" files with Internet Explorer.
Reference documents
The documents SIEMENSD and SIEMENSE on the SINUMERIK desktop contain
notes, explanations and conditions relating to the basic software that is currently
loaded.
Reference Default
Key HKLM\SOFTWARE\Siemens\SINUMERIK\Basesoftware\<version>\HM
IManager
User Input HMIUserName (STRING) auduser
Domain Input HMIUserDomainName (STRING) local
When the operator logs on as the (currently registered) HMI user, the HMI system
software is started automatically when the system boots. If the operator logs on as
a Windows user other than the HMI user, the SINUMERIK desktop opens.
The operator does not normally need to log on explicitly, as the system is
configured so that the operator logs on automatically as the HMI user.
To log on as another Windows user, the operator must press and hold down the
Shift key on the PS2 keyboard or on an external USB keyboard (this function is
not available on an OP…) as soon as the boot screen appears. The Windows
Logon screen then opens, in which the operator must enter the name and
password of the chosen Windows user.
4
4 Power On / Booting
4.1 Switching on
Preconditions
Before you connect the PCU to the power supply, you must unlock the hard disk
and connect an operator panel front and the I/O devices (keyboard and display or
monitor).
1. With the power supply to the PCU 50/70 switched off, plug the leads for the I/O
devices into the appropriate sockets on the interface side of the PCU.
2. Once the I/O devices have been connected, the device is ready.
Information on how to adapt and set the interface and which connection cable is
required, can be found in the User's Manual for your I/O device.
Note
When connecting I/O devices, please make sure that the components are
designed for use in industry.
! Caution
When plugging in/unplugging I/O connections (keyboard, mouse, printer, etc.),
make sure that the I/O devices and the PCU are disconnected from the power
supply. Otherwise they may be damaged.
This does not apply to USB connections.
4.2 Booting
Function
When the system is started for the first time, the software pre-loaded on the hard
disk (SINUMERIK products, including HMI Advanced software if applicable), is
installed under Windows NT/XP as follows:
Welcome to SINUMERIK
These SINUMERIK products will be installed now:
<product 1>
<product 2>
<product 3>
...
Install NOW
CANCEL Installing
The buttons can be selected by pressing the Tab key and activated by pressing
Enter.
Effect of the buttons:
Install NOW:
All the products displayed are installed one after another in the sequence in which
they are listed. If a reboot is required to activate the installation, it is executed
immediately after installation of the corresponding program. The system may
therefore be rebooted several times until all products are installed.
CANCEL Installing
Nothing is installed and the screen is not displayed again the next time the system
is rebooted. Other installations can then only be carried out explicitly in Windows
mode by activating the setup.exe programs directly in the setup directories.
Should you wish to install individual products at a later date, you will have to start
up HMI Explorer from the SINUMERIK desktop. See 3.4.5. Then in HMI Explorer
choose the Install menu option and select the product you wish to install.
Initial situation
The hard disk of the PCU is pre-partitioned for SINUMERIK 840D operation and
further SINUMERIK applications on delivery and the software required for a basic
start-up is installed:
• The boot software and other software needed for start-up are stored on C:
PCU
H ard disk
Prim ary partition Expanded partition P rim ary partition P rim ary partition
active w ith logical drive
REGIE.INI
The applications to be started are entered in the REGIE.INI file. This file can be
edited, see Chapter 5.
• When this file is written to the hard disk, the power supply to the PCU can be
disconnected without the loss of relevant information.
• Reactivating the operating system image file is far quicker than restarting
Windows XP as a full reboot.
Preconditions:
• All Windows XP drivers and all applications must support accelerated mode
(Hibernate) in order to execute Hibernate along with applications. For Touch
Panel drivers this may not be the case. Accelerated mode is therefore
unavailable for systems with TP0xx.
• The Windows system must be activated in standard mode (not service mode).
Use:
Since one or more applications/drivers cannot be closed in Hibernate mode, only a
limited Hibernate can be executed. All HMI Advanced applications must be closed.
Only the Windows XP image can be saved by Hibernate and restored the next time
the system is rebooted.
Reactivating the Windows XP image is slightly faster than restarting Windows
completely. All applications must be restarted once Windows XP has been
reactivated.
! Important
The "Hibernate" function has been tested in the standard configuration of HMI
Advanced. If add-on and OEM software components are installed, the user
should test this function.
Configuration
Selection of the suitable variant for an XP system and its configurations is
configured in the file regie.ini. See Chapter 5.
NETNAMES.INI
In M:N configuration the startup of the operator panel front(s) can be modified in
the file NETNAMES.INI, see Chapter 5, and
• Language localization
• MPI/OPI address
• Color settings for the user interface
Screen properties:
The required screen resolution is 640 x 480 to 1024 x 768 (depending on the OP),
with 256 colors.
F:\OEM\IB\DATA\<Nck type>\<Resolution>\<Bild.bmp>
If you want the same screen to be used each time (NCU-independent screen), it
can be saved in the "default" directory in the required resolutions.
If you want to display different screens for different NCUs, they must be stored in
the <NckType\<Resolution> subdirectories in the appropriate resolution.
Screen name
<Name>.bmp
You can choose any name you want, but you can store only one file per directory.
Resolution
The screens must be created with a graphics tool in the resolution indicated by the
subdirectory name and stored in the corresponding directory. The HMI software
selects the screen according to the NCK type and the resolution of the operator
panel.
Colors
The screen must be set to 256 colors.
Note
When the system is booted for the first time, a standard screen is displayed
because there is no viable connection to the NC. Thereafter, the screen
corresponding to the hardware in use is displayed.
Function
When the data management server is booted, the server reads
In the boot phase the data management server checks whether there are entries
for modified standard access authorizations in the file dh.ini.
The data management server uses these settings to update its internal image of
the data management chart with the modified access authorizations.
The access authorizations described in the entries are now used as standard
access authorizations for the selected data.
\wks.dir\*.wpd\*.mpf = 75775
\mpf.dir\*.mpf = 75775
An entry comprises the path at which data of the data type can be created and the
new standard access mask.
The new standard access mask 75775, with which new part programs are created,
is defined in all workpieces. Access mask 75775 stands for:
Access mask
7 Read access for all 0 to 7 are permissible
5 Write access from protection level 5 0 to 7 are permissible
7 Execution access is set 0 or 7 are permissible
7 Display access for all 0 to 7 are permissible
5 Delete access from protection level 5 0 to 7 are permissible
Restrictions
When the HMI database is installed, data is always created with the access
authorizations defined in the standard data chart.
Access authorizations for nodes such as wks.dir cannot be changed.
Example
[Accessmasks]
\wks.dir\*.wpd\*.mpf = 75775
\mpf.dir\*.mpf = 75775
\cus.dir\*.spf = 33773
CAPSLOCK
The CAPSLOCK function is used to lock conversion of lower case to upper case
letters. It is used with external SINUMERIK keyboards. If lower case letters occur,
they can be added by means of the SHIFT commands function.
The function is only active when HMI Advanced is running, not in standard
Windows NT/XP operation.
Pressing the key sequence CTRL and SHIFT in succession reverses the function
so that upper case letters that occur are converted into lower case letters.
Pressing the CTRL, SHIFT sequence again switches back to conversion from
lower case to upper case letters. There is no limit on the time elapsing between
pressing CTRL and SHIFT, but no other character can be entered between CTRL
and SHIFT.
Activation
The function is activated by the display machine data 9009
$MM_KEYBOARD_STATE activated.
0: CAPSLOCK off
2: CAPSLOCK on
This data is only evaluated on startup. If the MD is changed, the system must be
rebooted.
Screen display
When lower case letters are activated, an icon of the SHIFT key appears in the
dialog line.
Restrictions
• When the CAPSLOCK function is activated, the SHIFT key has no effect on
letter keys.
• In standard Windows applications CTRL/ALT key sequences only work in
lower case mode.
• Switching to lower case mode is not available on the integral keyboards on the
OP 010/OP 12.
• The CTRL + Shift switching sequence only works with PS2 keyboards and
external USB PC keyboards, not with panel keyboards.
can be used in conjunction with HMI Advanced in the event of a failure in the
power supply to the PCU50/70 to continue operation for a limited period using the
backup battery and to shut down the HMI properly before the battery runs out.
Preconditions
• HMI Base 06.03.14
• SITOP software version 2.5 and higher
– configuration manager
– monitoring program
are installed.
• The SITOP UPS hardware is connected
The necessary programs are set up as part of the HMI Advanced installation.
! Important
The "SITOP UPS" function has been tested in the standard configuration of HMI
Advanced. If add-on and OEM software components are installed, the user
should test the shutdown of the entire system.
Procedure
Start the configuration manager in Windows mode. In the parameters area for the
buffer memory enter the path of the program that you want to close HMI Advanced
and shut down the PCU in the event of a power failure. The path name is:
E:\WINNT.40\System32\hmiexit.exe
Parameterization
Parameterization is carried out in the file:
[Actions]
#Waiting time in seconds for closing HMI Advanced applications
Wait = 120
ForceShutdown = True
The default settings are shown above. With ForceShutdown = True, a Windows
shutdown is executed on expiration of the waiting time, regardless of the status of
the HMI applications (recommended).
With ForceShutdown = False, Windows is not shut down.
References:
More information can be found in the product descriptions with the corresponding
order number.
The following errors can occur when the operator panel front is booted:
The operator panel front is connected to the NC and the PLC via a serial bus.
This alarm occurs if the HMI is started for the first time and the NC/PLC has
not yet finished booting or communication with these components is faulty.
When this alarm occurs, all display values connected with the NC/PLC become
invalid. Such faults are normal while the controls are starting up (e.g. after
resetting).
The alarm disappears automatically as soon as the fault situation has ended. If
the alarm continues, a wide variety of causes may be to blame (e.g. line break,
NC/PLC not booted, faulty address/baud rate configuration on one of the bus
nodes, etc.).
The following standard BIOS parameters are factory-set on the PCU50 device:
Main
System time 1) hh:mm:ss
System date MM/DD/YYYY
Disk A: 1.44 MB, 3 ½" (connected
externally
=> disable additional HD test)
Primary master C: 10056 MB (currently) or higher 10056 MB (currently) or higher
Primary slave None
Secondary master None
Secondary slave None
Memory cache Write back
Boot options
Quick boot mode Enabled
SETUP prompt Enabled
POST errors Enabled
Floppy check Disabled
Summary screen Enabled Disabled
Keyboard features
Num Lock Off Off
Key click Disabled
Keyboard auto–repeat rate 30/s
Keyboard auto–repeat delay 1/2s
Hardware options
PCI–MPI/DP: Enabled
On-board Ethernet Enabled
Ethernet address 08000624xxxx
LAN remote boot Enabled
Cardbus/PCMCIA slot Enabled
Fan control Enabled
SafeCard functions Enabled
Legacy USB support Enabled Enabled
CRT/LCD selection SIMULTANEOUS
CRT 640 x 480 75 Hz
CRT 800 x 600 75 Hz
CRT 1024 x 768 75 Hz
LCD screensize Graph & text expanded
DSTN contrast 154
Trackball / PS2 mouse Auto
Advanced
COM/LPT Configuration
Internal COM1 Enabled
Base I/O address 3F8
Interrupt IRQ4
Internal COM2 Enabled
Base I/O address 2F8
Interrupt IRQ3
Internal LPT1 Enabled
Mode EPP EPP
Base I/O address 378 Not applicable for EPP
Interrupt IRQ7
DMA channel DMA 10 Not applicable for EPP
PCI configuration:
PCI device slot 1
Option ROM scan Enabled
Enable master Enabled
Latency timer 0040 h
PCI device slot 2
Option ROM scan Enabled
Enable master Enabled
Latency timer 0040 h
on-board PCI
Ethernet
Option ROM scan Disabled
Enable master Disabled
Latency timer 0040 h
PCI/PnP ISA IRQ exclusion
IRQ3 Available
IRQ4 Available
IRQ5 Available
IRQ7 Available
IRQ9 Available
IRQ10 Available
IRQ11 Reserved
PCI IRQ line 1 Auto-select 5
PCI IRQ line 2 Auto-select
PCI IRQ line 3 Auto-select
PCI IRQ line 4 Auto-select
Installed O/S Other
Reset configuration data No
Floppy disk controller Enabled
Local bus IDE adapter Primary & secondary, both
Large disk access mode DOS
Hard disk pre-delay Disabled
Memory gap at 15MB Disabled
Security
Supervisor password is Disabled
User password is Disabled
Set supervisor password [Enter]
Set user password [Enter]
Password on boot Disabled
Fixed disk boot sector Normal
Floppy disk access Supervisor
Power
APM Enabled
Power savings Disabled
Standby timeout Off
Suspend timeout Off
Hard disk timeout Disabled
Fan control Enabled
Boot sequence
Hard drive Hard drive
Removable devices Removable devices
Floppy disk drive CD-ROM drive
ATAPI CD-ROM drive IntelBootAgent (IBA)
Version
Component SINUMERIK PCU 50
BIOS version V07.01.07 V02.03.04
BIOS number -A5E00054959A-DS02 - A5E00124434-ES01
MPI/DP firmware V01
CPU type PENTIUM II PENTIUM III
CPU speed 333 MHz or higher 866 MHz
CPU ID
Code revision
1)
Italics: Automatic setting, cannot be changed
You can activate this via the operator panel front as described below.
The system will then boot as described in Subsection 7.6.1 of the Operator
Components Manual.
Note
Changes to the BIOS settings, with the exception of the boot sequence and the
LPT mode (EPP, EPC), require an OEM agreement to be signed.
Notes
5 Functions / Parameterization
5
5.1 Functions .....................................................................................IM4/5-57
5.1.1 Alarm protocol ........................................................................IM4/5-57
5.1.2 Activating data transfer via PLC.............................................IM4/5-59
5.1.3 Informing the PLC of the current HMI task number
(HMI version 6.2 and higher) .................................................IM4/5-62
5.1.4 Fine zero offset and base offset.............................................IM4/5-64
5.1.5 Defining the machine position and rotary axis position
(version 6.1 and higher) .........................................................IM4/5-64
5.1.6 Block search in program test mode, multi-channel
(not version 6.1) .....................................................................IM4/5-65
5.1.7 Configuring language selection..............................................IM4/5-67
5.1.8 Access protection...................................................................IM4/5-70
5.1.9 Changing access protection for the base offset softkey ........IM4/5-72
5.1.10 Hiding axes ............................................................................IM4/5-72
5.1.11 Changing the coordinates system for actual-value display....IM4/5-74
5.1.12 Activating the active tool offset immediately ..........................IM4/5-74
5.1.13 Checking for boot viruses ......................................................IM4/5-75
5.1.14 Cross-channel status display with icons
(version 6.2 and higher) .........................................................IM4/5-76
5.1.15 Inverting the spindle icon in the spindle display
(version 6.2 and higher) .........................................................IM4/5-82
5.1.16 Configurable displays in the header
(version 6.2 and higher) .........................................................IM4/5-83
5.1.17 Selecting the channel/spindle from the PLC
(version 6.2 and higher) .........................................................IM4/5-87
5.1.18 User-specific operating trees .................................................IM4/5-88
5.1.19 Cycles in the DRAM ...............................................................IM4/5-95
5.1.20 Image provision for classic/new layout variants.....................IM4/5-97
5.1.21 User additions in the service overview...................................IM4/5-98
5.2 Simulation data matching ..........................................................IM4/5-101
5.2.1 Simulation data ....................................................................IM4/5-101
5.2.2 Displaying simulation data ...................................................IM4/5-106
5.2.3 Expansion of geometrical tool data in the simulation...........IM4/5-107
5.2.4 Data matching in simulation.................................................IM4/5-110
5.2.5 Memory configuration for simulation ....................................IM4/5-114
5.2.6 Simulation with OEM transformations..................................IM4/5-115
5.2.7 Accelerating simulation startup ............................................IM4/5-115
5.3 Parameterization with ini files ....................................................IM4/5-117
5.3.1 Editing Ini files ......................................................................IM4/5-117
5.3.2 Tool management ................................................................IM4/5-120
5.3.3 MD for actual-value setting, scratching, PRESET ...............IM4/5-120
5.3.4 Executing from the hard disk in M : N ..................................IM4/5-123
5.3.5 Editor ....................................................................................IM4/5-124
5.1 Functions
The functions of HMI Advanced can be altered in the INI files, display MD or the
user interface.
There are a number of strategies for reducing the load on the disk. Multiple
protocol files can be maintained in parallel on the disk. With the multiple file
strategy, each time the HMI is started the next file is selected. This reduces the
load on the disk hardware, in the area of both data and directory information. In
addition, this strategy detects physical disk errors in the data area on startup and
avoids them by reallocating memory space.
The multiple file strategy can be selected by means of the DiskCare Ini file entry
File: "mbdde.ini",
Section: [PROTOCOL],
Entry: "DiskCare".
DiskCare=-1 The MBDDE server controls the alarm protocol in the memory.
The alarm protocol is saved to the hard disk if it is displayed in
the diagnostics operating area or if the Alarm Cancel key is
actuated.
DiskCare=n Changes to the alarm status are written to the protocol file if no
change occurs within n seconds.
In addition, the alarm protocol is saved to the hard disk if
it is displayed in the diagnostics operating area or if the Alarm
Cancel key is actuated.
The file "mbdde.ini" is evaluated on startup. The unused alarm files and the current
protocol file are located in the mmc2 directory. The names of these hidden files
(attribute "hidden") consist of an 8-digit hexadecimal number with the extension
".alr". The names of files in which write errors are detected on startup also consist
of an 8-digit hexadecimal number, but with the extension ".al_".
[Alarms]
Records = value ; Size of protocol file
Default value: 150
Minimum value: 18
Maximum value: 32000
With standard value 150, 75 alarms can be displayed. 2 records are needed for
each alarm.
[PROTOCOL]
Filter=Expression
Syntax
[IDENTIFIER][RELATION][FEATURE][OPERATORS]
IDENTIFIER:
• No. Alarm number
• Prio Priority
• Mode Message line/alarm line or dialog box
• Type Alarm type (PowerOn, Cancel, etc.)
• From Source of alarm
• AckVar Acknowledgment variable
RELATION:
• ':' Equal to
• '<' Less than
• '>' Greater than
• '!' Not
FEATURE:
• Numbers
• Strings
OPERATORS
• ',' Comma denotes logical OR, only within
a filter.
• '' Space/blank denotes logical AND between
individual filters.
• '|' Pipe denotes logical OR between individual filters.
Examples:
Filter=Type<3
Only POWERON and RESET alarms are logged.
Filter=From:NCU_1
Only alarms from NCU_1 are logged
Filter=From:NCU_1 Type:1,3
Only POWERON and CANCEL alarms from
NCU_1 are logged
Data transfer from/to NCK with the following properties can be started via the PLC:
• Data transfer from the hard disk in or from the NCK (workpiece directory, part
program, etc.) using job lists.
• The "Job lists" function in HMI Advanced allows full part program handling, such
as loading, unloading, selecting or executing, from the hard disk.
References relating to job lists: /IAD/ Installation and Start-Up Guide 840D,
Chapter 11
/BA/ Operator's Guide MMC 103, Chapter 2
By means of the interface between the PLC and HMI in DB19 the PLC gives the
HMI jobs that initiate a data transfer between the HMI (hard disk) and NCK.
Acknowledgment byte from HMI for the current data transfer status:
Job processing
A PLC job is processed according to the following scheme:
1. The PLC may only initiate a job in the job byte if the acknowledgment byte is 0.
2. The HMI mirrors the job (excluding the parameter set) in the acknowledgment
byte (signaling to the PLC that a PLC job is being processed). The PLC
receives a "job active" signal for an unfinished job.
3. Once the operation is finished (OK or Error), the PLC must respond again and
delete the job byte.
4. In response, the HMI sets the acknowledgment byte to 0.
The PLC sets an index (1-127) via DB19.DBB16, which determines the control file
in which the job list names are stored.
• Define PLC index for the control file (DB 19, DBB16 = 131)
• Define PLC line offset 2 (DB 19, DBB17 = 2)
• PLC job: Load (DB 19, DBB13,6=1)
Job list B is loaded
• HMI signals to the PLC: Job list is loaded (DB19.DBB26,6=1)
Note
This function is not available if the MACHINE operating area is suppressed from
the HMI startup.
0 No error
1 Invalid number for control file.
(value in DB19.DBB16 < 127 or invalid)
2 Unable to read DB19.DBB15
3 Control file /BD.DIR/PLC_IN_OUT_xxx.TEA not found.
(value in DB19.DBB16 invalid)
4 Invalid index in control file.
(incorrect value in DB19.DBB17)
5 Selected job list in control file could not be opened
6 Error in job list (job list interpreter returns error)
7 Job list interpreter returns empty job list
9 Error while executing job list
For example:
[param network]
netmaster= NCU_LEFT
This setting for the netmaster NCU/PLC means that data transfer is only activated
by the NCU/PLC with the symbolic name NCU_LEFT.
Machine manufacturer
See machine manufacturer's specifications.
5.1.3 Informing the PLC of the current HMI task number (HMI
version 6.2 and higher)
Task number
A task describes the position at which an operating area is attached in the HMI
area menu, i.e. the highest level.
The following fixed relationship exists between softkey bars in the area menu and
tasks:
From software version 6.3 and higher, a 4th softkey bar can be used for OEM
applications.
Application
For manufacturer-configured user interfaces, correct concurrence of key strokes on
the machine operator panel and the operating areas/screens displayed is essential.
Example:
The function "Move unit" is selected in a screen form. On the MCP are "forward"
and "backward" traversing keys, which are used to move the unit in real time.
To prevent a new screen from opening before the traversing key movement has
been completed, due to a change of operating area in the HMI for example, the
PLC is always able to know and check the current task number.
Configuration
The current task number is transferred to the PLC in a data block area, which can
be specified in display machine data 9032: HMI_MONITOR as a string in the
following format:
DBxx.DBByy
where:
xx is the number of a data block
yy is the byte number of the 1st byte of the transfer area (word limit)
The transfer area is 8 bytes long.
The transfer takes place in the 1st byte. Bytes 2 to 8 are reserved.
Note
Check that the specified area is not already occupied by input bytes, output bytes
or flag bytes.
Updating
The task number in the 1st byte is updated
Value range
The task number can assume values from 0 to 95, including the operating areas
configured by the user.
All visible tasks in the main menu (0 to 31) and the hidden child tasks (32 to 95) are
therefore displayed.
Another column for the fine offset is inserted alongside the column for entering the
offsets. The inputs are checked against the display machine data
These settings apply to both the actual-value window and the editor window.
Example
In the NC program the movement of axes from X120 Y20 Z-50 to X200 Y200 Z-120
looks like this in binary display:
Function
The NC is operated in program test mode for this block search, so that interactions
between channel and synchronous actions and between multiple channels are
possible within an NCU.
During "Block search in program test mode", all auxiliary functions of the NC are
output to the PLC and the parts program commands for channel coordination
(WAITE, WAITM, WAITMC, Replace axis, Write variables) are carried out by the
NC. This means
Activation
The function is activated by the "Prog.test contour" softkey.
The NC then starts the block search and switches the selected program in the
current channel to program test mode:
• the auxiliary functions of the parts program are output by the NC to the PLC
• no axis movements are executed.
If during the block search the NC finds one of the parts program commands
WAITE, WAITC or WAITMC, the NC waits for the specified partner channels,
regardless of the current mode of these partner channels (e.g. normal program
execution, program test, search via program test, etc.).
When the NC reaches the specified target block in the current channel, the NC
stops the block search and deselects program test mode; the auxiliary functions of
the target block are no longer output.
Dialog message
A dialog message appears as soon as all the channels involved in the current
search have exited program test mode. This message indicates that, depending on
the particular parts program, Repos offsets may have been produced in the
channels involved in the block search during the search and will be retracted by the
NC through interpolation the next time it starts. You must acknowledge this
message.
Any repositioning offsets (in the individual channels) can be executed manually
one by one in JOG mode, before program execution is continued at the point in the
program reached by the block search by pressing the "NC Start" key.
Search configurations
"Block search in program test mode" supports the following configurations:
1. Block search in the currently selected channel
(the currently selected channel is the channel selected by the HMI)
2. Block search in the currently selected channel and in all channels in which
the same workpiece as in the current channel is selected
3. Block search in the currently selected channel and in all channels that are in
the same mode group as the current channel
4. Block search in all channels of the NC
Configurations 2 to 4:
No block search is performed in the other channels (in contrast to the current
channel); in the other channels program test mode is active until a stop condition
(e.g. WAITMC) is detected.
Deactivate function
The following entries are possible in the [BlockSearch] section:
[BlockSearch]
SeruproEnabled
=0 Function inactive
=1 Function active (default)
Language-dependent
If there are more than 2 language options on the control, the "Select language"
softkey can be configured in the main setup screen in order to change languages
via the menu.
With the setting TRUE (Select language) the following values must be added to the
entries in the "[LANGUAGE]" section in the "MMC.INI" file:
LanguageList= ... , GR
FontList= ... , Europe
FontListKO= ... , Europe2
LBList= ... , German
Note
With Select language the first language is not provided as a choice. By listing the
first language in the language list again (and therefore also in the corresponding
font settings) the first language also appears in the language selection menu.
Parameterization
The names of the soft keys are predefined.
Note
A carriage return in the softkey text is created with %n. A maximum of 2 lines of 9
characters each are available.
Examples:
VS7=("Abort", se3, ac1) ;Define softkey VS7 and assign
the text "Abort", the status
"highlighted" and the access level 1.
The properties Text, Status and Access Level can be changed in the methods
while the application is running.
SK.st = Text
SK.se = Status
SK.ac = Access level
where:
Status 1 visible
2 disabled (gray text)
3 highlighted (last softkey used)
Access level 0
...
7
For meaning see Subsection 5.1.8 Access protection.
Access levels
• 0 to 3 are locked by means of a password and
• 4 to 7 by means of keyswitch positions.
The operator only has access to information corresponding to this particular access
level and the levels below it. Machine data is routinely assigned different access
levels.
Note
For information about changing access levels, please refer to
References: /BA/, Operator's Guide
/FB/, A2, Various Interface Signals
Access levels 0 to 3 require the input of a password. The password for level 0
provides access to all data areas. The passwords can be changed after activation
(not recommended). If the passwords have been forgotten, for example, then the
system must be reinitialized (NCK general RESET). This resets all passwords to
the defaults for this software version.
Example:
%_N_SGUD_DEF ; File for global variables
; $PATH=/_N_DEF_DIR
REDEF $MA_CTRLOUT_SEGMENT_NR APR 2 APW 2
; (APR ... read access)
REDEF $MA_ENC_SEGMENT_NR APR 2 APW 2
; (APW ... write access)
REDEF $SN_JOG_CONT_MODE_LEVELTRIGGRD APR 2 APW 2
M30
The file becomes active when the next _N_INITIAL_INI is read in. Different access
levels are specified for writing (changing) or reading (parts program or PLC).
Example:
MD 10000 is protected by access levels 2/7, i.e. writing requires access level 2
(corresponding to password) and reading requires access level 7. In order to
access the machine data area, key switch position 3 or more is required.
Function
Channel-specific MD 20098 DISPLAY_AXIS can be used to hide axes in the
Machine operating area.
All axes are displayed by default.
Axes can be hidden in the following windows in the machine area.
In this way you can specify separately for the view in the machine or workpiece
coordinate system whether or not the axis is displayed:
Bits 0 to 15 Show (=1)/hide (=0) geometrical axes (WCS)
Bits 16 to 31 Show (=1)/hide (=0) machine axes (MCS)
20098 DISPLAY_AXIS
MD number Display or hide axis on MMC/HMI
Default setting: 0xFFFFFFFF Minimum input limit: 0 Maximum input limit:
0xFFFFFFFF
Changes effective after POWER ON Access level: 2/7 Unit: -
Data type: DWORD Applies from version 4.4
Meaning: Bits 0 to 15: WCS
Bit 0= 1 Show geometrical axis in actual-value windows
0 Hide geometrical axis in actual-value windows
Bit 1 1 Show geometrical axis in reference point windo
0 Hide geometrical axis in actual-value windows
Bit 2= 1 Show geometrical axis in preset/base
offset/scratching/zero offset window
0 Hide geometrical axis in preset/base offset/
scratching window
Bit 3= 1 Show geometrical axis in handwheel selection window
0 Hide geometrical axis in handwheel selection window
Special cases
• Reference point approach and Safety Integrated
MD 20098 DISPLAY_AXIS is not evaluated in the displays for referencing
mode, i.e. in the axis reference point and acknowledge safe position display. All
machine axes are always displayed.
Therefore the operator cannot change the values for the base zero offset without
the appropriate access authorization.
Function
• Via the MD you can define whether the actual values are to be displayed
• without programmed offset = WCS or
Example:
Program WCS display SZS display
....
N110 X100 100 100
N120 X0 0 0
N130 $P_PFRAME=CTRANS(X,10) 0 0
N140 X100 100 110
N150 ...
Machine manufacturer
To set the actual-value display:
see the machine manufacturer's information.
Function
Display machine data 9440: ACTIVATE_SEL_USER_DATA can be used to ensure
that the active tool offset is activated as soon as the parts program is in the "Reset"
or "Stop" state.
! Caution
The offset is applied after NC Start of the Reset in response to the next
programmed axis movement in the parts program.
SYSLOCK V2
The SYSLOCK program is used for the basic detection of boot sector and partition
table viruses. This takes advantage of the fact that for technical reasons all viruses
of this type must install themselves in a memory area just below the 640 KB limit.
These viruses then manipulate the BIOS so that it reduces the available memory
and displays it as 639 KB, for example.
The SYSLOCK driver uses this characteristic to detect a virus infection. In this way
both known viruses and those not yet identified by the usual virus scanners can be
detected.
This requires a full virus scanner product (e.g. Trend OfficeScan from Trend Micro,
Inc.).
Virus alarm
If the program detects that the size of the main memory has changed since it was
first initialized, a virus alarm and the following system responses are initiated:
If a virus message is received, the system must be checked and disinfected with a
full virus scanner. The conventional procedure should be used for disinfecting boot
viruses:
5.1.14 Cross-channel status display with icons (version 6.2 and higher)
Function
The status of
• channels
• spindles
• machine states (if applicable) or
• of machine states only
Activation
The function is activated by MD 9052 SHOW_CHANNEL_SPANNING_STATE > 0.
SINUMERIK icons
The following SINUMERIK icons are available (name in brackets):
Channel status
Dimensions
The dimensions of the SINUMERIK icons are as follows:
Resolution 640x480: 16x16 pixels
Resolution 800x600: 20x20 pixels
Resolution 1024x768: 27x26 pixels
Colors
TrueColor
Note
When using the "Reversible spindles" or "Axis container" functions, the spindle
status is output before the spindle reversal or assignment to axis/spindle
container, i.e. the spindle number displayed under spindle status is the "logical"
spindle.
A.
SINUMERIK status display
The following four predefined displays are available:
• Channel status (active, stopped, RESET) with superimposed spindle stop and
feed stop
• Channel status (active, stopped, RESET) with superimposed feed stop
• Channel status (active, stopped, RESET)
• Spindle status (rotation left, rotation right, spindle stop, spindle halt M05)
Display 1
The channel status, feed stop and spindle status are output as an icon at the
display position. The channel status icons can be superimposed with the "Spindle
not enabled" or "Feed not enabled" icon. The following hierarchy applies (from
highest to lowest priority):
Syntax:
Display 2
The channel status and spindle status are output as an icon at the display position.
(Spindle status can be output separately, for example, see "Display 4"). The
channel status icons can be superimposed with the "Feed not enabled" icon. The
following hierarchy applies (from highest to lowest priority):
Syntax:
Display 3
The channel status is output as an icon at the display position. (Feed stop is also
output in the feed window in the machine operating area, for example).
Syntax:
Display 4
Note
• Empty positions need not be specified.
• Predefined status displays can be switched off in the HEADER.INI file in the
OEM or USER directories with the value <empty>, e.g.
ChanStatFeedStopSpindleStop = <empty>.
• The complete HEADER.INI file can be found in Section 5.7.
16 display positions
There are 16 display positions defined in the program status line (header), each
SINUMERIK icon occupying two positions: number + icon.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
1
Fig. 5-1
The SINUMERIK icons are assigned to a fixed output position. A section is created
in the HEADER.INI configuration file for each position used.
Sample view of the program status line with SINUMERIK icons for 4 channels and
2 spindles:
S1 S2
Fig. 5-2
Example:
The status displays for 2 channels and 1 spindle should always be output at the
first, third and fifth display position.
HEADER.INI file:
[Pos1] ; first display position
ChanStatFeedStopSpindleStop = 3
Spindles=1,2 ; channel status of channel 3 is displayed,
; superimposed with feed disable for channel 3 and
; spindle disable for spindles 1 and 2
[Pos3] ; third display position
ChanStatFeedStop = 2 ; channel status of channel 2 is displayed
; superimposed with feed disable for channel 2
[Pos5] ; fifth display position
SpindStat= 3 ; spindle status for spindle 3 is displayed
The following display, for example, appears in the program status line:
S3
Fig. 5-3
Deactivation
Icon displays configured in this way can be deactivated if user status displays are
used as described in B. Create empty entries in a user-specific HEADER.INI file
(not in the HMI_ADV directory, because it will be overwritten again when the
software is upgraded).
Example:
[Pos5]
SpindStat=<EMPTY>
B.
User status display
Additionally (or alternatively), PLC-controlled (DB x, DBB y) user icons can be
output, which are linked to specific machine states.
Procedure:
1. Enter the name of the user icons and the associated positions in the
HEADER.INI file in the UserIcons section under identifiers UI_0 to UI_31.
[UserIcons]
UI_0= <Icon_00.bmp> , <Position>
; UI_0: Identifier
; Icon_00.bmp: Name of user icon (8 characters.bmp)
; Position: Display position (1 to 16)
...
UI_31= <Icon_31.bmp> , <Position>
USER_ICON_BASE = DBx.DBBy
Further on in the UserIcons section:
DBx.DBBy: User-specified double word for controlling icon
selection.
If a bit is set for a user icon, the associated UI_x entry must exist,
otherwise nothing is displayed.
To display an icon according to the above agreement, the PLC sets the
corresponding bit in the double word. For example:
Example:
UI_3=Icon_01.bmp,12.
Setting bit 3 displays the icon "Icon_01.bmp" at position 12 if no other icon with a
higher identifier (>UI_3) and the same position (,12) is active.
Possible applications
• 32 alternative images for a position, each selected with a different bit (currently
only one active selection bit)
• 2 alternative images for each of the permissible 16 positions, each position
requires 2 of the 32 selection bits
(maximum 16 active selection bits at any one time)
• Combination thereof with a total of max. 32 images for the max. 16 positions
(max. 16 active selection bits at any one time)
• More than 16 selection bits, see Superimposition
Superimposition
With non-unique selection (bits for multiple identifiers whose image is to be
displayed at the same position):
The image with the lower identifier number is superimposed with the image with the
higher identifier number for the same position. Non-unique selection can also be
used with less than 16 active selection bits. The PLC can deliberately use this
superimposition to overlay less important displays (with lower identifier numbers)
with important displays (high identifier numbers).
Note
If two HMI units are assigned to one NC/PLC unit (M:N), the PLC must first
determine from the control interface which of the HMI interfaces is active. Icons
can only be requested by the PLC for the active HMI unit.
9052 SHOW_CHANNEL_SPANNING_STAT
MD number Change cross-channel status display
Default value: 0 Min. input value: 0 Max. input value: 1
Changes effective after POWER ON Access level (R/W) 4/1 Unit: -
Data type: STRING Applies from version 6.2
Meaning Cross-channel status display:
0 = Display previous program status in header
1 = Display in program status line in header according to configuration
in Header.ini file.
9033 MA_DISPL_INVERT_DIR_SPIND_M3
MD number Spindle direction display
Default value: 0x0000 Min. input value: 0x0000 Max. input value:
0x7FFFFFFF
Change effective after: IMMEDIATE Access level (R/W) 3/4 Unit: -
Data type: LONG Applies from version 6.2
Meaning Spindle direction display:
Bit[n]=0 M3 displayed as clockwise rotation in the icon
Bit[n]=1 M3 displayed as counter-clockwise rotation in the icon
n = spindle number –1 (i.e. bit 0 is spindle S1)
Note:
With the corresponding setting for MD 9014:
USE_CHANNEL_DISPLAY_DATA
MD 9033 can be managed channel specifically in the NC.
Text length
The maximum length of the texts to be displayed is 30 characters per line.
Syntax
The texts can consist of
• one language-specific part (from the alarm/message text file *.COM) and
• 3 parameters (%1, %2, %3)
User PLC-DB
The display is configured via a user PLC-DB.
• The number of the DBx with DBBy should be entered by the user in the
HEADER.INI file as follows:
[UserTextInfo]
USER_TEXT_BASE=DBx.DBBy
where x = data block number, y = first byte in block. See Chapter
If this interface is specified, the text length limit
Textlength = 33
must also be activated.
• The name of the PLC alarm text file (e.g. "alpu_") should be entered by the user
in the MBDDE.INI file in the [TextFiles] section under "UserPLC":
[TextFiles]
UserPLC=alpu_
can be output.
If "00" is written to a byte in text input,
the HMI evaluates this as the end of the text. Inputs after this "00" are not
displayed.
Table 5-5 User PLC-DB interface for displays in the program path/program name line
Program Start DBBx Start DBWx Start DBBx Start DBBx Start DBBx +
path line +1 +3 +4 5-17
Data type Byte Word Byte Byte String
Meaning Bit0=1: there is Offset for text Number from Index from Character string
something to from 0 to 255 –127 ...128 max. 12
do alpu_xx.com (corresponds negative characters
all bytes=1: job is to be to number (corresponds
acknowledged by (-1=0xFF, -2=0xFE) to 3rd
displayed, 1st parameter
HMI is machine axis
700000 is base %1) parameter
all bytes=0: PLC index,
address and is
can write to
always summed positive number %3)
interface again
internally is channel axis
=0: Delete line index
The index is
then converted
to an axis name
before being
displayed.
(corresponds to
2nd parameter %2)
Program Start DBBx Start DBWx Start DBBx Start DBBx Start DBBx
name line +20 +21 +23 +24 +25-37
Data type Byte Word Byte Byte String
Meaning As above As above As above As above As above
Start DBBx
HMI detects a job and acknowledges it (all bytes=0).
Start DBWx+1
Start DBWx+1 contains the offset for a text number based on 700,000 (user PLC
texts). If this parameter = 0, the corresponding line is deleted.
Start DBBx+3
Start DBBx+3 contains a number that is displayed without being converted.
Start DBBx+4
Start DBBx+4 contains an axis index.
• Negative value = machine axis index (AXCONF_MACHAX_NAME_TAB
[ Index-1], MD 10000),
• Positive value = channel axis index (AXCONF_CHANAX_NAME_TAB
[ Index-1], MD 20080),
These indices always refer to the channel currently displayed in the HMI. The index
is converted to an axis name before being displayed.
Start DBB+5
Start DBBx +5 to +17 contains a character string comprising a maximum of 12
characters.
Note
Bit0=1 can only be set in Start DBBx for a new job if
• all bytes from the previous job were reset to zero and
• the parameters for the new job Start DBBx+1 to Start DBBx+5 have been set
correctly.
• Special characters that have a special meaning within the syntax for this
function (", %, $, #) must not appear within the user's character string (Start
DBB+5…).
The data for the program name line (second line) are located 20 bytes after the
start byte.
Response in M:N
In the M:N function the two text lines must be cleared in passive switching.
Example
Task
In JOG and MDA modes the following texts should be output in the "Program
name" field in the header:
• "Handwheel acting on axis …" in the first line with the appropriate axis name
• "Slide … active" in the second line with the appropriate slide number.
Procedure
1. Identify the PLC-HMI interface in the HEADER.INI file, e.g. DB60.DBB10
4. Initiate text display from the PLC and describe the interface, e.g. for the first
display line:
DB60.DBW11 = 100
DB60.DBB14 = 2
DB60.DBB10 = 1
e.g. for the second display line:
DB60.DBW31 = 101
DB60.DBB33 = 1
DB60.DBB30 = 1
Result
With the following axis configuration:
MD 20080 AXCONF_CHANAX_NAME_TAB[0] = "X"
MD 20080 AXCONF_CHANAX_NAME_TAB[1] = "Y"
MD 20080 AXCONF_CHANAX_NAME_TAB[2] = "Z"
the display is as follows:
Channel selection
Channel selection and display is initiated as follows (display in "Channel name"
field):
Spindle selection
Spindle selection is initiated as follows (display in spindle window):
Error identifiers
The following error codes, which identify errors in the function request from the
PLC to the HMI, are stored in DB 19, DBB 36:
Value Meaning
0 No error
1 No function number (DBB32 bit 0-5)
2 Invalid parameter
3 Error when writing HMI-internal variable
10 Channel not present (DBB33)
• The PLC sets bit6 to 1 "Function request". The function request can only be set
by the PLC if bits 6 and 7 have the value zero.
• After displaying the text in the header the HMI writes zero again in bit 6 and the
interface is enabled for the PLC for the next action.
Note
If two HMI units are assigned to one NC/PLC unit (M:N), the PLC must first
determine from the control interface which of the HMI interfaces is active.
Channel/spindle displays can only be requested by the PLC for the active HMI
unit. The interface for selecting channel/spindle displays for the 2nd HMI unit is
located in DB19, DBB82-86. The use is the same as described for DBB32-36.
• Using the "Skeleton application" function, existing operating areas used in HMI
Advanced can be combined and selected with a new softkey – simply by
means of configuration. This releases operating areas/softkeys in the main
menu for dedicated operating areas (OEM applications).
When you leave an operating area that was selected from a skeleton application,
you return to the higher-level menu of the skeleton application.
The following standard applications can be selected from a skeleton application:
• Machine
• Parameters
• Services
• Program
- Simulation
- HMI settings
• Diagnostics
• Startup and
• OEM applications
A skeleton application can provide its own home screen as a bitmap file or display
a standard image.
Configuration principle
New operating levels are created by skeleton applications and attached to existing
operating levels. The assignments of horizontal and vertical softkey bars to
skeleton applications can be configured.
Configuration files
Configuration is carried out in the following files:
REGIE.INI
TASKCONF.INI
RE_xx.INI
Examples
The following sample entries should clarify the procedure:
REGIE.INI
Skeleton application for user-specific operating trees. See also 6.6.14
; Sample entry
The task number (7 in this case) is assigned to the softkey that calls the skeleton
application.
Task0: Horizontal softkey 1
...
Task7: Horizontal softkey 8
mntmmc is the name of a standard task for interpreting the softkeys in the
skeleton application in TASKCONF.INI and for activating them.
The value of cmdline indicates the section in the TASKCONF.INI file in which the
softkey assignments in the skeleton application are described in detail.
There may be more than one Task<No.>= name := mntmmc, ... entry if several
sections in TASKCONF.INI have been defined with skeleton application
parameters. This also allows operating trees to be designed with multiple levels.
TASKCONF.INI
[SectionName1]
; REGIE.INI must contain a reference to the freely selectable section name.
; Sample entries:
; The Services application should be activated when the skeleton
; application is started for the first time
; The StartIndex entry specifies the softkey index that activates the
; desired task when the program is started
; Services with StartIndex 5 in this example
StartIndex = 5
; Home screen for the skeleton application, for more details see below
Picture= Skeleton1.bmp
; the first softkey is assigned the Program task (task index 2) as child (Hsk1IsTask=0)
; with the <root> parameter, the softkey texts specified for German (via default)
; and English (UK)
Hsk1Task=2
Hsk1IsTask=0
; the fifth softkey is assigned the Services task (task index 3) as child (Hsk1IsTask=0)
; with the empty command parameter, the softkey texts specified for the default German
; (_GR) and English (_UK)
Hsk5Task=3
Hsk5IsTask =0
Hsk5Command=
Hsk5SkText=SERVICES
Hsk5SkText _GR=Services
Hsk5SkText _UK=service
; the 2nd softkey in the ETC bar is assigned the Setup task (task index 5) as child
; (Hsk10IsTask=0) with empty command parameter,
; the softkey texts specified for German (_GR) and English (_UK)
Hsk10Task=5
Hsk10IsTask=0
Hsk10Command=
Hsk10SkText _GR=setup
Hsk10SkText _UK=setup
Language-dependence of softkeys
The softkeys are labeled according to the current language setting. The softkeys
are updated whenever the language is changed. If the softkey text for the current
language (Hsk<SoftkeyIndex>SkText_<Language>=...) is not found, the softkey is
assigned the default text (Entry (Hsk<SoftkeyIndex>SkText=...) or, if there is no
default text, the task index.
Picture=BackgroundSkeleton1.bmp
The screen is displayed when the skeleton application is selected or on return from
an application called by the skeleton application. Entering 1 rather than a picture
file causes the "Setup" screen to be displayed (default).
Note
If StartIndex and a picture are configured, the picture is superimposed as soon
as the skeleton application is selected and the application configured with
StartIndex opens. If the picture is larger than the window available in the current
operating device, the part from the center of the picture that fits in the window is
displayed.
Access authorizations
The softkeys in the skeleton application can be secured with access authorizations.
0: System
... ...
7: Keyswitch position 0
; Example:
; Access authorizations for the "Services" softkey
Hsk5AccessLevel= 3
NCK-dependent softkeys
With
Hsk<SoftkeyIndex>NckLink=1
in the corresponding softkey entries in TASKCONF.INI a softkey can be bound to
the existence of an intact connection to the NCK. The softkey can then only be
used when the connection exists. Default is 0: no check.
Exit button
An exit button can be configured to close the entire HMI operating area. It is
defined in TASKCONF.INI in the section for the corresponding skeleton application.
In the example below the exit button is assigned to the 8th softkey in the ETC bar.
Hsk16Task=ExitButton
Hsk<SoftkeyIndex>Task= x/y
x Operating area
y Command or state= i
Example:
Hsk1Task=Program/<root>
Hsk1Task=2
Hsk1IsTask=0
Hsk1Command=<root>
Hsk1SkText=Program
x y Explanation
Machine <root> Go to the Machine home screen (task 0) with recall to
the highest level for return. The softkey text is Machine.
Parameters <root> Go to the Parameters home screen (task 1) with recall
to the highest level for return. The softkey text is
Parameters.
Program <root> Go to the Program home screen (task 2) with recall to
the highest level for return. The softkey text is Program.
Service <root> Go to the Service home screen (task 3) with recall to the
highest level for return. The softkey text is Service.
Diagnostics <root> Go to the Diagnostics home screen (task 4) with recall
to the highest level for return. The softkey text is
Diagnostics.
Diagnostics State=10 Go to the Diagnostics home screen with recall to the
highest level for return and selection of the alarm
screen. The softkey text is Alarms.
IBSetup <root> Go to the Settings home screen (task 34) with recall to
the highest level for return. The softkey text is System
settings.
Simulation <root> Go to Simulation (task 27). A modal dialog is opened
which is used to select the program to be simulated. The
simulation is aborted by pressing Cancel. The softkey
text is Simulation.
The following commands should be noted to the right of the equals sign in the
softkey command definition:
Hsk<SoftkeyIndex>Command=Commando1; Commando2; ... or
Vsk<SoftkeyIndex>Command=Commando1; Commando2; ...
Example:
; Hide some softkeys in the horizontal softkey bar for
; standard operation
Hsk1Command=DisableHsk(1, 3-4)
Commands:
DisableHsk(<SoftkeyList>)
The horizontal softkeys are removed from the softkey list. Individual softkeys can
be separated by commas or softkey ranges <from> - <to> specified, e.g.
DisableHsk(1,3,5-7).
Note
Softkeys in the ETC bar cannot be removed.
DisableVsk(<SoftkeyList>)
The vertical softkeys are removed from the softkey list. Individual softkeys can be
separated by commas or softkey ranges <from> - <to> specified, e.g.
DisableVsk(1,3,5-7).
DoVsk=<SoftkeyIndex>
The action of the vertical softkey (1-8) is initiated.
Recall(<StatusList>)
On reaching a status from the list the application returns to the calling application.
The statuses can be separated by commas or specified as ranges <from> - <to>,
e.g. Recall(1,5-7,48).
Highlight=<SoftkeyIndex>
The horizontal (1 – 8) or vertical (9 – 16) softkey is displayed with a blue
background when the application is called.
ZuMat=<StatusMatrix>
The status matrix (e.g. dg\dg.zus) transferred is read and replaces the original
status matrix.
RE_GR.INI
[HSoftkeyTexts]
HSK7 = "Special menu" // 20
! Important
You must save all relevant data before changing the memory sizes or
reconfiguring the memories.
! Important
Direct changes to objects stored in the DRAM and saved in the FFS are not
enabled. Only cycles should be specified for saving in the FFS.
Any changes that are required must be made before loading onto the HMI.
Direct changes to objects in the DRAM that are not saved on the FFS are
lost on Power Off.
By default, zip files in the data management system (DM directory) and in the
subdirectories of the HMI installation directory (hmi_adv, mmc2) are opened.
If you also want to include user-specific images for layout-dependent displays, they
must be placed in a zip archive for each layout variant. Details of user-specific
images are configured in the LAYOUTSW.INI file. See 5.6.20.
The LAYOUTSW.INI file with user modifications can be stored in the oem or user
directories.
The following details must be entered in the [all] section in LAYOUTSW.INI for
each layout variant:
• The number of DLLs (applies to both layout variants)
• The number of directories in which there are archives to be opened in the data
management system DM (applies to both layout variants)
• The number of HMI directories in which there are archives to be opened in the
user or oem directories (applies to both layout variants)
together with the directories in the [Directories] section in which the archives for
the images in the DM area and the images in the HMI area in user/oem are
located.
In the [Design_x] section (where x = 0 for New Design and x = 1 for Classic
Design) the following details are specified:
• DLLs to be used
• files to be opened
• the screen color depth to be set
Files to be opened:
The information is specified in the following entries:
HMI_ZipName_i = *.zip where i = running number 0, 1, 2, … and
DM_ZipName_i = *.zip where i = running number 0, 1, 2, …
[SIG2].
.
.
[SIG<n>]
.
.
NrOfSignals:
Number of additional signals. The signals are located in the [SIG<nr>] section,
where <nr> goes from 1 to NrOfSignals (continuously and with no gaps).
Text:
either
language-specific text in the form $T<TextNr>
where <TextNr> is a number in the language-specific ini file DgOvw_xx.ini (where
xx is the language abbreviation).
or
non-language-specific text "<any text>".
"<any text>" is expressed exactly as it is written in this ini file.
expr:
This can be an IF statement or a bitmap assignment.
Syntax:
expr=<IF_Statement> or
expr=<Bmp_Assignment>
<Statement>::= <EntryName> or
<Statement>::= <Bmp_Assignment>
<BoolExpression>::= <Val> or
<BoolExpression>::= <Val><OP><Value>
<Val>::= # or
<Val>::= #.<BitNr>
<BitNr>::=Bit number to be evaluated (0..31)
<OP>::= < , > ,= ,>=, <=, <>
<EntryName>::= any name, which must be defined in the same section as expr. It
is treated in the same way as expr.
[BMP]
Any internal bitmaps can be specified in this section. The first bitmap in the [BMP]
section must have number 100, the second 101, etc.
The name must be specified in double inverted commas. If no path is stated, the
system searches for the bitmap in mmc2 or addon, oem, user…, otherwise in the
stated path.
[GLOBAL]
NrOfSignals=1
[BMP]
100=“test.bmp“
101=“c:\tmp\test2.bmp“
[SIG1]
text= “Measuring system 1 active“
Item= /Nck/MachineAxis/encChoice[u1, <AX>]
expr= if #=1 then BMP=100 else expr2
expr2= if #=0 then BMP=101 else BMP=2
Files used
On initialization/startup of simulation HMI Advanced reads the following files (if
present) from the data management directory \DP.DIR\SIM.DIR:
Booting
The above files, if present, are read when the simulation application boots.
Of the initialization data INITIAL.INI, only the machine data are read by the
simulation application during booting.
The files (CH(c)_xxx.INI, NC_xxx.INI and AX_SEA.INI) are read in date stamp
sequence, starting with the oldest file.
DPCUSCYC.COM:
The file DPCUSCYC.COM (mapping of user cycle interfaces) is only read if in the
DPSIM.INI file in the [PRELOAD] section
CYCLES=0 or
CYCLEINTERFACE=1 is set.
Note
The CMA.DIR directory (manufacturer cycles) only exists from version 5.3/6.1
and higher.
NC cycles
The NC cycles (CUS.DIR, CMA.DIR and CST.DIR) are copied as an image into the
corresponding directories in data management. The location is determined in the
DPSIM.INI file by the CYCLE entry (\DP.DIR\SIM.DIR) in the [MAIN] section.
Matching takes place on starting the HMI and with every cycle match. This
provides optimized access to the cycles and automatic creation of the images of
the cycle interfaces.
By default the first 3 geometrical axes are displayed. In addition, any other channel
axes can also be displayed. Assignment takes place in the [LINKS] section
[LINKS]
ACT_POS_DISPL_1=1
ACT_POS_DISPL_2=2
ACT_POS_DISPL_3=3
ACT_POS_DISPL_4=0
ACT_POS_DISPL_5=0
Value = 0 The associated space in the display is freed
Value = 1 The associated default geometrical axis is displayed
Value = 1 to n Geometrical axis is displayed
(n = 1 to number of generated axes)
Formatting
For the formatting of the axis values the number of digits (3 to 15) can be specified.
[LINKS]
ACT_POS_DIGITS=10
The number of digits after the decimal point (maximum number of digits) is read
from the simulation initialization data via MD 9004 DISPLAY_RESOLUTION or
MD 9011 DISPLAY_RESOLUTION_INCH.
Hiding axes
From NC software version 5.3, the geometrical/channel axes can be hidden via
MD 20098 DISPLAY_AXIS. Bit 0 (display in the actual-value windows) is evaluated
for the simulation.
As a maximum, as many axes can be displayed with their values that are not
hidden with ACT_POS_DISPL_<x> with 0, i.e. as a maximum the first 5 unhidden
geometrical/channel axes in sequence.
Note
The more space that is required to display the axes, the less space is available to
display the actual block. Axis display can optionally be switched off from the
Settings/Options on/off menu in the "Actual position" field (within the Display
options field).
Search strategy
If a program (with no path) is required by the simulation, the following directories
are searched:
1. File in current NCK workpiece directory
2. File in current HMI Advanced workpiece directory
3. File in NCK subroutine/main program directory
4. File in HMI Advanced subroutine/main program directory
5. File in NCK user cycle directory
6. File in HMI user cycle directory
7. File in NCK manufacturer directory
8. File in HMI manufacturer directory
9. File in NCK standard cycle directory
10. File in HMI standard cycle directory
If a program is not present in the simulation, it is loaded from the NC or from the
HMI.
All programs (apart from cycles) that are loaded into the simulation are deleted
from the simulation again in the event of a workpiece change. If one of these
programs is needed again by the simulation, it is reloaded.
Program selection
If a parts program for a workpiece is selected for the simulation, the following
actions are executed:
1. All tools are cleared with the file TO_CLEAR.INI (in HMI_ADV\DP\SIM) (if
present).
2. If WPD_INI_MODE is set to 1 (see point 5) and if a TOA file with the selected
program name exists in the workpiece directory, this file is loaded into the
active file system for the simulation (otherwise file TO_INI.INI if it exists in the
data management system in \DP.DIR\SIM.DIR).
3. If tool management is active, the file TO_ADDON.INI (in HMI_ADV\DP\SIM) is
also loaded into the simulation and executed.
4. Workpieces: an initialization file with the workpiece name is loaded into the
simulation
5. Workpieces:
• MD 11280 WPD_INI_MODE = 1
All files (RPA, GUD, SEA, UFR, PRO, CEC, TMA) with the part program names
are loaded into the passive file system in the simulation. Program-specific TOA
files are loaded directly into the active file system for the simulation, all tools are
first cleared and then, if tool management is active, the file TO_ADDON.INI (in
HMI_ADV\DP\SIM) is loaded into the simulation and executed.
The parts program is then loaded into the simulation and selected.
If another parts program from the same workpiece is selected for the simulation, it
is loaded into the simulation together with the associated data (if MD 11280
WPD_INI_MODE = 1) and then selected.
If a parts program from another workpiece is selected, the previous workpiece is
removed from the simulation.
If a workpiece is selected for the simulation, the parts program with the workpiece
name is loaded into the simulation together with its data and the workpiece
selected. If the parts program with the workpiece name does not exist, an error
message is output.
Channel change
Only one channel/program at a time can be simulated in the simulation, i.e. direct
synchronization across channels is not possible.
The preset channel is channel 1 or the first channel in the simulation. Before
programs are selected, the simulation is switched to the channel for the current
program.
MD 11280 WPD_INI_MODE = 1:
The system checks whether a TOA file with the current program name exists. If it
does,
All files (RPA, GUD, SEA, UFR, PRO, CEC, TMA) with the part program names
are then loaded into the passive file system in the simulation.
The programs in the channel/spindle list are executed one at a time in the specified
sequence with each "NC start" of the simulation; with each program change the
graphics status is retained as a blank specification for the next program. Hidden
programs are skipped.
After the last program the graphic is cleared – after prompting – and the simulation
starts again with the first program.
User programs
All programs currently copied into the simulation are displayed. They are deleted
from the simulation again when a different workpiece is selected.
Changes to these programs via the compensation editor are made directly in the
HMI or NCK, and the modified programs are automatically copied into the
simulation. If these programs are modified externally (e.g. via Services), the
change is detected at the time of the next simulation selection and the programs
concerned are copied into the simulation.
If files exist for the current workpiece (extension RPA, GUD, SEA, UFR, PRO,
CEC, TOA, TMA), they are loaded into the simulation when the workpiece is
selected. These files are retained when the workpiece is changed and their date
stamp is monitored.
If these files are modified externally (e.g. via Services/Programs), the change is
detected at the time of the next simulation selection and the files concerned are
automatically loaded into the passive file system for the simulation.
User cycles
All user cycles loaded into the simulation are displayed. If the cycles have not been
loaded before, the cycle interfaces must be defined in the file DPCUSCYC.COM.
The cycles are then copied into the simulation when required. Changes to the
cycles are not detected automatically and must be detected by means of the
"Match cycles" softkey.
With the expansion of the geometrical tool data, it is now possible to show only the
cutting edge ("flying edge") in the simulation image, without the shaft and holder.
Additional/deviating parameters can also be incorporated into the simulation on a
tool-by-tool basis.
Other requirements
Note
- Tools are still displayed in the 3 main planes, XY, YZ or ZX.
- If a tool cannot be displayed, a polymarker is displayed.
- With the SimToGeo.ini file the tool_type can be defined differently from the
NC settings. If the corresponding cutting edge parameters (e.g.
$TC_DPCS1[t,d]) can be set, a link to/evaluation by SimToGeo.ini geometrical
data is also possible.
- A complete sample file with entries for each permissible tool type can be found
in Subsection 5.6.10.
MD 18206: MM_NUM_CCS_TOA_PARAM=1
; Number of OEM data per cutting edge 0 to 10
MD 18204: MM_TYPE_CCS_TOA_PARAM[0]=4
; Data type 4 = Real
MD 18080: MM_TOOL_MANAGEMENT_MASK='H4'
; Set aside memory for OEM data
Startup procedure
[SETUP]
;*** only SW6.4 or later ***
;Display tool only as cutting edge-"flying edge" (on/off)
TOOL_AS_CUTTING_EDGE=ON ;default = OFF
or
3. Set up SimToGeo.ini:
Define link entry for Siemens or User OEM parameter and expand geometrical
data.
This is done using the OEM variable ($TC_DPCS1/$TC_DPC1).
The value of this variable determines the geometrical block that is used.
For example, the entry for tool 1 cutting edge 1 (T1D1) $TC_DPCS1[1,1]=500.1
would be referred to the geometrical data block [500.1] in the SimToGeo.ini file.
It is possible for more than one tool to refer to the same geometrical data block.
[Settings]
Link=TC_DPCS1 ; Link to TO_INI.INI, Siemens OEM
;Link=TC_DPC1 ; Link to TO_INI.INI, USER OEM
Note
The data can be adjusted manually using the editor in the SERVICES operating
area, but if improper changes are made there is a risk that the simulation will not
be able to start. You should therefore save the files systematically in case the
data cannot be retrieved from the NC.
Note
If you do not wish the definition files in the data management directory to be
matched with the NC, you can set this in DPSIM.INI.
[MAIN]
MATCH_NCU_ENVIRONMENT=0
; Only the INITIAL.INI file is copied from the NC.
MATCH_NCU_ENVIRONMENT=1 (default)
; Definition files in the
; data management directory are also matched with the NC.
Match cycles
Cycle changes are not monitored by the simulation. Cycles are
If a cycle is changed, it must be copied into the simulation using the "Match cycles"
softkey. Only cycles that have changed since they were last accessed are copied
into the simulation (along with newly imported cycles). Cycles in the simulation that
have since been deleted are deleted from the simulation. If an automatic cycle
interface is not used, the simulation must be restarted.
• R parameters (RPA)
• User data (GUD)
• Global user data
• Zero offsets (UFR)
• Global zero offsets
• Setting data (SEA)
• Global setting data
• Axis-specific setting data
• Protection zones (PRO)
• Sag/angularity (CEC)
The data can be selected in any combination. The channels are selected using
softkeys (if there is more than one channel for simulation); the current channel is
offered as default.
Channel-specific data are only offered if the selected channel is present on the
NCK.
The selected data are copied into corresponding files in the data management
system in \DP.DIR\SIM.DIR using the "OK" softkey and loaded into the simulation.
Existing files are overwritten without prompting.
If data are selected for all channels, any associated channel-specific files that are
present are deleted; channel-specific files are always created or overwritten.
Before the data are loaded into the simulation, a "channel reset" is performed for
the simulation.
If an error occurs when copying from the NCK, the transfer can be repeated or
aborted (Abort/Repeat dialog box). If an error occurs when loading into the
simulation or a simulation alarm is triggered, the transfer is aborted.
Pressing the "OK" softkey saves the current data selection and displays it again the
next time the dialog box is opened.
Mirroring tools
Differently oriented tool carriers (e.g. in different NC channels) can be used in the
same machine tool, for which the TOA length compensation parameters are
subject to machine tool-specific frame transformations (e.g. MIRROR) and have to
be specified differently from the usual settings.
To support this arrangement in the orientation of graphics tools, the SIM graphics
module DPSMASCH.DLL has been expanded to include, among other things, an
almost universal evaluation of the TOA parameters. For example,
$TC_DP3[n,m]=... can also be evaluated with negative values, with the
convention that by default, positive lengths generally lead to machining "behind
the turning center" and negative lengths to machining "in front of the turning
center".
Special NC instructions may also be needed in the corresponding user cycles for
tool carrier selection to ensure that the simulation proceeds with the correct
orientation of the graphics tools, e.g.
...
IF $P_SIM
$SC_MIRROR_TOOL_LENGTH=1 ; tool length compensation
mirror mirrored axes in SIM
ENDIF
...
Use (milling and lathe version):
The sign-compliant evaluation of the TOA parameters at the interface to the
graphics module means that no operator action is required.
The INI entry [VIS] PLANE_VIEW=.. (in ..\user\dpmwp.ini for the milling version
and dptwp.ini for the lathe version) can be modified for this purpose.
In order for advantage to be taken of these possibilities in machines that differ from
the standard orientations,
• the value range for the entry has been published (B/F: back/front, U/D:
up/down, L/R: left/right) and
• the lathe functions (including the resulting views: external, half section, full
section, surface area) expanded accordingly (wire-frame model retained as
before).
• In some cases (lathes) the entries have been made directly accessible from
the user interface:
[VIS]
..
;Plane viewpoint default for standard milling: BDL(BackDownLeft)
;possible BDL, BUL, BUR, BDR, FDL, FUL, FUR or FDR
PLANE_VIEW=BDL
or
[VIS]
..
;Plane viewpoint default for standard horizontal lathes: BDR(BackDownRight)
;for vertical lathes with +Z upward: BDL or with +Z downward: FUL (*** from SW5.3
***)
;possible BDL, BUL, BUR, BDR, FDL, FUL, FUR or FDR
PLANE_VIEW=BDR
Note
Entries other than BDR, BDL or FUL are of no use for lathes at present.
Using the "Change default" softkey the adjustments made here can also be used
as a permanent reference for all new workpieces.
Optimizations
1. "Unwinding diameter surface area" input monitoring
In the lathe version, in conjunction with the blank inputs, the consistency of the
"External diameter" and "Unwinding diameter surface area" parameters is
checked and if necessary adjusted automatically (e.g. if the external diameter
reduces) and incorrect entries are signaled (e.g. empty input field for unwinding
diameter).
2. Tool counter-point path ("without tool data") is temporarily retained when a tool
data source (e.g. "with tools", etc.) is selected.
In order for the correct selection and deselection of tool compensations (LK, FRK,
SRK) to be checked visually, it is useful to be able to visually compare the tool
counter-point path when tool compensations are deselected and the tool path
when tool compensations are selected.
From version 5.3.8 onwards, the tool counter-point path produced from a
simulation run "without tool data" is therefore generally retained for the first
subsequent simulation run "with tool data" (tool paths with and without tool
compensations are overlaid for one SIM session). Thereafter the tool paths are
reset as usual at the start of each simulation.
Function
To avoid having to carry out memory settings in NC machine data if additional
memory is needed for the simulation, these settings can be carried out in the
DPSIMNCK.INI file in the [DP_SIMNCK] section.
The default values for the simulation are entered in the DPSIMNCK.INI file in the
[DP_SIMNCK] section, generally eliminating the need for additional memory
settings in the NC. These offset values have a cumulative effect on machine
data with the same name.
Negative values are ignored.
DPSIMNCK.INI [DP_SIMNCK]
The following entries with default values are contained in the [DP_SIMNCK]
section:
...
[DP_SIMNCK]
DP_SIMNCK_MM_NUM_GUD_MODULES_OFFSET = 0
corresponding machine data:
18118 MM_NUM_GUD_MODULES
DP_SIMNCK_MM_NUM_GUD_NAMES_NCK_OFFSET = 5
corresponding machine data:
18120 MM_NUM_GUD_NAMES_NCK
DP_SIMNCK_MM_NUM_GUD_NAMES_CHAN_OFFSET = 30
corresponding machine data:
18130 MM_NUM_GUD_NAMES_CHAN
DP_SIMNCK_MM_GUD_VALUES_MEM_OFFSET = 20
corresponding machine data:
18150 MM_GUD_VALUES_MEM
DP_SIMNCK_MM_NUM_USER_MACROS_OFFSET = 10
corresponding machine data:
18160 MM_NUM_USER_MACROS
DP_SIMNCK_MM_NUM_MAX_FUNC_NAMES_OFFSET = 40
corresponding machine data:
18170 MM_NUM_MAX_FUNC_NAMES
DP_SIMNCK_MM_NUM_MAX_FUNC_PARAM_OFFSET = 350
corresponding machine data:
18180 MM_NUM_MAX_FUNC_PARAM
DP_SIMNCK_MM_MAX_SIZE_OF_LUD_VALUE_OFFSET = 400
corresponding machine data:
18242 MM_MAX_SIZE_OF_LUD_VALUE
...
Simulation startup
The simulation application is normally started only on request by the operator. This
prevents the system from being overloaded by the software components that have
to be loaded.
At the same time, however, this significantly increases the start time for the
simulation when it is called for the first time. The start time is the time from
selecting the simulation to execution of the first NC command ("visible" result).
Loading during HMI startup
To accelerate simulation startup, the loading times can be transferred to the HMI
startup. The settings for this are carried out in the REGIE.INI file (OEM or USER
directory).
[StartupConfiguration]
Startup12 = name:=dpncsim, Timeout:=0
[TaskConfiguration]
Task27 = name := dpsim, Timeout := 30000
Note
The entry used in the [StartupConfiguration] section must not have been used
anywhere else. Check this in the REGIE.INI file in the MMC2, ADD_ON, OEM
and USER directories.
Configuration files for the NC environment (tool data, cycles) are loaded when the
SimNCK is started. This means that only the program to be executed and its
subroutines need to be loaded into the simulation NCK. This startup procedure is
controlled by means of the [PRELOAD] and [MAIN] sections in the DPSIM.INI file.
The simulation start time can also be reduced as follows:
[PRELOAD]
CYCLES=1
All cycles (from NCK and hard disk) are preloaded when the simulation NCK is
started with DPNCSIM.EXE.
TOOLS=1
The files for the tool mapper (TO_INI.INI and TO_ADDON.INI) are preloaded when
the simulation NCK is started (if applicable).
Notation
[xxx] ; Section identification
General
1. The system directory structure is organized in such a way that user changes are
retained if the software is upgraded. There is a clear separation between:
• HMI system software and
• customer-specific additions.
2. The system directories "MMC2" and HMI_Adv (and their subdirectories) are
intended to be read only. They contain the original software supplied. They are
only overwritten if the software is upgraded.
User changes to the original software are made in parallel directories. The
content of these directories is unaffected by a software upgrade.
The diagram below shows the priority sequence. This means that entries in the
directory to the right overwrite corresponding entries in directories to the left.
F:\
Priority
• HMI_ADV:
The directory contains area applications, DLLs and HMI-specific data.
• mmc2:
System directory for basic HMI software.
• add_on:
Directory for additional Siemens products
(e.g. AUTOTURN, DIGITALISIEREN, SINDNC,...)
This can have the same directory structure (e.g. language subdirectory) and
directory contents as mmc2. Entries for the add-on product in regie.ini and
re_*.ini, for example, are also stored here.
• oem:
Directory for OEM users in which internal OEM applications are located. This
can have the same directory structure (e.g. language subdirectory) and
directory contents as mmc2. Entries for the OEM product in regie.ini and
re_*.ini, for example, are also stored here.
• user:
User directory in which customer differences from the ini files supplied are
stored. Changes to the appearance of the user interface, which can be made
by the user by means of settings on the HMI user interface, are also stored here
(e.g. language setting, file selection, file manager view, etc.). Other settings that
do not concern OEM or add-on products are also stored in the user directory,
e.g. alarm server settings.
Changes to “auxiliary files”, e.g. assignment of specific access authorizations
for functions, or hiding of specific softkeys, also have to be stored in the user
file.
In principle, only entry differences in the ini files as compared with the originals in
mmc2 are stored in the parallel directories to mmc2. For example, if an OEM
application is added to "oem", a complete "regie.ini" is not created; only the
modified sections are stored in "oem".
Note
None of the INI files in the "MMC2" and "HMI_Adv" directory may be modified.
Note
Do not copy the entire file from "MMC2"! Only copy the differences.
3. In the INI file in the USER directory simply copy the header for the section you
wish to change and write the new or modified entry below it.
Example:
[TextFiles]
User PLC = F:\DH\MB.DIR\MYPLC_
[Alarms]
;Scroll through alarm lines
Rotation Cycle = 1000
The same procedure applies for the F:\ADD_ON and F:\OEM directories.
\ADD_ON is reserved for Siemens products, e.g. AUTOTURN.
All OEM applications should be installed in \OEM
! Important
The associated entries, e.g. in REGIE.INI, should be modified in these directories
and not in \MMC2\!
Example:
Remedy: Omit the full comments in USER\PARAMT.ini, for example, since they
are also included in MMC2\PARAMT.INI.
Introduction
The behavior of the scratching and actual-value setting, PRESET functions is
influenced by a number of machine data. The selected settings also affect
operation. (Display of softkeys and values, saving of input values).
With the introduction of system frames in software version 6, two variants are
available for the functions. The variants are differentiated by a channel-specific
MD:
MD 28082: $MC_SYSTEM_FRAME_MASK
Bit: 0 Preset actual-value memory, scratching
1 External zero offset
2 TCARR, PAROT
3 TOROT, TOFRAME
4 Workpiece reference points
5 Cycles
6 Transformations
The MD does not exist (older NCK software versions) or bit 0 for system frame for
scratching and actual-value setting is not set.
Bit 0 for system frame for scratching and actual-value setting is not set in the MD.
Note
MD 9220: $MM_USER_CLASS_PRESET can also be set to hide the PRESET –
actual-value setting and scratching softkeys.
- The values are written to the first base frame (version 4 and lower)
or (version 5 and higher)
depending on the entry in display machine data 9245:
$MM_MA_PRESET_FRAMEIDX = index of base frame
in the specified base frame
Scratching
When this is selected the active frame is offered. A different frame can be selected
with the entry in the "Zero offset" field.
You cannot choose any tool other than the one in the spindle.
If there is no tool in the spindle, you can choose any tool you want.
From software version 5 onwards, the values are written to the base frame
according to the entry in display MD 9245: $MM_MA_PRESET_FRAMEIDX = base
frame index.
With a value other than G500 in the "Zero offset" field, the values are written to the
frame defined in the field.
NETNAMES.INI
Included in this file are descriptions of the following:
In order to execute external programs located on the hard disk of the HMI in the
data management system from the parts program with the program command
EXTCALL, the following entries, for example, are required in the NETNAMES.INI
file in the "Connection part" section:
[own]
owner= MMC_3
[conn MMC_3]
conn_1= NCU_1
conn_2= NCU_2
conn_3= NCU_3
conn_4= NCU_4
EXTCALL_conns=conn_1, conn_2, conn_3, conn_4
; conn_i Identifier for the NCUs from which the HMI
can be accessed. See note below
; MMC definitions
[param MMC_3]
mmc_type = 0x40
mmc_......
Note
The entry EXTCALL_Conns … is only needed in the main operating field in the
NETNAMES.INI file, not in the secondary operating fields.
5.3.5 Editor
AEDITOR.INI
Information about the ASCII editor can be found in the aeditor.ini file. The
[ACCESSLEVEL]
GlobalReplace=6
SettingHiddenCheck=7
Enable_Simulation = 7
; Softkey simulation can be hidden
; in the editor
[MMC_Wizard]
AEDITOR=AEDITOR.COM ; BE1
Precondition
• A network drive connection is set up on the HMI (hardware + software) and
activated in the Windows environment for the HMI.
9676 CMM_DIRECTORY_SOFTKEY_PATH1="Path1"
9677 CMM_DIRECTORY_SOFTKEY_PATH2="Path2"
9678 CMM_DIRECTORY_SOFTKEY_PATH3="Path3"
9679 CMM_DIRECTORY_SOFTKEY_PATH4="Path4"
Operation
The softkeys are available in the Machine area under Program overview --> ETC
and in the Program area.
In HMI Advanced version 6.2 and higher, if network drives have been defined, the
first three are directly accessible from the horizontal softkey bar, while if a fourth
network drive has been defined it can be accessed from --> ETC. If network drives
exist, the softkeys for the cycle directories are located in the continuation bar -->
ETC.
Configuring drives/computers
MD 9676: CMM_DIRECTORY_SOFTKEY_PATH1 to MD 9679 are used to enter
the names of the external drive/computer with/without a directory. Up to 4
connections can be set up.
Connections can be specified as
in MD 9676 to 9679.
Example:
MD9677 CMM_DIRECTORY_SOFTKEY_PATH2=F:\R4711
;Drive + directory
MD9678 CMM_DIRECTORY_SOFTKEY_PATH3=\\R4712\PART1\SHAFT1.DIR
;Computer name, share name with directory
MD9679 CMM_DIRECTORY_SOFTKEY_PATH4=\\R4713\Part2\MPF_DAT .DIR
;Computer name, share name with directory
Example:
mbdde.ini:
...
[TextFiles]
USER_PLC=F:\DH\MB.DIR\MYTXT_
MYTXT_GR.COM:
89901 0 0 "" Reserved
89902 0 0 "F:\R4711" Softkey text for softkey 2
89903 0 0 "R4712/ MMC1" Softkey text for softkey 3
89904 0 0 "R4713/ MMC2" Softkey text for softkey 4,
(2 spaces denote a line break)
...
HMI display
The network drives are offered
• in the MACHINE operating area in the extended SK (softkey) bar after the
"Program overview" softkey
• in the PROGRAM operating area as an extended softkey bar in the main menu
• in the SERVICES operating area under Manage data (if 4 network drives are
configured, 3 are displayed directly as horizontal softkeys, the fourth is
accessed by pressing the ETC button)
• in the SERVICES operating area under Data on and Data off under the second
vertical softkey Network drives …
The softkeys in the various (expanded) softkey bars are assigned according to
MD 9676 (SK1) to 9679 (SK4) (i.e. with gaps if applicable). The plain text identifier
is used as the softkey text. If no text is configured, the value of the corresponding
MD is shown. In version 6.2 and higher, the arrangement of the softkeys is as
described above under "Operation".
Error messages
The network drive configuration is evaluated when the HMI is started. This
evaluation does not check whether the connection actually exists. This check is
only made when the drive is selected during use. If the configured path cannot be
accessed, the error message "No files available for display" appears.
5.6.1 MMC.INI
[GLOBAL]
MMCScreenOffTimeInMinutes = 5 ; latency for the screensaver
; screensaver on delay
ServerVisible=1
[CONTROL]
; Resolution: 0=fixed (640x480), 1=variable, default:0
Resolution=0
; BaseScreen specifies the resolution, for which the
; applications originally were developed (typically: 640x480)
; BaseScreen - default: 640x480
BaseScreen=640x480
MoveCursor=0
[WP_SELECT]
TOA_WARNING_MESSAGE=yes
[HEADER]
5.6.2 NETNAMES.INI
This file is used for setting M:N assignments for control units and NCUs. See
References: /FB/, B3, Multiple Operator Panel Fronts and Multiple NCUs,
Distributed Systems
and the definition of channel groups if there is a 1:1 assignment between the
control unit and the NCU.
Channel menu
Access to the channel menu configuration is granted by extending the file
"NETNAMES.INI".
Procedure
To do this, proceed as follows:
Note
The NC writes the channel number for the HMI in DB19, DBB22.
Example:
NETNAMES.INI
[own]
owner = MMC_1
; Description of possible connections
[conn MMC_1]
conn_1 = NCU_1
conn_2 = NCU_2
; Description of significant net parameters
[param network]
bus = opi ; the MPI interface must be used on the SINUMERIK 810D
[param MMC_1]
mmc_address = 1
[param NCU_1]
nck_address = 12
plc_address = 12
; core name for the PLC symbol files for representing signals with symbols
PlcSymbolFile= ...
[param NCU_2]
nck_address = 14
plc_address = 14
; core name for the PLC symbol files for representing signals with symbols
PlcSymbolFile= ...
[chan MMC_1]
DEFAULT_logChanGrp = Milling1
DEFAULT_logChan = Channel13
ShowChanMenu = TRUE
logChanSetList = Milling1, Milling2
[Milling1]
logChanList = Channel11, Channel12, Channel13, Channel14, Channel15
[Channel14]
logNCName = NCU_1
ChanNum = 4
[Channel15]
logNCName = NCU_1
ChanNum = 5
[Milling2]
logChanList = Channel21, Channel22, Channel23, Channel24, Channel25
[Channel21]
logNCName = NCU_2
ChanNum = 1
[Channel22]
logNCName = NCU_2
ChanNum = 2
[Channel23]
logNCName = NCU_2
ChanNum = 3
[Channel24]
logNCName = NCU_2
ChanNum = 4
[Channel25]
logNCName = NCU_2
ChanNum = 5
5.6.3 MBDDE.INI
The multiple file strategy can also be selected by means of the DiskCare Ini file
entry
File: "mbdde.ini",
Section: [PROTOCOL],
Entry: "DiskCare". See below.
[Alarms]
RotationCycle=0
; determines if the alarm server should connect to ALARM_S/SQ
; or not
; possible values:
; 0 Alarm_S/SQ not handled
; 1 Alarm_S/SQ handled (default)
Alarm_S=1
; if Alarm_S/SQ handling is enabled this key determines if Quits
; should be entered into the alarm protocol
; possible values:
; 0 Alarm_SQ quits are not entered into the alarm protocol
; (backward compatible)
; 1 Alarm_SQ quits are entered into the alarm protocol (default)
Protocol_Alarm_SQ=1
; path and file names of the alarm text lists
; The filename fragments must not exceed 6 chars, because it is
; extended automatically by the message module according to the
; selected language.
; The alarm texts in the files specified under UserMMC, UserNCK ...
; overload the corresponding texts of the files defined in MMC, NCK ...
; Therefore the user should modify files according to the needs of his
; system exclusively in UserMMC, UserNCK ...
; Creating alarm text with any DOS editor may cause problems with special
; characters like ä, ö or ü. To import DOS-generated files in any case,
; add a blank and the string "DOS" after the name of the text file.
; If you add or remove the parameter DOS, you have to actuate (new date
; of file) the corresponding file (*.com) otherwise the change is not
; accepted.
[TextFiles]
MMC=F:\MMC_52\dh\mb.dir\alm_
NCK=F:\MMC_52\dh\mb.dir\aln_
PLC=F:\MMC_52\dh\mb.dir\alp_
ZYK=F:\MMC_52\dh\mb.dir\alz_
CZYK=F:\MMC_52\dh\mb.dir\alc_
STANDARD_CYCLES=F:\MMC_52\dh\mb.dir\alsc_
SHOPMILL_MANUALTURN_CYCLES=
MEASURE_CYCLES=F:\MMC_52\dh\mb.dir\almc_
PLC_PMC=
USER_CYCLES=
UserMMC=
UserNCK=
UserPLC=
UserZYK=
UserCZYK=
UserSTANDARD_CYCLES=
UserSHOPMILL_MANUALTURN_CYCLES=
UserMEASURE_CYCLES=
UserUSER_CYCLES=
UserPLC_PMC=
[net TextFiles]
; NCU_RECHTS=F:\dh\mb.dir\rechts (Name of NCU=Path of texts)
; NCU_MITTE=F:\dh\mb.dir\mitte
; NCU_LINKS=F:\dh\mb.dir\links
; Maximum 8 entries
[IndexTextFiles]
ALNX=F:\MMC_52\dh\mb.dir\alnz_
[DEFAULTPRIO]
CANCEL=100
RESET=100
POWERON=100
NCSTART=100
PLC=100
PLCMSG=100
MMC=100
[PROTOCOL]
; Criteria for selecting the alarm messages to be recorded. The notation
; is described in SINUMERIK 840D OEM package MMC User's Manual.
Filter=Expression
; Details of how to form filter expressions to control the
; messages logged can be found in: 5.1.1 Alarm protocol
Records=150
; This section specifies the names and paths of the help files that
; contain help texts in the WinHelp format.
; This list include a maximum of 10 entries.
; The filename fragments must not exceed 6 chars, because it is extended
; automatically by the message module according to the selected language.
; For additional information see SINUMERIK 840D OEM package
; MMC User's Manual.
[Helpcontext]
File0=hlp\alarm_
[COLOR]
ForeColor_Alarm=000000FF
BackColor_FirstAlarm=00FFFFFF
ForeColor_FirstAlarm=000000FF
BackColor_Message=00FFFFFF
ForeColor_Message=00000000
BackColor_ApplMessage=00FFFFFF
ForeColor_ApplMessage=0000FF00
BackColor_Alarm=00FFFFFF
; default factor for maximum size of buffer file for editing NC domains
; see explanation for MemFactor above
; the factor should be high enough for the whole NCU memory
; the application cannot override this default factor
MemNCFactor=2
[STEPS]
; maximum number of blocks to search for a step, 0 == no limit
MaxNrOfBlocks=1500
[ACCESSLEVEL]
GlobalReplace=6
SettingHiddenCheck=7
Enable_Simulation=7 ; Access level for softkey simulation in editor
5.6.5 COMIC.NSK
REM ----- TYPICAL COMIC START
REM CHANNEL 1
TOPIC(machineswitch) COMIC_START("COMIC001MachineSwitch
",/Channel/Configuration/mmcCmd[u1],/Channel/Configuration/mmcCmdQuit[u1])
REM CHANNEL 2
TOPIC(machineswitch) COMIC_START("COMIC002MachineSwitch
",/Channel/Configuration/mmcCmd[u2],/Channel/Configuration/mmcCmdQuit[u2])
5.6.6 DINO.INI
[ACCESSLEVEL]
USER=3 ; Read authorization for series setup
; Customer password (default)
PROGRAMMER=4 ; Setup authorization for series setup
; corresponds to keyswitch 3 (default)
[Function]
; 0 : ISO-formatted paper tape is not supported
; 1 : ISO-formatted paper tape is supported
IsoActive=0
; 1: ask before overwriting CFG_RESET.INI, 0: don't ask
Ask_for_CFG_RESET.INI=0
Note
"Only handshake" or "ZMODEM with RTS/CTS" are the only protocols offered in
the HMI.
...
; take in consideration only for XON/XOFF protocol
; 0: don't send XON, 1: send XON by receiving data
; not changeable by user interface
Send XON=0
5.6.7 DPDH.INI
[ACCESSLEVEL]
PROGRAMMER=4
OPERATOR=5
ENABLE_DIALPROG=0
SetStandardWpSave=2
ENABLE_SIMULATION=7
5.6.8 DH.INI
[ACCESSMASKS]
See 4.3.2
5.6.9 DPSIM.INI
[ACCESSLEVEL]
; minimum level for changing setup standard:
SETUP=1
USER=3
OPERATOR=5
[MAIN]
; <>0: simulate program external modal (see also
; EXTERN_SIZE,EXTERN_CHECK)
EXTERN_MODAL=0
[PRELOAD]
;=1: TO_INI.INI and TO_ADDON.INI are preloaded by DPNCSIM.EXE
;=0: TO_INI.INI and TO_ADDON.INI are loaded by simulation
TOOLS=0
;= 1: all cycles are preloaded by DPNCSIM.EXE
; if section MAIN, entry CYCLE is set, additionally all cycles from
shadow directory are preloaded by DPNCSIM.EXE
;= 0: cycles are loaded by simulation, if cycle is called
CYCLES=1
;=2: load for simulation to \CUS.DIR, \CMA.DIR or \CST.DIR (default)
; load only cycles from NCK
; only evaluated if [MAIN]CYCLE is set and [PRELOAD]CYCLES=1
;=0: load all cycle (from NCK and MMC) for simulation to
; \CUS.DIR, \CMA.DIR or \CST.DIR
; only evaluated if [MAIN]CYCLE is set and [PRELOAD]CYCLES=1
;=1: use the cycle interface in \DP.DIR\SIM.DIR
CYCLEINTERFACE=2
5.6.10 SIMTOGEO.INI
Sample file with the details required for the individual tool types.
If Link is set to 0 in the [Settings] section, the other entries in SimToGeo.ini are
redundant.
[Settings]
; this entry is dependent on settings such as
;
; MD 18206: $MN_MM_NUM_CCS_TOA_PARAM=1
; MD 18207: $MN_MM_TYPE_CCS_TOA_PARAM[1]=4
; MD 18080: $MN_MM_TOOL_MANAGEMENT_MASK='H4'
;
; if wanted and / or other oem parameters are used the index can be changed
; ( e.g. TC_DPCS4 if $MN_MM_NUM_CCS_TOA_PARAM=4 )
; or any other oem variable as TC_DPCS1 can be used :
;
;LINK=TC_DPC7
;
; MD 18096: $MN_MM_NUM_CC_TOA_PARAM=7
; MD 18097: $MN_MM_TYPE_CC_TOA_PARAM[7]=4
; MD 18080: $MN_MM_TOOL_MANAGEMENT_MASK='H4'
;
LINK=0 ; example LINK=TC_DPCS1
5.6.11 MASCHINE.INI
The [AccessLevel] section in the "maschine.ini" file can be used to
set access authorizations for functions. The file includes detailed comments.
[ACCESSLEVEL]
;
; 7 = Keyposition 0 everyone in front of the machine,
; Suggestion: Permission only for NC start, no selection of
part program
; 6 = Keyposition 1 machine operator, production shop-floor operators
; Suggestion: Permission to select Part-Program, no editing
; 5 = Keyposition 2 machine setter (more experienced), the one to set up tools
; and test and run in new Part-Programs
; Suggestion: Permission to modify (edit) Part-Programs
; 4 = Keyposition 3 not yet used, same permissions as 5
[Customer]
MDASingleSTEP=yes
ONLY_MKS_ToolBaseDistToGo=no
NcVersionCheck=true
; Due to performance issues the functionality offered with respect to
; Block correction, block view and block search depends on the
; Nc-version currently used.
; However, to get access to the whole functionality, regardless of the
; Nc version in use,
; set the flag NcVersionCheck to False.
[BlockSearch]
; Shows (SeruproEnabled=1) or
; hides (SeruproEnabled=0)
; the softkey used to do a block search in mode "programtest".
; The softkey appears in both dialogs
; "Blocksearch Searchposition" and "Blocksearch Searchpointer"
SeruproEnabled=1
; When doing a block search in mode "programtest" you can do
; a multi-channel block search. There are 4 channel configurations which
; define the NC-channels being affected by the block search:
; SeruproConfig =
; 1: selected/active channel
; 2: selected/active channel and all channels having selected the same
; workpiece as the active channel
; 3: selected/active channel and all channels belonging to the active
; channel's mode group
; 4: all NC channels
SeruproConfig=1
[SetZero]
; Display_Sign_Switch switch the sign of the toollength in the scratch picture
5.6.12 PARAM.INI
[ACCESSLEVEL]
READ_SYSVAR=7
EDIT_VIEW=7
[ToolParams]
UserDataParamName1=T_Param_1
UserDataParamName2=T_Param_2
UserDataParamName3=T_Param_3
UserDataParamName4=T_Param_4
UserDataParamName5=T_Param_5
UserDataParamName6=T_Param_6
UserDataParamName7=T_Param_7
UserDataParamName8=T_Param_8
UserDataParamName9=T_Param_9
UserDataParamName10=T_Param_10
[ToolEdgeParams]
UserDataParamName1=D_Param_1
UserDataParamName2=D_Param_2
UserDataParamName3=D_Param_3
UserDataParamName4=D_Param_4
UserDataParamName5=D_Param_5
UserDataParamName6=D_Param_6
UserDataParamName7=D_Param_7
UserDataParamName8=D_Param_8
UserDataParamName9=D_Param_9
UserDataParamName10=D_Param_10
The tool compensation (turning) is calculated in Diameter when the selected axis
is equal to the traverse axis and the entry CalDiaVal=1 is set in the [Bezugma]
section in the Param.ini file.
5.6.13 PARAMTM.INI
Full details of the possible parameter settings are described in the tool
management description.
5.6.14 REGIE.INI
[Miscellaneous]
; needed if regie is to support an 'EXIT' button
; set 'ExitButton' to True, and 'ExitButtonIndex'
; identifies index of exit button
ExitButton = True
ExitbuttonIndex = 15
HibernateMode = ...
HibernateMode = Off
Default setting. Hibernate saves and Hibernate reboots are not performed.
HibernateMode = Normal
A type-1 Hibernate is performed. This means that HMI Advanced first closes all
applications and then starts a Hibernate in Windows XP. In HMI software
version 6.3 onwards, this is the default for 840D systems with Windows XP.
[TaskConfiguration]
; 3rd bar
; Task16 = name := oemframe, cmdline := "sysmeter", Timeout := 10000,
; ClassName := "SysMeter", HeaderOnTop := False, PreLoad := False
The 3rd horizontal softkey bar is only displayed if a task or the EXIT button is
assigned to Task16 or higher in the bar. See above.
The 4th horizontal softkey bar is only displayed if a task or the EXIT button is
assigned to Task96 or higher in the bar. See above.
5.6.15 TASKCONF.INI
[CONTROL]
MDIList=MntMMC\MntMMC.mdi
ControlFile=MntMMC\MntMMC.zus
ScreenTwips=1
[DEBUG]
;MDISize 0 = Debug, 1 = Full screen
MDISize=0
[APPLICATION]
; Hsk1.. - Hsk8.. (horizontal softkeys)
; Hsk9.. - Hsk16.. (ETC softkeys)
; Vsk1.. - VSK8.. (vertical softkeys)
;=================================================;
; for each softkey (Hsk1 - Hsk16 / Vsk1 - Vsk8) ;
;=================================================;
; 0 : SwitchToChild (default)
; 1 : SwitchToTask -> switch only to task
; 2 : SwitchToTask2 -> switch to child of specified task (if it exists)
Hsk1IsTask=
;0 : no link to NCK
; <> 0 : link softkey to NCK (lock softkey while no connection to NCK)
Hsk1NckLink=
5.6.16 DG.INI
Softkey access in the Diagnostics operating area can be set individually by
entering the access level.
Enter the required access level in file DG.INI in the
[AccessLevel] section:
[ACCESSLEVEL]
ALARMS=7 ; Alarms
The chosen button should correspond to the signal specified in the Quit
acknowledgement parameter by FC 10. For example:
Call FC 10
ToUserIF:=TRUE
Quit:=DB21.DBX7.7 //Channel 1 RESET
Select a value for the image to be displayed in the [ALARM_PICTURE] section:
[ALARM_PICTURE]
;0 = Image for PLC button
;1 = Image for Cancel button
;2 = Image for Reset button
;3 = Image for HMI button
;4 = Image for user-defined button
ButtonImage=1
5.6.17 IB.INI
Softkey access in the Setup operating area can be set individually by entering the
access level.
Enter the required access level in file IB.INI in the [AccessLevel] section. The
operating languages are defined in the [Language] section.
[ACCESSLEVEL]
[LANGUAGE]
;LanguageList= ... , GR
;FontList= ... , Europe
;FontListKO= ... , Europe2
;LBList= ... , deutsch
SkSelectLngInsteadSkChangeLng=False
Note
In the [HELP_EXTENSION] section the HelpFileExtension parameter must be set
to 0 (WinHelp) if you want old, OEM-specific help files with the extension *.hlp to
be displayed.
5.6.18 IF.INI
The following sections are available in the "If.ini" file for configuring the Help
functions:
• TECHNOLOGY
• TEXTFILES
• CONTEXT
• TEXTSEARCH
TECHNOLOGY section
The relevant technology category of the connected machine can be entered in the
[TECHNOLOGY] section so as to limit the display of instruction texts to relevant
technology entries, i.e. only entries pertinent to the relevant technology are
displayed.
The following technology codes can be specified:
"m" = milling
"t" = turning
"g" = grinding
"s" = nibbling
"p" = punching
"a" = display all technologies
TEXTFILES section
The paths (path\name) used for the Short Help text files on which the help function
is based are parameterized in the section [TEXTFILES].
The help function accesses the following text files:
Siemens "DH\CST.DIR\IFS_GR.COM"
Machine manufacturer "DH\CST.DIR\IFM_GR.COM" (any file name)
End user "DH\CST.DIR\USER_GR.COM“ (any file name)
(Also entered via "Settings")
! Important
The path for the Siemens text file “DH\CST.DIR\IFS_GR.COM“ must exist
otherwise an error message is output.
The entry for Siemens is specified in conjunction with ISO language as:
SiemensI=file
There are different parameterization options for the names of the text files when
assigning the text path.
The following table lists the parameterization options and their interpretation by the
Help function.
Table 5-6
Example: ENDUSER=CUS.DIR\IFM_.COM
First of all, the non-language-specific text file "Ifm.com" is opened in the path
"C:\DH\CUS.DIR\" by default or, if the non-language-specific text file does not exist,
the relevant language-specific text file (e.g. "IFM_GR.COM") is opened.
Extract from Short Help txt file "IFM_GR.COM":
...
a2//G00/Linear interpolation with rapid traverse (m)
a2//G01/Linear interpolation with feed (m)
a2//G02/Circular interpolation in clockwise direction (m)
...
CONTEXT section
An increased context sensitivity of the Help function can be selected in the
[CONTEXT] section. This setting is activated with "1" and deactivated with "0".
(Also entered under "Settings").
If the increased context sensitivity is activated and the cursor is positioned to the
left of, next to or on an instruction text, then all instructions with the same initial
letters are displayed when Help is called.
For example, if the programmer has selected instruction "G1", then all instructions
beginning with "G1" (e.g. "G1", "G17", "G18", "G19") are displayed.
If increased context sensitivity has been deactivated with "0", then only the
instruction actually selected (if available) is displayed.
TEXTSEARCH section
The text search type can be specified in the [TEXTSEARCH] section. The following
search methods can be parameterized:
1 = instruction texts only
2 = descriptive texts only
3 = instruction and descriptive texts
(Also entered under "Search").
File IF.INI
[TECHNOLOGY]
; "m" = milling
; "t" = turning
; "g" = grinding
; "s" = nibbling
; "p" = punching
; "a" = display all technologies
Technology=m
[TEXTFILES]
; Siemens = DH\CST.DIR\IFS_GR.COM
; SiemensI= DH\CST.DIR\IFIT_GR.COM ISO turning or
; SiemensI= DH\CST.DIR\IFIM_GR.COM ISO milling
; Machine manufacturer = DH\CST.DIR\IFM_GR.COM
; Machine manufacturer = DH\CST.DIR\IFI_GR.COM
; End user = DH\CST.DIR\USER_GR.COM
; Notation in the section e.g.:
Siemens=Cst.dir\ifs_gr.com
SiemensI=Cst.dir\ifit_gr.com
Manufacturer= …
End user=
[CONTEXT]
[TEXTSEARCH]
Search type=3
5.6.19 OEMFRAME.INI
[SysMeter]
;fSearchOnlyForTaskWindow=1
;nDelayInitComplete=10000
WindowStyle_Off = 720896
x=
y=
Width =
Height =
5.6.20 LAYOUTSW.INI
If user-specific pictures are to be used in layout switching as defined in MD 9021:
LAYOUT_MODE, the file must be extended and stored in the user or oem
directory. (See 5.1.22)
; Directory/directories below
; the HMI installation directory
HMI_Zip_Dir_0=hmi_adv
HMI_Zip_Dir_1=mmc2
[internal]
;Do not change this part! Do not change!
TraceEnabled=0
5.6.21 DGOVW.INI
This file is used to configure user-specific additional signals in
Diagnostics → Service displays, "Service overview" screen. Configured signals are
added below the standard signals in this screen and can be viewed there (scrolling
may be required). For configuration details and an example see 5.1.21. The file
must be explicitly stored in one of the directories mmc2 or addon, oem, user.
[GLOBAL]
; Number of additional signals
NrOfSignals=
; Bitmaps with customized icons to be displayed
[BMP]
100="<Bitmapname>"
101="..."
.
.
; One section per signal
[SIG1]
text=
Item=
expr=
.
.
[SIG2].
.
.
[SIG<n>]
.
.
5.6.22 DGOVWTXT_xx.INI
xx in the file name stands for the language abbreviation for the language.
The file contains the language-specific texts for user-specific signals in the service
overview. See also 5.1.21. It must be explicitly stored in the directories
mmc2 or user, addon, oem \language.
[TEXT]
5.6.23 HMIDesk.ini
Default settings: an explanation of the settings can be found in 9.2.2.
[Global]
;Global configuration data
;Definition of desktops (minimum 2, maximum 4)
NumberOfDesktops = 2
KeyboardControl = False
[Desktop1]
[Desktop2]
[Desktop3]
[Desktop4].
5.7.1 MMC.INI
Screen saver
The delay time before the screen saver is activated can be adjusted:
Section: GLOBAL
Entry: MMCScreenOffTimeInMinutes
! Important
The HMI screen saver and Windows screen saver must not be used at the same
time.
Server
You can choose to display the server name with:
Section: GLOBAL
Entry: ServerVisible
Channel menu
The grouping of multiple channels in an NCU and the channel assignments to
NCUs if multiple NCUs are used in M:N mode can be configured in the
NETNAMES.INI file.
M:N assignments
In the NETNAMES.INI file you can determine which operating components can
operate which NCUs. The following details are specified:
• Names of the operating components
• Names of the NCUs
• Communication links between them
• Clear assignments for startup
Details can be found in
Multi-channel display
In order to be able to use the multi-channel display (dual-channel display) in the
Machine operating area, [MULTI_CHAN_i] sections are required:
[MULTI_CHAN_i]
CHAN_2 = k
"i" denotes the channel number in the current NCU.
The 2nd channel displayed is specified in the CHAN_2 entry CHAN_2 = k
Note
When the channel menu is selected, all entries under [MULTI_CHAN_i] are
ignored.
This default configuration only applies when switching from 1-channel to 2-channel
display. If 2-channel display is active and a channel is switched within the display,
the other channel remains unaffected.
[MULTI_CHAN_1]
CHAN_2 = 6
[MULTI_CHAN_2]
CHAN_2 = 7
[MULTI_CHAN_3]
CHAN_2 = 8
[MULTI_CHAN_6]
CHAN_2 = 1
[MULTI_CHAN_7]
CHAN_2 = 2
[MULTI_CHAN_8]
CHAN_2 = 3
Note: Each of the paired channels appears once in [MULTI_CHAN_i] and once as
the 2nd channel in CHAN_2=i.
5.7.3 REGIE.INI
EXIT button
If you want the sequence control in the HMI software to support an Exit button, you
should make the following settings:
[Miscellaneous]
ExitButton=True
ExitButtonIndex = index
ExitButtonAccessLevel=7
; Dialog box to ask user
ExitButtonQueryUser = True
5.7.4 HEADER.INI
Status display with icons
The function "Status display for SINUMERIK control across multiple channels" in
the program status line is controlled by means of the HEADER.INI file and can be
changed by the machine manufacturer. Manufacturer-defined icons can also be
used in addition to standard icons.
[CondStopIcons]
DefaultIcon=CondWait.bmp ;0 = No stop state
1=CondStop.bmp ;No NC ready
2=CondStop.bmp ;No ModeGroup ready
3=CondStop.bmp ;EMERGENCY STOP active
4=CondStop.bmp ;Alarm active with stop
5=CondStop.bmp ;M0/M1 active
6=CondStop.bmp ;Block ended in SBL mode
7=CondStop.bmp ;NC Stop active
8=CondStop.bmp ;Read-in enable missing
9=CondStop.bmp ;Feedrate enable missing
10=CondWait.bmp ;Dwell active
11=CondWait.bmp ;Aux. function acknowledgment missing
12=CondStop.bmp ;Axis enable missing
13=CondWait.bmp ;Exact stop not reached
14=CondWait.bmp ;Waiting for positioning axis
15=CondWait.bmp ;Waiting for spindle
16=CondWait.bmp ;Waiting for other channel
17=CondStop.bmp ;Waiting for feed override
18=CondStop.bmp ;Error in NC block
19=CondStop.bmp ;Waiting for external NC blocks
20=CondWait.bmp ;Waiting for synchronous action
21=CondWait.bmp ;Block search active
22=CondStop.bmp ;No spindle enable
23=CondStop.bmp ;Axis feed override 0
24=CondWait.bmp ;Waiting for tool change acknowledgment
25=CondWait.bmp ;Gear step change
26=CondWait.bmp ;Waiting for position control
27=CondWait.bmp ;Waiting for thread cut
28=CondWait.bmp ;Reserved
29=CondWait.bmp ;Waiting for punching
30=CondWait.bmp ;Waiting for safe operation
31=CondWait.bmp ;No channel ready
;Version 4.1 and higher
32=CondStop.bmp ;Oscillation active
;Version 4.1 to $[[SW440000]]
33=CondWait.bmp ;Axis replacement active
;Prevents block change because an axis replacement has started,
;version 4.1 and higher
34=CondWait.bmp ;Axis container rotation
;Version 4.4 and higher
35=CondWait.bmp ;AXCT: following axis active
;Axis container replacement, version 5.2 and higher
36=CondWait.bmp ;AXCT: leading axis active
;Axis container replacement, version 5.2 and higher
37=CondWait.bmp ;AXCT: follow up mode active
;Axis container replacement, version 5.2 and higher
[Pos1]
ChanStatFeedStopSpindleStop = 1 ;Channel status channel 1 is displayed,
;superimposed with
[Pos3]
SpindStat = 1 ;Spindle status for spindle 1
;ChanStatFeedStop = 3 ;Channel status for channel 3 is displayed,
;superimposed
;with feed disable for channel 3
[Pos5]
ChanStat = 2 ;Channel status for channel 2 is displayed
;SpindStat = 3 ;Spindle status for spindle 3 is
;displayed
[Pos7]
ChanStat = 3 ;Channel status for channel 3 is displayed
;SpindStat = 3 ;Spindle status for spindle 3 is
;displayed
[Pos9]
ChanStatFeedStopSpindleStop = 1 ;Channel status for channel 1 is displayed,
;superimposed
Spindles = 1 ;with feed disable for channel 1 and
;spindle disable for spindle 1
[Pos11]
ChanStatFeedStop = 2 ;Channel status for channel 2 is displayed,
;superimposed
;with feed disable for channel 2
[Pos13]
SpindStat = 2 ;Spindle status for spindle 2
[Pos15]
ChanStatFeedStopSpindleStop = 1 ;Channel status for channel 1 is displayed,
;superimposed
Spindles = 1 ;with feed disable for channel 1 and
;spindle disable for spindle 1
;
[UserIcons]
;UI_0 = <name.bmp> , <Position> ;Name of icon, position
...
;UI_31 = <name.bmp> , <Position> ;Name of icon, position
;USER_ICON_BASE = DBxx.DBByy
; xx data block with
; control double word for user icons
; yy start byte for double word.
[UserTextInfo]
;USER_TEXT_BASE = DBxx.DBByy
; xx data block with
; interface for user messages in
; header
; yy start byte for interface
5.7.5 KEYS.INI
Entries in this file allow hard keys on the operator panel fronts OP 010 and
OP 010c or SINUMERIK keyboards with hotkey block and PLC softkeys to be
used.
Notes
Structure of
MBDDE.INI
Extract from MBDDE.INI relating to the configuration of alarm text files:
...
[Textfiles]
MMC=f:\dh\mb.dir\alm_
NCK=f:\dh\mb.dir\aln_
PLC=f:\dh\mb.dir\plc_
ZYK=f:\dh\mb.dir\alz_
CZYK=f:\dh\mb.dir\alc_
UserMMC=
UserNCK=
UserPLC=f:\dh\mb.dir\myplc_
UserZyk=
UserCZyk=
...
A detailed description of MBDDE.INI can be found in Subsection 5.4.3.
Standard files
On the hard drive of the HMI the standard texts are stored in ASCII format
in the following files:
MMC F:\dh\mb.dir\alm_XX.com
NCK F:\dh\mb.dir\aln_XX.com
PLC F:\dh\mb.dir\alp_XX.com
ZYK F:\dh\mb.dir\alz_XX.com
CZYK F:\dh\mb.dir\alc_XX.com
In these file names, "XX" stands for the code of the appropriate language. The
standard files should not be changed by the user to store his or her own error
texts. If these files are replaced by new ones when the HMI software is upgraded,
then the added or modified user-specific alarms will be lost. Users should store
their own error texts in user files.
User files
Users can replace the error texts stored in the standard files
• with their own texts, or
• add new ones.
To do this, copy additional files into directory f:\dh\mb.dir (MBDDE alarm texts) via
the Services operating area. The names of these text files are set in file
f:\mmc2\mbdde.ini. An editor is provided in the Diagnostics\Setup\MMC area for
this purpose.
Examples of the configuration of two additional user files (texts for PLC alarms,
altered NCK alarm texts) in file MBDDE.INI:
...
User MMC =
User NCK = F:\dh\mb.dir\mynck_
User PLC = F:\dh\mb.dir\myplc_
User ZYK =
User CZYK =
...
The texts from the user files overwrite standard texts with the same alarm number.
Alarm numbers which do not already exist in the standard texts are added.
Note
To prevent a modified MBDDE.INI file from being overwritten when the software
is updated, it must be stored in the designated USER path
<InstallationPath>\user\mbdde.ini.
Editor
Any ASCII editor (e.g. the DOS editor edit) can be used for editing files.
When editing the text files with a different editor, make sure that they are then
saved in ASCII format.
Language-specific
alarm texts
Language assignment of the user alarm texts is carried out using the name of the
text file. The appropriate code and the extension .com are added to the user file
name entered in mbdde.ini:
Language Code
German gr
English uk
French fr
Italian it
Spanish sp
The language code for other non-standard languages can be found in Table 6-1.
Example
File for customized German PLC alarm texts
MYPLC_GR.COM:
%_N_MYPLC_GR_COM ; } only required for reading via V.24
;$Path=/_N_MB_DIR ; } only required for reading via V.24
700000 0 0 “DB2.DBX180.0 set”
700000 0 0 “No lubrication pressure”
....
Note
Changes to alarm texts do not take effect until the HMI is powered up again.
When creating text files, make sure that the correct date and time are set on the
PC. Otherwise, the user texts may not appear on screen.
Alarm numbers
For cycle, compile cycle and PLC alarms the following alarm numbers can be used:
Format of the
text file for
cycle alarm texts
The number range in the list is not available with every number
(see References: /FB/ P3, “Basic PLC Program”, Lists)
The structure of the text file for cycle and compile cycle alarms is as follows:
Example:
3
14510.0 My text for PLC-MD 14510.0
14510.3 Text for PLC-MD 14510.3
14514.0 My text for float data 14514.0
6.3 Languages
6.3.4 Setup
Languages that are not included as standard must be installed as described in
Section 7.2.
An additional tool is implicitly required for Asian languages (e.g. NJWIN). The
appropriate fonts are installed automatically with this.
When each language module is installed, the appropriate fonts are installed by the
tool at the same time, and all necessary entries made in mmc.ini and in the
registry.
Notice:
Windows 95 and Windows NT registries are not compatible in terms of fonts !
During setup
DLLs, text files (machine data files) and language-specific INI files are stored in the
"\mmc2\language" directory,
the alarm texts in the "\dh\mb.dir" directory.
Function
If multiple operator panel fronts/NCUs (M : N) are used, NCU-specific alarm texts
can be created and managed in the MMC.
This function requires entries to be made in the MBDDE.INI file in the [netTextFiles]
section. The file is located in the C:\USER directory.
The entries for the NCUs must match the entries in section [paramNCU_Bez] of the
current NETNAMES.INI file.
The NETNAMES.INI file in connection with the function "Multiple operator panel
fronts/NCUs" is described in
References: /FB2/ B3 Multiple Operator Panel Fronts and NCUs.
Search sequence
To output an NCU-specific alarm, the associated text is searched for in the
following sequence:
1. NCU-specific texts
2. Non-NCU-specific texts
Entry in MBDDE.INI
Example:
[net TextFiles]
NCU_1=C:\DH\MB.DIR\NC1_GR.COM
NCU_2=C:\DH\MB.DIR\NC2_GR.COM
NCU_3=C:\DH\MB.DIR\NC3_GR.COM
7.1 General
This chapter describes the installation and updating of additional software along
with data backup and restore processes based on the pre-installed "Basic PCU
software with Windows NT 4.0/XP".
The description refers to the hardware and software components supplied as
standard, as described in Section 3.3. The key tools are the Service menu and
SINUMERIK desktop, also described in Subsection 3.3.6, and the Norton Ghost
program (see 7.3.1).
The following possibilities are available for backing up and restoring software and
data:
• Parallel connection between HMI and PG/PC
• Ethernet connection between HMI and PG/PC
• Local partition backup on the HMI hard disk
Comment: any
User limit: any
"Permissions..." button
Enter permission (e.g. User1 [local user] or "anyone" with access type: "read").
PG/PC with Windows 95/98:
Assign share name (e.g. HMINEW).
Enter access authorization.
Assign password if necessary.
PG/PC with Windows XP:
Select the directory to be shared and click the right mouse key. Click "Sharing
and Security…". Select the "Sharing" tab, activate "Share this folder" and assign
a share name and comment if required. Click the "Permissions" button to set
the access rights for users and then click "OK" to leave the Permissions window
and the Share window.
• Cable connected
Cable for point-to-point connection in Ethernet port: Ethernet cable of type
"Converted Twisted Pair cable".
• PG/PC with Windows 95/98:
Share level selected
under Start→Settings→Control Panel→Network symbol:→Access Control tab→
"Share level"
The following submenus are available for the individual menu options:
1 Connect to Network Drives
Type your passwd:
Enter the password permitting the user to retrieve data (e.g. software) from or write
data (e.g. PCU images) to the shared directory on the networked PG/PC.
Enter the letter of the PCU drive from which the connection must be accessed (e.g.
"G")
Enter the computer name of the PG/PC and the name of the directory (share
name) that you wish to access.
PLEASE SELECT
1 Connect to Network Drive
2 Show connected Network Drives
3 Disconnect from all Network Drives
4 Change Network Settings
Machine Name :
User Name : USER
Transport Protocol : NETBEUI
Logon to domain : No
PLEASE SELECT:
Note
If a new name is not entered, the old name is retained.
Note
If a connection has already been established with NETBEUI, you must restart the
system to toggle to TCP/IP. If a connection has not yet been established, you can
toggle to the other protocol immediately.
If a connection has already been established with TCP/IP, you must restart the
system to toggle to NETBEUI.
If you toggle to TCP/IP as the current protocol, the extended Change Network
Settings screen includes the additional option 6 Change TCP/IP settings.
PLEASE SELECT:
1 Change Machine Name (for DOS Net only)
2 Change User name
3 Toggle Protocol (NETBEUI or TCPIP)
4 Toggle logon to domain (Yes or No)
6 Change TCPIP settings
WARNING:
You already had a connection with TCPIP, now you want to toggle the protocol.
Note
All IP address/subnetmask entries in this screen form must be entered with a
space as separator rather than the usual full stop.
Example: 192 168 3 2 instead of 192.168.3.2
2 Change IP Address
If "Get IP Addresses" is set to manually, the IP address of the PG/PC is entered
here. DHCP cannot be selected.
3 Change Subnetmask
If "Get IP Addresses" is set to manually, the subnetmask of the PG/PC is entered
here. DHCP cannot be selected. Notation is the same as for IP address with a
space as separator.
4 Change Gateway
If "Get IP Addresses" is set to manually, the gateway is entered here. The gateway
is entered as an IP address.
General procedure
The hard disk of the PCU is pre-partitioned for SINUMERIK 840D operation and
further SINUMERIK applications on delivery and the software required for a basic
start-up is installed:
• The boot software and other software needed for start-up are stored on C:
PCU
H a r d d is k
P r im a r y p a r t i t io n E x p a n d e d p a r t it i o n P r im a r y p a r t i t io n P r im a r y p a r t it io n
a c tiv e w ith lo g ic a l d riv e
Welcome to SINUMERIK
These SINUMERIK products will be installed now:
<product 1>
<product 2>
<product 3>
...
Install NOW
CANCEL Installing
The buttons can be selected by pressing the Tab key and activated by pressing
Enter.
Effect of the buttons:
Install NOW:
All the products displayed are installed one after another in the sequence in which
they are listed. If a reboot is required to activate the installation, it is executed
immediately after installation of the corresponding program. The system may
therefore be rebooted several times until all products are installed.
CANCEL Installing
Nothing is installed and the screen is not displayed again the next time the system
is rebooted. Other installations can then only be carried out explicitly in Windows
mode by activating the setup.exe programs directly in the setup directories.
Preconditions
You will need a PC or a PG with a CD ROM drive.
INTERSVR is used on the external PG/PC to transfer the software to the PCU. It
can only be operated under DOS/Win3.11/Win95/Win98 if the PG/PC has a hard
disk partition with a FAT16 file structure (not FAT32 !).
General procedure
This function transfers the HMI software to be installed to D:\INSTALL. The actual
installation is carried out by Windows NT on the next boot provided the software
includes an exe file, e.g. "setup.exe".
! Important
Before you attempt to install the software, make sure that there is sufficient
memory available on partition D of the hard disk.
Transfer
You must use the parallel (not the serial) interface to transfer the HMI software.
Operator actions
1. Switch off the PCU
2. 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.
3. Copy the HMI_Advanced directory from the CD to drive C:\ on the hard disk of
your PG/PC and rename it "MMC2". If there is insufficient memory available on
drive C:\ or it does not have a FAT16 file structure, you can also use another
local hard disk drive (e.g. D:\). The software cannot be installed directly from
the CD.
4. Installation of the HMI software is started by calling it from the Windows menu
Start -> Run -> Intersvr C: (or the drive on which the MMC2 directory is
located).
IMPORTANT: When your PC/PG is in this state, the PCU MUST be switched
off. (If the PCU is switched on, switch it off now).
5. SWITCH ON the PCU and select "Service menu" in the boot manager.
(Hidden menu option, see 3.3.6 Service menu).
9 Reboot (Warmboot)
6. Select option 1
passwd:
5 REBOOT
General procedure
This function transfers the HMI software to be installed to D:\INSTALL. The actual
installation is carried out by Windows on the next boot provided the software
includes an exe file, e.g. "setup.exe".
! Important
Before you attempt to install the software, make sure that there is sufficient
memory available on partition D of the hard disk.
Preconditions
You will need a PC or a PG with a CD ROM drive.
You will also need a full keyboard on the PCU.
To install the software you will need the CD ROM with the system software.
Transfer
You must use the parallel (not the serial) interface to transfer the HMI software
installation.
When to use
This method must be used if your PC/PG only has partitions with a FAT32 file
structure.
Operator actions
1. Copy INTERLNK.EXE from the HMI directory on the CD to
WINDOWS\COMMAND on the PC/PG. Insert the following line in
CONFIG.SYS:
device=c:\windows\command\interlnk.exe /AUTO
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 "Service menu" in the boot manager [hidden menu entry]
PLEASE SELECT:
9 Reboot (Warmboot)
5. Select option 8
The system prompts you for a password with:
passwd:
- System
- Manufacturer
- Service
7. Now copy the entire contents of the HMI_Advanced directory on the CD to the
D:\INSTALL directory on the PCU. On completion of the transfer close
INTERSVR on the PCU by pressing Alt + F4. The system boots to Windows.
8. In Windows NT/XP: The software is now installed automatically with
InstallShield from the PCU. You can operate the InstallShield prompt boxes
with TAB and the cursor keys (TAB corresponds to the END key on the
OP0xx).
9. The system starts up after the PCU has rebooted.
General procedure
This function transfers the HMI software to be installed to D:\INSTALL on the PCU.
The actual installation is carried out by Windows on the next boot provided the
software includes an exe file, e.g. "setup.exe".
! Important
Before you attempt to install the software, make sure that there is sufficient
memory available on partition D of the hard disk.
Note
If you are using a different language version of the Windows system, the terms
used in the following setting operations may be different. The sequence of
operations as specified below, however, is always the same.
Operator actions
While the PCU is booting (after switching the control off and then on again):
1. Select the "Service Menu" [hidden menu option] in the boot manager.
PLEASE SELECT:
2. Select option 1.
passwd:
- System
- Manufacturer
- Service
5 REBOOT
3. Select option 3.
An input screen form is displayed in which you can specify settings for the network
if necessary. See 7.2 Settings for network drives
4. Select option 1 to specify the settings for a network connection. A screen form
containing the detailed network functions is opened.
PLEASE SELECT
1 Connect to Network Drives
2 Show connected Network Drives
3 Disconnect from all Network Drives
4 Change Network Settings
5. Select option 1.
Enter the letter of the PCU drive from which the connection must be accessed (e.g.
"G")
Enter the computer name of the PG/PC and the name of the directory (share
name) that you wish to access.
PLEASE SELECT
1 Connect to Network Drive
2 Show connected Network Drives
3 Disconnect from all Network Drives
4 Change Network Settings
7. Press 9 twice
PLEASE SELECT
1 Manage Network Drives
8. Select option 4.
An input screen form appears in which you can specify the installation directory
(e.g. HMI_INST):
PLEASE SELECT:
9. Select option 5.
Install
• The system starts the transfer from the PG/PC to the PCU.
• The PCU is automatically rebooted after the transfer.
• Select "SINUMERIK" in the boot manager. The software that has just been
transferred is now installed, menu-assisted in some cases.
The system checks whether the D:\INSTALL directory already contains files.
Note
If the software cannot be copied to the D:\INSTALL directory on the PCU, then
the system cannot start the installation.
LPT1: LPT:
Preconditions
• Ghost version 6.x/7.x is installed on the PCU and on the PG/PC.
Note
The PCU and PG/PC must both be using either 6.x or 7.x. Windows XP requires
version 7.x.
• The directory in which the backup image is to be stored exists on the PG/PC.
• There is sufficient free memory on the PG/PC
• One of the operating systems MS-DOS 6.X, Windows 3.x, Windows 95 or
Windows 98 is present on the PG/PC.
• The PCU and PG/PC are connected with the parallel cable (6FX2002-1AA02-
1AD0) or a LapLink cable.
• In the BIOS of the PCU and of the PG/PC, the parallel interface is set to EPP or
ECP.
Operator actions
While the PCU is booting (after switching the control off and then on again)
PLEASE SELECT:
9 End (Warmboot)
2. Select option 7.
passwd:
4. Select option 1.
Note
The paths are default settings and depend on the drive.
You can change these path names.
"Optional" start
The following steps down to the next separator line are only applicable if you need
to change the default settings for GHOST.
PLEASE SELECT:
Here you can set the interface type, the backup image path and the backup image
split mode.
Set interface
• Change interface:
Select <1> Set Connection Mode PARALLEL (LPT:)
(default) and confirm
Notice:
For the parallel connection described here the interface type must always be set
to PARALLEL.
"Optional" end
The following steps are always applicable.
--------------------------------------------------------------------------------------------------------------
Choosing this menu option opens the following menu if local partition data backups
already exist (see Backup/restore partition):
PLEASE SELECT:
If you do NOT want to backup local images (substantial reduction in transfer time
and memory), choose 1 instead of 2.
Note
Local images are data backups of partitions C, E, F on the local partition D of the
PCU. See 7.5.
• PG/PC:
In a DOS window or at the DOS level enter the command
ghost -Ips to start Norton Ghost.
• PCU:
Type "Y" in the message box to acknowledge and start the backup.
The Norton Ghost message box appears with:
display of the transfer progress
display of the paths used
details of the amount of data to be transferred
7. PCU
Aborting the backup triggers the prompt:
Do you want to try to backup again [Y,N] ?
Press "N" to return to the main menu.
Press "Y" to restart the backup from scratch.
LPT1: LPT:
PCU PG/PC CD
Preconditions
• Ghost version 6.x is installed on the PCU and on the PG/PC.
• The directory in which the restore image is stored exists on the PG/PC.
• One of the operating systems MS-DOS 6.X, Windows 3.x, Windows 95 or
Windows 98 is present on the PG/PC.
• The PCU and PG/PC are connected with the parallel cable (6FX2002-1AA02-
1AD0) or a LapLink cable.
• In the BIOS of the PCU and of the PG/PC, the parallel interface is set to EPP or
ECP.
Operator actions
1. Switch on the PG/PC and insert the CD in the drive.
While the PCU is booting (after switching the control off and then on again)
2. Select the "Service Menu" [hidden menu option] in the boot manager.
The following menu is displayed:
PLEASE SELECT:
9 Reboot (Warmboot)
3. Select option 7.
passwd:
PLEASE SELECT:
5. Select option 1.
PLEASE SELECT:
Note
The paths are default settings and depend on the drive. You can change these
path names.
--------------------------------------------------------------------------------------------------------------
"Optional" start
The following steps are only applicable if you wish to change the default settings.
PLEASE SELECT:
Here you can set the interface type and the restore image path.
Set interface
6.1 Change interface:
Select <1> Set Connection Mode PARALLEL (LPT:)
(default) and confirm.
Notice:
For the parallel connection described here the interface type must always be set to
PARALLEL.
"Optional" end
The following steps are always applicable.
--------------------------------------------------------------------------------------------------------------
Please select the SYSTEM BASE the image was created by!
PLEASE SELECT:
Select the operating system on which the restore image is based. This affects the
type of hard disk partitioning that is performed.
When you select the appropriate operating system, another menu opens:
Specify whether you want a standard hard disk partitioning, i.e. with a fixed number
and size of partitions (depending on the operating system), or whether you want to
define the partitioning yourself. In the first case Norton Ghost automatically sets
the partition parameters, whereas in the second case the user sets the partition
parameters in Norton Ghost.
In the third case the partition is taken from the GHOST image.
* PG/PC:
In a DOS window or at the DOS level enter the command
ghost -lps to start Norton Ghost.
* PCU:
Type "Y" in the message box to acknowledge and start the restore process.
* PCU:
The Norton Ghost message box appears with:
display of the transfer progress
display of the paths used
details of the amount of data to be transferred
! Caution
A boot disk is required to boot the PCU.
Booting
8. After a successful restore you must reboot the system.
HMI
The procedure for restoring the data backup of a complete HMI hard disk, so that
all user and system data are available in the event of servicing, is described below.
Norton Ghost
Using Norton Ghost® the entire contents of a PCU hard disk can be stored as a
disk image file. This disk image file can be stored on various data carriers for a
later restoration of the hard disk.
Norton Ghost® is factory-installed on every PCU module and on replacement hard
disks.
For further information please go to "www.ghost.com" or refer to the previous
section.
Note
Recommendation:
Archive the hard disk backup (hard disk image) including the Norton Ghost utility
on CD.
Restoring
a data backup
Preconditions:
• Ghost is installed on the PG.
• A new replacement hard disk has been obtained.
• The HMI is connected to the PC/PG with a parallel cable
• The operating system Windows 3.x or Windows 95 is installed on the PC/PG
ÉÉÉ
and a CD drive is available.
1. Install the new replacement hard disk in the PCU or install the new HMI (see
instructions supplied with the hard disk)
– Click the hard disk into place
– Plug in the connecting cable from the hard disk to the PCU
– Secure the hard disk with the 4 knurled screws
– Release the transport lock: Turn towards "operating" until it engages.
References: /BH/Operator Components, Manual
Note
The replacement hard disk does not include the Windows NT operating system or
HMI system software.
* PG/PC:
In a DOS window or at the DOS level enter the command
ghost –lps to start Norton Ghost.
* MMC:
Start the restore process by acknowledging the message window (Yes).
* MMC:
The Norton Ghost message box appears with:
display of the transfer progress
display of the paths used
details of the amount of data to be transferred
Note
If the data transfer is interrupted during the restore process, the system on the
hard disk will be incomplete. An HMI boot disk containing the MS-DOS_6.x boot
software and the Norton Ghost utility will be needed.
Ethernet Ethernet
PCU PG/PC
Preconditions
• Ghost version 6.x/7.x (>= 7.x required for Windows XP) is installed on the PCU
and on the PG/PC.
• The Ghost versions on the PCU and the PG/PC must be the same.
• The directory in which the backup image is to be stored exists on the PG/PC.
• There is sufficient free memory on the PG/PC
• Windows (any version) is installed on the PG/PC.
• The PCU and PG/PC are connected with an Ethernet cable.
Operator actions
While the PCU is booting (after switching the control off and then on again):
1. Select the "Service Menu" [hidden menu option] in the boot manager.
The following menu is displayed:
PLEASE SELECT:
9 Reboot (Warmboot)
2. Select option 7.
passwd:
PLEASE SELECT:
Select option 1.
PLEASE SELECT:
Note
The paths are default settings and depend on the drive.
You can change these path names.
--------------------------------------------------------------------------------------------------------------
"Optional" start
The following steps are only applicable if you wish to change the default settings.
PLEASE SELECT:
Here you can set the interface type, the network connection, the backup image
path and the backup image split mode.
Set interface
• Change interface:
Select <2> Set Connection Mode LOCAL/NETWORK
and confirm.
Notice:
For the network connection described here the interface type must always be set to
LOCAL/NETWORK.
Choose whether you wish to split the backup image into portions and, if so,
enter the split size (max. split size: 2048 MB; default split size:
640 MB). The names of the split files are assigned as follows:
<name>.gho
<name>.001
<name>.002
<name>. ...
"Optional" end
--------------------------------------------------------------------------------------------------------------
The following steps are always applicable.
Selecting this option opens the following menu if local partition data backups are
available: (See Backup/restore partitions).
PLEASE SELECT:
If you do NOT want to back up local partition data (substantial reduction in transfer
time and memory), select:
You are prompted to check whether this directory exists on the PG/PC.
* PCU:
Type "Y" in the message box to acknowledge and start the backup.
* PCU:
7.5.2 Restoring the PCU hard disk from the PG/PC hard disk
Ethernet Ethernet
PCU PG/PC
Preconditions
• Ghost version 6.x/7.x is installed on the PCU and on the PG/PC.
• The directory in which the restore image is stored exists on the PG/PC.
• Windows (any version) is installed on the PG/PC.
• The PCU and PG/PC are connected with an Ethernet cable.
Operator actions
1. Switch on the PG/PC and insert the CD in the drive.
While the PCU is booting (after switching the control off and then on again):
2. Select the "Service Menu" [hidden menu option] in the boot manager.
PLEASE SELECT:
9 Reboot (Warmboot)
3. Select option 7.
The system prompts you for a password with:
passwd:
PLEASE SELECT:
5. Select option 1.
PLEASE SELECT:
Note
The paths are default settings and depend on the drive. You can change these
path names.
--------------------------------------------------------------------------------------------------------------
"Optional" start
The following steps are only applicable if you wish to change the default settings.
PLEASE SELECT:
Set interface
6.1 Change interface:
Select <2> Set Connection Mode LOCAL
and confirm.
! Important
For the network connection described here the interface type must always be set
to LOCAL/NETWORK.
See 7.2:
Enter the complete path for the HMI.gho restore file on the PG/PC, e.g.
C:\SINUBACK\PCU\HMI.gho
"Optional" end
--------------------------------------------------------------------------------------------------------------
PLEASE SELECT:
Select the operating system on which the restore image is based. This affects the
type of hard disk partitioning that is performed.
When you select the appropriate operating system, another menu opens:
Specify whether you want a standard hard disk partitioning, i.e. with a fixed number
and size of partitions (depending on the operating system), or whether you want to
define the partitioning yourself. In the first case Norton Ghost automatically sets the
partition parameters, whereas in the second case the user sets the partition
parameters in Norton Ghost. In the third case the image to be loaded determines
the partitioning.
CAUTION:
The machine name shouldn't be changed, if
1. the restore image is a backup image of your machine
AND
2. the name of your machine hasn't been changed since
creating the backup image.
PLEASE SELECT:
You can choose to enter a computer name for the PCU yourself or have a name
generated automatically:
The new computer name (including the name generated randomly with option 2)
and the new system ID (SID) are assigned to the PCU with the Ghostwalker utility.
PLEASE SELECT:
You can change the computer name again at a later stage by selecting option 5
"Change Machine Name (for Windows and DOS net)" in the submenu
Backup/Restore-> Harddisk Backup/Restore with GHOST->Configure GHOST
Parameters. This change is also made via Ghostwalker.
Booting
8. After a successful restore you must reboot the system.
! Important
If the restore process was interrupted, the system on the hard disk will be
incomplete. In this situation a boot disk with Norton Ghost and the network
software is required. The boot disk is available from eSupport.
To load/restore software and data for the new hard disk, follow the instructions in:
• 7.3 Software installation/update
• 7.4 Data backup/restore with a parallel connection
• 7.5 Data backup/restore with an Ethernet connection
In addition to backing up the entire contents of the hard disk onto an external drive,
you can also back up partitions C:, E:, and F: of the PCU locally onto partition D: of
the PCU (partition data backup).
C: E: F: D:
The local backup image generated by a partition data backup can be used to
restore partitions C:, E: and F: again if necessary (partition data restore).
C: E: F: D:
C: E: F: D:
For a partition data restore process or a partition E data restore process, any of the
local backup images located on partition D: can be used in theory.
Naturally, however, for a partition E data restore the local backup image to be used
must be chosen with care: the registry entries for all applications installed on
partition F: will need to be present on the partition E: to be restored.
Definition of a local backup image for a possible emergency and simple starting of
the partition E data restore in the event of an emergency are supported in the
Service menu.
The maximum number of local backup images that can be stored simultaneously
on partition D: (<=7) can be set.
C: E: F: D:
Operator actions
While the PCU is booting (after switching the control off and then on again):
1. Select the "Service Menu" [hidden menu option] in the boot manager.
PLEASE SELECT:
9 Reboot (Warmboot)
2. Select option 7.
The system prompts you for a password with:
passwd:
4. Select option 4.
PLEASE SELECT:
--------------------------------------------------------------------------------------------------------------
"Optional" start
The following steps are only applicable if you wish to change the default settings.
PLEASE SELECT:
"Optional" end
--------------------------------------------------------------------------------------------------------------
The following steps are always applicable.
Back up partitions
6. Select option 2.
< 2 > Partitions Backup, Mode LOCAL
You are prompted for the name under which the new local backup image is to be
stored, e.g. BACKUP1. Length of name: max. 7 characters.
Under "Description" you are asked whether you want to store an additional
description for the local backup image, e.g. "Data backup1 by Hugo".
In the restore process this additional description is offered as a selection text in the
list of available backup images (if there is no description, the name of the backup
image is displayed in the list).
You are asked whether you want the new local backup image to be used as an
emergency backup image too (and an existing emergency backup image to be
deleted).
C: E: F: D:
Operator actions
While the PCU is booting (after switching the control off and then on again):
1. Select the "Service Menu" [hidden menu option] in the boot manager.
PLEASE SELECT:
9 Reboot (Warmboot)
2. Select option 7.
The system prompts you for a password with:
passwd:
PLEASE SELECT:
4. Select option 4.
PLEASE SELECT:
Restore partition
5. Select option 3.
< 3 > Partitions Restore, Mode LOCAL
You are asked which local backup image you wish to restore, e.g. "Data
backup1 by Hugo".
On confirming your choice the warning "All data will be overwritten" is displayed
and restoration of the chosen backup image to partitions C:, E: and F: is started.
After each restore process partitions E: and F: are checked by the test program
CHKDSK the next time Windows is started.
The system is rebooted between checking E: and F:.
C: E: F: D:
Operator actions
While the PCU is booting (after switching the control off and then on again)
1. Select the "Service Menu" [hidden menu option] in the boot manager.
PLEASE SELECT:
9 Reboot (Warmboot)
2. Select option 7.
The system prompts you for a password with:
passwd:
PLEASE SELECT:
4. Select option 4.
PLEASE SELECT:
Restore partition E
5. Select option 4.
< 4 > Partition E (only Windows) Restore, Mode LOCAL
You are asked for the local backup image whose partition E: (= Windows partition)
you wish to restore, e.g. "Data backup1 by Hugo".
PLEASE SELECT:
The next time Windows NT is started, partition E: is checked by the test program
CHKDSK.
Operator actions
While the PCU is booting (after switching the control off and then on again)
1. Select the "Service Menu" [hidden menu option] in the boot manager.
PLEASE SELECT:
9 Reboot (Warmboot)
2. Select option 7.
PLEASE SELECT:
4. Select option 4.
PLEASE SELECT:
From the list of backup images, select the one you wish to delete.
The system asks you whether you really want to delete the image.
Operator actions
While the PCU is booting (after switching the control off and then on again):
1. Select the "Service Menu" [hidden menu option] in the boot manager.
PLEASE SELECT:
9 Reboot (Warmboot)
2. Select option 7.
passwd:
PLEASE SELECT:
4. Select option 4.
PLEASE SELECT:
5. Select option 1.
< 1 > Configure GHOST Parameters:
PLEASE SELECT:
6. Select option 2.
You are asked which local backup image you want to use as the emergency
backup image (this choice can be changed at any time).
3 Data backup2
[02-05-2000; 07:07:14pm]
N No Emergency Image
N No Emergency Image
b) Based on the emergency backup image (provided that a local backup image
has been defined as the emergency backup image, see Subsection 7.7.6)
Operator actions
While the PCU is booting (after switching the control off and then on again)
1. Select the "Service Menu" [hidden menu option] in the boot manager.
PLEASE SELECT:
9 Reboot (Warmboot)
2. Select option E.
passwd:
The next time Windows NT is started, partition E: is checked by the test program
CHKDSK.
It is used as a platform for network operation (e.g. for installing HMI system
software), for setting the processing environment for the HMI system software or
for system operations such as SIMATIC STEP7 authorization, hard disk check,
version check, etc.
For details, please refer to 3.5 Basic functions of the SINUMERIK desktop.
Windows NT Windows XP
The network connection is pre-installed in Connect the Ethernet cable for
so far as all that is required for TCP/IP TCP/IP communication.
communication, after plugging in the The default setting is DHCP.
Ethernet cable, is to enter the IP address
of the PCU or select the use of a DHCP
server.
To do this, select The settings can be adjusted in
Start→ Settings→ Control Panel→ Start→ Settings→Network
Network, Protocols tab, and set the Connections→Local Area
properties to TCP/IP Protocol. Connection→ Properties.
At this stage at the latest, the PCU must At this stage at the latest, the PCU
be given a unique computer name to must be given a unique computer
identify it in the network. Select name to identify it in the network.
Start→Settings→Control Panel→Network, Select Start→Settings→Control
Identification tab Panel→System, Computer Name tab,
to enter an appropriate name. Change button to enter an appropriate
name.
In addition to the TCP/IP protocol, the NETBEUI protocol is also pre-installed for
network operation.
Windows NT Windows XP
Item supplied Item supplied
SIMATIC STEP7 V5.1 for PCU50/ SIMATIC STEP7 V5.2 for PCU50/ 70
70/MMC103 on CD on CD
Order No.: 6FC5252-5AY01-1AG0 Order No.: 6FC5252-5AY01-2AG0
Components: Components:
SIMATIC STEP 7 V5.1 SP2 and SIMATIC STEP 7 V5.2 and
AddOn for SINUMERIK 810D/840D(i) AddOn for SINUMERIK 810D/840D(i)
Form in which supplied: , Form in which supplied: ,
Data volume: approx. 430 MB Data volume: approx. 480 MB
System requirements System requirements
PCU50/70 with basic software 6.1.9 or PCU50/70 with basic software 7.3.2 or
higher higher
Note (NT)
If STEP7 5.0 is already installed, we recommend that you uninstall it and delete
the associated directory Add_on\step7.
! Important
The "MPI Drivers" pack on the PCU 50/70/MMC103 is part of the HMI/MMC103
software and must not be uninstalled.
Operation in Windows NT
This procedure also applies to MMC103 with Windows NT 4.0.
You must follow the installation sequence described here !
1. Start up the PCU50 in the Windows NT desktop (via Service menu option 4,
then 1).
5. Call the desktop icon "STEP7 Authorizing". STEP7 is now authorized and can
now be used to start the HMI Advanced software (2nd menu bar in the area
menu, protected with access level 3).
Operation in Windows XP
Operation is the same as for Windows NT, except that the software version for
STEP7 must be 5.2 or higher.
Note
STEP7 must not be installed in partitions D: or E:.
If STEP7 version 5.1 is installed on the control and subsequently you wish to
reinstall version 5.0, after uninstalling version 5.1 and before installing version 5.0
the directory
F:\mmc2\step7\dat
Delivery
The software is supplied on CD together with a readme file (in English).
Preconditions
Windows NT 4.0 with Service Pack 6 is required.
Installation
Establish a connection between the PCU 50/70 and the CD drive as described in
"Setting up access to external drives/computers".
Usable media
Following installation of the CardWare V6.0 software, the PCMCIA interface is
ready to operate (Plug & Play) the following components (tested for PCU 50):
The manufacturers of the CardWare V6.0 software run a knowledge base on their
website, where you can find other PCMCIA components that are supported.
Notes on use
Ensure that before removing a flash card you switch the card to "Slot Power Off".
(See README.TXT)
SINUCOPY is not designed to be used with this software and has not been tested
with it.
Restrictions
The current restrictions can be found in PRODIS.
MMC2 includes:
• servers and COM objects
• master control and
• associated INI and NSK files with MMC.INI from HMI base.
ADD_ON, OEM and USER are used in the same way as before
The number of files in each directory (each *.WPD workpiece directory for
workpieces) is limited to 1000 files.
The total of 100,000 does not apply to the other DM directories, however each
directory is also limited to a maximum of 1000 files, e.g. a maximum of 1000
archives in the archive directory. Network drives are also limited to a maximum of
1000 files in each directory.
The options that are available depend on the file size and the available memory
space. A large number of files slows down the display building for directory
displays.
8 Diagnostics
8
8.1 Action log ................................................................................ IM4/8-242
8.1.1 Log file ................................................................................. IM4/8-245
8.1.2 Displaying the log file/setting the action log ........................ IM4/8-245
8.1.3 Outputting the log file........................................................... IM4/8-246
• Logging of alarms
• Logging of key actuations (SINUMERIK ShopMill, ShopTurn, ManualTurn)
• Output of log file via RS 232 C (V.24)
• The action log is password-protected.
• It can be switched on and off via
• MD 9012 ACTION_LOG_MODE or
• the "Action log settings" screen form in the Setup operating area.
9012 ACTION_LOG_MODE
MD number Action log settings
Default value: 254 Min. input value: 0 Max. input value: 0xffff
Changes effective after POWER ON Access level (R/W) 2/2 Unit: -
Data type: DWORD Applies from version 5.2
Meaning This MD can be used to enable/disable the action log and to define a
choice of the data to be logged.
Bit 0 =1 Action log ON (default)
=0 Action log OFF
Bit 1 =1 MMC 103: Variable services (write access to
geometrical data, e.g. tool compensation) are logged
For the meaning of variables refer to the help texts in
the Parameters operating area under Variable Views
(default)
=0 Variable services are not logged
Bit 2 =1 MMC 103: PI services (e.g. program selection) are
logged, for the meaning of variables refer to the help
texts in the Parameters operating area under Variable
Views (default)
=0 PI services are not logged
Bit 3 =1 MMC 103: Domain services (e.g. load/unload program)
are logged (default)
=0 Domain services are not logged
Bit4 =1 Changes to the alarm status are logged (default)
=0 Changes to the alarm status are not logged
Bit5 =1 Key actuations are logged
- SINUMERIK ShopMill, ShopTurn, ManualTurn only
(default), not in HMI Advanced
=0 Key actuations are not logged
Bit6 =1 Channel status/override is logged (default)
=0 Channel status/override is not logged
Bit7 =1 MMC 103: Softkey actuations and menu changes
are logged. For Siemens internal use only
(default)
=0 Softkey actuations and menu changes are not
logged
If the action log is switched on, the files that can be logged are recorded by default.
The following events can be logged:
Variable services
All variables that are written via an input field (e.g. write access to geometrical data
such as tool compensation and zero offsets) can be logged. A declaration of the
variables can be called by means of the Help function in the Parameters operating
area under Variable Views.
PI services
All PI services (e.g. program selection, file deletion, tool deletion) can be logged. A
declaration of the variables can be called by means of the Help function in the
Parameters operating area under Variable Views.
Domain services
All domain services (e.g. load/unload program) can be logged.
Alarm status
All NC/PLC and MMC alarms and messages that are displayed can be logged.
Channel status/override
NC/PLC statuses can be logged using information about the channel status and
the position of the override switch. At least some of these statuses, where they can
be recorded by time, are used to verify the operation of the MCP.
The current log file is displayed on the screen of the operator panel front in the
Diagnostics operating area in the Service Displays -> Action Log menu in the
"Action Log File" screen.
The vertical softkey "Read out via V.24" can be used to output and archive the log
file.
The selected setting must be confirmed by pressing the "Save settings" softkey.
The bit is set and reset from the PLC at the user interface (as with key lock, screen
darkening, etc.).
The MMC evaluates the rising edge of the signal (i.e. a transition from 0 to 1) and
creates the log file when the signal comes. The MMC only reads the data, i.e. the
signal must be reset from the PLC/user program.
If the bit is already set when the MMC boots, the MMC does not respond to the
value of the bit (until it is reset and set again).
Operating sequence
1. Switch on the control and select Setup mode (press "6" when the DOS or
Windows screen appears).
2. In the Service menu choose the "A__Actionlog" menu (press "A"). The
"A__Actionlog" menu is only available if a log file exists.
3. The current log files (AC_LOGA.TXT and AC_LOGB.TXT) are copied to the
part program directory. The message "The action log is filed in the part
program directory for output (files AC_LOG?.TXT)" is then displayed.
4. Press any key to return to the main menu.
5. After rebooting the control you can read out the log files (e.g. onto a floppy
disk) from the Services operating area in the Data Out -> Via V.24 menu.
Operating sequence
1. Switch on the control.
2. As the system boots you are prompted for crash files from the log file. If one or
more crash files exists, the following message appears: "The action log (crash)
is filed in the part program directory for output (files AC_LOG?.TXT). Please
confirm that you will file out the files immediately after start of MMC(V24,
Disk,..)".
The current crash files (AC_LOGP1.TXT to AC_LOGPn.TXT) are copied to the
part program directory.
3. After booting the control you can read out the log files (e.g. onto a floppy disk)
from the Services operating area in the Data Out -> Via V.24 menu.
Procedure
1. Select the DIAGNOSTICS area
2. Select the "Service displays" softkey
3. Select the "Version" softkey
The NCK software versions are displayed first by default. To view the HMI software
versions, press the "MMC" softkey.
Notes
Software components
• MPI driver V5.0
• NCDDE server
• Alarm server
• Data/archive server
• Language tool
• Startup tool
• Standard HMI system
Operating sequence
1. Insert the CD in the CD drive
2. Start setup.exe
3. Select a language
4. Specify the destination folder
5. Select:
- Online (with communication to NC)
The system asks whether you wish to install the MPI drivers
- Turning
7. The system lists all the entries you have made.
8. On confirmation the copy process starts
9. At the end of the copying process you are prompted to restart the PC.
Windows NT/XP
Fig. 9-1 Separate desktops for HMI software and other applications
! Important
1. The task manager key combination CTRL-ALT-DEL only works in the
standard desktop. In dynamic desktops the task manager can only be
called directly from the taskbar.
2. When a dynamic desktop is closed, the application that is started
automatically by inclusion in HMIDesk.ini is closed with the desktop.
Manually started applications continue to run, however.
The applications can no longer be used, however, since they are not
displayed in other desktops. If the dynamic desktop is started again later,
applications that are still running are visible again and can continue to be
used.
3. All external applications (ProTool, Transline) that use the basic HMI
Advanced system must be started on the HMI desktop if they are to be
executed in parallel with HMI Advanced.
Background: The master control subsystems cannot be used beyond
desktop limits because Windows restricts window communications to
one desktop.
The user interface for the desktop switch application can be configured.
Options:
• Keyboard hotkeys
• Dialog boxes
• Icons in the taskbar
Hotkeys
Alt-1 Switches to desktop 1 (user's standard desktop)
Alt-2 Switches to desktop 2 (HMI Advanced desktop in
standard configuration)
Alt-3 Switches to desktop 3 (optional additional user desktop)
Alt-4 Switches to desktop 4 (optional additional user desktop)
Dialog boxes
When configured accordingly (see below) this dialog box can be displayed on
screen in the current desktop. Click the left-hand side to activate the standard
desktop (1), click the right-hand side to activate the HMI desktop.
Note
If WindowOnTop = FALSE is configured (see below), the box must be moved to
the front first by pressing Alt-Tab if it is covered by the application.
The configured desktops are displayed on the right of the taskbar. The active
desktop is highlighted. To switch desktops, click the desktop number you require.
1 Standard desktop
2 HMI desktop
(3, 4) Other desktops optional
Note
Since the taskbar is covered up in the HMI desktop, the user must first make it
visible by pressing the left or right Window key in order to be able to actuate the
corresponding desktop icons.
Desktop n section
StartupApplication = "Path\Program.exe"
Note
For the HMI desktop (2) the path and associated program name, which point to
the current HMI installation, are set automatically.
When switching between desktops, the desktop switcher sets the appropriate color
scheme automatically.
Notes
Introduction
With software version 4.4 and higher, you can configure your own dialog windows
(dialog screens) and display them on the MMC/HMI Embedded/HMI Advanced.
The appearance of the dialog windows is configured purely by text (COM file in the
cycles directory). The dialog window is opened and closed by function calls from
the parts program.
This does not affect the HMI/MMC system software (user interface).
User-defined dialog windows cannot be called simultaneously in different channels.
The "Configure Windows in the NC Program" function is also referred to as the
"command channel".
Application
One possible application of user dialog windows is, for example, to selectively
assign current values to particular user variables (GUD) prior to a parts program
run.
10.1 Setup
Up to 2 channels:
The "command channel" is activated by default for channels 1 and 2.
• More than 2 channels:
For MMC 103/PCU50 the "command channel" must be activated (if the
SIEMENS measuring cycles have not yet been installed).
This requires a modification to be made to the file C:\MMC2\ COMIC.NSK in the
Setup operating area:
- Select the file c:\mmc2\comic.nsk in the "Setup" operating area with the
"MMC" – "Editor" – "Load" softkeys
- Insert the following text (after channel 1 and 2):
REM CHANNEL
TOPIC(machineswitch) COMIC_START(COMIC001MachineSwitch"...)
[compare the text for channels 1 and 2]
When the control is restarted (off/on), the command channel is activated for the
corresponding channel.
Parameters:
Operating area
Name of softkey with which the configured user dialogs can be called. Default
entry: CYCLES, displayed as "Cycles" on softkey 14 and accessible via the ETC
key.
Command
Picture_on select screen
Picture_off deselect screen
Com file
Name of the dialog box file (max. 8 characters, in the user cycles or standard
cycles directory CST.DIR). The dialog screen design is defined here. The dialog
screen is used to display user variables and/or comment texts.
Graphics file
File name of a BMP graphic to be inserted.
• If the graphics file is stored in the CST.DIR directory, the name of the graphics
file must be changed to *.AWB (the control does not accept *.bmp).
• If the graphics file is stored in the "Dialog Programming/Help" directory, the
name *.BMP can be retained.
From HMI version 6.2 onwards, *.bmp files are stored in resolution-specific
subdirectories:
These are:
For standard cycles:
\CST.DIR\HLP.DIR\640.DIR For 640 dpi resolution
\CST.DIR\HLP.DIR\800.DIR For 800 dpi resolution
\CST.DIR\HLP.DIR\1024.DIR For 1024 dpi resolution
Text variables
Screen header or comment text from a text variable in the COM file
Acknowledgment mode
"S" Synchronous, acknowledgment via "OK" softkey
MMC("CYCLES,PICTURE_ON,T_SK.COM,SCREEN1,MGUD.DEF,SCREEN_3.AWB,TEST_1,A1","S")
Operating area
Acknowledgment mode:
Synchronous, Asynchronous, No Quit
*) On the MMC103/ PCU50, the filename is T_SK_GR.COM, but here the language
identifier "GR" is omitted.
%_N_UGUD_DEF
;$PATH=/_N_DEF_DIR
Channel to which
it applies
Data type
//C3(Picture3)
R/ 15 75 / 5 /COMMENT,%1,%2,%3/ W,RJ / TEST_1 / ....)
Variable type
real integer string
Preset value
for user var.
Access type:
W = write/read
R = read only
W, r j = write/read with comment
no j: left-justified to input/output field
j: right-justified to input/output field
Note
For variable names, text variables and cycle names, capital letters must be used.
Text variables
[TEXT VARIABLES]
Ref. parameter
for MMC command
[SCREEN3]
SK1 = END
SK2 = Screen2
Softkeys SK0 to SK15 can be configured
Text variable
TEXT VARIABLES]
A1 =............Example1: MMC command without acknowledgment………
Sequence
The user variable TEST_1 from GUD4.DEF with header A1 is displayed for a short
time.
Text variable
[TEXT VARIABLES]
The 7th parameter is interpreted as the display time for the mode without
acknowledgment (10 seconds).
The contents of the table are then deleted. The screen form remains on the screen
until Picture_off is selected.
The 8th parameter (T1) is the text variable for the screen header. If there is no
entry, the operating area name (cycles) is displayed.
The parameters 9 to 23 are optional text variables (in this case "G1=optional text
variable").
In this COM file, the optional text variables must be loaded with default values in
the "[Text variables]" section.
Sequence
The comment text from the COM file (USER VAR TEST_1) is expanded in this
example at the position of the first wild card (%1) by the contents of the text
variable "G1optional text variable". By calling the text variables contained in the
MMC command (9th to 23rd parameters), messages or names can be "composed"
in this way.
Text variable
F1 = ...Example3: MMC command with synchronous acknowledgment mode…
OK
Sequence
The user variable Test_1 is displayed until the "OK" softkey is pressed.
The user variable has also been overwritten with the value 5 here.
Without STOPRE, this assignment would be carried out before the keyboard input
(after it with STOPRE).
(R///Var.Name/R/TEST_3/6000,2800,8000/ 200,3000,7500)
The two parameters each consist of three numerical values; these specify the
position and length of the field. The values are specified in Twips, with 15 Twips
roughly corresponding to one pixel.
The field height is defined as being 250 Twips.
Meaning of values:
(./6000,2800,8000/....)
OK
To ensure that the cursor control works seamlessly, the configured fields must
overlap one another (see below):
1.000000
1.000000
1.000000
1.000000
OK
A comment text for the image can also be preassigned via the Com file. You can
position this comment text by specifying position parameters.
Note
You can only move the image itself by repositioning it in the graphics program.
Parts program
N10 MMC("CYC.,PICTURE_ON,T_SK.COM,SCREEN8,GUD4.DEF,GRA.AWB,,
M1","S")
N20 MMC("CYCLES,PICTURE_OFF","N")
N30 M30
Text variable
M1 = ......Example5: Insert image…..
Images are created, e.g. with the drawing tool "Paintbrush".
Image size: 300X500 pixels, you can only change the image size in Paintbrush.
OK
Parts program
MMC("CYCLES,PICTURE_ON,T_SK.COM,SCREEN7,GUD4.DEF,,TEST_1,J1","S")
(*.COM)
//C7(Screen7)
(R///Test_1/R/Test_1)
(I///); (Interpreted as space line))
(R///Actual value from axis 1/R/$actual value)
(R//1/R parameter 12/W/$R[12])
Text variable
J1 = ...Example7: OPI variables
[OPIVar]
$Actual value=/Channel/machineaxis/actToolbasePos[u1,1]
$R[12]=/Channel/Parameter/r[u1,12]
R parameter12 1.000000
OK
Sequence
A space line is created under the variable TEST_1.
The actual axis value is read-only.
Parts program
N10 QUIT_1 = "START"
N20 MMC("CYCLES, PICTURE_ON,T_SK.COM,SCREEN3,GUD4.DEF,,
QUIT_1,K1","A")
N30 LABEL0:
N40 STOPRE
N50 IF MATCH (QUIT_1,"SK1") >= 0 GOTOF LABEL1
N60 IF MATCH (QUIT_1,"SK2") >= 0 GOTOF LABEL2
N70 GOTOB LABEL0
N80 LABEL2:
N90 MMC("CYCLES, PICTURE_ON,T_SK.COM,SCREEN1,GUD4.DEF,,,
N1","N")
N100 G4F10
N110 LABEL1:
N120 MMC("CYCLES, PICTURE_OFF","N")
N130 M30
(*.COM)
//C3(Screen3)
(S/// USER VAR QUIT_1/W/QUIT_1//)
[TEXT VARIABLES]
K1 = ..Example8: MMC command with asynchronous acknowledgment mode
N1 = ..Example8: Screen2
Text variable
[SCREEN3]
SK1 = END
SK2 = Screen2
Softkey 8
Softkey 9
Example 8: MMC command with asynchronous acknowledgment mode
Softkey 10
USER VAR TEST_1 START
Softkey 11
Softkey 12
Softkey 13
Softkey 14
OK Softkey 15
END Screen2
Sequence
The screen called via the asynchronous MMC command continues to be displayed
until one of the two configured softkeys is actuated:
The "END" softkey closes the user dialog immediately.
The "Screen2" softkey then displays another screen for a period of 10 s.
Program
• The acknowledgment variable is defined as a string.
Length of the string: >= 20
(Values < 20 are evaluated internally only,
SK0 ... SK15 are entered at position 17...20 on actuation of the softkey).
• The string is assigned a value in the parts program and any old softkey
information is deleted.
Example 8: Screen2
OK
%_N_MMC_EXAMPLE2_MPF
N10 MMC("CYCLES,PICTURE_ON,T_SK.COM,SCREEN6,GUD4.DEF,,10,
T1,G1","N")
N15 G4 F15
N20 MMC("CYCLES,PICTURE_OFF","N")
M30
%_N_MMC_EXAMPLE3_MPF
N15 MMC("CYCLES,PICTURE_ON,T_SK.COM,SCREEN1,GUD4.DEF,,,F1",
"S")
N20 TEST_1 = 5
N30 MMC("CYCLES,PICTURE_OFF","N")
M30
%_N_MMC_EXAMPLE4_MPF
N15 MMC("CYC.,PICTURE_ON,T_SK.COM,SCREEN2,GUD4.DEF,,,C1","S")
N20 TEST_3 = 5
N30 MMC("CYCLES,PICTURE_OFF","N")
M30
%_N_MMC_EXAMPLE5_MPF
N15 MMC("CYCL.,PICTURE_ON,T_SK.COM,SCREEN8,GUD4.DEF,GRA.BMP,,
M1","S")
N30 MMC("CYCLES,PICTURE_OFF","N")
M30
%_N_MMC_EXAMPLE6_MPF
N10 MMC("CYC.,PICTURE_ON,T_SK.COM,SCREEN4,GUD4.DEF,,,H1","S")
N20 TEST_2 = 12
N30 MMC("CYC.,PICTURE_ON,T_SK.COM,SCREEN5,GUD4.DEF,,,I1","S")
N35 MMC("CYCLES,PICTURE_OFF","N")
N40 M30
%_N_MMC_EXAMPLE7_MPF
N15 MMC("CYC.,PICTURE_ON,T_SK.COM,SCREEN7,GUD4.DEF,,,J1","S")
N20 TEST_1 = 5
N30 MMC("CYCLES,PICTURE_OFF","N")
M30
%_N_MMC_EXAMPLE8_MPF
N10 QUIT_1 = "START"
N20 MMC("CYCLES, PICTURE_ON,T_SK.COM,SCREEN3,GUD4.DEF,,
QUIT_1,K1","A")
N30 LABEL0:
N40 STOPRE
N50 IF MATCH (QUIT_1,"SK1") >= 0 GOTOF LABEL1
N60 IF MATCH (QUIT_1,"SK2") >= 0 GOTOF LABEL2
N70 GOTOB LABEL0
N80 LABEL2:
N90 MMC("CYCLES,
PICTURE_ON,T_SK.COM,SCREEN1,GUD4.DEF,,,N1","N")
N100 G4 F10
N110 LABEL1:
N120 MMC("CYCLES, PICTURE_OFF","N")
N130 M30
(I///)
(R///Actual value from axis1/R/$actual value)
(R//1/R parameter12/W/$R[12])
//C8(SCREEN8)
(I///Insert image no.///4000,3000,7500)
(I///Created with Paintbrush///4000,3250,7500)
I Index
I
I.1 Subject index
Change TCP/IP settings ................IM4/3-22
Change User Name .......................IM4/3-22
6 Changing language......................IM4/6-175
Channel change
6 Change TCP/IP settings........... IM4/7-182 Simulation .................................IM4/5-105
Channel menu
A NETNAMES.INI ........................IM4/5-160
Connect to Network Drives ............IM4/3-22
ac................................................... IM4/5-69 Cross-channel status display with
Accelerated WIN XP startup.......... IM4/4-42 symbols .......................................IM4/5-76
Access level................................... IM4/5-69
Access rights ................................. IM4/4-46 D
Action log
Outputting the log file ............... IM4/8-246 Data management limits ..............IM4/7-240
Activating data transfer via PLC Data matching in simulation.........IM4/5-110
Job processing ........................... IM4/5-60 Defining an emergency backup
Actual value display: Settable zero image.........................................IM4/7-229
system......................................... IM4/5-64 Disconnect from all Network
ANSI tables/fonts......................... IM4/6-174 Drives ..........................................IM4/3-22
Displaying axis names/axis values
B Simulation .................................IM4/5-103
Displaying simulation data ...........IM4/5-106
Backing up/restoring Domain Name Server ....................IM4/3-22
partitions .............IM4/7-218, 7-220, 7-223 DPSIM.INI ....................................IM4/5-116
Basic PCU software ...................... IM4/3-17
Boot manager ................................ IM4/3-18 E
Booting
Simulation................................. IM4/5-102 EMC/ESD measures........................ IM4/1-9
Error messages to the PLC ...........IM4/5-61
C EXIT button
REGIE.INI .................................IM4/5-161
Change DNS Extension ................ IM4/3-22
Change Domain Name.................. IM4/3-22 F
Change Gateway........................... IM4/3-22
Change IP Address ....................... IM4/3-22 Files
Change Machine Name ................ IM4/3-22 Simulation .................................IM4/5-101
Change Network Settings menu First boot ......................................IM4/7-184
options ...................................... IM4/7-181 Flying edge ..................................IM4/5-107
Change Network Settings.............. IM4/3-22
Change Subnetmask..................... IM4/3-22
H P
Screen saver................................IM4/5-159
M se ...................................................IM4/5-69
Search configurations
M:N assignments Multi-channel block search .........IM4/5-66
NETNAMES.INI........................ IM4/5-160 Search strategy
Make server name visible............ IM4/5-159 Simulation .................................IM4/5-104
Manage Network Drives ................ IM4/3-22 Service menu .................................IM4/3-18
Match cycles Setting the action log ...................IM4/8-245
Simulation................................. IM4/5-111 Settings for saved protocol ..........IM4/5-136
Match MD Setup............................................IM4/6-174
Simulation................................. IM4/5-110 Show connected Network
Match setup data Drives ..........................................IM4/3-22
Simulation................................. IM4/5-111 Simulation data display................IM4/5-106
Match tools SINUMERIK desktop .....................IM4/3-18
Simulation................................. IM4/5-110 Softkey properties ..........................IM4/5-68
Mechanical and electrical Software components
installation .................................. IM4/2-13 Basic PCU software....................IM4/3-17
Mirroring tools st ....................................................IM4/5-69
Simulation................................. IM4/5-111 STAT ..............................................IM4/5-64
MMC .......................................... IM4/10-259 Status display with symbols...........IM4/5-76
Moving joint STAT ......................... IM4/5-64 Status.............................................IM4/5-69
Supported languages...................IM4/6-173
N Switching on...................................IM4/4-40
SYSLOCK
NC cycles Boot virus check .........................IM4/5-75
Simulation................................. IM4/5-102
NC language commands.............. IM4/5-72 T
NCU-specific alarm texts with multiple
operator panels/NCUs .............. IM4/6-175 TCP/IP settings ............................IM4/7-183
Toggle logon to domain ................IM4/3-22
Toggle Protocol..............................IM4/3-22
Notes
SINUMERIK 840D/840Di/810D
1 Introduction ..............................................................................................................................TX1/1-3
1.5 Terms.....................................................................................................................................TX1/1-8
2 Editing Files............................................................................................................................TX1/2-13
3.6 Variable changes to the keyboard layout (with quick switchover) ........................................TX1/3-29
3.7 Variable keyboard layout with the correct language assignment .........................................TX1/3-34
3.7.1 Supplementary conditions for the variable keyboard layout.............................................TX1/3-34
3.7.2 Concept of the keyboard language property....................................................................TX1/3-35
3.7.3 Managing the language property in word processing programs ......................................TX1/3-36
3.7.4 Language property for text files in WordPad....................................................................TX1/3-36
3.7.5 Text with several language properties .............................................................................TX1/3-40
3.7.6 Restrictions in Windows 95..............................................................................................TX1/3-41
3.8 Special considerations when working with Greek and Cyrillic texts .....................................TX1/3-42
5 References..............................................................................................................................TX1/5-51
I Index .........................................................................................................................................TX1/I-53
1 Introduction
1
1.1 General .......................................................................................TX1/1-4
1.5 Terms..........................................................................................TX1/1-8
1.1 General
Since the nineties, Microsoft has been working incredibly hard to meet the
requirements of global information processing and software development.
As well as supporting as many languages as possible, they have also been striving
to develop a single operating system to support all languages, unlike the language-
specific operating system versions used in the past.
As part of this project, many system components and applications have gradually
been converted to the cross-language Unicode platform.
Although these conversions will have in many cases gone unnoticed by users, the
procedure adopted to the subject addressed in these instructions will vary
fundamentally depending on the operating system being used.
The procedure recommended for Windows 2000/XP is much simpler than that for
Windows 95/NT4. We therefore recommend that you upgrade to the new system.
The instructions for the older systems have been included simply for reasons of
compatibility and will no longer be subject to editorial revisions.
1.2 Preconditions
This document describes the procedure for creating a text with the following
specifications:
• The text is to be created on a Microsoft Windows operating system
(Windows 95 or Windows NT 4).
• This description uses German as the default language for all examples provided
herein. However, the procedure described will work just as well with all localized
variants of Microsoft Windows.
• The text is to be created as what is known as a text file, i.e. without formatting
information such as font, font size, underline, etc. Therefore, in addition to text
characters, the text will only contain ASCII control characters such as tab, CR
and LF.
• The language of the text requires a different Windows code page to that of the
default language, i.e. the target language does not belong to the same
language family as the default language.
• The text file is to be coded using this code page, not as a Unicode file.
• The target language does not belong to the pictorial languages using a double-
byte character set (Japanese, Korean, Chinese) or to the languages using what
is known as complex scripting (Arabic, Hebrew, Urdu, etc.). For the pictorial
languages, refer to the information provided in Section 4.1 "Problems and
remedies".
• The means used to create the text are to be as simple as possible, i.e. if at all
possible, no additional software should need to be installed.
Remedy:
• Switch the keyboard or
• Use the ALT+digit combination to enter these characters, or
• Use the Windows "character map"
In this case, no further problems should occur. Section 2.4 and Chapter 3 need not
be observed.
The procedure described here requires that you did not exclude certain
components from your Windows installation. You should have installed the
following components:
• WordPad (required)
Older versions of Windows 95 only support the Greek, Cyrillic and Central
European (or "Eastern European") language families.
Windows 98
Windows 98 Version 5.00 includes WordPad. With this version, however, it is not
possible to create text files, which do not belong to the same language family as
the system language.
Recommended
Use Windows 95 or Windows NT 4.
1.5 Terms
Default user
If you have activated user management in Windows 95, there is a special user
without name and password - the default user. Copy the settings of this user to
create a new user.
2. If you are using a keyboard layout other than that of the default user, then
(Windows 95!) the "Start Exit Exit all applications and log in using another
name" process will remove the current keyboard layout from the memory
without loading the keyboard layout for the default user. The log-in screen form
will then no longer function.
To avoid this, proceed as follows:
- Before you log out, either reset the keyboard settings to the original
keyboard layout
- Or restart Windows.
Diacritical characters
(diacritical = distinguishing)
In most cases, a relatively small supplementary character is attached to a letter to
give the letter a specific stress, a specific pronunciation or even a new meaning.
• For combined input (see Section 3.4) if there is no dedicated key for the
required combined character
In all other cases, the combined letter is always considered as a compound unit.
In some cases, however, the combined letter is incorrectly also treated as the
diacritical character.
Language property
A property (attribute), which is managed in Microsoft text processing programs as
other text properties per character. In such cases, the program will remember the
language to which the character, the character sequence, the word or the whole
sentence belongs.
Word and WordPad support this property, NotePad does not. In both programs,
this property is not directly visible.
In WordPad, the language property is independent of the font language family. For
example, a Cyrillic character can possess the language property "German".
Modifications are only possible in the following cases:
• When changing the "Font language family" text property, WordPad will
automatically change to the appropriate keyboard setting if a keyboard
setting with the appropriate language property exists. However, this change
is undone with the next time a key is pressed.
Microsoft sometimes uses the designation "locale" for the language property,
whereby this term also covers properties such as currency, date format, decimal
separators, etc.
Language family
A language family is a group of languages, which uses the same code page. This
requires the use of the same basic alphabet (e.g. Latin or Cyrillic), but it does not
mean that the alphabet of all languages of this group is the same.
Instead of font files stored separately for each code page, Windows NT4 and
Windows 95 (with "language pack" installed) use what are known as "Big Fonts",
i.e. fonts that contain the character set for several code pages, saving memory
capacity for common characters.
The appropriate subset for this total character set is not selected via code page
numbers but via the language family. However, there is a 1:1 assignment between
Windows code page and language family.
Section 1.2 contains a list of the language families in Table 1-1.
Default language
The term "default language" is used in this guide for the language of the operating
system, i.e. German in a German version of Windows and English in an English
version of Windows.
Unicode
A 16-bit character set with which no more code pages are required. Unicode
programs cannot interpret characters on a code-page-specific basis, which means
that their appearance does not change according to the font language family
selected.
2 Editing Files
2
2.1 Starting WordPad .....................................................................TX1/2-14
1. Use the mouse to select the whole empty document by clicking on it, e.g. to the
left of the cursor.
Figure 2-1
Click
Figure 2-2
2. From the "Open" dialog box, choose the "Text Documents (*.txt)" setting under
"Files of type". Search for the file you want to open and then click on "Open". If
your file has a different extension, then select "All Documents (*.*)" from the
"Files of type" menu.
The file opens. WordPad can manage multi-language texts. Since the text file
does not contain language information, the text is treated as belonging to the
language set as the default setting on the keyboard. However, this may be
ignored initially if the keyboard does not need to be switched (see Chapter 3
"Changing the keyboard layout").
No text attributes are stored in the text file, meaning that the text will under
certain circumstances be displayed using the wrong code page and
language-specific special characters will not appear correctly. Therefore, first
you must set the font and the language family.
3. To do so, choose the entry "Select All" from the "Edit" menu or press Ctrl-A to
select the whole file.
! Important
These settings have to be made again every time the file is opened.
You can choose the font in two different ways: Figure 2-3
Figure 2-3
Font dialog box
2. Use the font dialog box to select the font type and language family separately.
Choose the "Font" command from the "Format" menu to open the font dialog
box.
From the "Font" menu, choose the name of the font, and from "Script", the
language family of the font.
Figure 2-4
These settings will change the appearance, but not the coding, of the existing text.
Windows 98
Under Windows 98, the existing text remains unchanged, i.e. the formatting with
the desired font language family remains without effect. In WordPad Version 5.0,
the characters are saved internally in Unicode so that changing the language
family would be the same as changing the code page.
Note
It is not possible to use Windows 98 for this purpose.
If a language family other than that selected is displayed, you may have an
unsuitable installation:
• The language pack may not be installed. Check whether the Windows
"language pack" component is installed, as described in Section 1.3.
• Your Windows system may include a variant of WordPad, which does not
permit the language family settings you have chosen for the existing text
(WordPad Version 5.00 and higher, e.g. Windows 98). In this case, you
should use an older Windows version, e.g. Windows 95 or Windows NT 4.
Language family Characters that only occur here Characters that also occur in
other language families
Baltic languages ėĖģĢįĮķĶļĻņŅūŪųŲ ĄĄęĘčČäÄåÅöÖõÕšŠ üÜžŽ
Central European ąĄćĆęĘłŁśŚżŻ (Polish) óÓ
čČěĚřŘůŮ (Czech) áÁéÉíÍýÝžŽ
őŐűŰ (Hungarian) áÁéÉíÍóÓöÖúÚüÜ
Turkish ĞĞıİşŞ çÇöÖüÜ
3. Type a special character to test whether your settings are correct. If you have
opened an existing file, no text must be selected (for example press Ctrl-End to
go to the end of the file).
Use the input method ALT+numerical keypad to type a special character,
which is displayed differently in each language.
Example:
Table 2-2 Example: Special characters
1. Choose the "Save As ..." command from the "File" menu in WordPad.
Figure 2-5
4. The following message will appear the first time you click on "Save":
Figure 2-6
Your file will now be saved as a text file. When the document is next opened,
font type, language family and language property will be reinitialized, as these
properties are not saved.
After you have finished your work, save the file as a text document to obtain the
final file format.
3 Input of Text
3
3.1 Special characters belonging to various language families......TX1/3-22
acute ˝, grave accent `, háčekˇ, macron ¯, ogonek (nasal hook, crooked hook) ˛,
squiggle ˚, slash /, hyphen – or tilde ˜.
Other characters of the alphabet are special letters (Þþ, Ðð, ß ) or ligatures
(Ææ, Œœ, IJij ). Language-specific abbreviations and punctuation marks are
also used, e.g. for the endings of the ordinal numbers in Spanish (ª and º) as well
as upturned exclamation and interrogation marks (¡ and ¿).
The input methods described below apply only for Latin-based language families
without limitations.
Example (Turkish):
ALT+0222 results in Ş (S with cedilla).
To produce this character, you will only need the character map of the appropriate
code page (see Section 1.2).
You will find overview tables for the code pages e.g. at Microsoft at:
http://msdn.microsoft.com/library/default.asp?URL=/library/books/dev
intl/s2570.htm
Under "Font", choose the same font as you have selected for the text file.
Depending on the version of your Windows 95 operating system, you will see the
language families listed as font type variants:
Figure 3-1
Language codes
The following codes are used for the language families:
Baltic Baltic
Greek Greek
Cyrillic Cyr
Central European CE
Turkish Tur
Western None
Precondition
In more recent versions of Windows 95 (4.00.950b, known as OSR2, OEM Service
Release 2), all language families mentioned in Section 1.2 will appear here.
If you are using the original version of Windows 95 (with or without Service
Pack 1), you may not be offered these language versions. In this case, you cannot
use this method.
Entering characters
1. Choose the characters you wish to enter.
2. After each character, click on "Select".
3. Once you have selected all characters, click on "Copy".
The characters will be copied to the clipboard.
4. Go back to WordPad and press Ctrl-V.
The characters are pasted from the Clipboard into the text
Note
The characters are always inserted with font size 12.
The font you selected in the "Character Map" program is assigned to the
characters as a font setting when they are inserted into WordPad. If this font is
not the same as the one you selected previously in WordPad, this will produce a
font mix or even a font family mix in WordPad.
The keys with the diacritical characters, which are thus dealt with in a special way,
are marked in the descriptions of the keyboard layouts with a special color.
Keyboard layout
The table below shows some keyboard layouts for the diacritical characters
supported:
Table 3-1
Grave accent
Double-acute
Circumflex
Squiggle
Ogonek
Cedilla
Háček
Breve
Colon
Acute
Point
Tilde
Keyboard
assignments
´ ` ˆ ˇ ˘ ˛ ˙ ¨ ¸ ˝ ˚ ˜
German X X X
French X X X X
Polish X X X X X X X X X X
Grave accent
Double-acute
Circumflex
Squiggle
Ogonek
Cedilla
Háček
Breve
Colon
Acute
Point
Tilde
Spanish X X X X X
Czech X X X X X X X X X X
Hungarian X X X X X X X X X
US International X X X X X
If you press the space bar after the diacritical character, you will see the character
itself.
Note
It may be advisable to switch the keyboard layout to "US International", which is
essentially the same as the American keyboard but also contains 5 diacritical
characters and provides many special characters.
Your default language (the language of your operating system) with your
default keyboard layout. This entry is selected and specified below as the
default entry.
At least one entry exists (the default entry).
Figure 3-2
5. Make sure that the default entry is selected and click on "Properties". The
"Language Properties" dialog box (NT 4: "Input Locale Properties") will
appear.
6. Select a suitable keyboard layout for the target language and click on OK.
Figure 3-3
7. Click on "OK" to quit the dialog. Some keyboard drivers may now be loaded
from the CD, meaning that you will have to restart Windows.
Figure 3-4
Note
Important for Windows 95:
Do not try to set up the target language as such using "Add".
Some additional conditions still need to be met
(see Section 3.6).
Result
You will create text with a keyboard layout suitable for the target language. The text
display has already been adapted by setting the font with the language family as
described in detail above.
Your default language, e.g. German, will be used unchanged as a text language
property managed internally by WordPad (i.e. WordPad will assume that your texts
will be created in German). If you were to transfer text to Word using the copy and
paste function, the German spell checker would be used.
If you were to set the target language as the keyboard language, although the
language property would be correct, you would still have to take some additional
issues into account (see Section 3.7).
Note
• All menus will also use the switched keyboard layout. You will no longer find
your key combinations with Alt and the appropriate letter key (e.g. Alt-D for
the "File" menu) or Ctrl + letter key (e.g. Ctrl-V for "Paste") and could even
inadvertently initiate a wrong command. You should therefore use the mouse
or, in menus, the arrow keys.
• In order to work with the keyboard layout to which you are accustomed, i.e. to
switch back to your original keyboard layout, you must repeat the procedure
described, this time selecting your original keyboard layout.
• Before you shut down your PC, you must switch back to your original
keyboard layout. If your screen saver is password-protected, you may
experience difficulties entering the password.
• If you use a user ID under Windows 95, the function "Exit all applications and
log in using another" may only work if you first have switched back to your
original keyboard layout.
• For the Windows log-in, the keyboard layout set for the default user is used.
To log in as the default user, press the ESC key when the log-in dialog box
appears.
Example
In Hungarian, for example, you could enter these characters as follows:
őŐűŰ numerical
öÖüÜ directly
áÁéÉíÍóÓúÚ combined input
Figure 3-5
5. Click on "Add". The "Add Input Locale" dialog box will appear.
Figure 3-6
6. Select your default language, e.g. German. Do not select the target language
for your text!
Note
Windows NT 4 will again offer the languages already set up here although
Windows 95 will not.
7. Disable the "Use default properties for this input locale" field.
8. Click on "OK". The "Input Locale Properties" dialog box will appear.
9. Select a suitable keyboard layout for the target language and click on "OK".
The layout already selected will not appear again here.
Figure 3-7
10. Use "Switch locales" to select how you wish to switch the keyboard layout. If
you select "None", you can only switch using the mouse.
11. Check "Enable indicator on taskbar". This enables the option to switch over
quickly using the mouse.
12. Click on "OK" to quit the dialog. Some keyboard drivers may now be loaded
from the CD, meaning that you will have to restart Windows.
Figure 3-8
Result
You will create text with a keyboard layout suitable for the target language (for the
input of your texts in a foreign language) or with your previous default keyboard
layout (for the remaining operation). You can switch between the two layouts as
required.
The text display has already been adapted by setting the font with the language
family as described in detail above.
Your default language, e.g. German, will be used unchanged as a text language
property managed internally by WordPad (i.e. WordPad will continue to assume
that your texts will be created in German). If you were to transfer text to Word using
the copy and paste function, the German spell checker would be used.
If you were to set the target language as the keyboard language, although the
language property would be correct, you would still have to take some additional
issues into account (see Section 3.7).
Now, a small blue field with a two-letter language abbreviation should appear in the
taskbar indicating the language you have set:
If you position the mouse pointer on this field (without clicking on it), the complete
setting is displayed (language and keyboard layout).
Figure 3-9
If you click with the left mouse button on this field, the languages you have set will
be displayed in a small menu.
Figure 3-10
If you click with the right mouse button on this field, an abridged version of the
"Keyboard Properties" dialog box can be accessed via the "Properties" menu
option.
Figure 3-11
• A new window is always started with the default setting. After starting
WordPad, you may have to reselect the keyboard layout.
• Open the window in which you want to enter texts before you select the
keyboard settings for this window.
Additional information
• If you unhide a dialog in WordPad, e.g. Format Font, the keyboard may
automatically revert to the default layout.
• If you do not want to switch back to the second keyboard layout so often, you
can also declare the new, second combination with the special keyboard
layout as the default in the "Keyboard Properties" dialog box:
To do this, select the second entry and click on "Set as default".
Please note that the display text "Standard input locale: German
(Germany)" does not change because only the language property, and
not the keyboard layout, is displayed. Both settings have the same
language property.
Please note that all new windows, the Start menu and the desktop will
now also use the new keyboard layout. See also the warning notes with
regard to screen savers in the previous section.
Menu operation
All menus will also use the switched keyboard layout. You may no longer find
certain key combinations with ALT and the letter key or Ctrl with a letter key or may
even inadvertently initiate a wrong command. You should therefore use the mouse
or, in menus, the arrow keys.
Switchover
Switching method via keyboard:
"Left Alt + SHIFT" and
"Ctrl + SHIFT"
The correct language assignment is described here only for the sake of
completeness and for improved clarity; in most cases, however, the simpler variant
(see Section 3.5/3.6) will suffice.
This section describes the steps to be taken to ensure that the language property
of the keyboard setting (not to be confused with the keyboard layout itself) matches
the target language.
• With some keyboard layouts, e.g. Czech, the digits cannot be accessed on the
standard keyboard level.
• As a German native speaker, you wish to prepare part of the text and have
only a second part created by your translator.
Figure 3-12
In particular, Microsoft Word and Outlook use this property to carry out the spell
check for the appropriate language. WordPad also supports this language property,
although simple text editors such as NotePad do not.
If, in Word, Outlook or WordPad, for example, you position the cursor in the center
of a bold word, all characters entered subsequently will also be inserted in bold.
The language property of the text is treated in the same way: If several different
languages are set up, Word, Outlook and even WordPad will switch the keyboard
automatically when the cursor moves, so that the keyboard language matches the
language property of the cursor position.
However, this property can generate significant confusion if parts of the text are
assigned an incorrect language property by mistake. You must therefore exercise
caution when using the language switchover feature.
2. At the end of each file, there is a line feed (or end of paragraph), which can be
selected, but not deleted. If you use WordPad to create a new file (see
Section 2.2), this file will also contain this undeletable line feed. To view this
line feed, select the entire empty document (see Section 2.2).
This line feed is also assigned the language of the default keyboard setting as
the language property. This will come into effect if you position the cursor at
the end of the document.
! Important
Language properties assigned in this way cannot be changed in WordPad.
Example
Carry out the following example to understand the effects:
Table 3-2
3. Disable the "Auto hide" property in the taskbar property window and enable
the "Always on top" property. The taskbar will thus always remain visible and
you can check the language setting. (Click with the right mouse button on a
free space in the taskbar and then on "Properties" to adjust the taskbar
properties.)
5. Format the empty file with "Courier New (Central European)", as described in
Chapter 2, by selecting the undeletable line feed, and then the font type. Now
watch the taskbar. You will see that the keyboard has automatically been
switched to Czech.
6. Once you cancel the selection again or enter a character, the keyboard will
revert to German. Formatting with the font and the font language family did
not change the language property of the undeletable line feed. This line feed
has "inherited" the language property German from the default setting of the
keyboard.
On a German keyboard, use the numerical keys 2345 for example to enter
the Czech haček characters ěščř. Then press ENTER. The text will now
appear as shown below.
Figure 3-14
9. Press the ArrowUp key ↑ and enter a few more Czech characters in the first
line. Press the ArrowDown key ↓ and watch the taskbar. The keyboard has
switched to German again. Explanation: Until now, the second line contained
only the undeletable last line feed, which still possesses the language
property German. Even the font has switched to "Courier New (Western)".
10. Position the cursor at the end of the first line. The keyboard will revert, e.g. to
Czech, because the first line has been entered with the language property
Czech. Press ENTER again and type a few Czech characters. You can now
enter Czech text without undue problems.
11. As soon as you position the cursor at the end of the file again, the setting will
revert to German!
Example: You want to type the word "Haček". Only at the third letter, the "č",
do you realize that the keyboard has been switched to German , because a
"4" appears. Delete the "4", switch the keyboard back to Czech and continue
typing.
A small section in the center of the text, i.e. the first two letters "Ha" of this
word, now have the language property German. Whenever you position the
cursor there, the keyboard will revert to German.
12. Save this file as a text file (see Section 2.6) and quit WordPad.
Then restart WordPad and open this file. The Czech characters will now
appear incorrectly.
13. Format the whole text with "Courier New (Central European)", as described in
Section 2.3. The Czech characters will appear correctly again. The keyboard
is switched to Czech.
14. Position the cursor at any point in the text (the keyboard will switch to
German), switch the keyboard explicitly to Czech and enter the Czech text.
15. However, as soon as you position the cursor at another point in the previous
text (with the mouse or arrow keys), the keyboard will revert to German.
Result: Although the Czech characters are displayed correctly, the old text
possesses the language property German.
16. Worse still, whenever the keyboard switches to German due to the position of
the cursor, the font "Courier New (Western)" will appear in the format bar
even though the characters to the left and right of the cursor have been
formatted with "Courier New (Central European)". Only when the cursor
moves again (e.g. RightArrow key ) will the correct font reappear.
Result
A mixture of smaller sections with different language properties and font type family
properties may be produced.
Remedy in NT4
In Windows 95 only possible subject to restrictions (see Subsection 3.7.6)
1. Set up two keyboard settings - one with German and one with your target
language:
Table 3-3
3. Select the line that contains your target language (e.g. Czech) and click on
"Set as default". Then click "OK" to quit the dialog box.
4. Disable the "Auto hide" property in the taskbar property window and enable
the "Always on top" property. The taskbar will thus always remain visible and
you can check the language setting. (Click with the right mouse button on a
free space in the taskbar and then on "Properties" to adjust the taskbar
properties.)
If you start WordPad, the undeletable line feed at the end of the file will be
assigned the language property Czech (or of your target language).
If you open an existing text file with WordPad, the existing text will also be
assigned the language property of your target language.
If you do not switch the keyboard explicitly to German, the keyboard setting will
remain unchanged in your foreign language.
• Select the whole line, copy it to the clipboard by using Ctrl-C and paste it
several times by pressing Ctrl-V. You will obtain two columns; the left one is
German, and the right one Russian, and this is not only the font language
family, but also the language property so that the keyboard is switched
automatically when the two text columns are edited:
Table 3-4
[Text 103][Mode 28] "йцукенгшщзхъфывапролджэячсмить"
[Text 103][Mode 28] "йцукенгшщзхъфывапролджэячсмить"
[Text 103][Mode 28] "йцукенгшщзхъфывапролджэячсмить"
[Text 103][Mode 28] "йцукенгшщзхъфывапролджэячсмить"
[Text 103][Mode 28] "йцукенгшщзхъфывапролджэячсмить"
[Text 103][Mode 28] "йцукенгшщзхъфывапролджэячсмить"
German Russian
Only after complete editing, select "Save As ..." and then "Text file" as the file
type.
Note
Make sure that you do not inadvertently use characters, which are not contained
in the code page of your target language, e.g. the superscript digits ¹ ² ³ and the
fractions ¼ ½ ¾ are not contained in code pages 1250 (Central European) and
1251 (Cyrillic)!
If the whole text is formatted with the same font language family, you are still in
compliance with the code page.
Figure 3-15
The acceptance as the default language may not take effect. Restart Windows.
The new default setting will then be effective.
If you have the original version of Windows 95 or the original version with Service
Pack 1, then the definition of the target language as the default keyboard setting
may only take effect on the undeletable line feed at the end of the file and not on
the language property of existing text when opening a text file.
This restriction does not apply to version Windows 95 OSR2 ("OEM Service
Release 2").
In terms of language, the Greek and Cyrillic alphabets are considered as separate
and independent alphabets, and not as an extension of the Latin alphabet.
This means that Greek and Cyrillic letters, which in their appearance are identical
to Latin letters, are not the same characters and may therefore also not be coded
identically.
This is also evidenced to some extent by the fact that despite uppercase letters
looking identical, the corresponding lowercase letters look different.
Example
The effects of incorrect coding can be fatal:
Suppose you write the Russian word for "NO" ("HET") using Latin letters instead of
"НЕТ" using Cyrillic letters. Initially, you will not notice a difference. However, if you
use the "Ignore uppercase/lowercase letters" search option when searching for
"нет" in lowercase letters, you will not find the incorrectly coded spelling.
! Important
Switch the keyboard to Latin only if absolutely necessary! When doing so, do not
switch over for individual letters, only for complete words and sentences.
Under no circumstances may words with different coding be used!
Note
Find out whether and to what extent certain German, English or international
abbreviations (e.g. DIN/ISO) may or must be written using Latin fonts or whether
a conversion (ДИН/ИСО) should be preferred according to the conventions of the
country in question.
The key assignment for combinations such as Ctrl-C, Ctrl-V, Ctrl-Z, Alt-A etc.
normally depends on the U.S. American keyboard layout.
Remedy:
You have set up at least two keyboard settings with different language properties.
In Windows 95, set up only one keyboard setting (see Section 3.5) or, in Windows
NT 4, use the same language property for all keyboard settings.
Then save your file and restart WordPad.
Version of Windows 95
Problem:
Identifying the version of Windows 95
Remedy:
Open Settings Control Panel System. You will find the system version on the
"General" page. The following version numbers are displayed here:
4.00.950 Windows 95, original version
4.00.950a Windows 95, original version, with "Service Pack 1 for Windows 95"
4.00.950b Windows 95, OEM Service Release 2
The latter version is only available as a full version, not as an update.
Remedy:
When creating texts in Word, observe the following:
• If you already have an existing text file and you want to use Word 6.0, open the
file in Word 6.0 and format the text as described in Section 2.3.
• If you already have an existing text file and you want to use Word 97, then
open and format the file in WordPad, as described in Section 2.3, then save
the file as a "Word for Windows 6.0" file. Open this file in Word 97.
• Enter your text in Word, as described. The information about different input
methods in Chapter 3 also applies here.
• Save your text as a Word document (*.doc). When doing so, the text
properties, such as font type and language property, will not be lost.
• When reopening the file, you need not set the font again.
• Disable the automatic conversion of straight quotes (") to smart quotes (”)
along with any other automatic formatting settings, to avoid incorrect special
characters.
• If required, you can change the language property of parts of the text using
"Tools" "Change Language".
• Not all Word versions switch the keyboard based on the language property. In
such cases, you can ignore the language property.
• In Word 6.0, you will be offered the font family with language family, as
described in Section 3.2.
• In Word 97, you cannot set the font language family! A character displayed
incorrectly is coded incorrectly. Enter the character again or check the steps
you have completed so far.
Finally, convert your file to a text file, as described in below. If you will need to edit
the text later again in Word, create a copy of your Word document.
Remedy:
You have created a Word document in your target language and now want to
convert it into a text file.
If you are using Word 6.0, you can use either Word or WordPad to open the Word
file and save it as a text file.
• If you are using Word 97 or a later version, first save the file in Word as a
"Word 6.0/95" document then carry out the conversion with WordPad.
• Alternatively, you can also use "Copy" and "Paste" to accept the text into
WordPad. Word97 files internally use Unicode.
You should always finish by checking the result (open and format the text file with
WordPad as described in Section 2.3). When doing so, take into account the
special characters and compare with the Word document. If individual special
characters do not appear correctly, you may have used characters that do not
appear in the code page of the target language.
Remedy:
This is obviously an error in the documentation or in the keyboard driver. In the
Polish or Czech keyboard layout, this key combination will correctly produce the
diacritical character "Dot above letter", e.g. for ė and ż.
WordPad 5.0
Problem:
WordPad 5.0 does not work.
Remedy:
Like Word 97, WordPad 5.0 uses Unicode. Here you cannot use the font language
property to set the code page with which the characters are to be displayed, since
the code pages are no longer used.
A code page character can be interpreted with different code pages and thus also
be displayed differently. A Unicode character has exactly one defined
interpretation, which cannot be changed.
Remedy:
Windows 98 and higher features WordPad 5.0, which cannot be used as
described. If necessary, check the version of WordPad by searching for the
Wordpad.exe in the Explorer and unhiding the "Properties" dialog box.
WordPad will be located in one of the following directories:
C:\Program Files\Accessories\Wordpad.exe or
C:\Program Files\Windows NT\Accessories\Wordpad.exe
Remedy:
Check whether the language pack is installed, as described in Chapter 1.
Remedy:
Your version of Windows 95 is probably too old. Use Windows 95 OSR2 (OEM
Service Release 2).
Remedy:
You have selected a section of text to which different language family properties
are still assigned. Use the font list box in the format bar. You may have to unhide
the format bar first. Use the menu command "View Format Bar" to hide or unhide
the format bar.
Remedy:
If you are using a keyboard layout other than that of the default user, then
(Windows 95!) the "Start Exit Exit all applications and log in using another
name" process will remove the current keyboard layout from the memory without
loading the keyboard layout for the default user. The log-in screen form will then no
longer function.
To avoid this, proceed as follows:
Before you log out, either reset the keyboard settings to the original keyboard
layout
or restart Windows.
If the log-in screen form is already blocked, proceed as follows:
Press Ctrl-Alt-Del and choose "Shut down"
or press ESC (to log in as the default user) and then choose "Start Exit Restart
Windows".
Remedy:
To enter these languages, in particular, an Input Method Editor (IME) is required.
This is a tool for composing the ideographs, which are contained in the language-
specific variants of Windows, on a European keyboard.
You will therefore need:
A translator who is a native speaker of your target language
A Windows operating system in the target language
Make sure that your texts are created as a text file. It is also common to use the
following terms for the codes used:
Language Code page Designation
Chinese (Simplified) 936 GB2312
Chinese (Traditional) 950 Big 5
Japanese 932 Shift-JIS
Korean 949 Hangul, Wansung,
KSC 5601
Converting CJK text files in Word format into a text file
Problem:
You have already received texts in Chinese, Japanese or Korean from your
translator. Unfortunately, these texts are stored in Word format.
You want to create a text file from them.
Remedy:
You will need the language pack for the appropriate language for your operating
system.
Microsoft only allows you to download this type of language pack in conjunction
with an Input Method Editor (IME). Appropriate notes and download options can be
found, e.g. at:
http://www.microsoft.com/windows/ie/features/ime.asp
Please note that the IME is offered for each language both with and without the
language pack. You will need, in particular, the language pack.
IME can only be used directly (i.e. direct input of Asian characters) on European
Windows systems with the Microsoft software of the latest generation, e.g. in input
fields of the Internet Explorer 5, as well as with Word 2000. The IME is therefore
offered primarily for the Internet Explorer.
Once you have installed the appropriate language pack, you should be able to
display the Word file correctly.
Format the text using a suitable font. The following fonts are contained in each
language pack:
Language Font
Chinese (Simplified) MS Hei or MS Song
Chinese (Traditional) MingLiU
Japanese MS Mincho or MS Gothic
Korean Gulim
Please note that on an Asian Windows operating system, the names of these font
types may also be written in this font so that illegible characters may initially appear
in the font list box.
Once you have assigned the right font type to the whole text, the characters should
be displayed correctly. If necessary, request a fax copy of the text for comparison.
First save this version of the Word file once more with another name.
Now you can convert the text to a text file, as described in this section under
"Converting a Microsoft Word document into a text file". If the original text was
created using Word 97 or a later version, an intermediate step is required via the
"Word 6.0" format, as described above.
5 References
5
5.1 References for text creation......................................................TX1/5-52
Unicode
Tables, definitions, standards and tools
http://www.unicode.org
I Index
I
I.1 Subject index
Font list in WordPad
Baltic and Turkish missing......... TX1/4-48
C
L S
SINUMERIK 840D/840Di/810D
1 Introduction ..............................................................................................................................TX2/1-3
1.5 Terms.....................................................................................................................................TX2/1-7
3.8 Special considerations when working with Greek and Cyrillic texts .....................................TX2/3-37
3.9 Special considerations when working with East Asian texts ................................................TX2/3-38
5 References..............................................................................................................................TX2/5-47
I Index .........................................................................................................................................TX2/I-49
1 Introduction
1
1.1 General .......................................................................................TX2/1-4
1.5 Terms..........................................................................................TX2/1-7
1.1 General
Since the 1990s, Microsoft have put considerable effort into satisfying global
demands for information processing and software development.
In addition to supporting as many languages as possible, one of the aims was to
be able to support all languages with the same uniform operating system, as
opposed to the language-specific versions of operating systems which were used
before.
As part of these efforts, many of the system components and applications were
gradually converted to the cross-language platform Unicode.
Although in many cases the user would have been completely unaware of this
conversion process, in terms of the subjects discussed in this guide fundamentally
different procedures need to be adopted depending on which version of the
operating system is used.
The procedure recommended for Windows 2000/XP is much simpler than the one
recommended for Windows 95/NT4. Therefore it makes sense to change over to
the new systems. The guide for older systems is only included for reasons of
compatibility and will no longer be maintained or kept up to date.
1.2 Preconditions
This document describes the procedure for creating a text with the following
preconditions:
• The text is to be created on a Microsoft Windows operating system
(Windows 2000 or Windows XP).
• The present description uses German as the default language for all examples
provided herein. However, the described procedure will work just as well with a
different language as the default Windows language.
• The text is to be created as a so-called text file, i.e. without formatting such as
font types, font sizes, underscores etc. This means that, apart from the text
characters, the file will only contain ASCII control characters like Tab, CR and
LF (tab indent, carriage return and line feed).
• The language of the text requires a different Windows code page to that of the
default language, i.e. the target language does not belong to the same
language family as the default language.
• The text file is to be coded using this code page, not as a Unicode file.
• The means used to create the text are to be as simple as possible, i.e.
especially without the need to install any additional software.
• For the purposes of this guide, it is assumed that you have installed Microsoft
Word 2000 (or a later version) and are familiar with using it.
Operating system and target language from the same language family
If the language of the operating system (e.g. German) belongs to the same
language family as the target language (e.g. Portuguese), then some difficulties
could possibly occur with the input of certain characters. However, there will be no
problems displaying these characters with a simple text editor.
Remedy:
• Use the Windows "Character Map"
(see Section 3.2: Entering characters with the character map) or
There should not be any further problems in this case. Use a simple text editor
(e.g. Notepad) and save the texts in the usual way.
Chapter 2 does not apply.
Checking the installation of the Language Support for East Asian languages
Installation of the Language Support for East Asian languages is performed
differently for Windows 2000 and Windows XP.
Please refer to Section 3.9 for details: Special requirements for East Asian
languages
1.5 Terms
Code page
A list of characters which forms the character set for one or more languages. A
code which is unique within this code page is assigned to each of the characters in
the list.
All of the code pages used under Windows share the ASCII range (codes 0 to
127).
There is a 1:1 assignment between Windows code page and language family.
Section 1.3 (Language family) contains a list of the language families in Table 1-1.
Diacritical characters
(diacritical = distinguishing)
In most cases, a relatively small supplementary character, which is attached to a
letter to give the letter a specific stress, a specific pronunciation or even a new
meaning.
• for the combined input if there is no separate key that possesses the required
combined character (see Section 3.4: Using a different keyboard layout),
In all the other cases, the combined letter is always considered as a compound
unit.
In some cases, however, the combined letter is incorrectly referred to as the
diacritical character.
Language family
A language family is a group of languages which uses the same code page. This
requires the use of the same basic alphabet (e.g. Latin or Cyrillic), but it does not
mean that the alphabet of all languages of this group is the same.
There is a 1:1 assignment between Windows code page and language family.
Section 1.3 (Language family) contains a list of the language families in Table 1-1.
Default language
The term "default language" is used in this guide for the language of the operating
system, i.e. German for a German Windows environment and English for an
English Windows environment.
Windows XP:
Under "Control Panel" "Regional and Language Options", in the tab
"Languages", click under the heading "Text Services and Input languages" on the
button "Details..." to reach the dialog "Text Services and Input languages".
Here you can see the default keyboard setting in the "Settings" tab under the
heading "Default Language and Region Support".
Unicode
A 16-bit character set for which code pages are no longer required.
All character codes are unique, without needing to specify the code page.
Unicode programs like Word 2000 do not offer code page-dependent interpreting
of characters and thus also cannot display characters differently by assigning a font
or language property.
2.1 Overview
This section describes how text files can be edited using Microsoft Word 2000.
Word 2000 does not edit text files We recommend saving an additional
directly. Instead, it converts them to version of the text file as a Word file
Word files upon opening. and using this version as the basis for
During saving Word can then convert future editing.
the edited text back into a text file. It is then no longer necessary to open
and convert the file.
Edit
Fig. 2-1
• Make a copy of an existing text file you wish to use as a template for the new
text file.
Now open the text file with Word 2000 in the way described in the next section.
2. From the "Open" dialog box, choose the setting "Encoded Text Files (*.txt)"
under "Files of type".
If your file does not end in "txt" then you will need to rename it first so that it
does end in "*.txt".
Fig. 2-2
3. Choose the file you would like to open and click on "Open".
Instead of steps 1-3, you can also use one of the standard shortcuts:
• In Word you can use the list of the recently used files.
• Drag and drop the text file from Explorer to the Word icon on your desktop.
• If Word has already been launched, drag and drop the text file from Explorer to
the title bar of the Word window.
If however the file is opened straight away with neither the "Convert File" nor
the "File Conversion" dialog boxes opening up, then Word has probably opened
the file incorrectly under the assumption that the text has been written using the
default language.
Be careful with special characters. The special characters will appear incorrectly
if the code page of the text file is not the same as the code page of the default
language.
In this case, go to "Extras" "Options..." and open the Options dialog for Word.
Click on "General" and select the option "Confirm conversion at Open".
When this option is active the additional dialog "Convert File" (see point 5.) will
appear every time, but when the option is inactive it is skipped.
Afterwards close the file and start again from point 1.
Fig. 2-3
Fig. 2-4
Fig. 2-5
7. Click on "OK".
The file is opened and converted to a Word file at the same time.
The existing text is formatted using a default font.
Fig. 2-6
3. Enter the name of the file in the "File name" box and click on "Save".
Fig. 2-7
This warning tells you that saving the file as a text file may result in formatting
information and graphics objects being lost.
This message will even appear if there are no special formatting or graphics
objects in the text.
Click "Yes" to confirm.
Fig. 2-8
Select the encoding which is suitable for your target language and click on "OK".
Section 2.5 (Codes for SINUMERIK HMI) lists which encoding is suitable in
Table 2-1.
Your file is now saved as a text file and encoded using the selected code page in
the process.
Fig. 2-9
This warning will also appear if you have selected the correct code but your file
contains characters which are not permitted, such as Latin mutated vowels in a
Cyrillic text.
Fig. 2-10
If you choose to ignore the warning then all characters which cannot be encoded
are replaced with a question mark.
Depending on the installation of your system, many other codes may be listed,
including those for Unix (ISO), Apple (Mac), OEM (DOS) and mainframe (EBCDIC)
platforms.
Please use the Windows (ANSI) codes for SINUMERIK HMI.
Use the following codes to open and save files (shown in alphabetical sequence in
accordance with the Word listing):
3 Input of Text
3
3.1 Special characters of various language families ......................TX2/3-20
3.9 Special considerations when working with East Asian texts ....TX2/3-38
If you do leave any of the options active then you can always use Ctrl+Z to undo
any automatic corrections. As a general rule this will give the same results as if the
option was deactivated.
2. From "Font", choose the same font type as you have selected for the text file.
Fig. 3-1
4. Under "Character set" select the code page for your text file in order to restrict
the number of available characters to this code page.
The code pages are identified as follows:
Entering characters
1. Choose a character you want to enter.
The information bar at the bottom will display the Unicode code (U+...,
hexadecimal), the code page code (in brackets) and the clear text
description of the character.
If you have set up the keyboard layout accordingly (see Section 3.4: Using
a different keyboard layout), the keystroke combination for entering the
character numerically will appear at the bottom right in the status bar (see
Section 3.5: Numerical text entry).
Fig. 3-2
2. Click on "Select".
The character is copied into the "Characters to copy" field.
Example
With a German keyboard layout, press for example the keys ´ (acute) and "a" one
after the other to obtain the character á (a-acute).
The keys with the diacritical characters, which are thus dealt with in a special way,
are marked with a special color in the descriptions of the keyboard layouts.
Keyboard assignments
The table below shows some keyboard layouts for the supported diacritical
characters:
Table 3-2
Grave accent
Double-acute
Circumflex
Squiggle
Ogonek
Cedilla
Háček
Breve
Colon
Acute
Pixel
Tilde
Keyboard
´ ‚ ˆ ˇ ˘ ˛ ˙ ¨ ¸ ˝ ˚ ˜
assignments
German X X X
French X X X X
Polish X X X X X X X X X X
Spanish X X X X X
Czech X X X X X X X X X X
Hungarian X X X X X X X X X
U.S International X X X X X
http://www.microsoft.com/globaldev/reference/keyboards.aspx
If you press the space bar after the diacritical character, you will see the character
itself.
Note
It can be useful to switch the keyboard layout to "U.S. International" which
corresponds mainly to the American keyboard, but additionally contains 5
diacritical characters and provides many special characters.
However, if you (as a German) only need to make smaller changes to existing files,
then the German keyboard layout may be enough provided there are only a few
special characters which cannot be represented with the German keyboard. You
can enter these characters using the Character Map.
Example
In Hungarian for example, you would have to enter these characters as follows:
• őŐűŰ (O double-acute, U double acute) via the character map
• öÖüÜ directly
• áÁéÉíÍóÓúÚ compound input
If a symbol like DE is displayed in the right-hand task bar then you can also right-
click on this symbol and select the command "Properties" to speed up steps 1
and 2.
Fig. 3-3
3. Click on "Add".
The dialog box "Add Input Locale" is opened.
Fig. 3-4
4. In the dialog "Add Input Locale", select a language under "Input language" and
the associated keyboard layout under "Keyboard layout".
The language ("Input language") may also be the same as the default language
or as some other language for which you have already set up a keyboard
layout. However, in this case you will not be able to make such a good
distinction between the two keyboard layouts, as Windows usually only displays
the language ("Input language").
5. Click on "OK". The dialog box "Add Input Locale" is closed. You then return to
the "Keyboard Properties" window.
6. Use "Hot keys for input locales" to select the way how you want to switch the
keyboard layout. If you select "none", you can only switch using the mouse.
Fig. 3-5
7. Activate the option "Enable indicator on taskbar". This provides you with the
possibility of switching over quickly using the mouse.
2. Click on the "Languages" tab and click on the button "Details..." under the
heading "Text Services and Input Languages".
If a symbol like DE is displayed in the right-hand task bar then you can also right-
click on this symbol and select the command "Properties" to speed up steps 1
and 2.
3. The dialog "Text Services and Input Languages" is opened. Select the
"Settings" tab.
Fig. 3-6
4. Click on "Add".
The dialog box "Add Input Locale" is opened.
Fig. 3-7
5. In the dialog "Add Input Locale", select a language under "Input locale" and the
associated keyboard layout under "Keyboard layout".
The language ("Input language") may also be the same as the default language
or as some other language for which you have already set up a keyboard
layout. However, in this case you will not be able to make such a good
distinction between the two keyboard layouts, as Windows usually only displays
the language ("Input locale").
6. Click on "OK". The dialog box "Add Input Locale" is closed. You then return to
the "Text Services and Input Languages" window.
7. Use "Key settings…" to select the way how you want to switch the keyboard
layout. If you select "none", you can only switch using the mouse.
8. Under the "Language Bar" you can select whether and how the current
keyboard layout is displayed in the task bar or in a special button bar.
3.4.4 Usage
You can now create text with a "keyboard layout" suitable for the target language
(for the input of your texts in a foreign language) or with your previous default
keyboard layout (for the remaining operation). You can switch between the two
layouts as required.
Now, a small blue field with a two-letter language abbreviation should appear in the
task bar for the language you have set:
If you position the mouse pointer on this field (without clicking on it), the setting is
displayed .
If the selected keyboard layout is the default layout for the selected language (e.g.
"Turkish" – "Turkish Q"), then only the language ("Turkish") is displayed, otherwise
the complete settings with language and keyboard layout will be displayed
("Turkish – Turkish F").
Fig. 3-8
If you click with the left mouse button on this field, the languages you have set will
be offered in a small menu.
The current setting is marked by an arrow (Windows XP does this with a check).
Fig. 3-9
If you click with the right mouse button on this field, an abbreviation of the dialog
box "Keyboard Properties" is displayed above the "Properties" menu option.
Fig. 3-10
Further settings are offered under Windows XP. Among other things you can also
arrange this display as an Input language bar independently of the task bar, for
example at the top edge of the screen.
• Enable the window in which you want to enter texts before you select the
keyboard settings for this window.
Menu operation
All menus in the active program will also use the changed keyboard layout. You will
possibly no longer find certain key combinations with ALT and the letter key or Ctrl
with a letter key or even initiate a wrong command by mistake. You should
therefore use the mouse or, in menus, the arrow keys.
Other information
If you do not want to switch back to the other keyboard layout quite as frequently,
you can also declare the new combination with the special keyboard layout as the
default target language in the "Keyboard Properties" (Windows 2000) or "Text
Services and Input Languages" (Windows XP) dialog box:
Windows 2000:
Select the new entry and click on the button "Set as default".
The default setting is indicated with a check mark on the left.
Windows XP:
Select the new setting under "Default Language and Region Support".
Please note that all new windows, the Start menu and the desktop will now also
use the new keyboard layout.
Note
Check whether the automatic option for switching over the keyboard has been
activated in Word. Inadvertent switching of the keyboard layout by Word can
cause confusion.
Section 3.7 (Multi-language Word files) describes situations in which the
automatic keyboard switchover function is useful and how to activate and
deactivate it.
Press the ALT key, and while holding down the key, enter zero and then the three-
digit decimal coding of the desired special character on the numerical key group.
Only then release the ALT key.
Example (Turkish):
ALT+0222 results in Ş (S with cedilla).
To produce this character, you will only need the character map of the appropriate
code page (see Section 1.3: Language family).
You will find overview tables of the code pages e.g. at Microsoft under
http://www.microsoft.com/globaldev/reference/WinCP.mspx
From these tables, combine the headers for the column and row (hexadecimal 00
to FF) and convert this number to form a decimal number (0 to 255).
The 4-digit hexadecimal numbers contained in the individual table fields are the
corresponding Unicode codes which can be used for identification of a character,
but they cannot be used for numerical input of that character.
Section 3.2 (Input via the Character Map) also describes where the key
combination is displayed in the Character Map.
Fig. 3-11
3. In the "Language" dialog box you can choose the correct language. Click on
"OK" when you are done.
Fig. 3-12
4. Then select "Language" from the list of commands on the right (see Fig.).
5. Drag and drop this entry with the left mouse button into a symbol bar.
Fig. 3-13
With this selection box you can then change the selected language for any part of
the text.
Note
The "Detect language automatically" function can often deliver confusing results,
particularly in technical texts.
This option is usually pre-activated as a default setting.
1. Make sure that no part of the text has been highlighted and select the command
"Tools" → "Language" → "Set Language...".
Fig. 3-14
Examples
This can be necessary in the following cases:
• With Greek and Cyrillic texts, the Latin letters and other ASCII characters are
missing in the appropriate keyboard layouts.
• With some keyboard layouts, e.g. Czech, no access to the digits is granted on
the standard keyboard level.
• You as a German want to prepare one part of the text, and a second part is to
be created by your translator.
• This does not need to be a Word table with borders and fields. You can also
use a simple line and separate the different parts with spaces.
• Select the whole line, copy this to the clipboard by using Ctrl-C and paste this
line several times by pressing Ctrl-V. This will give you two columns with
German on the left and Russian on the right.
Table 3-3
[Text 103][Mode 28] "йцукенгшщзхъфывапролджэячсмить"
[Text 103][Mode 28] "йцукенгшщзхъфывапролджэячсмить"
[Text 103][Mode 28] "йцукенгшщзхъфывапролджэячсмить"
[Text 103][Mode 28] "йцукенгшщзхъфывапролджэячсмить"
[Text 103][Mode 28] "йцукенгшщзхъфывапролджэячсмить"
[Text 103][Mode 28] "йцукенгшщзхъфывапролджэячсмить"
German Russian
Fig. 3-15
Note
Accidental use of the automatic keyboard switching function can be confusing.
Only use this option when the above boundary conditions are met.
With Windows XP you are also free to position the Input language bar anywhere
you want on the screen. To do this, click on the button for switching over the
keyboard (e.g. DE ) in the task bar and select "Restore Language and Region
Support Bar".
Fig. 3-16
4. Then select "DE Keyboard Language" from the list of commands on the right
(see Fig.).
5. Drag and drop this entry with the left mouse button into a symbol bar.
Note
If you create texts in the Greek or Cyrillic language for the first time, then you
MUST read this section!
From the view of the language sciences, the Greek and Cyrillic alphabets are
considered as separate and independent alphabets, and not for example as an
extension of the Latin alphabet.
This means that Greek and Cyrillic letters which in their appearance are identical to
Latin letters, are not the same characters and may therefore also not be coded
identically.
In some cases this becomes evident by the fact that although certain letters look
the same in upper case, the corresponding lower case letters look different.
Table 3-4
Example
Incorrect coding could have the following consequences:
Supposed you write the Russian word for "NO" ("HET") using Latin letters instead
of "HET" using Cyrillic letters. Initially you will see no difference. However, the
search for "нет" in lower case letters with the search option "Ignore uppercase/
lowercase letters" will not find the incorrectly coded spelling.
Note
Switch the keyboard to Latin only if this is absolutely necessary! When doing so,
do not switch over for individual letters, but only for complete words and
sentences.
Never use words with mixed codings!
Note
Find out whether and to what extent certain German, English or international
abbreviations (e.g. DIN/ISO) may or must be written using Latin fonts, or whether
a conversion (ДИН/ИСО) is more appropriate according to the conventions of the
country in question.
The key assignment for combinations, such as Ctrl-C, Ctrl-V, Ctrl-Z, Alt-A, etc.
normally follow the US keyboard layout.
• You can see the installed language families in the lower part of the window
under "Language settings for the system".
• Check whether the language family you want to use has been activated.
Fig. 3-17
You may require the Microsoft installation CD to install any missing components.
You will also require Administrator Rights to perform the installation.
Fig. 3-18
You will not usually need the installation CD to reinstall the files for East Asian
languages in Windows XP, as the files are already present on the hard drive in
compressed form.
You will however require Administrator Rights to perform the installation.
Input
An Input Method Editor (IME) is used for inputting. This is a tool which is used to
put together the pictograms on a European keyboard and can be activated
analogously to a keyboard layout.
You will normally need a translator who speaks the target language as his/her
mother tongue to operate the IME system.
From Windows 2000 it is no longer necessary to have the Windows operating
system in the target language.
If you are using characters with a functional significance it is important to use the
ASCII versions.
Fig. 3-19
Note
In the remaining part of the text it is quite acceptable to use full-width characters
for better readability (as in the example here for G49).
Caution
There is even a full-width version of the space character (ideographic space).
You can only recognize this character from its width by selecting it.
Incorrect example:
Fig. 3-20
The circled characters are full-width variants which have been used incorrectly.
Note
When placing a translation order, tell the translator that only the narrow, ASCII-
compatible characters must be used for characters with a functional significance.
Simplified/traditional Chinese
Note
Please make a careful distinction between simplified Chinese and traditional (or
standard) Chinese. The former is used in the PR of China, whereas the latter is
used in Taiwan. These two variants are coded differently and therefore have to
be treated differently. You should therefore also make sure that this is clearly
specified in your translation order.
Creating texts
When you are creating texts in Japanese, Chinese or Korean, it definitely makes
sense to initially create a Word file.
There should be no problems if you are using Word 2000 to exchange documents
with your external translator.
Afterwards you can then convert this Word file into a text file in the way described
in Section 2.4 (Saving text files).
Remedy:
Check the option for automatic switchover of the keyboard as described in Section
3.7: Multi-language Word files.
Deactivate this option.
Remedy:
Deactivate the automatic language recognition option as described in Section 3.6:
Language properties in Word files.
Remedy:
As a result of assigning a different keyboard layout, the keyboard shortcuts have
changed for certain commands. Use the mouse while you are working with the
other keyboard layout.
Remedy:
Check the formal text criteria:
Are all of the characters which have a functional significance correctly encoded?
• If inverted commas are a requirement, check whether Word has converted the
straight inverted commas (ASCII characters) that were entered into
typographic quotation marks. Some disruptive Word options are listed in
Section 3.1: Special characters of various language families.
• If the texts in question are East Asian texts, check the coding of the non-Asian
characters, see Section 3.9: Special requirements for East Asian texts.
If full-width characters have been used for functional characters, replace them
with the corresponding ASCII variants.
Remedy:
This is not necessarily a mistake.
Instead, this has historic reasons. For many years the Yen character has been
used in Japan and the Won character in Korea in place of the backslash character.
This representation was kept once the PC users in those countries had got used to
using this representation in path names (where you would otherwise expect the
backslash character). However, internally this is still the backslash character.
In the fonts "MS Gothic" (Japanese) and "Batang" (Korean) the backslash symbol
is represented as a currency character.
However, it is also possible that the Yen character (Unicode U+00A5) or Won
character (Unicode U+20A9) was actually entered instead of the backslash
character (Unicode U+005C).
To check this, reformat the text in Word using a different font, e.g. "Courier New".
If you see the backslash character in its normal representation then everything is in
order.
However, if you can still see the currency symbol or a symbol which is not a valid
symbol then you should correct the character and replace it with a backslash.
Afterwards revert back to the normal font (MS Gothic or Batang).
5 References
5
5.1 References for text creation......................................................TX2/5-48
Pictures of the keyboard layouts in Microsoft can be found at the following address:
http://www.microsoft.com/globaldev/reference/keyboards.aspx
For printing:
http://www.microsoft.com/globaldev/dis_v1/disv1.asp?DID=dis45d&File=
S25B8.asp
Unicode
Tables, definitions, standards and tools
http://www.unicode.org
I Index
I
I.1 Subject index
Input Method Editor (IME) .............. TX2/1-8
A
K
Automatic keyboard switching...... TX2/3-35
Keyboard layout always visisble ... TX2/3-36
Keyboard layout specific to input
C window ..................................... TX2/3-29
Character Map
Code page..................................TX2/3-22 L
Input ...........................................TX2/3-21
Checking installation .......................TX2/1-7 Language family
CJK characters ................................TX2/1-8 Overview ..................................... TX2/1-5
Code page Language family.............................. TX2/1-8
Designations ..............................TX2/2-18
Number.......................................TX2/2-18
Code page .......................................TX2/1-7 M
Cyrillic language family..................TX2/3-37
Multi-language Word files ............. TX2/3-34
D
O
Default keyboard setting..................TX2/1-9
Overview of diacritical
characters ................................ TX2/3-20
E
File Conversion..............................TX2/2-14
S
A
A Appendix
A.1 References
General Documentation
/ST7/ SIMATIC
Products for Totally Integrated Automation and Micro Automation
Catalog ST 70
Order number: E86060-K4670-A111-A8-7600
/Z/ MOTION-CONNECT
Connections & System Components for SIMATIC, SINUMERIK,
MASTERDRIVES, and SIMOTION
Catalog NC Z
Order number: E86060-K4490-A001-B1-7600
Electronic Documentation
User Documentation
Manufacturer/Service Documentation
a) Lists
/LIS/ SINUMERIK 840D/840Di/810D (03.04 Edition)
SIMODRIVE 611D
Lists
Order number: 6FC5297-7AB70-0BP0
b) Hardware
/ASAL/ SIMODRIVE 611, MASTERDRIVES VC/MC (10.03 Edition)
Planning Guide General Section for AC Induction Motors
Order number: 6SN1197-0AC62-0BP0
c) Software
/FB1/ SINUMERIK 840D/840Di/810D/FM-NC (03.04 Edition)
Description of Functions Basic Machine (Part 1)
(the various sections are listed below)
Order number: 6FC5297-7AC20-0BP0
A2 Various Interface Signals
A3 Axis Monitoring, Protection Zones
B1 Continuous Path Mode, Exact Stop and Look Ahead
B2 Acceleration
D1 Diagnostic Tools
D2 Interactive Programming
F1 Travel to Fixed Stop
G2 Velocities, Setpoint/Actual Value Systems, Closed-Loop Control
H2 Output of Auxiliary Functions to PLC
K1 Mode Group, Channels, Program Operation Mode
K2 Axis Types, Coordinate Systems, Frames,
Actual-Value System for Workpiece, External Zero Offset
K4 Communication
N2 EMERGENCY STOP
P1 Transverse Axes
P3 Basic PLC Program
R1 Reference Point Approach
S1 Spindles
V1 Feeds
W1 Tool Compensation
d) Installation
& start-up
/BS/ SIMODRIVE 611 analog (10.00 Edition)
Description Start-Up Software for
Main Spindle and Asynchronous Motor Modules Version 3.20
Order number: 6SN1197-0AA30-0BP1
I Index
I
I.1 Subject index
Activating data transfer via PLC
Job processing............................IM4/5-60
/ Actual value display: settable zero
system.......................................IM4/5-64
//A ..................................................BE1/3-64 ADDHTX ....................................... BE1/3-52
//B ..................................................BE1/3-85 Addressing system variables
//M..................................................BE1/2-21 indirectly..................................... BE1/3-57
//S ........................................ BE1/2-18, 2-29 al ................................................... BE1/3-55
Alarm display .................................IM2/5-58
6 Alarm text files
MMC 103 ................................. BE1/7-173
6 Change TCP/IP settings........... IM4/7-182 Alarm text files for HT 6 .............IM2/11-203
Alarm text variables ......................HE1/1-17
Alarm texts ...................................IM2/6-116
A ALARM_ROTATION_CYCLE
MD 9056 .....................................IM2/5-99
ac......................... BE1/2-31, 3-55, IM4/5-69 Alarms
Accelerated WIN XP startup.......... IM4/4-42 Comments .................................HE1/2-31
Access level......... BE1/2-30, 3-44, IM4/5-69 Altered MD, Data backup.............IM2/8-153
Access mode Analog spindles..............................IM2/5-66
Direct ..........................................BE1/3-66 ANSI tables/fonts .........................IM4/6-174
Search ........................................BE1/3-66 AP ................................................. BE1/3-89
Access rights ................. IM2/5-51, IM4/4-46 Array access ................................. BE1/3-65
Accessories for PCU20 ................. IM2/2-13 Array status................................... BE1/3-69
Accessories ..................................... IM2/1-8 Array ............................................. BE1/3-64
Action log Articulated position STAT ..............IM2/5-72
HT 6........................................ IM2/11-213 ASCII editor................................... BE1/2-14
Outputting the log file ............... IM4/8-246 Attributes..............................BE1/2-24, 3-44
Read out log file, HMI Automatic keyboard switching ...... TX2/3-35
Emdedded............................. IM2/9-165
Reading out the log file, HT6.. IM2/11-215
Set, HT 6 ................................ IM2/11-215
B
ACTION_LOG_MODE
9012 ....................................... IM2/11-213 Background color .......................... BE1/3-45
ACTION_LOG_MODE Backing up/restoring
MD 9012..................................... IM2/5-97 partitions............. IM4/7-218, 7-220, 7-223
ACTION_LOG_MODE Base offset .....................................IM2/5-67
MD9012.................................... IM2/9-162 Basic PCU software .......................IM4/3-17
Action.............................................BE1/3-36 bc .................................................. BE1/3-56
Activate tool offset immediately..... IM2/5-65 Binary notation .............................. BE1/3-95
ACTIVATE_SEL_USER_DATA Block ............................................. BE1/3-85
MD 9440................................... IM2/5-108 Blue screen, HT 6 ......................IM2/11-216
Displays .........................................BE1/3-59 F
Distribution
Configuration files ....................BE1/7-168 FALSE........................................... BE1/3-97
DLGL .............................................BE1/3-83 fc ................................................... BE1/3-56
DLL file .........................................BE1/3-94 FCT ............................................... BE1/3-93
Documentation ................................ IM2/1-9 Feature
Domain Name Server.................... IM4/3-22 Custom .................................... BE1/6-151
DOS conventions ...........................BE1/1-8 File
DP..................................................BE1/3-91 Check......................................... BE1/3-91
DPSIM.INI.................................... IM4/5-116 Copy .......................................... BE1/3-91
Dynamic user memory (DRAM) .... IM2/5-93 Deleting...................................... BE1/3-91
Selecting .................................... BE1/3-90
Transferring ......................BE1/3-89, 3-90
E
File Conversion ............................ TX2/2-14
File functions................................. BE1/3-88
East Asian texts ............................TX2/3-38
File transfer
Edit resource display ..................... IM2/5-89 RCS Viewer PCU 20 .................IM2/5-87
Edit user list File transfer between RCS Host PCU 20
Network Manager....................... IM2/3-27
and RCS Viewer PCU 20..........IM2/5-83
ELSE .............................................BE1/3-98 Files
EMC/ESD measures ....................... IM4/1-9 Simulation .................................IM4/5-101
ENDIF............................................BE1/3-98
Find a character .......................... BE1/3-100
Enter server name......................... IM2/3-37 Find text ...................................... BE1/4-111
Entering characters .......................TX1/3-24 Fine offset of tools for wear ...........IM2/5-65
ENTRY ........................................BE1/3-106
First boot ......................................IM4/7-184
EP..................................................BE1/3-91 FIRST_LANGUAGE
ERR .............................................BE1/3-105 MD 9003 .....................................IM2/5-96
Error
Flying edge ..................................IM4/5-107
Display selection ......................BE1/5-134 FOC ............................................ BE1/3-105
Error mesages to the PLC Focus .......................................... BE1/3-105
HMI Embedded ........................ IM2/8-157
FOCUS ......................................... BE1/3-38
Error messages to the PLC ........... IM4/5-61 Font
Error status screen ........................ IM2/3-42 Dialog box ................................. TX1/2-16
Error variable ...............................BE1/3-105 List box ...................................... TX1/2-16
ESD measures .............................. IM2/1-10 Font list in WordPad
Establish readiness for operation .. IM2/4-48
Baltic and Turkish missing......... TX1/4-48
EVAL .............................................BE1/3-84 Font size ....................................... BE1/3-44
Event .............................................BE1/3-36 Foreground color........................... BE1/3-45
EXE ..................................... BE1/2-20, 3-79
Free contour programming ...........IM2/5-74
EXIT button fs ................................................... BE1/3-55
REGIE.INI................................. IM4/5-161 Functions ...................................... BE1/3-76
EXIT...............................................BE1/3-78
EXITLS ..........................................BE1/3-79
Expand user displays ................... IM2/5-58 G
EXPONENT_LIMIT
MD 9030..................................... IM2/5-98 G code editor .................................IM2/5-75
EXPONENT_SCIENCE GC................................................. BE1/3-88
MD 9031..................................... IM2/5-98 Graphic position ............................ BE1/2-24
Exponential notation......................BE1/3-95 Graphic ......................................... BE1/2-24
EXTCALL....................................... IM2/3-41 Graphics text................................. BE1/3-43
External functions..........................BE1/3-93 Greek/Cyrillic language
family ...................... TX1/3-22, TX2/3-37
Greek/Cyrillic texts
Special considerations............... TX1/3-42
gt ................................................... BE1/3-55
H I
K Language property
Change ........................................ TX1/1-9
Key words........................................BE1/1-9 Manage...................................... TX1/1-10
Keyboard layout Managing in word processing
Change variable .........................TX1/3-29 programs ................................ TX1/3-36
Check ........................................TX1/3-33 Reinitialize ................................. TX1/3-36
For Greek/Cyrillic font ...............TX1/3-42 Retain ....................................... TX1/2-20
For the Russian font...................TX1/3-43 Save............................................. TX1/1-9
Hungarian...................................TX1/4-47 Language property for text files in
In pictorial format ............. TX1/3-25, 3-33 WordPad.................................. TX1/3-36
Necessity to change...................TX1/3-28 Language property.......................... TX1/1-9
Permanent change ....................TX1/3-25 Language selection
Variable, with correct language Modifying the configuration.......IM2/7-131
assignment..............................TX1/3-34 Language selection........................IM2/5-56
Keyboard layout active ..................TX1/4-46 LANGUAGE_SETTINGS
Keyboard layout always visisble ...TX2/3-36 MD 9980 ...................................IM2/5-114
Keyboard layout specific to input Language-dependent texts ......... BE1/7-158
window ....................................TX2/3-29 LAYOUT_MODE
Keyboard layout specific to input MD 9021 .....................................IM2/5-98
window .....................................TX1/3-32 LB.................................................. BE1/3-86
Keyboard layout ............................TX1/3-24 LCD_CONTRAST
Keyboard setting MD 9000 ....................................IM2/5-96
Default ........................................TX1/1-10 li..................................................... BE1/3-55
Examples....................................TX1/3-38 Limit values ..........................BE1/3-43, 3-72
Keyboard switchover Line feed ....................................... TX1/1-11
Under Windows NT4 ..................TX1/3-34 Linear Flash memory
Keyboard switchover .....................TX1/3-33 card ............................IM2/7-142, 11-202
KEYBOARD_STATE LM ........................................BE1/2-20, 3-76
MD 9009..................................... IM2/5-97 LOAD ............................................ BE1/3-37
KEYBOARD_TYPE Loading a block............................. BE1/3-86
MD 9008..................................... IM2/5-97 Log file
KeyConfiguration .........................BE1/5-130 Display, HT 6 ..........................IM2/11-215
Keys.ini ........................................BE1/5-122 Read out, HMI Emdedded .......IM2/9-165
Keyswitch position......................... IM2/5-53 Reading out, HT 6 ..................IM2/11-215
Keyswitch ...................................... IM2/5-51 Structure ...................................IM2/9-164
Log file .........................................IM4/8-245
Log in default user ......................... TX1/1-8
L Logging in as the default user......... TX1/1-8
Logical drives .................................IM2/3-36
LA ..................................................BE1/3-64 Log-in no longer possible.............. TX1/4-49
Language families ...........................TX1/1-5 Long text ....................................... BE1/3-43
Language family LS.........................................BE1/2-20, 3-77
Language codes.........................TX1/3-23 lt .................................................... BE1/3-55
Overview .....................................TX2/1-5
Language family list box grayed
out ............................................TX1/4-49 M
Language family not appearing .....TX1/4-48
Language family .............TX1/1-10, TX2/1-8 M key ......................................... BE1/5-127
Language group ..............................TX1/1-5 M:N assignments
Language pack ..............................TX1/4-50 NETNAMES.INI ........................IM4/5-160
Language properties MA_AXES_SHOW_GEO_FIRST
Change.......................................TX1/3-36 MD 9421 ...................................IM2/5-107
Save ...........................................TX1/3-41 MA_COORDINATE_SYSTEM
Two in one table ........................TX1/3-40 MD 9424 ...................................IM2/5-107
Q S
USER_CLASS_TM_SKTLLREPR1 V
MD 9265................................... IM2/5-103
USER_CLASS_TM_SKTLLREPR2 V24_PG_PC_BAUD
MD 9266................................... IM2/5-103 MD 9325 ...................................IM2/5-106
USER_CLASS_TM_SKTLLREPR3 V24_PG_PC_CONTROLS
MD 9267................................... IM2/5-103 MD 9323 ...................................IM2/5-105
USER_CLASS_TM_SKTLNEWTOOL V24_PG_PC_DATABITS
MD 9264................................... IM2/5-103 MD 9326 ...................................IM2/5-106
USER_CLASS_TM_SKTOOLLOAD V24_PG_PC_EOF
MD 9252................................... IM2/5-102 MD 9322 ...................................IM2/5-105
USER_CLASS_TM_SKTOOLMOVE V24_PG_PC_LINE
MD 9254................................... IM2/5-102 MD 9329 ...................................IM2/5-106
USER_CLASS_TM_SKTOOLUNLOAD V24_PG_PC_PARITY
MD 9253................................... IM2/5-102 MD 9327 ...................................IM2/5-106
USER_CLASS_VERT_MODE_SK V24_PG_PC_RTS
MD 9249................................... IM2/5-102 MD 9324 ...................................IM2/5-106
USER_CLASS_WRITE_FINE V24_PG_PC_STOPBIT
MD 9203................................... IM2/5-100 MD 9328 ...................................IM2/5-106
USER_CLASS_WRITE_GUD_LUD V24_PG_PC_XOFF
MD 9212................................... IM2/5-100 MD 9321 ...................................IM2/5-105
USER_CLASS_WRITE_PRG_CONDIT V24_PG_PC_XON
MD 9214................................... IM2/5-100 MD 9320 ...................................IM2/5-105
USER_CLASS_WRITE_PROGRAM V24_PRINTER_BAUD
MD 9217................................... IM2/5-100 MD 9315 ...................................IM2/5-105
USER_CLASS_WRITE_RPA V24_PRINTER_CONTROLS
MD 9222................................... IM2/5-101 MD 9313 ...................................IM2/5-105
USER_CLASS_WRITE_SEA V24_PRINTER_DATABITS
MD 9215................................... IM2/5-100 MD 9316 ...................................IM2/5-105
USER_CLASS_WRITE_TCARR V24_PRINTER_EOF
MD 9181..................................... IM2/5-99 MD 9312 ...................................IM2/5-105
USER_CLASS_WRITE_TOA_ADAPT V24_PRINTER_LINE
MD 9209................................... IM2/5-100 MD 9319 ...................................IM2/5-105
USER_CLASS_WRITE_TOA_GEO V24_PRINTER_PARITY
MD 9201................................... IM2/5-100 MD 9317 ...................................IM2/5-105
USER_CLASS_WRITE_TOA_WEAR V24_PRINTER_RTS
MD 9202................................... IM2/5-100 MD 9314 ...................................IM2/5-105
USER_CLASS_WRITE_ZOA V24_PRINTER_STOPBIT
MD 9210................................... IM2/5-100 MD 9318 ...................................IM2/5-105
USER_WRITE_CYCFRAME V24_PRINTER_XOFF
MD 9186..................................... IM2/5-99 MD 9311 ...................................IM2/5-104
USER_WRITE_EXTFRAME V24_PRINTER_XON
MD 9188..................................... IM2/5-99 MD 9310 ...................................IM2/5-104
USER_WRITE_PARTFRAME V24_USER_BAUD
MD 9184..................................... IM2/5-99 MD 9305 ...................................IM2/5-104
USER_WRITE_TOOLFRAME V24_USER_CONTROLS
MD 9183..................................... IM2/5-99 MD 9303 ...................................IM2/5-104
USER_WRITE_TRAFRAME V24_USER_DATABITS
MD 9187..................................... IM2/5-99 MD 9306 ...................................IM2/5-104
USER_WRITE_WPFRAME V24_USER_EOF
MD 9185..................................... IM2/5-99 MD 9302 ...................................IM2/5-104
ut....................................................BE1/3-55 V24_USER_LINE
Utilization display........................... IM2/5-89 MD 9309 ...................................IM2/5-104
V24_USER_PARITY
MD 9307 ...................................IM2/5-104
V24_USER_RTS W
MD 9304................................... IM2/5-104
V24_USER_STOPBIT Windows 95
MD 9308................................... IM2/5-104 Identify version........................... TX1/4-46
V24_USER_XOFF Windows 98, Windows Millennium
MD 9301................................... IM2/5-104 Edition, Windows 2000 ............ TX1/4-48
V24_USER_XON Windows 98 .................................... TX1/1-7
MD 9300................................... IM2/5-104 Windows code page ....................... TX2/1-5
val ............................. BE1/3-56, 3-57, 3-104 Windows tools
Value range .................................BE1/5-123 Scope........................................... TX1/1-6
Var ....................................... BE1/2-25, 3-56 Windows 95
Variable Restrictions ................................ TX1/3-41
Calculation .................................BE1/3-58 Wizard............................................. BE1/1-6
Check .........................................BE1/3-83 WNP.............................................. BE1/3-80
S_CHAN...................................BE1/3-106 Word
Variable propertiy .........................BE1/3-42 Text creation .............................. TX1/4-46
Variable status...............................BE1/3-55 WordPad
Variable type..................................BE1/3-42 Language properties.................. TX1/3-36
Variable value................................BE1/3-55 Start ........................................... TX1/2-14
Variable .........................................BE1/3-42 WordPad 5.0 ................................. TX1/4-48
Variablen properties Work offset fine .............................IM2/5-67
Changing ....................................BE1/3-55 Work offset.....................................IM2/5-67
Variables Workpiece
Default ........................................BE1/3-51 Template ....................................IM2/5-66
Variant ...........................................BE1/3-46 wr .................................................. BE1/3-55
Virtual keys ..................................BE1/5-123 Write mode.................................... BE1/3-46
vld ....................BE1/3-56, 3-57, 3-69, 3-104 WRITE_TOA_FINE_LIMIT
MD 9450 ...................................IM2/5-108
WRITE_ZOA_FINE_LIMIT
MD 9451 ...................................IM2/5-108
Siemens AG Corrections
For Publication/Manual
A&D MC BMS
P.O. Box 3180 SINUMERIK 840D/840Di/810D
Safety
SINUMERIK SINUMERIK Integrated SINUMERIK SINUMERIK SINUMERIK SINUMERIK
840D/810D 840D/840Di/ Application 840D/810D/ 840D/840Di/ 840D/840Di/ 840D/840Di/
810D/ Manual FM-NC 810D 810D 810D
Programming Guide Operator ’s Guide System Overview Configuring Operator Description of Func-
– Short Guide – ManualTurn (HW) *) Components tions
– Fundamentals *) – Short Guide ManualTurn – 810D (HW) *) – ManualTurn
– Advanced *) – ShopMill – 840D – ShopMill
– Cycles – Short Guide ShopMill – ShopTurn
– Measuring Cycles – ShopTurn
– ISO Turning/Milling – Short Guide ShopTurn
– Lists System Variables
Manufacturer/Service Documentation
SINUMERIK
SINUMERIK SIMODRIVE SINUMERIK SINUMERIK SINUMERIK SINUMERIK SINUMERIK
611D 840D/840Di/ 840D/840Di/ 840D/810D 840D/810D 840D/810D 840D/810D
840D/810D 810D 810D
Manufacturer/Service Documentation
MOTION
SINUMERIK SINUMERIK SINUMERIK SINUMERIK SINUMERIK CONTROL
SIMODRIVE SINUMERIK SIMODRIVE SIMODRIVE SIMODRIVE SIMODRIVE SYSTEMS
840D 840D/840Di 840D 840D
810D 611D 611D
611D
Description of Description of Installation & Start-Up – Lists *) Description of Description of Functions EMC
Functions Functions Guide *) Functions – Hydraulics Module Guidelines
SINUMERIK Digitizing – 810D Linear Motor – Analog Module
Safety Integrated – 840D/611D
– HMI
Manufacturer/Service Documentation
Electronic Documentation