198
Software Library Reference Manual for VME 429
Section 10 – Troubleshooting
After either of the two error messages as shown in Figures 10.1-4 and 10.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 Figure 10.1-6. Upon completion of the display
of this error message,
Target communication will be aborted
and
switched
automatically into emulation mode
to prevent further Target I/O errors. The library
should then be closed and opened again with a call to the
Api429Reset
function to
force initial states on the Target hardware and Target S/W.
Figure 10.1-6 Target S/W Status and Acknowledge Interpretation Message
(a) Error message CMD:xxxxxxxxh ACK:yyyyh!
Where:
(a) Error message is
"(1) General I/O Error"
"(2) ACK returned"
"(3) ACK2 returned"
"(4) NAK returned"
"(5) Acknowledge Error"
"(6) Target Communication closed"
"ERROR NO: (
a
) " for unknown error code
xxxxxxxx
is an 8 digit hexadecimal number where the first two digits are
associated with the biu number and the last two digits are associated
with the driver command utilized for the function call (See Table 10.2-I)
yyyy
is an 4 digit hexadecimal number where the first two digits are associated
with the biu number and the last two digits are 20h (ACK), 22h (ACK2),
24h (No Acknowledge (NAK), or 26h (NAK2).
At this point if the
ApiIo
function received a status error code from _ApiIo (Target
S/W detected error) then prior to completion of the
ApiIo
function, an error message
"
ERROR in function
" message as shown in Figure 10.1-2 will occur with
ApiIo
as
the function name. Since the error code is reserved for Target S/W errors, it will be
interpreted as (unknown) by the
ApiIo
function.
Summary of Contents for AMC429
Page 2: ......
