User Manual
Table Of Contents
- Communication Regulation Information
- Chapter 1: Introducing the Mercury Embedded Reader
- Chapter 2: Setting Up the Reader
- Chapter 3: Using the Reader Assistant
- Appendix A: Hardware Details
- Appendix B: Error Messages
- Common Error Messages
- FAULT_MSG_WRONG_NUMBER_OF_DATA - (100h)
- FAULT_INVALID_OPCODE - (101h)
- FAULT_UNIMPLEMENTED_OPCODE - 102h
- FAULT_MSG_POWER_TOO_HIGH - 103h
- FAULT_MSG_INVALID_FREQ_RECEIVED (104h)
- FAULT_MSG_INVALID_PARAMETER_VALUE - (105h)
- FAULT_MSG_POWER_TOO_LOW - (106h)
- FAULT_UNIMPLEMENTED_FEATURE - (109h)
- FAULT_INVALID_BAUD_RATE - (10Ah)
- Bootloader Faults
- Flash Faults
- Protocol Faults
- FAULT_NO_TAGS_FOUND - (400h)
- FAULT_NO_PROTOCOL_DEFINED - 401h
- FAULT_INVALID_PROTOCOL_SPECIFIED - 402h
- FAULT_WRITE_PASSED_LOCK_FAILED - 403h
- FAULT_PROTOCOL_NO_DATA_READ - 404h
- FAULT_AFE_NOT_ON - 405h
- FAULT_PROTOCOL_WRITE_FAILED - 406h
- FAULT_NOT_IMPLEMENTED_FOR_THIS_PROTOCOL - 407h
- FAULT_PROTOCOL_INVALID_WRITE_DATA - 408h
- FAULT_PROTOCOL_INVALID_ADDRESS - 409h
- FAULT_GENERAL_TAG_ERROR - 40Ah
- FAULT_DATA_TOO_LARGE - 40Bh
- FAULT_PROTOCOL_INVALID_KILL_PASSWORD - 40Ch
- FAULT_PROTOCOL_KILL_FAILED - 40Eh
- FAULT_GEN2 PROTOCOL_OTHER_ERROR - 420h
- FAULT_GEN2_PROTOCOL_MEMORY_OVERRUN_BAD_PC - 423h
- FAULT_GEN2 PROTOCOL_MEMORY_LOCKED - 424h
- FAULT_GEN2 PROTOCOL_INSUFFICIENT_POWER - 42Bh
- FAULT_GEN2 PROTOCOL_NON_SPECIFIC_ERROR - 42Fh
- FAULT_GEN2 PROTOCOL_UNKNOWN_ERROR - 430h
- Analog Hardware Abstraction Layer Faults
- Tag ID Buffer Faults
- System Errors
- Common Error Messages
- Appendix C: Antennas
- End User License and Warranty Agreement
Protocol Faults
55
FAULT_WRITE_PASSED_LOCK_FAILED – 403h
Cause
During a Write Tag Data for ISO18000-6B or UCODE, if the lock fails, this error is returned. The
write command passed but the lock did not. This could be a bad tag.
Solution
Try to write a few other tags and make sure that they are placed in the RF field.
FAULT_PROTOCOL_NO_DATA_READ – 404h
Cause
A Read Tag ID or Data command was sent but did not succeed.
Solution
The tag used has failed or does not have the correct CRC. Try to read a few others to check the
HW/SW configuration.
FAULT_AFE_NOT_ON – 405h
Cause
A command was received for an operation, like read or write, but the AFE was in the off state.
Solution
Start the AFE, then rerun the command.
FAULT_PROTOCOL_WRITE_FAILED – 406h
Cause
This fault can occur when an operation such as write, lock, kill, set password, or initialize, fails.
There are many reasons for failure.