Keysight x-series Instruction Manual

3 Short-Range Comms & IoT Mode
3.5 Channel Power Measurement
the [:SENSe]:AVERage[:STATe] command description below
–
:TRACe:MODE WRITe sets :TRACe:TYPE WRITe (Clear/Write) unless average is true, in
which case it sets it to :TRACe:TYPE AVErage. It also sets :TRACe:UPDate ON,
:TRACe:DISPlay ON, for the selected trace
–
:TRACe:MODE MAXHold sets :TRACe:TYPE MAXHold (Max Hold). It also sets
:TRACe:UPDate ON, :TRACe:DISPlay ON, for the selected trace
–
:TRACe:MODE MINHold sets :TRACe:TYPE MINHold (Min Hold). It also sets
:TRACe:UPDate ON, :TRACe:DISPlay ON, for the selected trace
–
:TRACe:MODE VIEW sets :TRACe:UPDate OFF, :TRACe:DISPlay ON, for the selected
trace
–
:TRACe:MODE BLANk sets :TRACe:UPDate OFF, :TRACe:DISPlay OFF, for the
selected trace
The query returns the same value as :TRACe:TYPE?, meaning that if you set :TRACe:MODE:VIEW
or :TRACe:MODE:BLANk, the query response will not be what you sent
:TRACe[n]:MODE was formerly used to set the type or “writing mode” of the trace. At that time,
View and Blank were writing modes. The new :TRACe:TYPE command should be used in the future,
but :TRACe:MODE is retained to provide backwards compatibility
In X-Series, unlike earlier instruments, Max Hold and Min Hold now obey the Average Number and
counts up to a terminal value as Average always has
As the Average/Hold Number now affects Min Hold and Max Hold, the operations that restart
Averaging (for example, the Restart key) now also restart Min Hold and Max Hold
As a result of these changes, legacy code that restarts averaging while retaining a running Max Hold
will need to be rewritten, because the Max Hold will now restart when the Average does
Also, previous to X-Series:
–
Pressing Max Hold while already in Max Hold (or doing so remotely) had no effect. Now it will clear
the trace and restart the sweep and the Max Hold sequence
–
Changing the vertical scale (Log/Lin or dB/div) of the display restarted Max Hold and Min Hold.
This is no longer the case
Preset
OFF
State Saved The state of Average is saved in Instrument State for ghosting purposes
Backwards
Compatibility
SCPI
[:SENSe]:AVERage[:STATe] ON | OFF | 1 | 0
[:SENSe]:AVERage[:STATe]?
Backwards
Compatibility
Notes
Previous to X-Series, Averaging (also sometimes known as trace averaging) was global to all traces,
that is, it was either on or off for all active traces. The legacy command [:SENSe]:AVERage
[:STATe] ON|OFF|1|0 was used to turn Averaging on or off
In X-Series, Averaging is turned on or off on a per-trace basis, so it can be on for one trace and off for
another
For backwards compatibility, the old global Average State variable is retained solely as a legacy
666 Short Range Comms & IoT Mode User's &Programmer's Reference

Keysight x-series Specifications

General

Analysis Bandwidth	Up to 1 GHz (depending on model)
Real-Time Bandwidth	Up to 1 GHz (depending on model)
Form Factor	Benchtop
Connectivity	LAN, USB, GPIB
Resolution Bandwidth	1 Hz to 10 MHz (depending on model)