Table of Contents
Advertisement
If a character string contains a double quotation mark
(
"
), the double quotation mark will be replaced by two
concatenated double quotation marks (
also applies to a single quotation mark within a
character string.
<Character string data> is an arbitrary character string,
therefore this instrument assumes that the remaining
program message units are part of the character string
if no single (
) or double quotation mark (
'
encountered. As a result, no error will be detected if a
quotation mark is omitted.
<Filename>
Gives the name of a file. The format is as follows.
Form
{<NRf>|<Character data>|<Character string>}
If you input an <NRf> value, the system converts the
value (after rounding to the nearest integer) to the
corresponding 8-character ASCII string. (If you set the
value to 1, the name becomes
negative values are not allowed.
If you enter a <character data> or <character string>
argument that is longer than eight characters, only the
first eight characters are used.
Response messages always return filenames as
<character string> arguments.
<Block data>
<Block data> is arbitrary 8-bit data. <Block data> is
only used for response messages. Response
messages are expressed in the following form.
Form
#N<N-digit decimal value><Data byte string>
#N
Indicates that the data is <Block data>. "
character string number (digits) which indicates the
number of data bytes that follow.
<N-digits decimal value>
Indicates the number of bytes of data. (Example:
00000010 =
10 bytes)
<Data byte string>
The actual data. (Example:
ABCDEFGHIJ
Data is comprised of 8-bit values (0 to 255). This
means that the ASCII code "
"
NL
", can also be a code used for data. Hence, care
must be taken when programming the controller.
IM 253710-11E
). This rule
"""
) is
"
Example
1
CASE
"CASE"
"00000001"
.) Note that
Example
#800000010ABCDEFGHIJ
" is an ASCII
N
)
0AH
", which stands for
3.5 Synchronization with the Controller
3.5 Synchronization with the
Controller
Overlap Commands and Sequential Commands
There are two kinds of command; overlap commands
and sequential commands. Execution of an overlap
command may start before execution of the previously
sent command is completed.
The
[CHANnel1:VOLTage:RANGe]
example, is a sequential command. Assume that you
set a new voltage range value and immediately
request return of the new value, as follows:
:CHANnel1:VOLTage:RANGe 200V;RANGe?<PMT>
In this case, the oscilloscope always returns the
newest setting ("
200V
"). This is because it always
completes processing of the current sequential
command (in this case, "
RANGe 200V
on to the next command ("
RANGe?
In contrast, assume that you begin a file load and then
immediately query the voltage range value:
:FILE:LOAD:SETup "FILE1";:CHANnel1:VOLTage:
RANGe?
Because "
FILE:LOAD:SETup
" is an overlapped
command, the oscilloscope will advance to the
"
CHANNel1:VOLTage:RANGe?
finishes the load. The returned voltage range value
will not show the newest setting, but will rather show
the setting in use before the setup was changed.
Obviously, use of overlapped commands may in some
cases produce inappropriate results. Where
necessary, you can avoid such problems as described
below.
Synchronization with an Overlap Command
Using the *WAI command
The
*WAI
command causes the commands which
follow it to wait until an overlap command has been
executed.
Example
:COMMunicate:OPSE #0040;:FILE:LOAD:
SETup "FILE1";*WAI;:CHANnel1:VOLTage:
<PMT>
The "
COMMunicate:OPSE
" command is used to
designate which commands are to be subject to the
*WAI
command. In the above example, only auto set-
up is designated.
Since a
command is executed just before
*WAI
"
CHANnel1:VOLTage:RANGe?
"
CHANnel1:VOLTage:RANGe?
auto set-up has been completed.
command, for
") before moving
").
" command before it
",
" will not be executed until
3-7
3
Advertisement
Table of Contents
