Interrupts and diagnostic, error, and system alarms
5.3 Alarms
IM 155-5 PN HF Interface Module (6ES7155-5AA00-0AC0)
42 Manual, 10/2018, A5E32840985-AB
Causes of error and corrective measures
The error causes and corrective measures of the diagnostic alarms are described in the
manuals for the I/O modules
(http://support.automation.siemens.com/WW/view/en/67296522/133300) in the
Interrupts/Diagnostic alarms section.
Channel diagnostics (Page 43)
Maintenance events
Triggering of a maintenance event
The PROFINET interface of the interface module supports the diagnostic concept and
maintenance concept in PROFINET 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 executes the diagnostic interrupt OB. The
event that triggered the maintenance event is entered in the start information of the
diagnostic interrupt OB.
The interface module signals a maintenance event to the higher-level diagnostic system in
the case of the following events:
Table 5- 4 Triggering of a maintenance event
MAINT LED is lit
Synchronization
loss
• No synchronization frame received
No synchronization frame was received by the sync master within the
timeout period after parameter assignment or during operation.
• Successive synchronization frames are located outside permitted
limits (jitter)
Maintenance
event of an I/O
module
The maintenance event of a power supply module is passed through.
The maintenance information is generated in STEP 7 with the following system alarms:
● Maintenance demanded - indicated for each port by a yellow wrench icon
in the
device view or in the hardware configuration.
You can find additional information in the STEP 7 online help.