Rockwell Automation 8520-9API 9/Series OCI API Developer's Guide - Manual (Page 216)

Appendix
E C
Publication 8520-6.6. - August 1999
OCI Error Handling
The table on the following pages lists the errors that can be returned or generated
by your OCI system. The text files for these error strings can not be edited and
are not in ASCII text form. If you purchased the optional basic display set
source code, you can use the routine GetMsgString to call error messages.
GetMsgString is found in the Global.BAS module and must be passed the integer
error message number to return the text string of the appropriate error message.
API Data Request Errors
Requests to the OCI data server that are invalid are returned as a text string to the
requesting item. For example if you are requesting AXIS_NAME(7) and only 6
axes are configured on the system, the value of AXIS_NAME would be “Server
Error [29]”. Always test returned data for the string “Server Error” before
presenting data to your application.
Command and Data Item POKE Errors
The following tables list the error or status messages returned by the OCI data
server or CNC when you issue a command or data item request. The server will
return the Error Number as data for the API data items. When POKE requests
are made to data items errors (or success indication) are returned to the API item
WRITE_ERROR_CODE. In the case of commands errors are returned to the
API data item COMMAND_ERROR_CODE.
Error Num: Error Name:
Misc. System Errors:
0 "OK"
1 "FILE DOESN'T EXIST"
2 "CONTINUE TO 'RE-RUN' THIS TEST?"
3 "*** CORRUPTED PASSWORD FILE ***"
4 "*** INCORRECT PASSWORD ***"
5 "*** MISSING PASSWORD FILE ***"
6 "CANNOT LINK:"
7 "DIVIDE BY ZERO"
8 "MISSING LATHE/MILL 'PD' FILES"
9 "CORRUPTED"
10 "MISSING GRINDER 'SPD' FILES"
11 "MISSING LATHE/MILL 'SPD' FILES"
12 "MISSING PROMPT FILES"
OCI Error Handling
Overview