Resolving Siemens PC Station Configuration Console Mode Errors

Overview: Siemens PC Station Configuration Console Mode Failure

Engineers commissioning a SIMATIC PC Station frequently encounter a Configuration Console in which the mode selector for a virtual module (typically the OPC Server entry, the IE General entry, or a CP entry) refuses to switch from PG operation to Configuration — or the dropdown is greyed out entirely. The cause is rarely a defect in the SIMATIC NET installation. In nearly every documented case the Station Configuration Editor on the PC contains a runtime configuration that no longer matches the offline HW Config inside the STEP 7 / TIA Portal project. Because the Configuration Console reads its mode list from the Station Configuration Editor, a mismatch silently disables the mode change.

This reference documents the complete diagnostic and recovery procedure for this failure mode on STEP 7 V5.5 + SIMATIC NET V8.x and on TIA Portal V13–V17 with SIMATIC NET V12–V16. It also covers the alternative runtime architecture introduced in TIA Portal V15.1 in which the OPC Server is hosted directly inside the project and the Configuration Console mode selector is no longer required.

Reference documentation: Siemens Industry Online Support, Siemens Industrial Communication product page, SIMATIC PC-based Control overview.

PC Station Architecture and Component Roles

A Siemens PC Station is a software-defined automation node that runs entirely on a Windows PC. It exposes the same slot / index model as a physical S7-300 / S7-400 rack so that the rest of the STEP 7 project can treat the PC as if it were a real PLC. The three tools that cooperate to build this image must be understood individually before the failure mode makes sense.

The slot numbering inside HW Config (STEP 7 V5.x style) is fixed by convention:

• Index 1 — OPC Server (mandatory for any OPC-based data exchange)
• Index 2 — Industrial Ethernet interface (either IE General for Softnet, or a hardware CP such as CP 1613 A2, CP 1623, CP 1628)
• Index 3 — Application slot (WinCC, WinCC flexible, SIMATIC BATCH, user applications)
• Additional PROFIBUS CPs (CP 5611, CP 5611 A2, CP 5613 A2, CP 5614 A2, CP 5623, CP 5624) appear at index 4+ as required

If the HW Config in the engineering project lists OPC Server at index 1 and IE General at index 2 but the Station Configuration Editor on the target PC only knows IE General, the Configuration Console refuses to toggle the mode on the missing OPC Server entry because no runtime slot exists for it. This is the precise scenario reported in the field report.

Configuration Console vs. Station Configuration Editor vs. HW Config

The three tools are frequently confused because they all live in the same Start menu under SIMATIC / SIMATIC NET. The data flow between them is strictly one-way:

Figure 1 — Data flow between HW Config, the on-disk INI file, Station Configuration Editor, and Configuration Console.

HW Config is the source of truth in the offline project. The PC Station is added with the catalog ("SIMATIC PC Station" → "User Object" → "PC Station" in SIMATIC Manager). Slots are filled from the catalog and connected to the S7 subnet in NetPro. When the configuration is compiled and downloaded to "PC internal", STEP 7 writes a binary configuration file (S7PCSTSR.INI on the PC, located under the SIMATIC NET install path) that the Station Configuration Editor reads at startup.

Station Configuration Editor is a runtime status view. It does not edit anything — it only displays what the PC Station believes is installed at each index. Each row shows:

• Index number
• Module type (OPC Server, IE General, CP xxxx, Application)
• Status icon (green check, yellow triangle, red X)
• Configured / Not configured state
• Diagnostic text (visible in the Status column on right-click → Properties)

Configuration Console is the mode selector. It enumerates the modules detected by the Windows driver layer and the SIMATIC NET service and lets the user pick one of three operating modes for each entry. It does not write the slot map — it only writes the operating mode of an already-enumerated module.

Root Cause: HW Config and Station Configuration Editor Mismatch

The classic mechanism producing the failure is a mismatch between the slot map written by HW Config and the slot map expected by the runtime services. The discussion thread identifies the precise cause:

The HW config does not match Station configuration editor. Index 1 is OPC and index 2 is IE general. Change HW config and download it to PC (using PC internal).

This produces the following observable symptoms:

1. Station Configuration Editor shows only one entry (typically IE General or the Softnet driver) instead of the expected two (OPC + IE).
2. The OPC Server row is absent, or it shows a red X with diagnostic text "not configured" or "invalid".
3. Opening Configuration Console reveals that the only available mode for the visible module is "PG operation" — the "Configuration" option is either greyed out or causes the change to revert immediately after the OK button.
4. OPC Scout V10 cannot establish any connection because the OPC Server process sees no valid configuration.
5. SIMATIC NET diagnostic files in the install path show entries referencing missing slot indices.

The underlying reason is that the configuration file on the PC (S7PCSTSR.INI) does not contain an OPC Server entry. This file is overwritten only when HW Config is downloaded — manual edits or Configuration Console changes do not add new slots.

Diagnostic Procedure: Reading Station Configuration Editor Status

Before opening HW Config, capture the current state from the PC so that any deviation is documented. The diagnostic should be run as the same Windows user that owns the SIMATIC NET services (typically a domain admin or the user configured during SIMATIC NET installation), because the SCE refuses to write diagnostic logs for restricted users.

1. Open Station Configuration Editor from Start → SIMATIC → SIMATIC NET → Station Configuration Editor.
2. Note every row visible under "Index / Module / Status". A healthy PC Station with OPC + IE shows at minimum two rows with green check icons.
3. Right-click each row and choose Properties. The Properties dialog shows the diagnostic text in the lower pane. Record any text containing "not configured", "invalid", "wrong target", or "module missing".
4. Close the SCE. Open the file %ProgramFiles%\Siemens\Automation\SIMATIC_NET\cfg\S7PCSTSR.INI (or the equivalent path under TIA Portal / SIMATIC NET V12+) in Notepad. The file is a plain-text INI; every [Module] section should correspond to a row in the SCE.
5. Compare the [Module] sections in the INI against the HW Config slot map. Any missing section = missing runtime module.
6. If the SCE shows no OPC row but the INI contains an OPC section, the SIMATIC NET OPC service may be stopped. Restart it from services.msc → "SIMATIC NET OPC Server" / "S7OPCSRV".
7. Open Configuration Console and note which mode is currently selected for each module. PG Operation is the default for IE General after a fresh install; Configuration is required for any data traffic.

For deeper diagnostics, the SIMATIC NET trace tool S7Trace32.exe (Start → SIMATIC → SIMATIC NET → Commissioning → Trace) can be started with the "PC Station" preset to log every configuration event as it occurs.

Step-by-Step Resolution: Rebuilding the PC Station Configuration

The recovery procedure is identical for STEP 7 V5.5 and for TIA Portal V13–V17 except for menu paths. The sequence is: verify prerequisites, rebuild the offline HW Config, compile and download to PC internal, restart the SIMATIC NET services, then change the Configuration Console mode.

Prerequisites

• STEP 7 V5.5 SP4 or later (recommended: current K5.5.x patch) with SIMATIC NET V8.2 SP1 or later — see Siemens Industry Online Support for current patch levels.
• TIA Portal V13 / V14 / V15 / V15.1 / V16 / V17 with the matching SIMATIC NET support package.
• Local administrator rights on the target PC (the SIMATIC NET services must be installable, restartable, and writable).
• A working STEP 7 / TIA Portal project that contains the PC Station object, or the credentials to create one.
• The Windows computer name of the target PC — the PC Station name must match it exactly.

STEP 7 V5.5 Procedure

1. In SIMATIC Manager, open the project that owns the PC Station. If the PC Station does not exist yet, right-click the project, choose Insert New Object → SIMATIC PC Station, and give it the exact same name as the Windows computer name of the target PC (case-sensitive on some service packs).
2. Open HW Config on the PC Station (double-click "Configuration").
3. From the hardware catalog (View → Catalog), open SIMATIC PC Station → CP Industrial Ethernet and drag IE General into slot 2. If a hardware CP is used instead, drag the exact catalog part number — for example 6GK1 161-3AA01 (CP 1613 A2) or 6GK1 162-3AA00 (CP 1623) — into slot 2 and remove the IE General entry.
4. Open SIMATIC PC Station → User application in the catalog and drag OPC Server into slot 1.
5. Open NetPro (button on the toolbar). Connect the OPC Server to an S7 subnet if data traffic targets S7-300/400 PLCs, or to a PROFINET subnet for S7-1500. The subnet must match the subnet configured in the S7 project for the target PLC.
6. Save and compile the PC Station: Station → Save and Compile. The action generates the S7PCSTSR.INI and embeds it in the XDB file used for download.
7. Download: PLC → Download to PC Station. The "Select Target Station" dialog must show the target PC as "PC internal" — if it shows nothing, verify that the SCE on the target PC is open and that the PC Station name matches the Windows computer name.
8. Confirm the download with "OK". STEP 7 writes the new S7PCSTSR.INI to the SIMATIC NET install directory on the target PC.
9. Close HW Config. Re-open Station Configuration Editor on the target PC. The OPC Server row at index 1 and the IE General row at index 2 must now both show a green check icon.
10. Open Configuration Console. Right-click the OPC Server row and change the mode from "PG operation" to "Configuration". Confirm with OK. Repeat for the IE General entry if it is not already in Configuration mode.
11. Restart the SIMATIC NET services in the specified order: first "SIMATIC NET Configuration Service", then "S7OPCSRV" (the OPC Server service), then any application services (e.g., WinCC). Restarting in the wrong order can re-trigger the original fault.

TIA Portal V13–V17 Procedure

1. In the TIA Portal project tree, expand the PC Station. If no PC Station exists, add one via Devices & Networks → Add new device → PC system → SIMATIC PC station.
2. Open the Device view of the PC Station. The slot view is identical to HW Config.
3. From the hardware catalog, drag OPC Server into slot 1 and IE General (or the appropriate CP) into slot 2. Catalog path: PC systems → Communication modules → OPC Server / IE General.
4. Open the Network view and connect the OPC Server to the PROFINET / Industrial Ethernet subnet that carries the target PLC.
5. Compile the PC Station: right-click the device → Compile → Hardware (rebuild all).
6. Download: select the PC Station in the project tree and click Download to device. Use the "PG/PC interface" dropdown to select the target PC's S7ONLINE access point. Confirm with "Load".
7. On the target PC, restart the SIMATIC NET services and re-open Station Configuration Editor. Verify both rows show green status.
8. Open Configuration Console and switch the mode of every row from "PG operation" to "Configuration".

Module Modes in Configuration Console

The Configuration Console exposes three operating modes per module. They are not equivalent and selecting the wrong one is a frequent secondary failure cause.

The mode is stored per module under HKEY_LOCAL_MACHINE\SOFTWARE\Siemens\SIMATIC_NET\IE\Mode (or the equivalent Softnet key for Softnet-based IE General). Inspecting this registry hive is useful for scripting large rollouts.

OPC Server and IE General Module Indexing

Index assignment is not arbitrary. The HW Config catalog assigns indices by type, and the runtime view inherits the assignment directly from the compiled XDB. The standard layout used in the majority of PC Stations with S7-300/400 connectivity is:

Common Error Conditions and Status Codes

The following table maps the most common Station Configuration Editor status icons to their root cause and corrective action. Each status icon also writes a corresponding entry to the Windows Event Log under "Applications and Services Logs → Siemens Automation".

Alternative: TIA Portal Embedded OPC Server (V15.1+)

Starting with TIA Portal V15.1 and SIMATIC NET V15.1, the OPC Server can be embedded as a software controller inside the TIA project itself. In that architecture the Configuration Console mode selector is replaced by the "Operating mode" property on the OPC Server device in the Device view. This eliminates the entire class of Configuration Console mode change failures because there is no separate runtime slot to synchronize.

For projects that do not require this embedded architecture, the legacy PC Station + Configuration Console path remains supported. The two configurations can coexist on the same PC only if they are placed under separate Windows user profiles — the SIMATIC NET service installer registers the services per profile.

Verification Checklist

After completing the resolution procedure, run through this checklist to confirm the fault is gone and will not return on the next reboot:

1. Station Configuration Editor shows a green check on every row, with no yellow triangle or red X.
2. Configuration Console shows "Configuration" mode for every OPC Server, IE General, and CP entry.
3. OPC Scout V10 (Start → SIMATIC → SIMATIC NET → OPC Scout) can browse the OPC namespace and read at least one tag from the target PLC.
4. The Windows service "S7OPCSRV" is in state "Running" and startup type is "Automatic".
5. Windows Event Log under "Siemens Automation" contains no entries with Event ID 2001, 2002, 2003, 2004, 2005, or 2010 from the last 24 hours.
6. A reboot of the PC restores the same state — if Configuration mode is lost after reboot, the SIMATIC NET Configuration Service is not set to Automatic startup. Fix via services.msc.
7. A STEP 7 / TIA Portal online "Accessible nodes" browse shows the target PLC with the configured IP and rack/slot, confirming end-to-end connectivity.

Field-Proven Caveats

• Antivirus interaction. Some endpoint protection suites quarantine the SIMATIC NET service executables after the first SIMATIC NET update. The Configuration Console then silently fails to write the mode change because the underlying service cannot be restarted. Add the SIMATIC NET install directory to the antivirus exclusion list before any mode change.
• Windows User Account Control. Configuration Console must be run as Administrator even when the logged-in user is a member of the local Administrators group. Right-click → "Run as administrator" is required.
• Firewall. The OPC Server uses DCOM, which requires the Windows firewall to allow the "SIMATIC NET OPC Server" exception on TCP port 135 plus the dynamic RPC range. Failure to allow DCOM presents as a mode change that succeeds in the UI but does not persist after service restart.
• Multiple PC Stations on one PC. Only one PC Station name can be registered per Windows user profile. Attempting to run two PC Station configurations from the same profile causes the SCE to display the last downloaded configuration only, and the Configuration Console operates against the wrong slot map.
• Time synchronization. The Configuration Console mode change is timestamped against the local system clock. PCs with a failed CMOS battery that boot with a year 2000 date refuse to write the new mode and silently revert. Synchronize the system clock before commissioning.
• Project name vs. computer name. STEP 7 stores the target computer name inside the XDB. If the target PC is renamed after the first download, subsequent "Download to PC Station" operations route to the old name and silently fail with "Target PC not found" event 2004.

FAQ