Why AS Connections and Tags Fail to Appear in OS Compilation After Adding a New Controller

In SIMATIC PCS 7, when a newly added Automation Station (AS) does not appear in the OS compilation wizard or fails to transfer tags to WinCC, the primary cause is that the new AS contains zero CFC blocks with active Operator Control and Monitoring attributes (s7_m_c := 'true'), the Plant Hierarchy folders of the new AS have not been assigned to the target OS, or the Industrial Ethernet subnets are unmerged in NetPro. To resolve this, ensure the subnets are merged under a common name in NetPro, assign the Plant Hierarchy folder to the OS in Plant Hierarchy Settings, and verify that at least one OCM-capable block exists in the new charts.

Prerequisites for AS Inclusion in OS Compilation

When expanding an operational PCS 7 facility, adding a new Automation Station (AS) to an existing multiproject is a routine task.

However, engineers frequently encounter a scenario where the new AS has been configured in HW Config, network connections are established in NetPro, and new graphics are created in WinCC—yet when launching the Compile OS wizard:
* The connection to the new AS is completely missing from the Select network connection step.
* Or, the AS is selectable, but the compile completes instantly with zero tags transferred, leaving process graphics unlinked.

This behavior occurs because the PCS 7 OS compilation engine enforces strict structural preconditions across three separate project dimensions: Network Routing (NetPro), Plant Hierarchy (PH), and Block OCM Metadata (s7_m_c).

Root Causes of Missing AS Connections in the OS Compilation Wizard

To resolve the issue, evaluate the three mandatory criteria required by the OS compiler:

1. The Zero-OCM Parameter Trap

The OS compiler does not establish communication channels or transfer data for empty controllers. It scans the AS chart folder specifically for blocks containing parameters with the attribute s7_m_c := 'true' (Operator Control and Monitoring).
* If the newly added AS is still under development and contains only basic logic (or charts that have not yet had APL technological blocks inserted), the OS compiler detects zero tags to transfer.
* In many cases, the compiler completely omits the AS from connection generation because there is literally nothing to display in WinCC!

2. Missing Plant Hierarchy OS Assignment

In SIMATIC Manager Plant View, every hierarchy folder containing CFC charts must know which WinCC OS Server is responsible for visualizing its data. If a new AS is inserted into the Component View but its corresponding Plant Hierarchy folders have not been assigned to the target OS under Plant Hierarchy -> Settings, the OS compiler ignores the new station.

3. Unmerged Subnets in NetPro

When an AS is added, its Ethernet interface is often assigned to a local subnet object (e.g., Ethernet(1)). If the OS Server resides on Ethernet-Wide, the two subnets remain logically segregated. The OS compiler cannot route communication between stations on different unmerged subnets. Subnets must be merged in NetPro under a single shared subnet.

Comparison Table - OS Compilation Prerequisites and Failure Modes

The following table details the three critical pillars of PCS 7 OS compilation and the symptoms that manifest when each is misconfigured.

Engineering PillarRequired ConfigurationFailure Symptom if MissingVerification LocationBlock OCM MetadataAt least one block with s7_m_c := 'true' in CFCAS compiles with 0 tags transferred; graphics unlinkedCFC block properties / I&O tablePlant Hierarchy AssignmentHierarchy folder assigned to target OSAS charts completely omitted from OS compilationPlant Hierarchy -> Customize / SettingsNetPro Subnet MergingAll stations bound to shared merged subnetAS does not appear in connection selection dialogNetPro -> Edit -> Merge/Unmerge SubnetsNamed S7 ConnectionValid S7 / S7 Fault-Tolerant connection definedOS compile warns of missing communication pathNetPro connection table

Step-by-Step Resolution and Engineering Workflow

To resolve the missing AS connection and successfully transfer tags to the OS, execute the following engineering sequence:

Merge Industrial Ethernet Subnets in NetPro:
* Open NetPro.
* In the menu, select Edit -> Merge/Unmerge Subnets -> Industrial Ethernet.
* Locate the subnet associated with the new AS and merge it into the main plant network (typically named Ethernet-Wide or Plant_Bus).
* Verify that both the OS Server communications processor (e.g., CP 1623) and the new AS communications interface (e.g., CP 443-1 or CPU PN port) are attached to this shared subnet.
* Save and compile network routing in NetPro.
Assign the Plant Hierarchy to the Target OS:
* Switch to the Plant View in SIMATIC Manager.
* Locate the top-level hierarchy folder representing the new plant unit.
* Right-click the folder and select Plant Hierarchy -> Settings.
* In the dialog, verify that the Assigned OS dropdown points to the target WinCC OS Server.
* If nested hierarchy folders exist, ensure the assignment is distributed down the tree.
Ensure OCM-Capable Blocks Exist in CFC:
* Open a CFC chart inside the new AS hierarchy folder.
* Drag at least one standard APL block with OCM attributes (such as MonAnL, VlvL, or MotL) onto the chart.
* Ensure that the block has a valid name and that at least one technological parameter (e.g., PV_Out) has the OCM checkmark enabled.
* Perform a quick CFC compile (Scope: Changes only).
Execute OS Compilation Wizard:
* In Component View, right-click the OS project and select Compile.
* Step through the wizard:
- In the Select AS dialog, verify that the new AS is now listed with a checkmark.
- In the Select network connection dialog, select the desired connection path (e.g., Named S7 connection or ISO).
- Select Scope: Changes (or Entire OS if first compile).
- Check Tags and messages and Create/update block icons.
- Click Compile to execute.

Verification

Confirm that the AS connection and tags are successfully integrated into WinCC:

Verify WinCC Tag Management:
* Open the OS project in WinCC Explorer.
* Expand Tag Management -> Named Connections.
* Confirm that a connection group for the new AS exists and displays active tags corresponding to the CFC blocks.
Verify OS Compilation Transfer Log:
* In SIMATIC Manager, open the OS compile log (Options -> Logs -> Compile OS).
* Confirm that the log lists the new AS, reports the exact count of tags created, and concludes with 0 Errors, 0 Warnings.
Verify Graphic Runtime Connection:
* Open a process picture containing a block icon for the new AS in Graphics Designer.
* Verify that the block icon connects dynamically to the new tag prefix without @ substitution errors.

Limitations and Operational Precautions

Avoid Compiling Empty Projects: Never initiate an OS compile for a new AS before configuring basic I/O and technological blocks; doing so creates empty connection structures that can confuse WinCC tag management.
Redundant OS Compilation: In redundant OS Server configurations, always compile the master OS Server project; the standby OS Server project is synchronized automatically during compilation.
S7 Connection Naming Consistency: Do not rename the S7 connection in NetPro after initial OS compilation without performing a full OS compilation, as WinCC tag paths will point to the obsolete connection name.

Engineer FAQ

Why did the OS compile say successful but 0 tags were generated?

This occurs when the AS charts contain no blocks with the attribute s7_m_c := 'true'. Standard logic gates (AND, OR, ADD) do not have OCM attributes. You must place at least one technological block (like MonAnL or OpDi01) to generate OS tags.

Can an AS connect to multiple WinCC OS Servers simultaneously?

Yes. Different hierarchy folders within the same AS can be assigned to different OS Servers, or the same AS can be compiled into multiple OS Single Stations or Server pairs.

What is the difference between 'Named Connection' and 'ISO' in OS compile?

'Named Connection' uses the symbolic connection defined in NetPro (mandatory for fault-tolerant S7-REDCONNECT). 'ISO' uses direct MAC addressing without symbolic routing.

Do I need to compile the OS if I only added an unlinked CFC block?

If the newly added block has s7_m_c := 'true' and needs to be visualized on WinCC, an OS compilation is mandatory. If the block is purely internal logic with no OCM attributes, OS compilation is not required.