C135 PCS 7 (PCS7)
6C
6 Cielo Ciencia y Tecnología
·Publicada en C135 PCS 7 (PCS7)

Transferring CFC Charts Between Engineering Workstations in SIMATIC PCS 7 - Copy-Paste Workflow and Multiuser Engineering

Transferring CFC Charts Between Engineering Workstations in SIMATIC PCS 7 - Copy-Paste Workflow and Multiuser Engineering

To transfer newly created or modified CFC charts from an offline laptop virtual machine to the primary Engineering Station (ES) in SIMATIC PCS 7, engineers can use either a structured Multiuser Engineering network workflow or an isolated project copy-paste procedure. When moving individual CFC charts between multiprojects, you must open both projects concurrently in SIMATIC Manager, copy the charts directly from the source S7 program chart folder to the target chart folder, and resolve block type versions against the Master Data Library. Direct file-level copying of underlying database files (.S7P or chart files in Windows Explorer) is strictly prohibited as it destroys internal cross-reference databases and block instance pointers.

Table of Contents

Architectural Considerations for Offline and Distributed CFC Authoring

In industrial plant engineering, automation specialists frequently create or modify Continuous Function Charts (CFC) on offline portable workstations or virtual machines (VMs) disconnected from the central plant network. In SIMATIC PCS 7 (including STEP 7 v5.5 and v5.6 environments), CFC charts are not standalone flat text files. Instead, each CFC chart is an integrated technological entity consisting of graphic topologies, symbol table connections, runtime group sequence entries in cyclic interrupt Organization Blocks (such as OB35), and database records linked to the central project database (Sycon.db / pbase.db).

Attempting to move charts by copying files within Windows Explorer causes severe project corruption, resulting in phantom block instances and broken internal S7 links. To safely integrate charts authored on a separate laptop VM into the production Engineering Station, two approved Siemens methodologies exist:
1. Multi-Project Copy-Paste Workflow: Opening both the retrieved offline project and the target plant project concurrently on the Engineering Station, copying the specific charts via SIMATIC Manager, and updating block types from the Master Data Library.
2. Multiuser Engineering: Operating both the laptop and the ES across a shared local area network (LAN) where multiple engineers open the same central multiproject concurrently, utilizing chart reservation and checkout features.

Prerequisites and Master Data Library Synchronization

Before transferring any CFC charts between different PCS 7 project databases, strict library and environmental alignment must be verified:

  1. Software Version Parity: The engineering toolsets on both machines must match identically in version and installed updates (e.g., PCS 7 v8.2, CFC v8.2 Upd1, S7-SCL v5.6). Different CFC compiler versions will trigger mandatory full AS compilation and full CPU downloads.
  2. Master Data Library (MDL) Uniformity: The block types (FBs and FCs) placed on the offline charts must originate from the identical Master Data Library as the target plant project. If a block type has a newer timestamp or modified interface on the laptop, pasting the chart will prompt an interface conflict.
  3. Symbol Table and Global Data Alignment: Any symbolic global memory addresses (flags, shared DBs, peripheral inputs IW, outputs QW) referenced on the chart must exist in the target project symbol table with identical data types.
  4. Hierarchical Folder Structure: If the project utilizes Technological Hierarchy (Plant Hierarchy), ensure the destination hierarchy folder path exists in the target project prior to copying.

Step-by-Step Procedure: Moving CFC Charts via Multiproject Copy-Paste

Execute the following procedure on the primary Engineering Station to transfer charts authored on an offline laptop:

Step 1: Export and Transfer Project Archive from Offline Machine

  1. On the offline laptop VM, in SIMATIC Manager, select File > Archive....
  2. Choose Multiproject or the specific User Project containing the new charts, select a destination folder, and create the .zip archive file.
  3. Transfer the .zip archive to the central Engineering Station via an approved external drive or secure file transfer protocol.

Step 2: Retrieve the Offline Project into an Isolated Directory

  1. On the central ES, launch SIMATIC Manager.
  2. Navigate to File > Retrieve..., select the transferred .zip archive, and extract it to a temporary staging folder (e.g., D:\Staging\Project_Temp). Never overwrite the production project folder during retrieval.
  3. Open the production multiproject in SIMATIC Manager.
  4. Concurrently, open the retrieved staging project via File > Open > Project.

Step 3: Copy and Paste the CFC Charts

  1. In the staging project tree, navigate to: [AS Station] > [CPU Object] > S7 Program > Charts.
  2. Select the specific new CFC charts (hold Ctrl for multiple selections).
  3. Right-click the selected charts and choose Copy (or press Ctrl+C).
  4. Switch to the production multiproject window, navigate to the target Charts folder (or target Plant Hierarchy folder).
  5. Right-click the folder and select Paste (or press Ctrl+V).

Step 4: Resolve Block Interface and Conflict Dialogs

  1. If the dialog 'Import Block Types' appears, verify that the listed blocks match the target Master Data Library. Select 'OK' to confirm.
  2. If an 'Interface Conflict' prompt appears, investigate whether the block on the source chart has a different timestamp or attribute set. Do not force an overwrite without verifying interface compatibility.
  3. Open the newly pasted CFC charts in the target project. Press F5 to refresh. Verify that chart interconnections to other existing charts are correctly established or need manual reconnecting if source charts had different chart names.

Technical Comparison: Chart Transfer Methods in PCS 7

The following table compares the operational characteristics, safety, and suitability of methods for moving CFC charts:

Engineering MethodNetwork RequirementType Conflict RiskCross-Reference IntegrityRecommended Use CaseCopy-Paste Between Open ProjectsOffline / DisconnectedModerate (requires MDL check)Fully maintained by SIMATIC Manager1 to 5 charts developed offline on mobile laptopMultiuser Engineering (LAN/UNC)Continuous Local NetworkLow (centralized MDL)Real-time centralized synchronizationCollaborative engineering during commissioningRemove / Insert Project from MultiprojectOffline / Split MultiprojectLowRe-synchronized upon multi-project rejoinLarge distributed packages (entire AS programs)Windows Explorer File CopyAnyExtreme (Guaranteed Corruption)Destroyed (corrupts internal pointers)STRICTLY PROHIBITED

Verification

Following the paste operation, perform the following verification and build steps:

  1. Check Runtime Sequence:
    - In CFC Editor, open Options > Customize > Compile/Download... and examine runtime placement.
    - Open the Runtime Editor (Ctrl+Alt+R) and confirm that block instances on the transferred charts are correctly assigned to the intended cyclic interrupt OB (e.g., OB35) and positioned logically within the execution group.
  2. Check Reference Data:
    - In SIMATIC Manager, select the Charts folder and click Options > Reference Data > Display.
    - Verify that there are no unresolved chart connections or overlapping address allocations.
  3. Compile Changes Only:
    - Right-click the Charts folder, select Compile > Charts as Program.
    - Choose Changes only. If the transfer maintained type consistency, PCS 7 compiles without requiring an entire compilation.
  4. Download Changes to Controller:
    - Verify that Download > Changes only is active. This confirms that the chart addition can be loaded into the S7-400 or CPU 410 controller in RUN mode without triggering a CPU STOP.

Limitations and Operational Precautions

Observe the following engineering constraints when transferring charts:
- Never copy CFC charts while any station in the multiproject is currently executing an online download or background OS compilation.
- External chart-to-chart cross-references will be severed if the destination project uses different chart names or hierarchy folders; always review sheet margin pointers after pasting.
- If block versions differ between the laptop and the ES, updating block types may force an unavoidable full AS compilation and CPU STOP. Always synchronize Master Data Libraries prior to offline chart development.

Engineer FAQ

What happens if a block type in the copied chart is missing in the target project?

If the block type is missing in the target S7 program offline block folder, PCS 7 automatically copies the block from the source project into the target project block folder, provided the block exists in the source. However, to maintain architectural consistency, you should always copy the block from the Master Data Library into the target project prior to transferring the chart.

Why does PCS 7 prompt for a full AS compilation after pasting a chart?

A full compilation prompt occurs if: (a) a block type interface on the transferred chart differs from the block version installed in the target CPU, (b) the compiler detected a change in the central database structure, or (c) DB numbers or FC ranges had to be reallocated. To avoid full downloads, ensure both projects use identical Master Data Library versions prior to copying.

Can I copy charts across different PCS 7 major versions (e.g., v8.0 to v8.2)?

Directly copying charts across major versions is not supported without first running the PCS 7 project migration and block update utilities. Pasting charts containing newer system attributes into an older PCS 7 version will result in compilation aborts and missing block icon errors.

Technical References

Related Articles

Related Tags

  • PCS 7 CFC
  • Multiuser Engineering
  • SIMATIC Manager
  • Chart Migration
  • Master Data Library
6 respuestas