Resolving CFC Error 1739:460 'Operand Not Permitted' When Copying Charts Between PCS 7 Controllers

CFC error 1739:460 'Insert (1739:460) operand not permitted' occurs when copying a CFC chart containing symbolic I/O connections into a target controller whose Symbol Table contains an incompatible definition for that symbol name. The conflict arises when the symbol in the target PLC is assigned to a different data type (such as BOOL instead of WORD), points to an address outside the configured process image, or conflicts with hardware channel allocations. To resolve the error, open the target PLC Symbol Table, verify the data type and address assignment of the referenced symbol, reconcile any type mismatches with the chart's channel driver input requirements, and re-execute the copy operation.

Executive Summary

In SIMATIC PCS 7 multiproject engineering, modular design frequently involves copying standardized CFC charts (such as analog input loops or valve drivers) between different AS stations. However, when an interconnected chart references symbolic names mapped to field addresses, CFC validates the incoming symbol against the target station's local Symbol Table. If the target project already defines the identical symbol name with an incompatible operand data type (for example, mapping PT001 as a discrete input bit I 0.0 instead of an analog word IW 10) or binds it to an address unsupported by the channel block parameter, CFC immediately halts the paste operation with error 1739:460. Resolving this issue requires strict operand type reconciliation across the multiproject symbol tables or temporary disconnection of the hardware address prior to chart migration.

Architecture and Fundamental Mechanics

The PCS 7 Continuous Function Chart (CFC) editor enforces strict type safety and operand validation during chart instantiation and cross-project copy routines. When a block input—such as parameter PV_In on an FbAnIn or Pcs7AnIn channel driver—is linked to an absolute address via a symbolic name, the connection is governed by three synchronized metadata layers:

The Block Parameter Data Type: The channel driver input defines a fixed STEP 7 data type (e.g., WORD or INT for raw peripheral inputs PEW, or REAL for engineering values).
The Local Symbol Table (Symbols): Each AS program contains its own local symbol database mapping alphanumeric tags (e.g., FIT_101) to absolute memory addresses (IW 512) and data types (WORD).
The Hardware Configuration (HW Config): HW Config allocates specific address ranges to installed I/O modules and defines whether an address resides within the automatic process image partition (PIP) or requires direct peripheral addressing (PIW / PEW).

When a CFC chart is copied from PLC A to PLC B, CFC parses all external symbolic interconnections. If symbol FIT_101 already exists in PLC B's Symbol Table but is defined as BOOL (pointing to I 10.0), CFC detects a type violation between the WORD expected by FbAnIn.PV_In and the BOOL defined in PLC B. Because CFC cannot automatically alter an existing symbol definition in the target project without risking corruption of other logic, it raises error Insert (1739:460) "FIT_101" operand not permitted and blocks chart insertion. A similar error occurs if the symbol points to a non-existent bit within a word or an address exceeding the target CPU's process image boundary.

Step-by-Step Implementation Procedure

Follow these engineering steps to diagnose and resolve error 1739:460 when copying CFC charts:

Identify Conflicting Symbols: Note the exact symbol name displayed in the CFC error dialog Insert (1739:460) "<symbolname>" operand not permitted.
Inspect the Source Symbol Definition: In the source PLC under SIMATIC Manager, navigate to [Source AS] > CPU 41x > S7 Program > Symbols. Locate the referenced symbol and record its exact Address, Data Type, and Comment (e.g., Name: FIT_101, Address: IW 512, Data Type: WORD).
Inspect the Target Symbol Definition: Open [Target AS] > CPU 41x > S7 Program > Symbols. Search for the identical symbol name. Check whether the target symbol already exists with a different data type (e.g., BOOL), an invalid address, or an conflicting memory area.
Reconcile the Target Symbol Table:
* If the symbol was mistakenly defined in the target PLC: Delete or rename the conflicting entry in the target Symbol Table.
* If the target PLC requires a different symbol name: In the source chart, either rename the symbolic interconnection or temporarily delete the symbolic link to the block parameter before copying.
* If the hardware address differs: Ensure the target HW Config has the appropriate analog/digital module configured and enter the correct target address and data type (WORD for analog, BOOL for digital) into the target Symbol Table.
Alternative Decoupling Method for Chart Templates:
* If copying a chart template between disparate projects where target I/O addresses are not yet established, open the source chart, delete the direct symbolic operand connection from the driver block parameter (leaving the block input open), and then copy the chart.
* Paste the chart into the target plant hierarchy, and reconnect the driver block to the target symbol using the target station's Symbol Table.
Save, Recompile, and Validate: Save the target Symbol Table, paste the CFC chart into the target chart folder, and execute Chart > Check Consistency to ensure all interconnections resolve cleanly.

Verification

Confirm chart insertion by pasting the CFC chart into the target hierarchy folder without error popups. Open the pasted chart, locate the channel driver block, and verify that the symbolic interconnection appears highlighted in yellow/green with the correct symbol name, address, and data type matching the target HW Config. Run Chart > Check Consistency in CFC; verify zero errors. Finally, execute PLC > Compile > Charts as Program with 'Generate module drivers' enabled to confirm that diagnostic and driver blocks compile without warnings.

Limitations and Operational Precautions

Ensure that target symbol addresses do not exceed the Process Image Partition (PIP) assigned to the cyclic interrupt OB where the CFC chart executes (e.g., OB35). If an address falls outside the process image and the driver expects process image access (IW instead of PIW), runtime value updates will fail. Avoid manual editing of symbol tables during active multi-user engineering sessions without coordinating with other engineers.

Engineer FAQ

Why does error 1739:460 occur even when the symbol name does not exist in the target PLC?

The error can also trigger if the source chart references an absolute operand format that is invalid for the target CPU architecture, or if the block parameter requires a specific elementary type (e.g., INT) while the inserted symbol is assigned a user-defined type (UDT) or incompatible standard type.

Can I bypass the error by copying the entire chart folder at once?

No. When copying multiple charts or an entire hierarchy folder, CFC performs the same operand validation for every chart. If any chart contains an invalid or conflicting symbol, the batch copy operation will halt at that specific chart.

Does renaming the symbol in the source chart affect the block algorithm?

No. CFC interconnections to process hardware rely on the underlying absolute address or symbolic binding. Renaming the symbol updates the reference in the Symbol Table and the chart display without altering the block execution logic.

What is the difference between error 1739:460 and error 1739:60451?

Error 1739:460 indicates an operand data type or address permission failure during symbolic connection insertion, whereas 1739:60451 indicates an internal block type interface mismatch or obsolete parameter assignment structure within the chart.