Appendix Ifirmware Log - Kipp & Zonen Brewer Mk III Operator's Manual

APPENDIX I
Messages appearing in the Instrument Log (accessed using the RL command) have the following
format:
yyyy ddd hh mm ss <message part 1>
yyyy ddd hh mm ss <message part 2>
...
yyyy ddd hh mm ss <message part n>
The 'yyyy ddd hh mm ss' identifies the time on the instrument clock at the time when the message
was recorded. The possible values of <message part 1> are given below. Usually there is only the
<message part 1>.
<name>: Bad arraySpacing, AddVectors().
Please notify KIPP & ZONEN <info.holland@kippzonen.com> of the circumstances in which
this message was generated.
<name>: Can't add preexisting symbol.
Please notify KIPP & ZONEN <info.holland@kippzonen.com> of the circumstances in which
this message was generated.
<name>: Enum type mismatch.
Please notify KIPP & ZONEN <info.holland@kippzonen.com> of the circumstances in which
this message was generated.
<name>: Hash table too full.
Please notify KIPP & ZONEN <info.holland@kippzonen.com> of the circumstances in which
this message was generated.
<name>: Symbol not found.
Please notify KIPP & ZONEN <info.holland@kippzonen.com> of the circumstances in which
this message was generated.
A command used only by one mode was entered in another mode.
Please notify KIPP & ZONEN <info.holland@kippzonen.com> of the circumstances in which
this message was generated.
Analog: initialization timed out.
During initialization the circuitry used to read analog input channels failed to initialize
properly.
Attempt to exceed max boundary
An M command was issued to a position beyond the highest in the range of the motor.
Instead it was moved to the highest legal position.
Attempt to exceed min boundary
An M command was issued to a position beyond the lowest in the range of the motor.
Instead it was moved to the lowest legal position.
Bad command, no config variables:
A command was issued which required configuration when no configuration was loaded. The
subsequent message indicates the command. If the instrument is in Cosmac mode at the
time, it also responds immediately with "Sorry, need configuration variables."
FIRMWARE LOG
MKIII OPERATOR'S MANUAL
APPENDIX I FIRMWARE LOG
127