EasyManua.ls Logo

Hioki 3560 - Separators; Abbreviation of Compound Commands

Hioki 3560
156 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
59
────────────────────────────────────────────────────
7.2 Operating Procedure (RS-232C)
────────────────────────────────────────────────────
7
.2.8 Separators
7
.2.9 Abbreviation of Compound Commands
(1) Message unit separator
A semicolon (;) is used as a message unit separator when it is desired to
set out several messages on a single line.
When message are combined in this way, if a syntax error occurs, all
subsequent messages up to the next delimiter will be ignored.
Example :RRAN 3E‑2;:VRAN 50;:MEAS:BATT?
(2) Header separator
In a message which has a header and data, a apace (represented by "
"(space) in the examples) is used as the header separator to separate the
header from the data.
Example :COMPARATOR 1
(3) Data separator
If a message has several data items, commas (,) are required as data
separators for separating these data items from one another.
Example :CSET:RPAR
data1,data2
When several compound headers have a common head portion (for
example, :CSET:
), then, when and only when writing them directly
following on from one another, this common portion (:CSET: in this
example) can be omitted.
This common portion is called "the current path", by analogy with the
general concept of the current directly in the directly structure of UNIX
or MSDOS, and until it is cleared the analysis of following commands is
performed by deeming them to be preceded by the current path is shown
in the following example:
Normal expression
:CSET:NUMBer;:CSET:RPARameter
Abbreviated expression
:CSET:NUMBer;RPARameter
The current path is cleared when the power is turned on, when a colon (:)
appears at the start of a command, and when delimiter is detected.
Messages with particular headers can be executed without relation to the
current path. Further, they have no effect upon the current path.
While simple and complex command headers don’t require a colon ": "
prefix, we recommend using the colon to avoid confusion with abbreviated
expressions and to prevent 3560 malfunction.
With the 3560, there are 3 possible current paths:
":CSET", ":LOCK", ":MEAS"

Table of Contents

Related product manuals