Resolving Missing PROFINET System and Node Diagnostic Alarms in SIMATIC PCS 7 Alarm Logging

Missing system diagnostic alarms for PROFINET nodes (such as remote I/O stations, variable speed drives, and motor controllers) in SIMATIC PCS 7 Alarm Logging occurs when the PCS 7 Module Driver Generator cannot bind device diagnostic addresses to the @System diagnostic block family. To resolve this, ensure that: 1) Hardware diagnostic interrupts are enabled and unique diagnostic addresses (LADDR) are assigned in HW Config, 2) Dedicated PROFINET driver blocks (MOD_PND, RACK_PND, PNDP) are present in the project library, 3) Technological blocks such as FbDrive (FB1905) are interconnected to device diagnostic addresses, and 4) CFC charts are compiled with 'Generate module drivers' enabled.

Automated System Diagnostic Message Architecture in PCS 7

In SIMATIC PCS 7, hardware health monitoring is designed to be fully automated. When distributed I/O stations, communications processors, or field devices suffer power loss, wire breaks, or communication drops, the DCS automatically generates standardized system messages in the WinCC Alarm Logging @System message family.

This automation is achieved via the Module Driver Generator:
* During CFC compilation, the compiler parses the STEP 7 Hardware Configuration (HW Config).
* For each configured rack, module, and communication channel, it dynamically creates system driver blocks inside auto-generated CFC charts prefixed with @.
* These blocks (OB_BEGIN, MOD_PND, RACK_PND) intercept organization blocks (OB82 Diagnostic Interrupt, OB83 Pull/Plug Interrupt, OB86 Rack Failure) and dispatch structured Alarm_8P messages to WinCC.

PROFINET Device Diagnostics vs Classic PROFIBUS Drivers

When facilities transition from classic PROFIBUS DP to Industrial Ethernet / PROFINET IO on S7-400 or CPU 410-5H controllers, driver differences frequently cause missing diagnostics:

Network ArchitectureDistributed Head BlockModule Monitoring BlockProtocol Interface BlockHardware Diagnostic EventClassic PROFIBUS DPRACK_NO / OB86MOD_D1 / MOD_PADP_DIAGOB86 Subnet Failure / OB82 Channel FaultPROFINET IORACK_PNDMOD_PNDPNDPOB86 Station Return / OB82 PROFINET Alert

If a project was migrated from an older PCS 7 library version that lacks the PROFINET diagnostic blocks, the driver generator cannot construct the @ charts for PROFINET nodes, resulting in silent communication failures.

Interconnecting Technological Blocks (FbDrive FB1905) to Hardware

Technological driver blocks for intelligent field equipment—such as FbDrive (FB1905) for variable frequency drives or SIMO_DIR for motor management relays—require explicit hardware address linkages:
* The LADDR Parameter: The input pin LADDR on FbDrive must be interconnected to the base logical input/output address of the drive's configured standard telegram (e.g. PIW 512 or logical base address).
* Diagnostic Address Binding: The diagnostic address of the PROFINET head station (configured in HW Config under Device Properties) must be valid and non-overlapping.
* Driver Generator Automatic Interconnection: When LADDR is linked, the module driver generator automatically establishes internal interconnections between FbDrive and the corresponding MOD_PND block in chart @System.

Executing Module Driver Generation and System Alarm Binding

To re-establish automated diagnostic message generation across all PROFINET slaves:

[SIMATIC Manager -> Component View]
   │
   ├─► Open HW Config
   │     • Select PROFINET IO System
   │     • For each slave: Ensure "Diagnostic Interrupt" is checked
   │     • Check for non-overlapping diagnostic addresses
   └─► Save and Compile HW Config
         │
         ▼
[CFC Chart Compilation]
   │
   ├─► Open CFC Editor -> Select: Chart -> Compile -> Charts as Program...
   ├─► Scope: Select "Entire program"
   ├─► Checkbox: MANDATORY -> [x] "Generate module drivers"
   │     • Compiler parses HW Config and creates/updates @-charts
   └─► Click OK -> Confirm compilation log shows "0 Errors"
         │
         ▼
[AS-OS Compilation]
   │
   ├─► Right-click OS -> Select: "Compile"
   └─► Compiles @System alarm definitions into WinCC Alarm Logging

Following this sequence, PROFINET station disconnects trigger instant system alarms on operator displays.

Verification

To confirm that PROFINET node diagnostic messages are functional:
1. In SIMATIC Manager, inspect the CFC chart folder; verify the presence of chart @System containing RACK_PND and MOD_PND blocks.
2. Open WinCC Explorer, launch Alarm Logging, and filter by message class System, without acknowledgment; verify that messages for the PROFINET device addresses are listed.
3. Activate WinCC Runtime.
4. Deliberately power down a test PROFINET remote I/O rack or disconnect its Ethernet patch lead.
5. Confirm that an immediate flashing alarm appears in the WinCC Alarm banner displaying: PROFINET station failure: Device <Device_Name>, Rack <Rack_Number>.

Limitations and Operational Precautions

Never attempt to manually place, rewire, or delete blocks within the @System charts. Manual edits will corrupt driver generator cross-references and will be overwritten during the next CFC compilation. Always resolve diagnostic driver issues by correcting HW Config parameters, updating library versions, or adjusting block interconnections in user charts.

Engineer FAQ

Why did `FbDrive` not automatically connect to the `@System` blocks?

If the LADDR (Logical Address) input on FbDrive is left unconnected, or if it points to an address not recognized in HW Config as a supported drive telegram, the driver generator skips the block.

Where are system-generated alarm messages configured in PCS 7?

System alarms originate inside the PCS 7 Basis Library driver blocks (MOD_PND, RACK_PND). Their message texts and attributes are compiled automatically into WinCC Alarm Logging.

What happens if 'Generate module drivers' is disabled during compile?

User logic compiles faster, but no driver blocks are updated. Newly added hardware, modified addresses, or altered diagnostic parameters will have no alarms or communication links.

Can third-party PROFINET devices generate PCS 7 system messages?

Yes, provided the third-party device GSDML file supports standard PROFINET diagnostic interrupts and is compiled using standard channel drivers.

Technical References

Related Tags

PROFINET Diagnostics
System Messages
Module Driver Generator
FbDrive FB1905
MOD_PND

PROFINET Diagnostics

System Messages

Module Driver Generator

FbDrive FB1905

MOD_PND

6 respuestas

Resolving Missing PROFINET System and Node Diagnostic Alarms in SIMATIC PCS 7 Alarm Logging