When using, for example, a telnet client to control the unit, it is enough just type commands and
press enter to send the command.
6.2.2
Protocol Errors
Below is a list of possible errors and their explanations. They can be retrieved using
tSYSTem:ERRor[:NEXT]?
-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 defined in IEEE-
488.2, 11.5.1.1.4 has occurred.
-102,"Syntax error"
. An unrecognized command or data type was encountered.
-105,"GET not allowed"
. A Group Execute Trigger was received within a program mes
sage (see IEEE-488.2, 7.7).
-108,"Parameter not allowed"
. Parameter given for command which does not have any
parameters.
-109,"Missing parameter"
. Command requiring parameter(s) is issued without them.
-112,"Program mnemonic too long"
. Protocol keyword too long. All keywords are less
than 12 characters long.
-113,"Undefined header"
. The header is syntactically correct, but it is undefined for this
specific device; for example, BXYZ is not defined for any device.
-120,"Numeric data error"
. Number format is not recognized.
-129,"Numeric data out of range"
. Numeric parameter value is invalid.
-140,"Character data error"
. This error, as well as errors 141 through –149, is
generated when parsing a character data element. This particular error message is
used when the device cannot detect a more specific error.
-141,"Invalid character data"
. Either the character data element contains an invalid char
acter or the particular element received is not valid for the header.
-148,"Character data not allowed"
. Character data detected when number is expected.
-150,"String data error"
. String. This error as well as errors –151 through –159 is gen
erated when parsing a string data element. This particular error message is used when
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 allowed"
. String data detected when number is expected.
-160,"Block data error”
. This error, as well as errors –161 through –169, is generated
when parsing a block data element. This particular error message is used when the instru
ment cannot detect a more specific error.
6.2 Protocol
CHAPTER
6
•
User Manual GSG-5/6 Series
Rev.
26
215
Summary of Contents for GSG-5 series
Page 2: ......
Page 4: ...Blank page II User Manual GSG 5 6 Series...
Page 116: ...BLANK PAGE 3 6 Options Menu 100 CHAPTER 3 User Manual GSG 5 6 Series Rev 26...
Page 182: ...BLANK PAGE 4 9 Studioview Tasks 166 CHAPTER 4 User Manual GSG 5 6 Series Rev 26...
Page 368: ...BLANK PAGE 6 7 Revision History SCPI Guide 352 CHAPTER 6 User Manual GSG 5 6 Series Rev 26...
