Gaussmeter IGM11 Operating Instructions
Chapter 9 Serial Interfaces
Page 64 / 106
MAGSYS
magne t
systeme
Version 01/2013
© 2013 MAGSYS magnet syste
me GmbH - All Rights Reserved.
9.10.3
SCPI Data Types
The SCPI data language defines different data formats that are used in a program
message and in a reply message. An SCPI device can normally accept commands
and parameters in different formats. In particular the numerical parameters can be
used very freely. Contrary to this general definition, the data formats are restricted in
some places here.
9.10.3.1
Numerical Parameter
Commands that require numerical parameters, accept the generally used decimal
notation of numerical characters including leading characters, decimal points and
leading zeros. The scientific notation is supported. The technical unit is preset for
most commands and will then not be transmitted. For some commands the unit is
part of the command being an additional parameter.
9.10.3.2
Discrete Parameter
Discrete parameters are used in order to program setups that have a limited amount
of values. You have a long and a short form for command key words. Upper and
lower case can be mixed. Replies to queries are always only emitted in long form and
in upper case.
9.10.3.3
Boolean Parameter
Boolean parameters represent a single state that is either true or false. As a false
value the gaussmeter accepts "OFF" or "0". As a true value the gaussmeter accepts
"ON" or "1". If a Boolean set-up is queried, the device always emits "0" or "1".
9.10.3.4
Character String Parameter
Character string parameters can, in principle, contain a limited amount of ASCII-
characters. A character string must begin and end with either an apostrophe (',
0x
27h
) or with a quotation mark (", 0
x22h
), with the same character at the
beginning and at the end of the character string. The delimiter can be used within the
character string, if it occurs twice in the string without any blank.
9.10.3.5
Line Ending
Program messages that are sent to the gaussmeter must end with an
<LF>
character.
Likewise a
<CR>
character followed by an
<LF>
character is accepted. By terminating
a message, the current path is always set back to the root node.
Trial Version
Subje
ct to chan
ge