Owner manual

Protocol Faults
Appendix C: Error Messages 221
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.
Here is a list of possible reasons that could be causing this error:
 No tag in the RF field
 Read/write power too low
 Antenna not connected
 Tag is weak or dead
Solution
Make sure there is a good tag in the field and all parameters are set up correctly. The best
way to check this is to try few tags of the same type to rule out a weak tag. If none
passed, then it could be SW configuration such as protocol value, antenna, and so forth,
or a placement configuration like a tag location.
FAULT_NO_PROTOCOL_DEFINED – 401h
Cause
A command was received to perform a protocol command but no protocol was initially
set. The reader powers up with no protocols set.
Solution
A Set Current Tag Protocol (63h) command must be sent followed by resending the
desired command.
FAULT_INVALID_PROTOCOL_SPECIFIED – 402h
Cause
A Set Current Tag Protocol (63h) command was received for a protocol value that is not
supported with the current version of SW.