MDO3000 Programmer Manual.pdf - 第175页
Commands Listed in Alphabetical Order Group Status and Erro r Syntax ALLEv? Related Commands *ESR? , EVMsg? Examples ALLEV? might return :ALLEV 2225,"Measurem ent error, No wavefor m to meas ure ; "420,"Qu…
Commands Listed in Alphabetical Order
ALIas:DELEte
[:NAMe] (No Query Form)
Removesaspecifiedalias.
Group
Alias
Syntax
ALIas:DELEte[:NAMe] <QString>
Arguments
<QString> is the name of the alias to remove. Using ALIas:DELEte[:NAM e]
without specifying an alias causes an execution error. <QString> must be an
existing alias.
Examples
ALIAS:DELETE[:NAME] “STARTUP” deletes the alias named STARTUP.
ALIas[:STATE]
Turns aliases on or off. (See page 2-13, Alias Command Group.)
Group
Alias
Syntax
ALIas[:STATE] {<NR1>|O FF|ON}
ALIas[:STATE]?
Arguments
OFF or <NR1> = 0 turns alias expansion off. If a defined alias is sent when
ALIas:STATE is OFF, a command error (102) is generated.
ON or <NR1>0 turns alias expansion on. When a defined alias is received, the
specified command sequence is substituted for the alias and executed.
Examples
ALIAS[:STATE] OFF turns the command alias feature off.
ALIAS[:STATE]? returns 0 when the alias feature is off.
ALLEv? (Query Only)
Prompts the oscilloscope to return all events and their messages (delimited by
commas), and removes the
returned events from the Event Queue. Use the *ESR?
query to enable the events to be returned. This command is similar to repeatedly
sending *EVMsg? queries to the oscilloscope.
2-144 MDO4000/B/C, MSO/DPO4000B and MDO3000 Series Oscilloscopes Programmer Manual
Commands Listed in Alphabetical Order
Group
Status and Erro
r
Syntax
ALLEv?
Related Commands
*ESR?, EVMsg?
Examples
ALLEV? might return :ALLEV 2225,"Measurem ent error, No waveform
to meas ure; "420,"Query UNTERMI NATED;"
APPLication:LICENSE:SLOT<x>:LOCation? (Query Only)
This query returns the license location. < x> can be slot number 1-4 (1-2 for
MDO3000 models).
NOTE. In order to use many of the advanced oscilloscope features, you must
purchase an application module that contains a license. A license turns on a
feature that is already present in the firmware. The module can be inserted
into any of the four application module slots in the oscilloscope (two for the
MDO3000 series). While only four of the more than twelve physical application
modules available c an be supported at one time (or two for the MDO3000 s eries),
more than this number of applications can be used simultaneously: a license can
be transferred from the physical application module to an internal location within
the oscilloscope. Once a license has been transferred to an internal location, the
application that it enables can be used without the physical application module
being present; the physical application module can be removed, thus freeing up
a slot. However, the license then needs to be transferred back to the physical
application module in order to use the license with another instrument.
Group
Miscellaneous
Syntax
APPLication:LICENSE:SLOT<x>:LOCation?
Related Commands
APPLication:LICENSE:SLOT<x>:TRANSFER,
APPLication:LICENSE:SLOT<x>:TYPe?
Returns
SCOPE - The license has been transferred to the oscilloscope and is active
internally.
MODULE - The license is in the application module and has not been transferred
to the scope.
MDO4000/B/C, MSO/DPO4000B and MDO3000 Series Oscilloscopes Programmer Manual 2-145
Commands Listed in Alphabetical Order
BOTH - The licen
se is in the application module and the license from another
application module of the same type has already been transferred to the scope.
NEITHER -Thel
icense is neither in the application module nor in the scope's
internal memory. (In this situation, the license must have been transferred to a
different oscilloscope.)
NONE - There is no application module in the slot.
Examples
APPLication:LICENSE:SLOT1:LOCation? might return SCOPE, indicating
that the license is active internally.
APPLication:LICENSE:SLOT<x>:TRANSFER (No Query Form)
You can use this command to transfer a license from a physical application module
to an internal memory location within the oscilloscope, and to transfer it back.
Once a license has been transferred to an internal location, the application that it
enables can be used without the physical application module being present;the
physical application module can be removed, thus freeing up a slot. However,
the license then needs to be transferred back to the physical application module
in order to use the license with another instrument.
After licenses have been transferred, the oscilloscope power must be cycled in
order to enable/disable the features affected by the module. Applications modules
must only be installed and removed when the oscilloscope power is off.
CAUTION. Applications modules must only be installed and removed when the
oscilloscope power is off.
< x> can be slot number 1-4 (1-2 for MDO3000 models).
NOTE. In order to use many of the advanced oscilloscope features, you must
purchase an application module that contains a license. A license turns on a
feature that is already present in the firmware. The module can be inserted
into any of the four application module slots in the oscilloscope (two for the
MDO3000 series). While only four of the more than twelve physical a pplication
modules available can be supported at one time (or two for the MDO3000 series),
more than this number o f applications can be used simultaneously: a license
can be transferred from the physical application module to an internal location
within the oscilloscope.
Conditions
If the license currently resides in the physical application module and the license
does not also reside in the scope, it is transferred to the scope and the license is no
longer in the module.
2-146 MDO4000/B/C, MSO/DPO4000B and MDO3000 Series Oscilloscopes Programmer Manual