содержание .. 26 27 28 29 ..
FTB-2 и FTB-2 Pro. Руководство пользователя - часть 28
D SCPI-Based Errors
Error
Description
Probable Cause
Number
–100
“Command error”
This is the generic syntax error for devices that
cannot detect more specific errors.
This code indicates only that a Command Error as
defined in IEEE 488.2, 11.5.1.1.4 has occurred.
-101
“Invalid character”
A syntactic element contains a character which is
invalid for that type; for example, a header
containing an ampersand, SETUP&.
This error might be used in place of errors -114,
-121, -141, and perhaps some others.
-102
“Syntax error”
An unrecognized command or data type was
encountered; for example, a string was received
when the device does not accept strings.
-103
“Invalid separator”
The parser was expecting a separator and
encountered an illegal character; for example, the
semicolon was omitted after a program message
unit, *EMC 1:CH1:VOLTS 5.
-104
“Data type error”
The parser recognized a data element different
than one allowed; for example, numeric or string
data was expected but block data was
encountered.
-105
“GET not allowed”
A Group Execute Trigger was received within a
program message (see IEEE 488.2, 7.7).
-108
“Parameter not
More parameters were received than expected for
allowed”
the header; for example, the *EMC common
command only accepts one parameter, so
receiving *EMC 0,1 is not allowed.
-109
“Missing parameter”
Fewer parameters were received than required for
the header; for example, the *EMC common
command requires one parameter, so receiving
*EMC is not allowed.
FTB-2 and FTB-2 Pro
423
SCPI-Based Errors
Error
Description
Probable Cause
Number
-110
“Command header
An error was detected in the header. This error
error”
message should be used when the device cannot
detect the more specific errors described for errors
-111 through -119.
-111
“Header separator
A character which is not a legal header separator
error”
was encountered while parsing the header; for
example, no white space followed the header, thus
*GMC"MACRO" is an error.
-112
“Program mnemonic
The header contains more that twelve characters
too long”
(see IEEE 488.2, 7.6.1.4.1).
–113
“Undefined header”
The header is syntactically correct, but it is
undefined for this specific device; for example,
*XYZ is not defined for any device.
-114
“Header suffix out of
The value of a numeric suffix attached to a
range”
program mnemonic (see IEEE 488.2, Syntax and
Style section 6.2.5.2) makes the header invalid.
-115
“Unexpected number
The number of parameters received does not
of parameters”
correspond to the number of parameters
expected. This is typically due an inconsistency
with the number of instruments in the selected
group (see section on
INSTrument:DEFine:GROup).
-120
“Numeric data error”
This error, as well as errors -121 through -129, are
generated when parsing a data element which
appears to be numeric, including the non-decimal
numeric types.This particular error message
should be used if the device cannot detect a more
specific error.
-121
“Invalid character in
An invalid character for the data type being parsed
number”
was encountered; for example, an alpha in a
decimal numeric or a "9" in octal data.
424
FTB-2 and FTB-2 Pro
SCPI-Based Errors
Error
Description
Probable Cause
Number
-123
“Exponent too large”
The magnitude of the exponent was larger than
32000 (see IEEE 488.2, 7.7.2.4.1).
-124
“Too many digits”
The mantissa of a decimal numeric data element
contained more than 255 digits excluding leading
zeros (see IEEE 488.2, 7.7.2.4.1).
-128
“Numeric data not
A legal numeric data element was received, but
allowed”
the device does not accept one in this position for
the header.
-130
“Suffix error”
This error, as well as errors -131 through -139, are
generated when parsing a suffix. This particular
error message should be used if the device cannot
detect a more specific error.
-131
“Invalid suffix”
The suffix does not follow the syntax described in
IEEE 488.2, 7.7.3.2, or the suffix is inappropriate for
this device.
-134
“Suffix too long”
The suffix contained more than 12 characters (see
IEEE 488.2, 7.7.3.4).
-138
“Suffix not allowed”
A suffix was encountered after a numeric element
which does not allow suffixes.
-140
“Character data error”
This error, as well as errors -141 through -149, are
generated when parsing a character data element.
This particular error message should be used if the
device cannot detect a more specific error.
-141
“Invalid character data”
Either the character data element contains an
invalid character or the particular element
received is not valid for the header.
-144
“Character data tool
The character data element contains more than
long”
twelve characters (see IEEE 488.2, 7.7.1.4).
–148
“Character data not
A legal character data element was encountered
allowed”
where prohibited by the device.
FTB-2 and FTB-2 Pro
425
SCPI-Based Errors
Error
Description
Probable Cause
Number
-150
“String data error”
This error, as well as errors -151 through -159, are
generated when parsing a string data element. This
particular error message should be used if the
device cannot detect a more specific error.
-151
“Invalid string data”
A string data element was expected, but was
invalid for some reason (see IEEE 488.2, 7.7.5.2);
for example, an END message was received before
the terminal quote character.
-158
“String data not
A string data element was encountered but was
allowed”
not allowed by the device at this point in parsing.
–160
“Block data error
This error, as well as errors -161 through -169, are
generated when parsing a block data element. This
particular error message should be used if the
device cannot detect a more specific error.
-161
“Invalid block data”
A block data element was expected, but was
invalid for some reason (see IEEE 488.2, 7.7.6.2);
for example, an END message was received before
the length was satisfied.
-168
“Block data not
A legal block data element was encountered but
allowed”
was not allowed by the device at this point in
parsing.
-170
“Expression error”
This error, as well as errors -171 through -179, are
generated when parsing an expression data
element. This particular error message should be
used if the device cannot detect a more specific
error.
-171
“Invalid expression”
The expression data element was invalid (see IEEE
488.2, 7.7.7.2); for example, unmatched
parentheses or an illegal character.
-178
“Expression data not
A legal expression data was encountered but was
allowed”
not allowed by the device at this point in parsing.
426
FTB-2 and FTB-2 Pro
SCPI-Based Errors
Error
Description
Probable Cause
Number
-180
“Macro error”
This error, as well as errors -181 through -189, are
generated when defining a macro or executing a
macro. This particular error message should be
used if the device cannot detect a more specific
error.
-181
“Invalid outside macro
Indicates that a macro parameter placeholder
definition”
($<number) was encountered outside of a macro
definition.
-183
“Invalid inside macro
Indicates that the program message unit sequence,
definition”
sent with a *DDT or *DMC command, is
syntactically invalid (see IEEE 488.2, 10.7.6.3).
-184
“Macro parameter
Indicates that a command inside the macro
error”
definition had the wrong number or type of
parameters.
-200
“Execution error”
This is the generic syntax error for devices that
cannot detect more specific errors. This code
indicates only that an Execution Error as defined in
IEEE 488.2, 11.5.1.1.5 has occurred.
-201
“Invalid while in local”
Indicates that a command is not executable while
the device is in local due to a hard local control
(see IEEE 488.2, 5.6.1.5); for example, a device with
a rotary switch receives a message which would
change the switches state, but the device is in local
so the message can not be executed.
-202
“Settings lost due to rtl”
Indicates that a setting associated with a hard local
control (see IEEE 488.2, 5.6.1.5) was lost when the
device changed to LOCS from REMS or to LWLS
from RWLS.
-203
“Command protected”
Indicates that a legal password-protected program
command or query could not be executed
because the command was disabled.
FTB-2 and FTB-2 Pro
427
SCPI-Based Errors
Error
Description
Probable Cause
Number
-210
“Trigger error”
-----
–211
“Trigger ignored”
Indicates that a GET, *TRG, or triggering signal was
received and recognized by the device but was
ignored because of device timing considerations;
for example, the device was not ready to respond.
Note: a DT0 device always ignores GET and treats
*TRG as a Command Error.
-212
“Arm ignored”
Indicates that an arming signal was received and
recognized by the device but was ignored.
-213
“Init ignored”
Indicates that a request for a measurement
initiation was ignored as another measurement
was already in progress.
-214
“Trigger deadlock”
Indicates that the trigger source for the initiation of
a measurement is set to GET and subsequent
measurement query is received. The
measurement cannot be started until a GET is
received, but the GET would cause an
INTERRUPTED error.
-215
“Arm deadlock”
Indicates that the arm source for the initiation of a
measurement is set to GET and subsequent
measurement query is received. The
measurement cannot be started until a GET is
received, but the GET would cause an
INTERRUPTED error.
-220
“Parameter error”
Indicates that a program data element related error
occurred. This error message should be used
when the device cannot detect the more specific
errors described for errors -221 through -229.
-221
“Settings conflict”
Indicates that a legal program data element was
parsed but could not be executed due to the
current device state (see IEEE 488.2, 6.4.5.3 and
11.5.1.1.5).
428
FTB-2 and FTB-2 Pro
SCPI-Based Errors
Error
Description
Probable Cause
Number
-222
“Data out of range”
Indicates that a legal program data element was
parsed but could not be executed because the
interpreted value was outside the legal range as
defined by the device (see IEEE 488.2, 11.5.1.1.5).
-223
“Too much data”
Indicates that a legal program data element of
block, expression, or string type was received that
contained more data than the device could handle
due to memory or related device-specific
requirements.
-224
“Illegal parameter
Used where exact value, from a list of possible,
value”
was expected.
–225
“Out of memory”
The device has insufficient memory to perform the
requested operation.
-226
“Lists not same length”
Attempted to use LIST structure having individual
LIST's of unequal lengths.
-230
“Data corrupt or stale”
Possibly invalid data; new reading started but not
completed since last access.
-231
“Data questionable”
Indicates that measurement accuracy is suspect.
–232
“Invalid format”
Indicates that a legal program data element was
parsed but could not be executed because the data
format or structure is inappropriate. For example
when loading memory tables or when sending a
SYSTem:SET parameter from an unknown
instrument.
FTB-2 and FTB-2 Pro
429
SCPI-Based Errors
Error
Description
Probable Cause
Number
-233
“Invalid version”
Indicates that a legal program data element was
parsed but could not be executed because the
version of the data is incorrect to the device. This
particular error should be used when file or block
data formats are recognized by the instrument but
cannot be executed for reasons of version
incompatibility. For example, a not supported file
version, a not supported instrument version
-240
“Hardware error”
Indicates that a legal program command or query
could not be executed because of a hardware
problem in the device. Definition of what
constitutes a hardware problem is completely
device-specific. This error message should be used
when the device cannot detect the more specific
errors described for errors -241 through -249.
-241
“Hardware missing”
Indicates that a legal program command or query
could not be executed because of missing device
hardware; for example, an option was not
installed. Definition of what constitutes missing
hardware is completely device-specific.
-250
“Mass storage error”
Indicates that a mass storage error occurred. This
error message should be used when the device
cannot detect the more specific errors described
for errors -251 through -259.
-251
“Missing mass storage”
Indicates that a legal program command or query
could not be executed because of missing mass
storage; for example, an option that was not
installed. Definition of what constitutes missing
mass storage is device-specific.
-252
“Missing media”
Indicates that a legal program command or query
could not be executed because of a missing
media; for example, no disk. The definition of what
constitutes missing media is device-specific.
430
FTB-2 and FTB-2 Pro
SCPI-Based Errors
Error
Description
Probable Cause
Number
-253
“Corrupt media”
Indicates that a legal program command or query
could not be executed because of corrupt media;
for example, bad disk or wrong format. The
definition of what constitutes corrupt media is
device-specific.
-254
“Media full”
Indicates that a legal program command or query
could not be executed because the media was full;
for example, there is no room on the disk. The
definition of what constitutes a full media is
device-specific.
-255
“Directory full”
Indicates that a legal program command or query
could not be executed because the media
directory was full. The definition of what
constitutes a full media directory is device-specific.
-256
“File name not found”
Indicates that a legal program command or query
could not be executed because the file name on
the device media was not found; for example, an
attempt was made to read or copy a nonexistent
file. The definition of what constitutes a file not
being found is device-specific.
-257
“File name error”
Indicates that a legal program command or query
could not be executed because the file name on
the device media was in error; for example, an
attempt was made to copy to a duplicate file name.
The definition of what constitutes a file name error
is device-specific.
-258
“Media protected”
Indicates that a legal program command or query
could not be executed because the media was
protected; for example, the write-protect tab on a
disk was present.The definition of what constitutes
protected media is device-specific.
FTB-2 and FTB-2 Pro
431
SCPI-Based Errors
Error
Description
Probable Cause
Number
-260
“Expression error”
[Indicates that a expression program data element
related error occurred. This error message should
be used when the device cannot detect the more
specific errors described for errors -261 through -
269.]
-261
“Math error in
[Indicates that a syntactically legal expression
expression”
program data element could not be executed due
to a math error; for example, a divide-by-zero was
attempted. The definition of math error is
device-specific.]
-270
“Macro error”
[Indicates that a macro-related execution error
occurred. This error message should be used
when the device cannot detect the more specific
errors described for errors -271 through -279.]
-271
“Macro syntax error”
[Indicates that a syntactically legal macro program
data sequence, according to IEEE 488.2, 10.7.2,
could not be executed due to a syntax error within
the macro definition (see IEEE 488.2, 10.7.6.3).]
-272
“Macro execution
[Indicates that a syntactically legal macro program
error”
data sequence could not be executed due to some
error in the macro definition (see IEEE 488.2,
10.7.6.3).]
-273
“Illegal macro label”
[Indicates that the macro label defined in the
*DMC command was a legal string syntax, but
could not be accepted by the device (see IEEE
488.2, 10.7.3 and 10.7.6.2); for example, the label
was too long, the same as a common command
header, or contained invalid header syntax.]
-274
“Macro parameter
[Indicates that the macro definition improperly
error”
used a macro parameter placeholder (see IEEE
488.2, 10.7.3).]
432
FTB-2 and FTB-2 Pro
SCPI-Based Errors
Error
Description
Probable Cause
Number
-275
“Macro definition too
[Indicates that a syntactically legal macro program
long”
data sequence could not be executed because the
string or block contents were too long for the
device to handle (see IEEE 488.2, 10.7.6.1).]
-276
“Macro recursion
[Indicates that a syntactically legal macro program
error”
data sequence could not be executed because the
device found it to be recursive (see IEEE 488.2,
10.7.6.6).]
-277
“Macro redefinition not
[Indicates that a syntactically legal macro label in
allowed”
the *DMC command could not be executed
because the macro label was already defined (see
IEEE 488.2, 10.7.6.4).]
-278
“Macro header not
[Indicates that a syntactically legal macro label in
found”
the *GMC? query could not be executed because
the header was not previously defined.]
-280
“Program error”
[Indicates that a downloaded program-related
execution error occurred. This error message
should be used when the device cannot detect the
more specific errors described for errors -281
through -289. A downloaded program is used to
add algorithmic capability to a device. The syntax
used in the program and the mechanism for
downloading a program is device-specific.]
-281
“Cannot create
[Indicates that an attempt to create a program was
program”
unsuccessful. A reason for the failure might include
not enough memory.]
-282
“Illegal program name”
[The name used to reference a program was
invalid; for example, redefining an existing
program, deleting a nonexistent program, or in
general, referencing a nonexistent program.]
-283
“Illegal variable name”
[An attempt was made to reference a nonexistent
variable in a program.]
FTB-2 and FTB-2 Pro
433
SCPI-Based Errors
Error
Description
Probable Cause
Number
-284
“Program currently
[Certain operations dealing with programs may be
running”
illegal while the program is running; for example,
deleting a running program might not be possible.]
-285
“Program syntax error”
[Indicates that a syntax error appears in a
downloaded program. The syntax used when
parsing the downloaded program is
device-specific.]
-286
“Program runtime
-----
error”
-290
“Memory use error”
[Indicates that a user request has directly or
indirectly caused an error related to memory or
<data_handle>, this is not the same as “bad”
memory.]
-291
“Out of memory”
-----
–292
“Referenced name
-----
does not exist”
-293
“Referenced name
-----
already exist”
-294
“Incompatible type”
[Indicates that the type or structure of a memory
item is inadequate]
-300
“Device-specific error”
[This is the generic device-dependent error for
devices that cannot detect more specific errors.
This code indicates only that a Device-Dependent
Error as defined in IEEE 488.2, 11.5.1.1.6 has
occurred.]
-310
“System error”
[Indicates that some error, termed "system error"
by the device, has occurred. This code is
device-dependent.]
-311
“Memory error”
[Indicates some physical fault in the device's
memory, such as parity error.]
434
FTB-2 and FTB-2 Pro
SCPI-Based Errors
Error
Description
Probable Cause
Number
-312
“PUD memory lost”
[Indicates that the protected user data saved by the
*PUD command has been lost.]
-313
“Calibration memory
[Indicates that nonvolatile calibration data used by
lost”
the *CAL? command has been lost.]
–314
“Save/Recall memory
[Indicates that the nonvolatile data saved by the
lost”
*SAV? command has been lost.]
–315
“Configuration
[Indicates that nonvolatile configuration data saved
memory lost”
by the device has been lost. The meaning of this
error is device-specific.]
-320
“Storage fault”
[Indicates that the firmware detected a fault when
using data storage. This error is not an indication of
physical damage or failure of any mass storage
element.]
-321
“Out of memory”
[An internal operation needed more memory than
was available.]
-330
“Self-test failed”
-----
–340
“Calibration failed”
-----
–350
“Queue overflow”
[A specific code entered into the queue in lieu of
the code that caused the error. This code indicates
that there is no room in the queue and an error
occurred but was not recorded.]
-360
“Communication
[This is the generic communication error for
error”
devices that cannot detect the more specific errors
described for errors -361 through -363.]
-361
“Parity error in program
[Parity bit not correct when data received for
message”
example, on a serial port.]
–362
“Framing error in
[A stop bit was not detected when data was
program message”
received for example, on a serial port (for example,
a baud rate mismatch).]
FTB-2 and FTB-2 Pro
435
SCPI-Based Errors
Error
Description
Probable Cause
Number
-363
“Input buffer overrun”
[Software or hardware input buffer on serial port
overflows with data caused by improper or
nonexistent pacing.]
-365
“Time out error”
[This is a generic device-dependent error.]
–400
“Query error”
[This is the generic query error for devices that
cannot detect more specific errors. This code
indicates only that a Query Error as defined in IEEE
488.2, 11.5.1.1.7 and 6.3 has occurred.]
-410
“Query INTERRUPTED”
[Indicates that a condition causing an
INTERRUPTED Query error occurred (see IEEE
488.2, 6.3.2.3); for example, a query followed by
DAB or GET before a response was completely
sent.]
-420
“Query
[Indicates that a condition causing an
UNTERMINATED”
UNTERMINATED Query error occurred (see IEEE
488.2, 6.3.2.2); for example, the device was
addressed to talk and an incomplete program
message was received.]
-430
“Query DEADLOCKED”
[Indicates that a condition causing an
DEADLOCKED Query error occurred (see IEEE
488.2, 6.3.1.7); for example, both input buffer and
output buffer are full and the device cannot
continue.]
-440
“Query
[Indicates that a query was received in the same
UNTERMINATED after
program message after an query requesting an
indefinite response”
indefinite response was executed (see IEEE 488.2,
6.5.7.5).]
-500
“Power on”
[The instrument has detected an off to on
transition in its power supply.]
-600
“User request”
[The instrument has detected the activation of a
user request local control.]
436
FTB-2 and FTB-2 Pro
SCPI-Based Errors
Error
Description
Probable Cause
Number
-700
“Request control”
[The instrument requested to become the active
IEEE 488.1 controller-in-charge.]
-800
“Operation complete”
[The instrument has completed all selected
pending operations in accordance with the IEEE
488.2, 12.5.2 synchronization protocol.]
FTB-2 and FTB-2 Pro
437
содержание .. 26 27 28 29 ..