MIL-STD-1553 Reference Manual
Chapter 12– Troubleshooting
Error Reporting by ApiIo Function Call – Point 3
At point 3, command status and acknowledgement information is returned by the Target
software to the ApiIo function. If the command status indicates an error, an error message as
shown in Figure 12.1-4 will be displayed:
Figure12.1-4 _ApiIo Driver Command Status Error
Error detected: _ApiIo() for module:
a
, biu:
b
returned API_ERR (cmd =
xxxxxxxx
, tg=c, err_msg=d)
Where:
a is the API module number/destination board
b is the bus interface unit (1 or 2)
xxxxxxxx is an 8 digit hexadecimal number where the last two digits are
associated with the driver command utilized for the function call (See Table
0.2-I)
c is the error returned by the Target software
d is the error returned to the module address (should be the same as c)
If the returned acknowledgement status is not what the API S/W Library function indicated to
expect from the Target software, an error message as shown in Figure 12.1-5 will be displayed:
Figure12.1-5 Did Not Get Expected Ack – Acknowledgement Error
Error detected: Did not get expected ACK for module
a
, biu:
b
(cmd =
xxxxxxxx
,
expected
c
, ret
d
)
Where:
a is the API module number/destination board
b is the bus interface unit (1 or 2)
xxxxxxxx is an 8 digit hexadecimal number where the last two digits are
associated with the driver command utilized for the function call (See Table
0.2-I)
c is the expected acknowledgement code expected as defined by the library
function call
d is the returned response code received from the Target software
After either of the two error messages as shown in Figures 12.1-4 and 12.1-5 are received, an
error message routine will be called to interpret the error code and acknowledgment codes
returned by the Target S/W. Another error message will immediately follow which is shown in
To Next Page
Loading...