Error Messages in Alphabetical Order
0
130
Sux error
This error, as well as errors
0
131 through
0
139, are generated when parsing a sux. This
particular error message is used if the analyzer cannot detect a more specic error.
0
138
Sux not allowed
A sux was encountered after a numeric element that does not allow suxes.
0
134
Sux too long
The sux contained more than 12 characters (see IEEE 488.2, 7.7.3.4).
0
102
Syntax error
An unrecognized command or data type was encountered. For example, a string was received
when the analyzer was not expecting to receive a string.
0
310
System error
Some error, termed \system error" by the analyzer, has occurred.
T
0
124
Too many digits
The mantissa of a decimal numeric data element contains more than 255 digits excluding
leading zeros (see IEEE 488.2, 7.7.2.4.1).
77
TOO MANY SEGMENTS OR POINTS
Frequency list mode is limited to 31 segments or 801 points
.
64
TOO MANY SEGMENTS
The maximum number of segments for the limit line table is 18.
0
223
Too much data
A legal program data element of block, expression, or string type was received that
contained more data than the analyzer could handle due to memory or related device-specic
requirements.
54
TOO MUCH DATA
Either there is too much binary data to send to the analyzer when the data transfer format is
FORM 2, FORM 3 or FORM 5, or the amount of data is greater than the number of points
.
78
TOO SMALL POINTS OR TOO LARGE STOP
STOP+SPAN/(NOP
0
1) is out of sweep range. Increase NOP or change STOP value to lower
frequency to avoid this error.
0
210
Trigger error
A trigger related error occurred. This error message is used when the analyzer cannot detect
the more specic errors described for errors
0
211 through
0
219.
Messages-13