Appendix A – Error Messages
The ESP300 controller has an elaborate command interpreter and
system monitor. Every command is analyzed for syntax and correct
format after it is received. The result of the analysis is stored in an
output buffer in plain English. During moves and while, idle system
inputs are monitored and any change is reported to the user via the
output buffer. To read the contents of the output buffer, send the
command
TB (tell buffer).
For more compact error messages, use the
TE command. The ESP300
controller response to this command is a one byte; binary coded error
number, e.g., 33.
0 NO ERROR DETECTED
No errors exist in the output buffer.
1 PCI COMMUNICATION TIME-OUT
2 Reserved for future use
3 Reserved for future use
4 EMERGENCY SOP ACTIVATED
5 Reserved for future use
6 COMMAND DOES NOT EXIST
The issued command does not exist. Check the Command Syntax.
The specified parameter is out of range. Refer to the description of
issued command for valid parameter range.
For the sake of convenience, error messages are divided into two
categories – non-axis specific error messages and axis specific error
messages. Below is a list of all possible ESP300 controller error
messages that are not axis specific:
A communication transfer was initiated through PCI bus interface and
was never completed.
An emergency stop was executed because the motion controller
received a '#' character or "STOP ALL AXES" button was pressed.
7 PARAMETER OUT OF RANGE
Appendix A – Error Messages A-1
To Next Page
Loading...
Need help?
General
