Keysight 53210A - Page 164

6 53210A Math, Graphing, and Data Logging
164 Keysight 53210A User’s Guide
Example: Limit Checking
The following is an example of enabling and using limit checking.
CONF:FREQ (@1) // configure measurement
SAMP:COUN 500 // check limit on 500 rdgs
CALC:STAT ON // enable math operations
CALC:LIM:STAT ON // enable limit checking
CALC:LIM:LOW 99.9E3;UPP 100.1E3 // set limits
INIT // initiate the measurements
*WAI // wait for readings to complete
STAT:QUES:EVEN? // query questionable data register
Notice that the limits are set on the same line to prevent a settings conflict error.
This Error can also be avoided by enabling limit checking after the limits are set.
Clearing Limit Conditions
The ‘Limit’ annunciator is turned off and bits 11 and 12 (only) in the Questionable
Data Register are cleared by any of the following:
– enabling limit checking
- CALCulate[1]:LIMit[:STATe] ON
– a new measurement cycle - INITiate:IMMediate, READ?, MEASure?
– sending a new SCPI command or changing a current SCPI parameter
– a reset or instrument preset
- *RST, SYSTem:PRESet
These steps also clear all readings in reading memory. (*RST and SYSTem:PREset
additionally reset the lower and upper limits to 0.0.)
To turn off the ‘Limit’ annunciator and clear only the limit-sensing bits (11/12 in
the Condition register) without clearing reading memory, the following command
is used:
CALCulate[1]:LIMit:CLEar[:IMMediate]