Remote Command Examples; Compound Headers Using A Tree - Usage And Examples - Fluke BT5300 Series User Manual

Remote Command Examples

Compound Headers Using a Tree – Usage and Examples
Figure 47 presents the instrument command structure that has implemented compound headers
using a tree structure. Headers were chosen with short form mnemonic value.
Figure 47. Compound header organization example using a tree
Then the following commands shall behave as described:
•
:CALC:AVER:STATE ON;:MEM:STATE ON<PMT> The leading colon (:) in the second <PROGRAM
MESSAGE UNIT> puts the parser at the top of the command tree. Both paths are legal.
•
:CALC:AVER:STATE ON<PMT>MEM:STATE ON<PMT> The first <PMT> puts the parser at the top of
the command tree. A leading colon (:) at the beginning of the next <PROGRAM MESSAGE UNIT>
is unnecessary because the previous <PROGRAM MESSAGE UNIT> in a <PROGRAM
MESSAGE> starts the parser at the root.
•
:MEM:STAT ON;CLE;COUN?<PMT>The entire path is not given in the second and third <PROGRM
MESSAGE UNIT> elements. Because the "CLE" and "COUN" are referenced to the same tree
level as the "STAT", ":MEM:" is assumed to be prefixed to the second and third <PROGRM
MESSAGE UNIT> elements. This commands is equivalent to :MEM:STAT
ON;:MEM:CLE;:MEM:COUN?<PMT>
•
:SYST:LANG ENG;CUST:MOD?;MAN?<PMT> Same as 3), the second and third <PROGRAM
MESSAGE UNIT> elements are assumed to be prefixed by the implied prefix of the immediately
previous command, ":SYST:". This command is equivalent to :SYST:LANG
ENG;:SYST:CUST:MOD?;:SYST:CUST:MAN?<PMT>
•
:SYST:LANG ENG;*IDN?;CUST:MOD?;MAN?<PMT> The insertion of the common commands has no
effect on the application of the prefixing rules. This command is equivalent to :SYST:LANG
ENG;*IDN?;:SYST:CUST:MOD?;:SYST:CUST:MAN?<PMT>
Battery Tester
Remote Control
107