User Manual

Protocol Faults
53
Protocol Faults
The following table lists the common faults discussed in this section.
FAULT_NO_TAGS_FOUND – (400h)
Cause
A command was received (such as like read, write, or lock) but the operation failed. There are
many reasons that can cause this error to occur.
Fault Message Code
FAULT_NO_TAGS_FOUND – (400h)
400h
FAULT_NO_PROTOCOL_DEFINED – 401h
401h
FAULT_INVALID_PROTOCOL_SPECIFIED – 402h
402h
FAULT_WRITE_PASSED_LOCK_FAILED – 403h
403h
FAULT_PROTOCOL_NO_DATA_READ – 404h
404h
FAULT_AFE_NOT_ON – 405h
405h
FAULT_PROTOCOL_WRITE_FAILED – 406h
406h
FAULT_NOT_IMPLEMENTED_FOR_THIS_PROTOCOL – 407h
407h
FAULT_PROTOCOL_INVALID_WRITE_DATA – 408h
408h
FAULT_PROTOCOL_INVALID_ADDRESS – 409h
409h
FAULT_GENERAL_TAG_ERROR – 40Ah
40Ah
FAULT_DATA_TOO_LARGE – 40Bh
40Bh
FAULT_PROTOCOL_INVALID_KILL_PASSWORD – 40Ch
40Ch
FAULT_PROTOCOL_KILL_FAILED - 40Eh
40Eh
FAULT_GEN2 PROTOCOL_OTHER_ERROR - 420h
420h
FAULT_GEN2_PROTOCOL_MEMORY_OVERRUN_BAD_PC -
423h
423h
FAULT_GEN2 PROTOCOL_MEMORY_LOCKED - 424h
424h
FAULT_GEN2 PROTOCOL_INSUFFICIENT_POWER - 42Bh
42Bh
FAULT_GEN2 PROTOCOL_NON_SPECIFIC_ERROR - 42Fh
42Fh
FAULT_GEN2 PROTOCOL_UNKNOWN_ERROR - 430h
430h