User Manual
Table Of Contents
- M6e-31.5dBm Hardware Guide
- Contents
- Mercury6e Introduction
- Hardware Overview
- Firmware Overview
- Communication Protocol
- Functionality of the Mercury6e
- Appendix A: 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_PROTOCOL_BIT_DECODING_FAILED - 40Fh
- FAULT_PROTOCOL_INVALID_EPC – 410h
- FAULT_PROTOCOL_INVALID_NUM_DATA – 411h
- 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 B: Getting Started - Devkit
Power Management
48 Functionality of the Mercury6e
Power Management
The M6e is designed for power efficiency and offers several different power management
modes. The following power management modes affect the power consumption during
different periods of M6e usage and impact performance in different ways. The available
power management modes are:
Power Modes - set in /reader/powerMode - Controls the power savings when the M6e
is idle.
Transmit Modes - set in
Power Modes
The Power Mode setting (set in /reader/powerMode) allows the user to trade off
increased RF operation startup time for additional power savings. The details of the
amount of power consumed in each mode is shown in the table under Power
Consumption. The behavior of each mode and impact on RF command latency is as
follows:
Power Mode 0 – In this mode, the unit operates at full power to attain the best
performance possible. This mode is only intended for use in cases where power
consumption is not an issue. This is the default Power Mode at startup.
Power Mode 1 – This mode may add up to 50 ms of delay from idle to RF on when
initiating an RF operation. It performs more aggressive power savings, such as
automatically shutting down the analog section between commands, and then
restarting it whenever a tag command is issued.
Power Mode 2 – This mode essentially shuts down the digital and analog boards,
except to power the bare minimum logic required to wake the processor. This mode
may add up to 100 ms of delay from idle to RF on when initiating an RF operation.
Power Mode 2 is not supported when using the USB interface.
Note
See additional latency specifications under Event Response Times.
Transmit Modes
The Transmit Mode setting (set in /reader/radio/enablePowerSave) allows the
user to trade off RF spectral compliance with the Gen2 DRM Mask for increased power
savings while transmitting. The details of the amount of power consumed in each mode is
shown in the table under Power Consumption
. The behavior of each mode is as follows: