project comparison

8/6/2019 Project Comparison

1/46

Edition 08/2008

SIMOTION

Project comparison

Function Manual

s

Preface, Contents

Overview of project comparison1

General information about object comparison2

Functions3

Overview of comparison attributes4

Index
http://-/?-http://-/?-http://-/?-http://-/?-


2/46

Copyright Siemens AG 2008 All Rights Reserved

The reproduction, transmission or use of this document or its contentsis not permitted without express written authority. Violation of this rulecan lead to claims for damage compensation. All rights reserved, es-pecially for granting patents or for GM registration.

Siemens AGAutomation & DrivesMotion Control SystemsPO Box 3180, D-91050 ErlangenGermany

Disclaimer of liability

We have checked that the contents of this document correspond tothe hardware and software described. Since variance cannot be pre-cluded entirely, we cannot guarantee full consistency. The data in thisdocument is regularly checked and the necessary corrections are in-cluded in subsequent editions.

Siemens AG 2008Subject to change without prior notice

Safety Guidelines

This manual contains notices you have to observe in order to ensure your personal safety, as well as to

prevent damage to property. Notices referring to your personal safety are highlighted in the manual by a

safety alert symbol; notices referring to property damage only have no safety alert symbol. The notes

shown below are graded according to the level of danger in downward sequence:

If more than one level of danger exists, the warning notice for the highest level of danger is used. A warn-

ing with a warning triangle indicating possible injury to personnel may also include a warning relating to

property damage.

Qualified personnel

The device/system may only be set up and used in conjunction with this documentation. Commissioning

and operation of a device/system may only be performed by qualified personnel. Within the context ofthe safety notes in this documentation qualified persons are defined as persons who are authorized to

commission, ground and label devices, systems and circuits in accordance with established safety prac-

tices and standards.

Intended purpose

Please note the following:

Trademarks

All names identified by are registered trademarks of the Siemens AG. The remaining trademarks in this

publication may be trademarks whose use by third parties for their own purposes could violate the rights

of the owner.

Danger

indicates that death or serious injury will result if proper precautions are not taken.

Warning

indicates that death or serious injury may result if proper precautions are not taken.

Caution

with a safety alert symbol, indicates that minor personal injury may result if proper precautions are not

taken.

Caution

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

taken.

Notice

indicates that an unintended result or situation may occur if the corresponding information is not taken into

account.

Warning

This device may only be used for the applications described in the catalog or the technical description and

only in conjunction with devices or components from other manufacturers which have been approved or

recommended by Siemens.

Correct transport, storage, installation and assembly, as well as careful operation and maintenance, are

required to ensure that the product operates safely and without faults.

Siemens Aktiengesellschaft SIMOTION Project comparison


3/46

Preface-3 Siemens AG 2008 All Rights ReservedSIMOTION Project comparison, Edition 08/2008

Preface

This document is part of the SIMOTION System and Function Descriptionsdocumentation package.

SIMOTION Documentation

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

This document is supplied in electronic format with SIMOTION SCOUT.The SIMOTION documentation consists of 9 documentation packages containingapproximately 75 SIMOTION documents and documents on related systems (e.g.SINAMICS).

The following documentation packages are available for SIMOTION V4.1 SP2:

SIMOTION Engineering System

SIMOTION System and Function Descriptions

SIMOTION Diagnostics

SIMOTION Programming

SIMOTION Programming - References

SIMOTION C

SIMOTION P350

SIMOTION D4xx

SIMOTION Supplementary Documentation

Hotline and Internet addresses

Technical support

If you have any technical questions, please contact our hotline:

Europe / Africa

Phone +49 (0) 180 5050 222 (subject to charge)

Fax +49 (0) 180 5050 223

Internet http://www.siemens.de/automation/support-request
http://www.siemens.de/automation/support-requesthttp://www.siemens.de/automation/support-request


4/46

Preface


Questions about this documentation

If you have any questions (suggestions, corrections) regarding this documenta-tion, please fax or e-mail us at:

Siemens Internet address

The latest information about SIMOTION products, product support, and FAQscan be found on the Internet at

Americas

Phone +1 423 262 2522

Fax +1 423 262 2200

E-mail [email protected]

Asia / Pacific

Phone +86 1064 719 990

Fax +86 1064 747 474

E-mail [email protected]

Note:

Country-specific telephone numbers for technical support are provided under thefollowing Internet address:

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

Calls are subject to charge (e.g. 0.14 /min on the German landline network). Tar-iffs of other phone companies may differ.

Fax: +49 9131 / 98 - 63315

E-mail: mailto: [email protected]

General information:

http://www.siemens.de/simotion (German)

http://www.siemens.com/simotion (International)

Product support:

http://support.automation.siemens.com/WW/view/de/10805436
mailto:[email protected]:[email protected]://www.siemens.com/automation/service&supportmailto:[email protected]://www.siemens.de/simotionhttp://www.siemens.com/simotionhttp://support.automation.siemens.com/WW/view/de/10805436mailto:[email protected]://www.siemens.com/automation/service&supportmailto:[email protected]://support.automation.siemens.com/WW/view/de/10805436http://www.siemens.com/simotionhttp://www.siemens.de/simotionmailto:[email protected]


5/46

Preface


Further support

We also offer introductory courses to help you familiarize yourself with SIMO-TION.

Please contact your regional training center or the central training center in D-90027 Nuremberg, phone +49 (911) 895 3202 for more information.


6/46

Preface



7/46

Contents-7 Siemens AG 2008 All Rights ReservedSIMOTION Project comparison, Edition 08/2008

Contents

Preface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preface-3

Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Contents-7

1 Overview of project comparison . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9

2 General information about the object comparison . . . . . . . . . . . . . . . . . . . . . 2-11

2.1 The user interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11

2.2 Comparison icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13

2.3 Comparison tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14

2.4 Comparison attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15

2.5 Object attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16

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

3.1 Downloading additional data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17

3.2 Starting the object comparison . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17

3.3 Assignment of objects in object comparison . . . . . . . . . . . . . . . . . . . . . 3-203.3.1 Manual selection of comparison objects . . . . . . . . . . . . . . . . . . . . . . . . 3-203.3.2 Automatic assignment of the subordinate comparison objects . . . . . . . 3-203.3.3 Changing the object address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22

3.4 Detailed comparison . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-233.4.1 Starting the detailed comparison. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-233.4.2 ST detailed comparison. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-233.4.3 TO/DO detail comparison . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-26

3.5 Data transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29

4 Overview of comparison attributes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-33

4.1 SIMOTION objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34

4.2 SINAMICS objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-42

4.3 MICROMASTER and SINAMICS G120 objects . . . . . . . . . . . . . . . . . . 4-43

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Index-45


8/46

Contents

Contents-8 Siemens AG 2008 All Rights ReservedSIMOTION Project comparison, Edition 08/2008


9/46

1-9 Siemens AG 2008 All Rights ReservedSIMOTION Project comparison, Edition 08/2008

Overview of project comparison 1You can use the SIMOTION SCOUT/Starter function Project comparison (startusing Start object comparison button) to compare objects within the sameproject and/or objects from different projects (online or offline) with one another.Objects are devices, programs, technology objects (TOs) or drive objects (DOs)and libraries. The project comparison is available to you under SIMOTIONSCOUT and Starter. Comparing projects helps you in the event of service workon the system.

Cases may occur for example where inconsistencies are indicated when chang-ing into online mode in the project navigator, i.e. there are deviations betweenyour project in the SCOUT and the project loaded in the target system. Possiblecauses for this are e.g.:

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 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 necessaryrun a data transfer to rectify the differences. The following comparisons are pos-sible:

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) is in the open project while thesecond partner (the comparison object) can be a comparison object in the openproject, in a different project or the online partner.

Note

A comparison with online objects is only possible if there is already an online con-nection. No implicit connection is established when the comparison is started!


10/46

Overview of project comparison


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

a SIMOTION device,

a drive unit or

a library.

A detailed comparison is available of the individual objects for ST programs, DOs

(drive objects) and TOs (technology objects).

Note

When comparing with another project, this must be at least in SIMOTIONSCOUT/Starter version 4.1. Otherwise you will first have to convert the project.

The project comparison function is also available when using devices with olderfirmware versions if you have edited or converted the project with SIMOTIONSCOUT or Starter V4.1 SP2. The project then has to be recompiled and loaded.


11/46


General information about object comparison 2Below you will find an overview of the elements and structure of the object com-parison dialog. You can start the detailed comparison for ST programs, TOs andDOs from this dialog.

2.1 The user interface

A user interface in which the differences in the various objects have beendetected was selected by way of example for the following screenshot. If workingwith programs, all the data from this user interface could be transferred and adetailed comparison would be possible for two programs.

Fig. 2-1 SIMOTION object comparison


12/46

General information about object comparison


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

No. Description

1 Comparison partner A and comparison partner B

2 Comparison tree made up of comparison partner elements.

3 Object present (column A, column B):

You can see in the columns whether a tree object is present for comparison part-

ner A and/or comparison partner B or not.

4 Result of comparison:

The comparison result is shown in this column (same/different).

(See Comparison icons on page 2-13)

5 Select/change comparison partner

6 Update comparison

7 Call up online help8 Display object attributes (See Object attributes on page 2-16)

The attributes of the comparison partners are compared in two columns.

9 Start a detailed comparison

10 Comparison attributes of one object (See Comparison attributes on page 2-15)

11 Data transfer:

Transfer of data from comparison partner B into the open project.

12 Status bar

13 Object comparison tab


13/46


14/46



2.3 Comparison tree

The way in which the comparison tree is depicted is oriented towards the waytrees are depicted in the project navigator. Depiction of the comparison attributes

is added to the comparison tree. (See Overview of comparison attributes onpage 4-33)

Onetree is produced from the two trees/sub-trees of the comparison partners. Ifit has been possible to assign two of the comparison partners' objects, there isoneentry in the tree, columns 'A' and 'B' feature the symbol for 'Object present'.If it has not been possible to assign any comparison partners, the symbol 'Objectpresent' or 'Object not present' is shown in the corresponding column dependingon whether it belongs to comparison partner A or comparison partner B (seeexample below).

Fig. 2-2 Example of merging comparison partners

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

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

The comparison tree shows a snapshot. As a result of changes in the openproject, the comparison status may no longer be up-to-date. You are informed ofthis status in the status bar: The comparison is no longer up-to-date.

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

Note

You will find more information on assigning objects in the chapter Assignment ofobjects in object comparison, page 3-20.


15/46



2.4 Comparison attributes

In order to be able to analyze the differences when comparing objects, there area series of comparison attributes per object type which structure an object into

smaller units (comparison features) and in total contain all the object's data of rel-evance to the process.

You will already be familiar with some of the comparison attributes from theproject navigator (e.g. global device variables). In addition to this, there are newattributes which can contain various pieces of data, such as the compilation resultfor programs, and these also contain the global and local compiler settings.

You will find an overview of the specific comparison attributes for SIMOTION,SINAMICS and MICROMASTER objects in chapter Overview of comparisonattributes.

To enable the attributes to be compared as efficiently as possible, information iscalculated, e.g. a check sum, which is stored along with the project or objects, and

online too. If this information is not available (e.g. with the hardware configura-tion), a statement on the comparison cannot be made (indicated in the compari-son tree by ?).

You can start a detailed comparison for comparison attributes if you find differ-ences. The detailed comparison is available for

ST programs,

TOs (configuration data, system variables) and

DOs (parameters).

You can compare and transfer the content of data in the detailed comparison.


16/46



2.5 Object attributes

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

Table 2-3 Object attributes

Name Description

Name Name of the object1

1 from the Object properties dialog.

Object address Unique object address 1

You need the object address e.g. to address the objects via

the HMI.

Author Name of the author1

Version external External version code1

Version internal Internal version code of object, e.g. for TOs, the technologypackage version

Creation version SIMOTION SCOUT version with which the object was cre-

ated

Time stamp of last

change

Date and time of last change

Comment Comment 1


17/46


Functions 33.1 Downloading additional data

To enable you to run a detailed comparison and if necessary a complete datatransfer into PG/PC during an offline/online comparison, when downloading theproject onto the target device, you must also save the additional data, e.g.sources, symbol information etc. This is a setting in the SIMOTION SCOUT.

Procedure

Proceed as follows:

1. Select the Options > Settings menu command. The Settings windowappears.

2. Switch to the CPU-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 datais saved on the target device. If deactivated, the additional data is deleted whennext downloading to the target device.

3.2 Starting the object comparison

The object comparison is only undertaken using saved data. In contrast, thedetailed comparison uses the data in the work memory of the PC/PG. The objectand detailed comparisons may therefore result in different results.

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

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

During an online comparison the device you are comparing with is implicitlyuploaded. The comparison is therefore made with a copy of the online data.

Note

The downloading of additional data is also available when using devices witholder firmware versions if you have edited or converted the project with SIMO-TION SCOUT or Starter V4.1 SP2. The project then has to be recompiled andloaded.


18/46

Functions


Starting 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 projectnavigator.

2. Either start the object comparison via

the menu bar using Options > Compare...,

the button Start object comparison or

the context menu for the comparable objects Compare....The following dialog appears.

Fig. 3-1 Select comparison partner dialog

The object you selected previously in the project navigator is highlighted ascomparison partner A. If you had not selected an object, the first object inthe list is highlighted.

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

Object from the open project:You can select from the objects in the open project.

Object from a saved project:First open a saved project using the button:

You can select from the objects in this project.

Note

A comparison with online objects is only possible if the objects are online. Noimplicit connection is established when the comparison is started!


19/46

Functions


Object from the target system (online): (only possible in ONLINE mode andif the project is present in the target system)The object from the SCOUT or Starter is compared with the object on thetarget system.

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

Different versions detected (offline comparison with saved project)

If the comparison partner is in a different project, that was created with an olderversion of SIMOTION SCOUT, a comparison cannot be undertaken. The follow-ing note appears:

Fig. 3-2 Different comparison partner versions

In this case, first convert to the current version of SIMOTION SCOUT. Thenrestart the comparison.

Note

When comparing with a different project, this must at least be in SIMOTIONSCOUT/Starter version 4.1. Otherwise you will first have to convert the project.


20/46

Functions


3.3 Assignment of objects in object comparison

The objects of the two comparison partners must be assigned to one another. Thecomparison types and comparison categories are needed for this:

Every object and every folder has just one comparison type and can be assignedto one comparison category. For example, two SIMOTION devices (e.g. C230and D435) belong to the same category, but have different comparison types. Acomparison category may therefore contain objects with different comparisontypes.

A distinction is made between the following cases when assigning objects:

Manual assignment when selecting the comparison objects

Automatic assignment of the subordinate objects

3.3.1 Manual selection of comparison objects

The comparison objects you have selected represent the roots in the comparisontree. The objects must at least belong to the same comparison category while thecomparison type may differ.

If the names are different, e.g. CPU_1 is being compared with CPU_2, bothnames are shown in the root node of the comparison tree.

If the object types are different, a difference is marked and attempts are made toassign the lower level objects.

3.3.2 Automatic assignment of the subordinate comparison objects

During automatic assignment, all objects below the root are assigned taking theirposition in the tree into account. For example, axis 1 and axis 2 are assigned inthe comparison. During automatic assignment of the subordinate objectsattempts are made to assign the probes under axis 1 to the probes under axis 2provided that they are of the same comparison type.

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

Assignment of TOs/DOs using object addresses

TOs/DOs are assigned using their object address. In this case, the objectaddress appears after the name: (). Since the name ofthe object may differ in this case, both names are shown in the event of deviation.

Note

When switching into ONLINE mode, TOs/DOs for the consistency display in theproject navigator are also assigned using the object address.


21/46

Functions


When assigning using the object address, cases may arise where e.g. a probeunder axis A1 has the same object address as the probe under axis A2 in thecomparison project:

Fig. 3-3 Example of assignment when the object addresses differ

Since the object addresses are issued automatically, this may occur if the objectsare created e.g. in a different order or using script.

But this assignment is not desirable as it would result in incorrect object assign-ment. The object address is therefore only taken into account within the samehierarchy level during assignment but not over hierarchy levels.

If necessary, you can change the object addresses of TOs yourself. This allows

you to enforce correct assignment of the object address for TOs later on.

Assignment of other objects using names

Other objects, i.e. all objects outside the TOs/DOs, are assigned using theirnames.

Note

We would recommend always explicitly issuing the object address for TOs (SeeChanging the object address on page 3-22). You cannot change the address ofDOs!

Note

If objects are not automatically assigned despite having the same name and aretherefore positioned one above the other in the comparison tree, the comparisontype is different.


22/46

Functions


3.3.3 Changing the object address

Procedure

To change the object address:

1. Select the appropriate TO in the project navigator.

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

3. Click on the Object address tab.

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

5. Click on the Assign button and confirm with OK.


23/46

Functions


3.4 Detailed comparison

3.4.1 Starting the detailed comparison

Requirement

The detailed comparison for ST programs, TOs and DOs can be started from thecomparison tree by clicking on the

button.

You can only start the detailed comparison if

you have found differences or

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

In the detailed comparison, the corresponding content are shown next to oneanother, the differences marked and the transfer of changes from the comparisonobject into the reference object made possible if required.

Procedure

1. First run an object comparison on the device you want. (See Starting theobject comparison on page 3-17)

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

Fig. 3-4 Example of detailed comparison for two ST programs

3. Click on the Start detailed comparison button to compare the ST programsor DOs/TOs. The corresponding editors are opened next to one another in theview and the differences marked.

3.4.2 ST detailed comparison

The ST detailed comparison allows you to run a textual comparison on STsources. The compared sources are shown next to one another and the differ-ences marked in color. Missing lines (marked in gray) are added so that identicallines can be shown synchronized.

You can transfer the differences line by line. You have to open the ST editor forediting. You cannot edit in the detailed comparison.


24/46

Functions


Fig. 3-5 Example of ST detailed comparison

Note

Not the information provided in the status bar at the end of the view.

Note

In isolated cases, a difference is detected as a result of a control character, e.g.a line break, which is not however of any relevance to the source text.


25/46

Functions


Function buttons of the ST detailed comparison

Menu ST detailed comparison

Procedure

1. Perform an object comparison test.

2. Start the ST detail comparison. The sources are compared in the ST detailcomparison and the differences marked in color.

3. If necessary, transfer the differences into the project.

4. Close the detail comparison and confirm with OK.

Table 3-1 Function buttons ST detailed comparison

Description

Jumps to next difference

Jumps to last difference

Jump to marked line(s) in the source (from comparison partner B to A)

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

Table 3-2 Menu ST detailed comparison

Menu item Description

Display line numbers Displays the line numbers of comparison partners A

and B

Ignore indents Indents in the source are ignored; you need to

define this before first transferring changes as youcannot change the setting for the current compari-

son afterwards.

Transfer changes into project Transfers the changes into the project and saves

the changes

Close and open editor Opens comparison partner A in the ST editor. Thedetail comparison closes.


26/46


27/46

Functions


TO detailed comparison

Example of a TO detailed comparison.

Fig. 3-6 Example of a TO detailed comparison.


28/46

Functions


DO detailed comparison

Example of a DO detailed comparison

Fig. 3-7 Example of a DO detailed comparison


29/46

Functions


3.5 Data transfer

You can use the "Data transfer" function in the object comparison to transfer thedata of the comparison object (B) into the open project (A). You can transfer indi-

vidual data working from the detail comparison. You can run a complete onlinecalibration from B to A using the function Download into PG/PC or from A to Busing Download to target device.

Rules for data transfers in the object comparison

Rules applicable to the transfer:

When you transfer an object, the content of the object is transferred in full fromthe comparison object (e.g. compiler settings too) and overwrites the data inthe reference object. In other words, changes that you undertook in the refer-ence project may be lost!

If the comparison partner is in the target system, the corresponding informa-tion must be available online. If this is not the case (e.g. if there is no intercon-nection information for DCC plans, or if the sources of ST programs have notbeen downloaded to the target device), the transfer is not possible.

DOs cannot be transferred.

A TO/program can be transferred into an existing TO/program. TOs/programs

cannot on the other hand be created, e.g. in cases where there is not a TO inA, but there is one in B.

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

Know how-protected objects are transferred. Objects open in an editor areclosed.

When entire objects are transferred, the object address is also transferred(see duplicate assignment of an object address).

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 (for TOs) orwith the same name (for programs) and then repeat the data transfer. TOs ora program entry in the execution system then still has to be linked by hand.

If you do not want to transfer entire objects but just individual pieces of datafrom an object, you can only do this in the detail comparison. Here you can forexample transfer one particular change to an ST program (see detailed com-parison).

Note

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


30/46

Functions


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 youwant to transfer.

Fig. 3-8 Selection and transfer of objects

2. Start the transfer by clicking on the button Data transfer and confirm the fol-lowing dialog with OK.

Fig. 3-9 Data transfer dialog

Once transferred, the check box is replaced by a check mark. The result of thecomparison in the object comparison is then no longer up-to-date. This is indi-cated in the status bar at the end of the view.

Fig. 3-10 View following transfer


31/46

Functions


Duplicate assignment of an object address

When transferring entire objects, the object address is also transferred. Since theobject address in the address space of a SIMOTION device must be unique,address conflicts may result. A transfer which would result in a duplicate assign-

ment is not carried out. The object affected by the address conflict is entered inthe log in the detailed view.

Change the object address as required.

(See Changing the object address on page 3-22)


32/46


33/46


Overview of comparison attributes 4Below you will find an overview of the comparison attributes for SIMOTION,SINAMICS and MICROMASTER objects.

The comparison attributes are made up of several comparison features. Thereare various reasons for a difference in comparison attributes. A difference in thecompilation result may e.g. result from program changes (source code) and/or achange to the compiler settings. The tables below describe the comparisonattributes for the individual object types. They should help you to be able to

quickly establish the causes in the event of a difference if a detailed comparisonis not available.

We recommend the following procedure for efficiently finding the reason for a dif-ference to a comparison attribute:

If necessary compile the project if the compilation result is no longer up-to-date

Start detailed comparison, if available

Search for description of comparison attribute in the object table

Check the comparison features

To be able to check the comparison features (e.g. the compiler settings) duringan online comparison, create a new project with a SIMOTION device and down-

load the target devices into the PG for this new SIMOTION device. The additionaldata must have already been downloaded.

When comparing with a different project, we would recommend opening this in asecond SCOUT/Starter.


34/46

Overview of comparison attributes


4.1 SIMOTION objects

SIMOTION device

Table 4-1 Comparison attributes of a SIMOTION device

Comparison attributes of a

SIMOTION device

Comparison features which are included in the com-

parison attribute

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 function "Set system

cycles..." (Servo, Ipo, Ipo_2, TControl)

Execution system - compila-

tion result

The part which results from the project's compilation pro-

cess.

The compilation result includes:

The configuration of the execution system (see above)

The technology packages used

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.

Global device variables Configuration global device variables

Note: Structural changes to the global device variables

are also included in the "HMI relevant data" comparison

attribute.

HW config (time stamp com-

parison)

Comparison of the hardware configuration is based solely

on a time stamp comparison. The time stamp of the last

change is used. A comparison undertaken on this basis

only allows a same statement to be made if the time

stamp is the same. If the time stamp is different, the hard-

ware configuration may be the same or different. This is

the case e.g. if the last change has been reversed.

STEP7 SIMATIC manager offers a block comparison for

such cases.

Offline comparison

The comparison is undertaken as described above.

Online comparison (devices which have been down-loaded with a SCOUT/STARTER version


35/46



HW config (system integra-tion) The data from the hardware configuration which isincluded in the SIMOTION configuration:

I/O addressing (in HW config)

DP cycle (bus cycle)

Equidistant bus cycle

Devices which have been downloaded with a

SCOUT/STARTER version


36/46


37/46


38/46



DCC plan

Table 4-4 Comparison attributes of a DCC plan


DCC plan


parison attribute

Source code

(time stamp comparison)

Offline only

Changes in the DCC editor based on a time stamp (last

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 com-

parison only. The time stamp of the last change is used.

A comparison undertaken on this basis only allows a

same statement to be made if 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 last change

was reversed). A statement on this cannot be made inthe object comparison. This is shown by a ?.

Blocks Block instances and their properties, like

Type

Name

Address

Constant values (initial values) of inputs and outputs

Assignment to run-time group

Predecessor in run-time group

Interconnections The following interconnections are included in the com-

parison:

Plan interconnections

Interconnection of all the plan's inputs

Interconnections with run-time groups

Interconnections with @ parameters

Interconnections with non-DCC-objects within SIMO-

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

Run-time groups Plan run-time groups and their properties

Name

Task assignment

Predecessor run-time group

Initial state of run-time group (active / inactive)


39/46



@ parameters and externalreferences SIMOTION: Published parameters

Compiler settings

External references

Interfaces of referenced sources (pro-

grams(ST,MCC,KOP-FUP),

Reference parameters of other DCC plans,

Interfaces of DCC libraries used,

Global device variables used,

I/O variables used,

TO system variables used

SINAMICS:

Parameter values of the @parameters

p parameter: Values of adjustable parameters and

BICO interconnections on BICO dies

HMI relevant data Records the structural set-up (data type of variables,

number of variables) of the data which an HMI system

can access. If the set-up changes, the HMI configuration

must be updated. Data included:

SIMOTION:

Online/offline comparison:

The @ parameters of the plan (published parameters)

The object address (see plan properties)

Offline/online comparison:

See @ parameters and external references

SINAMICS:

Not applicable

Table 4-4 Comparison attributes of a DCC plan


DCC plan


parison attribute


40/46


41/46



DCC plan in a library

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


DCC library


parison attribute

Source code (time stamp

comparison)

Offline only

Changes in the DCC editor based on a time stamp (last

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 com-

parison only. The time stamp of the last change is used.

A comparison undertaken on this basis only allows a

same statement to be made if 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 last change

was reversed). A statement on this cannot be made inthe object comparison. This is shown by a ?.

Blocks Block instances and their properties, like

Type

Name

Address

Constant values (initial values) of inputs and outputs

Assignment to run-time group

Predecessor in run-time group

Interconnections The following interconnections are included in the com-

parison:

Plan interconnections

Interconnection of all the plan's inputs

Interconnections with run-time groups

Interconnections with @ parameters

Interconnections with non-DCC-objects within SIMO-

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

Run-time groups Plan run-time groups and their properties

Name

Task assignment

Predecessor run-time group

Initial state of run-time group (active / inactive)


42/46



4.2 SINAMICS objects

Drive unit

DO

DCC plan

Description of comparison attributes: See DCC plan on page 4-38

Table 4-8 Comparison attributes of a drive unit


drive unit


parison attribute

Reference topology The reference topology

For this comparison attribute, the serial number is not

taken into account in the comparison.

Topology

(with serial number)

Topology

For this comparison attribute, the serial number is taken

into account in the comparison.

Table 4-9 Comparison attributes of a DO


drive object (DO)


parison attribute

Function modules Function modules (see parameter 108 in the DO list of

experts)

Structure parameters Parameter which determine structures, e.g. DDS

Download parameters Download parameters (see DO list of experts)

Units Units

This comparison feature does not determine structure.


43/46



4.3 MICROMASTER and SINAMICS G120 objects

Table 4-10 Comparison attributes

Comparison attribute Comparison features which are included in the com-parison attribute

Device version Power unit/infeed

(configuration vector specifies the device version of a

device type)

(Only available with G120, not MM4 or Combimaster)

Download parameters Download parameters (see list of experts)


44/46


45/46

Index-45 Siemens AG 2008 All Rights ReservedSIMOTION Project comparison, Edition 08/2008

Index

CChanging object address

Object comparison, 3-22Comparison attributes

Data of relevance to the process, 2-15DCC plan, 4-38DCC plan in a library, 4-41DCC plan SINAMICS, 4-42

Detailed comparison, 2-15DO SINAMICS, 4-42Library, 4-40MICROMASTER, 4-43Object comparison, 4-33SIMOTION device, 4-34SINAMICS drive unit, 4-42SINAMICS G120, 4-43Source in a library, 4-40Sources, 4-36Technology objects, 4-36

Comparison status

not up-to-date, 2-14Comparison tree

Update, 2-14

DData transfer

Object comparison, 3-29Detailed comparison, 3-23Different versions object comparison, 3-19DO detailed comparison, 3-28

IInconsistencies in the project comparison

Project navigator, 1-9

OObject address object comparison

Technology objects, drive objects, 2-16Object comparison

Additional data, 3-17Assignment of objects, 3-20Automatic assignment of objects, 3-20Changing object address, 3-22

Comparison tree, 2-14Elements, 2-11Manual assignment of objects, 3-20Starting, 3-17

PProject comparison

Overview, 1-9

RResult of comparison

Object comparison icons, 2-13

Same/different, 2-12Status in object comparison, 2-12

SSIMOTION objects, 4-34SINAMICS objects

Comparison attributes, 4-42ST detailed comparison, 3-23Starting detailed comparison, 3-23Structure, 2-11

TTO detailed comparison, 3-27

TO/DO detail comparison, 3-26


46/46

project comparison

Documents