Limitations of SIMATIC PCS 7 Maintenance Station Diagnostics During PLCSIM and OS Simulation

When testing a SIMATIC PCS 7 Maintenance Station (MS Basic or MS Standard) using S7-PLCSIM and WinCC OS Simulation on a single Engineering Station, diagnostic overview screens appear blank, unpopulated, or indicate communication faults because S7-PLCSIM simulates only user logic execution (OBs, DBs) and does not emulate physical S7-400 system status lists (SZL), hardware diagnostic interrupts (OB82), or SNMP network agent queries. As documented in the PCS 7 Maintenance Station manual (Section 5.1), OS simulation for a Maintenance Station is supported only to a very limited extent without live hardware. Validating system diagnostics, module health, and asset management requires connection to physical AS controllers and network switches.

Executive Summary

The SIMATIC PCS 7 Maintenance Station (MS) provides plant-wide asset management and diagnostic monitoring across automation hardware, field instrumentation, network infrastructure, and PC stations. Automation engineers configuring new projects routinely attempt to validate Maintenance Station displays within an offline engineering sandbox using S7-PLCSIM and the WinCC 'Start OS Simulation' function on a single laptop. However, after executing Create/update diagnostic screens in the Plant Hierarchy, launching OS simulation reveals empty diagnostic overview screens, missing CPU status symbols, and inactive PC station icons. While engineers frequently suspect incorrect hardware configurations or broken AS-OS communication links, this behavior is a documented system limitation of simulation tools. This guide clarifies the underlying diagnostic mechanics and outlines testing alternatives.

PCS 7 Maintenance Station System Architecture

The Maintenance Station functions as a specialized OS Server or Single Station:

System Diagnostic Driver: System blocks (AS_DIAG, PC_DIAG, ET200M_DIAG) read live system status records from the controller firmware using system function SFC51 (RDSYSST).
SNMP OPC Server: The SIMATIC NET SNMP OPC server polls managed network switches (SCALANCE) and PC stations via SNMP to evaluate link status, fan speeds, and power supply states.
WinCC Asset Faceplates: Graphic pictures (@Diagnostics.pdl) read diagnostic tags generated during OS compilation to display device status symbols.

Why PLCSIM Bypasses Hardware Diagnostics and SZL Lists

Siemens official documentation (SIMATIC PCS 7 Maintenance Station Manual, Section 5.1) explicitly states:

'You can only use the OS simulation function in the MS Standard or MS Basic version. OS simulation for a PCS 7 Maintenance Station in MS Standard and MS Basic is possible only to a limited extent (for example, no identification or diagnostics data).'

S7-PLCSIM emulates CPU program execution instructions (ladder, logic, registers) but does not emulate physical backplane ASICs, hardware interrupt lines, or System Status Lists (SZL 0x00B1, 0x00B2, 0x00B3, 0x00B4). When diagnostic driver blocks call SFC51 inside PLCSIM, the function returns an error code or empty data buffers, causing the diagnostic screen generator to report that hardware modules are offline or unassigned.

Maintenance Station Feature Availability Comparison

The following table compares Maintenance Station capabilities between offline simulation and live hardware operation:

Asset Management FeatureS7-PLCSIM / OS SimulationLive Hardware AS / Physical NetworkRoot Architectural DifferenceDiagnostic Screen GenerationSupportedFully SupportedHandled entirely by offline SIMATIC Manager.CPU Status DisplayUnpopulated / FaultReal-Time Healthy / FaultPLCSIM lacks SZL system status data.I/O Module DiagnosticsNot AvailableChannel-Level Wire-Break/ShortHardware diagnostic interrupts (OB82) inactive in PLCSIM.PC Station DiagnosticsNot AvailableLive Fan/Temp/Disk HealthDiagMonitor & SNMP agents require physical PC hardware.Network Switch DiagnosticsNot AvailableLive Port/Link TopologySCALANCE switches require physical SNMP communication.Asset Management Data (I&M)Blank / MissingFull Serial / Firmware DisplayI&M data reads directly from physical EEPROMs.

Diagnostic Screen Generation Workflow in Plant Hierarchy

Generating diagnostic screens relies on the Plant Hierarchy structure:

In Plant View, open Settings under the multiproject root and configure the designated Maintenance Station OS.
Assign the target AS controllers and PC stations to the diagnostic hierarchy.
Execute Create/update diagnostic screens; this compiles hardware configuration data into specialized WinCC pictures (@Diagnostics.pdl, @Diagnostics_AS.pdl, @Diagnostics_PC.pdl).

Step-by-Step Procedure to Configure and Validate Maintenance Station

Method 1: Proper Configuration in Plant Hierarchy

Open the multiproject in SIMATIC Manager.
Switch to Plant View.
Right-click the root folder and select Plant Hierarchy > Settings.
Check the box Maintenance Station and select the designated OS project from the dropdown.
Right-click the root folder again and select Plant Hierarchy > Create/update diagnostic screens.
Select the AS systems to include and click OK to generate the diagnostic pictures.
Compile the OS project completely with Tags and messages enabled.

Method 2: Testing Diagnostics on Physical Hardware

Download the compiled S7 program and hardware configuration to a physical S7-400 Automation Station.
Activate WinCC Runtime on the Maintenance Station or OS Server.
Navigate to the Diagnostics area screen (@Diagnostics.pdl).
Verify that the CPU icon shows a green checkmark indicating normal operational status.
Simulate a physical module fault (such as disconnecting an active sensor or pulling a channel fuse) and verify that the channel fault indicator transitions to red with associated diagnostic alarms in the message list.

Verification

To verify Maintenance Station configuration integrity:

Generation Log Audit: Review the diagnostic screen generation log. Confirm that all target AS controllers and PC stations were processed without compilation errors.
Picture Verification: Open @Diagnostics.pdl in Graphic Designer. Confirm that the diagnostic overview picture hierarchy contains valid linked icons for all CPUs.
Physical Hardware Validation: On physical hardware, confirm that clicking the CPU diagnostic icon opens the detailed AS diagnostic faceplate displaying firmware version, mode selector switch state, and cycle time.

Limitations and Operational Precautions

Do Not Rely on Simulation for Asset Audits: Never conclude that a Maintenance Station configuration is flawed based on empty screens in PLCSIM; true diagnostic validation requires physical AS connections.
MS Licensing Requirements: A dedicated SIMATIC PCS 7 Maintenance Station license (MS Basic or MS Standard) is required in runtime to avoid non-acknowledged license violation messages.
SNMP Community Strings: Monitoring third-party network devices or SCALANCE switches requires configuring matching SNMP v1/v2c community strings in the SIMATIC NET OPC configuration.

Engineer FAQ

Can S7-PLCSIM Advanced simulate Maintenance Station diagnostics?

S7-PLCSIM Advanced is designed for S7-1500 controllers; PCS 7 utilizes classic S7-400 CPUs which are limited to classic S7-PLCSIM V5.4.

Why do PC stations appear with a red cross in Maintenance Station runtime?

A red cross indicates that the SIMATIC NET SNMP OPC server or Siemens DiagMonitor agent is not running on that target PC.

Does the Maintenance Station require separate Process Object (PO) licenses?

MS Basic does not consume runtime POs for diagnostic objects; MS Standard asset management packages require dedicated MS asset licenses.

Technical References

Related Tags

https://industrialautomation.net/search?query=simatic-pcs7
https://industrialautomation.net/search?query=maintenance-station
https://industrialautomation.net/search?query=plcsim
https://industrialautomation.net/search?query=diagnostics

6 respuestas

Limitations of SIMATIC PCS 7 Maintenance Station Diagnostics During PLCSIM and OS Simulation