Omega Vehicle Security 1400 User Manual
ChartScan User’s Manual,
1-4-99
G-1
Appendix G
ChartScan Error Messages
At initial power-up, ChartScan performs automatic self-tests to ensure it is fully functional. Rear-panel LEDs
indicate errors, if they occur. Possible error conditions and their corresponding indicator light patterns are
shown in the following table. Any pattern not shown indicates an internal error that is not field-serviceable; in
this case, contact the factory.
indicate errors, if they occur. Possible error conditions and their corresponding indicator light patterns are
shown in the following table. Any pattern not shown indicates an internal error that is not field-serviceable; in
this case, contact the factory.
When only the POWER and ERROR LEDs are on, a configuration error exists as a
result of the setup information in NV-RAM.
result of the setup information in NV-RAM.
If you observe a configuration error, refer to E? in Appendix A; then perform an
error status query. If you observe any other type of error condition, make note of
the error and contact your service representative.
error status query. If you observe any other type of error condition, make note of
the error and contact your service representative.
If no problems are found, ChartScan will begin its power-up initialization. This self-test is performed each
time the unit is
time the unit is
powered up, regardless of whether power-up is initiated by the power switch, or the Power-On Reset (*R)
command.
LED Indications of Error Conditions
Error Condition
LED Indicators
ALARM
TRIGGER
SCAN
ERROR
POWER
General Hardware Failure
ON
ON
-Flash-
ON
ROM Invalid for
U22, COMM2
-Flash-
ON
ROM Checksum Error for
U21, COMM1
ON
-Flash-
ON
ROM Checksum Error for
U22, COMM2
ON
-Flash-
ON
Non-Volatile RAM Error
ON
-Flash-
ON
Dynamic RAM Error
ON
ON
-Flash-
ON
Interprocessor COM Error
ON
ON
ON
-Flash-
ON
Configuration Error
ON
ON
Error Status Query (E?) is used to determine the present error condition. After execution of the E?
command, ChartScan will respond with one of several possible error codes, as indicated below.
command, ChartScan will respond with one of several possible error codes, as indicated below.
E000: No error has occurred.
E001: Invalid device dependent command (IDDC) due to a command syntax error.
E002: Invalid device dependent command option (IDDCO). A command parameter was out of range
or missing.
or missing.
E004: A Channel Configuration Error indicates that a channel has been inappropriately configured,
either because the channel is not present or because the specified channel type is not compatible with
the card type installed.
either because the channel is not present or because the specified channel type is not compatible with
the card type installed.
E008: A Calibration Error occurs when the card calibration has failed or has been inappropriately
calibrated.
calibrated.
E016: A Trigger Overrun Error occurs when more than one trigger event occurs for a given trigger
state or when a non-expectant trigger event occurs.
state or when a non-expectant trigger event occurs.
E032: An Open T/C Error or Range Error, occurs when the hardware circuitry detects an open
thermocouple, or when the software detects the A/D input has reached or exceeded its linearization.
thermocouple, or when the software detects the A/D input has reached or exceeded its linearization.
E064: Custom Table Error indicates that a Custom Table has been inappropriately defined or has not
been loaded properly. This error usually occurs because Custom Table is out of memory or the
inappropriate specification of the Set Table Entry Pointer (W) command.
been loaded properly. This error usually occurs because Custom Table is out of memory or the
inappropriate specification of the Set Table Entry Pointer (W) command.
E128: A Command Conflict Error indicates the issuance of a command that is in conflict with other
commands that have been issued or the current configuration. This error usually occurs when a
command is issued that cannot be performed because of the current state of the unit. For instance, if
commands that have been issued or the current configuration. This error usually occurs when a
command is issued that cannot be performed because of the current state of the unit. For instance, if