Visualizing ET 200SP HA Diagnostic Data Without Maintenance Station Standard Licenses in PCS 7

In SIMATIC PCS 7, plant engineers can monitor decentralized ET 200SP HA interface modules and I/O cards without purchasing costly Maintenance Station (MS) Standard runtime licenses. By utilizing Maintenance Station Basis—which is included license-free within standard PCS 7 engineering—system diagnostic alarms are generated automatically in WinCC. Alternatively, engineers can evaluate asynchronous interrupt organization blocks (OB82/OB86) and extract channel driver health flags (ModErr, Bad) in CFC to construct custom visualization faceplates without requiring dedicated Asset Management software packages.

Maintenance Station Basis vs Maintenance Station Standard Licensing

A common commercial confusion in SIMATIC PCS 7 relates to Asset Management and plant diagnostics licensing:

Maintenance Station Basis (License-Free):
Included automatically with every standard SIMATIC PCS 7 system without requiring additional runtime licenses.
Generates WinCC system alarms and diagnostic overview displays for PC stations, automation stations (AS 410-5H), network components (SCALANCE switches), and distributed fieldbus lines.
Renders basic diagnostic status (Good, Maintenance Required, Maintenance Demanded, Fault) conforming to NAMUR NE 107.
Maintenance Station Standard (Separately Licensed):
Requires dedicated SIMATIC PCS 7 Maintenance Station licenses (MS Engineering, MS Runtime, and Asset Management device count packages).
Provides granular, hierarchical diagnostic faceplates down to individual electronic submodules, terminal base units, calibration timers, and cyclical field device health records.

If a plant does not purchase MS Standard licenses, ET 200SP HA hardware diagnostics can still be fully visualized using native PCS 7 driver outputs.

Automatic Diagnostic Driver Generation Without Asset Licenses

During standard chart compilation with Generate module drivers enabled, PCS 7 automatically creates diagnostic charts (@...):

System Diagnostic Blocks: Blocks such as MOD_HA (for ET 200SP HA modules) and OB_DIAG are instantiated automatically in the background.
Interrupt Interception: These blocks intercept operating system interrupts (OB82 for module diagnostic alarms, OB83 for module insertion/removal, and OB86 for rack failure).
WinCC Alarm Logging Integration: Standard system messages (e.g., "Module error entering state", "Wire break on Channel X") are dispatched via ALARM_8P to WinCC Alarm Logging without needing any Maintenance Station licenses.

Extracting Channel Driver Diagnostic Flags in CFC (ModErr, Bad)

To create custom operator visualizations for ET 200SP HA modules in standard process graphics:

Bad Output: The primary channel drivers (Pcs7DiIn, Pcs7AnIn, Pcs7DiOu, Pcs7AnOu) output Bad.Value = 1 whenever the physical hardware channel experiences a fault (wire break, short circuit, missing 24V DC auxiliary power).
ModErr Output: Asserts to 1 when the underlying I/O module reports an internal hardware error or communication loss.
Channel Status Word (Quality Code): The PV_Out.ST structured parameter outputs 16#00 (Bad - Device failure) or 16#28 (Bad - Process related), providing immediate feedback on sensor health.

Engineers can interconnect these boolean outputs directly into standard alarm blocks (ALARM_8P) or pack them into technological status words.

Custom WinCC Diagnostic Faceplate Design

To visualize ET 200SP HA rack health on a standard WinCC process graphic:

Create an SCL Diagnostic Aggregator Block:
* Create a simple SCL block that aggregates ModErr and Bad signals from all 8 or 16 channels of an ET 200SP HA card.
* Add inputs for rack communication health (OB86_Fault).
Assign S7_m_c Attributes:
* Tag the status variables with { S7_m_c := 'true' } to expose them to WinCC Tag Management.
Design a Graphical Rack Display in Graphics Designer:
* Draw an ET 200SP HA rack graphic showing the IM 155-6 PN HA interface module and I/O cards.
* Dynamically link card colors to the aggregated status tags:
- Green: Healthy (ModErr = 0 and Bad = 0).
- Yellow: Channel wire break / maintenance demanded.
- Red: Complete module fault or rack communication failure.

Verification

Confirm diagnostic reporting without Maintenance Station licenses:

WinCC Alarm System Verification:
* Induce a wire break on an ET 200SP HA analog input channel.
* Open the WinCC Alarm Logging list.
* Confirm that an alarm indicating channel wire break appears automatically.
Channel Driver Output Check:
* Open the CFC chart in Test Mode.
* Verify that Pcs7AnIn.Bad.Value = 1 and Pcs7AnIn.PV_Out.ST = 16#00.
Custom Graphic Verification:
* Verify that the custom rack graphic in WinCC updates from green to yellow/red to reflect the channel fault.

Limitations and Operational Precautions

Maintenance Station Standard Features Omitted: Custom logic can display faults and wire breaks, but cannot provide advanced asset management functions such as automated wear timers, calibration logs, or electronic device description (EDD) parameter menus.
Never Manually Edit @... System Charts: Do not attempt to rewire blocks inside the automatically generated @ diagnostic charts; any manual changes will be overwritten during the next compilation.
Processing Overhead: Writing complex custom diagnostic parsing code for hundreds of I/O cards increases CPU cycle time; leveraging standard channel driver outputs (Bad, ModErr) is far more efficient than manual OB parsing.

Engineer FAQ

Can I view ET 200SP HA module diagnostics without buying a Maintenance Station license?
Yes, basic diagnostics are provided license-free via Maintenance Station Basis, and channel driver outputs (Bad, ModErr) can be used for custom graphics.
What is the difference between Maintenance Station Basis and Standard?
Maintenance Station Basis is free and covers PC/AS/network alarms; Maintenance Station Standard requires licenses and provides granular asset faceplates for I/O modules and field devices.
Which channel driver parameter indicates an I/O card hardware defect?
The ModErr output parameter asserts to 1 when the physical I/O module reports a hardware fault or communication loss.
Does WinCC log wire-break alarms if no Maintenance Station is installed?
Yes, the standard PCS 7 module driver generator creates ALARM_8P messages that report wire breaks and channel faults directly to WinCC Alarm Logging.
What output quality code does an APL driver produce during a module fault?
The driver outputs PV_Out.ST = 16#00 (Bad - Device failure).
Which interrupt organization blocks handle ET 200SP HA diagnostics in the S7-400?
OB82 handles module diagnostic interrupts, OB83 handles module pull/plug events, and OB86 handles rack/station communication failures.
Can I create a custom WinCC graphic showing ET 200SP HA rack status?
Yes, by aggregating driver ModErr and Bad signals in an SCL block and creating a dynamic graphic in WinCC Graphics Designer.
What happens if an ET 200SP HA module is pulled from the rack?
The CPU executes OB83 and OB82, the diagnostic driver asserts ModErr = 1, and WinCC logs a module pulled alarm.
Does ET 200SP HA support hot-swapping under power (Run mode)?
Yes, ET 200SP HA modules can be inserted and removed under power during RUN without disturbing adjacent I/O cards.
Is an Asset Management license required to view diagnostic buffer entries in STEP 7?
No, the STEP 7 Module Information dialog (Ctrl+D) is a standard engineering tool accessible without runtime asset licenses.

Technical References

Siemens Industry Online Support (SIOS) Portal: SIMATIC PCS 7 Compendium Part A - Section 12: Integrated Asset Management (Entry ID: 109742323).
SIMATIC ET 200SP HA Distributed I/O System System Manual, Siemens AG.
SIMATIC PCS 7 Maintenance Station Operating Manual, Siemens AG.

Related Tags

PCS 7, ET 200SP HA, Diagnostics, Maintenance Station, Asset Management, ModErr, Channel Drivers, WinCC

Visualizing ET 200SP HA Diagnostic Data Without Maintenance Station Standard Licenses in PCS 7