Interrupts, diagnostics, error, and system messages
5.3 Alarms
Causes of error and troubleshooting
The causes of error and remedies for the diagnostics alarms are described in the Product
Manuals for I/O modules
(http://support.automation.siemens.com/WW/view/en/55679691/133300) in the section,
"Interrupts/diagnostics alarms".
See also
Channel diagnostics (Page 37)
5.3.2
Maintenance events
Triggering of a maintenance event
The PROFINET IO interfaces of the interface module support the diagnostic concept and
maintenance concept in PROFINET IO according to the IEC 61158-6-10 standard. The goal
is to detect and remove potential problems as soon as possible.
For the interface module, maintenance events signal to the user when a network component
must be checked or replaced.
The CPU interrupts user program execution and processes the diagnostic block OB 82. The
event that triggered the maintenance event is entered in the start information of the OB 82.
The interface module signals a maintenance event to the higher-level diagnostic system in
the case of the following events:
Table 5- 7
Maintenance alarm
Maintenance demand-
ed (
manded
LED MAINT is lit.
System events in STEP 7 (TIA Portal)
The maintenance information is generated in STEP 7 with the following system events:
● Maintenance demanded - indicated for each port by a yellow wrench icon
device view or in the hardware configuration.
You can find more information in the STEP 7 online help.
36
Triggering of a maintenance event
Event
Synchronization
maintenance de-
loss
)
Meaning
No synchronization frame received
•
No synchronization frame was received by the sync
master within the timeout period after parameter as-
signment or during operation.
Successive synchronization frames are located out-
•
side permitted limits (jitter)
IM 155-6 PN ST interface module (6ES7155-6AU01-0BN0)
in the
Manual, 04/2017, A5E03576904-AE