
Document No: LT0499
RDU Mk2 Installation & Programming Manual
Programming Part 1
Issue 1.02
8 April 2015
Page 6-41
6.6
ERROR MESSAGES DURING CONFIGURATION
Listed below are some error messages that can appear on the LCD during installation.
Refer also to the Operator Manual for a list of error and event messages.
Error messages that can occur on start-up
"Shift reg clocking fault"
"Invalid # shift regs.Total # regs=xxx # input regs=xxx"
These messages indicate a hardware fault with the shift register bus that connects the
Controller with MAF/PSU module. The fault could be on the Controller, the interconnecting
FRCs or any of the connected boards. Try with different cables.
"Shift reg driver fault"
This message indicates a problem with the software driver for the shift register bus.
"Clock crystal timebase check fail"
"Clock chip ram write read fail"
"Clock register write read fail"
"Clock startup fault"
These messages indicate a hardware fault on the Controller.
“Firmware checksum fail”
"Eprom CRC fail"
These messages indicate the checksum of the software program code is incorrect. This can
be caused by a damaged/corrupted memory chip or some other hardware fault on the
controller.
Error messages that can occur on entry to program mode
1. "Flash database version error Must reinit or reload database."
This message appears on entry to program mode and indicates that the database was
created with a different version of software and cannot be used. This message does not
appear if the database checksum is incorrect so it indicates the database is valid but
incompatible with this software version.
2. "WARNING-the database in flash is invalid. Recommend save->PC before save to
flash."
This message appears on entry to program mode if the database checksum is
incorrect.
Error messages that can occur on exit from program mode
1. "Flash database checksum fail. Processing is disabled."
This indicates the database checksum is invalid and the panel is non-operational. A
"DBASE CHKSUM ERROR"
event is also logged.
2. "History queue is being cleared"
This indicates that the size of the history queue has been decreased to enable the print
queue. This occurs when the programmable option to enable or disable event printing is
changed from disable to enable. When event printing is disabled, the history queue uses
the memory normally used for event printing.