CALCulate:LIMit:LOWer
Syntax
CALCulate:LIMit:LOWer {<value>|MIN|MAX|DEF}, (@<ch_list>)
CALCulate:LIMit:LOWer? [{MIN|MAX},] (@<ch_list>)
Description
The instrument has four alarms which you can configure to alert you when a reading exceeds specified limits on a multiplexer channel during a scan. This command sets the lower limit for alarms on the specified channels.
Used With:
34921A through 34925A Multiplexer Modules
Parameters
|
Name |
Type |
Range of Values |
Default Value |
|
<value> |
Numeric |
Any value between -120% and +120% of the highest range, for the present function. |
-1.0E+15 |
|
<ch_list> |
Numeric |
One or more channels in the form (@sccc). |
This is a required parameter. |
Remarks
Alarms are evaluated during a scan using the multiplexer modules. For scanning using a multiplexer module, an error is generated if the internal DMM is disabled (see INSTrument:DMM[:STATe] command) or not installed in the mainframe.
You can assign a lower limit, an upper limit (see CALCulate:LIMit:UPPer command), or both to any configured channel in the scan list. The lower limit must always be less than or equal to the upper limit.
Once you have defined the lower limits, use the CALCulate:LIMit:LOWer:STATe command to enable alarms on the specified channels.
The alarms are evaluated by the internal DMM from the time the CALCulate:LIMit:LOWer:STATe ON command is executed.
You must configure the channel (function, transducer type, etc.) before setting any alarm limits. If you change the measurement configuration, alarms are turned off and the limit values are cleared. Alarms are also turned off when you change the temperature probe type, temperature units, or disable the internal DMM.
You can assign multiple channels to any of the four available alarms (numbered 1 through 4, see OUTPut:ALARm<n>:SOURce command). For example, you can configure the instrument to generate an alarm on the Alarm 1 output when a limit is exceeded on any of channels 1003, 2005, or 3010. You cannot, however, assign alarms on a specific channel to more than one alarm number.
If you plan to use alarms on a channel which will also use Mx+B scaling, be sure to configure the scaling values first. If you attempt to assign the alarm limits first, the instrument will turn off alarms and clear the limit values when you enable scaling on that channel. If you specify a custom measurement label with scaling, it is automatically used when alarms are logged on that channel.
If you redefine the scan list, alarms are no longer evaluated on those channels (during a scan) but the limit values are not cleared. If you decide to add a channel back to the scan list (without changing the function), the original limit values are restored and alarms are turned back on. This makes it easy to temporarily remove a channel from the scan list without entering the alarm values again.
To generate an alarm when a specific count is reached on a totalizer channel (34950A and 34952A), see the CALCulate:LIMit:UPPer command. To generate an alarm when a specific bit pattern or bit pattern change is detected on a digital input channel, see the CALCulate:COMPare commands.
The instrument clears all alarm limits and turns off all alarms after a Factory Reset (*RST command), Instrument Preset (SYSTem:PRESet command), or Card Reset (SYSTem:CPON command).
Return Format
The query command returns the lower limit in the form "-1.00000000E+15" for each channel specified. Multiple responses are separated by commas.
Examples
The following command sets the lower limit to -0.25 on channels 3 and 13 in slot 1.
CALC:LIM:LOW -0.25,(@1003,1013)
The following query returns the limit settings on channels 3 and 13 in slot 1.
CALC:LIM:LOW? (@1003,1013)
Typical Response: -2.50000000E-01,-2.50000000E-01