-160 to -168Block data errorsThe multimeter does not accept block data.-170 to -178Expression errorsThe multimeter does not accept mathematical expressions.-211Trigger ignored

A Group Execute Trigger (GET) or *TRG was received but the trigger was ignored. Make sure the multimeter is in the “wait-for-trigger” state before issuing a trigger, and make sure the correct trigger source is selected.

-213Init 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 multimeter in the “idle” state.

-214Trigger deadlock

A trigger deadlock occurs when the trigger source is BUS and a READ? command is received.

-221Settings conflictThis error can be generated in one of the following situations:

You sent a CONFigure or MEASure command with autorange enabled and with a fixed resolution. Example: CONF:VOLT:DC DEF,0.1

You turned math on (CALC:STAT ON) and then changed to a math operation that was not valid with the present measurement function. For example, dB measurements are not allowed with 2-wire ohms. The math state is turned off as a result of this condition.

-222Data out of range

A numeric parameter value is outside the valid range for the command. Example: TRIG:COUN -3

-223Too much data

A character string was received but could not be executed because the string length was more than 12 characters. This error can be generated by the CALibration:STRing and DISPlay:TEXT commands.

-224Illegal parameter value

A discrete parameter was received which was not a valid choice for the command. You may have used an invalid parameter choice. Examples: CALC:FUNC SCALE (SCALE is not a valid choice) or SAMP:COUN ON (ON is not a valid choice).

-230Data stale

A FETCh? command was received but internal reading memory was empty. The reading retrieved may be invalid or settings have changed since the data was taken.

Appendix B

HP E1312A and HP E1412A Multimeter Error Messages 187