Page 1 Preface HMI Advanced Expanding the user interface SINUMERIK Online help SINUMERIK 840Di sl/840D sl/840D Generating target language Base software and HMI Advanced texts PCU-Basesoftware V8.2 Commissioning Manual Appendix Valid for: Controls SINUMERIK 840Di sl/840DiE sl SINUMERIK 840D sl/840DE sl SINUMERIK 840D/840DE Software version: HMI Advanced V7.6...
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 Preface SINUMERIK documentation The SINUMERIK documentation is organized in three parts: ● General documentation ● User documentation ● Manufacturer/service documentation An overview of publications, which is updated monthly and also provides information about the language versions available, can be found on the Internet at: http://www.siemens.com/motioncontrol...
Page 4 For technical support telephone numbers for different countries, go to: http://www.siemens.com/automation/service&support Calls are subject to charge, e.g. €0.14/min. from a German landline. Tariffs of other telephone service providers may vary. SINUMERIK Internet address http://www.siemens.com/sinumerik Base software and HMI Advanced Commissioning Manual, 03/2009, 6FC5397-0DP10-3BA0...
Page 5 SINUMERIK as well as the data on the memory card. ● If you cannot use a memory card with the SINUMERIK, it is probably because the memory card is not formatted for the control system (e.g. Ext3 Linux file system), the memory card file system is faulty or it is the wrong type of memory card.
Page 6 Preface Base software and HMI Advanced Commissioning Manual, 03/2009, 6FC5397-0DP10-3BA0...
Page 7 Introduction Configuring the HMI system Parameterizing machine data SINUMERIK Programming PLC Functions SINUMERIK 840Di sl/840D sl/840D HMI Advanced (IM4) Diagnostics and service Tool management Commissioning Manual List of the INI Files List of Abbreviations Valid for: Controls SINUMERIK 840Di sl/840DiE sl...
Page 8 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 9 Table of contents Introduction..............................7 State of the system when supplied ....................7 Booting ............................8 1.2.1 Settings at the HMI ........................8 1.2.2 System settings..........................10 1.2.3 Behavior of the keys for the PCU....................12 Access levels concept........................13 Licensing (solution line only)......................15 Limits of data management......................17 Configuring the HMI system........................
Page 10 Table of contents Configuring user alarms ......................83 2.5.1 Classifying user alarms ....................... 83 2.5.2 Configuring user alarms ......................86 2.5.3 Example: Extending an alarm text for user PLC alarms ............. 88 Parameterizing machine data ........................91 Handling machine data via the HMI .................... 91 3.1.1 Setting-up a display filter for machine data.................
Page 11 Table of contents 5.6.2 Structure of the log file .......................155 5.6.3 How to save the log file......................157 5.6.4 "NCDDE Trace" log........................158 HMI Analyzer..........................160 5.7.1 Using the HMI Analyzer ......................160 5.7.2 Using the HMI Analyzer ......................161 5.7.3 Analyzing INI Files ........................163 5.7.4 Application Examples.........................165 Tool management..........................
Page 12 Table of contents DPDH.INI........................... 281 DPSIM.INI ..........................282 HEADER.INI..........................283 A.10 HMIDESK.INI ..........................287 A.11 IB.INI ............................288 A.12 IF.INI............................290 A.13 KEYS.INI ........................... 291 A.14 LOGDRIVE.INI .......................... 292 A.15 MACHINE.INI ..........................295 A.16 MBDDE.INI..........................298 A.17 MMC.INI ............................ 303 A.18 NETNAMES.INI.........................
Page 13 State of the system when supplied Overview This manual describes the commissioning of the HMI-Advanced software. When commissioning the SINUMERIK control, you may require additional manuals: ● Operator Components and Networking ● Commissioning Manual PCU Basic Software ● Diagnostics Manual ●...
Page 14 Introduction 1.2 Booting Booting 1.2.1 Settings at the HMI Selecting languages Once you have selected a first and second language in the "Startup" area, you can subsequently toggle between them using the "Change Language" softkey. The following standard languages are available: ●...
Page 15 Introduction 1.2 Booting Pressing the “Default address” softkey transfers the factory set IP address 192.168.214.1 to the address field for the NCU. However, if the control is linked to a company network, for example, the IP addresses will be different. You must restart the HMI for the changes to take effect. The section with the new IP address is written to user/mmc.ini.
Page 16 Introduction 1.2 Booting 1.2.2 System settings Overview Under "System settings", settings are made for inquiry windows, file tree display and screen display in the Machine, Program and Services operating areas. File display You can set the file tree display for the Services, Machine and Program operating areas. The following columns can be selected: ●...
Page 17 In the event of communication errors, a trace log for communication processes can be recorded following an instruction to the Service department or to our hotline. The trace log is only evaluated by Siemens. HMI exit mode During the commissioning phase it is often necessary to shut down the HMI-Advanced and operating system and then reboot the PCU.
Page 18 Behavior of the keys for the PCU CAPSLOCK The CAPSLOCK function allows all entries made with external SINUMERIK keyboards to be in upper case instead of lower case. If lower case letters are needed, they can be added by means of the SHIFT commands function.
Page 19 Introduction 1.3 Access levels concept Access levels concept Overview The access levels concept controls access to functions and data areas. Access levels 0 to 7 are available, where 0 represents the highest level and 7 the lowest level. Access levels 0 to 3 are locked using a password and 4 to 7 using the appropriate key- operated switch settings.
Page 20 Introduction 1.3 Access levels concept Changing the password Procedure: 1. Press the "Password" softkey. 2. Press the "Set password" softkey. 3. The input window is displayed "Please enter password" 4. Enter one of the three possible passwords and press the Enter key or icon to acknowledge.
Page 21 Introduction 1.4 Licensing (solution line only) Licensing (solution line only) Licensing an option The HMI-Advanced options manager provides support when entering the License Key for an option. Note Default setting The option data for the NC is subject to a protection level for retailers/end users. The input dialog for setting the options and inputting the license key is assigned protection level 3 = end user.
Page 22 No reset is required after writing the license key, the "License key set!" message appears in the user response line. References: Manual SINUMERIK 840Di sl, Chapter "Automation License Manager" All options All of the options selectable for this control are listed here. Furthermore, the list states whether or not a valid and adequate license key has already been entered and how many licenses are available.
Page 23 Introduction 1.5 Limits of data management Limits of data management Overview Data are stored in the following directories: ● Workpieces ● Part programs ● Subroutines ● User cycles ● Standard cycles ● Manufacturer cycles The data management directories can contain a combined total of 100,000 files, whereby each directory (each *.WPD workpiece directory for workpieces) is limited to 1000 files.
Page 24 Introduction 1.5 Limits of data management HMI Advanced (IM4) Commissioning Manual, 03/2009, 6FC5397-0DP10-3BA0...
Page 25 Configuring the HMI system Processing INI files Notation [xxx] ;Designating a section Identifier=value ;Value assignment Identifier=<empty> ;Delete value ;Separator (comma) for multiple assignments ;Introduction of comment: As a general rule, comments indicate the range of values ;Introduction of comment Directory structure The system directory structure is organized in such a way that user changes are retained if the software is upgraded.
Page 26 System directory of the HMI software. ● add_on: Directory for additional Siemens products (e.g. TPM, MDA, DNC ...). This can have the same directory structure (e.g. subdirectory \language) and subdirectories as mmc2. Entries for an add-on product in REGIE.ini and re_*.ini, for example, are also stored here.
Page 27 ;Scroll in the alarm line RotationCycle = 1000 The same procedure applies to the F:\ADD_ON and F:\OEM directories. \ADD_ON is reserved for Siemens products. All OEM applications should be installed in the directory \OEM. NOTICE The associated entries, e.g. in REGIE.INI, should be modified in these directories and not...
Page 28 Configuring the HMI system 2.1 Processing INI files Switching off settings If, for the search sequence, there are specific entries in a lower-priority directory that you wish to be disabled in a directory with a higher-priority, you can do this by specifying an <empty>...
Page 29 Configuring the HMI system 2.1 Processing INI files Accept selected INI files: If you wish to only accept specific initialization files, press the “Select data” vertical softkey. A list of all files stored in the USER directory is displayed. 2.1.2 Activating the screensaver Function Tasks of the screensaver:...
Page 30 Configuring the HMI system 2.1 Processing INI files Settings in the REGIE.INI file: Default: No prompt dialog box [Miscellaneous] EnableRebootDialog = True If the protection level is lower than the manufacturer level (protection level 0 to 2) or if the above entry is set to "False"...
Page 31 Configuring the HMI system 2.1 Processing INI files DiskCare=n Changes of the alarm state are written to the log file if no change occurs in n seconds. In addition, the following applies: The alarm log is saved on the hard disk if it is displayed in the operator area "Diagnostics"...
Page 32 Configuring the HMI system 2.1 Processing INI files ● RELATION: ":" Equal to "<" less than ">" greater than "!" ● FEATURE: Numbers of strings ● OPERATORS "," Comma denotes logical OR, only within a filter " " Space/blank denotes logical AND between individual filters. "|"...
Page 33 Configuring the HMI system 2.1 Processing INI files Select a value for the image to be displayed in the [ALARM_PICTURE] section: [ALARM_PICTURE] ;0 = Image for PLC button ;1 = Image for Cancel button ;2 = Image for Reset button ;3 = Image for HMI button ;4 = Image for User Defined button ButtonImage=1...
Page 34 Configuring the HMI system 2.1 Processing INI files Formats and data type All entries are located in the [ACCESSMASKS] section. The entries have, e.g. the following format: [ACCESSMASKS] \wks.dir\*.wpd\*.mpf = 75775 \mpf.dir\*.mpf = 75775 \cus.dir\*.spf = 33773 A standard access mask can be declared for each data type and storage location. An entry comprises the path at which data of the data type can be created and the new standard access mask.
Page 35 Configuring the HMI system 2.1 Processing INI files The values of "SkSelectLngInsteadSkChangeLng" have the following significance: False: "Change Language" softkey for changing between the foreground and background language, same as before (default setting). True: "Select Language" softkey to select one of the installed languages. This means that online, more than two languages can be changed over at the language change position after the appropriate selection.
Page 36 Configuring the HMI system 2.1 Processing INI files A skeleton application can define up to 16 horizontal and 8 vertical softkeys. When you leave an operating area that was selected from a skeleton application, you return to the higher- level menu of the skeleton application. The following standard applications can be selected from a skeleton application: ●...
Page 37 Configuring the HMI system 2.1 Processing INI files Example The following entries in the REGIE.INI clarify the process: Skeleton application for user-specific operating trees. ; sample entry Task7 = name := mntmmc, cmdline := "SectionName1", Timeout := 60000 The task number (7 in this case) is assigned to the softkey that ;...
Page 38 Configuring the HMI system 2.1 Processing INI files ; The fifth softkey is assigned the task services (Taskindex 3) as ; child (HSK1IsTask=0) with the empty command parameter, that ; specify the softkey texts for default German (_GR) and English (_UK).
Page 39 Configuring the HMI system 2.1 Processing INI files Skeleton application as child task The skeleton application can also be started from a dedicated process as a child application. Then, upon recall, the skeleton application returns to the starting application and closes, if applicable: ;...
Page 40 Configuring the HMI system 2.1 Processing INI files Shortened configuration in TaskConf.INI The above configuration of TASKCONF.INI for a softkey in the skeleton application can be simplified for the following entries when standard operations are addressed: HSK<SoftkeyIndex>Task= x/y x operator area y command or state= i Example: HSK1Task=Program/<root>...
Page 41 Configuring the HMI system 2.1 Processing INI files Explanation Setup State=50 Entry into the Drive overview screen in Start-up with recall on exiting the level. The softkey Drives/Servo text is IBSetup <root> Entry into the Settings (task 34) main screen with recall to the highest level for return. System settings The softkey text is Simulation...
Page 42 Configuring the HMI system 2.1 Processing INI files On reaching a status from the list the application returns to the calling application. The from statuses can be separated by commas or specified as ranges < > - < >, e.g. Recall(1,5- 7,48).
Page 43 Configuring the HMI system 2.1 Processing INI files Structure of the DGOVW.INI file [GLOBAL] NrOfSignals= [BMP] 100="<Bitmapname>" 101="..." [SIG1] text= Item= expr= [SIG2]. [SIG<n>] Significance of entries NrOfSignals: Number of additional signals. The signals are located in the [SIG<nr>] section, where <nr> goes from 1 to NrOfSignals (continuously and with no gaps).
Page 44 <EntryName>::= any name, which must be defined in the same section as expr. It is treated in the same way as expr. <BitmapNr>::= Number of a bitmap file. The numbers 0 to 99 are reserved for Siemens. Internal bitmaps must be defined in the [BMP] section.
Page 45 $T<Text No.>= "<any text>" listed. Values from 1000 to 32767 are permitted for <Text-Nr> and may only occur once. Values below 1000 are reserved for Siemens. This file has to exist for all languages that are required (language abbreviation as in MMC.INI).
Page 46 Configuring the HMI system 2.1 Processing INI files Activating the function REGIE.INI configuration file section: [UpperScreen] ; Upper screen area above HMI-Wide-Screen. ; The upper screen area is managed by an independent native windows ; application independently of the REGIE management. ;...
Page 47 Configuring the HMI system 2.1 Processing INI files Example Figure 2-2 Example HMI-Advanced Operating the HMI program and OEM application When switching the operation between HMI program and OEM application, use the window shift key <NEXT WINDOW> or simply click. The OEM application is operated in the main window, either via actuation or by a mouse click.
Page 48 ● End user dh\cst.dir\user_gr.com (any file name; is also entered under "Settings") Note The path for the Siemens text file "Dh\Cst.dir\Ifs_gr.com" must exist; if not, an error message is output accordingly. The entry for Siemens is specified in conjunction with ISO language as: SiemensI=file where file equals ifit_xx.com for turning or...
Page 49 Configuring the HMI system 2.1 Processing INI files There are different parameterization options for the names of the text files when assigning the text path. The following table lists the parameterization options and their interpretation by the Help function: Parameters for the text file Interpretation FileName.com The text file that is independent of the language is read-out...
Page 50 Configuring the HMI system 2.1 Processing INI files 2.1.12 Set-up workpieces with job lists Requirements The option "multiple channel sequential programming" and a multiple channel machine with 20 channels are prerequisites. An offline mode is possible; the channels cannot be checked in this case.
Page 51 Configuring the HMI system 2.1 Processing INI files Error messages Error messages are displayed in the following cases: If a part program that does not contain a valid INIT instruction is selected: No INIT instruction found in the part program! There is a reference to a non-existent file in the JOB/DAT file: The following non-existent programs are addressed: There is a reference to a non-existent channel number in the JOB/DAT file:...
Page 52 Configuring the HMI system 2.1 Processing INI files - curMagNo Magazine number; "0", if the current tool is not to be found in or intended for a tool location. - curPlaceNo magazine location number; "0" if current tool is not to be found in or intended for a tool location. Current magazine in magazine list view: - curMagLiMagNo magazine number, Target magazine, target magazine place during loading, unloading, reloading, positioning,...
Page 53 Configuring the HMI system 2.1 Processing INI files Thus, the difference between the name of the NCDDE variables and the tool management variables lies in the prefix. Note The NcddeMmcName and NcddeMmcName entries in the [GLOBAL] section must not have standard value "__xxxx__".
Page 54 2.1.15 Executing from the hard disk (m:n configuration) Requirements This function applies to SINUMERIK powerline only. Included in the NETNAMES.INI file are descriptions of the following: ● Configuration of assignments of multiple HMI components and multiple NCU components (m:n configuration).
Page 55 Configuring the HMI system 2.1 Processing INI files conn_1= NCU_1 conn_2= NCU_2 conn_3= NCU_3 conn_4= NCU_4 EXTCALL_conns=conn_1, conn_2, conn_3, conn_4 ; conn_i identifier only for the NCUs from which the PCU ; can be accessed (with HMI) (see note) ; Description of significant net parameters [param network] bus= opi ;...
Page 56 Configuring the HMI system 2.1 Processing INI files 2.1.16 Activating the V.24 interface Activating the V.24 interface The serial V.24 interface can be activated in the DINO.INI file, section [System]. Here it is possible to save files and assign them to the V.24/PG (COM1/COM2) interfaces. The default setting is 0 (no interface parameterization).
Page 57 It is configured in the NETNAMES.INI file. The "control unit management" option is required for operation station switchover for SINUMERIK powerline. That means maximum 9 PCUs can be operated on 9 NCUs for the m:n configuration or 1 PCU can be operated on max. 20 NCUs (powerline).
Page 58 After switchover: HMI Advanced 1 to NCK1.channel1 HMI Advanced 1 to NCK2.channel1 HMI Advanced 2 to NCK2.channel2 HMI Advanced 2 to NCK1.channel2 Switchover procedure for SINUMERIK solution line Figure 2-4 Switchover (solution line) Initial situation: After switchover: Operating_station1 (on HMI1) to NCK1.channel1 Operating_station1 (on HMI2) to NCK2.channel1...
Page 59 Configuring the HMI system 2.2 Configuring a channel menu Figure 2-5 Assignment of softkeys Note In a system, for example, an operating station can correspond to a channel group. Up to 32 channel groups each with up to 8 channels can be configured in a channel menu. 2.2.3 Configuration of a channel menu for direct channel selection (1:1 configuration) Configuring a channel menu...
Page 60 Configuring the HMI system 2.2 Configuring a channel menu [Stat_2] logChanList = CH_5, CH_7, CH_8 [Stat_3] logChanList = CH_6 [Stat_all] logChanList = CH_1, CH_2, CH_3, CH_4, CH_5, CH_6, CH_7, CH_8 ;********************************************************** ; definition of the channels [CH_1] logNCName = NCU_1 ChanNum = 1 [CH_2] logNCName = NCU_1...
Page 61 Configuring the HMI system 2.2 Configuring a channel menu Switching over channels The following channel menu is displayed when the channel switchover key is pressed with this configuration. Select the channel menu using the channel switchover key from any operating area of the HMI, as shown in the following example: Figure 2-6 Example channel menu...
Page 62 Configuring the HMI system 2.2 Configuring a channel menu 2.2.4 Configuring a double-channel display Configuring a double-channel display If a double-channel display is used, the control unit management options cannot be used. Before the double-channel display in the "Machine" operating area, the following entries must be made in file NETNAMES.INI: [own] owner= HMI_1...
Page 63 Configuring the HMI system 2.2 Configuring a channel menu [MULTI_CHAN_5] CHAN_2 = 2 [MULTI_CHAN_3] CHAN_2 = 4 [MULTI_CHAN_4] CHAN_2 = 3 2.2.5 Channel menu for control unit management for an m:n configuration (powerline) m:n configuration m:n configuration means a group comprising m HMI Advanced units and n NCU units. The HMI units for operating the relevant NCUs can be freely switched over during operation.
Page 64 Configuring the HMI system 2.2 Configuring a channel menu Figure 2-7 Switchover options See also ● On configuring the channel menu for the application case: NETNAMES.INI (Page 308) ● On displaying the channel menu in HMI Advanced: Configuration of a channel menu for direct channel selection (1:1 configuration) (Page 53) 2.2.6 Channel menu for control unit management for an m:n configuration (solution line)
Page 65 The file NETNAMES.INI must be distributed to all systems (NCU, PCU) on which an HMI runs, i.e. for HMI sl on NCU, this file must be placed in directory /oem/sinumerik/hmi/cfg or /user/sinumerik/hmi/cfg, for HMI Advanced it must be placed in directory F:\OEM or F:\USER\.
Page 66 Configuring the HMI system 2.2 Configuring a channel menu Differences between HMI sl and HMI Advanced For HMI Advanced, a channel menu for the direct channel selection must be configured in addition to the channel groups that are used for switching over the operating stations. This configuration is not evaluated or might be missing for HMI sl.
Page 67 Configuring the HMI system 2.2 Configuring a channel menu [K_2] logNCName=NCU_1 ChanNum=2 [K_3] logNCName=NCU_1 ChanNum=3 [K_4] logNCName=NCU_1 ChanNum=4 ;*************************** /* channel menu for TCUs [chan HMI_1] /* common part for HMI Advanced ShowChanMenu = true /* and HMI sl ;Channel groups ;Correlation from channel group to horizontal softkey ;->...
Page 68 Configuring the HMI system 2.2 Configuring a channel menu [CH_GRP_3] Text = Transport Member1.Target = NCU720-1.#1 Member1.Text = NCU720_K1 Member2.Target = NCU720-1.#2 Member2.Text = NCU720_K2 Member3.Target = NCU720-1.#3 Member3.Text = NCU720_K3 Member4.Target = NCU720-1.#4 Member4.Text = NCU720_K4 … [CH_GRP_15] Text = Headend Member1.Target = 192.168.214.241.#1 Member1.Text = NCU720_K1 Member2.Target = 192.168.214.241.#2...
Page 69 Configuring the HMI system 2.2 Configuring a channel menu File CONFIG.INI [T2M2N] SK1=CH_GRP_1 SK2=CH_GRP_3 SK8=CH_GRP_15 The references CH_GRP_xx of the softkeys refer to the channel groups which must be defined in NETNAMES.INI. This notation is binding. This example and the conditional configuration in NETNAMES.INI defines that the channel menu for this operating station must be assigned as follows: Figure 2-8 Horizontal softkey menu...
Page 70 Configuring the HMI system 2.2 Configuring a channel menu [param NCU_1] nck_address= 192.168.214.1,LINE=10,NAME=/NC,SAP=030d,PROFILE=CLT1__CP_L4_INT plc_address= 192.168.214.1,LINE=10,NAME=/PLC,SAP=0201,PROFILE=CLT1__CP_L4_INT name=Machine_1 [param NCU_2] nck_address= 192.168.214.2,LINE=10,NAME=/NC,SAP=030d,PROFILE=CLT1__CP_L4_INT plc_address= 192.168.214.2,LINE=10,NAME=/PLC,SAP=0201,PROFILE=CLT1__CP_L4_INT name=Machine_2 [param NCU_3] nck_address= 192.168.214.3,LINE=10,NAME=/NC,SAP=030d,PROFILE=CLT1__CP_L4_INT plc_address= 192.168.214.3,LINE=10,NAME=/PLC,SAP=0201,PROFILE=CLT1__CP_L4_INT name=Machine_3 ;*************************** ; ChanMenu ;*************************** [chan HMI_1] DEFAULT_logChanSet = Machine_1 DEFAULT_logChan = NCK1.1 ShowChanMenu = true logChanSetList = Machine_1, Machine_2, Machine_3 [Machine_1]...
Page 71 Configuring the HMI system 2.2 Configuring a channel menu [NCK3.1] logNCName = NCU_3 ChanNum = 1 Note Function 1:N for solution line • An HMI-Advanced can be switched over to as many as 4 NCUs. • Drive alarms from an NCU which is not currently linked with the HMI are displayed as a group alarm.
Page 72 ; computer name, enable name with directory data MD9679 CMM_DIRECTORY_SOFTKEY_PATH4=\\R4713\Part2\MPF_DAT .DIR ; Computer name, enable name with directory data The network connection to be specified in MD 9676 CMM_DIRECTORY_SOFTKEY_PATH1 is reserved for SINUMERIK ShopMill or ShopTurn. HMI Advanced (IM4) Commissioning Manual, 03/2009, 6FC5397-0DP10-3BA0...
Page 73 Configuring the HMI system 2.3 Connecting network drives Configuring texts for softkeys Plain text identifiers for selecting network drive connections with softkeys can be stored as language-dependent user alarm texts under numbers 89901 to 89905 in a user text file that is known to the message block (see MBDDE.INI, [TextFiles] section).
Page 74 Configuring the HMI system 2.3 Connecting network drives For the Machine area: $MM_USER_CLASS_DIRECTORY1_M (9516) $MM_USER_CLASS_DIRECTORY2_M (9517) $MM_USER_CLASS_DIRECTORY3_M (9518) $MM_USER_CLASS_DIRECTORY4_M (9519) The display machine data for access authorizations are activated immediately, i.e., after switchover to the respective application, while a change in directories takes effect only after a restart.
Page 75 Configuring the HMI system 2.3 Connecting network drives Configuring a logical drive comprises the following tasks: ● Path name with the following structure: "acttcu://<TCU connector>,<Partition>/<Path name>" For the USB at a TCU name entry, connection field identifying the required connector, and a partition number ●...
Page 76 Configuring the HMI system 2.3 Connecting network drives Connection type / connection The following connections can be selected. No drive: No additional fields are displayed: Local USB: Designation of the local USB interface: - Front (0.2 or 1:0.2 or FRONT) - X203 (1 or 1:1 or X203) - X204 (2 or 1:2 or X204) Partition:...
Page 77 Configuring the HMI system 2.3 Connecting network drives If an operation (copy, delete, edit) is active on the drive at the time of the TCU switchover, the display is retained until the action is finished. The display is not updated until the operation is finished.
Page 78 Configuring the HMI system 2.3 Connecting network drives "Network drives" option The following overview clarifies when the network drives option is needed: Legend: Usable without option: all USB interfaces at the TCU Usable without option: locally usable Locally usable without option; "Remote" only usable with network drives option Only usable with network drives option Only usable with HMI user memory option, locally usable Figure 2-10...
Page 79 Configuring the HMI system 2.4 Simulation Simulation Overview This function can be used to simulate machining on the screen. Data evaluated by the simulation has to be copied into data management in the Dialog programming\Simulation data directory (\DP.DIR\SIM.DIR). When the simulation program is started the following functions can be selected with the "Data matching"...
Page 80 Configuring the HMI system 2.4 Simulation ● User cycles All user cycles loaded into the simulation are displayed: If the cycles have not been loaded before, the cycle interfaces must be defined in the file DPCUSCYC.COM. The cycles are then copied into the simulation when required. Changes to the cycles are not detected automatically and must be detected by means of the "Match cycles"...
Page 81 Configuring the HMI system 2.4 Simulation ● Global work offsets ● Setting data (SEA) ● Global setting data ● Axis-specific setting data ● Protection zones (PRO) ● Sag/angularity (CEC) The data can be selected in any combination. The channels are selected using softkeys (if there is more than one channel for simulation);...
Page 82 Configuring the HMI system 2.4 Simulation If a cycle is changed, it must be copied into the simulation using the "Match cycles" softkey. Only cycles that have changed since they were last accessed are copied into the simulation (along with newly imported cycles). Cycles in the simulation that have since been deleted are deleted from the simulation.
Page 83 Configuring the HMI system 2.4 Simulation In some cases (lathes) the entries can be directly accessed at the user interface: a[VIS] … ;Plane viewpoint default for standard milling: BDL(BackDownLeft) ;possible BDL, BUL, BUR, BDR, FDL, FUL, FUR or FDR PLANE_VIEW=BDL [VIS] …...
Page 84 Configuring the HMI system 2.4 Simulation 2.4.3 Speeding up the simulation boot Simulation start The simulation application is normally started only on request by the operator. This means that the system is only loaded as required as a result of the software components to be downloaded.
Page 85 Configuring the HMI system 2.4 Simulation 2.4.4 Expanding geometrical tool data Representation of the tools Previously tools could only be shown with their cutting edge, shaft and holder, which could be calculated from the data in the NCK. With the expansion of the tool geometry data, it is now possible to show only the cutting edge ("flying edge") in the simulation image, without the shank and holder.
Page 86 $MN_MM_TYPE_CC_TOA_PARAM[0]=4 ;data type float for TC_DPC1 3. Set up SimToGeo.ini: Define link entry for Siemens or User OEM parameter and expand geometrical data. This is done using the OEM variable ($TC_DPCS1/$TC_DPC1). The values of these variables determine the geometrical block that is used.
Page 87 For example [500.1]. [Settings] Link=TC_DPCS1 ;link to TO_INI.INI, Siemens OEM ;Link=TC_DPC1 ;link to TO_INI.INI, USER OEM [500.1] ;T1 D1 roughing tool type 500 SL3 L1=100, L2=55, R1 tool_type=500 ;tool type then $TC_DP1 is not required insert_length=10 ;TC_DP8, plate length...
Page 88 Configuring the HMI system 2.4 Simulation DP_SIMNCK_MM_NUM_GUD_NAMES_NCK_OFFSET = 5 with MD 18120: MM_NUM_GUD_NAMES_NCK DP_SIMNCK_MM_NUM_GUD_NAMES_CHAN_OFFSET = 30 with MD 18130: MM_NUM_GUD_NAMES_CHAN DP_SIMNCK_MM_GUD_VALUES_MEM_OFFSET = 20 with MD 18150 MM_GUD_VALUES_MEM DP_SIMNCK_MM_NUM_USER_MACROS_OFFSET = 10 MD 18160: MM_NUM_USER_MACROS DP_SIMNCK_MM_NUM_MAX_FUNC_NAMES_OFFSET = 40 with MD 18170 MM_NUM_MAX_FUNC_NAMES DP_SIMNCK_MM_NUM_MAX_FUNC_PARAM_OFFSET = 350 with MD 18180 MM_NUM_MAX_FUNC_PARAM DP_SIMNCK_MM_MAX_SIZE_OF_LUD_VALUE_OFFSET = 400...
Page 89 The following alarm numbers are available for the cycle alarms, compile cycle alarms, and PLC alarms: Numerical range Designation Effect Deletion 60000 - 60999 Cycle alarms (Siemens) Display, interlocking NC start Reset 61000 - 61999 Display, interlocking NC start, no motion Reset after executing the pre-decoded blocks...
Page 90 Configuring the HMI system 2.5 Configuring user alarms Supported languages Table 2- 2 Languages and code page/ANSI table used Language ⇓ Abbreviation Code page ANSI table (Windows) (DOS) Czech 1250 Danish 1252 Finnish 1252 French 1252 German 1252 Hungarian 1250 Italian 1252 Dutch...
Page 91 Configuring the HMI system 2.5 Configuring user alarms Assignment between ANSI tables and fonts Table 2- 3 ANSI table 1250 (Central Europe) Font File name Name of font Arial Cearial.ttf Arial CE (True Type) Arial bold Ceariabd.ttf Arial CE Bold (True Type) Arial italic Ceariali.ttf Arial CE Italic (True Type)
Page 92 Configuring the HMI system 2.5 Configuring user alarms 2.5.2 Configuring user alarms Files supplied with the system The files with the alarm texts in the ASCII format are saved on the PCU hard disk under the following path: F:\dh\mb.dir\alm_XX.com F:\dh\mb.dir\aln_XX.com F:\dh\mb.dir\alp_XX.com F:\dh\mb.dir\alz_XX.com CZYK...
Page 93 Configuring the HMI system 2.5 Configuring user alarms Editor Any ASCII editor (e.g. DOS editor) can be used for editing files. When editing the text files with a different editor, make sure that they are then saved in ASCII format. Note Changes to the alarm texts only take after the HMI has restarted.
Page 94 Configuring the HMI system 2.5 Configuring user alarms The alarm and message texts are stored in the MBDDE alarm texts directory. 1. Convert the old text file to an ANSI text file using "Save As…" in the Windows Editor (WinWord, Notepad, etc.). 2.
Page 95 Configuring the HMI system 2.5 Configuring user alarms 1. The alarm text extension is inserted into the alarm text file (e.g. alp_gr.com) as follows: 700000 0 0 "Attention: %1<DUMMY> failed!" The %1 parameter evaluates the first parameter transferred from the PLC and is linked to the "dummy_gr.com"...
Page 97 Parameterizing machine data Handling machine data via the HMI Overview Specific settings can be made to address manufacturer manufacturer and user requirements ● Configuring the HMI operator interface using INI files ● Parameterizing the control using machine data ● Programming PLC Functions DANGER Changes in the machine data have a considerable influence on the machine.
Page 98 Parameterizing machine data 3.1 Handling machine data via the HMI ● Unit of the machine data ● Effectiveness Effectiveness of the machine data The right-hand column indicates when a machine data becomes effective: so = immediately effective cf = when confirmed via the "Activate MD" softkey re = reset po = POWER ON (NCK Power On reset) Physical units of the machine data...
Page 99 Parameterizing machine data 3.1 Handling machine data via the HMI ● Each area has a maximum of 13 groups (group 14 is reserved for Expert parameters, bit 15 is reserved for add-ons). ● Display machine data is subdivided into groups. Display filter active If the display filter is active, only the set display groups are displayed.
Page 100 Parameterizing machine data 3.1 Handling machine data via the HMI Filter criteria The following table shows the criteria for displaying machine data in the order in which they are evaluated: Criterion Checks 1. Access authorizations If the level of access authorization is not sufficient, the MD is not displayed.
Page 101 Parameterizing machine data 3.1 Handling machine data via the HMI • General display machine data • Channel-specific display machine data • Machine data for SIMODRIVE drives (powerline) • Machine data for SINAMICS drives, for Control Units, I/O modules and infeed Example Creating user view TEST01: 1.
Page 102 Parameterizing machine data 3.1 Handling machine data via the HMI The following softkeys are available to edit the user view: 1. You can shift lines using the softkeys "Up" or "Down" - correspondingly, lines are deleted with "Delete line". 2. Select "Properties" in order to enter descriptive text for the machine data or to modify existing text.
Page 103 Parameterizing machine data 3.2 Parameterizing the control using machine data Parameterizing the control using machine data 3.2.1 Machine data for setting actual value, scratching, PRESET Access levels for system frames The machine manufacturer or user can assign the access levels for system frames as well as for individual functions and data areas using display machine data.
Page 104 Parameterizing machine data 3.2 Parameterizing the control using machine data MD 28082: $MC_SYSTEM_FRAME_MASK Workpiece reference points Cycles Transformations Version 1 without system frame: The MD does not exist or Bit 0 for the system frame for scratching or actual value setting is not set.
Page 105 Parameterizing machine data 3.2 Parameterizing the control using machine data Scratching When this is selected the active frame is offered. A different frame can be selected by means of an entry in the "Work offset" field. ● Scratching with system frame: With G500 in the "Work offset"...
Page 106 Parameterizing machine data 3.2 Parameterizing the control using machine data Example: Program WCS display SZS display N110 X100 N110 X100 N120 X0 N130 $P_PFRAME=CTRANS(X,10) N140 X100 N150 ... Note To set the actual-value display: see the machine manufacturer's information. 3.2.3 Changing the access level for the "Basis WO"...
Page 107 // Definition file for access level instructions for Siemens system applications (e.g. standard cycles, ShopMill, etc.) A additional Siemens definition file, which is used to configure the system, is saved on the PCMCIA card or CF card in the NC system software. HMI Advanced (IM4)
Page 108 14018. The preset for the current execution authorization corresponds to the access authorization on the control unit, i.e. key-operated switch setting 0 to 3 or a password for end users as far as Siemens. References: Programming Manual, Chapter "Access levels for NC commands".
Page 109 Parameterizing machine data 3.2 Parameterizing the control using machine data Entry in the file NCTEA_GR.TXT: 14510[0] My integer text for PLC-MD 14510.0 14514[0] Text for float data 14514.0 14516[2] This is the text in HEX for MD14516.2 result in the display: 14510[0] My integer text for PLC-MD 14510.0 14514[0] Text for float data 14514.0 14516[2] This is the text in HEX for MD14516.2...
Page 110 Parameterizing machine data 3.2 Parameterizing the control using machine data 3.2.7 Hiding axes Function Via the channel-specific MD 20098: DISPLAY_AXIS to suppress the display of the axes in the Machine area. All axes are displayed by default. Axes can be hidden in the following windows in the Machine operating area. ●...
Page 111 The data for the specified directory is to be stored in the DRAM. Depending on MD 11291: DRAM_FILESYST_SAVE_MASK a copy is kept in the FFS on the NC card. Bit 0 CST directory (Siemens cycles) Bit 1 CMA directory (machine manufacturer cycles) Bit 2...
Page 112 No files are saved. If the control is switched off, the data on the NCK is lost. = 1: The data in the DRAM is saved in the FFS of the NC card. Bit 0 CST directory (Siemens cycles) Bit 1 CMA directory (machine manufacturer cycles) Bit 2 CUS directory (user cycles) Saving in the FFS avoids having to reload the objects when booting.
Page 113 Parameterizing machine data 3.2 Parameterizing the control using machine data Possible values are: Display as binary value Display as decimal value Display as hexadecimal value These settings apply to both the actual-value window and the editor window. Example In the NC program, the movement of axes from X120 Y20 Z-50 to X200 Y200 Z-120 looks like this in binary display: X=120 Y=20 Z=-50 STAT='B010' TU'B011101' X=200 Y200 Z=-120 STAT'B110' TU='B011111'...
Page 114 Parameterizing machine data 3.2 Parameterizing the control using machine data 3.2.11 Representing the spindle utilization Function Up to now, the display range of the spindle utilization in the Machine main screen was represented at 100%. You can set the display range of the bar graph for representation of the spindle load to 200% using display MD 9429: MA_SPIND_POWER_RANGE.
Page 115 Parameterizing machine data 3.2 Parameterizing the control using machine data Determining the normalization factor The normalization factor is determined by measuring the spindle using a function generator, servo trace function, and information in the motor data sheet. Function generator Figure 3-4 Function generator 1.
Page 116 Parameterizing machine data 3.2 Parameterizing the control using machine data Servo trace function Figure 3-5 Servo trace: Main screen 1. Open the Trace function main screen by pressing the "Drive/servo" softkey followed by the "Servo trace" softkey in the "Start-up" operating area. 2.
Page 117 Parameterizing machine data 3.2 Parameterizing the control using machine data Example: In the diagram, the measured power is 10.5 kW. Figure 3-6 Servo trace: Evaluation If the utilization display is to indicate 100% for nominal data and higher values at operation above the nominal working point, the normalization factor setting can be calculated from the motor data or from the diagram and measurement as follows: MA_SPIND_MAX_POWER = Maximum_of_the_measured_power / rated power_S1 * 100...
Page 118 Parameterizing machine data 3.2 Parameterizing the control using machine data HMI Advanced (IM4) Commissioning Manual, 03/2009, 6FC5397-0DP10-3BA0...
Page 119 Programming PLC Functions Activating the data transfer between the PLC and NCK Function Data transfer from/to NCK with the following properties can be started via the PLC: ● Data transfer from the hard disk to or from the NCK (workpiece directory, part program, etc.) using job lists.
Page 120 Programming PLC Functions 4.1 Activating the data transfer between the PLC and NCK References: ● Operating Manual HMI-Advanced ● Function Manual Basic Functions: Various NC/PLC interface signals and functions (A2) Job processing A PLC job is processed according to the following scheme: ●...
Page 121 MASCHINE.INI: [PLC_REQUEST] DefaultAnswer=yes Multiple operator panel fronts/NCUs M:N (only SINUMERIK powerline) In an m:n system, HMI-Advanced is assigned to a netmaster NCU/PLC in NETNAMES.INI. The bus address of the NCU is configured in the [param network] section.
Page 122 Programming PLC Functions 4.2 Transferring the actual task number of the HMI to the PLC Transferring the actual task number of the HMI to the PLC Task number A task describes the position at which an operating area is attached in the HMI area menu, i.e., the highest level.
Page 123 Programming PLC Functions 4.2 Transferring the actual task number of the HMI to the PLC Configuration The current task number is transferred to the PLC in a data block section that can be specified as a string in the display MD 9032: HMI_MONITOR as follows: DBxx.DBByy with: xx is the number of a data block yy is the byte number of the 1st byte of the transfer area (word limit)
Page 124 Programming PLC Functions 4.3 Channel/spindle selection via the PLC Channel/spindle selection via the PLC Channel selection Channel selection or display is initiated as follows (display in "Channel name" field): DB 19, DBB 32 = 01000001 [binary] channel selection DB 19, DBB 33 = <channel number> FF for next channel Spindle selection Spindle selection is initiated as follows (display in spindle window):...
Page 125 Programming PLC Functions 4.4 Configuring the display of messages in the header Configuring the display of messages in the header Function Using the PLC (also see the Chapter Cross-channel status display with icons), it is possible to configure a two-line text display to appear in the "Program name" field in the header of JOG and MDA modes (e.g.
Page 126 Programming PLC Functions 4.4 Configuring the display of messages in the header Table 4- 1 User PLC-DB interface Program path Start DBBx Start-DBWx Start-DBBx Start-DBBx Start-DBBx line +5-17 Data type Byte Word Byte Byte String Significance Bit0=1: there is Offset for text to Number from 0 Index from –127 ...128 String containing...
Page 127 After displaying the text in the header, the HMI writes zero again in bit 0 and the interface is enabled for the PLC for the next action. Behavior for M: N (only SINUMERIK powerline) For the function M : N, both text lines for passive switching must be deleted. In active switching, as in area switching, the content of the variables is evaluated and displayed.
Page 128 Programming PLC Functions 4.5 Starting a block search across several channels Starting a block search across several channels Function For this block search, the NCK is operated in the program test mode, so that interactions between channel and synchronous actions and between multiple channels are possible within an NCK.
Page 129 Programming PLC Functions 4.5 Starting a block search across several channels Configurations 2 to 4: No block search is performed in the other channels (in contrast to the current channel); "program test" mode is active in the other channels until a stop condition (e.g.
Page 130 In addition to SINUMERIK icons, manufacturer-defined icons can also be configured in the file HEADER.INI file and in DB19 DBB32-34. SINUMERIK icons The following SINUMERIK icons with the TrueColor color setting are available (file name in brackets): Channel status Channel RESET (NC_RESET.BMP)
Page 131 Programming PLC Functions 4.6 Cross-channel status display The dimensions of the SINUMERIK icons are as follows: ● Resolution 640x480: 16x16 pixels ● Resolution 800x600: 20x20 pixels ● Resolution 1024x768: 27x26 pixels Note When using the "Reversible spindles" or "Axis container" functions, the spindle status is output before the spindle reversal or assignment to axis/spindle container, i.e.
Page 132 Programming PLC Functions 4.6 Cross-channel status display The following hierarchy applies (from highest to lowest priority): 1. Channel STOP (highest priority) 2. Spindle not enabled 3. Feed is not enabled 4. Channel active 5. Channel RESET (lowest priority) Syntax: ChanStatFeedStopSpindleStop = <Channel number> Spindles = <Spindle number1>,...,<Spindle number n>...
Page 133 The SINUMERIK icons are permanently assigned to an output position. A section is created in the HEADER.INI configuration file for each position used. Example 1 with SINUMERIK icons: View of the program status line with SINUMERIK icons for 4 channels and 2 spindles: Figure 4-2 Program status line with icons (1) These displays always have the predefined channel or spindle number.
Page 134 Programming PLC Functions 4.6 Cross-channel status display HEADER.INI file: [Pos1] first display position ChanStatFeedStopSpindleStop = 3 Spindles = 1,2 Channel status of channel 3 is displayed, superimposed with feed inhibit channel 3 and spindle inhibit for spindles1 and 2 [Pos3] third display position ChanStatFeedStop = 2 Channel status of channel 2 is displayed...
Page 135 Programming PLC Functions 4.7 User status display (OEM) User status display (OEM) Function Additionally (or alternatively), PLC-controlled (DB x, DBB y) user icons (symbols) linked to specific machine states can be output. Procedure: 1. Declaration of icons and positions 2. Control of icon call by the PLC Enter the name of the user icons and the associated positions in the HEADER.INI file in the [UserIcons] section under identifiers UI_0 to UI_31.
Page 136 Programming PLC Functions 4.7 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: Superimposition With a non-unique selection (bits for multiple identifiers whose image is to be displayed at the same position): The image with the lower identifier number is superimposed with the image with the higher...
Page 137 Programming PLC Functions 4.7 User status display (OEM) The interface in the user DB has the following format: Start-DBB byte Bit0=1: there is something to do All bits=1: job is acknowledged by HMI Start-DBB +18 byte All bits=0: PLC can write to interface again. Start-DBB +1 word Offset for text from alpu_xx.com to be displayed;...
Page 138 Programming PLC Functions 4.7 User status display (OEM) Each bit in this double word represents exactly one OEM icon corresponding to the screen number. Thus, if bit 0 is set, bit map OI_0 is displayed. If a bit is reset, the associated bit map is deleted.
Page 139 – The system asks whether you wish to install the MPI drivers – Local without communication to NC, with NC simulation 6. For SINUMERIK solution line, select: – Online with communication to NC 7. The system lists all the entries you have made...
Page 140 With the Connection Wizards, connections are possible both via MPI and Ethernet, depending on the control unit. Use an Ethernet connection for SINUMERIK solution line and an MPI connection for SINUMERIK powerline. The type of connection depends on the software installed on the 840Di control unit.
Page 141 Diagnostics and service 5.1 Installing HMI software on a PG/PC ● Focus control in connection with OEM software ● All applications of a standard PC run under one desktop. How to call-up HMI-Advanced in a separate desktop as remedy is described in the following section.
Page 142 Diagnostics and service 5.1 Installing HMI software on a PG/PC Note 1. The key combination CTRL+ALT+DEL of the task manager only works in the standard desktop. In dynamic desktops, the task manager can only be called directly from the task bar.
Page 143 Diagnostics and service 5.1 Installing HMI software on a PG/PC closing of the application. During this synchronization, the desktop switch cannot process any other requests. The synchronization is aborted if the application is still being executed after 15 seconds. In this case, the desktop is closed too.
Page 144 Diagnostics and service 5.1 Installing HMI software on a PG/PC 5.1.4 Operating the desktop switch application Overview The user interface for the desktop switch application can be configured: ● Keyboard hotkeys ● Dialog window ● Icons in the task bar Hotkeys: <Alt+1>...
Page 145 Diagnostics and service 5.1 Installing HMI software on a PG/PC Note If WindowOnTop = False is configured in HMIDESK.INI, the window must be brought to the foreground using <Alt + TAB>. HMI Advanced (IM4) Commissioning Manual, 03/2009, 6FC5397-0DP10-3BA0...
Page 146 Diagnostics and service 5.2 Saving a screenshot Saving a screenshot Application To provide more information for troubleshooting and problem analysis, you can save a screenshot of a file. File type and file name for screenshots You can generate a screenshot with key combination <Ctrl> + <P>. The entire screen is copied to a file with automatically generated file name according to the following scheme: ●...
Page 147 Diagnostics and service 5.3 Displaying versions Displaying versions Overview The version data displayed under “NCU Version” state the software versions on the CF card. This especially applies to measurement cycles and cycle versions. ● Version data, NCU ● Version data, HMI files ●...
Page 148 Diagnostics and service 5.4 Setting-up and upgrading the system Setting-up and upgrading the system 5.4.1 Series commissioning Series commissioning The "series commissioning" function is used to back-up (archive) the data of a control. This data back-up can also be transferred to other controls so that they are all brought into the same state.
Page 149 Diagnostics and service 5.4 Setting-up and upgrading the system Creating an archive To create a commissioning archive: 1. In the operator area "Services" select "Series commissioning" on the expanded softkey bar. 2. Select archive content. If HMI data are selected for the archive: The F:USER directory is always backed up.
Page 150 Diagnostics and service 5.4 Setting-up and upgrading the system For compile cycles (CC) that can be downloaded, the following specifically applies: The compile cycles that can be loaded are archived in the series commissioning under the following requirements: ● In the commissioning archive, in the target directory ../NC_CARD.DIR/CCOEM.DIR, there must be at least one compile cycle.
Page 151 Diagnostics and service 5.4 Setting-up and upgrading the system Figure 5-5 Selecting system data blocks Structure of the INI file The data blocks are entered into a descriptive file with the *.INI file extension; their contents should be kept when upgrading. The contents of this file are structured line-by-line as follows: ;message=<Text>...
Page 152 Diagnostics and service 5.4 Setting-up and upgrading the system ● If ranges of data blocks are addressed (2), then it is not permissible to specify additional byte addresses or byte range, otherwise an error message is output. If byte addresses are defined for a data block (3, 4), then for this data block there may be no entry without byte address (1, 2) otherwise an error is output.
Page 153 In the following example, data blocks DB3, DB67 and DB111 are not to be overwritten. 1. As back-up, create a series commissioning archive of the PLC data. 2. Create a descriptive file with the following contents: ;Message= designed by XXX (SIEMENS AG Erlangen) DB3[3-78] DB67 ; DB67 complete...
Page 154 Diagnostics and service 5.4 Setting-up and upgrading the system Result All of the data blocks of the upgrade archive are transferred into the PLC for which no entry exists in the descriptive file: The PLC was upgraded to the current status without overwriting data blocks DB3, DB67 and DB111.
Page 155 Diagnostics and service 5.5 Service displays Service displays Overview of service displays When "Service Displays" is selected the "Service Overview" window is displayed. Here, the various operating states are indicated for each machine axis by traffic lights. A selection of more displays for diagnosing faults also appears: ●...
Page 156 Diagnostics and service 5.5 Service displays Output of configuration data The configuration data of a machine (HMI version, NCU version, axis configuration, drive configuration, bus parameters, active bus nodes) can be written into a file and subsequently read out or printed. Configuration data is output in 2 stages: 1.
Page 157 Diagnostics and service 5.5 Service displays 5.5.2 Displaying system resources Function The system resources for the NCU are displayed in the dialog "NC utilization": ● The net and overall runtime of the position controller, the interpolator and the pre-run in milli-seconds ●...
Page 158 Diagnostics and service 5.6 Action log Action log 5.6.1 Setting the action log Overview The "action log" function can be used to log operating sequences. By default, if the action log is enabled, the data that can be logged are recorded. The action log setting is password- protected (access level 3: end user).
Page 159 Diagnostics and service 5.6 Action log Logged data The following data are logged: • Alarm status change: Alarms and PLC messages, incoming and outgoing. All of the displayed alarms and messages can be logged. • Keys (only ShopMill): For HMI-Advanced, this selection has no function. •...
Page 160 Diagnostics and service 5.6 Action log PLC signal: (initiates writing to file CRASH.COM) • Operating mode • Actual main program that is selected (only AUTO) • Actual block that is active (only AUTO and MDI) and its predecessor and successor (three block display). •...
Page 161 Diagnostics and service 5.6 Action log See also ACTLOG.INI (Page 274) 5.6.2 Structure of the log file Overview The file ACTION.COM is generated if the action log is activated, i.e. data logging is enabled. The file ACTION.COM is a binary file and is always repeatedly overwritten as ring-type buffer.
Page 162 Diagnostics and service 5.6 Action log --- 30.03.2006 13:26:04 HMI-Adv. RE 0 KEY_PRESSED Key pressed: VSK 7 SHIFT+F8 ( 14) --- 30.03.2006 13:26:01 <default> 0 OPEN_WINDOW Windowstate changed: State 9, Index 13 in Application "DG" --- 30.03.2006 13:26:01 HMI-Adv. RE 0 KEY_PRESSED Key pressed: VSK 5 SHIFT+F6 ( 12) --- 30.03.2006 13:25:59 <default>...
Page 163 Diagnostics and service 5.6 Action log Zero-Offset Shift Fine Mirror Rotation Factor ACTFRAME 24.000000 22.300000 0 0.000000 1.000000 IFRAME 56.000000 3.300000 0 0.000000 1.000000 PFRAME 4398.000000 34.340000 0 0.000000 1.000000 EXTFRAME 0.000000 0.000000 0 0.000000 1.000000 TOTFRAME 0.000000 0.000000 0 0.000000 1.000000 ACTBFRAME 0.000000 0.000000 0 0.000000 1.000000 SETFRAME 12.000000 0.300000 0 0.000000 1.000000 EXTSFRAME 33.000000 2.300000 0 0.000000 1.000000...
Page 164 Diagnostics and service 5.6 Action log Saving logs To read out the log files, proceed as follows: 1. In order to save the log files, select "Save log". The following files can be saved: – ACTION.COM (binary file) – ACTION.LOG –...
Page 165 Diagnostics and service 5.6 Action log The Trace options should be selected in consultation with system or OEM development personnel. The log created is used to investigate software problems and must be sent to system or OEM development personnel for analysis and diagnostics purposes. Creating the log file The log file is called debug.out or _debug.out and is saved in the following directory: ..\mmc2...
Page 166 Diagnostics and service 5.7 HMI Analyzer HMI Analyzer 5.7.1 Using the HMI Analyzer The HMI Analyzer diagnoses any problems occurring on a PCU 50.3. The result of the analysis is displayed via the HMI Analyzer in lists. It can also be stored in ASCII files and analyzed later.
Page 167 Diagnostics and service 5.7 HMI Analyzer Section [Additional] Additional INI files that are not subject to the INI concept of HMI-Advanced, i.e. INI files from add-on applications, can be entered here. The complete path is needed for the entries. Only the file of this path is analyzed.
Page 168 Diagnostics and service 5.7 HMI Analyzer The INI files saved as profiles are the "resultant" INI files. In this way, the profile shows the current valid configuration. The result files can be considered individually in an external ASCII editor. Deleting the current data (profile) Individual profiles can be deleted from the hard disk via the menu item "File"...
Page 169 Diagnostics and service 5.7 HMI Analyzer 5.7.3 Analyzing INI Files System → Files All entries of the analyzed INI files are displayed here. Display of the corresponding INI entries from files that are subject to the INI concept of HMI-Advanced. The directory from which the entry comes is also displayed ("Source"...
Page 170 Diagnostics and service 5.7 HMI Analyzer PagePoolUsage Swap memory in KB DiffPagePoolUsage Modification of the swap memory since the start of the HMI Analyzer or since the last reset PageFaults Access violations of the swap file DiffPageFaults Modification of the access violations of the swap file since the start of the HMI Analyzer or since the last reset Additional settings (below): Cyclic...
Page 171 Diagnostics and service 5.7 HMI Analyzer 5.7.4 Application Examples (1) OEM application that is linked-in does not start Problem: An OEM application was linked into HMI-Advanced, but it does not start after actuating the corresponding softkey or it starts another application. Possible cause: Due to the hierarchical execution of the HMI directory, the entry made in the Regie.ini file was overwritten by an entry in another regie.ini file with a higher priority and is therefore not...
Page 172 Diagnostics and service 5.7 HMI Analyzer (2) No connection to the NCU/PLC Problem: In spite of adaptation to the NCU/PLC address in the mmc.ini file, no connection to the NCU/PLC can be established. Possible cause: Due to the hierarchical execution of the HMI directory, the entry made in the mmc.ini file was overwritten by an entry with a higher priority and is therefore not in effect.
Page 173 Diagnostics and service 5.7 HMI Analyzer (3) Blocking, very slow system Problem: The system is very slow and blocks the area switcher completely in some aspects. After a certain period of time, all the operating actions are suddenly processed sequentially. Possible causes: The area application that is newly selected by the area switcher sets up hotlinks when loading.
Page 174 When programming an OPC Client Application, the variables to be read are automatically set up as a hotlink if a variable of the respective group is defined as a hotlink. In addition, PLC variables for SINUMERIK OPC Server are automatically (Flag IsActive=True) set up as a hotlink.
Page 175 Tool management Setting tool management parameters on the HMI 6.1.1 How to create a real magazine Creating real magazines In this screen, magazines are defined with the appropriate data or displayed with existing data. Figure 6-1 Start-up: Magazines Magazines Name Enter a new name or select an existing name for the real magazine.
Page 176 Tool management 6.1 Setting tool management parameters on the HMI Note Up to 32 magazines (including buffer and loading magazine) are possible, therefore a maximum of 30 real magazines. Creating a new magazine Follow the steps outlined below: 1. Press the "New" softkey. The magazine number is assigned by the system (in the order they were created).
Page 177 Tool management 6.1 Setting tool management parameters on the HMI Creating PLC data: ● When all magazines, buffers and loading points (for all channels / TO areas) are entered, the configuration data must be created for the PLC and transferred to it. To do this, press the "PLC data"...
Page 178 Tool management 6.1 Setting tool management parameters on the HMI Locations Name Enter or select the name of the buffer. Display text Language-dependent name of the magazine If it exists, the display text is immediately displayed from patm_xx.ini. Number Display of the current magazine number Type Selection of buffer type (spindle/toolholder, gripper, transfer location, loader) Index...
Page 179 Tool management 6.1 Setting tool management parameters on the HMI Example If, for example, tools are to be loaded from 2 magazines onto "Spindle_1", the assignment must be made for both magazines. Figure 6-3 Example of a machine with buffer and loading magazine Name Distance to change position Spindle_1...
Page 180 Tool management 6.1 Setting tool management parameters on the HMI 6.1.3 Loading points and loading locations Loading locations Loading locations are places that are needed for loading the magazine. There are two types of loading locations: ● Loading points ● Loading stations All loading locations are stored in an internal loading magazine with the number 9999.
Page 181 Tool management 6.1 Setting tool management parameters on the HMI Note Loading magazine 9999/1 is always automatically set for loading/unloading of the spindle (manual loading point). Loading points Loading points are areas on the machine at which it is possible to directly load the magazine, i.e.
Page 182 Tool management 6.1 Setting tool management parameters on the HMI Example Both magazines can be loaded via Spindle_1. Loading point_1 is only assigned to Magazine_1 and Loading point_2 is only assigned to Magazine_2. Figure 6-5 Example of a machine with 2 magazines and 3 loading locations Name Distance to change position Manual loading point...
Page 183 Tool management 6.1 Setting tool management parameters on the HMI 6.1.4 Select location type Location types In this screen, new location types are defined with the required data or existing ones are displayed. Figure 6-6 Start-up: Location types Location types Name Name of the location type (max.
Page 184 Tool management 6.1 Setting tool management parameters on the HMI Assigning parameters for a location type The number of half locations occupied by a tool in the magazine is defined when a location is parameterized. This corresponds to the tool size. The four-digit number, e.g.
Page 185 Tool management 6.1 Setting tool management parameters on the HMI Oversized location type for chain magazines In a chain magazine, a tool with the size 2 2 1 1 occupies one half location on the right and one half location on the left in addition to the normal magazine location. Figure 6-8 Oversized location type for chain magazines Parameter settings for the location type:...
Page 186 Tool management 6.1 Setting tool management parameters on the HMI Oversized location type with free half locations for box magazine In a box magazine, a tool with the size 2 2 2 2 occupies one half location in each direction in addition to the normal magazine location.
Page 187 Tool management 6.1 Setting tool management parameters on the HMI First a check is performed to see whether there is a location with type A in the magazine to be searched. If there is not, the search function will proceed to search for a location of type B or C.
Page 188 Tool management 6.1 Setting tool management parameters on the HMI 6.1.7 Magazine configuration Create magazine configuration For each TO unit, there is only one common magazine configuration for configuring the tool management. A magazine configuration can consist of one or more real magazines. As one TO unit can be assigned to several channels, this magazine configuration is available to the associated channels simultaneously.
Page 189 Tool management 6.1 Setting tool management parameters on the HMI Empty location search First location forward / Current location forward Last location backward / Current location backward Symmetric current location Wear group (wear Leave tool status unchanged group) Actively change tool state Number of locations: Total number of locations in the configuration (all assigned magazines)
Page 190 Tool management 6.1 Setting tool management parameters on the HMI 6.1.8 How to create and load a configuration Create new magazine configuration The "Configuration" and "Real magazine" screens show the location type assignments for the entire configuration or the selected magazine. 1.
Page 191 Tool management 6.1 Setting tool management parameters on the HMI Delete magazine configuration: 1. If the cursor is positioned on the selection field for the configuration, you can delete the selected configuration by pressing the "Delete" softkey. 2. Load magazine configuration 3.
Page 192 Tool management 6.2 Settings in the configuration file Settings in the configuration file 6.2.1 Parameterize the paramtm.ini file Configuration Customized differences from the factory-set ini data are stored in the "user" or "oem" directories. Only changes to the visual aspect of the operator interface are stored here, i.e. changes that can be made by settings in the HMI operator interface itself.
Page 193 Tool management 6.2 Settings in the configuration file ● If adapter data is set in the NCK, the magazine list can be displayed either transformed or not transformed (softkey on the ETC bar). The setting is made in paramtm.ini, section [TMMODES], with the entry START_MAGLIST_TRANSFORMED ●...
Page 194 Tool management 6.2 Settings in the configuration file SKTLLIST=7 ; Displays the tool list SKACLIST=7 ; Displays the tool offset list SKTOOLLOAD=5 ; Loading tools SKTOOLUNLOAD=5 ; Unloading tools SKTOOLMOVE=7 ; Moving tools in the magazine SKSETTINGS=4 ; Softkey settings SKFILFCT=4 ;...
Page 195 Tool management 6.2 Settings in the configuration file SKNCNEWTOOLED=6 ; Create new cutting edges in NC SKNCDELTOOLED=6 ; Delete cutting edges in NC SKNCDELTOOL=5 ; Delete tools in NC SKTRAFO=7 ; Toggle transformed / not transformed view of edge data SKCHECKACTIVATE=6 ;...
Page 196 Tool management 6.2 Settings in the configuration file SKACLREPR2=7 ; Display 3_ActList SKACLREPR3=7 ; Softkey delete D numbers SKDZERO=7 ; Softkey search for D numbers SKDFIND=7 ; Softkey filter lists SKBATCH=7 SKBFILTER1=7 ; Softkey Filter1 SKBFILTER2=7 ; Softkey Filter2 SKBFILTER3=7 ;...
Page 197 Tool management 6.2 Settings in the configuration file TOOLBASE_COL3=20 TOOLBASE_COL4=20 [DEFAULT SETTINGS] ; Create default tool settings: ; see paramtm.ini or paramtm.txt in path mmc2 ; Magazine list: Load, data input directly in the list: ; 0=Due to the missing input, the default settings must be ;...
Page 198 Tool management 6.2 Settings in the configuration file TOOLPLACESPEC=1 ; 0=No monitoring (default) ; 1=Time monitoring ; 2=Workpiece count monitoring TOOLMONITOR_MODE=0 ; Tool search, number of replacement tool ($TC_TP10) ; 0 ... 32000 TOOLSEARCH_MODE=0 ; Default setting of grinding-specific tool data at creation: ;...
Page 199 Tool management 6.2 Settings in the configuration file ; (magazine list only) ; DELETE_TOOL_ON_UNLOAD=0 ; 0=Do not process cutting edge parameters outside the tool type ; (default) ; 1=Process cutting edge parameters outside the tool type ; (if not equal to 0) EDGE_PARAMS_OUT_OF_TOOLTYPE=1 ;...
Page 200 Tool management 6.2 Settings in the configuration file ; "Tool / magazine list" main menu, the "Tool details" softkey ; can be replaced by the new "Data management" softkey. ; The "Tool details" softkey is then stored with the same ;...
Page 201 Tool management 6.2 Settings in the configuration file ; stored on the code carrier in inches. . If "inch" is set in the NCK ; all softkeys are disabled and code carrier functions start. DATABASE_LENGTH_UNIT=-1 ; The inch/metric setting is considered for the code carrier ;...
Page 202 Tool management 6.2 Settings in the configuration file ; 2048=in (Load) ; 4096=Regular tool (permanent in NCK) ; 8192= ; 16384= ; Default is 4828 (4+8+16+64+128+512+4096), ; For code carrier 92 (4+8+16+64) CABIB_TOOLSTATE_MASK=4828 SINCOM_TOOLSTATE_MASK=4828 CODECARRIER_TOOLSTATE_MASK=92 TOOLSEARCH_TC_TP10_FROM_DB=0 ; Tool search:Processing $TC_TP10 in conjunction with the ;...
Page 203 Tool management 6.2 Settings in the configuration file ; 0: Do not read ReadLanguageIni=1 SearchPlaceMethod=NoInternalTool ; Don’t modify! ; Tool details forms: colors for mixed adapter transformed/ ; untransformed display: ; Hex values, 8 characters per color(SSBBGGRR where SS=System, ; BB=Blue, GG=Green, RR=Red) ;...
Page 204 Tool management 6.2 Settings in the configuration file ; in the magazine list and in the tool list. ; Example: ToolState_Lang_12345678=12345678_ToolState_Lang MagPlaceState_Lang_12345678=12345678_MagPlaceState_Lang ; use patm_*.ini ; The new magazine location status bits can be displayed in each ; list display. The parameters are set in the sections: "[1_MagList]", "[2_MagList]", "[3_MagList]"...
Page 205 Tool management 6.2 Settings in the configuration file ; the data or on scrolling through the list and the ; number of visible lines in the list is used to smaller than ; NumLinesPerReq. If data exchange between the HMI and NCK ;...
Page 206 Tool management 6.2 Settings in the configuration file ; lpaatdl0.bmp, lpapt.bmp, lpaptd0.bmp, lpaptdl0.bmp, lpaap.bmp. ; Further you can define a extra column for bitmap exclusive ; display, which will not contain any other data. ; Example: ; [3_ActList] ; ShowActToolCol = 1 ;...
Page 207 Tool management 6.2 Settings in the configuration file ; TOWSTD = G56-current-value G56ResetTOWSTDEqualCurrBitmap = pestd.bmp ; File name of bitmap used in lists to show: G56-reset-value = ; TOWMCS <> G56-current-value G56ResetTOWMCSUnequalCurrBitmap = pumcs.bmp ; File name of bitmap used in lists to show: G56-reset-value = ;...
Page 208 Tool management 6.2 Settings in the configuration file ; "[GeneralSettingsForMagAndToolList]", entry ; "MagPlaceState_Lang_12345678" or "second "TC_TP2"" 1_MagList=M1 2_MagList=M2 3_MagList=M3 1_ToolList=T1 2_ToolList=T2 3_ToolList=T3 1_ActList=A1 2_ActList=A2 3_ActList=A3 [FormTitles] ; List display titles for the untransformed display of ; data with locale-dependent and transformation-dependent ;...
Page 209 Tool management 6.2 Settings in the configuration file T1=TT1 T2=TT2 T3=TT3 A1=TA1 A2=TA2 A3=TA3 [SearchOfMagPlaces] ; Defines how the location search is to take place. ; Softkey text for 1st location search, locale-dependent 1_SoftkeyText=EL1 ; Half location; left, right, top, bottom 1_ToolSizeLRTB=1,1,1,1 ;...
Page 210 Tool management 6.2 Settings in the configuration file ; Min:=-9999, Max:=9999 ;Comment" ; "UserDataParamIO6= ; Type:=Int, Min:=-99, Max:=99" ; "UserDataParamIO7= ; Type:=Int, Min:=0, Max:=1" ; "5": Number of the OEM data ; "Type:=...": Defines the type of OEM data; ; Default: "Float" ;...
Page 211 Tool management 6.2 Settings in the configuration file ApplDataParamName3 = TC_TPCS3 ApplDataParamName4 = TC_TPCS4 ApplDataParamName5 = TC_TPCS5 ApplDataParamName6 = TC_TPCS6 ApplDataParamName7 = TC_TPCS7 ApplDataParamName8 = TC_TPCS8 ApplDataParamName9 = TC_TPCS9 ApplDataParamName10 = TC_TPCS10 ApplDataParamIO1 = <EndOfList> ; ApplDataParamIO1 = Type:=Float, Res:=2 ;...
Page 212 Tool management 6.2 Settings in the configuration file ; the sequence in paramtm.ini. ; For the values of EdgeParamName... we used the character string ; "TC_DP..." to indicate how the texts relate to the ; associated NCK variables. However, other ;...
Page 213 Tool management 6.2 Settings in the configuration file EdgeParamNameAng1 = TC_DP10 ; Angle2 EdgeParamNameAng2 = TC_DP11 UserDataParamName1 = TC_DPC1 UserDataParamName2 = TC_DPC2 UserDataParamName3 = TC_DPC3 UserDataParamName4 = TC_DPC4 UserDataParamName5 = TC_DPC5 UserDataParamName6 = TC_DPC6 UserDataParamName7 = TC_DPC7 UserDataParamName8 = TC_DPC8 UserDataParamName9 = TC_DPC9 UserDataParamName10 = TC_DPC10 UserDataParamIO1 = <EndOfList>...
Page 214 Tool management 6.2 Settings in the configuration file ; Transformed radius l1 TC_DP8 = TTC_DP8 ; Transformed radius l2 TC_DP9 = TTC_DP9 ; Transformed radius r1 TC_DP6 = TTC_DP6 ; Transformed radius r2 TC_DP7 = TTC_DP7 ; Transformed angle1 TC_DP10 = TTC_DP10 ;...
Page 215 Tool management 6.2 Settings in the configuration file UserDataParamName8 = TC_MOPC8 UserDataParamName9 = TC_MOPC9 UserDataParamName10 = TC_MOPC10 UserDataParamIO1 = <EndOfList> ; UserDataParamIO1 = Min:=-4, Max:=6 ; UserDataParamIO2 = Min:=-10, Max:=122 UserDataParamSize = TC_MOPC_UNIT UserDataParamSize1 = <EndOfList> ; UserDataParamSize1=TC_MOPC1_UNIT ; ... ;...
Page 216 Tool management 6.2 Settings in the configuration file ; ... ; UserDataParamSize10=TC_MAPC10_UNIT ApplDataParamName1 = TC_MAPCS1 ApplDataParamName2 = TC_MAPCS2 ApplDataParamName3 = TC_MAPCS3 ApplDataParamName4 = TC_MAPCS4 ApplDataParamName5 = TC_MAPCS5 ApplDataParamName6 = TC_MAPCS6 ApplDataParamName7 = TC_MAPCS7 ApplDataParamName8 = TC_MAPCS8 ApplDataParamName9 = TC_MAPCS9 ApplDataParamName10 = TC_MAPCS10 ApplDataParamIO1 = <EndOfList>...
Page 217 Tool management 6.2 Settings in the configuration file ApplDataParamName8 = TC_MPPCS8 ApplDataParamName9 = TC_MPPCS9 ApplDataParamName10 = TC_MPPCS10 ApplDataParamIO1 = <EndOfList> ; ApplDataParamIO1 = Min:=-42, Max:=62 ; ApplDataParamIO2 = Min:=-210, Max:=712 ApplDataParamSize = TC_MPPCS_UNIT ApplDataParamSize1 = <EndOfList> ; ApplDataParamSize1=TC_MPPCS1_UNIT ; ... ;...
Page 218 Tool management 6.2 Settings in the configuration file ; If "MultiLine=SINGLE" appears in a list definition section of a ; magazine or tool list, then the cutting edge number ; can be specified by adding "@Ee", where "e" is the ;...
Page 219 Tool management 6.2 Settings in the configuration file [1_MagList] MultiLine=SINGLE NrOfFixedColumns=1 1= ToolInPlace, 3, ToolInPlace 2= TC_MPP4_1, 1, TC_MPP4_1 3= TC_MPP4_2, 1, TC_MPP4_2 4= TC_MPP4_3, 1, TC_MPP4_3 5= TC_MPP4_4, 1, TC_MPP4_4 6= TC_MPP4_5, 1, TC_MPP4_5 7= TC_MPP4_6, 1, TC_MPP4_6 8= TC_MPP4_7, 1, TC_MPP4_7 9= TC_MPP4_8, 1, TC_MPP4_8 10= TC_TP2, 11, TC_TP2 11= TC_TP1, 5, TC_TP1...
Page 220 Tool management 6.2 Settings in the configuration file 12= TC_TP5, 1, TC_TP5 13= TC_TP6, 1, TC_TP6 14= TC_MPP2, 4, TC_MPP2 15= TC_ADPT1, 11, TC_ADAPT1 16= TC_ADPT2, 11, TC_ADAPT2 17= TC_ADPT3, 11, TC_ADAPT3 18= TC_ADPT4, 4, TC_ADAPT4 19= <EndOfList> [3_MagList] NrOfFixedColumns=1 1= ToolInPlace, 3, ToolInPlace 2= TC_TP2, 11, TC_TP2 3= TC_TP1, 5, TC_MPP6...
Page 221 Tool management 6.2 Settings in the configuration file 21= <EndOfList> [2_ToolList] MultiLine=MULTI NrOfFixedColumns=1 1= NO, 4, NO 2= MagNo, 4, MagNo 3= ToolInPlace, 3, ToolInPlace 4= TC_TP2, 11, TC_TP2 5= TC_TP1, 5, TC_TP1 6= TC_MPP6, 5, TC_MPP6 7= CuttEdgeNo, 1, CuttEdgeNo 8= TC_DP1, 4, TC_DP1 9= TC_DP3, 11, TC_DP3 10= TC_DP4, 11, TC_DP4...
Page 222 Tool management 6.2 Settings in the configuration file 1= NO, 4, NO 2= TC_TP2, 11, TC_TP2 3= TC_TP1, 5, TC_TP1 4= TC_MPP6, 5, TC_MPP6 5= CuttEdgeNo, 1, CuttEdgeNo 6= TC_DPCE, 6, TC_DPCE 7= MagNo, 4, MagNo 8= ToolInPlace, 3, ToolInPlace 9= TC_MPP2, 3, TC_MPP2 10= TC_MPP5, 4, TC_MPP5 11= TC_DP1, 11, TC_DP3...
Page 223 Tool management 6.2 Settings in the configuration file 16= TC_DP3, 11, TC_DP3 17= TC_DP4, 11, TC_DP4 18= <Empty> 19= <Empty> 20= TC_ADPT1, 11, TC_ADAPT1 21= TC_ADPT2, 11, TC_ADAPT2 22= TC_ADPT3, 11, TC_ADAPT3 23= TC_ADPT4, 4, TC_ADAPT4 24= <EndOfList> [3_ActList] NrOfFixedColumns=3 NumLinesPerReq = 11 1= NO, 4, NO 2= MagNo, 4, MagNo...
Page 224 Tool management 6.2 Settings in the configuration file ; message "missed trafo text" is ; displayed. TC_DP3 = TTC_DP3 e1TC_DP3 = Te1TC_DP3 e2TC_DP3 = Te2TC_DP3 e3TC_DP3 = Te3TC_DP3 TC_DP4 = TTC_DP4 TC_DP5 = TTC_DP5 TC_DP6 = TTC_DP6 TC_DP7 = TTC_DP7 TC_DP8 = TTC_DP8 TC_DP9 = TTC_DP9 TC_DP10 = TTC_DP10...
Page 225 Tool management 6.2 Settings in the configuration file TC_SCP25 = TTC_SCP25 TC_SCP33 = TTC_SCP33 TC_SCP34 = TTC_SCP34 TC_SCP35 = TTC_SCP35 e1TC_SCP13 = Te1TC_SCP13 e1TC_SCP14 = Te1TC_SCP14 e1TC_SCP15 = Te1TC_SCP15 e1TC_SCP23 = Te1TC_SCP23 e1TC_SCP24 = Te1TC_SCP24 e1TC_SCP25 = Te1TC_SCP25 e1TC_SCP33 = Te1TC_SCP33 e1TC_SCP34 = Te1TC_SCP34 e1TC_SCP35 = Te1TC_SCP35 e2TC_SCP13 = Te2TC_SCP13...
Page 226 Tool management 6.2 Settings in the configuration file TC_ECP34 = TTC_ECP34 TC_ECP35 = TTC_ECP35 e1TC_ECP13 = Te1TC_ECP13 e1TC_ECP14 = Te1TC_ECP14 e1TC_ECP15 = Te1TC_ECP15 e1TC_ECP23 = Te1TC_ECP23 e1TC_ECP24 = Te1TC_ECP24 e1TC_ECP25 = Te1TC_ECP25 e1TC_ECP33 = Te1TC_ECP33 e1TC_ECP34 = Te1TC_ECP34 e1TC_ECP35 = Te1TC_ECP35 e2TC_ECP13 = Te2TC_ECP13 e2TC_ECP14 = Te2TC_ECP14 e2TC_ECP15 = Te2TC_ECP15...
Page 227 Tool management 6.2 Settings in the configuration file ; 1. Date for which the condition applies ; 2. Condition ; 3. Comparison value ; The following data can be a filter criterion: ; Tool data: TC-TP1 Duplo number TC-TP2 Tool identifier TC-TP3 Tool size in half locations left TC-TP4 Tool size in half locations right TC-TP5 Tool size in half locations top...
Page 228 Tool management 6.2 Settings in the configuration file ; "TC_DPCS1" to "TC_DPCS10" ; The tool cutting edge user data must be activated on the NC ; and the numbers must be permissible on the NC. ; Cutting edge monitoring user data: ;...
Page 229 Tool management 6.2 Settings in the configuration file ; especially if it contains formatting information ; enclosed by " ". ; The user setting the parameters is responsible for the ; correct syntax. The syntax is not checked by the OPI. ;...
Page 230 Tool management 6.2 Settings in the configuration file ; Width of a typical character CharToGetColWidthPerCharacter= CharToGetColWidth Language-dependent, see ...\language\patm_xx.ini ; Selection of the tool status bits which are displayed in the ; result list: ; ResultToolStatusColumnsEnable= 1111100100110000 ; Bits 1 to 16, bit 1 is the least-significant bit in the tool status and ;...
Page 231 Tool management 6.2 Settings in the configuration file 2_FindResultHeadlineText = R2HL ; "Tools disabled" 2_FindCondition = TC_TP8 && 4 ; Disabled=bit 3 (2 to the power of (3-1)=4) 2_FindResultAddColumnBtss = <empty> 2_FindResultAddColumnText = <empty> ; or R2AddCol 2_FindResultAddColumnDisplayedNumberOfCharacters=0 2_FindLimitedToCurMagazine=False ; "True", "False" (default); restricted to current magazine ;...
Page 232 Tool management 6.2 Settings in the configuration file ; 0: Do not position, ; 1: Ask the operator whether to position, ; 2: Always position (default setting) 5_FindSoftkeyText = F5SK ; "Load identifier" 5_FindResultHeadlineText = R5HL ; "Load list for all tools with load identifier" 5_FindCondition = TC_TP8 &&...
Page 233 Tool management 6.2 Settings in the configuration file ; automatically to magazine list state Values "NoAuto<<" ; and "Auto<<". ; magazine "turret15" ($TC_MAP2) can be displayed by shortcut 3, ; you must use "<<" softkey explicitly to leave magazine select ;...
Page 234 Tool management 6.2 Settings in the configuration file Figure 6-14 Texts for the softkeys Displaying the displays Hidden fields can be made visible by scrolling with the cursor keys. The serial number defined by the input sequence during start-up is displayed in the location type box rather than the name of the location.
Page 235 Tool management 6.2 Settings in the configuration file Special characters Special characters such as ü, ä, ö, ß are entered in ANSI code in order for them to be displayed. Optional selection of magazines Up to now, the softkey "Next magazine" could only control the display of the individual magazine lists.
Page 236 Tool management 6.2 Settings in the configuration file Entries in the paramtm.ini file [GeneralSettingsForMagAndToolList] ;In magazine list forms change softkey "Next Mag" ; to softkey "Magazine Selection", to activate vertical softkeys ; in an additional state for magazine selection. ; This helps to prevent users from excessive use of ;...
Page 237 Tool management 6.2 Settings in the configuration file > language\patm_*.ini: [ShortcutSoftKeysForMagSelect] ; Softkey text of magazine selection shortcut softkeys. ; Syntax: magIdent=ShortcutSoftkeyText ; Explanation: "magIdent": magazine ident like in $TC_MAP2 or ; in magazine configuration in application ; maintenance tool management. ;...
Page 238 Tool management 6.2 Settings in the configuration file Settings in the INI files paramtm.ini / paramtm.txt: [GeneralSettingsForMagAndToolList] MagPlaceState_Lang_12345678=<Empty> ; use language-DLL MagPlaceState_Lang_12345678=12345678_MagPlaceState_Lang ; use patm_*.ini ; The new magazine location status bits can be displayed in each ; list display. The parameters are set in the sections: "[1_MagList]", "[2_MagList]", "[3_MagList]"...
Page 239 Tool management 6.2 Settings in the configuration file Coding of location status and tool status Location statuses Tool statuses G Disabled location G Disabled tool Free location Released tool Reserved for tool in buffer Active tool Reserved for tool to be loaded M Measured tool Left half location occupied Prewarning limit reached...
Page 240 Tool management 6.2 Settings in the configuration file User-defined bitmaps can be stored in the "user" directory. They are displayed instead of the standard bitmaps in the lists. Handling of lists The columns of the lists in which the bitmaps are to be entered can be set for each list view. The width of the bitmaps is set in characters for the entire highlighted areas.
Page 241 Tool management 6.2 Settings in the configuration file ; if the current cutting edge D=0. ProgToolZeroDBitmap = paptd0.bmp ; Name of the bitmap for the programmed tool /DNo./DL, ; if the current DL=0. ProgToolZeroDLBitmap = paptdl0.bmp ; File name of the bitmap for the current magazine location ActPlaceBitmap = paap.bmp [1_MagList] ;...
Page 242 Tool management 6.2 Settings in the configuration file SKTLLIST=2 The tool list can only be activated with the manufacturer password, i.e. it is blocked in normal operation. SLTOOLCAB=2 The tool catalog and cabinet SKTOOLCAT=2 can only be activated with the manufacturer password, i.e. they are blocked in normal operation.
Page 243 Tool management 6.2 Settings in the configuration file Note Access authorization If access rights have been assigned for functions and the protection level is "less" than that assigned, then the softkey is not displayed in the operator interface and the function cannot be called.
Page 244 Tool management 6.3 Language-dependence for user-defined name Language-dependence for user-defined name 6.3.1 Language-dependent name for magazines Function The magazine names are configured by the user in the Magazines screen via the tool management start-up tool (IW). This is why the assigned names are contained in the tool management database and after loading a magazine configuration also in the NCK but not in a language DLL.
Page 245 Tool management 6.3 Language-dependence for user-defined name Display magazine names in the HMI tool management screens The language-specific names of the magazines are displayed in all the tool management screens and the tool management start-up screens. If there are no entries are the corresponding INI files, the standard names from the NCK (in the tool management) or from the tool database (in the startup tool) are displayed.
Page 246 Tool management 6.3 Language-dependence for user-defined name The tool management startup tool does not evaluate the entry NameOfBufferPlaceFrom and always uses the name from the tool database and the language-specific INI files. Entries in the language-specific INI files Users must make the entries described here themselves. They are not written to the to the INI files by HMI Advanced.
Page 247 Tool management 6.3 Language-dependence for user-defined name You can achieve this by entering name texts in the language-specific tool management INI files for the loading locations configured in the database. There are two names for each loading location: ● the standard name which is used internally (tool database) ●...
Page 248 Tool management 6.3 Language-dependence for user-defined name Display loading locations in the HMI tool management screens The language-specific names of the loading locations are displayed in all the relevant tool management screens and tool management start-up screens. If there are no entries in the corresponding INI files, the standard name from the tool database is displayed.
Page 249 Tool management 6.3 Language-dependence for user-defined name The language-specific INI files are called patm_xx.ini and can be found under . ./hmi_adv/language. The user-defined patm_xx.ini files are found under ../user/language. File patm_xx.ini Section [Placetype_VISName] Entry Standard name="Language-specific text" Example [Placetype_VISName] Standard="Location type standard". SmallPlaceType="small"...
Page 250 Tool management 6.4 Job processing of tools Job processing of tools Prerequisite The settings for batch processing of tools are contained in paramtm.ini and language\patm_xx.ini in the section [BatchTools]. The filter only works if bit 4 is set in MD 18080: TOOL_MANAGEMENT_MASK. Up to 6 search filters can be defined.
Page 251 Tool management 6.4 Job processing of tools ● 00 00 FF 00: Green ● 00 FF 80 00: Blue green Examples for setting colors, see [BatchTools], "General settings which apply to all filters" in paramtm.txt. Bitmaps for the status display of the individual job elements The user can replace the names of the bitmaps or the bitmaps themselves with custom bitmaps.
Page 252 Tool management 6.4 Job processing of tools Tool status bits You can set which tool status bits are to be displayed in the results list. Language-specific letters can also be specified in bits for header and list lines. Example: Paramtm.ini, [BatchTools]: ResultToolStatusColumnsEnable= 1111100100110000 1: display, 0: do not display.
Page 253 Tool management 6.4 Job processing of tools SKBATLOAD=7; Softkey batch function "Load" SKBATLIST=7; Softkeys for controlling the job processing 6.4.2 Settings that are valid for one filter at a time Search criteria The search criteria are set in "n_FindCondition" (with n=1 to 6) for each filter. A maximum of 8 part conditions are permissible, separated by ",".
Page 254 Tool management 6.4 Job processing of tools A_TOOLMN: Magazine number A_TOOLMLN: Magazine location number P_TOOLND: Number of cutting edges Tool cutting edge parameters TC_DP1 to TC_DP24 Tool cutting edge monitoring parameters TC_MOP1: Tool life warning limit TC_MOP2: Tool life actual value TC_MOP3: Pre-warning limit for count TC_MOP4: Actual value for workpiece count TC_MOP5: Prewarning limit for wear...
Page 255 Tool management 6.4 Job processing of tools If this condition is applied to the tool status, you can locate tools with specific set (AND) tool status bits. If several set bits are queried at the same time, just one set bit is sufficient for the tool to appear in the hit list.
Page 256 Tool management 6.4 Job processing of tools Example 4: "/Tool/MagazineDescription/userData[u#TOA#,c#MAG,1](l)" Magazine OEM parameter 1 Placeholder The following placeholders are permissible: #TOA# TOA number (of the current channel) #TNO# Internal T number (of the tool found) #MAG# Magazine number (of the tool found) #RES# Standard value for the number of decimal places Placeholders are substituted by the data for the current tool or by general settings.
Page 257 Tool management 6.4 Job processing of tools Result list type You can select the result list type for each filter. determines which job functions are available for each softkey. There is one setting for each filter: n_ResultListType Result list type, value range: Standard list (default) for unload, delete, into the cabinet, reactivate Load list for loading, reactivate Example:...
Page 258 Parameter for PI TSEARCH Note Siemens reserves the right to withdraw support in future versions. The parameters for the PI TSEARCH used for filtering can be specified for each filter. This setting is very sensitive to errors. It does not support insertion of blanks; the number of places must be strictly adhered to;...
Page 259 Tool management 6.5 Grinding tools and tool-specific grinding data Grinding tools and tool-specific grinding data Overview The HMI Advanced tool management is modified so that the "tool-specific grinding data" of grinding tools is displayed and can be edited. This data is exchanged with the NC via the OPI block TG; it largely corresponds to the NC variables $TC_TPG1 to $TC_TPG9.
Page 260 Tool management 6.5 Grinding tools and tool-specific grinding data ;Maximum grinding wheel peripheral speed (as $TC_TPG7) TOOLGRINDmaxTipSpeed=0 ;Inclination angle of inclined wheel (as $TC_TPG8) TOOLGRINDinclAngle=0 ;Compensation parameter for grinding wheel peripheral speed (as $TC_TPG9) TOOLGRINDparamNrCCV=3 Note The HMI Advanced function "Change tool" used up to now is not modified. Therefore, with grinding tools too, when the tool type is changed, most tool data is set by the HMI to "0".
Page 261 Tool management 6.6 Inch/metric setting Inch/metric setting Overview The tool database (tool cabinet and tool catalog) and code carrier support machining in inch or mm measurements. The behavior with respect to length units is set for the tool database or the code carrier in the paramtm.ini file in the [TMMODES] section via the DATABASE_LENGTH_UNIT and CODECARRIER_LENGTH_UNIT entries.
Page 262 Tool management 6.6 Inch/metric setting DATABASE_LENGTH_UNIT=-1 ; If DATABASE_LENGTH_UNIT is assigned the setting 0 or 1, the ; following occurs: The first time a new tool management with ; inch/metric differentiation is started up, a new entry is added to ;...
Page 263 Tool management 6.6 Inch/metric setting 4. Switchover by changing the machine data 10240. $MN_SCALING_SYSTEM_IS_METRIC. Then call tool management and Power ON reset in the already selected tool management. This corresponds to point 3. 5. Switchover by changing the machine data 10240. $MN_SCALING_SYSTEM_IS_METRIC.
Page 264 From SW 6.3 code carrier systems can only be operated via SinTDC and no longer directly. WToolIdSys = SinTDC See also: /FBTC/ SINUMERIK Tool Data Communication SinTDC. In order for the code carrier system to be activated from the tool management, it must be entered in the file ...\user\mmc.ini.
Page 265 Tool management 6.7 Start-up of code carrier ; code-carrier format. ; The file resides in directory ...\add_on or ...\user. [TIS] ; Tool Identification System ; EOT for code-carrier data TIS_EOT=0x2F2F ; The end identifier for data on the code carrier has to be ;...
Page 266 Tool management 6.7 Start-up of code carrier ; $MN_CONVERT_SCALING_SYSTEM=1 is set in the NC. ; If it is an old NC without an inch/metric ; conversion function, or if ; $MN_CONVERT_SCALING_SYSTEM=0, then the NC operates without ; inch/metric conversion. For this reason, ;...
Page 267 Tool management 6.7 Start-up of code carrier ; 16=Warning limit reached ; 32=In change ; 64=Fixed place coding ; 128=Was used ; 256=Tool in buffer ; 512=Disabled, ignored (because of PLC) ; 1024=Out (unload) ; 2048=in (Load) ; 4096=Regular tool (permanent in NCK) ;...
Page 268 Tool management 6.7 Start-up of code carrier Tool dialog data The tool dialog data is defined as follows: Dialog Data type Designation Assignment $TC... variable String Tool name, max. 32 characters $TC_TP2 Integer Duplo number $TC_TP1 Integer Number of cutting edges $P_TOOLND[tnr] tnr=tool number Integer...
Page 269 Tool management 6.7 Start-up of code carrier Cutting edge dialog data The cutting edge dialog data is defined as follows: Dialog Data type Designation Assignment $TC... variable Integer Subtype $TC_DP1 Integer Length of cutting edge $TC_DP2 Geometry tool length compensation Double Length 1 $TC_DP3...
Page 270 Tool management 6.7 Start-up of code carrier Dialog Data type Designation Assignment $TC... variable Double Prewarning limit for wear $TC_MOP5 Double Wear $TC_MOP6 Double Setpoint wear $TC_MOP15 C38 * Double Downtime in minutes $TC_MOP2 C39 * Double Prewarning limit for tool life in minutes $TC_MOP1 C40 * Double...
Page 271 Tool management 6.7 Start-up of code carrier Note This format for the beginning of a comment is used only in the description file for code carriers. Otherwise, the beginning of a comment is introduced by a semicolon (;). Datalen DATALEN=CONST | VARIABLE 0x<delimiter> The following data have a constant (CONST) or a variable (VARIABLE) data length.
Page 272 Tool management 6.7 Start-up of code carrier BItem BItem<n>=<line> <n> := consecutive number of code carrier data within block<i>, in ascending order from 1 without gaps <line> := analog Item<n> Conversion rule for code carrier data <n> within a block. If the code carrier data is assigned a tool dialog data T<n>, the dialog data is assigned the first value of the code carrier data in the block.
Page 273 Tool management 6.7 Start-up of code carrier 6.7.3 Data conversion rule Code carrier data formats The following code-carrier data formats are supported: ● Data format: Explanation ● ASCII: ASCII character set ● INT: 16-bit integer (Intel format) Range of values: -32768 <= INT <= +32767 ●...
Page 274 Tool management 6.7 Start-up of code carrier index = index within tool/cutting edges dialog data - = no assignment to a dialog variable <dvar1>&<dvar2>=<uv> : Conversion rule applies to <dvar1> and <dvar2> uv := <arithm. Op1> [ <arithm. Op2> ] .. [ <arithm. OpN> ] arithm.
Page 275 Tool management 6.7 Start-up of code carrier Assignment of code carrier variable to a dialog variable according to the comparison result INVSIGN While reading: Sign for dialog variables. While writing: Invert sign for code carrier variables. Example: C1=(<0 INVSIGN) , C2=(>=0) ●...
Page 276 Tool management 6.7 Start-up of code carrier Code carrier Length Data format Dialog Comments variable (bytes) variable Bitem2 ' Cutting edge position ' Tool length compensation Bitem3 ' Length 1 Bltem4 ' Length 2 Bltem5 ' Length 3 'Tool radius compensation Bltem6 ' Length 1 Bltem7...
Page 277 Tool management 6.7 Start-up of code carrier 6.7.5 Example: Data string Structure of a data string conversion file: wkonvert.txt Code carrier Length in Format Dialog variable variable Bytes Item1 ASCII T1 Identifier, $TC_TP2 Item2 T2 Duplo, $TC_TP1 Item3 T4 = (Tet1), T5 = (Tet2), T6 = (Tet3), T7 = (Tet4) Tool size: left, right, top, bottom, $TC_TP3, 4, 5, 6 Item4 ASCII...
Page 278 Tool management 6.7 Start-up of code carrier String Value Entry Data types for dialog variables wkonvert.txt 1 BCD T3 T3 Integer Number of cutting edges, $P_TOOLND[tnr] tnr=tool number D00010E3 -10.300 4 BCD A1 A1 Double Tool OEM1, TC_TPC1 D0000005 4 BCD A2 A2 Double Tool OEM2, TC_TPC2 0205...
Page 279 List of the INI Files NOTICE This chapter provides an alphabetical listing of all INI files indicating the sections that can be changed by the machine manufacturer or end user. All other sections must not be changed! See also: ACTLOG.INI (Page 274) AEDITOR.INI (Page 275) DINO.INI (Page 277) DG.INI (Page 278)
Page 280 List of the INI Files A.1 ACTLOG.INI ACTLOG.INI Overview The settings from the screen "Action log settings" are combined and from this a configuration file ACTLOG.INI generated. Note We recommended that the action log is configured using the setting dialog boxes and not using this file.
Page 281 List of the INI Files A.2 AEDITOR.INI AEDITOR.INI Overview Information about the ASCII editor can be found in the AEDITOR.INI file. The data regarding the size of the files that can be edited is in the section [MEMORY]. [MEMORY] ; default factor for maximum size of file ;...
Page 282 List of the INI Files A.2 AEDITOR.INI ; default mode for checking of readonly blocks, 0: no check, ; else check for readonly ReadOnlyCheck=1 HiddenCheck=1 ; default text for identification of readonly blocks TextForReadOnlyCheck=;*RO* TextForHiddenCheck=;*HD* [MMC_Wizard] Aeditor=Aeditor.com A new line is inserted by pressing the <Return> key: NewLineInStepMode (Default) If HiddenCheck=TRUE, whereby certain lines are hidden, <Return>...
Page 283 List of the INI Files A.3 DINO.INI DINO.INI Access authorization The access authorizations for series commissioning are assigned in the file DINO-INI and additional settings are defined for the archive: [ACCESSLEVEL] USER=3 ; read authorization for series commissioning ; customer password (standard) PROGRAMMER=4 ;...
Page 284 List of the INI Files A.4 DG.INI DG.INI Overview In the operator area "Diagnostics", the access to individual softkeys can be individually set by entering the protection level. Enter the required protection level in the DG.INI file under [ACCESSLEVEL]: [ACCESSLEVEL] ALARMS=7 ;...
Page 285 List of the INI Files A.5 DGOVW.INI DGOVW.INI Overview This file is used for configuring additional customized signals in the "Diagnostics" → "Service Displays", "Service Overview" screen. Configured signals are added below the standard signals in this screen and can be viewed there (scrolling may be required). The file must be specifically created in one of the following directories: mmc2, addon, oem or user.
Page 286 List of the INI Files A.6 DH.INI DH.INI Overview The access authorizations for directories of the data management are defined in the file DH.INI. [ACCESSMASKS] \wks.dir\*.wpd\*.mpf = 75775 \mpf.dir\*.mpf = 75775 \cus.dir\*.spf = 33773 HMI Advanced (IM4) Commissioning Manual, 03/2009, 6FC5397-0DP10-3BA0...
Page 287 List of the INI Files A.7 DPDH.INI DPDH.INI Overview Access authorizations for processing/editing workpiece programs are configured in the file DPDH.INI. [ACCESSLEVEL] PROGRAMMER=4 OPERATOR=5 ENABLE_DIALPROG=0 SetStandardWpSave=2 ENABLE_SIMULATION=7 HMI Advanced (IM4) Commissioning Manual, 03/2009, 6FC5397-0DP10-3BA0...
Page 288 List of the INI Files A.8 DPSIM.INI DPSIM.INI Overview The run environment for the simulation is set in the file DPSIM.INI. [ACCESSLEVEL] ;minimum level for changing setup standard: SETUP=1 USER=3 OPERATOR=5 [MAIN] ;<>0: simulate program external modal (see also ; EXTERN_SIZE,EXTERN_CHECK) EXTERN_MODAL=0 ;...
Page 289 List of the INI Files A.9 HEADER.INI HEADER.INI Overview User-specific icons and texts are configured in the HEADER.INI file that are output in the global cross-channel status display (header). [CondStopIcons] DefaultIcon=CondWait.bmp ;0 = No wait state 1=CondStop.bmp ; No NC ready 2=CondStop.bmp ;...
Page 290 List of the INI Files A.9 HEADER.INI 33=CondWait.bmp ; Axis exchange active ; block change inhibited because axis exchange in progress 34=CondWait.bmp ; Axis container rotation 35=CondWait.bmp ; AXCT: Following axis active 36=CondWait.bmp ; AXCT: Leading axis active 37=CondWait.bmp ; AXCT: Follow up mode active 38=CondWait.bmp ;...
Page 291 List of the INI Files A.9 HEADER.INI 69=CondWait.bmp ; "Synchronism: Synchronous spindle" 70=CondWait.bmp ; "Synchronous spindle deactivation position" 71=CondWait.bmp ; "Waiting for enable of the transformer axis" 72=CondWait.bmp ; "Waiting because of possible collision" 73=CondWait.bmp ; "JOG: Position reached %2 %3 %4" 74=CondWait.bmp ;...
Page 292 List of the INI Files A.9 HEADER.INI [Pos15] ChanStatFeedStopSpindleStop = 1 ;channel status, channel 1 is displayed, superimposed Spindles=1 ;from feed inhibit channel 1 and spindle inhibit ;of Spindle 1 [UserIcons] ;UI_0 = <name.bmp> , <Position> ;name of the icon, position ;UI_31 = <name.bmp>...
Page 293 List of the INI Files A.10 HMIDESK.INI A.10 HMIDESK.INI Overview Settings are only necessary in this file if HMI-Advanced is installed on a PG/PC. [Global] ;Global configuration data ;definition of the desktop (minimum 2, maximum 4) NumberOfDesktops = 2 ;Control mode for using the mouse: Task bar ControlMode = Icon KeyboardControl = False [Desktop1]...
Page 294 List of the INI Files A.11 IB.INI A.11 IB.INI Overview Softkey access in the "Startup" operating area can be set by entering the protection level. ● Enter the required protection level in section [ACCESSLEVEL]. ● The operator languages are defined in Section [LANGUAGE]. Note In the [HELP_EXTENSION] section, the HelpFileExtension parameter must be set to 0 (WinHelp) if you want old, OEM-specific help files with the extension *.hlp to be...
Page 295 List of the INI Files A.11 IB.INI [LANGUAGE] ;Softkey "select language" instead of softkey "change language" ; in the main menu of area setup. ;False: Softkey "change language" to toggle between the foreground and background language. ;True: Softkey "select language" instead of softkey "change language" ;to select one of the installed languages.
Page 296 ; "a" = display all technologies ; Notation in the section e.g.: Technology=m [TEXTFILES] ; Siemens = Dh\Cst.dir\Ifs_gr.com ; SiemensI= Dh\Cst.dir\IfIT_gr.com turning ISO or ; SiemensI= Dh\Cst.dir\IfIM_gr.com milling ISO ; machinery construction OEM = Dh\Cst.dir\IfM_gr.com ; machinery construction OEM = Dh\Cst.dir\IfI_gr.com ;...
Page 297 Overview Entries in this file allow the use of hardkeys of the operator panel front OP 010 and OP 010C or SINUMERIK keyboards with hotkey block and PLC softkeys. Reference: Commissioning Manual "Supplementing the operator interface", Chapter "Configuring OP hotkeys and PLC keys".
Page 298 List of the INI Files A.14 LOGDRIVE.INI A.14 LOGDRIVE.INI Overview In the file LOGDRIVE.INI, logical drives are linked-in and the associated access authorizations assigned. Note The logical drives are set up via the HMI-Advanced operator interface under "Startup" → "HMI" → "Logic drives"; this enters them in the LOGDRIVE.INI file. [PCU] ;...
Page 299 List of the INI Files A.14 LOGDRIVE.INI ; example for usb device of tcu TCU1, port X203. for second port use X204 ; a partition number may be specified. if omitted, ; the default partition is 1 : the partition number has no effect on a usb device of the pcu ;...
Page 300 List of the INI Files A.14 LOGDRIVE.INI SK_Connection6=Labeling6 AccessMachine6=6 AccessProgram6=6 AccessServices6=6 Connection7=smb:\\<computer name>\<directory> SK_Connection7=Network drive Username7=Mustermann Password7=431S0Y2E3K530I28 AccessMachine7=6 AccessProgram7=6 AccessServices7=6 Connection8=\\<computer name>\tmp SK_Connection8=Drive%nlocal AccessMachine8=5 AccessProgram8=5 AccessServices8=5 User name: (only for NW Windows) Username<x> = The user name can be entered in the user interface, e.g. Mustermann. Password: (only for NW Windows) Password<x>...
Page 301 ; 4 = Key position 3 not yet used, same permissions as 5 ; 1 = manufacturer of machine only, System specialist ; 0 = manufacturer of Numeric Control only (Siemens experts) ; at the state of delivery all users got (nearly) all permissions for work JOG_PRESET=7 ;...
Page 302 List of the INI Files A.15 MACHINE.INI ==>6 Suggestion operator MDI_EDITOR=7 ; Edit program at MDI mode ==>5 Suggestion machine setter MDI_ED_DAT=7 ; Editor functions at MDI mode ==>5 Suggestion machine setter MDI_ED_CLR=7 ; Clear buffer at MDI mode ==>5 Suggestion machine setter MDI_V_ISTW=7 ;...
Page 303 List of the INI Files A.15 MACHINE.INI ; Due to performance issues the functionality offered with respect ; block correction, block view and block search depends on the ; Nc-version currently used. ; However, to get access to the whole functionality, regardless of the ;...
Page 304 List of the INI Files A.16 MBDDE.INI A.16 MBDDE.INI Overview The file MBDDE.INI is evaluated when booting. Settings are made to alarms and the actual log file in directory \mmc2. [Alarms] ; determines the order in which the alarms are inserted in the alarm list ;...
Page 305 List of the INI Files A.16 MBDDE.INI Alarm_S_FWA_Inactive=1 ; path and file names of the alarm text lists ; The filename fragments must not exceed 6 char., because it is extended ; automatically by the message module according to the selected language.
Page 306 Chapter "Setting the memory space for the alarm log". ; Criteria for selecting the alarm messages to be recorded. The notation ; is described in SINUMERIK 840D OEM package HMI User's Manual. Filter=Expression ; Characterizes the numbers of entries in the log file. If the actual ;...
Page 307 ; The file name fragments must not exceed 6 characters, because it ; extended automatically by the message module according to the ; selected language. A file name extension may also be added (optional). ; For additional information, see SINUMERIK 840D OEM package ; HMI User's Manual. [Helpcontext] File0=hlp\alarm_ .pdf For OEM users: ;...
Page 308 List of the INI Files A.16 MBDDE.INI DisableSenderOfMmcAlarm2=PLC DisableSenderOfMmcAlarm3= DisableSenderOfMmcAlarm4= DisableSenderOfMmcAlarm5= DisableSenderOfMmcAlarm6= DisableSenderOfMmcAlarm7= DisableSenderOfMmcAlarm8= HMI Advanced (IM4) Commissioning Manual, 03/2009, 6FC5397-0DP10-3BA0...
Page 309 Settings regarding the current system structure and the communication of the individual system components and the languages available at the HMI are configured in the file MMC- INI. [GLOBAL] ; connectiontype 0 = default setting: Connection SINUMERIK 810D/840D ; 1 = Connection to SINUMERIK 840Di connectiontype=0 NcddeServiceName=ncdde...
Page 310 ; WINCOS-->CP-->TCPIP-->CP-->LINCOS-->NC/PLC/DRIVE0-5 ; 1.) change TCPIP-Address below to your target TCPIP-Address ; 2.) do not forget to start your windows CP (e.g. cp_840di.exe) ; 3.) note: no disconnection detection in some cases ;[NCU840D] only SINUMERIK solution line ADDRESS0=192.168.214.1,LINE=10,NAME=/NC,SAP=040d,PROFILE=CLT1__CP_L4 _INT ADDRESS1=192.168.214.1,LINE=10,NAME=/PLC,SAP=0201,PROFILE=CLT1__CP_L 4_INT ADDRESS2=192.168.214.1,LINE=10,NAME=/CP,SAP=0501,PROFILE=CLT1__CP_L4...
Page 311 FloppyDisk= a: PCCard= Note If you want to adjust the font size for different display modes/languages, contact the Siemens hotline. OPI settings consist of the display machine data, which can also be set on a technology- specific basis via the operator interface of the HMI in the operating area "Startup" →...
Page 312 List of the INI Files A.17 MMC.INI $MM_MD_DRV_TEA_IDX_LIMIT = 0 $MM_MD_TEXT_SWITCH=0 $MM_ACTION_LOG_MODE = 0xFE $MM_PROGRAM_SETTINGS = 0 $MM_SW_OPTIONS = 0 $MM_HMI_TESTAUTOMAT_OPTION = 0 $MM_HMI_WIZARD_OPTION = 0 $MM_TRACE=0 The action log can also be set via the operator interface of the HMI in the operating area "Startup"...
Page 313 List of the INI Files A.17 MMC.INI WND_NAME=SIM_LOCAL_NCK STARTUP_TIMEOUT=50 ;WAIT_SYNC_MESSAGE= CLOSE_TIMEOUT=30 [WP_SELECT] ; for displaying a message that TOA/TMA-data on NCK will be overwritten ;TOA_WARNING_MESSAGE = yes/no TOA_WARNING_MESSAGE=yes [PCU] ; device name of PCU for USB local UsbFront=G: ' access rights of the PCU USB device (0-7) for the application machine, program and services AccessMachine=7 AccessProgram=7...
Page 314 List of the INI Files A.18 NETNAMES.INI A.18 NETNAMES.INI Overview In the m:n assignment in file NETNAMES.INI, you define which PCU operator components (HMI) can be connected with which NCU in the network (powerline) or which TCU can be switched to which PCU/NCU (solution line). The following details are specified: ●...
Page 315 List of the INI Files A.18 NETNAMES.INI ; Description of possible connections ; Connection part [conn PCU_1] conn_1 = NCU_1 conn_2 = NCU_2 conn_3= NCU_3 EXTCALL_conns=conn_1, conn_2, conn_3 ; Description of significant net parameters ; descriptive part, NCU components [param network] bus = opi ;...
Page 316 List of the INI Files A.18 NETNAMES.INI PlcSymbolFile= ... ; Channel data ;**************** [chan PCU_1] DEFAULT_logChanSet = Stat_1 DEFAULT_logChan = N1_K1 ShowChanMenu = True logChanSetList = Stat_1, Stat_2, Stat_3 ;**************************** [Stat_1] logChanList = N1_C1, N1_C2 [N1_K1] logNCName = NCU_1 ChanNum = 1 [N1_K2] logNCName = NCU_1 ChanNum = 2...
Page 317 List of the INI Files A.18 NETNAMES.INI [N3_K1] logNCName = NCU_3 ChanNum = 1 [N3_K2] logNCName = NCU_3 ChanNum = 2 ;End of file See also Configuration of a channel menu for direct channel selection (1:1 configuration) (Page 53) Configuring a double-channel display (Page 56) HMI Advanced (IM4) Commissioning Manual, 03/2009, 6FC5397-0DP10-3BA0...
Page 318 List of the INI Files A.19 OEMFRAME.INI A.19 OEMFRAME.INI Overview The starting behavior of OEM-applications is configured in the file OEMFRAME.INI. [SysMeter] ; let OEMFrame just look for Windows which have been ; created by the OEMApp ; default is 0 (means NO) ;fSearchOnlyForTaskWindow=1 ;...
Page 319 List of the INI Files A.20 PARAM.INI A.20 PARAM.INI Overview The tool compensation data that the user enters via the HMI operator interface are input into this file. [ACCESSLEVEL] READ_SYSVAR=7 EDIT_VIEW=7 ;Tool compensation user data ;Tool-specific parameters [ToolParams] UserDataParamName1=T_Param_1 UserDataParamName2=T_Param_2 UserDataParamName3=T_Param_3 UserDataParamName4=T_Param_4 UserDataParamName5=T_Param_5...
Page 320 List of the INI Files A.21 PARAMTM.INI A.21 PARAMTM.INI Overview All data that describe the operator interface of the tool manager are saved in the file ...\user\paramtm.ini. See also Structure of the paramtm.ini file (Page 187) HMI Advanced (IM4) Commissioning Manual, 03/2009, 6FC5397-0DP10-3BA0...
Page 321 List of the INI Files A.22 REGIE.INI A.22 REGIE.INI Overview Settings to start and end the HMI application and the associated sub-systems are made in the file REGIE.INI. [Miscellaneous] ; needed if regie is to support an 'EXIT' button ; set 'ExitButton' to True, and 'ExitButtonIndex' ;...
Page 322 OEM software in the range from 12 to 24 can be started in this section. The [StartupConfiguration] section is subdivided as follows: 0 to 12 is reserved for expanded functionality provided by Siemens 12 to 24 free for OEM applications...
Page 323 List of the INI Files A.23 SEDITOR.INI A.23 SEDITOR.INI Overview You can modify the displays in the multi-channel step sequence programming (option) by making the appropriate settings or specific supplements in this file. The sections that contain the code [ *User* ] allow the cycles of the machinery construction OEM and the user to be identified as "steps"...
Page 324 List of the INI Files A.23 SEDITOR.INI ;- You can use the ?-statement once per entry: ; L1? -> OK ; L1?? -> OK ; L23??? -> OK ; L2??3? -> NOT OK !!! ;************************************************************* [MISC] IconPath Relative path to the directory in which the icons are stored. The path is relative to ..\mmc2.
Page 325 List of the INI Files A.23 SEDITOR.INI Presently, only the following setting is available: 0: Cache is not active. 1: Cache is active. [DefaultIcons] These icons are displayed if icons are not specified in the individual definitions, e.g. if an icon is not included in SEFORM(…).
Page 326 ; If you don't project anything here, in all ; channels must stand the M4711 call ; respective if there are *C in [SyncMarks] ; only these channels will be synchronized. ;SIEMENS [SyncMarks_Siemens] sync1 = WAITM*(*n,*c,*c,*c,*c,*c,*c,*c,*c,*c,*c) sync1_Ico = clock.bmp sync1_Chans = ;USER...
Page 327 0: Main block CycleX_Ico Associated icon, it must be located in the directory that was specified in IconPath. [ProgSupport_User] Machine manufacturers can enter their expansions for their own cycles here. Example: ;Programming Support - Siemens Standard [ProgSupport_Siemens] NCG_1=CYC82 NCG_2=CYC86 NCG_3=CYC83 NCG_4=CYC84...
Page 328 List of the INI Files A.23 SEDITOR.INI NCG_6=CYC840_1 NCG_7=HOL1 NCG_8=HOL2 NCG_9=POS1 NCG_10=WPOS ;drilling [CYC82] ;drilling NCG_1_Label=NC1 NCG_1_Text=$80854 NCG_1_Ico=cm_poly_dr_drill.bmp NCG_1_Level=0 NCG_2_Label=NC2 NCG_2_Text=$80855 NCG_2_Ico=cm_poly_dr_drill.bmp NCG_2_Level=0 ;reaming NCG_3_Label=NC3 NCG_3_Text=$80853 NCG_3_Ico=cm_poly_dr_reaming.bmp NCG_3_Level=0 NCG_4_Label=NC4 NCG_4_Text=$80852 NCG_4_Ico=cm_poly_dr_reaming.bmp NCG_4_Level=0 … [CYC86] ;boring NCG_1_Label=NC1 NCG_1_Text=$80666 NCG_1_Ico=cm_poly_dr_bore.bmp NCG_1_Level=0 NCG_2_Label=NC2 NCG_2_Text=MCALL CYCLE86 NCG_2_Ico=cm_poly_dr_bore.bmp NCG_2_Level=0...
Page 329 List of the INI Files A.23 SEDITOR.INI NCG_2_Label=NC2 NCG_2_Text=MCALL CYCLE83 NCG_2_Ico=cm_poly_dr_deepdrill.bmp NCG_2_Level=0 Explanations: As an example, two graphically-supported cycles are shown here. The following lines appear in place of the cycle in the NC program: ;NCG#CYC82#\CST.DIR\bohren.com#NC1#2#*NCG;*RO*;*HD* ;#1#1#1#1#1###"M3"####1##1#*NCG;*RO*;*HD* CYCLE82(1,2,3,4,,0) ;#END#*NCG;*RO*;*HD* [ProgSupport_User] Here, the number of the following entries must be specified.
Page 330 List of the INI Files A.24 SIMTOGEO.INI A.24 SIMTOGEO.INI Overview Sample file with the details required for simulation for the individual tool types. Note If Link is set to 0 in the [Settings] section, the other entries in SIMTOGEO.INI are redundant. [SETTINGS] ;...
Page 331 ;TC_DPV3= ; 1=+X; -1=-X ;TC_DPV4= ; 1=+Y; -1=-Y ;TC_DPV5= ; 1=+Z; -1=-Z ; default tool data sets reserved by SIEMENS AG for later use ; default data sets are recognized by non digit values ; examples ;[500] ; number corresponding to tool type, roughing tool ;insert_length= ;...
Page 332 List of the INI Files A.24 SIMTOGEO.INI ;[510] ; number corresponding to tool type, finishing tool ;insert_length= ; TC_DP8, plate length ;holder_angle= ; TC_DP10, holder angle ;reference_direction= ; TC_DP11, cutting direction ;clearance_angle= ; TC_DP24, clearance angle HMI Advanced (IM4) Commissioning Manual, 03/2009, 6FC5397-0DP10-3BA0...
Page 333 List of the INI Files A.25 TASKCONF.INI A.25 TASKCONF.INI Overview Softkeys and softkey bars for user-specific operator areas are configured in the file TASKCONF.INI. [CONTROL] MDIList=MntMMC\MntMMC.mdi ControlFile=MntMMC\MntMMC.zus ScreenTwips=1 [DEBUG] ;MDISize 0 = Debug, 1 = Full screen MDISize=0 ;Buttons: 0 = button invisible, 1 = button visible Stop_Button=1 ;...
Page 334 List of the INI Files A.25 TASKCONF.INI ; must be supported by application ! HSK1TerminateTask= ; 0 : SwitchToChild (default) ; 1 : SwitchToTask -> switch only to task ; 2 : SwitchToTask2 -> switch to child of specified task ;(if it exists) HSK1IsTask= ;...
Page 335 List of Abbreviations Abbreviations Abbreviation Significance Output in the PLC ASCII American Standard Code for Information Interchange American coding standard for the exchange of information Mode group Operator Panel Interface Computer-Aided Design Computerized Numerical Control Computerized numerical control Carriage Return Digital-to-Analog Converter Data Block in the PLC Data Block Byte in the PLC...
Page 336 List of Abbreviations B.1 Abbreviations Abbreviation Significance Increment: Increment INItializing data Initializing data Interpolator International Standard Organization JOGging: Setup mode K1 .. C4 Channel 1 to channel 4 Light-Emitting Diode: Light-emitting diode Line Feed Servo gain factor Local User Data: Local user data Megabyte Machine Control Panel Machine control panel (→...
Page 337 List of Abbreviations B.1 Abbreviations Abbreviation Significance Software SYstem Files System files Testing Data Active: Identifier for machine data Tool Offset Tool offset Tool Offset Active: Identifier (file type) for tool offsets User frame Feed Drive Workpiece coordinate system Tool offset Tool change Zero Offset Active: Identifier (file type) for work offset data HMI Advanced (IM4)
Page 338 List of Abbreviations B.1 Abbreviations HMI Advanced (IM4) Commissioning Manual, 03/2009, 6FC5397-0DP10-3BA0...
Page 339 Index Control unit management (option), 50 Creating alarm texts, 85 Access authorizations Creating an operator menu, 29 Drives, 66 Cutting edge dialog data, 264 Access levels Cycles Basis WO softkey, 99 Match, 74 Changing default setting, 27 save in the DRAM, 104 Concept, 13 NC commands, 101 NC data, 99...
Page 340 Index Tools, 245 TSEARCH, 253 Filter User authorization, 247 Additional data, 250 alarms, 25 Conditions, 249 Criterion, 248 Header, 251 KEYS.INI, 293 restricted to one magazine, 252 Search criteria, 248 Flash File System (FFS), 104 Flying edge, 78 License key, 15 Loading locations, 174, 240 Location types, 177, 242 Hierarchy, 180...
Page 341 Index MM_NUM_MAX_FUNC_PARAM, 81 Multi-channel step sequence programming, 309, 319 MD 182420 Multiple file strategy, 24 MM_MAX_SIZE_OF_LUD_VALUE, 81 MD 18351 MM_DRAM_FILE_MEM_SIZE, 104 MD 20098 NC commands, 101 DISPLAY_AXIS, 103 NCDDE Trace, 158 MD 28082 NCU Connection Wizard, 134 SYSTEM_FRAME_MASK, 96 NCU link, 8 MD 30100 NETNAMES.INI, 47, 52, 310 CTRLOUT_SEGMENT_NR, 100...
Page 342 Index Rotating the coordinate system, 75 User views, 92 Scratching, 96 V.24 interface, 48 Screenshot, 140, (Siehe Bildschirmabzug) SEDITOR.INI, 319 Selecting the technology, 41 Series commissioning, 142 Wide Display, 39 Service axis, 149, 150 Work offset, fine, 98 Service displays, 149 Workpieces with job lists, 43 Set actual value, 96 SimNCK, 77...
Page 343 ______________ Scope of performance SINUMERIK 840Di sl/840D sl SINUMERIK 810D/840D SINUMERIK Expanding the user interface ______________ Programming ______________ Programming support SINUMERIK 840Di sl/840D sl SINUMERIK 810D/840D Configure hotkeys and ______________ PLC keys SINUMERIK Expanding the user interface ______________ "Custom" operating area...
Page 344 Trademarks All names identified by ® are registered trademarks of the Siemens AG. The remaining trademarks in this publication may be trademarks whose use by third parties for their own purposes could violate the rights of the owner.
Page 345 Table of contents Scope of performance ..........................1-1 Programming ............................2-1 Getting started..........................2-1 2.1.1 Fundamentals of Configuration....................2-1 2.1.2 Configuration and start files ....................... 2-2 2.1.3 Structure of configuration file ..................... 2-3 2.1.4 Troubleshooting (log book) ......................2-4 Structure and elements of a dialog .................... 2-6 2.2.1 Defining a dialog ........................
Page 346 Table of contents 2.4.7 Defining columns........................2-49 2.4.8 Focus control in the table grid ....................2-51 2.4.9 Example Defining columns....................... 2-52 2.4.10 Example Loading different table grids..................2-53 Softkey menus ......................... 2-55 2.5.1 Softkey description........................2-55 2.5.2 Define softkey menu ........................ 2-55 2.5.3 Changing softkey properties during runtime ................
Page 347 Table of contents Programming support ..........................3-1 What does programming support do? ..................3-1 Cycle support ..........................3-2 Activating a dialog from the NC program................... 3-4 3.3.1 Structure of "MMC" instruction....................3-5 3.3.2 Example of MMC instruction ...................... 3-7 3.3.3 Example 1: MMC instruction without acknowledgment .............
Page 348 Table of contents Storage structure of configuration files ..................6-8 6.3.1 HMI Embedded sl........................6-8 6.3.2 HMI Advanced..........................6-9 Search function on the HW platform common to both HMI systems ........6-10 6.4.1 Search function principle......................6-10 6.4.2 Search function for COMMON.COM..................6-13 6.4.3 Search function for images ......................
Page 349 The "Expand user interface" tools can be used to create user interfaces that display functional expansions designed by the machine manufacturer or end user, or simply to implement your own dialog layout. Preconfigured user interfaces supplied by Siemens or the machine manufacturer can be modified or replaced.
Page 350 The programming support functions described in the chapter of the same name and the user interfaces for Siemens cycles have been created with the system tools for Expand user interface. As a result, they can be modified as required by the machine manufacturer or end user within the scope described in this chapter.
Page 351 Programming Getting started 2.1.1 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 be set up by the user. An ASCII editor (e.g., Notepad or the HMI editor) is used to create configuration files.
Page 352 Programming 2.1 Getting started Start softkeys One or more softkeys (start softkeys), which are used to initiate your own operating sequences, are defined in one of the specified configuration files. The loading of a dedicated dialog is associated with a softkey definition or another softkey menu.
Page 353 Programming 2.1 Getting started Creating configuration file as ASCII file Dialogs can contain, for example, the following elements: ● Input/output fields (variables) with – Short text – Graphic text – Text for units ● Images ● Tables ● Softkey menus Search sequence for configuration files ●...
Page 354 Programming 2.1 Getting started Example //S (START) ; Definition of the start softkey (optional) ..//END //M (..) ; Definition of the dialog DEF ..; Definition of variables LOAD ; Description of the blocks END_LOAD UNLOAD END_UNLOAD ACTIVATE END_ACTIVATE //END //S (...) ;...
Page 355 Programming 2.1 Getting started //S(Start) HS6=("1st screen form") PRESS(HS6) LM("Screen form1") END_PRESS //END //M(Screen form1) DEF Var1=(R) //END Content of ERROR.COM If "Expand user interface" detects errors when interpreting the configuration files, these errors will be written to the ERROR.COM ASCII file. The file indicates: ●...
Page 356 Programming 2.2 Structure and elements of a dialog Structure and elements of a dialog 2.2.1 Defining a dialog Definition A dialog is part of a user interface consisting of a display line, dialog elements and/or graphics, an output line for messages and 8 horizontal and 8 vertical softkeys. Dialog elements are: ●...
Page 357 Programming 2.2 Structure and elements of a dialog Figure 2-2 Structure of the dialog Machine status display ("header") Header line of the dialog with header and long text Dialog Graphic Displaying messages Dialog element 8 vertical softkeys 8 horizontal softkeys Overview The definition of a dialog (definition block) is basically structured as follows: Definition block...
Page 358 Programming 2.2 Structure and elements of a dialog 2.2.2 Example Opening the Dialog Programming A new dialog is called via start softkey "Example" from the "Parameters" operating area. //S(Start) HS7=("Example", ac7, se1) PRESS(HS7) LM("Screen form1") END_PRESS //END //M(Screen form1/"Cycles") HS1=("") HS2=("") HS3=("") HS4=("")
Page 359 Programming 2.2 Structure and elements of a dialog Result Figure 2-3 Example Call "Cycles" dialog with the start softkey "Example" Expanding the user interface Commissioning Manual, 11/2006, 6FC5397-0DP10-0BA0...
Page 360 Programming 2.2 Structure and elements of a dialog 2.2.3 Dialog properties Description The properties of the dialog are defined in the start identifier line of the dialog. Figure 2-4 Dialog properties Machine status display ("header") Header line of the dialog with header and long text Dialog Graphic Programming...
Page 361 Programming 2.2 Structure and elements of a dialog Graphic position Position of the graphic in pixels (distance from left- hand side, distance from right-hand side), in relation to the upper left-hand corner of the dialog. The minimum distance from the top is 18 pixels. The entries are separated by a comma.
Page 362 Programming 2.2 Structure and elements of a dialog Example //S(Start) HS7=("Example", se1, ac7) PRESS(HS7) LM("Screen form1") END_PRESS //END //M(Screen form1/"Example 2 : Display graphics"/"MCP.BMP") HS1=("new%nheader") HS2=("") HS3=("") HS4=("") HS5=("") HS6=("") HS7=("") HS8=("") VS1=("") VS2=("") VS3=("") VS4=("") VS5=("") VS6=("") VS7=("") VS8=("") PRESS(HS1) Hd = "new header"...
Page 363 Programming 2.2 Structure and elements of a dialog Figure 2-5 "Example 2:Display graphics" See also Using display images/graphics (Page 2-17) Language-dependent text (Page 6-6) 2.2.4 Dialog elements Dialog element The term "dialog element" refers to the visible part of a variable, i.e., short text, graphics text, input/output field and unit text.
Page 364 Programming 2.2 Structure and elements of a dialog Figure 2-6 Elements of a dialog Main body of the dialog Short text Graphic text Input/output field Text for units Header line of the dialog with header and long text Dialog element Programming - Overview The single parameters to be separated by commas are enclosed in round parentheses: Identifier...
Page 365 Programming 2.2 Structure and elements of a dialog 2.2.5 Dialogs with multiple columns Overview Multiple variables can also be represented in a dialog on one line. In this case, the variables are all defined in the configuration file on a single definition line. DEF VAR11 = (S///"Var11"), VAR12 = (I///"Var12") To make individual variables in the configuration file more legible, the definition lines can be wrapped after every variables definition and following comma.
Page 366 Programming 2.2 Structure and elements of a dialog Figure 2-7 Appearance in HMI Embedded sl Below you can see how, despite being configured identically, the same screen appears differently under HMI Advanced. Figure 2-8 Appearance in HMI Advanced Expanding the user interface 2-16 Commissioning Manual, 11/2006, 6FC5397-0DP10-0BA0...
Page 367 Programming 2.2 Structure and elements of a dialog Setting for the same screen appearance In order for the appearance in HMI Advanced to tally with that in HMI Embedded sl, the font is changed to a fixed font in the configuration file WIZARD.INI: [FONT] FixedFont=1 The text will be displayed in the current language in fixed font format.
Page 368 Programming 2.2 Structure and elements of a dialog Storage locations HMI Embedded sl automatically finds the resolution of the connected monitor and searches for the desired display image first in the associated resolution directory. If it is not found there, HMI Embedded sl searches for the display image in the next smaller resolution directory until –...
Page 369 Programming 2.3 Variables "Display in display" You can insert further displays in the background (Help display), even as a function of the values of variables.Like for softkeys you can assign a graphics file to a display field. Examples: ● Short text field is overlaid with graphics: DEF VAR1=(S///,"\\image1.bmp"...
Page 370 Programming 2.3 Variables Variable status The "Variable status" property can be scanned during runtime to find out whether a variable has a valid value. This property can be read and written with the value FALSE = 0. Programming Syntax: Identifier.vld Description: Variable status vld (validation) Parameters:...
Page 371 Programming 2.3 Variables 2.3.2 Programming variables Programming The parameters of the variables are explained briefly in the following overview. A comprehensive description can be found in subsequent chapters. Parameter Description 1 Variable type The variable type must be specified. R[x]: REAL (+ digit for the decimal place) INTEGER S[x]:...
Page 372 Programming 2.3 Variables Parameter Description 5 Attributes The attributes influence the following properties: Input mode • Access level • Alignment of short text • Font size • Limits • Response when dialog is opened in terms of CHANGE block • The attributes are separated by commas and appear in any order.
Page 373 Programming 2.3 Variables Parameter Description cb0: The CHANGE block defined for this variable is processed when the dialog is opened (default setting). Multiple attributes are separated by commas. cb1: The CHANGE block defined for this variable is then only processed if the value of the variable changes. 6 Help display Help display file: Name of the PDF-file...
Page 374 Programming 2.3 Variables Parameter Description The data is separated by commas, the sequence is defined. The Help file and Help text appear in double quotation marks. The PDF files must be filed in folder CUS.DIR\hlp.dir or CST.DIR\hlp.dir. PDF and text files corresponding to one another must have the same name.
Page 375 Programming 2.3 Variables Valid INTEGER type specifications: Integer variable 32 bits in binary notation Integer variable 32 bits in binary notation Integer variable 16 bits in binary notation Integer variable 8 bits in binary notation Integer variable 32 bits in decimal notation signed Integer variable 32 bits in decimal notation signed Integer variable 16 bits in decimal notation signed Integer variable 8 bits in decimal notation signed...
Page 376 Programming 2.3 Variables The display mode of variables can be changed: ● For INTEGER, the display type can be changed. Binary Decimal signed hexadecimal unsigned With the addition of U for Unsigned ● For REAL data types, only the number of places after the decimal point can be changed. Changing the type is illegal and generates an error message in the ERROR.COM file.
Page 377 Programming 2.3 Variables 2.3.4 Detailed information about the toggle field [2] Description The toggle field extension function can be used to display texts (entries in toggle field) as a function of NC/PLC variables. A variable, which makes use of a toggle field extension, is read-only.
Page 378 Programming 2.3 Variables Toggle-field-dependent displays The toggle field is overlaid with alternating graphics: If the value of the flag byte is 1, "image1.bmp" will appear. If it is 2, "image2.bmp" will appear. DEF VAR1=(IDB/*1="\\image1.bmp", 2="\\image2.bmp"//,$85000/wr1//"MB[0]"//160,40,50,50) The size and position of the image is defined under "Position of input/output field (left, top, width, height)".
Page 379 Programming 2.3 Variables 2.3.6 Detailed information about the position of the short text [8] and position of the input/output field [9] Overview The short text and graphic text, as well as the input/output field and unit text, are each treated like a unit, i.e., position settings for short text apply to the graphic text and settings for the input/output field and to unit text.
Page 380 Programming 2.3 Variables Syntax: CLRHTX (Identifier) Description: Deletes the Help loop Parameters: Identifier Name of the variable whose Help loop is to be deleted Help file: Path specification of the file (PDF format) Index: Index in the Help text file to the Help text Help text: Help text for display in the Help text file Example...
Page 381 Programming 2.3 Variables Calculation with variables Variables are calculated every time you exit an input/output field (by pressing the ENTER or TOGGLE key). The calculation is configured in a CHANGE method that is processed every time the value changes. You can scan the variable status to ascertain the validity of the value of the variable, e.g., Var1 = Var5 + SIN(Var2) Otto = PI * Var4 Addressing system variables indirectly...
Page 382 Programming 2.3 Variables DEF Var1 = (R///,"Actual value",,"mm"//"Var1.bmp"////8,2) Colors: Foreground color: Background color: Help: none 2.3.10 Example 2: Assigning the Variable Type, Limits, Attributes, Short Text Position properties Example 2 Assigning the Variable Type, Limits, Attributes, Short Text Position properties DEF Var2 = (I/0,10///wr1,al1///,,300) Variable Type: INTEGER...
Page 383 Programming 2.3 Variables 2.3.11 Example 3: Assigning the Variable Type, Default, System or User Variable, Input/Output Field Position properties Example 3 Assigning the Variable Type, Default, System or User Variable, Input/Output Field Position properties DEF Var3 =(R//10////"$R[1]"//300,10,200//"Help.pdf",1,"Help1") Variable Type: String Limits or toggle field entries: none Default:...
Page 384 Programming 2.3 Variables Example 5 (HMI Advanced only) Several Help calls per dialog element: DEF Var5 = (R//////////"Help1.pdf",1,"Help1",,2,"Help2","Help3.pdf",3,) Variable Type: REAL Limits or toggle field entries: none Default: none Texts: none Attributes: none Help display: none System or user variable: none Position of short text: None...
Page 385 Programming 2.3 Variables DEF VAR6= (V///,"\\image1.bmp" ////160,40,50,50) Position of short text: image1.bmp Position of input/output field Distance from left: Distance from the top: Width: Height: Colors: No data, i.e., default Help: none 2.3.13 Use of strings Strings Strings can be used as part of the configuration. These allow text to be displayed dynamically or different texts to be chained for the purpose of code generation.
Page 386 Programming 2.3 Variables Editing strings: ● Chaining of strings: VAR12.VAL = VAR1 << " Error." ;Result: "This is an error" ● Deleting a variable: VAR10.VAL = "" ;Result: Blank string ● Setting a variable with a text variable: VAR11.VAL = VAR1.VAL ;Result: "This is an"...
Page 387 Programming 2.3 Variables 2.3.15 CURVER variable Description The CURVER (CURrent VERsion) property allows the programming to be adapted in order to handle different versions. The CURVER variable is read-only. Note Even if previously recompiled with an older version, the code is automatically generated with the most recent version.
Page 388 Programming 2.3 Variables 2.3.16 ENTRY variable Description The ENTRY variable can be used to check by what method a dialog has been called. Programming Syntax: ENTRY Description: The ENTRY variable is a read only variable. Return Value: The result of the scan can be: 0 = No programming support 1 = Programming support (the dialog was called by programming support)
Page 389 Programming 2.3 Variables 2.3.17 ERR variable Description Variable ERR can be used to check whether the preceding lines have been executed correctly. Programming Syntax: Description: The ERR variable is read-only. Return Value: The result of the scan can be: FALSE = previous line was executed error-free TRUE = previous line was not executed error-free Example VAR4 = Thread[VAR1,"CDM",3]...
Page 390 Programming 2.3 Variables 2.3.18 FILE_ERR variable Description Variable FILE_ERR can be used to check whether the preceding GC or CP command has been executed correctly. Programming Syntax: FILE_ERR Description: The FILE_ERR variable is read-only. Return Value: Possible results are: 0 = Operation okay 1 = Drive/path not available 2 = Path/file access error 3 = Drive not ready...
Page 391 Programming 2.3 Variables CP("D:\source.mpf","E:\target.mpf") VAR5 = "All OK" If no errors have occurred in CP (or GC), "All OK" is output ENDIF 2.3.19 FOC variable Description The FOC variable can be used to control the input focus (the current active input/output field) in a dialog.
Page 392 Programming 2.4 Complex dialog elements 2.3.20 S_CHAN variable Description The S_CHAN variable can be used to determine the number of the current channel for display or evaluation purposes. Complex dialog elements 2.4.1 Array Definition An array can be used to organize data of the same data type stored in the memory in such a way that it is possible to access the data via an index.
Page 393 Programming 2.4 Complex dialog elements Example //A(Thread) Size/lead/core diameter (0.3 / 0.075 / 0.202) (0.4 / 0.1 / 0.270) (0.5 / 0.125 / 0.338) (0.6 / 0.15 / 0.406) (0.8 / 0.2 / 0.540) (1.0 / 0.25 / 0.676) (1.2 / 0.25 / 0.676) (1.4 / 0.3 / 1.010)
Page 394 Programming 2.4 Complex dialog elements Access mode Direct Searches the line, column directly Searches the column, line directly Searches Searches line index Searches column index Compare mode Search concept must be located in the range of values of the line or column. Search concept must be located exactly.
Page 395 Programming 2.4 Complex dialog elements When compare mode C = 1 is used, the search concept must be found in the search line or search column. If the search concept cannot be found, the value 0 or an empty string is output and the error variable ERR is set to TRUE.
Page 396 Programming 2.4 Complex dialog elements Examples ● Access mode example 1: The search concept is in Z. This key is always sought in column 0. The value from column S is output with the line index of the concept found. VAR1 = Thread[0.5,1,1] ;VAR1 has the value 0.125 Explanation:...
Page 397 Programming 2.4 Complex dialog elements 2.4.4 Scanning the status of an array element Description The Status property can be used to run a scan to find out whether an array access operation is supplying a valid value. Programming Identifier [Z, S, [M[,C]]] Syntax: .vld Description:...
Page 398 Programming 2.4 Complex dialog elements Assignment A variables definition is assigned to the table-elements definition via a table identifier: ● The variables definition determines the values to be displayed and the table-elements definition determines the on-screen appearance and assignment. The table grid takes the properties of the input/output fields from the variables definition line.
Page 399 Programming 2.4 Complex dialog elements 2.4.6 Defining table grids Description The table block comprises: ● Header ● 1 to n column descriptions Programming (Table identifier/Table type/Number of lines/ Syntax: [Fixed line attribute],[Fixed column attribute]) Description: Defines table grids Parameters: Table identifiers The table identifier is used without a leading % sign.
Page 400 Programming 2.4 Complex dialog elements Programming (Type/Limits/Empty/Long text,column header/Attributes/Help display/ Syntax: System or user variable/Column width/Offset1, Offset2, Offset3) Description: Defines columns Parameters: Similar to variables Type Data type Limits Limit value MIN, limit value MAX Long text, column header Attributes Help display System or user The PLC or NC variables should be entered in...
Page 401 Programming 2.4 Complex dialog elements Column properties cannot be read in the LOAD block. The wr, ac and li attributes can be specified for column definitions. See also Dialog elements (Page 2-13) List of accessible system variables (Page A-7) 2.4.8 Focus control in the table grid Description The Row and Col properties can be used to set and calculate the focus within a table:...
Page 402 Programming 2.4 Complex dialog elements 2.4.9 Example Defining columns Overview The next three examples show the assignment between cells and PLC variables in a standard table (table type=0). Example 1: The first line shows the column headers: //G(MB_TAB/0/4/,1) (I///,"MB 1 to MB 3"///"MB1"/100/1) (I///,"MB 4 to MB 6"///"MB4"/100/1) Result: MB 1 to MB 3...
Page 403 Programming 2.4 Complex dialog elements //G(MB_TAB/0/4/,1) (IB///,"M1.1, M2.1, M3.1"/// "M1.1"/100/1) (IB///,"M1.1, M1.2, M1.3"/// "M1.1"/100/,1) Result: M1.1, M2.1, M3.1 M1.1, M1.2, M1.3 Value(M1.1) Value(M1.1) Value(M2.1) Value(M1.2) Value(M3.1) Value(M1.3) Other options: ● Ascending numbers can be entered in the first column: Example: (I///,"Line"///"0"/60/1) ●...
Page 404 Programming 2.4 Complex dialog elements VS7=("EXIT",ac7,se1) VS8=("") LOAD REG[0] = RNP ("$R[0]") IF (REG[0] == 0) LG ("grid1", "var1") ELSE LG ("grid2", "var1") ENDIF END_LOAD PRESS(VS7) EXIT END_PRESS //END ; (Name/Type/Lines...) //G(grid1/0/5/1,1) (R///"Long text1","R1 to ; 1. Column, header "R1 to R4", from R1 with R4"/wr2//"$R[1]"/80/1) Offset1 (R///"Long text2","R5 to...
Page 405 Programming 2.5 Softkey menus Softkey menus 2.5.1 Softkey description Overview The names of the soft keys are predefined. Not all softkeys need to be assigned. HSx x 1 - 8, horizontal softkeys 1 to 8 VSy y 1 - 8, vertical softkeys 1 to 8 The term softkey menu is used to refer to all the horizontal and vertical softkeys displayed on a screen form.
Page 406 The meanings of the different protection levels are as follows: ac0 is the highest protection level and ac7 the lowest. Security level Locked by range Password Siemens Password Machine manufacturer Password Service Password User Keylock switch position 3...
Page 407 Programming 2.5 Softkey menus Example //S(Menu1) Start identifier of softkey menu HS1=("NEW",ac6,se2) Define softkey HS1, assign the label "OK", security level 6 and the status "disabled" HS3=("\\bild1.bmp") Assign a graphic to the softkey HS5=("Exit") VS2=("Subscreen") VS3=($85011, ac7, se2) VS7=("Abort", ac1, se3) Define softkey HS1, assign the label "Cancel", security level 1 and the status "displayed".
Page 408 Programming 2.5 Softkey menus 2.5.3 Changing softkey properties during runtime Description The softkey properties Text, Access Level and Status can be changed in the methods during runtime. Programming Syntax: SK.st = "Text"" ;Softkey with label SK.ac = Access level ;Softkey with security level SK.se = Status ;...
Page 409 Programming 2.5 Softkey menus VS3=("") VS4=("") VS5=("") VS6=("") VS7=("") VS8=("OK", AC7, SE1) PRESS(VS8) EXIT END_PRESS //END Figure 2-9 Example 3: Graphics and softkeys Expanding the user interface 2-59 Commissioning Manual, 11/2006, 6FC5397-0DP10-0BA0...
Page 410 Programming 2.5 Softkey menus 2.5.4 Defining the start softkey Dialog-independent softkey Start softkeys are dialog-independent softkeys that, rather than being called from a dialog, have been configured before the first new dialog. In order to access the start screen or a start softkey menu, the start softkey must be defined.
Page 411 Programming 2.5 Softkey menus If the start softkey definition is designated as a comment (semicolon (;) at beginning of line) or the configuration file removed, the start softkey will not function. //S(Start) ; Start identifier HS6=("1st screen form") ; horizontal SK 6 labeled "1st screen form" PRESS(HS6) ;...
Page 412 Programming 2.6 Methods Methods Overview Various types of event (exit input field, actuate softkey) can initiate specific actions in dialogs and dialog-dependent softkey menus (softkey menus that are called from a newly configured dialog). These actions are configured in methods. The following table shows the basic principle used to program a method: Definition block Comment...
Page 413 Programming 2.6 Methods Example DEF VAR1=(S//////"DB20.DBB1") A system variable is assigned to Var1 CHANGE(VAR1) IF VAR1.Val <> 1 VAR1.st="Tool OK!" If the value of the system variable ≠ 1, the short text of the variable states: Tool OK! otto=1 ELSE VAR1.st="Attention: Error!"...
Page 414 Programming 2.6 Methods 2.6.2 FOCUS Description The FOCUS method is executed if the focus (cursor) is positioned on another field in the dialog. The FOCUS method must not be initiated as a result of a navigation event. The cursor may only be moved in softkey PRESS blocks, CHANGE blocks, etc.
Page 415 Programming 2.6 Methods Programming (Grid name, Variable name [,File name]) Syntax: Description: Loads a table Parameters: Grid name Name of the table (grid) in inverted commas Variable name Name of the variable to which the table is to be assigned, in inverted commas File name Name of the file in which the table (grid) is defined, in inverted commas.
Page 416 Programming 2.6 Methods 2.6.5 UNLOAD Description The UNLOAD method is executed before a dialog is unloaded. Programming Syntax: UNLOAD END_UNLOAD Description: Unload Parameters: - None - Example UNLOAD REG[1] = VAR1 Save variable in register END_UNLOAD 2.6.6 OUTPUT Description The OUTPUT method is executed if the "GC" function is called.Variables and Help variables are configured as an NC code in an OUTPUT method.
Page 417 Programming 2.6 Methods Programming (Identifier) Syntax: OUTPUT END_OUTPUT Description: Outputs variables in the NC program. Parameters: Identifier Name of OUTPUT method Block numbers and skip identifiers The OUTPUT block must not contain line numbers or skip identifiers if you wish to keep the line numbers and hide markings directly set with active program support in the parts program in case of recompilations.
Page 418 Programming 2.6 Methods Parameters: Softkey Name of softkey: HS1 - HS8 and VS1 - VS8 RECALL <RECALL> key Page Up Screen up Page Down Screen down Scroll left Cursor left Scroll right Cursor right Scroll up Cursor up Scroll down Cursor down Example HS1 = ("another softkey menu")
Page 419 Programming 2.6 Methods Example OUTPUT(NC1) Only the variables of the original version are made available in the OUTPUT block. OUTPUT(NC1,1) The variables of the original version and the expansions with version identifier 1 are made available in the OUTPUT block The OUTPUT block for the original version does not need a version identifier, however you can specify it with 0.
Page 420 Programming 2.7 Functions OUTPUT(NC1,1) Version 1 var100","var101"," var102 END_OUTPUT Functions Overview A variety of functions are available in dialogs and dialog-dependent softkey menus. These can be activated by specific events (exit input field, actuate softkey) and configured in methods. Subroutines Repeatedly used configuring instructions or others, which define the process for a particular operation can be configured in subprograms.
Page 421 Programming 2.7 Functions 2.7.1 Activate Program (AP) Description The AP (Activate Program) function transfers a file from the passive HMI file system to the active NC file system. The file is loaded into the NC and enabled and then deleted in the HMI file system.
Page 422 Programming 2.7 Functions 2.7.2 Define block (//B) Description In the program file, subprograms are identified by the block identifier //B and terminated with //END. Several subprograms can be defined under each block identifier. Note The variables used in the subprogram must be defined in the dialog in which the subprogram is called.
Page 423 Programming 2.7 Functions VAR1.val="Otto" END_SUB End of subprogram //END Block end 2.7.3 Subprogram call (CALL) Description The CALL function can be used to call a loaded subprogram from any point in a method. Subprogram nesting is supported, i.e., you can call a subprogram from another subprogram. Programming ("Identifier") Syntax:...
Page 424 Programming 2.7 Functions 2.7.4 Check Variable (CVAR) Description You can use the CVAR (CheckVariable) function to run a scan to ascertain whether all or only certain variables or Help variables in a screen form are error-free. It may be useful to check if variables contain a valid value before an NC code with the GC function.
Page 425 Programming 2.7 Functions 2.7.5 Copy Program (CP) Description The CP (Copy Program) function copies files within the HMI file system or NC file system. Note With HMI Embedded on NCU, copying is only possible within the NC file system. Programming ("Source file", "Target file") Syntax: Description:...
Page 426 Programming 2.7 Functions Example IF Var1 > Var2 DLGL("Value too large!") ; The text "Value too large!" appears in the dialog line if variable1 > variable2. ENDIF 2.7.7 Delete Program (DP) Description The DP (Delete Program) function deletes a file from the passive HMI or active NC file system.
Page 427 Programming 2.7 Functions 2.7.8 Evaluate (EVAL) Description The EVAL function evaluates a transferred expression and then executes it. With this function, expressions can be programmed during runtime. This can be useful, for example, for indexed access operations to variables. Programming (exp) Syntax: EVAL...
Page 428 Programming 2.7 Functions 2.7.9 Execute (EXE) Description The EXE function can be used on HMI Advanced to call a program created as an application with the HMI Advanced OEM package or to start the Free Contour Programming application. With HMI Embedded sl, EXE can only be used to start the Free Contour Programming application.
Page 429 Programming 2.7 Functions 2.7.10 Exist Program (EP) Description The EP (Exist Program) function checks whether a particular NC program is stored on the specified path in the NC or HMI file system. Programming ("File Syntax: ") Description: Checks the existence of the NC program Parameters: File Complete path to the file in the NC or HMI file system...
Page 430 Programming 2.7 Functions 2.7.11 Exit dialog (EXIT) Description The EXIT function is used to exit a dialog and return to the master dialog. If no master dialog is found, you will exit the newly configured user interfaces and return to the standard application.
Page 431 Programming 2.7 Functions Example //M(Screen form1) PRESS(HS1) LM("SCREEN FORM2","CFI.COM",1, POSX, POSY, DIAMETER) ; Interrupt screen form1 and open screen form2. Transfer variables POSX, POSY and DIAMETER in doing this. DLGL("Screen form2 ended") ; On returning from screen form2, the following text appears in the dialog line of screen form 1: Screen form2 ended.
Page 432 Programming 2.7 Functions Example PRESS(HS1) EXITLS( "Menu1", "AEDITOR.COM" ) END_PRESS 2.7.13 Generate code (GC) Description The GC (Generate Code) function generates NC code from the OUTPUT method. Programming Identifier"[,"Target file"][,Opt],[Append]) Syntax: GC(" Description: Generates an NC code Parameters: Identifier Name of OUTPUT block from which code is generated Target file Path name of target file for HMI or NC file system If the target file is not specified (only possible within...
Page 433 Programming 2.7 Functions Example //M(TestGC/"Code generation:") DEF VAR1 = (R//1) DEF VAR2 = (R//2) DEF D_NAME LOAD VAR1 = 123 VAR2 = -6 END_LOAD OUTPUT(CODE1) "Cycle123(" VAR1 "," VAR2 ")" "M30" END_OUTPUT PRESS(VS1) D_NAME = "MPF.DIR\MESSEN.MPF" GC("CODE1",D_NAME) ; Write code from OUTPUT method to file \MPF.DIR\MESSEN.MPF: Cycle123(123, -6) END_PRESS...
Page 434 Programming 2.7 Functions In the case of HMI Embedded sl, the target file specification is converted into NC notation and the file is created on the NCU. In the case of HMI Advanced or HMI Embedded WIN32, the file is created in the data management path.
Page 435 Programming 2.7 Functions 2.7.14 Load Array (LA) Description The LA (Load Array) function can be used to load an array from another file. Programming (Identifier [, File]) Syntax: Description: Loads array from file Parameters: Identifier Name of array to be loaded File File in which the array is defined Note...
Page 436 Programming 2.7 Functions Note Please note that a valid value must be assigned to a variable after the LA function has been used to assign another array to the toggle field of the variable. 2.7.15 Load Block (LB) Description The LB (Load Block) function can be used to load blocks containing subprograms during runtime.
Page 437 Programming 2.7 Functions 2.7.16 Load Mask (LM) description. The LM function can be used to load a new dialog. Master dialog/Sub-dialog A dialog, which calls another dialog, but is not ended itself, is referred to as a master dialog. A dialog that is called by a master dialog is referred to as a sub-dialog. Programming ("Identifier"[,"File"] [,MSx [, VARx] ] ) Syntax:...
Page 438 Programming 2.7 Functions Note Parameter VARx transfers only the value of the variable in each case, i.e., variables can be read and written in the sub-dialog, but are not visible in it. Variables can be returned from the sub-dialog to the master dialog by means of the EXIT function. Example PRESS(HS1) LM("SCREEN FORM2","CFI.COM",1, POSX, POSY, DIAMETER)
Page 439 Programming 2.7 Functions Example PRESS(HS4) LS("Menu2",,0) ; Menu2 overwrites the existing menu. All existing softkeys are deleted END_PRESS Notice As long as the interpreter has not displayed a dialog, i.e., no LM function has yet been processed, only one LS or one LM command, but no other action, can be configured in the PRESS method of the definition block for the start softkey and the softkey menu.
Page 440 Programming 2.7 Functions 2.7.19 Read NC/PLC (RNP), Write NC/PLC (WNP) Description The RNP (Read NC PLC) command can be used to read NC or PLC variables or machine data. Programming System or user variable", value Syntax: RNP (" Description: Reads NC or PLC variable or machine data Parameters: System or user Name of NC or PLC variable...
Page 441 Programming 2.7 Functions Example WNP("DB20.DBB1",1) Write PLC variable 2.7.20 Multiple Read NC PLC (MRNP) Description This MRNP command can be used to transfer several system or OPI variables in a single register access. This access method is significantly faster than reading via individual access attempts.
Page 442 Programming 2.7 Functions Example MRNP("$R[0]*$R[1]*$R[2]*$R[3]",1) The values of variables $R[0] to $R[3] are written to REG[1] to REG[4]. Reading display machine data: Display machine data can be read with RNP ($MM...) within the LOAD block. General read/write access to display machine data is not possible using the "Expand user interface"...
Page 443 Programming 2.7 Functions PLC data Byte y of data block x DBx.DBBy Word y of data block x DBx.DBWy Double word y v. of data block x DBx.DBDy Real y of data block x DBx.DBRy Flag byte x bit y Mx.y Flag byte x Flag word x...
Page 444 Parameters: Register index with x = 0...19; Type: REAL or STRING = VARIANT Registers with x ≥ 20 have already been assigned by Siemens. Description of register value The assignment of values to registers is configured in a method. Note...
Page 445 Programming 2.7 Functions Example UNLOAD REG[0] = VAR1 Assign value of variable 1 to register 0 END_UNLOAD UNLOAD REG[9].VAL = 84 Assign value 84 to register 9 END_UNLOAD These registers can then be assigned to local variables again in a method in the next dialog.
Page 446 Programming 2.7 Functions 2.7.23 RETURN Description The RETURN function can be used to prematurely terminate execution of the current subprogram and to return to the branch point of the last CALL command. If no RETURN command is configured in the subprogram, the subprogram will run to the end before returning to the branch point.
Page 447 Programming 2.7 Functions Programming Variables from the NC code are transferred to the dialog. At the same time, the variable values from the NC code are compared with the calculated variable values from the configuration file. If the values do not coincide, an error message is written to the log book because values have been changed during NC code generation.
Page 448 Programming 2.7 Functions 2.7.25 Search Forward, Search Backward (SF, SB) Description The SF, SB (Search Forward, Search Backward) function is used to search for a string from the current cursor position in the NC program currently selected in the Editor and to output its value.
Page 449 Programming 2.7 Functions 2.7.26 Select Program (SP) Description The SP (Select Program) function selects a file in the active NC file system for execution, i.e., the file must be loaded into the NC beforehand. Programming ("File") Syntax: Identifiers: Select Program Parameters: "File"...
Page 450 Programming 2.7 Functions 2.7.27 STRING functions Overview The following functions enable strings to be processed: ● Determine length of string ● Find a character in a string ● Extract substring from left ● Extract substring from right ● Extract substring from mid-string ●...
Page 451 Programming 2.7 Functions String2 Chain of characters in which the search is being made Direction (optional) Direction in which the search is being made 0: From left to right (default setting) 1: From right to left 0 is returned if string1 does not occur in string2. Example DEF VAR01 DEF VAR02...
Page 452 Programming 2.7 Functions RIGHT function: String from right (string, length) Syntax: RIGHT Description: RIGHT returns a string containing the specified number of characters starting from the right-hand side of a string. Parameters: string Character string or variable with the string to be processed length Number of characters that are to be read out...
Page 453 Programming 2.7 Functions REPLACE Function: Replacing characters ( string, FindString, ReplaceString [, start [, count ] ] ) Syntax: REPLACE Description: The REPLACE function replaces a character/string in a string with another character/string. Parameters: string String in which FindString is to be replaced with ReplaceString.
Page 454 Programming 2.7 Functions Example PRESS (HS2) PI_SERVICE("_N_CREATO",55) END_PRESS PRESS(VS4) PI_SERVICE("_N_CRCEDN",17,3) END_PRESS Starting OEM services The PI_START command executes a PI service based on OEM documentation. Programming Transfer string" Syntax: PI_START(" Description: Executes PI service Parameters: "Transfer string" Unlike the OEM documentation, the transfer string should be entered in inverted commas.
Page 455 Programming 2.7 Functions 2.7.29 External functions (only HMI Advanced) Description Additional user-specific functions can be used by means of this call. External functions are stored in a DLL file and identified by an entry in the definition lines of the configuration file. Note An external function must have at least one return parameter.
Page 456 Programming 2.7 Functions //M(SCREEN FORM1) REG[2]) The value of the "InitConnection" external function is assigned to RET along with the call parameters VAR1+SIN(VAR3), 13, Servus, VAR2 and REG[2]. END_LOAD Extract from DLL file void __export WINAPI InitConnection(ExtFctStructPtr FctRet, ExtFctStructPtr FctPar, char cNrFctPar) FctRet->value.i Return value of function FctPar[0]->value.r...
Page 457 Programming 2.7 Functions 2.7.30 Programming example Programming //S(Start) HS7=("Example", se1, ac7) PRESS(HS7) LM("Screen form4") END_PRESS //END //M(Screen form4/"Example 4: Machine control panel"/"MST.BMP") DEF byte=(I/0/0/"Input byte, default=0","Byte no.:",""/wr1,li1///380,40,100/480,40,50) DEF feed=(IBB//0/"","Feed override.",""/wr1//"EB3"/20,180,100/130,180,100), Axistop=(B//0/"","Feed stop",""/wr1//"E2.2"/280,180,100/380,180,50/0,11) DEF spin=(IBB//0/"","Spindle override",""/wr1//"EB0"/20,210,100/130,210,100), spinstop=(B//0/"","Spindle stop",""/wr1//"E2.4"/280,210,100/380,210,50/0,11) DEF custom1=(IBB//0/"","User key 1",""/wr1//"EB6"/20,240,100/130,240,100) DEF custom2=(IBB//0/"","User name 2",""/wr1//"EB7"/20,270,100/130,270,100)
Page 458 Programming 2.7 Functions VS7=("") VS8=("OK", SE1, AC7) LOAD By1=1 By2=2 By3=3 By6=6 By7=7 END_LOAD PRESS(HS1) Byte.wr=2 END_PRESS CHANGE(Byte) By1=byte+1 By2=byte+2 By3=byte+3 By6=byte+6 By7=byte+7 Feed.VAR="EB"<<By3 Spin.VAR="EB"<<Byte Custom1.VAR="EB"<<By6 Custom2.VAR="EB"<<By7 Axisstop.VAR="E"<<By2<<".2" Spinstop.VAR="E"<<By2<<".4" Byte.wr=1 END_CHANGE CHANGE(Axis stop) IF Axistop==0 Axistop.BC=9 ELSE Axistop.BC=11 ENDIF END_CHANGE CHANGE(Spin stop) IF Spinstop==0 Spinstop.BC=9...
Page 459 Programming 2.7 Functions END_CHANGE PRESS(VS8) EXIT END_PRESS Result Figure 2-10 Machine control panel Note You will find further examples in the supplied tool box. Expanding the user interface 2-109 Commissioning Manual, 11/2006, 6FC5397-0DP10-0BA0...
Page 460 Programming 2.8 Operators Operators Overview The following operators can be used when programming: ● Mathematical operators ● Relational operators ● Logic (Boolean) operators ● Bit operators ● Trigonometric functions 2.8.1 Mathematical operators Overview Mathematical operators Identifier Addition Subtraction Multiplication Division Modulo operation Parentheses AND operator...
Page 461 Programming 2.8 Operators VAR1 contains the number to be rounded. The parameter “4” indicates the number of decimal places in the result, which is placed in VAR2. Trigonometric functions Trigonometric functions Identifier SIN(x) Sine of x COS(x) Cosine of x TAN(x) Tangent of x ATAN(x, y)
Page 462 Programming 2.8 Operators Example IF VAR1.VAL == 1 VAR2.VAL = TRUE ENDIF Conditions The nesting depth is unlimited. Condition with a command: ENDIF Condition with two commands: ELSE ENDIF 2.8.2 Bit operators Overview Bit operators Identifier Bit-serial OR BXOR Bit-serial XOR BAND Bit-serial AND BNOT...
Page 463 Programming 2.8 Operators Example PRESS(VS1) VAR01 = 16 SHL 2 ; Result = 64 VAR02 = VAR02 SHL VAR04 ; Convert content of VAR02 to 32-bit unsigned , and shift content to left by number of bits specified in VAR04. Then convert 32-bit value back to format of variable VAR02.
Page 464 Programming 2.8 Operators Expanding the user interface 2-114 Commissioning Manual, 11/2006, 6FC5397-0DP10-0BA0...
Page 465 Programming support What does programming support do? Overview The purpose of the programming support system is to assist programmers in writing an NC program using the ASCII Editor. Customized user interfaces can also be created in the Programming support system. These interfaces are configured using the ASCII Editor and the tools provided by the "Expanding the Operator Interface"...
Page 466 ;# can be provided by configuring INI files. For Siemens cycles, the required configuration files are included in the scope of supply. This means that after recompilation it will be possible to work with the following cycle calls using the dialog support: ●...
Page 467 Programming support 3.2 Cycle support For dialogs generated with the "Expand user interface" function for the purpose of supporting user cycles, the information in the dialog descriptive files can be used for this process. Cycle-specific settings can be made in the configuration to define whether cycles with ;# lines are to be processed in the parts program or recompiled via the configuration files.
Page 468 The "command channel" is activated by default for channels 1 and 2. ● More than 2 channels: For HMI Advanced, the "command channel" must be activated (if the Siemens measuring cycles have not yet been installed). This requires a modification to be made to the file F:\MMC2\ COMIC.NSK in the "Startup"...
Page 469 Programming support 3.3 Activating a dialog from the NC program Select file F:\MMC2\COMIC.NSK in the "Startup" operating area using the softkeys "HMI" → "Editor" and attach the following text (after channels 1 and 2): REM CHANNEL TOPIC(machineswitch) COMIC_START(COMIC001MachineSwitch"...) [compare the text for channels 1 and 2] When the control is restarted (OFF/ON), the command channel is activated for the corresponding channel.
Page 470 Programming support 3.3 Activating a dialog from the NC program GUD file User-data definition file accessed on reading/writing of variables. Graphics file File name of the BMP graphic to be inserted (HMI Advanced only) Acknowledgment Acknowledgment in acknowledgment mode "A" variable (HMI variable Advanced only)
Page 471 Programming support 3.3 Activating a dialog from the NC program 3.3.2 Example of MMC instruction MMC instruction in the parts program MMC("CYCLES,PICTURE_ON,T_SK.COM,PICTURE1,MGUD.DEF,PICTURE3.BMP, TEST_1,A1","S") CYCLES Operating area PICTURE_ON Select dialog T_SK.COM File name in cycle directory PICTURE1 Name of the dialog MGUD.DEF User data definition file PICTURE3.BMP...
Page 472 Programming support 3.3 Activating a dialog from the NC program Text variable [Text variables] A1 = Example 2: MMC instruction without acknowledgment Reference parameters for MMC instruction Example 2: MMC statement without Screen header or comment text acknowledgment Note For variable names, text variables and cycle names, capital letters must be used. Configuring softkeys for dialog call Softkey assignment for MMC command with asynchronous acknowledgment mode.
Page 473 Programming support 3.3 Activating a dialog from the NC program 3.3.3 Example 1: MMC instruction without acknowledgment Selecting N10 MMC("CYCLES,PICTURE_ON,T_SK.COM,PICTURE1,GUD4.DEF,,,A1","N") N20 TEST_1 = 1 N25 G4 F10 N30 MMC("CYCLES,PICTURE_OFF","N") Parameters: //C1(PICTURE1) Dialog file (*.COM) (R///USER VAR TEST_1/W/TEST_1///) Text variable [TEXT VARIABLES] A1 =..Example 1: MMC command without acknowledgment Figure 3-2...
Page 474 Programming support 3.3 Activating a dialog from the NC program 3.3.4 Example 2: Hold time and optional text variables Selecting MMC("CYCLES,PICTURE_ON,T_SK.COM,PICTURE6,GUD4.DEF,,10,T1,G1","N") N15 G4 F15 N30 MMC("CYCLES,PICTURE_OFF","N") Parameters: //C6(screen6) Dialog file (*.COM) (R///USER VAR TEST_1,%1/W/TEST_1///) Text variable [TEXT VARIABLES] T1 = Example 2: Dwell time and optional text variables ...
Page 475 Programming support 3.3 Activating a dialog from the NC program "G1=optional text variable". By calling the text variables contained in the MMC command (9th to 23rd parameters), messages or names can be "composed" in this way. 3.3.5 Example 3: MMC instruction with synchronous acknowledgment mode Selecting N15 MMC("CYCLES,PICTURE_ON,T_SK.COM,PICTURE1,GUD4.DEF,,,F1","S") N18 STOPRE...
Page 476 Programming support 3.3 Activating a dialog from the NC program 3.3.6 Example 4: Positioning of input/output field Description By specifying position parameters in the COM file, you can insert the comment field, or input and output field, at any point in the display area. Selecting N15 MMC("CYCLES,PICTURE_ON, T_SK.COM;...
Page 477 Programming support 3.3 Activating a dialog from the NC program Sequence of operations It is possible to graphically configure 16 comment and 16 input or output fields. Where there are more than 16 fields, they can be controlled via a scroll bar. Figure 3-5 Example 4a Position parameters To ensure that the cursor control works seamlessly, the configured fields must overlap:...
Page 478 Programming support 3.3 Activating a dialog from the NC program 3.3.7 Example 5: Displaying graphics in the dialog screen Description Graphics created with Paintbrush, for example, can be displayed in the dialog by means of a graphics file specification. A comment text for the graphic can also be preassigned using the COM file. You can position this comment text by specifying position parameters.
Page 479 Programming support 3.3 Activating a dialog from the NC program 3.3.8 Example 6: Displaying OPI variables Description You can display OPI variables. Selecting MMC("CYCLES,PICTURE_ON,T_SK.COM,SCREEN7,GUD4.DEF,,TEST_1,J1","S") Parameters: //C7(Screen7) Dialog file (*.COM) (R///Test_1/R/Test_1) (I///); (Interpreted as space line)) (R///Actual value from axis 1/R/$actual value) (R//1/R parameter 12/W/$R[12]) Text variable J1 = ...Example7: OPI variables...
Page 480 Programming support 3.3 Activating a dialog from the NC program 3.3.9 Example 7: Asynchronous acknowledgment mode with softkeys Description Softkeys can be preprogrammed in the COM file for display in asynchronous mode, linked with the acknowledgment variable and evaluated in the parts program. Selecting N10 QUIT_1 = "START"...
Page 481 Programming support 3.3 Activating a dialog from the NC program IF Match (Quit_1,"SK1") >= 0 GotoF Label1 ;searches for a string within the string. If no softkey has been pressed, the loop is executed again. Figure 3-9 Example 7: Asynchronous acknowledgment mode Sequence of operations The screen called via the asynchronous MMC command continues to be displayed until one of the two configured softkeys is actuated:...
Page 482 Programming support 3.3 Activating a dialog from the NC program Expanding the user interface 3-18 Commissioning Manual, 11/2006, 6FC5397-0DP10-0BA0...
Page 483 Overview This chapter describes the configuration of the following control elements: ● 6 hotkeys on OP 010, OP 010C and SINUMERIK keyboards with hotkey block, as well as the <MACHINE> and <MENU SELECT> keys, whose assignment can be changed. ● Keys evaluated by the PLC, e.g., keys on the machine control panel ●...
Page 484 Configure hotkeys and PLC keys 4.1 Introduction ● Selection of additional screens, depending on the current operating situation, in screens created using the "Expanding the Operator Interface" system. Configuration Configuration is carried out using the "Expand user interface" functions. ● The 6 OP hotkeys can be used to display any HMI operating area directly. This shortens the usual selection process via the main menu.
Page 485 ● mmc2 *) ● hmi_adv *) *) These directories are reserved for Siemens. The files are executed in the above sequence. Entries in the directory, which appears at the beginning of the sequence will disable existing entries in directories, which appear later in the sequence.
Page 486 Configure hotkeys and PLC keys 4.2 Configuration On delivery, the assignments for HK1 to HK6 are stored in KEYS.INI in the mmc2 directory for the standard system: Function Position Machine operating area, last screen Program Program operating area, last screen Offset Parameters operating area, last screen Prg.
Page 487 Configure hotkeys and PLC keys 4.2 Configuration Figure 4-2 Configuration overview Expanding the user interface Commissioning Manual, 11/2006, 6FC5397-0DP10-0BA0...
Page 488 Configure hotkeys and PLC keys 4.2 Configuration 4.2.2 Configuration in the KEYS.INI file Overview Every instance of the KEYS.INI configuration file in the above directories drives the the hotkey responses in a section [KeyConfiguration]. Every entry (line) defines the response of the system to a specific actuation (in the sense of multiple actuation of specific hotkeys).
Page 489 Note Multiple keypress is possible for HK1 - HK8 and for keys HK9 - HK49, which are reserved for Siemens. Example of multiple hotkey keypress The first time the hotkey is pressed, the associated area is activated and a state/action may be initiated in this area (entry 1).
Page 490 Configure hotkeys and PLC keys 4.2 Configuration Assignment of the softkeys to the action values Horizontal softkeys (SKHi) Action SKH1 SKH2 SKH3 SKH4 SKH5 SKH6 SKH7 SKH8 Vertical softkeys (SKVi) Action SKV1 SKV2 SKV3 SKV4 SKV5 SKV6 SKV7 SKV8 Action <RECALL>...
Page 491 The range of values for the event n goes from 0 to 9 (10 keystrokes) Hotkeys 1 to 8 are assigned to the keys of the OPs. Hotkeys 9 to 49 are reserved for Siemens. PLC-specific keys from 50 to 254 are also available. These keys are not actual hotkeys, but are used for selecting screens via the PLC (virtual keys).
Page 492 Configure hotkeys and PLC keys 4.2 Configuration Pressing the <ETC> key again returns to softkey menu 1. In HMI Advanced, the range of values for the task numbers is between 0 and 23, in HMI Embedded it is between 0 and 15. If no task is specified, the event is assigned to the current task (current operating area).
Page 493 Configure hotkeys and PLC keys 4.2 Configuration configuration file for the key, but no response was saved, then the key does not have a function. Hotkey assignment: MF2 keyboard Hotkey Key <Machine> SHIFT+F10 Key <MENU SELECT> If there is no entry in the keys.ini configuration file for hotkey 7 or hotkey 8, the key will not be mapped as a hotkey but will retain its original function (compatible mode).
Page 494 In the PLC interface, area DB19. Byte10 is provided for key selection. Here, the PLC can directly select one key between 50 and 254. (Keys 1 to 49 are reserved for Siemens, keys 50 to 254 are specific PLC keys.) Note In M:N mode, the area for the 2nd HMI interface is DB19.Byte60.
Page 495 Configure hotkeys and PLC keys 4.3 PLC interface Acknowledgment An HMI system acknowledgment is divided into two steps: ● In the first step, the HMI software transfers the control information 255 to DB19.Byte10. ● In the second step, the actual acknowledgment takes place on the PLC in which DB19.Byte10 is cleared.
Page 496 Configure hotkeys and PLC keys 4.3 PLC interface Structure of the interface The interface between HMI Embedded sl and the PLC uses the following data: HMI 1: DB19.DBW28: Screen number DB19.DBB30: Control bits PLC → HMI, PLC byte DB19.DBB31: Control bits HMI → PLC, HMI byte HMI 2: DB19.DBW28: Screen number...
Page 497 Configure hotkeys and PLC keys 4.3 PLC interface PLC → HMI Selection Deselection HMI → PLC Selection Deselection − − Inactive Display selection The relations with the individual steps are shown in the above table by the numbers in brackets (step numbers). ●...
Page 498 Configure hotkeys and PLC keys 4.3 PLC interface Operating areas With HMI Advanced, the displays are shown in a separate operating area similar to the measuring cycle displays. This operating area can be selected manually by means of the sixth softkey (PLC displays) on the second operating area menu. If no PLC display is active when the area is selected, the text "Currently no PLC display active"...
Page 499 Configure hotkeys and PLC keys 4.4 Selecting dialog/softkey menus Selecting dialog/softkey menus 4.4.1 Assigning INI files to operating areas Overview An Action value ≥ 100 automatically switches the HMI software to "Expand user interface" operational sequences. If Action ≥ 100, the configuration of the INI files determines which softkey menu or screen form should be displayed and in which state.
Page 500 Configure hotkeys and PLC keys 4.4 Selecting dialog/softkey menus [MachineMDI] 4.4.2 Configuring "Expand user interface" functions Description One or more states (according to the State list) can be configured for each action (≥ 100) and you can also specify which "Expand user interface" function is to be initiated. If nothing is configured in these INI files, no screen forms or softkey menus will appear.
Page 501 Configure hotkeys and PLC keys 4.5 List of selectable states List of selectable states 4.5.1 Selectable states in HMI Advanced Overview In general, the following conditions apply to all tasks in HMI Advanced: No configuration: Maintains current state. Configuration with 0: The basic state of an operating area is activated.
Page 502 Configure hotkeys and PLC keys 4.5 List of selectable states "Parameters" operating area It is not possible to move from the current screen in this area. "Program" operating area State Function Data selection Program management Services operating area State Function Data in Data out Manage data...
Page 503 Configure hotkeys and PLC keys 4.5 List of selectable states State Function Optimization/test (V7.1 and later) Custom operating area See chapter "Custom operating area". 4.5.2 Selectable states in HMI Embedded sl Overview There are the following configuration options for the state in HMI Embedded sl: A configuration: Maintains current state.
Page 504 Configure hotkeys and PLC keys 4.5 List of selectable states State Function Workpiece zero – 2 holes Workpiece zero – 3 holes Workpiece zero – 4 holes Workpiece zero – rectangular spigot Workpiece zero – 1 circular spigot /user screen form Workpiece zero –...
Page 505 Configure hotkeys and PLC keys 4.5 List of selectable states Program Manager State Function NC directory Parts programs* Subprograms* User directory 1 * User directory 2 * User directory 3 * User directory 4 * Standard cycles* Manufacturer cycles* User cycles* User directory 5 * User directory 6 * User directory 7 *...
Page 506 Configure hotkeys and PLC keys 4.5 List of selectable states State Function – /user screen form User data Machine data 4.5.4 Selectable states in ShopTurn on NCU Machine manual (without "Machine manual" option) Legend: If option available (display MD is set) Custom screen These designated functions can be configured with the "Expanding the Operator Interface"...
Page 507 Configure hotkeys and PLC keys 4.5 List of selectable states State Function – /user screen form (tailstock) ShopTurn settings Machine hand (with "Machine manual" option) State Function Main screen Measure tool Measure tool – length manual X/user screen form Measure tool – length manual Z/user screen form Measure tool –...
Page 508 Configure hotkeys and PLC keys 4.5 List of selectable states State Function 1600 Milling* 1613 Milling – rectangular pocket* 1614 Milling – circular pocket* 1623 Milling – rectangular spigot* 1624 Milling – circular spigot* 1633 Milling – longitudinal groove* 1634 Milling –...
Page 509 Configure hotkeys and PLC keys 4.5 List of selectable states State Function User directory 4 * Standard cycles* Manufacturer cycles* User cycles* User directory 5 * User directory 6 * User directory 7 * User directory 8 * Program State Function Machining plan / G code editor Simulation –...
Page 510 Configure hotkeys and PLC keys 4.5 List of selectable states Expanding the user interface 4-28 Commissioning Manual, 11/2006, 6FC5397-0DP10-0BA0...
Page 511 "Custom" operating area Delivery condition and use Overview The operating areas described thus far can be extended and modified using "Expanding the Operator Interface" tools. Extensions can only be applied to softkeys, which have not been used previously. Using the tools described below, it is possible to configure a separate operating area in both HMI Embedded sl and HMI Advanced, where all 8 horizontal and 8 vertical softkeys are available for a user-specific user interface.
Page 512 "Custom" operating area 5.2 Activating the operating area Activating the operating area HMI Advanced The operating area is enabled in the REGIE.INI file and is assigned to a softkey. Example Activation via horizontal softkey 4 in the 1st expanded menu (default setting). ●...
Page 513 "Custom" operating area 5.3 Defining the start dialog Activation by keys ● Hotkey The "Custom" hotkey on the OP 010 and OP 010C always activates this operating area (default setting). Other additional configurations are possible. ● Horizontal softkey Activation via the horizontal softkey 4 in the 1st expanded menu is the default setting. The softkey assignment can be changed in HMI Advanced;...
Page 514 "Custom" operating area 5.3 Defining the start dialog ● Operating area name HMI Advanced HMI Embedded sl The name specified appears on the top left The name specified appears on the top left of the of the start dialog displayed. start dialog displayed.
Page 515 Configuring environment Scope of supply Overview The software that interprets the configuration files for user interfaces and provides or activates the functions described is included in the scope of delivery of the HMI software, along with an ASCII editor for creating the content of the configuration files (program editor). Products ShopMill on NCU and ShopTurn on NCU are based on HMI Embedded sl.
Page 516 Configuring environment 6.2 Creating configuration data Creating configuration data 6.2.1 Using the COMMON.COM file Overview When using HMI Advanced, no entries are required in the COMMON.COM file. In HMI Embedded sl, this central control file contains the following information: ● Assignment between start softkeys and configuration files ●...
Page 517 Configuring environment 6.2 Creating configuration data files are not subject to any particular restrictions. It should be noted, however, that large files are processed more slowly. 6.2.2 Structure of the COMMON.COM file Overview The COMMON.COM file is supplied together with the cycles. It contains various sections for specific hardware settings.
Page 518 Configuring environment 6.2 Creating configuration data Control entries Syntax: CHK_FILE_EXIST= Identifiers: This control flag: specifies whether configuration files must be copied each time by the NC or whether a check must be made as to whether the files are already stored on the RAM drive of the HMI. Parameters: Possible values: 0: A check whether the file already exists on the...
Page 519 Configuring environment 6.2 Creating configuration data Example of COMMON.COM [MMC_DOS] sc101=tooth.com ; MACHINE sc111=mda.com ; The files are stored on the flash memory of the HMI. sc122=auto.com sc207=param.com ; PARAMETER sc314=aeditor.com ; PROGRAM, Editor sc315=aeditor.com sc316=aeditor.com sc407=dienste.com ; SERVICES sc507=diagnose.com ;...
Page 520 Configuring environment 6.2 Creating configuration data Entry points in the operating areas Operating area SCxxx Output dialog MACHINE SC101 MACHINE JOG Horizontal SK 1 SC111 MACHINE MDA Horizontal SK 1 SC122 MACHINE AUTO Horizontal SK 2 PARAMETER SC207 Main screen of PARAMETERS Horizontal SK 7 PROGRAM SC308...
Page 521 Configuring environment 6.2 Creating configuration data Permissible file names The file names are defined as follows: Alsc.txt Contains the language-dependent texts for the Siemens standard cycles Almc.txt Contains the language-dependent texts for the manufacturer cycles Aluc.txt Language-dependent user texts Format of a text entry Syntax 8xxxx 0 0 "Text"...
Page 522 HMI Embedded sl Storage In the Linux environment, the user configurations are copied to the /user/sinumerik/hmi/proj directory (for "normal" user dialogs, i.e., everything except cycles support) on the CF card. User configurations for user cycles support are copied to the /user/sinumerik/cycles/proj directory on the CF card.
Page 523 \hmi\proj \hmi\lng\... \hmi\ico\... In the PROGRAM operating area, the entire \cycles or \hmi directory is copied from the USB memory to the /user/sinumerik directory on the CF card. 6.3.2 HMI Advanced Overview When using HMI Advanced, no control file entries are required.
Page 524 Configuring environment 6.4 Search function on the HW platform common to both HMI systems Search function on the HW platform common to both HMI systems 6.4.1 Search function principle Overview HMI Embedded WIN32 searches the configuration files for "Expand user interface" on the same paths as HMI Advanced.
Page 525 Configuring environment 6.4 Search function on the HW platform common to both HMI systems Directory on the RAMDISK: Filename.bin Filename.bmp Bitmap name without path In HMI Advanced, files with a .bin extension are not used Search sequence if no archive is specified and the file name does not contain a path: Filename.bin in the CUS directory on the data management path Filename.bmp...
Page 526 Configuring environment 6.4 Search function on the HW platform common to both HMI systems Filename.bmp Filename.bm_ in the archive in the CST\resolution directory on the data management path Filename.bin in the current directory (Bin directory) Filename.bmp in the current directory (Bin directory) Filename.bin Filename.bi_ in the...
Page 527 Configuring environment 6.4 Search function on the HW platform common to both HMI systems Filename.bmp in archive CST.ARJ in the current directory (Bin directory) Filename.bxx Partial binary files, which have to be processed for reasons of compatibility with Real mode and when starting Protected mode.
Page 528 Configuring environment 6.4 Search function on the HW platform common to both HMI systems 6.4.3 Search function for images Search sequence The expanded search function for images (bitmaps) in HMI Embedded sl can also be used for images in the "Expand user interface" system. If HMI Embedded WIN32 (ShopMill/ShopTurn) is installed together with HMI Advanced on a single hardware platform, a relevant data management path can be preset.
Page 529 Appendix List of start softkeys Start softkeys for ShopMill and ShopTurn ShopMill SCxxx Output dialog SC818 Machine Manual operating area (large Horizontal SK 8 dialog) SC8181 Machine Manual operating area Horizontal SK 8 (medium dialog) SC8182 Machine Manual operating area (small Horizontal SK 8 dialog) SC8131...
Page 530 Appendix A.1 List of start softkeys ShopMill SCxxx Output dialog SC826 Machine Auto operating area (large Horizontal SK 6 dialog) SC8261 Machine Auto operating area (medium Horizontal SK 6 dialog) SC8262 Machine Auto operating area (small Horizontal SK 6 dialog) SC8426 Program-Drilling operating area Vertical SK 6...
Page 531 Horizontal SK 6 (measuring area (expanded area) cycles support) SC8407 Program-G-Code-Editor operating Horizontal SK 7 (measuring area (expanded area) cycles support) * These are Siemens dialogs. ShopTurn SCxxx Output dialog SC818 Machine Manual operating area (large Horizontal SK 8 dialog)
Page 532 SC8406 Program-G-Code-Editor operating Horizontal SK 6 (turning area (expanded area) measuring cycles support)* SC8407 Program-G-Code-Editor operating Horizontal SK 7 (milling area (expanded area) measuring cycles support)* * These are Siemens dialogs. Expanding the user interface Commissioning Manual, 11/2006, 6FC5397-0DP10-0BA0...
Page 533 Appendix A.2 List of colors List of colors Available colors A standard color table is available for HMI Advanced and HMI Embedded sl for the purpose of configuring dialogs (subset of the respective standard colors): Number Color black Red/brown Dark green Light gray Dark gray Blue...
Page 534 Appendix A.2 List of colors Activating a color table in Paint Shop Pro: ● File → Open → ...\*.bmp ● Colors → Open picture palette → ...\*.PAL ● Apply palette by selecting the "Color Indices: Open" option. System colors There is a choice of 10 colors available for the color of an element (text, input field, background, etc.).
Page 535 Appendix A.3 List of accessible system variables List of accessible system variables Name Index Description $A_DBB[x] x=ByteNo Data byte from/to PLC $A_DBD[x] x=Offset Double data word (32bit) from/to PLC $A_DBR[x] x=Offset Real data (32 bit) from/to PLC $A_DBW[x] x=Offset Data word (16 bit) from/to PLC $A_DLB[index] index=Offset Data byte in link area...
Page 536 Appendix A.3 List of accessible system variables Name Index Description $A_OUTSI Safe Programmable Logic: Internal NCK output safety $A_OUTSID Safe Programmable Logic: Image of internal NCK output safety $A_OUTSIP Safe Programmable Logic: Internal PLC output 611D safety $A_OUTSIPD Safe Programmable Logic: Image of internal PLC output 611D safety $A_TIMERSI Safe Programmable Logic: NCK timers...
Page 537 Appendix A.3 List of accessible system variables Name Index Description $AA_DTEPB[x] x=Axis Drive-specific dist.-to-go infeed oscillation in basic coordinate system $AA_DTEPW[x] x=Axis Drive-specific dist.-to-go infeed oscillation in $AA_DTEW[x] x=Axis Drive-specific path, end of block in WCS $AA_EG_ACTIVE [a,b] a = Following axis EG coupling active b = Leading axis $AA_EG_AX[n,a]...
Page 538 Appendix A.3 List of accessible system variables Name Index Description $AA_OSCILL_REVERSE_POS1[x] x=Axis Current reversal position 1 oscill. in synchronous actions $AA_OSCILL_REVERSE_POS2[x] x=Axis Current reversal position 2 oscill. in synchronous actions $AA_OVR[x] x=Axis Drive-specific override for motion-synchronous actions $AA_POWER[x] x=Axis Drive active power in [Watts] $AA_S[x] x=SpindleNo Spindle speed, setpoint...
Page 539 Appendix A.3 List of accessible system variables Name Index Description $AC_MARKER[x] x=MarkerNo Counter for motion synchronous actions $AC_MEA Probe has responded $AC_OVR Path override for synchronous actions $AC_PARAM[x] x=ParameterNo Dyn. parameter for motion synchronization $AC_PATHN Normalized path parameter $AC_PLTBB Distance from start of block in basic coordinate system $AC_PLTEB Distance from block end in basic coordinate...
Page 540 Appendix A.3 List of accessible system variables Name Index Description $MN_MAX_SUMCORR_ Max. number of total offsets per cutting edge PERCUTTING_EDGE $MN_MM_KIND_OF_SUMCORR Properties of total offsets in NCK $MN_MM_NUM_CC_MAGAZINE_ Number of parameters for one tool magazine PARAM $MN_MM_NUM_CC_MAGLOC_ Number of parameters for one tool magazine PARAM location $MN_MM_NUM_CC_MON_ PARAM...
Page 541 Appendix A.3 List of accessible system variables Name Index Description $SC_PA_CENT_ABS[x,1] x=Number protection zone Abscissa of arc center of 2nd contour element $SC_PA_CENT_ABS[x,2] x=Number protection zone Abscissa of arc center of 3rd contour element $SC_PA_CENT_ABS[x,3] x=Number protection zone Abscissa of arc center of 4th contour element $SC_PA_CENT_ABS[x,4] x=Number protection zone Abscissa of arc center of 5th contour element...
Page 542 Appendix A.3 List of accessible system variables Name Index Description $SC_PA_CONT_TYP[x,2] x=Number protection zone Contour type of 3rd contour element $SC_PA_CONT_TYP[x,3] x=Number protection zone Contour type of 4th contour element $SC_PA_CONT_TYP[x,4] x=Number protection zone Contour type of 5th contour element $SC_PA_CONT_TYP[x,5] x=Number protection zone Contour type of 6th contour element...
Page 543 Appendix A.3 List of accessible system variables Name Index Description $SN_PA_CONT_ABS[x,8] x=Number protection zone Abscissa of end point of 9th contour element $SN_PA_CONT_ABS[x,9] x=Number protection zone Abscissa of end point of 10th contour element $SN_PA_CONT_NUM[x] x=Number protection zone Number of valid contour elements $SN_PA_CONT_ORD[x,0] x=Number protection zone Ordinate of end point of 1st contour element...
Page 544 Appendix A.3 List of accessible system variables Name Index Description $TC_MAP3 Status of magazine $TC_MAP4 Link 1 between magazine and next magazine $TC_MAP5 Link 2 between magazine and preceding magazine $TC_MAP6 Magazine dimension $TC_MAP9 Number of active wear group $TC_MAPCx[y] x=ParameterNo Magazine user data for a tool magazine y=MagazineNo...
Page 545 Appendix A.4 List of Pl services Name Index Description $TC_TPG9 Compensation parameter for GWPS $VA_COUP_OFFS[x] x=Axis Offset to leading axis / leading spindle, actual value $VA_IS[x] x=Axis Safe actual position of axis $VA_VACTM[x] x=Axis Actual-value, load-end axis velocity in MCS system List of Pl services Programming...
Page 546 Appendix A.4 List of Pl services Service Explanation Parameter Example _N_CRCEDN Create tool edge by specifying the cutting edge number. If the T number of an existing tool is entered in parameter "T Number" of this service, then a tool edge for the existing tool is created (in this case, the parameter "D number", i.e., the number of the edge to be created, has a value range of 1-9).
Page 547 Appendix A.4 List of Pl services Service Explanation Parameter Example _N_DELECE Delete a cutting edge: If the T number of an existing tool is entered in parameter "T Number" of this PI service, then the tool edge for the relevant tool is deleted (in this case, the parameter "D number, i.e., the number of edge to be deleted, has a value range of 1-9).
Page 548 Appendix A.4 List of Pl services Service Explanation Parameter Example _N_SETUFR The SYSTEM OR USER variables 'linShift', 'mirrorImgActive', 'rotation' and 'scaleFact' in channel-specific data block FU can be used to define up to 8 zero offsets per channel. PI service _N_SETUFR must be called in order to activate these user-defined zero offsets.
Page 549 List of abbreviations Abbreviations Output ASCII American Standard Code for Information Interchange American coding standard for the exchange of information Mode group Operator Panel Interface Computer-Aided Design Computerized Numerical Control Computerized numerical control Carriage Return Digital-to-Analog Converter Data Block in the PLC Data Block Byte in the PLC Data Block Word in the PLC Data block bit in the PLC...
Page 550 List of abbreviations B.1 Abbreviations Hardware Hardware Start-up Interpolatory Compensation Interpolatory compensation Increment: Increment INItializing data Initializing data Interpolator International Standard Organization JOGging: Setup mode K1 .. C4 Channel 1 to channel 4 Light-Emitting Diode: Light-emitting diode Line Feed Servo gain factor Local User Data: Local user data Megabyte Machine Control Panel Machine control panel (→...
Page 551 List of abbreviations B.1 Abbreviations SRAM Static RAM (non-volatile) GWPS Grinding wheel surface speed Software SYstem Files System files Testing Data Active: Identifier for machine data Tool Offset Tool offset Tool Offset Active: Identifier (file type) for tool offsets User frame Feed Drive Workpiece coordinate system Tool offset...
Page 552 List of abbreviations B.1 Abbreviations Expanding the user interface Commissioning Manual, 11/2006, 6FC5397-0DP10-0BA0...
Page 553 Glossary Action Anything configured within a → Method: → Functions, → Calculating variables, → Changing properties, etc. User variable Variables defined by the user in the → Parts program or data block. Array An array can be used to organize data of a standard data type stored in the memory in such a way that it is possible to access the data via an index.
Page 554 Internal arithmetic variable to which no → Properties can be assigned and is not, therefore, visible in the → Dialog. Hotkeys 6 keys on OP 010, OP 010C and SINUMERIK keyboards with hotkey blocks. Pressing the keys selects an operating area directly. As an option, 2 additional keys can be configured as hotkeys.
Page 555 Programmed sequence of operations executed when a corresponding → Event occurs. HMI Advanced, HMI Embedded sl User interface for PLC Numerical Control: System components of a SINUMERIK system, which controls the motional sequences of axes on the basis of → Parts programs. NC code Permissible language elements used to write SINUMERIK →...
Page 556 In contrast to → Machine data, setting data can be altered immediately by the operator. ShopMill Optimized SINUMERIK application and user interface for 2½D milling operations. ShopTurn Optimized SINUMERIK application and user interface for turning operations.
Page 557 Glossary Simulation Simulation of a → Parts program run without movement of the actual machine axes. Softkey Key on front of operator panel, which activates a function displayed on the assigned area of the screen. Softkey labels Text/image on the screen, which is assigned to a → Softkey. Softkey menu All horizontal or all vertical →...
Page 558 Glossary Line index Row number of an array Access level Graduated system of authorization, which makes the accessibility and utilization of functions on the → User interface dependent on the authorization rights of the user. Expanding the user interface Glossary-6 Commissioning Manual, 11/2006, 6FC5397-0DP10-0BA0...
Page 559 Index Properties, 2-10 Dialog change mode, 2-87 Dialog element, 2-13 DLL file, 2-105 Action, 4-10 Array Access mode, 2-44 Column index, 2-43 Compare mode, 2-44 Exponential notation, 2-26 Definition, 2-42 Element, 2-43 Line index, 2-43 Status, 2-47 Fig. Attributes, 2-22 Deselection, 4-15 display as short text, 2-34 selecting, 4-15...
Page 560 Index MRNP (Multiple Read NC PLC), 2-91 Overview, 2-70 Limits, 2-21 PI_SERVICE, 2-103 Long text, 2-21 PI_START, 2-104 PP (Passivate Program), 2-89 Recompile NC code, 2-97 REFRESH (Update), 2-93 REPLACE (strings), 2-103 Master dialog, 2-87 RETURN (Back), 2-96 MD 9016 RIGHT (strings), 2-102 MM_SWITCH_TO_AREA, 5-2 RNP (Read NC PLC Variable), 2-90...
Page 561 Index Text, 2-21 Text for units, 2-21 Range of values, 4-9 Toggle field, 2-27 Registers Trigonometric functions, 2-111 Exchanging data, 2-94 Status, 2-95 Value, 2-94 Relational operators, 2-111 Return, 2-2 User variable, 2-23 Scratch buffer, 4-13 Variable Security level, 2-56 calculating, 2-31 Short text, 2-21 Change property, 2-20...
Page 562 Index Expanding the user interface Index-4 Commissioning Manual, 11/2006, 6FC5397-0DP10-0BA0...
Page 563 Programming help systems Alarm/Machine data help SINUMERIK SINUMERIK 840D sl/840Di sl/810D Online Help (HE1) Commissioning Manual Valid for: control system SINUMERIK 840D sl/840DE sl SINUMERIK 840Di sl/840DiE sl SINUMERIK 840D/840DE SINUMERIK 840Di/840DiE SINUMERIK 810D/810DE Software Software Version HMI Advanced 11/2006...
Page 564 Trademarks All names identified by ® are registered trademarks of the Siemens AG. The remaining trademarks in this publication may be trademarks whose use by third parties for their own purposes could violate the rights of the owner.
Page 565 Table of contents Programming help systems ........................5 Overview ............................5 Quick "ASCII" help .........................8 1.2.1 Extending/replacing the help function....................8 1.2.2 Entries in the file "IF.INI" ........................8 1.2.3 Extension of text files ........................11 1.2.4 Extension of a topic........................13 1.2.5 Extension of an instruction......................14 1.2.6 Parameterization of extended "PDF"...
Page 566 Table of contents Online Help (HE1) Commissioning Manual, 11/2006, 6FC5397-0DP10-0BA0...
Page 567 Software • HMI Advanced • Adobe Reader 4.x (available free over the Internet/from specialist dealer) The Adobe Acrobat Reader 4.x software is supplied on the SINUMERIK 840D sl controller as standard. • Adobe Acrobat 4.x You will need the Adobe Acrobat Distiller 4.x software in order to convert documents to PDF and for editing documents once they are available in this format.
Page 568 Programming help systems 1.1 Overview Principle of PDF help The PDF help depends on the following components being available in the help file storage location: • Call file, e.g., PG_GR.TXT, with the information: <PDF file name> <ID> <search term> for each call •...
Page 569 The help adheres to the search sequence below: • F:\USER\HLP • F:\ OEM\HLP • F:\ ADD_ON\HLP • F:\MMC2\HLP • F:\HMI_ADV\HLP • F:\ DH\CUS.DIR\HLP.DIR (user directory) • F:\ DH\CMA.DIR\HLP.DIR (manufacturer directory) • F:\ DH\CST.DIR\HLP.DIR (Siemens directory) • F:\ DH\COM.DIR\HLP.DIR Online Help (HE1) Commissioning Manual, 11/2006, 6FC5397-0DP10-0BA0...
Page 570 Programming help systems 1.2 Quick "ASCII" help Quick "ASCII" help You can call up a number of help functions in the editor to provide programming support "Information" with the editing of part programs via the key: • Quick "ASCII" help –...
Page 571 • End user "DH\CUS.DIR\USER_GR.COM" (any file name) "Settings" (entered under Note The path for the Siemens text file "DH\CST.DIR\lFS_GR.COM" must exist, otherwise an error message is output. There are different parameterization options for the names of the text files when assigning the text path.
Page 572 Programming help systems 1.2 Quick "ASCII" help Extract from TXT file "IFM_GR.COM": a2//G00/Linear interpolation with rapid traverse (m) , quick help a2//G01/Linear interpolation with feed (m) a/20/"PGA.PDF",2,"="/=/Assignment operator with extended help a/3/"PG.PDF",17,"ANG"/ANG/Contour angle (s) with extended cycle help m/14/"PGZ.PDF",302,"CYCLE77"/CYCLE77/Circular spigot milling cycle with extended cycle help CONTEXT section Increased context sensitivity of the help function can be selected in the [CONTEXT] section.
Page 573 "t" = Turning "g" = Grinding "s" = Nibbling "p" = Punching "a" = Display all technologies [TEXTFILES] Siemens = DH\CST.DIR\IFS_GR.COM Machine manufacturer = DH\CMA.DIR\IFM_GR.COM Machine manufacturer = DH\CMA.DIR\IFI_GR.COM End user = DH\CUS.DIR\USER_GR.COM [CONTEXT] = 0: Context sensitivity not active...
Page 574 Note Within each of the individual text files, the Siemens topics are displayed first, followed by those of the machine manufacturer and finally those of the end user. The specified sequence only appears if the topics are declared first and then the instructions of the text file.
Page 575 Topic ID User 0..49 Siemens 50...99 Machine manufacturer From 100 End user The following topic IDs exist as standard in the Siemens text file: Table 1-2 Defined topic IDs Topic ID Topic name Topic ID Topic name Preparatory functions Program handling...
Page 576 Programming help systems 1.2 Quick "ASCII" help 1.2.5 Extension of an instruction Extension of an instruction An instruction contains descriptive texts, e.g., "G0/Linear interpolation with rapid traverse". An instruction is assigned to a topic via the topic ID. Parameters of instruction definition An instruction definition contains the following parameters: Technology/topic ID/extended help/instruction text/descriptive text Example of editor help:...
Page 577 Programming help systems 1.2 Quick "ASCII" help Technology The following characters are defined for specifying the technology category: "m" = Milling "t" = Turning "g" = Grinding "s" = Nibbling "p" = Punching "a" = Display for all technologies Note Entries are separated by commas so as to enable them to be assigned to several technologies and different topics.
Page 578 Programming help systems 1.2 Quick "ASCII" help Parameters of instruction definition Technology/topic ID/extended help/instruction text/descriptive text Extended help The following entries are possible in the "Extended help" parameter: • Editor help /"PDF file name", help ID, "search string"/ • Cycle help /"PDF file name", help ID, "search string"...
Page 579 Programming help systems 1.2 Quick "ASCII" help Instruction text An instruction text could be "G17", for example. This text is transferred to the part program "Transfer to editor" currently being edited when the command is issued. The instruction text can be approx. 12 characters long. Descriptive text The descriptive text is the help text which describes the instruction in more detail.
Page 580 Programming help systems 1.3 Extended "PDF" help 1.2.7 Extension with alarm text variables Function A special situation with respect to parameterization of the section for descriptive texts or topic names is to store these in the section instead of the descriptive texts ("alarm text variables").
Page 581 Programming help systems 1.3 Extended "PDF" help 1.3.2 Extending programming help A special entry in the "Extended help" parameter of the instruction definition makes it possible to integrate an extended help in addition to the quick help (e.g., detailed information on the selected command).
Page 582 Programming help systems 1.3 Extended "PDF" help 2) Generate text file Copy the single-column index generated above (right-justified page numbers) and save it in a text file (*.TXT). Example: MEAW 155 <Search string> <page> The text file for the PDF call requires the following syntax: <PDF file name>...
Page 583 (IFIT_COM or IFIM_COM) for the ISO mode quick "ASCII" help. The extended "PDF" help can thus be called from the quick "ASCII" help. IF.INI [TEXTFILES] [TEXTFILES] ;text files containing the information shown in the help system Siemens=cst.dir\ifs_.com SiemensI=cst.dir\ifit_.com or ifim_.com Manufacturer= End user= Online Help (HE1)
Page 584 • MD20150 GCODE_RESET_VALUES[n(active channel),47] If MD20150 [47] = 2, the file entered in the INI file under "SiemensI" (ISO mode) is used (otherwise the file under "Siemens" is used). • MD10880 MM_EXTERN_CNC_LANGUAGE MD10880 specifies whether the controller is to be designed for turning or milling in ISO mode.
Page 585 Programming help systems 1.4 ISO mode help Necessary files • IFIT_.COM or IFIM_.COM: Text file with ISO mode commands and brief description • *.PDF: e.g., 840D_PGIT_GR.PDF • *.TXT: e.g., 840D_PITG_GR.TXT 1) Define jump labels in document The jump labels must be identified by an index entry and a single-column index list (right-justified page numbers) must be generated in the document (e.g., Winword) which is to be displayed on the controller as a PDF.
Page 586 Programming help systems 1.4 ISO mode help 5) Read files into controller The generated files (*.PDF and *.TXT) must now be read into directory F:\USER\HLP on the controller. Note In the case of a larger volume of indices, the call file can be created automatically using Microsoft Excel: •...
Page 587 Software • HMI Advanced • Adobe Reader 4.x (available free over the Internet/from specialist dealer) The Adobe Acrobat Reader 4.x software is supplied on the SINUMERIK 840D/840D sl controller as standard. • Adobe Acrobat 4.x You will need the Adobe Acrobat Distiller 4.x software in order to convert documents to PDF and for editing documents once they are available in this format.
Page 588 Alarm/Machine data help 2.1 Overview Creation procedure • Define jumps in the help document (e.g., using standard index function of DTP systems) and generate • Store jump file as text file • Generate PDF file Result: • A call file (text file) with the information: <PDF file name>...
Page 589 The help adheres to the search sequence below: • F:\USER\HLP • F:\ OEM\HLP • F:\ ADD_ON\HLP • F:\MMC2\HLP • F:\HMI_ADV\HLP • F:\ DH\CUS.DIR\HLP.DIR (user directory) • F:\ DH\CMA.DIR\HLP.DIR (manufacturer directory) • F:\ DH\CST.DIR\HLP.DIR (Siemens directory) • F:\ DH\COM.DIR\HLP.DIR Online Help (HE1) Commissioning Manual, 11/2006, 6FC5397-0DP10-0BA0...
Page 590 When help is called up, a PDF file is opened and the relevant alarm is displayed on the controller in Adobe Reader. The files containing the alarms are stored in the directories below: • Siemens alarms: F:\HMI_ADV\HLP • Manufacturer alarms: F:\DH\CMA.DIR\HLP • User alarms: F:\DH\USER\HLP...
Page 591 Alarm/Machine data help 2.2 Alarm help Other languages The alarm texts are available in the following languages: CH: Simplified Chinese TW: Standard Chinese KO: Korean JA: Japanese SW: Swedish HU: Hungarian PO: Portuguese CZ: Czech TR: Turkish RU: Russian PL: Polish NL: Dutch The naming convention specified above for language codes must be used for the file names of the user alarms (must not be changed).
Page 592 Alarm/Machine data help 2.2 Alarm help 2) Generate text file Copy the single-column index generated above (right-justified page numbers) and save it in a TXT file. Example: 10702 90 <ID> <page> The search string (alarm number) is identical to the ID number in this case. The text file for the PDF call now requires the following syntax: <PDF file name>...
Page 593 Alarm/Machine data help 2.2 Alarm help 2.2.4 Changing "Win-Help" alarm help to "PDF help" To change the help function from "Win-Help" to "PDF help", proceed as described in in the previous section: "Extension of alarm help". 1. Define jump labels for each alarm number in the document: The jump labels must be identified by an index entry and a single-column index list (right-justified page numbers) must be generated in the document (e.g., Winword) which is to be displayed on the controller as a PDF.
Page 594 The machine data help is based on the "PDF help", i.e., when help is called up, a PDF file is opened and the relevant alarm is displayed on the controller in Adobe Reader. The files containing the machine data are stored in the directories below: • Siemens MD: F:\MMC2\HLP • User MD: F:\USER\HLP File names...
Page 595 Alarm/Machine data help 2.3 Machine data help Structure of text file PDF file without language code MD number Page DROT.PDF 1000 DROT.PDF 1001 DROT.PDF 1002 Meanings of names Name Meaning N_NCK_GR.PDF General MD C_NCK_GR.PDF Channel-specific MD A_NCK_GR.PDF Axis-specific MD S_NCK_GR.PDF Setting data DISPL_GR.PDF Display MD...
Page 596 Alarm/Machine data help 2.3 Machine data help 2) Generate text file Copy the single-column index generated above (right-justified page numbers) and save it in a TXT file. Example: 10000 170 <ID> <page> The search string (MD number) is identical to the ID number in this case. The text file for the PDF call now requires the following syntax: <PDF file name>...
Page 597 Index Text property, 17 ISO mode help, 21 Extend, 22 Alarm help, 28 Comments, 30 Extend, 29 File name, 28 Jump file Alarm texts Create alarm/MD help, 26 Language code, 29 Create programming help, 6 Test, 7, 27 CONTEXT, 10 Machine data help, 32 Extend, 33 File name, 32...
Page 598 Online Help (HE1) Commissioning Manual, 11/2006, 6FC5397-0DP10-0BA0...
Page 599 840D sl/840Di sl/840D/840Di/810D References for text generation Generating target language texts (TX2) Commissioning Manual Valid for: Controls SINUMERIK 840D sl/840DE sl SINUMERIK 840D powerline/840DE powerline SINUMERIK 840Di powerline/840DiE powerline SINUMERIK 810D powerline/810DE powerline Software Release: HMI Advanced V7.3 HMI Embedded V7.2...
Page 600 Trademarks All names identified by ® are registered trademarks of the Siemens AG. The remaining trademarks in this publication may be trademarks whose use by third parties for their own purposes could violate the rights of the owner.
Page 601 Editing files with Word ..........................11 Overview ............................11 Generating a new text file ......................11 Opening an existing file........................12 Saving text files ..........................14 Codes for SINUMERIK HMI......................16 Input of Text............................. 17 Special characters in different language families ................17 Inputting characters via the Character Map.................18 Compound input...........................20 Using a different keyboard assignment ..................21...
Page 602 Table of contents Tables Table 1-1 Language families ......................... 6 Table 2-1 Encoding ............................. 16 Table 3-1 Text file coding ..........................19 Generating target language texts (TX2) Commissioning Manual, 11/2006, 6FC5397-0DP10-0BA0...
Page 603 Introduction General Since the 1990s, Microsoft have put considerable effort into satisfying global demands for information processing and software development. In addition to supporting as many languages as possible, one of the aims was to be able to support all languages with the same uniform operating system, as opposed to the language- specific versions of operating systems which were used before.
Page 604 Introduction 1.3 Language families • The text file is to be coded using this code page, not as a Unicode file. • The text should be generated as simply as possible: in particular, this means that if possible, no additional software should have to be installed. •...
Page 605 Introduction 1.4 Tools Operating system and target language from the same language family If the language of the operating system (e.g., German) belongs to the same language family as the target language (e.g., Portuguese), then some difficulties could possibly occur with the input of certain characters.
Page 606 Introduction 1.5 Terms Terms Code page A list of characters which forms the character set for one or more languages. A code which is unique within this code page is assigned to each of the characters in the list. All of the code pages used in Windows share the ASCII range (codes 0 to 127). A distinction is made between single-byte code pages and multiple-byte code pages.
Page 607 Introduction 1.5 Terms Input Method Editor (IME) An aid for inputting the CJK characters (CJK: Abbreviation for Chinese, Japanese and Korean). Language family A language family is a group of languages which uses the same code page. This requires the use of the same basic alphabet (e.g., Latin or Cyrillic), but it does not mean that the alphabet of all languages of this group is the same.
Page 608 Introduction 1.5 Terms Text file The term "Text file" is used to describe a file which does not contain any formatting (font type, font size, underscore, bold, italics etc.) or embedded objects (pictures, tables, graphics, footnotes etc.). This means that, apart from the text characters, the file will only contain ASCII control characters like Tab, CR and LF (tab indent, carriage return and line feed).
Page 609 Editing files with Word Overview This section describes how text files can be edited using Microsoft Word 2003. Word 2003 does not edit text files directly. We recommend saving an additional version of Instead, it converts them to Word files upon the text file as a Word file and using this version opening.
Page 610 Editing files with Word 2.3 Opening an existing file Opening an existing file 1. In Word 2003, select "Open…" from the "File" menu. 2. From the "Open" dialog box, choose the "Text files" (*.txt)" setting under "Files of type". If your file has a different extension from "txt", you must rename it. 3.
Page 611 – If "Windows (default)" is selected, activate "Other Encoding". Select the correct encoding (Word will make a suggestion, which will not necessarily be correct). – Section "Codes for SINUMERIK HMI", Table 2-1 lists the suitable encoding options. Check the preview area while doing this.
Page 612 – Select the encoding which is suitable for your target language and click "OK". Section "Codes for SINUMERIK HMI", Table 2-1 lists the suitable encoding options. – Your file is now saved as a text file and encoded using the selected code page in the process.
Page 613 Editing files with Word 2.4 Saving text files – If you have selected a completely unsuitable code then a warning is displayed in the dialog box. This warning will also appear if you have selected the correct code but your file contains characters which are not permitted, such as Latin mutated vowels in a Cyrillic text.
Page 614 Depending on the installation of your system, many other codes may be listed, including those for Unix (ISO), Apple (Mac), OEM (DOS) and IBM (EBCDIC) platforms. Please use the Windows (ANSI) codes for SINUMERIK HMI. Use the following codes to open and save files (shown in alphabetical sequence in...
Page 615 Input of Text Special characters in different language families Latin language family With the Latin-based language families (Baltic, Central European, Turkish, Western), you can enter most of the characters, i.e., the basic Latin alphabet, directly with your (e.g., Western) keyboard. Most of the special characters, such as ĄáâåçđéèÍïŁŇñöőÓťŤůū, are made up of the Latin letters A-Z a-z and diacritical characters such as acute ', breve ˘, cedilla, circumflex (caret) ˆ, point ˙, colon (dieresis, trema) ¨, double-acute ˝, grave accent ', háček (caron) ˇ, macron ˉ,...
Page 616 Input of Text 3.2 Inputting characters via the Character Map Disruptive Word options Deactivate the following options in Word to prevent unwanted characters from reaching the text: In the dialog box "Tools" → "AutoCorrect Options" go to the "AutoFormat as you type" tab and under "Replace as you type"...
Page 617 Input of Text 3.2 Inputting characters via the Character Map 3. Activate the box "Advanced view". 4. Under "Character set" select the code page for your text file in order to restrict the number of available characters to this code page. The code pages are referred to as follows: Table 3-1 Text file coding...
Page 618 Input of Text 3.3 Compound input Inputting characters 1. Choose a character you want to input. The information bar at the bottom will display the Unicode code (U+..., hexadecimal), the code page code (in brackets) and the clear text description of the character. If you have set up the keyboard assignment accordingly (see Section "Using a different keyboard assignment"), the keystroke combination for entering the character numerically will appear at the bottom right in the status bar (see Section "Numerical text input").
Page 619 Input of Text 3.4 Using a different keyboard assignment Keyboard assignments The table below shows some keyboard assignments for the supported diacritical characters: Keyboard Acute Grave Circum- Há- Breve Ogon- Point Colon Double Squig- Tilde assignments flex ček dilla acute ˆ...
Page 620 Input of Text 3.4 Using a different keyboard assignment Example In Hungarian, for example, you would have to input these characters as follows: • őŐűŰ (O double-acute, U double-acute) via the Character Map • öÖüÜ directly • áÁéÉíÍóÓúÚ compound input 3.4.1 Concept of the keyboard language Windows manages pairs for the keyboard consisting of "Language ("Language and Region...
Page 621 Input of Text 3.4 Using a different keyboard assignment 4. Click "Add". The dialog box "Add Language and Region Support" is opened. 5. In the dialog box "Add Language and Region Support", select a language under "Language and Region Support" and the associated keyboard assignment under "Keyboard Assignment".
Page 622 Input of Text 3.4 Using a different keyboard assignment 6. Click "OK". The dialog box "Add Language and Region Support" is closed. You then return to the "Text Services and Input Languages" window. 7. Use "Keyboard…" to select the way in which you want to switch the keyboard assignment.
Page 623 Input of Text 3.4 Using a different keyboard assignment If you click this field with the right mouse button, an abbreviation of the dialog box "Keyboard Properties" is displayed above the "Properties" menu option. Among further settings that are offered is the ability to arrange this display as an Input language bar independently of the taskbar: at the top edge of the screen, for example.
Page 624 Input of Text 3.5 Numerical text input Keyboard assignment in picture form You can obtain the keyboard assignment in picture form. For appropriate Internet addresses, see Section "References for text generation" Checking the keyboard assignment Compare the keyboard assignment and note a key with two different assignments. If you are not sure, press this key when inputting the text to test which assignment is active.
Page 625 Input of Text 3.6 Language properties in Word files Language properties in Word files Language property The language is a property (attribute) that is managed separately in Word for each character, in the same way as other text properties (bold, underline, etc.): •...
Page 626 Input of Text 3.6 Language properties in Word files Setting the language property Proceed as follows to set the language property for a text: 1. Highlight the part of the text for which you wish to set the language property, or press CTRL+A to select the entire text.
Page 627 Input of Text 3.6 Language properties in Word files Default setting of the language property Word automatically sets the language property in the following situations: • When opening a file of type "Encoded Text File" (see Section "Opening an existing text file").
Page 628 Input of Text 3.7 Multi-language Word files Multi-language Word files In certain cases it may be useful to deliberately set different language properties for different parts of the text in a Word file. Supplementary conditions for multi-language Word files You want to enter certain parts of the text with the German keyboard assignment and then also edit these parts later on with the German keyboard assignment, whereas other parts of the text are to be generated and edited with the keyboard assignment of the target language.
Page 629 Input of Text 3.7 Multi-language Word files Automatic keyboard switching In order to automatically have the correct keyboard assignment when working on different parts of the text, in Word go to "Tools" → "Options" and activate the "Auto-Keyboard switching" option in the "Edit" tab. Note Accidental use of the automatic keyboard switching function can be confusing.
Page 630 Input of Text 3.8 Special considerations when working with Greek and Cyrillic texts Another option is to activate keyboard switching in Word: 1. In the "Extras" menu select the command "Customize..." 2. In the "Customize" dialog box select the "Commands" tab. 3.
Page 631 Input of Text 3.8 Special considerations when working with Greek and Cyrillic texts Font Name Meaning Latin P, p Latin letter P Greek Ρ, ρ Greek letter RHO Cyrillic Р, р Cyrillic letter ER Latin H, h Latin letter H Greek Η, η...
Page 632 Input of Text 3.9 Special considerations when working with East Asian texts. Special considerations when working with East Asian texts. Requirement To author or correct texts in Japanese, Chinese or Korean, you will need to have installed the corresponding expansion package for the operating system. Checking the system installation Open the dialog box "Regional and Language Options"...
Page 633 These versions of the characters are twice as wide and are not compatible with the ASCII characters. If you are using characters with a functional significance it is important to use the ASCII versions. Correct example (SINUMERIK alarm text, Japanese): The circled characters are: 014195 0 0 Identifier and attributes...
Page 634 Input of Text 3.9 Special considerations when working with East Asian texts. Incorrect example: The circled characters are full-width variants which have been used incorrectly. Note When placing a translation order, tell the translator that only the narrow, ASCII-compatible characters must be used for characters with a functional significance. Simplified/traditional Chinese Please make a careful distinction between simplified Chinese and traditional (or standard) Chinese.
Page 635 Problems and remedies Keyboard assignment switches unintentionally Problem: The keyboard occasionally switches to a different assignment while text is being entered, without this being explicitly requested. Remedy: Check whether the option for automatic keyboard switching is set as described in Section "Multi-language Word files".
Page 636 Problems and remedies Individual texts not working Problem: In some cases, the finished text files do not work in the SINUMERIK Runtime system. Individual texts or lines of text are obviously not being read correctly. Remedy: Check the formal text criteria: Are all of the characters which have a functional significance correctly encoded? •...
Page 637 References for text generation For further information about generating texts, please refer to: Developing International Software, Second Edition • Book: Microsoft Press, October 2002, ISBN 0-7356-1583-7 http://www.microsoft.com/globaldev/getwr/dis_v2/default.mspx • Overview tables of the Microsoft code pages http://www.microsoft.com/globaldev/reference/WinCP.mspx • Pictures of the keyboard assignments in Microsoft can be found at the following address: http://www.microsoft.com/globaldev/reference/keyboards.mspx •...
Page 638 References for text generation Generating target language texts (TX2) Commissioning Manual, 11/2006, 6FC5397-0DP10-0BA0...
Page 639 Index Character Map keyboard assignment Code page, 19 Changing, 21 Input, 18 Keyboard assignment Inputting characters, 19 Always visible, 31 Select, 18 in picture form, 21 Checking the installation, 7 In picture form, 25 Chinese (simplified), 36 Set up in Windows XP, 22 Chinese (traditional), 36 Keyboard assignments CJK characters, 9...
Page 640 Index Open, 12 Save, 14 Windows code page, 6 Text input Word files Numerical, 25 Multi-language, 29 TrueType fonts, 9 Unicode, 10 Generating target language texts (TX2) Commissioning Manual, 11/2006, 6FC5397-0DP10-0BA0...
Page 641 Commissioning a system Configuring the system Install software and updates SINUMERIK Backing up and restoring data SINUMERIK 840D sl PCU-Basesoftware (IM8) Service and diagnostics List of Abbreviations Commissioning Manual Valid for: PCU-Basesoftware version 8.6 03/2009 6FC5397-1DP10-4BA0...
Page 642 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 643 Configuration of the SITOP UPS module ..................48 2.4.3 Configuration for exiting the HMI ....................51 Install software and updates ........................53 Installing SINUMERIK products ....................53 Installation via service desktop ....................54 How to install and authorize SIMATIC STEP 7................57 How to install additional languages under Windows XP (DVD)...........59...
Page 644: Table Of Contents
Table of contents Backing up and restoring data ......................... 61 Backing up and restoring data ....................61 4.1.1 How to create a service system for PCU ..................61 4.1.2 Starting ServiceCenter Backup Restore ..................63 4.1.3 Select service task ........................65 4.1.4 How to backup and restore local partitions .................
Page 645 Delivery condition of the system Overview The high-performance SINUMERIK PCU 50.3 has onboard interfaces for communicating via Ethernet, MPI and PROFIBUS DP. The integrated free slots remain free for other tasks. The PCU 50.3 is equipped with the Windows XP ProEmbSys operating system and for data backup tasks with the Symantec Ghost software.
Page 646 Commissioning a system 1.1 Delivery condition of the system Supplied software on the PCU The software installed on delivery of the PCU includes the components below, among others: MS Windows XP Professional SP2 Internet Explorer V 6.0 MPI driver V 6.03 Symantec Ghost (default) V 8.2 (incl.
Page 647 The partition names EMERGENCY, TMP, SYSTEM, USER must not be changed; otherwise the "ServiceCenter" will no longer function. See also Installing SINUMERIK products (Page 53) Starting ServiceCenter Backup Restore (Page 63) 1.1.2 System features...
Page 648 "Start" → "Settings" → "Control Panel" → "System", "Computer Name" tab. Pre-configuration of the PCU The PCU 50.350.3 has two Ethernet interfaces that are suitably preset with the SINUMERIK solution line for connecting to the system network. Eth 1 is preset as a default DHCP client for connection to a company network.
Page 649 "Power User" Operator auduser SUNRISE HMI+Service Administrators local administrator System administrators siemens ***** System administrators The individual user types differ in terms of their main tasks: User type Task card Boot up of the PCU HMI (operator.group) • Operating the HMI program •...
Page 650 Commissioning a system 1.2 User administration Service Desktop The service desktop provides the HMI+Service user with a Windows desktop, which is expanded to include tools and functions for service tasks, such as manage users, install software, save/restore data, check system integrity, etc. Windows desktop The HMI user is able to use a Windows desktop which can be expanded to suit his or her individual needs.
Page 651 Commissioning a system 1.2 User administration "Startup (1)" tab Figure 1-2 Global Settings: Startup (1) tab Table 1- 1 The default is marked in "bold". Startup (1) tab Option Effect Background Bitmaps folder: F:\hmi_adv\ib\data\10700\0 Directory with boot screens Default bitmap folder: F:\hmi_adv\ib\data\default Directory containing default boot screens Installing...
Page 652 Commissioning a system 1.2 User administration Startup (1) tab Option Effect Authentication: "manual" Authentication of an HMI+Service user in the "Service Logon" dialog is undertaken manually. "EKS" Authentication of an HMI+Service user in the "Service Logon" dialog involves EKS. The "Service Logon" dialog appears if authentication by EKS has failed in the background.
Page 653 Commissioning a system 1.2 User administration Startup (2) tab Option Effect "yes" The password is not case-sensitive. Authentication: "manual" Authentication with user name and password (manual) "EKS" Authentication with EKS "manual+EKS" Either authentication with user name and password or with EKS "HMI"...
Page 654 Commissioning a system 1.2 User administration "Desktop" tab Figure 1-5 Desktop tab Table 1- 4 The default is marked in "bold". "Desktop" tab Option Effect Enable: "no" Dialog: Do not display "Desktop Access" dialog (default setting: for HMI user) "yes" Dialog: Display "Desktop Access"...
Page 655 Commissioning a system 1.2 User administration Principle of passing on The settings made under "Global Settings" are passed on to individual users. The settings which are passed on can still be adapted to suit each user. Example: "HMI (user.group)" user type Figure 1-6 Settings for the "HMI (user.group)"...
Page 656 Commissioning a system 1.2 User administration 1.2.3 How to create a new user Overview As an HMI+Service user, you can execute the following tasks in the Users ServiceCenter: ● Create new users. ● Delete users. ● Change user names. ● Add users from a domain. Creating new users To create a new user: 1.
Page 657 Commissioning a system 1.2 User administration Deleting users To delete a user again, follow these steps: 1. Left or right-click the user who you wish to delete in the list. 2. To delete the user, select "Delete" from the pop-up menu. Result: The user is deleted with a confirmation prompt.
Page 658 Commissioning a system 1.3 Boot up behavior of the PCU Boot up behavior of the PCU 1.3.1 Service dialogs during boot up Selection when booting up The following dialogs are shown during boot up: ● "Service Logon" dialog This dialog is displayed if an "Install" directory is found on a bootable storage medium (e.g.
Page 659 Commissioning a system 1.3 Boot up behavior of the PCU ● "Desktop Access" dialog – This dialog is displayed either if no HMI program is installed or if HMI program startup is deactivated during booting. Displaying this dialog can be suppressed through configuration in the global or user settings.
Page 660 Commissioning a system 1.3 Boot up behavior of the PCU ● "Desktop Logon" dialog The "Desktop Logon" dialog enables the user to log on to the desktop. This dialog also appears – If no valid user data has been provided by the authentication system (EKS). –...
Page 661 Commissioning a system 1.3 Boot up behavior of the PCU 1.3.2 Boot up of the PCU: no HMI program installed Requirement No HMI program is installed during the PCU boot up. Ramp-up phase Figure 1-11 PCU bootup diagram (without HMI program) PCU-Basesoftware (IM8) Commissioning Manual, 03/2009, 6FC5397-1DP10-4BA0...
Page 662 Commissioning a system 1.3 Boot up behavior of the PCU Explanations: ● If installation programs are present in directory D:\Install, you will be prompted during the first boot up as to whether the installation procedure should be started. After installation is completed, you need to restart the system.
Page 663 Commissioning a system 1.3 Boot up behavior of the PCU Ramp-up phase Figure 1-12 PCU bootup diagram (HMI program installed) Explanations: ● If the HMI program is already installed, the PCU boots up and the HMI program is started (default). ●...
Page 664 Overview The system behavior during boot up for the screen resolution is set in the file tcu.ini. You will find the delivery status for tcu.ini in E:\siemens\system\etc. Modified tcu.ini files are saved in F:\addon_base\..., F:\oem_base\..., F:\user_base\... Reference: Operator Components Manual, "Networking" chapter Set the resolution when booting up the PCU The following options are available in the # RESOLUTION section in the tcu.ini:...
Page 665 The resolution is set to the max. resolution of the PCU monitor, reduced to the next lowest SINUMERIK resolution. The SINUMERIK resolutions are 640x480, 800x600, 1024x768 and 1280x1024. Example: In the case of a PCU monitor with a max. resolution of 1440x900, the SINUMERIK resolution setting is 1280x1024.
Page 666 The resolution is set to the max. resolution of the PCU panel (max. 1280x1024). 640X480 During boot up, the SINUMERIK resolution is set to 640x480. 800X600 During boot up, the SINUMERIK resolution is set to 800x600. 1024X768 During boot up, the SINUMERIK resolution is set to 1024x768.
Page 667 Commissioning a system 1.4 BIOS settings BIOS settings Overview The BIOS of the PCU 50.3 is preset in such a way that no changes are required. The date and time can be set under Windows or the HMI operator interface. NOTICE Your device configuration is preset for working with the software supplied with the unit.
Page 668 Commissioning a system 1.4 BIOS settings BIOS setup: Defaults The following system parameters are saved on delivery: Menu: Main System parameters Defaults Custom entries System Time hh:mm:ss System Date MM/DD/YYYY IDE Channel 0 Master None IDE Channel 0 Slave None SATA Port 0 40008 MB SATA Port 1...
Page 669 Commissioning a system 1.4 BIOS settings Menu: Advanced System parameters Defaults Custom entries Installed O/S Other Reset configuration data Legacy USB support Disabled USB controller restart Enabled I/O Device Configuration Internal COM 1 Enabled Base I/O address Interrupt IRQ 4 PCI Configuration PCI device slot 1 Option ROM scan...
Page 670 1: SATA0: Fujitsu MHT2040BHTBD 2: PCI BEV: VIA BootAgent Excluded from boot order: Menu: Version System parameters Defaults SIMATIC PC SINUMERIK PCU50.3 BIOS version V05.01.06 BIOS number A5E00370214-ES005 MPI/DP firmware CPU type Celeron ® M processor 1.50GHz CPU ID 06D8...
Page 671 Commissioning a system 1.4 BIOS settings 6. Press <ESC> (<Alarm Cancel> key) to go to the "Exit" menu (or press the right cursor key again). 7. Press the <Enter> key to exit the setup menu. Then the system powers up. Note Changes to the BIOS settings, with the exception of the boot sequence, require an OEM contract to be concluded.
Page 672 Commissioning a system 1.4 BIOS settings PCU-Basesoftware (IM8) Commissioning Manual, 03/2009, 6FC5397-1DP10-4BA0...
Page 673 Configuring the system System settings 2.1.1 How to change the name of the PCU Default The PCU is supplied with an automatically generated computer name. Procedure To change the name of the PCU: 1. Select "Start" → "Control Panel" → "System". 2.
Page 674 Configuring the system 2.1 System settings 2.1.2 How to set the IP address of the PCU 50.3 Default NOTICE The IP address 192.168.214.241 is set as a factory default for every PCU 50.3 on the system network. You must only perform the steps described below if you wish to change this default. Procedure 1.
Page 675 Configuring the system 2.1 System settings 4. Under the "General" tab, select the "Use the following IP address" option and enter the IP address and the subnet screen form. Recommended setting for the first PCU: 5. Enter the required new IP address and confirm the settings with "OK". 2.1.3 How to add the PCU to a domain Requirement...
Page 676 Configuring the system 2.1 System settings Proceed as follows To add the PCU to a domain: 1. Select: "Start" → "Settings" → "Control Panel" → "System", "Computer Name" tab. Default: The PCU belongs to a "WORKGROUP" and is not assigned to any domain. 2.
Page 677 Configuring the system 2.1 System settings 2.1.4 How to connect an external monitor Conditions To connect an external monitor, the following conditions apply: ● The external monitor is connected to the DVI interface on the PCU (using an adapter, if necessary).
Page 678 In order to be able to switch languages, the desired languages must be installed from the DVD of the "SINUMERIK Service Pack Recovery Media Win XP ProEmbSys SP2". With the "Multilingual User Interface" (MUI), you can switch to menus, dialogue boxes and keyboard...
Page 679 Configuring the system 2.2 Configuring a customized operator interface 2. Choose the "Languages" tab, in order to switch the language for the Windows XP operator interface. Under "Language used in menus and dialogues," choose the new language and confirm with OK. 3.
Page 680 2.2.2 Storage location of HMI boot screen Default setting The Siemens boot screens are stored under the path below on the appropriate PCU, e.g., for the SINUMERIK 840D sl controller: F:\hmi_adv\ib\DATA\10700\0\<Resolution>\10700_0.bmp A directory tree can also be created for manufacturer-specific boot screens. The...
Page 681 Overview A background pattern for the service desktop is not set via the "Control Panel" (system control), but in the registry: ● Background pattern: Key: HKLM\SOFTWARE\Siemens\SINUMERIK\Basic software\ <version>\HMI desktop Value: Pattern (STRING) Date: <bit code>” (e.g., “0 80 114 32 0 5 39 2”, see HKCU\Control Panel\Patterns) “(None)”...
Page 682 Configuring the system 2.3 Customized settings during boot up Customized settings during boot up Overview If an HMI program, e.g. HMI Advanced, is to be started following boot up, the settings and functionality differ from those that apply if the service desktop is to be started. 2.3.1 Configuring key filters for an HMI program Filtering keys...
Page 683 This behavior can be changed by making an entry in the registry. The following settings can be saved via this registry entry: ● Positions of open windows ● Size and position of the task bar ● Moving and deleting links Key: HKLM\SOFTWARE\Siemens\SINUMERIK\Basic software\ <version>\HMI Manager Value: SaveSINDesktopSettings (DWORD) Date: 1 (the settings are saved) or...
Page 684 Windows when the service desktop is opened. This start in parallel to the HMI program can be configured. If the programs to be started are located in the Windows directories of E:\Documents and Settings, the following registry entry must be set: Key: HKLM\SOFTWARE\Siemens\SINUMERIK\Basic software\ <version>\HMI Manager Value: StartSINHMIStartupDirsPrograms (DWORD) Date:...
Page 685 Configuring the system 2.3 Customized settings during boot up 2.3.4 Starting OEM programs Overview You can start OEM programs directly before starting the HMI system software. This requires these programs (or their links) to be stored in subdirectories of the directory C:\RunOEM. Starting sequence The subdirectories are executed in the order listed.
Page 686 ● HMI Advanced of V07.01.00 or higher ● SITOP software, version 2.5.2.4or higher is installed: SITOP software is available to download from: www.automation.siemens.com/sitop. ● SITOP monitor/configuration program is installed: To enable this, the SITOP software must be copied to the E:\SITOP directory set up on the PCU.
Page 687 Configuring the system 2.4 PCU 50.3 with SITOP UPS module 2.4.1 Starting and configuring the SITOP monitor Windows boot up The SITOP monitor has to be started by Windows automatically during booting. A new value has to be entered for the SITOP monitor under the key below in the Windows registry: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run ValueName: SITOP ValueType: REG_SZ...
Page 688 Configuring the system 2.4 PCU 50.3 with SITOP UPS module Parameterization of the SITOP monitor Enter the path of the program that ensures that HMI Advanced and the PCU shut down properly in the event of a power failure into the parameter area of the buffer. E:\SITOP\Shutdown.bat Figure 2-4 Configuration of the SITOP monitor: Buffering settings...
Page 689 Configuring the system 2.4 PCU 50.3 with SITOP UPS module Required settings on the UPS module (USB interface) On - Off Cut-in threshold +22V (fixed) +0.5V End-of-charge voltage +0.5V + 26.3V fixed +0.2V +0.2V +0.1V 0.35A / 0.7A Charging current On - Off Set time/max.
Page 690 Configuring the system 2.4 PCU 50.3 with SITOP UPS module “Fixed buffer time” mode In this mode, the UPS module always buffers for the pre-selected, fixed period of time. It is not possible to synchronize the UPS module with the operating system shutdown. Required settings on the UPS module On - Off Cut-in threshold...
Page 691 Configuring the system 2.4 PCU 50.3 with SITOP UPS module 2.4.3 Configuration for exiting the HMI HMI monitoring Exiting of the HMI advanced is monitored by a separate application, hmiexit.exe. This application is started implicitly via the shutdown.bat batch file. In case of error, the application forces the operating system to shut down.
Page 692 Configuring the system 2.4 PCU 50.3 with SITOP UPS module PCU-Basesoftware (IM8) Commissioning Manual, 03/2009, 6FC5397-1DP10-4BA0...
Page 693 Install software and updates Installing SINUMERIK products Overview This chapter describes how to install additional software on the basis of the pre-installed PCE basic software or how to carry out an update. The description below is based on the delivery condition of the hardware and software components.
Page 694 Install software and updates 3.2 Installation via service desktop Installation via service desktop Installing additional software The service desktop makes it possible to install system software or a software update. This mostly affects installation/update packages that are to be installed via the Windows network. Installation can be performed in two ways: ●...
Page 695 SINUMERIK product. ● Language of the product The "Language" dialogue box lists the installed languages for the respective SINUMERIK product and provides information on the name of the installed language. If the language is not known, an abbreviation of its name is displayed. Known languages of HMI Explorer are German, English, Spanish, French and Italian.
Page 696 3.2 Installation via service desktop ● History of the product The "History" dialogue box shows information on the history of the SINUMERIK product. This dialogue box gives information on the release version, any service packs and hot fixes. The "release" entry is always available. The entries for "service pack" and "hot fix"...
Page 697 4. The prompt for "Transfer license keys" must be answered with "No, transfer the license keys later." The licensing is done after the installation of SINUMERIK add-on. Once installation is complete, the PC will need to be rebooted. During boot up, select the service desktop again.
Page 698 Install software and updates 3.3 How to install and authorize SIMATIC STEP 7 The following entries are made automatically in F:\Add_on\oemframe.ini: [s7tgtopx] ; with HMI Advanced: eliminate minimize/maximize buttons ; of the Step7 window WindowStyle_Off=196608 ; with HMI Advanced: switch to previous task when Step7 is terminated nSwitchToTaskAfterTermination= -2 These entries may also need to be modified in OEM configurations.
Page 699 3.4 How to install additional languages under Windows XP (DVD) How to install additional languages under Windows XP (DVD) Use the SINUMERIK service pack recovery Media WIN XP ProEmbSys SP2 to: ● Subsequently install Windows components ● Re-establish the delivery condition of the PCU without HMI Advanced ●...
Page 700 Install software and updates 3.4 How to install additional languages under Windows XP (DVD) Installing languages To install additional languages, proceed as follows: 1. If no DVD drive is directly connected via a USB port, the DVD can be accessed via a network to a released DVD disk drive via "Explorer"...
Page 701: Backing Up And Restoring Data
Backing up and restoring data Backing up and restoring data Overview The entire contents of hard disks can be saved as a disk image using the Symantec Ghost utility. These disk images can be stored on various storage media and the data restored to the hard disk at a later date.
Page 702 Backing up and restoring data 4.1 Backing up and restoring data Booting up the service system 1. Plug the EBS into one of the rear USB ports of the PCU 50.3. 2. Press the <ALARM CANCEL> key on the operator panel or the <ESC> key on an external keyboard while the BIOS of the PCU is booting up in order to display the "Boot Menu".
Page 703: Starting Servicecenter Backup Restore
● Backing up/restoring data – Starting via linking from the service desktop – Starting during boot up via entry in the "background" under SINUMERIK ● From the service system in the event of service ● When installing a replacement hard disk In order to ensure that the user is authorized to carry out service tasks, direct access is password-protected during boot up of the PCU.
Page 704 Backing up and restoring data 4.1 Backing up and restoring data Network settings 1. To connect the PCU to a programming device or PC, choose "Settings" in order to check or reset the set IP addresses. 2. Select "Use Windows settings", to keep the factory defaults. (This is the default here as well.) Figure 4-2 Network settings...
Page 705: Select Service Task
Backing up and restoring data 4.1 Backing up and restoring data See also System features (Page 7) 4.1.3 Select service task Selecting the service task After start-up of the ServiceCenter, the following dialog opens: Figure 4-3 ServiceCenter Selection Select from the following service tasks: ●...
Page 706: How To Backup And Restore Local Partitions
Backing up and restoring data 4.1 Backing up and restoring data Network Settings With "Network Settings," you open the dialogue box for network settings. Launch Program To start a program in service mode, enter the program name here, e.g. "cmd" for starting a DOS shell.
Page 707: How To Backup And Restore The Hard Disk
Backing up and restoring data 4.1 Backing up and restoring data Restoring partitions Select the "Restore" action from "Backup/Restore a local Partition Image" to restore an image of one or more C, E, and F partitions locally from the D:\Images partition: Restore the Rollback Image To restore the most recently saved image, namely the current image ("Rollback Image"), select "Restore the Rollback Image".
Page 708 Backing up and restoring data 4.1 Backing up and restoring data 3. To receive access rights, enter a user name and password. Figure 4-6 Drive Connection 4. Under "Options," select whether the disk image that is to be created is divided into several files of a certain size, so that these files can fit on one CD.
Page 709: Restoring System Data From "Emergency Image
Backing up and restoring data 4.1 Backing up and restoring data 4.1.6 Restoring system data from "Emergency Image" Restoring system data Select "Restore the Emergency Image", to restore the emergency image. This image must contain the back-up of partition E and can also contain a back-up of partitions C, D or F. It is provided in the event that only the system on partition E: is defective.
Page 710: Saving The Hmi Advanced Environment
Saving the HMI Advanced environment Setting the original SINUMERIK HMI environment The "Original SINUMERIK HMI Environ" function is available as a script file on the service desktop. The original delivery condition is set up, i.e., the contents of the directories below are saved, when this function is executed: ●...
Page 711: Operating The Service Pc Or The Pg On The Network
Backing up and restoring data 4.3 Operating the service PC or the PG on the network Operating the service PC or the PG on the network Applications For the following applications, you will, for example, need a connection in the system network between the PCU and a PG/PC: ●...
Page 712 Backing up and restoring data 4.3 Operating the service PC or the PG on the network Configuration with PG/PC and switch to PCU Figure 4-8 Connecting a PG via a switch to a PCU Note If a PCU is switched off and on again without its own OP/TP including TCU, and if the PCU boot-up is supposed to take place from the service system (EBS), an external VGA monitor and keyboard are needed in order to operate the PCU.
Page 713: How To Connect A Pc/Pg To A Pcu Within The System Network
Backing up and restoring data 4.3 Operating the service PC or the PG on the network See also How to backup and restore the hard disk (Page 67) 4.3.2 How to connect a PC/PG to a PCU within the system network Settings on a PG/PC with Windows XP On a PG/PC, the following settings must be made: 1.
Page 714 255.255.255.0. 4. Select "Control Panel" → "System" → "Computer Name" tab to view the computer name of the PCU: e.g. SIEMENS-ABC4711 5. Select "Control Panel" → "Folder Options" → "View" and activate "Use simple file sharing (Recommended)", to avoid problems with the release of the directory.
Page 715 Backing up and restoring data 4.3 Operating the service PC or the PG on the network Releasing directory for network access (Windows XP) 1. Create a directory on a local drive; e.g. D:\PCU_Backup 2. Using the right mouse key, open the "Properties" dialogue box of the directory and the "Sharing"...
Page 716 255.255.255.0 1. In the ServiceCenter, select the service task "Backup/Restore a Disk Image". 2. Establish a network connection to the released directory, e.g. \\SIEMENS- ABC4711\PCU_Backup. 3. Restore the hard disk of the PCU using the ghost image.
Page 717: How To Connect A Pc/Pg To An Ncu Within The Company Network
Backing up and restoring data 4.3 Operating the service PC or the PG on the network 4.3.3 How to connect a PC/PG to an NCU within the company network Add route ... in WINPE This function is required for the following application: Backing up/restoring ghost images Example configuration Figure 4-9 Network routing...
Page 718 Backing up and restoring data 4.3 Operating the service PC or the PG on the network Procedure Activate routing prior to establishing the network connection: 1. Press the "Add Route ..." button. Figure 4-10 ServiceCenter Backup-Restore 2. Establish the network connection using "Add Network Drive ...". In the example: \\192.168.215.2\<sharename>...
Page 719 Backing up and restoring data 4.3 Operating the service PC or the PG on the network 3. Logon and password details for a local user on the PG: Figure 4-12 ServiceCenter: Add Network Drive 4. Define the computer name as an IP address; you cannot give it your own name. Share access to a directory or to the CD or DVD drive on the PG/PC must have been enabled.
Page 720: Commissioning The Replacement Hard Disk
● Ethernet 1 (Company Network) as a standard DHCP client ● Ethernet 2 (System Network) as a SINUMERIK DHCP server with the fixed IP address 192.168.214.241 and subnet screen 255.255.255.0 The PCU must therefore be disconnected from the system network before the replacement hard disk is fitted.
Page 721: Service And Diagnostics
The PLC interface of HMI Advanced is located in DB 10 of the PLC program and is supplied by the PCU hardware monitor in the event of a failure. See also Description of the alarms: Diagnostics Manual SINUMERIK Operator Components and Networking Manual: Chapter PCU 50.3, spare parts Commissioning the replacement hard disk (Page 80)
Page 722: Evaluating 7-Segment Display
Service and diagnostics 5.2 Evaluating 7-segment display Evaluating 7-segment display Purpose The 7-segment display is intended for initial diagnosis of the PCU 50.3 during operations without a local OP (known as "Headless mode"). If an error is detected during booting, a local display is needed for subsequent error analysis of the connection.
Page 723 Service and diagnostics 5.2 Evaluating 7-segment display LED H1 LED H2 7-segment Status display TCU support test Wait for VNC server to start step 3 HMI manager Wait for HMI manager to start ● During operation: LED H1 LED H2 7-segment Status display...
Page 724: Enabling/Disabling Error Log During Boot Up
InfoLevel <= 3 is treated as InfoLevel == 3) ● Outputting information to the screen Whether the information is also to be displayed on the screen (as well as being output to the log file) is set via registry value 'HKLM\SOFTWARE\Siemens\SINUMERIK\Basic software\<version>\HMI Manager\ShowInfo': ShowInfo (DWORD)
Page 725: How To Search For Stations Within The System Network
Service and diagnostics 5.4 How to search for stations within the system network How to search for stations within the system network Intended use The VNC scanner is used within the system network. The scanner is primarily used to identify devices containing an active VNC server, e.g. NCUs or PCUs. The VNC scanner offers the option of connecting directly to the VNC server and, for example, operating an HMI application.
Page 726 Service and diagnostics 5.4 How to search for stations within the system network 2. "IP start / IP end": Set the IP-address browsing range. Eight ranges can be saved. Click on button " >" to switch to the next range. 3.
Page 727 Service and diagnostics 5.4 How to search for stations within the system network 5. By right-clicking a network station from the list, you can execute the following actions via a pop-up menu: – "VNC": Connecting directly to the VNC server and, if applicable, operating the HMI. –...
Page 728 Service and diagnostics 5.4 How to search for stations within the system network ● VNC scanning algorithm: Default is "Fast", i.e. device feedback within approximately 100 ms ● Devices detection: (corresponds to the "VNC" option, see point 3). – "VNC server devices": only search for VNC servers. –...
Page 729 Service and diagnostics 5.4 How to search for stations within the system network After clicking the "Options ..." button, the following dialog opens: Figure 5-6 Default: Connection Options ... PCU-Basesoftware (IM8) Commissioning Manual, 03/2009, 6FC5397-1DP10-4BA0...
Page 730: Openssh For Winscp And Putty
Service and diagnostics 5.5 OpenSSH for WinSCP and PuTTY OpenSSH for WinSCP and PuTTY Intended use The service tools WinSCP and PuTTY are already used to access NCU 7x0. They can now similarly be used to access the PCU50. Default The user "auduser"...
Page 731: List Of Abbreviations
List of Abbreviations Abbreviations CompactFlash card: Memory card Direct Control Keys Direct control key Device Control Protocol DHCP Dynamic Host Configuration Protocol: Dynamic assignment of an IP address and other configuration parameters on a computer in a network Domain Name System: Conversion of domain names into IP addresses Emergency Boot System Electronic Key System: System to check the identity of a user (authentication system) EUNA...
Page 732 List of Abbreviations A.1 Abbreviations User Datagram Protocol: NTP is mostly processed via UDP. Universal Serial Bus Uninterruptible power supply Universal Time, Coordinated Coordinated universal time Virtual Network Computing PCU-Basesoftware (IM8) Commissioning Manual, 03/2009, 6FC5397-1DP10-4BA0...
Page 733: Index
Index 7-segment display, 82 Global Settings, 10 Access level, 20 HMI monitoring, 51 Activating the firewall, 7 Mains-fed operation, 54 Backup time, 48 Multilingual User Interface (MUI), 59 Backup/Restore Disc image, 67 Partition image, 66 Rollback image, 67 Network settings, 64 BIOS NTFS file system, 6 Changing default setting, 30...
Page 734 Index Select language (MUI), 38 Service Desktop Background, 41 install, 54 starting, 63 Service system for PCU, 61 Service tasks, 65 Shutdown, 83 SIMATIC STEP 7 Installing, 57 SITOP Monitor Configure, 47 Parameterizing, 48 Software Components, 6 install, 53 Starting OEM programs, 45 Starting ServiceCenter, 63 System boot, 82 UPS module (SITOP), 46...
Page 735 This document will be continuously improved with regard to its quality and ease of use. Please help us with this task by sending your comments and suggestions for improvement via e-mail or fax to: E-mail: mailto:docu.motioncontrol@siemens.com Fax: +49 9131 - 98 2176 Please use the fax form on the back of this page.
Page 736 Appendix A.1 Feedback on the documentation Base software and HMI Advanced Commissioning Manual, 03/2009, 6FC5397-0DP10-3BA0...

Siemens SINUMERIK Commissioning Manual

Quick Links

Related Manuals for Siemens SINUMERIK

Summary of Contents for Siemens SINUMERIK

Table of Contents