Pinnacle Systems DR - Manual (Page 37)

Appendix “A”
Diagnostics & Troubleshooting
SBLK
SLAVE microprocessor detected blockage when the
MASTER did not. Some of the receiver signals are
so weak that the leading edge of the pulse is missed
by the SLAVE but the trailing edge is not missed by
the MASTER. Re-align the pylons.
Serial data corrupted
The MASTER has requested data from the SLAVE
but the check-sum value received does not match
the value calculated from the data received. Faulty
computer board in the door of the Controller Module,
bad CPU chip, or noise glitch.
Serial data transfer incomplete
Data passed between both computers could not be
completely transferred. Electrical noise is the main
culprit. Hardware failure is the second. Also, check
amp loading of the STOP circuit. Relay sparking
can cause faults.
Short LED in emitter pylon xxy
An LED in Emitter pylon was found not fi ring. xx
indicates board number in 4” increments from
circular connector; y indicates beam number of
that board (1 to 8). Could also be a faulty cable,
computer board, or R27 on the computer board has
burned short.
Slave Found
Guard has been powered down with a fault code in
memory. Push the FN1 button on top of Controller
Module to reset fault.
Unknown Code
Garbage data in memory that has no fault code.
Push the FN1 button on top of Controller Module
to clear.
Waiting for reset button
Master is waiting for user to push the RESET button
to start scanning. This indicates that you pushed
the RESET button too soon after getting an error
message and prevented the SLAVE from saving the
error code in permanent memory. You should wait
until the message displays one time before pushing
the RESET button.
Watchdog failure reset
MASTER has reset due to either a power loss or
some condition that caused the SLAVE to lockup,
in which case the watchdog reset it.
A-4