6100 MPS-B Programming Manual

WRITING APPLICATIONS THAT USE 6100 MPS-B
Status Codes and Status Detail Codes
For some codes, an additional status detail code is returned in
the response buffer Text field. If the Status field contains a
value greater than zero and the Text In field contains a value
equal to or greater than 2, a status detail code can be found in
the Text field.
For example, if the status code is 22 (invalid parameter), the
status detail code might be 12 (invalid station address). Your
application can check the code in the Status field and then, if
necessary, check the Text field for more information.
Table 3-1 lists the status codes together with a description of
their meaning. Table 3-2 lists the same type of information for
the status detail codes.
Table 3-1. Status Code Values Returned by 6100 MPS-B
(Continued on next page)
-----------------------------------------------------------------
| |
| Code |
|(Decimal) Description |
| |
| 0 The request completed as expected. |
| |
| 22 Invalid parameter. A field in the request buffer |
| had an illegal value. The Text field contains a |
| status detail code identifying the invalid |
| parameter. |
| |
| 28 Too many requests. Only one CONTROL, READ, or |
| WRITE requests is permitted at a time. |
| |
| 32 No memory available. 6100 MPS-B cannot allocate |
| READ buffer or Poll List memory space. |
| |
| 122 Request aborted. This or some other process |
| issued an abort request. |
| |
| 140 Modem error. The Text field contains a status |
| detail code identifying the error. |
| |
| 160 Invalid request for current line state. The Text |
| field contains a status detail code identifying |
| the line state (line not configured, line not |
| polled, Poll/Select list not defined, or I/O |
| active). |
| |
-----------------------------------------------------------------
3-12