Table of Contents
Advertisement
5.3.2.2
Interrupts
The IO device initiates interrupts following certain errors. The evaluation of the interrupt is
dependent on the IO controller used.
The PN/MF Coupler supports the following interrupts:
• Diagnostics interrupts
If the communication relation exists between the IO controller and the PN/MF Coupler,
manufacturer-specific diagnostics of the PN/MF Coupler also become active as interrupts.
The interrupts trigger the call of an OB 82 in a SIMATIC CPU.
Note
Start information of the OB
Diagnostics on the PN/MF Coupler can already be pending, which will not be reported by a
diagnostics interrupt. You must then explicitly read the diagnostic information with a
diagnostic data record in the user program.
Use the start information of OB 86, for example, and the list of the diagnostics and
configuration data records
(https://support.industry.siemens.com/cs/ww/en/view/19289930) for PROFINET IO for this
purpose.
• Maintenance alarms
The PN/MF Coupler supports diagnostics and the maintenance concept in PROFINET
according to IEC 61158-6-10. The goal is to detect and remove potential problems as early
as possible.
For the PN/MF Coupler, maintenance alarms signal to the user when a network
component must be checked or replaced.
Maintenance alarms
The PN/MF Coupler signals a maintenance alarm to the higher-level diagnostics system when
the following events occur:
Maintenance alarms
Maintenance demanded
(maintenance demanded)
MT LED is lit
System alarms in STEP 7
The maintenance information is generated in STEP 7 with the following system alarm:
• Maintenance demanded, identified by a yellow wrench icon at the relevant port.
PN/MF Coupler
Hardware Installation and Operating Manual, 07/2020, A5E50018670-AA
5.3 PROFINET IO interrupts, diagnostics, error messages and system events
Event
Message/Meaning
Loss of synchroniza-
•
tion
•
Diagnostics Un-
Undervoltage diagnostics applies when the power supply supplies a
dervoltage
value from ≤19.2 V to ≥20.4 V.
No synchronization message frame received
After parameterization or during operation, the sync master did
not receive a synchronization message frame within the timeout
period.
Successive synchronization message frames are outside the per-
missible limits (jitter).
PROFINET IO
55
Advertisement
Table of Contents
