Table of Contents
Advertisement
Troubleshooting and Diagnostics
This section describes how the Model 241CE II Analyzer detects and
displays alarms associated with its operation, what the alarms mean, and
action to take to correct the alarms. This section also discusses how to
view the alarms from the User Interface and how to reset the analyzer if a
system reset is required.
Generally, most troubleshooting and diagnostics can be done by working
from the User Interface on the front of the analyzer's Electronics Enclo-
sure.
About Alarms and Status Codes
The analyzer incorporates a built-in diagnostics function that continuous-
ly monitors key operating parameters and the progression of each stage of
the measuring cycle.
If the diagnostics function detects parameter values that are different from
the established norm or if the measuring cycle stage ends abnormally,
primary Status Code (SCode) messages are generated. The SCode, which
is the sum of the primary SCodes, can be viewed from the Stat\History
menu. The SCode is also presented on an analog output channel (which
allows you to view it on the User Interface). Primary SCodes relating to
analyzer performance set alarms which trigger relay contacts that turn
on LEDs on the User Interface. Alarms are generated if the determined
HCDP temperature is above the preset value or if other operating thresh-
old parameters exceed (fall below/rise above) their predetermined values.
A description of each alarm is recorded in the appropriate sub-menu
(SCode or XSCode) in the Stat\History menu. The alarm description is
preceded by 'w' for a warning alarm (example, "w TimeOut") or 'f ' for a
Fault alarm (example, "f Cool Cct"). After an alarm has been corrected, it
is stored in its corresponding History Buffer (^SC or ^XSC). A history
of the last nine alarms generated by the analyzer (if they have been cor-
rected) can be logged in each buffer.
|
Maintenance and Troubleshooting
6-31
Advertisement
Table of Contents
Troubleshooting
