hmi sl 1 - siemens ag · 5.5.8 identifiers of cutting edge parameters ... the hmi sl software is...

HMI sl

____________________________________________________________________________________

Preface

System overview 1

Prerequisites 2

Data structure on the CompactFlash card

3

Principles of start-up 4

Functions 5

Appendix A

HMI sl

Commissioning Manual

08/2006 6FC5397-1DP10-0BA0

Valid for SINUMERIK 840D sl/840DE sl control system Software Version NCU system software for 840D sl/840DE sl 2.3 with HMI sl 2.0

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

Danger

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

Warning

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

Caution

with a safety alert symbol, indicates that minor personal injury can result if proper precautions are not taken.

Caution

without a safety alert symbol, indicates that property damage can result if proper precautions are not taken.

Notice

indicates that an unintended result or situation can occur if the corresponding information is not taken into account.

If more than one degree of danger is present, the warning notice representing the highest degree of danger will be used. A notice warning of injury to persons with a safety alert symbol may also include a warning relating to property damage.

Qualified Personnel The device/system may only be set up and used in conjunction with this documentation. Commissioning and operation of a device/system may only be performed by qualified personnel. Within the context of the safety notes in this documentation qualified persons are defined as persons who are authorized to commission, ground and label devices, systems and circuits in accordance with established safety practices and standards.

Prescribed Usage Note the following:

Warning

This device may only be used for the applications described in the catalog or the technical description and only in connection with devices or components from other manufacturers which have been approved or recommended by Siemens. Correct, reliable operation of the product requires proper transport, storage, positioning and assembly as well as careful operation and maintenance.

Trademarks All names identified by ® are registered trademarks of the Siemens AG. The remaining trademarks in this publication may be trademarks whose use by third parties for their own purposes could violate the rights of the owner.

Disclaimer of Liability We have reviewed the contents of this publication to ensure consistency with the hardware and software described. Since variance cannot be precluded entirely, we cannot guarantee full consistency. However, the information in this publication is reviewed regularly and any necessary corrections are included in subsequent editions.

Siemens AG Automation and Drives Postfach 48 48 90437 NÜRNBERG GERMANY

Order No.: 6FC5397-1DP10-0BA0 Edition 08/2006

Copyright © Siemens AG 2006. Technical data subject to change

HMI sl Commissioning manual, 08/2006, 6FC5397-1DP10-0BA0 iii

Preface

Introduction

Structure of the documentation The SINUMERIK documentation is organized in 3 parts: • General documentation • User documentation • Manufacturer/service documentation An overview of publications, which is updated monthly and also provides information about the language versions available, can be found on the Internet at: http://www.siemens.com/motioncontrol Select "Support" → "Technical Documentation" → "Overview of Publications". The Internet version of DOConCD (DOConWEB) is available at: http://www.automation.siemens.com/doconweb Information about training courses and FAQs (Frequently Asked Questions) can be found at the following website: http://www.siemens.com/motioncontrol under menu option "Support"

Target group This document is designed for machine tool manufacturers. The present documentation provides all information required by the manufacturer to start up the software HMI sl.

Standard version This documentation only describes the functionality of the standard version. Extensions or changes made by the machine tool manufacturer are documented by the machine tool manufacturer. Other functions not described in this documentation might be executable in the control. This does not, however, represent an obligation to supply such functions with a new control or when servicing. For the sake of simplicity, this documentation does not contain all detailed information about all types of the product and cannot cover every conceivable case of installation, operation, or maintenance.

http://www.siemens.com/motioncontrol

http://www.automation.siemens.com/doconweb


Preface

HMI sl iv Commissioning manual, 08/2006, 6FC5397-1DP10-0BA0

Technical Support If you have any queries, please contact our hotline:

Europe and Africa time zone: A&D Technical Support Phone: +49 (0) 180 / 5050 - 222 Fax: +49 (0) 180 / 5050 - 223 Internet: http://www.siemens.com/automation/support-request E-mail: mailto:[email protected]

Asia and Australia time zone A&D Technical Support Phone: +86 1064 719 990 Fax: +86 1064 747 474 Internet: http://www.siemens.com/automation/support-request E-mail: mailto:[email protected]

America time zone A&D Technical Support Phone: +1 423 262 2522 Fax: +1 423 262 2289 Internet: http://www.siemens.com/automation/support-request E-mail: mailto:[email protected]

Note Country telephone numbers for technical support are provided under the following Internet address: Enter http://www.siemens.com/automation/service&support

http://www.siemens.com/automation/support-request

mailto:[email protected]





http://www.siemens.com/automation/service&support

Preface

HMI sl Commissioning manual, 08/2006, 6FC5397-1DP10-0BA0 v

Questions about the manual If you have any queries (suggestions, corrections) in relation to this documentation, please fax or e-mail us: Fax: +49 (0) 9131 / 98 - 63315 E-mail: mailto:[email protected] Fax form: See the reply form at the end of the document.

Internet address http://www.siemens.com/motioncontrol

EC declaration of conformity The EC Declaration of Conformity for the EMC Directive can be found/obtained • in the internet:

http://www.ad.siemens.de/csinfo under the Product/Order No. 15257461

• at the relevant branch office of the A&D MC Business Division of Siemens AG



http://www.ad.siemens.de/csinfo

Preface

HMI sl vi Commissioning manual, 08/2006, 6FC5397-1DP10-0BA0

HMI sl Commissioning manual, 08/2006, 6FC5397-1DP10-0BA0 vii

Table of contents Preface ...................................................................................................................................................... iii 1 System overview..................................................................................................................................... 1-1 2 Prerequisites........................................................................................................................................... 2-1

2.1 Hardware/Software .................................................................................................................... 2-1 2.2 Limitations .................................................................................................................................. 2-1

3 Data structure on the CompactFlash card .............................................................................................. 3-1 4 Principles of start-up ............................................................................................................................... 4-1

4.1 Processing a file via program manager ..................................................................................... 4-1 4.2 External processing of a file....................................................................................................... 4-2

5 Functions ................................................................................................................................................ 5-1 5.1 Protection levels......................................................................................................................... 5-1 5.1.1 Setting protection level via password ........................................................................................ 5-2 5.1.2 Setting protection level via machine data display ...................................................................... 5-3 5.2 Display machine data................................................................................................................. 5-4 5.3 Access to internal and external storage media - logical drives................................................ 5-12 5.3.1 Introduction .............................................................................................................................. 5-12 5.3.2 Configuring drive connection ................................................................................................... 5-13 5.4 Configuring user alarm texts .................................................................................................... 5-16 5.4.1 Creating in-house alarm texts .................................................................................................. 5-16 5.4.2 SourceURLs of the NC ............................................................................................................ 5-20 5.4.3 Parameter specifications in alarm texts ................................................................................... 5-21 5.4.4 Creating in-house text library ................................................................................................... 5-22 5.4.5 Supported languages............................................................................................................... 5-26 5.5 Configuring tool management.................................................................................................. 5-27 5.5.1 HMI sl without or with tool management.................................................................................. 5-27 5.5.2 Modifying the user interface of the tool management.............................................................. 5-28 5.5.3 Configure tool types ................................................................................................................. 5-28 5.5.4 Configure the "New tool - favorites" window............................................................................ 5-29 5.5.5 Configure lists .......................................................................................................................... 5-30 5.5.6 Configure general settings ....................................................................................................... 5-31 5.5.7 Identifiers of parameters .......................................................................................................... 5-32 5.5.8 Identifiers of cutting edge parameters ..................................................................................... 5-33 5.5.9 Identifiers of monitoring data.................................................................................................... 5-34 5.5.10 Identifiers of magazine location data ....................................................................................... 5-35 5.6 Axis moving buttons on HT 8 ................................................................................................... 5-36 5.7 Entering the license key........................................................................................................... 5-37 5.8 Virtual keyboard ....................................................................................................................... 5-38 5.9 Setting the time and date ......................................................................................................... 5-38

Table of contents

HMI sl viii Commissioning manual, 08/2006, 6FC5397-1DP10-0BA0

5.10 Change Language.................................................................................................................... 5-39 A Appendix.................................................................................................................................................A-1

A.1 Correction sheet - fax template..................................................................................................A-1 A.2 Overview of SINUMERIK............................................................................................................A-2

Index................................................................................................................................................ Index-1

Tables

Table 5-1 Protection levels concept ........................................................................................................... 5-1 Table 5-2 Standard parameter specifications .......................................................................................... 5-21 Table 5-3 Supported languages ............................................................................................................... 5-26

HMI sl Commissioning manual, 08/2006, 6FC5397-1DP10-0BA0 1-1

System overview 1Introduction

The HMI sl V2.0 software is an integral component of the NCU V2.3 software and it can thus run on the NCUs 7x0. The visualization and operation is handled via a SINUMERIK operation panel (e.g. OP 012, TP 015AT, OP 08T, HT 8) which is connected via TCU (Thin Client Unit) to the NCU (Numerical Control Unit). The standard data carrier of the HMI sl software is the CompactFlash card of the NCU. The HMI sl software is started automatically when the NCU software starts up and in the delivery state offers its standard functional scope, which depends on the current NC and PLC configuration. This start-up manual describes the possible functional expansions and adjustments by the machine manufacturer.

System overview

HMI sl 1-2 Commissioning manual, 08/2006, 6FC5397-1DP10-0BA0


Prerequisites 22.1 2.1 Hardware/Software

It is a requirement that all system components be fully mounted, installed and configured. The start-up of NC and PLC should be essentially completed. The PLC is in the "Run" condition. • USB keyboard: handles text input with capital and lower-case letters. • Storage medium, e.g. USB FlashDrive and/or network connection: handles data

exchange with an external PC/PG. • TextPad text editor: handles external creation and editing of XML and ini files in

Windows. For further information please visit us on the Internet at: http://www.textpad.com/

• WinSCP: enables protected data transfer between different computers. You can get the program on the Internet at: http://winscp.net/eng/docs/lang:de

2.2 2.2 Limitations With HMI sl, the tool management only supports "milling" technology.

http://www.textpad.com/

http://winscp.net/eng/docs/lang:de

Prerequisites 2.2 Limitations



Data structure on the CompactFlash card 3For HMI sl, all files are stored on the CompactFlash card. The file system of HMI sl consists at the top level of four directories "Siemens", "Add_on", "OEM", and "User". These directories have essentially an identical structure. The files in the “siemens” directory represent the original status and cannot be modified! In order to modify files, copy the original file from the Siemens directory and insert it into the appropriate place in the Add_on, OEM or User directory.

Structure The section of the directory structure on the CompactFlash card that is relevant for HMI sl is depicted below:

/Siemens/sinumerik

/hmi

/osal/qt.cfs // Qt

/osal/ace.cfs // ACE/TAO

/base.cfs // basic system

/appl.cfs // Applications (operating areas)

/lngs/baselng_std.cfs // Texts of the basic system (standard languages)

/lngs/baselng_ex1.cfs // Texts of the basic system (special languages 1)

... // Texts of the basic system in additional

languages

/lngs/appllng_std.cfs // Texts of the applications (standard languages)

/lngs/appllng_ex1.cfs // Texts of the applications (special languages 1)

... // Texts of the applications in additional

languages

/hlps/applhlp_std.cfs // Online help of the applications for standard

languages

/hlps/applhlp_ex1.cfs // Online help of the applications for special

languages 1

... // Online help of the applications for additional

languages

/ico/ico640 // Symbols in resolution 640x480

/ico/ico800

/ico/ico1024

/ico/ico1280

/ico/ico1600

/cfg // All config files for runtime

/lng // All language-dependent texts for runtime (*.qm)

/hlp // Online help for runtime



/deu // Online help in German

/hmi // Directory for HMI online help in German

/hmi.xml

... // Directories for additional books

/eng // Online help in English

/hmi // Directory for HMI online help in English

/hmi.xml

... // Directories for additional help books

... // Directories for additional languages

/tmpp/acxcache

/tmpp/md

/squish // Directories for squish components for test

// Note the following:

// At runtime, the config files are linked from base.cfs and appl.cfs to /cfg

// At runtime, the files are linked with the language-dependent texts to /lng

// At runtime, the files of the online help are linked to /hlp

/Add_on/sinumerik

/hmi

/addon1.cfs // Addon1 (everything except texts and online help)

/addon2.cfs // Addon2 (everything except texts and online help)

... // Additional add-ons

/lngs/addon1lng_std.c

fs

// Language-dependent texts Addon1

/lngs/addon2lng_std.c

fs

// Language-dependent texts Addon2

... // Language-dependent texts of other add-ons

/hlps/addon1hlp_std.c

fs

// Online help Addon1

/hlps/addon2hlp_std.c

fs

// Online help Addon2

... // Online help additional add-ons


/ico/ico800

/ico/ico1024

/ico/ico1280

/ico/ico1600

/appl // Binaries for runtime

/cfg // Config files for runtime

/lng // Language-dependent texts for runtime

/hlp // Online help for runtime (see above)

// Note the following:

// At runtime, the binaries from addon1.cfs, addon2.cfs are linked to /appl.



// At runtime, the config files are linked from addon1.cfs and addon2.cfs to /cfg.

// At runtime, the files are linked with the language-dependent texts to /lng

// At runtime, the files of the online help are linked to /hlp

/OEM/sinumerik /hmi

/oem1.cfs // OEM1 (everything except texts and online help)

/oem2.cfs // OEM2 (everything except texts and online help)

... // Additional OEMs

/lngs/oemlng_std.cfs // Language-dependent texts OEM1

/lngs/oem2lng_std.cfs // Language-dependent texts OEM2

... // Language-dependent texts of other OEMs

/hlps/oem1hlp_std.cfs // Online help OEM1

/hlps/oem2hlp_std.cfs // Online help OEM2

... // Online help additional OEMs


/ico/ico800

/ico/ico1024

/ico/ico1280

/ico/ico1600





/data

/archive // Manufacturer archive (previous card dir for

powerline)

/cc // Compile cycles



/User/sinumerik

/hmi

/dh

user // user (everything except texts and online

help)


/ico/ico800

/ico/ico1024

/ico/ico1280

/ico/ico1600


/base




/data

/data // User memory on CF

/archive // Manufacturer archive (previous card dir for

powerline)

/prog

/wks.dir/*.wpd

/mpf.dir

/spf.dir

/*.dir


Principles of start-up 44.1 4.1 Processing a file via program manager

In order to make specific adjustments, you must copy the original file from the "Siemens" directory into the corresponding folder of the "User" or "OEM" directory. You need the protection level "machine manufacturer."

Procedure 1. Open the operating area "Program Manager." 2. Press the expansion key. 3. Press the "System data" softkey. 4. The available articles are displayed. Open the desired folder in the "CF-

Card\Siemens\sinumerik\hmi directory. 5. Select the desired file. 6. Press the "Copy" softkey. 7. Now open the corresponding folder in the directory:

CF-Card\User\sinumerik\hmi\ or CF-Card\OEM\sinumerik\hmi\ 8. Press the "Insert" softkey. 9. Press the "Input" key or double-click the marked file. The editor is activated automatically

and the file opened.

Note Settings made in the file only become effective after a restart of the HMI sl.

Principles of start-up 4.2 External processing of a file


4.2 4.2 External processing of a file

Editing ini/XML files externally In order to create or process an XML file on an external PC with Windows, use the "TextPad.exe" text editor. TextPad supports the "UTF-8" coding required for XML files. Save the file in UTF-8 coding by selecting UTF-8 for "Encoding" on the "SaveAs" dialog in "TextPad."

Entering comments in XML files If to explain a program, you are entering comments, you must keep the following in mind: • A comment always begins with the sequence: !

Example 

Note In the comment itself, you can never use two minus signs one right after the other!

Entering comments in ini files If you enter a comment in an ini file, begin the comment line with a semicolon.

Copying files with "WinSCP" Copy files via network connection from an external computer to the NCU by using the program "WinSCP." For a detailed description, see the following documentation: References: Start-up operating system NCU sl (IM7), Chapter: Backing up and restoring data and Chapter: Service Tools WinSCP and PuTTY


Functions 55.1 5.1 Protection levels

Introduction Access to programs, data and functions is useroriented and controlled via 8 hierarchical protection levels. These are divided into • 4 password levels for Siemens, machine manufacturer, start-up personnel, and end user • 4 keyswitch positions for end user There are protection levels 0 to 7 (see table below); where • 0 is the highest and • 7 is the lowest level.

Table 5-1 Protection levels concept

Protection level Locked by Area 0 Password Siemens 1 Password: SUNRISE (default) Machine manufacturer 2 Password: EVENING (default) Installation engineer, service 3 Password: CUSTOMER (default) End user 4 Keylock switch position 3 Programmer, machine setter 5 Keylock switch position 2 Qualified operator 6 Keylock switch position 1 Trained operator 7 Keylock switch position 0 Semi-skilled operator

Functions 5.1 Protection levels


5.1.1 Setting protection level via password

Introduction You can influence the protection levels used with passwords via softkeys. Press the "HMI" -> "Password" softkey in the “Startup” operating area. The following softkeys are available: • Set the password • Change the password • Delete (clear) the password

Setting the password 1. Press the softkey "Set password." The "Please enter password:" input window appears. 2. Enter one of the possible default passwords (see table "Protection levels concept") and

confirm the entry with the softkey "OK." A permissible password is set and the valid access level is displayed. Invalid passwords will be rejected.

Changing the password For secure access protection, you should change the default passwords 1. Press the "Change password" softkey. The current access level is displayed in the

window that opens. 2. Mark the area for which you would like to assign the new password. You can select the

following areas here: – System – Vendor – Service – User

3. Enter the new password in the input fields "New password" and "Repeat password." 4. Confirm the entry with the softkey "OK." Both entered passwords must match for the

modified password to become valid.

Functions 5.1 Protection levels


Deleting (clearing) the password 1. Press the softkey "Delete password" in order to reset the access authorization. Access authorization is not automatically deleted at POWER ON!

Notice For a system boot in which standard machine data is loaded, the passwords are set to the default values.

5.1.2 Setting protection level via machine data display Via settings in the display machine data, e.g. "USER_CLASS_.." you have the opportunity to set appropriate read and write protection. In the following chapter, there is a listing of all existing display machine data.

Functions 5.2 Display machine data


5.2 5.2 Display machine data Since for HMI sl there is no user interface for the display machine data, you must change the settings or make changes to the data in the file "hmi_md.ini." This file is located in the directory user/sinumerik/hmi/cfg.

Note Only the data described here is relevant.

List of the display machine data and its function

$MM_DISPLAY_RESOLUTION = 3 Description: Number of decimal places for metric values, e.g. actual values Range: 0 - 5 Default: 3 Effective: Restart

$MM_DISPLAY_RESOLUTION_INCH = 4 Description: Number of decimal places for inch values, e.g. actual values Range: 0 - 6 Default: 4 Effective: Restart

$MM_DISPLAY_RESOLUTION_FeedPerTime = 3 Description: Number of decimal places for linear feed values metric Range: 0 - 5 Default: 3 Effective: Restart

$MM_DISPLAY_RESOLUTION_INCH_FeedPerTime = 4 Description: Number of decimal places for linear feed values inch Range: 0 - 6 Default: 4 Effective: Restart



$MM_DISPLAY_RESOLUTION_FeedPerRevolution = 3 Description: Number of decimal places for revolutional feedrate values metric Range: 0 - 5 Default: 3 Effective: Restart

$MM_DISPLAY_RESOLUTION_INCH_FeedPerRevolution = 4 Description: Number of decimal places for revolutional feedrate values inch Range: 0 - 6 Default: 4 Effective: Restart

$MM_DISPLAY_RESOLUTION_RotaryAxis = 3 Description: Number of decimal places for rotary axes metric Range: 0 - 5 Default: 3 Effective: Restart

$MM_DISPLAY_RESOLUTION_RotaryAxisIn = 3 Description: Number of decimal places for rotary axes inch Range: 0 - 6 Default: 3 Effective: Restart

$MM_DISPLAY_RESOLUTION_SPINDLE = 0 Description: Number of decimal places for spindles Range: 0 - 5 Default: 0 Effective: Restart

$MM_ACTIVATE_FRAME_CHANGES_AT_ONCE =1 Description: Changes to a user or base frame are applied on the next block change,

even if they have already been selected. Range: 0 - 1 Default: 1 Effective: Restart



$MM_AXES_SHOW_GEO_FIRST= 1 Description: Geometry axes are always output in the first position in lists Range: 0 - 1 Default: 1 Effective: Restart

$MM_BLOCK_SEARCH_MODE_MASK=0x33 Description: Via a bit mask, determine the possible selection for the block search

mode 0x01, Search mode end of block 0x02, Search mode contour 0x10, Search mode without calculation in the main program 0x20, Search mode SERUPRO test run

Range: 0 – 0xFF Default: 0x33 Effective: Restart

$MM_COORDINATE_SYSTEM=0 Description: Show actual values SZS coordinate system Range: 0 - 1 Default: 0 Effective: Restart

$MM_MAX_SKP_LEVEL=1 Description: Specify how many skip levels can be selected Range: 1 - 10 Default: 1 Effective: Restart



$MM_TEACH_MODE=5 Description: Set teach mode: TEACH_MODE

bit0 Standard teaching Taught block is incorporated with softkey "Include in the program."

TEACH_MODE bit1

Inclusion of the taught block can be blocked by the PLC. DB19.DBX13.0 = 0 block is included DB19.DBX13.0 = 1 block is not included

TEACH_MODE bit2

Block selection explicit

TEACH_MODE >= 0x0000FFFF

Bits 16-31 are reserved for the OEM

Default: TEACH_MODE = 0x05

Standard teaching with explicit block selection

Range: 0 – 0xFFFFFFFF Default: 5 Effective: Restart

$MM_ONLY_MKS_DIST_TO_GO=0 Description: Always show distances-to-go in the MCS coordinate system Range: 0 - 1 Default: 0 Effective: Restart

$MM_SPIND_MAX_POWER=100 Description: Spindle load in normal range (green) Range: 0 - 200 Default: 100 Effective: Restart

$MM_SPIND_POWER_RANGE=100 Description: Spindle load total range (green + red) Range: 0 - 200 Default: 100 Effective: Restart



$MM_STAT_DISPLAY_BASE=2 Description: Numerical basis for representation of moving joint STAT

Possible values are: 00: Not displayed 02: Display as binary value 10: Display as decimal value 16: Display as hexadecimal value

Range: 0 - 16 Default: 2 Effective: Restart

$MM_TU_DISPLAY_BASE=2 Description: Numerical basis for representation of rotary axis position TU

Possible values are: 00: Not displayed 02: Display as binary value 10: Display as decimal value 16: Display as hexadecimal value

Range: 0 - 16 Default: 2 Effective: Restart

$MM_USER_CLASS_CLEAR_RPA=7 Description: Delete-protection of R parameters for Delete all softkeys Range: 0 - 7 Default: 7 Effective: Restart

$MM_USER_CLASS_READ_GUD_LUD=7 Description: Read protection for user data (GUD, PUD, LUD) Range: 0 - 7 Default: 7 Effective: Restart



$MM_USER_CLASS_SHOW_SBL2=7 Description: Activation protection for SBL2 (calculation block coarse) Range: 0 - 7 Default: 7 Effective: Restart

$MM_USER_CLASS_WRITE_BASE_FRAME =7 Description: Write protection for base frames (basic ZO) Range: 0 - 7 Default: 7 Effective: Restart

$MM_USER_CLASS_WRITE_CYCFRAME=7 Description: Write protection for cycle frame Range: 0 - 7 Default: 7 Effective: Restart

$MM_USER_CLASS_WRITE_EXTFRAME=7 Description: Write protection for frame exernal ZO Range: 0 - 7 Default: 7 Effective: Restart

$MM_USER_CLASS_WRITE_GUD_LUD=7 Description: Write protection for user data (GUD, PUD, LUD) Range: 0 - 7 Default: 7 Effective: Restart

$MM_USER_CLASS_WRITE_PARTFRAME=7 Description: Write protection for frame tool reference point Range: 0 - 7 Default: 7 Effective: Restart



$MM_USER_CLASS_WRITE_PRG_CONDIT=7 Description: Write protection program control Range: 0 - 7 Default: 7 Effective: Restart

$MM_USER_CLASS_WRITE_RPA=7 Description: Write protection for R parameters also applies to softkey Delete area Range: 0 - 7 Default: 7 Effective: Restart

$MM_USER_CLASS_WRITE_SEA=7 Description: Write protection for setting data Range: 0 - 7 Default: 7 Effective: Restart

$MM_USER_CLASS_WRITE_SETFRAME =7 Description: Write protection for frame preset Range: 0 - 7 Default: 7 Effective: Restart

$MM_USER_CLASS_WRITE_TOOLFRAME=7 Description: Write protection for frame tool Range: 0 - 7 Default: 7 Effective: Restart



$MM_USER_CLASS_WRITE_TRAFRAME=7 Description: Write protection for frame transformation Range: 0 - 7 Default: 7 Effective: Restart

$MM_USER_CLASS_WRITE_WPFRAME=7 Description: Write protection for frame workpiece reference point Range: 0 - 7 Default: 7 Effective: Restart

$MM_USER_CLASS_WRITE_USER_FRAME =7 Description: Write protection for user frames (settable ZO) Range: 0 - 7 Default: 7 Effective: Restart

$MM_USER_CLASS_WRITE_FRAMES_FINE =7 Description: Write protection for all ZOs fine Range: 0 - 7 Default: 7 Effective: Restart

$MM_WRITE_FRAMES_FINE_LIMIT =7 Description: Input limit for all ZOs fine Range: 0 - 7 Default: 7 Effective: Restart

USER_CLASS_WRITE_PROGRAM=7 Description: Protection level for editing a part program Range: 0 - 7 Default: 7 Effective: Restart

Functions 5.3 Access to internal and external storage media - logical drives


USER_CLASS_TEACH_IN=7 Description: Protection level for writing a program Range: 0 - 7 Default: 7 Effective: Restart

5.3 5.3 Access to internal and external storage media - logical drives

5.3.1 Introduction The NCU hardware has its own network card and can be integrated in an existing network. As implemented, the operating area "Program manager" displays only NC data (passive file system) and the data of the local drive (HMI). However additional views can be incorporated into the program manager for so-called logical drives.

Setting up connections The number of connections between the HMI sl and different local and logical drives is limited to eight. The connections are set up via the file "logdrive.ini." The first time you set up "logical drives," copy the file from the Siemens directory into the "User" directory. The original file is in the following directory: CF-Card\Siemens\sinumerik\hmi\cfg



5.3.2 Configuring drive connection

Using the "logdrive.ini" file • You define all logical drives in section [CONNECTIONS]. • You can enter the number of logical drives next to "ConnectionNum." There are further settings for each logical drive. The "X" at the end must be replaced in each case with the number of the drive connection.

ConnectionX Path of the drive, e.g. //my computer/my path UsernameX User name (for network drives) PasswordX Password belonging to UsernameX SK_ConnectionX Enter softkey text NetDriveTypeX Network connection type, e.g. NFS, SMBFS SoftkeyIndexX Softkey position on the horizontal softkey bar.

• Index 1-8 is the first ETC level, • Index 9-16 second level, etc.

SoftkeyTextContextX: Text context associated with Text-ID (only for language-dependent softkey texts) -> is not supported for SW-HMI sl V2.0!

SoftkeyTextFileX Text file that contains the softkey text specified via Text-ID (only for language-dependent softkey texts) -> is not supported for SW-HMI sl V2.0!

SoftkeyPictureX Name of the file with the icon that is depicted on the softkey -> is not supported for SW-HMI sl V2.0!

AccessProgramX Access level for the program editor area AccessMachineX Access level for the Machine area AccessServicesX Access level for the Program manager area

Drive paths Use the following syntax to identify the drive paths:

Logical drive Description //NC/MPF.DIR Current NC /SIEMENS/SINUMERIK/MPF.DIR/ /siemens/sinumerik/mpf.dir/ /card/user/data

Local drive on CF

C:/ MPF.DIR/ c:\mpf.dir

External drives WinXP hard disk (Win version)

//tcu1/X204/mpf.DIR //tcu1/X203,1/test/mpf.dir

Global TCU-USB drive Global TCU-USB drive with partition specification



//ACTTCU/FRONT //ACTTCU/FRONT,1

Local TCU-USB drive (=USB device on the active TCU, also has a matching global path) -Local TCU-USB drive with partition data

//ef3307/MPF.DIR External network drives (WinXP) //ef3307/MPF.DIR External network drives (Linux) //NC/NC_CARD/MPF.DIR CF Card via SSH

Note New entries and changes are only incorporated after a restart of the HMI sl.

Exemplary structure of the ini file Standard configuration • The standard softkey is in the position HSK 3 (position 3 on the horizontal softkey bar). • The softkey text is called "USB." Text is read from the text file. • The icon sk_usb_front.png is displayed. • The softkey is visible starting from access level 7 in the program manager.

[CONNECTIONS]

ConnectionNum=1

; local USB device of the current TCU

Connection1=//ACTTCU/FRONT,1

SK_Connection1=SL_PM_SK_LOCAL_TCU_USB

SoftkeyIndex1=3

SoftkeyTextContext1=SlPmLogicalDrives

SoftkeyTextFile1=slpmdialog

SoftkeyPicture1=sk_usb_front.png

AccessProgram1=7

AccessMachine1=7

AccessServices1=7

Configuring NFS drive In the following example, a connection to the computer ef35161c is configured with an NFS network drive. The softkey with the text "LW_NFS" is on the HSK bar in position 4.

Connection2=//ef35161c/testshare

NetDriveType2=nfs

SK_Connection2=LW_NFS

SoftkeyIndex2=4

In addition, you must release the NFS share for the client computer on the NFS server.



Configuring SMB drive In the following example, a connection to the computer ef32123c is configured with a SMB network drive. The softkey with the text "LW_SMB" is located on the 2nd HSK bar in position 1. In addition, user name the and associated password are required.

Connection3=//ef32123c/public

NetDriveType3=smbfs

Username3=test

Password3=Systst02

SK_Connection3=LW_SMBFS

SoftkeyIndex3=9

In addition, you must set up an account on the Windows computer and release the directory (//ef32123c/public) for this account: 1. Properties/Release/Authorizations/Add... 2. Properties/Security/Add... Configuring USB drive In the following example, the USB plug "X203" is configured. The softkey with the text "X203" is on the second HSK bar in position 2.

Connection4=//TCU2/X203

SK_Connection4=x203

SoftkeyIndex3=10

Functions 5.4 Configuring user alarm texts


5.4 5.4 Configuring user alarm texts

Introduction This chapter describes the basics and how to include user-specific alarms and message texts. In the case of HMI sl, all alarm text files are stored on the CompactFlash card or hard disk. The alarm and message text files are stored in the "lng" subdirectory:

"Siemens" (/Siemens/sinumerik/hmi/lng/) "Add_on" (/Add_on/sinumerik/hmi/lng/) "OEM" (/OEM/sinumerik/hmi/lng/) "user" (/User/sinumerik/hmi/lng/)

The user's own alarm text files can be inserted into the areas "Add_on", "OEM" (for the machine manufacturer) or “user” (for end user).

5.4.1 Creating in-house alarm texts

General The alarm texts are stored in standard format (".ts" format) by the HMI sl. The ".ts" format is XML-based and can be read and written with the editor of the HMI sl. To include in-house alarm texts, the following files are provided as samples:

File Folder oem_alarms_deu.ts /siemens/sinumerik/hmi/lng/ oem_slaesvcadapconf.xml /siemens/sinumerik/hmi/base

The alarm texts can be modified or added in the renamed copy of the file "oem_alarms_deu.ts". In the "oem_slaesvcadapconf.xml" file renamed "slaesvcadapconf.xml," the newly created alarm text file is announced to the Alarm&Event Service.

Procedure 1. Create new alarm text file 2. Insert alarm texts 3. Create foreign-language alarm text files and translate texts 4. Create new configuration file 5. Complete configuration file 6. Restart the HMI sl



Create new alarm text file 1. Place a copy of the original file "oem_alarms_deu.ts" from the "siemens" directory in the

directory /oem/sinumerik/hmi/lng/ or /user/sinumerik/hmi/lng/. 2. Enter an OEM-specific name, e.g. "namexyz_deu.ts". Please observe the following when

choosing a name: – Any name can be chosen but it must be written in lower case – The name must be followed by an underscore character – Use the defined abbreviations for the languages, as shown in the "Supported

languages" table – The name must contain a period and postfix

Insert alarm texts 1. Open the file "oem_alarms_deu.ts" in the editor.

2. For each alarm, a separate area must be inserted between the tags <message> and </message>, e.g. <message> <source>700000/PLC/PMC</source> <translation>First OEM sample alarm text</translation> </message>

3. The <source> tag contains the alarm number (acc. to scheme "700000" or "700001") and the source URL (acc. to scheme "/PLC/PMC"). For the possible source URLs, see the following table "SourceURLs of the NC".

4. The <translation> tag contains the OEM alarm text.



Create foreign-language alarm text files and translate texts 1. Copy the file you have just modified 2. Change the language abbreviation in the file name, see "Supported languages" table, e.g.

"namexyz_eng.ts". 3. Place a copy of the file in the same directory /oem/sinumerik/hmi/lng/ or

/user/sinumerik/hmi/lng/. 4. Open the file in the editor. 5. Enter the translated alarm text in the <translation> tag.

Create new configuration file To announce the OEM alarms to the Alarm&Event Service, the "basename" (file name of the alarm text files just created without the language abbreviation and postfix) has to be included in the configuration of the Alarm&Event Service as the new basename. 1. Copy the sample configuration file "oem_slaesvcadapconf.xml" from the directory

/siemens/sinumerik/hmi/base. 2. Insert the file into directory /oem/sinumerik/hmi/lng/ or /user/sinumerik/hmi/lng/ with the

name "slaesvcadapconf.xml".

Complete configuration file 1. Open the file "slaesvcadapconf.xml" in the editor.

2. Enter the new basename, "oem_alarms" in the example. Several files with in-house alarm texts: 1. If there are several files with OEM alarm texts, the same number of base names must be

included in the configuration. The list can be extended to any length. 2. Copy the content of the tag <BaseName>, in the example:

<BaseName_02 type="QString" value="oem_alarms"/> 3. Insert the line between the tag <BaseNames> and </BaseNames>. 4. Increment the number of the last existing "BaseName_xx" tag by one. 5. Insert the basename of the corresponding alarm text file.

Note The tag "BaseName_01" is reserved for Siemens



Restart the HMI sl So that the "Alarm&Event Service" can read the new alarm texts, they must be converted from the ".ts" form into binary format. Thus files with the same name with the postfix ".qm" are created in the same directory. Since the conversion only occurs at start-up, the HMI sl must be restarted. The result of the conversion is written into the file "alarmtext_conversion.log". This also affects errors that occur during conversion, e.g. syntax errors in an alarm text file. You can mark the file "alarmtext_conversion.log" in the program manager and open it in the following directory: CF-Card/User/sinumerik/hmi/log.

Note The conversion only occurs if the file "*.ts" is newer than the associated file "*.qm". To force a new conversion, the file "*.ts" must be edited. (deletion of the file "*.qm" is not possible since it is loaded at runtime of the HMI sl.)



5.4.2 SourceURLs of the NC

SourceURLs of the NC Numerical range Description SourceURL 000.000 – 009.999 General alarms 010.000 – 019.999 Channel alarms 020.000 – 029.999 Axis/spindle alarms 030.000 – 039.999 General 040.000 – 059.999 Reserved 060.000 – 064.999 Cycle alarms SIEMENS 065.000 – 069.999 Cycle alarms user 070.000 – 079.999 Compile cycle manufacturer

& OEM 080.000 – 081.999 Messages standard cycles 082.000 – 082.999 Messages Shopmill & CMT

cycles 083.000 – 084.999 Messages measuring cycles 085.000 – 089.999 Messages user cycles 090.000 – 099.999

Functional alarms

Reserved

/NCK

100.000 – 129.000 System 130.000 – 139.000 OEM 140.000 – 199.999 Reserved

/HMI

200.000 – 299.999 SINAMICS drive 300.000 – 399.999 611D drive

/NCK

400.000 – 499.999 General alarms 500.000 – 599.999 Channel alarms 600.000 – 699.000 Axis/spindle alarms 700.000 – 799.999 User area 800.000 – 899.999 Sequencers/graphs

/PLC/PMC

810.000 – 810.009 System error messages /PLC/DiagBuffer 900.000 – 999.999 611U drive /NCK



5.4.3 Parameter specifications in alarm texts Alarm texts can contain alarm parameters (accompanying values) that specify the cause of an alarm in more detail. These parameters are usually numerical values that are transmitted from an alarm source when the alarm is signaled along with the other alarm data. How the parameters are incorporated into the alarm text is specified via placeholders (parameter specifications) in the language-specific alarm texts, e.g.: "Channel%1 Axis%2 in machine data%3 defined for several channels". On occurrence of an alarm, the text is replaced by the corresponding parameters, e.g.: "Channel%5 AxisA3 in machine data4711 defined for several channels".

Standard parameter specifications The following table shows the standard parameter specifications:

Table 5-2 Standard parameter specifications

Parameter specifier

Description

%1 First parameter from the alarm data of the alarm source %2 Second parameter from the alarm data of the alarm source %3 Third parameter from the alarm data of the alarm source %4 Fourth parameter from the alarm data of the alarm source %5 Fifth parameter from the alarm data of the alarm source

Only for NCK alarms First part (up to the separator) of the fourth parameter from the alarm data of the alarm source

%6 Sixth parameter from the alarm data of the alarm source Only for NCK alarms Second part (between the first and second separator) of the fourth parameter from the alarm data of the alarm source

%7 Seventh parameter from the alarm data of the alarm source Only for NCK alarms Third part (between the second and third separator) of the fourth parameter from the alarm data of the alarm source

%8 Eighth parameter from the alarm data of the alarm source Only for NCK alarms Fourth part (between the third and fourth separator) of the fourth parameter from the alarm data of the alarm source

%9 Ninth parameter from the alarm data of the alarm source %0 Tenth parameter from the alarm data of the alarm source %Z Specially for PLC alarms:

like %1, for S7-HiGraph alarms, the step number of the graph is displayed %A Specially for PLC alarms:

Third and fourth places of the decimal Alarm-ID: 123456, corresponds to the axis number

%K Specially for PLC alarms: Fifth and sixth places of the decimal Alarm-ID: 123456, corresponds to the channel number



Parameter specifier

Description

%N Specially for PLC alarms: First and second places of the decimal Alarm-ID: 123456, corresponds to the signal number

5.4.4 Creating in-house text library

General If a string, called the "identifier", is inserted in the alarm text in pointed brackets next to the place holder (e.g. "%1<ALNX>"), the parameter itself is not inserted in the alarm text but a further text or text fragment from a text library. The parameter value is used as an index in the text library and selects the text to be used. The text to be used can also contain parameters, including index parameters. The text library is selected using the identifier in pointed brackets. The reference from the identifier to the text library is defined via the settings of the Alarm & Event Service adapter. To include in-house alarm texts, the following files are provided as samples:

File Folder oem_indexparams_deu.ts /siemens/sinumerik/hmi/lng/ oem_slaesvcadapconf.xml /siemens/sinumerik/hmi/base

The format of the text library corresponds to that of an alarm text file.

Procedure 1. Creating new parameter file for text library 2. Insert parameter texts 3. Create foreign-language parameter file and translate parameter texts 4. Complete configuration file 5. Restart the HMI sl

Creating new parameter file for text library 1. Place a copy of the original file "oem_alarms_deu.ts" from the "siemens" directory in the

directory /oem/sinumerik/hmi/lng/ or /user/sinumerik/hmi/lng/. 2. Enter an OEM-specific name, e.g. "namexyz_deu.ts". Please observe the following when

choosing a name: – Any name can be chosen but it must be written in lower case.



– The name must be followed by an underscore character. – Use the defined abbreviations for the languages, as shown in the "Supported

languages" table. – The name must contain a period and postfix.

Insert parameter texts 1. Open the file "oem_indexparams_deu.ts" in the editor

2. In the tag <name>, enter an in-house name, e.g. <name>oem_context</name>

3. For each parameter text, a separate area must be inserted between the tags <message> and </message>, e.g. <message> <source>1</source> <translation>First OEM parameter text</translation> </message>

4. The <source> tag contains the parameter value (acc. to the scheme "1" or "2"). 5. The <translation> tag contains the parameter text.

Create foreign-language parameter file and translate parameter texts 1. Copy the file you have just modified. 2. Change the language abbreviation in the file name, see "Supported languages" table, e.g.

"namexyz_eng.ts". 3. Place a copy of the file in the same directory /oem/sinumerik/hmi/lng/ or

/user/sinumerik/hmi/lng/. 4. Open the file in the editor. 5. Enter the translated parameter text in the <translation> tag.

Complete configuration file So that the newly-created parameter file is recognized in the text library of the "Alarm&Event Service," the following names must be included in the configuration of the "Alarm&Event Service": • Identifer • Basename (file name of the just-created parameter text files without language

abbreviation and postfix) • ContextName 1. Open the file "slaesvcadapconf.xml" already created for the in-house alarm texts in the

directory /oem/sinumerik/hmi/cfg or /user/sinumerik/hmi/cfg.

2. Remove the lines "". 3. Enter the identifier, e.g. <Identifier type="QString" value="OEM"/>. The identifier is always

stated in pointed brackets next to the parameter specification in the alarm text, e.g.: %1<OEM>.

4. Enter the correct BaseName, e.g. <BaseName type="QString" value="oem_indexparams"/>.

5. Enter the ContextName, e.g. <ContextName type="QString" value="oem_contextEM"/>.



Inserting several identifiers: 1. Mark and copy the definition area <OEM_IndexText_01> bis </OEM_IndexText_01>. 2. Insert the area before the tag </IndexTexts>. 3. Change the names of the opening and closing tags, as well as the abovementioned fields

"Identifier," "BaseName," and "ContextName."

Note To prevent overlaps, use different names for the opening and closing tags of the definition area. The names "IndexText_01" to "IndexText_99" are reserved for Siemens.

Restart the HMI sl So that the "Alarm&Event Service" can read the new parameter texts, they must be converted from the ".ts" form into binary format. Thus files with the same name with the postfix ".qm" are created in the same directory. Since the conversion only occurs at start-up, the HMI sl must be restarted. The result of the conversion is written into the file "alarmtext_conversion.log". This also affects errors that occur during conversion, e.g. syntax errors in a parameter file. You can mark the file "alarmtext_conversion.log" in the program manager and open it in the following directory: CF-Card/User/sinumerik/hmi/log.

Note The conversion only occurs if the file "*.ts" is newer than the associated file "*.qm". To force a new conversion, the file "*.ts" must be edited. (deletion of the file "*.qm" is not possible since it is loaded at runtime of the HMI sl.)



5.4.5 Supported languages

Table 5-3 Supported languages

Language Language codes Standard languages Chinese (simplified) chs X Chinese (traditional) cht Danish dan German en X English eng X Finnish fin French fra X Italian ita X Japanese jpn Korean kor Dutch nld Polish plk Portuguese ptb Russian rus Swedish sve Spanish esp X Czech csy Turkish trk Hungarian hun

Functions 5.5 Configuring tool management


5.5 5.5 Configuring tool management

5.5.1 HMI sl without or with tool management

Machine data for operation without tool management If HMI sl should be operated without tool management, the following MD settings must be made:

19320

$ON_TECHNO_FUNCTION_MASK = 02000000H Bit25 (counted from 0) must be 1 so that the channel-specific $MC_TOOL_MANAGEMENT_MASK Bit1 can be switched on.

18080

$MN_MM_TOOL_MANAGEMENT_MASK = 02H Bit1 (counted from 0) must be 1.

20310

$MC_TOOL_MANAGEMENT_MASK = 02H Bit1 (counted from 0) must be 1 for each channel of a TOA.

17530

$MN_TOOL_DATA_CHANGE_COUNTER = 0FH Bit0, Bit1, Bit2 und Bit3 (counted from 0) must be 1.

28450

$MC_MM_TOOL_DATA_CHG_BUFFER_SIZE = 100 For each 1st channel of a TOA.

Machine data for operation with tool management If HMI sl should be operated with tool management, the following MD settings must also be made:

18080

$MN_MM_TOOL_MANAGEMENT_MASK = 02H Bit1 (counted from 0) must be 1.

20310

$MC_TOOL_MANAGEMENT_MASK = 02H Bit1 (counted from 0) must be 1.

17530

$MN_TOOL_DATA_CHANGE_COUNTER = 0FH Bit0, Bit1, Bit2 und Bit3 (counted from 0) must be 1.

28450

$MC_MM_TOOL_DATA_CHG_BUFFER_SIZE = 100 For each 1st channel of a TOA.



5.5.2 Modifying the user interface of the tool management Enter the settings in order to change the user interface of the tool management in the configuration file "sltmlistconfig.xml." Enter the settings for the PLC tool management "TRANSLINE 2000" in the configuration file "sltmplclistconfig.xml" ch These files are stored in the following directory: siemens\sinumerik\hmi\appl Before you change the files, make a copy of the sample file in the Siemens directory in the directory: oem\sinumerik\hmi\cfg or user\sinumerik\hmi\cfg.

Procedure • Configure tool types - (not possible for turning and grinding tools!) • Configure the "New tool - favorites" window • Configure lists • General settings

5.5.3 Configure tool types

Note SW HMI sl V2.0 does not support turning and grinding tools!

All information for displaying the tool types on the user interface is stored under <TOOLTYPE_XXX>.

Entries Meaning TOOLTYPE_XXX Tool type: The number (XXX) defines the tool type Tooltype Number of the tool type Name Name for display in the "New tool – Favorites" window Shortname Suggested name for the tool list Tooltip Display on the tooltip IconX Symbol that embodies the tool types and, if present, represents a cut line.

The X stands for the position of the cut. There are 9 cut lines, see the picture below For tool types with a fixed position (e.g. milling), the position 9 is assigned. The assigned icons are displayed in the tool list or in the "New tool – Favorites" window.



Entries Meaning The tool types infeed 520, casting 530 and thread steel 540 are also assigned

cut directions via the icon.

Figure 5-1 Cut lines

Example

5.5.4 Configure the "New tool - favorites" window All information for configuring the "New tool - favorites" window is stored in the tag <NEWTOOLFAVORITENCONFIGURATION>. The window comprises a static and a dynamic part. The upper static part of the window provides the most frequently used tool types. The tool types offered in the dynamic part with the "favorites" are determined by the tools last used.



Entries Meaning MaxDynamicFavorites Defining the number of favorites that are shown in the dynamic part. StaticTooltypes Definition of the tool types that are offered in the static part. DynamicTooltypes Pre-assignment for the favorites.

Example

5.5.5 Configure lists All information for configuring the lists "Tool list", "Tool wear", "OEM", and "Magazine" is stored in the <LISTCONFIGURATION> tag.

Entries Meaning <SlTmToollistForm> Identifier for the tool list. <SlTmToolwearForm> Identifier for the tool wear list. <SlTmToolmagazinForm> Identifier for the magazine list. <SlTmTooloemForm> Identifier for the OEM list. <CAPTION> Definition of the list name. <COLUMNX> Definition of which column is shown. X stands for the column number. <TOOLTYPE_ALL> <TOOLTYPE_XXX> <EMPTY_MAG_PLACE>

Definition of whether the setting of the column applies to all tool types (_ALL) or for a certain tool type (_XXX). XXX stands for the number of the tool type. EMPTY_MAG_PLACE stands for the empty magazine place.

<Item > Identifier of the parameter for the column is entered here.

Deleting/ inserting columns: To just change an existing file, i.e. delete entries from the configuration file or insert entries into it, you can use the following tags:

Entries Meaning <DELETE_COLUMN> Delete column. <COLUMNX> The column to be deleted. <INSERT_COLUMN> Insert column. <COLUMNX> The column to be inserted. <TOOLTYPE_ALL> <TOOLTYPE_XXX> <EMPTY_MAG_PLACE>

Definition of whether the setting of the column applies to all tool types (_ALL) or for a certain tool type (_XXX). XXX stands for the number of the tool type. EMPTY_MAG_PLACE stands for the empty magazine place.

<Item > Identifier of the parameter for the column is entered here.



Example

5.5.6 Configure general settings General settings for the tool management user interface are stored in the <SETTINGS> tag.

Entries Meaning ReactivateWithMagPos true - reactivate with positioning of the magazine

false - reactivate without positioning of the magazine MagazineMoveMessage true - message magazine movement running or ended is displayed

false - no message



Example

5.5.7 Identifiers of parameters For the magazine location data, the following identifiers can be used in the configuration file:

Content_identifier Parameter or property Empty Empty field ToolNo Number of active tool AdaptNo Adapter number assignment DuploNo Duplo number NumCuttEdges Number of cutting edges of tool ToolIdent Tool name ToolIdentRO Tool name, read only access ToolInfo Tool information ToolInMag Magazine in which the tool is located ToolInPlace Magazine in which the tool is located ToolInMagInPlace Magazine location/magazine number ToolMon Tool monitoring method ToolPlaceSpec Location type ToolSearch Tool search type for replacement tools ToolMyMag Owner magazine of the tool ToolMyPlace Owner magazine of the tool ToolSizeLeft Tool size left in half locations ToolSizeRight Tool size right in half locations ToolSizeUpper Tool size upper in half locations ToolSizeDown Tool size down in half locations ToolStateActiv Tool status - tool active ToolStateEnabled Tool status - tool released ToolStateLocked Tool status - tool locked ToolStateLockedRO Tool status - tool locked, only read access ToolStateMeasured Tool status - tool measured ToolStatePrewarn Tool status - tool has reached prewarning limit ToolStatePrewarnRO Tool status - tool has reached prewarning limit, only read access ToolStateInChange Tool status - tool is being changed ToolStateFixed Tool status - tool fixed place coded



Content_identifier Parameter or property ToolStateUsed Tool status - tool was in use ToolAlarmIsExtended PLC tool status - function "extended alarm" active ToolAlarmLimit PLC tool status - alarm limit reached ToolExtAlarmLimit PLC tool status - limit "extended alarm" reached

5.5.8 Identifiers of cutting edge parameters For the cut parameters, the following identifiers can be used in the configuration file:

Content_identifier Parameter or property EdgeNo Cutting edge number ToolType Tool type, Param 1 CuttEdgePos Cut type, Param 2 GeoLength1 Length 1, Param 3 GeoLength2 Length 2, Param 4 GeoLength3 Length 3, Param 5 GeoRadius Radius, Param 6 GeoCornerRadius Corner radius, Param 7 GeoLength4 Length 4, Param 8 GeoLength5 Length 5, Param 9 GeoPitch Thread pitch, Param 9 GeoAngle1 Angle 1, Param 10 GeoAngle2 Angle 2, Param 11 CuttDirection Cut direction, Param 11 WearLength1 Wear length 1, Param 12 WearLength2 Wear length 2, Param 13 WearLength3 Wear length 3, Param 14 WearRadius Wear radius, Param 15 WearCornerRadius Wear corner radius, Param 16 WearLength4 Wear length 4, Param 17 WearLength5 Wear length 5, Param 18 WearAngle1 Wear angle 1, Param 19 WearAngle2 Wear angle 2, Param 20 AdaptLength1 Adapter length 1, Param 21 AdaptLength2 Adapter length 2, Param 22 AdaptLength3 Adapter length 3, Param 23 ReliefAngle Free angle, Param 24 NoseAngle Peak angle, Param 24 TeethCount Tooth number, Param 24 CuttRate Cut speed, Param 25



Content_identifier Parameter or property IsoHNo ISO H number, Param 26 OrientNo Cut orientation, Param 27 OrientV1 Cut orientation vector 1, Param 28 OrientV2 Cut orientation vector 2, Param 29 OrientV3 Cut orientation vector 2, Param 30

5.5.9 Identifiers of monitoring data For the monitoring data, the following identifiers can be used in the configuration file:

Content_identifier Parameter or property SupWarning Prewarning limit, general SupRemaining Actual value, general SupDesired Setpoint, general SupWarningTime Tool life warning limit SupRemainingTime Tool life actual value SupWarningPieces Warning limit for count SupRemainingPieces Actual value for workpiece count SupDesiredTime Setpoint for tool life SupDesiredPieces Setpoint for workpiece count SupWarningWear Prewarning limit for wear SupRemainingWear Actual value for wear SupDesiredWear Setpoint for wear SupExtendedAlarm PLC tool management - extended alarm SupWarningPiecesIncremental PLC tool management - prewarning limit workpiece number,

incrementing SupActualPieces PLC tool management - actual value workpiece number,

incrementing



5.5.10 Identifiers of magazine location data For the magazine location data, the following identifiers can be used in the configuration file:

Content_identifier Parameter or property MagPlaceKind Location type MagPlaceType Location type MagPlaceTNo Tool number of the tool in this location MagPlaceWatchNeighbour Consider adjacent location MagPlaceStateLocked Magazine location locked MagPlaceStateEmpty Magazine location free MagPlaceStateResIntermag Reserved for tool in buffer MagPlaceStateResLoadtool Reserved for tool to be loaded MagPlaceStateOccupiedLeft Magazine location occupied, left half location MagPlaceStateOccupiedRight Magazine location occupied, right half location MagPlaceTNo Tool number of the tool in this location MagPlaceStateOccupiedUpper Magazine location occupied, upper half location MagPlaceStateOccupiedDown Magazine location occupied, lower half location MagPlaceMagazineNo Magazine number MagPlaceTypeIdx Artindex MagPlaceWearGroup Wear group number MagPlaceAdaptNo Adapter number MagPlaceNo Magazine location number MagPlaceNoMagNo Magazine location number/magazine number

Functions 5.6 Axis moving buttons on HT 8


5.6 5.6 Axis moving buttons on HT 8 With the HT 8, the menu of the axis moving buttons consists of two vertical rows of buttons with 8 buttons apiece so that you can plan up to 16 texts. You can configure the labeling of the axis moving buttons in the file "sljkconfig.xml."

Sample structure of the file "sljkconfig.xml"

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<CONFIGURATION>

<State_1>

<Label_2_1>

<ParamText value="%m1%n-" type="QString" />

</Label_2_1>

<Label_2_2>

<ParamText value="%m1%n+" type="QString" />

</Label_2_2>

<Label_3_1>


</Label_3_1>

<Label_3_2>


</Label_3_2>

<Label_4_1>


</Label_4_1>

<Label_4_2>


</Label_4_2>

<Label_5_1>


</Label_5_1>

<Label_5_2>


</Label_5_2>

<Label_5_2>


</Label_5_2>

<Label_7_1>

<Picture value="gripper_open.png" type="QString" />

</Label_7_1>

<Label_7_2>

<Picture value="gripper_close.png" type="QString" />

<Label_7_2>

<State_1>

Functions 5.7 Entering the license key


<CONFIGURATION>

Entries Meaning Label_x_y Assigned to every axis moving button.

The parameters x and y specify the position of the button on the menu. x = position of the button within the sequence, 1 to 8 y = specification of the button row, 1 or 2

ParamText Text on the button: • The text input occurs next to the attribute "value"

2-line labeling possible, max 6 characters per line. • Attribute "type=" contains the fixed value "QString"

%n Sets a line break "%m1" to "%m6" Machine axis name of an axis is referenced and built into the text.

The axis number currently active is read from the table in DB10 and determined using this index of the name from the machine data.

Picture Symbol on the button • The input of he file name of the symbol to be displayed occurs next to the

attribute "value". The files with the symbols are stored in the directory /oem/sinumerik/hmi depending on the resolution in subdirectories /ico/ico640, /ico/ico800, etc.

• Attribute "type=" contains the fixed value "QString"

For the procedure for making additional HT 8 settings, see the following Literature IAM2, IM5: CNC Part 5 (Base software), Thin Client Configuration

5.7 5.7 Entering the license key A suitable license is needed in order to use various options. Licenses are not enabled until you have announced the license key you have purchased to the system.

Procedure 1. In the "Startup" operating area, press the expansion key ">" and the softkey "Licenses". 2. Enter your license key when prompted with "You can enter a new license key here".

Hyphens are inserted automatically after every fourth character. Their only purpose is to improve legibility.

3. When you press the “Apply” softkey, the data is transmitted to the NCU and stored there. 4. Press the “NCK Reset” and “OK” softkey to activate the licenses.

Functions 5.8 Virtual keyboard


5.8 5.8 Virtual keyboard The configuration of the virtual keyboard occurs in the file "slgfw.ini". Copy the file "slgfw.ini" from the directory CF-Card\Siemens\sinumerik\hmi\cfg into the directory CF-Card\user\sinumerik\hmi\cfg and make the following settings to activate or deactivate the keyboard.

Activate virtual keyboard In the [TouchPanel] section, EnableTouch = true In the [Keyboard] section, EnableVirtualKeyBoard = true

Deactivate virtual keyboard In the [TouchPanel] section, EnableTouch = true In the [Keyboard] section, EnableVirtualKeyBoard = false

5.9 5.9 Setting the time and date You can enter the date and time manually as well as select from among different display formats.

Procedure 1. Press the "HMI" -> "Date time" softkey in the “Startup” operating area. 2. In the "Format" fields, select with a mouse click the desired formats for date and time

display. The following formats are made available: – Date:

D.M.YY DD.MM.YY DD.MM.YYYY D/M/YY DD/MM/YY DD/MM/YYYY M/D/YY MM/DD/YY MM/DD/YYYY YYYY/MM/DD

– Time: H:MM:SS HH:MM:SS H:M:S AP H:M:S ap HH:MM:SS AP HH:MM:SS ap

Functions 5.10 Change Language


3. Enter the date and the time in the "new" field. 4. Confirm the entry with the softkey "OK." The new date and time details are accepted and

output on the first line in the "current" fields.

5.10 5.10 Change Language The HMI sl software is available in 6 languages as standard:

Procedure 1. The selection of the first and second language, set in the operating area "Startup" via the

softkeys "HMI" -> "Language selection." 2. Select the first and second languages from the “Language Selection” menu. The following

languages are available: – Simplified Chinese – English – Spanish – French – Italian

During operation, the switchover between the set languages is performed via the "Change Language" softkey in the “Startup” operating area.

HMI sl Commissioning manual, 08/2006, 6FC5397-1DP10-0BA0 A-1

A Appendix AA.1 A.1 Correction sheet - fax template

Appendix

HMI sl A-2 Commissioning manual, 08/2006, 6FC5397-1DP10-0BA0

A.2 A.2 OverviewOverview of SINUMERIK 840D sl/840Di sl

HMI sl Commissioning manual, 08/2006, 6FC5397-1DP10-0BA0 Index-1

Index

A Activate keyboard, 5-38 Alarm text files

Storing, 5-16 alarmtext_conversion.log, 5-19, 5-25 Axis moving buttons HT 8, 5-36

C CAPTION, 5-30 Change Language, 5-39 Changing the password, 5-2 Changing tool management user interface, 5-28 COLUMNX, 5-30 Comment input

ini file, 4-2 XML file, 4-2

CompactFlash Card Directory structure, 3-1

Complete configuration file, 5-18, 5-24 Configuring NFS drive, 5-14 Configuring SMB drive, 5-15 Configuring USB drive, 5-15 Copying original files, 4-1 Create alarm text file, 5-17 Create configuration file, 5-18 Create foreign-language alarm text files, 5-18 Creating parameter file for text library, 5-22 Cut lines, 5-29 Cut parameters

Identifiers, 5-33

D Deactivate keyboard, 5-38 DELETE_COLUMN, 5-30 Deleting (clearing) the password, 5-3 Display machine data, 5-4 Drive path

Syntax, 5-13 DynamicTooltypes, 5-30

E EMPTY_MAG_PLACE, 5-30 Example

NEWTOOLFAVORITECONFIGURATION, 5-30

H HMI sl V2.0, 1-1 hmi_md.ini, 5-4 HT 8, 5-36

I Icon, 5-28 ini file

Example, 5-14 Insert alarm texts, 5-17 Insert foreign-language alarm texts, 5-18 Insert foreign-language parameter texts, 5-24 Insert parameter texts, 5-23 INSERT_COLUMN, 5-30 Item, 5-30 Item, 5-30

L Language codes, 5-26 License key, 5-37

Entering, 5-37 LISTCONFIGURATION, 5-30 logdrive.ini

File structure, 5-13

M Magazine location data

Identifiers, 5-35 MagazineMoveMessage, 5-31 MaxDynamicFavorites, 5-30 Monitoring data

Identifiers, 5-34

Index

HMI sl Index-2 Commissioning manual, 08/2006, 6FC5397-1DP10-0BA0

N NEWTOOLFAVORITENCONFIGURATION, 5-29

O oem_alarms_deu.ts, 5-16 oem_indexparams_deu.ts, 5-22 oem_slaesvcadapconf.xml, 5-16, 5-22

P Parameter specification

Alarm text, 5-21 PLC tool management, 5-28 Program Manager, 4-1 Protection levels, 5-1

Influence via softkeys, 5-2

Q qm-Format, 5-19, 5-25

R ReactivateWithMagPos, 5-31

S Selecting the language, 5-39 Setting the date, 5-39 Setting the password, 5-2 Setting the time, 5-39 Setting up drive (logical drive), 5-12 SETTINGS, 5-31

Shortname, 5-28 slgfw.ini, 5-38 sljkconfig.xml, 5-36 sltmplclistconfig.xml, 5-28 SlTmToollistForm, 5-30 SlTmToolmagazinForm, 5-30 SlTmTooloemForm, 5-30 SlTmToolwearForm, 5-30 SourceURLs of the NC, 5-20 Standard parameter specification

Alarm text, 5-21 StaticTooltypes, 5-30

T TextPad, 2-1, 4-2 Tool parameters

identifiers, 5-32 Tooltip, 5-28 TOOLTYPE, 5-28 TOOLTYPE_ALL, 5-30 TOOLTYPE_XXX, 5-28, 5-30 ts-Format, 5-16

U USB FlashDrive, 2-1 USB keyboard, 2-1 UTF-8, 4-2

W WinSCP, 2-1, 4-2 Write protection

Via display MD, 5-3

hmi sl 1 - siemens ag · 5.5.8 identifiers of cutting edge parameters ... the hmi sl software is...

Documents