Filter
Top Products
146 Digitizers Error Messages Appendix C
-123 Numeric overflow A numeric parameter was found whose exponent was larger than
32,000. Example: SAMP:COUN 1E34000
-124 Too many digits A numeric parameter was found whose mantissa contained more than
255 digits, excluding leading zeroes.
-128 Numeric data not
allowed
A numeric parameter was found but a character string was expected.
Check the list of parameters to verify you have used a correct
parameter type. Example: TRIG:SOUR 2 EXT (should be TRIG:SOUR2
EXT)
-138 Suffix not allowed A suffix was received following a numeric parameter which does not
accept a suffix. Example: SAMP:COUN 1 SEC (SEC is not a valid suffix).
-148 Character data not
allowed
A character string was received but a numeric parameter was
expected. Check the list of parameters to verify that you have used a
valid parameter type. Example: CAL:VAL XYZ
-158 String data not
allowed
A character string was received but is not allowed for the command.
Check the list of parameters to verify that you have used a valid
parameter type. Example: CALC:LIM:LOW:STAT 'ON
-160 to -168 Block data errors The digitizer does accept block data.
-170 to -178 Expression errors The digitizer does not accept mathematical expressions.
-211 Trigger ignored A Group Execute Trigger (GET) or *TRG was received but the trigger
was ignored. Make sure the digitizer is in the “wait-for-trigger” state
before issuing a trigger, and make sure the correct trigger source is
selected.
-213 Init ignored An INITiate command was received but could not be executed
because a measurement was already in progress. Send a device clear
to halt a measurement in progress and place the digitizer in the “idle”
state.
-214 Sample Trigger
deadlock
You tried to read data before readings are finished, but the sample
source is keeping readings from being taken. It is possible to request
reading data before the measurment is entirely completed, and
normally this will work.
However, if your sample source is BUS or HOLD and you request
reading data, the instrument can no longer receive the command to
begin sampling because it is busy waiting to bring back data - a
deadlock could occur. So, we generate an error when we detect this
situation and abort the fetching of data.
-215 Arm Trigger
deadlock
Same situation as for Sample Trigger deadlock, except the Trigger
source (or Arm source) is set to BUS or HOLD (which requires a
software command to proceed), so you would be deadlocked waiting
for a trigger which could never occur because the system is busy
waiting for data to show up in the reading buffer.
Number Title Description