Fluke Wavetek-Datron 395 - Example Command Tree

TRACE NAMES (numeric label data)
The following restrictions govemparameter names (user waveformnames):
1. They cannot exceed 12 characters in length, preferred length is 4.
2. They must not have any embedded whitespace.
3. They must startwith an alphabetic character. They cannot start with a
numeric, a whitespace,
or an underscore.
4. AlI alphanumeric characters may be used, bOth upper and lower case.
The underscore
L) may also be used.
5. There is no abbreviation for the users trace na me, it must be used as
defined.
The command bierarchy can be represented in three ways; theCOMMAND TREE, the
COMMAND TABLE. or the COMMAND SYNTAX DIAGRAM. AIl three are
illustrated on the fol1owing pages. Refer to Figure 5-3, the Example Command Tree.
5.2.6 Example (Hypothetical) Command Tree
1
POINt
root
~
•• ~ ûTHER
r----- :R~ 7:_SU_B..,-SYSTEMS
1 1
POSition [sTATe) SYNC
1 1
JFF~
1
<trace
name>
5-6 Remote Operation
Figure 5-3. Example (Marker Subsystem) Command Tree
Example command lines for this subsystem follow. Assume a trace name and size have
been entered and a trace name is currently selected. Only the entered trace name is
acted
upon by the commands except in the case of global commands like DELete:ALL or
MODE, etc. The long fonn
of the keywords are given with the approved (or Wavetek
selected) abbreviations in capitals. Items
in bold, with the exception of optional
commands, are minimum requirements.
The first character on the command line is the colon (:). This places the "pointer"
at the
"root" and
just above all subsystems. The leading colon is optional if the command
pointer is already
at the "roof'. The following example shows the development of the
command tine by "walking" down the tree. Select the MARKer subsystem by entering:
: MARKer
Artisan Technology Group - Quality Instrumentation ... Guaranteed | (888) 88-SOURCE | www.artisantg.com