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
Common Error Messages
46
FAULT_INVALID_OPCODE – (101h)
Cause
The opCode received is invalid or not supported with the current version of code.
Solution
Check the documentation for the opCode the host sent and make sure it is supported.
FAULT_UNIMPLEMENTED_OPCODE – 102h
Cause
Some of the reserved commands might return this error code.
This does not mean that they always will do this since ThingMagic reserves the right to modify
those commands at anytime.
Solution
Check the documentation for the opCode the host sent to the reader and make sure it is
supported.
FAULT_MSG_POWER_TOO_HIGH – 103h
Cause
A message was sent to set the read or write power to a level that is higher than the current HW
supports.
Solution
Check the HW specifications for the supported powers and insure that the level is not
exceeded.
The M5e 1 Watt units support power from 5 dBm to 30 dBm.
The M5e-Compact units support power from 10 dBm to 23 dBm.