Simotion: Function Manual

Edition 08/2008
SIMOTION
Project comparison
Function Manual

s
Preface, Contents
Overview of project comparison
1
General information about object comparison
2
Functions
3
Overview of comparison attributes
4
Index
Copyright Siemens AG 2008 All Rights Reserved
The reproduction, transmission or use of this document or its contents
is not permitted without express written authority. Violation of this rule
can lead to claims for damage compensation. All rights reserved, es-
pecially for granting patents or for GM registration.
Siemens AG
Automation & Drives
Motion Control Systems
PO Box 3180, D-91050 Erlangen
Germany
Disclaimer of liability
We have checked that the contents of this document correspond to
the hardware and software described. Since variance cannot be pre-
cluded entirely, we cannot guarantee full consistency. The data in this
document is regularly checked and the necessary corrections are in-
cluded in subsequent editions.
Siemens AG 2008
Subject 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 of
the 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
Preface-3 Siemens AG 2008 All Rights Reserved
SIMOTION Project comparison, Edition 08/2008
Preface
This document is part of the SIMOTION System and Function Descriptions
documentation package.
SIMOTION Documentation
An overview of the SIMOTION documentation can be found in a separate list of
references.
This document is supplied in electronic format with SIMOTION SCOUT.
The SIMOTION documentation consists of 9 documentation packages containing
approximately 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
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 FAQs
can be found on the Internet at
Americas
Phone +1 423 262 2522
Fax +1 423 262 2200
E-mail techsupport.sea@siemens.com
Asia / Pacific
Phone +86 1064 719 990
Fax +86 1064 747 474
E-mail adsupport.asia@siemens.com
Note:
Country-specific telephone numbers for technical support are provided under the
following 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: docu.motioncontrol@siemens.com
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
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.
Preface
Contents-7 Siemens AG 2008 All Rights Reserved
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-20
3.3.1 Manual selection of comparison objects . . . . . . . . . . . . . . . . . . . . . . . . 3-20
3.3.2 Automatic assignment of the subordinate comparison objects . . . . . . . 3-20
3.3.3 Changing the object address. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22
3.4 Detailed comparison . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23
3.4.1 Starting the detailed comparison. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23
3.4.2 ST detailed comparison. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23
3.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
Contents
Contents-8 Siemens AG 2008 All Rights Reserved
1-9 Siemens AG 2008 All Rights Reserved
Overview of project comparison 1
You can use the SIMOTION SCOUT/Starter function Project comparison (start
using Start object comparison button) to compare objects within the same
project 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 SIMOTION
SCOUT and Starter. Comparing projects helps you in the event of service work
on 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 between
your project in the SCOUT and the project loaded in the target system. Possible
causes 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 necessary
run 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 the
second partner (the comparison object) can be a comparison object in the open
project, 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!
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,
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 SIMOTION
SCOUT/Starter version 4.1. Otherwise you will first have to convert the project.
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.1 SP2. The project then has to be recompiled and loaded.
General information about object comparison 2
Below 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 and
DOs from this dialog.
2.1 The user interface
A user interface in which the differences in the various objects have been
detected was selected by way of example for the following screenshot. If working
with programs, all the data from this user interface could be transferred and a
detailed comparison would be possible for two programs.
Fig. 2-1 SIMOTION object comparison
1
1
2
3
3
4
5
9
6 7
8
8
9
11
12
10
11
13

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 help
8 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
2.2 Comparison icons
Below you will find an overview of the icons used in columns A and B and their
status.
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. The characteristic of
the attributes may however be the same or different and same or different 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.
Table 2-2
Icon Description
Object is present (is displayed in columns A and/or B).
Object is not present (is displayed in columns A and/or B).
Difference in at least one subordinate object or comparison attribute (is only dis-
played if the folder or object is collapsed).
The comparison attribute is the same.
The comparison attribute is different.
The result of compilation does not match the source status of comparison part-
ner A or B.
A same/different statement cannot be made.
One possible cause of this is e.g. that the hardware configuration is being com-
pared using the time stamp. If the time stamp deviates, a same/different state-
ment cannot be made.
2.3 Comparison tree
The way in which the comparison tree is depicted is oriented towards the way
trees are depicted in the project navigator. Depiction of the comparison attributes
is added to the comparison tree. (See Overview of comparison attributes on
page 4-33)
One tree is produced from the two trees/sub-trees of the comparison partners. If
it has been possible to assign two of the comparison partners' objects, there is
one entry 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 'Object
present' or 'Object not present' is shown in the corresponding column depending
on whether it belongs to comparison partner A or comparison partner B (see
example below).
Fig. 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 are informed of
this status in the status bar: The comparison is no longer up-to-date.
Since the comparison tree is not automatically updated, you have to explicitly
start the update by clicking on the Update button.
Note
You will find more information on assigning objects in the chapter Assignment of
objects in object comparison, page 3-20.
Tree A Tree B
Object 1 Object 1
Object 2
Comparison
tree
Object 1
Object 2
A B
2.4 Comparison attributes
In order to be able to analyze the differences when comparing objects, there are
a 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 the
project navigator (e.g. global device variables). In addition to this, there are new
attributes which can contain various pieces of data, such as the compilation result
for 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 comparison
attributes.
To enable the attributes to be compared as efficiently as possible, information is
calculated, 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.
2.5 Object attributes
You can select the following object attributes in the two right-hand columns in the
object comparison.
Table 2-3 Object attributes
Name Description
Name Name of the object
1
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 author
1
Version external External version code
1
Version internal Internal version code of object, e.g. for TOs, the technology
package 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
Functions 3
3.1 Downloading additional data
To enable you to run a detailed comparison and if necessary a complete data
transfer into PG/PC during an offline/online comparison, when downloading the
project 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 window
appears.
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 data
is saved on the target device. If deactivated, the additional data is deleted when
next downloading to the target device.
3.2 Starting the object comparison
The object comparison is only undertaken using saved data. In contrast, the
detailed comparison uses the data in the work memory of the PC/PG. The object
and 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 implicitly
uploaded. The comparison is therefore made with a copy of the online data.
Note
The downloading of additional data is also available when using devices with
older 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 and
loaded.
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 project
navigator.
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 as
comparison partner A. If you had not selected 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 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. No
implicit connection is established when the comparison is started!
Functions
Object from the target system (online): (only possible in ONLINE mode and
if the project is present in the target system)
The object from the SCOUT or Starter is compared with the object on the
target system.
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
button Start comparison.
Different versions detected (offline comparison with saved project)
If the comparison partner is in a different project, that was created with an older
version 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. Then
restart the comparison.
Note
When comparing with a different project, this must at least be in SIMOTION
SCOUT/Starter version 4.1. Otherwise you will first have to convert the project.
Functions
3.3 Assignment of objects in object comparison
The objects of the two comparison partners must be assigned to one another. The
comparison types and comparison categories are needed for this:
Every object and every folder has just one comparison type and can be assigned
to one comparison category. For example, two SIMOTION devices (e.g. C230
and D435) belong to the same category, but have different comparison types. A
comparison category may therefore contain objects with different comparison
types.
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 comparison
tree. The objects must at least belong to the same comparison category while the
comparison type may differ.
If the names are different, e.g. CPU_1 is being compared with CPU_2, both
names are shown in the root node of the comparison tree.
If the object types are different, a difference is marked and attempts are made to
assign 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 their
position in the tree into account. For example, axis 1 and axis 2 are assigned in
the comparison. During automatic assignment of the subordinate objects
attempts are made to assign the probes under axis 1 to the probes under axis 2
provided that they are of the same comparison type.
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. 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.
Note
When switching into ONLINE mode, TOs/DOs for the consistency display in the
project navigator are also assigned using the object address.
Functions
When assigning using the object address, cases may arise where e.g. a probe
under axis A1 has the same object address as the probe under axis A2 in the
comparison project:
Fig. 3-3 Example of assignment when the object addresses differ
Since the object addresses are issued automatically, this may occur if the objects
are 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 same
hierarchy 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 their
names.
Note
We would recommend always explicitly issuing the object address for TOs (See
Changing the object address on page 3-22). You cannot change the address of
DOs!
Tree A
Comparison tree A B
Probe M1 (10)
Axis A2
Probe M2 (20)
Tree B
Axis A1
Probe M1 (30)
Axis A2
Probe M2 (10)
Axis A1
Probe M1 (10)
Probe M1 (30)
Axis A2
Probe M2 (20)
Probe M2 (10)
Axis A1
Note
If objects are not automatically assigned despite having the same name and are
therefore positioned one above the other in the comparison tree, the comparison
type is different.
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.
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 the
comparison 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 one
another, the differences marked and the transfer of changes from the comparison
object into the reference object made possible if required.
Procedure
1. First run an object comparison on the device you want. (See Starting the
object comparison on page 3-17)
2. The Start detailed comparison button is shown in the Status column for
objects 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 programs
or DOs/TOs. The corresponding editors are opened next to one another in the
view and the differences marked.
3.4.2 ST detailed comparison
The ST detailed comparison allows you to run a textual comparison on ST
sources. 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 identical
lines can be shown synchronized.
You can transfer the differences line by line. You have to open the ST editor for
editing. You cannot edit in the detailed comparison.
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.
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 detail
comparison 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 you
cannot 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. The
detail comparison closes.
Functions
3.4.3 TO/DO detail comparison
You will find a detailed description of the function in the basic manual under the
list of experts comparison.
The differences between the TO/DO detailed comparison and list of experts com-
parison are summarized in the table below.
Table 3-3 Comparison of detailed comparison and list of experts comparison
Features Detailed comparison List of experts comparison
Number of comparison
objects
1 1 ... n
Origin of comparison objects Objects from different projects Object from the open project only
Values to be compared
1
Configured values, actual values
are not included in the comparison
Actual values
Indication of differences
(structural differences)
Complete indication of all parame-
ters (DOs) or system variables and
configuration data (TOs), regard-
less of whether they occur in com-
parison partner A or B or both.
Only the parameters and system
variables and configuration data of
comparison partner A are displayed.
You therefore only see whether the
parameters contained in the refer-
ence object are present in the com-
parison objects or not. Parameters
that only the comparison objects
contain but 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 objects
2
Change to data in comparison part-
ner A (reference object) only during
an offline comparison
Note:
You can use the context menu for
the table cells of comparison part-
ner 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 list
of experts comparison
1 Differences between configured values and actual values are only of any consequence if the comparison partner is
an online TO.
Offline all parameters only ever have one (configured) value.
With online DO objects there is only ever one value and the following applies:
actual value = configured value
2 Fields hatched out in the detail comparison cannot be edited.
Functions
TO detailed comparison
Example of a TO detailed comparison.
Fig. 3-6 Example of a TO detailed comparison.
Functions
DO detailed comparison
Example of a DO detailed comparison
Fig. 3-7 Example of a DO detailed comparison
Functions
3.5 Data transfer
You can use the "Data transfer" function in the object comparison to transfer the
data 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 online
calibration from B to A using the function Download into PG/PC or from A to B
using 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 from
the comparison object (e.g. compiler settings too) and overwrites the data in
the 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 not
been 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 in
A, but there is one in B.
TOs/DOs cannot be deleted by transferring them, e.g. if there is a TO/DO in
A, but not in B.
Know how-protected objects are transferred. Objects open in an editor are
closed.
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) or
with the same name (for programs) and then repeat the data transfer. TOs or
a 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 data
from an object, you can only do this in the detail comparison. Here you can for
example 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 the
detail view in the object comparison tab.
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 you
want 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 the
comparison 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
Functions
Duplicate assignment of an object address
When transferring entire objects, the object address is also transferred. Since the
object 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 in
the log in the detailed view.
Change the object address as required.
(See Changing the object address on page 3-22)
Functions
Overview of comparison attributes 4
Below 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. There
are various reasons for a difference in comparison attributes. A difference in the
compilation result may e.g. result from program changes (source code) and/or a
change to the compiler settings. The tables below describe the comparison
attributes 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 comparison
is 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) during
an 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 additional
data must have already been downloaded.
When comparing with a different project, we would recommend opening this in a
second SCOUT/Starter.
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 <= 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
avoids the SIMOTION device being displayed as incon-
sistent in the project navigator, but everything is the same
in the object comparison (the only difference is in the HW
config).
HW config (system integra-
tion)
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 which have been downloaded with a
SCOUT/STARTER version <= V4.0:
Comparison attribute is only available offline.
Device settings Device name
Behavior of dynamic data during STOP/RUN transition
Fast I/O configuration (onboard I/Os, TM15/TM17 high
feature)
Devices which have been downloaded with a
SCOUT/STARTER version <= V4.0:
This comparison attribute is not present.
System variables Configuration of system variables in the SIMOTION
device
TO interconnections Interconnections of TOs on the target device
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:
Structure information of I/O variables
Structure information of global device variables
For every library used:
Compilation result <Lib-
name>
Compilation result of the specific device version
This comparison attribute is only shown if a library is
used.
A library comparison can be undertaken for a detailed
comparison.
Table 4-1 Comparison attributes of a SIMOTION device
SIMOTION device
parison attribute
Technology objects (TO)
Sources
The following overview applies to ST, KOP, FUP and MCC.
Table 4-2 Comparison attributes of a TO
technology object (TOs)
parison attribute
Configuration Contains the configuration of a TO, consisting of
The configuration setting (linear/rotary axis; TO acti-
vated/deactivated)
All configuration data (see list of experts)
Indirect influence of unit configuration
1
1 The unit and value of a technological parameter are always viewed separately and not the result-
ant parameter. That 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 con-
verted and the result parameter is the same.
A linear axis/pressure uses different physical parameters to a linear axis/force; even if the numer-
ical values are the same, these different parameters will result in a difference.
System variables The system variable of the TO
Indirect influence of unit configuration and configuration
settings
1
Units Configuration of units
This comparison attribute is not present in cam discs.
Alarm configuration Configuration of TO alarms (see TechnologicalFault-
Task)
The configuration data
The object address (see TO properties)
Indirect influence of unit configuration and configuration
settings
1
For TO cam disc only:
Configuration data
Configuration data of cam disc (e.g. support points,
interpolation, scaling)
Table 4-3 Comparison attributes of a source
source
parison attribute
Source code The source text (based on ASCII)
Compilation result The compilation result for a source includes:
The source text of relevance to execution, i.e. every-
thing apart from comments and formats
The compiler settings (local and global)
The compiler version (e.g. compilation with new
SCOUT)
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 (the numbers assigned to
symbols)
If a different number has been assigned to a symbol
of an alarmS configuration and this symbol has been
used in this program, then the source code is the
same in both cases but the compilation result is dif-
ferent. If you need to work out online which number
has been used for a symbol, you upload a device into
an empty project. There you can look into the mes-
sage configuration (the symbols and the assigned
numbers are entered there during the upload)
Offline comparison
VAR_GLOBAL variables of the source
The object address (see source properties)
Online comparison
At the moment the comparison attribute does not pro-
duce a meaningful result.
Table 4-3 Comparison attributes of a source
source
parison attribute
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 in
the 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)
@ parameters and external
references
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
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
Library
Source in a library
Table 4-5 Comparison attributes of a library
library
parison attribute
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 regardless of device.
The following data is included in the comparison:
The source text of relevance to execution, i.e. every-
thing 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)
Like compilation result <device type>
Compilation result regardless of devices
Table 4-6 Comparison attributes of a source in a library
library
parison attribute
Source code Source text (based on ASCI)
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 in
the 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)
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.
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)
Index-45 Siemens AG 2008 All Rights Reserved
Index
C
Changing object address
Object comparison, 3-22
Comparison attributes
Data of relevance to the process, 2-15
DCC plan, 4-38
DCC plan in a library, 4-41
DCC plan SINAMICS, 4-42
Detailed comparison, 2-15
DO SINAMICS, 4-42
Library, 4-40
MICROMASTER, 4-43
SIMOTION device, 4-34
SINAMICS drive unit, 4-42
SINAMICS G120, 4-43
Source in a library, 4-40
Sources, 4-36
Technology objects, 4-36
Comparison status
not up-to-date, 2-14
Comparison tree
Update, 2-14
D
Data transfer
Detailed comparison, 3-23
Different versions object comparison, 3-19
DO detailed comparison, 3-28
I
Inconsistencies in the project comparison
Project navigator, 1-9
O
Object address object comparison
Technology objects, drive objects, 2-16
Object comparison
Additional data, 3-17
Assignment of objects, 3-20
Automatic assignment of objects, 3-20
Changing object address, 3-22
Comparison tree, 2-14
Elements, 2-11
Manual assignment of objects, 3-20
Starting, 3-17
P
Project comparison
Overview, 1-9
R
Result of comparison
Object comparison icons, 2-13
Same/different, 2-12
Status in object comparison, 2-12
S
SIMOTION objects, 4-34
SINAMICS objects
Comparison attributes, 4-42
ST detailed comparison, 3-23
Starting detailed comparison, 3-23
Structure, 2-11
T
TO detailed comparison, 3-27
TO/DO detail comparison, 3-26
Index
Index-46 Siemens AG 2008 All Rights Reserved

Simotion: Function Manual

Caricato da

Informazioni sul documento

Descrizione originale:

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Simotion: Function Manual

Caricato da

Copyright:

Formati disponibili

Edition 08/2008

Potrebbero piacerti anche