Decoding SIMATIC PCS 7 Hardware Diagnostic Messages: Mapping 'Module 1/5/5' to Physical Racks and Slots
In SIMATIC PCS 7 and WinCC, an alarm reporting an error at 'Module 1/5/5' when the physical hardware fault is on an ET 200 station labeled Rack 3 Slot 4 Channel 0 is caused by standard diagnostic message placeholder formatting. PCS 7 diagnostic driver blocks (such as MOD_1, MOD_D1, and RACK) format error strings using the internal addressing schema [@1%d@/@2%d@/@3%d@], which represents [Master System ID / Station Address / Slot Number]. Here, '1' is DP Master System 1, the first '5' is PROFIBUS/PROFINET Station Address 5 (the slave address of the station named 'Rack 3' in HW Config), and the second '5' is logical Slot 5 (the I/O module location following the interface and power modules).
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
System operators and maintenance technicians frequently observe apparent discrepancies between WinCC diagnostic alarm messages and physical plant hardware. For example, a channel fault on an ET 200M distributed I/O station labeled 'Rack 3, Slot 4' in the project hierarchy or electrical schematics generates an alarm text displaying 'Module 1/5/5 : Channel error'. This mismatch leads technicians to inspect the wrong physical cabinet. This guide explains how PCS 7 automatically generates diagnostic messages in the @charts layer, decodes the numerical placeholders used by system diagnostic blocks, and provides a clear mapping method between logical telegram addresses and physical cabinet locations.
Architecture and Fundamental Mechanics
The PCS 7 automated module driver generator builds diagnostic alarm structures during CFC compilation:
1. Generation of Diagnostic Charts (@charts):
When 'Generate module drivers' is selected during CFC compilation, the compiler inspects HW Config and generates background diagnostic charts prefixed with @. It instantiates OB_BEGIN, RACK, and MOD_ blocks (e.g., MOD_1 or MOD_D1) tailored to each physical module.
2. Standard System Message String Formatting:
The alarm messages attached to MOD_ blocks use standard format strings defined in the PCS 7 Basis Library:
Module @1%d@/@2%d@/@3%d@ : @4%s@
- @1%d@ = Master System ID: The logical bus number of the DP master system or PROFINET IO controller (e.g., System 1).
- @2%d@ = Station Address: The physical PROFIBUS DP slave address or PROFINET device number (e.g., Station Address 5).
- @3%d@ = Physical/Logical Slot Number: The slot position in the rack configuration (e.g., Slot 5).
- @4%s@ = Fault Description: Extracted from OB82 diagnostic interrupt bytes (e.g., Wire break, Short circuit).
3. Why 'Rack 3 Slot 4' Maps to '1/5/5':
- The station was assigned PROFIBUS address 5 in HW Config, even though the engineer assigned it the symbolic or rack name 'Rack 3'.
- In an ET 200M rack, Slot 1 is the power supply, Slot 2 is the IM 153 interface module, Slot 3 is reserved, and I/O modules occupy Slots 4 through 11. However, if an active bus module or dual-slot interface is configured, the module residing at physical user position 4 can be addressed at logical slot 5 in the telegram image.
Step-by-Step Implementation Procedure
-
Identify the Diagnostic Message Parameters in WinCC:
a. Open the WinCC Alarm Control on the OS Client or Server.
b. Inspect the faulted diagnostic line: note the stringModule 1/5/5and associated event timestamp.
c. Note the associated block tag name (e.g.,@<AS_Name>/pcs_rack_3_4). -
Locate the Station Address in HW Config:
a. Open STEP 7 HW Config for the target AS controller.
b. Locate the DP Master System or PROFINET IO System numbered1.
c. Scan the distributed stations connected to this line for Station Address5(PROFIBUS DP address5).
d. Observe that this station is the one symbolically named 'Rack 3'. -
Verify Slot Numbering in the Station Rack:
a. Click on Station 5 to open its rack configuration table in the lower pane of HW Config.
b. Locate Slot5in the rack table.
c. Confirm the module part number and verify that its peripheral addressing corresponds to the channel driver block (Pcs7DiIn/Pcs7AnIn) reporting the bad signal status (ST = 16#00). -
Reconcile Channel Numbering:
a. In the channel driver block instance in CFC, check the interconnected input parameterDataXchg.
b. Verify thatDataXchglinks directly to the module driver block@.../pcs_rack_3_4.
c. Note that while the module is at physical rack position 4, the diagnostic telegram evaluates logical slot 5. -
Align Plant Documentation and Message Customization (Optional):
a. If site conventions mandate showing cabinet and physical rack names in alarms, edit the 'Block Comment' or 'Message Text' of the channel driver or module block in CFC to append the physical cabinet name (e.g.,Cabinet MCC-02 / Rack 3 / Slot 4).
b. Recompile OS changes to deploy customized diagnostic text.
Verification
- In HW Config online test mode, double-click the module at Slot 5 of Station 5 and open 'Module Information -> Diagnostic Interrupt'.
- Confirm that the channel error reported in the hardware diagnostic buffer matches the WinCC alarm description (e.g., 'Channel 0 Wire break').
- Correct the physical field wiring break: verify that the diagnostic interrupt clears, the green LED on the physical module restores, and the WinCC alarm automatically transitions to 'Cleared/Departed'.
Limitations and Operational Precautions
Do not manually edit automatically generated @charts in CFC; any manual changes made directly inside @charts will be overwritten and erased during the next 'Generate module drivers' compilation.
Engineer FAQ
What do the three numbers in 'Module 1/5/5' represent?
They represent [Master System ID / Station Address / Slot Number] in the hardware diagnostic telegram.
Why does the alarm say Station 5 when my project calls it Rack 3?
WinCC displays the numerical PROFIBUS/PROFINET slave address (5) assigned in HW Config, whereas 'Rack 3' is an engineering symbolic label.
Why is physical slot 4 reported as slot 5 in the message?
Modular distributed I/O stations reserve initial slots for interface modules and backplane bus connectors, shifting physical card slots relative to telegram slot indices.
Where are the diagnostic driver blocks created?
They are generated automatically by the CFC compiler in system charts prefixed with @ when 'Generate module drivers' is selected.
Can I customize the diagnostic message text in WinCC?
Yes. You can customize message texts by editing block message parameters in CFC and performing an AS-OS compilation.
Technical References
- SIMATIC PCS 7 Basis Library Function Manual
- SIMATIC S7-400 / ET 200M Diagnostics and System Errors Reference Manual
- SIMATIC PCS 7 Engineering System Compendium Part A
Related Articles
- Interconnecting APL Channel Drivers (Pcs7AnIn, Pcs7DiIn, Pcs7AnOu) with Monitoring Blocks and Field Diagnostics
- Resolving Module Driver Generation Failures with ET 200SP Interface Modules and Generic GSDs
- Diagnosing Area Length Read Errors and Local Data Failures in APL Execution
Related Tags
- Hardware Diagnostics
- Module Drivers
- WinCC Alarms
- ET 200M
- PROFIBUS Address
- CFC @charts