Page 1 Preface Fundamental safety instructions SINUMERIK Operate (IM9) SINUMERIK Easy XML SINUMERIK 840D sl Basesoftware and operating SINUMERIK Integrate Access MyMachine / OPC UA software SINUMERIK Integrate Run MyScreens (BE2) Commissioning Manual NCU operating system PCU base software (IM8) PCU base software (IM10) Appendix Valid for Control:...
Page 2 Note the following: WARNING Siemens products may only be used for the applications described in the catalog and in the relevant technical documentation. If products and components from other manufacturers are used, these must be recommended or approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and maintenance are required to ensure that the products operate safely and without any problems.
Page 3 Siemens' content, and adapt it for your own machine documentation. Training At the following address (http://www.siemens.com/sitrain), you can find information about SITRAIN (Siemens training on products, systems and solutions for automation and drives). FAQs You can find Frequently Asked Questions in the Service&Support pages under Product Support (https://support.industry.siemens.com/cs/de/en/ps/faq).
Page 4 This way you avoid mechanical damage to the memory card or the device. ● Only use memory cards that have been approved by Siemens for use with SINUMERIK. Even though SINUMERIK follows general industry standards for memory cards, it is...
Page 5 Table of contents Preface.................................3 Fundamental safety instructions........................7 General safety instructions.......................7 Equipment damage due to electric fields or electrostatic discharge........11 Warranty and liability for application examples..............12 Industrial security........................13 Residual risks of power drive systems...................14 SINUMERIK Operate (IM9)........................15 Easy XML..............................719 SINUMERIK Integrate Access MyMachine / OPC UA................917 SINUMERIK Integrate Run MyScreens (BE2)..................987 NCU operating system...........................1319 PCU base software (IM8)........................1421...
Page 6 Table of contents Basesoftware and operating software Commissioning Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 7 Fundamental safety instructions General safety instructions WARNING Electric shock and danger to life due to other energy sources Touching live components can result in death or severe injury. ● Only work on electrical devices when you are qualified for this job. ●...
Page 8 Fundamental safety instructions 1.1 General safety instructions WARNING Electric shock due to equipment damage Improper handling may cause damage to equipment. For damaged devices, hazardous voltages can be present at the enclosure or at exposed components; if touched, this can result in death or severe injury.
Page 9 ● If you come closer than around 2 m to such components, switch off any radios or mobile phones. ● Use the "SIEMENS Industry Online Support App" only on equipment that has already been switched off. WARNING...
Page 10 Fundamental safety instructions 1.1 General safety instructions WARNING Malfunctions of the machine as a result of incorrect or changed parameter settings As a result of incorrect or changed parameterization, machines can malfunction, which in turn can lead to injuries or death. ●...
Page 11 Fundamental safety instructions 1.2 Equipment damage due to electric fields or electrostatic discharge Equipment damage due to electric fields or electrostatic discharge Electrostatic sensitive devices (ESD) are individual components, integrated circuits, modules or devices that may be damaged by either electric fields or electrostatic discharge. NOTICE Equipment damage due to electric fields or electrostatic discharge Electric fields or electrostatic discharge can cause malfunctions through damaged individual...
Page 12 Fundamental safety instructions 1.3 Warranty and liability for application examples Warranty and liability for application examples The application examples are not binding and do not claim to be complete regarding configuration, equipment or any eventuality which may arise. The application examples do not represent specific customer solutions, but are only intended to provide support for typical tasks.
Page 13 Siemens’ products and solutions undergo continuous development to make them more secure. Siemens strongly recommends to apply product updates as soon as available and to always use the latest product versions. Use of product versions that are no longer supported, and failure to apply latest updates may increase customer’s exposure to cyber threats.
Page 14 Fundamental safety instructions 1.5 Residual risks of power drive systems Residual risks of power drive systems When assessing the machine- or system-related risk in accordance with the respective local regulations (e.g., EC Machinery Directive), the machine manufacturer or system installer must take into account the following residual risks emanating from the control and drive components of a drive system: 1.
Page 15 System overview Principles of start-up General settings SINUMERIK Licensing SINUMERIK 840D sl SINUMERIK Operate (IM9) Creating drive connections Channel menu Commissioning Manual Machine and setting data Customizing the "Machine" operating area Simulation and simultaneous recording Spindle functions Drive system Tool management Configuring alarms Collision avoidance Valid for...
Page 16 Siemens AG Document order number: 6FC5397-1DP40-6BA1 Copyright © Siemens AG 2006 - 2017. Division Digital Factory Ⓟ 12/2017 Subject to change All rights reserved Postfach 48 48 90026 NÜRNBERG GERMANY...
Page 17 Continued Configuring the network Service and diagnostics OEM-specific online help SINUMERIK 840D sl SINUMERIK Operate (IM9) SINUMERIK Integrate - AMB, AMC, AMM Technologies and cycles Commissioning Manual Additional language SINUMERIK Operate on PC/ HT 8 List of abbreviations/ acronyms...
Page 18 Note the following: WARNING Siemens products may only be used for the applications described in the catalog and in the relevant technical documentation. If products and components from other manufacturers are used, these must be recommended or approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and maintenance are required to ensure that the products operate safely and without any problems.
Page 19 Table of contents System overview............................17 System overview........................17 System requirements......................18 Principles of start-up...........................21 Data structure of SINUMERIK Operate..................21 Editing files..........................24 2.2.1 Editing the file at the controller....................24 2.2.2 Editing a file externally......................26 General settings............................29 Changing the language......................29 Set date/time..........................30 Using the time server......................32 Use time zone........................33 Configuring Caps Lock......................34 Activating/deactivating the virtual keyboard................35...
Page 20 Table of contents 3.14.2 Creating your own display configurations................55 3.14.2.1 Displays..........................55 3.14.2.2 Frames...........................56 3.14.2.3 Menus............................58 3.14.2.4 Menu actions..........................64 3.14.2.5 Applications..........................66 3.14.2.6 Global settings........................70 Licensing..............................73 Determining the license requirement..................74 Activating the test license.......................76 Exporting license requirements....................77 Reading in the license key.....................77 Backing up the license of a new CompactFlash card............78 Creating drive connections.........................81 Setting up drives........................81...
Page 21 Table of contents Managing data........................108 7.10 User views..........................110 7.10.1 Creating a user view......................111 7.10.2 Editing the user view......................112 7.10.3 Deleting a user view......................114 7.11 Plain texts for machine and setting data................114 Customizing the "Machine" operating area....................117 Setting the font size of the actual value display..............117 Inserting a user-specific logo....................117 Configuring the display of the G-code groups..............119 Configuring the channel operational message..............120...
Page 22 Table of contents 10.3.9 Clamping system: Diagnostic statistics................158 10.3.10 Clamping system: Clamping time statistics................159 10.3.11 Fetching the logistics data....................159 Drive system.............................161 11.1 Commissioning of drives .....................161 Tool management.............................163 12.1 Machine data for tool management..................163 12.1.1 Settings with/without magazine management..............163 12.1.2 Configuring the access levels of the tool management............164 12.1.3 Additional settings........................166...
Page 23 Table of contents 12.4.1.2 Adaptation of the customer text file..................236 12.4.2 Example: Configuring magazine location types with names..........238 12.4.2.1 Adapting the configuration file....................238 12.4.2.2 Adaptation of the customer text file..................239 12.5 Working with two tool holders....................242 12.6 Editor for the tool and magazine management..............244 12.6.1 Function overview of the tool management editor...............244 12.6.2...
Page 24 Table of contents 14.7 Creating a kinematic structure.....................299 14.7.1 Kinematic elements......................299 14.7.1.1 Creating a kinematic chain element..................299 14.7.1.2 Kinematic rotation and parallel kinematic rotation..............301 14.7.1.3 Linear axis and parallel linear axis..................301 14.7.1.4 Rotary axis and parallel rotary axis..................302 14.7.1.5 Offset and parallel offset......................302 14.7.1.6 Switch and parallel switch....................303 14.7.2...
Page 25 Table of contents Data backup.............................355 16.1 Overview..........................355 16.2 Creating a start-up archive....................356 16.3 Reading-in a start-up archive....................359 16.4 Backing up the hardware configuration................360 16.5 Creating an archive with original data..................361 16.6 Reading in an archive with original data................363 16.7 Generating the complete archive..................364 16.8 Serial interface (V24 / RS232).....................364 16.8.1...
Page 26 Table of contents 18.2.2 Axis diagnostics........................413 18.2.3 Service drive........................418 18.3 System utilization.........................425 18.4 Creating screenshots......................426 18.5 Machine identity........................427 18.5.1 Entering machine-specific information.................428 18.5.2 Create a template.........................429 18.5.3 Import template........................431 18.5.4 Save information........................433 18.5.5 Adding hardware components.....................434 18.5.6 Configuration data........................436 18.6 Logbook..........................436 18.6.1 1.
Page 27 Table of contents 18.12.5 Evaluate a trace........................470 18.12.5.1 Setting trace views.......................470 18.12.5.2 Selecting a variable......................471 18.12.5.3 Scaling the display.......................472 18.12.5.4 Zooming the display......................473 18.12.5.5 Position the cursor.......................474 18.12.5.6 Acquiring measured values....................475 18.13 PROFIBUS/PROFINET and AS-i bus diagnostics...............476 18.13.1 PROFIBUS/PROFINET......................476 18.13.2 Displaying PROFIBUS/PROFINET diagnostics..............477 18.13.3 Configuring the AS-i bus......................478...
Page 28 Table of contents 21.5 Turning..........................529 21.5.1 General..........................529 21.5.2 Setting up cycles for turning....................529 21.5.3 Setting-up ShopTurn cycles for turning................533 21.5.4 Setting up a counterspindle....................535 21.5.5 Setting up the counterspindle under ShopTurn..............538 21.5.6 Technology cycles for turning....................539 21.5.7 Axis configuration of a lathe....................543 21.5.8 Cylinder surface transformation (TRACYL)................544 21.5.9...
Page 29 Table of contents 21.10.5 Logging..........................648 21.10.5.1 Logging the measuring, general...................648 21.10.5.2 Logging while measuring in the JOG mode.................649 21.10.5.3 Logging while measuring in the AUTOMATIC mode............649 21.10.5.4 Manufacturer and user cycle CUST_MEAPROT.SPF............650 21.11 Compare cycles version.......................651 21.11.1 Display cycles version......................651 21.11.2 Specify cycles version......................653 Additional language..........................655...
Page 30 Table of contents SINUMERIK Operate (IM9) Commissioning Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 31 System overview System overview Note PCU / IPC In this document, any textual use of PCU also applies to IPC. The SINUMERIK Operate V4.x operating software is an integral component of the CNC software V4.x and can therefore run on an NCU 7x0.3. The NCU's CompactFlash card is the standard data carrier of the CNC software.
Page 32 System overview 1.2 System requirements System requirements Overview It is a requirement that all system components be fully mounted, installed and configured. Commissioning of the NC and PLC must have been completed. The PLC is in the "Run" condition. ● Storage medium, e.g. USB FlashDrive and/or network connection: Handles data exchange with an external PC/PG.
Page 33 System overview 1.2 System requirements References A detailed description of the structure and commissioning of the system network with controller and operator components is provided in the following description: SINUMERIK 840D sl/840Di sl Operator Components and Networking SINUMERIK Operate (IM9) Commissioning Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 34 System overview 1.2 System requirements SINUMERIK Operate (IM9) Commissioning Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 35 These directories have essentially an identical structure. Note The files in the “siemens” directory represent the original status and cannot be modified! Files, whose contents can be supplemented or modified, are available as templates (specimen files) in the following directories:...
Page 36 Principles of start-up 2.1 Data structure of SINUMERIK Operate siemens directory /cfg // all configuration files /data // version data /hlp // online help files /hlps // online help files, zipped and version files /ico // symbol files /Ico640 // icons in resolution 640x480...
Page 37 Principles of start-up 2.1 Data structure of SINUMERIK Operate addon directory /ico1280 // icons in resolution 1280x1024 /ico1600 // icons in resolution 1600x1240 /lng // text files /lngs // text files zipped and versions files /proj // EasyScreen configuring /template // various templates oem directory /oem/sinumerik...
Page 38 As soon as the file is in the user-specific directory, the entries of this file have priority over the Siemens file. If an entry is missing in a user-specific file, the corresponding entry from the Siemens file is used instead.
Page 39 Principles of start-up 2.2 Editing files Position the cursor on the desired file. Press the "Copy" softkey. For instance, on the NCU in the "System CF card" directory, under "oem" or "user" open the required directory (e.g. /sinumerik/hmi/cfg), in which the copied file should be saved.
Page 40 Principles of start-up 2.2 Editing files - OR - Press the ">>" and "Delete" softkeys. You receive an alarm and you can delete the file by pressing the "OK" softkey. Press the "Cancel" softkey to cancel the delete operation. Displaying the file in the preview window Select the required file.
Page 41 Principles of start-up 2.2 Editing files Example  Note In the comment itself, you can never use two minus signs one right after the other! Special characters If you use characters in the text where the syntax of XML is of significance, then these must specifically formatted: Special characters Notation &...
Page 42 Principles of start-up 2.2 Editing files SINUMERIK Operate (IM9) Commissioning Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 43 General settings Changing the language The operating software is available as standard in several languages. Selecting a language You can define the language selection mode using the following machine data. MD9100 $MM_CHANGE_LANGUAGE_MODE Language selection mode The user-interface language is specified via the "Language Selection" window (default val‐ ue).
Page 44 General settings 3.2 Set date/time Press the ">>" softkey. Press the "Language selection" softkey. The "Language Selection" window opens. All the installed languages are displayed in the fields "First language" and "Second language". Select a language in each of these. Press the <INPUT>...
Page 45 General settings 3.2 Set date/time Time display formats Format Example Hour system H:m:s AP 1:2:4 PM 24 hour system, with display of "AM" / "PM" h:m:s ap 1:2:8 pm 12 hour system, with display of "am" / "pm" HH:mm:ss AP 13:02:08 PM 24 hour system, with display of "AM"...
Page 46 General settings 3.3 Using the time server Note You require administrator rights to set the date and time on the PCU/PC. Using the time server To ensure that the correct time information is always automatically available to the control, you can connect up to three time servers to the operating software.
Page 47 General settings 3.4 Use time zone Note The system checks the time server connection cyclically. If a change is made, it may take a few seconds for the setting to take effect. Procedure Select the "Setup" operating area. Press the "HMI" softkey. Press the "Date/Time"...
Page 48 General settings 3.5 Configuring Caps Lock Procedure Select the "Setup" operating area. Press the "HMI" softkey. Press the "Date/Time" softkey. The "Set Date and Time" window opens. Set the check mark in the "Use time zone" field. The "Time zone" input field becomes active. Enter your time zone in the "Time zone"...
Page 49 The virtual keyboard is configured in the file "slguiconfig.ini". Procedure 1. Copy the "slguiconfig.ini" file from the folder /siemens/sinumerik/hmi/template/cfg. 2. Paste the copy of the file into the following directory: /oem/sinumerik/hmi/cfg or /user/sinumerik/hmi/cfg. 3. Open the file in the editor.
Page 50 General settings 3.9 Setting the screensaver Changing the skin design Displaying the machine data You can change the skin design via the following item of machine data. MD9112 $MM_HMI_SKIN Skin design The number of the skin is indicated Skin 0 (traditional) Skin 1 (SINUMERIK Operate Generation 2) After changing the machine data, the operating software must be restarted.
Page 51 3.11 Access levels 3.10 Inserting a user-specific run up screen OEM-specific run up screen You can replace the Siemens run up screen by your own run up screen. Procedure: 1. Call your own run up screen "splash.png". Note The file name must not contain any lower case letters.
Page 52 General settings 3.11 Access levels Password security Note Assigning secure passwords Observe the following rules when creating new passwords: ● When creating new passwords, never choose passwords that can be easily guessed, e.g. simple words, sequences of consecutive keys on the keyboard, etc. ●...
Page 53 General settings 3.11 Access levels Setting the password Select the "Start-up" operating area. Press the "Password" softkey. Press the "Set password" softkey. The "Set Password" window opens. Enter one of the possible default passwords and press the "OK" soft‐ key to confirm the entry. A permissible password is set and the valid access level is displayed.
Page 54 General settings 3.11 Access levels Note Access authorization is not automatically deleted at POWER ON. 3.11.3 Access levels for programs Objective Access levels can be allocated to protect information; they can also be used to prevent unauthorized operation or deliberate damage to the control system or machine. With access authorization levels to files and directories, it can be defined as to which users are authorized to execute which operations on a directory or a file in a file system.
Page 55 Settings in the slfsfileattributes.ini file The slfsfileattributes.ini file is available as a template in the following directory: ../siemens/sinumerik/hmi/template/cfg The values from 0 ... 7 correspond to the access levels that, for example, also apply to the password. The 4-digit numbers designate the sequence according to the following rights:...
Page 56 General settings 3.11 Access levels All entries are in the section [ACCESSMASKS] and have the following form: [ACCESSMASKS] \wks.dir\*.wpd\*.mpf = 7777 \mpf.dir\*.mpf = 6577 \cus.dir\*.spf = 6577 See also Definition of access levels (Page 37) 3.11.4 Access rights for files Changing access rights Access rights for execution, writing, listing and reading are displayed in the "Properties"...
Page 57 General settings 3.11 Access levels 3.11.5 Access levels for softkeys The display and operation of softkeys can be suppressed by both the manufacturer as well as the user. This allows the operating software to be specifically adapted to the required functional scope and therefore be configured as transparently as possible.
Page 58 General settings 3.11 Access levels softkey is deactivated as long as no softkeys have been allocated new access levels: This setting remains effective until the system is rebooted. Note Applicability of modified access levels for softkeys The setting of specific access levels for softkeys on a PCU has an exclusive effect on the respective PCU softkeys themselves.
Page 59 General settings 3.11 Access levels 3. Place the mouse cursor on a softkey and using the right-hand mouse key call the context menu "Define access level", in order to define a new access level for this softkey. – The displayed access level is the default setting. –...
Page 60 General settings 3.12 Program selection 3.12 Program selection 3.12.1 Displaying the softkey The softkeys on the user interface for calling the program lists are activated via general configuration machine data. Configuring a softkey MD51041 $MNS_ENABLE_PROGLIST_USER No softkey The "Prog. list" softkey is displayed MD51043 $MNS_ENABLE_PROGLIST_MANUFACT No softkey The "MANUFACTURER"...
Page 61 General settings 3.12 Program selection Select the "Program manager" operating area if you have the authoriza‐ tion for access level 3 (password: User). Press the menu forward key and the "Prog. list" softkey. The "Program List" window opens. Press the "Manufacturer" softkey if you want to create a program list that can be used for all machines of a certain series.
Page 62 General settings 3.13 Activate and configure the Sidescreen window 3.13 Activate and configure the Sidescreen window 3.13.1 Activate Sidescreen In addition to SINUMERIK Operate, Multitouch Panels with widescreen displays offer the option of using the additional area at the side of the screen for displaying Sidescreen windows. The Sidescreen windows give you a quick and permanent view of important information and enable you to operate virtual keys for quick selection.
Page 63 Not only the standard windows but also the window for an ABC keyboard can be displayed in the Sidescreen display of the Multitouch panel. Procedure 1. Copy the sample file "slsidescreen.ini" from the directory /siemens/sinumerik/hmi/template/sidescreen 2. Place the copy of the file in one of the following directories: /oem/sinumerik/hmi/cfg or /user/sinumerik/hmi/cfg...
Page 64 The example of a machine control panel is displayed by the following procedure: Procedure 1. Copy the sample files "slsidescreenmcppageconfig.xml", "slsidescreenmcppage_eng.ts" and the subdirectories of the icon files from the directory /siemens/sinumerik/hmi/template/sidescreen/mcp/ The icon files are stored in the following subdirectories: /ico1024 for HD Ready /ico1920 for Full HD 2.
Page 65 General settings 3.13 Activate and configure the Sidescreen window 7. Open the copy of the file "slsidescreen.ini", and delete the comment sign ";" in front of the keyword PAGE003. Note The values of the attributes name and implementation must not be changed. 8.
Page 66 General settings 3.13 Activate and configure the Sidescreen window Description A key group combines two keys under one header. <buttonGroup spacing="false" The property enables the display type of spacing title="COOLANT"> the keys to be determined: together "false" or separate "true". The de‐ fault is separate.
Page 67 General settings 3.13 Activate and configure the Sidescreen window /user/sinumerik/hmi/ico Depending on the screen resolution, under the following subdirectories: /ico1024 for HD Ready /ico1920 for Full HD Note The icon file names must be the same as the names used in the XML file, e.g. icon="slsidescreenmcp_cooling.png".
Page 68 General settings 3.14 Display Manager Example extract of the file "slsidescreenmcppage_eng.ts" <message> <source>ON</source> <translation>EIN</translation> <chars>8</chars> </message> 3.14 Display Manager 3.14.1 Display configurations Using the Display Manager and display configurations, it is possible to reduce SINUMERIK Operate, in other words, run in less than full-screen mode, and to allocate the vacant space to other applications.
Page 69 General settings 3.14 Display Manager Activation To activate the Display Manager, the following display machine data must be set. MD9114 $MM_SIDESCREEN SINUMERIK Operate Sidescreen Enables the Sidescreen display area in HD Ready. Releases the Display Manager in Full HD. The default configurations used by the Display Manager for the two screen resolutions, 1920x1080 and 1366x768, are in the two files: ●...
Page 70 General settings 3.14 Display Manager 3.14.2.2 Frames A frame is a container for applications or menus and primarily describes the desired position and size of the application and menus in pixels. In addition, this is also where the application or menu that should be displayed in the frame after the Display Manager starts is specified. The applications that can be assigned to the frames are specified in the systemconfiguration.ini file.
Page 71 General settings 3.14 Display Manager ● 1854x1080 ● 1920x1080 Property Meaning Name of the frame. Used in the frame list of the displays, for example name Absolute position (x, y), width and height of the frame in pixels x, y, width, height Application displayed in the frame the first time the frame is displayed.
Page 72 General settings 3.14 Display Manager 3.14.2.3 Menus In addition to applications, menus can also be displayed in the frames of a display. These menus are typically used to display certain applications in another frame or to switch displays. A menu configuration consists of four parts: ●...
Page 73 General settings 3.14 Display Manager Property Meaning Access level from which the menu item is displayed: accessLevel System, Manufacturer, Service, Customer, Key_3, Key_2, Key_1, Key_0 or numerical equivalent (0-7) Default: Key_0 (7) Style of the menu item that defines all visual properties of the menu item. menuItemStyle Note All of the properties described below can be specified for configuring the...
Page 74 General settings 3.14 Display Manager Property Meaning Color of the menu item text in the pressed state of the menu item pressedTextColor See paragraph "Color definitions". Default: Qt::white Width of the border of the menu item in pixels borderWidth Default: 1. Color of the border of the menu item borderColor See paragraph "Color definitions".
Page 75 General settings 3.14 Display Manager Description of MenuItemStyle properties: See above. Example 2 [menuitemstyles] MENUITEMSTYLE001= name:=misMenu, textSize:=10, textAlignment:=bottom, imageAlignment:=top, color:=37/53/63, textColor:=153/173/185, pressedColor:=52/87/140, pressedTextColor:=White, borderColor:=37/53/63, pressedBorderColor:=52/87/140, borderWidth:=5, height:=66, width:=66 For unspecified properties, the corresponding default values (see above) take effect. In the [menus] section, one or more menuItems are combined into a menu. This is done using the menuItems property, which contains a list of the menu items (buttons/buttons) to be displayed in a certain menu.
Page 76 General settings 3.14 Display Manager Property Meaning Alignment of menu items: layout "row", "col" or "grid". With a "row" or "col" layout, the menu items are aligned horizontally in a row or vertically in a column. With a "grid" layout, the menu items are arranged in a grid. Default: "row"...
Page 77 General settings 3.14 Display Manager FRAME003= name:=frame3, x:=0, y:=970, width:=460, height:=110, menu:=menu2 SINUMERIK Operate (IM9) Commissioning Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 78 General settings 3.14 Display Manager 3.14.2.4 Menu actions The actions to be performed when a menu item is pressed are defined in the onClicked property of the menu items. This property can include one or more command statements (separated by semicolons), which are executed one after the other. The following commands are available: Command Meaning...
Page 79 General settings 3.14 Display Manager Command Meaning Enables (true) or disables (false) mirror mode setMirrorMode(true|false) When mirror mode is enabled, the frames of all displays in which mirror mode has not been disabled with enableMirrorMode(false) are mirrored horizontal‐ ly. In other words, frames that were previously displayed on the left are now displayed on the right and vice versa.
Page 80 Type B applications are handled like OEM frame applications and are therefore declared in the [processes] section. In addition, the nPlacementMode parameter must be set to 3 for the applications in the C:\Program Files (x86)\Siemens\MotionControl\compat\user\OEMFRAME.INI file. The following applications are included in the standard version: ●...
Page 81 General settings 3.14 Display Manager The document to be displayed is specified in the "cmdline" parameter. The two parameters have the following meaning: ● pdfFile: File to be displayed in the PDF Viewer. The file can be in the appl or hlp directories. ●...
Page 82 General settings 3.14 Display Manager process:=SlHmiHost1, preload:=false, cmdline:="-settingsFile sldm_keyboard.ini" The application name to be used for configuration within a display configuration: SlKeyboardApp The application may only be used in one instance within a display configuration. In the standard version, three sizes are pre-configured for the virtual keyboard (see file sldm_1920x1080.ini): [760x505] Num= KeyboardLayout:="numpadlayout", x:=430, y:=270...
Page 83 General settings 3.14 Display Manager The application name to be used for configuration within a display configuration: SlMcpApp The application may only be used in one instance within a display configuration. Application for displaying widgets Configuration in the standard version: [dialogs] DLG110= name:=SlWidgetsApp, implementation:=sldmsidescreenapp.SlSideScreenDialog,...
Page 84 General settings 3.14 Display Manager ● 1440x1080 ● 1454x1080 ● 1854x1014 ● 1854x1080 ● 1920x1080 Example of Type B applications Configuration in the systemconfiguration.ini file with the notepad.exe application as an example: [processes] PROC500=process:=Notepad, image:=notepad, cmdline:="C:\Windows \system32\notepad.exe", oemframe:=true, windowname:="Unknown - Editor", classname:="Notepad", processaffinitymask:=0xFFFFFFFF, deferred:=true The application name to be used for configuration within a display configuration:...
Page 85 General settings 3.14 Display Manager Entry Meaning Language-dependent texts can be used in the same way as with SINU‐ textfile MERIK Operate. One or more text files can be specified. In addition to specifying the text context for configuration of the menus textcontext or the menu items, a global text context can be specified here, which then applies to the language-dependent texts of all menu items.
Page 86 General settings 3.14 Display Manager SINUMERIK Operate (IM9) Commissioning Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 87 Press the "Licenses" softkey. The "Licensing" window opens. The general data for control and licenses is displayed. License database You purchase licenses via the Web License Manager in the Internet, administered by Siemens Industry. SINUMERIK Operate (IM9) Commissioning Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 88 Licensing 4.1 Determining the license requirement References For a detailed description, please refer to the following documentation: CNC Commissioning Manual: NCK, PLC, drive; Chapter "Licensing" Deactivate options When importing old archives from other HMI systems, it can occur that options are set which are no longer required in the actual system –...
Page 89 Licensing 4.1 Determining the license requirement To activate new selected options, press the "Reset (po)" softkey. A safety prompt appears. For several options, you will have to also restart SINUMERIK Operate. Corresponding prompts will appear in the user response line. Press the "OK"...
Page 90 Licensing 4.2 Activating the test license Activating the test license If you wish to use options without any restrictions – and without purchasing a license – you can activate these for a limited time using the test license. Six test license periods are available. The first test license period has a longer operating time.
Page 91 Licensing 4.4 Reading in the license key Note Interruption of the test license A test license period is interrupted in the following cases: ● If no axis is operated actively, e.g. during simulation mode. ● If a new valid license key is entered. ●...
Page 92 Licensing 4.5 Backing up the license of a new CompactFlash card. Procedure The "Licensing" window is open. Enter license key manually If you obtained the license key via the Web License Manager, enter the license key manually in the field "You can enter a new license key here". Press the <INPUT>...
Page 93 Licensing 4.5 Backing up the license of a new CompactFlash card. 6. Copy the license key, renamed keys.txt, back to directory cards/keys/sinumerik. 7. Insert the CompactFlash card into the control again. After the control has been powered up again, the license key will be installed from the file keys.txt onto the system and be activated.
Page 94 Licensing 4.5 Backing up the license of a new CompactFlash card. SINUMERIK Operate (IM9) Commissioning Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 95 Creating drive connections Up to 21 connections to so-called logical drives (data carriers) can be configured. These drives can be accessed in the "Program manager" and "Startup" operating areas. The following logical drives can be set up: ● USB interface ●...
Page 96 Creating drive connections 5.3 Setting the EES General information Note We do not recommend that a USB front interface is permitted for part program execution using EES if a system has several local USB front interfaces (several TCUs, the use of a HT8, etc.). The connection to the USB FlashDrive can be interrupted as a result of the TCU switchover.
Page 97 Creating drive connections 5.4 Creating a global part program memory Activating the function Software option To use this function together with the user memory (100 MB) on the CompactFlash Card, you require the software option "CNC extended user memory." If you use a PCU with this option, the entire memory area of the storage medium is at your disposal, e.g.
Page 98 Creating drive connections 5.4 Creating a global part program memory Possible procedure 1. Declare the global part program memory in the "Creating drives" window 2. Shift the content of the local program memory with SPF, MPF and WCS directory to an external drive, e.g.
Page 99 Channel menu Configuring a channel menu The channel menu is activated for display via the channel switchover key. The channel menu is used to switchover the NC channel displayed in the SINUMERIK Operate or more precisely at the operator station. If a channel menu has been configured, when the channel switchover key is pressed, the channel menu for the channel switchover is displayed to make the appropriate operator action.
Page 100 Channel menu 6.3 General structure of the channel menu a channel menu, when pressing the channel switchover key, the NC channels must be scrolled through consecutively until the desired NC channel has been selected. An operator station can only be switched over across NCUs using the channel menu. Constraints ●...
Page 101 Channel menu 6.4 Defining channel groups in the "netnames.ini" file Note In a system, for example, a channel group can correspond to a machining station, the channels contained in it, machining units. Up to 32 channel groups each with up to 8 channels can be configured in a channel menu. Configuring the total structure For a system, the total structure of the channel menu is configured in the "netnames.ini"...
Page 102 Channel menu 6.5 Configuring operating stations in the "config.ini" file "netnames.ini" file A channel group, e.g. channel group 1 is therefore specified as follows: [CH_GRP_1] Name of the channel group; the notation must follow this scheme. The groups are consecutively numbered at the last position.
Page 103 ● A PCU with SINUMERIK Operate can be connected to a maximum of four NCUs. ● SINUMERIK Operate must be switched off on all NCUs. ● The following configuration files must be adapted: siemens/sinumerik/hmi/template/cfg/netnames.ini siemens/sinumerik/hmi/template/cfg/mmc.ini This is illustrated in the following sections using an example with 1 PCU and 2 NCUs.
Page 104 Channel menu 6.6 Example: Settings for 1:N [NCU840D_2] ADDRESS0=192.168.214.2,LINE=14,NAME=/NC,SAP=040d, PROFILE=CLT1__CP_L4_INT ADDRESS1=192.168.214.2,LINE=14,NAME=/PLC,SAP=0202, PROFILE=CLT1__CP_L4_INT ADDRESS2=192.168.214.2,LINE=14,NAME=/CP,SAP=0502, PROFILE=CLT1__CP_L4_INT ADDRESS10=192.168.214.2,LINE=14,NAME=/DRIVE_00_000,SAP=0201, SUBNET=0000-00000000:000,PROFILE=CLT1__CP_L4_INT ADDRESS11=192.168.214.2,LINE=14,NAME=/DRIVE_03_003,SAP=0900, PROFILE=CLT1__CP_L4_INT Example netnames.ini ;****************************************************************** netnames.ini - EXAMPLE - ; This is an example of a netnames.ini for 1:N NCU-switching in ; a configuration of 3 NCU and a PCU50. ;******************************************************************* [own] owner = HMI...
Page 105 Channel menu 6.7 Distribution via job lists in the case of 1:N Text = 2. NCU Member1.Target = 192.168.214.241.192.168.214.2.#1 Member1.Text = NCU2%nKanal 1 Member2.Target = 192.168.214.241.192.168.214.2.#2 Member2.Text = NCU2%nKanal 2 Note For switching over an MCP with the operating software, the PLC block FB9 must not be used (FB9 must not be active).
Page 106 Channel menu 6.7 Distribution via job lists in the case of 1:N ; Select B.MPF on NCU2 in channel 2. SELECT B.MPF ch=NCU2,2 Sequence: 1. If a distributed job list is active during the selection, all distributed programs on the NCU are deleted without confirmation.
Page 107 Channel menu 6.7 Distribution via job lists in the case of 1:N Restrictions: ● In the event of changes of distributed programs on the local drive using the Editor, it should be noted that only the channel states are monitored on the NCU currently connected. If the program is still interrupted or active on another NCU, it cannot be correctly distributed after the change.
Page 108 Channel menu 6.7 Distribution via job lists in the case of 1:N SINUMERIK Operate (IM9) Commissioning Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 109 Machine and setting data Machine and setting data Overview Prefix Number ranges Machine/setting data Storage in range (softkey) 9000 - 9999 Display machine data Display MD $MNS 51000 - 51299 General configuration machine data General MD 51300 - 51999 General cycle machine data $MCS 52000 - 52299 Channel-specific configuration machine data...
Page 110 Machine and setting data 7.2 Displaying/editing machine data ● I/O component parameters: Drive parameters ● Communication parameters (CULINK, DMC): Drive parameters Note The display of the machine data / drive parameters depends on the configuration of your control. Access authorization to the machine data operating area can be controlled by keyswitch position or password.
Page 111 Machine and setting data 7.2 Displaying/editing machine data Procedure Select the "Start-up" operating area. Press the "Mach. data" softkey. Additional softkeys for the individual ma‐ chine data areas are displayed. Press the "General MD", "Channel MD", or "Axis MD" softkey. The window opens and the selected machine data is displayed.
Page 112 Machine and setting data 7.4 Displaying/editing setting data Press the "OK" softkey to save the setting. - OR - Press the "Cancel" softkey to reject the settings. Displaying/editing display machine data You can access the display machine data via the user interface in the "Start-up" operating area.
Page 113 Machine and setting data 7.4 Displaying/editing setting data Procedure Select the "Start-up" operating area. Press the "Mach. data" softkey. Press the menu forward key. The softkeys "General SD", "Channel SD", and "Axis SD" are displayed. Press the relevant softkey to display a particular setting data area. The window opens and the selected setting data is displayed.
Page 114 Machine and setting data 7.5 Displaying/editing drive parameters Axis/channel selection If several components are available for the area selected (e.g. "Axis SD" or "Channel SD"), you can choose from the following options: Press the "Axis +" or "Axis -" or "Channel +" or "Channel -" softkey. The values of the next (+) and the previous axis/channel (-) are displayed.
Page 115 Machine and setting data 7.5 Displaying/editing drive parameters Procedure Select the "Start-up" operating area. Press the "Mach. data" softkey. The "Control unit parameters", "Supply MD" and "Drive MD" softkeys are displayed. Press the softkey of an area to show its parameters. Place the cursor on the desired parameter.
Page 116 Hiding the expanded softkey bar The "Extended reset" softkey is defined in the "slsuconfig.ini" file. If the softkey is not to be displayed, proceed as follows: 1. Copy the "slsuconfig.ini" file from the /siemens/sinumerik/hmi/template/cfg/ directory. 2. Insert the file into the following directory: /user/sinumerik/hmi/cfg/ 3.
Page 117 Machine and setting data 7.6 Machine data display options Only display axes that are used If this checkbox is activated, axes that are not used are hidden when scrolling. Indices from ... to The index filter refers to the machine data arrays. On the display, this machine data can be identified by the field index attached to the machine data string.
Page 118 Machine and setting data 7.7 Editing machine data and drive parameters Select the required filter options (according to display groups, indices or expert parameters) by activating the checkboxes. Press the "Select all" softkey to activate all display groups. - OR - Press the "Deselect all"...
Page 119 Machine and setting data 7.7 Editing machine data and drive parameters 7.7.2 Editing BICO values You can use the BICO editor to enter BICO values for drive parameters. Note BICO values can also be entered by copying and inserting or also directly entered the field. Procedure Select the "Start-up"...
Page 120 Machine and setting data 7.8 Searching for data Procedure Select the "Start-up" operating area. Press the "Mach. data" softkey. Select the desired drive parameter area, e.g. "Control unit MD". Select the desired parameter, e.g. "p3" and position the cursor at the entry to be changed, e.g.
Page 121 Machine and setting data 7.8 Searching for data Searched fields A search is made in the following fields of the machine data for the character string that has been entered if the "Additionally search in the explanation texts" option is not set: ●...
Page 122 Machine and setting data 7.9 Managing data Managing data Overview The "Manage data" function is used to simplify the commissioning and permits the transfer, backup, loading and comparing of machine, setting, compensation and drive data at the file level. The files are saved in the .tea ASCII format. The "Manage data"...
Page 123 Machine and setting data 7.9 Managing data Transfer data within the controller Position the cursor on a controller object and confirm with "OK". In the window that opens, select the target controller object and confirm with "OK". Save data to a file Position the cursor on a controller object and confirm with "OK".
Page 124 Machine and setting data 7.10 User views 7.10 User views In the "User Views" window you can create and adapt all machine data relevant to a particular functionality. Machine data is individually collated to simplify the user's task. You can include additional comments when creating and/or editing user views. Note Importing user views (compatibility) If you have already created user views in HMI-Advanced, copy the *.klb files to /user/sinumerik/...
Page 125 Machine and setting data 7.10 User views 7.10.1 Creating a user view Procedure Select the "Start-up" operating area and press the "Mach. data" softkey. Press the softkeys "User views", "Manage view" and "New view". The "New View" window opens. Enter the desired view name. Press the "OK"...
Page 126 Machine and setting data 7.10 User views Press the "Back" softkey to close the list box and return to the user view you want to edit. Your entries are automatically stored. Press the "Insert text" softkey to insert any text in the open user view. The "Insert Text"...
Page 127 Machine and setting data 7.10 User views Press the "Edit view” softkey. Additional softkeys to edit the user view are listed. Press the "Insert data" softkey if you wish to enter another data item. Select a machine data item with the cursor keys. Press the "Up"...
Page 128 Machine and setting data 7.11 Plain texts for machine and setting data 7.10.3 Deleting a user view Procedure Select the "Start-up" operating area. press the "Machine data" softkey. Press the "User views" softkey. Press the "Manage view” softkey. Select the desired view from the selection list. Press the "Delete view"...
Page 129 Machine and setting data 7.11 Plain texts for machine and setting data Files File Machine/setting data nctea_xxx.txt General machine/setting data chtea_xxx.txt Channel-specific machine/setting data axtea_xxx.txt Axis-specific machine/setting data hmitea_xxx.txt Display machine data For "xxx" the specified language code must be used, e.g. "deu" for German, "eng" for English, etc.
Page 130 Machine and setting data 7.11 Plain texts for machine and setting data Result in the display The plain text is displayed in the table or in the diagnostics line in the operating area "Startup", "General MD". Machine data Text 14510 My integer text for PLC_MD 14510 14510[1] My integer text for MD 14510[1]...
Page 131 Number of actual values with a larger font (default setting) Inserting a user-specific logo For the traditional SINUMERIK Operate display, the Siemens logo is visible in the "Machine" operating area in the header. For the SINUMERIK Operate display of the second generation, the Siemens logo is permanently displayed in the header.
Page 132 Customizing the "Machine" operating area 8.2 Inserting a user-specific logo You can replace the Siemens logo with your own logo. OEM-specific logo in traditional display Procedure: 1. Name your own logo "logo.png". Note The file name must not contain any lower case letters.
Page 133 Configuring G-code groups Section Meaning Selected G groups This area is intended for operation of the controller in Siemens mode. Selected G groups ISO This area is intended for operation of the controller in ISO mode. mode Enter the G-code group and position as follows: SelectedGGroupN = M Position where G-code group M will be displayed.
Page 134 As soon as the file is located in the user-specific directory, the entries for this file take precedence over the Siemens file. If an entry is missing in a user-specific file, the corresponding entry from the Siemens file is used instead.
Page 135 /Ico800 17 x 17 /Ico1024 27 x 27 2. Copy the sample file "slmahdconfig.ini" from the directory /siemens/sinumerik/hmi/template/cfg. 3. Place the file in the following directory: /oem/sinumerik/hmi/cfg or /user/sinumerik/hmi/cfg 4. Open the file and make the required settings: – Specify an individual icon by changing the file name of the icon for channel operational messages.
Page 136 Customizing the "Machine" operating area 8.5 Deactivating program test condstop.png ; Emergency stop active condstop.png ; Alarm with stop active condstop.png ; M0/M1 active condstop.png ; Block in SBL mode terminated condstop.png ; NC stop active condstop.png ; Read-in enable missing condstop.png ;...
Page 137 Customizing the "Machine" operating area 8.7 Activating the "Teach In" function The test option is described in the following documentation: References Function Manual, Basic Functions, Mode Group, Channel, Program Operation, Reset Behavior (K1) Display STAT and TU Display STAT and TU in the "WCS" window If you want to display the joint position of the machine and the position of the rotary axes in the "Machine"...
Page 138 Customizing the "Machine" operating area 8.7 Activating the "Teach In" function Settings MD51034 $MNS_TEACH_MODE Bit 0 = 1 The "Progr. teach in" softkey is displayed. The approached position is taken into the program with the "Accept" softkey. (default) Bit 1 = 1 The acceptance of the teach-in block can be blocked by the PLC.
Page 139 Customizing the "Machine" operating area 8.8 Block search Accept STAT and TU If you want to import the joint position of the machine and the position of the rotary axes into the traversing block for Teach In for Cartesian PTP traversing, click on the checkboxes STAT and TU in the "Settings"...
Page 140 Customizing the "Machine" operating area 8.8 Block search Bit 1 = 1 Block search with calculation, with approach Notice: In a ShopMill/ShopTurn program, the search is performed only on G code-blocks. Bit 3 = 1 Skip EXTCALL programs Bit 5 = 1 Block search with test run MD52212 $MCS_FUNCTION_MASK_TECH General function screen for all technolo‐...
Page 141 Customizing the "Machine" operating area 8.9 Multi-channel support 8.8.2 Accelerated block search for execution from external The accelerated block search function allows you to run the part program forward until you reach the block you require. Settings If you activate the "Skip EXCALL" function, then you must set the following general configuration machine data: MD51028 $MNS_BLOCK_SEARCH_MODE_MASK Bit mask for the available search modes...
Page 142 Customizing the "Machine" operating area 8.9 Multi-channel support Precondition ● Multi-channel data only involve machines where the first technology is turning. ● For multi-channel machine, the following data must be the same for all channels: – Measurement unit – Work offset (e.g. G54) –...
Page 143 Customizing the "Machine" operating area 8.10 Manual machine Only programming G code programs If the job list only contains G code programs, then you can deactivate the "multi-channel data" function. To do this, set the following machine data: MD51228 $MNS_FUNCTION_MASK_TECH Cross-technology function mask Bit 0 G code programming without multi-channel data...
Page 144 Customizing the "Machine" operating area 8.10 Manual machine Bit 5 Enable spindle control, tool spindle = 0 via the NC/PLC interface = 1 via the user interface SD43200 $SA_SPIND_S Speed for spindle start using NC/PLC interface signal; value outputs using the operating software SD43202 $SA_SPIND_CONSTCUT_S Cutting speed for spindle start using...
Page 145 Customizing the "Machine" operating area 8.11 User status display (OEM) Feedrate SD42600 $SC_JOG_FEED_PER_REV_SOURCE = -3 Revolutional feedrate control in JOG mode SD43300 $SA_ASSIGN_FEED_PER_REV_SOURCE [X ax‐ Revolutional feedrate for positioning is] = -3 axis X SD43300 $SA_ASSIGN_FEED_PER_REV_SOURCE [Z ax‐ Revolutional feedrate for positioning is] = -3 axis Z Note...
Page 146 Customizing the "Machine" operating area 8.11 User status display (OEM) Alternatively, you can use the following parameters for the definition: ● USER_ICON_BASE This means that 32 bits are available with UI_0 (highest bit) to UI_31 (lowest bit). Example: USER_ICON_BASE=DB80.DBB0 ⇒ UI_0 = DB80DBX3.0 and UI_31 = DB80.DBX0.7 ●...
Page 147 Customizing the "Machine" operating area 8.11 User status display (OEM) ● Combination thereof with a maximum total of 32 images for the maximum 16 positions (maximum of 16 active selection bits at any one time) ● More than 16 selection bits. Configuring OEM texts Machine manufacturers can display their own texts in the program directory and program name lines.
Page 148 Customizing the "Machine" operating area 8.13 Activate machining time recording Configuring OEM icons OEM icons indicating the machine state can be output in the field provided for the program control display (e.g. SBL, M01, etc.). If OEM icons are defined, the elements for the program control display are hidden.
Page 149 Customizing the "Machine" operating area 8.13 Activate machining time recording You will find additional information about making these settings in the following document: References Universal/Turning/Milling/Grinding Operating Manual ● Section "Machining a workpiece" > "Settings for Automatic mode mode" ● Section "Machining a workpiece" > "Editing a program" > "Settings for the editor" Switching on the time recording To use the function, the following channel machine data must be so set in all channels, even if the machining time recording is not activated for all channels:...
Page 150 Customizing the "Machine" operating area 8.13 Activate machining time recording SINUMERIK Operate (IM9) Commissioning Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 151 Simulation and simultaneous recording Simulation overview Software option You require the "3D simulation 1 (finished part)" option for the 3D representation of the simulation. Simulation is supported with its own program interpreter (SNCK) and a separate simulation- data environment in SINUMERIK Operate. The SNCK considers the complete syntax of the SINUMERIK control family, including the possibility of incorporating special user options on the machine by comparing data with the NC environment.
Page 152 Simulation and simultaneous recording 9.1 Simulation overview ● Compile cycles are supported only to a limited extent. ● Blank CAD data cannot be imported (for example, for castings). ● Couplings cannot be simulated (coupled motion, axial master-value coupling, electronic gearbox): –...
Page 153 Simulation and simultaneous recording 9.2 Setting the technology for simulation Setting the technology for simulation Turning technology Examples of machine kinematics: ● Conventional turning with two geometry axes ● Three spindles: Main spindle, counterspindle, tool spindle ● Counterspindle slides, tailstock as NC axis ●...
Page 154 Simulation and simultaneous recording 9.2 Setting the technology for simulation Auxiliary spindle (driven tool) Main spindle (turning) C axis of the main spindle (turning) Counterspindle (turning) C axis of the counterspindle (turning) Linear axis of the counterspindle (turning) Tailstock (turning) Back rest (turning) Note To prevent errors occurring, the same axis must be defined as main or counterspindle for all...
Page 155 Simulation and simultaneous recording 9.3 Simultaneous recording overview Simultaneous recording overview Software option You require the option "Simultaneous recording (real-time simulation)" for the "Simultaneous recording" function. Software option You require the "ShopMill/ShopTurn" option to display the tailstock Software option You require the "3D simulation 1 (finished part)" option for the 3D representation of the simultaneous recording function.
Page 156 Simulation and simultaneous recording 9.4 Clamping a blank Example: Activating the tailstock representation in the spindle chuck data Procedure: 1. Make the tailstock visible by making the selection in the program. 2. Specify the tailstock dimensions: Select in the operating area "Parameters" → "Setting data" → "Spindle chuck data", and enter the "ZR"...
Page 157 Simulation and simultaneous recording 9.4 Clamping a blank Requirements ● The machine has several clamping options available for selection. ● The machine has a clamping option that does not point in the Z direction as standard (e.g. a boring mill). Under the following circumstances, you can specify the position and orientation of the rotary axes in the machine data MD53220 and MD52207: ●...
Page 158 Simulation and simultaneous recording 9.4 Clamping a blank Function options In the program header, a blank can be optionally set to A, B, C and table clamping: Clamping View Machine data A axis MD52207 $MCS_AXIS_USAGE_ATTRIB bit 0 and bit 8 = 1 B axis MD52207 $MCS_AXIS_USAGE_ATTRIB bit 1 and bit 8 = 1...
Page 159 Simulation and simultaneous recording 9.4 Clamping a blank Example for the machine configuration Example for a machine configuration when the A axis should rotate at the X axis: MD20080 $MC_AXCONF_CHANAX_NAME_TAB[n] Channel axis name in channel [n] Spindle MD52207 $MCS_AXIS_USAGE_ATTRIB[4] Attribute of rotary axis A = 181H Bit 0 = 1 Rotates around 1st Geometry axis (for rotation axes)
Page 160 Simulation and simultaneous recording 9.4 Clamping a blank SINUMERIK Operate (IM9) Commissioning Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 161 Spindle functions 10.1 Spindle control You can select from the following spindle control settings: End of program The following M functions are used for the end of program: M function from Main program end Spindle continues MD10714 $MN_M_NO_FCT_EOP to run M2, M30 End of main program and return jump to Spindle stops...
Page 162 Spindle functions 10.2 Analog spindle Note If the spindle must be stopped when the program is running, then set the interface signal DB3x.DBX4.3, "Feed stop/spindle stop" in the user PLC. Additional settings: MD11450 $MN_SEARCH_RUN_MODE Search run parameterization Bit 1 = 1 Automatic ASUB start after output of the action blocks (see also MD11620 $MN_PROG_EVENT_NAME).
Page 163 Spindle functions 10.3 Spindle diagnostics In order that the operating software identifies the spindle as analog spindle, enter the axis index of the analog spindle in the following machine data: MD51068 $MNS_SPIND_DRIVELOAD_FROM_PLC1 Machine axis index spindle 1 Utilization display from the PLC Machine axis index of a spindle (analog) that draws the data for the utilization display in the T,F,S window from the PLC (DB19.DBB6).
Page 164 The "S1 Spindle Diagnostics" window opens. Note If several spindles are in operation, select the desired spindle using the "Spindle +" or "Spindle -" softkey. See also Tool change with hybrid spindle from the company Weiss (https:// support.industry.siemens.com/cs/ww/en/view/109475707) SINUMERIK Operate (IM9) Commissioning Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 165 Spindle functions 10.3 Spindle diagnostics 10.3.2 Temperatures Which temperatures are evaluated and displayed depends on the number and the mounting location (e.g. for sensor S6, bearing temperature front) of the sensors installed in the spindle. The motor temperature is not displayed when the temperature sensor sensor type parameter p0601 = 0 or 1.
Page 166 Spindle functions 10.3 Spindle diagnostics Signal Sensor Column/meaning Description Overtemperature protec‐ Actual When the overtemperature protec‐ tion tion responds, "Active" is displayed (in red). The value 250° C is dis‐ played in the "Actual" column as mo‐ tor temperature. Limit Stored threshold for motor overtem‐...
Page 167 Spindle functions 10.3 Spindle diagnostics 10.3.3 Motor temperature sensor Shutdown response The alarm and fault thresholds of the motor temperature sensor that are displayed on the user interface as limits, are stored in the SMI24. They are used for the statistical evaluation of the SMI24 and for the shutdown response of the drive.
Page 168 Spindle functions 10.3 Spindle diagnostics Alarms: ● 207017 = additional temperature alarm threshold violated ● 207018 = additional temperature fault threshold violated 10.3.5 Temperature histograms The motor temperature and optionally additional temperatures, such as bearing temperature or housing temperature, are displayed in a histogram. The color coding indicates the following temperature ranges: Color Meaning...
Page 169 Spindle functions 10.3 Spindle diagnostics Possible conclusions ● The speed histogram is an indication of the load on the bearings and rotary gland caused by the speed. ● The speed histogram is an indication of the load on the bearings caused by the stock removal forces.
Page 170 Spindle functions 10.3 Spindle diagnostics Signal Sensor Description Value Meaning State Clamping states Sensor S1 not available or state values inactive. The state initialization is in progress. Released with signal (error state) Released Clamping with tool Releasing with tool Releasing without tool Clamped with tool and S4 = 0 (No).
Page 171 Spindle functions 10.3 Spindle diagnostics 10.3.8 Clamping system: Speed limits For safety reasons and to protect the spindle, only maximum speeds are permitted for certain clamping states. The drive limits the spindle speed in the respective clamping state to the entered speed.
Page 172 Spindle functions 10.3 Spindle diagnostics 10.3.9 Clamping system: Diagnostic statistics This window displays the statistics for clamping operations and speed violations. Statistical data Meaning Number of correct clamping cycles Accumulated number of correct clamping cycles with or without tool. Correct clamping cycle means: "Released" clamping state [3] → "Clamped"...
Page 173 Spindle functions 10.3 Spindle diagnostics 10.3.10 Clamping system: Clamping time statistics This window displays the statistics for the determined clamping times. Statistical data Meaning Last determined clamping time Measured time for the last performed clamping operation. Definition of a clamping operation: "Released" clamping state [3] →...
Page 174 Spindle functions 10.3 Spindle diagnostics ● Serial number ● Date of manufacture ● Service date and service information (1...4): The service information corresponds to the reference number for the service report from the WEISS Spindeltechnologie GmbH company. SINUMERIK Operate (IM9) Commissioning Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 175 Drive system 11.1 Commissioning of drives Procedure Once commissioning of the PLC has been completed, you can carry out commissioning of the SINAMICS drives via the user interface of SINUMERIK Operate. Select the "Start-up" operating area. Press the "Drive system" softkey. The "Drive system overview"...
Page 176 Drive system 11.1 Commissioning of drives SINUMERIK Operate (IM9) Commissioning Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 177 Tool management 12.1 Machine data for tool management 12.1.1 Settings with/without magazine management Setting without magazine management Make the following settings if you are commissioning the tool management without NC magazine management: MD18080 $MN_MM_TOOL_MANAGEMENT_MASK Memory for the tool management is re‐ served step-by-step (SRAM).
Page 178 Tool management 12.1 Machine data for tool management Setting with magazine management Make the following settings if you are commissioning the tool management with NC magazine management: MD18080 $MN_MM_TOOL_MANAGEMENT_MASK Memory for the tool management is re‐ served step-by-step (SRAM). = 03H Bit 0 Provide tool management data.
Page 179 Tool management 12.1 Machine data for tool management MD51203 $MNS_ACCESS_WRITE_TM_SC Access level, write TM additive offsets. MD51204 $MNS_ACCESS_WRITE_TM_EC Access level, write TM operating off‐ sets. MD51205 $MNS_ACCESS_WRITE_TM_SUPVIS Access level, write TM monitoring data. MD51206 $MNS_ACCESS_WRITE_TM_ASSDNO Access level, write TM unique D num‐ ber.
Page 180 Tool management 12.1 Machine data for tool management 12.1.3 Additional settings Additional settings You can enable further functions on the user interface via the following machine data / setting data: MD52270 $MCS_TM_FUNCTION_MASK Bit 0 Creating a tool at the magazine location is not permitted. Bit 1 Load/unload lock if the machine is not in the reset state.
Page 181 Tool management 12.1 Machine data for tool management Bit 9 Diameter display for face axis - wear. The wear value of the transverse axis is displayed as a diameter value, if a transverse axis is defined in MD20100 $DIAMETER_AX_DEF and SD42940 $TOOL_LENGTH_CONST is set to 18 and SD42950 $TOOL_LENGTH_TYPE is set to 2.
Page 182 Tool management 12.1 Machine data for tool management Enabling the graphic tool and magazine display function Make the following settings when the tools and the magazine should be represented graphically: MD52271 $MCS_TM_MAG_PLACE_DISTANCE Distance between individual magazine lo‐ cations in the unit of measurement of the basic NC system.
Page 183 Tool management 12.2 Configuring the user interface Setting the manual tool function MD22562 $MC_TOOL_CHANGE_ERROR_MODE Response when errors occur at tool change. Bit 1 = 1 Manual tools can be loaded. Bit 2 = 1 Active D No. > 0 and active T No. = 0 generate an alarm message. Active D No.
Page 184 ● Configure the code carrier connection ● Configuring store to file The following sections explain how you configure these adaptations. Procedure 1. Open the directory: /siemens/sinumerik/hmi/template/cfg. 2. Copy the "oem_sltmlistconfig.xml" template file 3. Copy the file to the directory /oem/sinumerik/hmi/cfg OR: /user/sinumerik/hmi/cfg.
Page 185 Tool management 12.2 Configuring the user interface Enter your configuration using the following xml identifiers: Identifier <tag> for the following setting: General settings (Page 172) <SETTINGS> Configuring tool lists (Page 177) <LISTCONFIGURATION> Configuring list parameters (Page 191) <PARAMETERCONFIGURATION> Configure tool types (Page 197) <TOOLTYPECONFIGURATION>...
Page 186 Tool management 12.2 Configuring the user interface 12.2.1 General settings <SETTINGS> tag The general settings for the tool management user interface are stored in the <SETTINGS> tag. Entries Meaning ReactivateWithMagPos True - reactivate with positioning of the tool to the tool mag‐ azine loading point.
Page 187 Tool management 12.2 Configuring the user interface Entries Meaning NewToolFavoritesOnly Refers to the "New tool" function. True - only those tool types that are configured as favorites are listed. False - default setting, all tool types are listed. SortationInFirstEtcLevel True - the "Sorting" function is placed at the first softkey level.
Page 188 Tool management 12.2 Configuring the user interface Entries Meaning AdaptTransDataViewEnabled The magazine location adapter transformed display of the cutting edge parameters is enabled. It can be switched on and off in the settings dialog of the tool lists. False - default setting, the magazine location adapter trans‐ formed display of the cutting edge parameters is not ena‐...
Page 189 Tool management 12.2 Configuring the user interface Entries Meaning FixKindOfDistInMultiTools Multitools are created with a fixed type of clearance input of the multitool locations. There is no prompt when you create the multitool. Possible input value: 3 - clearance of the multitool locations as an angle.
Page 190 Tool management 12.2 Configuring the user interface Entries Meaning MagazineMoveMessage True - "Magazine movement running" or "Magazine move‐ ment ended" message is displayed. False - default setting, message is not displayed. ToolLoadErrorMessage Refers to the output of the fault message due to a negative PLC.
Page 191 Tool management 12.2 Configuring the user interface Entries Meaning ShowConflictPositionAndDirection Marking of a conflict; tool position and cutting direction do not match. True - default setting. ShowConflictActiveToolWarning Marking of a conflict; turret magazine type and the active tool are not at the the machining position. True - default setting.
Page 192 Tool management 12.2 Configuring the user interface Entry Meaning TOOLTYPE_ALL_XXX The column setting applies to all tool types of a group. XXX stands for the group number of the tool types. The hundreds position is used as the group number, for example, TOOLTYPE_ALL_100 or TOOL‐ TYPE_ALL_200 etc.
Page 193 Tool management 12.2 Configuring the user interface  <COLUMN10>  <TOOLTYPE_ALL>  <Item value="MagPlaceType" type="QString" /> </TOOLTYPE_ALL> </COLUMN10>  <COLUMN11>...
Page 194 Tool management 12.2 Configuring the user interface  <TOOLTYPE_ALL>  <Item value="ToolPlaceSpec" type="QString" /> </TOOLTYPE_ALL>  <TOOLTYPE_9997>  <Item value="MultiToolPlaceSpec"...
Page 195 Tool management 12.2 Configuring the user interface Result ● The "OEM Tool Data" window is displayed. It automatically displays the columns shown in the figure. ● The new "OEM tools" softkey appears and can be operated. 12.2.2.1 Tool parameter identifiers Tool parameters For the tool parameters, the following identifiers are used in the configuration file: Identifier...
Page 196 Tool management 12.2 Configuring the user interface Identifier Parameter or property System variable ToolInMagInPlace Magazine number/Magazine location $A_TOOLMN / $A_TOOL_MLN ToolMonTCW Type of tool monitoring, tool life, workpiece $TC_TP9 count and wear. If wear monitoring has not been enabled via the machine data, this parameter is handled like ToolMonTC.
Page 197 ToolUser_1, ... ToolUser_10 OEM tool parameters 1 to 10 $TC_TPC1, ... $TC_TPC10 ToolAppl_1, ... ToolAppl_10 Siemens application tool parameters 1 to 10 $TC_TPCS1, ... $TC_TPCS10 Parameter corresponds to the system variable or the system variable is the basis for this parameter. Note Tool name "ToolIdent"...
Page 198 Tool management 12.2 Configuring the user interface Identifier Parameter or property System variable GeoLengthGeoAx3 Length of geometry axis 3, cutting edge $TC_DP4 parameter 4, e.g. length Z GeoLengthGeoAx3DiscDiameter Grinding wheel diameter in geometry axis $TC_DP4 3, cutting edge parameter 4 GeoLengthGeoAx3DresserDiameter Dressing tool diameter in geometry axis 3, $TC_DP4...
Page 199 Tool management 12.2 Configuring the user interface Identifier Parameter or property System variable WearLengthGeoAx1 Wear length of geometry axis 1, cutting $TC_DP12 edge parameter 12, e.g. Δ length X WearLength Wear length, cutting edge parameter 12 $TC_DP12 WearLength2 Wear length 2, cutting edge parameter 13 $TC_DP13 WearLengthGeoAx3 Wear length of geometry axis 3, cutting $TC_DP13...
Page 200 OEM cutting edge parameters 1 to 10 $TC_DPC1, ... $TC_DPC10 EdgeAppl_1, ..., EdgeAppl_10x Siemens application cutting edge parame‐ $TC_DPCS1, ... ters 1 to 10 $TC_DPCS10 Parameter corresponds to the system variable or the system variable is the basis for this parameter.
Page 201 OEM cutting edge monitoring parameters 1 to 10 $TC_MOPC1, ... EdgeSupUser_10 $TC_MOPC10 EdgeSupAppl_1, ... Edge‐ Siemens application cutting edge monitoring pa‐ $TC_MOPCS1, ... SupAppl_10 rameters 1 to 10 $TC_MOPCS10 Parameter corresponds to the system variable or the system variable is the basis for this parameter.
Page 202 MagNoMagPlaceNo Magazine number/Magazine location number - MagPlaceUser_1, ... MagPla‐ OEM magazine location parameters 1 to 10 $TC_MPPC1, ... ceUser_10 $TC_MPPC10 MagPlaceAppl_1, ... MagPla‐ Siemens magazine location parameters 1 to $TC_MPPCS1, ... ceAppl_10 $TC_MPPCS10 SINUMERIK Operate (IM9) Commissioning Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 203 Tool management 12.2 Configuring the user interface Parameter corresponds to the system variable or the system variable is the basis for this parameter. 12.2.2.6 Magazine location adapter parameter identifiers The following identifiers are used in the configuration file for the magazine location adapter parameters: Identifier Parameter or property...
Page 204 MultiToolUser_1, ... MultiToolUs‐ OEM multitool parameters 1 to 10 $TC_MTPC1, ... er_10 $TC_MTPC10 MultiToolAppl_1, ... MultiToo‐ Siemens application multitool parameters $TC_MTPCS1, ... lAppl_10 1 to 10 $TC_MTPCS10 Parameter corresponds to the system variable or the system variable is the basis for this parameter.
Page 205 OEM multitool location parameters 1 to 10 $TC_MTPPC1, … tiToolPlaceUser_10 $TC_MTPPC10 MultiToolPlaceAppl_1, … Mul‐ Siemens application multitool location parame‐ $TC_MTPPCS1, … tiToolPlaceAppl_10 ters 1 to 10 $TC_MTPPCS10 Parameter corresponds to the system variable or the system variable is the basis for this parameter.
Page 206 Tool management 12.2 Configuring the user interface Multitool location parameter identifiers (Page 190) Entries Meaning HeadLine Column header. Text entered is displayed as a header. Example: Text "Radius" is displayed as a header (default). Tooltip Text that is displayed in the tooltip. Example: Text "Geometry radius"...
Page 207 Tool management 12.2 Configuring the user interface Entries Meaning UpperLimit Upper input limit for these parameters in the user interface. Only applies for numerically entered parameters. LowerLimit Lower input limit for these parameters in the user interface. Only applies for numerically entered parameters. Example In the following example, the <GeoRadius>...
Page 208 Tool management 12.2 Configuring the user interface Example 2 Entries Meaning Assign new cutting edge parameter name The name is "EdgeUser_1_Bit0" in the following example. Base Name of the parameter on which the new parameter is based. In the following example, the "EdgeUser_1" parameter is used as template. Also enter only the changed data here.
Page 209 Tool management 12.2 Configuring the user interface 12.2.4 List of tool types Coding of tool types for milling tools Group with type 1xy (milling tool): Milling tool according to CLDATA (DIN 66215) Ballhead cutter (cylindrical die milling tool) Ballhead cutter (tapered die milling tool) End mill (without corner rounding) End mill (with corner rounding) Angle head cutter (without corner rounding)
Page 210 Tool management 12.2 Configuring the user interface Coding of tool types for drills Group type 2xy (drills): Twist drill Solid drill Boring bar Center drill Countersink Counterbore Tap regular thread Tap fine thread Tap Whitworth thread Reamer Coding of tool types for grinding tools Group type 4xy (grinding tools): Grinding wheel circumference Face grinding wheel...
Page 211 Tool management 12.2 Configuring the user interface Coding of tool types for special tools Group type 7xy (special tools): Slotting saw 3D probe Edge probe Mono probe L probe Star probe Calibration tool Stop Spindle sleeves End support Auxiliary tools 12.2.5 Configure tool types <TOOLTYPECONFIGURATION>...
Page 212 Tool management 12.2 Configuring the user interface Entries Meaning Icon9 - for milling technology Icon representing the tool type. The icons are displayed in the following windows: ● "Tool List" in the "Type" column ● "New Tool - Favorites" in the "Tool position" column ●...
Page 213 Tool management 12.2 Configuring the user interface Example 2 <TOOLTYPECONFIGURATION> <DELETE_TOOLTYPE> <TOOLTYPE_110 /> </DELETE_TOOLTYPE> </TOOLTYPECONFIGURATION> 12.2.6 Configuring the "Additional Data" window <MOREDATACONFIGURATION> tag The entries used for configuring the "Additional Data" window are located in the <MOREDATACONFIGURATION> tag. Various data items can be displayed for each tool type in a number of rows and columns.
Page 214 Tool management 12.2 Configuring the user interface A brief description of the parameter (ShortText) then appears in the window with the value itself beside it. Configuring list parameters (Page 191). If another description text is required in the "More Data" window, a text can also be entered in a row or column.
Page 215 Tool management 12.2 Configuring the user interface Example 2 <MOREDATACONFIGURATION> <TOOLTYPE_ALL_500> <ROW1_COL1> <Item value="TM_DGL_LENGTH" type="QString" /> </ROW1_COL1> <ROW2_COL1> <Item value="GeoLengthGeoAx3" type="QString" /> </ROW2_COL1> </TOOLTYPE_ALL_500> <WITHOUT_MORE_DATA> <TOOLTYPE_580 /> </WITHOUT_MORE_DATA> </MOREDATACONFIGURATION> 12.2.7 Configure the "New tool - favorites" window <NEWTOOLFAVORITECONFIGURATION> tag In the tag <NEWTOOLFAVORITECONFIGURATION> you define the tool types that are most frequently used.
Page 216 Tool management 12.2 Configuring the user interface 12.2.8 Configuring the "New Tool" window <NEWTOOLCONFIGURATION> tag You use the "New Tool" dialog to supply a new tool with specific tool data before creating the tool or before loading the tool to a magazine location. These are typically the tool size and/or the tool location type because these parameters can no longer be changed when the tool is loaded.
Page 217 Tool management 12.2 Configuring the user interface In the <NEWMULTITOOLCONFIGURATION>tag, specify the parameters that you wish to have displayed in the "New Multitool" dialog. Entries Meaning ItemX Entry of the identifier of the multitool parameter. "X" specifies the order in which the parameters will be displayed in the window.
Page 218 Tool management 12.2 Configuring the user interface 12.2.12 Configuring default values for new tools <NEWTOOLDEFAULTVALUECONFIGURATION> tag In the <NEWTOOLDEFAULTVALUECONFIGURATION> tag, you can specify default values for tools that you create via the user interface. These values can be configured depending on the tool type and, if required, also depending on the cutting edge position: Entries Meaning...
Page 219 Tool management 12.2 Configuring the user interface <CUTTEDGEPOS_3> <Default value="93.0" type="double" /> </CUTTEDGEPOS_3> <CUTTEDGEPOS_4> <Default value="93.0" type="double" /> </CUTTEDGEPOS_4> <CUTTEDGEPOS_5> <Default value="49.0" type="double" /> </CUTTEDGEPOS_5> <CUTTEDGEPOS_6> <Default value="49.0" type="double" /> </CUTTEDGEPOS_6> <CUTTEDGEPOS_7> <Default value="49.0" type="double" /> </CUTTEDGEPOS_7> <CUTTEDGEPOS_8> <Default value="49.0" type="double" /> </CUTTEDGEPOS_8>...
Page 220 Tool management 12.2 Configuring the user interface The following combinations between the cutting-edge position and the cutting direction result dependent on the tool type. When creating the new tool, the operator selects a combination in the "New Tool - Favorites" window. Tool type $TC_DP1 Default values Cutting edge $TC_DP2...
Page 221 Tool management 12.2 Configuring the user interface Tool type $TC_DP1 Default value $TC_DP25 Direction of spindle rotation Type 730/731/732 Bit 8 = 0 Spindle stop Bit 9 = 0 All other tool types Bit 8 = 1 Spindle right Bit 9 = 0 Tool type $TC_DP1 Default value $TC_DP25 for switching direction Type 712 mono probe...
Page 222 Tool management 12.2 Configuring the user interface 12.2.13 Configuring the "Details" window <DETAILSCONFIGURATION> tag In the tag <DETAILSCONFIGURATION>, you can make the settings for the "Detail" window: Entries Meaning ShowToolNumber The tool number is displayed in the upper right field of the "Detail" window. UseAxisNameInLength The tool length is displayed with axis identifiers, for example, Length X instead of Length 1.
Page 223 Tool management 12.2 Configuring the user interface <PLACE_2> <Name value="TM_SPECIAL_MAG_PLACE_1" type="QString" /> </PLACE_2> </MAGAZINE_9998> <MAGAZINE_1> <PLACE_3> <Name value="TM_SPECIAL_MAG_PLACE_2" type="QString" /> </PLACE_3> </MAGAZINE_1> </MAGAZINEPLACENAMECONFIGURATION> Name for a magazine Dedicated texts can also be allocated for magazines. The text or the text identifier is entered into the magazine configuration file (ini file) of the NC.
Page 224 Tool management 12.2 Configuring the user interface See also Please refer to the following section for the procedure to create language-dependent text: Creating OEM texts (Page 228) 12.2.15 Configuring the "Assign Tooltips for Multitool Locations" window <MULTITOOLPLACETOOLTIPCONFIGURATION> tag You will find the entries for assigning tooltips in the tag <MULTITOOLPLACETOOLTIPCONFIGURATION>.
Page 225 Tool management 12.2 Configuring the user interface 12.2.16 Assigning a name for magazine location types <PLACETYPECONFIGURATION> tag You can find entries to allocate your own location type identifiers in the tag <PLACETYPECONFIGURATION>. Magazines and magazine location types can be displayed with texts in the tool lists.
Page 226 Tool management 12.2 Configuring the user interface See also Please refer to the following section for the procedure to create language-dependent text: Creating OEM texts (Page 228) 12.2.17 Assignment of magazines and magazine locations to channels Requirement Turning technology or milling technology and technology extension turning have been set: Name of the associated configuration file sltmturninglistconfig.xml or sltmmillturnlistconfig.xml.
Page 227 Tool management 12.2 Configuring the user interface location which is assigned a channel via this configuration, then the tool icon is output depending on this position that has been set. This setting option is only available in turning technology and in milling technology with the technology extension milling.
Page 228 Tool management 12.2 Configuring the user interface Example 2 Magazine location 1 of the buffer will be assigned to channel 1. Magazine location 2 of the buffer will be assigned to channel 2. <CHANNELMAGAZINEASSIGNMENT> <CHANNELNO_1> <MAGAZINE_9998> <Places value="1" type="QString" /> </MAGAZINE_9998>...
Page 229 Tool management 12.2 Configuring the user interface Entries Meaning MAGAZINE_XXX Number of the magazine whose locations will be assigned to the coordinate system. Places Number of magazine locations that will be assigned to the coordinate system. Example The following assignment between magazines or magazine locations and coordinate systems is to apply: Magazine 1,3, and 4 Coordinate system 34...
Page 230 Tool management 12.2 Configuring the user interface Entries Meaning FirstEdge Filter "Only first cutting edge," default setting "Edges" StandBy Filter "Only tools that are ready to use," default setting "NewTool" Active Filter "Only tools with active code," default setting "NewTool" Locked Filter "Only disabled tools,"...
Page 231 Tool management 12.2 Configuring the user interface </MAGAZINE_2> </LOADSTATIONSHANDLEALLTOOLS> 12.2.21 Coolant and tool-specific functions Assigning coolant (ShopMill/ShopTurn) In the tool management of ShopMill/ShopTurn, you can assign coolant and tool-specific functions to each tool. These are activated when the tool is changed. You assign the coolant to the corresponding machine functions (M functions) using the following machine data: MD52230 $MCS_M_CODE_ALL_COOLANTS_OFF M code for all coolants OFF...
Page 232 Tool management 12.2 Configuring the user interface If M functions less than 100 are used, the number and sequence of the M commands has no significance. They are located in the user PLC in the decoded area (DB21.DBB194 to DB21.DBB206), independent of the number and the sequence when programming. However, if M functions from 100 and higher are used, then you must decode these yourself in the user PLC.
Page 233 Own comment - entry is not displayed at the user interface. Procedure 1. You can copy the sample file "oem_slstepforms_deu.ts" from the following directory: / siemens/sinumerik/hmi/template/lng 2. Save or create the file in the /oem/sinumerik/hmi/lng or /user/sinumerik/hmi/lng directory. 3. Change the file name to "slstepforms_deu.ts".
Page 234 Tool management 12.2 Configuring the user interface Example of a file "slstepforms_deu.ts" <?xml version="1.0" encoding="utf-8"?> <!DOCTYPE TS><TS> <context> <name>SlStepLabels</name> <message> <source>T_LAB_USER_MACHINE_FUNC_1</source> <translation>tool-specific function 1</translation> <chars>20</chars> </message> <context> <name>SlStepToolTip</name>  <message> <source>T_TT_USER_MACHINE_FUNC_1</source> <translation>User%nMachine functions 1</translation> <chars>25</chars>...
Page 235 Tool management 12.2 Configuring the user interface Text identifier Text TM_DGL_TYPE_REEQUIPPING Type reequipping TM_DGL_TOOL_TRIAL Tool trial TM_DGL_PREVENTIVE_CHANGE Preventive change <TOOLCHANGEREASON> tag You configure the function in the <TOOLCHANGEREASON> tag: Parameter Designation Enabled True - "Reason for tool change" selection window is displayed when reactivating.
Page 236 Tool management 12.2 Configuring the user interface Example 1 The following example uses the texts for the tool change reason, already prepared in the operating software. In this example, the tool change reason is stored in parameters that still have to be configured, e.g. the OEM tool data 1, bit 1 and following. <TOOLCHANGEREASON>...
Page 237 Tool management 12.2 Configuring the user interface <OnlyOneReasonAllowed value="true" type="bool" /> <UseCapLocalParameter value="true" type="bool" /> <REASON1> <Text value="TM_DGL_DESIRED_PIECES_ELAPSED" type="QString" /> <BitMask value="1" type="int" /> </REASON1> <REASON2> <Text value="TM_DGL_TOOL_BREAKAGE" type="QString" /> <BitMask value="2" type="int" /> </REASON2> <REASON3> <Text value="TM_DGL_CUTTING_EDGE_DAMAGE" type="QString" /> <BitMask value="4"...
Page 238 Tool management 12.2 Configuring the user interface 12.2.23 Configure the code carrier connection Requirement Software option You require the "Access MyTool ID" option for this function (Tool Ident Connec‐ tion). <IDENTCONNECTIONCONFIGURATION> tag The entries used for configuring the code carrier connection in the tool list of the user interface are located in the <IDENTCONNECTIONCONFIGURATION>...
Page 239 Tool management 12.2 Configuring the user interface The following functions in the tool list are available: 1. Creating tools for the code carrier: Figure 12-1 New tool from code carrier The data of the tool are read from the code carrier tool and displayed in the "New Tool" window.
Page 240 Tool management 12.2 Configuring the user interface Entries Meaning UnloadWithDelete true - the tool is deleted when unloaded to the code carrier. The "On code carrier" function is not offered for "Delete tool". false - default setting, the tool is only unloaded for "unload to code carrier"...
Page 241 Tool management 12.2 Configuring the user interface 12.2.24 Configuring Save to file <SAVETOOLDATACONFIGURATION> tag The entries used for configuring the functions "Save tools to file" or "Create tools from file" are located in the <SAVETOOLDATACONFIGURATION> tag: The following functions in the tool list are available: 1.
Page 242 Tool management 12.3 Creating OEM texts The following settings can be made: Entries Meaning Enabled true - Tool from/in file is offered. false - Tool from/in file is not offered. UnloadWithDelete true - The tool is deleted when unloaded to a file. The "In File" function is not offered for "Delete tool."...
Page 243 Own comments - are not displayed. Procedure 1. You can copy the sample file "oem_sltmlistdialog_eng.ts" from the following directory: / siemens/sinumerik/hmi/template/lng 2. Save the file in the /oem/sinumerik/hmi/lng or /user/sinumerik/hmi/lng directory. 3. Change the file name to "sltmlistdialog_eng.ts". If you wish to create texts for additional languages, then a separate file must be created for each language.
Page 244 Tool management 12.3 Creating OEM texts OEM tool parameters "ToolUser_1" to "ToolUser_10" "ToolAppl_1" to "ToolAppl_10" Text identifier of the column heading Text identifier of the tooltip TM_HL_TOOL_USER_1 to ...10 TM_TT_TOOL_USER_1 to ...10 TM_HL_TOOL_APPL_1 to ...10 TM_TT_TOOL_APPL_1 to ...10 Text identifiers in tool details Text identifiers in tool details - all parameters TM_HL_TOOL_USER_1_DETAILS to ...10_DETAILS TM_HL_TOOL_USER_1_LONG to ...10_LONG...
Page 245 Tool management 12.3 Creating OEM texts "MultiToolAppl_1" to "MultiToolAppl_10" Text identifier of the column heading Text identifier of the tooltip TM_HL_MULTITOOL_USER_1 to ...10 TM_TT_MULTITOOL_USER_1 to ...10 TM_HL_MULTITOOL_APPL_1 to ...10 TM_TT_MULTITOOL_APPL_1 to ...10 Text identifiers in tool details Text identifiers in tool details - all parameters TM_HL_MULTITOOL_USER_1_DETAILS to ...
Page 246 Tool management 12.3 Creating OEM texts 12.3.2 Examples of OEM texts Example 1 with a single-line and double-line text <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE TS><TS>   <context> <name>SlTmListForm</name>  ...
Page 247 Tool management 12.3 Creating OEM texts <ItemType value="CheckBox" type="QString" /> <DisplayMode value="AnyMode" type="QString" /> <BitMask value="1" type="int" /> <Width value="17" type="int" /> <HeadLine value="TM_HL_EDGE_USER_1_Bit0" type="QString" /> <ToolTip value="TM_TT_EDGE_USER_1_Bit0" type="QString" /> </EdgeUser_1_Bit0> </PARAMETERCONFIGURATION> The two texts under HeadLine and ToolTip should be output depending on the language. To do this, the two text identifiers must be included in the sltmlistdialog_xxx.ts file: <?xml version="1.0"...
Page 248 Tool management 12.4 Examples 12.4 Examples 12.4.1 Example: Configuring an OEM tool list 12.4.1.1 Adapting the configuration file The following excerpt shows the contents of the configuration file: ● Milling technology: sltmlistconfig.xml ● Turning technology: sltmturninglistconfig.xml The file in this example is stored in the "user/sinumerik/hmi/cfg" directory. This example describes a configuration of the OEM tool list.
Page 249 Tool management 12.4 Examples   <Item value="PriorTool" type="QString" /> </TOOLTYPE_ALL> </COLUMN7>  <COLUMN8>  <TOOLTYPE_ALL>...
Page 250 Tool management 12.4 Examples 12.4.1.2 Adaptation of the customer text file The following excerpt shows the contents of the "sltmlistdialog_eng.ts" customer text file. The file in this example is stored in the "user/sinumerik/hmi/lng" directory. Example "sltmlistdialog_eng.ts" file: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE TS><TS>...
Page 251 Tool management 12.4 Examples </message>   <message> <source>TMO_HL_PRIOR_TOOL</source> <translation>V</translation> <remark>priority tool</remark> <chars>1</chars> <lines>2</lines> </message>   <message>...
Page 252 Tool management 12.4 Examples 12.4.2 Example: Configuring magazine location types with names 12.4.2.1 Adapting the configuration file The following excerpt shows the contents of the configuration file: ● Milling technology: sltmlistconfig.xml ● Turning technology: sltmturninglistconfig.xml The file in this example is stored in the "user/sinumerik/hmi/cfg" directory. This example describes a configuration of the location types in the magazine list.
Page 253 Tool management 12.4 Examples  <TOOLTYPE_9997>  <Item value="MultiToolPlaceSpecIdent" type="QString" /> </TOOLTYPE_9997> </COLUMN11> </SlTmToolmagazinForm> </LISTCONFIGURATION>  <PLACETYPECONFIGURATION>...
Page 254 Tool management 12.4 Examples Example "sltmlistdialog_eng.ts" file: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE TS><TS>    <context> <name>SlTmListForm</name>    ...
Page 255 Tool management 12.4 Examples <source>TMMP_TT_HEAVY_TOOL</source> <translation>heavy tool</translation> <chars>35</chars> <lines>2</lines> </message>   <message> <source>TMMP_TT_BIG_TOOL</source> <translation>big</translation> <chars>9</chars> </message>   <message>...
Page 256 Tool management 12.5 Working with two tool holders 12.5 Working with two tool holders It is possible to work on a single turning machine with two tool holders, both of which are mounted on an X axis. The tool holders may be revolvers, multifix, or a combination of both. As both tool adapters are mounted on the same axis it is only possible to machine with one tool.
Page 257 Tool management 12.5 Working with two tool holders MD24007 $MC_CHSFRAME_RESET_CLEAR_MASK Clear system frames after RESET Bit 4 = 0 Do not clear system frame workpiece reference after RESET MD28082 $MC_MM_SYSTEM_FRAME_MASK Setting-up system frames (SRAM) Bit 4 = 1 Workpiece reference ($P_WPFRAME) MD28083 $MC_MM_SYSTEM_DATAFRAME_MASK Setting-up data management, system frames (SRAM)
Page 258 Tool management 12.6 Editor for the tool and magazine management MD10712 $MN_NC_USER_CODE_CONF_NAME_TAB[0]="TRANSMIT" MD10712 $MN_NC_USER_CODE_CONF_NAME_TAB[1]="TRANSM" Subprogram TRANSMIT.SPF: PROC TRANSMIT(INT_NR) F_T_REV2 TRANSM(_NR) F_T_REV2 Note In the status display, TRANSM is now displayed instead of TRANSMIT. General conditions ● The taper turning is not enabled for "working with two tool holders." ●...
Page 259 Tool management 12.6 Editor for the tool and magazine management General sequence The following steps are required to create a tool management: ● Create tool unit ● Define buffer locations ● Define loading location ● Create magazine configuration ● Link assignments Note When you create a new tool unit, a buffer location with a spindle location, a loading magazine with a loading location and a real magazine with five locations are created by default.
Page 260 Tool management 12.6 Editor for the tool and magazine management Procedure The "Tool management" window is open. Adding a new tool unit Position the cursor on the "Active data" folder element. Press the "New element" softkey. A folder element with the standard designation <tool unit> is inserted and the "TO unit"...
Page 261 Tool management 12.6 Editor for the tool and magazine management Press the <Cursor right> or <INPUT> key. The input window for the element settings opens. Enter the desired changes and press the "OK" softkey to confirm the en‐ tries. Note You define the number of buffer and magazine locations in the input window of the higher-level <Magazine>...
Page 262 Tool management 12.6 Editor for the tool and magazine management Deleting elements Place the cursor on the desired element and press the "Delete element" softkey. Press the "OK" softkey to confirm the deletion. The selected object is removed. 12.6.3 Parameterizing the tool management 12.6.3.1 Create tool unit A tool unit is the grouping of tools and magazines to form a unit.
Page 263 Tool management 12.6 Editor for the tool and magazine management 12.6.3.2 Define buffer locations Buffer locations are spindles, grippers, loaders and transfer locations. All buffer locations are managed in an internal buffer magazine with the number 9998. The number of buffer locations is defined from the "Magazine"...
Page 264 Tool management 12.6 Editor for the tool and magazine management You can define the following parameters in the "Magazine" window from the loading magazine directory: Parameters Description Name Designation of the loading magazine The designation is displayed in the tree structure. Magazine number 9999 (cannot be changed) Locations...
Page 265 Tool management 12.6 Editor for the tool and magazine management You can define the following parameters in the "Magazine" window from the magazine directory: Parameters Description Magazine type Selection menu: ● Chain magazine ● Box magazine ● Revolver Name Designation of the magazine. The designation is displayed in the tree structure.
Page 266 Tool management 12.6 Editor for the tool and magazine management Element values You can change the magazine location type with the parameters in the "Location" window: Parameters Description Location type Identification for the magazine location type Consider adjacent location ● Yes ●...
Page 267 Tool management 12.6 Editor for the tool and magazine management Parameters Assignment Spindle/gripper/loader for ● Tool spindle location 1 for magazine (separation 0) magazine ● Gripper location 2 for magazine (separation 0) ● Gripper location 3 for magazine (separation 0) ●...
Page 268 Tool management 12.6 Editor for the tool and magazine management SINUMERIK Operate (IM9) Commissioning Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 269 Configuring alarms 13.1 Creating alarm and message texts via the user interface From the user interface, you can create and edit your alarm and message texts from the part program. In turn, the alarm and message texts are saved corresponding to their number in various text files.
Page 270 In order that a search can be made for alarm files in subdirectories other than the existing /lng directory, you have the following option: Copy the "systemconfiguration.ini" configuration file from the following directory: /siemens/sinumerik/hmi/cfg Store the file in the following directory: /oem/sinumerik/hmi/cfg Create any subdirectory under /hmi, e.g. /oem_dir.
Page 271 Configuring alarms 13.2 Configuring alarm and message texts via alarm text files Create the following section in the configuration file "systemconfigura‐ tion.ini": [oem_dirs] OEM_3=oem_dir Restart SINUMERIK Operate. When searching, the subdirectory is now also taking into account. Foreign language alarm and message texts If you create foreign language alarm and message texts, change over into the desired language.
Page 272 13.2.1 Creating in-house alarm texts Creating an alarm text file 1. You can copy a sample file "oem_alarms_eng.ts" from the following directory: /siemens/ sinumerik/hmi/template/lng 2. Save or create the file in the /oem/sinumerik/hmi/lng or /user/sinumerik/hmi/lng directory. Create a separate file for each country language that is supported.
Page 273 Note The names of the <BaseNames> tag can be freely selected. They must be unique in the system and must not clash with names used by Siemens. The "Siemens_BaseName_01" name is reserved for Siemens. Several alarm text files can also be registered. To do this, use names such as "OEM_BaseName_02", "OEM_BaseName_03", etc.
Page 274 Creating an index text file 1. You can copy a sample index text file "oem_indexparams_eng.ts" from the following directory: /siemens/sinumerik/hmi/template/lng 2. Save or create the file in the /oem/sinumerik/hmi/lng or /user/sinumerik/hmi/lng directory. Create a separate file for each country language that is supported.
Page 275 Configuring alarms 13.2 Configuring alarm and message texts via alarm text files Creating index texts 1. Open the "my_indextexts_eng.ts" file. 2. In the <name> tag, enter a name that you have selected, e.g. "my_context". 3. For each index text, a separate area must be inserted between the <message> and </ message>...
Page 276 <IndexTexts> and </IndexTexts> tags. The tags for these sections are called, e.g. <OEM_IndexText_01>, <OEM_IndexText_02>, <OEM_IndexText_03>, etc. The tags <IndexText_01> to <IndexText_99> are reserved for Siemens. Example <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <!- Configuration of the Solutionline Alarm & Event Service Adapter ->...
Page 277 Creating message texts Procedure: 1. You can copy a sample message text file "oem_pp_messages_eng.ts" from the following directory: /siemens/sinumerik/hmi/template/lng 2. Save or create the file in the /oem/sinumerik/hmi/lng or /user/sinumerik/hmi/lng directory. Create a separate file for each country language that is supported.
Page 278 Note The names of the <BaseNames> tag can be freely selected. They must be unique in the system and must not clash with names used by Siemens. The "Siemens_BaseName_01" name is reserved for Siemens. Several message text files can also be registered. To do this, use names such as "OEM_BaseName_02", "OEM_BaseName_03", etc.
Page 279 Configuring alarms 13.2 Configuring alarm and message texts via alarm text files 3. Now open the "slaesvcconf.xml" configuration file. 4. Enter the respective NC channel in the <Connections> tag. Only use the XML tags from the following table to specify the NC channel. NC chan‐...
Page 280 Create alarm attribute file Procedure: 1. You can copy a sample alarm attribute file "oem_slaedatabase.xml" from the directory: / siemens/sinumerik/hmi/template/cfg/ 2. Save the file in the directory /oem/sinumerik/hmi/cfg/ or /user/sinumerik/hmi/cfg/ 3. Assign a unique name to the file, e.g. " muster_slaedatabase.xml ".
Page 281 Configuring alarms 13.2 Configuring alarm and message texts via alarm text files 3. Enter the attribute name of the alarm color to be changed in the <Attribute AttrName=…> tag. You can change the following colors: – Font color of the alarm/message text = TEXTCOLOR –...
Page 282 Configuring alarms 13.2 Configuring alarm and message texts via alarm text files <AttrDescr> Text color of an alarm used when displayed within the header panel. </AttrDescr> </Attribute> <Attribute AttrName="TEXTBACKGROUNDCOLOR" AttrID="5004" AttrDataType="10"> <AttrDescr> Background color of an alarm used when displayed within the header panel.
Page 283 Note The names of the <DataBases> tag can be freely selected. They must be unique in the system and must not clash with names used by Siemens. The "Siemens_DataBase_01" name is reserved for Siemens. If you register additional alarm attribute files, i.e. you wish to include them in the configuration file, use names such as "OEM_DataBase_02", "OEM_DataBase_03", etc.
Page 284 Note The name for the <name> tag can always be freely selected. However, the name must not clash with the "slaeconv" name used by Siemens. 4. The <source> tag contains the alarm number of the standard alarm, e.g. 10000. 5. The <translation> tag contains the actual alarm text, e.g. "OEM alarm text example for NCK alarm 10.000".
Page 285 Note The names of the <BaseNames> tag can be freely selected. They must be unique in the system and must not clash with names used by Siemens. The "Siemens_BaseName_01" name is reserved for Siemens. Several alarm text files can also be registered. To do this, use names such as "OEM_BaseName_02", "OEM_BaseName_03", etc.
Page 286 Configuring alarms 13.2 Configuring alarm and message texts via alarm text files Replacing standard alarm texts You still have to define which standard alarm texts should be replaced by your alarm texts so that during the program runtime, the original alarm text is replaced by your alarm text. 1.
Page 287 Note The names of the <DataBases> tag can be freely selected. They must be unique in the system and must not clash with names used by Siemens. The <Siemens_DataBase_01> tag name is reserved for Siemens. If you register additional alarm attribute files, i.e. you wish to include them in the configuration file, use the names <OEM_DataBase_02>, <OEM_DataBase_03>, etc.
Page 288 Functional alarms General 9999 (99. NCU) 040 000 ... 059 999 Reserved 060 000 ... 064 999 Siemens cycle alarms 065 000 ... 069 999 Cycle alarms user 070 000 ... 079 999 Compile cycles Manufacturer and OEM 080 000 ... 084 999 Siemens cycles mes‐...
Page 289 Configuring alarms 13.2 Configuring alarm and message texts via alarm text files SourceIDs 1 ... 10 The SourceIDs 1 ... 10 have the following relationship: SourceID SourceURL /NCK/Channel#1/Partprogram /NCK/Channel#2/Partprogram /NCK/Channel#3/Partprogram /NCK/Channel#4/Partprogram /NCK/Channel#5/Partprogram /NCK/Channel#6/Partprogram /NCK/Channel#7/Partprogram /NCK/Channel#8/Partprogram /NCK/Channel#9/Partprogram /NCK/Channel#10/Partprogram 13.2.7 Parameter specifications in alarm texts Alarm texts can contain alarm parameters (accompanying values) that specify the cause of an alarm in more detail.
Page 290 Configuring alarms 13.2 Configuring alarm and message texts via alarm text files Parameter Description specifier Seventh parameter from the alarm data of the alarm source Only for NCK alarms: Third part (between the 2nd and 3rd separator) of the fourth parameter from the alarm data of the alarm source.
Page 291 Configuring alarms 13.3 Configuring an alarm log 13.3 Configuring an alarm log Default Per default, the alarm log contains all alarms and messages - with their incoming and outgoing time stamps - in chronological order since the last boot. The exceptions are messages from the NC part program (msg command).
Page 292 13.3.2 Loading alarm log via configuration file Creating the configuration file Adjustments are made in file "slaesvcconf.xml". Copy a sample configuration file "oem_alarmprot_slaesvcconf.xml" from the following directory: /siemens/sinumerik/hmi/ template/cfg. Procedure: 1. Save or create the file in the /oem/sinumerik/hmi/cfg or /user/sinumerik/hmi/cfg directory.
Page 293 Configuring alarms 13.3 Configuring an alarm log 3. Open the file and enter the number of events to be output in the tag <Records type .../>. The default value is 500. The maximum number depends on the storage medium (hard disk or CompactFlash card).
Page 294 Configuring alarms 13.3 Configuring an alarm log Cancel criteria Cancel criteri‐ Alarm source Description on (ClearInfo) (Source) /HMI Alarms that are canceled by the HMI. /NCK Alarms that are canceled by power-on of the NCU. Conditions are canceled by a hardware reset of the NCU. Conditions are deleted by a "CANCEL"...
Page 295 (default: 10). Example: Switching off existing filters To switch off the existing Siemens filter - without overwriting the filter - proceed as follows: 1. An "empty" filter switches off all previously set filters. Knowledge of the filter designation is not required.
Page 296 Configuring alarms 13.4 PLC alarms with parameters <Filter_03 value="CLEARINFO NOT 15 AND AlarmID HIGHER 700599" type="QString"/> </Filters> </Protocol> </CONFIGURATION> Result For the changes to the protocol settings to take effect, restart SINUMERIK Operate. 13.4 PLC alarms with parameters Introduction For alarms that are triggered via the PLC blocks SFC17 and SFC18, a parameter can be transferred each time the block is called.
Page 297 Configuring alarms 13.4 PLC alarms with parameters 13.4.1 Definition of a parameter of the octet string data type Parameter statement The parameter statement describes how one or more parameters can be defined with the maximum 12-bytes long octet string supplied with the alarm PDU. Syntax The following syntax applies for the parameter statement: <Parameter directive ext>...
Page 298 Configuring alarms 13.4 PLC alarms with parameters %1B0%1B1%1B2%1B3%1I1 → 1st parameter: 1st associated value, BOOL at bit offset 2nd parameter: 1st associated value, BOOL at bit off‐ set 1 3rd parameter: 1st associated value, BOOL at bit offset 4th parameter: 1st associated value, BOOL at bit offset 5th parameter: 1st associated value, INTEGER (16-bit, signed) at byte offset 1 Example of an alarm attribute file (how to create an alarm attribute file, see Changing alarm...
Page 299 Configuring alarms 13.4 PLC alarms with parameters <Alarm AlarmID="700002"> <MSGTEXT>my_oem_plc_alarms_context|700002/PLC/PMC</MSGTEXT> <HMIPROPARAMDESCR2>%1I0%1I2%1Y4</HMIPROPARAMDESCR2> </Alarm>  <Alarm AlarmID="700003"> <MSGTEXT>my_oem_plc_alarms_context|700003/PLC/PMC</MSGTEXT> <HMIPROPARAMDESCR2>%1Y0%1W1%1D3%1Y7</HMIPROPARAMDESCR2> </Alarm> </Alarms> </Source> </Sources> </SlAeAlarmAttributes> 13.4.2 Definition of the language-dependent formatting Format statement The format statement is part of the alarm text and is used as a placeholder for a parameters to be displayed.
Page 300 Configuring alarms 13.5 Deactivating a warning Examples @1%b@ → Value from the first parameter description to be displayed as a binary num‐ ber, e.g. "1011011" @2%8X@ → Value from the second parameter description to be displayed as a hexadec‐ imal number with eight digits, missing digits are filled with 0, e.g. "00AF37FE" @1%7.2f@ →...
Page 301 Configuring alarms 13.5 Deactivating a warning You can copy this area from the original file. The "slaesvcadapconf.xml" file is in the following directory: /siemens/sinumerik/hmi/base Setting In the <MissingTextWarning type="bool" value="FALSE"/> tag, deactivate/activate the warning. Entry Meaning TRUE The warning is displayed.
Page 302 Configuring alarms 13.5 Deactivating a warning SINUMERIK Operate (IM9) Commissioning Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 303 Collision avoidance 14.1 Overview Collision avoidance allows you to avoid collisions and damage while machining a workpiece or creating programs. Software option You require the "Collision Avoidance ECO (machine)" software option in order to use this function for geometrically primitive protection area elements. Software option You require the "Collision Avoidance (machine, working area)"...
Page 304 Collision avoidance 14.2 General sequence Note The collision monitoring is only valid for single-channel machines. Note Referenced axes The positions of the axes in the machine area must be known so that the protection areas can be monitored. For this reason, the collision avoidance is only active after the referencing. NOTICE No complete machine protection Incomplete models, e.g.
Page 305 Collision avoidance 14.3 Set collision avoidance ● Create kinematic structure (with kinematic elements) ● Creating protection areas ● Creating protection area elements ● Define collision pairs 14.3 Set collision avoidance Enable function Set the following machine data item in order to enable the function: MD19830 $ON_COLLISION_MASK Functional scope of the collision avoidance Bit 0...
Page 306 Collision avoidance 14.4 Graphic machine model editor Note If a specific safety clearance has been set for a collision pair via the system variable $NP_SAFETY_DIST, this has priority over the NC-specific safety clearance set in the MD10622 $MN_COLLISION_SAFETY_DIST machine data. NC/PLC interface signals Signal Meaning...
Page 307 Collision avoidance 14.5 Editing the machine model Procedure Select the "Start-up" operating area. Press the softkeys "NC" and "Machine model". The "Tree" window opens. The "Tree" window opens. The following folders are available in the tree view: ● Active data ●...
Page 308 Collision avoidance 14.5 Editing the machine model Press the "OK" softkey if you wish to attach the element to the chain as the next element. The element is inserted and the name is automatically extended by a long underscore and incremented. Note: You have the option of changing the name of the element in the associ‐...
Page 309 Collision avoidance 14.6 Changing and adapting the machine model view Activating the machine model Each time that an element of the collision model is entered or changed, then the collision model is automatically activated. If the collision model is incorrect, an error message is output and the incorrect element has a pink background.
Page 310 Collision avoidance 14.6 Changing and adapting the machine model view 14.6.2 Changing the section of the machine graphic Use the magnifying glass if you would like to move, enlarge or reduce the size of the section when viewing the machine model, e.g. to view details and to subsequently display the complete model.
Page 311 Collision avoidance 14.6 Changing and adapting the machine model view Procedure Position the cursor in the graphic. Press the "Rotate view" softkey. Press the "Arrow right", "Arrow left", "Arrow up", "Arrow down", "Arrow clockwise" or "Arrow counter-clockwise" softkey to change the position of the machine model.
Page 312 Collision avoidance 14.6 Changing and adapting the machine model view Precondition ● You are in the graphic machine model editor. ● The "Graphic" and "Autozoom" softkeys are active. Procedure Position the cursor in the graphic Press the ">>" and "Views" softkeys. Press the "From front"...
Page 313 Collision avoidance 14.7 Creating a kinematic structure The machine model with all display and monitoring elements is displayed in the graphics window. By deselecting, i.e. by pressing the corresponding softkey again, you can display and hide the display elements and monitoring elements. Setting the detail level If, for protection elements, different detail levels are specified, then soft‐...
Page 314 Collision avoidance 14.7 Creating a kinematic structure World coordinate system To uniquely describe the kinematic structure of a machine, all elements of the kinematic chain are referred to the world coordinate system. You have the option of freely selecting the origin and orientation of the world coordinate system. However, it is recommended that you orientate the world coordinate system so that the coordinate axes are arranged in the positive traversing direction of the machine linear main axes.
Page 315 Collision avoidance 14.7 Creating a kinematic structure 14.7.1.2 Kinematic rotation and parallel kinematic rotation You can define fixed rotation of a subsequent element in the "Rotation" window. Display in the tree topology Kinematic rotations are identified by this symbol in the tree topology. Element values Parameter Meaning...
Page 316 Collision avoidance 14.7 Creating a kinematic structure 14.7.1.4 Rotary axis and parallel rotary axis In the "Rotation axis" window, you define a rotary axis, whose traversing motion describes a circle or arc. This means that you change the orientation of the subsequent elements. Display in the tree topology Dynamic rotation axes are identified by this symbol in the tree topology.
Page 317 Collision avoidance 14.7 Creating a kinematic structure 14.7.1.6 Switch and parallel switch In the "Switch" window, you specify which of the following elements can be switched on or off in an active kinematic chain. Display in the tree topology Switching elements are identified by this symbol in the tree topology. Element values Parameter Meaning...
Page 318 Collision avoidance 14.7 Creating a kinematic structure Procedure Position the cursor at the kinematic chain element to which you wish to attach a protection area. Press the "New element" softkey. Press the "Collision element" softkey. The "New Collision Element" selection window opens. Select "Machine protection area"...
Page 319 Collision avoidance 14.7 Creating a kinematic structure Display in the tree topology Tool protection areas are identified by this symbol in the tree topology. Element values Parameter Meaning Name Designation that is displayed in the tree structure. Color Selection of the color Detail level Defines from which detail level the protection area or the protection area elements are displayed on the user interface.
Page 320 Collision avoidance 14.7 Creating a kinematic structure Display in the tree topology Machine protection areas are identified by this symbol in the tree topology. Element values Parameter Meaning Name Designation, which is displayed in the tree structure. Color Selection of the color Detail level Defines from which detail level the protection area or the protection area elements are displayed on the user interface.
Page 321 Collision avoidance 14.7 Creating a kinematic structure ● Sphere or parallel sphere ● Cylinder or parallel cylinder ● Cone and parallel cone ● File or parallel 3D file Note Parallel protection area elements You have the possibility of creating two protection area elements in parallel in a hierarchic level of the tree structure.
Page 322 Collision avoidance 14.7 Creating a kinematic structure Cylinder and parallel cylinder protection area element (Page 312) Protection area element cone and parallel cone (Page 314) 14.7.3.2 Frame and parallel frame protection area element You define a coordinate system transformation that will take effect for the following protection area elements in the "Frame"...
Page 323 Collision avoidance 14.7 Creating a kinematic structure 14.7.3.3 Box and parallel box protection area elements You can specify the values for the display or collision monitoring of a box-shaped protection area element in the "Box" window. Sum of the offset and rotation between this element and the root element. Offsets and rotation from the parameters of this element.
Page 324 Collision avoidance 14.7 Creating a kinematic structure Parameter Meaning ● Display The protection area element is shown in the graphic view. The element is only visible if the "Display model" softkey is active. The element is not monitored for collision. ●...
Page 325 Collision avoidance 14.7 Creating a kinematic structure 14.7.3.4 Sphere and parallel sphere protection area elements You can specify the dimensions and position as well as values for the display and collision monitoring of a sphere-shaped protection area element in the "Sphere" window. Sum of the offset and rotation between this element and the root element.
Page 326 Collision avoidance 14.7 Creating a kinematic structure Parameter Meaning ● Display The protection area element is shown in the graphic view. The element is only visible if the "Display model" softkey is active. The element is not monitored for collision. ●...
Page 327 Collision avoidance 14.7 Creating a kinematic structure Sum of the offset and rotation between this element and the root element. Offsets and rotation from the parameters of this element. Display in the tree topology Cylinder-shaped protection area elements are identified by this symbol in the tree topology.
Page 328 Collision avoidance 14.7 Creating a kinematic structure Parameter Meaning ● Display The protection area element is shown in the graphic view. The element is only visible if the "Display model" softkey is active. The element is not monitored for collision. ●...
Page 329 Collision avoidance 14.7 Creating a kinematic structure Sum of the offset and rotation between this element and the root element. Offsets and rotation from the parameters of this element. Display in the tree topology Cone-shaped protection area elements are identified by this symbol in the tree topology.
Page 330 Collision avoidance 14.7 Creating a kinematic structure Parameter Meaning ● Display The protection area element is shown in the graphic view. The element is only visible if the "Display model" softkey is active. The element is not monitored for collision. ●...
Page 331 Collision avoidance 14.7 Creating a kinematic structure Sum of the offset and rotation between this element and the root element. Offsets and rotation from the parameters of this element. Display in the tree topology STL files are identified by this symbol in the tree topology. Element values Parameter Meaning...
Page 332 Collision avoidance 14.7 Creating a kinematic structure Parameter Meaning ● Display The protection area element is shown in the graphic view. The element is only visible if the "Display model" softkey is active. The element is not monitored for collision. ●...
Page 333 Collision avoidance 14.7 Creating a kinematic structure Procedure Position the cursor in the tree view on the "Collision groups" folder. The "New collision element" selection window opens. Select "Collision pair" and press the "OK" softkey. Enter the values and press the "OK" softkey to confirm the entries. See also Collision pair (Page 319) 14.7.4.2...
Page 334 Collision avoidance 14.8 Collision avoidance example 14.7.5 Supplementary condition Tool changes If, in a machine model, tools change as a result of being replaced/exchanged or wear without programming a tool offset selection (D number), then the recalculation of the machine model must be explicitly requested.
Page 335 Collision avoidance 14.8 Collision avoidance example The following elements are defined for the example of the 3-axis milling machine: Element Color Direction of movement Table Green X, Y Z axis Gray Column Gray None Tool holder Blue Tool (when used) Machine zero None None...
Page 336 Collision avoidance 14.8 Collision avoidance example Structure of the geometric machine modeling The kinematic chain begins with the first offset kinematic element that represents the machine zero. The other kinematic elements form the linear axes X, Y and parallel Z. The protection area is used to define the basic bodies of the machine and tools.
Page 337 Collision avoidance 14.8 Collision avoidance example 14.8.2 Create machine model example 14.8.2.1 Creating kinematic elements Offset Mark the "Active data" folder and press the "New element" softkey. A selection window with kinematic elements opens. Select the "Offset" kinematic element and press the "OK" softkey. The appropriate input window for the element values opens in the lower part of the tree view.
Page 338 Collision avoidance 14.8 Collision avoidance example Linear axis Y under linear axis X Mark the "X axis" kinematic element and press the "New element" softkey. A selection window with kinematic elements opens. Select the "Linear axis" kinematic element and press the "OK" softkey. The appropriate input window for the element values opens in the lower part of the tree view.
Page 339 Collision avoidance 14.8 Collision avoidance example 14.8.2.2 Creating machine protection areas Stand under offset Mark the "ROOT" kinematic element and press the "New element" soft‐ key. Press the "Collision element" softkey. In the "New collision element" window, select the collision element "Ma‐ chine protection area"...
Page 340 Collision avoidance 14.8 Collision avoidance example Table under linear axis Y Mark the "Y axis" kinematic element and press the "New element" softkey. Press the "Collision element" softkey. Select the "Machine protection area" collision element and press the "OK" softkey. Enter the following values: Name: Table...
Page 341 Collision avoidance 14.8 Collision avoidance example Select the "Machine protection area" collision element and press the "OK" softkey. Enter the following values: Name: Z axis Color: Gray Detail level: 0 PLC bit: Activation: Activated Press the "OK" softkey to save the values. Box element under Z axis Select the "Z axis"...
Page 342 Collision avoidance 14.8 Collision avoidance example PLC bit: Activation: Activated Press the "OK" softkey to save the values. Cylinder element under tool holder Mark the "Tool holder" machine protection area and press the "New ele‐ ment" softkey. Select the "Cylinder" protection area element and press the "OK" softkey. Enter the following values: Name: SBE tool holder...
Page 343 Collision avoidance 14.8 Collision avoidance example Location: Press the "OK" softkey to save the values. 14.8.2.4 Creating collision pairs Tool/table collision pair Mark the "Collision groups" folder and press the "New element" softkey. A selection window for the collision element opens. Select the "Collision pair"...
Page 344 Collision avoidance 14.8 Collision avoidance example SINUMERIK Operate (IM9) Commissioning Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 345 Transformations 15.1 Activate commissioning screen for transformations Requirement A kinematic chain must also be present for the kinematic transformations. For further information on kinematic chaining, see Chapter "Kinematic elements (Page 299)". Parameters Set one or both of the following machine data to activate the commissioning screen for transformations: MD18866 $MN_MM_NUM_KIN_TRAFOS Maximum number of transformations that can be...
Page 346 Transformations 15.2 Function overview of the commissioning screen for transformations Calling transformations You can open the Transformations window as follows: Select the "Start-up" operating area. Press the "NC" and "Transformations" softkeys. The "Transformations" window opens. General sequence The following elements are numbered and offered for set-up in the "Transformations" window: ●...
Page 347 Transformations 15.3 Assigning and editing transformations Meaning of the symbols Symbol Description Offset Linear axis Rotary axis Spindle Rotary axis Axis without Hirth gearing Axis with Hirth gearing References You will also find information on transformation in the following references: ●...
Page 348 Transformations 15.4 Assigning and editing tool carriers Press the "New" softkey. The "New transformation" window opens. The following transformation types are available: ● Dynamic orientation transformation TRAORI_DYN ● Static orientation transformation (turning) TRAORI_STAT ● Face end transformation TRANSMIT_K ● Peripheral surface transformation, TRACYL_K ●...
Page 349 Transformations 15.4 Assigning and editing tool carriers Procedure The "Transformations" window is open. Assigning new tool carriers Position the cursor on the TC element. Press the "New" softkey. The "New tool carrier" window opens. The following tool carriers are available: ●...
Page 350 Transformations 15.5 Copying/pasting or deleting transformations 15.5 Copying/pasting or deleting transformations If you want to create a transformation that is similar to an existing transformation, then you can save time if you copy the existing properties and paste them in a different place. Procedure The "Transformations"...
Page 351 Transformations 15.6 Selecting element from chain 15.6 Selecting element from chain If input fields in the Transformations window refer to kinematic elements, you can select the appropriate element designation directly from the tree view of the graphic machine model and then import it: Procedure You are in the "Transformations"...
Page 352 Transformations 15.7 Assigning parameters to transformation types and tool carriers 15.7 Assigning parameters to transformation types and tool carriers 15.7.1 TRAORI_DYN Requirement You are on a KT element in the operating area "Start-up" → "NC" → "Transformations" → "New" and have selected the transformation type TRAORI_DYN - dynamic orientation transformation. The dialog for the combinations opens.
Page 353 Transformations 15.7 Assigning parameters to transformation types and tool carriers Parameter or property System variable Description End of tool chain $NT_T_CHAIN_LAST_ELEM[n] Name of last chain ele‐ ment in the tool chain Close tool chain $NT_CNTRL[n] Bit 8 Close tool chain automati‐ cally ●...
Page 354 Transformations 15.7 Assigning parameters to transformation types and tool carriers The parameter is only displayed in the window if an initialization value was set. A name must be indicated for the chain element depending on the parameter assignment. The properties of the retraction positions are displayed depending on the "Selection of retraction" parameter.
Page 355 Transformations 15.7 Assigning parameters to transformation types and tool carriers Parameter or property System variable Description Icon NT_CNTRL[n] Bit 1 - 3 Rotational axis/spindle Icon $NT_CNTRL[n] Bit 4 - 6 Without/with Hirth gearing End of tool chain $NT_T_CHAIN_LAST_ELEM[n] Name of last chain ele‐ ment in the tool chain Close tool chain $NT_CNTRL[n] Bit 8...
Page 356 Transformations 15.7 Assigning parameters to transformation types and tool carriers Parameter or property System variable Description Selection of preferred direction $NT_IDENT[n, 0] Show selection of prefer‐ THOUSANDS red direction on input screen ● No, always=- ● Yes, default=- ● No, always=+ ●...
Page 357 Transformations 15.7 Assigning parameters to transformation types and tool carriers Parameter or property System variable Description Ignore active tool $NT_IGNORE_TOOL_ORIENT[n] No: Use orientation from ac‐ tive tool ● No Yes: Always use the basic ● Yes tool orientation 15.7.3 TRANSMIT_K Requirement You are on a KT element in the operating area "Start-up"...
Page 358 Transformations 15.7 Assigning parameters to transformation types and tool carriers Parameter or property System variable Description Rotational axis $NT_ROT_AX_NAME[n, 1] Name of chain element of the rotational axis End of workpiece chain $NT_P_CHAIN_LAST_ELEM[n] Name of last chain ele‐ ment in the workpiece chain Linear axis Transformation axis...
Page 359 Transformations 15.7 Assigning parameters to transformation types and tool carriers Parameter or property System variable Description Invert tool direction Z $NT_CNTRL[n] Bit 20 Invert tool direction Z (only if $NT_CNTRL[n] ● No Bit 19 = 1) ● Yes The parameter is only displayed in the window if an initialization value was set. The following parameters are only displayed if they deviate from the initialization values: Parameter or property System variable...
Page 360 Transformations 15.7 Assigning parameters to transformation types and tool carriers Parameters or properties System variable Description $NT_TRAFO_INDEX[n] call number Tens and hundreds place ● 01 - 04: call number ● Otherwise: error $NT_TRAFO_INDEX[n] Call from channel Thousands and ten thousands digit ●...
Page 361 Transformations 15.7 Assigning parameters to transformation types and tool carriers Parameters or properties System variable Description Order of the geometry axes $NT_CNTRL[n] Bit 16 - 18 Order of the geometry axes ● X Y Z ● Z X Y ● Y Z X (default) ●...
Page 362 Transformations 15.7 Assigning parameters to transformation types and tool carriers System variable assignment Parameters are assigned for the following system variables using the operating software for the TRAANG_K transformation type - "inclined axis" transformation: Parameter or property System variable Description Name $NT_NAME[n] Name of transformation...
Page 363 Transformations 15.7 Assigning parameters to transformation types and tool carriers The following parameters are only displayed if they deviate from the initialization values: Parameter or property System variable Description Assignment of chains Tool chain Tool reference point $NT_T_REF_ELEM[n] Name of chain element for the tool reference Properties (transformation) Alarm in the event of motion of re‐...
Page 364 Transformations 15.7 Assigning parameters to transformation types and tool carriers Parameter or property System variable Description Kinematics Tool chain Start of tool chain $TC_CARR_KIN_TOOL_STAR Name of first chain element in the tool chain Offset element $TC_CARR_CORR_ELEM[n, 0 Name of offset element for - 3] measuring kinematics Rotational axis 1...
Page 365 Transformations 15.7 Assigning parameters to transformation types and tool carriers Parameter or property System variable Description Selection of swivel mode $TC_CARR37[n] Show selection of swivel mode ONES on input screen ● Axis-by-axis ● Rotary axes direct ● Projection angle ● Solid angle Selection of preferred direction $TC_CARR37[n] Show selection of preferred di‐...
Page 366 Transformations 15.7 Assigning parameters to transformation types and tool carriers Kinematic types und number of rotary axes The following combinations are permissible: Kinematic type ($TC_CARR23) Swivel head Swivel head + Swivel table swivel table Number of rotational axes in the head Number of rotational axes in the table System variable assignment Parameters are assigned for the following system variables using the operating software for...
Page 367 Transformations 15.7 Assigning parameters to transformation types and tool carriers Parameter or property System variable Description Hirth gearing $TC_CARR28[n] > 0 With/without Hirth gearing $TC_CARR28[n] Angular grid $TC_CARR26[n] Angle offset Offset l2 $TC_CARR4[n] Offset l2 (X) $TC_CARR5[n] Offset l2 (Y) $TC_CARR6[n] Offset l2 (Z) Fine offset l2...
Page 368 Transformations 15.7 Assigning parameters to transformation types and tool carriers Parameter or property System variable Description ● Retraction position Z $TC_CARR38[n] Retraction position WCS $TC_CARR39[n] ● Retraction position X $TC_CARR40[n] ● Retraction position Y Selection of swivel mode $TC_CARR37[n] Show selection of swivel mode ONES on input screen ●...
Page 369 Data backup 16.1 Overview Data backup The following times are recommended for performing a data backup: ● After a start-up ● After changing machine-specific settings ● After replacing a hardware component ● For a software upgrade ● Before the activation of memory-configuring machine data Note A start-up archive is saved as a file of the type ".arc"...
Page 370 Data backup 16.2 Creating a start-up archive Setting line checksums To read in a data archive, you need, at a minimum, the authorization that is needed to carry out existing machine data assignments in the archive without any errors. The "Manufacturer" authorization is usually used for this.
Page 371 Data backup 16.2 Creating a start-up archive Data of the control components Control components Data NC data Machine data Setting data Option data Global (GUD) and local (LUD) user data Tool and magazine data Protection zone data R parameters Zero offsets Workpieces, part programs and subprograms Standard and user cycles Definitions and macros...
Page 372 Data backup 16.2 Creating a start-up archive Control components Data Comment Entry field for possible comments regarding the start-up archive. Created by Entry field for the creator as well as creation date of the start-up archive. Procedure Select the "Start-up" operating area. Press the menu forward key.
Page 373 Data backup 16.3 Reading-in a start-up archive 16.3 Reading-in a start-up archive NOTICE Loss of additional languages during software upgrade All the system languages are overwritten during software upgrades. If there are more languages in the system than in the upgrade archive, these additional languages are lost when the archive is read in.
Page 374 Data backup 16.4 Backing up the hardware configuration Select the required storage location, press the "Search" softkey and enter the required search term. Then press the "OK" softkey if you wish to search for a certain directory, subdirectory or start-up archive. Press the "OK"...
Page 375 Data backup 16.5 Creating an archive with original data Activate "Create PLC hardware upgrade archive (SDBs only)" and press the "OK" softkey. The "Create PLC hardware upgrade archive (SDBs only): Select Storage Location" window opens. Select the desired storage location in the displayed data tree. - OR - Press the "New directory"...
Page 376 Data backup 16.5 Creating an archive with original data Data of the control components Control components Data NC data Machine data Setting data Option data Global (GUD) and local (LUD) user data Tool and magazine data Protection zone data R parameters Zero offsets Compensation data Workpieces, part programs and subprograms...
Page 377 Data backup 16.6 Reading in an archive with original data Procedure Select the "Start-up" operating area. Press the menu forward key. Press the "Start-up archive" softkey. The "Start-up" window opens. Activate the "Create archive of original status" checkbox and press the "OK"...
Page 378 Data backup 16.8 Serial interface (V24 / RS232) Press the "Start-up archive" softkey. The "Start-up" window opens. Activate the "Read in archive of original status" checkbox and press the "OK" softkey. SINUMERIK Operate automatically accesses the "original.arc" file. A window opens prompting whether you want to perform a start-up. Press the "OK"...
Page 379 Interface and softkeys are not available = false Storage of file "slpmconfig.ini" The template of the file "slpmconfig.ini" for SINUMERIK Operate is stored in the following directory: <Installation path>/siemens/sinumerik/hmi/template/cfg Copy the file to one of the following directories: <Installation path>/user/sinumerik/hmi/cfg <Installation path>/oem/sinumerik/hmi/cfg Note If you want to achieve a better overview of the changes you have made yourself, simply delete the unchanged parameters from the file copy "slpmconfig.ini".
Page 380 Data backup 16.8 Serial interface (V24 / RS232) Externally processing the punched tape format If you wish to externally process an archive, then generate this in the punched tape format. Procedure Select the "Program manager" operating area, and press the "NC" or "Local.
Page 381 Data backup 16.8 Serial interface (V24 / RS232) 16.8.2 Setting interface parameters Procedure Select the "Start-up" operating area. Press the "System data" softkey. Press the ">>" and "Archive" softkeys. Select the "RS-232-C settings" softkey. The "Interface: RS-232-C" window is opened and the interface set‐ tings are displayed.
Page 382 Data backup 16.9 Backing up setup data Parameter Meaning Parity Parity bits are used for error detection: The parity bits are added to the coded characters to make the number of positions set to "1" an uneven number (uneven parity) or to an even number (even parity). ●...
Page 383 By default, the network settings cannot be backed up. The archiving of the network settings must be enabled: 1. Copy the "slpmconfig.ini" file from the /siemens/sinumerik/hmi/template/cfg directory. 2. Store the file in the /oem/sinumerik/hmi/cfg or /user/sinumerik/hmi/cfg directory. 3. Open the file and enter the following for [SeriesSetup]: SupportNetworkSettings=true 4.
Page 384 Data backup 16.10 Network settings Basic procedure ● Backup of network settings After activation, the network settings can also be backed up when a commissioning archive is created when a check mark is set, see Creating a start-up archive (Page 356). ●...
Page 385 Configuring the network Overview If you wish to perform network settings in SINUMERIK Operate, you have the following options: ● The Start-up operating area allows you to set up all of the basic configurations for the plant and company networks (see Section "Displaying the network overview (Page 371)"). ●...
Page 386 Configuring the network 17.2 Settings of the system network 17.2 Settings of the system network The configuration for the DHCP server, the routing, active protocols, for DNS servers and other properties of the system network is performed in the "Settings of the system network" window. Setting Description DHCP activated...
Page 387 Configuring the network 17.2 Settings of the system network Setting Description Timeout when waiting for master Specifies a maximum waiting time (in seconds) for the response of the master server (see DHCP server synchronization mode). After this time elap‐ ses, the server itself becomes the active server. This additional pause makes it possible for the in‐...
Page 388 17.2 Settings of the system network Setting Description Function This string is used for the Siemens Industry-spe‐ cific OID automationSystemIdent.automation‐ FunctionTag. If required, a function designation can be specified here which can be called by an SNMP client. This is for information purposes only.
Page 389 Configuring the network 17.3 Settings of the factory network Procedure The network overview is open. Press the "System network" softkey. The "Settings of the System Network" window opens. Press the "Change" softkey to edit settings. Press the "Reset DHCP server" softkey to return the current settings of the DHCP server to the original settings.
Page 390 Configuring the network 17.3 Settings of the factory network Setting Description Host name Here you can define a name for the local host. This manually assigned name takes priority over all oth‐ er names. The host name is determined in the following order: ●...
Page 391 Configuring the network 17.4 Saving network settings Procedure The network overview is open. Press the "Company network" softkey. The "Settings of the Company Network" window opens. Press the "Change" softkey to edit settings. 17.4 Saving network settings You have the option of saving the NCU settings as file. In window "Save network settings: Select archive", select a target folder.
Page 392 Configuring the network 17.5 Configuring operator panels 17.5 Configuring operator panels 17.5.1 Displaying the available operator panels A list with all the available operator panels is displayed in the upper part of the Available Operator Panels ... window. One line corresponds to one operator panel and contains the following information: Column Description...
Page 393 Configuring the network 17.5 Configuring operator panels The active DHCP server that contains the data for the operator panels can be a different NCU, but also the local NCU itself. Irrespective of this, a copy of the data is stored and used on the local NCU.
Page 394 Configuring the network 17.5 Configuring operator panels Column Description Display area Specifies which HMI screen is displayed when activating the TCU. Channel Specifies which channel is displayed when activating the TCU. Editing the list of VNC connections The "Available Operator Panels ..." window is open. Press the "Change"...
Page 395 Configuring the network 17.6 Station-related network diagnostics softkeys in the channel menu, the switchover targets themselves (HMI, NC channel) are displayed on the vertical softkeys assigned to a channel group. Linking of softkeys to channel groups A list for the linking of the HMI softkeys to configured channel groups is displayed in the lower part of the window.
Page 396 Configuring the network 17.6 Station-related network diagnostics Error analysis You have the option of initiating a fault analysis for the components involved. You obtain the result of a such a diagnostics in the form of a fault message. The possible fault states and causes are described in this fault message together with how to resolve the fault.
Page 397 Configuring the network 17.6 Station-related network diagnostics ● IP address ● DNS name ● MCP index from the configuration ● MCP index requested from HMI ● MCP index requested from PLC Procedure Select the "Diagnostics" operating area. Press the menu forward key and the "Bus TCP/IP" softkey. Press the "TCP/IP diagnostics"...
Page 398 Configuring the network 17.6 Station-related network diagnostics Procedure The "TCP/IP Diagnostics" window opens. Position the cursor on the component that is marked as having an error (NCU). Press the "Error analysis" softkey. The corresponding error message is displayed. 17.6.2.2 MCP/EKS as network participant cannot be accessed Error Possible error causes and remedies The MCP/EKS cannot be accessed as network participant.
Page 399 Configuring the network 17.6 Station-related network diagnostics 17.6.2.3 HMI on the PCU cannot establish a network connection to the NC Error Error cause 1 Remedy HMI displays alarm 120202 The IP address of the target NCK/PLC From the HMI, correct the target address for "Wait for connection to NC/ set on the PCU is incorrect.
Page 400 Configuring the network 17.6 Station-related network diagnostics Error Error cause 2.3 Remedy HMI displays alarm 120202 The PCU has an IP address that does not Correctly set the network settings for the sys‐ "Wait for connection to NC/ belong to the network or has an invalid IP ad‐ tem network in the Windows service mode PLC"...
Page 401 Configuring the network 17.6 Station-related network diagnostics Error Possible error causes and remedies Connect the service PG to the NCU via X127. Log into Linux via WinSCP or Putty. Using the service command 'sc show ip -eth0', display the actual settings - and check these. If the cause of the error is confirmed, then the NCU must be reparameterized.
Page 402 Configuring the network 17.6 Station-related network diagnostics Error Possible error causes and remedies Connect the service PG to the NCU via X127. Log into Linux via WinSCP or Putty. If the set NCU mode (no DHCP) is to be kept, the fixed IP address of the NCU must be changed.
Page 403 Configuring the network 17.6 Station-related network diagnostics Error Possible error causes and remedies There is no physical connection. Possible error causes include: ● A switch is not closed/has failed; this can also be the switch of an MCP ● The cable connection has become loose (poor contact) ●...
Page 404 Configuring the network 17.6 Station-related network diagnostics Error Possible error causes and remedies No active DHCP server is found in the system network. Possible error causes include: ● Only a single computer has been configured in the system network with active DHCP server - and this computer is not available.
Page 405 Configuring the network 17.6 Station-related network diagnostics 17.6.2.5 The TCU cannot establish a network connection to the assigned PCU Error Possible error causes and remedies The PCU does not have the IP address specified in the configuration, but an address from the IP range of the system network that can be dynamically allocated.
Page 406 Configuring the network 17.6 Station-related network diagnostics Error Possible error causes and remedies Perform the following steps: ● Under network settings, on the PCU, set the required address again as fixed IP address in the system network. ● At the NCU/PCU, which runs in the DHCP synchronization mode ON_MASTER or is active DHCP server, execute a 'Clear DHCP' (for an NCU using the sc command sc clear dhcp –...
Page 407 Configuring the network 17.6 Station-related network diagnostics Availability of the network connections Network adapter connection White Network cable inserted Network cable not inserted Availability The availability describes the percentage of faulty packages compared to all the sent and received packages. Problems in the company network (e.g.
Page 408 Configuring the network 17.6 Station-related network diagnostics ● Address type Information about the configuration of the network adapter in the configuration file "basesys.ini": – DHCP: DHCP is active for this network adapter. The information behind the hyphen "-" specifies the DHCP mode of operation: off - DHCP is deactivated for this adapter Client - a DHCP client that receives an IP address and further data from a server, is running on the interface...
Page 409 Configuring the network 17.6 Station-related network diagnostics Modifiable parameters The following parameters of the company network adapter (X130) can be set by selecting the "Address type": ● Address type ● IP address ● Subnet mask ● DNS server 1 and 2 ●...
Page 410 Configuring the network 17.6 Station-related network diagnostics Enter the desired changes and press the "OK" softkey to confirm the entries. Press the "New display" softkey to refresh the display. 17.6.4 Ethernet network diagnostics 17.6.4.1 Diagnostics of the network and DHCP server In order to more effectively influence the commissioning, press the "Network diagnostics"...
Page 411 Configuring the network 17.6 Station-related network diagnostics Press the "DHCP server" softkey to fetch information and query the status of the DHCP server. The "DHCP Server" window opens. For each active DHCP server, the status, the role (priority), the MAC address, the TCU version and the lease version are displayed in tabular form in the upper part of the window.
Page 412 Configuring the network 17.6 Station-related network diagnostics General information ● The function is protected with the standard password NETWORK Note Change the standard password to prevent improper use. ● The log is recorded via the tcpdump program (Linux) or the windump program (Windows). Further information can be found at www.tcpdump.org Requirement If you want to change the password, you require access level 1 (manufacturer).
Page 413 Configuring the network 17.6 Station-related network diagnostics Change password The "Network Trace" window is open. Press the "Change password" softkey. The "Change Password" window opens. Enter a new password and confirm with "OK". Trace parameters You can parameterize the conditions for the log recording via the "Parameters (tcpdump)" input field in the Network Trace window.
Page 414 Configuring the network 17.6 Station-related network diagnostics Parameter <option> Option Value Meaning IP address or host Only those packets are recorded that have the specified IP host name address or host name as source or as destination. Network range Only those packets are recorded that have an IP address or host name from the specified network range as source or as destination.
Page 415 Configuring the network 17.6 Station-related network diagnostics 192.168.214.4 and not net 10.113.20.0 ; Records the entire network traffic of system 192.168.214.4 which does not run via system 10.113.20.0. -i 10.113.20.0 -q '(tcp port 80) or ; Records HTTP and also HTTPS (tcp port 443)' packets of the network interface from system...
Page 416 Configuring the network 17.6 Station-related network diagnostics Press the "Topology" softkey if you require an overview of all of the net‐ worked nodes, e.g. to check if there are connection problems. The "Network Topology" window opens. The interface, port and the actual connection are displayed for each node using a tree topology.
Page 417 Configuring the network 17.6 Station-related network diagnostics Deviations during the comparison are identified by being color-highlighted: ● Red: missing or non-accessible components compared with the reference topology. ● Pink: components that deviate in their attribute values compared with the reference topology.
Page 418 Configuring the network 17.6 Station-related network diagnostics SINUMERIK Operate (IM9) Commissioning Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 419 Service and diagnostics 18.1 NC/PLC variables 18.1.1 Displaying and editing PLC and NC variables Changes can only be made to the NC/PLC variables with the appropriate password. WARNING Incorrect parameterization Changes in the states of NC/PLC variables have a considerable influence on the machine. Incorrect configuration of the parameters can endanger life and cause damage to the machine.
Page 420 Service and diagnostics 18.1 NC/PLC variables PLC variables Counters ● Counter (Cx) ● Counter (Cx) Data ● Data block (DBx): Data bit (DBXx), data byte (DBBx), data word (DBWx), data double word (DBDx) ● Data block (VBx): Data bit (VBXx), data byte (VBBx), data word (VBWx), data double word (VBDx) Formats Binary...
Page 421 Service and diagnostics 18.1 NC/PLC variables The GUD from the machine data is only displayed in the Search window for the variable selection when the associated definition file has been activated. Otherwise, the sought variables must be entered manually, e.g. GUD/SYG_RM[1] The following machine data is representative for all variable types (INT, BOOL, AXIS, CHAR, STRING): MD18660 $MN_MM_NUM_SYNACT_GUD_REAL[1].
Page 422 Service and diagnostics 18.1 NC/PLC variables Press the "Details" softkey. The "NC/PLC Variables: Details" window opens. The information for "Var‐ iable", "Comment" and "Value" is displayed in full length. Position the cursor in the "Format" field and select the required format with <SELECT>.
Page 423 Service and diagnostics 18.1 NC/PLC variables Changing operands Depending on the type of operand, you can increment or decrement the address by 1 place at a time using the "Operand +" and "Operand -" softkeys. Note Axis names as index For axis names, the "Operand +"...
Page 424 Service and diagnostics 18.2 Displaying the Service overview Enter the name for the file and press the "OK" softkey. A message in the status line informs you that the screen form was saved in the specified folder. If a file with the same name already exists, they you will receive a prompt. Press the "Load screen"...
Page 425 Service and diagnostics 18.2 Displaying the Service overview ● Motor temperature ● Measuring system 1 active / measuring system 2 active The states for measuring system 1/2 have the following meaning: Symbol Meaning The position measuring system is active. The position measuring system is parked. - OR: - The position measuring system is not configured.
Page 426 Service and diagnostics 18.2 Displaying the Service overview Selection overview The following information is provided in the selection overview. Column Description Bus No. Bus number for drives without NC assignment. No entry for NC axes. Slave address Slave address for drives without NC assignment. No entry for NC axes.
Page 427 Service and diagnostics 18.2 Displaying the Service overview All axes/drives are selected. No axis/drive is selected. Only internal drives are selected. Only external drives are selected. Those axes are selected that are assigned to a real drive. All axes are selected, which are defined in a minimum of one channel. Press the "OK"...
Page 428 Service and diagnostics 18.2 Displaying the Service overview Procedure Select the "Diagnostics" operating area. Press the menu forward key and the “Axis diagnostics" softkey. The "Service Overview" window opens. Press the "Service axis" softkey. The "Service Axis/Spindle" window opens. Press the "Axis +" or "Axis -" softkey to scroll the axes forward or backward. - OR - Press the "Axis selection"...
Page 429 Service and diagnostics 18.2 Displaying the Service overview Display data Meaning Servo gain factor (calculated) The servo gain factor in the display is calculated by the NC according to the following equation: Velocity setpoint = setpoint currently being output to the axis/spindle References: Basic Functions Function Manual;...
Page 430 Service and diagnostics 18.2 Displaying the Service overview Display data Meaning Spindle speed setpoint cur‐ Current active speed setpoint with correct sign, including calculated rent compensation value and any active speed limitation (specified by set‐ ting or machine data) Unit: rpm Display applies to spindles only.
Page 431 Service and diagnostics 18.2 Displaying the Service overview Display data Meaning Feedforward control mode Indicates whether and if so, which mode of the dynamic feedforward control for the axis is active: ● Inactive ● Velocity The velocity-dependent speed feedforward control is active. ●...
Page 432 Service and diagnostics 18.2 Displaying the Service overview Display data Meaning "Travel to fixed stop" state Indicates whether or not the axis has fulfilled the conditions for "Fixed stop reached" when the "Travel to fixed stop" function is active (IS DB31, ...
Page 433 Service and diagnostics 18.2 Displaying the Service overview Press the "Drive selection" softkey. The "Drive direct selection:" window opens. Select the desired drive directly from the selection list. Confirm the selection with "OK." The drive data is displayed. Overview The individual status displays, warnings, messages, etc. that are displayed in the "Service Drive"...
Page 434 "Drive operating display". Number of faulty signs-of-life Display of communications errors detected in hardware between NC and drive. Note If the display shows a value other than "0", please contact your Siemens regional office! SINUMERIK Operate (IM9) Commissioning Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 435 Service and diagnostics 18.2 Displaying the Service overview SC1 drive alarm message Displays (yes/no) whether messages of status class 1 are active. Status class 1 messages are alarms with the following properties: ● They lead to internal responses (e.g. regenerative braking, immediate pulse suppression) ●...
Page 436 Service and diagnostics 18.2 Displaying the Service overview Integrator disabling The display as to whether the integrator of the speed controller is active, corresponds to the interface signal: DB31, ... DBX93.6 "n-controller integrator disabled". Status Meaning Display The requested shutdown of the speed controller integrator is active in the drive.
Page 437 Service and diagnostics 18.2 Displaying the Service overview Actual motor data set The display (MDS0...3) of which motor data set is currently active corresponds to the interface signal: DB31, ... DBX93.3 to 93.4 "Active motor A, B". Operating mode The display of the control type of a drive corresponds to the drive parameter: p1300[0…n] "Open-loop/closed-loop control mode".
Page 438 Service and diagnostics 18.2 Displaying the Service overview Ramp-up function completed The status display of the drive as to whether the ramp-up has been completed corresponds to the interface signal: DB31, ... DBX94.2 "Ramp-up completed". Status Meaning Display The actual speed value has reached the speed tolerance band specified via p2164 after a new speed setpoint specification and has not left the band for the duration of p2166.
Page 439 Service and diagnostics 18.3 System utilization Actual speed = set speed The status display of the drive as to whether the actual speed value matches the speed setpoint corresponds to the interface signal: DB31, ... DBX94.6 "|n | < n ".
Page 440 Service and diagnostics 18.4 Creating screenshots Note The utilization evaluation of the synchronized actions is only displayed when the value in MD11510 $MN_IPO_MAX_LOAD ≠ 0. Procedure Select the "Diagnostics" operating area. Press the menu forward key. Further horizontal softkeys are displayed. Press the "System utilization"...
Page 441 When the equipment is serviced, these entries can be viewed by means of remote diagnostics or can be transmitted for the purpose of registering the machine on the Siemens Service Platform Industry. You can store the following data for each machine: ●...
Page 442 Service and diagnostics 18.5 Machine identity Machine information Entries Meaning Machine No. The unique machine number (serial number of the CompactFlash card) is dis‐ played in the header. This number serves as information only and cannot be changed. Machine name The manufacturer assigns a unique machine number in this field which is stored in machine data MD17400 $MN_OEM_GLOBAL_INFO.
Page 443 Service and diagnostics 18.5 Machine identity Procedure Select the "Diagnostics" operating area. Press the "Version" softkey. It takes some time to call the version display. While the version data is being determined a progress message box and the appropriate text are displayed in the dialog line.
Page 444 Service and diagnostics 18.5 Machine identity Alternatively, you can use the "PridaNet identSNAPSHOT" program to export the machine and address information from the Service Platform Industry database and use it as a template. This ensures that the information is clear. Templates The directory HMI Data/Templates/Examples/Machine identity contains a selection of templates.
Page 445 Service and diagnostics 18.5 Machine identity <Customer-Id></Customer-Id> <Name></Name> <Street></Street> <ZIP code></ZIP code> <Location></Location> <Country></Country> <State></State> <Contact></Contact> <Phone></Phone> <Fax></Fax> <E-mail></E-mail> <URL></URL> </Dealer> </Addresses> You enter the address data of any number of manufacturers in the "oem.xml" file. If you want to enter additional manufacturers, copy the area <Manufacturer> to </Manufacturer> for each dealer.
Page 446 Service and diagnostics 18.5 Machine identity Templates You have the capability of importing files with any name. The content of the files is evaluated. The new file name is derived from the contained information. File Information ma_types.xml Machine types dealer.xml Dealer's data oem.xml Manufacturer's data...
Page 447 Service and diagnostics 18.5 Machine identity 18.5.4 Save information All the machine-specific information of the control is combined in a configuration via the user interface. You then have the option of saving the machine-specific information on the drives that have been set up. Procedure Select the "Diagnostics"...
Page 448 18.5 Machine identity 18.5.5 Adding hardware components Most of the hardware components supplied by Siemens are already electronically acquired. You can add further hardware components. You can view and supplement the hardware components in the version screen at the user interface.
Page 449 Service and diagnostics 18.5 Machine identity Procedure Select the "Diagnostics" operating area. Press the "Version" softkey. It takes some time to call the version display. While the version data is being determined a progress message box and the appropriate text are displayed in the dialog line.
Page 450 Service Platform Industry. ● The data can be read by remote diagnostics. ● The data can also be transferred directly to the Service Platform Industry. Further information at the address (https://www.siemens.com/sinumerik/register). Configuration data The configuration data includes: ●...
Page 451 Service and diagnostics 18.6 Logbook 18.6.1 1. Documenting startup Precondition As a minimum, the machine name/No., the customer No. and the country where the manufacturer is located must be entered into the machine identity. Procedure The machine-specific information data are entered. Start-up (commission) the machine.
Page 452 Service and diagnostics 18.6 Logbook Note Registering the machine identity on the Service Platform Industry. After completion of the 2nd start-up, you are prompted to send the machine identity to the Service Platform Industry database via the Internet. See also Entering machine-specific information (Page 428) 18.6.3 Making a logbook entry...
Page 453 Service and diagnostics 18.7 Action log Searching for a logbook entry You have the option for searching for specific entries using the search function. The "Machine logbook" window is opened. Press the "Find" softkey. Enter the desired term in the search form. You can make a search ac‐ cording to date/time, company name/department or according to fault di‐...
Page 454 Service and diagnostics 18.7 Action log Channel status change NC/PLC states are logged via the information channel status. If this information can be obtained in a timely manner, in many cases these states can be used to verify the operation of the machine control panel.
Page 455 Service and diagnostics 18.7 Action log Procedure Select the "Start-up" operating area. Press the "HMI", "Diagnostics", and "Action log" softkeys The "Action Log Settings" window opens. Activate the "Logging on" checkbox to activate the action log. Check the relevant checkbox if you want to acquire particular events in the action log.
Page 456 Service and diagnostics 18.7 Action log Select the desired com file and press the "Open" softkey or double-click the file. Press the "Display new" softkey to update the display of events in the log (actual_actionlog.com). The entries made since the log file was called up are displayed. 18.7.3 Searching in the log files You can search for specific events in the log.
Page 457 Service and diagnostics 18.7 Action log The following logs are generated: ● action.com (binary file) ● action.log (ASCII file) ● crash.com (binary file) ● crash.log (ASCII file) Requirement The relevant log file is open. Procedure Press the "Save log" softkey. The log is stored in the "HMI data/Logs/Alarm logs"...
Page 458 Service and diagnostics 18.7 Action log Entry Description PLC_CRASH Entry of a PLC crash KEY_PRESSED Entry of a keystroke KEY_HOLD Entry of a key hold KEY_RELEASED Entry of a key released ALARM_ON Entry of an incoming alarm event See below "Alarm display"...
Page 459 Service and diagnostics 18.7 Action log Alarm display ALARM Date/time Deletion criterion Text DETAILS Entry Description ALARM Type of alarm: ALARM_ON, ALARM_OFF, ALARM_ACK Date/time Data and time of the event Alarm number Deletion criterion: Information as to how the alarm was acknowledged AUTOMATIC Automatic acknowledgement POWER ON...
Page 460 Service and diagnostics 18.8 HMI trace Procedure 1. You can copy a sample configuration file "actlog.ini" from the following directory: /siemens/ sinumerik/hmi/template/cfg. 2. Save or create the file in the /oem/sinumerik/hmi/cfg or /user/sinumerik/hmi/cfg directory. 3. Open the file and after "; ActionLogSize=", enter the file size (in bytes).
Page 461 Service and diagnostics 18.9 PROFIBUS diagnosis 4. Start the trace by activating the checkbox or from any place on the user interface with the following key combination: <Alt> + <T> on the operator panel <Alt> + <Shift> + <T> on an external keyboard The following icon is displayed at the top right in the header to show that a trace is active: 5.
Page 462 Service and diagnostics 18.9 PROFIBUS diagnosis Display Meaning/information Status Bus status POWER_ON (0): State after the control has been switched on OFFLINE (1): Basic initialization has been performed STOP (2): Start in accordance with the hardware configuration (SDB) CLEAR (3): PROFIBUS slaves have been parameterized and configured in accordance with the hardware configuration (SDB) and taken into the cyclic data exchange with zero output data OPERATE (4): Cyclic data exchange with the PROFIBUS slaves running...
Page 463 Service and diagnostics 18.9 PROFIBUS diagnosis Procedure Select the "Diagnostics" operating area. Press the "Menu forward" key and the "Bus TCP/IP" softkey. The "PROFIBUS Diagnostics" window is opened. If several PROFIBUS connections have been configured, press the "Bus -" or "Bus +" softkey to select the desired configuration. - OR - Press the "Select bus"...
Page 464 Service and diagnostics 18.10 Drive system Display Meaning/information Communication state Actual communication state of the slot If a value is not available for the NC axes, then the display remains hidden. Green: Slot used by the NC, communication active Red: Slot used by the NC, communication currently not active Gray: No NC axis Machine axis Display of the name defined in the machine data for this slot...
Page 465 Service and diagnostics 18.10 Drive system Display icon Meaning Gray The drive status could not be determined for this drive object. Special charac‐ Error when reading the data. ters Procedure Select the "Diagnostics" operating area. Press the menu forward key and the "Drive system" softkey. The "Drive System Diagnostics"...
Page 466 Service and diagnostics 18.10 Drive system ● Commissioning parameter filter – (p0009) – control unit The value of the "Device commissioning parameter filter" control unit parameter (p0009) is displayed. – (p0010) – further drive object The value of the "Drive object commissioning parameter filter" parameter (p0010) is displayed.
Page 467 Service and diagnostics 18.11 Remote diagnostics The "Drive System Diagnostics" window opens. Select the drive object for which you want to display further details. Press the "Details" softkey. The "Drive System Diagnostics - Details " window opens. The name of the drive object is displayed in the window header. Press the "Faults"...
Page 468 Service and diagnostics 18.11 Remote diagnostics ● Variable PingTransmissionInterval Duration in seconds after which send is repeated, e.g. PingTransmissionInterval = 15 ● Variable PingServerPor Port number of the Ping service with the manufacturer, e.g. PingServerPort=6201 18.11.2 Remote diagnostics via Teleservice adapter IE at X127 The following settings must be made for remote diagnostics via modem using a Teleservice adapter IE (TS Adapter) that is connected at X127.
Page 469 Service and diagnostics 18.11 Remote diagnostics Figure 18-2 Basic system with SINUMERIK Operate on PCU With the previously mentioned settings and the default values, in this configuration, remote diagnostics via TS Adapter is possible without any additional changes having to be made. When operating a SINUMERIK Operate on a PCU, the SINUMERIK Operate in the NCU must be switched off.
Page 470 Service and diagnostics 18.11 Remote diagnostics the remote access can be used and set at each station (SINUMERIK Operate in the NCU) individually for the station in conjunction with the relevant local PLC. Figure 18-4 System with several NCUs, several PCUs and a fixed modem The "Access MyMachine /P2P"...
Page 471 Service and diagnostics 18.12 Trace Meaning Operating rights for remote Only monitoring for re‐ control mote control Result Operating rights for remote Only monitoring for re‐ No remote control control mote control 18.12 Trace The trace provides you with an oscilloscope function that allows the following data (signals) to be graphically displayed: ●...
Page 472 Service and diagnostics 18.12 Trace Analyzing the result The following functions are available to analyze the result: ● Scaling characteristic graphs ● Zooming characteristic graphs ● Defining a characteristic range using markers 18.12.1 General procedure Sequence ● Create a trace session file as follows: –...
Page 473 Service and diagnostics 18.12 Trace 18.12.2 Trace session 18.12.2.1 Creating a session file Procedure Select the "Diagnostics" operating area. Press the menu forward key and the “Trace" softkey. Press the "Load trace" and "New" softkeys. The "New Session" window opens in which the "Session" name is rec‐ ommended.
Page 474 Service and diagnostics 18.12 Trace Procedure You have edited an active trace session. Press the "Store trace" softkey. The "Save Trace: Session ... " window opens and offers the following storage options. Activate the corresponding checkbox and press the "OK" softkey. The "Store Trace"...
Page 475 Service and diagnostics 18.12 Trace Precondition A session file of recorded traces is available. Procedure You have selected the "Trace" function. Press the "Load trace" softkey. The "Load Session File: Please Select File" window opens. Select the desired session file from the appropriate directory, e.g. "Trace", and press the "Display trace"...
Page 476 Service and diagnostics 18.12 Trace Filter: Display of the following variables: PLC variables PLC alarms Manufacturer-specific PLC alarm signals All (no filter) All variables in alphabetical order Inserting variables The start value for "Filter/Search" of variables differs. For example, to insert the variable $R[0], enter the following start value: ●...
Page 477 Service and diagnostics 18.12 Trace Directly enter the variable into the "Search" entry field. The cursor jumps to the term that is found. Press the "Delete search" softkey if you wish to terminate the search. Press the "Add" softkey to enter the required variable into a trace session. The "Variable Attributes"...
Page 478 Service and diagnostics 18.12 Trace Attributes Meaning Line type selection to display the characteristic graphs. ● No line ● Solid line ● Dashed line ● Dash-dot line ● Dash-dot-dot line ● Dotted line ● Stepped line XY ● Stepped line YX ●...
Page 479 Service and diagnostics 18.12 Trace Attributes Meaning ● Block start, type 1 or block end (all program levels, without intermediate blocks) ● Block start, type 2 or block end (all program levels, with intermediate blocks) ● Block start, type 3 or block end (all main programs, without intermediate blocks) ●...
Page 480 Service and diagnostics 18.12 Trace Attributes Meaning Bit mask In the case of an integer variable, a bit mask can be specified in this field. For a bit mask, the particular signal value is AND'ed before being displayed. After the mask has been applied, all of the selected bits are moved to the right so that it looks as if the bit or the bits all start with bit zero.
Page 481 Service and diagnostics 18.12 Trace 18.12.4 Trace settings 18.12.4.1 Trace settings (PLC, NC, servo) In the "Trace Settings (PLC, NC, Servo)" window, you define the conditions for starting and stopping the trace session. Condition for Start trace With "Start trace" softkey The recording is started immediately after pressing the "Start trace"...
Page 482 Service and diagnostics 18.12 Trace Condition for Start trace With "Start trace" softkey The recording is started immediately after pressing the "Start trace" softkey. If variable The recording is activated after pressing the "Start trace" softkey when the selected variable clearly satisfies the con‐ dition and the specified value.
Page 483 Service and diagnostics 18.12 Trace 18.12.4.3 Trace options You define the following properties of a trace session in the "Trace - Options" window. ● Setting the graphic window – Displaying main grid lines: You define whether a horizontal grid is displayed and in which color.
Page 484 Service and diagnostics 18.12 Trace Recording the trace session ● Manually starting and stopping a trace ● Starting and stopping recording using a trigger Procedure You have listed the desired variables for a trace section. Press the "Display trace" softkey. The "Trace"...
Page 485 Service and diagnostics 18.12 Trace ● Zoom – Increasing or decreasing the section ● Cursors: The cursor display provides functions that allow one, two or both curves to be precisely measured. – Cursor A – Cursor B – Both cursors –...
Page 486 Service and diagnostics 18.12 Trace Displaying a legend and selecting a variable A recording is opened in the "Trace" graphics window. Press the "Legend / selection" softkey. The graphic window is halved. The variables are displayed as comment and with checkbox in the left-hand section of the window. Activate or deactivate the required variable using the checkbox to display it as curve.
Page 487 Service and diagnostics 18.12 Trace Press the "Scale +" or "Scale -" softkey until the desired scaling is reached. - OR - Enter the scaling values directly into the input window and select the ap‐ propriate property. Press the "Scale" softkey to save the settings. - OR - Press the "Adapt selected"...
Page 488 Service and diagnostics 18.12 Trace - OR - Press the "Individually adapt Y" or "Adapt all" softkey if you only wish to scale the Y value axis in the graphic window. - OR - Press the "Adapt Y together" softkey if you wish to adapt the value axis of all characteristic graphs to the graphic window.
Page 489 Service and diagnostics 18.12 Trace Position "(A)" at the position on the curve where you wish to start the measurement. The coordinates are specified in a tooltip and in the status line. Press the "Cursor B" softkey. The reference number, color of the variables as well as the color of the coordinate crossing point are also displayed on this softkey.
Page 490 Service and diagnostics 18.13 PROFIBUS/PROFINET and AS-i bus diagnostics If you press the "Peaks" softkey, the cursor only goes to the peak-peak values. If you press the "Minimum" softkey, the cursor only goes to the peak-valley values. 18.13 PROFIBUS/PROFINET and AS-i bus diagnostics 18.13.1 PROFIBUS/PROFINET With the PROFIBUS/PROFINET diagnostics, you obtain a quick overview from which, when...
Page 491 PROFIBUS address data Additional information for the second version PROFIBUS/PROFINET module or channel diagnostics Device diagnostics For Siemens DP/DP coupler and diagnostics repeater Additional diagnostic information for the third version Name Module designation from the HMI offline data Name Module name from the HMI offline data Order no.
Page 492 Service and diagnostics 18.13 PROFIBUS/PROFINET and AS-i bus diagnostics Press the "Available devices" softkey to display the diagnostics data of the available modules. - OR - Press the "Suppressed devices" softkey to display the diagnostics data of the suppressed modules. - OR - Press the "Failed devices"...
Page 493 Service and diagnostics 18.13 PROFIBUS/PROFINET and AS-i bus diagnostics Entry Description 1. Entry [SKO_Index0] Type ID of the AS-i component (refer above) DiagType= 6 Designation of the AS-i component, which should be TypeSection=DP-AS-i-Link- output in the selection list Advanced 1 E address of the AS-i component from the hardware Logical_Address=43 configuration...
Page 494 TypeSection=DP-AS-i-Link-Advanced Logical_Address=75 RequestDB=449 Procedure 1. Copy the "sltlprodiaghmi.ini" file from the /siemens/sinumerik/hmi/template/cfg directory. 2. Place the file in the directory: /oem/sinumerik/hmi/cfg or /user/sinumerik/hmi/cfg. If the file is already available in the directory, then just supplement this by the corresponding entries.
Page 495 Service and diagnostics 18.14 Backing up log data for service case Flags acc. to the AS-i specification Description Operating mode Operating mode state Auto.-Addr.progr. executed Automatic address assignment executed Auto-Addr.progr. possible Automatic address assignment possible AS-i slave with addr.=0 available Slave with address 0 available Reference config.
Page 496 This function collects all available LOG files of the operating software and stores them as a ZIP file in the following directory: C:\Program Files(x86)\Siemens\MotionControl\user\sinumerik\didac\out_<Date-Time>.zip In there is a problem with the system, you can send the ZIP file to the SINUMERIK hotline to help with the analysis of the problem.
Page 497 OEM-specific online help 19.1 Overview In addition to the existing extensive online help, you also have the option of generating a manufacturer-specific online help and then linking this into SINUMERIK Operate. This online help is generated in the HTML format, i.e. it comprises HTML documents that are linked with one another.
Page 498 OEM-specific online help 19.2 Generating HTML files 19.2 Generating HTML files Generating help files in the HTML format. It is possible to save all information in a single HTML file or to distribute the information over several HTML files. You can assign the file names yourself, however, you must observe the following: ●...
Page 499 OEM-specific online help 19.2 Generating HTML files Description Comment Horizontal line Supported attributes: width (can be specified as absolute or relative value) html HTML document Italic Image Supported attributes: src, width, height User-entered text meta Meta-information List item nobr Non-breakable text Ordered list The standard attributes for lists are supported Paragraph...
Page 500 OEM-specific online help 19.2 Generating HTML files Standard attributes for lists The following attributes are supported by tags ol and ul: ● type (1, a, A, square, disc, circle) Standard attributes for tables The following attributes are supported by tags td and th: ●...
Page 501 OEM-specific online help 19.3 Generating the help book Supported CSS selectors All CSS 2.1 selector classes are supported with the exception of so-called pseudo selector classes such as :first-child, :visited and :hover. 19.3 Generating the help book The help book is an XML file in which the structure of the online help is defined. In this file, you define: ●...
Page 502 OEM-specific online help 19.3 Generating the help book Example for a help book In the following example, the structure of a help book with the "My Help" name is described. Further, it forms the basis for the table of contents and subject index. <?xml version="1.0"...
Page 503 OEM-specific online help 19.4 Integrating the online help in SINUMERIK Operate You have the following three options to format the subject index: 1. Single entry: <INDEX_ENTRY ...title="index"/> 2. Two two-stage entry, whereby each title has a main and a subentry. Separate the entries from one another using a comma.
Page 504 OEM-specific online help 19.4 Integrating the online help in SINUMERIK Operate Num‐ Meaning III -DisableSearch Disable the subject (keyword) search for the help book. Attributes: 0, 1 value true, false type type, data type of the value (bool) III-DisableFullTextSearch Disable the full text search for the help book. Attributes: value true, false...
Page 505 When displaying the list of contents and subject index of a help book, the help files are saved in the binary format (slhlp_<Hilfe-Buch_*.hmi) under the directory /siemens/ sinumerik/sys_cache/hmi/hlp for faster use. If you change the help book, you must always delete these files.
Page 506 3. Place the files in the corresponding language directories. For instance, place the file for the German help text in the following directory: /oem/sinumerik/hmi/hlp/deu/ sinumerik_alarm_plc_pmc/sinumerik_alarm_oem_plc_pmc.html 4. Delete the file "slhlp_sinumerik_alarm_plc_pmc_*.hmi" in the /siemens/sinumerik/ sys_cache/hmi//hlp directory and restart the operating software. "sinumerik_alarm_oem_plc_pmc.html" file...
Page 507 OEM-specific online help 19.6 Generating online help for user alarms and machine data Distribute the online help for user alarms over several HTML files You have the option of distributing the online help for user alarms over several HTML files. 1.
Page 508 OEM-specific online help 19.6 Generating online help for user alarms and machine data Directory for HTML files Area Directory PLC alarms /oem/sinumerik/hmi/hlp/<lng>/sinumerik_alarm_plc_pmc/ or /user/sinumerik/hmi/hlp/<lng>/sinumerik_alarm_plc_pmc/ HMI alarms /oem/sinumerik/hmi/hlp/<lng>/sinumerik_alarm_hmi/ or /user/sinumerik/hmi/hlp/<lng>/sinumerik_alarm_hmi/ NC alarms /oem/sinumerik/hmi/hlp/<lng>/sinumerik_alarm_nck/ or /user/sinumerik/hmi/hlp/<lng>/sinumerik_alarm_nck/ NC MD /oem/sinumerik/hmi/hlp/<lng>/sinumerik_md_nck/ Channel MD /oem/sinumerik/hmi/hlp/<lng>/sinumerik_md_chan/ Axis MD /oem/sinumerik/hmi/hlp/<lng>/sinumerik_md_axis/ <lng>...
Page 509 OEM-specific online help 19.7 Example: This is how you create an online help for NC/PLC variables 19.7 Example: This is how you create an online help for NC/PLC variables Overview In order to create context-sensitive online help for NC/PLC variables or system variables as shown in the following example, the descriptive texts are managed in language-dependent html files.
Page 510 2. Copy the html files to one of the following directories: /oem/sinumerik/hmi/hlp/<lng>/ /user/sinumerik/hmi/hlp/<lng>/ <lng> stands for the language code. 3. Delete all files in the directory: /siemens/sinumerik/sys_cache/hmi//hlp The settings become effective only after restarting the system. SINUMERIK Operate (IM9) Commissioning Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 511 OEM-specific online help 19.8 Example: This is how you create a programming online help 19.8 Example: This is how you create a programming online help Preconditions Create the following files: ● Configuration file "prog_help.ini" [milling] CYCLE1=cycle1_help.html CYCLE2=cycle2_help.html#TextAnchor1 CYCLE3=cycle3_help.html CYCLE4=cycle4_help.html [turning] CYCLE3=cycle2_help.html CYCLE4=cycle3_help.html ●...
Page 512 OEM-specific online help 19.8 Example: This is how you create a programming online help ● Language-dependent file "<prog_help_eng>.ts": this filename is permanently specified. <?xml version="1.0" encoding="utf-8" standalone="yes"?> <!DOCTYPE TS> <TS> <context> <name>oem_cycles</name> <message> <source>CYCLE1</source> <translation>short description for cycle 1</translation> <chars>*</chars> </message>...
Page 513 OEM-specific online help 19.9 Help files in PDF format 19.9 Help files in PDF format In addition to help files in HTML format, you can also include PDF-format information in the operating software. Individual PDF helps can be opened with links from the table of contents or index, or directly from HTML files.
Page 514 OEM-specific online help 19.9 Help files in PDF format SINUMERIK Operate (IM9) Commissioning Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 515 SINUMERIK Integrate - AMB, AMC, AMM Precondition To start the "SINUMERIK Integrate - AMB, AMC, AMM" software, configure a softkey using a display machine data. To do this you require, as a minimum, authorization for access level 3 (user). Configuring a softkey MD9108 $MM_SINUMERIK_INTEGRATE The "SINUMERIK integrate"...
Page 516 SINUMERIK Integrate - AMB, AMC, AMM SINUMERIK Operate (IM9) Commissioning Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 517 Technologies and cycles 21.1 Activating turning/milling/drilling/grinding technologies The cycles are automatically loaded when the controller boots (Power On). The configuration is realized using cycle machine data and cycle setting data. In so doing, a differentiation is made between the following data: ●...
Page 518 Technologies and cycles 21.1 Activating turning/milling/drilling/grinding technologies Adapting the user interface The softkey display for the selection of the cycle support in the program editor is set using the following channel-specific configuration machine data: MD52200 $MCS_TECHNOLOGY Technology Setting for turning Setting for milling Setting for the cylindrical grinding technology Setting for the surface grinding technology...
Page 519 Technologies and cycles 21.1 Activating turning/milling/drilling/grinding technologies Setting the coordinate system MD52000 $MCS_DISP_COORDINATE_SYSTEM Position of the coordinate system Default setting With this machine data you adapt the position of the coordinate system of the user interface to the coordinate system of the machine. In the user interface, all help screens, sequence graphics, simula‐ tions, and input fields with circle direction indication change automatically according to the selected position.
Page 520 Technologies and cycles 21.1 Activating turning/milling/drilling/grinding technologies Meaning of the axes MD52206 $MCS_AXIS_USAGE[n] Meaning of the axes in the channel [n] channel axis number No special meaning Tool spindle (rotating tool) Auxiliary spindle (rotating tool) Main spindle (turning) Separate C axis of the main spindle (turning) Counterspindle (turning) Separate C axis of the counterspindle (turning) Linear axis of the counterspindle (turning)
Page 521 Technologies and cycles 21.1 Activating turning/milling/drilling/grinding technologies "Easy" input in cycle support You can influence the number of visible input parameters via MD52210 $MCS_FUNCTION_MASK_DISP with bit 9: ● All input parameters are displayed with the default setting bit 9 = 0 for "Complete". ●...
Page 522 Technologies and cycles 21.2 Technology cycles for drilling Additional settings MD52005 $MCS_DISP_PLANE_MILL Plane selection G17, G18, G19 Milling: Plane selection in the cycle support when programming under "programGUIDE G code" = 17 G17 plane (default value) = 18 G18 plane = 19 G19 plane MD52006 $MCS_DISP_PLANE_TURN...
Page 523 Technologies and cycles 21.2 Technology cycles for drilling SD55216 $SCS_FUNCTION_MASK_DRILL_SET Drilling function screen form Bit 1 Boring CYCLE86: Take into account the rotation of the tool plane when positioning the spindle Note: Spindle direction of rotation M3/ M4 and direction of rotation of the rotary axes must be set according to DIN.
Page 524 Technologies and cycles 21.3 Manufacturer cycles SD55482 $SCS_DRILL_TAPPING_SET_GG21[0] Setting tapping G group 21: Acceleration behavior Acceleration behavior as before the cycle call (default value). SOFT BRISK DRIVE SD55483 $SCS_DRILL_TAPPING_SET_GG24[0] Setting tapping G group 24: Precontrol Precontrol, the same as before the cycle call (default value). FFWON FFWOF Tapping (CYCLE84)
Page 525 Technologies and cycles 21.3 Manufacturer cycles PROG_EVENT.SPF Standard cycle to support the following functions: ● Block search when milling or turning is activated ● Block search and swivel plane ● Block search and align / advance tool Note MD52212 $MCS_FUNCTION_MASK_TECH bits 3, 5 and 15 ... 17. CUST_T Cycle is used to track the T preparation after SERUPRO.
Page 526 Technologies and cycles 21.3 Manufacturer cycles Example In the following example, the simulation mode in PROG_EVENT or CYCPE1MA.SPF is stopped by the PLC access: N100 REPEAT N110 UNTIL PLC_VAR <> 0 If you use the system variable $P_SIM, then PLC access in the simulation mode is prevented: N099 IF NOT $P_SIM N100 REPEAT N110 UNTIL PLC_VAR <>...
Page 527 Technologies and cycles 21.3 Manufacturer cycles 21.3.4 Manufacturer cycle for tool change CUST_T and CUST_M6 Function The two cycles are used to track the T preparation (CUST_T) and the tool change (CUST_M6) according to SERUPRO. In so doing, depending on the specific tool holder, the following is output: ●...
Page 528 Technologies and cycles 21.3 Manufacturer cycles T replacement cycle If a T replacement cycle is being used, then the following note must be observed: Note The CUST_T cycle uses the language command TCA (ToolChangeAbsolut) for the T call and therefore also has the possibility of inserting tools that have been disabled. However, this language command cannot be substituted.
Page 529 Technologies and cycles 21.3 Manufacturer cycles Adapt manufacturer cycle CUST_TECHCYC.SPF You can execute the following actions with the aid of the _MODE parameter: Marker Action Main spindle: Changeover to C axis mode Changeover to spindle mode Clamp C axis Release C axis clamping Rinse chuck Close chuck Open chuck when spindle is stationary...
Page 530 Technologies and cycles 21.3 Manufacturer cycles Marker Action _M100 Drawer: Position before cut-off _M101 Open during cut-off _M102 Close after cut-off _M103 Cut-off completed _M110 Tool change _M111 After end of tool change cycle (with tool change) _M112 Before tool change on retraction plane _M113 Before cutting edge reselection _M114...
Page 531 Technologies and cycles 21.4 Milling Marker Action _M231 Start of program (ShopMill program) _M232 End of program header (ShopMill program) _M235 End of program loop (ShopMill program) _M236 End of program (ShopMill program) _M300 Boring CYCLE86 Adapt the spindle to the tool position (SD55216 $SCS_FUNCTION_MASK_DRILL_SET bit 6 = 1) For specific machine kinematics, it may be necessary to make an additional adjustment of the correction angle for the spindle positioning (e.g.
Page 532 Technologies and cycles 21.4 Milling 21.4.2 Technology cycles for milling Milling function screen SD52214 $SCS_function_MASK_MILL Milling function screen Bit 0 Enable cylinder surface transformation (ShopMill) Bit 1 List table to accept blank (on milling machines) (This bit only has to be set, if the machine has a rotary axis and a fixed table for accepting the blank.) Bit 2 reserved...
Page 533 = 10000 21.4.3 Setting-up ShopMill cycles for milling Load ShopMill cycles for milling When the control boots, the ShopMill cycles are automatically loaded into the following directory: ../siemens/sinumerik/cycles/sm/prog Setting the coordinate system MD52000 $MCS_DISP_COORDINATE_SYSTEM Position of the coordinate system Examples:...
Page 534 Technologies and cycles 21.4 Milling Simulation and simultaneous recording In order that simulation and simultaneous recording are displayed without any errors, set the machine data as described in the following section: Setting the technology for simulation (Page 139) Defining the direction of rotation In order that the direction of rotation is correctly displayed in the ShopMill user interface, and when programming ShopMill functions, the correct direction of rotation is executed, you must make some settings that are coordinated with one another.
Page 535 Technologies and cycles 21.4 Milling = 1 Tapping also possible without encoder Bit 3 Constant cutting speed referred to the diameter of the centering = 0 Constant cutting speed referred to the diameter of the tool = 1 Constant cutting speed referred to the diameter of the centering MD52229 $MCS_ENABLE_QUICK_M_CODES Enable fast M commands Bit 0...
Page 536 Technologies and cycles 21.4 Milling Channel-specific cycle setting data SD55212 $SCS_FUNCTION_MASK_TECH_SET Cross-technology function screen Bit 0 Tool preselection active. The next tool is prepared directly after a tool change. Note: For a revolver, the setting data must be set to "0". Bit 1 Automatic calculation of the thread depth for metric threads.
Page 537 Technologies and cycles 21.4 Milling There are two variants of cylinder surface transformation, i.e. 1. with groove side offset (ON) 2. without groove side offset (OFF) Figure 21-1 Grooves with and without groove side offset 21.4.5 Example: Milling machine with the XYZ-AC axis configuration Example: Milling machine with the XYZ-AC axis configuration Example of an axis configuration on the following machine: SINUMERIK Operate (IM9)
Page 538 Technologies and cycles 21.4 Milling Axis configuration 1st axis of the machining plane parallel to the rotary axis 2nd axis of the machining plane Infeed axis (tool axis) perpendicular (radial) to the rotary axis Rotary axis Working spindle Figure 21-2 Machining slots on a cylinder surface with X-A-Z kinematics You must configure two data sets with the following machine data for the machine illustrated above:...
Page 539 Technologies and cycles 21.4 Milling General settings for the transformation MD10602 $MN_FRAME_GEOAX_CHANGE_MODE Frames when switching over geometry screens The actual total frame (zero offsets) is recalculated when switching over geometry axes (se‐ lecting - deselecting TRACYL). Data set for the 1st transformation in the channel MD24100 $MC_TRAFO_TYPE_1 Definition of transformation 1 in the chan‐...
Page 540 Technologies and cycles 21.4 Milling Data set for the 2nd transformation in the channel MD24200 $MC_TRAFO_TYPE_2 = 513 Transformer type (513 = cylinder surface transformation with groove side offset) MD24210 $MC_TRAFO_AXES_IN_2 [0] = 3 Channel axis: Infeed axis perpendicular (radial) to rotary axis [1] = 4 Channel axis: Rotary axis [2] = 1...
Page 541 Technologies and cycles 21.4 Milling 21.4.6 ShopMill cycles for multiple clamping Software options You require the following software option in order to use this function: "ShopMill/ ShopTurn" Function The Multiple clamping function provides optimized tool change over several workpiece clampings. On the one hand, this reduces downtimes and, on the other, eliminates tool change times because a tool performs as many machining operations as possible in all clampings before the next tool change is initiated.
Page 542 Technologies and cycles 21.4 Milling Figure 21-3 Rotating clamping device (reversible clamping device) The cycle CLAMP.SPF must be adapted as follows: DEF INT _NV ; Auxiliary variable ;–––––––––––––––––––––––––––––––––––– ;Adaptation IF _ACT==1 G0 A=DC(0) ENDIF IF _ACT==2 G0 A=DC(90) ENDIF IF _ACT==3 G0 A=DC(180) ENDIF IF _ACT==4...
Page 543 Technologies and cycles 21.5 Turning ;–––––––––––––––––––––––––––––––––––– _NV=_NPV+_ACT ; Calculate current zero offset N10 G[8]=_NV ; There must not be a calculation here 21.5 Turning 21.5.1 General All settings for machine and setting data of the standard cycles are also applicable for milling under ShopMill and turning under ShopTurn.
Page 544 Technologies and cycles 21.5 Turning Bit 6 Enable balance cutting for two-channel stock removal Bit 7 Retraction when cutting along the contour with G1 Bit 8 Enter the spindle chuck data in the program Bit 9 Additional input of the tailstock data in the program Bit 10 Enable crowned thread Bit 12...
Page 545 Technologies and cycles 21.5 Turning As a result, the following setting options are obtained for the main spindle: Main spindle direction of rotation 52207[n] 52207[n] 52207[n] DB31, ... bit 3 = bit 4 = *) bit 5 = DBX17.6 Note MD52207[n] bit 4 = *) Bit 4 can be set from the operator's view (values as specified) or according to DIN ("0"...
Page 546 Technologies and cycles 21.5 Turning Stop dimensions Jaw dimensions MD53241 $MAS_SPINDLE_CHUCK_TYPE[ ] Spindle jaw type Clamping, outer Clamping, inner Additional settings The M code, e.g. M34 or M1 = 34 for the spindle chuck is defined in the following machine data.
Page 547 Technologies and cycles 21.5 Turning Rounding the contour SD55582 $SCS_TURN_CONT_TRACE_ANGLE Contour turning: Minimum angle for rounding the contour Specifies the angle between the cutting edge and contour, above which for contour turning, the contour is rounded in order to remove residual material (default value). SD 55218 $SCCS_FUNCTION_MASK_TURN_SET Turning function screen Bit 3...
Page 548 Technologies and cycles 21.5 Turning Bit 4 If you have implemented the "Clamp/release spindle" function using the manufacturer cycle CUST_TECHCYC.SPF, then using this machine data, you can activate the "Clamp/ release spindle" parameter in the drilling and milling screens. = 0 The "Clamp/release spindle" parameter is not displayed in the drilling and milling screens. ShopTurn automatically clamps the spindle if it makes sense for the particular machining operation.
Page 549 Technologies and cycles 21.5 Turning SD55505 $SCS_TURN_ROUGH_O_RELEASE_DIST Retraction distance for stock remov‐ al during external machining Specifies the distance, by which the tool is retracted from the contour when removing stock from an outer corner. This does not apply to stock removal at a contour (default value). = -1 The distance is internally defined.
Page 550 Technologies and cycles 21.5 Turning You set the direction of rotation of an NC rotary axis via MD32100 $MA_AX_MOTION_DIR. MD32100 $MA_AX_MOTION_DIR Traversing direction (not control direction) Direction reversal 0, 1 No direction reversal Defining the direction of rotation You set the directions of rotation for the user interface in the following machine data: MD52207 $MCS_AXIS_USAGE_ATTRIB[n] Attributes of the axes in the channel [n] channel axis number...
Page 551 Technologies and cycles 21.5 Turning Counterspindle direction of rotation 52207[n] 52207[n] 52207[n] DB31, ... bit 3 = bit 4 = *) bit 5 = DBX17.6 Note MD52207[n] bit 4 = *) Bit 4 can be set from the operator's view (values as specified) or according to DIN ("0" and "1" are then interchanged).
Page 552 Technologies and cycles 21.5 Turning 21.5.5 Setting up the counterspindle under ShopTurn Software option You require the following software option in order to use the counterspindle on your machine: "Generic coupling 'CP-STATIC'" or higher The position to which the counterspindle travels when the program starts is defined in the following channel-specific cycle setting data: SD55232 $SCS_SUB_SPINDLE_REL_POS Retraction position Z for counterspindle...
Page 553 Technologies and cycles 21.5 Turning If, however, the specified force is reached during the cut-off check (i.e. travel to fixed stop is successful), alarm 61255 "Error during cut-off: Tool break?" is issued. Note The "Travel to fixed stop" function can also be used when gripping the spindle (see above). If travel to fixed stop does not succeed when gripping, an alarm will of course still be issued.
Page 554 Technologies and cycles 21.5 Turning SD55510 $SCS_TURN_GROOVE_DWELL_TIME Dwell time, which is necessary between grooving and retracting for grooving technol‐ ogy. Tool clearance time during grooving at the base. = > 0 Dwell time in seconds = < 0 Dwell time in spindle revolutions SD55580 $SCS_TURN_CONT_RELEASE_ANGLE Angle, through which the tool is lifted from the contour for contour turning, roughing.
Page 555 Technologies and cycles 21.5 Turning SD55583 $SCS_TURN_CONT_VARIABLE_DEPTH Percentage of the changing cutting depth when turning a contour You can select changing the cutting depth for stock removal and for removing residual material. = 20 20% variable cutting depth SD55584 $SCS_TURN_CONT_BLANK_OFFSET Safety clearance when avoiding obstacles, to avoid collisions during approach or retrac‐...
Page 556 Technologies and cycles 21.5 Turning SD55587 $SCS_TURN_CONT_MIN_REST_MAT_AX1 Limit value during contour turning for removal of residual material in the di‐ rection of axis 1 (for G18 Z). This also applies to residual machining – stock removal, grooving and plunge turning. The roughing step for residual machining is not executed, if the material to be removed is less than 50% of the finishing allowance.
Page 557 Technologies and cycles 21.5 Turning Distance to the last cut, SD55595 Retraction between plunge-cutting and stock removal, SD55596 As the tool bends during plunge turning, the tool would make an excessively deep cut during stock removal. The retraction distance of the tool between plunge-cutting and stock removal is specified in the following channel-specific cycle setting data: SD55596 $SCS_TURN_CONT_TURN_RETRACTION Retraction depth before turning...
Page 558 Technologies and cycles 21.5 Turning Lathe with X and Z axes, main and tool spindle For example, for a lathe with X and Z axes, main spindle (C1) and tool spindle (WZ), you can configure the following channel-specific machine data: MD20080 $MC_AXCONF_CHANAX_NAME_TAB[ ] Channel axis name in the channel [0] = XC...
Page 559 Technologies and cycles 21.5 Turning Setting up General settings for cylinder transformation MD10602 $MN_FRAME_GEOAX_CHANGE_MODE Frames when switching over geometry ax‐ The actual total frame (work offsets) and when switching over geometry axes (selecting - deselecting TRACYL) is recalculated. MD24040 $MC_FRAME_ADAPT_MODE Adapting the active frames.
Page 560 Technologies and cycles 21.5 Turning [1] = 3 Rotary axis (main spindle) C1 [2] = 2 Parallel to the rotary axis ZC MD24320 $MC_TRAFO_GEOAX_ASSIGN_TAB_3[ ] Assignment of geometry axes to channel axes for transformation 3. [0] = 1 1st channel axis X [1] = 3 2nd channel axis Y [2] = 2...
Page 561 Technologies and cycles 21.5 Turning Cylinder surface transformation with groove side offset MD24300 $MC_TRAFO_TYPE_3 Definition of the 3rd transformation in the channel. = 513 TRACYL main spindle MD24310 $MC_TRAFO_AXES_IN_3[ ] Axis assignment for transformation 3. [0] = 1 Perpendicular to the rotary axis XC [1] = 3 Rotary axis (main spindle) C1 [2] = 2...
Page 562 Technologies and cycles 21.5 Turning 21.5.9 End face machining (TRANSMIT) Software option You require the following software option in order to use this function: "Transmit and peripheral surface transformation" Function Using the end face machining function (TRANSMIT), you can machine the end face of a turned part.
Page 563 Technologies and cycles 21.5 Turning MD24905 $MC_TRANSMIT_ROT_AX_FRAME_1 Axial offset of the rotary axis is taken into account during TRANSMIT 1. MD24910 $MC_TRANSMIT_ROT_SIGN_IS_PLUS_1 Sign of the rotary axis for the 1st TRANSMIT transformation. MD24911 $MC_TRANSMIT_POLE_SIDE_FIX_1 Limitation of working range in front of/behind the pole, 1st TRANSMIT. MD24920 $MC_TRANSMIT_BASE_TOOL_1[ ] Vector of the base tool for the 1st TRANS‐...
Page 564 Technologies and cycles 21.5 Turning MD24910 $MC_TRANSMIT_ROT_SIGN_IS_PLUS_1 Sign of the rotary axis for the 1st TRANSMIT transformation. MD24911 $MC_TRANSMIT_POLE_SIDE_FIX_1 Limitation of working range in front of/behind the pole, 1st TRANSMIT. MD24920 $MC_TRANSMIT_BASE_TOOL_1[ ] Vector of the base tool for the 1st TRANS‐ MIT transformation.
Page 565 Technologies and cycles 21.5 Turning = 0 The "Clamp/release spindle" parameter is not displayed in the drilling and milling screens. ShopTurn automatically clamps the spindle if it makes sense for the particular machining operation. = 1 The "Clamp/release spindle" parameter is displayed in the drilling and milling screens. The operator decides for which machining operation the spindle should be clamped.
Page 566 Technologies and cycles 21.5 Turning Inclined axis under ShopTurn Please also note the following: Note In the user interface, the inclined axis function is automatically integrated in the cycles after setting up. For machining with inclined axis, in the screen forms of the machining plane, you can select "Face Y"...
Page 567 Technologies and cycles 21.5 Turning MD20144 $MC_TRAFO_MODE_MASK Bit 0 = 1 TRAANG runs in the background (persistent) and is not shown on the user interface. MD20070 $MC_AXCONF_MACHAX_USED[4] Channel axis YC = 5th machine axis. MD20080 $MC_AXCONF_CHANAX_NAME_TAB[ ] Name of channel axis in the channel. [0] = XC 1st channel axis XC [1] = ZC...
Page 568 Technologies and cycles 21.5 Turning MD24444 $MC_TRAFO_GEOAX_ASSIGN_TAB_6[ ] Assignment of geometry axes to channel axes for transformation 6. [0] = 1 1st axis = channel axis XC [1] = 3 2nd axis = channel axis YC [2] = 2 3rd axis = channel axis ZC MD24995 $MC_TRACON_CHAIN_1[ ] Transformation linking [0] = 1...
Page 569 Technologies and cycles 21.6 Grinding For further information about speed limitation, please refer to: References ● Programming Manual Fundamentals, Section "Spindle motion" > "Programmable spindle speed limitation (G25, G26)" ● Programming Manual Job Planning, Section "Flexible NC programming" > "Variables" > "Redefinition of system data, user data, and NC commands (REDEF)"...
Page 570 Technologies and cycles 21.6 Grinding Oscillation cycles: Activate GUD variables for synchronized actions MD18661 $MN_MM_NUM_SYNACT_GUD_INT[n] Number of configurable integer-type GUD variables > 0 With the machine data, the individual GUD blocks can be extended by additional channel- specific parameter areas of the type integer. [n] is equivalent to the access rights data block References For further information about oscillating cycles and GUD variables for synchronized actions,...
Page 571 Technologies and cycles 21.6 Grinding Display fit-dependent corrections in the operating area "Parameters" → "Work offsets" window: MD52211 $MCS_FUNCTION_MASK_DISP_ZOA Function screen Display overview of work offsets Bit 22 Display fit-dependent corrections ($P_GFRAME) Details of disk size MD52842 $MCS_GRIND_DIAMETER_LENGTH Number of the tool length for the disk diameter = 1 Length 1 is disk diameter = 2 Length 2 is disk diameter...
Page 572 Technologies and cycles 21.7 Swiveling 21.7 Swiveling 21.7.1 Technology cycles for swiveling Requirement The commissioning of the machine kinematics is a mandatory requirement for correct swiveling functionality (CYCLE800). The vectors of the machine kinematics are stored in the tool parameters $TC_CARR1 to $TC_CARR65. Note The vectors of the machine kinematics can be determined with the "Measure kinematics"...
Page 573 Technologies and cycles 21.7 Swiveling References ● "siemensd.txt" file in the supplied software (standard cycles) ● Function Manual Basic Functions; W1: Tool offset Section: "Tool holder with orientation capability" > "Oblique machining with 3 + 2 axes" ● Programming Manual, measuring cycles: CYCLE996 Activating the swivel function The swivel function is enabled on the user interface via the following channel-machine data: MD52212 $MCS_FUNCTION_MASK_TECH...
Page 574 Technologies and cycles 21.7 Swiveling = 0 With direction selection + or -, both calculated solutions for the rotary axes are approached = 1 With direction selection + or -, only one of the calculated solutions for the rotary axes is approached Bit 8 Traverse the zero offset for the rotary axes of the swivel data set as offset...
Page 575 Technologies and cycles 21.7 Swiveling Additional settings For the swivel function, set the following machine data as a minimum to the following - although this deviates from the default value: MD10602 $MN_FRAME_GEOAX_CHANGE_MODE The actual total frame (zero offsets) is recalculated when switching over geometry axes (selecting/deselecting TRAORI).
Page 576 Technologies and cycles 21.7 Swiveling Using angular tools Angular tools are created and managed in the NC with tool type 130. The tool lengths are entered in the tool of tool type 130. If an angular tool is also used on a swiveled machining plane (CYCLE800), the basic tool orientation must be enabled with MD18114 $MM_ENABLE_TOOL_ORIENT = 2.
Page 577 Technologies and cycles 21.7 Swiveling Note If, after a RESET from the NC, a frame must be calculated in the tool direction, then MD20150 $MC_GCODE_RESET_VALUES[52] can be set to a value > 1. Applications: ● Machine kinematics with Hirth joint ●...
Page 578 Technologies and cycles 21.7 Swiveling MD21186 $MC_TOCARR_ROT_OFFSET_FROM_FR Offset of the rotary axes for a tool holder with orientation capability from the zero offset of the rotary axis. In CYCLE800, the WCS is recalculated when there is a value in the zero offset (ZO) of the rotary axes.
Page 579 Technologies and cycles 21.7 Swiveling MD24007 $MC_CHSFRAME_RESET_CLEAR_MASK Clear system frames after RESET Bit 4 System frame workpiece reference = 0 Do not delete = 1 Delete When used for measuring or swiveling in JOG, the workpiece reference must be active at RESET and not cleared (cascaded measuring).
Page 580 Technologies and cycles 21.7 Swiveling Bit 3 = 1 Tool reference ($P_TOOLFRAME) Bit 4 = 1 Workpiece reference ($P_WPFRAME) MD28085 $MC_MM_LINK_TOA_UNIT Assigning a TO unit to a channel (SRAM) If several channels are set-up, then the following can be set in the machine data: Assignment of the TO units (tools and orientable tool holders) to the NC channel.
Page 581 Technologies and cycles 21.7 Swiveling Swiveling in the JOG mode Cycle alarms 62186 and 62187 can be hidden or displayed using the following cycle machine data: MD55410 $MC_MILL_SWIVEL_ALARM_MASK Activate fault evaluation CYCLE800 Bit 0 Activate fault 61186 = 0 Hide fault 61186 "Active zero offset G%4 and base (base reference) contains rotations" (default setting).
Page 582 Technologies and cycles 21.7 Swiveling 21.7.3 Commissioning swivel data (machine kinematics) Defining a swivel data set You must create a swivel data set for every swivel head, swivel table or each combination of both. Swivel data sets can be declared in several channels. A swivel data set comprises the parameters $TC_CARR1[n] to $TC_CARR65[n] n = number of the swivel data set.
Page 583 Technologies and cycles 21.7 Swiveling Kinematic types $TC_CARR23[n] Swivel head (type T) Swivel table (type P) Swivel head + Swivel table (type M) Offset vector I1 Offset vector I2 Offset vector I1 Rotary axis vector V1 Rotary axis vector V1 Rotary axis vector V1 Offset vector I2 Offset vector I3...
Page 584 Technologies and cycles 21.7 Swiveling Name of the swivel data set Figure 21-4 Dialog to input parameters for the swivel data set If several swivel data sets are declared in each NC channel, then a name is assigned to each swivel data set: $TC_CARR34[n] No name needs to be specified if the swivel-mounted tool holder is not exchangeable (i.e.
Page 585 Technologies and cycles 21.7 Swiveling Manually adjustable rotary axes (manual mode) are possible with and without measuring systems and can be used with "simple machines". Rotary axes that are positioned by an additional mechanical system, can be declared in the "Semiautomatic"...
Page 586 Technologies and cycles 21.7 Swiveling In the case of machine kinematics that move the workpiece (rotary table), the axis direction is reversed. Note Interrelation of TOOLCARRIER ⇔ 5-axis transformation (transformer type 24, 40, 56): For 5-axis transformation, transformer type 72 in MD24100: $MC_TRAFO_TYPE_1 can be used.
Page 587 Technologies and cycles 21.7 Swiveling Assignment of base vectors to the fine offset vectors: I1 $TC_CARR1..3[n] $TC_CARR41..43[n] I2 $TC_CARR4..6[n] $TC_CARR44..46[n] I3 $TC_CARR15..17[n] $TC_CARR55..57[n] I4 $TC_CARR18..20[n] $TC_CARR58..60[n] The fine offsets are activated by the following setting data: SD42974 $SC_TOCARR_FINE_CORREC‐ Fine offset TCARR on/off TION = 1 When activating a tool holder that can be oriented, the fine offset values are not taken into account.
Page 588 Technologies and cycles 21.7 Swiveling The following identifiers should be preferably chosen for the names of the rotary axes: ● Rotary axis rotates around machine axis X → A ● Rotary axis rotates around machine axis X → B ● Rotary axis rotates around machine axis Z → C For automatic rotary axes, the channel names of the corresponding NC rotary axes must be entered (see $TC_CARR37[n] TENS and HUNDREDS position: Automatic mode).
Page 589 Technologies and cycles 21.7 Swiveling $TC_CARR37[n] Display variants of the input screens for CYCLE800 Decimal place Meaning THOUSANDS Selection field direction: Direction selection of the rotary axes 0 = No display of the direction reference for kinematics that only have one solution.
Page 590 Technologies and cycles 21.7 Swiveling $TC_CARR37[n] Display variants of the input screens for CYCLE800 Decimal place Meaning HUNDRED MILLION Swivel data set enabled Setting swivel data set change Automatic or manual tool change is only necessary under ShopMill or Shop‐ Turn (→...
Page 591 Technologies and cycles 21.7 Swiveling Retracting the geometry axes before swiveling Figure 21-6 Dialog to select the type of retraction Select the retraction variant in the input field: This is defined in the ONE MILLION and TEN MILLION position of the system variable $TC_CARR37[n]: ●...
Page 592 Technologies and cycles 21.7 Swiveling The type of retraction is modified in the Manufacturer cycle CUST_800.SPF (Page 589). Note Retraction in the tool direction is useful for swivel data sets in which the tool is re-oriented (swivel head or mixed kinematics). This applies particularly for turning machines with a B axis. During retraction in "maximum tool direction", traversing is performed until one of the relevant linear axes reaches the software limit switch.
Page 593 Technologies and cycles 21.7 Swiveling 21.7.4 Examples of machine kinematics for the commissioning of the Swivel function Example 1: Swivel head 1 "HEAD_1" The vectors in the drawing refer to the initial setting of the kinematics. The drawing is not true to scale.
Page 594 Technologies and cycles 21.7 Swiveling Kinematics Swivel head HEAD_1 Correct tool Rotary axes Rotary axis 1 Mode Manual Angular range 0.000 360.000 Rotary axis 2 Mode Manual Angular range -15.000 100.000 Example 2: Swivel head 2 "HEAD_2" The vectors in the drawing refer to the initial setting of the kinematics. If the swivel head is fixed-mounted, the vector chain is closed.
Page 595 Technologies and cycles 21.7 Swiveling Kinematics Swivel head HEAD_2 Rotary axis vector V1 0.000 1.000 0.000 Offset vector I2 0.000 172.000 172.000 Rotary axis vector V2 0.000 1.000 1.000 Offset vector I3 0.000 0.000 93.800 Display version Swivel mode Axis-by-axis Direction reference Rotary axis 2 Rotary axes...
Page 596 Technologies and cycles 21.7 Swiveling Rotary axis vector V1 Rotary axis B rotates around Y and around Z. Rotary axis vector V2 Rotary axis C rotates about Z. Offset vector I2 The distance from the reference point of the machine to the center of rotation/ intersection of rotary axis 1.
Page 597 Technologies and cycles 21.7 Swiveling Kinematics Swivel table TABLE_45 Rotary axis 2 Mode Auto Angular range 0.000 360.000 1) Calculation of rotary axis vector: V1: β = -45 degrees V1Y= sin(-45)= -0.7071 V1Z= cos(-45)= 0.7071 V1Y and V1Z can be normalized to -1 and 1. Example 4: Swivel head/rotary table "MIXED_45"...
Page 598 Technologies and cycles 21.7 Swiveling Rotary axis vector V1 Rotary axis B rotates around Y and around Z. Rotary axis vector V2 Rotary axis C rotates about Z. Offset vector I2 The distance from the reference point of the tool adapter to the center of rotation/intersection of rotary axis 1 Offset vector I1 Closure of vector chain, I1 = - I2.
Page 599 Technologies and cycles 21.7 Swiveling Kinematics Mixed kinematics MIXED_45 Rotary axis 2 Mode Auto Angular range 0.000 360.000 1) Calculation of rotary axis vector: V1: β = 45 degrees V1Y= sin(-45)= -0.7071 V1Z= cos(-45)= 0.7071 V1Y and V1Z can be normalized to 1. Example 5: Swivel table "TABLE_5"...
Page 600 Technologies and cycles 21.7 Swiveling Rotary axis vector V2 Rotary axis C rotates about Z. Offset vector I2 The distance from the reference point of the machine to the center of rotation/ intersection of rotary axis 1. Offset vector I3 The distance from the center of rotation of rotary axis 1 to the center of rota‐...
Page 601 Technologies and cycles 21.7 Swiveling Rotary axis vector V1 The rotary axis A rotates about X. Rotary axis vector V2 Rotary axis C rotates about Z. Offset vector I2 The distance from the reference point of the machine to the center of rotation/ intersection of rotary axis 1.
Page 602 Technologies and cycles 21.7 Swiveling Example 6: Setting up a turning machine with B axis For turning machines with an additional rotary axis B, the tool can be aligned or swiveled on the X/Z plane. If your machine has a counterspindle, you can, for example, machine with a tool alternating between the main spindle and counterspindle.
Page 603 Technologies and cycles 21.7 Swiveling References Function Manual Basic Functions; W1: Tool offset, parameter CUTMOD: ● The CUTMOD NC function is activated when data set 2 is called in the NC program (CYCLE800 align turning tool). This means that the cutting edge position or the tool reference point is updated corresponding to the tool orientation: ●...
Page 604 Technologies and cycles 21.7 Swiveling Retract prior to swiveling If the CUST_800.SPF cycle is not modified, the Z axis (marker _M41) or the Z axis followed by the X, Y axes (marker _M42) are first traversed in the Machine to the positions when retracting prior to swiveling.
Page 605 Technologies and cycles 21.7 Swiveling CYCLE800 structured chart Sequence in AUTOMATIC mode Figure 21-14 Structure: CYCLE800.SPF / CUST_800.SPF SINUMERIK Operate (IM9) Commissioning Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 606 Technologies and cycles 21.7 Swiveling Figure 21-15 Structure: E_TCARR.SPF (F_TCARR.SPF) / CUST_800.SPF SINUMERIK Operate (IM9) Commissioning Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 607 Technologies and cycles 21.7 Swiveling Note on markers _M2 to _M13 When the swivel data set or tool is changed, the linear axes are recovered using the last retraction mode (modal). If this behavior is not desired in milling/turning, the corresponding calls must be commented out with a semicolon (;).
Page 608 Technologies and cycles 21.7 Swiveling Note on label _M40 This label is called before the calculation and activation of the tool holder function as user initialization. This makes it possible for special kinematics, to calculate or rewrite the current vectors of the active swivel data set. Boring mill application example: For parallel axes, the vector in the Z direction can be updated with the actual value of the W axis.
Page 609 Technologies and cycles 21.7 Swiveling Note on labels _M57 to _M59 Labels _M57 to _M59 are used for swiveling in JOG mode and active 5-axis transformation (TRAORI). Note on "Correct tool" "Correct tool" requires that a 5-axis transformation is set up which is equivalent to the corresponding swivel data set.
Page 610 Technologies and cycles 21.7 Swiveling The swivel data set is changed in the CYCLE800 following the CUST_800 jump to the _M40 marker. This means that the variable can also be described in the CUST_800. Programming example N10 _TC_CHANGE="HEAD_2" N20 CYCLE800(0,"HEAD_1",100000,57,0,0,0,0,0,0,0,0,0,-1,100,1) N30 M0 ;* HEAD_2 is active N40 _TC_CHANGE="HEAD_3"...
Page 611 Requirements The following requirements must be met in order to use CYCLE996 (Measure kinematics): ● SIEMENS measuring cycles package is installed ● Workpiece probe is calibrated ● Calibration ball is mounted ● Oriented tool holder is set up (MD18088 MM_NUM_TOOL_CARRIER > 0) ●...
Page 612 Technologies and cycles 21.8 Turning on milling machines The precise procedure when measuring and programming, including examples, is described in the following manual: References Programming Manual, Measuring Cycles: CYCLE996 21.8 Turning on milling machines You can set up the turning technology as an extended technology on milling machines. The operating software has all the setting options of a milling machine and a turning machine.
Page 613 Technologies and cycles 21.8 Turning on milling machines MD51226 $MNS_FUNCTION_MASK_SIM Simulation function screen Bit 5 = 1 Turning tool in tool spindle rotatable (for simulation) MD51781 $MNS_MEA_T_PROBE_THICKNESS Tool probe thickness for the automatic approach of turning tools to the probe on milling/turning ma‐ chines Default value MD20100 $MC_DIAMETER_AX_DEF...
Page 614 Technologies and cycles 21.8 Turning on milling machines MD20360 $MC_TOOL_PARAMETER_DEF_MASK Definition of the tool parameters Bit 17 = 0 With CUTMOD for turning and grinding tools, the cutting edge for the calculation of the compensation values is not configured in the machining plane. Bit 18 = 1 With CUTMOD for turning and grinding tools, always use the active plane for turning and grinding tools.
Page 615 Technologies and cycles 21.8 Turning on milling machines MD52214 $MCS_FUNCTION_MASK_MILL Milling function screen Bit 1 = 1 Offer fixed table for blank clamping Note Only set bit 1 in MD52214 when a fixed table is used in addition to a rotary table. MD52780 $MCS_J_MEA_T_PROBE_APPR_MO Approach mode for measuring a tool in JOG Technology-dependent approaching of the tool probe (default value)
Page 616 Technologies and cycles 21.8 Turning on milling machines SD42940 $SC_TOOL_LENGTH_CONST Change of tool length components at change of plane = 17 L1 = Z, L2 = Y, L3 = X SD42942 $SC_TOOL_LENGTH_CONST_T Change of tool length components for turning tools at change of plane = 19 L1 = Z, L2 = Y, L3 = X...
Page 617 Technologies and cycles 21.8 Turning on milling machines SD54648 $SNS_MEA_TPW_TYPE[k] Probe version Compatibility (measuring cycles: cube, turning surface shows probe, milling surface shows disk) Cube Additional settings ● Set the current zero point in the center point of the turning tool, e.g. via a settable zero offset.
Page 618 Technologies and cycles 21.8 Turning on milling machines Setting up system variables Use the following system variables to set up the kinematics transformation: System variable Meaning $NT_NAME[n] Name of the transformation that appears on the user interface $NT_TRAFO_TYPE[n] Transformation type for turning and milling machines: TRAORI_STAT $NT_T_CHAIN_LAST_ELEM[n] Name of the chain element that describes the end of the chain...
Page 619 Technologies and cycles 21.8 Turning on milling machines Decimal place Meaning HUNDRED MILLION Enable data set 4 = Kinematics active (fixed value) See system variables $NT_AUX_POS[n,0] to $NT_AUX_POS[n,2] Meaning of the bits of $NT_CNTRL[n] You can make the following settings for the machine adaptation: Bit 0 = 1 Fixed sequence of axes For easier handling of the data, the sequence of the axes is fixed:...
Page 620 Technologies and cycles 21.8 Turning on milling machines [14] = 1 The current setting of the 15th G group is also retained after reset / part program end (G94, ...). [28] = 1 The current setting of the 29th G group is also retained after reset / part program end (DIAMxxx).
Page 621 Technologies and cycles 21.8 Turning on milling machines 21.8.5 Setting up the Hirth joint If the tool spindle or the swivel axis has a Hirth joint with, for example, incrementing of 2.5° (360°/2.5° = 144 division), you can set up the following: Settings MD30505 $MA_HIRTH_IS_ACTIVE Axis is indexing axis with Hirth joint...
Page 622 Technologies and cycles 21.8 Turning on milling machines Settings Set the appropriate coordinate system via the following channel-specific machine data (values, for example, for boring mills): MD52000 $MCS_DISP_COORDINATE_SYSTEM Position of the coordinate system (variable) = 16 Y up, Z to the right MD52001 DISP_COORDINATE_SYSTEM_2 Coordinate system for turning on milling machines (variable)
Page 623 Technologies and cycles 21.8 Turning on milling machines _M71: ; Alignment tool: Swivel rotary axis _AX1=$PC_TRAFO_ROT_CHAN_AX_IN[1] ; Rotary axis B _AX2=$PC_TRAFO_ROT_CHAN_AX_IN[2] ; Tool spindle IF(_TC_N_WZ==0) ; No tooltip tracking N800710 TRAFOOF ENDIF SBLON N800711 G0 G40 G60 G90 AX[_AX1]=_A1 AX[_AX2]=_A2 SBLOF GOTOF _MEND _M72:...
Page 624 Technologies and cycles 21.8 Turning on milling machines Simplified flow diagrams During tool retraction, the markers _M44 to _M48 are run through before the rotary axis positioning in accordance with the retraction variant. SINUMERIK Operate (IM9) Commissioning Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 625 Technologies and cycles 21.8 Turning on milling machines For swiveling with retraction to MCS fixed position, see Chapter "Manufacturer cycle CUST_800.SPF (Page 589)". 21.8.8 Rotary axis positioning during block search After a block search, you must position the rotary axis as follows (refer to swivel plane). Generally, there are two rotary axes (swivel axis and tool spindle): Procedure Read out the position value of the rotary axis via the following system variable:...
Page 626 Technologies and cycles 21.9 High-speed machining IF($PC_TRAFO_TYPE_NAME=="TRAORI_STAT") IF(($NT_IDENT[($P_TRAFO_PARSET MOD 1000),0] _DEC5)>=2) _TC_N_WZ=1 ; Correct tool CUST_800(71,,$AC_RETPOINT[$PC_TRAFO_ROT_CHAN_AX_IN[1]], $AC_RETPOINT[$PC_TRAFO_ROT_CHAN_AX_IN[2]]) ENDIF ENDIF ENDIF 21.9 High-speed machining 21.9.1 High speed settings: Configuring CYCLE832 Function The High Speed Settings function (CYCLE832) is used to preset data for the machining of sculptured surfaces so that optimum machining is possible.
Page 627 Technologies and cycles 21.9 High-speed machining There are 2 options available for this: 1. Direct entry of the orientation tolerance OTOL Machining types: _ORI_ROUGH, _ORI_SEMIFIN, _ORI_FINISH To enter the orientation tolerance in the input screen for CYCLE832, bit 1 =1 must be set in the setting data SD55220 $SCS_FUNCTION_MASK_MILL_TOL_SET 2.
Page 628 Technologies and cycles 21.9 High-speed machining MD32310 $MA_MAX_ACCEL_OVL_FACTOR[0..4] Overload factor for axial velocity jumps. MD32431 $MA_ MAX_AX_JERK[0..4] Maximum axial jerk for path mo‐ tion. MD32432 $MA_PATH_TRANS_JERK_LIM[0..4] Maximum axial jerk at the block transition in continuous-path mode. Note During the optimization of the machine axes, the values (note array index) of the specified machine data must be set correctly.
Page 629 Technologies and cycles 21.9 High-speed machining The programming of FGREF () is useful when machining with active multi-axis transformation (e.g. TRAORI). In this case, in CUST_832.SPF, variable _FGREF is pre-assigned a value of 10 mm. This value can also be modified. In CYCLE832.SPF, the value of variable _FGREF is written to the rotary axes involved in the machining, which are declared as orientation axis of a 5-axis transformation, using the FGREF(rotary axis) command.
Page 630 Technologies and cycles 21.9 High-speed machining 21.9.3 Top Surface: CYCLE832 extension Function Besides Advanced Surface, the High Speed Settings (CYCLE832) function also offers the extension Top Surface. You can use Top Surface to improve the quality of free-form surfaces. If set actively, the continuous-path control is optimized within contour tolerances. The CYCLE832 call also contains the smoothing parameter.
Page 631 Technologies and cycles 21.10 Measuring cycles and measurement functions = 0 The best available mold making function is automatically used: ● Top Surface not active → Advanced Surface ● Top Surface active → Top Surface = 1 The mold making function (Advanced Surface or Top Surface) can be selected in the input screenform.
Page 632 Technologies and cycles 21.10 Measuring cycles and measurement functions References NCU Manual: Digital inputs / outputs Setting the switching behavior You set the electrical polarity of the connected probe using the following general machine data: MD13200 $MN_MEAS_PROBE_LOW_ACTIVE Polarity change of the probe Probe in the non-deflected state, 0 V default value Probe in the deflected state, 24 V Probe in the non-deflected state, 24 V...
Page 633 Technologies and cycles 21.10 Measuring cycles and measurement functions Program code Comment N30 MTSIGNAL=$AC_MEA[1] ;Switching operation at the 1st measuring input completed, ;YES / NO N35 IF MTSIGNAL == 0 GOTOF _FEHL1 ;Evaluation of the signal N40 R1=$AA_MM[X] ;Save measured value in machine coordi- nates at R1 N45 R2=$AA_MW[X] ;Save measured value in workpiece coordi-...
Page 634 Technologies and cycles 21.10 Measuring cycles and measurement functions MD54740 $SNS_MEA_FUNCTION_MASK Measuring cycles function screen Bit 0 Workpiece, repeat measurement if TSA, TDIF exceeded Bit 1 Workpiece, repeat measurement with M0 if TSA, TDIF exceeded Bit 2 Workpiece, stop at M0 if TUL, TLL exceeded Bit 3 Workpiece, accept calibrated probe sphere radius in tool data Bit 4...
Page 635 Technologies and cycles 21.10 Measuring cycles and measurement functions You can use the CUST_MEACYC.SPF to program and execute sequences that are necessary before and/or after a measurement (e.g. activating/deactivating a probe). Note Copy the CUST_MEACYC cycle before performing the changes from the directory NC data/ Cycles/Standard cycles to the directory NC data/Cycles/Manufacture cycles or NC data/Cycles/User cycles.
Page 636 Technologies and cycles 21.10 Measuring cycles and measurement functions CUST_MEACYC structogram Sequence in the AUTOMATIC mode, using measure bore as example, CYCLE977 with probe type 712. Figure 21-17 Structure: CYCLE977 / CUST_MEACYC SINUMERIK Operate (IM9) Commissioning Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 637 Technologies and cycles 21.10 Measuring cycles and measurement functions Note Commenting out spindle SPOS commands If the spindle SPOS command is to be commented out in the CUST_MEACYC.SPF cycle, set the cycle setting in SD55740 $SCS_MEA_FUNCTION_MASK to active with Bit 1 = 1. You can see how to comment out a spindle SPOS command in the CUST_MEACYC.SPF cycle in the following example: Example...
Page 638 Technologies and cycles 21.10 Measuring cycles and measurement functions Workpiece measurement For milling: ● The probe has been inserted in the tool spindle. ● The probe has been selected in the tool list as type 7xx (probe). ● The probe is activated as tool in the current NC channel. Tool measurement To measure tools, an appropriate probe must be located in the machine space so that this can be reliably and safely reached with a tool in the spindle.
Page 639 Technologies and cycles 21.10 Measuring cycles and measurement functions Checking and setting the general machine data MD11450 $MN_SEARCH_RUN_MODE "Search run" programming. Bit 1 = 1 Automatic ASUB start after output of the action blocks (see also MD11620 $MN_PROG_EVENT_NAME). Alarm 10208 is not output until the ASUB is completed.
Page 640 Technologies and cycles 21.10 Measuring cycles and measurement functions The following channel-specific machine data is only effective if the system frame actual value setting and scratching is set up using the above mentioned machine data MD28082 $MC_SYSTEM_FRAME_MASK, bit 0 = 0. MD24006 $MC_CHSFRAME_RESET_MASK Active system frames after reset.
Page 641 Technologies and cycles 21.10 Measuring cycles and measurement functions MD52207 $MCS_AXIS_USAGE_ATTRIB[n] Attributes of the axes [n] channel axis number Bit 6 Request rotational axis as offset target for measuring = 0 Default value = 1 Rotary axis is displayed as offset target in the "Measuring in JOG" window Bit 9 SPOS behavior of main spindle influenced in connection with measuring cycles = 0 The positioning behavior of the tool spindle is not influenced...
Page 642 Technologies and cycles 21.10 Measuring cycles and measurement functions Bit 3 = 1 Selects the probe calibration data, enable Bit 6 = 1 Selects ZO correction in the basis reference (SETFRAME), enable Bit 7 = 1 Selects ZO correction in channel-specific basic frames, enable Bit 8 = 1 Selects ZO correction in the global basic frame, enable Bit 9 = 1...
Page 643 Technologies and cycles 21.10 Measuring cycles and measurement functions Decimal place ONES 1st axis axis not possible only minus direction only plus direction both directions TENS 2nd axis axis not possible only minus direction only plus direction both directions HUNDREDS 3rd axis axis not possible only minus direction...
Page 644 Technologies and cycles 21.10 Measuring cycles and measurement functions MD51752 $MNS_J_MEA_M_DIST_TOOL_LENGTH Measuring path to measure the tool length. Default value MD51753 $MNS_J_MEA_M_DIST_TOOL_RADIUS Measuring path to measure the tool ra‐ dius. Default value MD51786 $MNS_J_MEA_T_PROBE_MEASURE_DIST Measuring path to calibrate the probe or for measurements with stationary spindle.
Page 645 Technologies and cycles 21.10 Measuring cycles and measurement functions Note If the spindle is already rotating when the measuring cycle is called, this direction of rotation remains independent of the setting of this data. SD54675 $SNS_MEA_CM_FEEDFACTOR_1[0] Feedrate factor 1 = 10 Default value Only single probing with the feedrate calculated by the cycle.
Page 646 Technologies and cycles 21.10 Measuring cycles and measurement functions Effective radius of the tool Arc distance = SD54692 Maximum number of probe contacts = SD54693 ① 1st measuring point. Figure 21-18 Single cutting edge measurement General cycle setting data for correction using the correction tables when forming measurements with rotating spindle.
Page 647 Technologies and cycles 21.10 Measuring cycles and measurement functions 21.10.3.3 Measuring tools at the turning machines Measuring feedrate for tool measurement in turning operation SD55628 $SCS_MEA_TP_FEED_MEASURE Calibrate measuring feedrate for tool probe and measure tool with station‐ ary spindle. = 300 Default value Note Measuring feedrate for tool measuring...
Page 648 Technologies and cycles 21.10 Measuring cycles and measurement functions Read access rights: Access level 4 (keyswitch 3), default value Write access: Access level 3 (user) 21.10.3.4 Measuring without electronic probe in JOG Measure workpiece For manual measuring functions in the JOG operating mode, for which a rotating spindle is required, the following applies: ●...
Page 649 Technologies and cycles 21.10 Measuring cycles and measurement functions Workpiece measurement Sequence in milling technology: 1. The probe has been selected in the tool list as type 7xx (probe). 2. The probe has been inserted in the tool spindle. 3. The probe is activated in the actual NC channel. Sequence in turning technology: 1.
Page 650 Technologies and cycles 21.10 Measuring cycles and measurement functions SD55623 $SCS_MEA_EMPIRIC_VALUE[n] Empirical values Default value SD55618 $SCS_MEA_SIM_ENABLE Measuring cycle simulation When calling measuring cycles in conjunction with SINUMERIK Operate, ShopMill or Shop‐ Turn simulation, the measuring cycles are skipped, default value. Default setting: When calling measuring cycles in conjunction with SINUMERIK Operate, ShopMill or Shop‐...
Page 651 Technologies and cycles 21.10 Measuring cycles and measurement functions Requirement You have already made the settings from the following section: See also: Measuring cycles and measurement functions, general (Page 617) Settings General cycle setting data SD54760 $SNS_MEA_FUNCTION_MASK_PIECE Settings for the input screen, measuring cycles in AUTOMATIC, workpiece meas‐...
Page 652 Technologies and cycles 21.10 Measuring cycles and measurement functions Note Measuring feedrate for workpiece measuring All measuring cycles use the value saved in SD54611 $SNS_MEA_WP_FEED[n] as measuring feedrate after the tool probe has been calibrated. A different measuring feedrate can be assigned for each calibration field [n]. When calibrating the probe, either the measuring feedrate from SD55630 $SCS_MEA_FEED__MEASURE is used, or the measuring feedrate can be overwritten in the input screen when calibrating.
Page 653 Technologies and cycles 21.10 Measuring cycles and measurement functions SD55642 $SCS_MEA_EDGE_SAVE_ANG Safety angle when measuring a corner (CYCLE961) Degrees This angle is added to the angle that the user entered between the workpiece reference edge and the 1st axis of the active coordinate system in a positive direction, and refers to the corner measurement in the automatic mode (CYCLE961).
Page 654 Technologies and cycles 21.10 Measuring cycles and measurement functions SD54606 $SNS_MEA_WP_TRIG_PLUS_DIR_AX3[n] Trigger point, plus direction, 3rd measuring axis opposite to the tool direction. In the default case = 0. SD54607 $SNS_MEA_WP_POS_DEV_AX1[n] Position deviation, 1st measuring axis in the plane. SD54608 $SNS_MEA_WP_POS_DEV_AX2[n] Position deviation, 2nd measuring axis in the plane.
Page 655 Technologies and cycles 21.10 Measuring cycles and measurement functions Calibration data of the tool probe, referred to the machine coordinate system Before calibration is started, the position of the tool probe in the machine coordinate system (MCS) must be entered into the following general cycle setting data. In this case, the reference point is the outer diameter or the tool length of the active tool in the spindle.
Page 656 Technologies and cycles 21.10 Measuring cycles and measurement functions Decimal place axis not possible only minus direction only plus direction both directions HUNDREDS 3rd axis axis not possible only minus direction only plus direction both directions Example If the general cycle machine data SD54632 $SNS_MEA_TP_AX_DIR_AUTO_CAL has the value 123, the tool probe is calibrated as follows in the G17 plane: ●...
Page 657 Technologies and cycles 21.10 Measuring cycles and measurement functions SD54640 $SNS_MEA_TPW_TRIG_MINUS_DIR_AX1[k] Trigger point of the 1st measuring axis in the negative direction. SD54641 $SNS_MEA_TPW_TRIG_PLUS_DIR_AX1[k] Trigger point of the 1st measuring axis in the positive direction. SD54642 $SNS_MEA_TPW_TRIG_MINUS_DIR_AX2[k] Trigger point of the 2nd measuring axis in the negative direction.
Page 658 Technologies and cycles 21.10 Measuring cycles and measurement functions Decimal place only plus direction both directions Example If the general cycle machine data SD54647 $SNS_MEA_TPW_AX_DIR_AUTO_CAL has the value 123, the tool probe is calibrated as follows in the G17 plane: ●...
Page 659 Technologies and cycles 21.10 Measuring cycles and measurement functions SD54675 $SNS_MEA_CM_FEEDFACTOR_1[0] Feedrate factor 1 = 10 Default value Only single probing with the feedrate calculated by the cycle. However, as a minimum, the value from SD54673[0] $SNS_MEA_CM_MIN_FEEDRATE. = ≥1 First probing with feedrate. However, as a minimum with the value from SD54673[0] $SNS_MEA_CM_MIN_FEEDRATE) SD54675[0] $SNS_MEA_CM_FEEDFACTOR_1 SD54676 $SNS_MEA_CM_FEEDFACTOR_2[0]...
Page 660 Technologies and cycles 21.10 Measuring cycles and measurement functions Correction values for users If the general cycle setting data SD54691 $SNS_MEA_T_PROBE_OFFSET= 2, the following settings apply: SD54695 to SD54700 Correction values for radius meas‐ See the subsequent general cycle urement. setting data.
Page 661 Technologies and cycles 21.10 Measuring cycles and measurement functions SD54621 $SNS_MEA_CAL_EDGE_PLUS_DIR_AX2[n] Calibration slot edge in the positive direc‐ tion of the 2nd measuring axis. SD54622 $SNS_MEA_CAL_EDGE_MINUS_DIR_AX2[n] Calibration slot edge in the negative di‐ rection of the 2nd measuring axis. Note For a standard lathe with axes X and Z (G18), axis Z is the 1st measuring axis and axis X is the 2nd measuring axis.
Page 662 Technologies and cycles 21.10 Measuring cycles and measurement functions Tool measurement using the "Orientable tool holder" or "Swivel tool" function If the general cycle machine data MD52740 $MNS_MEA_FUNCTION_MASK, bit 16 = 1, then the following setting applies: MD51618 $MNS_MEA_CM_ROT_AX_POS_TOL Tolerance parameter for rotary axis set‐ tings = 0.5 Default value...
Page 663 Technologies and cycles 21.10 Measuring cycles and measurement functions 21.10.5.2 Logging while measuring in the JOG mode You can set the following setting data in the "Settings for Measurement Log" window for the JOG mode. References Operating Manual, Turning/MIlling/Grinding; Chapter "Settings for the measurement result log" Cycle channel setting data SD55774 $SCS_J_MEA_PROTOCOL_FILE Name and path for the log file for measuring in JOG...
Page 664 Technologies and cycles 21.10 Measuring cycles and measurement functions Note The logging operation checks whether the S_USERTXT array is available. If S_USERTXT is available, the content of the array is logged. If S_USERTXT is not available, the content of the S_PROTTXT array is logged.
Page 665 Technologies and cycles 21.11 Compare cycles version 21.11 Compare cycles version 21.11.1 Display cycles version If cycles have version details, you can display them in the version screen. Precondition The version details are included in the cycles files in the following form: ;VERSION: <Version>...
Page 666 Technologies and cycles 21.11 Compare cycles version Procedure Select the "Diagnostics" operating area. Press the "Version" softkey. It takes some time to call the version display. While the version data is being determined a progress message box and the appropriate text are displayed in the dialog line.
Page 667 File overview The following files are required: Name Path Meaning versions.xml /siemens/sinumerik/hmi/data/version/oem/cma Version file versions.xml /oem/ Version path file Adapting the version file The cycles version specification requires a manual adaptation of the version file. 1. Copy the "versions.xml" sample file from the following directory: /siemens/sinumerik/hmi/data/version/oem/cma 2.
Page 668 2. Replace the standard path in the <Path> tag for the "Manufacturers Cycles" with your own path for the version file. 3. Close the file to save the changes. Standard: <Component> <Name>Manufacturer Cycles</Name> <Path>/siemens/sinumerik/hmi/data/version/oem/cma</Path> </Component> Example: <Component> <Name>Manufacturer Cycles</Name> <Path>/oem/sinumerik/hmi/data/version/oem/cma</Path>...
Page 669 Additional language 22.1 Installing additional languages Additional languages In addition to the already existing standard languages, additional user interface languages are available on a separate DVD. The integrated online help is either displayed in the relevant language of the country or in English.
Page 670 Additional language 22.3 Supported languages 22.2 Uninstalling languages If you no longer require a language interface, then you can uninstall this. Note Standard languages and the currently active language for the operating software cannot be uninstalled. Procedure Select the "Startup" operating area. Press the "Change language"...
Page 671 Additional language 22.3 Supported languages Language Language code Standard languages Portuguese Romanian Russian Swedish Slovenian Slovakian Spanish Thai Czech Turkish Hungarian Vietnamese SINUMERIK Operate (IM9) Commissioning Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 672 Additional language 22.3 Supported languages SINUMERIK Operate (IM9) Commissioning Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 673 SINUMERIK Operate on PC/PCU 23.1 Link OEMFrame application Integrating an OEM application The following files should be adapted and created in order to integrate an OEMFrame application into the operating software: ● Configuration file "systemconfiguration.ini" The operating software is started and controlled from the system manager; the system manager also controls the OEMFrame applications.
Page 674 SINUMERIK Operate on PC/PCU 23.1 Link OEMFrame application Value Meaning The linked process starts as follows: startupTime immediately: immediately (default) afterServices: after all services have started afterGuis: after all GUI components have started If SINUMERIK Operate is shut down, the process goes in reverse: immediately: immediately (default) afterServices: after all services have shut down afterGuis: after all GUI components have shut down...
Page 675 SINUMERIK Operate on PC/PCU 23.1 Link OEMFrame application Keys Meaning Channel switchover key Shift+F11 M key (hard key) Info/help Shift+F12 Custom key (hard key) Alarm cancel HOME Window switchover key PROGRAM (hard key) PAGE UP ALARM (hard key) PAGE DOWN TOOL OFFSET (hard key) HOME (NUMPAD) PROGRAM MANAGER (hard key)
Page 676 SINUMERIK Operate on PC/PCU 23.1 Link OEMFrame application You can parameterize the bit mask "disablekeyshigh" as follows: Meaning 0 - 28 Reserved Key sequences Ctrl-F1 to Ctrl-F8 can be mapped onto key sequences Ctrl-F13 to Ctrl-F20. 30 - 31 Reserved Note The "gimmekeys", "disablekeys"...
Page 677 SINUMERIK Operate on PC/PCU 23.1 Link OEMFrame application PROC500= process:=keycatcherOEM, cmdline:="keycatcher.exe", oemframe:=true, deferred:=true, windowname:="keycatcher", classname:="QWidget", gimmekeys:=0x1F, disablekeys:=0x300FF [areas] AREA500=name:=AreaKeyCatcher, process:= keycatcherOEM The Windows application "keycatcher.exe" is integrated in the following example. In this case, all four softkey bars and the F10 key will reach the Windows application. Press Ctrl+F12 to show the operating area menu when a Windows application is displaying (the system configuration no longer evaluates F10): [processes]...
Page 678 23.1 Link OEMFrame application NOTICE Basic components are overwritten If you use numbers less than 500, then it is possible that Siemens basis components will be overwritten. In the "processes" and "areas" sections, the number range 500 - 999 is permissible.
Page 679 SINUMERIK Operate on PC/PCU 23.1 Link OEMFrame application Configuring additional settings In order to configure the following settings you require the "slamconfig.ini" configuration file: ● Assigning a softkey position to a specific operating area. ● Creating a language-dependent text for the softkey. ●...
Page 680 SINUMERIK Operate on PC/PCU 23.1 Link OEMFrame application TextFile = mytext ; Context in the text file to which the Text-ID is assigned to TextContext = mycontext ; File name of an icon shown on the area softkey Picture = mypicture.png ;...
Page 681 SINUMERIK Operate on PC/PCU 23.2 Parameterizing the OEMFrame application mytext_<lng>.ts <TS> <context> <name>mycontext</name> <message> <source>MY_AREA</source> <translation>Text, which is displayed on the softkey</translation> <remark>comment (optional)</remark> <chars>20</chars> <lines>2</lines> </message> </context> </TS> <lng> stands for the language code. 23.2 Parameterizing the OEMFrame application File "oemframe.ini"...
Page 682 SINUMERIK Operate on PC/PCU 23.2 Parameterizing the OEMFrame application Parameter Meaning Default value Width of the OEMFrame applica‐ Desktop width Width tion (unit: pixels) Height of the OEMFrame appli‐ Desktop height Height cation (unit: pixels) Delays the feedback to the Sys‐ nDelayInitComplete tem Manager States whether the window...
Page 683 SINUMERIK Operate on PC/PCU 23.2 Parameterizing the OEMFrame application The following control options are possible with WindowsStyle parameters (binary characteristic values): 0000 0000 xxxx xxxx 0000 0000 0000 0000 1010 Header 1000 Border 0100 Type of window frame on a dialog box 0010 Vertical scroll bar 0001...
Page 684 SINUMERIK Operate on PC/PCU 23.2 Parameterizing the OEMFrame application The available working area depends on the screen layout being used. Width This parameter defines the width of the window for the Windows application, measured in pixels from the window origin according to parameter x. Height This parameter defines the height of the window for the Windows application, measured in pixels from the window origin according to parameter y.
Page 685 SINUMERIK Operate on PC/PCU 23.2 Parameterizing the OEMFrame application The following parameter assignment is possible: [startup] fSearchOnlyForTaskWindow = 0 fRestoreTaskWindow This parameter defines the behavior when exiting a Windows application that was started from the OEMFrame application as second task level. When the OEMFrame application is deselected, the last window that was active (ForegroundWindow) is saved by default.
Page 686 SINUMERIK Operate on PC/PCU 23.2 Parameterizing the OEMFrame application On switching from one operating area to another, the last active window ForegroundWindow of the OEMFrame application is saved. When reselecting the application, the ForegroundWindow window is then reactivated. The behavior can be changed via the following values: fForceTaskFocus and fSearchForPopUps When the OEMFrame application is deselected, an active popup window is searched for rather than the ForegroundWindow window.
Page 687 SINUMERIK Operate on PC/PCU 23.2 Parameterizing the OEMFrame application [fixres] fKeepPlacement = 1 fSearchForPopUps No active pop-up window is searched for. nInitShowMode/nShowMode/nUnShowMode The three parameters define how the application window will be displayed when the application is started, hidden, and shown. The parameter nInitShowMode starts the application.
Page 688 SINUMERIK Operate on PC/PCU 23.2 Parameterizing the OEMFrame application Note Display problems The default settings function for most of the applications. In exceptional cases, display problems can occur in applications with Borland-Delphi development, i.e. shifted windows, etc. Use the following parameters in this case: nUnShowMode = 0 fKeepPlacement = 1 nInitShowMode = 1...
Page 689 Example An application is to be integrated that contains the start time in the attribute window name: oemframe.ini [MyQtTest] fFindWindowWithWildcards = 1 systemconfiguration.ini [processes] PROC500=process:=ProcessOEM, cmdline:="C:\\Program Files(x86)\\Siemens\\ MotionControl\\oem\\sinumerik\\hmi\\appl\\MyQtTest.exe",oemframe:=true, windowname:="MyQtTest - ??:??:??", classname:="QWidget",deferred:=true [areas] AREA500=name:=Test, process:=ProcessOEM 23.3 FindWindow program application Via the FindWindow program, you can determine all the parameters in the "systemconfiguration.ini"...
Page 690 SINUMERIK Operate on PC/PCU 23.4 Setting text legibility by means of font smoothing FindWindow (findwindow.exe) is located in the following directory: C:\Program Files (x86)\Siemens\MotionControl\Common\FindWindow\ Application 1. Start the PCU. 2. Install the application to be integrated using OEMFrame. 3. Open the application.
Page 691 If you want to achieve a better overview of the changes you have made yourself, simply delete the unchanged parameters from the file copy "slstartup.ini". The missing parameters continue to be read by the directory /siemens/sinumerik/hmi/cfg from the template. SINUMERIK Operate (IM9)
Page 692 SINUMERIK Operate on PC/PCU 23.5 Using interactive or silent installation versions 23.5 Using interactive or silent installation versions General Information If you install SINUMERIK Operate using PC/PCU, then the execution is realized using an MSI setup. The following installation versions are available, which you can use in the interactive or silent mode using the appropriate Windows command line: ●...
Page 693 SINUMERIK Operate on PC/PCU 23.6 Setting the IP address of the NCU Silent installation versions Complete installation in the silent mode setup.exe /v"/qn" setup.exe /s /v"/qn" (/s suppresses all of the setup messages) Base installation in the silent mode with help files setup.exe /v"/qn BASEONLY=1"...
Page 694 SINUMERIK Operate on PC/PCU 23.7 SINUMERIK Operate exiting Press the vertical softkey "NCU connection". The "NCU Connection" window opens. Enter the IP address of the NCU into the input field. Press the "OK" softkey to confirm the data. 23.7 SINUMERIK Operate exiting Procedure Press the <MENU SELECT>...
Page 695 HT 8 24.1 Configuring the traversing keys The traversing keys of the HT 8 are not labeled as their type of action is not predefined. The labeling of the traversing keys should adapt dynamically to the type of action of the keys. To recognize the type of action of the traversing keys, they are shown within the display in the vertical softkey area.
Page 696 /ico1024 /ico1280 Procedure 1. Copy the "sljkconfig.ini" configuration file from the folder /siemens/sinumerik/hmi/template/cfg 2. Place the copy into the folder /oem/sinumerik/hmi/cfg or /user/sinumerik/hmi/cfg 3. Open the copy in the Editor and define the traversing key labeling. Example of a "sljkconfig.ini" configuration file 12 axes are defined in the example, with text for softkey 1 and softkey 2, as well as an image on softkey 3 and softkey 4.
Page 697 Spanish Italian Chinese Procedure 1. You can copy the sample file " oem_sljk_deu.ts" from the following directory: /siemens/ sinumerik/hmi/template/lng. 2. Store or create the file in the /oem/sinumerik/hmi/lng or /user/sinumerik/hmi/lng directory. 3. Give the file a name, e.g. for German texts: "sljk_deu.ts".
Page 698 HT 8 24.1 Configuring the traversing keys 4. Open the file and in the <message> and </message> area, define the labeling. 5. Restart the HMI. In order that the labeling is displayed during the program runtime, the file must be converted into a binary format.
Page 699 HT 8 24.2 Configuring user-specific key labeling <message> <source>JK_AXISNAME_8</source> <translation>V</translation> </message> <message> <source>JK_AXISNAME_9</source> <translation>W</translation> </message> <message> <source>JK_AXISNAME_10</source> <translation>UV1</translation> </message> <message> <source>JK_AXISNAME_11</source> <translation>UV2</translation> </message> <message> <source>JK_AXISNAME_12</source> <translation>UV3</translation> </message>  <message> <source>OEM_JK_TEXT_1</source> <translation>SF1</translation> </message> <message> <source>OEM_JK_TEXT_2</source>...
Page 700 Number of characters. A maximum of 10 characters per line are possible. lines Number of lines. 2 lines are possible. Procedure 1. You can copy the sample file " oem_slck_deu.ts" from the following directory: /siemens/ sinumerik/hmi/template/lng. 2. Store or create the file in the /oem/sinumerik/hmi/lng or /user/sinumerik/hmi/lng directory.
Page 701 HT 8 24.2 Configuring user-specific key labeling 4. Open the file and in the <message> and </message> area, define the key labeling. 5. Restart the HMI. In order that the key labeling is displayed during the program runtime, the file must be converted into a binary format.
Page 702 HT 8 24.3 Configuring the function display at user-specific keys (U keys) 24.3 Configuring the function display at user-specific keys (U keys) Function Active functions can be displayed at the configurable user keys via the PLC. For instance, small LEDs can be emulated on the softkeys. You configure the function in the "slckcpf.ini"...
Page 703 "Single Block" softkey. false The icon is not displayed. 1. You can copy the sample file "slckcpf.ini" from the following directory: /siemens/sinumerik/ hmi/template/cfg 2. Store the file in the /oem/sinumerik/hmi/cfg or /user/sinumerik/hmi/cfg directory. 3. If you use your own icon, then locate it together with the corresponding resolution for HT 8 directory: /oem/sinumerik/hmi/ico/ico640 or /user/sinumerik/hmi/ico/ico640.
Page 704 HT 8 24.3 Configuring the function display at user-specific keys (U keys) ; Use the following settings to use this status bits instead of the led map for a specific sk ;U1LED=/channel/parameter/R[U1,1] ;..;U16LED=/channel/parameter/R[U1,16] ;VarIncLED = DB11.DBX8.5 ;SBLLED = DB21.DBX0.4 ;WCSLED = DB19.DBX0.7 ;...
Page 705 List of abbreviations/acronyms Abbreviation Meaning ASCII American Standard Code for Information Interchange: American coding standard for the exchange of information Mode group Operator Panel Interface Computerized Numerical Control: Computerized numerical control Cross Error Compensation: Sag compensation Communication Processor Discovery and basic Configuration Protocol: ProfiNet protocol DHCP Dynamic Host Configuration Protocol Deutsche Industrie Norm...
Page 706 List of abbreviations/acronyms Abbreviation Meaning Machine Coordinate System MLFB Maschinenlesbare Fabrikatbezeichnung Main Program File: NC part program (main program) Machine Control Panel: Machine control panel Numerical Control: Numerical control Numerical Control Kernel: NC kernel with block preparation, traversing range, etc. Numerical Control Unit: NCK hardware unit Network File System Network Time Protocol...
Page 707 List of abbreviations/acronyms Abbreviation Meaning Feed Drive Workpiece Coordinate System Tool Management SINUMERIK Operate (IM9) Commissioning Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 708 List of abbreviations/acronyms SINUMERIK Operate (IM9) Commissioning Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 709 Index Creating foreign-language texts, 257 Deactivating a warning, 287 Registering the file, 259 Replacing, 270 3D file Replacing standard alarm texts, 270 Protection area elements, 316 Select font color, 255 3D simulation, 137, 141 Standard parameter specification, 275 Supported languages, 656 alarmtext_conversion.log, 260, 262, 265, 273, 276 Analog spindle, 148 Access levels, 37...
Page 710 Index Collision avoidance CUST_MEACYC Changing the section, 296 Structogram, 622 Creating a machine model, 293 CUST_MEACYC.SPF, 510 Creating a tool protection area, 328 CUST_MEAPROT.SPF, 510, 650 Creating collision pairs, 329 CUST_MULTICHAN, 511, 517 Creating kinematic elements, 323 CUST_T, 511, 513 Creating machine protection areas, 325 CUST_TECHCYC.SPF, 510 Enable function, 291...
Page 711 Index dealer.xml, 430 EXTCALL Defining channel groups, 87 switch off and on again, 82 DHCP server detection, 396 Diagnostics AS-i, 480 Ethernet/PROFINET network, 396 Face machining HMI trace, 446 in turning, 548 Direction of rotation under ShopTurn, 550 Counterspindle, 536 fast block search, 127 Main spindle, 530 File...
Page 712 Index HT 8 Parallel linear axis, 301 Activating, deactivating the virtual keyboard, 35 Parallel offset, 302 Configuring the traversing keys, 681 Parallel rotary axis, 302 Key labeling, 685 Parallel switch, 303 LED display on user keys, 688 Rotary axis, 302 oem_sljk_deu.ts, 683 Switch, 303 slguiconfig.ini, 35...
Page 713 Index Display filter, 102 Multitool parameters Displaying, 95 Identifiers, 189 Editing enum values, 105 OEM identifier, 230 Editing hexadecimal values, 104 Entering BICO values, 105 Information, 96 Overview, 95 NC/PLC variables Search, 106 Changing, 407 Machine function, defining texts, 218 displaying, 405 Machine identity, 427 NCU connection...
Page 714 Index Parallel cylinder Protection area elements, 312 Parallel frame Protection area element, 308 RCS Commander, 18 Parallel linear axis Remote diagnostics Kinematic elements, 301 Adapting, 453 Parallel offset Replacing standard alarm texts Kinematic elements, 302 Create file, 270 Parallel sphere Creating texts, 270 Protection area elements, 311 Registering the alarm text file, 271...
Page 715 Index Setting-up a lathe with milling tools, 543 Spindle load, 154 Setting-up measuring in JOG, 624 Temperature, 151 ShopMill Temperature histograms, 154 Settings for milling, 520 Standard parameter specifications of alarm Tool-specific functions, 217 texts, 275 ShopTurn Starting SINUMERIK Operate Cylinder surface transformation, 546 IPC, 17 Face machining, 550...
Page 716 Index Swiveling, 558 Topologies, 401 Turning, 539 TRAANG, 553 Template files, 24 in turning, 551 Test license, 76 under ShopTurn, 552 Text legibility, 677 Trace TextPad, 18 Changing the scale, 472 Thread-cutting, 539 Creating a session, 459 Time Cursor A/B positioning, 474 Selecting the format, 31 Data acquisition, 467 Setting, 31...
Page 717 Index Parameter assignment for TOOLCARR (chain), 349 Parameter assignment for TOOLCARR (conventional), 352 Variable screen forms, 409 Parameter assignment for TRAANG_K, 348 Parameter assignment for TRANSMIT_K, 343 Parameter assignment for TRAORI_DYN, 338 Parameterizing TRACYL_K, 345 Selecting an element, 337 WinSCP, 18, 27 TRANSMIT Workpiece measurement in turning, 548...
Page 718 Index SINUMERIK Operate (IM9) Commissioning Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 719 Generating user dialogs Generating commissioning dialogs SINUMERIK SINUMERIK 840D sl Easy XML Programming Manual Valid for: CNC software Version 4.8 SP2 12/2017 6FC5397-1DP40-6BA1...
Page 720 Note the following: WARNING Siemens products may only be used for the applications described in the catalog and in the relevant technical documentation. If products and components from other manufacturers are used, these must be recommended or approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and maintenance are required to ensure that the products operate safely and without any problems.
Page 721 Table of contents Generating user dialogs..........................5 Scope of functions........................5 Fundamentals of Configuration....................7 Configuration files........................9 Structure of configuration file....................12 Language dependency......................18 XML diagnostics........................19 XML identifier.........................21 1.7.1 General structure........................21 1.7.2 Instruction/identifier descriptions....................22 1.7.3 Color coding...........................46 1.7.4 Special XML syntax........................46 1.7.5 Operators..........................47 1.7.6 System variables........................48 1.7.7 Generating softkey menus and dialog forms................49...
Page 722 Table of contents 1.12.3 Switch on/off.........................157 1.12.4 Functions of the switch......................158 1.12.4.1 Properties for the switch.......................158 1.12.4.2 Control variables for the switch....................159 1.12.5 Radio button.........................161 1.12.6 Checkbox..........................161 1.12.7 Groupbox..........................162 1.12.8 Scroll area..........................163 1.13 Sidescreen application......................166 1.13.1 Easy XML in the Sidescreen....................166 1.13.2 Integrating Sidescreen dialogs.....................167 1.13.3...
Page 723 Generating user dialogs Scope of functions Overview The "Generate user dialogs" function offers an open structure and enables the user to develop customer-specific and application-specific user interfaces in SINUMERIK Operate. The control system offers an XML-based script language for generating user dialogs. This script language makes it possible to display machine-specific menus and dialog forms in the <CUSTOM>...
Page 724 Generating user dialogs 1.1 Scope of functions 6. Variables – Read (NC, PLC and user variables) – Write (NC, PLC and user variables) – Combine with mathematical, comparison or logic operators 7. Execute functions: – Subprograms – File functions – PI services 8.
Page 725 Generating user dialogs 1.2 Fundamentals of Configuration Fundamentals of Configuration Configuration files The defining data for new user interfaces are stored in configuration files. These files are automatically interpreted and the result displayed on the screen. Configuration files are not stored in the software supplied and must first be set up and loaded by the user.
Page 726 Generating user dialogs 1.2 Fundamentals of Configuration Figure 1-2 Manufacturer's folder The following files in the manufacturer's folder "System CF-Card/oem/sinumerik/hmi" on the control are needed to configure user dialogs: Table 1-1 Files for configuration File type Name of the file Description Storage location in operating area Set‐...
Page 727 Generating user dialogs 1.3 Configuration files Configuration files Introduction The figure below shows the manufacturer’s folder "System CF-Card/oem/sinumerik/hmi" on the control. Figure 1-3 Manufacturer's folder The following files in the manufacturer's folder "System CF-Card/oem/sinumerik/hmi" on the control are needed to configure user dialogs: Table 1-2 Files for configuration File type...
Page 728 Generating user dialogs 1.3 Configuration files File type Name of the file Meaning Storage location in operating area Setup > System data Bitmaps The control system supports Manufacturer's folder > sub‐ BMP and PNG formats. directory "ico" The bitmaps are saved in the subdirectory for the screen resolution belonging to the control.
Page 729 Generating user dialogs 1.3 Configuration files Load configuration As described in the "Storage location in the operating area" column in the previous "Files for configuration" table, the generated files must be copied to the appropriate subdirectories in the manufacturer's folder. Note As soon as there is a script file "xmldial.xml"...
Page 730 Generating user dialogs 1.4 Structure of configuration file Structure of configuration file Overview A configuration file consists of the following elements: ● Description of the "main" start menu with start softkeys ● Definition of the dialogs ● Definition of the variables ●...
Page 731 Generating user dialogs 1.4 Structure of configuration file xmldial.xml <DialogGui> ...
Page 732 Generating user dialogs 1.4 Structure of configuration file xmldial.xml <control name = "edit11" xpos = "210" ypos = "56" refvar="nck/Channel/ GeometricAxis/progDistToGo[0]" hotlink="true" fieldtype="readonly" format="%9.3f" time="super fast"/> <control name = "edit12" xpos = "210" ypos = "76" refvar="nck/Channel/ GeometricAxis/progDistToGo[1]" hotlink="true" fieldtype="readonly" format="%9.3f"...
Page 733 Generating user dialogs 1.4 Structure of configuration file Dialog form section "R Parameters" Easy XML Programming Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 734 Generating user dialogs 1.4 Structure of configuration file xmldial.xml .. <menu name ="MENU_R_PARAMETER"> <OPEN_FORM name = "R-Parameter" /> <softkey POSITION="16"> <caption>Back</caption> <navigation>MAIN</navigation> </softkey> </menu> <form name = "R-Parameter"> <init> <DATA_ACCESS type="true" /> <caption>R - Parameter</caption> <control name = "edit1"...
Page 735 Generating user dialogs 1.4 Structure of configuration file xmldial.xml </paint> </form> </DialogGui> Easy XML Programming Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 736 Generating user dialogs 1.5 Language dependency Language dependency Language-dependent texts are used for: ● Softkey labels ● Headers ● Help texts ● Any other texts The language-dependent texts are stored in text files. Note You will need to perform the following steps when using these text files: ●...
Page 737 Generating user dialogs 1.6 XML diagnostics XML diagnostics The system provides the Easy XML diagnostic function for diagnosing and finding script errors. The use of the diagnostic function checks the XML syntax and runs through all the scripts belonging to the project. To do this, functions, menus, forms and the existence/validity of variables are also checked.
Page 738 Generating user dialogs 1.6 XML diagnostics Dialog Softkey Function "Document" dialog Save Changes in the XML file are be‐ ing saved. Cancel The XML file is closed un‐ changed. The check result is dis‐ played again. Easy XML Programming Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 739 Generating user dialogs 1.7 XML identifier XML identifier 1.7.1 General structure Structure and instructions of the script file for dialog configuration All dialog configurations should be stored in the DialogGui tag. <DialogGui> … </DialogGui> Example: <?xml version="1.0" encoding="utf-8"?> <DialogGui> … <FORM name ="Hello_World">...
Page 740 Generating user dialogs 1.7 XML identifier 1.7.2 Instruction/identifier descriptions The following XML tags are defined for generating dialogs and menus, and for executing program sequences: Note Attribute values that are in quotation marks "<...>" should be replaced by the currently used expressions.
Page 741 Generating user dialogs 1.7 XML identifier Tag identifier Meaning CREATE_CYCLE_EVENT If the parser starts to process the tag CREATE_CYCLE, initially, the message <CRE‐ ATE_CYCLE_EVENT sent> is sent to the active form. This message can be used for pre‐ paring the cycle parameters, before the parser generates the NC operation from the pa‐ rameter list and the generation rule.
Page 742 Generating user dialogs 1.7 XML identifier Tag identifier Meaning DATA The tag allows writing to NC, PLC, GUD and drive data. The "Component addressing" (Page 85) section contains details on address formation. Attribute: ● name Variable address Tag value: All alphanumeric terms are approved as tag values. If a value is to be written directly from a local variable, the name of the local variable should be preceded by the $ replacement operator.
Page 743 Generating user dialogs 1.7 XML identifier Tag identifier Meaning DATA_LIST The tag enables the listed drive and machine data to be saved or restored. Addresses are listed in lines. Chapter "Component addressing" (Page 85) describes how addresses are formed. Up to 20 temporary data lists can be created. Attributes: ●...
Page 744 Generating user dialogs 1.7 XML identifier Tag identifier Meaning DYNAMIC_INCLUDE The tag includes an XML script file. Contrary to the INCLUDE tag, read-in is first only realized when executing the corresponding operation. For large projects, the use of the tag reduces the load time of the customer area and/or the cycle support.
Page 745 Generating user dialogs 1.7 XML identifier Tag identifier Meaning For loop for (initialization; test; continuation) instruction(s) Syntax: <FOR> <INIT>…</INIT> <CONDITION>…</CONDITION> <INCREMENT>…</INCREMENT> Instructions … </FOR> The For loop is executed as follows: 1. Evaluation of the expression initialization (INIT). 2. Evaluation of the expression test (CONDITION) as a Boolean expression. If the value is false, the For loop is exited.
Page 746 Generating user dialogs 1.7 XML identifier Tag identifier Meaning Conditional instruction (IF, THEN, ELSE) The THEN and ELSE tags are enclosed in the IF tag. The condition that is executed in the CONDITION tag follows the IF tag. The further pro‐ cessing of the instructions depends upon the result of the operation.
Page 747 Generating user dialogs 1.7 XML identifier Tag identifier Meaning The instruction creates a local variable under the specified name. Fields: Using the attribute dim (dimension) single or two-dimensional fields can be created. The field index addresses the individual field elements. For a two-dimensional field, initially the line index is specified and then the column index.
Page 748 Generating user dialogs 1.7 XML identifier Tag identifier Meaning LET Continued Example: One-dimensional field: <let name="array" dim="10"></let> Two-dimensional field: <let name="list_string" dim="10,3" type="string"></let> Pre-assignment: A variable can be initialized with a value. <LET name = "VAR1" type = "INT"> 10 </LET> If values comprising NC or PLC variables are saved in a local variable, the assignment operation automatically adapts the format to that of the variables which have been loaded.
Page 749 Generating user dialogs 1.7 XML identifier Tag identifier Meaning LET Continued Variable type struct: This variable type contains a composition of variables that can be addressed using the structure name. A structure can contain all variable types and structures. Within the structure, a variable is declared with the "element" tag. The attributes of the tags and the initialization correspond to the attributes and initialization of the let instruction.
Page 750 Generating user dialogs 1.7 XML identifier Tag identifier Meaning LOCK_OPERATING_AREA The operating area switchover is locked. The operating area switchover lock is withdrawn with the UNLOCK_OPERATING_AREA tag. Syntax: <LOCK_OPERATING_AREA /> The operator component shows the message which is indicated in the tag. If an alarm number is used, the dialog box displays the text which is saved for the number.
Page 751 Generating user dialogs 1.7 XML identifier Tag identifier Meaning The tag executes the specified operations. The operations listed in Chapter "Operators (Page 47)" can be executed. For the purpose of accessing the NC, PLC, and drive data, the complete variable name should be placed in quotation marks.
Page 752 Generating user dialogs 1.7 XML identifier Tag identifier Meaning OPERATION Operation Instructions can be moved within an equation. Move left "<<" operator The << function moves bits to the left. You can specify the value and the number of move increments directly or with a variable.
Page 753 Generating user dialogs 1.7 XML identifier Tag identifier Meaning PRINT The tag outputs a text in the dialog line or copies the text to the variable specified. If the text contains formatting identifiers, the variable values are inserted at the appropriate places.
Page 754 Generating user dialogs 1.7 XML identifier Tag identifier Meaning PRINT Continued Values: Number of variables whose values are to be inserted into the text. The variable types must match the corresponding type identifier for the formatting instruction and must be separated from one another with a comma. Example: Output of a text in the information line <PRINT text="Infotext"...
Page 755 Generating user dialogs 1.7 XML identifier Tag identifier Meaning SEND_MESSAGE The tag sends a message with two parameters to the active form, which is processed in the tag message. Syntax: <SEND_MESSAGE>p1, p2</SEND_MESSAGE> Example: <SOFTKEY POSITION="3"> <caption>Set%nParameter</caption> <send_message>1, 0</send_message> </SOFTKEY> <FORM> …...
Page 756 Generating user dialogs 1.7 XML identifier Tag identifier Meaning SLEEP The tag interrupts script execution for the specified period. The interruption time is obtained from the transferred value multiplied by the time base of 50 ms. Syntax: <SLEEP value="Interruption time" /> Example: Wait time, 1.5 sec.
Page 757 Generating user dialogs 1.7 XML identifier Tag identifier Meaning SWITCHTOAREA The SWITCHTOAREA tag changes from the Customer area into the specified operating area. The parameter is specified as an attribute value. Syntax: <switchToArea name="area" args="argument "/> Attributes: name The following names are declared for the operating areas: ●...
Page 758 Generating user dialogs 1.7 XML identifier Tag identifier Meaning TYPEDEF A new identifier for a data type can be defined with this tag. This has the benefit for the structure definitions that the data type can be defined once and then used as a data type in a LET instruction.
Page 759 Generating user dialogs 1.7 XML identifier Tag identifier Meaning TYPEDEF Continued Some predefined functions expect variables of structure type RECT, POINT, or SIZE as the call parameter. These structures are defined in the file struct_def.xml. RECT: <typedef name="StructRect" type="struct" > <element name="left"...
Page 760 Generating user dialogs 1.7 XML identifier Tag identifier Meaning WHILE WHILE loop WHILE (Test) Instruction Syntax: <WHILE> <CONDITION>…</CONDITION> Instructions … </WHILE> The While loop executes a sequence of instructions repeatedly while a condition is met. This condition is tested before the sequence of instructions is executed. Example: <WHILE>...
Page 761 Generating user dialogs 1.7 XML identifier Tag identifier Meaning XML_PARSER Continued Interfaces The value of the name attribute contains the path to the XML file. To assign events to the call-back functions, the following properties must be specified: Standard startElementHandler endElementHandler charactersHandler Optional...
Page 762 Generating user dialogs 1.7 XML identifier Tag identifier Meaning XML_PARSER Continued The parser also supplies variables so that the call-back functions can access the event data. startElementHandler: Function parameters tag_name - tag name - number of attributes found System variables $xmlAttribute String array with the number of elements indicated by num.
Page 763 Generating user dialogs 1.7 XML identifier Tag identifier Meaning XML_PARSER Continued charactersHandler: System variables $xmlCharacters String with data $xmlCharactersStart Always 0 $xmlCharactersLength Number of bytes Example: <function_body name="charactersHandler" return="true" > <print text="chars %s"> $xmlCharacters </print> </function_body> documentHandler: Function parameters state 1 start document, 2 end document errorHandler: System variables...
Page 764 Generating user dialogs 1.7 XML identifier 1.7.3 Color coding The color attribute uses the color coding scheme for the HTML language. In terms of syntax, color specifications consist of the "#" (hash) character and six digits from the hexadecimal system, with each color represented by two digits. R –...
Page 765 Generating user dialogs 1.7 XML identifier 1.7.5 Operators The operation instruction processes the following operators: Operator Meaning Assignment Equal to <, < Less than >, > Greater than <=, <= Less than or equal to >=, >= Greater than or equal to OR operation in bits Logic OR operation &, &...
Page 766 Generating user dialogs 1.7 XML identifier 1.7.6 System variables System variables are variables available in every script, which are used for exchanging data between the parser and the script execution. The following table provides an overview of the tags for which variables are automatically generated.
Page 767 Generating user dialogs 1.7 XML identifier 1.7.7 Generating softkey menus and dialog forms User menus can only be inserted if there is a main-menu tag with the name "main" in the XML description. This tag is called by the system after the <CUSTOM> operating area has been activated.
Page 768 Generating user dialogs 1.7 XML identifier Tag identifier Meaning FORM The tag contains the description of a user dialog. The relevant tags are described in the section on generating menus and dialog forms. Syntax: <FORM name="<dialog name>" color="#ff0000"> Attributes: ● color Background color of the dialog form (color coding, see Chapter "Color coding (Page 46)") –...
Page 769 Generating user dialogs 1.7 XML identifier Tag identifier Meaning FORM continued Dialog messages: ● INIT ● PAINT ● TIMER ● CLOSE ● FOCUS_IN ● INDEX_CHANGED ● EDIT_CHANGED ● GESTURE_EVENT ● KEY_EVENT ● MESSAGE ● MOUSE_EVENT ● RESIZE FORM continued Easy XML Programming Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 770 Generating user dialogs 1.7 XML identifier Tag identifier Meaning FORM continued Syntax: <FORM name = "<dialog name>" color = "#ff0000"> Example: <FORM name = "R-Parameter"> <INIT> <DATA_ACCESS type = "true" /> <CAPTION>R - Parameter</CAPTION> <CONTROL name = "edit1" xpos = "322" ypos = "34" refvar = "nck/ Channel/Parameter/R[1]"...
Page 771 Generating user dialogs 1.7 XML identifier Tag identifier Meaning KEY_EVENT Dialog message The tag KEY_EVENT can be integrated in the form to evaluate keyboard events. The system sends the MF2 keyboard code to the active form if the tag is available in a form. If the variable $actionresult is not set to zero, the system then subsequently processes the keyboard event.
Page 772 Generating user dialogs 1.7 XML identifier Tag identifier Meaning MOUSE_EVENT The tag can be linked into the script for processing mouse events. It is executed when the following activities have been performed with the mouse: ● A button has been pressed ●...
Page 773 Generating user dialogs 1.7 XML identifier Tag identifier Meaning MESSAGE Dialog message If the Send_message operation is executed in the script, then the parser processes the tag message. Values P1 and P2 are provided in the variables $message_par1 and $mes‐ sage_par2 (see the "SEND_MESSAGE"...
Page 774 Generating user dialogs 1.7 XML identifier Tag identifier Meaning SEND_MESSAGE The tag sends a message with two parameters to the active form, which is processed in the tag message (see also MESSAGE). Syntax: <SEND_MESSAGE>p1, p2</SEND_MESSAGE> Example: <LET name="user_selection" /> <SOFTKEY POSITION="3"> <CAPTION>Set%nParameter</CAPTION>...
Page 775 Generating user dialogs 1.7 XML identifier Tag identifier Meaning RESIZE Dialog box message The tag can be linked into the script for processing a RESIZE event. This event is created by a dynamic resolution switchover. Easy XML Programming Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 776 Generating user dialogs 1.7 XML identifier Tag identifier Meaning RESIZE Continued Example: <let name="screen_size" type="StructSize" /> <form name="menu_userscale_form" autoscale_content="off"> <init> <caption>Use auto scaling</caption> <function name="hmi.get_hmi_resolution">screen_size</function> <print text="screen size: w %d h: %d">screen_size.width, screen_size.height</print> <data_access type="true" /> <control name="s_c" xpos="8" ypos="140" fieldtype="readonly" width="500"...
Page 777 Generating user dialogs 1.7 XML identifier Tag identifier Meaning FOCUS_IN Dialog box message The tag is called if the system places the focus on a control. To identify the control, the system copies the name of the control into variable $focus_name and the value of the attribute item_data into variable $focus_item_data.
Page 778 Generating user dialogs 1.7 XML identifier Tag identifier Meaning CLOSE_FORM The tag closes the active dialog. This instruction is only necessary if the dialog is opened by the MMC command and the user is offered a softkey function to close the dialog. Generally, dialogs are automatically managed and do not have to be explicitly closed.
Page 779 Generating user dialogs 1.7 XML identifier Tag identifier Meaning CONTROL The tag is used to generate control elements. Syntax: <CONTROL name = "<control name>" xpos = "<X position>" ypos = "<Y position>" refvar = "<NC variable>" hotlink = "true" format = "<format>"...
Page 780 Generating user dialogs 1.7 XML identifier Tag identifier Meaning CONTROL Continued ● fieldtype – graphicbox The field type generates a 2D broken line graphic control. Using the tag <ITEM> a graphical element can be inserted into the control. Parameters width and height specify the width and height of the box.
Page 781 Generating user dialogs 1.7 XML identifier Tag identifier Meaning CONTROL continued ● fieldtype – listbox The field type generates an empty list box control. Using the tag <ITEM> a list box element can be inserted in the list box. The ITEM attribute value allows this element to be assigned a unique value. This can serve to identify the element, for example.
Page 782 Generating user dialogs 1.7 XML identifier Tag identifier Meaning CONTROL continued Example: <CONTROL name = "button1" xpos = "10" ypos = "10" fieldtype = " combobox "> <ITEM>text1</ITEM> <ITEM>text2</ITEM> <ITEM>text3</ITEM> <ITEM>text4</ITEM> </CONTROL> If any integer value is to be assigned to an expression, the attribute value = "value" should be added to the tag.
Page 783 Generating user dialogs 1.7 XML identifier Tag identifier Meaning CONTROL Continued The image box control manages a picture in bitmap or GIF format. If the picture is larger than the displayable area, the control will show a scroll bar. To control the visible area, the system provides the function CONTROL.IMAGEBOXSET (see Chapter "Predefined functions (Page 98)").
Page 784 Generating user dialogs 1.7 XML identifier Tag identifier Meaning CONTROL continued Control change in an operating instruction Another possibility of changing properties of a control during runtime is to make the change in an operating instruction. Therefore the name of the control and the property to which a new value is to be assigned must be defined.
Page 785 Generating user dialogs 1.7 XML identifier Tag identifier Meaning DATA_ACCESS The tag controls the behavior of the dialog forms when user inputs are being saved. The behavior should be defined within the INIT tag. If the tag is not used, inputs are buffered in each case. Exception: Controls for which the hotlink attribute is set to true are always written to and read directly.
Page 786 Generating user dialogs 1.7 XML identifier Tag identifier Meaning MENU The tag defines a menu containing the softkey description and the dialog to be opened. Attribute: ● name Menu name Syntax: <MENU name = "<menu name>"> … <open_form …> … <SOFTKEY …>...
Page 787 Generating user dialogs 1.7 XML identifier Tag identifier Meaning OPEN_FORM The tag opens the dialog form given under the name. Attribute: ● name Name of the dialog form Syntax: <OPEN_FORM name = "<form name>" /> Example: <menu name = "main"> <open_form name = "main_form"...
Page 788 Generating user dialogs 1.7 XML identifier Tag identifier Meaning PROPERTY This tag can be used to define additional properties for an operator control. The tag is embed‐ ded in the control tag. Attributes: ● max = "<maximum value>" ● min = "<minimum value>" ●...
Page 789 Generating user dialogs 1.7 XML identifier Tag identifier Meaning SOFTKEY The tag defines the properties and responses of a softkey. Attributes: ● position Number of the softkey. 1-8 horizontal softkeys, 9-16 vertical softkeys The following attributes become effective from: ● type Defines the property of the softkey.
Page 790 Generating user dialogs 1.7 XML identifier Tag identifier Meaning SOFTKEY continued The following additional actions can be defined within the softkey block: ● picturealignment The image orientation is specified by this attribute. The image is aligned with the left side of the softkey by default. The following values can be specified for alignment: –...
Page 791 Generating user dialogs 1.7 XML identifier Tag identifier Meaning SOFTKEY continued Syntax: Standard softkey: <state type="<softkey state>" /> <softkey position = "<1>"> … … </softkey> Script-controlled softkey: <softkey position = "<1>" type="<user_defined>" > <state type="<softkey state>" /> … … </softkey> Toggle softkey: <softkey position = "<1>"...
Page 792 Generating user dialogs 1.7 XML identifier Tag identifier Meaning SOFTKEY continued Example: <let name="curr_softkey_state" type="string">PRESSED</let> </softkey> <softkey POSITION="3" type="toggle_softkey" refvar="curr_softkey_state"> <caption>Toggle%nSK</caption> … </softkey> SOFTKEY_OK The tag defines the response of the softkey "OK". The following additional actions can be defined within the softkey block: ●...
Page 793 Generating user dialogs 1.7 XML identifier Tag identifier Meaning SOFTKEY_BACK The tag defines the response of the softkey "Back". The following additional actions can be defined within the softkey block: ● navigation ● update_controls ● function Syntax: <SOFTKEY_BACK> … … </SOFTKEY_BACK>...
Page 794 Generating user dialogs 1.7 XML identifier Tag identifier Meaning The tag is used to display an image in the specified position. The BMP and PNG image formats are supported. Syntax: <IMG xpos = "<X position>" ypos = "<Y position>" name = "<name>" /> <IMG …...
Page 795 Generating user dialogs 1.7 XML identifier Tag identifier Meaning The tag draws a rectangle at the specified position, colored as indicated. Syntax: <BOX xpos = "<X position>" ypos = "<Y position>" width = "<X extension>" height = "<Y extension>" color = "<Color code>" /> Attributes: ●...
Page 796 Generating user dialogs 1.7 XML identifier Tag identifier Meaning FUNCTION_BODY Function body The tag contains the function body of a subfunction. The function body needs to be program‐ med within the DialogGui tag. Attributes: ● name = "Name of the function body" ●...
Page 797 Generating user dialogs 1.7 XML identifier Tag identifier Meaning FUNCTION_BODY contin‐ Example: <function_body name = "test" parameter = "c1,c2,c3" return = "true"> <LET name = "tmp">0</LET> <OP> tmp = c1+c2+c3 </OP> <OP> $return = tmp </OP> </function_body> … … … <LET name = "my_var">...
Page 798 Generating user dialogs 1.7 XML identifier Tag identifier Meaning RECALL This tag can be used in a menu if a navigation is to take place via Recall button. If the tag is programmed, the Recall icon is shown, and the parser may process the Recall button. Syntax: <recall>...
Page 799 Generating user dialogs 1.8 Generating user menus Generating user menus 1.8.1 Creating processing cycle forms The cycle support function allows the automatic creation and decompilation of a cycle call through the form dialog. To manage this functionality, the following tags are available: ●...
Page 800 Generating user dialogs 1.8 Generating user menus This is then copied to the specified variable. Tag identifier Description NC_INSTRUCTION This tag is used to define the NC instruction to be generated. All listed cycle parameters are automatically created as string variables of the FORM and are available to the FORM.
Page 801 Generating user dialogs 1.8 Generating user menus Tag identifier Description CREATE_CYCLE The tag generates an NC block, whose syntax is defined by the value of the NC_IN‐ STRUCTION tag. Before generating the NC instruction, the parser calls the CYCLE_CRE‐ ATE_EVENT tag of the FORM. This tag can be used to calculate the cycle param‐ eters.
Page 802 Generating user dialogs 1.8 Generating user menus 1.8.2 Substitution characters The system offers the option of defining control properties (attribute values) for the runtime. In order to use this function, the desired property must be set in a local variable and the variable name must be transferred to the tag as an attribute value preceded by the character $.
Page 803 Generating user dialogs 1.9 Addressing components Addressing components Address identifiers for the desired data must be created to address NC variables, PLC blocks or drive data. An address consists of the subpaths component name and variable address. A slash should be used as a separating character. 1.9.1 PLC addressing Addressing the PLC starts with the path section plc.
Page 804 Generating user dialogs 1.9 Addressing components 1.9.2 Addressing NC variables Addressing the NC variables starts with the path section nck. This section is followed by the data address; its structure should be taken from the List Manual NC Variables and Interface Signals. Example: <LET name = "tempStatus"></LET>...
Page 805 Generating user dialogs 1.9 Addressing components 1.9.5 Addressing drive components Addressing the drive components starts with the path section drive. Then the drive device is specified: CU – Control Unit DC – Drive Control (Motor Module) CULNK – Expansion Modules (HUBs) TM –...
Page 806 Generating user dialogs 1.9 Addressing components Figure 1-7 Drive parameter p0978 [ ...] at the control Parameter number[do<DO-index>] Example: p0092[do1] Alternatively, the drive index can be read from a local variable using $<variable name> "substitution characters". z.B. DO$local variable Example: <DATA name ="drive/cu/p0092">1</DATA>...
Page 807 Generating user dialogs 1.9 Addressing components 1.9.6 Example: Determine the DO number for the Motor Module The DO number of a type 11 (servo) Motor Module can be determined as follows: All connected drive objects are listed with their slot number in field p978 of the relevant CU. The component type numbers are listed in the field p101 and the component types are listed in the field p107 simultaneously.
Page 808 Generating user dialogs 1.9 Addressing components Sample scripts: xmldial.xml and drv_sys_hlpfunct.xml xmldial.xml <DialogGui> <?include src="f:\appl\drv_sys_hlpfunct.xml" ?> <menu name = "main"> <open_form name = "main_form" /> <softkey POSITION="1"> <caption></caption> <navigation>main</navigation> </softkey> </menu> <form name="main_form"> <init> <caption>Component arrangement</caption> <let name="count" /> <let name="str" type="string" /> <let name="do_name"...
Page 809 Generating user dialogs 1.9 Addressing components xmldial.xml <function name="control.additem">_T"list_comp_no_do_idx", str, count</ function> <op> count = count +1; </op> </while> <paint> <text xpos="8" ypos="30">Motor moduls</text> <text xpos="8" ypos="60">CU</text> <text xpos="40" ypos="60">Comp.</text> <text xpos="92" ypos="60">DO Index</text> <text xpos="172" ypos="60">Name</text> </paint> </form> </DialogGui> Easy XML Programming Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 810 Generating user dialogs 1.9 Addressing components drv_sys_hlpfunct.xml <typedef name="components" type="struct"> <element name="cu_p978" dim="25" /> <element name="do_p0101" dim="25" /> <element name="do_p0107" dim="25" /> </typedef> <typedef name="comp_no_do_idx_map" type="struct">  <element name="cu_idx" />  <element name="comp_no" /> ...
Page 811 Generating user dialogs 1.9 Addressing components drv_sys_hlpfunct.xml <function name="ncfunc.cap.read" return="error" rows="$count">componentsList[$cuno].do_p0107, "drive/cu/p0107[0, cu $cuidx]"</function> <print text="gather data finished" /> <sleep value="20" /> <op> count = 0; </op> <while> <condition>count < _drv_sys_comp_array_size</condition> <if> <condition>componentsList[$cuno].cu_p978[$count] == 60</condition> <then> <op> next_nx= next_nx +1; </op>...
Page 812 Generating user dialogs 1.9 Addressing components drv_sys_hlpfunct.xml count = 0; </op> <while> <condition>count < _drv_sys_comp_array_size</condition> <if> <condition> componentsList[$cuno].do_p0107[$count] == 11</condition> <then> <op> address_idx_map[$map_index].cu_idx = cuno+1; address_idx_map[$map_index].comp_no = componentsList[$cuno].do_p0101[$count]; address_idx_map[$map_index].do_idx = do_index; do_index = do_index+1; map_index = map_index +1; </op> </then> </if>...
Page 813 Generating user dialogs 1.9 Addressing components 1.9.7 Addressing machine and setting data Drive and setting data is identified by the character $ followed by the name of the data. Machine data: $Mx_<name[index, AX<axis_number>]> Setting data: $Sx_<name[index, AX<axis_number>]> N – General machine or setting data C –...
Page 814 Generating user dialogs 1.9 Addressing components 1.9.8 Channel-specific machine data If no channel number is defined in the address token, access is always to the currently set channel of the operating software. If it is necessary to read data from a specific channel, the identifier u (Unit) with the desired channel number in square brackets is added to the address.
Page 815 Addressing starts with the path section gud, followed by the specification of the area CHANNEL. This address section is followed by the specification of the GUD areas: GUD areas Assignment sgud Siemens GUD mgud Machine manufacturer GUD ugud User GUD...
Page 816 Generating user dialogs 1.10 Predefined functions 1.10 Predefined functions The script language offers various string processing and standard mathematical functions. The function names listed below are reserved and cannot be overloaded. Function name Description Ncfunc cap read The function copies a value from the specified address into a local variable.
Page 817 Generating user dialogs 1.10 Predefined functions Function name Description Ncfunc cap write The function writes a value into the specified variable. If the write op‐ eration was error-free, then the return variable contains the value zero. Contrary to the operation instruction, in the event of a fault, this func‐ tion does not interrupt the processing of the script operations.
Page 818 Generating user dialogs 1.10 Predefined functions Function name Description Ncfunc PI-Service Jobs can be transferred to the NCK using the program invocation (PI) service. If the service has been executed error-free, the function returns the value 1 in the return variable. Manipulation of the tool list _N_CREATO - Create tool _N_DELETO - Delete tool...
Page 819 Generating user dialogs 1.10 Predefined functions Function name Description Ncfunc PI-Service Continued Arguments: ● _N_CREATO var1 - Tool number ● _N_DELETO var1 - Tool number ● _N_CREACE var1 - Tool number var2 - Cutting edge number ● _N_DELECE var1 - Tool number var2 - Cutting edge number ●...
Page 820 Generating user dialogs 1.10 Predefined functions Function name Description ncfunc chan PI-Service The function executes a PI service in a channel-related manner. The channel number is passed after the PI service name. This is followed by all other call parameters. Parameters: channel - Channel number Syntax:...
Page 821 Generating user dialogs 1.10 Predefined functions Function name Description Ncfunc bico to int The function converts a string specified in BICO format into an integer value. (see SINAMICS) Syntax: <function name="ncfunc.bicotoint" return="integer variable">bico-string</function> Example: <let name="s_np0480_0" type="string"></let> <let name="i_p0480_0">0</let> <function name="ncfunc.bicotoint" return="i_p0480_0">s_np0480_0</function>...
Page 822 Generating user dialogs 1.10 Predefined functions Function name Description Ncfunc password This function sets or deletes a password level from the NC. ● Set password: The password should be specified for the required password level as parameter. ● Delete password: A blank string deletes the password level.
Page 823 Generating user dialogs 1.10 Predefined functions Function name Description Control local time The function copies the local time in a field with 7 array elements. The name of the variable is expected as call parameter. The following is stored in an array element: ●...
Page 824 Generating user dialogs 1.10 Predefined functions Function name Description String to compare Two strings are compared with one another from a lexicographical perspective. The function gives a return value of zero if the strings are the same, a value less than zero if the first string is smaller than the second string or a value greater than zero if the second string is smaller then the first string.
Page 825 Generating user dialogs 1.10 Predefined functions Function name Description String to compare without making a distinction be‐ Two strings are compared from a lexicographical perspective (the tween uppercase/lowercase comparison is not case-sensitive). The function gives a return value of zero if the strings are the same, a value less than zero if the first string is smaller than the second string or a value greater than zero if the second string is smaller then the first string.
Page 826 Generating user dialogs 1.10 Predefined functions Function name Description String right The function extracts the last nCount character from string 1 and cop‐ ies this to the return variable. Parameter: str1 - string nCount - number of characters Syntax: <function name="string.right" return="<result string>">...
Page 827 Generating user dialogs 1.10 Predefined functions Function name Description String length The function gives the number of characters in a string. Parameter: str1 - string Syntax: <function name="string.length" return="<int var>"> str1 </function> Example: <let name="length">0</let> <let name="str1" type="string">A brown bear hunts a brown dog.</let>...
Page 828 Generating user dialogs 1.10 Predefined functions Function name Description Strings to remove The function removes all the substrings found. Parameter: string - string variable remove string - substring to be deleted Syntax: <function name="string.remove"> string, remove string </function> Example: <let name="index">0</let> <let name="str1"...
Page 829 Generating user dialogs 1.10 Predefined functions Function name Description String delete The function deletes the defined number of characters starting from the start position specified. Parameter: string - string variable start index - start index (zero based) nCount - number of characters to be deleted Syntax: <function name="string.delete">...
Page 830 Generating user dialogs 1.10 Predefined functions Function name Description String reverse find The function searches the transferred string for the last match with the substring. If the substring is found, the function provides the index to the first character (starting with zero) or, failing this, -1. Parameter: string - string variable find string - string to be found...
Page 831 Generating user dialogs 1.10 Predefined functions Function name Description String trim right The function trims the closing characters from a string. Parameter: str1 - string variable Syntax: <function name="string.trimright" > str1 </ function> Example: <let name="str1" type="string"> test trim right </let>...
Page 832 Generating user dialogs 1.10 Predefined functions Function name Description Tangent The function calculates the tangent of the value transferred in degrees. Parameter: double - angle Syntax: <function name="tan" return="<double val>"> double </function> Example: <let name= "tan_val" type="double"></let> <function name="tan" return="tan_val"> 20.0 </ function>...
Page 833 Generating user dialogs 1.10 Predefined functions Function name Description ARCTAN The function calculates the arctan of the value transferred in degrees. Parameter: double - arctan of y/x Syntax: <function name="arctan" return="<double val>"> double </function> Example: <let name= "arctan_val" type="double"></let> <function name="arctan" return="arctan_val"> 20.0 </function>...
Page 834 Generating user dialogs 1.10 Predefined functions Function name Description Reading a file The function reads the contents of the specified file into a string varia‐ ble. The number of characters to be read can optionally be specified as a second parameter. Attribute: name - The file name should be written in lowercase letters.
Page 835 Generating user dialogs 1.10 Predefined functions Function name Description Writing to a file The function writes the contents of a string variable to the file specified. The file name should be written in lowercase letters. Files in other directories are accessed via a relative path that uses the appl or dvm directory as a starting point.
Page 836 Generating user dialogs 1.10 Predefined functions Function name Description Deleting a file The function removes the file specified from the directory. The file name should be written in lowercase letters. Files in other directories are accessed via a relative path that uses the appl or dvm directory as a starting point.
Page 837 Generating user dialogs 1.10 Predefined functions Function name Description Extracting script parts The function copies a dialog description embedded in a part program into the specified local variable. The call parameters to be specified are the program name, the dialog name, and a variable for storing the main menu name.
Page 838 Generating user dialogs 1.10 Predefined functions Function name Description Exist If the file exists, the function returns the value 1. The file name should be written in lowercase letters. Files in other directories are accessed via a relative path that uses the appl or dvm directory as a starting point.
Page 839 Generating user dialogs 1.10 Predefined functions Function name Description Setting an individual bit The function is used to manipulate individual bits of the specified var‐ iables. The bits can either be set or reset. Syntax: <function name="ncfunc.bitset" refvar="address" value="set/reset" > bit0, bit1, … bit9 </function> Attributes: refvar - specifies the name of the variable, in which the bit combination should be written...
Page 840 Generating user dialogs 1.10 Predefined functions Function name Description Add Item The function inserts a new element at the end of the list. Note: The function is only available for the control types "listbox" and "graph‐ icbox". Syntax: <function name="control.additem"> control name, item </function>...
Page 841 Generating user dialogs 1.10 Predefined functions Function name Description Insert Item The function inserts a new element at the specified position. Note: The function is only available for the control type "listbox". Syntax: <function name="control.insertitem"> control name, index, item, itemdata </function> Attribute: name –...
Page 842 Generating user dialogs 1.10 Predefined functions Function name Description Load Item The function inserts a list of expressions into the control. The function is only available for the control types "listbox" and "graph‐ icbox". Syntax: <function name="control.loaditem"> control name, list </function> Attribute: name –...
Page 843 Generating user dialogs 1.10 Predefined functions Function name Description Empty The function deletes the contents of the specified list box or graphic box controls. Syntax: <function name="control.empty"> control name, </ function> Attribute: name – function name Values: control name – control name Example: <function name="control.empty">_T"listbox1"</ function>...
Page 844 Generating user dialogs 1.10 Predefined functions Function name Description Set focus The function sets the input focus to the specified control. The Controlname should be transferred as text expression of the func‐ tion. Syntax: <function name="control.setfocus"> control name </ function> Attribute: name –...
Page 845 Generating user dialogs 1.10 Predefined functions Function name Description Get Item For a list box, the function copies the contents of the selected line to the specified variable. A string variable should be specified as reference variable. The Controlname should be transferred as text expression of the func‐ tion.
Page 846 Generating user dialogs 1.10 Predefined functions Function name Description Image Box Set This function is used to control the visible area of the image box control. The call parameters to be specified are the control name, the control command, and the associated values. Syntax: <function name="control.imageboxset">control name, command, command parameter</function>...
Page 847 Generating user dialogs 1.10 Predefined functions Function name Description Image Box Get This function is for querying the control properties image box The call parameters to be specified are the control command and the associ‐ ated values. Syntax: <function name="control.imageboxget">control name, command, command parameter</function>...
Page 848 Generating user dialogs 1.10 Predefined functions Function name Description Get Caption Height The function returns the title bar height in pixels. Syntax: <function name="hmi.get_caption_heigt" return="<return var>" /> Attributes: return - integer variable This function returns the absolute value of the specified number. Syntax: <function name="abs"...
Page 849 Generating user dialogs 1.10 Predefined functions Function name Description The function calculates the logarithm of the specified value. Syntax: <function name="log" return="var"> value </ function> LOG10 The function calculates the common (decadic) logarithm of the speci‐ fied value. Syntax: <function name="log10" return="var"> value </ function>...
Page 850 Generating user dialogs 1.10 Predefined functions Function name Description Function: You can use the MMC command to display user-defined dialog boxes (dialog screens) from the part program in SINUMERIK Operate. The appearance of the dialog boxes is defined in a pure text configuration (XML file in the manufacturer’s folder).
Page 851 Generating user dialogs 1.10 Predefined functions Function name Description MMC continued Example of synchronous call: Due to changes in the operate base system, the parameters are as follows: XML → CYCLES or POPUPDLG XML_ON → PICTURE_ON XML_OFF → PICTURE_OFF NC instruction MMC("EASYXML oder CYCLES”,XML_ON,mmc_cmd.xml,cmd1,,,,,","S") File: mmc_cmd.xml...
Page 852 Generating user dialogs 1.10 Predefined functions Function name Description MMC continued Example of extraction of script parts from a part program: Due to changes in the operate base system, the parameters are as follows: XML → CYCLES or POPUPDLG XML_ON → PICTURE_ON XML_OFF →...
Page 853 Generating user dialogs 1.10 Predefined functions Function name Description MMC continued Programming example ;<main_dialog entry="rpara_main"> ; <let name="xpos" /> ; <let name="ypos" /> ; <let name="field_name" type="string" /> ; <let name="num" /> ; <menu name="rpara_main"> ; <open_form name="rpara_form"/> ; <softkey_back> ;...
Page 854 Generating user dialogs 1.10 Predefined functions Function name Description ; <text xpos = "$xpos" ypos = "$ypos" >$$ $field_name</text> ; <op> ; ypos = ypos +24; ; count = count +1; ; </op> ; </while> ; </paint> ;</form> ;</main_dialog> … G94 F100 MMC(“XML,XML_ON,XMLDIAL_EMB.XML,main","A") …...
Page 855 Generating user dialogs 1.10 Predefined functions Function name Description String find The function searches the transferred string for the first match with the substring. If the substring is found, the function returns the index to the first char‐ acter (starting with zero) or, if not, -1. Parameter: string - string variable findstring - string to be found...
Page 856 Generating user dialogs 1.10 Predefined functions Function name Description String reverse find The function searches the transferred string for the last match with the substring. If the substring is found, the function returns the index to the first char‐ acter (starting with zero) or, if not, -1. Parameter: string - string variable find string - string to be found...
Page 857 Generating user dialogs 1.11 Multitouch operation 1.11 Multitouch operation 1.11.1 Multitouch function Overview When multitouch displays are introduced, it is necessary to adjust operation to the extended functionality of the display. The rigid positioning of softkeys, for example, is eliminated and replaced or supplemented by free positioning of buttons.
Page 858 Generating user dialogs 1.11 Multitouch operation Flick vertically with two fingers ● Page-scroll in lists (e.g. ZO) ● Page-scroll in files (e.g. NC programs) Flick vertically with three fingers ● Scroll to the start or end of lists ● Scroll to the start or end of files Flick horizontally with one finger ●...
Page 859 Generating user dialogs 1.11 Multitouch operation 1.11.2 Programming finger gestures gesture_event tag Note This tag is only executed if the operating software's gesture control has been activated. If the operating software recognizes a finger gesture, the parser provides the gesture information in the $gestureinfo variable and executes the gesture_event tag.
Page 860 Generating user dialogs 1.11 Multitouch operation 1.11.3 Gesture control for graphics Imagebox control variable The following three extensions are available for the gesture control of graphics when using the Imagebox control variable: Attribute Meaning/behavior rotationangle This attribute value indicates the angle at which the graphic is to be dis‐ played.
Page 861 Generating user dialogs 1.11 Multitouch operation Example of bitmap zooming Allowing zooming for a bitmap: <control name="image_view" xpos="100" ypos="123" width="300" height="200" fieldtype="imagebox" refvar="image_box_pict_name" hotlink="true" > <property item_data="1000" /> <property setzoommode="true" /> </control> imageboxset control function The properties can also be set using the control.imageboxset function. Easy XML Programming Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 862 Generating user dialogs 1.11 Multitouch operation The following commands are available: Command Meaning/behavior SetRotationAngle The graphic is rotated around the angle indicated in lparam1. SetRotationMode The value of lparam1 defines the evaluation of the pinch gesture with respect to the rotation. Value equal to 1 - the gesture is processed by the control SetZoomMode If the value of lparam1 is equal to 1, the pinch gesture for zooming in to/out...
Page 863 Generating user dialogs 1.11 Multitouch operation 1.11.4 Gesture processing Tag message If the scaling factor is greater than 1.0, the image in the display area will be moved. If the factor is 1.0, this finger gesture can be used for browsing through a list of images, for example. In this case, the parser sends a message to the form, which can be evaluated in the message tag.
Page 864 Generating user dialogs 1.11 Multitouch operation <then> <switch> <condition>$message_par2</condition> <case value="1"> <op> pictindex = pictindex+1; </op> <if condition="pictindex > 3"> <then> <op> pictindex = 0; </op> </then> </if> </case> <case value="-1"> <op> pictindex = pictindex-1; </op> <if condition="pictindex < 0"> <then>...
Page 865 Generating user dialogs 1.12 Configuring your own buttons 1.12 Configuring your own buttons Buttons can be integrated into a form as action buttons or selection buttons. 1.12.1 Pushbutton Tag property The pushbutton is a control element that can be used as a button or checkable button. The button can be designed by means of attribute definitions in the "softkey look &...
Page 866 Generating user dialogs 1.12 Configuring your own buttons <control name="name" xpos="x position" ypos="y position" fieldtype="pushbutton" refvar="button_state" hotlink="true" > <caption></caption> <property checkable="true" /> </control> Not checked Checked Example <control name="name" xpos="x position" ypos="y position" fieldtype="pushbutton" refvar="button_state" hotlink="true" color_fg="#ff00ff" color_bk="#000eee"> <property checkable="true" /> <caption></caption>...
Page 867 Generating user dialogs 1.12 Configuring your own buttons 1.12.2 Functions of the pushbutton 1.12.2.1 Sub-tags for the pushbutton Tag caption The programmer uses the caption tag to specify the button text to be displayed for the "not pressed" state. In the default setting, the text is centered. The text alignment can be changed with the alignment attribute.
Page 868 Generating user dialogs 1.12 Configuring your own buttons Pressed display <control name="name" xpos="x position" ypos="y position" fieldtype="pushbutton" > <caption pressed=“true“>Button text pressed</caption> </control> Easy XML Programming Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 869 Generating user dialogs 1.12 Configuring your own buttons 1.12.2.2 Properties for the pushbutton Additional properties are assigned to the control with the property tag. Determining button properties The checkable attribute enables the button to be used as checkable pushbutton. To do so, the value of the attribute must be set to true.
Page 870 Generating user dialogs 1.12 Configuring your own buttons Attribute Meaning/behavior BackgroundPicture Icon in background Name of the icon for the "not pressed" state BackgroundPicturePressed Icon in background Name of the icon for the "pressed" state BackgroundPictureDisabled Icon in background Name of the icon for the "disabled" state Alignment attribute Further attributes can be specified in the tag whose values refer to the alignment of the listed icon assignments:...
Page 871 Generating user dialogs 1.12 Configuring your own buttons 1.12.2.3 Control variables for the pushbutton Button properties can be subsequently changed by assigning new values to the attribute variables listed below. The values are assigned in an operation instruction by specifying the control name followed by the control variable name.
Page 872 Generating user dialogs 1.12 Configuring your own buttons Control variable Meaning/behavior backgroundpicturedisabled_keepaspectratio Variable type: Bool Value: 1 = true 0 = false The aspect ratio of the "disabled state" back‐ ground icon is retained or ignored backgroundpicturepressed_keepaspectratio Variable type: Bool Value: 1 = true 0 = false...
Page 873 Generating user dialogs 1.12 Configuring your own buttons Control variable Meaning/behavior backgroundpicturepressed_scaled Variable type: Bool Value: 1 = true 0 = false The "pressed state" background icon is adjusted to the dimensions of the button picture_scaled Variable type: Bool Value: 1 = true 0 = false The icon is adjusted to the dimensions of the button...
Page 874 Generating user dialogs 1.12 Configuring your own buttons Picture PicturePressed PictureDisabled BackgroundPicture + Picture TextAlignedToPicture attribute If the value of the attribute is true, the text is aligned relative to the icons. <property picture="sk_circ_grind_cg.png" alignment="left" TextAlignedToPicture="true" /> Scaled attribute If the value of the attribute is true, the dimensions of the image are adjusted to the dimensions of the button in such a way that 50% of the height or width of the button at most is made available for the graphic.
Page 875 Generating user dialogs 1.12 Configuring your own buttons <property backgroundpicture="f:\appl\pbutton.png" alignment="stretch" transparent="#ffffff"/> <caption alignment="left" >This is my first touch button!</caption> <property picture="sk_circ_grind_cg.png" alignment="left" TextAlignedToPicture="true" scaled="true"/> <property backgroundpicture="pbutton.png" alignment="stretch" transparent="#ffffff"/> 1.12.3 Switch on/off A switch control is a graphic element that signals one of two states by means of an icon. This control can be operated by touch or by using a mouse.
Page 876 Generating user dialogs 1.12 Configuring your own buttons Alignment attribute Vertical switch: Value vr Horizontal switch: Value hr 1.12.4 Functions of the switch 1.12.4.1 Properties for the switch Tag property The following switch positions can be assigned to the control with the property tag: Attribute Meaning/behavior left_position...
Page 877 Generating user dialogs 1.12 Configuring your own buttons 1.12.4.2 Control variables for the switch Switch properties can be subsequently changed by assigning new values to the control variables listed below. The values are assigned in an operation instruction by specifying the control name followed by the control variable name.
Page 878 Generating user dialogs 1.12 Configuring your own buttons Control variable Meaning/behavior Caption_upper_position Variable type: String Text in the upper position Caption_lower_position Variable type: String Text in the lower position disabled Variable type: Bool Value: 1 = true - switch disabled 0 = false - switch can be operated Horizontal display <control name="name"...
Page 879 Generating user dialogs 1.12 Configuring your own buttons </control> Assigning properties by means of control variables <control name="main_switch" xpos = "450" ypos="340" width="20" height="46" fieldtype="switch" refvar="switch_statebf" hotlink="true" alignment="vr"> <property upper_position="1" /> <property lower_position="0" /> </control> … … … <op> main_switch.transparent = #ffffff; main_switch.picture_upper_position = _T"switch_up.png";...
Page 880 Generating user dialogs 1.12 Configuring your own buttons 1.12.7 Groupbox A groupbox optically encloses a group of controls with a frame and and a title. It groups logically related controls that are only intended to interact within the group. The coordinates of the embedded controls refer to the upper left-hand corner below the title line.
Page 881 Generating user dialogs 1.12 Configuring your own buttons 1.12.8 Scroll area A scroll area is used to display controls within a specified area. The coordinates of the embedded controls refer to the upper left-hand corner of the scroll area. If controls are created outside of the visible area, moving the visible area is enabled.
Page 882 Generating user dialogs 1.12 Configuring your own buttons <let name="RB1" /> <form name="scrollarea_form"> <init> <caption>scrollarea form</caption> <data_access type="true" /> <control name= "c_scroll" xpos = "2" ypos="24" width="520" height="300" fieldtype="scrollarea" > <control name= "c_group" xpos = "6" ypos="24" width="208" height="186" fieldtype="groupbox" > <caption>test group</caption>...
Page 883 Generating user dialogs 1.12 Configuring your own buttons <control name="radiobg1emb" xpos = "2" ypos="134" fieldtype="radiobutton" > <caption>test radio button</caption> <property backgroundpicture="f:\appl\cycle_my1.png" /> </control> </control> </control> <control name = "c22" xpos = "2" ypos = "400" refvar="nck/Channel/ Parameter/R[12]" hotlink="true" /> <control name="ChB1" xpos="208" ypos="430" width="50" height="30" fieldtype="checkbox"...
Page 884 Generating user dialogs 1.13 Sidescreen application 1.13 Sidescreen application 1.13.1 Easy XML in the Sidescreen The Easy XML scripting language can also be used to create dialogs in the Sidescreen area. The Sidescreen components Page and Widget are available for displaying the dialogs. The connection is made via the slsidescreen.ini file.
Page 885 Generating user dialogs 1.13 Sidescreen application 1.13.2 Integrating Sidescreen dialogs The pages or widgets are integrated using the slsidescreen.ini file. Pages are entered in the [Sidescreen] section. Each page must be specified with the keyword PAGE followed by the sequential page number and the required attributes. The name attribute defines the object name of the page.
Page 886 Generating user dialogs 1.13 Sidescreen application Property Meaning/behavior maskPath The property specifies the main module name to use. maskName The property specifies the main menu name to use. focusable The property determines whether the input focus can be set to the element. Example [Page_sidescreen_proginfluence] PROPERTY001= name:=focusable, type:=bool, value:="true"...
Page 887 Generating user dialogs 1.13 Sidescreen application 1.13.4 Sidescreen components 1.13.4.1 Sidescreen element If a page is linked to the default implementation, elements can be assigned to this page. A [Page_<page_name>] section is to be created for this and all elements associated with the page are listed.
Page 888 Generating user dialogs 1.13 Sidescreen application 1.13.4.2 Sidescreen widget A widget is assigned an area by the Sidescreen management in which the configured shapes can be displayed. By default, a widget does not obtain an input focus so that fields cannot be edited.
Page 889 Generating user dialogs 1.13 Sidescreen application Easy XML Programming Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 890 Generating user dialogs 1.13 Sidescreen application 1.13.4.3 Sidescreen page A page, which is started via the slagmforms.SlEESideScreenPage implementation, makes available the entire Sidescreen area of a form. It has no title line so that a heading cannot be configured with the Caption statement. By default, a page does not obtain an input focus so that fields cannot be edited.
Page 891 Generating user dialogs 1.13 Sidescreen application [Page_sidescreen_proginfluence] PROPERTY001= name:=focusable, type:=bool, value:="true" Icon=sidescreen_proginfluence.png Text file: sidescreen_proginfluence_deu.ts Easy XML Programming Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 892 Generating user dialogs 1.13 Sidescreen application Easy XML Programming Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 893 Generating commissioning dialogs Overview of functions Purpose The "Easy Extend" function provides a simple way of commissioning, activating, deactivating, or testing optional equipment. The available equipment and device states are displayed in a list by the control system. The system can manage a maximum of 64 devices. Softkeys are used to activate or deactivate a device.
Page 894 Generating commissioning dialogs 2.1 Overview of functions Configuration Figure 2-2 How "Easy Extend" works To use the "Easy Extend" function, the following functions must be configured by the machine manufacturer: ● PLC ↔ HMI interface The optional devices are managed via the interface between the user interface and the PLC.
Page 895 Generating commissioning dialogs 2.2 Configuration in the PLC user program Configuration in the PLC user program Loading configurations The configurations created are transferred to the manufacturer directory of the control, with the script and text file. Additionally, the corresponding PLC user program should be loaded. Programming the equipment Communication between the operator component and the PLC takes place in the PLC user program via a data block defined by the programmer, in which 128 words are reserved for the...
Page 896 Generating commissioning dialogs 2.2 Configuration in the PLC user program Four bytes with the following meanings are used for each device: Byte Description == 1 Device has been started up (HMI acknowledgment) == 1 Device is to be activated (HMI request) == 1 Device is to be deactivated (HMI request) Reserved...
Page 897 Generating commissioning dialogs 2.2 Configuration in the PLC user program General sequence The machine manufacturer must execute the following steps to make the required data available: 1. Creating a PLC user program which activates the device during activation on the PLC. 2.
Page 898 Generating commissioning dialogs 2.3 Dialog selection via PLC hardkeys Dialog selection via PLC hardkeys Field of application The following functions can be initiated by the PLC in the operating software: ● Select an operating area ● Select certain scenarios within operating areas ●...
Page 899 Generating commissioning dialogs 2.3 Dialog selection via PLC hardkeys The lines for configuring the hardkey events have the following structure: KEYx.n = area:=area, dialog:=dialog, screen:=screen, forms:=form, menus:=menu, action:=menu.action, cmdline:=cmdline KEYx.n = area:=area, dialog:=dialog, cmdline:=cmdline, action:= action x: Number of the hardkey, range of values: 1 – 254 n: Event number –...
Page 900 KEY50.0 = area:=CustomXML, dialog:=SlEECustomDialog The area and dialog identifiers can be found in the systemconfiguration.ini from [System Siemens directory]/cfg. If only the SlEECustomDialog is used, the parser expects the xmldial.xml file in the application directory as well as a menu tag with the name main. Other file names or main menu names can be declared by adding the cmdline key.
Page 901 Generating commissioning dialogs 2.4 Display on the user interface Display on the user interface Dialogs on the user interface The following dialogs are available for the "Easy Extend" function: ● The control offers a configurable dialog, in which the available devices are shown. ●...
Page 902 Generating commissioning dialogs 2.5 Creating language-dependent texts Creating language-dependent texts Structure of text file The XML files with the language-dependent texts must be created in UTF8 format: Example oem_aggregate_eng.ts <?xml version="1.0" encoding="UTF-8" ?> <!DOCTYPE TS> <TS> <context> <name>EASY_EXTEND</name> <message> <source>DEVICE_ONE</source> <translation>Device one</translation>...
Page 903 Generating commissioning dialogs 2.6 User example for a power unit User example for a power unit Activating the drive object The drive object to be activated has already been commissioned and deactivated again by the machine manufacturer, to market the axis (axes) as an option. To activate the axis carry out the following steps: ●...
Page 904 Generating commissioning dialogs 2.6 User example for a power unit Activating the PLC-controlled device The device is addressed via output byte 10 and signals data set ready to the PLC via input byte 9. The output byte is set to the specified coding for activation. The WHILE loop then waits for the data set ready of the device.
Page 905 Generating commissioning dialogs 2.7 Script language Script language Note All script elements described in the Generating user dialogs (Page 5) function form the basis for the "Easy Extend" function. Additional script elements are defined to manage additional devices. Program parts of the script The script is divided into the following areas: ●...
Page 906 Generating commissioning dialogs 2.7 Script language Identifier <tag> Meaning SET_ACTIVE The identifier contains a description of the sequences required to activate the device. Attributes: ● timeout The attribute permits a timeout to be specified in seconds. The system interrupts processing if the script has still not been completed after this time.
Page 907 Generating commissioning dialogs 2.7 Script language <SET_INACTIVE> Identifier for deactivating the device … </SET_INACTIVE> <TEST> Identifier for testing the device … </TEST> </DEVICE> … </AGM> Easy XML Programming Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 908 Generating commissioning dialogs 2.7 Script language 2.7.1 CONTROL_RESET Description This identifier allows one or more control components to be restarted. Execution of the script is only continued when the control has resumed cyclic operation. Programming Identifier: CONTROL_RESET Syntax: <CONTROL_RESET resetnc="TRUE" /> Attributes: resetnc="true"...
Page 909 Generating commissioning dialogs 2.7 Script language create A commissioning archive is created under the specified name in the …/dvm/archives/ directory. group Specifies the data groups that are to be contained in the archive. If several data groups are to be saved, the groups should be separated by a blank.
Page 910 Generating commissioning dialogs 2.7 Script language Programming Identifier: OPTION_MD Syntax: Area 0: <option_md name = "Address identifier of the data" /> <option_md name = "Address identifier of the data" index= "0"/> Area 1 to 3: <option_md name = "Address identifier of the data" index= "Area index"/> Attributes: name Identifier for the address, e.g.
Page 911 Generating commissioning dialogs 2.7 Script language 2.7.5 POWER_OFF Description Identifier for a message prompting the operator to switch the machine off. The message text is permanently saved in the system. Programming Identifier: POWER_OFF Syntax: <power_off /> Attributes: 2.7.6 WAITING Description After a reset of the NC or the drive, there is a wait for the restart of the respective component.
Page 912 Generating commissioning dialogs 2.7 Script language Example <?xml version="1.0" encoding="utf-8"?> <!DOCTYPE AGM> <AGM> <DEVICE> <NAME> Device 1 </NAME> <START_UP> … </START_UP> <SET_ACTIVE> … </SET_ACTIVE> … <FORM name="<dialog name>"> Identifier for a user dialog <INIT> <CONTROL name = "edit1" .../> Identifier for an input field </INIT>...
Page 913 Generating commissioning dialogs 2.7 Script language Programming Identifier: SOFTKEY_OK Syntax: <SOFTKEY_OK> … </SOFTKEY_OK> Identifier: SOFTKEY_CANCEL Syntax: <SOFTKEY_CANCEL> … </SOFTKEY_CANCEL> Easy XML Programming Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 914 Generating commissioning dialogs 2.7 Script language Easy XML Programming Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 915 Index Delete control, 121 Delete number of characters of a string, 111 DeleteItem, 123 Deleting a file, 118 Configuration file, 7 display resolution, 102 Empty, 125 Exist, 120 Extracting script parts, 119 Easy Extend, 175 Find substring, 111 Easy XML diagnostics, 19 Find substring (reverse), 112 FLOOR, 130 Get cursor selection, 126...
Page 916 Index string.insert, 110 NAME, 187 string.left, 107 NAVIGATION, 68 string.length, 109 NC_INSTRUCTION, 82 string.middle, 108 OP, 33 string.remove, 110 OPEN_FORM, 69 string.replace, 109 OPERATION, 34 string.right, 108 OPTION_MD, 192 Tangent, 114 PAINT, 59 Title bar height, 130 PASSWORD, 34 Writing to a file, 117 PLC_INTERFACE, 192 XML identifier POWER_OFF, 34, 193...
Page 917 Preface Introduction Safety notes SINUMERIK Setting up of OPC UA server SINUMERIK 840D sl SINUMERIK Integrate for User administration Engineering Access MyMachine / OPC UA Functionality Configuration Manual Diagnostics Update of OPC UA Server Technical data Trouble shooting Valid for: OPC UA server Version 2.0 CNC software...
Page 918 Note the following: WARNING Siemens products may only be used for the applications described in the catalog and in the relevant technical documentation. If products and components from other manufacturers are used, these must be recommended or approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and maintenance are required to ensure that the products operate safely and without any problems.
Page 919 Siemens' content, and adapt it for your own machine documentation. Training At the following address (http://www.siemens.com/sitrain), you can find information about SITRAIN (Siemens training on products, systems and solutions for automation and drives). FAQs You can find Frequently Asked Questions in the Service&Support pages under Product Support (https://support.industry.siemens.com/cs/de/en/ps/faq).
Page 920 Technical Support Country-specific telephone numbers for technical support are provided in the Internet at the following address (https://support.industry.siemens.com/cs/sc/2090/) in the "Contact" area. SINUMERIK Integrate for Engineering Access MyMachine / OPC UA Configuration Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 921 Table of contents Preface.................................3 Introduction..............................7 General description........................7 1.1.1 SINUMERIK OPC UA server....................7 Features...........................8 System setup...........................9 Reference to OPC UA specification..................10 Safety notes..............................11 Fundamental safety instructions....................11 2.1.1 General safety instructions.....................11 2.1.2 Warranty and liability for application examples..............11 2.1.3 Industrial security........................12 OPC UA safety notes......................13 Setting up of OPC UA server........................15 Prerequisites..........................15 Licensing..........................16...
Page 922 Table of contents 5.4.1 Overview..........................45 5.4.2 Subscribe / unsubscribe to alarms ..................46 5.4.3 SINUMERIK Alarm object......................47 5.4.3.1 Description..........................47 5.4.3.2 OPC UA event messages and alarms...................47 5.4.4 Sequence description of alarms.....................52 5.4.5 OPC UA Alarms and Conditions Constraints.................52 File transfer..........................53 5.5.1 Overview..........................53 5.5.2 File structure..........................53...
Page 923 Introduction General description Uniform standard for data exchange Industry 4.0 stands for the intensive utilization, evaluation and analysis of data from the production in IT systems of the enterprise level. PLC programs today already record a wide range of data at the production and process level (pressure values, temperatures and counter readings) and make them available to systems at the enterprise level, for example, to increase the product quality.
Page 924 Introduction 1.2 Features Features The SINUMERIK OPC UA server provides the possibility to communicate with SINUMERIK via OPC UA. The following functionalities of the OPC UA specification are supported by the server: ● Read, write and subscribe to SINUMERIK variables (NC, PLC) (see chapter Variable access (Page 38)) ●...
Page 925 Introduction 1.3 System setup System setup Accessibility of the server The accessibility of the server varies in the particular SINUMERIK systems. The following table shows the dependencies of the SINUMERIK systems: SINUMERIK Accessibility systems SINUMERIK After successful licensing and activation the OPC UA server is accessible via the X130 interface. 828D SINUMERIK The OPC UA server needs SINUMERIK Operate and runs on the same place as SINUMERIK Operate.
Page 926 Introduction 1.4 Reference to OPC UA specification Reference to OPC UA specification The SINUMERIK OPC UA server matches the specification of the OPC foundation (https:// opcfoundation.org/) V1.0.3. SINUMERIK Integrate for Engineering Access MyMachine / OPC UA Configuration Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 927 Safety notes Fundamental safety instructions 2.1.1 General safety instructions WARNING Danger to life if the safety instructions and residual risks are not observed If the safety instructions and residual risks in the associated hardware documentation are not observed, accidents involving severe injuries or death can occur. ●...
Page 928 Siemens’ products and solutions undergo continuous development to make them more secure. Siemens strongly recommends to apply product updates as soon as available and to always use the latest product versions. Use of product versions that are no longer supported, and failure to apply latest updates may increase customer’s exposure to cyber threats.
Page 929 Safety notes 2.2 OPC UA safety notes OPC UA safety notes NOTICE Safety risk due to access to security relevant data OPC UA provides read/write access on data in SINUMERIK. This access might also affect security relevant data. ● You can limit this access on SINUMERIK data by individual read and write permission. Please refer to chapter User administration (Page 31), especially chapter List of rights (Page 34).
Page 930 Safety notes 2.2 OPC UA safety notes SINUMERIK Integrate for Engineering Access MyMachine / OPC UA Configuration Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 931 You will find further information on the Defense-in-Depth concept, suitable protective measures and Industrial Security in general in the Configuration Manual Industrial Security (https://support.industry.siemens.com/cs/de/en/view/108862708). Requirement ● OPC UA requires SINUMERIK Operate. ● OPC UA requires an OPC UA license (6FC5800-0AP67-0YBO).
Page 932 Setting up of OPC UA server 3.2 Licensing Licensing Setting the license 1. Set the "Access MyMachine /OPC UA" license via the "Startup > Licenses" operating area. Figure 3-1 Setting the license 2. Restart the SINUMERIK Operate in order to activate the license. SINUMERIK Integrate for Engineering Access MyMachine / OPC UA Configuration Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 933 Setting up of OPC UA server 3.3 Commissioning Commissioning Executing the OPC UA configuration dialog 1. Start the OPC UA configuration dialog via the operating area "Startup > Network". 2. Press the "OPC UA" softkey. Note Please note that the OPC UA softkey is only visible when the license option is set. SINUMERIK Integrate for Engineering Access MyMachine / OPC UA Configuration Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 934 Setting up of OPC UA server 3.3 Commissioning 3. Press the "Change" softkey. The Settings dialog will appear. Make the necessary settings for connection, authentication and activation. Figure 3-2 Settings of OPC UA Server (with changes) SINUMERIK Integrate for Engineering Access MyMachine / OPC UA Configuration Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 935 Setting up of OPC UA server 3.3 Commissioning Group Setting Description Connection set‐ IP address The IPv4 address of the company network interface, tings since this is the primary server interface. This is deter‐ mined automatically. Even if there is only one address stated in this dialog, the OPC UA server is available at the following interfaces: SINUMERIK 828D -X130...
Page 936 Setting up of OPC UA server 3.3 Commissioning NOTICE Security risk due to data manipulation and data sniffing Anonymous access can be a security risk. Anonymous access should therefore be strictly limited to commissioning. ● For normal operation authentication via username and password or based on certificates should be used (see chapter Certificate handling (Page 22)).
Page 937 Setting up of OPC UA server 3.3 Commissioning 4. Then choose "OK". If you enter a port for the first time, you will receive a safety note. Figure 3-3 Security message for opening the TCP port 5. If settings are all done, restart is necessary to activate the new settings. Perform a hardware restart on the target systems NCU and PPU.
Page 938 Press the softkey “System data”. In the files and folders tree navigate to: ● Embedded systems (NCU 840Dsl / 828D): "System CF Card/addon/sinumerik/hmi/opcua/pki/rejected" ● PCU system: "System harddisk/C: System/ProgramData/Siemens/MotionControl/addon/sinumerik/hmi/ opcua/pki/rejected" Select the rejected certificate. Press softkey “Cut”. Navigate to folder “trusted/certs”. Press softkey “Paste”.
Page 939 Setting up of OPC UA server 3.4 Certificate handling The following message will appear: Shorten the filename to match SINUMERIK Operate requirements and make sure the extension (.der) is still appended. Then press softkey “Ok” Verify certificate is in trusted folder: 10.
Page 940 ● Connection without security ● Connection with the security policy "Basic128Rsa15" respectively "Basic256" and the security mode "SignAndEncrypt" SIEMENS always recommends setting up a connection with security, as only in this way the confidentiality of the data transmitted can be ensured. Installation The "Sample Applications"...
Page 941 Setting up of OPC UA server 3.5 Testing the connection Figure 3-4 Deactivating the "OPC UA Local Discovery Server" service on PCU 50 SINUMERIK Integrate for Engineering Access MyMachine / OPC UA Configuration Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 942 Setting up of OPC UA server 3.5 Testing the connection Procedure 1. Start the OPC UA "Sample client". Figure 3-5 Sample Client main window 2. Select the "New" entry from the drop-down list. The "Discover Servers" window opens. 3. Now enter the IPv4 address of the target system and click the "Discover" button. Figure 3-6 Discover servers 4.
Page 943 Setting up of OPC UA server 3.5 Testing the connection 5. Return to the main window and click the "Connect" button. 6. To establish a simple connection without security, configure the following settings. After clicking "OK", enter the administrator user assigned when OPC UA was set up and the administrator password.
Page 944 Setting up of OPC UA server 3.5 Testing the connection 7. Confirm the prompt asking if you want to trust the transferred certificate with "Yes". Figure 3-9 Certificate The connection to the SINUMERIK OPC UA server is now established and the available address space is displayed.
Page 945 Setting up of OPC UA server 3.5 Testing the connection – E.g. read, write, setup monitoring Figure 3-11 NodeID "Sinumerik > Channel > Parameter > R" – The attributes of a NodeID can be queried via the entry "View Attributes". One of these attributes is the "Value", which provides the corresponding value of R1.
Page 946 Setting up of OPC UA server 3.5 Testing the connection SINUMERIK Integrate for Engineering Access MyMachine / OPC UA Configuration Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 947 User administration Overview The admin can add/delete users and rights via OPC UA methods provided by the server. Therefore a connection with a generic client must be established, using the admin credentials. Users and rights can then be assigned using the following OPC UA server methods: ●...
Page 948 User administration 4.2 User management User management A new user created with the "AddUser" function has no rights at all. The user administrator has the responsibility for the user management and the associated rights. All users must use a secure password. Table 4-1 Methods for user administration Method...
Page 949 User administration 4.3 Rights management Rights management After setting up the OPC UA components, the administrator user has read access to all data ("SinuReadAll") but not write access. These rights must be explicitly set. Table 4-2 Methods for user administration Method Description GetMyAccessRights...
Page 950 User administration 4.4 List of rights List of rights Below is the list of rights a user is assigned: Table 4-3 List of rights Method Description GiveUserAccess Sets the specified access rights for a user. The rights below can be combined in any combi‐ nation.
Page 951 Functionality Overview Overview The SINUMERIK OPC UA server provides the possibility to communicate with SINUMERIK via OPC UA. The following functionalities of the OPC UA specification are supported by the server: ● Data Access: Read, write and subscribe to SINUMERIK variables (NC, PLC) ●...
Page 952 Functionality 5.2 Address space model Address space model Address space model If the OPC UA server is browsed, the available address space is mapped under the "Sinumerik" node. Global User Data (GUD) can be found under the "/Sinumerik/GUD" node. The PLC blocks (inputs, outputs, bit memory, data blocks) can be found under the "/Sinumerik/ Plc"...
Page 953 Functionality 5.2 Address space model Figure 5-1 Excerpt from browsing the OPC UA data access interface SINUMERIK Integrate for Engineering Access MyMachine / OPC UA Configuration Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 954 The variable paths for NC access are stored in the address space of the SINUMERIK Operate OPC UA server. You can obtain additional information from the List Manual for 840D sl and 828D "NC variables and interface signals" (https://support.industry.siemens.com/cs/de/de/view/109748365/en). Figure 5-2 Identifier for R parameter The displayed NC variables always represent only the first parameter of the corresponding NC data area (channel, TO area, mode group).
Page 955 Functionality 5.3 Variable access The R parameters are found under the identifier "/Channel/Parameter/R", which is eventually mapped to "/Channel/Parameter/R[u1, 1]". If you want to access other parameters, you must correspondingly extend the identifier, e.g. "/Channel/Parameter/R[u2, 56]". Table 5-1 Examples of variable paths (NC access operations) Variable path Description /Channel/Parameter/R[u1,10]...
Page 956 Functionality 5.3 Variable access Access is performed as follows: ABC[0,0] → /NC/_N_CH_GD3_ACX/ABC[u1, 1] ABC[0.1] → /NC/_N_CH_GD3_ACX/ABC[u1, 2] ABC[0.2] → /NC/_N_CH_GD3_ACX/ABC[u1, 3] ABC[1.0] → /NC/_N_CH_GD3_ACX/ABC[u1, 4] ABC[1.1] → /NC/_N_CH_GD3_ACX/ABC[u1, 5] ABC[1.2] → /NC/_N_CH_GD3_ACX/ABC[u1, 6] ABC[2.0] → /NC/_N_CH_GD3_ACX/ABC[u1, 7] ABC[2.1] → /NC/_N_CH_GD3_ACX/ABC[u1, 8] ABC[2.2] →...
Page 957 Functionality 5.3 Variable access Area Address (IEC) Permissible data types OPC UA data type Output image DWORD, UInt32 DINT, Int32 REAL Double Data block DBz.DBXx.y BOOL Boolean Data block DBz.DBBx BYTE, CHAR, UInt32 STRING String Data block DBz.DBWx WORD, CHAR, UInt32 Int32 Data block...
Page 958 Functionality 5.3 Variable access Examples of variable paths (PLC access operations) Table 5-3 Examples of variable paths (PLC access operations) Variable path Description /Plc/M5.0 Memory bit 0 at byte offset 5 /Plc/DB5.DBW2 Word (16-bit) at byte offset 2 in data block 5 /Plc/DB8.DBB2:STRING UTF8 string beginning at byte offset 2 in data block 8 /Plc/DB8.DBW2:[10]...
Page 959 5.3.5 Reference of OPC UA variables For more information on variable documentation, refer: NC variables and interface signals (https://support.industry.siemens.com/cs/de/de/view/109748365/en) Example 1: Finding an OPC UA variable in the variable documentation You want to find the variable "opMode" in folder "/Bag/State".
Page 960 Functionality 5.3 Variable access 1. At the beginning of each chapter for variable sections, you find the information "OEM-MMC: LinkItem“ specifying "/ToolCompensation/“. 2. Refer to the document and search for "ChannelCompensation" and then navigate manually to the requested parameter "cuttEdgeParam". Example 3: Finding a variable from documentation on OPC UA client You want to find the variable "cuttEdgeParam"...
Page 961 Functionality 5.4 Alarms Alarms 5.4.1 Overview Any OPC UA client supporting Alarms & Conditions connected to the SINUMERIK OPC UA server can subscribe to alarms to get the notifications of alarms. All OPC UA Clients that have subscribed for SINUMERIK alarms will be provided with an alarm as soon as it becomes active.
Page 962 Functionality 5.4 Alarms 5.4.2 Subscribe / unsubscribe to alarms Subscribe to alarms The SINUMERIK Alarm Event object is connected to the SINUMERIK node. To receive the alarms, an event subscription must be placed at the SINUMERIK node. The following example describes how to receive the alarms using the OPC UA Foundation Client: 1.
Page 963 Functionality 5.4 Alarms Figure 5-5 Alarm List Unsubscribe to alarms 1. Click "Conditions > Set Area Filter…". The "Select Area" window appears. 2. Right click on "Sinumerik" and select "Remove Monitored Item" to unsubscribe the server from the Quickstart Alarm Condition Client. 5.4.3 SINUMERIK Alarm object 5.4.3.1...
Page 964 Functionality 5.4 Alarms An alarm is composed of various nested or parallel state machines. Monitoring can generally be enabled or disabled. If monitoring is enabled, the alarm can be active or otherwise inactive. Acknowledgment, confirm and comments of alarms is currently not supported. The basic type for all condition objects is the condition type.
Page 965 Functionality 5.4 Alarms Attributes of BaseEventType Attribute Data type Mapping with respect to SINU‐ Description MERIK EventId String Unique node id generated from EventId is generated by the Server to SINUMERIK system. uniquely identify a particular Event Notifi‐ cation. The EventId shall always be returned as value and the Server is not allowed to re‐...
Page 966 Functionality 5.4 Alarms Severity of Alarms SINUMERIK systems use three severity levels (e.g. Information, Warning and Error). The table below shows the values at SINUMERIK system and its mapping in OpcUa Server/Client. Severity Level SINUMERIK System OpcUa Server/Client Information Warning 2-999 Error 1000...
Page 967 Functionality 5.4 Alarms Attribute Data type Mapping with respect to SINU‐ Description MERIK AddComment Not supported Not supported and the result code should return Bad_MethodInvalid. ConditionRe‐ None When the method is called up, an event freshMethod with the current state is triggered for the calling client for all conditions.
Page 968 Functionality 5.4 Alarms 5.4.4 Sequence description of alarms The OPC UA Server automatically sends an object of the "CNCAlarmtype" to the OPC UA Client containing the single alarm which has just been triggered. The OPC UA Server automatically resends an object of the "CNCAlarmtype" with the same content as when the corresponding alarm was triggered, except a change in the status.
Page 969 Functionality 5.5 File transfer File transfer 5.5.1 Overview The SINUMERIK OPC UA server offers two methods to copy NC Part programs from OPC UA Client to the SINUMERIK server and vice versa. 5.5.2 File structure Accessing the file system The OPC UA server allows the OPC UA client to support the transfer of files between the client and the server.
Page 970 Functionality 5.5 File transfer 5.5.3 Methods used to exchange the files In addition to the standard file system, this functionality supports two additional methods to transfer the files from server to client or vice versa. Figure 5-7 Comfort methods for the file transfer SINUMERIK Integrate for Engineering Access MyMachine / OPC UA Configuration Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 971 Functionality 5.5 File transfer 1. CopyFileFromServer: – Allows copying file from SINUMERIK OPC UA server to client location. – The user shall provide the name of the file with full path to be copied. – On completion of the file transfer, an appropriate message will be displayed. Type Data type Argument...
Page 972 Functionality 5.5 File transfer SINUMERIK Integrate for Engineering Access MyMachine / OPC UA Configuration Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 973 Diagnostics Overview Overview The OPC UA server offers a variety of diagnostics information, as described in the OPC UA Standard Part 5 - "Information Modell", Chapter 6. This diagnostics information can be found under the Server Node: Figure 6-1 Diagnostics Information - Server Node SINUMERIK Integrate for Engineering Access MyMachine / OPC UA Configuration Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 974 Diagnostics 6.2 OPC UA server version OPC UA server version OPC UA server version OPC UA server version and OPC UA dialog version information can be found in SINUMERIK OPERATE version screen. 1. Open SINUMERIK OPERATE and choose operating area "Diagnostics". Press the softkey "Version".
Page 975 Diagnostics 6.2 OPC UA server version Figure 6-3 Version data / system extensions The OPC UA entry is found. 3. Select the entry and press "Details" again to show more detailed information on OPC UA components. SINUMERIK Integrate for Engineering Access MyMachine / OPC UA Configuration Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 976 Diagnostics 6.2 OPC UA server version SINUMERIK Integrate for Engineering Access MyMachine / OPC UA Configuration Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 977 An update process is possible with SINUMERIK software version ≥ V4.7. SINUMERIK Integrate Create MyConfig (CMC) The necessary update (CMC) file can be provided by your regional SIEMENS office. Release of software version The release of new software version of OPC UA will be communicated via SINUMERIK newsletter by the SIEMENS Product Management.
Page 978 Installation of OPC UA server OPC UA - Server update To receive the latest OPC UA server software, contact your regional SIEMENS office. The installation procedure of the OPC UA server will vary depending whether a PCU or a PPU/ NCU is being used.
Page 979 In previous versions additionally added read rights have not been deleted with removing “SinuReadAll”. Same applies to “SinuWriteAll”. Note If you face any other compatibility issues or for further details, refer to hotline (https:// support.industry.siemens.com/cs/sc/2090/). SINUMERIK Integrate for Engineering Access MyMachine / OPC UA Configuration Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 980 Update of OPC UA Server 7.3 Compatibility SINUMERIK Integrate for Engineering Access MyMachine / OPC UA Configuration Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 981 Technical data Technical data Description Value Number of sessions 828D 840 D sl Number of subscriptions 828D 840D sl Maximum samples / second 828D 840D sl 1000 Sampling rate min. 100 ms Sampling interval {100, 250, 500, 1000, 2500, 5000} Publishing rate min.
Page 982 Technical data SINUMERIK Integrate for Engineering Access MyMachine / OPC UA Configuration Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 983 You can find all relevant information on error codes at Github (https://github.com/ OPCFoundation/UA-Nodeset/blob/master/DotNet/Opc.Ua.StatusCodes.cs). Technical Support Country-specific telephone numbers for technical support are provided in the Internet at the following address (https://support.industry.siemens.com/cs/sc/2090/) in the "Contact" area. SINUMERIK Integrate for Engineering Access MyMachine / OPC UA Configuration Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 984 Trouble shooting 9.1 Reference to OPC UA error code SINUMERIK Integrate for Engineering Access MyMachine / OPC UA Configuration Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 985 Index Accessibility, 9 License, 16 AddCertificateUser, 32 AddUser, 32 Application scenario, 9 OPC UA standard, 7 Browsing, 36 PCU / IPC, 9 ChangeMyPassword, 32 Checking the time, 21 Security settings, 8 Client, 7 SINUMERIK 828D, 9 SINUMERIK 840D sl, 9 SINUMERIK OPC UA server, 7 SINUMERIK systems, 9 Data types, 40...
Page 986 Index SINUMERIK Integrate for Engineering Access MyMachine / OPC UA Configuration Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 987 Introduction Getting Started Fundamentals SINUMERIK Dialogs SINUMERIK 840D sl SINUMERIK Integrate Run Variables MyScreens (BE2) Programming commands Programming Manual Graphic and logic elements "Custom" operating area Dialog selection Examples for cycle masks Reference lists Tips and tricks Animated elements Valid for CNC software Version 4.8 SP2 12/2017...
Page 988 Note the following: WARNING Siemens products may only be used for the applications described in the catalog and in the relevant technical documentation. If products and components from other manufacturers are used, these must be recommended or approved by Siemens. Proper transport, storage, installation, assembly, commissioning, operation and maintenance are required to ensure that the products operate safely and without any problems.
Page 989 Table of contents Introduction..............................9 Getting Started............................13 Introduction..........................13 Project example........................14 2.2.1 Task description........................14 2.2.2 Creating the configuration file (example)................18 2.2.3 Saving the configuration file in the OEM directory (example)..........21 2.2.4 Creating the online help (example)..................22 2.2.5 Integrating the online help and saving the files to the OEM directory (example)....25 2.2.6 Copying easyscreen.ini into the OEM directory (example)............26 2.2.7...
Page 990 Table of contents 4.3.4 Integrating the online help in SINUMERIK Operate...............77 4.3.5 Saving help files........................79 4.3.6 Help files in PDF format......................79 Variables..............................81 Defining variables........................81 Application examples......................82 Example 1: Assigning the variable type, texts, help display, colors, tooltips......84 Example 2: Assigning the Variable Type, Limits, Attributes, Short Text Position properties..........................85 Example 3: Assigning the Variable Type, Default, System or User Variable, Input/Output Field Position properties......................86...
Page 991 Table of contents Methods..........................126 6.2.1 ACCESSLEVEL........................126 6.2.2 CHANGE..........................127 6.2.3 CHANNEL..........................128 6.2.4 CONTROL..........................129 6.2.5 FOCUS..........................129 6.2.6 LANGUAGE.........................130 6.2.7 LOAD...........................130 6.2.8 UNLOAD..........................131 6.2.9 OUTPUT..........................132 6.2.10 PRESS..........................133 6.2.11 PRESS(ENTER)........................134 6.2.12 PRESS(TOGGLE)........................134 6.2.13 RESOLUTION........................135 6.2.14 RESUME..........................135 6.2.15 SUSPEND..........................136 6.2.16 Example: Version management with OUTPUT methods.............136 Functions..........................138 6.3.1 Reading and writing drive parameters: RDOP, WDOP, MRDOP........138...
Page 992 Table of contents 6.3.34 Recompile without user comment..................177 6.3.35 Search Forward, Search Backward (SF, SB)...............181 6.3.36 STRING functions........................182 6.3.37 WHILE/UNTIL loops......................188 6.3.38 Cyclic execution of scripts: START_TIMER, STOP_TIMER..........190 Graphic and logic elements........................193 Line, dividing line, rectangle, circle and ellipse..............193 Defining an array........................196 7.2.1 Accessing the value of an array element................197 7.2.2...
Page 993 Table of contents Dialog selection using PLC hard keys..................283 Dialog selection via NC......................286 Examples for cycle masks........................287 10.1 Examples for cycle masks....................287 Reference lists............................289 Lists of start softkeys......................289 A.1.1 List of start softkeys for turning....................289 A.1.2 List of start softkeys for milling.....................290 List of predefined softkeys....................293 List of access levels......................294 List of colors.........................295...
Page 994 Table of contents Display in Run MyScreens....................322 Glossary..............................323 Index.................................327 SINUMERIK Integrate Run MyScreens (BE2) Programming Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 995 Introduction Overview "Run MyScreens" can be used to create user interfaces that display functional expansions designed by the machine manufacturer or user, or to implement your own layout. Cycle calls can also be generated with user interfaces that you have created. Dialogs can be created directly on the control system.
Page 996 When saving configuration and language files, ensure that the coding is set to UTF-8 for the editor you are using. Storage paths Note the following convention when storing the configuration files, language files, etc. [System Siemens directory] Linux: /card/siemens/sinumerik/hmi Windows 7: C:\ProgramData\Siemens\MotionControl\siemens [System oem directory]...
Page 997 Introduction [System oem directory] /Ico/ico [Resolution] Image files: Example: [System oem directory] /Ico/ico640 Online Help: [System oem directory] /hlp/ [Language] Example: [System oem directory] /hlp/eng Application You can implement the following functions: Display dialogs containing the fol‐ ● Softkeys lowing elements: ●...
Page 998 Introduction SINUMERIK Integrate Run MyScreens (BE2) Programming Manual, 12/2017, 6FC5397-1DP40-6BA1...
Page 999 Getting Started Introduction Using the following example, you get to know the steps necessary to insert your own dialogs into the SINUMERIK Operate user interface using Run MySreens. You also learn how to create your own dialogs, insert context-sensitive help screens and help calls, define softkeys and how you can navigate between the dialogs.
Page 1000 Getting Started 2.2 Project example Project example 2.2.1 Task description In the project example you create the dialogs described in the following, including a context- sensitive help. Dialog 1 R parameters that can be written to (0 and 1) and geometry axis names are displayed in the first dialog (input fields).

This manual is also suitable for:

Sinumerik 840d sl

Siemens SINUMERIK 840DE sl Commissioning Manual

1 Delivery Condition

2 First Commissioning of the PCU 50.5

3 First Commissioning of SIMATIC Ipcs

4 Configuration of the System

5 Installing and Configuring Updates and Automation Software

6 Backing up and Restoring Data

7 Service and Diagnostics

Quick Links

Summary of Contents for Siemens SINUMERIK 840DE sl

This manual is also suitable for:

Siemens SINUMERIK 840DE sl Commissioning Manual

1 Delivery Condition

2 First Commissioning of the PCU 50.5

3 First Commissioning of SIMATIC Ipcs

4 Configuration of the System

5 Installing and Configuring Updates and Automation Software

6 Backing up and Restoring Data

7 Service and Diagnostics

Quick Links

Related Manuals for Siemens SINUMERIK 840DE sl

Summary of Contents for Siemens SINUMERIK 840DE sl

This manual is also suitable for:

Table of Contents