Close PCS 7 CFC Textual Interconnections to DB Addresses

You can bulk-close textual interconnections only when their text resolves to a valid CFC chart/block output path in the current chart folder. Siemens' CFC manual states that the folder-level command cannot close a single entry and leaves invalid or arbitrary references open. If the intended target is a shared DB address, configure it with CFC's Interconnection to Address... workflow instead of treating it as a CFC path reference.

Why the bulk close command may leave connections open

CFC's bulk command closes textual path references only when the referenced block/chart output exists and the path is valid. A textual request that is an arbitrary string, a path to a missing I/O, or an incompatible reference remains open and is reported in the log. Therefore, a DB-related entry may not close simply because the data block exists: the text must be a resolvable CFC source path, or the input must be configured as a shared-address interconnection.

Classify the open entries first

Open the current chart folder's textual-interconnection list and inspect the literal text and target input for representative entries. A path reference identifies a CFC chart/block output, such as the documented chart\block.I/O form. A string that names a global/shared DB address is a different connection type. Check whether the referenced source chart, block I/O, data type and path are present in the current project/chart folder before running the bulk close again.

Close valid CFC path references in bulk

When all intended CFC partners exist in the chart folder:

Open a chart in the relevant chart folder.
Run Options > Make Textual Interconnections (the wording may be shown as “Close Textual Interconnections” in the installed release).
Review the generated textual-interconnection log. Siemens documents that the command closes all resolvable textual interconnections in the current chart folder; it cannot close individual entries.
For each remaining entry, use the log/list's Go To function to locate its target and correct the missing or invalid source path, type, or I/O reference. Then rerun the folder-level close operation.
Confirm the entries intended as CFC links are converted to real interconnections before compiling.

Convert a textual entry to a DB/shared address

If the intended destination is a shared DB address rather than a CFC block/chart output, select the affected input or its textual entry and use the CFC Interconnection to Address... workflow to create an address interconnection. Specify the actual project-approved address and confirm the target type and address mapping. This is a deliberate per-connection configuration decision; do not substitute arbitrary marker-memory addresses merely to eliminate textual strings.

Review the log and compile safely

The CFC function manual identifies the textual-interconnection log under Logs > Textual Interconnections. It also warns that unresolved textual connections can still compile: for an open input, the block type's default value is used; an open output connection is ignored. Treat any remaining open entry as an engineering defect unless its intended behavior is explicitly understood and accepted. Review the compile log and project changes before any download.

Verification

After closing or reconfiguring the intended entries, inspect the textual-interconnection list/log for unresolved items and confirm each converted target is the intended CFC I/O or shared address. Compile the affected program and review the compile log for remaining textual connections. Verify the resulting signal path through project cross-reference/monitoring and the approved test procedure before downloading changes.

Limitations and Operational Precautions

The ticket states PCS 7 V9.1 SP1 but does not state the installed CFC component version. The directly opened Siemens manual is CFC for SIMATIC S7 V9.0 SP1; confirm exact command labels and behavior in the CFC documentation installed with the V9.1 SP1 system. Make Textual Interconnections works on the current chart folder and cannot close individual entries. Do not compile or download while unresolved entries may cause default input values or ignored output connections, unless that behavior has been deliberately evaluated and approved.

Engineer FAQ

Can CFC close every textual connection automatically? No. The bulk function closes resolvable path references in the current chart folder; arbitrary requests, missing paths and invalid I/Os remain open.

Can the bulk command close one selected connection? The Siemens CFC manual says the function closes all textual interconnections in the current chart folder and does not close single entries.

How should a DB address be connected? Use the CFC shared-address Interconnection to Address... workflow with the approved DB address and data type.

What happens if I compile with an open textual connection? Siemens documents that an open input uses the block type's default value and an open output is ignored; a warning is logged.

Where do I find why a connection stayed open? Review the Textual Interconnections log and use its listed chart/input reference to locate the unresolved item.

Technical References

CFC for SIMATIC S7 (V9.0 SP1), Function Manual, 10/2017, A5E41356073-AB, §10.8.8, pp. 147–150 — opened and reviewed; defines resolvable path references, entries that cannot be closed, shared-address conversion, folder-level close behavior and compilation effects.

PCS 7 CFC textual interconnections

PCS 7 CFC shared DB address connections

Close PCS 7 CFC Textual Interconnections to DB Addresses