Technical data

Configuring Messages
16.9 Configuring the 'Reporting of System Errors'
Programming with STEP 7
Manual, 05/2010, A5E02789666-01 379
16.9.3 Supported Components and Functional Scope
The components of S7 300 stations, S7 400 stations, PROFINET IO devices, DP slaves, and
WinAC are supported by Report System Error, as long as they support functions such as
diagnostic interrupt insert/remove module interrupt, and channel-specific diagnostics.
The following components are not supported by Report System Error:
• M7configurations
• PROFIBUS-DP configurations on DP master interface module (CP 342-5 DP) in S7-300
stations
• PROFINET IO devices over an external controller (CP 343-1 Advanced) in S7-300 stations
In the case of a restart, you must also note that missing interrupt messages can occur. This is
because the message acknowledgement memory of the CPU cannot be deleted during restart but
Report System Error resets the internal data. The module or channel errors that occur before
startup or during a failure are not all reported.
A maximum of 8 channel errors are reported per submodule.
Note
If you use a CP 443-5 and this is in STOP mode, no master system failure will be reported during
startup.
PROFIBUS-DP
In the tables that follow, you will find all the diagnostic blocks of the various PROFIBUS slaves
supported by "Report System Error".
Diagnostic Field ID (faulty slot) Channel
Designation
(channel error) 1)
Module Status
(module error,
incorrect/no
module)
Device Designation
Header ID 2) 0x01 0x10 0x00
Type 0x82
0x00 + 1 byte
diagnostic info
ET 200S Message:
"Diagnostic interrupt
was triggered"
Plain-text message Plain-text message -
ET 200pro Message:
"Diagnostic interrupt
was triggered"
Plain-text message Plain-text message -
ET 200M Not evaluated Plain-text message Plain-text message -
ET 200X Message:
"Diagnostic interrupt
was triggered"
- - -
ET 200X Desina Message:
"Diagnostic interrupt
was triggered"
Plain-text message Plain-text message -