Diagnostics
12.3 Diagnostic interrupts
FM 352 electronic cam controller
148 Operating Instructions, 05/2011, A5E01071724-03
12.3.2 Reaction of FM 352 to errors with diagnostics interrupt
Reactions
● Cam processing will be disabled.
● The synchronization will be cleared by the following diagnostic interrupts:
– Front connector missing, external power supply missing
– zero mark error detected, cable fault (5-V encoder signals)
– traversing range exceeded (indicated by a process/hardware error)
– Set actual value cannot be executed (indicated by a process error).
● With one exception, control signals are no longer processed.
Exception:
When the software limit switch is crossed, a direction reversal is still possible in
simulation mode.
● Function switch and job processing continues.
FM 352 detects an error ("incoming")
A diagnostic interrupt is an "incoming" event if at least one error is pending. If any errors are
pending clearance, the queued errors are reported again as "incoming" events.
Sequence:
1. FM 352 detects one or several errors, and generates a diagnostic interrupt. The "SF" LED
is lit. The error event is logged to the diagnostic buffer.
2. The CPU operating system calls OB82.
3. You can now evaluate the start information of OB82.
4. The OB82_MOD_ADDR parameter indicates which module triggered the interrupt.
5. Further information is available when the FB CAM_DIAG is called.
FM 352 detects the transition to the error-free state ("outgoing")
A diagnostic interrupt is only registered "outgoing" if all errors on the module are cleared.
Sequence:
1. FM 352 detects that all errors have been cleared and triggers a diagnostic interrupt. The
"SF" LED is no longer lit. The diagnostic buffer remains unchanged.
2. The CPU operating system calls OB82.
3. The OB82_MOD_ADDR parameter indicates which module triggered the interrupt.
4. Evaluate the OB82_MDL_DEFECT bit.
When this bit is "0", no errors are present on the module. You can close the evaluation
session at this point.