Troubleshooting OS Project Download Failures and PG-PC Station Interface Mismatches in PCS 7

Troubleshooting OS Project Download Failures and PG-PC Station Interface Mismatches in PCS 7

When OS project downloading fails and a yellow arrow appears over the target PC station in SIMATIC Manager in PCS 7 V9.0 SP3, the failure is caused by an interface assignment mismatch or station name divergence between the Engineering Station and the target OS. To resolve this: open 'Set PG/PC Interface' on the ES and assign Access Point 'S7ONLINE' to the physical Terminal Bus network adapter (TCP/IP), ensure the station name in Station Configuration Editor matches SIMATIC Manager identically, and verify that the target OS path uses a fully qualified UNC network share.

Table of Contents

• Executive Summary
• Architecture and Fundamental Mechanics
• Step-by-Step Implementation Procedure
• Verification
• Limitations and Operational Precautions
• Engineer FAQ
• Technical References
• Related Articles
• Related Tags

Executive Summary

Deploying operator station projects from the central Engineering Station (ES) across the Terminal Bus requires precise alignment between the physical communication adapters, STEP 7 Station Configuration Editor settings, and SIMATIC Manager station topologies in SIMATIC PCS 7 (V8.0 through V9.1). A classic visual symptom of communication misalignment is a yellow arrow displayed over a PC station in SIMATIC Manager Component View, indicating that the engineering tool cannot resolve the target station interface. This article details the mechanics of PC station symbolic routing, PG/PC interface configuration, and step-by-step resolution of transfer failures.

Architecture and Fundamental Mechanics

Station Configuration Architecture and PG/PC Interface Routing Mechanics:

• The Significance of the 'Yellow Arrow' in Component View:
• In SIMATIC Manager, a PC station icon represents a virtual backplane hosting applications (WinCC Appl.) and communication processors (CPs).

• When a yellow arrow appears over the PC station icon, it indicates that the Engineering Station cannot establish a direct hardware link or symbolic relationship with that station:

  1. Internal Loopback / Wrong Access Point: The local Access Point S7ONLINE in Windows 'Set PG/PC Interface' is configured to an internal driver (PC internal.local.1) or simulation adapter rather than the physical Terminal Bus network interface card.
  2. Station Name Mismatch: The station name declared in SIMATIC Manager differs from the station name configured in the Station Configuration Editor on the target PC.
  3. Simulation State: The project is configured for S7-PLCSIM / OS Simulation rather than physical plant hardware.

• Station Configuration Editor and Virtual Backplane:

• Every SIMATIC PCS 7 PC station operates a virtual backplane managed by the Station Configuration Editor (Station Configurator).
• Index 1 typically hosts the WinCC application (WinCC Appl.), while Index 2+ hosts network adapters (IE General or CP 1623).

• The station name assigned in Station Configuration Editor must match the name of the PC station object in SIMATIC Manager character-for-character (case-sensitive).

• Universal Naming Convention (UNC) Target Paths:

• The ES writes project data across the network via standard SMB protocol. The destination path defined in OS Properties must follow standard UNC syntax (e.g. \OS_SRV1\WinCC_Projects\OS_SRV1.mcp), never a local mapped drive letter (e.g. Z:\...).

Step-by-Step Implementation Procedure

Step-by-Step Procedure to Align Interfaces and Resolve OS Download Failures:

1. Configure PG/PC Interface on the Engineering Station:
   - Open Windows Control Panel on the ES; open Set PG/PC Interface.
   - Under 'Access Point of the Application', select S7ONLINE (STEP 7).
   - In the interface parameter assignment list, select your physical Terminal Bus network adapter with the TCP/IP protocol:
   TCP/IP -> [Network_Card_Name] (Auto) or TCP/IP -> [Network_Card_Name].1.
   - Do NOT select PC internal (local) or ISO protocol variants.
   - Click OK to apply.
2. Align Station Configuration Editor on Target OS Server:
   - On the target OS Server, open the Station Configuration Editor from the Windows taskbar icon.
   - Inspect the Station Name displayed in the top banner (e.g. OS_SRV1).
   - In SIMATIC Manager Component View on the ES, verify that the PC station is named identically (OS_SRV1).
   - If names differ, click Station Name... in Station Configuration Editor and update it to match SIMATIC Manager.
3. Verify Target OS UNC Path Configuration:
   - In SIMATIC Manager Component View, right-click the OS project object -> select Object Properties.
   - Select the Target OS and Standby OS Computer tab.
   - In the 'Path to the target OS computer' field, enter the verified UNC network path:
   \OS_SRV1\WinCC_Projects\OS_SRV1.mcp
   - Click Browse; verify that SIMATIC Manager connects to the remote folder without authentication errors.
4. Execute Station Configuration Download (If Station Backplane Changed):
   - In SIMATIC Manager, select the PC station object -> select PLC -> Configure....
   - Select target computer -> click Configure -> click OK to download virtual backplane components.
5. Execute OS Project Download:
   - Right-click the OS project -> select PLC -> Download.
   - Select Scope: Entire OS; click OK to complete project transfer.

Verification

Verification Procedure:
1. Icon Status Verification: In SIMATIC Manager Component View, confirm that the yellow arrow has disappeared from the PC station icon, indicating healthy interface binding.
2. Download Execution Check: Confirm that the download dialog transfers project tables without network timeout warnings.
3. Target Project Inspection: On the OS Server, launch WinCC Explorer; confirm that the downloaded project opens cleanly and displays the configured computer name in project properties.

Limitations and Operational Precautions

Operational Precautions and Network Integrity Rules:
- Avoid Mapped Drive Letters: Never use mapped network drives (e.g. Z:\WinCC); Windows services execute under system contexts where user drive mappings do not exist, causing transfer failures.
- Target Folder Sharing Discipline: Always share the parent project directory with the local SIMATIC HMI group on the OS Server.
- Close WinCC Explorer: Ensure WinCC Explorer is not open on the target OS Server during full project downloading.

Engineer FAQ

What does the yellow arrow over a PC station in SIMATIC Manager mean?

It indicates that the station is pointing to an internal loopback adapter, the PG/PC interface is misconfigured, or the station name differs from the Station Configuration Editor.

Which access point must be configured in 'Set PG/PC Interface'?

Access point S7ONLINE (STEP 7) must be assigned to the physical Terminal Bus network adapter with TCP/IP protocol.

Why should I use UNC paths instead of mapped drive letters for OS download?

Windows services (DCOM and RPC) run under system credentials that cannot resolve user-mapped network drive letters. UNC paths (\Server\Share) are mandatory.

What tool configures the virtual backplane on an OS Server?

The Station Configuration Editor configures the virtual backplane, applications, and CPs on a PC station.

Can I download an OS project across a wireless connection?

Downloading OS projects over wireless links is strictly unsupported by Siemens due to the risk of database corruption during packet drops.

Technical References

• SIMATIC Process Control System PCS 7 OS Process Control Manual
• SIMATIC Process Control System PCS 7 PC Configuration and Authorization Manual
• SIMATIC Process Control System PCS 7 Engineering System Manual

Related Articles

• Diagnosing OS Project Download Errors and Verifying SQL Server Service Dependencies in PCS 7
• Managing PCS 7 Project Revisions, Archiving Workflows, and Windows ProgramData Roles
• Migrating a SIMATIC PCS 7 OS Single Station to a Redundant Client-Server Architecture

Related Tags

• PG-PC Interface
• OS Download
• Station Configuration Editor
• Yellow Arrow
• Terminal Bus