2 User Interface
2.15 Status Bar
peak found”
–
A condition is an occurrence of finite duration, that is, it has a start and an end.
Conditions are states of the analyzer characterized by some combination of
settings or some kind of failure that the user needs to be told about while it is
happening, but then can stop being told once it goes away; for example “Input
overload; ADC over range”
The error queue contains error events as well as the DETECTED and CLEARED
events for condition errors, as seen in the figure above.
DETECTED events have numbers less than 1000 and CLEARED events have the
same number plus 1000. For example,
301, Meas Uncal – DETECTED
and later
1301, Meas Uncal – CLEARED
To detect a condition error over SCPI, you should read the error queue and note any
DETECTED error which is not followed eventually by an associated CLEARED error.
This means the condition is still in effect. It is not sufficient to simply read the error
queue until you get “No Errors” back. You may still have the condition error; the
condition may still be in effect, and if that is the case, all you have done by clearing
the error queue is to remove the first event (the DETECTED event) from the queue.
For a condition error, you have to read the error queue until you see the CLEARED
event for that condition. THEN you know that the condition is gone.
Current Conditions
The Current Conditions display shows all of the open conditions in the instrument.
An open condition is a condition error or warning for which a start (detected) event
has occurred but for which no corresponding stop (cleared) event has occurred.
An example of the Current Conditions screen appears below:
Spectrum Analyzer Mode User's &Programmer's Reference 150
To Next Page
Loading...
Need help?
General
