On this page you'll find the 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 device 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, however 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.
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 device 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.
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.
HOLD NOT IMPLEMENTED ERROR
Due to limited resources and the limited usefulness of the *HOLD command in this device it was decided not to implement this functionality.
The uploading of the Intel HEX file was aborted due to a checksum error.
HEX FORMAT ERROR
The uploading of the Intel HEX file was aborted because it contained data that was not formatted according to the Intel HEX file protocol.