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 - FAQs...
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
Benefits Engineering software Create MyConfig supports the machine manufacturer to create and run a project for automated production and commissioning of machines with SINUMERIK 840D sl or SINUMERIK 828D controls. These controls can also be upgraded for end users, and automatically executed.
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 (https:// support.industry.siemens.com/cs/de/en/ps/faq).
Page 5: Table Of Contents
Table of contents Preface.................................3 Safety information............................13 Fundamental safety instructions....................13 1.1.1 General safety instructions.....................13 Warranty and liability for application examples..............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........................18 2.2.3 Modifying installed program parts..................19 Create MyConfig - Diff ..........................21 Safety instructions........................21 3.1.1...
Page 6 4.2.5 Converting projects from existing CMC versions..............134 4.2.5.1 Conversion...........................134 4.2.5.2 Changes to system variables....................135 System support........................136 4.3.1 Differences during commissioning between SINUMERIK 840D sl and SINUMERIK 828D..136 4.3.2 Support CU320........................136 Project folder........................137 4.4.1 Package..........................137 4.4.1.1 Specifying the configuration for Package................137 4.4.2...
Page 7 Table of contents 4.4.2.1 Dependency of the dialog pages on data areas..............144 4.4.2.2 Dialog scripts........................145 4.4.2.3 Examples of scripts in the dialog pages................149 4.4.2.4 Package configuration (configuration)..................151 4.4.2.5 Package configuration (package execution)................154 4.4.2.6 Notes about acknowledgment (configuration)..............155 4.4.2.7 Notes about acknowledgment (package execution)............157 4.4.2.8 Notes on the package (configuration)..................158 4.4.2.9...
Page 8 Table of contents Component editor.........................252 4.5.1 Action scripts........................253 4.5.2 Execute..........................256 4.5.3 Delete...........................261 4.5.4 Copy.............................263 4.5.5 Change..........................266 4.5.6 Manipulate..........................274 4.5.6.1 Additional useful notes on the "Manipulate action"..............277 Script language........................279 4.6.1 Locations where the script languages is used..............279 4.6.2 Color coding of language elements..................280 4.6.3 Set channel..........................281 4.6.4...
Page 9 Table of contents 4.6.10.11 Text formatting options......................320 4.6.11 Resources..........................326 4.6.12 Miscellaneous........................327 4.6.12.1 Skip............................327 4.6.12.2 Redo.............................327 4.6.12.3 Return..........................327 4.6.12.4 ExtCall..........................328 4.6.12.5 DateTime..........................328 4.6.12.6 DOVar..........................329 4.6.12.7 Log............................330 4.6.12.8 Logging..........................330 4.6.12.9 MathRound...........................331 4.6.12.10 Version..........................331 4.6.13 Preprocessor........................332 4.6.13.1 #include..........................332 4.6.14 Data access operations......................333 4.6.15 Package variables........................336 4.6.15.1 Script variables........................336...
Page 10 Table of contents 4.7.11 Language selection......................366 4.7.12 Linking steps........................367 4.7.13 Conversion from projects with CMC version < version 4.8..........367 Reference list, system variables..................368 4.8.1 General information about system variables................368 4.8.2 System variables for the Package tab..................368 4.8.2.1 Package enumerators......................371 4.8.3 System variables for the Dialogs tab..................372 4.8.3.1 System variables for the Package configuration dialog............372...
Page 11 Table of contents 4.12.3.2 Package execution on the NCU/PPU from the USB medium..........409 4.12.3.3 Package execution on NCU/PPU from the CompactFlash card..........410 4.12.3.4 Package execution on the NCU/PPU from the network............410 4.12.3.5 Package execution dialogs....................411 4.12.4 Package execution logbook....................411 4.12.4.1 General information about the logbook................411 4.12.4.2 Start page logbook.......................412...
Page 12 Table of contents 6.4.4 Manage DO list........................470 6.4.4.1 Local DO list.........................473 6.4.4.2 Generating DO variables automatically................475 6.4.4.3 Extended DO list........................476 6.4.4.4 Predefined axis assignment for the EPLAN add-in..............482 6.4.5 Comparing topologies......................482 6.4.6 Deploy topology........................484 Axis-drive assignment......................485 6.5.1 Configuration........................485 6.5.2 Execution..........................487 6.5.3 Diagnostics...........................490 Command line call........................491...
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 engineering software "Create MyConfig" and the "NcuShareService" application on your PC: ● Installation using the installation wizard The CMC package is installed using the general setup. The general setup involves the installation of Create MyConfig - and the installation of Application License Managers (ALM).
Page 16 Deselection of the installation drive / Selection of installation drive #DestinationDrive=C --- DestinationPath --- Selection of the installation path / Selection of installation path default (Windows 64 Bit): "\Program Files\Siemens\Automation \SINUMERIK\Create MyConfig 4.8" SINUMERIK Integrate Create MyConfig - Diff, Expert, Topo Operating Manual, 12/2017, A5E36537479B-AE...
Page 17 Installation 2.2 Installation via command line default (Windows 32 Bit): "\Program Files (x86)\Siemens \Automation\SINUMERIK\Create MyConfig 4.8" #DestinationPath="\Program Files\Siemens\Automation\SINUMERIK \Create MyConfig 4.8" --- Features --- Selection of the components to be installed Selection of components to be installed #Features=Diff,Expert,Topo,Samples --- Settings ---...
Page 18: Command Line Call
Installation 2.2 Installation via command line [SETUPREQUESTS] SetupMode=Batch 2.2.2 Command line call Syntax for the command line call setup.exe /W /L<Language ID> /V"commandline=\"\"\"-OF:<absolute path \>OPFILE.txt\"\"\"" Options and arguments Options Arguments and description <Language ID> Option L (language) indicates the language ID for displaying the language in the dialogs and messages.
Page 19: Modifying Installed Program Parts
Installation 2.2 Installation via command line setup.exe /W /L1031 /V"commandline=\"\"\"-OF:D:\mySetupConfiguration \OPFILE.txt\"\"\"" 2.2.3 Modifying installed program parts The program components Diff, Topo, Expert and Samples can be subsequently individually added - or removed if they had been installed. There are three versions: Version 1 1.
Page 20 Installation 2.2 Installation via command line SINUMERIK Integrate Create MyConfig - Diff, Expert, Topo Operating Manual, 12/2017, A5E36537479B-AE...
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 Main menus The main menus in Diff are identical. The submenus are adapted dynamically to the associated SINUMERIK archive comparison, Folder comparison or File comparison component. The following main menus and submenus are provided in the SINUMERIK archive comparison: Table 3-1 Diff - SINUMERIK archive comparison - File main menu...
Page 26 Create MyConfig - Diff 3.3 SINUMERIK archive comparison Edit Delete <Del> Deletes the currently selected objects. Select All <Ctrl+A> Selects all lines of a folder or data node. Change <F2> Changes the value of a line, provided editing mode is activated and editing is permissible here.
Page 27 Create MyConfig - Diff 3.3 SINUMERIK archive comparison Comparison Edit configuration... <Ctrl+M> Clicking the "Edit configuration..." button changes a comparison config‐ uration or selects a different comparison configuration. For more information, refer to the Configuration - SINUMERIK archive comparison (Page 40) section. Select configuration Standard Switches the comparison configu‐...
Page 28 Create MyConfig - Diff 3.3 SINUMERIK archive comparison Table 3-5 Diff - SINUMERIK archive comparison - Tools main menu Tools Options... Opens the "Options" dialog with the tabs described below. Options can be activated or deactivated for representation/execution of Diff components.
Page 29 Create MyConfig - Diff 3.3 SINUMERIK archive comparison Tools ● Right - Blue ● Left - LimeGreen ● Not present in all comparison objects - DarkGrey Language Language selection of the Diff interface. Available languages are: ● German ● English Data comparison Data comparison configuration...
Page 30 Create MyConfig - Diff 3.3 SINUMERIK archive comparison Table 3-6 Diff - SINUMERIK archive comparison - Window main menu Window New horizontal tab group Displays the selected component in the new horizontal tab group. New vertical tab group Displays the selected component in the new vertical tab group. Move to previous tab group Moves the selected component to the previous tab group.
Page 31: Sinumerik Archive Comparison - Toolbar
Create MyConfig - Diff 3.3 SINUMERIK archive comparison 3.3.2.2 SINUMERIK archive comparison - Toolbar ① New SINUMERIK archive comparison ② New folder comparison ③ New file comparison ④ Update comparison ⑤ Display/save HTML/XML protocol ⑥ Comparison configuration ⑦ Copy / Insert ⑧...
Page 32 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 33: Sinumerik Archive Comparison - Overview Window
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 34 Create MyConfig - Diff 3.3 SINUMERIK archive comparison Data view tab - Normal tab ① Data view tab ② Folder view tab ③ Editing mode ④ Normal tab ⑤ Selective tab ⑥ Extend selection / Reduce selection Figure 3-2 Diff - window: Data view tab - Normal tab SINUMERIK Integrate Create MyConfig - Diff, Expert, Topo Operating Manual, 12/2017, A5E36537479B-AE...
Page 35 Create MyConfig - Diff 3.3 SINUMERIK archive comparison Data view tab - Selective tab ⑦ Display result: Different / Equal / Not available in all comparison objects ⑧ Configuration, expert list, filter, value comparison ⑨ Context menu ⑩ Display short description for the marked parameters ⑪...
Page 36 Create MyConfig - Diff 3.3 SINUMERIK archive comparison Folder view tab ⑰ Archive display area ⑱ Folder comparison display area ⑲ Configuration and filters display ⑳ Comparison results display: Available only left / Different / Equal / Available only right Figure 3-4 Diff - window: Folder view tab Description of the areas/functions in the SINUMERIK archive comparison window...
Page 37 Create MyConfig - Diff 3.3 SINUMERIK archive comparison ③ Editing mode button Editing mode can be activated or deactivated by clicking the button. Only in activated editing mode can values or identifiers be changed, deleted or added in the Data view or Folder view tabs.
Page 38 Create MyConfig - Diff 3.3 SINUMERIK archive comparison In the "Selective" comparison mode, the data structures of all comparison objects (archives, files) are placed one below the other - the structure is separately established for every comparison object. Contrary to the "Normal" comparison mode, in the "Selective" comparison mode, all data end nodes of the same type can be compared with one another as required.
Page 39 Create MyConfig - Diff 3.3 SINUMERIK archive comparison 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 40: Configuration
Create MyConfig - Diff 3.3 SINUMERIK archive comparison 3.3.3 Configuration SINUMERIK archive comparison The dialog for the configuration of the SINUMERIK archive comparison is called via the "Comparison configuration" button. Different comparison configurations, i.e. create, edit, delete, etc., can be managed in the "Configuration - NC data comparison" dialog. All criteria to be considered for a SINUMERIK archive comparison are defined in a comparison configuration.
Page 41 Create MyConfig - Diff 3.3 SINUMERIK archive comparison ① List of the available comparison configurations The existing comparison configurations are listed in this area of the configuration dialog and can be selected by clicking 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 42 Create MyConfig - Diff 3.3 SINUMERIK archive comparison A $MA_CTRLOUT_NR entry in an inclusion list includes all identifiers that belong to this field, i.e. $MA_CTRLOUT_NR[0] and $MA_CTRLOUT_NR[1]. ① Using the expert list ② Import... button ③ Extracting identifiers button ④ Combining indices button ⑤...
Page 43 Create MyConfig - Diff 3.3 SINUMERIK archive comparison $MN_AXCONF_MACHAX_NAME_TAB[3] → $MN_AXCONF_MACHAX_NAME_TAB The indices are removed and only one data item without indices remains in the list. The first comment on the data is retained at this data item. ⑤ Include/exclude data with identifiers Here, you specify whether the listed identifiers and your data are to be included or excluded for the comparison.
Page 44 Create MyConfig - Diff 3.3 SINUMERIK archive comparison ① Activate filter By selecting "Include/exclude data with block numbers or identifiers by way of a filter", the functionality of the inclusion and exclusion filter is activated. Note If a filter is active, then all of the identifiers that have been filtered-out are not displayed and are also not compared.
Page 45 Create MyConfig - Diff 3.3 SINUMERIK archive comparison Value range tab In the "Value range" tab, the value-based comparison of floating-point numbers is displayed at significant points. Floating point numbers are saved separately and internally in the computer in mantissa and exponent.
Page 46: Copying/Exporting Data From The Sinumerik Archive Comparison
Create MyConfig - Diff 3.3 SINUMERIK archive comparison 3.3.4 Copying/exporting data from the SINUMERIK archive comparison In the SINUMERIK archive comparison, data identifiers and the associated values can be copied to the clipboard or exported to a file. For instance, the copied or exported data can be used in manipulation tasks of Expert, in Excel for documentation, in another software application or where relevant, also in a SINUMERIK archive comparison in Diff.
Page 47 Create MyConfig - Diff 3.3 SINUMERIK archive comparison Using the "Copy" or "Data export to file..." context menu entries, you can transfer the selected values and their identifiers to the clipboard or 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 p100=0...
Page 48 Create MyConfig - Diff 3.3 SINUMERIK archive comparison The identifiers extracted by Diff are fully qualified, i.e. they again include the definition of the axis to which the data belongs. Note CHANDATA(1) is also automatically added for channel-independent data as this guarantees that a previous channel assignment greater than 1 is reset again.
Page 49: Pasting/Importing Data In The Si
Create MyConfig - Diff 3.3 SINUMERIK archive comparison p141 [0] p141 [1] p142 [0] p142 [1] 3.3.5 Pasting/importing data in the SI Introduction In the SINUMERIK data comparison, data can be pasted from the clipboard or imported from a file. This function is available only in the "Selective"...
Page 50 Create MyConfig - Diff 3.3 SINUMERIK archive comparison Figure 3-5 Pasting/importing data to the SINUMERIK data 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" values for the identifiers found.
Page 51: Data Jobs In The Sinumerik Archive Comparison
Create MyConfig - Diff 3.3 SINUMERIK archive comparison "Pasting preview" dialog To show what the result of pasting or importing values will be before values are actually pasted or imported, Diff displays the "Pasting preview" dialog. Figure 3-6 Pasting preview The following information is shown in the dialog: ●...
Page 52: Configuring Data Jobs
Create MyConfig - Diff 3.3 SINUMERIK archive comparison Application examples for data tasks ● Importing encoder data. Encoder data saved in an Excel file (template) can be imported into an archive. ● Exporting optimization data. For the identifiers of optimization data saved in an Excel template, values can be added and saved as Excel file.
Page 53 Create MyConfig - Diff 3.3 SINUMERIK archive comparison Task type tab Select the task types in the "Task type" tab: ● Data conversion ● Data export ● Data import SINUMERIK Integrate Create MyConfig - Diff, Expert, Topo Operating Manual, 12/2017, A5E36537479B-AE...
Page 54 Create MyConfig - Diff 3.3 SINUMERIK archive comparison Template tab You can store an Excel template in 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 55 Create MyConfig - Diff 3.3 SINUMERIK archive comparison Export tab The export area of the identifiers and values are specified in the Excel template in the "Export" tab. Further, a node type in the data structure tree must be specified in this tab. An export or conversion task can only be started at this node type.
Page 56: 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 57 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 58 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 59 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 60 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 61: Data Class Archives
Create MyConfig - Diff 3.3 SINUMERIK archive comparison 3.3.7 Data class archives Value change in data class archives A data class archive can be opened and edited like a normal SINUMERIK archive in the SINUMERIK archive comparison. A feature of the *.ard archive is that values in data classes can only be changed.
Page 62 Create MyConfig - Diff 3.3 SINUMERIK archive comparison 3. In the opened data class archive, you can change the associated values in the "Data view" tab > "Normal" tab or "Selective" tab in activated editing mode. Figure 3-8 Data class archive: Changing values in editing mode 4.
Page 63: Scripts In Diff
Create MyConfig - Diff 3.3 SINUMERIK archive comparison Figure 3-9 Data class archive: Copying and pasting values 3.3.8 Scripts in Diff 3.3.8.1 Data accesses / sections The data accesses function as described at CMC Expert in Section Data accesses (Page 333). Always use fully qualified identifiers in the script.
Page 64: Creating And Editing Scripts
Create MyConfig - Diff 3.3 SINUMERIK archive comparison 3.3.8.2 Creating and editing scripts You can use CMC scripts in Diff on opened archives in order, for example, to make extended data exports from archives, without having to create a CMC package. You can also manipulate data.
Page 65 Create MyConfig - Diff 3.3 SINUMERIK archive comparison Figure 3-11 Selection of the parser type Main menus The following main menus are available for the Script Editor. Table 3-10 File main menu File <Ctrl+N> Creates a new script file with the "*.upscr" file extension. Open <Ctrl+O>...
Page 66: Call Of Scripts
Create MyConfig - Diff 3.3 SINUMERIK archive comparison Table 3-12 Help main menu Help Content... <F1> Opens the online help for the Script Editor. In the opened online help, you can navigate to the desired topics of Diff or Expert. About...
Page 67: Command Line Call
Create MyConfig - Diff 3.3 SINUMERIK archive comparison Figure 3-13 Call of a Diff script in selective mode System variables The following query of the system variables (read-only) indicates whether Diff is in the editor mode: "UP.$Script.EditMode == TRUE" If the script is called from the command line, this query is not required. 3.3.8.5 Command line call Diff scripts can also be started without the graphic user interface of Diff via the command line.
Page 68: Folder Comparison
Create MyConfig - Diff 3.4 Folder comparison Further information on TraceToFile() can be found at Expert in Section "File operations" > "TraceToFile (Page 293)". 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.
Page 69 Create MyConfig - Diff 3.4 Folder comparison The following main menus and submenus are provided in the Folder comparison: Table 3-13 Diff - Folder comparison - File main menu File SINUMERIK archive comparison... Opens a new SINUMERIK archive comparison. Folder comparison... Opens a new Folder comparison.
Page 70 Create MyConfig - Diff 3.4 Folder comparison Table 3-15 Diff - Folder comparison - View main menu View Available only on the <Ctrl+Shift+L> Displays those objects available only in the left-hand comparison ob‐ left-hand side ject. The display can be activated or deactivated: Different <Ctrl+Shift+D>...
Page 71 Create MyConfig - Diff 3.4 Folder comparison Table 3-17 Diff - Folder comparison - Tools main menu Tools Options... Opens the "Options" dialog with the tabs described below. Options can be activated or deactivated for representation/execution of the Diff components. All options are activated as default. The Diff coloration and the language setting can be changed user-de‐...
Page 72 Create MyConfig - Diff 3.4 Folder comparison Tools This is useful, for example, for a red-green sight impediment. The standard setting can be re‐ stored: ● Unequal - Red ● Equal - Black ● Right - Blue ● Left - LimeGreen Language Language selection of the Diff in‐...
Page 73 Create MyConfig - Diff 3.4 Folder comparison Tools Export configurations... The following configuration types and the associated files can be se‐ lected or deselected in the "Export configurations" dialog: ● Archive/folder comparison configurations ● File comparison configurations ● Data comparison configurations ●...
Page 74: Folder Comparison - Toolbar
Create MyConfig - Diff 3.4 Folder comparison 3.4.2.2 Folder comparison - toolbar ① Buttons forEdit mode - Synchronize - Copy ② New folder comparison Calling a folder comparison. ③ Toggling between opened comparisons (tab) ④ Update comparison ⑤ Display/save HTML/XML report ⑥...
Page 75 Create MyConfig - Diff 3.4 Folder comparison Note Changes become effective immediately Changes in a folder become effective immediately in the original folder and cannot be saved again. As a consequence, the floppy disk icon remains deactivated. The content of the left-hand comparison object can be synchronized with the content of the right-hand comparison object using the "Syn‐...
Page 76 Create MyConfig - Diff 3.4 Folder comparison ⑨ Button group comparison results The associated lines of the comparison result can be hidden or displayed using this group of buttons. ⑪ Switchover between tree and list display. Improved synchronization functionality is obtained by being able to toggle. ⑫...
Page 77: Folder Comparison - Overview Window
Create MyConfig - Diff 3.4 Folder comparison 3.4.2.3 Folder comparison - overview window Below is an overview of the functions in the folder comparison window. ① Folder structure - Representation of the folders with the associated comparison objects in the tree structure ②...
Page 78 Create MyConfig - Diff 3.4 Folder comparison Description of the areas/functions in the Folder comparison window The individual functions of the folder comparison are described in more detail below: ① Folder structure - Representation of the folders with the associated comparison objects in the tree structure In this area, the folders of the comparison objects are shown in a tree structure arranged one on top of the other.
Page 79 Create MyConfig - Diff 3.4 Folder comparison Significance of the comparison icons: A green arrow indicates that the folder is only available in the left-hand comparison object. The unequal character indicates that the contents of the folder are not identical. The equal character indicates that the contents of both folders are identical.
Page 80: Changing The Column Arrangement
Create MyConfig - Diff 3.4 Folder comparison 3.4.3 Changing the column arrangement Changing the column arrangement for folder comparison The column arrangement when comparing folders can be modified via the menu "View > "Column Arrangement" > "Same Sequence" or "Mirrored". Same sequence Mirrored 3.4.4...
Page 81 Create MyConfig - Diff 3.4 Folder comparison Further information can be found in the Exporting and importing configurations (Page 108) section. ① List of the comparison configurations ② Buttons for managing the configurations ③ Comparison tab / Filter / Comment ④...
Page 82 Create MyConfig - Diff 3.4 Folder comparison Using "Add", a new configuration is generated which can also be adapted. A copy of the selected comparison configuration is created by clicking "Duplicate". With "Restore user-specified setting", the changes to the specified comparison configuration are undone.
Page 83 Create MyConfig - Diff 3.4 Folder comparison Otherwise, only the size is compared and possibly the date or the version. ⑧ 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, files can be hidden or displayed for comparison in screen forms.
Page 84: Copying From The Folder Comparison
Create MyConfig - Diff 3.4 Folder comparison Comment tab Any comments on the selected comparison configuration can be saved in the Comment tab. 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.
Page 85: Archive As User Or Sdb Archive
Create MyConfig - Diff 3.4 Folder comparison ① ② ③ In the selected folder , in the list of folders and files contained in it , the objects to be copied are selected using normal Windows tools (<Ctrl + mouse click>, <Shift + mouse click>, etc.).
Page 86: File Comparison
Create MyConfig - Diff 3.5 File comparison The following archives can be generated: ● Commissioning archive – "Standard SINUMERIK archive", just the same as it is also created in SINUMERIK Operate, it can include all data areas and control commands for a memory reset, loads standard data etc.
Page 87: Overview Of User Interface
Create MyConfig - Diff 3.5 File comparison 3.5.2 Overview of user interface 3.5.2.1 Main menus The main menus are consistent in Diff. The submenus are adapted dynamically to the associated SINUMERIK archive comparison, Folder comparison or File comparison component. The following main menus and submenus are provided in the file comparison: Table 3-21 Diff - File comparison - File main menu File...
Page 88 Create MyConfig - Diff 3.5 File comparison Edit Editing mode <Ctrl+E> Lines can be copied from one file to another file only in activated editing mode. (Copy right / Copy left). All context menu functions, such as Cut, Paste, Paste before selection and Delete lines, require activation of editing mode.
Page 89 Create MyConfig - Diff 3.5 File comparison Table 3-24 Diff - File comparison - Comparison main menu Comparison Refresh <Ctrl+D> The "Refresh comparison" button is always color-highlighted when the displayed comparison result is not current and the refresh of the com‐ parison should be restarted.
Page 90 Create MyConfig - Diff 3.5 File comparison Table 3-25 Diff - File comparison - Tools main menu Tools Options... Opens the "Options" dialog with the tabs described below. Options can be activated or deactivated for representation/execution of the Diff components. All options are activated as default. The Diff coloration and the language setting can be changed user- defined.
Page 91 Create MyConfig - Diff 3.5 File comparison Tools This is useful, for example, for a red-green sight impediment. The standard setting can be re‐ stored: ● Unequal - Red ● Equal - Black ● Right - Blue ● Left - LimeGreen Language Language selection of the Diff in‐...
Page 92 Create MyConfig - Diff 3.5 File comparison Tools Export configurations... The following configuration types and the associated files can be se‐ lected or deselected in the "Export configurations" dialog: ● Archive/folder comparison configurations ● File comparison configurations ● Data comparison configurations ●...
Page 93: File Comparison - Toolbar
Create MyConfig - Diff 3.5 File comparison 3.5.2.2 File comparison - toolbar ① Edit mode / Copy ② New file comparison Calling a file comparison. ③ Update comparison ④ Display/save HTML/XML report ⑤ Comparison configuration ⑥ Copy ⑦ Go to previous / next difference. ⑧...
Page 94 Create MyConfig - Diff 3.5 File comparison ③ Update comparison The update button is always shown in color if the displayed comparison result is not a current result and the comparison should be restarted using this button. ④ Display/save HTML/XML report The comparison result is shown in the standard browser (Internet Explorer) by clicking this button.
Page 95 Create MyConfig - Diff 3.5 File comparison This group contains: ● a button for opening a dialog box in which the search options can be defined ● an edit box for searching for character strings in the display fields ● buttons for searching upward and downward. →...
Page 96: File Comparison - Overview Window
Create MyConfig - Diff 3.5 File comparison 3.5.2.3 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 97 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 98 Create MyConfig - Diff 3.5 File comparison Note Lines or characters shown in gray have been excluded from a comparison by a filter. ⑤ Comparison configuration - filter A filter is active in the comparison configuration. The comparison configuration is opened with a double-click.
Page 99: Configuration
Create MyConfig - Diff 3.5 File comparison 3.5.3 Configuration File comparison You can call the dialog to configure a folder comparison using the "Comparison configuration" button or via the menu "Comparison > Edit configuration…". You can manage the comparison configurations (i.e. create, edit, delete, etc.) in the dialog. In a comparison configuration, all of the criteria that should be taken into account when comparing files can be defined.
Page 100 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 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 101 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 102 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 icon is shown in the status bar if this function is activated. ②...
Page 103 Create MyConfig - Diff 3.5 File comparison Alignment tab In 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 104: Configuration Of The Automatic File Identification
Create MyConfig - Diff 3.5 File comparison ⑤ ③ ④ In addition, for lines for which the definitions do not apply, this slider sets how the system handles lines that are not identical, but similar when it comes to aligning them. This means it is defined as to whether similar lines, depending on the degree of similarity, are shown offset to one another (green and blue arrow) or next to one another (red unequal icon).
Page 105 Create MyConfig - Diff 3.5 File comparison The dialog for setting the program options via the "Tools > Options" menu is called from the "Options" dialog ① Activate/deactivate comparison configuration ② Message for automatic change of the comparison configuration ③ File identification configuration...
Page 106 Create MyConfig - Diff 3.5 File comparison Configuration - File identification The dialog for configuring the automatic file identification has the same layout as the dialog for comparison configuration and should be operated similarly. ① List of stored configurations "Settings" tab: ②...
Page 107: Copying From The File Comparison
Create MyConfig - Diff 3.5 File comparison ② Identification of the file name via screen form A screen form to identify the file type using file names can be stored in this field. ③ Identification of the content based on a character string typical for the particular file type If the file name does not provide an unambiguous identification, an identification is made based on a character string typical for the particular file type.
Page 108: Display Modes
Create MyConfig - Diff 3.6 Exporting and importing configurations Objects are copied using the normal Windows tools (context menu, button, <Ctrl+C>, etc.). 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.
Page 109: 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 110: 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 111 Create MyConfig - Diff 3.7 Command line call Call SINUMERIK archive comparison Diff /data <Archive path 1> [< Archive path 2>] [< Archive path n>] [/importconfigs <Configuration file>] [/config <Comparison configuration>] [/compare] [/xml <Log file>] [/html <Log file>][/log <Log file>] Call folder comparison Diff /dir <Directory path 1>...
Page 112 Create MyConfig - Diff 3.7 Command line call Note Accented characters and special characters Avoid using accented characters and special characters in path names. To allow special characters or accented characters to be correctly processed in specified paths, save the batch files with command line calls with the same character set as used by the region-specific command line interpreter "*cmd.exe".
Page 113 Create MyConfig - Diff 3.7 Command line call Parameter Significance of the switches Table 3-28 Diff parameter Switch Arguments Description <Archives> ● Opens the SINUMERIK archive comparison. /data ● As arguments, one or more paths can be specified for archives or parameter files that are to be compared.
Page 114 Create MyConfig - Diff 3.7 Command line call Switch Arguments Description <Coding> ● Only functions in conjunction with the /file switch (file comparison). /encleft ● Specifies the display mode to be used or the coding for the left (first) file. ●...
Page 115: Use Of Regular Expressions In Diff
3.8 Use of regular expressions in Diff Example Precondition: ● Create MyConfig is installed in the "C:\Program Files\Siemens\Automation \SINUMERIK\Create MyConfig 4.8\Diff.exe" directory. ● An "Archive1.arc" archive is available in the "C:\Temp\" path. ● The "myConfig" comparison configuration is available in Diff.
Page 116: Meta Characters In The Regular Expressions
Create MyConfig - Diff 3.8 Use of regular expressions in Diff Escape sequence If a meta character is required as literal character to formulate a regular expression, i.e. it must only stand for itself, then the character must be masked with what is called an escape sequence.
Page 117 Create MyConfig - Diff 3.8 Use of regular expressions in Diff Meta charac‐ Description ters Corresponds to a line break. Corresponds to an ASCII character in the hexadecimal notation (precisely two posi‐ \x20 tions). Corresponds to a unicode character in the hexadecimal notation (precisely four po‐ \u0020 sitions).
Page 118: Examples Of Regular Expressions
Create MyConfig - Diff 3.8 Use of regular expressions in Diff 3.8.3 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 119 Create MyConfig - Diff 3.8 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 120 Create MyConfig - Diff 3.8 Use of regular expressions in Diff SINUMERIK Integrate Create MyConfig - Diff, Expert, Topo Operating Manual, 12/2017, A5E36537479B-AE...
Page 121: 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 122: 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 123: 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 an engineering software for creating a CMC project. An executable package for the production or upgrading of machines is generated from this project with the Deployment function.
Page 124 Create MyConfig - Expert 4.2 Introduction ● Components (Page 252) - Component editor ● Dockable window with the tabs: – Source explorer (Page 133) – Cross references (Page 392) – Verification run ① Main menus and toolbars ② Project folder ③...
Page 125 Create MyConfig - Expert 4.2 Introduction Easy to operate Expert user interface To a certain extent, you can adapt the Expert user interface to your requirements. When opening Expert for the first time, the dockable window with the tabs Verification run, Cross references and Source explorer is displayed in the bottom area of the Expert user interface.
Page 126 Create MyConfig - Expert 4.2 Introduction Procedure 1. With the default setting, the dockable window is anchored in the lower area of the Expert user interface. 2. To move the entire dockable window or only a tab in the right-hand working area, move it by pressing and holding the title bar or tab from the current position to the working area in which the positioning tiles are displayed.
Page 127 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, 12/2017, A5E36537479B-AE...
Page 128: Main Menus Overview
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 user interface of Expert.
Page 129: Main Menus And Toolbars
Create MyConfig - Expert 4.2 Introduction 4.2.3 Main menus and toolbars Table 4-1 Project main menu Project New... <Ctrl+N> Creates a new project with the specified name and storage path. Open... <Ctrl+O> Opens an existing project. Also permits an existing project to be selected for con‐ version.
Page 130 Create MyConfig - Expert 4.2 Introduction Project Close all Closes the project and all of the components that have been opened. Exit <Alt+F4> Terminates the Expert program Table 4-2 Edit main menu Edit <Ctrl+X> Removes the currently selected objects and copies them to the clipboard. Copy <Ctrl+C>...
Page 131 Create MyConfig - Expert 4.2 Introduction Component Close <Ctrl+F4> Closes the current component. Password protection The current component is protected from unauthorized access by passwords. Enter the password... Log on in the current component (active tab) with a different password (extended rights). Edit password list...
Page 132 Create MyConfig - Expert 4.2 Introduction Configuration (Page 245) Exporting into file... This selection allows active configurations to be exported as a file. Opens the "Configuration selection" dialog. Select the configuration areas to be exported: ● Package ● Dialogs ● Steps Clicking the "OK"...
Page 133: Source Explorer
Create MyConfig - Expert 4.2 Introduction Table 4-7 Window main menu Window New horizontal Displays the selected component in the new horizontal tab group. New vertical tab group Displays the selected component in the new vertical tab group. Move to previous tab group Moves the selected component to the previous tab group.
Page 134: Converting Projects From Existing Cmc Versions
Create MyConfig - Expert 4.2 Introduction Copy Folders and files can be dragged from the source explorer and dropped in a component. Copying is performed when the <Ctrl> key is pressed. Linking is performed when the <Ctrl +Shift> keys are pressed. Otherwise you are prompted as to what should be done. Copy &...
Page 135: Changes To System Variables
Create MyConfig - Expert 4.2 Introduction Procedure 1. Import the packages with the appropriate older Expert version. 2. Open and convert the created project with the current CMC Expert. 3. Store the project and forward it as package with the current version (*.exe, *uaz, *usz). 4.2.5.2 Changes to system variables Note...
Page 136: System Support
Create MyConfig - Expert 4.3 System support 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 SINUMERIK 840D sl and SINUMERIK 828D: SINUMERIK 840D sl...
Page 137: Project Folder
Create MyConfig - Expert 4.4 Project folder Support of the CU320 through Create MyConfig The following processes are supported: ● Administration of the drive data (DO) via the archive (copy, delete). ● Manipulation and access to SINAMICS parameters as for CU Integrated (bus 3) via the archive (script, manipulation task).
Page 138 Create MyConfig - Expert 4.4 Project folder ● Language ● Script libraries Figure 4-5 Package tab - project engineer view Note Help area for Package tab Note the color-coded help in the lower section of the "Package" tab. Click a property in the tab to display the appropriate help. Display associated system variables button You open the "Package - System variables"...
Page 139 Create MyConfig - Expert 4.4 Project folder General The following properties are available: Table 4-9 Package > General Comment You can enter project-internal information here. This comment is not displayed during package execution or in the logbook. Access The access rights are displayed and defined here. Clicking the button opens the "Edit password list [Rights without a password] (Page 400)"...
Page 140 Create MyConfig - Expert 4.4 Project folder Runtime system Linux package (NCU) Select the runtime system in which the package is executed. Windows package (PC/PCU) Package without the execut‐ able part Exclude data Specify whether data from the unused data areas, areas Archive, NCU/PPU and PCU is excluded from the deployment.
Page 141 Create MyConfig - Expert 4.4 Project folder Language The following properties are available: Table 4-12 Package > Language Manage resources Display of the already created language folder for the user interface of the package. Clicking the button opens the "List of language resources" dialog. The resource files of the standard languages are configured and managed in the "List of language resources"...
Page 142: Dialogs
Create MyConfig - Expert 4.4 Project folder 4.4.2 Dialogs Overview of dialog pages Below the project folder in the "Dialogs" tab, activate the dialog pages to be executed and configure their contents and behavior. You can see the dialog list with the dialog pages that can be configured for an example project below: Figure 4-6 Dialogs tab...
Page 143 Create MyConfig - Expert 4.4 Project folder You can find an overview for the dependencies of the dialog pages of data areas (Page 144) in the section with the same name. Show/hide inactive dialogs button With the button (Show/hide inactive dialogs), dialogs that are not enabled in this project can be shown or hidden.
Page 144: Dependency Of The Dialog Pages On Data Areas
Create MyConfig - Expert 4.4 Project folder Dialog pages for the "Dialogs" tab The following dialog pages are run through chronologically during package execution. In the following sections, the property groups and the setting options for the respective dialog pages are described. Finally, the configured dialog page is shown how it is displayed for the operator or commissioning engineer during package execution.
Page 145: 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-14 Overview, dependency of dialog pages on data areas Data areas Use archive Use PCU Use NCU/PPU Dialogs Package configuration...
Page 146 Create MyConfig - Expert 4.4 Project folder Events In the "Dialog scripts" dialog, scripts can be stored for the listed dialogs for the desired events (= time instants) that are executed when the package is executed at the event time of the dialog page.
Page 147 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-15 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 148 Create MyConfig - Expert 4.4 Project folder It behaves differently in automatic sequence than the manual sequence. Redo()* Redo() cancels the automatic sequence. Redo() should preferably be used in the dialogs in the OnNext event to monitor manual entries. Skip()** Skip() jumps immediately to the next dialog. The current dialog page is thus no longer executed.
Page 149: Examples Of Scripts In The Dialog Pages
Create MyConfig - Expert 4.4 Project folder Note Exceptions: Skip() not permissible It is not permissible to use Skip() on the following dialog pages and it is rejected with an error message during the verification run. ● Select offline archive ●...
Page 150 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 151: 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 input") if up.quest=="1024*768" up.quest=1024 endif if up.quest=="640*480" up.quest=640 endif if up.quest=="continue without input" msg("A resolution must be entered!") else up.leavewhile = true...
Page 152 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 Dependencies of the dialog pages of data areas (Page 144) section.
Page 153 Create MyConfig - Expert 4.4 Project folder Information on the System variables·can be found in the System variables for the Package configuration dialog (Page 372) section. Further general information on the system variables can be found in the Reference list system variables (Page 368) section.
Page 154: Package Configuration (Package Execution)
Create MyConfig - Expert 4.4 Project folder Dialog scripts In the "Dialog scripts" >, "Scripts" entry, click the button to call the "Dialog scripts" dialog. Here you can edit scripts that are to be executed at selectable times during package execution. You can find detailed information on the dialog scripts in the section with the same name "Dialog scripts (Page 145)".
Page 155: Notes About Acknowledgment (Configuration)
Create MyConfig - Expert 4.4 Project folder Buttons for the package execution dialogs Note The buttons are identical for all dialog pages of package execution and thus have the same meaning. Table 4-18 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.
Page 156 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 Dependencies of the dialog pages of data areas (Page 144) section.
Page 157: Notes About Acknowledgment (Package Execution)
Create MyConfig - Expert 4.4 Project folder Display associated system variables button Clicking the button (Display associated system variables) opens the "Notes about acknowledgment - system variables"dialog. This dialog lists all system variables used for "Notes about acknowledgment". Information on the system variables can be found in the System variables for the Notes on confirmation dialog (Page 373) section.
Page 158: 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 execution dialogs Information on the general buttons in the dialogs can be found at Meaning of buttons (Page 155).
Page 159 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 Dependencies of the dialog pages of data areas (Page 144) section.
Page 160: Notes On The Package (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 368) section. Dialog More detailed information about the "Dialog" property group can be found at Package configuration (configuring) (Page 153).
Page 161: Select Offline Archive (Configuration)
Create MyConfig - Expert 4.4 Project folder Buttons for the package execution dialogs Information on the general buttons in the dialogs can be found at Meaning of buttons (Page 155). 4.4.2.10 Select offline archive (configuration) This dialog specifies from where the output data for the NC, PLC and DRV control areas for the offline package execution without NCU is obtained.
Page 162 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 Dependencies of the dialog pages of data areas (Page 144) section.
Page 163 Create MyConfig - Expert 4.4 Project folder Display associated system variables button Clicking the button (Display associated system variables) opens the "Select offline archive - system variables"dialog. All system variables used for "Select offline archive" are listed in this dialog. Information on the system variables·can be found in the System variables for the Select offline archive dialog (Page 374) section.
Page 164: 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 165: Pcu Access (Configuration)
Create MyConfig - Expert 4.4 Project folder Figure 4-16 Select offline archive - Commissioning engineer / operator view Buttons for the package execution dialogs Information on the general buttons in the dialogs can be found at Meaning of buttons (Page 155). 4.4.2.12 PCU access (configuration) This dialog specifies with which PCU and which login data the package should be connected...
Page 166 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 Dependencies of the dialog pages of data areas (Page 144) section.
Page 167: Pcu Access (Package Execution)
Create MyConfig - Expert 4.4 Project folder Information on the system variables can be found in the System variables for the PCU access dialog (Page 373) section. Further general information on the system variables can be found in the Reference list system variables (Page 368) section.
Page 168: 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. This specifies with which control and which login data the package should be connected for the execution.
Page 169 Create MyConfig - Expert 4.4 Project folder You can configure the following property groups for the "NCU/PPU access" dialog page: ● Dialog ● Address ● Login information ● Dialog scripts 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"...
Page 170 Create MyConfig - Expert 4.4 Project folder Show/hide inactive dialogs button Clicking the button (Show/hide inactive dialogs) shows or hides dialogs not used in this project. Display associated system variables button Clicking the button (Display associated system variables) opens the "NCU/PPU access - System variables"...
Page 171: Ncu/Ppu Access (Package Execution)
4.4.2.15 NCU/PPU access (package execution) This dialog page enables access to the NCU in the case of SINUMERIK 840D sl or the PPU in the case of SINUMERIK 828D. This specifies with which control and which login data the package should be connected for the execution.
Page 172: Ncu/Ppu Initial State (Configuration)
Create MyConfig - Expert 4.4 Project folder 4.4.2.16 NCU/PPU initial state (configuration) This dialog allows a data backup of the initial state of the NCU/PPU prior to the package execution. All current control data, including the CF card, or only the current active online data of the NC, PLC and DRV subsystems can be saved as SINUMERIK archive.
Page 173 Create MyConfig - Expert 4.4 Project folder You can find an overview for this in the Dependencies of the dialog pages of data areas (Page 144) section. Show/hide inactive dialogs button Clicking the button (Show/hide inactive dialogs) shows or hides dialogs not used in this project.
Page 174: Ncu/Ppu Initial State (Package Execution)
Create MyConfig - Expert 4.4 Project folder Note For "Setting disabled" property The setting for selecting the data backup can be disabled for the operating procedure. The licenses of the control are also backed up. When restoring a backup, a query appears as to whether the licenses from the backup are to be restored, or the licenses on the control are to be retained.
Page 175: 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 execution dialogs Information on the general buttons in the dialogs can be found at Meaning of buttons (Page 155). 4.4.2.18 Notes on GSP (configuration) This dialog sends notes on "Service Platform Industry (GSP)"...
Page 176 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 Dependencies of the dialog pages of data areas (Page 144) section.
Page 177: Notes On Gsp (Package Execution)
Create MyConfig - Expert 4.4 Project folder Dialog More detailed information about the "Dialog" property group can be found at Package configuration (configuring) (Page 153). 4.4.2.19 Notes on GSP (package execution) This dialog sends notes on "Service Platform Industry (GSP)" to the operator. Package execution dialog A file in text format or HTML format with operating instructions for the following dialog page can be displayed on the "Notes on GSP"...
Page 178 Create MyConfig - Expert 4.4 Project folder You can configure the following property groups for the "Service Platform Industry (GSP)" dialog page: ● Dialog ● Specify machine identity ● Machine information ● Manufacturer data ● Subsidiary data ● Dealer data ●...
Page 179 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 Dependencies of the dialog pages of data areas (Page 144) section.
Page 180 Create MyConfig - Expert 4.4 Project folder Example of a "ma_types.xml" file (source: DOC_ON_CD): <?xml version="1.0" encoding="utf-8"?> <Machinetypes> <Type>LC 80</Type> <Type>LC 82</Type> <Type>LC 120</Type> <Type>LC 122</Type> <Type>LC 150</Type> </Machinetypes> Manufacturer data The following settings are available for the "Manufacturer data" property: Manufacturers (selection file) The "oem.xml"...
Page 181: Service Platform Industry (Gsp) (Package Execution)
Create MyConfig - Expert 4.4 Project folder Example of a "dealer.xml" file (source: DOC_ON_CD) You can acquire the address data of any number of dealers in the "dealer.xml" file. If you wish to enter additional dealers, copy the area <Dealer> to </Dealer> for each dealer. <?xml version="1.0"...
Page 182: Cnc Software (Configuration)
Further information can be found on package execution in the Package execution (Page 405) section. Note Templates for the described XML files can be viewed on the NCU/PPU at /card/siemens/ sinumerik/hmi/template/identity. Figure 4-26 Notes on GSP (Service Platform Industry) - commissioning engineer / operator view...
Page 183 Create MyConfig - Expert 4.4 Project folder You can configure the following property groups for the "CNC software" dialog page: ● Dialog ● Installation ● CNC software (*.tgz) ● Dialog scripts 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"...
Page 184 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 185: Cnc Software (Package Execution)
Create MyConfig - Expert 4.4 Project folder Note If the package is started from a service system USB FlashDrive, then generally booting is from the CF card after this dialog. Dialog scripts In the "Dialog scripts" property, "Scripts" entry, click the button to call the "Dialog scripts"...
Page 186: System Configuration (Configuration)
Create MyConfig - Expert 4.4 Project folder Figure 4-28 CNC software - commissioning engineer / operator view Using the "CNC software (*.tgz)" drop-down list, a file that was assigned to the package or a file lying next to the package (prefix: "./") can be selected. The "Browse"...
Page 187 Create MyConfig - Expert 4.4 Project folder This dialog corresponds with regard to the drive commissioning to the "SINAMICS topology" dialog. You can configure the following property groups for the "System configuration" dialog page: ● Dialog ● Offline archives ● NC archive data ●...
Page 188 Create MyConfig - Expert 4.4 Project folder 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 Dependencies of the dialog pages of data areas (Page 144) section.
Page 189 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-19 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 190 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 191 Create MyConfig - Expert 4.4 Project folder HW configuration (SDB) The following settings are available for the "HW configuration (SDB)" 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 192 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 in the package configuration, "Package" > "Data areas" > "Use NCU/PPU" has been activated in the tab, the archive data can be loaded directly from the control with the "initial state"...
Page 193: System Configuration (Package Execution)
Create MyConfig - Expert 4.4 Project folder Setting disabled The selection at "Origin of data" can be blocked by the project engineer via this option in order to prevent changes by the operator during the package execu‐ tion. Preselection of the offline archive At "Preselection of the offline archive", a SINUMERIK archive can be inserted, linked or preselected from the list.
Page 194 Create MyConfig - Expert 4.4 Project folder The "myArchive.arc" archive from the "myPath" folder, which is located next to the package, is used. The "./" prefix represents the current path in which the package file is located at the time of execution.
Page 195: Notes On The Topology (Configuration)
Create MyConfig - Expert 4.4 Project folder Buttons for the package execution dialogs Information on the general buttons in the dialogs can be found at Meaning of buttons (Page 155). 4.4.2.26 Notes on the topology (configuration) This dialog sends notes on the "SINAMICS topology" to the operator. You can configure the following property group for the "Notes on the topology"...
Page 196: Notes On The Topology (Package Execution)
Create MyConfig - Expert 4.4 Project folder Show/hide inactive dialogs button Clicking the button (Show/hide inactive dialogs) shows or hides dialogs not used in this project. Display associated system variables button Clicking the button (Display associated system variables) opens the "Notes on the topology - system variables"...
Page 197: 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 execution dialogs Information on the general buttons in the dialogs can be found at Meaning of buttons (Page 155).
Page 198 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 Dependencies of the dialog pages of data areas (Page 144) section.
Page 199 Create MyConfig - Expert 4.4 Project folder Display associated system variables button Clicking the button (Display associated system variables) opens the "SINAMICS topology - system variables" dialog. All system variables used for "SINAMICS topology" are listed in this dialog. Information on the System variables·can be found in the System variables for the SINAMICS topology dialog (Page 379) section.
Page 200 Create MyConfig - Expert 4.4 Project folder Comparison topology (*.ust) Note Prerequisite for comparison topology On the "SINAMICS topology" dialog page, a comparison topology is always used if, on the "System configuration" dialog page at DRV archive data / Drive configuration, for "Origin of data"Initial state, Automatic configuration, or Offline archive has been selected.
Page 201 Create MyConfig - Expert 4.4 Project folder The following properties available for the "user-specified topology (*.utz)" are activated when the package is executed: List Clicking the button opens the "List of user-specified topologies (*.utz)" dialog. Select the desired User-specified topology (*.utz) from the list. User-specified topologies can be pasted or inserted as link at "List".
Page 202 Create MyConfig - Expert 4.4 Project folder The following can be defined for a DO variable: Parameter Description Character DO variable Unique name within the package (without specifying Characters: Up.) A-z_0-9 DO type Type depending on the selected category: Category Type Control Unit Integrated (NCU)
Page 203: Sinamics Topology (Package Execution)
Create MyConfig - Expert 4.4 Project folder When UVDX files are used in Expert, only the DO data contained in the file is used. Any included component information is evaluated only by Topo. Note For DO manipulations using a comparison topology, user-specified topology, or DO list When changing the DO number, the assigned PS file is renamed and parameters "p101"...
Page 204 Create MyConfig - Expert 4.4 Project folder Dialog view during 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" or "Automatic configuration" is used for the device configuration for drives and a Comparison topology was selected at the SINAMICS topology.
Page 205 Create MyConfig - Expert 4.4 Project folder DO variables The upper part of the dialog page provides a list of all DO variables that are in the DO variable list in the comparison topology. The properties of the DO variables are specified in this list, and using a checkmark at the beginning of the line it is indicated whether a DO variable is used, i.e was assigned to a drive object.
Page 206 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 of the drives. Figure 4-35 SINAMICS topology - commissioning engineer / operator view - example of user-specified topology Performing axis-drive assignment Setting the check mark activates automatic axis-drive assignment.
Page 207 Create MyConfig - Expert 4.4 Project folder The "SM" column indicates whether a Sensor Module involves a first or second module. Sensor Modules are shown in blue. Column "AX DR" includes information about the axis-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 208: 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 not permissible that "Execute axis-drive assignment"...
Page 209 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 Dependencies of the dialog pages of data areas (Page 144) section.
Page 210: Version Display (Package Execution)
The applications identified during execution and their determined versions are displayed on the "Version display" dialog page. The information is obtained via: ● NCU/PPU from the file: "/siemens/versions.xml" ● PCU from the Registry: "HKLM Software\SIEMENS\AUTSW" Further information can be found on package execution in the Package execution (Page 405) section. Note For the version query (Overview (Page 225)) for the conditional step execution or in scripts, the application names displayed here should be used as keywords.
Page 211: 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 execution dialogs Information on the general buttons in the dialogs can be found at Meaning of buttons (Page 155). 4.4.2.32 Notes on the step tree (configuration) This dialog sends notes on the "step tree"...
Page 212 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 Dependencies of the dialog pages of data areas (Page 144) section.
Page 213: Notes On The Step Tree (Package Execution)
Create MyConfig - Expert 4.4 Project folder Dialog More detailed information about the "Dialog" property group can be found at Package configuration (configuring) (Page 153). 4.4.2.33 Notes on the step tree (package execution) This dialog sends notes on the "step tree" to the operator. Dialog view during package execution (for commissioning engineers / operators) A file in text format or HTML format with operating instructions for the following dialog can be displayed on the "Notes on the step tree"...
Page 214: Step Tree (Configuration)
Create MyConfig - Expert 4.4 Project folder 4.4.2.34 Step tree (configuration) This dialog permits the configuring of the package steps in a hierarchical tree structure. You can configure the following property groups for the "Step tree" dialog page: ● Dialog ●...
Page 215 Create MyConfig - Expert 4.4 Project folder Show/hide inactive dialogs button Clicking the button (Show/hide inactive dialogs) shows or hides dialogs not used in this project. Display associated system variables button Clicking the button (Display associated system variables) opens the "Step tree - system variables"...
Page 216: 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 217 Create MyConfig - Expert 4.4 Project folder Figure 4-42 1. Step tree dialog - commissioning engineer / operator view The "Step configuration (*.upcfg)" drop-down list allows a file assigned to the package or a file located next to the package (prefix: "./") used. The "Browse..."...
Page 218: 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 at Meaning of buttons (Page 155).
Page 219: Ncu/Ppu Result State (Configuration)
Create MyConfig - Expert 4.4 Project folder Dialog view during package execution (for commissioning engineers / operators) Further information can be found on package execution in the Package execution (Page 405) section. 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 at Meaning of buttons (Page 155).
Page 220 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 Dependencies of the dialog pages of data areas (Page 144) section.
Page 221 Create MyConfig - Expert 4.4 Project folder Information on the system variables·can be found in the System variables for the NCU/PPU result state dialog (Page 381) section. Further general information on the system variables can be found in the Reference list system variables (Page 368) section.
Page 222: 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 145)". 4.4.2.38 NCU/PPU result state (package execution) This dialog allows a data backup of the result state of the NCU/PPU after the package execution.
Page 223: End (Configuration)
Create MyConfig - Expert 4.4 Project folder Buttons for the package execution dialogs Information on the general buttons in the dialogs can be found at Meaning of buttons (Page 155). 4.4.2.39 End (configuration) This dialog page completes the package execution and saves the logbook. You can configure the following property groups for the "Finish"...
Page 224: End (Package Execution)
Create MyConfig - Expert 4.4 Project folder Show/hide inactive dialogs button Clicking the button (Show/hide inactive dialogs) shows or hides dialogs not used in this project. Display associated system variables button Clicking the button (Display associated system variables) opens the "Finish - system variables"...
Page 225: Steps
Create MyConfig - Expert 4.4 Project folder Dialog view during package execution (for commissioning engineers / operators) The "Finish" dialog page cannot be deactivated. A file in text format or restricted HTML format is displayed on this page for postprocessing. The operator can be prompted to save the logbook when closing the logbook.
Page 226: Step Tree Structure
Create MyConfig - Expert 4.4 Project folder Structuring of the steps Because of the structuring of the steps on several levels into main steps and substeps and the possibility of activating/deactivating the individual steps, the different variants of the machines of the series can be modeled by the step tree.
Page 227 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, 12/2017, A5E36537479B-AE...
Page 228 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 229: 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 230 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 231: 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 232: 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 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...
Page 233 Create MyConfig - Expert 4.4 Project folder Update link Updates the link. New step Inserts a new step after the currently selected step and selects this. New substep Shift+Ins Inserts a new substep into the selected step and select this. If a lower level does not exist, then it is created. New step as link...
Page 234 Create MyConfig - Expert 4.4 Project folder Alt+Up Shifts the component within the step upwards in the execution sequence. Down Alt+Down Shifts the component within the step downwards in the execution sequence. Adapt Link Adapts the link entry in the component list of the step for an external component.
Page 235: Linking Steps
Create MyConfig - Expert 4.4 Project folder The content of the function of internal and external components is completely identical. They differ only by their storage location. Internal components are stored in the project folder and external components are stored in any reachable folder. See also Step tree (configuration) (Page 214) 4.4.3.5...
Page 236 Create MyConfig - Expert 4.4 Project folder Green connecting line Permissible step logic operations from: ● Subproject Project 2 to main project Project 1 and ● Subproject Project 3 to main project Project 2. Red connecting line Impermissible step logic operation: Step [2] of the subproject Project 2 is already used in main project Project 1 (linking depth = 1).
Page 237 Create MyConfig - Expert 4.4 Project folder ● The linked steps retain their step ID from the subproject, in which a namespace is added in the main project for each link, in order to ensure unambiguous identification. The ID namespace is automatically assigned during configuration. This also prevents an ID namespace from being assigned twice.
Page 238 Create MyConfig - Expert 4.4 Project folder same step, in this case for "." in the main project. This must be taken into account in the programming. Example for step query The following shows how a query can be made whether the steps are active. The status in the relation of the projects to one another is either a main project (MP, black) or a subproject (SP, gray).
Page 239 Create MyConfig - Expert 4.4 Project folder Summary example step query Within a project (the status of the project can be both a main project and/or subproject), the step query is the following: ● If UP.$Step[2].Activated ==true Depending on which direction the query is started in, from MP to SP or vice versa, the condition for the step query must be formulated as follows: ●...
Page 240 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 241 Create MyConfig - Expert 4.4 Project folder Figure 4-55 Insert link step 3. The inserted blue link step has received in the MP an additional step property "ID namespace" and a step configuration property "Manage in". 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 242 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 243: Managing And Using Configurations
Create MyConfig - Expert 4.4 Project folder Updating the step links The step links can be selectively updated via the context menu or the "Update step tree completely (F5)" button. The update is also performed automatically when opening the project, when starting the verification run, and when starting to generate the cross reference list.
Page 244: Project Configurations
Create MyConfig - Expert 4.4 Project folder Further information on the individual system variables can be found in Section Reference list system variables (Page 368). The configurations are located in text files with the "*.upcfg" extension. You can also edit the text files with external editors.
Page 245: Step Configurations
Create MyConfig - Expert 4.4 Project folder 4.4.4.4 Step configurations Step configurations are configuration files used for executing a package. These configurations contain some or all configurations of the "Steps" tab of the project folder for which system variables (Page 368) exist. These package configurations are contained within the package on the "Step tree"...
Page 246 Create MyConfig - Expert 4.4 Project folder Configuration Export to file... You can export active configurations to a file via this selection. Opens the "Configuration selection" dialog. Select the configuration areas that you want to export: ● Package ● Dialogs ●...
Page 247 Create MyConfig - Expert 4.4 Project folder Figure 4-57 "Save in list" - "Select configuration" dialog The stored areas of a configuration are displayed in the "Content" column in the respective "List of the project, package or step configurations" dialog. Configuration - Load from list Stored configurations can be selected and loaded via the "Configuration"...
Page 248 Create MyConfig - Expert 4.4 Project folder Configuration - Export to file The configuration is exported to a file. In the "Select configuration" dialog, specify which areas (Package, Dialogs, Steps) you want to export and save. Specify the path and the file name of the "*.upcfg" configuration file. Configuration - Import from file A configuration that was exported to a file is imported again.
Page 249 Create MyConfig - Expert 4.4 Project folder Alternatively, stored configurations can be managed via the following dialogs: ● "Dialogs" tab > "Package configuration" The "List of project configurations" can also be displayed and the desired configuration selected here. – List To do this, select the "Package configuration"...
Page 250 Create MyConfig - Expert 4.4 Project folder – Preselection A configuration can be selected at Preselection via the "Preselect from list" context menu. The configuration is displayed with the "*.upcfg" file name. Figure 4-62 Package configuration > Preselection SINUMERIK Integrate Create MyConfig - Diff, Expert, Topo Operating Manual, 12/2017, A5E36537479B-AE...
Page 251 Create MyConfig - Expert 4.4 Project folder ● "Dialogs" tab > "Step tree" You can display the "List of step configurations" "*upcfg" and preselect the desired configuration. – List To do this, select the "Step tree" dialog page in the "Dialogs" tab. In the "Step configuration"...
Page 252: Component Editor
Create MyConfig - Expert 4.5 Component editor Component editor The contents of components, their actions, version and comment can be displayed, edited and configured in the Component Editor. Components and actions In order that a component is executed when executing the package, it must be linked with a step and the step must be selected for execution (green icon).
Page 253: Action Scripts
Create MyConfig - Expert 4.5 Component editor Figure 4-64 View of Actions tab with display of the individually open actions If a different order is required, the order of the actions can be adjusted via the toolbar in the "Actions" tab or via the "Up - Alt+Up" or "Down - Alt+Down" context menu. Actions opened for execution are assigned their own tabs in the Component Editor, which are given the name of the action.
Page 254 Create MyConfig - Expert 4.5 Component editor Executing action scripts Executing of actions and any existing action scripts (in the yellow box) is schematically shown in the diagram below. The procedures which could potentially control the sequence of the actions or script are listed by way of example.
Page 255 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, select the desired action in the Actions tab, and open it via the "Edit action script"...
Page 256: Execute
Execute action The "Execute" action allows a program, command or script to be executed. For example, software components from SIEMENS or other suppliers can be installed or special manipulations changed in the archive or other target areas. The following target areas are supported: ●...
Page 257 Create MyConfig - Expert 4.5 Component editor Note Display of the target area ● Gray - target area does not contain any data. ● Red - data in the target area is not used. ● Blue - linked data with resolution for deployment. ●...
Page 258 Create MyConfig - Expert 4.5 Component editor For an installation, additional operator actions may be required on the PCU. Execution on the PCU is controlled via the PCU handler that runs as a setup application on the PCU. When a communication error occurs, the PCU can be exited by pressing the key combination Shift+Esc (Shift+ ALARM CANCEL).
Page 259 Create MyConfig - Expert 4.5 Component editor Figure 4-70 Logbook entry - return value "1" More information is provided in section: "Additional useful notes" Execute - runtime system A package can be deployed for various runtime systems. Two scripts must be written to deploy a package for Linux and for Windows that makes special changes via "Execute"...
Page 260 Create MyConfig - Expert 4.5 Component editor Linux mkdir ./Save mv $UP_ARC/NC/CMA.DIR/OEM001.SPF ./Save/ rm -r $UP_ARC/NC/CMA.DIR/* mv ./Save/OEM001.SPF $UP_ARC/NC/CMA.DIR/ Additional useful notes Use "System variables for the environment" in a script file for Windows (cmd) or Linux (sh), because they are known only to the script interpreter. If, however, "System variables for the environment"...
Page 261: Delete
Create MyConfig - Expert 4.5 Component editor Under Windows, prefix the command line scripts to the command interpret‐ For example: Cmd.exe /c test.cmd NCU / PPU (Linux) Shell scripts (sh) for Linux must be stored in Unix file format (only LF, not CR/LF).
Page 262 Create MyConfig - Expert 4.5 Component editor PCU 50 (Windows 7)PCU drives/shares C:, D: Operate SINUMERIK Operate folder hmisl or card A "Task" must be created using the context menu in order to be able to enter delete instructions. The instructions can be sub-divided into several tasks in order to improve the structure. The task name can be freely selected.
Page 263: Copy
Create MyConfig - Expert 4.5 Component editor Additional useful notes Archive/PLC To delete PLC blocks, these must be specified in the archive name conven‐ tion. The naming convention has the format: TTNNNNN, whereby TT stands for the hexadecimal type, and NNNNN for the decimal number of the block. When necessary, both should be filled up with leading zeros to obtain 2 or 5 posi‐...
Page 264 Create MyConfig - Expert 4.5 Component editor Note Selected data areas define target areas Which target areas are displayed depends on the data areas (archive, PCU, NCU/PPU) that were activated for use. The data areas are defined in the project folder in the "Package" (Page 137) tab. If a data area is deactivated subsequently, all the target area nodes that cannot be hidden due to content are shown in red.
Page 265 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 266: Change
Create MyConfig - Expert 4.5 Component editor Additional useful notes Archive/PLC To copy PLC blocks, they must be specified in archive name convention. The naming convention has the format: TTNNNNN, whereby TT stands for the hexadecimal type, and NNNNN for the decimal number of the block. When necessary, add leading zeros to give 2 or 5 positions, respectively.
Page 267 Create MyConfig - Expert 4.5 Component editor Identifier=value Table 4-22 The following target areas are supported: Target area Description Example Archive Archive image NC, MMC, NC_MMC, PLC, CP, DRV NCU / PPU NCU/PPU CF card user, oem, addon PCU 50 (Win 7) PCU drives/shares C:, D: Operate...
Page 268 Create MyConfig - Expert 4.5 Component editor Tasks can be created in the following ways: ● New task – Enter the instructions directly in the Script Editor. The task name must be identical to the file to be changed. ● Import task –...
Page 269 Create MyConfig - Expert 4.5 Component editor "INI file" or "Preprocessor script" task mode For each task, a specification is made as to whether it is to be executed in "INI file" or "Preprocessor script" mode. Figure 4-71 Change action - Mode selection Example of Change action with "INI file"...
Page 270 Create MyConfig - Expert 4.5 Component editor Figure 4-72 Change action with INI file Change action in the "INI file" mode For the package execution in the "INI file" mode, the file specified via the target area path and task name is opened and the operations specified in the relevant section executed. If the file or the section is not available, it is created by the package in the target system.
Page 271 Create MyConfig - Expert 4.5 Component editor Figure 4-73 Example 1 - preprocessor instructions Change action in the "Preprocessor script" mode In the "Preprocessor script" mode, contents can be integrated script-controlled in files. Open and edit the file specified via the target area path and task name. If the file is not available, it is created by the package in the target system.
Page 272 Create MyConfig - Expert 4.5 Component editor The mode for the Change action is selected via the drop-down list below the tree view at Settings. Example 2 A Linux shell script is created on the CF card, which, with the aid of the SED Editor, deletes all tool data from the INITIAL.INI if the variable is Up.Cfg >= 2.
Page 273 Create MyConfig - Expert 4.5 Component editor Special operators (Page 289) 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 274: Manipulate
Create MyConfig - Expert 4.5 Component editor 4.5.6 Manipulate Manipulate action The "Manipulate" action allows machine data to be accessed, essentially independently of data storage in the control. 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 275 Create MyConfig - Expert 4.5 Component editor Figure 4-76 Components - manipulate action All cross-area data can be read and written in the "All" target area of theManipulate action. You can find additional information in the Data accesses (Page 333) section. Additional information on the possibilities associated with manipulation tasks is provided in the description of the script language (Page 279).
Page 276 The context menu assists you when inserting sections, control structures, functions, procedures, operators and area data. Furthermore, a catalog is available listing all of the identifiers specified by SIEMENS. The Script 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 277: Additional Useful Notes On The "Manipulate Action
Create MyConfig - Expert 4.5 Component editor Example of "Error" icon Figure 4-77 Manipulate - message preview Figure 4-78 Example of "Error" icon 4.5.6.1 Additional useful notes on the "Manipulate action" NC data NC data is manipulated on the basis of the NC archive area. If a context is not set with CHANDATA(n), channel 1 is assumed.
Page 278 For SINUMERIK Operate, data is read from section [BTSS-Settings] of file hmi_md.ini in the search sequence siemens → addon → oem → user, but written back only to hmi_md.ini at user. When deleting data, this results in a reset to a user-specified value of preceding files in the search sequence.
Page 279: Script Language
Create MyConfig - Expert 4.6 Script language 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 280: Color Coding Of Language Elements
Create MyConfig - Expert 4.6 Script language Manipulation tasks In the Component Editor, scripts can be added under actions of the type "Manipulate" (manipulation tasks). You can find additional information under Manipulation (Page 274). Change tasks In the Component Editor, scripts can be added under actions of the type "Change" (change tasks).
Page 281: Set Channel
Create MyConfig - Expert 4.6 Script language Program element Color Formatting Example Complex variables Yellow/orange whose value is not interpre‐ ted by CMC 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 282: Area Data
Create MyConfig - Expert 4.6 Script language NC data channel assignment within the NC [C1] to [C10] or CHANDATA (1) to CHANDATA (10) for NC channels 1 to 10. Examples [B3_S3_PS3] ; SINAMICS drive data p1082[1] = 9000 ; Maximum speed [SL] ;...
Page 283: 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 333).
Page 284: If-Elsif Control Structure / If-Elsif-Else Control Structure
Create MyConfig - Expert 4.6 Script language 4.6.6.2 If-ElsIf control structure / If-ElsIf-Else control structure After the If condition alternative conditions can be checked by specifying ElsIf or ElIf. The instruction block is executed after the first fulfilled condition. The instruction block after Else is executed if no condition is fulfilled.
Page 285: While Check Structure
Create MyConfig - Expert 4.6 Script language Each instruction 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 286: Operators
Create MyConfig - Expert 4.6 Script language 4.6.7 Operators 4.6.7.1 Overview operators The following operator groups are available for scripts in dialogs, step scripts, and manipulation tasks: ● Assignment operators (Page 286) ● Arithmetic operators (Page 287) ● Logic operators (Page 288) ●...
Page 287: Arithmetic Operators
Create MyConfig - Expert 4.6 Script language &= AND operation AND operation on the specified and existing value (reset bits). Assignment without evaluation Assignment without evaluation to the right of the operator. The value is transferred to the control as specified. Everything to the right of "="...
Page 288: Logic Operators / Comparison Operators
Create MyConfig - Expert 4.6 Script language Calculations must be set in brackets in order to define an unambiguous 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.7.4 Logic operators / comparison operators Condition- true != false The following logic operations and comparison operators are available to form Boolean expressions (True/False): Table 4-25...
Page 289: Special Operators
Create MyConfig - Expert 4.6 Script language Note Calculation in logic operations Calculation is also possible in logic operations. Example If (Up.Velo + Up.Offset)>2000) 4.6.7.5 Special operators Replacement operator - $(up.?) The "replacement operator" makes it is possible to replace parts of an instruction, an identifier, a value or a message text flexibly with the value of a package variable Up.identifier.
Page 290: String Concatenation (Concatenate-Operator)
Create MyConfig - Expert 4.6 Script language 4.6.7.6 String concatenation (Concatenate-Operator) The string concatenation operator "<<" can be used to combine constant strings and variables to form a resulting string. This operator is mainly intended for the assignment of Up variables when used in functions or procedures with string parameters.
Page 291: Stringmatch
Create MyConfig - Expert 4.6 Script language 4.6.8.2 StringMatch StringMatch("<string>", "<search>") The StringMatch() function searches in the <string> character string for the <search> search pattern. Regular expressions are used as search pattern. The return value of the function is a character string.
Page 292: Stringreplace
Create MyConfig - Expert 4.6 Script language Example Up.Pos=StringPos("Ingenuity for life", "e", 0) ;Up.Pos = 3 Up.Pos=StringPos("Ingenuity for life", "E", 5) ;Up.Pos = 17 Up.Pos=StringPos("Ingenuity for life", "e", 25) ;Up.Pos = -1 Up.Pos=StringPos("Ingenuity for life", "x", 0) ;Up.Pos = -1 Up.Pos=StringPos("Ingenuity for life", "for", 0) ;Up.Pos = 10 Up.Pos=StringPos("Ingenuity for life", "[efg]", 0) ;Up.Pos = 2...
Page 293: Stringsubstr
Create MyConfig - Expert 4.6 Script language Example Use the name of the input archive for the name of the package execution logbook. Up.$Dialog.PackageEnd.LogName = StringReplace(Up. $Dialog.ArcSelection.ArchiveIn, "\.arc","") The use of an ""NC.ARC"" input archive by this instruction produces the "NC.htm" logbook. As the file extension is replaced with an empty string and the package automatically adds the "*.htm"...
Page 294 Create MyConfig - Expert 4.6 Script language This procedure can be called in all dialog scripts, step scripts, action scripts and manipulation tasks. The <path> argument specifies the file with path and name. The path specification <path> can be relative to the package or absolute, but always refers to the runtime system of the package execution.
Page 295: Filecopy
Version files of the NCU are stored in the CF card folder next to the package. Up.cf = "./CF-" << Up.$Env.CFID << "/" FileCopy(NCU, "/user/system/etc/hwversions.xml", RTS, "$ (Up.cf)hwversions.xml") FileCopy(NCU, "/siemens/versions.xml", RTS, "$ (Up.cf)siemens_versions.xml") SINUMERIK Integrate Create MyConfig - Diff, Expert, Topo Operating Manual, 12/2017, A5E36537479B-AE...
Page 296: Filedelete
Create MyConfig - Expert 4.6 Script language 4.6.9.3 FileDelete FileDelete(<area>, "<path>") The FileDelete() procedure deletes a file in a target area. The procedure can generally be called in all dialog scripts, step scripts, action scripts and manipulation tasks. The target area is specified via the <area> argument, whereby the following values are permitted: ●...
Page 297 Exists() will no longer be supported in subsequent CMC versions. Only use the FileExist() function. Change all earlier calls to this new function name. Call examples FileExist(NCU, "/siemens/versions.xml") ;searches for the file on the NCU. FileExist(NCU, "/card/install/arc") ;searches for the folder on the CF card of the NCU.
Page 298: Fileread
Create MyConfig - Expert 4.6 Script language Example of the output of a message Output of a message if the "/siemens/versions.xml" file was found on the NCU/PPU. IF FileEXIST(NCU, "/siemens/versions.xml") Msg("The 'versions.xml' file exists on the NCU.") ENDIF Example of package variable UP.DH_exists Package variable "UP.DH_exists"...
Page 299: Filewrite
Create MyConfig - Expert 4.6 Script language Note Determination of the end of line / line break With the StringPos() function, you can determine which end of line / line break characters were used in the file. \r → Carriage return (CR or 0x0D) \n →...
Page 300 Create MyConfig - Expert 4.6 Script language The <string> character string may include characters coded in the ANSI character set or non-printable characters. Note Use of the end of line / line break If your character string has several lines, you can implement it with the string chaining operator. Further information can be found in Section String chaining (concate operator) (Page 290).
Page 301: Queryini
Create MyConfig - Expert 4.6 Script language ● ARC - for the text file in the archive image. The path must start with NC\, MMC\, PLC\, CP\ or DRV\. Example: FileWrite(ARC, "NC\CST.DIR\Test.SPF", Up.myfile) ● RTS - for the text file on the runtime system (NCU/PPU, PCU,PC) on which the package is executed.
Page 302 Create MyConfig - Expert 4.6 Script language The environment system variables of the runtime system can be used. By testing the return value for "Null", it can be determined whether or not the function could find the file, the section or the identifier. Example 1 Query the "FirewallOpenPorts"...
Page 303: Queryxml
Create MyConfig - Expert 4.6 Script language EndWhile EndIf 4.6.9.8 QueryXml QueryXml("<path>", "<xpath>") The QueryXml() function reads the contents of XML files that are on the runtime system ((RTS)) of the package execution. The <path> argument specifies the XML file (with path and file names (file path)) from where the content of an XML node should be read.
Page 304 Create MyConfig - Expert 4.6 Script language Note Warning in the logbook if the file is not an XML file If the specified file is not an XML file, the function behaves as if the specified path is invalid. The function provides the return value "Null" and writes the message of the invalid path as warning in the logbook.
Page 305 Create MyConfig - Expert 4.6 Script language ;Initialization of the input file (XML) Up.pathToInput = "/card/user/sinumerik/hmi/data/version/ identity.xml" ;If the input file does not exist on the NCU, ;"Input file not found!" is output if !FileExist(NCU,Up.pathToInput) TraceToFile(Up.pathToOutput,"Input file not found!") endif ;Initialization of the XPath expression Up.xpathCustomerId = "/Config_Identity/Addresses/Manufacturer/ Customer-Id/text()"...
Page 306 Create MyConfig - Expert 4.6 Script language Content of the script: ;Initialization of the output file (text) Up.pathToOutput = "Example2\Output.txt" ;If the output file exists on the RTS, it will be deleted if FileExist(RTS,Up.pathToOutput) FileDelete(RTS,Up.pathToOutput) endif ;Initialization of the input file (XML) Up.pathToInput = "/card/user/sinumerik/hmi/lng/ alarmtxt_nculin_deu.ts"...
Page 307 Create MyConfig - Expert 4.6 Script language Content of the input file "Example3\Input.xml": <TS> <message> <source>510104/PLC/PMC</source> <translation>Axes not referenced, tool changer locked</ translation> </message> <message> <source>510105/PLC/PMC</source> <translation>Tool changer not available!</translation> </message> <message> <source>510106/PLC/PMC</source> <translation>Something else not available!</translation> </message> </TS> Content of the script: ;Initialization of the output file (text) Up.pathToOutput = "Example3\Output.txt"...
Page 308: Dialogs
Create MyConfig - Expert 4.6 Script language ;If alarm texts exist if Up.alarmTextMax != null ;Output all available alarm texts while Up.alarmTextIndex <= $(Up.alarmTextMax) ;Determine the i-th alarm text Up.xpathAlarmtext = "/TS/message[$(Up.alarmTextIndex)]/ translation/text()" ;Use of the XPath expression on the input file with QueryXml Up.valAlarmtext = QueryXml( Up.pathToInput, Up.xpathAlarmtext) ;If the alarm text was found, it will be output if Up.valAlarmtext != null...
Page 309 Create MyConfig - Expert 4.6 Script language Up variables and local or global area data can also be used as arguments for the functions. Excluded are only those arguments that contain an ID parameter without straight quotation marks, e.g. the <area> argument for the FileExist function. Example of a function call with variables: $MC_CHAN_NAME=InputText(Up.Label,$MC_CHAN_NAME) Example of the use of functions in conditions:...
Page 310: Msg
Create MyConfig - Expert 4.6 Script language Note Handling special characters in strings The straight quotation mark " is enclosed by inverted commas '"' within a string, but only counts as one character. The special characters for line feed '\n' and carriage return '\r' can only be inserted in character strings individually by means of string chaining operator <<.
Page 311: Input
Create MyConfig - Expert 4.6 Script language The type-specific input functions require a default value. The user-specified value can be specified directly or applied only at runtime via variables. All of the input functions are always displayed in the Dialogs tab in the "Step tree" dialog, independently of the "Display messages"...
Page 312: Inputchoice
Create MyConfig - Expert 4.6 Script language 4.6.10.5 InputChoice InputChoice("<label>", "<button1>;<button2>") The InputChoice() function displays a dialog with icons in which during package execution the user can choose directly by pressing individual buttons. The selection that is made is returned as a string (the button labeling). The entry can be explained using the <label>...
Page 313 Create MyConfig - Expert 4.6 Script language Figure 4-80 Example without icon Example Selection with information icon Up.retI = InputChoice("*I;Beispiel für Symbol '"'Information'"'", "*&OK") Up.retI = InputChoice("*I;Example for Icon '"'Information'"'", "*&OK") Figure 4-81 Example of "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'"'",...
Page 314 Create MyConfig - Expert 4.6 Script language Figure 4-83 Example of "Warning" icon Example Selection with error icon Up.retE = InputChoice("*E;Beispiel für Symbol '"'Fehler'"'", "*&Abbruch;&Fortsetzen") Up.retE = InputChoice("*E;Example for Icon '"'Error'"'", "*&Abort;&Continue") Figure 4-84 Example of "Error" icon Example Pushbutton operation Up.example = InputChoice("*Q;Beispiel für Schaltflächenbedienung mit ...
Page 315: Inputenum
Create MyConfig - Expert 4.6 Script language Example of buttons one below the other Up.MaschineType = InputChoice("Wählen Sie die Technologie!", "&Fräsen;; &Drehen;; &Schleifen") Up.MaschineType = InputChoice("Please select technology!", "&Milling;; &Turning;; &Grinding") Figure 4-86 Example of buttons displayed one below the other 4.6.10.6 InputEnum InputEnum("<label>", "*<enum1>;<enum2>")
Page 316: Inputint
Create MyConfig - Expert 4.6 Script language Example Preselection with replacement operator Note the use of a replacement operator in the selection string. Up.Typ1 = "Milling machine" Up.Typ2 = "Drilling machine" Up.Auswahl = "$(up.Type1); $(Up.Type2); turning machine" Up.Maschinentyp = InputEnum("Which machine type?", "$(Up.Auswahl)") Figure 4-88 Example Preselection with replacement operator 4.6.10.7...
Page 317: Inputreal
Create MyConfig - Expert 4.6 Script language Up.Speed = InputInt("Confirm the speed.", $(Up.n)) Figure 4-90 Example of replacement from STRING, e.g. Enum (enumeration) 4.6.10.8 InputReal InputReal("<label>", <real>) The InputReal() function displays a dialog box in which during package execution the user can enter a real number.
Page 318: Inputtext
Example of InputText with and without replacement operators Up.Name = InputText("Enter the machine name.", "'Machine XY'") Figure 4-93 Example of InputText without replacement operator Up.FA = "Siemens" Up.Name = "'Machine XY'" Up.Manuafacturer = InputText("From which company is $(up.Name) manufactured?",up.FA) SINUMERIK Integrate Create MyConfig - Diff, Expert, Topo...
Page 319: Inputuint
Create MyConfig - Expert 4.6 Script language Figure 4-94 Example of InputText with replacement operator Example of InputText for password entry Up.Password = InputText("Enter your password", "*") Figure 4-95 Example of using InputText for password entry 4.6.10.10 InputUInt InputUInt("<label>", <uint>) The InputUInt() function displays a dialog box in which during package execution the user must enter an unsigned integer.
Page 320: Text Formatting Options
Create MyConfig - Expert 4.6 Script language Figure 4-96 Example of InputUInt entry unsigned integer Example of specification with replacement operator Up.Default = 0x9F Up.Uint = InputUInt("Enter an unsigned integer", $(Up.Default)) Figure 4-97 Example of specification with replacement operator 4.6.10.11 Text formatting options Programming options Examples are listed below on how you can format texts.
Page 321 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-99 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-100 Example of a header, bold Example of the representation of an italic header...
Page 322 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-102 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-103 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 323 Create MyConfig - Expert 4.6 Script language Example of a header, lowercase up.small=InputReal("Notice!Please enter a number.", 3.0) Figure 4-105 Example of a header, small Example of a header, strikethrough up.scratch=InputReal("<s>Notice!</s>Please enter a number.",3.0) Figure 4-106 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 324 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-108 Example of a header in superscript Example of a subscripted header up.sub=InputReal("Notice!Please enter a number.",3.0) Figure 4-109 Example of a subscripted header Examples of colored headers Some examples of colored texts are shown below.
Page 325 Create MyConfig - Expert 4.6 Script language Figure 4-111 Example of a green header Header red bold and text with yellow background up.red=InputReal("Notice! Enter a number.",3.0) Figure 4-112 Example representation, red bold header and text with yellow background Example of background color Header and text have different background colors, e.g.
Page 326: Resources
Create MyConfig - Expert 4.6 Script language align='left'>milling</td><td> 2 </td></tr><tr><td align='left'>grinding</td><td> 3 </td></tr></table>",1) Figure 4-114 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-115...
Page 327: Miscellaneous
Create MyConfig - Expert 4.6 Script language 4.6.12 Miscellaneous 4.6.12.1 Skip Skip() The Skip() procedure can be used in dialog scripts, step scripts and action scripts to skip the dialog, step or action. Use for non-deselectable dialogs and in manipulation tasks is not permissible. You can find further information in the Dependencies of the dialog pages of data areas (Page 144) section.
Page 328: Extcall
Create MyConfig - Expert 4.6 Script language The method of operation of the procedure for dialog, step and action scripts is also described in the Dialog scripts (Page 145), Step scripts (Page 231) and Action scripts (Page 253) sections. 4.6.12.4 ExtCall ExtCall("<path>") Calling an external manipulation task...
Page 329: Dovar
Create MyConfig - Expert 4.6 Script language Examples of units of time Up.year = DateTime("yyyy") ; the year as four digit number Up.month = DateTime("MM") ; the month as number with a leading zero (01-12) Up.day = DateTime("dd") ; the day as number with a leading zero (01 to 31) Up.hour = DateTime("hh") ;...
Page 330: Log
Create MyConfig - Expert 4.6 Script language DoVar(<axis>) Generates a DO variable using the permanently defined machine axis identifier <axis>. Example: Up.myVar2 = DoVar(AX1) 4.6.12.7 Log ("<label>") Logbook entry Any message text that is only written in the logbook represents the <label> argument. Example Giving the logbook entries a yellow background makes the logbook easier to read.
Page 331: Mathround
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 package area PCU, all SIEMENS applications installed on the PCU entered in the PCU registry with key HKEY_LOCAL_MACHINE\SOFTWARE\Siemens\AUTSW are determined.
Page 332: Preprocessor
Create MyConfig - Expert 4.6 Script language For the name of the application <app>, an abbreviated, unambiguous specification is sufficient, e.g. "SINUMERIK CNC" instead of "SINUMERIK CNC-SW 31-5". Note All applications that are found are displayed on the "Version Display" dialog page. Example of a query for whether a higher or lower version exists Query whether the version of the NCK is lower than or equal to 83.03 : Version(NCU, "NCK") <= 83.03...
Page 333: Data Access Operations
Create MyConfig - Expert 4.6 Script language ● The <path> path of the external file to be included can be specified as an absolute path or relative path. <path> contains the storage location and the file name, e.g. D:\Temp\Skript.txt or .\Skript.txt.. For internal (manipulation) tasks, the relative path refers to the storage folder of the component.
Page 334 Create MyConfig - Expert 4.6 Script language Data Dialog Step tree accesses pages 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 335 Create MyConfig - Expert 4.6 Script language 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. Namespaces and sections In detail, the following namespaces and sections are defined: Table 4-28 Namespaces and sections Target area...
Page 336: Package Variables
Create MyConfig - Expert 4.6 Script language 4.6.15 Package variables Package variables - Up.<identifier> Package variables are variables that have significance only within a package. The control does not know these variables and so they are not transferred to the control. The package variables consist of an identifier, preceded with the Up.Up.
Page 337: Do Variables
Create MyConfig - Expert 4.6 Script language Script variables can be read and written in all scripts and manipulation tasks, see Package variables (Page 336). In change tasks in "Preprocessor script" mode, script variables can only be read in control structures, writing is not possible.
Page 338: System Variables
Create MyConfig - Expert 4.6 Script language Up.doVar.doType Supplies the type of the drive object. Possible values lie between 0 and 600. The valid values correspond to the values set in SINAMICS at the Control Unit in parameter "drive objects type / DO type" P0107. Examples Possible values for "Up.doVar.doType"...
Page 339: Commenting
Create MyConfig - Expert 4.6 Script language 4.6.16 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 340 Create MyConfig - Expert 4.6 Script language Figure 4-117 Selection of the parser type Main menus The following main menus are available for the Script Editor. Table 4-30 File main menu File <Ctrl+N> Creates a new script file with the "*.upscr" file extension. Open <Ctrl+O>...
Page 341: Script Libraries
Create MyConfig - Expert 4.6 Script language 4.6.18 Script libraries In order to be able to easily address frequently recurring script code, the project engineer can define dedicated procedures and functions in "*.uplib" script libraries. This significantly reduces the number of lines required in the individual scripts. The resulting scripts are clearer and easier to read.
Page 342: Editing Script Libraries
Create MyConfig - Expert 4.6 Script language Toolbar Table 4-33 Toolbar for the "List of user script libraries" dialog Toolbar New script library Insert new script library Inserts a new "*.uplib" script library or links a new script library. Link new script library Insert...
Page 343 Create MyConfig - Expert 4.6 Script language Scripts library-specific syntax For the definition of procedures and functions, the command scope has been extended by the keywords "proc" and "func". When you create a new definition, start the line with one of the keywords. This is followed by a procedure name or function name, transferred arguments and on opening curly bracket.
Page 344: Call Of Procedures And Functions From A Script Library
Create MyConfig - Expert 4.6 Script language A comment with the keyword "Arg1:" to "Arg9:" describes the transferred argument in more detail. These specifications are taken into account in the later display in the context menu. In this way, the project engineer can ensure during the function creation that another user knows what the function performs and which arguments have to be used.
Page 345: Supplementary Conditions For The Use Of Script Libraries
Create MyConfig - Expert 4.6 Script language Figure 4-119 "Insert script" context menu 4.6.18.4 Supplementary conditions for the use of script libraries When using script libraries, the supplementary condition that the name of a procedure and the name of a function must only be defined once applies. If you define a procedure or function several times, this results in an error in the verification run.
Page 346: Patch
Create MyConfig - Expert 4.7 Configuring user interface languages for packages Machine data / time of the function call The following table shows which data is permitted and the point in time up to which it must be written to ensure that the machine data still takes effect. Machine data (MD) Latest point in time for a function call OnInit "System configuration"...
Page 347: Standard Languages Of The User Interface
Create MyConfig - Expert 4.7 Configuring user interface languages for packages standard buttons, selection boxes, etc. All texts that are not explicitly configured by the user, are system texts. The user texts are all texts that are configured by the project engineer while creating the package in a project.
Page 348: Schematic Overview
Create MyConfig - Expert 4.7 Configuring user interface languages for packages User texts in scripts You manually create user texts that you use in your scripts in user language resource files and reference these texts in your scripts. How to proceed here is also described in the following sections: When your translation office has translated the language resource files of your standard language, the language resource files can be used in the project for the other standard...
Page 349: Tabular Overview
Create MyConfig - Expert 4.7 Configuring user interface languages for packages Red arrow Export Green ar‐ Import Figure 4-120 Schematic representation - Creating the resource files 4.7.2.2 Tabular overview The following table provides an overview of which texts are displayed during the package execution.
Page 350: Language Resource Files
Create MyConfig - Expert 4.7 Configuring user interface languages for packages Information text Resource file Display in dialogs/steps in the project during package execution Plain text Available Text from resource file is displayed. Not available Plain text is displayed. Available The content of the file is displayed.
Page 351 Create MyConfig - Expert 4.7 Configuring user interface languages for packages You can open the dialog in Expert at: "Project folder" > "Package" tab > "Language" > "Manage resources" via the button. Double-click a "*.ts" language resource file to open the Resource Editor (Page 358). The resource files are generally below the language folderin the "List of language resources".
Page 352: Creation Of The Language Resource Files
Create MyConfig - Expert 4.7 Configuring user interface languages for packages Table 4-35 Toolbar for the "List of language resources" dialog Toolbar New language Folder You can insert a new folder with an arbi‐ trary name or a new standard language (Page 346) via the button.
Page 353: Procedure For 1St Standard Language
Create MyConfig - Expert 4.7 Configuring user interface languages for packages 4.7.5.2 Procedure for 1st standard language The 1st standard language is the language in which you have stored the texts in plain text on the user interface in Expert. The 1st standard language can be your native language, for example.
Page 354: Procedure For 2Nd To 6Th Standard Language
Create MyConfig - Expert 4.7 Configuring user interface languages for packages 4. In the "eng" folder use the "New language resource file" button to select "Insert new resource" > "User - Empty". 5. You have created a "User.ts" file which you can open and edit in the "Resource Editor" by double-clicking.
Page 355 Create MyConfig - Expert 4.7 Configuring user interface languages for packages Creating the "Dialog.ts" and "Step.ts" files Note Do not create "Dialog.ts" and "Step.ts" files in the 1st standard language Do not create the "Dialog.ts" and "Step.ts" language resource files in the language folder which corresponds to the language in which you have already stored texts on the user interface of Expert.
Page 356 Create MyConfig - Expert 4.7 Configuring user interface languages for packages 4. In the language folder, create the language resource files via the context menu by selecting "Insert new resource" > "Dialog - texts from project". For this selection, ensure that all configured information texts are entered in the "Dialog.ts" file.
Page 357: Resource Editor
Create MyConfig - Expert 4.7 Configuring user interface languages for packages 4.7.6 Resource Editor 4.7.6.1 Resource Editor - Standalone A Resource Editor is provided by Create MyConfig. Opening the Resource Editor from the Windows Start menu The Create MyConfig Resource Editor is inserted in the Windows Start menu during the installation of CMC.
Page 358: Resource Editor Integrated In Expert
Create MyConfig - Expert 4.7 Configuring user interface languages for packages Table 4-37 Extras main menu Extras Options... Opens the "Options" dialog > "Language" tab. You can switch between the German and English user interface languages here. The language change only takes effect at the next call of the Resource Editor. Table 4-38 Help main menu Help...
Page 359: Content Of The "Dialog.ts" File
Create MyConfig - Expert 4.7 Configuring user interface languages for packages Figure 4-125 Example: Resource Editor with "Dialog.ts" tab Each language resource file is opened in a separate tab. The tab is identified with the appropriate "*.ts" language resource file and a language code specified in square brackets. A new "Dialog.ts - [fra]"...
Page 360: Content Of The "Step.ts" File
Create MyConfig - Expert 4.7 Configuring user interface languages for packages The name of the open file and the language variant, e.g. "[deu]" are displayed in the title of the tab. A change to the file is indicated in the editor by an asterisk "*" in front of the file name. Edit the IDs and information texts only in the "Create MyConfig Resource Editor".
Page 361: Content Of The "User.ts" File
Create MyConfig - Expert 4.7 Configuring user interface languages for packages Figure 4-127 "Step.ts" file in the Resource Editor 4.7.6.5 Content of the "User.ts" file Edit the IDs and information texts only in the "Create MyConfig Resource Editor". The IDs are freely assignable IDs that you use in the texts with the ResText() function. The name of the open file and the language variant, e.g.
Page 362: Export Of The Language Resource Files For Translation
Create MyConfig - Expert 4.7 Configuring user interface languages for packages Figure 4-128 "User.ts" file in the Resource Editor 4.7.7 Export of the language resource files for translation The "*.ts"language resource files are structured in a format that simplifies the translation of the contained texts.
Page 363: Import Of The Language Resource Files After Translation
Create MyConfig - Expert 4.7 Configuring user interface languages for packages Note Text in angle brackets Text placed within angle brackets in the language resource files must never be translated. For example:"<source>text</source>" This text represents an identification (ID) for the text to be output, which must be identical for all languages.
Page 364: Use Of The Restext() Function
Create MyConfig - Expert 4.7 Configuring user interface languages for packages Figure 4-129 Package configuration - Information text 4.7.10 Use of the ResText() function ResText("<resid>"[, "<arg>"]*) The ResText() function calls text resources in the form of information texts from the "User.ts" language resource file.
Page 365 Create MyConfig - Expert 4.7 Configuring user interface languages for packages Figure 4-131 Package execution - Example 1 Example 2 of ResText() Up.Summand_1 = 2 Up.Summand_2 = 3 Up.Summe = Up.Summand_1 + Up.Summand_2 Up.MSG2 = ResText("ADD",Up.Summand_1,Up.Summand_2,Up.Summe) MSG("$(Up.MSG2)") Figure 4-132 Configuration in the Resource Editor Figure 4-133 Package execution - Example 2 SINUMERIK Integrate Create MyConfig - Diff, Expert, Topo...
Page 366: Language Selection
Create MyConfig - Expert 4.7 Configuring user interface languages for packages 4.7.11 Language selection Configuration language The project engineer specifies the language selection for the interface of the Package execution in the "Package" > "Language" > "Selection" (Page 141) tab. The operator cannot change this selection for the package execution.
Page 367: Linking Steps
Create MyConfig - Expert 4.7 Configuring user interface languages for packages Alternatives for the language selection for the package execution You can specify the language used in package execution in the following ways: ● Expert: "Project folder" > "Package" tab > "Language" > "Selection" (project engineer) ●...
Page 368: Reference List, System Variables
Create MyConfig - Expert 4.8 Reference list, system variables Reference list, system variables 4.8.1 General information about system variables System variables for Expert The system variables, which you can use in the script and when configuring, are structured using the Package (Page 137), Dialogs (Page 142) andSteps (Page 225). In addition, there is a list of system variables from the package environment (Page 391).
Page 369 Create MyConfig - Expert 4.8 Reference list, system variables The system variables with the "readOnly" entry cannot be changed in the script. SINUMERIK Integrate Create MyConfig - Diff, Expert, Topo Operating Manual, 12/2017, A5E36537479B-AE...
Page 370 Create MyConfig - Expert 4.8 Reference list, system variables Table 4-39 Package Up.$Pack System varia‐ Type Change effective until Description Example bles Up.$Pack. UserVersion STRING readOnly User version "1.0.0" or "V1.0" or "test" ● As configured in Expert ● As specified by a "*.upcfg" file DeployName Name of the package: "Machine_one"...
Page 371: Package Enumerators
Create MyConfig - Expert 4.8 Reference list, system variables System varia‐ Type Change effective until Description Example bles Up.$Pack. Use NCU/PPU data area. Note This area can only be deselected via a configuration file (change true → false). Subsequent selection in the de‐ ployed package is not possible.
Page 372: System Variables For The Dialogs Tab
Create MyConfig - Expert 4.8 Reference list, system variables Enumeration language preselection - Language Area Enumeration Type Change effective until Description Enumeration language preselection - Language Up.$Pack.Languages. Enumerator value readOnly Language preselection German Language preselection English Language preselection French Language preselection Italian Language preselection Chinese (sim‐...
Page 373: System Variables For The Notes About Acknowledgement Dialog
Create MyConfig - Expert 4.8 Reference list, system variables 4.8.3.2 System variables for the Notes about acknowledgement dialog Table 4-41 "Notes for confirmation" dialog - ConfirmNotes (Dialog ID) 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 374: System Variables For The Select Offline Archive Dialog
Create MyConfig - Expert 4.8 Reference list, system variables System variables Type Change effective until Description Example ProcessMode Enumeration Process‐ Current dialog → OnI‐ Enumeration processing mode Mode (Page 382) $Dialog.ProcessModes.MA NUAL InteractLevel Enumeration InteractLe‐ Enumeration message level vel (Page 383) $Dialog.InteractLevels.
Page 375: System Variables For The Ncu/Ppu Access Dialog
Create MyConfig - Expert 4.8 Reference list, system variables 4.8.3.6 System variables for the NCU/PPU access dialog Table 4-45 "NCU/PPU access" dialog - NcuAccess (Dialog ID) System variables Type Change effective until Description Example Up.$Dialog.NcuAccess. Activated BOOL Last script before dia‐ Activating the dialog processing false / true ProcessMode...
Page 376: System Variables For The Notes On The Service Platform Industry (Gsp) Dialog
Create MyConfig - Expert 4.8 Reference list, system variables System variables Type Change effective until Description Example ProcessMode Enumeration Process‐ Current dialog → OnI‐ Enumeration processing mode Mode (Page 382) $Dialog.ProcessModes.MA NUAL InteractLevel Enumeration InteractLe‐ Enumeration message level vel (Page 383) $Dialog.InteractLevels.
Page 377: System Variables For The Cnc Software Dialog
Create MyConfig - Expert 4.8 Reference list, system variables System variables Type Change effective until Description Example ProcessMode Enumeration Process‐ Current dialog → OnI‐ Enumeration processing mode Mode (Page 382) $Dialog.ProcessModes.MA NUAL InteractLevel Enumeration InteractLe‐ Enumeration message level vel (Page 383) $Dialog.InteractLevels.
Page 378: System Variables For The System Configuration Dialog
Create MyConfig - Expert 4.8 Reference list, system variables 4.8.3.11 System variables for the System configuration dialog Table 4-50 "System configuration" dialog - SystemConfig (Dialog ID) System variables Type Change effective until Description Example Up.$Dialog.SystemConfig. Activated BOOL Last script before dia‐ Activating the dialog processing false / true ProcessMode...
Page 379: System Variables For The Notes On The Topology Dialog
Create MyConfig - Expert 4.8 Reference list, system variables 4.8.3.12 System variables for the Notes on the topology dialog Table 4-51 "Notes on the topology" dialog - DriveTopologyNotes (Dialog ID) System variables Type Change effective until Description Example Up.$Dialog.DriveTopologyNotes. Activated BOOL Last script before dia‐...
Page 380: System Variables For The Version View Dialog
Create MyConfig - Expert 4.8 Reference list, system variables 4.8.3.14 System variables for the Version view dialog Table 4-53 "Version display" dialog - VersionView (Dialog ID) System variables Type Change effective until Description Example Up.$Dialog.VersionView. Activated BOOL Last script before dia‐ Activating the dialog processing false / true ProcessMode...
Page 381: System Variables For The Ncu/Ppu Result State Dialog
Create MyConfig - Expert 4.8 Reference list, system variables System variables Type Change effective until Description Example ProcessMode ProcessMode enumera‐ Current dialog → OnI‐ Processing mode enumeration tion (Page 382) $Dialog.ProcessModes.MA NUAL InteractLevel InteractLevel enumera‐ Message level enumeration tion (Page 383) $Dialog.InteractLevels.
Page 382: System Variables For The Finish Dialog
Create MyConfig - Expert 4.8 Reference list, system variables 4.8.3.18 System variables for the Finish dialog Table 4-57 "Finish" dialog - PackageEnd (Dialog ID) System variables Type Change effective until Description Example Up.$Dialog.PackageEnd. Activated BOOL Last script before dia‐ Activating the dialog processing false / true ProcessMode ProcessMode enumera‐...
Page 383 Create MyConfig - Expert 4.8 Reference list, system variables Enumeration message level - InteractLevel Range Enumeration Type Change effective Description Enumeration message level - InteractLevel Up.$Dialog.InteractLevels. Enumerator value readOnly Message level, display all messages ERROR Message level, only error messages. WARNING Message level, error and warning mes‐...
Page 384: System Variables For The Steps Tab
Create MyConfig - Expert 4.8 Reference list, system variables Range Enumeration Type Change effective Description ARCHIVE Enumerator value readOnly The data is taken from an archive. FACTORY This PLC data is used after a general reset ORIGIN The actual PLC data at the time of package execution is used.
Page 385 Create MyConfig - Expert 4.8 Reference list, system variables For all system variables, the time until a change of the system variables is appropriate and still effective for the package execution, is specified in the "Change effective until" table column. Table 4-58 Steps tab System variable...
Page 386 Create MyConfig - Expert 4.8 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 387 Create MyConfig - Expert 4.8 Reference list, system variables Example activate step Figure 4-136 Display activate step SINUMERIK Integrate Create MyConfig - Diff, Expert, Topo Operating Manual, 12/2017, A5E36537479B-AE...
Page 388 Create MyConfig - Expert 4.8 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 389 Create MyConfig - Expert 4.8 Reference list, system variables Example execute step Figure 4-137 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 390 Create MyConfig - Expert 4.8 Reference list, system variables Observe the type of blocking during step configuration: ● Activation disabled ● Activation disabled including substeps Example activation disabled Figure 4-138 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 391: System Variables For The Environment
Create MyConfig - Expert 4.8 Reference list, system variables Example collapsing steps Figure 4-139 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 392: Enumeration, Runtime Environments - Runtimes
Type Description Example environment Up.$Env. RunTime RunTimes RunTimes enumeration STRING NCU/PPU 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 the CF card at user/system/...
Page 393: Display Cross References
Create MyConfig - Expert 4.9 Cross references 4.9.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 394: Search In Cross-References
Create MyConfig - Expert 4.9 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 395: Filter According To Identifier Or Object
Create MyConfig - Expert 4.9 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.9.4 Filter according to identifier or object A partial string can be entered in the input field by which the column "Identifier"...
Page 396: Transferring A Project/Creating A Package
Create MyConfig - Expert 4.10 Transferring a project/creating a package Example: 4.10 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 is integrated with Open Source Software or Commercial off- the-shelf is transmitted to a third-party, the CMC package must contain explicit information on the legal conditions.
Page 397 Because manipulations to your project, package and component files can cause material damage, protect your data. Further information on security can be found in the Industrial Security (https:// support.industry.siemens.com/cs/ww/en/view/108862708) documentation: ● Chapter 7.1.9 Data backup ● Chapter 6.3 System integrity Note Ensure security of the CMC packages Handle CMC packages responsibly with regard to security aspects.
Page 398: Password Protection
Create MyConfig - Expert 4.11 Password protection To create a package, proceed as follows: 1. Select "Project" > "Deploy" and select whether you want to create a Windows package or a Linux package. 2. Select a name and a target directory for the package. An automatic verification run is started that checks the package for inconsistencies and errors.
Page 399: Protecting Projects And Components
The following documentation provides general and specific security notes for your work: SINUMERIK / SIMOTION / SINAMICS Motion Control Industrial Security (https:// support.industry.siemens.com/cs/ww/en/view/108862708/71018232843?dl=de) Note Observing security for projects and components Note the following when handling projects and components, including any linked data: ●...
Page 400: Access Levels
Create MyConfig - Expert 4.11 Password protection 4.11.2.1 Access levels In Expert, a CMC project is protected using three access levels with different authorization levels. The same access levels are also applied for components. It is necessary to specifically protect components, because components can be opened and processed independently of projects.
Page 401 Create MyConfig - Expert 4.11 Password protection By default, when creating a new project or an external component, an entry <Rights without password> will be created with the following authorizations: Figure 4-141 Edit password list [Rights without a password] 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,"...
Page 402 Create MyConfig - Expert 4.11 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 403: Transferring A Password List To Existing Components
Create MyConfig - Expert 4.11 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 404 Create MyConfig - Expert 4.11 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 405: Package Execution
Create MyConfig - Expert 4.12 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 406: Executing The Package Under Windows
Create MyConfig - Expert 4.12 Package execution Package execution using NCU/PPU If an NCU/PPU is involved in the package execution (NCU/PPU data area active), observe the following: ● To prevent errors during package execution, the NCU/PPU system state must be consistent. ●...
Page 407 If no sufficiently current version is found, the package execution installs a current version. This version is part of the package. During package execution, Create MyConfigNcuShareService shares the "C:\ProgramData \Siemens\UpNcuShare" folder as exchange release. Once the package execution has been completed, the service revokes the release again. NcuShareService The NcuShareService service is required to execute CMC packages with an NCU/PPU share component for Windows PC or PCU50.
Page 408: Executing The Package On The Pcu 50 From The Network
Create MyConfig - Expert 4.12 Package execution Note In a PCU with Windows 7, various settings are required to permit package execution for automated commissioning. 4.12.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. Requirements Take the following requirements into account: ●...
Page 409: Package Execution Dialogs
If the package was transferred to a "normal USB Flash Drive" (or hard disk or CD) that cannot be booted because it does not contain a Linux boot system from Siemens, the NCU/PPU starts Linux from the CompactFlash card and then starts the package on the USB medium.
Page 410: Package Execution On Ncu/Ppu From The Compactflash Card
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. Whereby, <responsible> can be "siemens", "addon", "oem" or "user". 3. Activate the "Off/On" main switch. 4. Follow the instructions of the package dialogs.
Page 411: Package Execution Dialogs
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. Whereby, <responsible> can be "siemens", "addon", "oem" or "user". 3. Activate the "Off/On" main switch. 4. Follow the instructions of the package dialogs.
Page 412: Start Page Logbook
Create MyConfig - Expert 4.12 Package execution Both files are displayed in your Web browser, although the ""*.exe"" file is displayed only after the correct password is specified. The ""*.exe"" file must be started for display via "Execute" or a double-click. NOTICE Password protection - read-protection Password protection protects the logbook from unwanted viewing by third parties.
Page 413 Create MyConfig - Expert 4.12 Package execution ● List of all of the dialog pages used in the package, with the exception of the Note dialogs. Note The Note dialogs used are displayed using the system variables. ● File name under which the logbook (*.htm) was saved in the control. ●...
Page 414: Package Selection
Create MyConfig - Expert 4.12 Package execution Explanation of the buttons The following buttons are available in the logbook: Table 4-59 Logbook buttons Buttons Meaning Expand Using this button, all of the dialogs are opened, and all operations associated with executing the package are shown.
Page 415: Example Of A Dialog Page: Package Configuration
Create MyConfig - Expert 4.12 Package execution Figure 4-143 Select package - package selection Package configuration for deployment In this subinstance, all system variables for the package, the dialogs and the steps are listed, which are configured in Expert for this package, or were entered via a configuration file for automated package deployment.
Page 416 Create MyConfig - Expert 4.12 Package execution Figure 4-144 Configuring in Expert: Package configuration dialog - system variables Here, in the logbook this is displayed in the fact that string " " did not contain any information and was now changed: changed Old: " " The change is specified with the configuration file: "./DescLogBook_Konfig_1.upcfg"...
Page 417: Example Of A Dialog Page: Cnc Software
Create MyConfig - Expert 4.12 Package execution Figure 4-146 Detailed display - dialog page example: Package configuration 4.12.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 418: Example Of A Dialog Page: Step Tree
Create MyConfig - Expert 4.12 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-147 Example of a dialog page: CNC software 4.12.4.6 Example of a dialog page: Step tree This dialog page is optional;...
Page 419 Create MyConfig - Expert 4.12 Package execution Display Dialog page main instance: Step tree The following example shows how a step tree can be structured in the logbook. Figure 4-148 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 420 Create MyConfig - Expert 4.12 Package execution The instructions of two responses were obtained in channel 1: ● checked: The value of the first machine data item is listed as being checked because its old value already corresponded to the new required value. Old and new values are also listed.
Page 421: Logbook - End
Create MyConfig - Expert 4.12 Package execution Figure 4-149 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 Step tree dialog page, after the archive data transfer, directly in the control.
Page 422: Command Line Call
As of version 4.8, the complete path for "Expert.exe" must be specified or added to the "Path" environment variable. Example: "C:\Program Files\Siemens\Create MyConfig 4.8\Expert.exe" Note Observe the sequence of the switches The switches should be written to in the specified sequence.
Page 423 Create MyConfig - Expert 4.13 Command line call Note Path data ● Paths must be specified in straight quotation marks if spaces are included. Example: "C:\path with spaces\Expert_Logfile.xml" ● Paths may never end with '\'. Note Saving batch files Always save batch files with ANSI/ASCII coding. Note Accented characters and special characters Avoid using accented characters and special characters in path names.
Page 424 Create MyConfig - Expert 4.13 Command line call Parameter Significance of the switch Table 4-60 Expert parameters Switch Arguments Optional Description /silent The graphical user interface of Create MyConfig Expert is hidden. /deploy The switch causes the specified project to be verified and deployed. /config (<"Path configuration The switch causes the configuration file (*.upcfg) to be processed...
Page 425 Errors (and possibly warnings) occurred when deploying the package. Command line call error. Example Assumption: Create MyConfig is installed in the "C:\Program Files\SIEMENS \Create MyConfig 4.8" directory and a "Pack_1.upz" package is available in the "C:\Packages \" path. @echo off PATH=%PATH%;"C:\Program Files\SIEMENS\Create MyConfig 4.8"...
Page 426: Verification Run
Create MyConfig - Expert 4.13 Command line call 4.13.2 Verification run For the verification run of a package, you can also start Create MyConfig Expert in the command line mode. The command line call is envisaged for the automated verification run of packages.
Page 427 Create MyConfig - Expert 4.13 Command line call Note Accented characters and special characters Avoid using accented characters and special characters in path names. If special characters or accented characters 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 428 Create MyConfig - Expert 4.13 Command line call Parameter Significance of the switch Table 4-63 Expert parameters Switch Arguments Optional Description /verify The switch causes the specified project to be onlyverified. /config (<"Path configuration The switch causes the configuration file (*.upcfg) to be processed file>") when calling Expert after opening the project.
Page 429: Package Execution
Warnings but no errors occurred when validating the package. Errors (and possibly warnings) occurred when validating the package. Command line call error. Example Assumption: Create MyConfig is installed in the "C:\Program Files\SIEMENS \Create MyConfig 4.8"directory and a "Pack_1.upz" package is available in the "C:\Packages \"path. @echo off PATH=%PATH%;"C:\Program Files\SIEMENS\Create MyConfig 4.8"...
Page 430 Create MyConfig - Expert 4.13 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 431: Sinamics Device Configuration
Create MyConfig - Expert 4.14 SINAMICS device configuration Parameter Table 4-66 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 432: Sinamics Device Configuration With Automatic Configuration Or User-Specified Topology
Create MyConfig - Expert 4.14 SINAMICS device configuration 4.14.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 433 Create MyConfig - Expert 4.14 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 434: Drive Data Generation Via "Automatic Configuration
Create MyConfig - Expert 4.14 SINAMICS device configuration 4.14.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 435: Assignment Of The Drive Data Using Do Variables
Create MyConfig - Expert 4.14 SINAMICS device configuration 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. SINAMICS has in the result a customized target topology (p9903) and customized DOs for the specified components.
Page 436 Create MyConfig - Expert 4.14 SINAMICS device configuration Example Execution step Result Export of data from a drive archive in Diff to an ASCII file with [B3_S3_PS5] (corresponds to the path of the data storage reference to the DO in the data storage. [BUS3.DIR\SLAVE3.DIR\PS000005.TEA]) Replacement of the reference with a symbolic path.
Page 437: The Advantages Of Using Comparison Or User-Specified Topology
Create MyConfig - Expert 4.14 SINAMICS device configuration Figure 4-152 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. Although a direct assignment via a path specification is possible in short form, this limits the flexibility and can easily result in errors.
Page 438 Create MyConfig - Expert 4.14 SINAMICS device configuration Advantages for the configuration of the topology with Topo ● Understandable topology creation thanks to a graphical wiring diagram ● Support with component box, context menu, verification run and graphic / color-coded visualization ●...
Page 439: Configuration Of The Topology With Topo
Create MyConfig - Expert 4.14 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 440: Generation Of The Comparison Topology Using External Software
Create MyConfig - Expert 4.14 SINAMICS device configuration With switchover from comparison topology to user-specified topology, the additional properties DO activation, component activation and component number must also be specified. With switchover to comparison topology, the data remains stored for switch-back to user- specified topology.
Page 441 Create MyConfig - Expert 4.14 SINAMICS device configuration topology must be created for each machine version, whereas one package can be sufficient for all machines. Figure 4-155 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.
Page 442: 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 443 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 444 Create MyConfig - Expert 4.15 Reimporting packages SINUMERIK Integrate Create MyConfig - Diff, Expert, Topo Operating Manual, 12/2017, A5E36537479B-AE...
Page 445: Create Myconfig - Packages
Create MyConfig - Packages Note Password protection - read-protection Password protection protects your project from unwanted viewing by third parties. Note that password protection provides only basic read protection. The password protection does not provide any secure protection against cyber attacks. Starting the package execution You will find additional information on package execution in the section Create MyConfig packages (Page 405).
Page 446 Create MyConfig - Packages 5.4 Command line call SINUMERIK Integrate Create MyConfig - Diff, Expert, Topo Operating Manual, 12/2017, A5E36537479B-AE...
Page 447: 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 448: 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 449: 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 450 Windows tools. ● Import of topologies from SINUMERIK archives, from deployed topologies (ECAD XML files) ● Import of topologies from Siemens Data Exchange "*.sdx" from EPLAN Add-In, the following applies as of CMC version V4.8. ● Verification run for created topologies ●...
Page 451: Overview Of User Interface
Create MyConfig - Topo 6.3 Overview of user interface Assignment of DO variables and DO properties You can assign DO variables to the modules in Topo. These DO variables provide properties that can be used for configuring the package execution in Expert. In this way, it is possible to work flexibly in Expert with defined DO variables whose absolute values only apply during the package runtime on the machine.
Page 452 Create MyConfig - Topo 6.3 Overview of user interface ① Topologies Display of the existing topologies ② Topology tree Topology tree / topology graph: ③ Both display types offer the same functionality with regard to creating and ed‐ Topology graph iting a topology.
Page 453: Topo - Menu Functions
Create MyConfig - Topo 6.3 Overview of user interface 6.3.2 Topo - menu functions Topo provides the following main menus and submenus: Table 6-1 Topo - Project main menu Project <Ctrl+N> Creates a new project. Open... <Ctrl+O> Opens an existing "*.uptz" project and all specified file types that can be imported.
Page 454 EPLAN / Siemens Data Exchange: The import from a Siemens Data Exchange "*.sdx" file is only available when you have installed the "EPLAN Plugin for CMC" license in the Automation License Manager.
Page 455 Create MyConfig - Topo 6.3 Overview of user interface Project "Archive transfer" dialog Print Topology Prints either the topology tree or the topology graph. Properties... Shows important project properties, such as path of the project, date of change, changed by, version and com‐ ment.
Page 456 Create MyConfig - Topo 6.3 Overview of user interface Table 6-3 Topo - View main menu View Topology tree Shows or hides the topology tree. The topology tree and the graphic representation can never be hidden simultaneously. Topology graph Shows or hides the graphic topology view. The topology tree and the graphic representation can never be hidden simultaneously.
Page 457 Create MyConfig - Topo 6.3 Overview of user interface Table 6-4 Topo - Data main menu Data Manage DO list... Ctrl+Alt+D Opens the "DO list" dialog for the administration of DO variables. The DO variables can be added, imported, exported, or linked. You can find additional information at Manage DO list (Page 470).
Page 458: 6.4 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. Table 6-7 Topo - Help main menu Help Content...
Page 459 Create MyConfig - Topo 6.4 Topo - operation To display and edit several topologies, they can be selected in the list of topologies by making a multiple selection. Just the same as for Comparing topologies (Page 482), both technologies are displayed next to one another. Table 6-8 Topologies display: Topology tree and topology graph Topology tree...
Page 460 Create MyConfig - Topo 6.4 Topo - operation 3. The following window for creating a topology is displayed: ① Without preconfiguration An empty topology opens. ② Imported DO list An empty topology opens in which an extended DO list "*.uvdx" from any drive can be imported. ③...
Page 461 Create MyConfig - Topo 6.4 Topo - operation 5. 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 associated components.
Page 462 Create MyConfig - Topo 6.4 Topo - operation Figure 6-3 Assign DO variables Additional functions In addition to the standard functions such as "Cut", "Copy", "Paste", etc., the context menu of the topology configurator provides further functions: Table 6-9 Context menu for the topology configurator / topology graph Function Description Wire module...
Page 463 Create MyConfig - Topo 6.4 Topo - operation Function Description Replace component Replaces the selected component with a preconfigured and unused component for the assigned DO in the DO list. The wiring of the component remains unchanged. The proper‐ ties that do not belong to the preconfigured component also remain unchanged.
Page 464: Module Catalog
Create MyConfig - Topo 6.4 Topo - operation See also Module catalog (Page 464) Topo - menu functions (Page 453) 6.4.2 Module catalog Modules The modules are stored with article numbers and a brief description in the module catalog. It is possible to insert the components specifically or unspecifically.
Page 465 Create MyConfig - Topo 6.4 Topo - operation Figure 6-4 Modules SINUMERIK Integrate Create MyConfig - Diff, Expert, Topo Operating Manual, 12/2017, A5E36537479B-AE...
Page 466 Create MyConfig - Topo 6.4 Topo - operation Component properties Each component can be assigned various properties, depending on the device class: Component properties of the user-specified Component properties of the comparison top‐ topology "*.utz" ology "*.ust" Property Description Note Module Device class Device class display...
Page 467 Create MyConfig - Topo 6.4 Topo - operation Property Description Note Name Name of the component. Component names must be unique and have a maximum of 50 ASCII characters. C no. The CU-related SINAMICS component number The component number can be edited. The follow‐ is displayed or specified.
Page 468: Dolist Editor
Create MyConfig - Topo 6.4 Topo - operation Property Description Note Axis Display of the axis type, cannot be edited Axis name Name of the axis. NC drive Display of the NC drive. Setpoint type Selection of the setpoint type. DO variable The specified DO variable is assigned to this Not available for device classes that do not consti‐...
Page 469 Create MyConfig - Topo 6.4 Topo - operation File Save as... Saves the current DO list with a different path or file name. Properties... Displays the properties of the DO list. Last opened The DO lists opened last are displayed with path and file name and can be selected. Exit <Alt+F4>...
Page 470: Manage Do List
Create MyConfig - Topo 6.4 Topo - operation DO list in the DOList Editor Display of the DO list in the DOList Editor: Figure 6-6 Display of the DO list in the DOList Editor 6.4.4 Manage DO list Call the DO list via the "Data" > "Manage DO list…" main menu. Manage the DO variables used in the topology project via the DO list.
Page 471 Create MyConfig - Topo 6.4 Topo - operation Figure 6-7 Example of a DO list DO variables - assign properties You can assign the following properties to each DO variable: Property Description Note DO variable Name of the DO variable used in the package for Valid characters are: a-z, A-Z, 1-9, _ assignment to a drive object.
Page 472 Create MyConfig - Topo 6.4 Topo - operation Property Description Note DO No. DO number via which a drive object is addressed. The following numbers are permitted: ● 2 to 54 ● 61 and 62 Permissible for control units (CU_I, NX): ●...
Page 473: Local Do List
Create MyConfig - Topo 6.4 Topo - operation The properties of the DO variables assigned to a component are displayed in the "Properties" dialog. Figure 6-8 Component properties 6.4.4.1 Local DO list Each topology of a project has a separate variable table for local DO lists. Earlier CMC versions used a global list.
Page 474 Create MyConfig - Topo 6.4 Topo - operation Figure 6-9 Local DO list - display of linked and unlinked DO variables Note DO variables are no longer needed in Expert Packages can be deployed without requiring a DO list. Preferably, use the DO variables from the topology file. SINUMERIK Integrate Create MyConfig - Diff, Expert, Topo Operating Manual, 12/2017, A5E36537479B-AE...
Page 475: Generating Do Variables Automatically
Create MyConfig - Topo 6.4 Topo - operation 6.4.4.2 Generating DO variables automatically If a new DO-forming component is added to a topology, a DO variable can be generated. ① No DO is created for this selection. ② A DO is generated. DO variable, DO number and DO name can be edited. The DO type is determined automatically. ③...
Page 476: Extended Do List
Only preconfigured DOs and components are used for a referenced DO list. 2. Use for configuring the EPLAN with the DQ topology export As described in item 1, the configured DO list in Topo is used in the Siemens DQ topology export (EPLAN Add-In) for deriving a topology.
Page 477 Create MyConfig - Topo 6.4 Topo - operation ① Open DO Clicking the blue plus character opens a drive object (DO). A new dialog displays the components that belong to the DO. ② Component display of a DO. The component properties are changed in the components dialog. Components can be added and/or deleted.
Page 478 Create MyConfig - Topo 6.4 Topo - operation Exporting an extended DO list For exporting an extended "*.uvdx" DO list, all components linked with the DOs are exported, irrespective whether the components were configured via the DO list or assigned from the topology to the DO.
Page 479 Create MyConfig - Topo 6.4 Topo - operation If one of the versions based on a DO list is selected, the DO list contains preconfigured DO properties and component properties. A DO list simplifies the assignment of properties when configuring the topology. Note Working with DO list "*.uvd"...
Page 480 Create MyConfig - Topo 6.4 Topo - operation Figure 6-14 "Select component" dialog Note Linked DO lists Only preconfigured components are available for linked DO lists. Use of a DO list on an existing topology If in an existing topology, a "*.uvdx" or "*.uvd" DO list is imported, all DO assignments in the topology are initially deleted.
Page 481 Create MyConfig - Topo 6.4 Topo - operation Figure 6-15 DO list - preconfigured components Figure 6-16 Preconfigured properties for a component The following options are available: ● "Retain existing component properties" The existing component properties are retained or can be adapted directly in the dialog. ●...
Page 482: Predefined Axis Assignment For The Eplan Add-In
The predefined axis assignment is only used for the import of a topology from the EPLAN Add- In via the Siemens Data Exchange "*.sdx" format. Whereby, the preconfiguration of the DOs used in the specific topology is performed in the axis-drive assignment.
Page 483 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 484: 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 485: Axis-Drive Assignment
Create MyConfig - Topo 6.5 Axis-drive assignment 1. Select the topology that you want to deploy. 2. Set the deploy mode of the topology to deploy this as "*.utz" user-defined topology or "*.ust" comparison topology. 3. Set the correct CNC version. If Control Units with different firmware versions are used in a topology, e.g.
Page 486 Create MyConfig - Topo 6.5 Axis-drive assignment Moreover, it is possible for the project engineer for Expert and the operator during package execution to deactivate this automatic Axis-drive assignment without having to open and edit the topology files. 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-19...
Page 487: Execution
Create MyConfig - Topo 6.5 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 488 Create MyConfig - Topo 6.5 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-20 Axis-drive assignment using I/O addresses Version 2: Axis-drive assignment using the drive number...
Page 489 Create MyConfig - Topo 6.5 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 490: Diagnostics
Create MyConfig - Topo 6.5 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-23 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 491: Command Line Call
Create MyConfig - Topo 6.6 Command line call 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 492 Create MyConfig - Topo 6.6 Command line call Starting Topo Topo is started with the following command, and a file can be displayed and edited. Topo <Topology path> Comparing topologies Two topologies can be compared with the following command, i.e. two files are displayed and can be edited.
Page 493 Create MyConfig - Topo 6.6 Command line call Note Path data ● Paths must be specified in straight quotation marks if spaces are included. Example: "C:\Path with spaces\Expert_Logfile.log" ● Paths must never end with '\'. Note Saving batch files Always save batch files with ANSI/ASCII coding. Note Accented characters and special characters Avoid using accented characters and special characters in path names.
Page 494 Create MyConfig - Topo 6.6 Command line call Parameter Significance of the switch Table 6-15 Topo - parameters Switch Arguments Optional Description <Topology path> ● Specifies the path of the project file – either absolute or relative. ● Paths must be specified in straight quotation marks if spaces are included.
Page 495 Create MyConfig - Topo 6.6 Command line call Switch Arguments Optional Description /target (UST|(UTZ|USZ|EXE[27|44|45|47| ● Deployment type and CNC software version of the 48])) NCU, on which the user-specified topology is applied. Note (UST|UVDX|(UTZ|USZ|EXE[27| 44| 45|47|48])) Deployment version If no deployment version is specified for the "UTZ", "USZ"...
Page 496: Sinamics Device Configuration
Faults (and possibly alarms) occurred when checking/deploying the project. Command line call error. Example Precondition: Create MyConfig is installed in the "C:\Program Files\SIEMENS\Create MyConfig 4.8" directory and a "TopoProj_1.uptz" project that contains the "Topo1" and "Topo2" topologies is available in the path "C:\Topology"...
Page 497: Sinamics Device Configuration With Automatic Configuration Or User-Specified Topology
Create MyConfig - Topo 6.7 SINAMICS device configuration The production of machines with 840D sl requires a basic commissioning of the SINAMICS, generally designated as "System configuration". The system configuration can be performed with CMC either as "Automatic configuration" or as "User-specified topology." When the system configuration is configured in the CMC package, all the data sets and optimization data in the step tree required within a series of modular machines in the maximum machine configuration can be specified.
Page 498 Create MyConfig - Topo 6.7 SINAMICS device configuration Differences between "Automatic configuration" and "User-specified topology" The table below shows the major differences between "Automatic configuration" and "User- specified topology." In the same way as the automatic device configuration via SINUMERIK Operate, the PROFIBUS assignment (p978), the message frames and the BICO links are also entered automatically in both CMC variants.
Page 499 Create MyConfig - Topo 6.7 SINAMICS device configuration Figure 6-25 CMC package structure SINUMERIK Integrate Create MyConfig - Diff, Expert, Topo Operating Manual, 12/2017, A5E36537479B-AE...
Page 500: Drive Data Generation Via "Automatic Configuration
Create MyConfig - Topo 6.7 SINAMICS device configuration 6.7.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 501: Assignment Of The Drive Data Using Do Variables
Create MyConfig - Topo 6.7 SINAMICS device configuration 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. SINAMICS has in the result a customized target topology (p9903) and customized DOs for the specified components.
Page 502 Create MyConfig - Topo 6.7 SINAMICS device configuration Example Execution step Result Export of data from a drive archive in Diff to an ASCII file with [B3_S3_PS5] (corresponds to the path of the data storage reference to the DO in the data storage. [BUS3.DIR\SLAVE3.DIR\PS000005.TEA]) Replacement of the reference with a symbolic path.
Page 503: The Advantages Of Using Comparison Or User-Specified Topology
Create MyConfig - Topo 6.7 SINAMICS device configuration Figure 6-27 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. Although a direct assignment via a path specification is possible in short form, this limits the flexibility and can easily result in errors.
Page 504 Create MyConfig - Topo 6.7 SINAMICS device configuration Advantages for the configuration of the topology with Topo ● Understandable topology creation thanks to a graphical wiring diagram ● Support with component box, context menu, verification run and graphic / color-coded visualization ●...
Page 505: Configuration Of The Topology With Topo
Create MyConfig - Topo 6.7 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 506: Generation Of The Comparison Topology Using External Software
Create MyConfig - Topo 6.7 SINAMICS device configuration With switchover from comparison topology to user-specified topology, the additional properties DO activation, component activation and component number must also be specified. With switchover to comparison topology, the data remains stored for switch-back to user- specified topology.
Page 507 Create MyConfig - Topo 6.7 SINAMICS device configuration topology must be created for each machine version, whereas one package can be sufficient for all machines. Figure 6-30 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.
Page 508: Extended User-Specified Topology
Create MyConfig - Topo 6.8 Extended user-specified topology Extended user-specified topology Requirement Create MyConfig contains the "Extended user-specified topology" as a third mode in addition to the comparison and user-specified topologies. Figure 6-31 Topologies display: Extended user-specified topology In addition to the SINAMICS wiring diagram, the extended user-specified topology also includes NC and DRV data.
Page 509 Create MyConfig - Topo 6.8 Extended user-specified topology This means that: ● When a DO is moved, the complete dataset is always moved, including all of the components used in it. ● All of the DO data is symbolically displayed by the "Motor Module" component (TM, hub). ●...
Page 510: Interface Topo Xml
Create MyConfig - Topo 6.9 Interface Topo XML Note No more than 6 Motor Module (MM) may be connected to a Slave. Deployment methods You can select between the following deployment methods: The extended user-specified topology is transferred directly to the control. The user can optionally select or deselect the PLC and NC data.
Page 511 Create MyConfig - Topo 6.9 Interface Topo XML <cliq index="2"/> </line_module> </cliq> <cliq index="1"> <motor_module doname="X-Antrieb" donr="3" dotype="11" dovar="doX" name="MM_X" compnr="3"> <cliq index="0" uplink="true"/> <cliq index="1"> <motor_module doname="Y-Antrieb" donr="4" dotype="11" dovar="doY" name="MM_Y" compnr="7"> <cliq index="0" uplink="true"/> <cliq index="1"> <sensor_module name="SM1_Y" compnr="9" sm="1" doref="doY"...
Page 512: Description Of The Xml Structure
Create MyConfig - Topo 6.9 Interface Topo XML gray, normal An attribute that is only required in a certain constellation blue, italics Optional attributes for the param‐ eterization of the package (varia‐ bles) brown, italics Optional attributes to change the component name green, italics Optional attributes to restrict to...
Page 513 Create MyConfig - Topo 6.9 Interface Topo XML Composite modules For composite modules, such as Double Motor Modules and 120 combi modules, their internal structure must be mapped in the XML structure. To ensure the correct display as composite module in Topo, all the internal components belonging to such a module must be identified with the attribute group="<name of the composite component>".
Page 514 Create MyConfig - Topo 6.9 Interface Topo XML DRIVE-CLiQ connection type Analog connection type Power connection type Figure 6-33 S120 Combi topological modeling DO-forming DRIVE-CLiQ components SINAMICS automatically creates drive objects (DO) for specific DRIVE-CLiQ components. DO-forming DRIVE-CLiQ components: control_unit_ncu, motor_module_hf control_unit_nx, control_unit_cu, line_module, motor_module, hub_module, terminal_module, terminal_board.
Page 515 Create MyConfig - Topo 6.9 Interface Topo XML If such a component was assigned a DO variable manually or via the Topo XML file, this DO 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 516: 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 517 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 518 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 519 Create MyConfig - Topo 6.9 Interface Topo XML <xs:simpleType name ="utzvers"> <xs:restriction base="xs:unsignedInt"> <xs:enumeration value="27"/> <xs:enumeration value="44"/> <xs:enumeration value="45"/> <xs:enumeration value="47"/> <xs:enumeration value="48"/> </xs:restriction> </xs:simpleType> <xs:simpleType name ="deploymode"> <xs:restriction base="xs:string"> <xs:enumeration value="UST"/> <xs:enumeration value="UTZ"/> <xs:enumeration value="NC"/> </xs:restriction> </xs:simpleType> <!-- <xs:simpleType name ="slotnr"> <xs:restriction base="xs:unsignedInt">...
Page 520 Create MyConfig - Topo 6.9 Interface Topo XML <xs:complexType name="slave"> <xs:choice minOccurs="1" maxOccurs="1"> <xs:element name="control_unit_ncu" type="control_unit_ncu" minOccurs="1" maxOccurs="1" /> <xs:element name="control_unit_cu" type="control_unit_cu" minOccurs="1" maxOccurs="1" /> <xs:element name="control_unit_nx" type="control_unit_nx" minOccurs="1" maxOccurs="1" /> </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"...
Page 521 Create MyConfig - Topo 6.9 Interface Topo XML </xs:complexType> <xs:complexType name="docomp" abstract="true"> <xs:complexContent> <xs:extension base="compbase"> <xs:attribute name="dovar" type="xs:string" use="optional" / > <xs:attribute name="dotype" type="dotype" use="optional" /> <xs:attribute name="donr" type="uShort" use="optional" /> <xs:attribute name="doname" type="xs:string" use="optional" / > <xs:attribute name="dodesc" type="xs:string" use="optional" / >...
Page 522 Create MyConfig - Topo 6.9 Interface Topo XML </xs:complexContent> </xs:complexType> <xs:complexType name="control_unit_ncu_828"> <xs:complexContent> <xs:extension base="docomp"> <xs:sequence> <xs:element name="cliq" type="cliq" minOccurs="3" maxOccurs="3" /> </xs:sequence> <xs:attribute name="utzversion" type="utzvers" use="optional" /> </xs:extension> </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"...
Page 523 Create MyConfig - Topo 6.9 Interface Topo XML <xs:element name="cliq" type="cliq" minOccurs="3" maxOccurs="3" /> </xs:sequence> <xs:attribute name="compstate" type="state" use="optional" / > </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="motor_module_base" abstract ="true"> <xs:complexContent> <xs:extension base="dostatecomp"> <xs:sequence> <xs:element name="cliq" type="cliq" minOccurs="3" maxOccurs="3" /> </xs:sequence> <xs:attribute name="compstate" type="state" use="optional" / >...
Page 524 Create MyConfig - Topo 6.9 Interface Topo XML </xs:choice> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="motor_module_hla"> <xs:complexContent> <xs:extension base="dostatecomp"> <xs:choice maxOccurs="2"> <xs:element name="cliq" type="cliq" minOccurs="4" maxOccurs="4" /> <xs:element name="valve" type="valve" minOccurs="0" maxOccurs="1" /> </xs:choice> <xs:attribute name="compstate" type="state" use="optional" / > </xs:extension> </xs:complexContent> </xs:complexType>...
Page 525 Create MyConfig - Topo 6.9 Interface Topo XML <xs:sequence> <xs:element name="motor" type="motor" minOccurs="0" maxOccurs="1" />  <xs:element name="encoder" type="encoder" minOccurs="0" maxOccurs="1" />  </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="motor"> <xs:complexContent> <xs:extension base="compbase"/> </xs:complexContent>...
Page 526 Create MyConfig - Topo 6.9 Interface Topo XML </xs:complexContent> </xs:complexType> <xs:complexType name="terminal_module"> <xs:complexContent> <xs:extension base="dostatecomp"> <xs:sequence> <xs:element name="cliq" type="cliq" minOccurs="2" maxOccurs="2" /> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> <xs:complexType name="terminal_board"> <xs:complexContent> <xs:extension base="dostatecomp"/> </xs:complexContent> </xs:complexType> <xs:complexType name="comm_board"> </xs:complexType> <xs:complexType name="cu_link"> <xs:complexContent> <xs:extension base="dostatecomp"> <xs:attribute name="address"...
Page 527 Create MyConfig - Topo 6.9 Interface Topo XML <xs:complexType name="ada_enc"> <xs:attribute name="idx" type="encidx" use ="required"/> <xs:attribute name="enctype" type="enctype" use="optional"/> <xs:attribute name="encinputnr" type="smnr" use="optional"/> <xs:attribute name="doref" type="xs:string" use="optional"/> </xs:complexType> </xs:schema> SINUMERIK Integrate Create MyConfig - Diff, Expert, Topo Operating Manual, 12/2017, A5E36537479B-AE...
Page 528 Create MyConfig - Topo 6.9 Interface Topo XML SINUMERIK Integrate Create MyConfig - Diff, Expert, Topo Operating Manual, 12/2017, A5E36537479B-AE...
Page 529: Create Myconfig - Faqs
Create MyConfig - FAQs Restoring the original status of a USB memory stick To be able to use a USB memory stick for CMC, you must make sure that the partitions are created correctly. 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/PPU.
Page 530: Help For Problems With Ncushareservice
Create MyConfig - FAQs 7.2 Help for problems with NcuShareService 3. Sel disk 1 selects this data storage medium. You must use the right number on the basis of your existing data storage medium. NOTICE Select Sel disk A data storage medium that you did not want could be destroyed if you specify a wrong number.
Page 531: Error Checking
Create MyConfig - FAQs 7.2 Help for problems with NcuShareService This permits the exchange of data between NCU/PPU and PC/PCU during the package execution. 7.2.3 Error checking What must be checked in the event of an error? Use of virtual machines In connection with virtual machines, problems may occur when establishing a connection, because the share of the NCU cannot be achieved.
Page 532 Create MyConfig - FAQs 7.2 Help for problems with NcuShareService UpNcuShare service, "General" tab default settings UpNcuShare service, "Log on" tab default settings SINUMERIK Integrate Create MyConfig - Diff, Expert, Topo Operating Manual, 12/2017, A5E36537479B-AE...
Page 533: Important Folders And Files
Create MyConfig - FAQs 7.3 Important folders and files Changing the share folder The share 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 534 Create MyConfig - FAQs 7.3 Important folders and files SINUMERIK Integrate Create MyConfig - Diff, Expert, Topo Operating Manual, 12/2017, A5E36537479B-AE...
Page 535: List Of Abbreviations
Table A-1 File extensions for the file formats used in CMC *.arc NC, PLC, SDB or DRV archive *.ard Data class archive *.sdx Siemens Data Exchange (from EPLAN plugin) SINUMERIK Integrate Create MyConfig - Diff, Expert, Topo Operating Manual, 12/2017, A5E36537479B-AE...
Page 536 List of abbreviations A.1 Abbreviations *.tgz CNC software *.ts Resource file *.ucz Expert component *.upcfg Step configuration *.uplib Script libraries *.upscr Script file in Diff *.upt Topology project; designation up to CNC Version V4.6 *.uptz Topology project; the designation applies as from CMC Version V4.7 *.upz Expert project *.uss...
Page 537: Index
Index Axis-drive assignment Configuration, 486 " Drive number, 488 I/O Addresses, 488 "EPLAN Plugin for CMC" license, 454 machine data, 490 "List of user script libraries" User-defined, 489 Toolbar, 342 "Script Editor 4.8", 339 Buttons for dialogs, 155 $Pack, 371 Step tree, 227 828D, 3, 23, 136, 168, 171 C no.
Page 538 Index Command line call Component status Diff, 110 C status, 467 Expert, 422, 426 Component type, 450 Notes, 111, 422, 426, 430, 492 Components Package deployment by Expert, 422 Differences, 483 Package execution, 429 Properties, 466, 483 Shield, 429 Concatenation operator Topo, 491 String concatenation, 290 Verification run, 426...
Page 539 Index Configuration - File identification Data task Comment tab, 107 Configuration, 52 Settings tab, 106 Data task wizard, 56 Configuration - Folder comparison Data tasks Comment tab, 84 Application examples, 52 Comparison tab, 82 Supplementary conditions, 51 Filter tab, 83 DateTime Configuration - SINUMERIK archive comparison Function, 328...
Page 540 Index Diff main menu DO variables Comparison, 26, 27, 70, 89 Assignment options, 437, 503 Edit, 25, 26, 69, 87, 88 Properties, 436, 502 File, 25, 69, 87 DOList Editor, 468 Help, 30, 73, 92 Extras, 469 Tools, 28, 29, 71, 72, 73, 90, 91, 92 File, 468, 469 View, 26, 70, 88 Help, 469...
Page 541 Index OnInit, 147 Expert main menus OnNext, 147 Component, 130, 131 Example, 295 Configuration, 131, 132, 245, 246 Comments, 339 Edit, 130 DateTime, 328 Help, 133 Diff, 115 Project, 129, 130 Expert, 425, 429 Tools, 132 FileDelete, 296 View, 130 FileExist, 298 Window, 133 Input, 311...
Page 542 Index Edit main menu, 69 If-ElseIf-Else control structure, 284 File main menu, 69 If-ElsIf control structure, 284 Help main menu, 73 Import tasks, 52 Overview, 68 Input Overview window, 77 Function, 310, 311 Toolbar, 74 Input function, 310 Tools main menu, 71, 72, 73 InputChoice View main menu, 70 Function, 312...
Page 543 Index Archive, 412 Mode, 383 Buttons, 414 Module Details on, 416 Replace, 462 Dialog page: CNC software, 417 Rewire, 462 Dialog page: Package configuration, 415 Wiring, 462 Dialog page: Step tree, 418 Module catalog, 464 Home page, 412 Package selection, 414 Procedure, 310 ServiceDate Transfer, 421 Storage location, 224...
Page 544 Index Notes on the package Network drive, 408 Configuration, 158 Notes about acknowledgment, 157 Package execution, 160 Notes on GSP, 177 Notes on the step tree Notes on the package, 160 Configuration, 211 Notes on the step tree, 213 Package execution, 213 Notes on the topology, 196 Notes on the topology Package configuration, 154...
Page 545 Resource Editor, 350, 357, 358 ServiceData, 377 Extras, 358 ServiceDataNotes, 376 File, 357 Share folder Help, 358 Create MyConfig NcuShare, 533 Resource Editor 4.8, 357 Siemens DQ-Topo Export, 454 SINAMICS, 450 SINUMERIK Integrate Create MyConfig - Diff, Expert, Topo Operating Manual, 12/2017, A5E36537479B-AE...
Page 546 StepSelection, 381 SINUMERIK 828D, 3, 23, 136, 168, 171 StepSelectionNotes, 380 828D, 458 Storage location HW Config, 136 Logbook, 224 SINUMERIK 840D sl, 23, 168, 171, 458 String concatenation Skip Concatenation operator, 290 Procedure, 327 StringLen Source explorer Function, 290...
Page 547 Index Package execution, 193 NcuOrigin, 376 User-specified topology, 432, 497 NcuResult, 381 System texts, 346 NcuSetup, 377 System variables Package properties $Pack, 371 $Pack, 371 PackageConfig, 372 ArcSelection, 374 PackageEnd, 382 Change to version 4.7 SP2, 135 PackageNotes, 373 ConfirmNotes, 373 PcuAccess, 374 DriveTopology, 379 Processing modes enumeration -...
Page 548 Index Data main menu, 457 Up.$Pack.Language, 370 Edit main menu, 455 Up.$Pack.Name, 371 Example, 496 Up.$Pack.NCU, 371 Help main menu, 458 Up.$Pack.PCU, 370 Parameter, 494 Up.$Pack.ProdVersion, 370 Project main menu, 453, 454, 455 Up.$Pack.UserVersion, 370 Return values, 495 Up.$Step, 385 Switch, 494 Up.$Step[id].Activated, 386 Tools main menu, 458...
Page 549 Index Warning Procedure, 310 Window SINUMERIK archive comparison, 36 Windows, 259 Windows package, 129 Network drive, 408, 410 PCU 50, 408 XML structure cliq, 516 doref, 515 dovar, 515 index, 516 oemid, 516 sm, 515 uplink =true, 516 ZIP archive, 68, 84 SINUMERIK Integrate Create MyConfig - Diff, Expert, Topo Operating Manual, 12/2017, A5E36537479B-AE...
Page 550 Index SINUMERIK Integrate Create MyConfig - Diff, Expert, Topo Operating Manual, 12/2017, A5E36537479B-AE...

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

Quick Links

Related Manuals for Siemens SINUMERIK 840D sl

Summary of Contents for Siemens SINUMERIK 840D sl