Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd
Upload
47 views

Copying/moving Charts: Working With Textual Interconnections

Copying charts allows you to duplicate structures between CPUs while also copying resources like block types, FBs, and FCs. When copying between charts, interconnections beyond the chart boundaries become textual interconnections that can be closed by copying related charts to the same folder. Nested charts may lose internal interconnections when moved. System attributes of copied blocks are compared to prevent inconsistencies. Block types must be compatible between CPUs or the chart won't copy.

Uploaded by

sybaritz
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
47 views

Copying/moving Charts: Working With Textual Interconnections

Copying charts allows you to duplicate structures between CPUs while also copying resources like block types, FBs, and FCs. When copying between charts, interconnections beyond the chart boundaries become textual interconnections that can be closed by copying related charts to the same folder. Nested charts may lose internal interconnections when moved. System attributes of copied blocks are compared to prevent inconsistencies. Block types must be compatible between CPUs or the chart won't copy.

Uploaded by

sybaritz
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Copying/moving charts

Introduction
Copying entire charts allows you to duplicate or move tested structures or substructures, even to
other CPUs.

Copying/moving
Including resources in the copy
When you copy/move charts, the resources will also be copied, provided they do not already exist
in the destination. The following elements are resources:
x Block types, FBs and FCs, including symbols
x System attributes
x Called blocks of multiple instance blocks
Textual interconnections
When you copy/move a chart to another chart folder, interconnections that exceed the chart
boundaries are implemented as textual interconnections. These open textual interconnections can
be closed again. They then form real block interconnections, provided you copy/move the chart
and the interconnection partner to this chart folder, or once you have copied/moved the
corresponding chart back to its original folder.
This includes textual interconnections of the chart you want to copy/move.
Peculiarities of nested charts: When you move or copy nested charts, the internal interconnections
to the chart I/Os are not converted to textual interconnections, that is, they will be lost.
You will find more detailed information in the section Working with textual interconnections
Shared addresses
When copying charts, remember that interconnections to shared addresses are also copied,
depending on the default setting. You can change this setting in the "Settings for Copying/Moving"
dialog box. You can open this dialog box with the menu command Options > Customize >
Copy/Move....
Runtime groups
When copying/moving charts, interconnections to runtime groups are not copied. No textual
interconnections are generated.
System attributes
When charts are copied or moved, the system attributes of the copied/moved blocks are
compared to existing blocks in the destination. You may abort the copying/moving operation based
on the results of the comparison. The reasons for this step are described in the section What you
should know about copying blocks in "Checking the System Attributes".

Copying/moving charts to a different CPU/library/project


When you copy charts to other CPUs, remember the following points:
x If a block type in the destination CPU is incompatible with the block type you are copying
(number, order, name, and data types of the block I/Os), the chart will not be copied.
You are shown a log with a list of relevant block types.
In this case, before you copy the chart again:
- You must copy the relevant block type either to the block folder of the source program or to
the block folder of the destination program.
- Select the block type in the "Chart Folder" box using the menu command Options > Block
Types... and click the "New Version" button.
A central block type change is made.
x The copied blocks will maintain the runtime properties of the blocks from the source CPU.
Therefore, the blocks are installed in the run sequence as they were installed in the source
CPU.
If no task with the same name exists on the destination CPU, a log displaying the missing
tasks is output and the copy operation will be rejected.
Note
We do not advise the copying of complete chart folders, since the resources (e.g., FBs, FCs, shared
DBs, symbols) are not included and program inconsistency might develop.
If you do not want to copy the complete program, you can select and copy all the charts in the chart
folder. In this case, the resources are also copied.
Copying the entire program, the CPU or a station does not lead to any inconsistency.
If a chart is empty, the chart run sequence is not copied or moved.

Charts on different target systems


You can copy and move CFC charts between different target systems. Once again, the block types
used on both target systems must be identical, since the block types are not included. If the block
types are not identical, copying of the charts would be rejected.

You might also like