On this page you'll find all possible error messages and their causes. Any of these error messages can be reported by the *ERROR? command. Usually it is only interesting to send the *ERROR? command after receiving an Execution Error prompt !> in response to the last issued command.
The last issued command was completed without any errors. The last command also reported this by sending an OK prompt => .
The last issued command could not be understood. Maybe there was a typing error in the command name, or the command was intended for a completely different SB-Bus device. The last attempt to execute a command resulted in a Syntax Error prompt ?> .
NOTHING TO REPEAT ERROR
You've tried to repeat the last command while the Fluke interface hasn't executed a command yet after it was switched on, so there's nothing to repeat.
The last command was aborted by the user. Usually only the commands that produce longer lists can be aborted, because all the others are finished very fast, and therefore can not be interrupted. You can interrupt longer lists by sending an ESC character to the SB-Bus.
NO PARAMETERS ALLOWED
The command you gave doesn't require any parameters. You did specify one or more parameters though but they can't be accepted.
MISSING PARAMETER ERROR
The command you gave did require one or more parameters but you failed to supply any or enough parameters.
TOO MANY PARAMETERS ERROR
You've supplied more parameters than the command could handle. Please read the command description to find out what parameters are to be expected.
ILLEGAL PARAMETER ERROR
At least one of the parameters you specified after the previous command could not be recognized. This is usually caused by a typing error, or you probably used spaces in the parameter field.
TOO MANY ERRORS
This error can only be generated if the Acknowledge flow control is selected. You must send an acknowledge character (usually = ) to the Fluke interface in response to every line it sends to the SB-Bus. Sending an error prompt ( ! or ? ) 10 times in a row will abort the previous command and will cause this error.
HOLD MODE DEACTIVATED
This error is caused by sending the *HOLD command while the *HOLD mode was already active (with or without a command in *HOLD). The *HOLD mode will be deactivated this way, and a command that was placed on *HOLD will be canceled.
Please note the difference between the system *HOLD command and the normal HOLD command!
HOLD NOT ACTIVE ERROR
The *TRIG command will cause this error when the *HOLD mode was not activated, so there is no command to be executed.
NOTHING IN HOLD ERROR
This error is caused by the *TRIG command when there was no command placed in *HOLD previously. The *HOLD mode will be deactivated when this error occurs.
A value in one of the parameters was out of its legal range. Please refer to the command's description to find out what the legal range of the specific parameter is.
DIVIDE BY 0 ERROR
This error is not very likely to occur. It only occurs when you try to read the MEAN? value immediately (typically within 400 ms) after sending the CLEAR command, or immediately after switching to a different range. In either case it may happen that no measurements are taken yet, so the Fluke interface won't be able to calculate the mean value.
LOG ACTIVE ERROR
Some of the SB-Bus commands are inhibited when the Log function is active. These are the START and the INTERVAL commands. Naturally you can't start an already active Log function and you may not change the interval time during an active Log.
LOG NOT ACTIVE ERROR
The STOP command can cause this error if you try to stop the Log function while it is not running at that moment.