3 Short-Range Comms & IoT Mode
3.12 Monitor Spectrum Measurement
Example
:TRAC:TYPE WRIT
:TRAC:TYPE?
Couplings Selecting a Trace Type (by pressing any of the Trace Type selections or sending :TRAC:TYPE) sets
the Trace to Active (Update: ON, Display: OFF), even if the same trace type was already selected
When Detector setting is “Auto” ([:SENSe]:<meas>:DETector:AUTO?), Detector
([:SENSe]:<meas>:DETector[:FUNCtion]?) switches aligning with the switch of this
parameter: “NORMal” with WRITe (Clear Write), “AVERage” with AVERage, “POSitive (peak)”
with MAXHold, and “NEGative (peak)” with MINHold
Preset Swept SA and Monitor Spectrum: WRITe
All other measurements: AVERage
Following Preset, all traces are cleared (all trace points set to mintracevalue)
State Saved The type of each trace is saved in instrument state
Annunciation The type for each trace is indicated in the Trace annunciator panel on the Measurement Bar
Trace Mode Backwards Compatibility Commands
In earlier instruments, the “Trace Modes” were: Clear/Write, Max Hold, Min Hold,
View and Blank. Averaging was global to all traces and was controlled under the
BW/Avg menu.
In X-Series, trace averaging can be done on a per-trace basis. The Trace Modes
(now called Trace Types) are Clear/Write, Trace Average, Max Hold and Min Hold.
View and Blank are set separately under "View/Blank" on page 1736.
While this provides more flexibility, it also gives rise to potential backwards
compatibility problems. To mitigate these, the old Trace Mode command has been
retained and a new Trace Type command has been added. The :TRACe:MODE
command is retained for backwards compatibility, and the :TRACe:TYPE,
:TRACe:UPDate and :TRACe:DISPlay commands introduced for ongoing use. The
old Trace Modes are selected using :TRAC:MODE, whose parameters are mapped
into calls to :TRACe:TYPE, :TRACe:UPDate and :TRACe:DISPlay, and the old
global Averaging command [:SENSe]:AVERage[:STATe] is provided for
backwards compatibility. See the individual command descriptions for details.
When Average/Hold in the Meas Setup, Legacy Compatibility menu is ON, the
following is true for traces in Max Hold and Min Hold:
–
They ignore the Average/Hold number; Single for Max Hold causes one sweep
only, so switching to Single stops after the current sweep, and switching to Cont
starts again without clearing the accumulated result
–
Max Hold is not cleared on a Restart, Single or :INIT:IMM, but changing a
measurement parameter, like frequency or bandwidth etc., still restarts the Max
Hold
Preset
WRITe
1732 Short Range Comms & IoT Mode User's &Programmer's Reference
To Next Page
Loading...
Need help?
General
