CALCulate:LIMit:LOWer:STATe
Syntax
CALCulate:LIMit:LOWer:STATe <mode>, (@<ch_list>)
CALCulate:LIMit:LOWer:STATe? (@<ch_list>)
Description
This command disables or enables the lower alarm limits on the specified multiplexer channels.
Used With:
34921A through 34925A Multiplexer Modules
Parameters
|
Name |
Type |
Range of Values |
Default Value |
|
<mode> |
Boolean |
{OFF|0|ON|1} |
Limit OFF |
|
<ch_list> |
Numeric |
One or more channels in the form (@sccc). |
This is a required parameter. |
Remarks
Alarm data can be stored in one of two locations depending on whether a scan list is running when the alarm occurs.
If an alarm event occurs on a channel as it is being scanned, then that channel's alarm status is stored in reading memory as the readings are taken. Each reading that is outside the specified alarm limit is logged in memory. You can store at least 500,000 readings in memory during a scan.
As alarm events are generated, they are also logged in an alarm queue, which is separate from reading memory. This is the only place that non-scanned alarms get logged (alarms during a channel monitor, alarms generated by the digital modules, etc.). Up to 20 alarms can be logged in the alarm queue. If more than 20 alarm events are generated, they will be lost (only the first 20 alarms are saved). Even if the alarm queue is full, the alarm status is stored in reading memory during a scan.
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.
When an alarm occurs, the instrument stores relevant information about the alarm in the queue. This includes the reading that caused the alarm, the time of day and date of the alarm, and the channel number on which the alarm occurred. The information stored in the alarm queue is always in absolute time and is not affected by the FORMat:READing:TIME:TYPE command setting.
Alarms are logged in the alarm queue only when a reading crosses a limit, not while it remains outside the limit and not when it returns to within limits.
In addition to being stored in reading memory, alarms are also recorded in their own SCPI Status System. You can configure the instrument to use the status register to generate a Service Request (SRQ) when alarms are generated. For more information on the SCPI Status System for the Agilent 34980A, see Status System Introduction.
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 "0" (OFF) or "1" (ON) for each channel specified. Multiple responses are separated by commas.
Examples
The following program segment sets a lower limit on channels 3 and 13 in slot 1 and then enables alarms on these channels.
CALC:LIM:LOW -0.25,(@1003,1013) CALC:LIM:LOW:STAT ON,(@1003,1013)
The following query returns the state of lower limits on channels 3 and 13 in slot 1.
CALC:LIM:LOW:STAT? (@1003,1013)
Typical Response: 1,1