Page 1 Preface Safety information Installation SINUMERIK Create MyConfig - Diff SINUMERIK 840D sl / 828D SINUMERIK Integrate Create Create MyConfig - Expert MyConfig - Diff, Expert, Topo Create MyConfig - Packages Operating Manual Create MyConfig - Topo Create MyConfig - NcuShare...
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
In contrast to the conventional procedure, individual operations on the machine can be performed faster and with greater ease and reliability. ● The production time for machines with SINUMERIK 840D sl respectively SINUMERIK 828D is significantly reduced. ● The upgrade time for end customers is also reduced.
Page 4 Shield according to the configuration. Training For information about the range of training courses, refer to: ● SITRAIN (www.siemens.com/sitrain) - training courses from Siemens for automation products, systems and solutions FAQs You can find Numerical control on the Service&Support pages under Product Support (www.siemens.com/automation/service&support).
Page 5: Table Of Contents
Table of contents Preface.................................3 Safety information............................13 Fundamental safety instructions....................13 1.1.1 General safety instructions.....................13 Industrial security........................14 Installation..............................15 Overview..........................15 Installation via command line....................15 2.2.1 Structure of the "OPFILE.txt" control file................15 2.2.2 Command line call........................17 2.2.3 Modifying installed program parts..................18 Create MyConfig - Diff ..........................21 Safety instructions........................21 3.1.1 Fundamental safety instructions....................21...
Page 6 Converting projects from older CMC versions..............102 4.2.4.1 Conversion...........................102 4.2.4.2 Rules for adapting the syntax....................102 4.2.4.3 Changes to system variables....................104 System support........................105 4.3.1 Differences during commissioning between SINUMERIK 840D sl and SINUMERIK 828D..105 4.3.2 Support CU320........................106 Project folder........................106 4.4.1 Package..........................106 4.4.2 Dialogs..........................111 4.4.2.1 Dependency of the dialog pages on data areas..............114...
Page 7 Table of contents 4.4.2.14 NCU/PPU access (configuration)..................139 4.4.2.15 NCU/PPU access (package execution)................141 4.4.2.16 NCU/PPU initial state (configuration)...................142 4.4.2.17 NCU/PPU initial state (package execution)................145 4.4.2.18 Notes on GSP (configuration)....................146 4.4.2.19 Notes on GSP (package execution)..................148 4.4.2.20 Service Platform Industry (GSP) (configuration)..............149 4.4.2.21 Service Platform Industry (GSP) (package execution)............153 4.4.2.22...
Page 8 Table of contents 4.6.7 Area data..........................249 4.6.8 Check structures........................250 4.6.8.1 If control structure / If-Else control structure................250 4.6.8.2 If-ElsIf control structure / If-ElsIf-Else control structure............251 4.6.8.3 While check structure......................252 4.6.9 Operators..........................253 4.6.9.1 Overview operators......................253 4.6.9.2 Assignment operators......................253 4.6.9.3 Arithmetic operators......................254 4.6.9.4 Logic operators / comparison operators................255 4.6.9.5...
Page 9 Table of contents 4.7.3.6 System variables for the NCU/PPU access dialog...............288 4.7.3.7 System variables for the NCU/PPU initial state dialog............289 4.7.3.8 System variables for the Notes on the Service Platform Industry (GSP) dialog....290 4.7.3.9 System variables for the Service Platform Industry (GSP) dialog........290 4.7.3.10 System variables for the CNC software dialog..............290 4.7.3.11...
Page 10 Table of contents 4.12.2 Package execution.......................337 4.13 SINAMICS device configuration...................339 4.13.1 Production of modular machines..................339 4.13.2 SINAMICS device configuration with Automatic configuration or user-specified topology..340 4.13.3 Drive data generation via "automatic configuration"............342 4.13.4 Drive data generation via "user-specified topology".............342 4.13.5 Assignment of the drive data using DO variables..............343 4.13.6 The advantages of using comparison or user-specified topology........346...
Page 11 Table of contents Extended user-specified topology..................391 Axis-drive assignment......................393 6.8.1 Configuration........................393 6.8.2 Execution..........................395 6.8.3 Diagnostics...........................398 Interface Topo XML......................400 6.9.1 Example for displaying the wiring using an XML image............400 6.9.2 Description of the XML structure..................402 6.9.3 XSD for XML-interface......................405 Create MyConfig - NcuShare........................417 Introduction..........................417 7.1.1 NcuShareService.........................417...
Page 12 Table of contents SINUMERIK Integrate Create MyConfig - Diff, Expert, Topo Operating Manual, 11/2016, A5E36537479B-AD...
Page 13: Safety Information
Safety information Fundamental safety instructions 1.1.1 General safety instructions WARNING Danger to life if the safety instructions and residual risks are not observed If the safety instructions and residual risks in the associated hardware documentation are not observed, accidents involving severe injuries or death can occur. ●...
Page 14: Industrial Security
Siemens’ products and solutions undergo continuous development to make them more secure. Siemens strongly recommends to apply product updates as soon as available and to always use the latest product versions. Use of product versions that are no longer supported, and failure to apply latest updates may increase customer’s exposure to cyber threats.
Page 15: Installation
Installation Overview You have two options for installing the Create MyConfig engineering software and the NcuShareService application on your PC: ● Installation using the installation wizard Installing the Create MyConfig setup as usual by running the setup file and by manually working through the setup dialogs.
Page 16 \Create MyConfig 4.7" A default installation path is used if a value is not entered. Under a 32-bit Windows operating system, for example, the path is "\Program Files\Siemens\Create MyConfig 4.7" This parameter is ignored if CMC components are already installed.
Page 17: Command Line Call
Installation 2.2 Installation via command line Note In addition to the setup file, the commented template "OPFILE.txt" is also stored, which can be adapted and used accordingly. Example of the "OPFILE.txt" control file for installation with standard settings [SETUPREQUESTS] SetupMode=Batch 2.2.2 Command line call Syntax for the command line call...
Page 18: Modifying Installed Program Parts
Installation 2.2 Installation via command line Example of a call for an English installation and OPFILE.txt in the setup folder setup.exe /W /L1033 /V"commandline=\”\”\”-OF:OPFILE.txt\”\”\”” Example of a call for a German installation and OPFILE.txt with absolute path data setup.exe /W /L1031 /V"commandline=\”\”\”-OF:D:\mySetupConfiguration \OPFILE.txt\”\”\””...
Page 19 Installation 2.2 Installation via command line These three versions can be combined. For example, this means you can first use version 1, for a subsequent change, version 3, and later, for a new change, version 2. SINUMERIK Integrate Create MyConfig - Diff, Expert, Topo Operating Manual, 11/2016, A5E36537479B-AD...
Page 20 Installation 2.2 Installation via command line SINUMERIK Integrate Create MyConfig - Diff, Expert, Topo Operating Manual, 11/2016, A5E36537479B-AD...
Page 21: Create Myconfig - Diff
Create MyConfig - Diff Safety instructions 3.1.1 Fundamental safety instructions 3.1.1.1 General safety instructions WARNING Danger to life if the safety instructions and residual risks are not observed If the safety instructions and residual risks in the associated hardware documentation are not observed, accidents involving severe injuries or death can occur.
Page 22: Industrial Security
Siemens’ products and solutions undergo continuous development to make them more secure. Siemens strongly recommends to apply product updates as soon as available and to always use the latest product versions. Use of product versions that are no longer supported, and failure to apply latest updates may increase customer’s exposure to cyber threats.
Page 23: Introduction
The contents for the Diff section are identical in the operating manual and the online help. Diff is software for displaying and comparing folders, SINUMERIK archives, general files and special files of the SINUMERIK 840D sl control. With Diff, SINUMERIK archives can also be modified and stored.
Page 24: Sinumerik Archive Comparison
Create MyConfig - Diff 3.3 SINUMERIK archive comparison SINUMERIK archive comparison 3.3.1 General information on the SINUMERIK archive comparison Any number of comparison objects (SINUMERIK archives or Sub files) can be imported, displayed and compared in a SINUMERIK archive comparison. The comparison is realized at the data level.
Page 25: Overview Of User Interface
Create MyConfig - Diff 3.3 SINUMERIK archive comparison 3.3.2 Overview of user interface 3.3.2.1 SINUMERIK archive comparison - Toolbar ① New SINUMERIK archive comparison ② New folder comparison ③ New file comparison ④ Update comparison ⑤ Display/save HTML/XML protocol ⑥ Comparison configuration ⑦...
Page 26 Create MyConfig - Diff 3.3 SINUMERIK archive comparison ④ Update comparison The button for updating the comparison is always shown in color if the displayed comparison result is not a current result and the comparison should be restarted using this button. Note Depending on the comparison situation, the comparison is automatically started by Diff in some cases.
Page 27 Create MyConfig - Diff 3.3 SINUMERIK archive comparison ⑫ Selection of the comparison objects Select archive or file for SINUMERIK archive comparison The last opened archives or files are listed. Close archive or file. Button to save a modified archive. ⑬...
Page 28: Sinumerik Archive Comparison - Overview Window
Create MyConfig - Diff 3.3 SINUMERIK archive comparison 3.3.2.2 SINUMERIK archive comparison - Overview window In the following, you find an overview of the functions in the SINUMERIK archive comparison window. ① Data view tab ② Folder view tab ③ Editing mode ④...
Page 29 Create MyConfig - Diff 3.3 SINUMERIK archive comparison ⑦ Expert list and filter configurations ⑧ Display of the comparison configuration ⑨ Context menu ⑩ A brief description of the selected parameter is displayed in the text area with yellow background. ⑪...
Page 30 Create MyConfig - Diff 3.3 SINUMERIK archive comparison The equal character in the end node indicates that the data of the objects being compared is identical within this end node. The unequal character in the end node indicates that not all of the data of the objects being compared is identical within this end node.
Page 31 Create MyConfig - Diff 3.3 SINUMERIK archive comparison The identifiers are listed in the column to the far left, and in all of the additional columns, the associated values of the individual comparison objects (archives, nodes). The comparison results are color-coded to make it easier to interpret the results: Identifiers shown in black indicate that all values of the comparison object for this particular identifier are the same.
Page 32: Configuration
Create MyConfig - Diff 3.3 SINUMERIK archive comparison 3.3.3 Configuration SINUMERIK archive comparison You can call the dialog for configuration of the SINUMERIK archive comparison via the "Comparison configuration" button . You can manage the different comparison configurations (i.e. create, edit, delete, etc.) in the dialog box. In a comparison configuration, all of the criteria that should be taken into account when comparing SINUMERIK archives can be defined.
Page 33 Create MyConfig - Diff 3.3 SINUMERIK archive comparison Configurations shown in gray are user-specified configurations; these can be changed, but not deleted - and can be restored again at any time. ② Buttons for managing the configurations Configurations can be managed using these buttons. Using "Add", a new configuration is generated which can also be adapted.
Page 34 Create MyConfig - Diff 3.3 SINUMERIK archive comparison ① Using the expert list ② Import... button ③ Extracting identifiers button ④ Combining indices button ⑤ Including/excluding data with identifiers ⑥ Field listing the identifiers ① Using the expert list The use of an expert list can be activated by selecting "Use expert list". Note If an expert list is active, then all of the identifiers that have been filtered-out are not compared and are also no longer displayed.
Page 35 Create MyConfig - Diff 3.3 SINUMERIK archive comparison The first comment on the data is retained on this date. ⑤ Include/exclude data with identifiers You can define as to whether the listed identifiers and their data are included or excluded when making the comparison.
Page 36 Create MyConfig - Diff 3.3 SINUMERIK archive comparison ② Define filter, as character string or regular expression Interpret filter as: You can define whether the filter should be interpreted as String or Regular expression (see Use of regular expressions in Diff (Page 85)). Generally, the filters do not describe complete identifiers, but distinct character strings of the identifier which are sufficient to clearly identify the required quantity of identifiers.
Page 37: Copying/Exporting Data From The Sinumerik Archive Comparison
Create MyConfig - Diff 3.3 SINUMERIK archive comparison Floating point numbers are saved separately and internally in the computer in mantissa and exponent. The exponent is adapted in such a way that the mantissa is normalized, i.e. in the range of 1 <= m <...
Page 38 Create MyConfig - Diff 3.3 SINUMERIK archive comparison Example 1: Copying SINAMICS data Using the context menu entries "Copy" or "Data Export to File", you can transfer the selected values and their identifiers to the clipboard or to a file. For the selection shown, the following content is obtained for the clipboard or file: [B3_S3_PS3] ;V2.40.43.00 p45=1...
Page 39 Create MyConfig - Diff 3.3 SINUMERIK archive comparison Example 2: Copying NC axis machine data For the selection shown, the following content is obtained for the clipboard or file: CHANDATA(1) N32000 $MA_MAX_AX_VELO[AX6]=8000 N32010 $MA_JOG_VELO_RAPID[AX6]=8000 N32020 $MA_JOG_VELO[AX6]=550 N32060 $MA_POS_AX_VELO[AX6]=8000 The identifiers extracted by Diff are fully qualified, i.e. they again include the definition of the axis to which the data belongs.
Page 40: Pasting/Importing Data In The Si
Create MyConfig - Diff 3.3 SINUMERIK archive comparison For the selection shown, the following content is obtained for the clipboard (to insert in Excel) or file: Identifier 1 DO3 (3.3.3 SERVO 11) 2 DO3 (3.3.3 SERVO 11) p125 p130 p131 [0] p139 [0] p139 [1] p139 [2]...
Page 41 Create MyConfig - Diff 3.3 SINUMERIK archive comparison The data must be in the clipboard or in a file in the form "identifier=value" (copy/export format, "Value assignment"). Note The copy/export format "Value table" from Diff is not supported for paste/import. ②...
Page 42: Data Jobs In The Sinumerik Archive Comparison
Create MyConfig - Diff 3.3 SINUMERIK archive comparison When pasting/importing data, Diff searches the identifiers contained in the clipboard/file in the ① ② data nodes selected in the value column and pastes the "new" value for the identifiers found. Note ③...
Page 43: Configuring Data Jobs
Create MyConfig - Diff 3.3 SINUMERIK archive comparison Supplementary conditions for data tasks ● Data tasks are only available in the "Selective" comparison mode. ● Data tasks can only be applied to data end nodes. Application examples for data tasks ●...
Page 44 Create MyConfig - Diff 3.3 SINUMERIK archive comparison You can also export or import configurations, for instance, to provide them to other users (see Exporting and importing configurations (Page 80)). Task type tab Under the "Task type" select task types: ●...
Page 45 Create MyConfig - Diff 3.3 SINUMERIK archive comparison Template tab You can store an Excel template under the "Template" tab for the selected data task. This is required for the data conversion, but also for the data import and the data export. Diff saves this template as a fixed component of the configuration.
Page 46 Create MyConfig - Diff 3.3 SINUMERIK archive comparison Export tab The export area of the identifiers and values are specified in the Excel template under the "Export" tab. Further, a node type in the data structure tree must be specified under this tab. An export or conversion task can only be started at this node type.
Page 47: Executing Data Tasks
Create MyConfig - Diff 3.3 SINUMERIK archive comparison The description is displayed in the data task wizard when the "Display description when executed" checkbox is activated. 3.3.6.3 Executing data tasks Configured data tasks can be executed using a data task wizard. You can start a data task using the context menu at a selected data end node in the selective mode of the SINUMERIK archive comparison.
Page 48 Create MyConfig - Diff 3.3 SINUMERIK archive comparison Dialog page: Description of the data task wizard The "Description" dialog page of the data task wizard provides the description saved in the configuration and allows users to view notes. ① Identification of the active step The current step and the following or processed steps are listed in this line.
Page 49 Create MyConfig - Diff 3.3 SINUMERIK archive comparison Dialog page: Import The "Import" dialog page allows the import values - determined by the wizard from the Excel template - to be viewed. ① List of import designators/values The import identifiers from the import area of the Excel template and the associated values, which were calculated in the Excel template, are listed in this area.
Page 50 Create MyConfig - Diff 3.3 SINUMERIK archive comparison Dialog page: Summary The "Summary" dialog shows the exported and imported values on a dialog and therefore provides an overview of the conversion operation. ① Color coding of the values If, in the Excel template, no values were able to be determined for the individual identifiers, then these identifiers are shown in a bright purple color.
Page 51 Create MyConfig - Diff 3.3 SINUMERIK archive comparison After clicking the "Yes" button, the converted data can be pasted at a data node via the context menu. The "Preview pasting" dialog is displayed; this shows the value changes after the pasting. Pasting can be acknowledged –...
Page 52: Folder Comparison
Create MyConfig - Diff 3.4 Folder comparison Folder comparison 3.4.1 General information In a Folder comparison of Diff, you can compare two comparison objects with each other, insert or delete files or folders, and store the modified objects again. The comparison and display of the comparison results is realized at the folders and files level.
Page 53: Overview Of User Interface
Create MyConfig - Diff 3.4 Folder comparison 3.4.2 Overview of user interface 3.4.2.1 Folder comparison - toolbar ① Buttons forEdit mode - Synchronize - Copy ② New folder comparison Calling a folder comparison. ③ Toggling between opened comparisons (tab) ④ Update comparison ⑤...
Page 54 Create MyConfig - Diff 3.4 Folder comparison ① Edit mode - Synchronize - Copy The edit mode can be activated and deactivated using the "Edit mode" button. When the edit mode is activated, using the context menu, the following edit functions can be applied: Files and folders can be cut, copied, pasted, deleted and renamed.
Page 55 Create MyConfig - Diff 3.4 Folder comparison ⑥ Comparison configuration Using this button, a comparison configuration is changed or a different comparison configuration is selected (see Configuration (Page 60)). ⑦ Copy / Paste Buttons for copying and pasting (only in edit mode) selected folders or files of the left-hand or right-hand comparison object (see Copy from the folder comparison (Page 64)).
Page 56: Folder Comparison - Overview Window
Create MyConfig - Diff 3.4 Folder comparison 3.4.2.2 Folder comparison - overview window Below is an overview of the functions in the folder comparison window. ① Folder structure - Display of the folders with respective comparison objects in the tree structure ②...
Page 57 Create MyConfig - Diff 3.4 Folder comparison Description of the areas/functionalities in the Folder comparison window The individual functionalities of the folder comparison are described in more detail below: ① Folder structure - Display of the folders with respective comparison objects in the tree structure.
Page 58: Changing The Column Arrangement
Create MyConfig - Diff 3.4 Folder comparison Example: Specifies that there are 8 unequal files from a total of 14 in the currently selected folder. ⑤ Special features context menu The "Open", "Send to" and "Copy" entries can be used to view and extract files from archives. The entry "Open with file comparison"...
Page 59 Create MyConfig - Diff 3.4 Folder comparison Same sequence Mirrored SINUMERIK Integrate Create MyConfig - Diff, Expert, Topo Operating Manual, 11/2016, A5E36537479B-AD...
Page 60: Configuration
Create MyConfig - Diff 3.4 Folder comparison 3.4.4 Configuration Folder comparison You can call the dialog to configure a folder comparison using the "Comparison configuration" button. You can manage the different comparison configurations (i.e. create, edit, delete, etc.) in the dialog box. In a comparison configuration, all of the criteria that should be taken into account when comparing folders can be defined.
Page 61 Create MyConfig - Diff 3.4 Folder comparison ① List of the comparison configurations The existing comparison configurations are listed in this area of the configuration dialog and can be selected by clicking on them. Configurations shown in gray are user-specified configurations; these can be changed, but not deleted - and can be restored again at any time.
Page 62 Create MyConfig - Diff 3.4 Folder comparison A regular expression that is generally used is already selected in the specified comparison configuration "SINUMERIK archive". Some regular expressions can be created in the drop down list box. An introduction to regular expressions can be found at the end of the document (see Use of regular expressions in Diff (Page 85)).
Page 63 Create MyConfig - Diff 3.4 Folder comparison Table 3-1 Examples of filters: *.ini The "*" expression (asterisk) stands for any number of any characters. If the entry in the inclusion filter is defined, then only file names with the file exten‐ sion "ini"...
Page 64: Copying From The Folder Comparison
Create MyConfig - Diff 3.4 Folder comparison 3.4.5 Copying from the folder comparison Files, folders or complete folder structures can be copied from the comparison objects of the folder comparison to the clipboard and then, e.g. in Expert, inserted in a component. This means that it is possible to extract files from SINUMERIK, ZIP, TAR or TGZ archives, without having to use a Create MyConfig external software.
Page 65: Archive As User Or Sdb Archive
Create MyConfig - Diff 3.5 File comparison 3.4.6 Archive as user or SDB archive The following archives with different properties are available for theSINUMERIK 840D sl: ● Commissioning archive (Commissioning archive) ● SDB archive (PLC hardware upgrade archive, PLC HW Config archive) ●...
Page 66: Overview Of User Interface
Create MyConfig - Diff 3.5 File comparison The comparison result is processed from qualitative and quantitative perspectives. Contents can be copied from the files line-by-line to the clipboard and used in other applications (Expert ...). In the edit mode, you can delete lines or characters directly in the file comparison, insert them or copy them backwards and forwards between files.
Page 67 Create MyConfig - Diff 3.5 File comparison Description of buttons/fields of the toolbar The buttons of the toolbar are described in more detail below. ① Edit mode / Copy The edit mode can be activated and deactivated using the "Edit mode" button. Using the "Copy to the right"...
Page 68 Create MyConfig - Diff 3.5 File comparison ⑩ Select file for comparison Here you select the left comparison object. → Selection of the file to be compared → Selection from the files that were last selected ⑫ Switch between opened comparisons In the opened tabs, similar to the Window task bar, you can toggle between the opened comparisons with a mouse click or by simultaneously pressing "Ctrl"...
Page 69: File Comparison - Overview Window
Create MyConfig - Diff 3.5 File comparison 3.5.2.2 File comparison - overview window Below is an overview of the functions in the file comparison window. ① Overview comparison result ② Column with the comparison result symbols, to separate the left-hand and right-hand files. ③...
Page 70 Create MyConfig - Diff 3.5 File comparison ① Comparison result overview The comparison result is shown over the complete content of both files in this bar as an overview. The colored dashes represent lines that are only available on the left-hand side, only on the right-hand side –...
Page 71: Configuration
Create MyConfig - Diff 3.5 File comparison ⑤ Comparison configuration - Filter A filter is active in the comparison configuration. The comparison configuration is opened with a double-click. Note Character strings that are not relevant can be excluded from the comparison using the inclusion/exclusion filter.
Page 72 Create MyConfig - Diff 3.5 File comparison ① The existing comparison configurations are listed in this area of the configuration dialog and can be selected by clicking on them. Configurations shown in gray are user-specified configurations; these can be changed, but not deleted - and can be restored again at any time. ②...
Page 73 Create MyConfig - Diff 3.5 File comparison ① Background color So that the user can immediately recognize how to select certain comparison configurations, a separate background color can be defined for each comparison configuration. Filter tab Using filters, parts of a line can be included in or excluded from the comparison based on regular expressions.
Page 74 Create MyConfig - Diff 3.5 File comparison ① The functionality of the inclusion and exclusion filter is activated using a check mark for "Parts of a line..." NOTE: The filter symbol is shown in the status bar if this function is activated. ②...
Page 75 Create MyConfig - Diff 3.5 File comparison Alignment tab Under the "Alignment" tab, you can define how the individual lines of both files should be aligned with one another after the comparison. ① Using this selection, you can define that all lines of the two files are aligned continuously next to one another (line 1 next to line 1, line 2 next to line 2, etc.).
Page 76 Create MyConfig - Diff 3.5 File comparison ⑤ ③ ④ In addition, with lines for which the definitions do not apply, this slider can be used to set how the system handles lines that are not identical, but similar when it comes to aligning them.
Page 77: Configuration Of The Automatic File Identification
Create MyConfig - Diff 3.5 File comparison 3.5.4 Configuration of the automatic file identification Automatic file identification in Diff An automatic file identification function is integrated in Diff for file comparison. This file identification function can identify the file type from the file name or the file content and can select an associated comparison configuration.
Page 78 Create MyConfig - Diff 3.5 File comparison ① When a file is opened, Diff goes through the saved identification configurations from the top to the bottom - and applies the first appropriate configuration corresponding to what has been configured under the Settings tab. As a consequence, the sequence in which the configurations were saved is of signifi‐...
Page 79: Copying From The File Comparison
Create MyConfig - Diff 3.5 File comparison Note For the user-specified configurations, the file identification configuration and the associated file comparison configuration have the same names. It is not mandatory that the names are the same. The configuration names have no significance from a functional perspective. Comment tab Any comments on the selected identification configuration can be saved under the Comment tab.
Page 80: Display Modes
Create MyConfig - Diff 3.6 Exporting and importing configurations 3.5.6 Display modes The display mode for the file to be compared can be selected using the context menu of the file comparison. Exporting and importing configurations 3.6.1 General information The comparison configurations, specified in Diff and those that you configured yourself, file identification configurations and data task configurations can be exported in a file, either individually or in groups, and imported from a file.
Page 81: Exporting
Create MyConfig - Diff 3.6 Exporting and importing configurations 3.6.2 Exporting The dialog to export configurations can be called via the main menu "Tools > Export Configurations". The configurations available in Diff are displayed and grouped according to application areas. ①...
Page 82: Command Line Call
Create MyConfig - Diff 3.7 Command line call The configurations available in the file are displayed and grouped according to application areas. ① Activating or deactivating a group node means that this action is accepted for all con‐ figurations of the group. ②...
Page 83 Create MyConfig - Diff 3.7 Command line call The significance of the switches and arguments is described in the following tableDiff parameters. Diff /data <Archive path 1> [<Archive path 2>] [<Archive path n>] [/ config <Comparison configuration>] Diff /dir <Directory path 1> [< Directory path 2>] [/config <Comparison configuration>] Diff /file <File path 1>...
Page 84 Create MyConfig - Diff 3.7 Command line call Note Absolute / relative path Either the absolute path or the relative path can be specified. The relative path (with .\ or ./ etc.) refers to the current work folder (where batch or CMD were called).
Page 85: Use Of Regular Expressions In Diff
Create MyConfig - Diff A Use of regular expressions in Diff Example Precondition: Create MyConfig is installed in directory "C:\Program Files\SIEMENS\Create MyConfig 4.7", in path "C:\Temp\" there is an archive "Archive1.arc" - and inDiffthere is the comparison configuration "myConfig". "C:\Program Files\SIEMENS\Create MyConfig 4.7\Diff.exe" /data "C: \Temp\Archive1.arc"...
Page 86: Meta Characters In The Regular Expressions
Create MyConfig - Diff A Use of regular expressions in Diff Meta characters in the regular expressions The most important meta characters are shown in the following subsections which are contained in the dialect of the regular expressions of Create MyConfig. Character classes one character, which may be one of the In a regular expression, a character class defines...
Page 87 Create MyConfig - Diff A Use of regular expressions in Diff Constructs Meta charac‐ Description ters Several regular expressions can be combined to form a single one using alternation (logical OR). Example: cat|dog|tiger. (cat or dog or tiger) The match to the far left has priority. The grouping is used to combine parts of regular expressions and to limit the range of validity of an alternation.
Page 88: Examples Of Regular Expressions
Create MyConfig - Diff A Use of regular expressions in Diff Examples of regular expressions Regular expression Charac‐ Description [Version] Describes a section, e.g. ^\[[^\]]+\] At the beginning of the line there should be an "open square brack‐ et" [ and then there should be at least one character other than a "close square bracket"...
Page 89 Create MyConfig - Diff A Use of regular expressions in Diff Regular expression Charac‐ Description ② Start of the definition of a character set (character is a meta char‐ ^[^=]+= acter). ③ Here, a negation character, i.e. the characters specified in the char‐ ^[^=]+= acter set should not occur.
Page 90 Create MyConfig - Diff A Use of regular expressions in Diff SINUMERIK Integrate Create MyConfig - Diff, Expert, Topo Operating Manual, 11/2016, A5E36537479B-AD...
Page 91: Create Myconfig - Expert
Create MyConfig - Expert Safety instructions 4.1.1 Fundamental safety instructions 4.1.1.1 General safety instructions WARNING Danger to life if the safety instructions and residual risks are not observed If the safety instructions and residual risks in the associated hardware documentation are not observed, accidents involving severe injuries or death can occur.
Page 92: Industrial Security
Siemens’ products and solutions undergo continuous development to make them more secure. Siemens strongly recommends to apply product updates as soon as available and to always use the latest product versions. Use of product versions that are no longer supported, and failure to apply latest updates may increase customer’s exposure to cyber threats.
Page 93: Introduction
Create MyConfig - Expert 4.2 Introduction Introduction Note Documentation setup: Operating Manual / Online Help The contents for the Expert section are identical in the Operating Manual and online help. Expert is the engineering software for creating a CMC project. An executable package for the production and upgrading of machines can be generated from this project with the "Deployment"...
Page 94 Create MyConfig - Expert 4.2 Introduction ① Main menus and toolbars ② Project folder ③ Component editor and freely available working area ④ Dockable window with the tabs Verification, Cross references, and Source explorer Figure 4-1 Default setting of the Expert interface User-friendly Expert interface To a certain extend, you can adapt the Expert interface to your requirements.
Page 95 Create MyConfig - Expert 4.2 Introduction Repositioning the dockable window You can adapt the dockable window with the tabs Verification, Cross references and Source explorer, which can be selected and deselected, to your ambient conditions and the work situation. Procedure 1.
Page 96 Create MyConfig - Expert 4.2 Introduction 3. You can enlarge the dockable window across the entire working area to suit your needs or you can leave room for the Component editor. Figure 4-3 Dockable window in the working area SINUMERIK Integrate Create MyConfig - Diff, Expert, Topo Operating Manual, 11/2016, A5E36537479B-AD...
Page 97: Main Menus And Toolbars
Create MyConfig - Expert 4.2 Introduction 4. To arrange the dockable window again in the lower window area, proceed as described above. 5. Another option is that the dockable window is displayed separately from Expert as its own window on a second screen. To do this, move the desired window out of the interface of Expert.
Page 98 Create MyConfig - Expert 4.2 Introduction Password protection The project, the components, the package, and the logbook can be protected from unauthorized access with passwords. Enter the password... Log on to the open project using the password (extended rights). Edit password list... Define the passwords with the corresponding rights on the package and project.
Page 99 Create MyConfig - Expert 4.2 Introduction Source explorer Hides or displays the source explorer at the upper edge of the working area. Cross references Shows all identifiers, folders, and file objects used in the project on tabs "Identifiers" and "Folders and File objects". Verification run Hides or displays the verification of package at the lower edge of the application window.
Page 100 Create MyConfig - Expert 4.2 Introduction Store in list Package... tab Permits storage of the active configuration (as a file) in the "list of the project configurations" on the Package tab. Dialogs tab > Package configura‐ Permits storage of the active configuration (as tion...
Page 101: Source Explorer
Create MyConfig - Expert 4.2 Introduction Move to previous tab group Moves the selected component to the previous tab group. Restore window layout Restore the distribution of the interface areas, e.g. after a restart or change. Note Window Layout Note the distribution of the interface areas. Move to next tab Moves the selected component to the next tab group.
Page 102: Converting Projects From Older Cmc Versions
Create MyConfig - Expert 4.2 Introduction 4.2.4 Converting projects from older CMC versions When opening a project or a component, Expert checks the existing CMC version. If the CMC version of the project to be opened is earlier than the installed CMC version, Expert converts the project and the internally and externally linked components.
Page 103 Create MyConfig - Expert 4.2 Introduction Adaptation of values in projects from Version 2.6 Replace the UP() function with a value query. Syntax Version 2.6 Conversion possible? Syntax as of Version 4.6: Up($Step[id]) Up.$Step[id] UP(data) UP.data UP(doX) != null & UP.doX != null &&...
Page 104: Changes To System Variables
Create MyConfig - Expert 4.2 Introduction Querying SINAMICS drive parameters Syntax Version 2.6 Conversion possible? Syntax as of Version 4.6: Not directly possible PS[B3_S3_PS1].p105 Sections in tasks of SINAMICS data The sections in tasks of SINAMICS data are converted from the long notation still tolerated in SCI into a new shorthand notation, if the section does not contain a replacement operator.
Page 105: System Support
The affected system variables are ignored in configuration files. In scripts, an error message is issued in the compilation run and an adjustment must be made. System support 4.3.1 Differences during commissioning between SINUMERIK 840D sl and SINUMERIK 828D Overview The following table shows the essential differences during configuration of packages between...
Page 106: Support Cu320
Create MyConfig - Expert 4.4 Project folder 4.3.2 Support CU320 Below it is shown how the CU320 is supported in package configuring and package execution by Create MyConfig. Support of the CU320 by Create MyConfig The following processes are supported: ●...
Page 107 Create MyConfig - Expert 4.4 Project folder Specifying the configuration for Package You can configure the following property groups on the "Package" tab: ● General ● Project configuration ● Deployment ● Package ● Data areas ● NcuShareService Figure 4-5 Package tab - project engineer view SINUMERIK Integrate Create MyConfig - Diff, Expert, Topo Operating Manual, 11/2016, A5E36537479B-AD...
Page 108 Create MyConfig - Expert 4.4 Project folder Note Help area for Package tab Note the color-coded help in the lower section of the Package tab. Click on a property in the tab to display the appropriate help. Display associated system variables button You open the "Package system variables"...
Page 109 Create MyConfig - Expert 4.4 Project folder Deployment The following properties are available: Table 4-4 Deployment Name Here, you define the name of the package for this deployment. Storage location Here, you define the storage location, i.e. the ab‐ solute path under which the package is saved. Runtime system Linux package (NCU) Here, you select the runtime system on which the...
Page 110 Create MyConfig - Expert 4.4 Project folder Package The following properties are available: Table 4-5 Package Language preselection German Here, you select the user interface language for processing the package. English The language can be switched for each dialog separately by the user during the package execu‐ tion.
Page 111: Dialogs
Create MyConfig - Expert 4.4 Project folder The following properties are available: Table 4-6 Data areas Use archive Here, you define whether the data area Archive, PCU and/or NCU is used when executing the package. Use PCU This configuration affects the target area nodes in the actions of components (partially also scripts).
Page 112 Create MyConfig - Expert 4.4 Project folder Figure 4-6 Dialogs tab By selecting the data areas in the Package tab, the usable dialog pages are defined in the Dialog tab. The dialogs are used for package execution in the order in which they are listed from top to bottom.
Page 113 Create MyConfig - Expert 4.4 Project folder Name In the table column under "Name", dialog pages with a black checkbox can be activated or deactivated for "Editing" directly in the dialog list or via the property "Edit" in the property field. Dialog pages with a gray checkbox are always required to execute the package, in accordance with the configuration of the areas in the Package tab, and cannot be deselected.
Page 114: Dependency Of The Dialog Pages On Data Areas
Create MyConfig - Expert 4.4 Project folder These property groups are described only once in the "Package configuration (Page 121)" dialog, but they apply for all dialog pages. To the dialog pages Here you can find detailed information about the individual dialog pages: ●...
Page 115: Dialog Scripts
Create MyConfig - Expert 4.4 Project folder You can find an overview of the interrelationship between data areas and dialog pages in the following table. Table 4-8 Overview, dependency of dialog pages on data areas Data areas Use archive Use PCU Use NCU/PPU Dialogs Package configuration...
Page 116 Create MyConfig - Expert 4.4 Project folder Events In the "Dialog <designation> Edit event scripts", for the listed dialogs for the required events (= instants in time), scripts can be saved, which are executed when the package is executed at the event time of the dialog page. Figure 4-7 Edit event scripts dialog box SINUMERIK Integrate Create MyConfig - Diff, Expert, Topo...
Page 117 Create MyConfig - Expert 4.4 Project folder Meanings of the Events The following table describes what you achieve when using a certain event: Table 4-9 Event - Meaning Event Meaning / Time of script execution OnInit The script is executed before the dialog page is displayed. OnInit is used, for example: ●...
Page 118 Create MyConfig - Expert 4.4 Project folder Redo()* In the automatic sequence behaves differently than in the manual sequence. Redo() results in cancellation in the automatic sequence. Redo() should preferably be used in the dialogs in event "OnNext" to monitor manual entries. Skip()** Skip() immediately jumps to the next dialog.
Page 119: Examples Of Scripts In The Dialog Pages
Create MyConfig - Expert 4.4 Project folder Note Exceptions: Skip() not permitted It is not permitted to use Skip() on the following dialog pages and it is rejected with an error message during the verification run. ● Select offline archive ●...
Page 120 Create MyConfig - Expert 4.4 Project folder Example: Entering an NCU-dependent SDB archive into the System configuration dialog if (up.$Env.NCU=="SIEMENS SINUMERIK 840D sl NCU730.3 PN"|| up.$Env.NCU=="SIEMENS SINUMERIK 840D sl NCU 730.3B PN with PLC 317-3PN/DP") Up.$Dialog.SystemConfig.SdbFile = "./_sdb/73015151515db.arc" return() endif if up.$Env.NCU=="SIEMENS SINUMERIK 840D sl NCU720.3 PN"...
Page 121: Package Configuration (Configuration)
Create MyConfig - Expert 4.4 Project folder redo() endif Example: Query with response selection by the operator in dialogs or steps up.leavewhile=false while (up.leavewhile==false) up.quest=inputchoice("Select the resolution","1024*768;640*480;continue without entry") if up.quest=="1024*768" up.quest=1024 endif if up.quest=="640*480" up.quest=640 endif if up.quest=="continue without entry" msg("A resolution must be entered!") else up.leavewhile = true...
Page 122 Create MyConfig - Expert 4.4 Project folder Figure 4-9 Package configuration - project engineer view By selecting the data areas in the Package tab, the usable dialog pages are defined in the Dialog tab. You can find an overview for this in the section Dependencies of the dialog pages of data areas (Page 114).
Page 123 Create MyConfig - Expert 4.4 Project folder Display associated system variables button You open the "Package configuration - system variables" dialog via the button (Display associated system variables). All system variables to be used under "Package configuration" are listed here. Information on the System variables·can be found in the System variables for the Package configuration dialog (Page 286) section.
Page 124 Create MyConfig - Expert 4.4 Project folder Package configuration The following properties are available: List The list of all existing package configurations in the package is displayed in the "List of package configurations". Preselection Here, you make the selection for the selected package config‐ uration for package execution.
Page 125: Package Configuration (Package Execution)
Create MyConfig - Expert 4.4 Project folder 4.4.2.5 Package configuration (package execution) Dialog view during the package execution (for commissioning engineers / operators) You will find additional information on package execution in the section under Package execution (Page 317). Figure 4-10 Package configuration - commissioning engineer / operator view Buttons for the package processing dialogs Note...
Page 126: Notes About Acknowledgment (Configuration)
Create MyConfig - Expert 4.4 Project folder Table 4-10 Meaning of buttons Button Meaning Output The output window is shown or hidden. Status messages are displayed in the output window while the package is being executed. Alarms The alarm list is shown or hidden. It displays errors and messages from NC, PLC, drive, and HMI.
Page 127 Create MyConfig - Expert 4.4 Project folder Figure 4-11 Notes about acknowledgment - project engineer view By selecting the data areas in the Package tab, the usable dialog pages are defined in the Dialog tab. You can find an overview for this in the section Dependencies of the dialog pages of data areas (Page 114).
Page 128: Notes About Acknowledgment (Package Execution)
Create MyConfig - Expert 4.4 Project folder Display associated system variables button You open the "Notes about acknowledgment - system variables" dialog via the button (Display associated system variables). All system variables to be used under "Notes about acknowledgment" are listed here. Information on the system variables can be found in the System variables for the Notes on confirmation dialog (Page 287) section.
Page 129: Notes On The Package (Configuration)
Create MyConfig - Expert 4.4 Project folder Figure 4-12 Notes about acknowledgment dialog page - commissioning engineer / operator view Buttons for the package processing dialogs Information on the general buttons in the dialogs can be found under Meaning of buttons (Page 126).
Page 130 Create MyConfig - Expert 4.4 Project folder Figure 4-13 Notes on the package - project engineer view By selecting the data areas in the Package tab, the usable dialog pages are defined in the Dialog tab. You can find an overview for this in the section Dependencies of the dialog pages of data areas (Page 114).
Page 131: Notes On The Package (Package Execution)
Create MyConfig - Expert 4.4 Project folder Information on the system variables·can be found in the System variables for the Notes on the package dialog (Page 287) section. Further general information on the system variables can be found in the Reference list system variables (Page 283) section.
Page 132: Select Offline Archive (Configuration)
Create MyConfig - Expert 4.4 Project folder Buttons for the package processing dialogs Information on the general buttons in the dialogs can be found under Meaning of buttons (Page 126). 4.4.2.10 Select offline archive (configuration) You can configure the following property groups for the "Select offline archive" dialog page: ●...
Page 133 Create MyConfig - Expert 4.4 Project folder Figure 4-15 Select offline archive - project engineer view By selecting the data areas in the Package tab, the usable dialog pages are defined in the Dialog tab. You can find an overview for this in the section Dependencies of the dialog pages of data areas (Page 114).
Page 134 Create MyConfig - Expert 4.4 Project folder Display associated system variables button You open the "Select offline archive - system variables" dialog via the button (Display associated system variables). All system variables to be used under "Select offline archive" are listed here. Information on the system variables·can be found in the System variables for the Select offline archive dialog (Page 288) section.
Page 135: Select Offline Archive (Package Execution)
Create MyConfig - Expert 4.4 Project folder DRV part archive (input) The following property is available: Preselection An archive can be preselected from which only the DRV area for package execution is used. An area originating from the "input archive" is thus replaced. Output archive The following property is available: File path...
Page 136: Pcu Access (Configuration)
Create MyConfig - Expert 4.4 Project folder Figure 4-16 Select offline archive - Commissioning engineer/operator view Buttons for the package processing dialogs Information on the general buttons in the dialogs can be found under Meaning of buttons (Page 126). 4.4.2.12 PCU access (configuration) You can configure the following property groups for the "PCU access"...
Page 137 Create MyConfig - Expert 4.4 Project folder Figure 4-17 PCU access - project engineer view By selecting the data areas in the Package tab, the usable dialog pages are defined in the Dialog tab. You can find an overview for this in the section Dependencies of the dialog pages of data areas (Page 114).
Page 138: Pcu Access (Package Execution)
Create MyConfig - Expert 4.4 Project folder Display associated system variables button You open the "PCU access - system variables" dialog via the button (Display associated system variables). All system variables to be used under "PCU access" are listed here. Information on the system variables can be found in the System variables for the PCU access dialog (Page 287) section.
Page 139: Ncu/Ppu Access (Configuration)
4.4.2.14 NCU/PPU access (configuration) This dialog page enables access to the NCU in the case of SINUMERIK 840D sl or the PPU in the case of SINUMERIK 828D. You can configure the following property groups for the "NCU/PPU access" dialog page: ●...
Page 140 Create MyConfig - Expert 4.4 Project folder Figure 4-19 NCU/PPU access - project engineer view By selecting the data areas in the Package tab, the usable dialog pages are defined in the Dialog tab. You can find an overview for this in the section Dependencies of the dialog pages of data areas (Page 114).
Page 141: Ncu/Ppu Access (Package Execution)
Create MyConfig - Expert 4.4 Project folder Display associated system variables button You open the "NCU/PPU access - System variables" dialog via the button (Display associated system variables). All system variables to be used under "NCU/PPU access" are listed here. Information on the system variables·can be found in the section System variables for the NCU/ PPU access dialog (Page 288).
Page 142: Ncu/Ppu Initial State (Configuration)
Create MyConfig - Expert 4.4 Project folder If, in the Package tab, under "Data areas > Use NCU/PPU" has been selected, this dialog page is executed automatically when executing a package. You will find additional information on package execution in the section under Package execution (Page 317).
Page 143 Create MyConfig - Expert 4.4 Project folder Figure 4-21 NCU/PPU initial state - project engineer view By selecting the data areas in the Package tab, the usable dialog pages are defined in the Dialog tab. You can find an overview for this in the section Dependencies of the dialog pages of data areas (Page 114).
Page 144 Create MyConfig - Expert 4.4 Project folder Display associated system variables button You open the "NCU/PPU initial state" dialog via the button (Display associated system variables). All system variables to be used under "NCU/PPU initial state" are listed here. Information on the system variables·can be found in the section System variables for the NCU/ PPU initial state dialog (Page 289).
Page 145: Ncu/Ppu Initial State (Package Execution)
Create MyConfig - Expert 4.4 Project folder Archive Back up archive A complete archive can also be created for the diagnostics, with a set‐ ting for all data to be backed up. The complete archive is stored in a folder named based on the CF card ID with the name "Backup_<Date>.arc".
Page 146: Notes On Gsp (Configuration)
Create MyConfig - Expert 4.4 Project folder Figure 4-22 NCU/PPU initial state - commissioning engineer / operator view Buttons for the package processing dialogs Information on the general buttons in the dialogs can be found under Meaning of buttons (Page 126). 4.4.2.18 Notes on GSP (configuration) You can configure the following property groups for the "Notes on GSP"...
Page 147 Create MyConfig - Expert 4.4 Project folder Figure 4-23 Notes on GSP - Project engineer view By selecting the data areas in the Package tab, the usable dialog pages are defined in the Dialog tab. You can find an overview for this in the section Dependencies of the dialog pages of data areas (Page 114).
Page 148: Notes On Gsp (Package Execution)
Create MyConfig - Expert 4.4 Project folder Further general information on the system variables can be found in the Reference list system variables (Page 283) section. Dialog / Operating instructions More detailed information about the property groups "General" and "Operating instructions" can be found under Package configuration (configuration) (Page 121).
Page 149: Service Platform Industry (Gsp) (Configuration)
Create MyConfig - Expert 4.4 Project folder 4.4.2.20 Service Platform Industry (GSP) (configuration) You can configure the following property groups for the "Service Platform Industry (GSP)" dialog page: ● Dialog ● Specify machine identity ● Machine information ● Manufacturer data ●...
Page 150 Create MyConfig - Expert 4.4 Project folder Figure 4-25 Service Platform Industry (GSP) - Project engineer view By selecting the data areas in the Package tab, the usable dialog pages are defined in the Dialog tab. You can find an overview for this in the section Dependencies of the dialog pages of data areas (Page 114).
Page 151 Create MyConfig - Expert 4.4 Project folder Display associated system variables button You open the "Service Platform Industry (GSP) - System variables" dialog via the button (Display associated system variables). All of the system variables to be used under "Service Platform Industry (GSP)"...
Page 152 Create MyConfig - Expert 4.4 Project folder Manufacturer data The following settings are available for the "Manufacturer data" property: Manufacturers (selection file) The "oem.xml" file that contains a list of manufacturers with their ad‐ dresses can be linked or inserted here. Manufacturer The manufacturers contained in the selection file are displayed via the context menu and can be selected.
Page 153: Service Platform Industry (Gsp) (Package Execution)
You will find additional information on package execution in the section under Package execution (Page 317). Note Templates for the described XML files can be viewed on the NCU under "/card/siemens/ sinumerik/hmi/template/identity". SINUMERIK Integrate Create MyConfig - Diff, Expert, Topo...
Page 154: Cnc Software (Configuration)
Create MyConfig - Expert 4.4 Project folder Figure 4-26 Service Platform Industry (GSP) - commissioning engineer / operator view Buttons for the package processing dialogs Information on the general buttons in the dialogs can be found under Meaning of buttons (Page 126).
Page 155 Create MyConfig - Expert 4.4 Project folder Figure 4-27 CNC software - project engineer view By selecting the data areas in the Package tab, the usable dialog pages are defined in the Dialog tab. You can find an overview for this in the section Dependencies of the dialog pages of data areas (Page 114).
Page 156 The following settings are available for the "CNC software (*.tgz)" property: List tgz files that contain the CNC software are provided by Siemens Support and can be inserted as copy or link in a list. Linked files are not taken into this list until the package is deployed.
Page 157: Cnc Software (Package Execution)
Create MyConfig - Expert 4.4 Project folder Dialog scripts Under "Dialog scripts", entry "Scripts", via the button you open the "Dialog 'CNC software' Edit event scripts". Here you can edit scripts that are to be executed at selectable times during package processing.
Page 158: System Configuration (Configuration)
Create MyConfig - Expert 4.4 Project folder After the tgz file has been loaded, the NCU is automatically restarted. Note TGZ files generated using "sc backup xyz.tgz" or backups generated using Create MyConfig can only be used for a new installation. They cannot be used for an upgrade.
Page 159 Create MyConfig - Expert 4.4 Project folder Figure 4-29 System configuration - project engineer view By selecting the data areas in the Package tab, the usable dialog pages are defined in the Dialog tab. You can find an overview for this in the section Dependencies of the dialog pages of data areas (Page 114).
Page 160 Create MyConfig - Expert 4.4 Project folder For "Source of the data", select from where the data of the individual areas should be sourced. This selection can be blocked individually for each area by the project engineer in order to prevent changes by the operator during the package execution.
Page 161 Create MyConfig - Expert 4.4 Project folder NC archive data The following settings are available for the "NC archive data" and are activated when the package is executed: Table 4-11 NC archive data Origin of data Note This selection can be blocked by the project engineer in order to prevent changes by the operator during the package execution.
Page 162 Create MyConfig - Expert 4.4 Project folder PLC archive data The following settings are available for the "PLC archive data" and are activated when the package is executed: Origin of data Note This selection can be blocked by the project engineer in order to prevent changes by the operator during the package execution.
Page 163 Create MyConfig - Expert 4.4 Project folder Setting disabled The selection at "Source of the data" can be blocked by the project engineer via this option in order to prevent changes by the operator during the package execution. Preselection of the offline archive Under "Preselection of offline archive"...
Page 164 Create MyConfig - Expert 4.4 Project folder The following settings are available for the "DRV archive data / drive configuration" and are activated when the package is executed: Origin of data Initial state If the "NCU area" was activated during package configuration, the archive data can be loaded directly from the control with the setting "Initial state".
Page 165: System Configuration (Package Execution)
Create MyConfig - Expert 4.4 Project folder Setting disabled The selection at "Source of the data" can be blocked by the project engineer via this option in order to prevent changes by the operator during the package execution. Preselection of the offline archive Under "Preselection of the offline archive", a SINUMERIK archive can be inser‐...
Page 166 Create MyConfig - Expert 4.4 Project folder Dialog view during the package execution (for commissioning engineers / operators) In this dialog you set which archive data (NC, PLC, and DRV) will be used later in the subsequent package stages. Note If the "Archive area"...
Page 167: Notes On The Topology (Configuration)
Create MyConfig - Expert 4.4 Project folder 4.4.2.26 Notes on the topology (configuration) You can configure the following property groups for the "Notes on the topology" dialog page: ● Dialog ● Operating instructions Figure 4-31 Notes on the topology - project engineer view By selecting the data areas in the Package tab, the usable dialog pages are defined in the Dialog tab.
Page 168: Notes On The Topology (Package Execution)
Create MyConfig - Expert 4.4 Project folder Display associated system variables button You open the "Notes on the topology - system variables" dialog via the button (Display associated system variables). All system variables to be used under "Notes on the topology" are listed here.
Page 169: Sinamics Topology (Configuration)
Create MyConfig - Expert 4.4 Project folder Figure 4-32 Notes on the topology - commissioning engineer / operator view Buttons for the package processing dialogs Information on the general buttons in the dialogs can be found under Meaning of buttons (Page 126).
Page 170 Create MyConfig - Expert 4.4 Project folder Figure 4-33 SINAMICS topology - project engineer view By selecting the data areas in the Package tab, the usable dialog pages are defined in the Dialog tab. You can find an overview for this in the section Dependencies of the dialog pages of data areas (Page 114).
Page 171 Create MyConfig - Expert 4.4 Project folder Display associated system variables button You open the "SINAMICS topology - system variables" dialog via the button (Display associated system variables). All system variables to be used under "SINAMICS topology" are listed here. Information on the System variables·can be found in the System variables for the SINAMICS topology dialog (Page 292) section.
Page 172 Create MyConfig - Expert 4.4 Project folder The following properties are available for the "comparison topology (*.ust)", which are activated when the package is executed: List button opens the "List of topologies (*.ust)" dialog. Select the desired topology from the list. Comparison topologies can be pasted or inserted as link under "List".
Page 173 Create MyConfig - Expert 4.4 Project folder DO variables The following properties are available for the "DO variables", which are activated when the package is executed: List button opens the "DO list" dialog. Enter the "DO variable" and its corresponding data here: ●...
Page 174 Create MyConfig - Expert 4.4 Project folder importance for the purely manual method of operation, where the user on the machine toggles the DO variables to the DOs. By assigning a DO variable, all components are identified that belong to a drive object (e.g. a Motor Module, two Sensor Modules).
Page 175: Sinamics Topology (Package Execution)
Create MyConfig - Expert 4.4 Project folder 4.4.2.29 SINAMICS topology (package execution) Dialog view during the package execution (for commissioning engineers / operators) The three possible dialog versions are subsequently described: ● Comparison topology ● User-specified topology ● Manual DO variable assignment Comparison topology This dialog version is used if "Initial state", "Offline archive"...
Page 176 Create MyConfig - Expert 4.4 Project folder As a prerequisite, this Axis-drive assignment must have been configured and activated in Topo. DO variables There is a list of all DO variables that are in the DO variable list in the comparison topology in the upper part of the dialog page.
Page 177 Create MyConfig - Expert 4.4 Project folder User-specified topology This dialog version is used for the SINAMICS topology if "User-specified topology" was selected for the device configuration for the drives. Figure 4-35 SINAMICS topology - commissioning engineer/operator view - example for user-specified topology Performing axis-drive assignment Setting the check mark activates automatic axis-drive assignment.
Page 178 Create MyConfig - Expert 4.4 Project folder The "SM" column indicates as to whether a sensor module involves a first or second encoder. Sensor modules are displayed in blue. Column "AX DR" includes information about theaxis-drive assignment. User-specified topology(*.utz) Using the "User-specified topology" drop-down list, a file that was assigned to the package or a file located next to the package (prefix: "./") can be used.
Page 179: Version Display (Configuration)
Create MyConfig - Expert 4.4 Project folder Precondition for manual DO variable assignment It is only possible to manually assign DO variables if no Comparison topology and no User- specified topology is used and in Expert a DO variable list was configured. It is notpermissible that "Execute axis-drive assignment"...
Page 180 Create MyConfig - Expert 4.4 Project folder Figure 4-37 Version display - project engineer view By selecting the data areas in the Package tab, the usable dialog pages are defined in the Dialog tab. You can find an overview for this in the section Dependencies of the dialog pages of data areas (Page 114).
Page 181: Version Display (Package Execution)
The applications identified during execution and their determined versions are displayed on the "Version display" dialog. The information about the NCU is obtained from the "/siemens/versions.xml" file and in the case of the PCU from the Registry: "HKLM\Software\SIEMENS\AUTSW". You will find additional information on package execution in the section under Package execution (Page 317).
Page 182: Notes On The Step Tree (Configuration)
Create MyConfig - Expert 4.4 Project folder Figure 4-38 Version display - commissioning engineer / operator view Buttons for the package processing dialogs Information on the general buttons in the dialogs can be found under Meaning of buttons (Page 126). 4.4.2.32 Notes on the step tree (configuration) You can configure the following property groups for the "Notes on the step tree"...
Page 183 Create MyConfig - Expert 4.4 Project folder Figure 4-39 Notes on the step tree - project engineer view By selecting the data areas in the Package tab, the usable dialog pages are defined in the Dialog tab. You can find an overview for this in the section Dependencies of the dialog pages of data areas (Page 114).
Page 184: Notes On The Step Tree (Package Execution)
Create MyConfig - Expert 4.4 Project folder Further general information on the system variables can be found in the Reference list system variables (Page 283) section. Dialog / Operating instructions You can find additional information on the property groups "Dialog" and "Operating instructions"...
Page 185: Step Tree (Configuration)
Create MyConfig - Expert 4.4 Project folder 4.4.2.34 Step tree (configuration) You can configure the following property groups for the "Step tree" dialog page: ● Dialog ● Step configuration (*.upcfg) ● Archive ● Dialog scripts Figure 4-41 Step tree - project engineer view By selecting the data areas in the Package tab, the usable dialog pages are defined in the Dialog tab.
Page 186 Create MyConfig - Expert 4.4 Project folder Show/hide inactive dialogs button Via the button (Show/hide inactive dialogs), dialogs that are not used in this project can be shown or hidden. Display associated system variables button You open the "Step tree - system variables" dialog via the button (Display associated system variables).
Page 187: Step Tree (Package Execution)
Create MyConfig - Expert 4.4 Project folder The following settings are available for "Archive": Create before step tree Here, you specify whether an archive with the NC, PLC and DRV areas is to be created before the execution of the step tree. The backup is performed for the NC area with the setting that all data is to be saved.
Page 188 Create MyConfig - Expert 4.4 Project folder Figure 4-42 1. Step tree dialog - commissioning engineer / operator view Via the "Step configuration (*.upcfg)" drop-down list, a file that was assigned to the package or a file located next to the package (prefix: "./") can be used. The "Browse"...
Page 189: Archive Data Transfer (Package Execution)
Create MyConfig - Expert 4.4 Project folder Figure 4-43 2. Step tree dialog - commissioning engineer / operator view Buttons for the package execution dialogs Information on the general buttons in the dialogs can be found under Meaning of buttons (Page 126).
Page 190: Ncu/Ppu Result State (Configuration)
Create MyConfig - Expert 4.4 Project folder Figure 4-44 Archive data transfer (package execution) Buttons for the package execution dialogs Information on the general buttons in the dialogs can be found under Meaning of buttons (Page 126). 4.4.2.37 NCU/PPU result state (configuration) You can configure the following property groups for the "NCU/PPU result state"...
Page 191 Create MyConfig - Expert 4.4 Project folder Figure 4-45 NCU/PPU result state - project engineer view By selecting the data areas in the Package tab, the usable dialog pages are defined in the Dialog tab. You can find an overview for this in the section Dependencies of the dialog pages of data areas (Page 114).
Page 192 Create MyConfig - Expert 4.4 Project folder Information on the system variables·can be found in the section System variables for the NCU/ PPU result state dialog (Page 294). Further general information on the system variables can be found in the Reference list system variables (Page 283) section.
Page 193: Ncu/Ppu Result State (Package Execution)
Create MyConfig - Expert 4.4 Project folder You can find detailed information on the dialog scripts in the section with the same name "Dialog scripts (Page 115)". 4.4.2.38 NCU/PPU result state (package execution) Dialog view during package execution (for commissioning engineers / operators) A data backup of the CF card including all current control data (NC, PLC, DRV) can be selected on this dialog page.
Page 194: End (Configuration)
Create MyConfig - Expert 4.4 Project folder 4.4.2.39 End (configuration) You can configure the following property groups for the "Finish" dialog page: ● Dialog ● Operating instructions ● Logbook Figure 4-47 Dialog page: Finish - project engineer view By selecting the data areas in the Package tab, the usable dialog pages are defined in the Dialog tab.
Page 195: End (Package Execution)
Create MyConfig - Expert 4.4 Project folder Display associated system variables button You open the "End - system variables" dialog via the button (Display associated system variables). All system variables to be used under "Finish" are listed here. Information on the system variables·can be found in the System variables for the Finish dialog (Page 295) section.
Page 196: Steps
Create MyConfig - Expert 4.4 Project folder Figure 4-48 Finish dialog - commissioning engineer / operator view Buttons for the package execution dialogs Information on the general buttons in the dialogs can be found under Meaning of buttons (Page 126). 4.4.3 Steps On the "Steps"...
Page 197: Step Tree Structure
Create MyConfig - Expert 4.4 Project folder Package execution When executing the package, the step tree is executed from top to bottom along the step sequence marked in green. A step is always executed if its checkbox is green in the display. When a step is executed, any existing step script is first checked.
Page 198 Create MyConfig - Expert 4.4 Project folder Figure 4-49 Example Structure of a step tree Buttons for the step tree The display options of the Steps tab are described in the following. Figure 4-50 Toolbar of the Steps tab SINUMERIK Integrate Create MyConfig - Diff, Expert, Topo Operating Manual, 11/2016, A5E36537479B-AD...
Page 199 Create MyConfig - Expert 4.4 Project folder Using the buttons, you can modify the representation of the step tree: Expand selection Here, you can either display a selected step or the entire step tree with all substeps and components. Reduce selection Here, you can reduce an individually selected step or the entire step tree to the main step.
Page 200: Step Properties
Create MyConfig - Expert 4.4 Project folder 4.4.3.2 Step properties Configuration You can configure the following property groups for each step or substep: ● Step ● Step configuration ● Miscellaneous ● Step scripts Step The following settings are available for the property group "Step": Name A name can be assigned to each step.
Page 201 Create MyConfig - Expert 4.4 Project folder Step configuration The following settings are available for the property group "Step configuration": Management in the Main project Specifies where the step configuration is to be managed. Subproject Activation The "Activation" defines whether a step is to be executed. For "Yes"...
Page 202: Step Scripts
Create MyConfig - Expert 4.4 Project folder None No warning message is output. If step activated A warning message is output if the step is activated. If step not activated A warning message is output if the step is not activated. The operator then has the option of confirming the setting using "OK"...
Page 203: Edit Step Tree
Create MyConfig - Expert 4.4 Project folder Skip()** Skip()jumps to next step. The current step is thus no longer processed. Figure 4-51 Executing the steps 4.4.3.4 Edit step tree Component editor Double-clicking a component link opens the component in the component editor. Open components are shown in bold in the step tree.
Page 204 Create MyConfig - Expert 4.4 Project folder Context menu Using the context menu, steps and components can be pasted, copied, deleted and resorted. The following operations are possible: Context menu steps Ctrl+X Cuts the selected step, including the substeps and the links to components.
Page 205 Create MyConfig - Expert 4.4 Project folder Edit link... Link new components... Displays the "Component explorer" dialog box, with which a new component can be created. This compo‐ nent is associated with the step. Link existing component(s)... Displays the "Component explorer" dialog box, with which one or more existing components can be linked with the step.
Page 206: Linking Steps
Create MyConfig - Expert 4.4 Project folder Insert a new step To create a new step, click on an existing step and select "New step" via the context menu. Figure 4-52 Create new step See also Step tree (configuration) (Page 185) 4.4.3.5 Linking steps Introduction...
Page 207 Create MyConfig - Expert 4.4 Project folder The commissioning engineer sees a complete step tree during project execution. The use of subprojects is no longer visible here. Due to the linking in step trees, the commissioning of modular machines is supported even more efficiently.
Page 208 Create MyConfig - Expert 4.4 Project folder The following rules must be observed when linking steps: ● In a main project (MP), several links from the same or different subprojects (SP) can be carried out. Note Linking depth with main projects and subprojects The step trees linked from subprojects must not contain any links to another subproject (linking depth = 1).
Page 209 Create MyConfig - Expert 4.4 Project folder ● The same names are permitted for the components in the MP and SP. ● The properties of the step configuration ("Activation", "Activation disabled" and "Collapse") can be alternatively managed in the main project or subproject. Various use cases are thus supported.
Page 210 Create MyConfig - Expert 4.4 Project folder The query in the figure shown above returns a value of "Null" for an independent execution of the subproject (SP). Before this query, the existence of the step in the main project (MP) can be checked. Example: If Up.$Step[.2] != Null ●...
Page 211 Create MyConfig - Expert 4.4 Project folder Creating a step link Procedure The following shows how a step is copied from a subproject (SP) and inserted into a main project (MP) as link. 1. In the Steps tab in a project of your choice that you would like to use as a subproject (SP), select a step and use Ctrl+C or the context menu to copy it.
Page 212 Create MyConfig - Expert 4.4 Project folder Figure 4-55 Insert link step 3. The inserted blue link step has allocated in the MP an additional step property "ID namespace" and a step configuration property "Managing in the". The values of both properties are assigned a standard default value, which you can change. These properties, which can only exist in the MP, are accepted for all gray steps below the link step, and displayed for these.
Page 213 Create MyConfig - Expert 4.4 Project folder Properties of linked steps For the step link and all substeps, all step properties are taken into the main project. The step properties are displayed and saved in the project. The step properties shown in gray cannot be changed in the main project. The ID namespace produced by the step link can be changed at any time in the link step marked in blue.
Page 214: Component Editor
Create MyConfig - Expert 4.5 Component editor Updating the step links The step links can be selectively updated via the shortcut menu or the "Refresh step tree completely (F5)" button. Further, update is automatic when opening the project, when starting the verification run and when starting to generate the cross reference list.
Page 215 Create MyConfig - Expert 4.5 Component editor Actions tab The actions to be performed by the component can be activated in the "Actions" tab. The following actions can be created: ● Execute (Page 219) ● Delete (Page 223) ● Copy (Page 226) ●...
Page 216: Action Scripts
Create MyConfig - Expert 4.5 Component editor Executing / copying actions Files and folders can be inserted below the "Execute" and "Copy" actions both as a copy and as a link. It is also possible to mix copied and linked objects. Deleting / editing / manipulating actions In the "Delete", "Edit"...
Page 217 Create MyConfig - Expert 4.5 Component editor Skip()** Skip() jumps to the next action. The current action is thus no longer processed. Figure 4-57 Executing actions in components SINUMERIK Integrate Create MyConfig - Diff, Expert, Topo Operating Manual, 11/2016, A5E36537479B-AD...
Page 218 Create MyConfig - Expert 4.5 Component editor Creating and editing an action script There are two ways to create and edit an action script in the editor: 1. In the Component editor, check the requested action in the Actions tab it and open "Edit action script"...
Page 219: Execute
Execute action The "Execute" action allows a program, command or script to be executed. For instance, software components from SIEMENS or other suppliers can be installed or special manipulations are possible in the archive or other target areas. The following target areas are supported: ●...
Page 220 Create MyConfig - Expert 4.5 Component editor Note Display of the target area ● Gray - target area does not contain any data. ● Red - data inserted in the target area is not permissible. ● Blue - linked data with resolution for deployment. ●...
Page 221 Create MyConfig - Expert 4.5 Component editor The return value of programs that were executed by the PCU handler is returned to the package execution and logged in the logbook. Example with return value 0 The return value of the script is evaluated as terminating error code, i.e. a return code not equal to 0 results in an error message and the user must decide whether the package should be canceled or continued.
Page 222 Create MyConfig - Expert 4.5 Component editor Example All of the files – with the exception of OEM001.SPF – should be deleted from the CMA.DIR directory of the NC. As there is no special delete instruction for this purpose, a script is generated which saves the file to be obtained, subsequently deletes the folder and then returns the file.
Page 223: Delete
Create MyConfig - Expert 4.5 Component editor NCU/Linux With shell scripts (sh) for Linux, it must be ensured that data is saved in the Unix file format, but only LF not CR/LF. The shell ID (e.g. #!/bin/sh) must be located in the first line – or the script should be started using a shell command (e.g.
Page 224 Create MyConfig - Expert 4.5 Component editor Note Delete instructions in the target area: Archive/MMC are only applied to the archive and do not affect the data management of HMI-Advanced F:\DH . A "Task" must be created using the context menu in order to be able to enter delete operations. The operations can be sub-divided into several tasks in order to improve the structure.
Page 225 Create MyConfig - Expert 4.5 Component editor Additional useful notes HMI-Adv/DH An error-tolerant procedure is used for delete operations as well as when navigating. A check is first made as to whether the name corresponds to a data man‐ agement name. If this is the case, then the system uses the information from data management.
Page 226: Copy
Create MyConfig - Expert 4.5 Component editor 4.5.5 Copy Copy action The "Copy" action enables folders and files to be copied into the target area. With the help of the context menu, you can insert folders and files in the component as a copy or link under the target area nodes.
Page 227 Create MyConfig - Expert 4.5 Component editor Inserting a link Permits data to be added to the project as a link from folders and files. (resolution for deployment) Archive contents can also be linked. These links are removed for package deployment from Expert and the data is imported as a copy into the components.
Page 228 Create MyConfig - Expert 4.5 Component editor Copying in the data management (HMI-Adv, archive) For folders and files in data management, names with characters: A-Z_0-9 and a maximum length of 24 characters are permissible. Further, especially folders are subject to the data management conventions regarding their names.
Page 229 Create MyConfig - Expert 4.5 Component editor Additional useful notes HMI-Adv/DH When copying and navigating, an error-tolerant procedure is used. A check is first made as to whether the name corresponds to a data management name. If this is the case, then the system uses the information from data management.
Page 230: Change
Create MyConfig - Expert 4.5 Component editor 4.5.6 Change Change action The "Change" action allows data in the configuration files to be adapted. Configuration files are text files comprising one or more sections including value assignments: [Section] Identifier=value The ini extension is generally used for configuration files. However, all files that comply with the structure of an INI file can be edited.
Page 231 Create MyConfig - Expert 4.5 Component editor Figure 4-62 Change action with preprocessor script Examples of change action with preprocessor script Example 1 In the following example, a cycle Cycle1.spf is created in the path /NC/CMA.DIR in the archive. The sets N003 to N006 are inserted depending on an Up variable. SINUMERIK Integrate Create MyConfig - Diff, Expert, Topo Operating Manual, 11/2016, A5E36537479B-AD...
Page 232 Create MyConfig - Expert 4.5 Component editor Figure 4-63 Example 1 - preprocessor statements Preprocessor statements always begin with "#". Only these lines are evaluated as script by the CMC package. Lines that do not begin with this character are imported into the file to be created without checking.
Page 233 Create MyConfig - Expert 4.5 Component editor Figure 4-64 Example 2 - deleting tool data from the INITIAL.INI In the configuration file for the SED editor, additional script-controlled operations could be inserted depending on Up variables or Config variables. Figure 4-65 Example 2 - inserting script-controlled operations Target areas Note...
Page 234 Create MyConfig - Expert 4.5 Component editor Note Display of the target area ● Gray - target area does not contain any data. ● Red - data inserted in the target area is not permissible. ● Blue - linked data with resolution for deployment. The following target areas are supported: Archive Archive image...
Page 235 Create MyConfig - Expert 4.5 Component editor Special operators (Page 255) can be inserted anywhere in a line to insert the contents of UP variables for modification. Note If folders, files, sections or identifiers are not available, then the package itself generates these to implement a value assignment.
Page 236: Manipulate
Create MyConfig - Expert 4.5 Component editor 4.5.7 Manipulate Manipulate action The "Manipulate" action allows machine data to be accessed, essentially independently of data storage in the control system. The data to be manipulated can be stored in the archive (e.g. NC data, drive data) as well as in the HMI (display data).
Page 237 The context menu assists you when inserting sections, control structures, functions, procedures, operators and range data. Furthermore, a catalog is available listing all of the identifiers specified by SIEMENS. The operation editor marks the syntax of faulty entries with a red wavy line. Syntax errors in the task can be easily found using the "Go to next error"...
Page 238 Create MyConfig - Expert 4.5 Component editor Use of the "Message preview" context menu entry requires that the cursor be in a line that contains a Function/Procedure with a user dialog. You can close a displayed dialog by pressing a button on this. Example for "Error"...
Page 239 SINUMERIK Operate , data is read from the section: [OPI settings] of the file: "hmi_md.ini" in the search sequence: siemens → addon → oem → user, but is only written back to hmi_md.ini under user. When deleting data, this results in a reset to a user-specified value of preceding files in the search sequence.
Page 240: Script Language
Create MyConfig - Expert 4.6 Script language Comparing tasks in Diff Manipulation tasks can also be used in Diff for comparison. To this end, export the task to a file and open it in the SINUMERIK archive comparison of Diff. All assignments in the form of "identifier = value" are then displayed in the data structure tree of Diff and can be used for a comparison, etc.
Page 241: Color Coding Of Language Elements
Create MyConfig - Expert 4.6 Script language Execution of the action can therefore be controlled or a script can also be kept out of tasks. The advantage of the latter is that the data derivations from Diff (machine data lists, etc.), for example, can be used directly and "unadulterated".
Page 242: Set Channel
Create MyConfig - Expert 4.6 Script language Program element Color Formatting Example Functions Violet Bold User frames, Yellow/orange variables that have not been interpreted Replacement operator Kaki Italic 4.6.3 Set channel Examples [C1] ;channel 1 is set as an area as of here $MC_CHAN_NAME = "Channel 1"...
Page 243 Create MyConfig - Expert 4.6 Script language The following section data is admissible depending on the target area: Target area Explanation Format SINAMICS data Subpath within the [B3_S3_PS3] drive system Notice No leading zeroes must be used No leading zeroes must be used for the figures. These are not detected during the validation run for replacement operators.
Page 244: Data Access Operations
Create MyConfig - Expert 4.6 Script language Drive data Syntax Description PS[B<bNr>_S<sNr>_PS<psNr>].<drvData> Value of the SINAMICS drive parameter "drvData" of the specified section: ● Bus with the bus number "bNr" ● Slave with the slave number "sNr" ● Drive object with the number "psNr" Values from 1 to 99 are valid for "psNr".
Page 245 Create MyConfig - Expert 4.6 Script language Data Dialog Step tree access op‐ pages erations Cross-area Area specific Dialog Step Action Manipulation tasks scripts scripts scripts NC data DRV data BD data Reading Package variables – Up.name and writing Only package variables - Simple identifiers Simple identifiers with simple section Up.name...
Page 246 Create MyConfig - Expert 4.6 Script language Syntax for simple identifiers with a fully qualified section The syntax for simple identifiers with a fully qualified section is generally: ● Namespace[section] Variable Below a fully qualified section, as many variables/identifiers and scripts as required that belong to this section can be also used for assignments or queries.
Page 247: Package Variables
Create MyConfig - Expert 4.6 Script language EndIf 4.6.6 Package variables Package variables - Up.identifier Package variables are variables that only have meaning within the package. The controller does not know these variables and they are not transferred to the controller. These variables consist of an identifier, which is preceded by the Up.
Page 248: Script Variables
Create MyConfig - Expert 4.6 Script language 4.6.6.1 Script variables Script variables - Up.myVar Users create script variables using operations of the form and using using a unique name "identifier" and immediate value initialization. Up.identifier = value Examples Up.M1=100.123 Up.xx_1= R[7] Up.NX_BOOL=true Up.channel="channel _1"...
Page 249: System Variables
Create MyConfig - Expert 4.6 Script language Up.doVar.dpSlot Supplies the PROFIBUS location number, starting with 1 (only for SERVO of the NCU and NX). 4.6.6.3 System variables Note When the password variables are used, the password that is used appears in the logbook during the package execution.
Page 250: Check Structures
Create MyConfig - Expert 4.6 Script language In the task/script editor, area data can be inserted via the context menu "Insert script → Area data...". Furthermore, the area data can be inserted via the Windows clipboard from Diff. Note You can get the options for the cross-area reading and writing of area data from section Data accesses (Page 244).
Page 251: If-Elsif Control Structure / If-Elsif-Else Control Structure
Create MyConfig - Expert 4.6 Script language 4.6.8.2 If-ElsIf control structure / If-ElsIf-Else control structure The If-Else control structure was expanded in Create MyConfig V4.7. After the If condition alternative conditions can be checked by specifying ElsIf or ElIf. The operation block is executed after the first fulfilled condition. The operation block after Else is executed if no condition is fulfilled.
Page 252: While Check Structure
Create MyConfig - Expert 4.6 Script language Each operation block can, in turn, contain control structures; this means that any nesting depth is possible. Example 1 CHANDATA(1) If Up.Velo_X != null If Up.Velo_X > $MA_MAX_AX_VELO[AX1] $MA_MAX_AX_VELO[AX1] = Up.Velo_X Else $MA_MAX_AX_VELO[AX1] = 1000 EndIf EndIf Example 2 - Alternative condition...
Page 253: Operators
Create MyConfig - Expert 4.6 Script language 4.6.9 Operators 4.6.9.1 Overview operators The following operator groups are available for scripts in dialogs, step scripts, and manipulation tasks: ● Assignment operators (Page 253) ● Arithmetic operators (Page 254) ● Logic operators (Page 255) ●...
Page 254: Arithmetic Operators
Create MyConfig - Expert 4.6 Script language &= AND operation AND logic operation of specified and existing value (resetting bits). Assignment without evaluation Assignment without evaluation to the right of the operator. The value is transferred to the controller as specified. Everything to the right of "="...
Page 255: Logic Operators / Comparison Operators
Create MyConfig - Expert 4.6 Script language Calculations must be set in brackets in order to define a clear sequence. Examples UP.Index=UP.Index +1 $MA_MAX_AX_VELO[AX1]= $MA_MAX_AX_VELO[AX2]*1.3 GUD_1=(100-50)/3 $MN_COMPAR_TYPE_1 = $MN_COMPAR_TYPE_1 | 'B10000' 4.6.9.4 Logic operators / comparison operators Condition- true != false The following logical operations and comparison operators are available to form Boolean expressions: Table 4-15...
Page 256: String Concatenation (Concatenate-Operator)
Create MyConfig - Expert 4.6 Script language The following rules must be observed when using the replacement operator: ● It can only be used with package variables, see Package variables (Page 247). ● During replacement, inverted commas are removed from string values. ●...
Page 257: Functions
Create MyConfig - Expert 4.6 Script language 4.6.10 Functions Note Please note that variables are permissible as arguments for functions. Functions for dialogs, steps, and manipulation jobs The functions described in the following can be used in scripts for dialogs, steps and in manipulation tasks.
Page 258: Input
Create MyConfig - Expert 4.6 Script language Input functions linked to the particular type return a typical value, contrary to input functions that are not linked to a particular type: ● "string" ● "integer" ● "real" ● Enumerator value as "string" ●...
Page 259: Inputenum
Create MyConfig - Expert 4.6 Script language Figure 4-68 Example Input 4.6.10.2 InputEnum InputEnum("<label>","<enum1>;<enum2>") When the InputEnum(label,enums) function is called, when the package is executed, a dialog box is displayed and the operator can make a selection. The chosen string is assigned to an Up variable. ●...
Page 260: Inputtext
Example Input text with and without replacement operators Up.Name = InputText("Enter the machine name.", "'Machine XY'") Figure 4-71 Example Input text without replacement operator Up.FA = "Siemens" Up.Name = "'Machine XY'" Up.Hersteller = InputText("$(up.Name) is manufactured by which company?",up.FA) SINUMERIK Integrate Create MyConfig - Diff, Expert, Topo...
Page 261: Inputint
Create MyConfig - Expert 4.6 Script language Figure 4-72 Example of input text with replacement operator Example of input text for password entry Up.Kennwort = InputText("Enter your password", "*") Figure 4-73 Example of using input text for password entry 4.6.10.4 InputInt InputInt("<label>",<int>) By calling the InputInt function, a dialog is shown during package processing in which the...
Page 262: Inputuint
Create MyConfig - Expert 4.6 Script language Figure 4-74 Example of entering an integer Example of replacement from string, e.g. from an Enum Up.n = "1500" Up.Drehzahl = InputInt("Confirm the speed.", $(Up.n)) Figure 4-75 Example of replacement from string, e.g. Enum (enumeration) 4.6.10.5 InputUInt InputUInt("<label>",<uint>)
Page 263: Inputreal
Create MyConfig - Expert 4.6 Script language Figure 4-76 Example of InputUInt entry unsigned integer number Example of specification with replacement operator Up.Vorgabe = 0x9F Up.Uint = InputUInt("Enter an unsigned integer number", $ (Up.Vorgabe)) Figure 4-77 Example of specification with replacement operator 4.6.10.6 InputReal InputReal("<label>",<real>)
Page 264: Inputchoice
Create MyConfig - Expert 4.6 Script language Figure 4-78 Example of real-number entry Example of specification with variables Up.Exp = 12eX-3 ; = 0.012 Up.RealZahl = InputReal("Input as exponential:", Up.Exp) Figure 4-79 Example of specification with variables 4.6.10.7 InputChoice InputChoice("<label>","<button1>;<button2>") If the function InputChoice is called, a dialog is shown with icons during package execution in which the user can choose directly by pressing individual buttons.
Page 265 Create MyConfig - Expert 4.6 Script language The ("<button>") argument can be used to specify the identifiers for multiple buttons, separated by semicolons. Two successive semicolons cause a line feed, i.e. all of the subsequently listed buttons are displayed in a new line. Thus, buttons can also be arranged amongst one another. The freely selectable identifiers simultaneously define the possible return values of the function.
Page 266 Create MyConfig - Expert 4.6 Script language Figure 4-81 Example for "Information" icon Example Selection with question mark icon Up.retQ = InputChoice("*Q;Beispiel für Symbol '"'Frage'"'", "*&Ja;&Nein") Up.retQ = InputChoice("*Q;Example for Icon '"'InputChoice'"'", "*&Yes;&No") Figure 4-82 Example for "InputChoice" icon Example Selection with warning icon Up.retW = InputChoice("*W;Beispiel für Symbol '"'Warnung'"'", "*&OK;&Abbruch") Up.retW = InputChoice("*W;Example for Icon '"'Warning'"'",...
Page 267 Create MyConfig - Expert 4.6 Script language Up.retE = InputChoice("*E;Example for Icon '"'Error'"'", "*&Abort;&Continue") Figure 4-84 Example for "Error" icon Example Pushbutton operation Up.example = InputChoice("*Q;Beispiel für Schaltflächenbedienung mit * Alt-Tastenkombination * Eingabe * ESC", "*Alt+&A oder Eingabe;Alt+&B;^Alt+&C oder ESC") Up.example = InputChoice("*Q;Example for push-button operation using ...
Page 268: Round
Create MyConfig - Expert 4.6 Script language Figure 4-86 Example of buttons displayed one below the other 4.6.10.8 Round Round("<value>", "<precision>") Values can be rounded using the Round function. The <value> argument describes the identifier (Up variable, machine data, NC data, drive data, display data, etc.), having a value that is to be rounded.
Page 269: Exists
Exists(RTS,"$(UP_PACK)/MyConfig.upcfg");path specification with environment variable under Linux. Exists(RTS,"$(Up.Pfad)/MyConfig.upcfg") ;path specification via up variable. Example display of a message Display of a message if the file "/siemens/versions.xml" has been found on the NCU. IF EXISTS(NCU, "/siemens/versions.xml") Msg("The file versions.xml exists on the NCU.") ENDIF...
Page 270: Version
Observe that only those versions which have also been activated in the project folder when the package was configured can be queried in the areas. For the package area PCU, all of the SIEMENS applications installed on the PCU which have been entered in the registry of the PCU under the key HKEY_LOCAL_MACHINE\SOFTWARE \Siemens\AUTSW are determined.
Page 271: Datetime
Create MyConfig - Expert 4.6 Script language 4.6.10.12 DateTime DateTime("<dt>") The DateTime() function permits the determination and use of the current date and the current time. The format in which the date and time is to be provided is communicated to the function via the argument ("<dt>").
Page 272: Dovar
Create MyConfig - Expert 4.6 Script language 4.6.10.13 DOVar Using the DOVar function, it is possible to generate DO variables during package execution in the script, irrespective of the SINAMICS topologydialog page. The precondition for this is that a SINAMICS has been commissioned without errors and there is a functioning axis-drive assignment.
Page 273: Text Formatting Options
Create MyConfig - Expert 4.6 Script language The following table shows which data is permitted and the point in time up to which it must be written to ensure it still takes effect: Latest point in time for a function call OnInit dialog page system configuration $MN_SINAMICS_MAX_SLAVE_ADDRESS[0-3] Example...
Page 274 Create MyConfig - Expert 4.6 Script language Example of the representation of a header with underscore up.underline=InputReal(" Notice! Please enter a number.",3.0) Figure 4-88 Example of a header with underscore Example of the representation of a bold font up.bold=InputReal(" Notice! Please enter a number.",3.0) Figure 4-89 Example of a header, bold Example of the representation of an italic header...
Page 275 Create MyConfig - Expert 4.6 Script language Example of the representation of a larger header up.big=InputReal("<big>Notice!</big> Please enter a number.",3.0) Figure 4-91 Representation of a larger header Example of the representation of an uppercase header up.header=InputReal("<h1>Notice!</h1>Please enter a number.",3.0) Figure 4-92 Example of a large header in a separate line Example of a header in another font up.type=InputReal("<tt>Notice!</tt>Please enter a number.",3.0)
Page 276 Create MyConfig - Expert 4.6 Script language Example of a header, lowercase up.small=InputReal("Notice!Please enter a number.", 3.0) Figure 4-94 Example of a header, small Example of a header, strikethrough up.scratch=InputReal("<s>Notice!</s>Please enter a number.",3.0) Figure 4-95 Example of the representation of a header, strikethrough Example of an empty line between the header and the text In order to display a warning, for example, a better representation can be achieved via an empty line.
Page 277 Create MyConfig - Expert 4.6 Script language Example of a header in superscript up.sup=InputReal("Notice!Please enter a number.",3.0) Figure 4-97 Example of a header in superscript Example of a header in subscript up.sub=InputReal("Notice!Please enter a number.",3.0) Figure 4-98 Example of a header in subscript Examples of colored headers Some examples of colored texts are shown below.
Page 278 Create MyConfig - Expert 4.6 Script language Figure 4-99 Example of the representation of the header and text in different colors Example of background color Header and text have different background colors, e.g. red and green up.background=InputReal("Notice! Please enter a number.",3.0) Figure 4-100 Example of the representation of text with a background color...
Page 279: Procedures
Create MyConfig - Expert 4.6 Script language Figure 4-101 Example of an invisible table Example of special characters Use the HTML code special characters for the representation. The special characters "less than" and "greater than" are used in the example: up.special=InputReal("Notice! Please enter a number that is <5 and >2.",3.0) Figure 4-102 Example of special characters...
Page 280: Error
Create MyConfig - Expert 4.6 Script language 4.6.11.2 Error Error ("<label>") Message output that must be confirmed with OK and results in termination of the package. Any message text which is also written in the logbook stands for the argument ("<label>") .
Page 281: Extcall
Create MyConfig - Expert 4.6 Script language 4.6.11.6 ExtCall ExtCall("<path>") Call of an external manipulation task. For this task, no verification is performed in Expert and thus no syntax check. The file must be stored in ANSI code. The path can be specified as an absolute path or relative path.
Page 282: Redo
Create MyConfig - Expert 4.6 Script language 4.6.11.9 Redo Redo() This procedure is used in the script of the dialog pages. With OnInit, an error message is displayed in Shield and during the verification run. With OnNext and OnEnd, the command is executed. 4.6.11.10 Patch Patch("<path>")
Page 283: Commenting
Create MyConfig - Expert 4.7 Reference list, system variables 4.6.13 Commenting Commenting - ; Comment Comments are identified by a semicolon as prefix. As a consequence, all of the characters up to the end of the line are no longer evaluated. In order to comment out several lines simultaneously, select the corresponding lines and use Ctrl+K+C.
Page 284: System Variables For The Package Tab
Create MyConfig - Expert 4.7 Reference list, system variables 4.7.2 System variables for the Package tab The following system variables are assigned the Package (Page 106)tab, and are addressed using the prefix Up.$Pack. For all of the system variables, the time until a change of the system variables makes sense and is still effective for the package execution is specified in the respective "Change effective until"...
Page 285: Enumerations
Create MyConfig - Expert 4.7 Reference list, system variables System varia‐ Type Change effective until Description Example bles UserVersion Version/STRING readOnly User version "1.0.0" or "V1.0" or "test" ● As configured in Expert ● As specified by a upcfg file ProdVersion VERSION CMC software version (cannot be...
Page 286: System Variables For The Dialogs Tab
Create MyConfig - Expert 4.7 Reference list, system variables Enumeration runtime system - DeployTarget Area Enumeration Type Change effective until Description Enumeration runtime system - DeployTarget Up.$Pack.DeployTargets. ADDON Enumerator value readOnly Package without the executable part LINUX LINUX package (NCU) WINDOWS Windows package (PC/PCU) Enumeration language preselection - Language...
Page 287: System Variables For The Notes About Acknowledgement Dialog
Create MyConfig - Expert 4.7 Reference list, system variables 4.7.3.2 System variables for the Notes about acknowledgement dialog Table 4-19 Notes about acknowledgment - ConfirmNotes dialog System variables Type Change effective until Description Example Up.$Dialog.ConfirmNotes. Activated BOOL Last script before dia‐ Activating the dialog processing false / true ProcessMode...
Page 288: System Variables For The Select Offline Archive Dialog
Create MyConfig - Expert 4.7 Reference list, system variables System variables Type Change effective until Description Example ProcessMode Enumeration Process‐ Current dialog → OnI‐ Enumeration processing mode Mode (Page 295) $Dialog.ProcessModes.MA NUAL InteractLevel Enumeration InteractLe‐ Enumeration message level vel (Page 295) $Dialog.InteractLevels.
Page 289: System Variables For The Ncu/Ppu Initial State Dialog
Create MyConfig - Expert 4.7 Reference list, system variables System variables Type Change effective until Description Example ProcessMode Enumeration Process‐ Current dialog → OnI‐ Enumeration processing mode Mode (Page 295) $Dialog.ProcessModes.MA NUAL InteractLevel Enumeration InteractLe‐ Enumeration message level vel (Page 295) $Dialog.InteractLevels.
Page 290: System Variables For The Notes On The Service Platform Industry (Gsp) Dialog
Create MyConfig - Expert 4.7 Reference list, system variables 4.7.3.8 System variables for the Notes on the Service Platform Industry (GSP) dialog Table 4-25 Notes on the Service Platform Industry (GSP) dialog - ServiceDataNotes System variables Type Change effective until Description Example Up.$Dialog.ServiceDataNotes.
Page 291: System Variables For The System Configuration Dialog
Create MyConfig - Expert 4.7 Reference list, system variables System variables Type Change effective until Description Example ProcessMode Enumeration Process‐ Current dialog → OnI‐ Enumeration processing mode Mode (Page 295) $Dialog.ProcessModes.MA NUAL InteractLevel Enumeration InteractLe‐ Enumeration message level vel (Page 295) $Dialog.InteractLevels.
Page 292: System Variables For The Notes On The Topology Dialog
Create MyConfig - Expert 4.7 Reference list, system variables System variables Type Change effective until Description Example ProcessMode Enumeration Process‐ Current dialog → OnI‐ Enumeration processing mode Mode (Page 295) $Dialog.ProcessModes.MA NUAL InteractLevel Enumeration InteractLe‐ Enumeration message level vel (Page 295) $Dialog.InteractLevels.
Page 293: System Variables For The Version View Dialog
Create MyConfig - Expert 4.7 Reference list, system variables System variables Type Change effective until Description Example ProcessMode Enumeration Process‐ Current dialog → OnI‐ Enumeration processing mode Mode (Page 295) $Dialog.ProcessModes.MA NUAL InteractLevel Enumeration InteractLe‐ Enumeration message level vel (Page 295) $Dialog.InteractLevels.
Page 294: System Variables For The Step Tree Dialog
Create MyConfig - Expert 4.7 Reference list, system variables 4.7.3.16 System variables for the Step tree dialog Table 4-33 Step tree dialog - StepSelection System variables Type Change effective until Description Example Up.$Dialog.StepSelection. Activated BOOL Last script before dia‐ Activating the dialog processing false / true ProcessMode Enumeration Process‐...
Page 295: System Variables For The Finish Dialog
Create MyConfig - Expert 4.7 Reference list, system variables 4.7.3.18 System variables for the Finish dialog Table 4-35 Finish dialog - PackageEnd System variables Type Change effective until Description Example Up.$Dialog.PackageEnd. Activated BOOL Last script before dia‐ Activating the dialog processing false / true ProcessMode Enumeration Process‐...
Page 296 Create MyConfig - Expert 4.7 Reference list, system variables Enumeration installation modes - Mode Range Enumeration Type Change effective Description CNC software dialog - NcuSetup Enumeration installation modes - Mode Up.$Dialog.NcuSetup.Modes. INSTALL Enumerator value readOnly Installations mode, new installation NONE Installation mode without installation UPDATE Installation mode upgrade...
Page 297: System Variables For The Steps Tab
Create MyConfig - Expert 4.7 Reference list, system variables Range Enumeration Type Change effective Description ARCHIVES Enumerator value readOnly The data are taken from an archive. FACTORY After a PLC memory reset, SDB data are used. ORIGIN The actual SDB data of the PLC - at the time that the package is executed - are used.
Page 298 Create MyConfig - Expert 4.7 Reference list, system variables For all of the system variables, the time until a change of the system variables makes sense and is still effective for the package execution is specified in the respective "Change effective until"...
Page 299 Create MyConfig - Expert 4.7 Reference list, system variables Query step - Up.$Step[id] The Up.$Step[id] system variable can be used to query whether a specific step is available in manipulation tasks, dialog scripts or step scripts. Example CHANDATA(1) If Up.$Step[C_AXIS] != null ;...
Page 300 Create MyConfig - Expert 4.7 Reference list, system variables Example activate step Figure 4-103 Display activate step SINUMERIK Integrate Create MyConfig - Diff, Expert, Topo Operating Manual, 11/2016, A5E36537479B-AD...
Page 301 Create MyConfig - Expert 4.7 Reference list, system variables The step configuration is configured for each step individually, either via the context menu or via the settings of the property field. Note Step activation The step activation can also be configured direct in the step tree and becomes effective immediately.
Page 302 Create MyConfig - Expert 4.7 Reference list, system variables Example execute step Figure 4-104 Display execute step Via the button (Display all system variables via a dialog), you can display the current status of the system variables for each step. Note Executing steps The "Execute"...
Page 303 Create MyConfig - Expert 4.7 Reference list, system variables Observe the type of blocking during step configuration: ● Activation disabled ● Activation disabled including substeps Example activation disabled Figure 4-105 View step - Activation disabled Collapse step(s) - Up.$Step[id].Collapsed Using the system variable Up.$Step[id].Collapsed, the selected step is collapsed in the step tree.
Page 304 Create MyConfig - Expert 4.7 Reference list, system variables Example collapsing steps Figure 4-106 Display collapse step Note Collapse steps When configuring in the step tree, you can continue to have all steps with "Collapsed" status displayed. The steps are identified by the italic font. The "Collapsed"...
Page 305: System Variables For The Environment
System variables for the Type Description Example environment Up.$Env. RunTime RunTimes Enumeration RunTimes STRING NCU type "SIEMENS SINUMERIK 840D sl NCU730.3 PN" (String from hwversion.xml) PLC type "SIEMENS SINUMERIK PLC317-3PN/ DP" (String from hwversion.xml) CFID CF card ID "2009123709B2A62AA61A" (String from hwversion.xml) hwversions.xml on CF card under user/system/etc...
Page 306: Display Cross References
Create MyConfig - Expert 4.8 Cross references 4.8.2 Display cross references Display options There are several ways of displaying cross references. Cross references can be displayed for a project with all linked components, for an individual component or for a cross-reference object (e.g.
Page 307: Search In Cross-References
Create MyConfig - Expert 4.8 Cross references "Folder and file object" tab Object Indicates which file or which folder is involved. Project/compo‐ Indicates in which project or in which component the cross-reference object is located. nent Area/action Indicates in which area of the project folder or in which action of the component the cross-reference object is located.
Page 308: Filter According To Identifier Or Object
Create MyConfig - Expert 4.8 Cross references Extended search using the search dialog The extended search dialog is opened by clicking on the binoculars located to the left of the search field. Under Conditions / Direction, you can define the various search properties. 4.8.4 Filter according to identifier or object A partial string can be entered in the input field by which the column "Identifier"...
Page 309: Transferring A Project/Creating A Package
Create MyConfig - Expert 4.9 Transferring a project/creating a package Example: Transferring a project/creating a package Transmission of a CMC package to a third party Note Legal information on Open Source Software and Commercial off-the-shelf If a CMC package in which Shield with Open Source Software or Commercial off-the-shelf is integrated, is transmitted to a third party, the CMC package must contain explicit information on the legal conditions.
Page 310: Password Protection
Create MyConfig - Expert 4.10 Password protection Procedure The generated Expert projects can be deployed as Windows or Linux packages. These can then be executed under the particular operating system. To create a package, proceed as follows: 1. Select "Project > Deployment" and select whether you want to create a Windows package or a Linux package.
Page 311: Protecting Projects And Components
Create MyConfig - Expert 4.10 Password protection You can use the password list to define various access levels. You can then execute the following activities only by entering the correct password: ● Opening or saving a project or a component. ●...
Page 312: Editing A Password List
Create MyConfig - Expert 4.10 Password protection Access levels Access level Authorizations "Read project" ● Opening a project/component for reading "Change project" ● Opening a project/component for reading ● Changing and saving a project/component "Full access to project" ● Opening a project/component for reading ●...
Page 313 Create MyConfig - Expert 4.10 Password protection You can select the maximum authorizations via the Extended access protection button. If, when opening the password list, other passwords exist with the access level "Full access," these cannot be viewed or modified, however they can be deleted. SINUMERIK Integrate Create MyConfig - Diff, Expert, Topo Operating Manual, 11/2016, A5E36537479B-AD...
Page 314 Create MyConfig - Expert 4.10 Password protection Overview of user interface ① Add "New password" You can add any number of entries to the list using this button. Passwords must be unique. The new entries that are added are allocated default passwords: the first entry is 001, the second 002 etc. These passwords should be changed in order to guarantee the appropriate level of security.
Page 315: Transferring A Password List To Existing Components
Create MyConfig - Expert 4.10 Password protection ⑨ Options ● Password list is always transferred to new internal components: If a new, internal component is created within the project, the password list of the project for this new component will automatically be transferred. ●...
Page 316 Create MyConfig - Expert 4.10 Password protection Overview of the user interface ① Display password If this is activated, the passwords are displayed in plain text. Passwords permitting full access are an exception to this. ② Selecting the target components. ③...
Page 317: Package Execution
Create MyConfig - Expert 4.11 Package execution ⑤ Action The desired actions are defined via the checkboxes: ● Add The password is added to the target component with the associated rights. If the password already exists, the rights are overwritten additively. ●...
Page 318: Executing The Package Under Windows
Create MyConfig - Expert 4.11 Package execution Package execution via NCU To be observed if the Package processing is to access or run on an NCU: To prevent errors during package execution, the NCU system state must be consistent. Before the start of a CMC package, the NCU must be in a state in which the LEDs "RDY" and "RUN"...
Page 319 If an insufficiently current version is found, the package execution installs a current version. (This is a component of the package.) While the package is being executed, with Create MyConfig NcuShareService, folder C: \ProgramData\Siemens\UpNcuShare is released for sharing. Once the package execution has been completed, the service cancels the share again. NcuShareService Service NcuShareService is required to execute CMC packages with an NCU component involving Windows PC or PCU50.
Page 320: Executing The Package On The Pcu 50 From The Network
Create MyConfig - Expert 4.11 Package execution Note In a PCU with Windows 7, various settings are required to permit package execution for automated commissioning. 4.11.2.2 Executing the package on the PCU 50 from the network Windows packages can be executed on the PCU 50. The package is on a network drive. Preconditions The following requirements apply: ●...
Page 321: Package Execution Dialogs
If the package was transferred to a "normal USB Flash Drive" (or hard disk or CD) which cannot be booted because it does not contain a Linux boot system from Siemens, then the NCU starts Linux from the CompactFlash card and then starts the package on the USB medium.
Page 322: Executing The Package On The Ncu From The Usb Media
1. Create an "sci.ini" file with the entry: "Start=<path>/<name>". Example: Start=/card/user/Test.usz 2. Save this file in the "/<responsible>/system/etc" folder of the CompactFlash card. <Responsible> can be "siemens", "addon", "oem" or "user". 3. Click on main switch "Off/On". 4. Follow the instructions of the package dialogs.
Page 323: Executing The Package On The Ncu From The Network
The specification of the domain is optional. Example: Start=//wwprod/user%pass@192.168.100.2/Share/NCU_Pack.usz 2. Save this file in the "/<responsible>/system/etc" folder of the CompactFlash card. <Responsible> can be "siemens", "addon", "oem" or "user". 3. Click on main switch "Off/On". 4. Follow the instructions of the package dialogs.
Page 324: Start Page Logbook
Create MyConfig - Expert 4.11 Package execution Project folder When configuring, you can specify the name and path for the logbook in the project folder on dialog page "Finish". This information is used as user-specified values in the dialog "Save under"...
Page 325 Create MyConfig - Expert 4.11 Package execution Structure when displaying the dialog pages The following information on the dialog pages can be found on the start page of the logbook: ● In a main instance, the titles of dialog pages are shown with a blue background. ●...
Page 326: Package Selection
Create MyConfig - Expert 4.11 Package execution 4.11.4.3 Package selection The package selection is not a dialog page that can be configured. This instance is always displayed in the logbook. The package only automatically displays the Package selection dialog if there is more than one package available for execution - or no package was uniquely started by a (batch) command or double-click.
Page 327: Example Of A Dialog Page: Package Configuration
Create MyConfig - Expert 4.11 Package execution Further information on the system variables can be found in the Reference list system variables (Page 283) section. 4.11.4.4 Example of a dialog page: Package configuration This dialog page is optional; this means that a display is only made in the logbook if it was configured in Expert.
Page 328 Create MyConfig - Expert 4.11 Package execution Display of subinstance Config script - ./DescLogBook_Konfig_1.upcfg Here, changes ("changed") to all system variables as a result of the selected configuration file are displayed. Figure 4-112 Example of a dialog page: Package configuration Display Details on The Details on button is clicked to display all system variables for the configuration file.
Page 329: Example Of A Dialog Page: Cnc Software
Create MyConfig - Expert 4.11 Package execution Figure 4-113 Detailed display - dialog page example: Package configuration 4.11.4.5 Example of a dialog page: CNC software This dialog page is optional; this means that a display is only made in the logbook if it was configured in Expert.
Page 330: Example Of A Dialog Page: Step Tree
Create MyConfig - Expert 4.11 Package execution Information about the logbook The type of message is documented in the logbook; here, information, the message text and the message that the user acknowledged with OK. Figure 4-114 Example of a dialog page: CNC software 4.11.4.6 Example of a dialog page: Step tree This dialog page is optional;...
Page 331 Create MyConfig - Expert 4.11 Package execution Display Dialog page main instance: Step tree Here, using an example, it is shown how a step tree can be structured in the logbook. Figure 4-115 Example, display in the logbook: Dialog page Step tree (button Details on activated) Display, subinstances in the step tree Depending on the configuration, in the step tree there are several subinstances.
Page 332 Create MyConfig - Expert 4.11 Package execution The operations of two responses were obtained in channel 1: ● checked: The value of the 1st machine data is listed as being checked, as the old value already corresponded to the new required value. Old and new values are also listed.
Page 333: Command Line Call
Create MyConfig - Expert 4.12 Command line call Figure 4-116 Example Step tree dialog - display of the step script Subinstance ServiceDate Transfer ServiceDate Transfer belongs to the dialog - Service Platform Industry (GSP). The listed actions are always carried out at the end of the dialog page Step tree, after the archive data transfer, directly in the controller.
Page 334 Create MyConfig - Expert 4.12 Command line call Call The commands subsequently shown and all switches and arguments that are used should be written in one line to a batch file or a command line interface. Note Change to the command line interface CMC 4.7 Command line interfaceCMC 4.7 supports the command line interface documented in versions <...
Page 335 Create MyConfig - Expert 4.12 Command line call Note Path data ● Paths must be specified in double inverted commas if spaces are included Example: "C:\Path with spaces\Expert_Logdatei.xml" ● Paths may never end with '\'. Note Saving batch files Always save batch files with ANSI/ASCII coding. Note Umlauts and special characters Avoid the use of umlauts and special characters in path names.
Page 336 Create MyConfig - Expert 4.12 Command line call Switch Arguments Optional Description /config (<"Path configuration The switch means that after calling Expert after opening the project, file>") the configuration file (*.upcfg) is processed. In addition to the defined system variables, system variables that are equivalent to the out-of-date switches can be included in this config‐...
Page 337: Package Execution
Faults (and possibly alarms) occurred when checking/deploying the package. Command line call error. Example Assumption: Create MyConfig is installed in the directory "C:\Program Files\SIEMENS \Create MyConfig 4.7" and in the path "C:\Packages\" a package "Pack_1.upz" is available. @echo off PATH=%PATH%;"C:\Program Files\SIEMENS\Create MyConfig 4.7"...
Page 338 Create MyConfig - Expert 4.12 Command line call The significance of the switches and arguments is described in the following tableParameters of the package execution. <package> [-hide] [-batch] [-pw:<pass>] Notes Observe the following notes for the command line call: Note Observe the sequence of the switches The switches should be written to in the specified sequence.
Page 339: Sinamics Device Configuration
Create MyConfig - Expert 4.13 SINAMICS device configuration Parameter Table 4-41 Package execution parameters Switch Arguments Description -hide ● This causes the package to be processed without being displayed. ● Implies in the "-batch" option. -batch ● This causes the package selection and the completion message to be bypassed for packages with NCU configuration.
Page 340: Sinamics Device Configuration With Automatic Configuration Or User-Specified Topology
Create MyConfig - Expert 4.13 SINAMICS device configuration 4.13.2 SINAMICS device configuration with Automatic configuration or user-specified topology Applications A differentiation is made between three applications that CMC supports when configuring SINAMICS: 1. The SINAMICS was commissioned previously with SINUMERIK Operate or with a different commissioning software.
Page 341 Create MyConfig - Expert 4.13 SINAMICS device configuration Automatic configuration User-specified topology The step-by-step commissioning is possible only to a limited The step-by-step commissioning is possible almost without extent (e.g. the addition of DQI/SMI motors). limitation (e.g. the addition of DQI/SMI motors). The specification of the comparison topology file allows the The SINAMICS reports an error if the topology specified in DRIVE-CLiQ wiring to be checked.
Page 342: Drive Data Generation Via "Automatic Configuration
Create MyConfig - Expert 4.13 SINAMICS device configuration 4.13.3 Drive data generation via "automatic configuration" Basic procedure The "automatic configuration" via SINUMERIK Operate or via CMC uses the same functions internally. In both cases, the SINAMICS determines its actual topology and saves it as target topology (p9903).
Page 343: Assignment Of The Drive Data Using Do Variables
Create MyConfig - Expert 4.13 SINAMICS device configuration as article number and component type. The structure with generalized drive data is also specified. Finally, the package processing requests the SINAMICS to check this data based on the currently available configuration and to customize it appropriately, i.e. define the DO or component status.
Page 344 Create MyConfig - Expert 4.13 SINAMICS device configuration As a result of the value assignment during the execution of the package, the symbolic path data is replaced with absolute paths and the topology-independent SINAMICS data that do not contain any component numbers are assigned to the drive-specific components in the current topology.
Page 345 Create MyConfig - Expert 4.13 SINAMICS device configuration processing. The properties of the DO variables can only be read in the manipulation tasks and step scripts. Figure 4-119 Assigning DO variables to SINAMICS components Note We recommend that the drive data is assigned to the drive objects via the assignment of DO variables.
Page 346: The Advantages Of Using Comparison Or User-Specified Topology
Create MyConfig - Expert 4.13 SINAMICS device configuration 4.13.6 The advantages of using comparison or user-specified topology The configuration of a comparison or user-specified topology withTopo and the use of the file in the package, offer a number of additional advantages: Advantages for the configuration of the topology with Topo ●...
Page 347: Configuration Of The Topology With Topo
Create MyConfig - Expert 4.13 SINAMICS device configuration ● When a user-specified topology is used, the component numbers must also be specified in addition to the DO names, DO numbers and component names. The use of the DO names, DO numbers and component names corresponds to the above explanations for the comparison topology.
Page 348: Generation Of The Comparison Topology Using External Software
Create MyConfig - Expert 4.13 SINAMICS device configuration With the changeover from comparison topology to user-defined topology, the additional properties DO activation, component activation and component number must also be specified. On switchover to comparison topology, the data remain stored for when switch-back to user- defined topology is performed.
Page 349: Miscellaneous
Create MyConfig - Expert 4.14 Miscellaneous Figure 4-122 Configuration of a CMC package with comparison topology or user-specified topology Compatibility of CMC versions and CNC software releases The Topo XML interface is available in the version SCI 2.6, CMC V4.4/4.5 and CMC V4.6. For transfer, CMC Topo V4.6 no longer supports the Topo XML interfaces SCI 2.6 and CMC V4.4/4.5.
Page 350 Create MyConfig - Expert 4.14 Miscellaneous A USB memory stick can be used without problems on a PC, whereas it cannot be used to run a CMC package on an NCU. This may be due to the partitions or the file system on the USB memory stick.
Page 351: Reimporting Packages
Create MyConfig - Expert 4.15 Reimporting packages 4.15 Reimporting packages 4.15.1 Overview With Expert, packages can be reimported via "Project > Import...", i.e. the project used as basis is regenerated. The complete know-how of the project engineer is in this project. To protect this know-how and prevent unauthorized use of a transferred package, three access levels can be assigned with different authorizations.
Page 352 Create MyConfig - Expert 4.15 Reimporting packages Rules for a reimport ● When opening a reimported project or a reimported component, all passwords are removed that are not identical to the password used for opening. The entry <permissions without password> remains unchanged with its configured rights. In the result, in the password list, there are a maximum of 2 entries;...
Page 353: Create Myconfig - Packages
Create MyConfig - Packages Starting the package execution You will find additional information on package execution in the section Create MyConfig packages (Page 317). Package execution dialog pages The package execution dialog pages are described in the section Dialogs (Page 111) Package execution logbook The package execution logbook is described in the section Package execution logbook (Page 323)
Page 354 Create MyConfig - Packages 5.3 Package execution logbook SINUMERIK Integrate Create MyConfig - Diff, Expert, Topo Operating Manual, 11/2016, A5E36537479B-AD...
Page 355: Create Myconfig - Topo
Create MyConfig - Topo Safety instructions 6.1.1 Fundamental safety instructions 6.1.1.1 General safety instructions WARNING Danger to life if the safety instructions and residual risks are not observed If the safety instructions and residual risks in the associated hardware documentation are not observed, accidents involving severe injuries or death can occur.
Page 356: Industrial Security
Siemens’ products and solutions undergo continuous development to make them more secure. Siemens strongly recommends to apply product updates as soon as available and to always use the latest product versions. Use of product versions that are no longer supported, and failure to apply latest updates may increase customer’s exposure to cyber threats.
Page 357: Introduction
Create MyConfig - Topo 6.2 Introduction Introduction Note Setup of documentation: Operating Manual / Online Help The contents for the section Topo are identical in the operating manual and online help. What is Topo? The Topo software is used in Create MyConfig to configure, display, print, and compare SINAMICS topologies.
Page 358 Create MyConfig - Topo 6.2 Introduction ● Comparison of topologies ● Assignment of module/component properties, such as component name, OEM-ID etc. ● Specification of criteria (Article No.), which the package compares with the actual properties of the SINAMICS modules on the machine to be produced (read-out TARGET topology of the SINAMICS), and reports any impermissible deviations.
Page 359: Overview Of User Interface
Create MyConfig - Topo 6.3 Overview of user interface Overview of user interface 6.3.1 Topo - overview window The following shows the various operating areas of the Topo software user interface: ① "Topologies" ② Topology tree Topology tree/topology graph: ③ Both of these display forms offer the same functionality with regard to creating Topology graph and editing a topology.
Page 360: Topo - Menu Functions
Create MyConfig - Topo 6.3 Overview of user interface 6.3.2 Topo - menu functions Designation Meaning Project <Ctrl+N> Create a new project. Open... <Ctrl+O> Open an existing project (*.uptz). Save <Ctrl+S> Save the current project as *.uptz file. If components are changed, they are marked in the topology tree with an asterisk at the component.
Page 361 Create MyConfig - Topo 6.3 Overview of user interface Designation Meaning <Ctrl+X> Removes the selected components and copies them to the clip‐ board. Copy <Ctrl+C> Copies the selected components to the clipboard. Paste <Ctrl+V> Pastes the components from the clipboard to the selected posi‐ tion.
Page 362: Topo - Operation
● Axis-drive assignment ● Messages ● Language Load module catalogs Opens a list of the available module catalogs for SINUMER‐ IK 828D and SINUMERIK 840D sl, with specification of the CNC and catalog version. Help Contents... <F1> Calls the online help of the Topo program.
Page 363 Create MyConfig - Topo 6.4 Topo - operation numbers determined by SINAMICS are entered in the properties of the components. Further, new DO variables are automatically generated and assigned to the imported components. As from a newer CNC software version, the DO variables used for CNC commissioning are stored in the control and can be assigned and displayed again.
Page 364 Create MyConfig - Topo 6.4 Topo - operation 3. You can now modify the name of the topology and wire the "Bus 3" directly to an NCU. The slave is created automatically. Note Wiring of external CU, e.g. CU320 Note that these cannot be connected to the internal "Bus 3." To do this, first insert the relevant bus 1, 2, 4 ...
Page 365 Create MyConfig - Topo 6.4 Topo - operation 4. The components are wired either from the selected structure node of the tree view or directly from the wiring diagram via the "Connect component" context menu entry. The components that can be used at this point of the topology can be selected from the module catalog and inserted and wired in the list of the used components.
Page 366: Module Catalog
Create MyConfig - Topo 6.4 Topo - operation Additional functions In addition to the standard functions such as "Cut", "Copy", "Paste", etc., the context menu of the topology configurator provides further functions: Function Description Edit If a topology has been read in via an archive, it will be displayed write-protected on a gray background.
Page 367 Create MyConfig - Topo 6.4 Topo - operation There are module catalogs for the corresponding CNC versions. The module catalog can be reloaded under Tools > Load module catalogs. The versions of the loaded catalogs can also be viewed here. Figure 6-3 Modules SINUMERIK Integrate Create MyConfig - Diff, Expert, Topo...
Page 368 Create MyConfig - Topo 6.4 Topo - operation Component properties Each component can be assigned various properties, depending on the device class: Component properties of user-defined topolo‐ Component properties of comparison topology gy (*.utz) (*.ust) Property Description Note Component group Name Name of the component.
Page 369 Create MyConfig - Topo 6.4 Topo - operation Property Description Note K no. The CU-related SINAMICS component number The component number can be edited. The follow‐ is displayed or specified. ing rules apply: ● The SINAMICS component number range is between 1 and 199.
Page 370: Manage Do List
Create MyConfig - Topo 6.4 Topo - operation 6.4.3 Manage DO list The DO list that you can call via the main menu "Data > Manage DO list" is used to manage the DO variables used in the topology project. DO variables can either be created manually or imported from an existing UVD file and then edited.
Page 371 Create MyConfig - Topo 6.4 Topo - operation Property Description Note DO No. DO number via which a drive object is addressed. Only numbers between 2 and 54 as well as 61 and 62 are permitted. For Control Units (CU_I, NX) only a "1" is per‐ missible.
Page 372: Local Do List
Create MyConfig - Topo 6.4 Topo - operation DO type Component type Permitted number Motor module Motor Sensor module Encoder Terminal Module Terminal Board Hub Module NX10 or NX15 Note You can recognize which components are assigned to which DOs. If you select a wired component, the remaining components that are assigned to the same DO are highlighted.
Page 373: Comparing Topologies
Create MyConfig - Topo 6.4 Topo - operation In contrast to older Topo versions, all of the data is now retained after the archive import. DO variables The yellow icon shows that data is already linked at the DO. If the icon is gray , no data is linked.
Page 374 Create MyConfig - Topo 6.4 Topo - operation Two topologies in the current project that have been selected can be compared via the menu "Compare > Refresh" It is also possible to compare a topology in the project with one from an archive or from a .ust or .utz file via the menu "Comparison >...
Page 375: Deploy Topology
Create MyConfig - Topo 6.4 Topo - operation Identifying the differences in the topologies After the topologies have been compared, then the result of the comparison is shown in the lower section. You can jump directly to the location in the topologies where the differences were identified via the context menu "Go to Difference"...
Page 376: Command Line Call
Create MyConfig - Topo 6.5 Command line call Command line call Call The commands subsequently shown and all switches and arguments that are used should be written in one line to a batch file or a command line interface. The meaning of the switches and arguments is described in the following table Topo parameters.
Page 377 Create MyConfig - Topo 6.5 Command line call Note Saving batch files Always save batch files with ANSI/ASCII coding. Note Umlauts and special characters Avoid the use of umlauts and special characters in path names. If special characters or umlauts are to be correctly processed in specified paths, batch files with command line calls must be saved with the same character set as used by the region- specific command line interpreter (cmd.exe).
Page 378 Create MyConfig - Topo 6.5 Command line call Parameter Significance of the switch Table 6-1 Topo parameter Switch Arguments Optional Description <Topology path> ● Specifies the path of the project file – either absolute or relative. ● The path must be specified in double inverted commas if spaces are included in it.
Page 379 Create MyConfig - Topo 6.5 Command line call Switch Arguments Optional Description /autocom‐ ● Automatically adds missing component numbers and plete DO properties and sets up standard encoder assignments if none have been specified. /log <Log file> ● Specifies the path of a log file in either absolute or relative terms.
Page 380: Sinamics Device Configuration
Create MyConfig - Topo 6.6 SINAMICS device configuration Example Precondition: Create MyConfig is installed in the directory "C:\Program Files\SIEMENS\Create MyConfig 4.7" and a project "TopoProj_1.upt" that contains the "Topo1" and "Topo2" topologies is available in the path "C:\Topologie." @echo off PATH=%PATH%;"C:\Program Files\SIEMENS\Create MyConfig 4.7"...
Page 381: Sinamics Device Configuration With Automatic Configuration Or User-Specified Topology
Create MyConfig - Topo 6.6 SINAMICS device configuration 6.6.2 SINAMICS device configuration with Automatic configuration or user-specified topology Applications With regard to device configuration of the SINAMICS, a general distinction is made between three use cases that CMC supports: 1. SINAMICS was commissioned previously with SINUMERIK Operate or with different commissioning software.
Page 382 Create MyConfig - Topo 6.6 SINAMICS device configuration Automatic configuration User-specified topology The step-by-step commissioning is possible only to a limited The step-by-step commissioning is possible almost without extent (e.g. the addition of DQI/SMI motors). limitation (e.g. the addition of DQI/SMI motors). The specification of the comparison topology file allows the The SINAMICS reports an error if the topology specified in DRIVE-CLiQ wiring to be checked.
Page 383: Drive Data Generation Via "Automatic Configuration
Create MyConfig - Topo 6.6 SINAMICS device configuration 6.6.3 Drive data generation via "automatic configuration" Basic procedure The "automatic configuration" via SINUMERIK Operate or via CMC uses the same functions internally. In both cases, the SINAMICS determines its actual topology and saves it as target topology (p9903).
Page 384: Assignment Of The Drive Data Using Do Variables
Create MyConfig - Topo 6.6 SINAMICS device configuration as article number and component type. The structure with generalized drive data is also specified. Finally, the package processing requests the SINAMICS to check this data based on the currently available configuration and to customize it appropriately, i.e. define the DO or component status.
Page 385 Create MyConfig - Topo 6.6 SINAMICS device configuration As a result of the value assignment during the execution of the package, the symbolic path data is replaced with absolute paths and the topology-independent SINAMICS data that do not contain any component numbers are assigned to the drive-specific components in the current topology.
Page 386 Create MyConfig - Topo 6.6 SINAMICS device configuration processing. The properties of the DO variables can only be read in the manipulation tasks and step scripts. Figure 6-10 Assigning DO variables to SINAMICS components Note We recommend that the drive data is assigned to the drive objects via the assignment of DO variables.
Page 387: The Advantages Of Using Comparison Or User-Specified Topology
Create MyConfig - Topo 6.6 SINAMICS device configuration 6.6.6 The advantages of using comparison or user-specified topology The configuration of a comparison or user-specified topology withTopo and the use of the file in the package, offer a number of additional advantages: Advantages for the configuration of the topology with Topo ●...
Page 388: Configuration Of The Topology With Topo
Create MyConfig - Topo 6.6 SINAMICS device configuration ● When a user-specified topology is used, the component numbers must also be specified in addition to the DO names, DO numbers and component names. The use of the DO names, DO numbers and component names corresponds to the above explanations for the comparison topology.
Page 389: Generation Of The Comparison Topology Using External Software
Create MyConfig - Topo 6.6 SINAMICS device configuration With the changeover from comparison topology to user-defined topology, the additional properties DO activation, component activation and component number must also be specified. On switchover to comparison topology, the data remain stored for when switch-back to user- defined topology is performed.
Page 390 Create MyConfig - Topo 6.6 SINAMICS device configuration Figure 6-13 Configuration of a CMC package with comparison topology or user-specified topology Compatibility of CMC versions and CNC software releases The Topo XML interface is available in the version SCI 2.6, CMC V4.4/4.5 and CMC V4.6. For transfer, CMC Topo V4.6 no longer supports the Topo XML interfaces SCI 2.6 and CMC V4.4/4.5.
Page 391: Extended User-Specified Topology
Create MyConfig - Topo 6.7 Extended user-specified topology Extended user-specified topology Requirement As of the Create MyConfig version V4.7there is also the extended user-specified topology as a third mode in addition to the comparison and user-specified topology. Figure 6-14 Extended user-specified topology In addition to the SINAMICS wiring diagram, the extended user-specified topology also includes NC and DRV data.
Page 392 Create MyConfig - Topo 6.7 Extended user-specified topology If individual measuring systems are processed, these must be changed via the data view (see below). Note Measuring system / Motor data Note that it is not possible to assign a measuring system or motor data to a different DO by moving a component.
Page 393: Axis-Drive Assignment
Create MyConfig - Topo 6.8 Axis-drive assignment Deployment methods You can choose between 3 deployment methods: The extended user-specified topology is transferred directly to the controller. The user can optionally select or deselect the PLC and NC data. The extended user-specified topology is deployed as a Windows (.exe) or Linux package (.usz), as is already known from Expert.
Page 394 Create MyConfig - Topo 6.8 Axis-drive assignment If "No" is selected during activation, the stored Axis-drive assignment is not used. Tabular view for configuration Example of a tabular view for configuration Figure 6-16 Table axis-drive assignment - representation standard In the lower status area/legend of the dialog, the assignment colors are explained and the essential axis-drive assignment highlighted.
Page 395: Execution
Create MyConfig - Topo 6.8 Axis-drive assignment Meaning of table columns The table for configuration of the axis-drive assignment is composed of the following table columns: Table column Meaning Axis Display of machine axes AX1 to AX31, including the two possible measurement systems MS1 and MS2. Axis name For the configuration, the machine axis name must be entered that when executing the package was written to MC machine data N10000 $MN_AXCONF_MACHAX_NAME_TAB.
Page 396 Create MyConfig - Topo 6.8 Axis-drive assignment Version 1: Axis-drive assignment using I/O addresses With this selection, the axis numbers are set the same as the drive numbers and the NC I/O address machine data calculated. Horizontal arrows always define default values (default connections) of the NC or SINAMICS software. Figure 6-17 Axis-drive assignment using I/O addresses Version 2: Axis-drive assignment using the drive number...
Page 397 Create MyConfig - Topo 6.8 Axis-drive assignment Axis-drive assignment using "mixed forms" With this type of axis-drive assignmentusers directly or indirectly individually define the assignment using drop-down lists. For the green/blue assignments/arrows, for the drive number and the I/O address, default values are used.
Page 398: Diagnostics
Create MyConfig - Topo 6.8 Axis-drive assignment machine data The following machine data that are listed are automatically set by the CMC package within the course of the axis-drive assignment. Figure 6-20 Machine data - axis-drive assignment Machine data, which are not set by the CMC package and which users must supply with the correct values using a manipulation task, include at least these machine data: ●...
Page 399 Create MyConfig - Topo 6.8 Axis-drive assignment When you open the "Axis-drive assignment" dialog, after importing in the "Axis-drive assignment" dialog, you will see the "Display: Standard". You can change the configuration. The axis drive dialog with "Display: Diagnostics" is not available for the topologies in the topology list.
Page 400: Interface Topo Xml
Create MyConfig - Topo 6.9 Interface Topo XML Interface Topo XML 6.9.1 Example for displaying the wiring using an XML image <?xml version="1.0" encoding="UTF-8"?> <dp preliminary="true" build="008" appVersion="4.7.0.2" version="4.7.0.0"> <bus subsystem="3"> <slave address="3"> <control_unit_ncu doname="NCU_XY" donr="1" dotype="3" dovar="doCU" name="NCU" compnr="1"> <cliq index="0">...
Page 401 Create MyConfig - Topo 6.9 Interface Topo XML <motor name="Motor_Y" compnr="11" group="DQI_Y"/ > </sensor_module> </cliq> <cliq index="2"/> </motor_module> </cliq> <cliq index="2"> <sensor_module name="SM_X" compnr="5" sm="1" doref="doX"> <cliq index="0" uplink="true"/> <encoder name="Encoder_X" compnr="6"/> </sensor_module> </cliq> <motor name="Motor_X" compnr="4"/> </motor_module> </cliq> <cliq index="2"> <sensor_module name="SM2_Y"...
Page 402: Description Of The Xml Structure
Create MyConfig - Topo 6.9 Interface Topo XML 6.9.2 Description of the XML structure SINAMICS components SINAMICS components should be specified in the structure as XML elements based on their device class. To further reduce the recognition tolerance level, restrictive attributes can be specified (order number).
Page 403 Create MyConfig - Topo 6.9 Interface Topo XML DRIVE-CLiQ connection type Analog connection type Power connection type Figure 6-22 S120 Combi topological modeling Automatically created DOs for DRIVE-CLiQ components SINAMICS automatically creates DOs for specific DRIVE-CLiQ components. Automatically created DOs for DRIVE-CLiQ components: control_unit_ncu, motor_module_hf control_unit_nx, control_unit_cu, line_module, motor_module, hub_module, terminal_module,...
Page 404 Create MyConfig - Topo 6.9 Interface Topo XML variable can also be used to specify the user-specific DO name and DO number. For each component that is assigned a DO variable, an appropriate type must also be specified via the "dotype"...
Page 405: Xsd For Xml-Interface
Create MyConfig - Topo 6.9 Interface Topo XML <motor_module nam=“eMM1" dovar="var1" dotype="11" donr="20" doname="do"> <cliq index="0" uplink="true"/> <cliq index="1"/> <cliq index="2"> <sensor_module name="SM1" group="DQI_01" doref="var1" sm="1"> <cliq index="0" uplink="true"/> <encoder name="Enc1" group="DQI_01"/> <motor name="Mot1" group="DQI_01"/> </sensor_module> </cliq> </motor_module> Non-DRIVE-CLiQ components (motor, encoder, sine_filter_module) must be adequately defined using their subordinate hierarchical position.
Page 406 Create MyConfig - Topo 6.9 Interface Topo XML <xs:simpleType> <xs:restriction base="xs:token"> <xs:enumeration value=""/> </xs:restriction> </xs:simpleType> </xs:union> </xs:simpleType> <xs:simpleType name="uShort"> <xs:union> <xs:simpleType> <xs:restriction base="xs:unsignedShort"/> </xs:simpleType> <xs:simpleType> <xs:restriction base="xs:token"> <xs:enumeration value=""/> </xs:restriction> </xs:simpleType> </xs:union> </xs:simpleType> <xs:simpleType name ="smnr"> <xs:restriction base="xs:unsignedShort"> <xs:enumeration value="1"/> <xs:enumeration value="2"/>...
Page 407 Create MyConfig - Topo 6.9 Interface Topo XML <xs:enumeration value="70"/> <xs:enumeration value="200"/>  <xs:enumeration value="201"/>  <xs:enumeration value="204"/>  <xs:enumeration value="207"/>  <xs:enumeration value="3006"/>  <xs:enumeration value="100"/>  <xs:enumeration value="150"/>  <xs:enumeration value="254"/>...
Page 408 Create MyConfig - Topo 6.9 Interface Topo XML  <xs:element name="dp"> <xs:complexType> <xs:sequence> <xs:element name="bus" type="bus" minOccurs="1" maxOccurs="unbounded"/> <xs:element name="ada" type="ada" minOccurs="0" maxOccurs="1" /> </xs:sequence> <xs:attribute name="version" type="xs:string" use="required" fixed="4.7.0.0"/>...
Page 409 Create MyConfig - Topo 6.9 Interface Topo XML </xs:choice> <xs:attribute name="address" type="xs:unsignedInt" use="required"/> </xs:complexType> <xs:complexType name="cliq"> <xs:choice minOccurs="0" maxOccurs="1"> <xs:element name="line_module" type="line_module" minOccurs="0" maxOccurs="1" /> <xs:element name="motor_module" type="motor_module" minOccurs="0" maxOccurs="1" /> <xs:element name="sensor_module" type="sensor_module" minOccurs="0" maxOccurs="1" /> <xs:element name="voltage_sensing_module" type="voltage_sensing_module" minOccurs="0" maxOccurs="1" /> <xs:element name="cu_link"...
Page 410 Create MyConfig - Topo 6.9 Interface Topo XML <xs:attribute name="doname" type="xs:string" use="optional" / > <xs:attribute name="dodesc" type="xs:string" use="optional" / > </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="dostatecomp" abstract="true"> <xs:complexContent> <xs:extension base="docomp"> <xs:attribute name="dostate" type="state" use="optional" /> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="dorefcomp" abstract="true"> <xs:complexContent>...
Page 411 Create MyConfig - Topo 6.9 Interface Topo XML </xs:complexContent> </xs:complexType> <xs:complexType name="control_unit_cu"> <xs:complexContent> <xs:extension base="docomp"> <xs:sequence> <xs:element name="cliq" type="cliq" minOccurs="1" maxOccurs="4" /> <xs:choice minOccurs="1" maxOccurs="1"> <xs:element name="terminal_board" type="terminal_board" minOccurs="0" maxOccurs="1" /> <xs:element name="comm_board" type="comm_board" minOccurs="0" maxOccurs="1" /> </xs:choice> </xs:sequence> </xs:extension> </xs:complexContent>...
Page 412 Create MyConfig - Topo 6.9 Interface Topo XML </xs:complexContent> </xs:complexType> <xs:complexType name="motor_module"> <xs:complexContent> <xs:extension base="motor_module_base"> <xs:sequence> <xs:element name="motor" type="motor" minOccurs="0" maxOccurs="1" /> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="motor_module_hf"> <xs:complexContent> <xs:extension base="motor_module_base"> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="damping_module"> <xs:complexContent> <xs:extension base="dorefcomp"> <xs:choice maxOccurs="2"> <xs:element name="cliq"...
Page 413 Create MyConfig - Topo 6.9 Interface Topo XML <xs:element name="cliq" type="cliq" minOccurs="1" maxOccurs="1" /> <xs:element name="encoder" type="encoder" minOccurs="0" maxOccurs="1" />  <xs:element name="motor" type="motor" minOccurs="0" maxOccurs="1" />  </xs:sequence> <xs:attribute name="sm" type="smnr" use="optional"/> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="voltage_sensing_module">...
Page 414 Create MyConfig - Topo 6.9 Interface Topo XML <xs:sequence> <xs:element name="actuator" type="actuator" minOccurs="0" maxOccurs="1" /> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="actuator">  <xs:complexContent> <xs:extension base="compbase"/> </xs:complexContent> </xs:complexType> <xs:complexType name="hub_module"> <xs:complexContent> <xs:extension base="dostatecomp"> <xs:sequence> <xs:element name="cliq" type="cliq" minOccurs="6" maxOccurs="6" /> </xs:sequence>...
Page 415 Create MyConfig - Topo 6.9 Interface Topo XML </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="ada"> <xs:sequence> <xs:element name="ada_ctrl" type="ada_ctrl" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> <xs:attribute name="mode" type="adamode" /> </xs:complexType> <xs:complexType name="ada_ctrl"> <xs:sequence> <xs:element name="ada_enc" type="ada_enc" minOccurs="0" maxOccurs="2"/> </xs:sequence> <xs:attribute name="axnr" type="axdrnr" use="required" /> <xs:attribute name="axname" type="xs:string" use="optional" /> <xs:attribute name="drnr"...
Page 416 Create MyConfig - Topo 6.9 Interface Topo XML SINUMERIK Integrate Create MyConfig - Diff, Expert, Topo Operating Manual, 11/2016, A5E36537479B-AD...
Page 417: Create Myconfig - Ncushare
Create MyConfig - NcuShare Introduction 7.1.1 NcuShareService An exchange release is required for processing Windows packages with NCU share. The previous configuration of the exchange release is replaced with the NcuShareService "Create MyConfig NcuShare". A setup is available for the installation of the service. Installation 7.2.1 Installation...
Page 418: Error Checking
Create MyConfig - NcuShare 7.3 Error checking Error checking What must be checked in the event of an error? Use of virtual machines (VMWare) In connection with virtual machines (VMWare), problems may occur when establishing a connection, because the release of the NCU cannot be achieved. To ensure the NcuShareService functions properly, the virtual machine must be operated in "Bridged Mode".
Page 419 Create MyConfig - NcuShare 7.3 Error checking Observe the following when setting the properties of the Create MyConfig NcuShare: 1. In the General tab, select the Type of start "Manually". Figure 7-1 Create MyConfig NcuShare - General tab 2. In the Login tab, select the option "Local system account". SINUMERIK Integrate Create MyConfig - Diff, Expert, Topo Operating Manual, 11/2016, A5E36537479B-AD...
Page 420 Create MyConfig - NcuShare 7.3 Error checking Figure 7-2 Create MyConfig NcuShare - Login tab Changing the release folder The release folder is defined during the installation of the "UpNcuShareService". In case of an installation with Create MyConfig or manual setups, the user can change the path during the installation.
Page 421: List Of Abbreviations
List of abbreviations Abbreviations Axis-drive assignment Automatic device configuration (per HMI) Create MyConfig Computerized Numerical Control Control Unit Data Block Drive Object Drive Data EUNA End User Notification Administration; is replaced by Service Platform Industry (GSP) as from Version V4.7. Function Block Function Global Service Platform;...
Page 422 List of abbreviations A.1 Abbreviations *.uss Step XML, step properties Note From version V4.7 SP1 and higher, to maintain compatibility to previous CMC versions, the USS file is still supported; however, it can no longer be created in Expert. *.ust Comparison topology *.usz Executable Linux package...
Page 423: Index
Index machine data, 398 User-defined, 397 "Create MyConfig NcuShare" service, 417 Buttons for dialogs, 126 Step tree, 198 $Pack, 285 CHANDATA(1), 39, 89, 239 828D, 3, 23, 105, 139, 362 Change 840D sl, 3, 23, 139, 362 Component editor, 230 Change action Preprocessor script, 230 Change operations, 234...
Page 424 Index Commissioning engineer/operator NCU/PPU access, 139 Archive data transfer, 189 NCU/PPU initial state, 142 CNC software, 157 NCU/PPU result state, 190 NCU/PPU access, 141 Notes about acknowledgment, 126 NCU/PPU initial state, 145 Notes on GSP, 146 NCU/PPU result state, 193 Notes on the package, 129 Notes about acknowledgment, 128 Notes on the step tree, 182...
Page 425 Index Created user, 418 Dialog scripts Installation, 417 Event, 116 Release folder, 420 Dialogs tab Created user Overview, 114 Create MyConfig NcuShare, 418 Diff Cross reference objects, 305 Command line call, 82 Cross references Example, 85 Displaying, 306 Introduction, 23 Search, 308 Parameter, 84 CU320, 106...
Page 426 Index DO variables InputText, 260 Assignment options, 345, 386 InputUInt, 262 Properties, 344, 385 Match, 268 DOVar, 272 Package execution, 339 Downlink port: Prepare, 273 Rewire, 366 Topo, 380 Drive data, 244 Version, 270 DriveTopology, 293 Examples DriveTopologyNotes, 292 Programming options, 273 DrvSource, 297 Execute Component editor, 219...
Page 427 Index Finish InteractLevel, 296 Configuration, 194 Package execution, 195 Folder comparison Archive types, 65 K no., 369 Configuration, 60 K status, 369 Overview, 52 Overview window, 56 Toolbar, 53 Function DateTime, 271 Language, 286 DOVar, 272 Line checksum, 239 Exists, 269 Link step Input("<label>"), 258 copy, 211...
Page 428 Index Number, 86 Space characters, 86 Square bracket, 86 Tab stop character, 86 OEM ID, 369 Tabulator, 86 OnEnd, 117 Underscore, 86 OnInit, 117 Unicode character, 86 OnNext, 117 Mode, 296 Operators, 235 Options menu Topo, 362 Name, 368 Namespace Logbook entry, 210 Package Query steps, 209...
Page 429 Manual DO variable assignment, 178 Package execution, 175 User-specified topology, 177 Quantifier, 87 SINUMERIK 828D, 139 Query step SINUMERIK 840D sl, 3 Example, 299 SINUMERIK archive, 52, 64 SINUMERIK Integrate Create MyConfig - Diff, Expert, Topo Operating Manual, 11/2016, A5E36537479B-AD...
Page 430 String concatenation, 256 Window, 29 Support SINUMERIK 828D, 3, 23, 105, 139, 362 CU320, 106 HW Config, 105 Switch SINUMERIK 840D sl, 23, 139, 362 Diff, 84 Source explorer Expert, 335 Copy, 101 Topo, 378 Double-click, 101 System configuration, 340, 381...
Page 431 Index for dialog, system configuration - TGZ archive, 52, 64 SystemConfig, 292 Toolbar for Notes on topology dialog - File comparison, 67 DriveTopologyNotes, 292 Folder comparison, 53 for SINAMICS topology dialog - SINUMERIK archive comparison, 25 DriveTopology, 293 Steps tab, 198 for the dialog CNC software - NcuSetup, 291 Toolbars for the dialog NCU/PPU result state -...
Page 432 Index Up.$Dialog.SystemConfig, 292 Windows package, 98 Up.$Dialog.VersionView, 293 Network drive, 320, 323 Up.$Pack.ARC, 285 PCU 50, 320 Up.$Pack.DeployDir, 284 Up.$Pack.DeployExclude, 284 Up.$Pack.DeployName, 284 Up.$Pack.DeployTarget, 284 XML structure Up.$Pack.Dir, 285 cliq, 405 Up.$Pack.Language, 284 doref, 404 Up.$Pack.Name, 285 dovar, 404 Up.$Pack.NCU, 285 index, 405 Up.$Pack.PCU, 285 oemid, 405...

This manual is also suitable for:

Sinumerik 828d

Siemens SINUMERIK 840D sl Operating Manual

1 Safety Information

2 Installation

3 Create Myconfig - Diff

4 Create Myconfig - Expert

5 Create Myconfig - Packages

6 Create Myconfig - Topo

7 Create Myconfig - Ncushare

Quick Links

Related Manuals for Siemens SINUMERIK 840D sl

Summary of Contents for Siemens SINUMERIK 840D sl