Exchange Signals Between S7-400H Controllers with PCS 7 AS-Wide Interconnections
For two supported automation systems in the same PCS 7 project or multiproject, AS-wide interconnections can link CFC block inputs and outputs across CPUs without manually building a GET/PUT data layout. Configure the network in NetPro, make the CFC block-I/O connection between the charts, then compile and load the affected S7 programs. This fits the reported need to transfer Boolean and analog signals, subject to supported data types, CPU/hardware requirements, and the CFC manual's restrictions.
Table of Contents
- Configure the multiproject network
- Create the CFC connection
- Compile and load
- Verify data exchange
- Limitations and Operational Precautions
- Technical References
- Related Articles
- Related Tags
- Verification
- Engineer FAQ
Configure the multiproject network
Place both automation systems in the common project or multiproject and configure their network in NetPro. The PCS 7 Compendium Part A describes the AS-wide interconnection feature as automatically inserting the correct S7 connection between the relevant AS.
Create the CFC connection
Open the source and destination charts in CFC and connect the source block output to the destination block input. The CFC manual describes selecting the two I/Os across charts; the connection appears on the sheet bar as an AS-wide interconnection. Use block I/Os and data types supported by the installed CFC version.
Compile and load
After creating or changing AS-wide interconnections, compile and load the affected S7 programs. The V9.0 SP4 CFC manual warns not to manually delete the generated NetPro S7 connection or change its IDs. Review compiler warnings and address any one-sided or unresolved connections before loading.
Verify data exchange
Monitor the source and destination values online and confirm Boolean and analog values update as expected at the destination. Check the CFC reference data and generated interconnection entries if the connection is unresolved. Test failure/recovery behavior under controlled conditions.
Limitations and Operational Precautions
CFC documentation specifies limits and exclusions, including no F-program/F-block AS-wide interconnections and no connections to addresses or runtime groups. Cycle time depends on cyclic interrupt OB configuration; the manual gives 200 ms as the fastest possible cycle. Check S7-400H CPU/firmware and communication processor requirements for the installed PCS 7 release.
Technical References
- Siemens, CFC for SIMATIC S7 V9.0 SP4 Function Manual, section 10.8, AS-wide interconnections and compiling/loading: https://support.industry.siemens.com/cs/attachments/109779389/s7cfcs7b_en-US.pdf
- Siemens, PCS 7 Compendium Part A – Configuration Guidelines V9.1, section 7.2.2, AS-OS communication and AS-wide interconnections: https://support.industry.siemens.com/cs/attachments/109809015/pcs7_compendium_part_a_en-US_en-US.pdf
Related Articles
Related Tags
Verification
Verify configuration and observable runtime behavior against the intended process requirements.
Engineer FAQ
What is an AS-wide interconnection? It links CFC block I/Os located on different automation systems within a common project or multiproject.
Is an AS-wide link different from GET/PUT? Yes. CFC AS-wide interconnections are configured between chart block I/Os and PCS 7 generates their network communication; GET/PUT are separately programmed communication function blocks.
What must be configured first? The CPUs must be in the common project or multiproject and the network must be configured in NetPro.
Can I connect a chart input directly to a block on another AS? The documented setup allows selecting the source and destination block I/Os in open CFC charts, subject to supported types and system limits.
Can AS-wide interconnections carry safety data? The cited CFC manual states F programs and F blocks are not supported for AS-wide interconnections.
Are all S7 CPU families supported? No. The CFC manual states only S7 target systems are supported and S7-300 CPUs are not supported in this function.
What happens after creating the connection? The affected S7 programs must be compiled and loaded; do not manually delete or change generated NetPro connection IDs.
Can runtime groups be AS-wide connected? No. The CFC manual says AS-wide interconnections to addresses and runtime groups are not possible.
What cycle time is available? The cited CFC manual documents a fastest possible AS-wide interconnection cycle of 200 ms; exact timing depends on configured cyclic interrupt OBs.
Is AS-wide interconnection the right choice for two S7-400H CPUs? It is a documented PCS 7 option for cross-AS block I/O in a multiproject, but CPU, firmware, communication hardware and safety restrictions must match the applicable release documentation.