INFO
This method can be adapted to troubleshoot any controller analogue output with a mA signal.
9.2 Alarms
9.2.1 Troubleshooting alarms
INFO
During commissioning, there is often a wider range of possible causes for alarms. This makes it difficult to provide
comprehensive alarm troubleshooting information. For example, during commissioning, the alarm may be activated
because of a wiring mistake. Careful thought, analysis and testing may be needed to find an alarm's cause.
See Troubleshooting alarms in the Operator's manual for troubleshooting information for a number of common
alarms.
9.3 Terminals
9.3.1 Troubleshooting terminal damage
All the terminals are tested before the controller leaves the factory. Therefore, the controller terminals do not generally need
to be checked, and problems with the terminals are rare.
However, the terminals can be damaged by electrostatic discharge, or by exposure to voltages and/or currents that are too
high. The hardware module self-check can be OK even though terminals are damaged.
If a high voltage or high current event, and/or the terminal input/output makes you suspect that the terminals are damaged,
then test the terminals.
If terminals are damaged, you can move the wiring and configure the input/output function on another set of terminals (if
there are terminals available).
Alternatively, replace the hardware module that has damaged terminals.
9.3.2 Troubleshooting the MPU input
Problem
The MPU voltage is too low (< 3 V).
Solution
Adjust the MPU position so that the detector is closer to the teeth.
PPU 300 Commissioning guidelines 4189341106 UK
www.deif.com Page 69 of 75
To Next Page
Loading...
