Filter
Top Products
21
Getting Started
N9061A General Rules and Limitations
Markers
The N9071A application emulates the behavior of legacy products. If someone uses a marker state which
is not available in the legacy instrument, further marker behavior is undefined until instrument preset.
On systems that supported MKACT, there are 4 completely different marker pairs, each with its own
information. The N9061A will store the currently active value of MKACT. If MKACT is 2 then it will
use Markers 3 and 4 instead of 1 and 2.
Parsing
For 8566B and 8568B, the N9061A will remember the active function and supports UP, DN, and OA, all
of which change the active function. It also supports '?', which does not change the active function.
One difference between N9061A and 8566/68 is that the 8566/68 parses a command for example CF
10.3GZ, immediately when it recognizes a complete command, in this example after the GZ. However
the N9061A parses at the end of a line when it sees the line termination sequence.
Couplings
To provide the most optimized use of the X-Series analyzers, the N9061A application uses the auto
coupling features of the X-Series analyzers and does not attempt to mimic the exact behavior of coupling
in the legacy analyzers. To eliminate the possibilities of "Meas Uncal" errors between auto and manual
values, values will default to the X-Series auto settings where applicable (for example resolution
bandwidth). There are several exceptions below.
To prevent timeout errors in the legacy code, the resolution bandwidth minimum matches the minimum
in the legacy analyzer. Resolution bandwidth steps and resolution, however, will be X-Series values.
The video bandwidth will couple to the resolution bandwidth according to the Video bandwidth coupling
offset value, specified by the VBO or VBR command. The X-Series analyzers sets the video bandwidth
according to the VBO or VBR setting, but uses the X-Series analyzers available bandwidths to prevent
'Meas Uncal' errors.
Predefined Functions
In the 8566/8568/8560 Series analyzers, a “predefined function” is an analyzer command that returns a
number that can be operated on by other analyzer commands. “Predefined variables” follow the same
idea, except the value to be passed as a parameter to the next command is stored in a variable.
The N9061A application does not support this type of behavior, so any commands that originally acted
as predefined functions or variables, or that allowed predefined functions or variables as arguments in
the 8566/8568/8560 Series no longer do so.
User-defined Functions
No user-defined functions, traces, or variables (FUNCDEF, TRDEF or VARDEF) can be used as
arguments or commands in programs controlling any analyzer running the N9061A application. In
addition, the behavior of certain commands that rely on the “active functions” (UP, DN, etc.) may be
slightly different.