Document: LT0344 Vigilant MX1 Operator Manual
Issue 2.4 8 August 2017 Page 4-7
Retrieval of non-volatile event messages failed during
system start up.
The LCD/Keyboard microprocessor has restarted.
A user able to use Level 3 functions logged on or
logged off, respectively.
The values of non-volatile logic variables were reset
(usually following a restore failure). All nonvolatile
variables will be initialised to FALSE.
Retrieval of non-volatile logic variables failed during
start up.
Non-volatile point disable states were reset (usually
following a restore failure). All points will have
become ENABLED.
Pnt disables restore fail
Retrieval of non-volatile point disable states failed
during start up.
The printer queue was over filled, so some events to
be printed were lost.
The MX1 internal checking routines have detected an
inconsistency that needs to be addressed. Xxx,
yyyyyyyy show the details of the fault. If this occurs
repeatedly contact your service company.
An operator command was received from a connected
RZDU.
An RZDU failed to report that a self-test passed within
4 minutes of starting.
The MX1 internal checking routines have detected an
inconsistency that needs to be addressed.
xxx,yyyyyyyy show the details of the faults. If this
occurs contact your service company.
This is a daily timestamp, indicating the system is
working.
A temporary access password has been used to log
onto the MX1.
The system time has been changed. The new time is
used for the event.
The MX1 has restarted without being powered down,
for example, to change the datafile.
Non-volatile zone disable states were reset (usually
following a restore failure). All zones will have
become ENABLED.
Retrieval of non-volatile zone disable states failed
during start up.