User`s manual

505150 PROCESSORS
63
Terminal Diagnostics
The results of the last startup self-test can also be viewed using the diagnostics screen in the terminal
protocol. Enter “D” to display this screen. A startup self-test result code will be displayed as an 8-bit
number: ABCDEFGH. Bits that are 1 indicate failures. These failure bits are interpreted as follows:
Startup Diagnostics in Terminal “D” Mode
A=1 Flash checksum test failed
B=1 EVEN regular RAM byte test failed
C=1 ODD regular RAM byte test failed
D=1 EVEN non-volatile RAM byte test failed
E=1 ODD non-volatile RAM byte test failed
F, G, H Not used, always zero
In addition, the diagnostics screen shows the last several errors detected by the software. A startup
failure is shown as “Startup Tests ABCDEFGH”,, where ABCDEFGH has the same interpretation
described above. If for example the even regular RAM byte test failed five different times during startup,
the message “Startup Tests 01000000” would be displayed five times. If there is no error the screen will
display the detectable errors:
 startup self-test failure
 panel polling failure
 vertical sync interrupt failure
 crosspoint output vertical interrupt callback failure
 DIP Switch mismatch with master processor
Processor Health
If a processor fails one of its startup diagnostics or the processor detects an operational failure, i.e. no
vertical sync or control panel network, the processor considers itself “sick”. The LEDd flashed to inform
the user that it has detected a problem. Otherwise, LEDc is lit to indicate normal operation. Any time a
processor has LEDd flashing, it indicates that something in the system is wrong. Use the protocol “D”
(DIAG) screen to make sure the processor didn’t fail its startup diagnostics or a processor fails.
It is possible for a processor to flash LEDd briefly and then stop if it should detect a problem. If this
happens, it would indicate a software failure.
LEDe and LEDf indicate the health of the redundant processor explained in the next section. Besides
monitoring their own health, both processors continually report to and monitor the other processor. If the
other processor stops reporting that it is okay, LEDf is flashed to tell the user that the other processor is
not working properly. Otherwise, LEDe is turned on to indicate that the other processor appears to be
working properly.