Stanford Research Systems RGA100, Руководство по эксплуатации и программированию

Страница: 219 / 362

Internal Error Detection in the SRS RGA 9-3
SRS Residual Gas Analyzer
Internal Error Detection in the SRS RGA
Several firmware-driven checks automatically test the RGA when the instrument is
turned on, and continuously monitor the internal workings of the unit. A ““Background
Filament Protection Mode”” is activated, when the filament is turned on to protect the
delicate filament (and CDEM) from accidental overpressures. Several commands can be
used to trigger hardware tests on the ECU. Any one of the internal checks just described
can detect and report errors, but it is the responsibility of the user to monitor the RGA
Head for error reports.
Note : Refer to the last section of this chapter for a listing of the built-in hardware checks
available in the RGA Head.
Important: Even though the hardware tests built into the RGA Head can check the
instrument for a large variety of problems, they cannot detect all possible error
conditions.
There are two ways to detect the presence of errors in the RGA:
1. Visually : Inspecting the red LED’’s on the rear panel of the ECU.
The Error LED is turned on whenever a hardware problem is detected, and it flashes
twice if a communications error is generated during programming.
The Burnt and Leak LED’’s indicate specific filament problems and are turned on, in
addition to the Error LED, whenever the ionizer’’s emission is internally shut down or
not established as requested.
2. Error Queries : Querying the Error Bytes with the Error Reporting commands.
The ““Error Byte Definitions”” section of the RGA Programming chapter describes the
different error bytes used to store the results of the internal checks. The ““Error
Reporting Commands”” query the error bytes and can be used to quickly diagnose
problems.
RGA Windows supports all the Error Reporting commands and constantly monitors the
value of the Error Bytes. ““Error Report”” Windows immediately announce all detected
errors and identify the different problems based on unique Error Codes. Refer to the next
section of this chapter for Troubleshooting information specific to each Error Code.
Users developing their own RGA control software should integrate the Error Reporting
commands into their software, and use them periodically. Consult ““Error Checking the
RGA””, in the RGA Programming chapter of this manual, for details. Use the Error Byte
Definitions listing to obtain the Error Codes for the detected errors.
Error Checking Tips:
x
Keep an eye on all three red (i.e. error reporting) LED’’s while operating the RGA.
x
Diagnose and troubleshoot problems as soon as they are detected.
x
RGA Windows users: Use the Retry button of the Error Report Window to trigger
one or two fresh error checks on the hardware, before declaring a problem.