simotion 3 - siemens · simotion documentation an overview of the simotion documentation can be...

� �Project comparison

___________________

___________________

___________________

___________________

___________________

___________________

SIMOTION

SIMOTION SCOUT Project comparison

Function Manual

02/2012

Preface

Overview of project comparison

1

General information on object comparison

2

Functions 3

Overview of comparison attributes

4

Appendix A A

Legal information

Legal information Warning notice system

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

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

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

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

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

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

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

Qualified Personnel The product/system described in this documentation may be operated only by personnel qualified for the specific task in accordance with the relevant documentation, in particular its warning notices and safety instructions. Qualified personnel are those who, based on their training and experience, are capable of identifying risks and avoiding potential hazards when working with these products/systems.

Proper use of Siemens products 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. The permissible ambient conditions must be complied with. The information in the relevant documentation must be observed.

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

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

Siemens AG Industry Sector Postfach 48 48 90026 NÜRNBERG GERMANY

Copyright © Siemens AG 2012. All rights reserved

Project comparison Function Manual, 02/2012 3

Preface

SIMOTION Documentation An overview of the SIMOTION documentation can be found in a separate list of references.

This documentation is included as electronic documentation in the scope of delivery of SIMOTION SCOUT. It comprises 10 documentation packages.

The following documentation packages are available for SIMOTION V4.3:

● SIMOTION Engineering System

● SIMOTION System and Function Descriptions

● SIMOTION Service and Diagnostics

● SIMOTION IT

● SIMOTION Programming

● SIMOTION Programming - References

● SIMOTION C

● SIMOTION P

● SIMOTION D

● SIMOTION Supplementary Documentation

Hotline and Internet addresses

Additional information Click the following link to find information on the the following topics:

● Ordering documentation/overview of documentation

● Additional links to download documents

● Using documentation online (find and search in manuals/information)

http://www.siemens.com/motioncontrol/docu

Please send any questions about the technical documentation (e.g. suggestions for improvement, corrections) to the following e-mail address: [email protected]

My Documentation Manager Click the following link for information on how to compile documentation individually on the basis of Siemens content and how to adapt this for the purpose of your own machine documentation:

http://www.siemens.com/mdm

Preface

Project comparison 4 Function Manual, 02/2012

Training Click the following link for information on SITRAIN - Siemens training courses for automation products, systems and solutions:

http://www.siemens.com/sitrain

FAQs Frequently Asked Questions can be found in SIMOTION Utilities & Applications, which are included in the scope of delivery of SIMOTION SCOUT, and in the Service&Support pages in Product Support:

http://support.automation.siemens.com

Technical support Country-specific telephone numbers for technical support are provided on the Internet under Contact:

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


Table of contents

Preface ...................................................................................................................................................... 3

1 Overview of project comparison................................................................................................................. 7

2 General information on object comparison ................................................................................................ 9

2.1 The user interface ..........................................................................................................................9

2.2 Comparison icons ........................................................................................................................12

2.3 Comparison tree ..........................................................................................................................13

2.4 Comparison attributes, aspects, and sub-aspects.......................................................................14

2.5 Object attributes...........................................................................................................................15

3 Functions ................................................................................................................................................. 17

3.1 Downloading additional data........................................................................................................17

3.2 Starting an object comparison .....................................................................................................18 3.2.1 Starting the object comparison and selecting comparison partners ............................................19 3.2.2 Different versions detected (offline comparison with saved project) ...........................................20 3.2.3 Object comparison with projects converted to a higher version ..................................................21 3.2.4 Going offline after online comparison (comparison is no longer up to date) ...............................22

3.3 Assignment of objects in object comparison................................................................................22 3.3.1 Object assignment .......................................................................................................................22 3.3.2 Automatic assignment of the subordinate comparison objects ...................................................23 3.3.3 Changing the object addresses of TOs .......................................................................................25

3.4 Detailed comparison ....................................................................................................................25 3.4.1 Introduction ..................................................................................................................................25 3.4.2 Starting the detailed comparison .................................................................................................26 3.4.3 Introduction: ST, LAD/FBD, MCC detail comparison...................................................................27 3.4.4 ST detail comparison ...................................................................................................................29 3.4.4.1 Introduction ..................................................................................................................................29 3.4.4.2 Example: ST detail comparison ...................................................................................................30 3.4.5 MCC and LAD/FBD detail comparison of declaration tables.......................................................30 3.4.5.1 Introduction ..................................................................................................................................30 3.4.5.2 Example: Detail comparison of declaration tables.......................................................................32 3.4.6 MCC detail comparison of charts.................................................................................................32 3.4.6.1 Introduction ..................................................................................................................................32 3.4.6.2 Examples: MCC detail comparison of charts...............................................................................33 3.4.7 LAD/FBD detail comparison of networks .....................................................................................37 3.4.7.1 Introduction ..................................................................................................................................37 3.4.7.2 Examples: LAD/FBD detail comparison of networks ...................................................................39 3.4.8 Detail comparison of simply structured data................................................................................40 3.4.8.1 Introduction ..................................................................................................................................40 3.4.8.2 Examples: Detail comparison of simply structured data..............................................................43 3.4.9 TO/DO detailed comparison ........................................................................................................45 3.4.9.1 Differences between TO/DO detailed comparison and experts list comparison .........................45

Table of contents


3.4.9.2 TO detailed comparison .............................................................................................................. 46 3.4.9.3 DO detail comparison.................................................................................................................. 47

3.5 Data transfer ............................................................................................................................... 49 3.5.1 Function....................................................................................................................................... 49 3.5.2 Rules for data transfer................................................................................................................. 49 3.5.3 Procedure for data transfer ......................................................................................................... 51 3.5.4 Duplicate assignment of an object address ................................................................................ 52

4 Overview of comparison attributes........................................................................................................... 53

4.1 SIMOTION objects ...................................................................................................................... 54 4.1.1 SIMOTION device ....................................................................................................................... 54 4.1.2 Technology object (TO)............................................................................................................... 56 4.1.3 Source......................................................................................................................................... 57 4.1.4 DCC chart.................................................................................................................................... 60 4.1.5 Library ......................................................................................................................................... 63 4.1.6 Source in a library ....................................................................................................................... 64 4.1.7 DCC chart in a library.................................................................................................................. 65

4.2 SINAMICS objects ...................................................................................................................... 66 4.2.1 Drive unit ..................................................................................................................................... 66 4.2.2 Drive object (DO) ........................................................................................................................ 66 4.2.3 DCC chart.................................................................................................................................... 67

4.3 MICROMASTER and SINAMICS G120 objects ......................................................................... 67 4.3.1 Drive unit ..................................................................................................................................... 67 4.3.2 Drive object (DO) ........................................................................................................................ 67

A Appendix A .............................................................................................................................................. 69

A.1 Frequently Asked Questions (FAQs) .......................................................................................... 69

Index........................................................................................................................................................ 73


Overview of project comparison 1

You can use the SIMOTION SCOUT/STARTER Project comparison function (start this via the Start object comparison button) to compare objects within the same project and/or objects from different projects (online or offline). Objects in the project comparison are SIMOTION devices, drive units, libraries. The project comparison is available with SIMOTION SCOUT and STARTER. Comparing projects is useful if you need to carry out service work on the system.

It may, for example, be the case that inconsistencies are indicated when you switch to online mode in the project navigator, i.e. there are deviations between your project in SIMOTION SCOUT/STARTER and the project loaded to the target system.

Examples of possible causes for this are:

● A program has been changed

● The result of compiling a program is different

● There is a deviation on the global device variables

● The execution system has been changed

● The hardware configuration has been changed

● An ST program in a library has been changed

● A piece of configuration data for an axis has been changed

The object comparison allows you to establish these differences and, if necessary, run a data transfer to rectify the differences. The following comparisons are possible:

● Offline object with offline object from the same project

● Offline object with offline object from a different project

● Offline object with online object (not for libraries)

The first comparison partner, the reference object (A), is in the open project, while the second partner, the comparison object (B), can be a comparison object in the open project, in a different project, or the online partner.

Note

When comparing to a project that has been created with a SIMOTION SCOUT/STARTER Version < 4.3, you must first convert the project to SIMOTION SCOUT/STARTER Version 4.3. For the comparison attributes, aspects and subaspects to be displayed, you must recompile the project after it has been upgraded.

The project comparison function is also available when using devices with older firmware versions if you have edited or converted the project with SIMOTION SCOUT or STARTER V4.3.

Overview of project comparison


The highest level for a comparison is a device, not the project. The comparison can be started via a

● SIMOTION device,

● Drive unit, or

● Library.

A detail comparison of the individual objects is available for the programming languages ST (Structured Text), LAD/FBD (ladder logic/function block diagram), and MCC (Motion Control Chart) as well as for DOs (drive objects) and TOs (technology objects) and simply structured data such as CPU system variables, TO interconnections, among others.

Note

Reliable statements on the comparison status of the creation data (e.g. compilation result of a program) can only be made when the project has been compiled. For example, changing an interface in source A has an effect on the compilation result of source B, which uses this interface.

Note

The displayed values are of generic nature, for example, as calculated in the CamEdit configuration, and are not rounded off.

Differences between the project comparison and the online/offline comparison

In terms of drive objects, the project comparison produces precise results compared to the online/offline method. This is because the project comparison compares the contents of projects whereas the online/offline method only evaluates on the basis of a change counter. The consistency information for DOs, displayed in the project navigator, is also based on the change counter.

Example: For a particular DO, the project navigator shows an inconsistency between the project data in the PG/PC and the project data in the target system. The online/offline comparison may highlight a difference, while the results of the project comparison show everything to be the same.


General information on object comparison 2

You can use the SIMOTION SCOUT/STARTER Object comparison function (start this via the Start object comparison button) to compare objects within the same project and/or objects from different projects (online or offline), see also Project comparison overview. Objects are devices, programs, technology objects (TOs) or drive objects (DOs), and libraries. Below you will find an overview of the elements and structure of the Object Comparison dialog box. You can start the detail comparisons from this dialog box, e.g. for LAD/FBD, ST or also for CPU system variables.

2.1 The user interface A user interface in which the differences in the various objects have been detected has been selected as an example for the screenshot below. In the case of programs, all the data from this user interface could be transferred and it would be possible to carry out a detailed comparison for two programs.

Table 2- 1 The user interface elements of the project comparison

No. Description 1 Comparison partner A and comparison partner B (online/offline) 2 Comparison tree made up of comparison partner elements 3 Object present (column A, column B):

The columns indicate whether or not a tree object is present for comparison partner A and/or comparison partner B.

4 Result of comparison: The comparison result is shown in this column (same/different). (See Comparison icons) Note: If the comparison is no longer up-to-date or only when offline during online comparisons, the status column heading is displayed hatched.

5 Select/change comparison partner 6 Update comparison 7 Call up online help 8 Display object attributes (see Object attributes)

The attributes of the comparison partners are compared in two columns. 9 Start detailed comparison 10 Comparison attributes of an object (see Comparison attributes, aspects and sub-

aspects) 11 Aspects of a comparison attribute (see Comparison attributes, aspects and sub-

aspects) 12 Aspect, created data

General information on object comparison 2.1 The user interface


No. Description 13 Data transfer:

Transfer of data from comparison partner B into the open project. 14 Status bar 15 Object comparison tab

General information on object comparison 2.1 The user interface


Figure 2-1 SIMOTION object comparison user interface

General information on object comparison 2.2 Comparison icons


See also Comparison icons ()

Object attributes (Page 15)

Comparison attributes, aspects, and sub-aspects (Page 14)

2.2 Comparison icons Below you will find an overview of the icons used in columns A and B, and their status.

Table 2- 2 Overview of icons used

Icon Description

Object is present (displayed in columns A and/or B).

Object is not present (displayed in column A and/or B).

Difference in at least one subordinate object or comparison attribute (only displayed if the folder or object is collapsed).

The comparison attribute is the same.

The comparison attribute is different.

The compilation result does not match the source status of comparison partner A or B.

A same/different statement cannot be made. An example of a possible cause of this is that the hardware configuration is being compared using the time stamp. If the time stamp deviates, a same/different statement cannot be made.

Please note the following:

● Columns A and B are not completed for comparison attributes. The same objects have the same attributes, i.e. they are present. However, the characteristic of the attributes may be the same or different; this same or different characteristic is indicated accordingly.

● If an object does not have a comparison partner, the comparison attributes cannot be seen (the objet cannot be expanded in the tree).

● Folders which do not contain any objects are not shown in the comparison tree.

General information on object comparison 2.3 Comparison tree


2.3 Comparison tree The way in which the comparison tree is displayed reflects how trees are displayed in the project navigator. The comparison tree is extended by displaying the comparison attributes (see the chapter titled Overview of comparison attributes (Page 53)).

A single tree is produced from the two trees/subtrees of the comparison partners. If it has been possible to assign two of the comparison partners' objects (see the Assigning objects in object comparison (Page 22) section), there will be one entry in the tree, and columns A and B will contain the Object available symbol. If it has not been possible to assign any comparison partners, the Object present or Object not present icon is displayed in the column for comparison partner A or comparison partner B, depending on which it belongs to (see example below).

Figure 2-2 Example of merging comparison partners

If an object is only present for one comparison partner, no comparison attributes are shown in the tree. Subordinate folders and objects are shown.

If the comparison partners are different , the tree is shown expanded. This gives you a quick overview of the differences.

The comparison tree shows a snapshot. As a result of changes in the open project, the comparison status may no longer be up to date. You will be informed of this status by means of

● the shaded column heading and

● the message The comparison is no longer up-to-date in the status bar.

Since the comparison tree is not automatically updated, you have to explicitly start the update by clicking the Update button.

Note

The comparison only displays parameter differences which are relevant to the download; differences relating to current data are not displayed. For the DOs, the download parameters are compared (please also refer to the Display filter for DO detail comparison) section; the configured values are compared for the TOs.

General information on object comparison 2.4 Comparison attributes, aspects, and sub-aspects


2.4 Comparison attributes, aspects, and sub-aspects In order to be able to analyze differences when comparing objects, there is a range of comparison attributes for each object type, which structure an object into smaller units (aspects and sub-aspects) and which, as a whole, contain all the object data that is of relevance to execution.

You will already be familiar with some of the comparison attributes from the project navigator (e.g. global device variables). In addition to this, there are comparison attributes into which various items of data can be incorporated, such as the compilation result for programs, where the global and local compiler settings are also included.

Categorization of comparison features Comparison features are divided into attributes, aspects, and sub-aspects on the basis of object type (sub-aspects are only available for MCC and LAD/FBD POUs). This enables you to determine the causes of differences as precisely as possible.

Comparison features are available in singular or multiple format (such as OEs) and their content can be empty, e.g. exported variables of a program. The comparison features are displayed in the object comparison, regardless of whether or not they are empty.

You will find an overview of the specific comparison attributes, plus their associated aspects and sub-aspects, for SIMOTION, SINAMICS, and MICROMASTER objects in the section titled Overview of comparison attributes (Page 53).

To enable the attributes to be compared as efficiently as possible, information is calculated (e.g. a checksum) and is then stored online along with the project or objects. If this information is not available (e.g. in the case of the hardware configuration), a statement on the comparison cannot be made (indicated in the comparison tree by ?).

General information on object comparison 2.5 Object attributes


2.5 Object attributes You can select the following object attributes in the two right-hand columns in the object comparison.

Table 2- 3 Overview of object attributes

Name Description Name Name of object1) Type Type of object

Objects with the same name but of a different type are not compared in the case of automatic assignment.

Object address Unique object address1) You need the object address to address the objects via the HMI, for example.

Author Name of the author1) Version external External version identifier1) Version internal Internal version identifier of object, e.g. the technology

package version in the case of TOs Creation version SIMOTION SCOUT version with which the object was created Know-how protection for programs Login for all know-how-protected objects Time stamp of last change Date and time of last change Comment Comment1) 1) from the Object properties dialog.

General information on object comparison 2.5 Object attributes



Functions 33.1 Downloading additional data

In order that can carry out a detailed comparison and, if necessary, a complete data transfer into the PG/PC during an offline/online comparison, when downloading the project to the target device you must also save the additional data, such as sources, icon information etc. This is a setting in SIMOTION SCOUT or STARTER.

If you only want to accept selected data from the additional data, you can do this via the detailed comparison.

Note

It is also possible to load supplementary data when using SIMOTION devices with older firmware versions if you have edited or converted the project with SIMOTION SCOUT V4.1 SP2. The project then has to be recompiled and loaded.

Further information on loading additional data can be found in the basic functions, Loading data from the target device to the PG/PC.

Procedure Proceed as follows:

1. Select Tools > Settings.

The Settings window appears.

2. Switch to the Download tab.

3. Activate Save additional data on the target device and confirm using OK.

The next time the project is downloaded to the target device, the additional data will be saved on the target device. If deactivated, the additional data will be deleted the next time downloading to the target device takes place. In addition, this option can be selected during each download (CPU-related).

Functions 3.2 Starting an object comparison


3.2 Starting an object comparison Object comparisons are only performed using saved data. Changes made after the object comparison was performed may mean that the object comparison and the detail comparison have different results.

You must note the following during an online comparison and a comparison with a different project:

The comparison only uses the saved data in the open project.

During an online comparison, the device being used for comparison purposes is implicitly uploaded. Therefore, the comparison is made with a copy of the online data.

Note

We recommend compiling the project prior to starting the project comparison. This ensures that you obtain a reliable comparison result (e.g. compilation result of a program).

Note

A comparison with online objects is only possible if there is already an online connection.

Note

If you delete a comparison partner and then update the comparison, an error message is displayed.

Note

The object comparison does not display differences of current data (current data values). Only download-relevant parameter differences are displayed.



3.2.1 Starting the object comparison and selecting comparison partners How to start the object comparison:

1. Click on the device with which you want to run the comparison in the project navigator.

2. Either start the object comparison via

– The menu bar, using Options > Compare...,

– Using the button or

– The context menu of the comparable objects (Compare...).

The following dialog appears:

Figure 3-1 Select comparison partner dialog

The object you selected previously in the project navigator is highlighted as comparison partner A. If you did not select an object, the first object in the list is highlighted.



3. Select comparison partner B. The following options are available:

– Object from the open project:

You can choose from the objects in the open project.

– Object from a saved project:

First open a saved project using the button:

You can choose from the objects in this project.

– Object from the target system (online): (only possible in ONLINE mode and if the project is present in the target system).

The object from SCOUT or STARTER is compared with the object on the target system.

Note

Only comparable devices are displayed as comparison partners.

4. The Start comparison button is activated once you have selected the object with which the comparison can be run. Open the object comparison using the Start comparison button.

3.2.2 Different versions detected (offline comparison with saved project)

Note

If you are carrying out a comparison with a different project, the project concerned must be available in SIMOTION SCOUT/STARTER Version 4.2; otherwise, you will have to convert the project first.

If the comparison partner is in a different project created using an older version of SIMOTION SCOUT, a comparison cannot be carried out. The following note is displayed:

Figure 3-2 Different comparison partner versions

In this case, first convert the project to the current version of SIMOTION SCOUT. Then restart the comparison.



3.2.3 Object comparison with projects converted to a higher version

Requirement To be able to perform an object comparison, where projects have been created with SIMOTION SCOUT/STARTER versions < 4.2, you first need to convert these projects to a higher version.

Display of new comparison attributes As part of SIMOTION SCOUT/STARTER version 4.2, new comparison attributes and aspects have been introduced for object comparison purposes. This results in the following scenarios when carrying out comparisons:

● You convert a project to V4.2, go online, and perform a comparison with an object on the target system:

The new comparison attributes are not displayed, as they are not available on the target system.

● You convert two projects to V4.2 and compare these offline:

The new comparison attributes are not displayed.

● You convert two projects to V4.2, compile one of the two projects, and compare these offline:

The new comparison attributes are displayed. However, no comparison is possible because the attributes in the non-compiled project are not available.

Note

The new comparison attributes are calculated when the projects are compiled with SIMOTION SCOUT/STARTER V4.2. When projects are recompiled, the previous comparison attributes are also recalculated.

Display of aspects Aspects are updated when the comparison attribute is opened, making them available for comparison.

Functions 3.3 Assignment of objects in object comparison


3.2.4 Going offline after online comparison (comparison is no longer up to date)

Comparison no longer up-to-date Certain pieces of status information depend on the online connection. If you go offline after performing an online comparison, it means that

● A comparison attribute cannot be expanded (unless it was previously opened)

● A detail comparison can no longer be started

● It is no longer possible for entire objects to be transferred

If you attempt to execute one of the functions, the message Target device is offline is displayed.

Column header display is hatched The hatching of column headers means that the comparison is no longer up-to-date. Update the comparison.

Hatching occurs in the following situations:

● If you have made a change on an open project (comparison partner A).

If a change has been made with a comparison partner B, e.g. with another SCOUT, there is no hatching.

● If you have performed an online comparison and then go offline.

3.3 Assignment of objects in object comparison

3.3.1 Object assignment The object comparison only allows you to compare objects which are sufficiently similar, for example, SIMOTION C240 can be compared with SIMOTION D445-2, but SIMOTION D445-2 cannot be compared with an ST source file. After you have decided which objects are to be compared (see the Starting the object comparison and selecting comparison partners section), the lower-level Simotion SCOUT/STARTER objects will be assigned automatically. The rules described in the next section apply within this context.



3.3.2 Automatic assignment of the subordinate comparison objects During automatic assignment, all objects below the selected comparison object are assigned, taking their position in the tree into account. For example, axis_1 and axis_2 are assigned in the comparison. Similarly, the automatic assignment of lower-level objects will attempt to assign the measuring inputs under axis_1 to the measuring inputs under axis_2.

During a specific object-to-object assignment, a distinction is made between TOs/DOs and other objects:

Assignment of TOs/DOs using object addresses TOs/DOs are assigned using their object address and name. In this case, the object address appears after the name: <Name>(<Object address>). Since the name of the object may differ in this case, both names are shown in the event of deviation.

When assignment uses the object address, it may be, for example,

1. that a measuring input under axis A1 has the same object address as the measuring input under axis A1 in the comparison project, although the object addresses of the axes are different.

Figure 3-3 Example of assignment where axes have different object addresses

2. A measuring input under axis A1 has the same object address as the measuring input under axis A2 in the comparison project:



Figure 3-4 Example of assignment where measuring inputs have different object addresses

Since the object addresses are assigned automatically, this may occur if the objects are created in a different order or using script, for example.

However, this assignment is not desirable as it would result in incorrect object assignment. Therefore, the object address is only taken into account within the same hierarchy level during assignment; not across hierarchy levels.

If necessary, you can change the object addresses of TOs yourself. This allows you to enforce correct assignment of the objects later on.

Note

It is recommended that you explicitly assign the object address for TOs in all cases (see Changing the object address (Page 25)). You cannot change the address of DOs.

Assignment of other objects using names Other objects, i.e. all objects outside the TOs/DOs, are assigned using their names.

Note

If objects are not automatically assigned despite having the same name and are therefore positioned one above the other in the comparison tree, this is because the type is different.

Functions 3.4 Detailed comparison


3.3.3 Changing the object addresses of TOs

Procedure To change a TO object address:

1. Select the appropriate TO in the project navigator.

2. In the context menu, open Properties....

3. Click the Object address tab.

4. Change the object address in the New address field.

5. Click the Assign button and confirm with OK.

3.4 Detailed comparison

3.4.1 Introduction The following section provides you with an overview of which detail comparisons are available and how you can make use of the respective types.

Detail comparison You can compare and partially transfer the content of data in the detail comparison. If differences are detected during an object comparison, you can start a detail comparison for

● ST programs

● LAD/FBD (ladder logic/function block diagram)

● MCC (Motion Control Chart)

● TOs (configuration data, system variables), and



● DOs (parameters).

● Simply structured data:

– I/O variables

– Global device variables

– Alarm configuration

– Execution system

– Compiler settings

– CPU system variables

– Technology object interconnections

– Used technology packages

– HW Config (system interface)

– Cam configuration

– Topology serial numbers

– Message configuration (used symbols/IDs)

Note

If you have compared individual data items, such as the device name, then this is called "scalar" in this context. Differences are then displayed in a dialog box.

Know-how protection for programs In the case of know-how-protected sources, differences are only displayed in the object comparison / detail comparison to a limited extent. Know-how protection for programs protects the source data, but not the attributes or properties. If you want to expand the source code comparison attributes, you will need to enter the password for the protected source. The source code aspects are only displayed when you are logged in.

3.4.2 Starting the detailed comparison

Requirement

The detail comparison can be started from the comparison tree by clicking the button.

You can only start the detailed comparison if

● you have found differences and

● if the additional data required is available for the online comparison.



In the detailed comparison, the corresponding contents are shown next to one another, the differences marked, and the transfer of changes from the comparison object to the reference object made possible if required.

Note

You can only start the detail comparison provided the relevant program of comparison partner A is not already open in an editor. The editor is automatically closed when a detail comparison is started.

The detailed comparison cannot process projects that are opened with write protection. You must first cancel the write protection.

Procedure 1. First, carry out an object comparison on the desired device (see Starting the object

comparison).

2. The Start detail comparison button is shown in the Status column for objects for which a detail comparison can be run.

Figure 3-5 Example of detailed comparison for two ST programs

3. Click the Start detail comparison button. The corresponding editor in the working area will open and the differences will be highlighted and displayed alongside each other.

3.4.3 Introduction: ST, LAD/FBD, MCC detail comparison The following section provides an overview of the function buttons and the menu commands for ST, MCC, and LAD/FBD detail comparisons.



Detail comparison function buttons The following section provides an overview of the function buttons for ST, MCC, and LAD/FBD detail comparisons.

Table 3- 1 Detail comparison function buttons

Button Description

Jump to next difference

Jump to previous difference

Transfer highlighted line(s) to source (from comparison partner B to A)

Complete transfer of differences to the source (from comparison partner B to A)

Detail comparison menu The following section provides an overview of the menu commands for ST, MCC, and LAD/FBD detail comparisons.

Table 3- 2 Detail comparison menu

Menu Description Jump to next difference Jumps to next difference Jump to previous difference Jumps to previous difference Accept current line / Accept current network (LAD/FBD networks only)

Transfers highlighted line(s)/highlighted network to source (from comparison partner B to A)

Accept all differences Transfers all differences (as regards current tab) to the source (from comparison partner B to A)

Display line numbers (ST only) Displays the line numbers of comparison partners A and B Ignore indents (ST only) Indents in the source are ignored; you need to define this

before accepting changes for the first time, as you cannot change the setting for the current comparison after you have done this.

Accept changes into project Changes are accepted in the project and saved Close and open editor Opens comparison partner A in the editor.

The detail comparison closes. Close Closes the detail comparison.



3.4.4 ST detail comparison

3.4.4.1 Introduction The ST detail comparison allows you to run a textual comparison on ST sources. The compared sources are shown next to one another and the differences highlighted in color.

Missing lines (highlighted in gray) are added so that the display of identical lines can be synchronized.

In addition, an overview tab appears in the project navigator. In this case, all lines of the source code are compressed and any differences are highlighted. Simply click on the differences on the overview tab to jump directly to each difference in the source code.

The differences in the source code can be transferred either on a line-by-line basis or simultaneously by marking several lines at once. You have to open the ST editor for editing. You cannot edit in the detail comparison.

Note

Note the information provided in the status bar at the end of the working area.

Note

In isolated cases, a difference may be detected as a result of a control character such as a line break despite the fact that this is of no relevance to the source text.



3.4.4.2 Example: ST detail comparison Example of an ST detail comparison

Figure 3-6 Example of ST detail comparison

Detail comparison overview tab

3.4.5 MCC and LAD/FBD detail comparison of declaration tables

3.4.5.1 Introduction The detail comparison helps you to identify differences between comparison partner A and B in the declarations. This concerns:

● MCC units and LAD/FBD units: Global unit declarations, "INTERFACE" section

● MCC units and LAD/FBD units: Global unit declarations, "IMPLEMENTATION" section

● MCC charts and LAD/FBD programs: POU local declarations



If differences have been detected within a tab during a detail comparison, this tab is underlined in the respective color for both comparison partners and appears in the foreground. If differences have been detected within a number of tabs, all the relevant tabs are underlined in the respective colors.

The reference order for the declarations is provided by comparison partner A. The order for comparison partner B is resorted accordingly, in order to see at a glance whether declarations are missing or the extent to which declarations differ in terms of content. Color highlighting in the column with the line numbering indicates differences in the order.

Note

If the order differs for comparison partners A and B, you can only align them by accepting all the differences.

If there are differences between the declarations for comparison partners A and B, you can correct the differences identified line by line.

Special features of enumerations, structures, and pragmas In future, pragmas will be used to mark the beginning of a new block both in the context of MCC and of LAD/FBD.

When the declarations of the two comparison partners are matched up, variables have to be located below a pragma for both comparison partners in order to be assigned to one another. If there is a pragma for one of the comparison partners, but not for the other one, the appropriate number of empty lines will be inserted for the comparison partner that does not have a pragma. Pragmas are assigned on the basis of names.

Note

If there are matching pragmas, you can accept subordinate variables to suit your specific requirements.

If the comparison partner has no matching assignment for a pragma, you must accept the pragma along with the variable declarations.



3.4.5.2 Example: Detail comparison of declaration tables Example of a detail comparison for declaration tables

Figure 3-7 Example of a detail comparison for declaration tables

3.4.6 MCC detail comparison of charts

3.4.6.1 Introduction The detail comparison is subdivided into the following areas: The upper area, which contains the local variable declarations for the comparison partner, and the lower area, which contains the two charts whose command blocks have been synchronized.

You can navigate between all the differences identified and align individual differences in accordance with your specific requirements.

In addition, an overview tab appears in the project navigator. This displays the differences in compact form. Simply click on the differences on the overview tab to jump directly to each difference in the chart.

Modules In general, it is possible to zoom in on/zoom out from the module in the case of both comparison partner A and comparison partner B.



If two modules have been matched up with one another, the commands within each zoom level are compared with one another (as in the case of a chart without modules).

Note

At every zoom level, you have the option of viewing the differences in terms of command parameterization and accepting individual commands in accordance with your specific requirements.

If there is a module for only one comparison partner or if a module has been assigned to comparison partner A, but not to comparison partner B, although you can zoom in on/zoom out from the module, you can only accept the module in its entirety.

Command blocks In order to analyze and align differences in terms of command block parameterization, you can open the generic detail comparison once a discrepancy has been identified.

Note

You can align differences in terms of parameterization by selecting checkboxes in accordance with your requirements. If a particular parameter cannot be aligned, no checkbox is made available.

3.4.6.2 Examples: MCC detail comparison of charts

Possible differences in the detail comparison The following table provides you with an overview of the possible differences and how they are identified. This is illustrated on the basis of specific examples (see figure below).

Nature of difference Identification Differences in the local variable declarations

Differences are highlighted using the object comparison colors (1).

A command or several related commands are missing for comparison partner A or B

There is a corresponding gap in the chart for comparison partner A or B. Any subsequent elements that are assigned to one another become synchronized again after the difference. As regards the comparison partner, where the relevant command or set of related commands is/are present, this/these are displayed using the object comparison color of orange (2).

Differences in structures In general, only structures of the same type are assigned to one another. Structures of different types are shown staggered. If there is a structure with subordinate commands for one comparison partner but the other comparison partner only features commands with a superordinate structure, the commands are still assigned.



Nature of difference Identification There is a discrepancy between the parameterizations for a command or for several commands of the same type

The command blocks of the same type that are assigned to one another are displayed on one level and are color-coded using the object comparison colors (blue on the left and orange on the right) (3). When you double-click on a command where there is a discrepancy (whether for A or B), a dialog opens showing the parameterization differences, matched up and highlighted in color (see Detail comparison command block)

Differences in commented-out commands

The same rules apply as for commands. You also need to be aware of the following points: If the only difference between two commands that have been assigned to one another is that the command is commented out for one comparison partner but not for the other one, both commands are color-coded using the object comparison colors (blue on the left and orange on the right). Where commented-out commands have been assigned to one another but are subject to differences in parameterization, when you double-click on the command where there is a discrepancy, a dialog opens showing the parameterization differences, matched up and highlighted in color.

Differences in the brief comments

Background highlighted using object comparison colors

Parameterization differences affecting an ST zoom

When you double-click either of the ST zooms, the detail comparison window opens (only if there are parameterization differences).

Parameterization differences affecting a comment block

When you double-click either of the comment blocks, the textual detail comparison window opens (only if there are parameterization differences).

Modules Modules are always matched up for the comparison partners, if the majority of command blocks within the module are of the same command type. If this criterion is not met, the modules for both comparison partners are highlighted in color and shown staggered. If a module is only present for one of the two comparison partners, this is color-coded accordingly. There is a gap in the chart for the comparison partner that does not have this module. In general, it is possible to zoom in on/zoom out from the module in the case of both comparison partner A and comparison partner B. See description below.



Figure 3-8 MCC detail comparison of charts



Detail comparison command block The following example shows the detail comparison of a command block.

Figure 3-9 Detail comparison command block



Detail comparison overview tab On the overview tab, you will find the following information in compact form:

● Differences in the numbers of commands (1)

● Differences in the parameterization of the commands (2)

● Missing elements for A or B (3)

Figure 3-10 MCC detail comparison overview tab

3.4.7 LAD/FBD detail comparison of networks

3.4.7.1 Introduction The detail comparison is subdivided into the following areas: The upper area, which contains the local variable declarations for the comparison partner, and the lower area, which contains the two networks that have been synchronized accordingly.

You can navigate between all the differences identified and align individual differences in accordance with your specific requirements.

In addition, an overview tab appears in the project navigator. This displays the differences between the networks in compact form. Simply click on the differences on the overview tab to jump directly to each difference in the network.



Assignment of networks The networks are matched up on the basis of the comparison result content. Two networks are assigned to each other, if:

● They are 100% identical

● The structure of the two networks is absolutely identical

(i.e. the number and position of blocks/elements are identical, all of these have a matching counterpart in the comparison partner, the connections are the same, the only differences relate to parameterization (different variables or constant values on the same pins) or instantiation (different instance names))

● Or if a relatively large number (for example, more than 50%) of elements can be assigned.

Detail comparison of networks of different types (LAD vs. FBD or FBD vs. LAD) LAD/FBD programs within an LAD/FBD unit are assigned on the basis of names. This makes it possible to assign two LAD/FBD POUs with the same name to one another even though the network type differs. If an LAD POE is assigned to an FBD POU, these POUs are marked as non-identical (i.e. aspect, comments, and formats).

When you open the detail comparison, the differences can only ever be displayed in the same format. An attempt is made to switch POU B to the format used for POU A. If this is not possible, an attempt is made to switch POU A to the format used for POU B.

If the switch is not possible, the following error message is displayed:

"Detail comparison not possible because the two comparison partners have different display formats, and it is not possible to switch to another format."

Note

The automatic switching process described above is only used for display purposes and is not saved automatically.



3.4.7.2 Examples: LAD/FBD detail comparison of networks

Possible differences in the detail comparison The following table provides you with an overview of the possible differences and how they are identified. This is illustrated on the basis of specific examples (see figure below).

Nature of difference Identification Different PINs Differences are highlighted using the comparison partner color. Operations without a matching counterpart in the respective comparison partner

Operations are highlighted using the comparison partner color (1).

Differences in the network comments

Differences are highlighted using the comparison partner color (2).

Network is missing completely for one comparison partner

The network that is present is color-coded (3).

Differences in the variables Differences are highlighted using the comparison partner color (4).

Figure 3-11 LAD/FBD detail comparison of networks



Detail comparison overview tab The overview tab displays the following information in compact form for both LAD and FBD:

● Differences in the number of networks (1)

● Number of different networks (2)

● Missing networks for A or B (3)

● Areas with identical networks (4)

Figure 3-12 Detail comparison of LAD/FBD networks overview tab

3.4.8 Detail comparison of simply structured data

3.4.8.1 Introduction The detail comparison can help you to analyze and align simply structured data, for example, for CPU system variables and TO interconnections.



User interface The following figure shows the structure of the detail comparison.

Figure 3-13 User interface of the detail comparison

Table 3- 3 The user interface elements of the detail comparison

No. Description 1 Comparison partner A and comparison partner B 2 Comparison tree made up of comparison partner elements 3 Filter

The filter can be used to determine whether the entire data volume should be displayed or just the differences. The selection is set by default to Differences only.

4 Result of comparison 5 Data transfer of the selected differences

See note below. 6 Update comparison 7 Print comparison 8 Data transfer of all differences

See note below. 9 Call up online help 10 Checkbox for data transfer (if no transfer is possible, the checkbox is not displayed)

See note below.



Note

Data transfers are not always possible, for example, during TO interconnections or generally for write-protected projects. In this case, checkboxes are not displayed for the transfer

Rules for data transfer ● Checkboxes for the data transfer are only displayed once a difference has occurred. If

there are not any differences on one level, checkboxes are also not displayed on the higher level.

● As a general rule, data is structured in hierarchical order. As such, you can either fully transfer a hierarchy level with subordinate hierarchy levels/objects or just individual subordinate hierarchies/objects.

● Please note the following when changing the transfer selection:

– Activate or deactivate the superordinate level: The checkboxes of the hierarchically subordinate elements assume the same value.

– Activate or deactivate subordinate elements: The checkbox of the subordinate hierarchy level is disabled, as long as activated and deactivated checkboxes are located below the level.

● The Data transfer button (see figure below user interface, No. 5) is only activated once at least one checkbox has been activated for the transfer.

● The data transfer is only activated by clicking the Data transfer button.

– If you only wish to transfer the selected differences, click on the Data transfer button in the column header (see figure below user interface, No. 5).

– If you wish to transfer all differences, click on the Data transfer button on the toolbar (see figure below user interface, No. 8).

Note

In certain cases, a difference may still be displayed following successful transfer, for example, different CPUs may have a different number of MotionTasks.

Data transfer failure Errors may occur during the data transfer. For example, the transfer of a non-existent A1 IO variable may fail if an A1 global device variable already exists. If the transfer fails, the following message is output: Errors occurred during data transfer!.

The comparison is updated following the transfer. In the case of transfer failure, the differences continue to be displayed.



3.4.8.2 Examples: Detail comparison of simply structured data The following section shows an example of a detail comparison of the HW Config system interface and global device variables.

HW Config (system interface)

Figure 3-14 Detail comparison of HW Config system interface



Global device variables

Figure 3-15 Detail comparison of global device variables



3.4.9 TO/DO detailed comparison

3.4.9.1 Differences between TO/DO detailed comparison and experts list comparison The differences between the TO/DO detailed comparison and expert list comparison are summarized in the table below.

Table 3- 4 Comparison of detailed comparison and Expert list comparison

Feature Detailed comparison Expert list comparison Number of comparison objects 1 1 ... n Origin of comparison objects Objects from different projects Objects from the open project only Values to be compared1) Configured values; actual values are

not included in the comparison Actual values

Indication of differences (structural differences)

Full indication of all parameters (DOs) or system variables and configuration data (TOs), regardless of whether they occur in comparison partner A, B, or both.

Only the parameters and system variables and configuration data of comparison partner A are displayed. Therefore, you only see whether or not the parameters contained in the reference object are present in the comparison objects. Parameters that only the comparison objects contain (not the reference object) are not checked.

Access to online values Always possible Only if the structure is consistent with the offline object

Options for changing data in the comparison objects2)

Change to data in comparison partner A (reference object) only during offline comparison Note: You can use the context menu for the table cells of comparison partner B to transfer the value from B to A.

Change to data in all objects shown in the comparison

Topicality of online data Snapshot from execution time of object comparison

Snapshot from execution time of expert list comparison

1) Differences between configured values and actual values are only of any consequence if the comparison partner is an online TO. Offline, parameters only ever have one (configured) value. There is only one value for online objects of DOs, and the following applies: actual value = configured value. 2) Fields hatched out in the detailed comparison cannot be edited.



3.4.9.2 TO detailed comparison Example of a TO detailed comparison:

Example of a TO detailed comparison

Note

For more detailed information, refer to the section titled Differences between TO/DO detail comparison and expert list comparison and, in the basic functions, Comparing expert lists.



3.4.9.3 DO detail comparison Example of a DO detailed comparison:

Figure 3-16 Example of a DO detailed comparison

Note

For more detailed information, refer to the sections titled Differences between TO/DO detail comparison and expert list comparison and Comparison - Expert list.



Display filter for DO detail comparison The display filter for the DO detail comparison is the same as for the expert list, with the following exception:

Figure 3-17 Display filter for DO detail comparison

The Only download parameters setting on the Parameter filter tab is always activated and cannot be changed. This ensures the detail comparison only includes parameters involved with the download. These are those parameters whose values will actually be loaded into the target device for a download from the PG. In contrast, adjustable parameters can only be changed online.

Note

For more information, refer to Display filter - Expert list.

Functions 3.5 Data transfer


3.5 Data transfer

3.5.1 Function You can use the Data transfer function in the object comparison to transfer the data of the comparison object (B) to the open project (A). You can transfer individual data items from the detailed comparison. You can run a complete online calibration from B to A using the function Download into PG/PC or from A to B using Download to target device.

Note

In the event of errors when downloading to the PG, note the information in the detailed view on the Object comparison tab.

Note

You have to save in order to achieve online consistency after the data transfer of TOs. Programs are compiled after the data transfer, whereby these can become implicitly consistent.

3.5.2 Rules for data transfer

General rules for data transfer The following rules apply to transfer procedures:

● A transfer is only possible from B to A.

● When you transfer an object, the content is transferred in full (including compiler settings, for example) and overwrites the data in the reference object. In other words, any changes that you made in the reference project may be lost.

● If the comparison partner is in the target system, the corresponding supplementary data must be downloaded. If this is not the case, the transfer cannot be performed.

● DOs cannot be transferred.

● A TO/program can be transferred to an existing TO/program. However, TOs/programs cannot be created in cases where there is no TO in A, but there is one in B, for example.

● TOs/DOs cannot be deleted by transferring them, e.g. if there is a TO/DO in A, but not in B.

● When entire objects are transferred, the object address is also transferred (see Duplicate assignment of an object address (Page 52)).



● If an object cannot be transferred because it is not present in the open project, you can create an empty object with the same object address and same name (for TOs) or with the same name (for programs) and then repeat the data transfer. TOs or a program entry in the execution system then still need to be linked manually.

● If you only wish to transfer individual pieces of data from an object, rather than an entire object, it is only possible to do this in the detail comparison. Here, you can transfer one particular change to an ST program, for example (see Detailed comparison (Page 25)).

Data transfer of POUs MCC and LAD/FBD POUs are dynamic aspects that you can accept in the object comparison. All the other dynamic aspects can only be accepted in the specific detail comparisons.

Rules for transferring dynamic aspects:

● When dynamic aspects are transferred, the data is transferred in its entirety, including for example the properties (creation type, author, comment, etc.).

● If a POU is only present for B, this POU is created for A during transfer.

● If a POU is only present for A, this POU is deleted for A during transfer.

● If the comparison partner is in the target system, the corresponding information must be available online (see General rules for data transfer).

● If the source containing the POU is know-how protected (for A and/or B), then special rules apply (see Data transfer with know-how protected projects).

Data transfer for write-protected projects If projects have been created in older SCOUT versions, you can open them as write-protected projects following an upgrade. The write-protected project allows you to perform an object comparison or detail comparison, but no data transfer is possible.

Data transfer with know-how protected projects You can transfer know-how protected objects. You must be logged in to ensure that aspects are displayed and that you are able to transfer individual POUs.



3.5.3 Procedure for data transfer To transfer data, proceed as follows:

1. Place a check mark in the check box (see diagram below) for the object you want to transfer.

Figure 3-18 Selection and transfer of objects

2. Start the transfer by clicking the Data transfer button, and confirm the dialog that follows with OK.

Figure 3-19 Data transfer dialog

3. Once the data have been transferred successfully, the check box is replaced with a check mark. The result of the comparison in the object comparison is then no longer up to date. This is indicated in the status bar at the end of the view.

You can, however, perform addition detail comparisons and data transfers without updating the comparison.



Figure 3-20 View following transfer

3.5.4 Duplicate assignment of an object address When transferring entire objects, the object address is also transferred. Since the object address in the address area of a SIMOTION device must be unique, address conflicts may arise. Transfers which would result in duplicate assignment are not carried out. The object affected by the address conflict is entered in the log in the detailed view.

If necessary, change the object address (see the chapter titled Changing the object address (Page 25)).


Overview of comparison attributes 4

Below you will find an overview of the comparison attributes, along with their associated aspects/sub-aspects, for SIMOTION, SINAMICS, and MICROMASTER objects.

The comparison attributes are made up of several comparison features. There are various reasons for differences in comparison attributes. A difference in the compilation result may result from program changes (source code), for example, and/or a change to the compiler settings. The tables below describe the comparison attributes for the individual object types. These should help you to quickly establish the causes of a difference if a detailed comparison is not available.

We recommend the following procedure for efficiently finding the reason for a difference to a comparison attribute:

● If necessary, compile projects (A + B) if the compilation results are no longer up-to-date

● Start detailed comparison, if available

● Search for description of comparison attribute in the object table

● Check comparison features

Note

In conjunction with the detailed comparison, the term "scalar" means that only a single data item, such as the device name, is compared. Differences are then displayed in a dialog box.

Note

Please note that no current parameter values are compared during an online/offline comparison. Only parameter differences which are relevant to the download are displayed.

Overview of comparison attributes 4.1 SIMOTION objects


4.1 SIMOTION objects

4.1.1 SIMOTION device

Table 4- 1 Comparison attributes of a SIMOTION device

Comparison attributes of a SIMOTION device

Aspects/Sub-aspects Detail comparison/Scalar

Execution system The configuration of the execution system: • The assignment of programs to the tasks • Configuration of tasks in the Task configuration tab. • System cycle settings using the Set system cycles... function (Servo,

Ipo, Ipo_2, TControl) Note: Compile the project prior to starting the project comparison. In this way, you will obtain a meaningful comparison result.

Execution system

Execution system - compilation result

The part which results from the project's compilation process. The compilation result includes: • The configuration of the execution system (see above) • The technology packages used

No detail comparison

Selected technology packages

The technology packages selected in SCOUT with associated version. Used technology packages

Address list of I/O variables

• Configuration of I/O variables Note: Structural changes to the I/O variables are also included in the HMI-relevant data comparison attribute.

Address list of I/O variables

Global device variables • Configuration of global device variables Note: Structural changes to the global device variables are also included in the HMI-relevant data comparison attribute.

Global device variables





HW Config (time stamp-comparison)

Comparison of the hardware configuration is based solely on a time-stamp comparison. The time stamp of the most recent change is used. If a comparison is carried out on this basis, a statement on the equivalence is only possible when the time stamp is the same. If the time stamp is different, the hardware configuration may be the same or different. This will be the case if the most recent change has been undone, for example. STEP7 SIMATIC Manager offers a block comparison for such cases. Offline comparison The comparison is carried out as described above. Online comparison (devices which have been downloaded with a SCOUT/STARTER version <= V4.1 SP2) The comparison result is always uncertain (=?) because the time stamp is not available online. The statement is that the hardware configuration is not included in the comparison. Displaying this attribute prevents the SIMOTION device from being displayed as inconsistent in the project navigator; however, everything is the same in the object comparison (the only difference is in HW Config).


HW Config (system integration)

The data from the hardware configuration which is included in the SIMOTION configuration: • I/O addressing (in HW Config) • DP cycle (bus cycle) • Equidistant bus cycle

Devices loaded with a SCOUT/STARTER version <= V4.0: Comparison attribute is only available offline.

HW Config (system interface)


• Device name Scalar

• Device address

Required for distributed synchronous operation; see Object properties (Object address tab)

Scalar

• Device type Scalar

• Behavior of dynamic data during STOP/RUN transition Scalar

• Fixed process image Scalar

• Time-of-day synchronization Scalar

• Fast I/O configuration (onboard I/Os, TM15/TM17 High Feature) 1) No detail comparison

Device settings

Devices loaded with a SCOUT/STARTER version <= V4.0: This comparison attribute is not available.

System variables • Configuration of system variables in the SIMOTION device Detail comparison, CPU system variables





TO interconnections • Interconnections of TOs on the device Detail comparison, technology object interconnections

HMI-relevant data Records the structural setup (data type of variables, number of variables) of the data which an HMI system can access. If the setup changes, the HMI configuration must be updated. • Structure information of I/O variables • Structure information of global device variables


For every library used: Compilation result <Libname>

• Compilation result of the specific device version

This comparison attribute is only shown if a library is used. A library comparison can be carried out for a detailed comparison.


1) Refers to the appropriate message frame of the fast I/O configuration. A difference is due to a discrepancy in terms of the fast I/O configuration (see drive units), or the failure to carry out HW Config alignment.

4.1.2 Technology object (TO)

Table 4- 2 Comparison attributes of a technology object

Comparison attributes of a technology object (TO)


Contains the configuration of a technology object. No detail comparison

• Configuration setting

For example, linear/rotary axis; technology object activated/deactivated

Scalar

• Object state

Values: Activated/deactivated

Scalar

• Configuration data (see Comparing expert lists)

Records the values and units

Detail comparison, expert list

• Configuration data structure

Records the data volume, for example the number of data sets or encoders


Configuration

• Units (Indirect influence of unit configuration1))

Detail comparison, unit configuration

System variables • The system variables of the TO

Records the values and units

(Indirect influence of unit configuration and configuration settings1))




Comparison attributes of a technology object (TO)


Alarm configuration • Configuration of TO alarms (see TechnologicalFaultTask) Detail comparison, alarm configuration

Records the structural setup (data type of variables, number of variables) of the data which an HMI system can access. If the setup changes, the HMI configuration must be updated. Data included:


• The configuration data Detail comparison, expert list

• The object address (see TO properties) Scalar

HMI-relevant data

Indirect influence of unit configuration and configuration settings1) Configuration data For TO cam only!

Configuration data of cam disc (e.g. support points, interpolation, scaling)

Detail comparison, configuration data

1) The unit and value of a technological parameter are always viewed separately (i.e. not the resultant parameter). This means: If a unit configuration is changed, the configuration data and system variables will be different to the original setting, even if the values in the new unit have been converted and the resultant variable is the same. A linear axis/pressure uses different physical variables to a linear axis/force; even if the numerical values are the same, these different variables will result in a difference. Not applicable to cams.

Note

Modified data is only considered in the comparison once Copy current data to RAM has been performed.

4.1.3 Source The following overview applies to ST, LAD, FBD, and MCC.

Table 4- 3 Comparison attributes of a source

Comparison attributes of a source


Source text (based on ASCII) Detail comparison

• Execution-relevant source code

Everything apart from comments and formats such as spaces, empty lines


Source code (ST)

• Comments and formats No detail comparison





Source text (based on ASCII) No detail comparison

• INTERFACE (exported declaration)

Declarations and connections (the detail comparison shows the first interface difference)

Detail comparison unit 1)

• IMPLEMENTATION (source-internal declaration)

Declarations and connections (the detail comparison shows the first difference in implementation)


• Comment language Scalar

• Comments

Only displayed if the comment language has the same value (the detail comparison shows the first comment difference)


• POU (n times, n>= 0) No detail comparison

Declarations Detail comparison Execution-relevant source code Detail comparison Formats Only displayed if the comment language is not the same

Source code (MCC/LAD/FBD)

Comments and formats Only displayed if the comment language is the same Examples of formatting: spaces, empty lines, network or block numbers

Detail comparison

• Compiler options

Corresponds to: Properties tab, Compiler and Additional settings

Detail comparison for local options incl. processor settings

Properties 2)

• Object address Scalar

Effective compiler options

Corresponds to: Properties tab, Compilation Detail comparison

The compilation result for a source includes:

• The source text of relevance to execution, i.e. everything apart from comments and formats


• The compiler settings (local and global)

• The compiler version (e.g. compilation with new SCOUT)

Compilation result

• External references – Interfaces of other sources used – Interfaces of libraries used – Global device variables used – I/O variables used – TOs used – Tasks used in the task control commands






• Message configuration (used symbols/IDs)

If a different number has been assigned to an alarmS configuration icon, and this icon has been used in this program, then the source code is the same in both cases but the compilation result is different. If you need to work out online which number has been used for an icon, you upload a device into an empty project. Here, you can look in the message configuration (the icons and the assigned numbers are entered in this during the upload).

Detail comparison

• Data structure of retain data No detail comparison

• Data structure of non-retain data No detail comparison

• Exported interface (effective)

Exported data and data types used 3)

Exported POUs


Records the structural setup (data type of variables, number of variables) of the data which an HMI system can access. If the setup changes, the HMI configuration must be updated. Data included:


Offline comparison • VAR_GLOBAL variables of the source

For ST: Detail comparison, Var block displayed Otherwise: Detail comparison unit

• The object address (see source properties) Scalar

HMI-relevant data

Online comparison Currently, the comparison attribute does not produce a meaningful result.

1) First difference is displayed 2) Not relevant for online consistency 3) "Data types used" means that they are used in the exported global variables or in the exported POUs. Constants plus default and initialization values are not taken into account.



4.1.4 DCC chart

Table 4- 4 Comparison attributes of a DCC chart

Comparison attributes of a DCC chart

Aspects/Sub-aspects

Source code Time stamp-comparison

Offline only • Changes in the DCC editor based on a time stamp (most recent change).

If values are changed in online mode, the changes and, therefore, the time stamp are detected offline.

Note: The comparison is based on a time-stamp comparison only. The time stamp of the most recent change is used. If a comparison is carried out on this basis, a statement on the equivalence is only possible when the time stamp is the same. If the time stamp is different, the source code may be the same or different (e.g. if the most recent change was reversed). In such cases, it is not possible to make any statements regarding this in the object comparison. This is shown by a ?.

Blocks Block instances and their properties, such as • Type • Name • Address • Constant values (initial values) of inputs and outputs • Assignment to runtime group • Change the predecessor of the execution group by inserting or deleting execution

groups • Change to the run sequence




Aspects/Sub-aspects

Interconnections The comparison attribute for interconnections indicates differences in terms of chart interconnections. This includes: • Interconnections of all the inputs within the chart • Interconnection/assignment of @ parameters to inputs and outputs • Simotion: Interconnections with runtime groups • Simotion: Interconnections with operands (TOs/sources, global device variables, IO) • External references for the chart (referenced operands, DCB and DCC libraries used) Notes: When interconnecting a chart's output with another chart's input, the interconnection is always incorporated in the chart's comparison attribute along with the input. If you have defined a Bico @ parameter for an input with Sinamics while making another interconnection at the same time, the interconnection will be executed as a Bico interconnection and, as such, will be incorporated in the "@ parameters and external references" attribute rather than the "interconnections" attribute. Interconnections with operands are only incorporated in the interconnections attribute with Simotion. With Sinamics, all interconnections with operands are executed as Bico interconnections and, as such, contained within the "@ parameters and external references" attribute. By incorporating the external references, the names and versions of the DCB and DCC libraries used are also incorporated in the interconnections attribute.

Runtime groups Chart runtime groups and their properties • Name • Task assignment (only applies to SIMOTION): • Predecessor execution group • Initial state of runtime group (active/inactive)




Aspects/Sub-aspects

@ parameters and external references

SIMOTION: • Published parameters • Compiler settings • External references

– Interfaces of referenced sources (programs: ST, MCC, LAD/FBD) – Reference parameters of other DCC charts – Interfaces of DCC libraries used – Global device variables used – I/O variables used – TO system variables used

SINAMICS: • Parameter values of the @ parameters (p parameters: Values of the adjustable

parameters and BICO interconnections on BICO sinks) • Adjustable parameter for DCC (p21000[0 to 9])

HMI-relevant data Records the structural setup (data type of variables, number of variables) of the data which an HMI system can access. If the setup changes, the HMI configuration must be updated. Data included: SIMOTION: Offline/offline comparison: • Data that can be addressed by the HMI • The object address (see chart properties) Offline/online comparison <= device version V4.1.2: No aspects Offline/online comparison with device versions as of V4.2: • Data that can be addressed by the HMI • The object address (see chart properties) SINAMICS: • Not relevant

Note

No detail comparison is available for the comparison features of the DCC charts!



Note

If a published connection is changed in offline mode, the Online/Offline Comparison window is not opened when the online mode is opened.

The difference between the target device and the project in the DCC chart can only be seen at Target system output and in the project navigator.

If a connection that has not been published is changed in offline mode, the Online/Offline Comparison window is opened when the online mode is opened.

4.1.5 Library

Table 4- 5 Comparison attributes of a library

Comparison attributes of a library



Corresponds to: Properties tab, Compiler

Detail comparison for local options

Properties

• Used technology packages <device type>

See compilation result, dynamic aspect

Detail comparison, used technology packages

Effective compiler options

Corresponds to: Properties tab, Compilation Detail comparison

Compilation result <Device type> Compilation result

Depending on the setting in the properties dialog (TPs/TOs), the compilation result is shown for each device type or as unrelated to the device type. The following data is included in the comparison: • The source code of relevance to execution, i.e. everything apart from

comments and formats • The compiler settings • The compiler version (e.g. compilation with new SCOUT) • External references (sources, libraries, TPs, TOs, I/Os, global device

variables, tasks) • As with the compilation result <Device type> Compilation result unrelated to device type




4.1.6 Source in a library

Table 4- 6 Comparison attributes of a source in a library

Comparison attributes of a source in a library


Source text (based on ASCII) Detail comparison

• Execution-relevant source code

Everything apart from comments and formats such as spaces, empty lines

No detail comparison Source code (ST)

• Comments and formats No detail comparison

Source text (based on ASCII) No detail comparison

• INTERFACE (exported declaration)

Declarations and connections (the detail comparison shows the first interface difference)


• IMPLEMENTATION (source-internal declaration)

Declarations and connections (the detail comparison shows the first difference in implementation)


• Comment language Scalar

• Comments

Only displayed if the comment language has the same value (the detail comparison shows the first comment difference)


• POU (n times, n>= 0) No detail comparison

Declarations Detail comparison Execution-relevant source code Detail comparison Formats Only displayed if the comment language is not the same

Source code (MCC/LAD/FBD)

Comments and formats Only displayed if the comment language is the same Examples of formatting: spaces, empty lines, network or block numbers

Detail comparison


Corresponds to: Properties tab, Compiler and Additional settings

Detail comparison for local options incl. processor settings

Properties 2)

• Object address Scalar



4.1.7 DCC chart in a library

Table 4- 7 Comparison attributes of a source in a DCC library

Comparison attributes of a DCC library

Aspects/Sub-aspects

Source code (time stamp comparison)

Offline only • Changes in the DCC editor based on a time stamp (most recent change).

If values are changed in online mode, the changes and, therefore, the time stamp are detected offline.

Note: The comparison is based on a time stamp comparison only. The time stamp of the most recent change is used. If a comparison is carried out on this basis, no statement can be made concerning whether the source code is the same unless the time stamp is the same. If the time stamp is different, the source code may be the same or different (e.g. if the most recent change was reversed). In such cases, it is not possible to make any statements regarding this in the object comparison. This is shown by a ?.

Blocks Block instances and their properties, such as • Type • Name • Address • Constant values (initial values) of inputs and outputs • Assignment to runtime group • Predecessor in runtime group

Interconnections The following interconnections are included in the comparison: • Chart interconnections • Interconnection of all the chart's inputs • Interconnections with runtime groups • Interconnections with @ parameters • Interconnections with non-DCC objects within SIMOTION

(TOs/sources, global device variables, I/Os)

Runtime groups Chart runtime groups and their properties • Name • Task assignment • Predecessor execution group • Initial state of runtime group (active/inactive)

Note

No detail comparison is available for the comparison features of the DCC charts in a library!

Overview of comparison attributes 4.2 SINAMICS objects


4.2 SINAMICS objects

4.2.1 Drive unit

Table 4- 8 Comparison attributes of a drive unit

Comparison attributes of a drive unit


Reference topology • The reference topology

With this comparison attribute, the serial number is not taken into account in the comparison.

No detail comparison (see note below)

Topology (with serial number)

• Reference topology

With this comparison attribute, the serial number is taken into account in the comparison.

Detail comparison, reference topology serial number

Note

If differences in the reference topology emerge during an online/offline comparison, you can use the topology editor to run a comparison. Please ensure the reference topology is selected for both comparison partners.

4.2.2 Drive object (DO)

Table 4- 9 Comparison attributes of a DO

Comparison attributes of a drive object (DO)


Function modules • Function modules (see Parameter r108 in the DO expert list or the properties dialog box of the DO)


Structure parameters • Parameters that determine the structure, e.g. r51 (drive data set DDS effective). These parameters are indexed, i.e. they form enums and bit arrays (arrays of a different dimension), in order to offer several selection options/settings or display values for a parameter. These parameters are identified in the expert list by a "+".


Overview of comparison attributes 4.3 MICROMASTER and SINAMICS G120 objects


Comparison attributes of a drive object (DO)


Download parameters • Download parameters (see DO Expert list). These are the parameters whose values will be downloaded to the device.


Units • Units

Values: Name of the unit system, e.g. "SI unit system"

This comparison feature does not determine the structure.

Scalar

4.2.3 DCC chart Description of comparison attributes: See DCC chart (Page 60) in the chapter titled "SlMOTION objects"

4.3 MICROMASTER and SINAMICS G120 objects

4.3.1 Drive unit There are no comparison attributes for these drive units.

4.3.2 Drive object (DO)

Table 4- 10 Drive object comparison attributes (DO)

Comparison attributes Aspects/Sub-aspects Detail comparison/Scalar

Device version • Power unit/infeed

(configuration vector specifies the device version of a device type) (Only available with G120, not MM4 or Combimaster)

No detail comparison (see note below)

•

Download parameters • Download parameters (see Comparing experts lists) Detail comparison, expert list

Units Device version as of V4.4: Values: Name of the unit system, e.g. "SI unit system"

Scalar

Overview of comparison attributes 4.3 MICROMASTER and SINAMICS G120 objects


Note

If you use the settings on the Workbench tab to activate the option Display Online/offline comparison for the connection, a comparison will be displayed when you go online. This is not the same as a project comparison.


Appendix A AA.1 Frequently Asked Questions (FAQs)

Note

As a general rule, the project comparison can only be performed based on saved data. For this reason, data is automatically saved prior to performing the comparison.

We recommend compiling the project prior to starting the project comparison.

Differences are detected in the project comparison, yet the detail comparison does not display any differences.

Possible causes:

● The project compilation is not up-to-date.

● The project comparison is no longer up-to-date, changes have been made to the project following the start of the project comparison (such as transfers in the detail comparison) which directly affect the detail comparison.

● Parts of the project were created with a SCOUT version earlier than 4.0 and therefore can no longer be changed (I/O variables). In this case, the hash codes required for the project comparison have not yet been calculated correctly.

In the online/offline comparison, a question mark is always displayed next to the HW Config system interface.

For the online/offline comparison, only SIMOTION data is downloaded to the offline PG project, in the same way as uploading the PG. As a result, only this data in particular can be used for the comparison. This is the reason why no statements can be made with regard to differences/similarities.

The DCC source code time-stamp comparison displays a question mark.

In the case of DCCs, comparison results can only be calculated correctly if the chart compilations are up-to-date.

This applies to both the online/offline comparison (if necessary, update the offline project compilation) and the offline/offline comparison (both project compilations must be up-to-date here).

Following transfer to the online/offline comparison, the object in question is still inconsistently online.

Possible causes:

Following the transfer, the project must be saved to ensure that it is consistently online.

Appendix A A.1 Frequently Asked Questions (FAQs)


When transferring individual programs, global settings such as compiler settings are not applied. The compilation result is therefore not always consistent. In this case, consistency can only be achieved by means of a download.

The configuration data of an axis has been changed by the system, yet the project comparison still does not display any differences.

Possible causes:

The project comparison compares only configured values (offline and online). Modifications to configuration data initially only change current data, i.e. configured data remains unchanged. To be able to compare the adapted data with the project comparison, you must firstly perform Copy current data to RAM.

The online/offline comparison displays differences, yet there are no buttons available for the detail comparison.

Possible causes:

It is likely that no supplementary data is available in the target system.

Program differences are highlighted in the online/offline comparison, but the source text folder can no longer be opened in the overview.

● If no supplementary data has been downloaded to the target system, statements cannot be made regarding the program details. The folder can therefore not be opened

● If the programs in the target system are know-how protected, details can only be displayed once the password has been entered.

There are program differences in the online/offline comparison, so why is there no data transfer button?

Possible causes:

● If there are no differences in source code, then there is no transfer button.

● If there is no supplementary data, then no transfer button is available.

In the detail comparison (online/offline comparison) for the execution system, no values are displayed for the cycles, only a question mark is displayed.

The cycle settings, which are displayed in the detail comparison of the execution system, are only partially based on SCOUT settings. Under the basic cycle clock, for example, the settings made in the HW Config are displayed. Due to the fact that HW Config cannot be used in the online comparison, it is not possible to upload HW Config via SCOUT and, as a result, no statements can be made regarding differences/similarities.

Unknown values are displayed in the detail comparison (online-offline comparison ) for the execution system

This can be TCMRM_MeasureSyncFuncs and TCMRM_BlockSyncFuncs, for example. These values show the internal representation of the configuration.

The displayed differences describe the existing differences in the configuration. The following applies:



● TCMRM_MeasureSyncFuncs = leave time monitoring active

● TCMRM_BlockSyncFuncs = discontinue time monitoring and interrupt the task

At the time of configuration, these values are indirectly set via the drop-down list box in the execution system of the IPO/ServoSynchronousTasks at "Monitoring during the execution of synchronous functions".

In the programs, a difference is displayed in the source text, yet the comparison of all POUs does not show any differences.

The project comparison enables fast comparison of online and offline projects based on hash calculations. In the case of detail comparisons, the original data is then applied.

Occasionally (such as following an upload), this may result in the calculated hash values no longer corresponding.

Save and compile the project and then perform a download.

The comparison tool displays numerous question marks.

To correctly display the comparison values, the projects to be compared must both be converted to SCOUT version 4.2 and preferably also compiled using this version. If necessary, also open the comparison project and re-compile it.

Objects are recreated during the import.

The project that has been exported and then imported again is subsequently no longer the same as the original project because the objects are recreated during the import. For example, the FastIO displays differences in the comparison.

Online-offline comparison refers to the device

The online-offline comparison always only refers to one device Therefore, cross-device TO interconnections are always displayed as non-existent online.

Converting DCC libraries

As of Version 4.3 it is possible to easily convert DCC libraries from SIMOTION libraries to SINAMICS libraries and vice versa. Complex conversion mechanisms are used in both directions. Therefore, a library that is copied back to the original location in this way is not identical to the original library.


Index

A Aspects, 14

C Comparison attributes

Execution-related data, 14 MICROMASTER and SINAMICS G120 objects, 68 Object comparison, 53 SIMOTION DCC chart, 62 SIMOTION DCC chart in library, 65 SIMOTION library, 63 SIMOTION source, 59 SIMOTION source in library, 64 SIMOTION technology object, 57 SINAMICS DCC chart, 67 SINAMICS drive object (DO), 67 SINAMICS drive unit, 66

Comparison tree Updating, 13

D Data transfer

Object comparison, 49 Detail comparison

ST detail comparison, 29 Starting, 26

Detailed comparison DO detailed comparison, 47 TO detailed comparison, 46 TO/DO detailed comparison, 45

M MICROMASTER objects

Comparison attributes, 68

O Object address

Changing, 25 Object comparison, 15, 25

Technology objects, drive objects, 15 Object comparison

Additional data, 17 Automatic assignment of objects, 23 Changing object address, 25 Comparison attributes, 53 Comparison tree, 13 Starting, 19 Structure, 9 User interface elements, 10

P Project comparison

Overview, 7 Project comparison inconsistencies

Project navigator, 7

R References, 3 Result of comparison

Object comparison icons, 12 Same/different, 9 Status in object comparison, 9

S Scalar, 25 SIMOTION DCC chart

Comparison attributes, 62 SIMOTION DCC chart in library

Comparison attributes, 65 SIMOTION library

Comparison attributes, 63 SIMOTION source

Comparison attributes, 59 SIMOTION source in library

Comparison attributes, 64 SIMOTION technology object

Comparison attributes, 57 SINAMICS DCC chart

Comparison attributes, 67 SINAMICS drive object (DO)

Comparison attributes, 67 SINAMICS drive unit

Comparison attributes, 66

Index


SINAMICS G120 objects Comparison attributes, 68

Sub-aspects LAD/FBD POUs, MCC, 14

simotion 3 - siemens · simotion documentation an overview of the simotion documentation can be...

Documents