05-01-2006 04:48 AM
05-01-2006 07:36 AM
From the manual. You know, that thing that no one reads anymore.
SYSTem
:BEEPer
:BEEPer:STATe {OFF|ON}
:BEEPer:STATe?
So you should be able to get the state of the beep using STAT? If it returns OFF then the issue is with Aligent or needs a different command to muzzle this device. Other options would be to use hardware. Put tape over the speaker to make it softer or open the device and cut the speaker wire.
05-02-2006 05:14 AM
Hi Datalog,
Thanks for posting on the NI Forums.
I agree with mfitzsimons suggestions, it would certainly be worth checking the Agilent's beeper state after attempting to set it, although I couldn't really endorse snipping wires on your device...!
It might be worth noting that the manual for this device seems to hint at the beeper only being disabled for the following circumstances:
1) a new minimum or maximum is found in a min-max test.
2) a stable reading is captured in reading hold.
3) a limit is exceeded in a limit test.
4) a forward-biased diode is measured in the diode test function.
I would assume that in any other circumstances the device may still emmit a beep. This would probably be worth confirming with Agilent.
Thanks,
Rob