M6e Har dwar e Guide
875-0053-08 RevA
For: M6e (Firmware Ver. 1.13.1 and later)
Government Limited Rights Notice: All documentation and manuals
were developed at private expense and no part of it was developed using
Government funds.
The U.S. Governmentʼs rights to use, modify, reproduce, release, perform,
display, or disclose the technical data contained herein are restricted by
paragraph (b)(3) of the Rights in Technical Data — Noncommercial Items
clause (DFARS 252.227-7013(b)(3)), as amended from time-to-time. Any
reproduction of technical data or portions thereof marked with this legend
must also reproduce the markings. Any person, other than the U.S.
Government, who has been provided access to such data must promptly
notify ThingMagic.
ThingMagic, Mercury, Reads Any Tag, and the ThingMagic logo are
trademarks or registered trademarks of ThingMagic, A Division of Trimble.
Other product names mentioned herein may be trademarks or registered
trademarks of Trimble or other companies.
©2013 ThingMagic – a division of Trimble Navigation Limited. ThingMagic
and The Engine in RFID are registered trademarks of Trimble Navigation
Limited. Other marks may be protected by their respective owners. All
Rights Reserved.d
ThingMagic, A Division of Trimble
4 Cambridge Center, 12th floor
Cambridge, MA 02142
866-833-4069
08 Revision A
September, 2013
A DIVISION OF TRIMBLE
Revision Table
Date Version Description
4/2010 01 RevA First Draft for Beta release
8/2010 01 RevB • Updated GPIO content
• Added FCC regulation info section
12/2010 02 Rev1 Updated for GA release
• new devkit content
• added approved antennas list
• updated power consumption data
• updated Gen2 settings
2/2011 02 Rev2 Updated Regulatory info
5/2011 03 RevA • Added M6e-A info
• updated ESD info
1/2012 04 RevA • updated devkit getting started section
• added new M6e-PRC frequency range info
• new ISO6b settings, including delimiter specific info
2/2012 05 RevA • fixed ISO6b delimiter information
7/2012 06 RevA • added warnings about using TTL interface in continuous
2/2013 07 RevA • Corrected default bootloader/RESET mode baud rate to
9/2013 08 RevA • added antenna detection requirements info
reading mode.
• Added new 128 byte limit to tag read data metadata
• added info on new Universal Reader Assistant 2.
115200
• Corrected RESET line pull-down resistance to 1.5kohms
3
A DIVISION OF TRIMBLE
4
A DIVISION OF TRIMBLE
Contents
Communication Regulation Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
M6e. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Federal Communication Commission Interference Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Industry Canada . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Industrie Canada 15
Authorized Antennas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
M6e-A. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Federal Communication Commission Interference Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Industry Canada . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Industrie Canada 20
Mercury6e Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Hardware Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Hardware Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Antenna Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Antenna Requirements 24
Digital/Power Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Control Signal Specification 25
General Purpose Input/Output (GPIO) 27
Reset Line 28
Power Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
RF Power Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Special RF Power Output Requirements for the M6e-A . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Power Settings for Authorized Antennas and Cables 29
Power Supply Ripple . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Power Consumption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Environmental Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Operating Temperature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Electro-Static Discharge (ESD) Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Assembly Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Cables and Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Digital Interface 33
Antennas 33
5
A DIVISION OF TRIMBLE
M6e Mechanical Drawing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Authorized Antennas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
M6e-A Authorized Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Firmware Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Boot Loader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Application Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Programming the M6e . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Upgrading the M6e. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Verifying Application Firmware Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Custom On-Reader Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Communication Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Serial Communication Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Host-to-Reader Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Reader-to-Host Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
CCITT CRC-16 Calculation 43
User Programming Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Functionality of the Mercury6e . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Regulatory Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Supported Regions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Frequency Setting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Frequency Units 48
Frequency Hop Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Protocol Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
ISO 18000-6C (Gen2). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Protocol Configuration Options 50
Protocol Specific Functionality 51
I-PX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Protocol Configuration Options 51
ISO 18000-6B . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Protocol Configuration Options 51
Antenna Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Using a Multiplexer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Port Power and Settling Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Tag Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Tag Buffer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
6
A DIVISION OF TRIMBLE
Tag Streaming/Continuous Reading 57
Tag Read Meta Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Power Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Power Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Transmit Modes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
DRM Compliant Mode 61
Power Save Mode (non-DRM Compliant) 61
Performance Characteristics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Event Response Times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Save and Restore Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Appendix A: Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Common Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
FAULT_MSG_WRONG_NUMBER_OF_DATA – (100h) 65
FAULT_INVALID_OPCODE – (101h) 65
FAULT_UNIMPLEMENTED_OPCODE – 102h 66
FAULT_MSG_POWER_TOO_HIGH – 103h 66
FAULT_MSG_INVALID_FREQ_RECEIVED (104h) 67
FAULT_MSG_INVALID_PARAMETER_VALUE - (105h) 67
FAULT_MSG_POWER_TOO_LOW - (106h) 67
FAULT_UNIMPLEMENTED_FEATURE - (109h) 67
FAULT_INVALID_BAUD_RATE - (10Ah) 68
Bootloader Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
FAULT_BL_INVALID_IMAGE_CRC – 200h 69
FAULT_BL_INVALID_APP_END_ADDR – 201h 69
Flash Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
FAULT_FLASH_BAD_ERASE_PASSWORD – 300h 70
FAULT_FLASH_BAD_WRITE_PASSWORD – 301h 70
FAULT_FLASH_UNDEFINED_ERROR – 302h 71
FAULT_FLASH_ILLEGAL_SECTOR – 303h 71
FAULT_FLASH_WRITE_TO_NON_ERASED_AREA – 304h 71
FAULT_FLASH_WRITE_TO_ILLEGAL_SECTOR – 305h 71
FAULT_FLASH_VERIFY_FAILED – 306h 72
Protocol Faults. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
FAULT_NO_TAGS_FOUND – (400h) 74
FAULT_NO_PROTOCOL_DEFINED – 401h 74
FAULT_INVALID_PROTOCOL_SPECIFIED – 402h 74
FAULT_WRITE_PASSED_LOCK_FAILED – 403h 75
FAULT_PROTOCOL_NO_DATA_READ – 404h 75
7
A DIVISION OF TRIMBLE
FAULT_AFE_NOT_ON – 405h 75
FAULT_PROTOCOL_WRITE_FAILED – 406h 76
FAULT_NOT_IMPLEMENTED_FOR_THIS_PROTOCOL – 407h 76
FAULT_PROTOCOL_INVALID_WRITE_DATA – 408h 76
FAULT_PROTOCOL_INVALID_ADDRESS – 409h 76
FAULT_GENERAL_TAG_ERROR – 40Ah 77
FAULT_DATA_TOO_LARGE – 40Bh 77
FAULT_PROTOCOL_INVALID_KILL_PASSWORD – 40Ch 77
FAULT_PROTOCOL_KILL_FAILED - 40Eh 77
FAULT_PROTOCOL_BIT_DECODING_FAILED - 40Fh 78
FAULT_PROTOCOL_INVALID_EPC – 410h 78
FAULT_PROTOCOL_INVALID_NUM_DATA – 411h 78
FAULT_GEN2 PROTOCOL_OTHER_ERROR - 420h 78
FAULT_GEN2_PROTOCOL_MEMORY_OVERRUN_BAD_PC - 423h 79
FAULT_GEN2 PROTOCOL_MEMORY_LOCKED - 424h 79
FAULT_GEN2 PROTOCOL_INSUFFICIENT_POWER - 42Bh 79
FAULT_GEN2 PROTOCOL_NON_SPECIFIC_ERROR - 42Fh 80
FAULT_GEN2 PROTOCOL_UNKNOWN_ERROR - 430h 80
Analog Hardware Abstraction Layer Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
FAULT_AHAL_INVALID_FREQ – 500h 81
FAULT_AHAL_CHANNEL_OCCUPIED – 501h 81
FAULT_AHAL_TRANSMITTER_ON – 502h 81
FAULT_ANTENNA_NOT_CONNECTED – 503h 81
FAULT_TEMPERATURE_EXCEED_LIMITS – 504h 82
FAULT_POOR_RETURN_LOSS – 505h 82
FAULT_AHAL_INVALID_ANTENA_CONFIG – 507h 82
Tag ID Buffer Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
FAULT_TAG_ID_BUFFER_NOT_ENOUGH_TAGS_AVAILABLE – 600h 84
FAULT_TAG_ID_BUFFER_FULL – 601h 84
FAULT_TAG_ID_BUFFER_REPEATED_TAG_ID – 602h 85
FAULT_TAG_ID_BUFFER_NUM_TAG_TOO_LARGE – 603h 85
System Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
FAULT_SYSTEM_UNKNOWN_ERROR – 7F00h 86
FAULT_TM_ASSERT_FAILED – 7F01h 86
Appendix B: Getting Started - Devkit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Devkit Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Included Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Setting up the DevKit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Connecting the Antenna 88
8
A DIVISION OF TRIMBLE
Powering up and Connecting to a PC 88
Devkit USB Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
USB/RS232 89
Native USB 89
Devkit Jumpers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Devkit Schematics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Demo Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Notice on Restricted Use of the DevKit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Appendix C: Environmental Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
ElectroStatic Discharge (ESD) Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
ESD Damage Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Identifying ESD as the Cause of Damaged Readers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Common Installation Best Practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Raising the ESD Threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Further ESD Protection for Reduced RF Power Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Variables Affecting Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Environmental . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Tag Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Multiple Readers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
9
A DIVISION OF TRIMBLE
10
Communication Regulation Information
A DIVISION OF TRIMBLE
Communication Regulation Information
The M6e module is available in two variants. The corresponding regulatory information
follows:
M6e - This module is covered under an FCC Modular Approval license and is limited
to 30dBm RF Output power when used in the FCC/NA Region.
M6e-A - This module is covered under an FCC Limited Modular Approval license and
can be operated at the full 31.5dBm RF Output Power with certain restrictions.
11
M6e
WARNING!
EMC FCC 47 CFR, Part 15
Industrie Canada RSS-210
M6e Regulatory Information
Federal Communication Commission Interference Statement
This equipment has been tested and found to comply with the limits for a Class B
digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to
provide reasonable protection against harmful interference in a residential installation.
This equipment generates uses and can radiate radio frequency energy and, if not
installed and used in accordance with the instructions, may cause harmful interference to
radio communications. However, there is no guarantee that interference will not occur in a
particular installation. If this equipment does cause harmful interference to radio or
television reception, which can be determined by turning the equipment off and on, the
user is encouraged to try to correct the interference by one of the following measures:
M6e
Reorient or relocate the receiving antenna.
Increase the separation between the equipment and receiver.
Connect the equipment into an outlet on a circuit different from that to which the
receiver is connected.
Consult the dealer or an experienced radio/TV technician for help.
This device complies with Part 15 of the FCC Rules. Operation is subject to the following
two conditions: (1) This device may not cause harmful interference, and (2) this device
must accept any interference received, including interference that may cause undesired
operation.
FCC Caution: Any changes or modifications not expressly approved by the party
responsible for compliance could void the user's authority to operate this equipment.
Operation of the M6e module requires professional installation to
correctly set the TX power for the RF cable and antenna selected.
This transmitter module is authorized to be used in other devices only by OEM
integrators under the following conditions:
12
M6e
Note
A DIVISION OF TRIMBLE
1. The antenna(s) must be installed such that a minimum separation distance of 25cm
is maintained between the radiator (antenna) & userʼs/nearby peopleʼs body at all
times.
2. The transmitter module must not be co-located with any other antenna or transmitter.
As long as the two conditions above are met, further transmitter testing will not be
required. However, the OEM integrator is still responsible for testing their end-product for
any additional compliance requirements required with this module installed (for example,
digital device emissions, PC peripheral requirements, etc.).
In the event that these conditions can not be met (for certain configurations
or co-location with another transmitter), then the FCC authorization is no
longer considered valid and the FCC ID can not be used on the final product.
In these circumstances, the OEM integrator will be responsible for reevaluating the end product (including the transmitter) and obtaining a
separate FCC authorization.
The OEM integrator has to be aware not to provide information to the end user regarding
how to install or remove this RF module in the user manual of the end product.
User Manual Requirement
The user manual for the end product must include the following information in a prominent
location;
“To comply with FCC’s RF radiation exposure requirements, the antenna(s) used for this
transmitter must be installed such that a minimum separation distance of 25cm is
maintained between the radiator (antenna) & user’s/nearby people’ s body at all times and
must not be co-located or operating in conjunction with any other antenna or transmitter.”
AND
“The transmitting portion of this device carries with it the following two warnings:
“This device complies with Part 15....”
AND
“Any changes or modifications to the transmitting module not expressly approved by
ThingMagic Inc. could void the user’s authority to operate this equipment” “
13
End Product Labeling
The final end product must be labeled in a visible area with the following:
“Contains Transmitter Module FCC ID: QV5MERCURY6E”
or
“Contains FCC ID: QV5MERCURY6E.”
Industry Canada
Under Industry Canada regulations, this radio transmitter may only operate using an
antenna of a type and maximum (or lesser) gain approved for the transmitter by Industry
Canada. To reduce potential radio interference to other users, the antenna type and its
gain should be so chosen that the equivalent isotropically radiated power (e.i.r.p.) is not
more than that necessary for successful communication.
M6e
This radio transmitter (identify the device by certification number, or model number if
Category II) has been approved by Industry Canada to operate with the antenna types
listed below with the maximum permissible gain and required antenna impedance for
each antenna type indicated. Antenna types not included in this list, having a gain greater
than the maximum gain indicated for that type, are strictly prohibited for use with this
device
Operation is subject to the following two conditions: (1) this device may not cause
interference, and (2) this device must accept any interference, including interference that
may cause undesired operation of the device.
To reduce potential radio interference to other users, the antenna type and its gain should
be so chosen that the equivalent isotropically radiated power (e.i.r.p.) is not more than
that permitted for successful communication.
This device has been designed to operate with the antennas listed in Authorized Antennas
table. Antennas not included in these lists are strictly prohibited for use with this device.
To comply with IC RF exposure limits for general population/uncontrolled exposure, the
antenna(s) used for this transmitter must be installed to provide a separation distance of
at least 25 cm from all persons and must not be collocated or operating in conjunction
with any other antenna or transmitter.
14
A DIVISION OF TRIMBLE
End Product Labeling
The final end product must be labeled in a visible area with the following:
“Contains ThingMagic Inc. Mercury6e (or appropriate model number youʼre filing with IC)
transmitting module FCC ID: QV5MERCURY6E-A (IC: 5407A-MERCURY6EA)”
Industrie Canada
Conformément à la réglementation d'Industrie Canada, le présent émetteur radio peut
fonctionner avec une antenne d'un type et d'un gain maximal (ou inférieur) approuvé pour
l'émetteur par Industrie Canada. Dans le but de réduire les risques de brouillage
radioélectrique à l'intention des autres utilisateurs, il faut choisir le type d'antenne et son
gain de sorte que la puissance isotrope rayonnée équivalente (p.i.r.e.) ne dépasse pas
l'intensité nécessaire à l'établissement d'une communication satisfaisante.
Le présent émetteur radio (identifier le dispositif par son numéro de certification ou son
numéro de modèle s'il fait partie du matériel de catégorie I) a été approuvé par Industrie
Canada pour fonctionner avec les types d'antenne énumérés ci-dessous et ayant un gain
admissible maximal et l'impédance requise pour chaque type d'antenne. Les types
d'antenne non inclus dans cette liste, ou dont le gain est supérieur au gain maximal
indiqué, sont strictement interdits pour l'exploitation de l'émetteur
M6e
Le fonctionnement de lʼ appareil est soumis aux deux conditions suivantes:
1. Cet appareil ne doit pas perturber les communications radio, et
2. cet appareil doit supporter toute perturbation, y compris les perturbations qui
pourraient provoquer son dysfonctionnement.
Pour réduire le risque d'interférence aux autres utilisateurs, le type d'antenne et son gain
doivent être choisis de façon que la puissance isotrope rayonnée équivalente (PIRE) ne
dépasse pas celle nécessaire pour une communication réussie.
Lʼ appareil a été conçu pour fonctionner avec les antennes énumérés dans les tables
Antennes Autorisées. Il est strictement interdit de lʼ utiliser lʼ appareil avec des antennes
qui ne sont pas inclus dans ces listes.
Au but de conformer aux limites d'exposition RF pour la population générale (exposition
non-contrôlée), les antennes utilisés doivent être installés à une distance d'au moins 25
cm de toute personne et ne doivent pas être installé en proximité ou utilisé en conjonction
avec un autre antenne ou transmetteur.
Marquage sur l’ étiquette du produit complet dans un endroit visible: "Contient
ThingMagic transmetteur, FCC ID: QV5MERCURY6E (IC:5407A-MERCURY6E)"
15
Authorized Antennas
This device has been designed to operate with the antennas listed in Authorized Antennas.
Antennas not included in this list are strictly prohibited for use with this device.
M6e
16
A DIVISION OF TRIMBLE
WARNING!
M6e-A
EMC FCC 47 CFR, Part 15
Industrie Canada RSS-210
Federal Communication Commission Interference Statement
This equipment has been tested and found to comply with the limits for a Class B
digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to
provide reasonable protection against harmful interference in a residential installation.
This equipment generates uses and can radiate radio frequency energy and, if not
installed and used in accordance with the instructions, may cause harmful interference to
radio communications. However, there is no guarantee that interference will not occur in a
particular installation. If this equipment does cause harmful interference to radio or
television reception, which can be determined by turning the equipment off and on, the
user is encouraged to try to correct the interference by one of the following measures:
M6e-A
Reorient or relocate the receiving antenna.
Increase the separation between the equipment and receiver.
Connect the equipment into an outlet on a circuit different from that to which the
receiver is connected.
Consult the dealer or an experienced radio/TV technician for help.
This device complies with Part 15 of the FCC Rules. Operation is subject to the following
two conditions: (1) This device may not cause harmful interference, and (2) this device
must accept any interference received, including interference that may cause undesired
operation.
FCC Caution: Any changes or modifications not expressly approved by the party
responsible for compliance could void the user's authority to operate this equipment.
Operation of the M6e-a module requires professional installation to
correctly set the TX power for the RF cable and antenna selected.
This transmitter module is authorized to be used in other devices only by OEM
integrators under the following conditions:
3. The antenna(s) must be installed such that a minimum separation distance of 25cm
is maintained between the radiator (antenna) & userʼs/nearby peopleʼs body at all
times.
17
M6e-A
Note
4. The transmitter module must not be co-located with any other antenna or transmitter.
As long as the two conditions above are met, further transmitter testing will not be
required. However, the OEM integrator is still responsible for testing their end-product for
any additional compliance requirements required with this module installed (for example,
digital device emissions, PC peripheral requirements, etc.).
In the event that these conditions can not be met (for certain configurations
or co-location with another transmitter), then the FCC authorization is no
longer considered valid and the FCC ID can not be used on the final product.
In these circumstances, the OEM integrator will be responsible for reevaluating the end product (including the transmitter) and obtaining a
separate FCC authorization.
The OEM integrator has to be aware not to provide information to the end user regarding
how to install or remove this RF module in the user manual of the end product.
User Manual Requirement
The user manual for the end product must include the following information in a prominent
location;
“To comply with FCC’s RF radiation exposure requirements, the antenna(s) used for this
transmitter must be installed such that a minimum separation distance of 25cm is
maintained between the radiator (antenna) & user’s/nearby people’ s body at all times and
must not be co-located or operating in conjunction with any other antenna or transmitter.”
AND
“The transmitting portion of this device carries with it the following two warnings:
“This device complies with Part 15....”
AND
“Any changes or modifications to the transmitting module not expressly approved by
ThingMagic Inc. could void the user’s authority to operate this equipment” “
End Product Labeling
The final end product must be labeled in a visible area with the following:
“Contains Transmitter Module FCC ID: QV5MERCURY6E-A”
18
A DIVISION OF TRIMBLE
or
“Contains FCC ID: QV5MERCURY6E-A.”
Industry Canada
Under Industry Canada regulations, this radio transmitter may only operate using an
antenna of a type and maximum (or lesser) gain approved for the transmitter by Industry
Canada. To reduce potential radio interference to other users, the antenna type and its
gain should be so chosen that the equivalent isotropically radiated power (e.i.r.p.) is not
more than that necessary for successful communication.
This radio transmitter (identify the device by certification number, or model number if
Category II) has been approved by Industry Canada to operate with the antenna types
listed below with the maximum permissible gain and required antenna impedance for
each antenna type indicated. Antenna types not included in this list, having a gain greater
than the maximum gain indicated for that type, are strictly prohibited for use with this
device
M6e-A
Operation is subject to the following two conditions: (1) this device may not cause
interference, and (2) this device must accept any interference, including interference that
may cause undesired operation of the device.
To reduce potential radio interference to other users, the antenna type and its gain should
be so chosen that the equivalent isotropically radiated power (e.i.r.p.) is not more than
that permitted for successful communication.
This device has been designed to operate with the antennas and cables listed in
Authorized Antennas
in these lists are strictly prohibited for use with this device.
To comply with IC RF exposure limits for general population/uncontrolled exposure, the
antenna(s) used for this transmitter must be installed to provide a separation distance of
at least 25 cm from all persons and must not be collocated or operating in conjunction
with any other antenna or transmitter.
and M6e-A Authorized Cables tables. Antennas or cables not included
End Product Labeling
The final end product must be labeled in a visible area with the following:
“Contains ThingMagic Inc. Mercury6e (or appropriate model number youʼre filing with IC)
transmitting module FCC ID: QV5MERCURY6E-A (IC: 5407A-MERCURY6EA)”
19
M6e-A
Industrie Canada
Conformément à la réglementation d'Industrie Canada, le présent émetteur radio peut
fonctionner avec une antenne d'un type et d'un gain maximal (ou inférieur) approuvé pour
l'émetteur par Industrie Canada. Dans le but de réduire les risques de brouillage
radioélectrique à l'intention des autres utilisateurs, il faut choisir le type d'antenne et son
gain de sorte que la puissance isotrope rayonnée équivalente (p.i.r.e.) ne dépasse pas
l'intensité nécessaire à l'établissement d'une communication satisfaisante.
Le présent émetteur radio (identifier le dispositif par son numéro de certification ou son
numéro de modèle s'il fait partie du matériel de catégorie I) a été approuvé par Industrie
Canada pour fonctionner avec les types d'antenne énumérés ci-dessous et ayant un gain
admissible maximal et l'impédance requise pour chaque type d'antenne. Les types
d'antenne non inclus dans cette liste, ou dont le gain est supérieur au gain maximal
indiqué, sont strictement interdits pour l'exploitation de l'émetteur
Le fonctionnement de lʼ appareil est soumis aux deux conditions suivantes:
1. Cet appareil ne doit pas perturber les communications radio, et
2. cet appareil doit supporter toute perturbation, y compris les perturbations qui
pourraient provoquer son dysfonctionnement.
Pour réduire le risque d'interférence aux autres utilisateurs, le type d'antenne et son gain
doivent être choisis de façon que la puissance isotrope rayonnée équivalente (PIRE) ne
dépasse pas celle nécessaire pour une communication réussie.
Lʼ appareil a été conçu pour fonctionner avec les antennes et les câbles énumérés dans
les tables Antennes Autorisées et Câbles Autorisés. Il est strictement interdit de lʼ utiliser
lʼ appareil avec des antennes ou câbles qui ne sont pas inclus dans ces listes.
Au but de conformer aux limites d'exposition RF pour la population générale (exposition
non-contrôlée), les antennes utilisés doivent être installés à une distance d'au moins 25
cm de toute personne et ne doivent pas être installé en proximité ou utilisé en conjonction
avec un autre antenne ou transmetteur.
Marquage sur l’ étiquette du produit complet dans un endroit visible: "Contient
ThingMagic transmetteur, FCC ID: QV5MERCURY6E-A (IC:5407A-MERCURY6EA)"
20
A DIVISION OF TRIMBLE
Mercury6e Introduction
The ThingMagic® Mercury6e® (M6e) embedded module is an RFID engines that you can
integrate with other systems to create RFID-enabled products.
Applications to control the M6e modules and derivative products can be written using the
high level MercuryAPI. The MercuryAPI supports Java, .NET and C programming
environments. The MercuryAPI Software Development Kit (SDK) contains sample
applications and source code to help developers get started demoing and developing
functionality. For more information on the MercuryAPI see the MercuryAPI Programmers
Guide and the MercuryAPI SDK, available on the ThingMagic website.
This document is for hardware designers and software developers. It describes the
hardware specifications and firmware functionality and provides guidance on how to
incorporate the M6e module within a third-party host system. The rest of the document is
broken down into the following sections:
Hardware Overview - This section provides detailed specifications of the M6e
hardware. This section should be read in its entirety before designing hardware or
attempting to operate the M6e module in hardware other than the ThingMagic
DevKit.
Firmware Overview - This section describes provides a detailed description of the M6e
firmware components including the bootloader and application firmware.
Communication Protocol - This section provides an overview of the low level serial
communications protocol used by the M6e.
Functionality of the Mercury6e - This section provides detailed descriptions of the M6e
features and functionality that are supported through the use of the MercuryAPI.
Appendix A: Error Messages - This appendix lists and provides causes and suggested
solutions for M6e Error Codes.
Appendix B: Getting Started - Devkit - QuickStart guide to getting connected to the M6e
Developerʼs Kit and using the Demo Applications included with the MercuryAPI SDK.
Mercury6e Introduction 21
A DIVISION OF TRIMBLE
22 Mercury6e Introduction
A DIVISION OF TRIMBLE
Hardware Overview
The following section provides detailed specifications of the M6e hardware including:
Hardware Interfaces
Power Requirements
Environmental Specifications
Assembly Information
Hardware Overview 23
A DIVISION OF TRIMBLE
Note
Note
Hardware Interfaces
Antenna Connections
The M6e supports four monostatic bidirectional RF antennas through four MMCX
connectors: labeled J1 through J4 on the module. See Cables and Connectors
information on antenna connector parts.
The maximum RF power that can be delivered to a 50 ohm load from each port is 1.4
Watts, or +31.5 dBm (regulatory requirements permitting).
The RF ports can only be energized one at a time.
FCC/NA Region max RF power is 30 dBm. For 31.5 dBm operation in the
FCC/NA Region the M6e-A module must be purchased.
Hardware Interfaces
for more
Antenna Requirements
The performance of the M6e is affected by antenna quality. Antennas that provide good
50 ohm match at the operating frequency band perform best. Specified sensitivity
performance is achieved with antennas providing 17 dB return loss or better across the
operating band. Damage to the module will not occur for any return loss of 1 dB or
greater. Damage may occur if antennas are disconnected during operation or if the
module sees an open or short circuit at its antenna port.
Antenna Detection
To minimize the chance of damage due to antenna disconnection, the M6e supports
antenna detection. Detection can be done automatically or manually, the choice of which
is configured through API calls. Regardless of how itʼs used it is generally recommend
that antenna detection be enabled as it helps protect the module from possible damage
due to return losses less than 1 dB.
In order for antennas to be detected by the M6e the antenna must pass some DC current
across the center pin and ground, i.e. must present between 50 Ohms and 10 kOhms DC
resistance.
24 Hardware Overview
Hardware Interfaces
A DIVISION OF TRIMBLE
Digital/Power Connector
The digital connector provides power, serial communications signals, shutdown and reset
signals to the M6e module, and access to the GPIO inputs and outputs. These signals are
provided through connector part number: Molex 53261-1571 - 1.25mm pin centers, 1 amp
per pin rating. which mates with Molex housing p/n 51021-1500 with crimps p/n 63811-
0300. See Cables and Connectors
M6e Digital Connector Signal Definition
for more information on typical cable parts.
Molex
53261-1571
Signal
Pin Number
1 GND P/S Return Must connect both GND pins to ground
2GND P/S Return
3 +5VDC P/S Input Must connect both 5V supplies
4 +5 VDC P/S Input
5 GPIO1 Bi-directional Input 5VDC tolerant, 16mA Source/Sink
6 GPIO2 Bi-directional
7 GPIO3 Bi-directional
8 GPIO4 Bi-directional
9 UART_RX_TTL In In (Pull-down with +10k Ohm to Ground)
10 UART_TX_TTL Out Out
11 USB_DM Bi-directional USB Data (D-) signal
12 USB_DP Bi-directional USB Data (D+) signal
13 USB_5VSENSE In Input 5V to tell module to talk on USB
14 SHUTDOWN In Pull LOW to enable module. Set HIGH to dis-
15 RESET Bi-directional
Signal
Direction
(In/Out of M6e)
Notes
able all 5V Inputs and shutdown module.
HIGH output indicates
LOW output indicates
running
Boot Loader is running
Application Firmware is
Note: Not 5V tolerant.
Control Signal Specification
TTL Level UART Interface
The module communicates to a host processor via a TTL logic level UART serial port or
via a USB port. Both ports are accessed on the 15-pin Digital/Power Connector
Hardware Overview 25
. The TTL
Hardware Interfaces
Note
Note
A DIVISION OF TRIMBLE
logic level UART supports complete functionality. The USB port supports complete
functionality except the lowest power operational mode.
Power Consumption specifications apply to control via the TTL UART.
It is not recommended to use the TTL interface when planning to operate the
module in Tag Streaming/Continuous Reading mode. The TTL interface (both the
module side and the host side) cannot detect physical disconnections, as
can the USB Interface, simplifying reconnection.
TTL Level TX
V-Low: Max 0.4 VDC
V-High: 2.1 to 3.3 VDC
8 mA max
TTL Level RX
V-Low: -0.3 to 0.6 VDC
V-High: 2.2 to 5 VDC
(Tied to ground through a 10kOhm pull-down resistor.)
A level converter could be necessary to interface to other devices that use standard 12V
RS232. Only three pins are required for serial communication (TX, RX, and GND).
Hardware handshaking is not supported. The M6e serial port has an interrupt-driven
FIFO that empties into a circular buffer.
The connected host processorʼs receiver must have the capability to receive up to 256
bytes of data at a time without overflowing.
Baud rates supported:
– 9600
– 19200
– 38400
– 115200
– 230400
– 460800
– 921600
26 Hardware Overview
Hardware Interfaces
Note
A DIVISION OF TRIMBLE
The baudrate in the Boot Loader mode depends on whether the module
entered the bootloader mode after a power-up or through an assert or “boot
bootloader” user command. Upon power up if the Reset Line is LOW then the
default baud rate of 115200 will be used. If the module returns to the
bootloader from Application Firmware mode, then the current state and
baudrate will be retained.
USB Interface
Supports USB 2.0 full speed device port (12 Megabits per second) using the two USB
pins (USB_DM and USB_DP).
General Purpose Input/Output (GPIO)
The four GPIO connections, provided through the M6e Digital Connector Signal Definition,
may be configured as inputs or outputs using the MercuryAPI. The GPIO pins connect
through 100 ohm resistors to the high current PA0 to PA3 pins of the AT91SAM7X
processor. The processor data sheet can be consulted for additional details.
Pins configured as inputs must not have input voltages that exceed voltage range of -0.3
volts to +5.5 volts. In addition, during reset the input voltages should not exceed 3.3V.
Outputs may source and sink 16 mA. Voltage drop in the series 100 ohm resistor will
reduce the delivered voltage swing for output loads that draw significant current.
Input Mode
– TTL compatible inputs,
– Logic low < 0.8 V,
– Logic high > 2.0V.
– 5V tolerant
Output Mode
– 3.3 Volt CMOS Logic Output with 100 ohms in series.
– Greater than 1.9 Volts when sourcing 8 mA.
– Greater than 2.9 Volts when sourcing 0.3 mA.
– Less than 1.2 Volts when sinking 8 mA.
– Less than 0.2 Volts when sinking 0.3 mA.
Module power consumption can be adversely affected by incorrect GPIO configuration.
Similarly, the power consumption of external equipment connected to the GPIOs can also
Hardware Overview 27
Hardware Interfaces
A DIVISION OF TRIMBLE
be adversely affected. The following instructions will yield specification compliant
operation.
On power up, the M6E module configures its GPIOs as inputs to avoid contention from
user equipment that may be driving those lines. The input configuration is as a 3.3 volt
logic CMOS input and will have a leakage current not in excess of 400 nA. The input is in
an undetermined logic level unless pulled externally to a logic high or low. Module power
consumption for floating inputs is unspecified. With the GPIOs configured as inputs
and individually pulled externally to either high or low logic level, module power
consumption is as listed in the M6e Power Consumption
GPIOs may be reconfigured individually after power up to become outputs. This
configuration takes effect either at API execution or a few tens of milliseconds after power
up if the configuration is stored in nonvolatile memory. The configuration to outputs is
defeated if the module is held in the boot loader by Reset Line
configured as outputs consume no excess power if the output is left open. Specified
module power consumption is achieved for one or more GPIO lines set as output and left
open. Users who are not able to provide external pull ups or pull downs on any given
input, and who do not need that GPIO line, may configure it as an output and leave it
open to achieve specified module power consumption.
table.
being held low. Lines
Configuring GPIO Settings
The GPIO lines are configured as inputs or outputs through the MercuryAPI by setting the
reader configuration parameters /reader/gpio/inputList and /reader/gpio/outputList. Once
configured as inputs or outputs the state of the lines can be Get or Set using the gpiGet()
and gpoSet() methods, respectively. See the language specific reference guide for more
details.
Reset Line
Upon power up the RESET (pin 15) line is configured as an input. The input value will
determine whether the Boot Loader
immediately load the Application Firmware
After that action is completed, this line is configured as an output line. While the unit
continues to be in bootloader the line is driven high.
Once in application mode, the RESET line is driven low. if the module returns to the
bootloader mode, either due to an assert or “boot bootloader”, the RESET line will again
be driven high.
To minimize power consumption in the application, the RESET line should be either left
open or pulled weakly low (1.5k Ohm to ground).
(pulled LOW) will wait for user commands or
(left open) image and enter application mode.
See Note about baud rate applicable when using TTL Level UART Interface
.
28 Hardware Overview
A DIVISION OF TRIMBLE
Note
Note
WARNING!
Power Requirements
RF Power Output
The M6e supports separate read and write power level which are command adjustable
via the MercuryAPI. Power levels must be between:
– Minimum RF Power = +5 dBm
– Maximum RF Power = +31.5 dBm (+/- 0.5 dB accuracy above +15 dBm)
Maximum power may have to be reduced to meet regulatory limits, which
specify the combined effect of the module, antenna, cable and enclosure
shielding of the integrated product.
Power Requirements
FCC regulations limit the maximum RF Power to 30 dBm in NA Region. For
31.5 dBm operation in the NA Region the M6e-A must be purchased.
Special RF Power Output Requirements for the M6e-A
Operation requires professional installation to correctly set the TX
power for the RF cable and antenna selected.
Power Settings for Authorized Antennas and Cables
The M6e-A has been designed to operate with the antennas listed in Authorized Antennas
list using the cables in the M6e-A Authorized Cables
and cable the maximum RF power is determined from antenna gain (Max Linear Gain
value from antenna list) and antenna cable loss (Insertion Loss value from cable list)
using the formula:
Pmax = 36 dBm - Antenna Gain + Cable Loss
For example, for the Laird S8658WPL and the ThingMagic CBL-P6 6ft cable the following
calculation can be performed:
list. For any combination of antenna
Max linear antenna gain = 6 dBiL
Hardware Overview 29
Power Requirements
CAUTION!
!
!
A DIVISION OF TRIMBLE
Minimum cable insertion loss = 0.8 dB
Pmax = 36 - 6 + 0.8 = 30.8 dBm
The maximum RF power that may be set using this configuration is 30.8 dBm (see
Warning above).
Power Supply Ripple
The following are the minimum requirements to avoid module damage and to insure
performance and regulatory specifications are met. Certain local regulatory specifications
may require tighter specifications.
5 Volt +/- 5%,
Less than 25 mV pk-pk ripple all frequencies,
Less than 11 mV pk-pk ripple for frequencies less than 100 kHz,
No spectral spike greater than 5 mV pk-pk in any 1 kHz band.
Operation in the EU Region (under ETSI regulatory specs) may need
tighter ripple specifications to meet ETSI mask requirements.
Power Consumption
The following table defines the power/transmit mode settings and power consumption
specifications for the M6e. Additional details about Power/Transmit Modes can be found
30 Hardware Overview
A DIVISION OF TRIMBLE
in the Power Management section.
Operation
Power/Transmit Mode
M6e Power Consumption
RF Transmit
Power
Setting
Max Power
(Watts)
(dBm)
1
Power Requirements
Voltage
(Volts)
Current
(mA)
Transmit CW
Transmit Mode = DRM
Tag Reading
Transmit Mode = DRM
Tag Reading
Transmit Mode = Power Save
Tag Reading
Transmit Mode = DRM + PreDistortion
Tag Reading
Transmit Mode = DRM
No Tag Reading (M6e idle)
Power Mode = FULL
No Tag Reading (M6e idle)
Power Mode = MINSAVE
No Tag Reading (M6e idle)
Power Mode = SLEEP
Boot N/A 0.12 5.0 +/- 5% 20
Shut Down N/A < 0.001 5.0 +/- 5% < 200uA
In Rush Current and Power, M6e
Power up and/or any state change
+31.5
+31.5
+30 5.8 5.0 +/- 5% 1060
+30 6.2 5.0 +/- 5% 1200
+17 and below 4 5.0 +/- 5% 800
N/A 0.35 5.0 +/- 5% 60
N/A 0.12 5.0 +/- 5% 20
N/A 0.005 5.0 +/- 5% 1.0
N/A 7.5 5.0 +/- 5% 1500 Max
7.5
7.5
2
2
5.0 +/- 5% 1400
5.0 +/- 5% 1400
Note: 1 - Power consumption is defined for TTL RS232 operation. Power consumption may
vary if the USB interface is connected.
Note: 2 - Power consumption is defined for operation into a 17dB return loss load or better.
Power consumption may increase, up to 8.2W, during operation into return losses
worse than 17dB and high ambient temperatures.
Hardware Overview 31
A DIVISION OF TRIMBLE
Note
WARNING!
Environmental Specifications
Operating Temperature
The M6e module may be considered as a single electronic component. It is designed so
that all the internal components have safe margins to their thermal limits when the heat
spreading plate (bottom, non-labeled side) does not exceed 70°C. The heat spreading
plate temperature must not exceed 70 degrees C. Heat sinking will be required for high
duty cycle applications.
When heat spreading plate reaches 70°C, the RF Shield (top, antenna connector side)
may exceed 70°C, this is acceptable.
Electro-Static Discharge (ESD) Specification
IEC-61000-4-2 and MIL-883 3015.7 discharges direct to operational antenna port
tolerates max 1200 Volt pulse.
Environmental Specifications
Survival level varies with antenna return loss and antenna characteristics.
See ElectroStatic Discharge (ESD) Considerations for methods to increase ESD
tolerances.
The M6e antenna ports may be susceptible to damage from Electrostatic
Discharge (ESD). Equipment failure can result if the antenna or
communication ports are subjected to ESD. Standard ESD precautions
should be taken during installation and operation to avoid static
discharge when handling or making connections to the M6e reader
antenna or communication ports. Environmental analysis should also be
performed to ensure static is not building up on and around the
antennas, possibly causing discharges during operation.
32 Hardware Overview
A DIVISION OF TRIMBLE
Note
Assembly Information
Cables and Connectors
The following are the cables and connectors used in the M6e Developerʼs Kit interface
board:
Digital Interface
The cable assembly used consists of the following parts:
2 Connector Shells [Molex 51021-1500] with 15 Crimp Contacts each [Molex 50079-
8100]
1 Wire (#28 AWG 7x36 - Black, Teflon) for Pin 1 connection [Alpha 284/7-2]
14 Wires (#28 AWG 7x36 - White, Teflon) for other connections [Alpha 284/7-1]
Assembly Information
Pin numbers and assignments are shown in the M6e Digital Connector Signal
Definition table.
Antennas
The cable assembly used to connect the “external” RP-TNC connectors on the M6e
Devkit to the M6e MMCX connectors consists of the following parts:
1 Reverse TNC Bulkhead Jack Connector
1 LMR-100A Coaxial Cable
1 MMCX Right Angle Plug Connector
Hardware Overview 33
A DIVISION OF TRIMBLE
M6e Mechanical Drawing
Assembly Information
34 Hardware Overview
Authorized Antennas
A DIVISION OF TRIMBLE
Authorized Antennas
This device has been designed to operate with the antennas listed below, and having a maximum gain of 6dBiL. Antennas not included in this list or having a gain greater than 6dBiLare
strictly prohibited for use with this device. The required antenna impedance is 50 ohms.
1
Vendor Model
ThingMagic ANT-NA-A5 6.0
ThingMagic ANT-WB-6-2025 5.1
ThingMagic ANT-NA-9025 3.4
ThingMagic ANT-NB-7-2031 6.0
MTI Wireless MT-242043/TRH/A/K 6.0
Linear Gain
(dBi)
Note: 1 - These are all circularly polarized antennas, but since most tag
antennas are linearly polarized, the equivalent linear gain of the
antenna should be used for all calculations.
Hardware Overview 35
A DIVISION OF TRIMBLE
M6e-A Authorized Cables
The following table contains the cable loss values for authorized shielded coaxial cables
provided by ThingMagic
M6e-A Authorized Cables
Cable Description
6' RTNC to RTNC Cable CBL-P6 0.8 dB
12' RTNC to RTNC Cable CBL-P12 1.5 dB
20' RTNC to RTNC Cable CBL-P20 2.4 dB
20' RTNC to RTNC Plenum
Cable
25' RTNC to RTNC Cable CBL-P25 3.0 dB
ThingMagic Part
Number
CBL-P20-PL 2.4 dB
Insertion Loss
36 Hardware Overview
A DIVISION OF TRIMBLE
Firmware Overview
The following section provides detailed description of the M6e firmware components:
Boot Loader
Application Firmware
Custom On-Reader Applications
Firmware Overview 37
A DIVISION OF TRIMBLE
Note
Boot Loader
The boot loader provides low-level functionality. This program provides the low level
hardware support for configuring communication settings, loading Application Firmware
and storing and retrieving data to/from flash.
When a module is powered up or reset, the boot loader code is automatically loaded and
executed.
Unlike previous ThingMagic modules (M4e and M5e) the M6e bootloader
should effectively be invisible to the user. The M6e is by default configured
to auto-boot into application firmware and for any operations that require the
module be in bootloader mode the MercuryAPI will handle the switching
automatically.
Boot Loader
38 Firmware Overview
A DIVISION OF TRIMBLE
Application Firmware
The application firmware contains the tag protocol code along with all the command
interfaces to set and get system parameters and perform tag operations. The application
firmware is, by default, started automatically upon power up.
Programming the M6e
Applications to control the M6e module and derivative products are written using the high
level MercuryAPI. The MercuryAPI supports Java, .NET and C programming
environments. The MercuryAPI Software Development Kit (SDK) contains sample
applications and source code to help developers get started demoing and developing
functionality. For more information on the MercuryAPI see the MercuryAPI Programmers
Guide and the MercuryAPI SDK, available on the ThingMagic website.
Application Firmware
Upgrading the M6e
New features developed for the M6e are made available to existing modules through an
Application Firmware upgrade, along with corresponding updates to the MercuryAPI to
make use of the new features. Firmware upgrades can be applied using the MercuryAPI
to build the functionality into custom applications or using the MercuryAPI SDK demo
utilities.
Verifying Application Firmware Image
The application firmware has an image level Cyclic Redundancy Check (CRC) embedded
in it to protect against corrupted firmware during an upgrade process. (If the upgrade is
unsuccessful, the CRC will not match the contents in flash.) When the boot loader starts
the application FW, it first verifies that the image CRC is correct. If this check fails, then
the boot loader does not start the application firmware and an error is returned.
Firmware Overview 39
A DIVISION OF TRIMBLE
Custom On-Reader Applications
The M6e does not support installing customer applications on the module. All reader
configuration and control is performed using the documented MercuryAPI methods in
applications running on a host processor.
Custom On-Reader Applications
40 Firmware Overview
A DIVISION OF TRIMBLE
Communication Protocol
The following section provides an overview of the low level serial communications
protocol used by the M6e.
Communication Protocol 41
A DIVISION OF TRIMBLE
Serial Communication Protocol
Header Data Length Command
Data
CRC-16 Checksum
Hdr Len Cmd CRC Hi CRC LO
I
1 byte 1 byte 1 byte 0 to 250 bytes 2 bytes
The serial communication between a computer (host) and the M6e is based on a
synchronized command-response/master-slave mechanism. Whenever the host sends a
message to the reader, it cannot send another message until after it receives a response.
The reader never initiates a communication session; only the host initiates a
communication session.
This protocol allows for each command to have its own timeout because some
commands require more time to execute than others. The host must manage retries, if
necessary. The host must keep track of the state of the intended reader if it reissues a
command.
Host-to-Reader Communication
Host-to-reader communication is packetized according to the following diagram. The
reader can only accept one command at a time, and commands are executed serially, so
the host waits for a reader-to-host response before issuing another host-to-reader
command packet.
Serial Communication Protocol
42 Communication Protocol
Serial Communication Protocol
Header Data Length Command Data CRC-16 Checksum
Hdr Len
Cmd
CRC HI CRC LO
1 byte 1 byte
1 byte
2 bytes
Status Word
Status Word
0 to 248 bytes2 bytes
A DIVISION OF TRIMBLE
Reader-to-Host Communication
The following diagram defines the format of the generic Response Packet sent from the
reader to the host. The Response Packet is different in format from the Request Packet.
CCITT CRC-16 Calculation
The same CRC calculation is performed on all serial communications between the host
and the reader. The CRC is calculated on the Data Length, Command, Status Word, and
Data bytes. The header is not included in the CRC.
Communication Protocol 43
A DIVISION OF TRIMBLE
User Programming Interface
The M6e does not support programming to the serial protocol directly. All user interaction
with the M6e must be performed using the MercuryAPI.
The MercuryAPI supports Java, .NET and C programming environments. The
MercuryAPI Software Development Kit (SDK) contains sample applications and source
code to help developers get started demoing and developing functionality. For more
information on the MercuryAPI see the MercuryAPI Programmers Guide and the
MercuryAPI SDK, available on the ThingMagic website.
User Programming Interface
44 Communication Protocol
A DIVISION OF TRIMBLE
Functionality of the Mercury6e
The following section provides detailed descriptions of the M6e features and functionality
that are supported through the use of the MercuryAPI.
Functionality of the Mercury6e 45
Regulatory Support
A DIVISION OF TRIMBLE
Regulatory Support
Supported Regions
The M6e has differing levels of support for operation and use under the laws and
guidelines of several regions. The regional support is shown in the following table.
Supported Regions
Region Regulatory Support Notes
North America (NA) FCC 47 CFG Ch. 1 Part 15
Industrie Canada RSS-210
European Union
(EU3)
Korea (KR2) KCC (2009) The first frequency channel (917,300kHz) of the
Revised ETSI EN 302 208 By default EU3 will use four channels. EU3
region can also be used in a single channel
mode. These two modes of operation are
defined as:
Single Channel Mode
• Set by manually setting the frequency hop
table to a single frequency. In this mode the
module will occupy the set channel for up to
four seconds, after which it will be quiet for
100ms before transmitting on the same
channel again.
Multi Channel Mode
• Set by leaving the default or manually setting
more than one frequency in the hop table. In
this mode the module will occupy one of the
configured channels for up to four seconds,
after which it may switch to another channel
and immediately occupy that channel for up
to four seconds. This mode allows for
continuous operation.
KR2 region will be derated to +22dBm to meet
the new Korea regulatory requirements. All
other channels operate up to +30dBm. In the
worst case scenario, each time the derated
channel is used it will stay on that channel for
400ms. The fastest it will move to the next channel, in the case where no tags are found using
that frequency, it will move to the next channel
after 10 empty query rounds, approximately
120ms.
46 Functionality of the Mercury6e
A DIVISION OF TRIMBLE
Regulatory Support
Supported Regions
Peopleʼs Republic of
China (PRC & CN)
Australia (AU) ACMA LIPD Class Licence
New Zealand (NZ) Radiocommunications Regula-
Open Region No regulatory compliance
SRRC, MII The PRC specifications limits channels 920 to
Variation 2011 (No. 1)
tions (General User Radio
Licence for Short Range
Devices) Notice 2011
enforced
920.5MHz and 924.5 to 925.0MHz to transmitting at 100mW or below. The default hop table
uses only the center channels which allow 2W
ERP, 1W conducted, power output. If the hop
table is modified to use the outer, lower power
channels the RF level will be limited to the outer
channels limit, 100mW or +20dBm
Note: With the M6e-PRC hardware the 840
to 845MHz band is also supported as
the CN region. It is not supported on
the standard M6e
Allows the module to be manually configured
within the full capabilities supported by the hardware, see
table. No regulatory limits, including: frequency
range, channel spacing and transmit power limits, are enforced. The Open Region should be
used with caution.
Regional Frequency Quantization
The regional functionality is set using the MercuryAPI. Setting the region of operation
configures the regional default settings including:
Loads the Frequency Hop Table with the appropriate table for the selected region.
Sets the PLL Frequency Setting to the first entry in the hop table, even if the RF is off.
Selects the transmit filter, if applicable.
Frequency Setting
The modules have a PLL synthesizer that sets the modulation frequency to the desired
value. Whenever the frequency is changed, the module must first power off the
modulation, change the frequency, and then turn on the modulation again. Since this can
take several milliseconds, it is possible that tags are powered off during a frequency hop.
In addition to setting the default regional settings, the M6e has commands that allow the
transmit frequency to be set manually.
Functionality of the Mercury6e 47
Regulatory Support
CAUTION!
!
!
A DIVISION OF TRIMBLE
Use these commands with extreme caution.
It is possible to change the moduleʼs compliance with the regional regulations.
Frequency Units
All frequencies in the M6e are expressed in kHz using unsigned 32-bit integers. For
instance, a carrier frequency of 915 MHz is expressed as 915000 kHz.
The PLL is set automatically to the closest frequency - based on the minimum frequency
quantization for the current region - that matches the specified value. The M6e has an
absolute minimum quantization of 25 kHz. Each region also has a minimum quantization
based on regulatory specifications, which may be greater. The following table details the
frequency quantization in kHz for each region setting.
Regional Frequency Quantization
Region
NA 250 kHz 902,000 kHz 928,000 kHz
EU3 100 kHz 865,600 kHz 867,600 kHz
KR 25 kHz 910,000 kHz 914,000 kHz
KR2 25 kHz 917,000 kHz 923,500 kHz
PRC 250 kHz 920,125 kHz 924,875 kHz
CN 250 kHz
AU 250 kHz 920,750 kHz 925,250 kHz
NZ 250 kHz 922,250 kHz 927,250 kHz
Open 25 kHz 865,000 kHz
Frequency
Quantization
Minimum
Frequency
840,000 kHz
902,000 kHz
Maximum
Frequency
1
845,000 kHz
869,000 kHz
928,000 kHz
Note: 1 - Only supported on M6e-PRC hardware. On M6e-PRC
hardware the OPEN region is limited to the two PRC frequency
ranges
1
When manually setting frequencies the module will round down for any value that is not
an even multiple of the supported frequency quantization.
48 Functionality of the Mercury6e
Regulatory Support
A DIVISION OF TRIMBLE
For example: In the NA region, setting a frequency of 902,999 kHz results in a
setting of 902,750 kHz.
When setting the frequency of the module, any frequencies outside of the valid range for
the specified region are rejected.
Frequency Hop Table
The frequency hop table determines the frequencies used by the M6e when transmitting.
The hop table characteristics are:
Contains up to 62 slots.
Valid frequencies for the region currently selected.
Changes not stored in flash, thus changes made are not retained after a power cycle
or a restart of the boot loader.
Inability to change individual entries after uploading without reloading the entire table.
Frequencies used in the order of entries in the table.
If necessary for a region, the hop table can be randomized to create a pseudo-random
sequence of frequencies to use. This is done automatically using the default hop tables
provided for each region.
Functionality of the Mercury6e 49
A DIVISION OF TRIMBLE
Note
Protocol Support
The M6e has the ability to support many different tag protocols. Using the MercuryAPI
ReadPlan classes the M6e can be configured to single or multi-protocol Read operations.
The current protocols supported are (some may require a license to enable):
ISO 18000-6C (Gen2)
I-PX
ISO 18000-6B
ISO 18000-6C (Gen2)
Protocol Configuration Options
The M6e supports multiple ISO-18000-6C profiles including the ability to specify the Link
Frequency, encoding schemes, Tari value and modulation scheme. The protocol options
are set in the MercuryAPI Reader Configuration Parameters (/reader/gen2/*). The
following table shows the supported combinations:
Protocol Support
Backscatter
Link Frequency
(kHz)
250 Miller (M=8) 12.5 PR-ASK
250 Miller (M=4) 12.5 PR-ASK
250 Miller (M=2) 12.5 PR-ASK
250 FM0 12.5 PR-ASK
250 Miller (M=8) 25 PR-ASK
250 Miller (M=4) 25 PR-ASK Default
250 Miller (M=2) 25 PR-ASK
250 FM0 25 PR-ASK
250 Miller (M=8) 25 PR-ASK
640 FM0 6.25 PR-ASK Not supported in PRC
It is important that the /reader/baudRate is greater than /reader/
gen2/BLF, in equivalent frequency units. If its not then the reader could be
ISO-18000-6C Protocol Options
Encoding
Tari
(usec)
Modulation
Scheme
Notes
Region
50 Functionality of the Mercury6e
Protocol Support
Note
A DIVISION OF TRIMBLE
reading data faster than the transport can handle and send, and the readerʼs
buffer might fill up.
Protocol Specific Functionality
See the MercuryAPI Programmers Guide and language specific reference guides for
details on supported Gen2 command functionality.
I-PX
Protocol Configuration Options
The M6e supports multiple I-PX profiles including the ability to specify the Return Link
Frequency, encoding and modulation scheme. The two profiles are treated as distinct
protocols, the individual parameters are not configurable as with the other protocols. The
following table shows the supported combinations:
ISO-18000-6B Protocol Options
Return Link
Freq (kHz)
64 PWM Protocol ID = TagProtocol.IPX64
256 PWM Protocol ID = TagProtocol.IPX256
Modulation
Scheme
Notes
The two link rates are effectively two different protocols and treated as such.
I-PX tags are fixed to one of the two frequencies and cannot communicate
on the other, unlike ISO 18000-6B/C tags which can operate under multiple
profiles.
ISO 18000-6B
Protocol Configuration Options
The M6e supports multiple ISO-18000-6B profiles including the ability to specify the
Return Link Frequency, encoding, Forward Link Rate and modulation scheme. The
Functionality of the Mercury6e 51
Protocol Support
A DIVISION OF TRIMBLE
protocol options are set in the MercuryAPI Reader Configuration Parameters (/reader/
iso18000-6b/*). The following table shows the supported combinations:
ISO-18000-6B Protocol Options
Return Link
Freq (kHz)
40 FM0 10 Manchester 11%
40 FM0 10 Manchester 99%
160 FM0 40 Manchester 11%
160 FM0 40 Manchester 99% (default)
Return
Encoding
Forward Link
Freq (kHz)
Forward
Encoding
Modulation
Depth
Delimiter
ISO18000-6B tags support two delimiter settings on the transmitter. Not all tags support
both delimiters, some tags require the delimiter be set to 1, the default is 4.
The delimiter setting is set using the MercuryAPI Reader Configuration Parameter:
/reader/iso180006b/delimiter
In addition to setting the delimiter to 1, a TagFilter of the class
ISO180006b.Select must be used in order to read certain ISO18000-6b tags,
specifically one of the following options must be used:
GROUP_SELECT_EQ
–
– GROUP_SELECT_NE
– GROUP_SELECT_GT
– GROUP_SELECT_LT
– GROUP_UNSELECT_EQ
– GROUP_UNSELECT_NE
– GROUP_UNSELECT_GT
– GROUP_UNSELECT_LT
52 Functionality of the Mercury6e
A DIVISION OF TRIMBLE
Note
Note
Antenna Ports
The M6e has four monostatic antenna ports. Each port is capable of both transmitting and
receiving. The modules also support Using a Multiplexer
antenna ports, controlled using two GPIO lines and the internal physical port J1/J2/J3/J4
switching.
The M6e does not support bistatic operation.
Using a Multiplexer
Multiplexer switching is controlled through the use of the internal module physical port J1/
J2/J3/J4 switch along with the use of one or more of the General Purpose Input/Output
(GPIO) lines. In order to enable automatic multiplexer port switching the module must be
configured to use Use GPIO as Antenna Switch in /reader/antenna/
portSwitchGpos.
Antenna Ports
, allowing up to 16 total logical
Once the GPIO line(s) usage has been enabled the following control line states are
applied when the different Logical Antenna settings are used. The tables below show the
mapping that results using GPIO 1 and 2 for multiplexer control (as is used by the
ThingMagic 1 to 4 multiplexer) allowing for 16 logical antenna ports.
The Logical Antenna values are static labels indicating the available control
line states. The specific physical antenna port they map to depends on the
control line to antenna port map of the multiplexer in use. The translation
from Logical Antenna label to physical port must be maintained by the
control software.
Functionality of the Mercury6e 53
A DIVISION OF TRIMBLE
Antenna Ports
GPIO 1 & 2 Used for Antenna Switching
Logical Antenna
Setting
1 Low Low J1
2 Low Low J2
3 Low Low J3
4 Low Low J4
5 Low High J1
6 Low High J2
7 Low High J3
8 Low High J4
9 High Low J1
10 High Low J2
11 High Low J3
12 High Low J4
13 High High J1
GPIO
Output 1
State
GPIO
Output 2
State
Active M6e
Physical Port
14 High High J2
15 High High J3
16 High High J4
If only one GPIO Output line is used for antenna control, the combinations of the available
output control line states (the GPIO line in use and the module port) result in a subset of
logical antenna settings which can be used.
ONLY GPIO 1 Used for Antenna Switching
Logical Antenna
Setting
1 Low J1
2 Low J2
GPIO
Output 1
State
Active M6e
Physical Port
54 Functionality of the Mercury6e
A DIVISION OF TRIMBLE
Note
Antenna Ports
Logical Antenna
Setting
3 Low J3
4 Low J4
9 High J1
10 High J2
11 High J3
12 High J4
GPIO
Output 1
State
Active M6e
Physical Port
The “missing” logical antenna settings are still usable when only one GPIO
line is used for antenna control and simply results in redundant logical
antenna settings. For example, using only GPIO 1, logical setting 4 and 8
both result in GPIO1=Low and M6e port J4 active.
ONLY GPIO 2 Used for Antenna Switching
Logical Antenna
Setting
GPIO
Output 2
State
Active M6e
Physical Port
1 Low J1
2 Low J2
3 Low J3
4 Low J4
5 High J1
6 High J2
7 High J3
8 High J4
Port Power and Settling Time
The M6e allows the power and settling time for each logical antenna to be set using the
reader configuration parameters /reader/radio/portReadPowerList and /
Functionality of the Mercury6e 55
Antenna Ports
Note
A DIVISION OF TRIMBLE
reader/antenna/settlingTimeList, respectively. The order the antennas settings
are defined does not affect search order.
Settling time is the time between the control lines switching to the next
antenna setting and RF turning on for operations on that port. This allows
time for external multiplexerʼs to fully switch to the new port before a signal is
sent, if necessary. Default value is 0.
56 Functionality of the Mercury6e
A DIVISION OF TRIMBLE
Tag Handling
When the M6e performs inventory operations (MercuryAPI Read commands) data is
stored in a Tag Bu ff er
client if operating in Tag Streaming/Continuous Reading
Tag Buffer
The M6e uses a dynamic buffer that depends on EPC length and quantity of data read.
As a rule of thumb it can store a maximum of 1024 96-bit EPC tags in the TagBuffer at a
time. Since the M6e supports streaming of read results the buffer limit is, typically, not an
issue. Each tag entry consists of a variable number of bytes and consists of the following
fields:
Tag Handling
until retrieved by the client application, or streamed directly to the
mode.
Tag Buffer Entry
Total Entry
Size
68 bytes
(Max EPC
Length = 496bits)
The Tag buffer acts as a First In First Out (FIFO) — the first Tag found by the reader is
the first one to be read out.
Field Size Description
EPC
Length
PC Word 2 bytes Contains the Protocol Control bits for the tag.
EPC 62 bytes Contains the tagʼs EPC value.
Tag CRC 2 bytes The tagʼs CRC.
2 bytes Indicates the actual EPC length of the tag
read.
Tag Read Meta Data
Tag Streaming/Continuous Reading
When reading tags during asynchronous inventory operations (MercuryAPI
Reader.StartReading()) using an /reader/read/asyncOffTime=0 the M6e “streams”
the tag results back to the host processor. This means that tags are pushed out of the
buffer as soon as they are processed by the M6e and put into the buffer. The buffer is put
into a circular mode that keeps the buffer from filling. This allows for the M6e to perform
continuous search operations without the need to periodically stop reading and fetch the
contents of the buffer. Aside from not seeing “down time” when performing a read
operation this behavior is essentially invisible to the user as all tag handling is done by the
MercuryAPI.
Functionality of the Mercury6e 57
Tag Handling
Note
A DIVISION OF TRIMBLE
It is recommended the USB Interface be used when operating the M6e in
continuous reading mode. When the TTL Level UART Interface is used it is not
possible for the module to detect a broken communications interface
connection and stop streaming the tag results.
58 Functionality of the Mercury6e
A DIVISION OF TRIMBLE
Tag Read Meta Data
In addition to the tag EPC ID resulting from M6e inventory operation each TagReadData
(see MercuryAPI for code details) contains meta data about how, where and when the tag
was read. The specific meta data available for each tag read is as follows:
Tag Read Meta Data
Meta Data Field Description
Antenna ID The antenna on with the tag was read. If the same tag is read
on more than one antenna there will be a tag buffer entry for
each antenna on which the tag was read. When
plexer, if appropriately configured, the Antenna ID entry will
contain the logical antenna port of the tag read.
Read Count The number of times the tag was read on [Antenna ID].
Timestamp The time the tag was read, relative to the time the command to
read was issued, in milliseconds. If the Tag Read Meta Data is
not retrieved from the Tag Buffer between read commands
there will be no way to distinguish order of tags read with different read command invocations.
Tag Data When reading an embedded TagOp is specified for a Read-
Plan the TagReadData will contain the first 128 words of data
returned for each tag.
Note: Tags with the same TagID but different Tag Data
can be considered unique and each get a Tag
Buffer entry if set in the reader configuration
parameter /reader/tagReadData/
uniqueByData. By default it is not.
Frequency The frequency on which the tag was read
Tag Phase
LQI/RSSI The receive signal strength of the tag response in dBm.
GPIO Status The signal status (High or Low) of all GPIO pins when tag was
Average phase of tag response in degrees (0
read.
Tag Read Meta Data
Using a Multi-
°-180°)
Functionality of the Mercury6e 59
A DIVISION OF TRIMBLE
Note
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 /reader/radio/enablePowerSave - controls power
savings while transmitting.
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 Management
PowerMode.FULL – 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.
PowerMode.MINSAVE – 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.
PowerMode.SLEEP – 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. PowerMode.SLEEP is not supported when using the USB interface.
Using the setting PowerMode.MEDSAVE is the same as SLEEP.
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
60 Functionality of the Mercury6e
Power Management
A DIVISION OF TRIMBLE
shown in the table under Power Consumption. The behavior of each mode is as follows:
DRM Compliant Mode
This mode maximizes performance in dense reader environments, minimizing
interference when used with other M6e or similar DRM-compliant readers, and is fully
compliant with the Gen2 DRM spectral mask.
Power Save Mode (non-DRM Compliant)
This mode reduces the power consumption during RF operations but is not 100%
compliant with the DRM spectral mask. This can result increased interference with other
readers and reduce overall systems performance.
Functionality of the Mercury6e 61
A DIVISION OF TRIMBLE
Performance Characteristics
Event Response Times
The following table provides some metrics on how long common M6e operations take. An
event response time is defined as the maximum time from the end of a command (end of
the last bit in the serial stream) or event (e.g. power up) to the response event the
command or event causes.
Event Response Times
Performance Characteristics
Start Command/
Event
Power Up Application Active (with
Power Up Application Active 120 Once the firmware CRC has been veri-
Tag Read RF On 20 When in Power Mode = FULL
Tag Read RF On 50 When in Power Mode = MINSAVE
Tag Read RF On 120 When in Power Mode = SLEEP
Change to MINSAVE PowerMode.MINSAVE 5 From Power Mode = FULL
Change to SLEEP PowerMode.SLEEP 5 From Power Mode = FULL
End Event
CRC check)
Time
(msecs)
1500 This longer power up period should only
occur for the first boot with new firmware.
fied subsequent power ups do not
require the CRC check be performed,
saving time.
Notes
62 Functionality of the Mercury6e
A DIVISION OF TRIMBLE
Save and Restore Configuration
The M6e supports saving module and protocol configuration parameters to the module
flash to provide configuration persistence across boots. Currently (M6e FW v.1.B) the
region, baud-rate, and default protocol can be saved across reboots. Future firmware
upgrades will support saving other configuration values.
See the MercuryAPI Programmers Guide and sample applications for details on saving
and restoring reader configuration.
Save and Restore Configuration
Functionality of the Mercury6e 63
A DIVISION OF TRIMBLE
Save and Restore Configuration
64 Functionality of the Mercury6e
Appendix A: Error Messages
Common Error Messages
The following table lists the common faults discussed in this section.
Fault Message Code
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)
100h
101h
102h
103h
104h
105h
106h
109h
10Ah
FAULT_MSG_WRONG_NUMBER_OF_DATA – (100h)
Cause
If the data length in any of the Host-to-M5e/M5e-Compact messages is less than or more
than the number of arguments in the message, the reader returns this message.
Solution
Make sure the number of arguments matches the data length.
FAULT_INVALID_OPCODE – (101h)
Cause
The opCode received is invalid or not supported in the currently running program
(bootloader or main application) or is not supported in the current version of code.
Appendix A: Error Messages 65
Common Error Messages
Solution
Check the following:
Make sure the command is supported in the currently running program.
Check the documentation for the opCode the host sent and make sure it is correct and
supported.
Check the previous module responses for an assert (0x7F0X) which will reset the
module into the bootloader.
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.
66 Appendix A: Error Messages
Common Error Messages
FAULT_MSG_INVALID_FREQ_RECEIVED (104h)
Cause
A message was received by the reader to set the frequency outside the supported range
Solution
Make sure the host does not set the frequency outside this range or any other locally
supported ranges.
FAULT_MSG_INVALID_PARAMETER_VALUE - (105h)
Cause
The reader received a valid command with an unsupported or invalid value within this
command.
For example, currently the module supports four antennas. If the module receives a
message with an antenna value other than 1 to 4, it returns this error.
Solution
Make sure the host sets all the values in a command according to the values published in
this document.
FAULT_MSG_POWER_TOO_LOW - (106h)
Cause
A message was received to set the read or write power to a level that is lower than the
current HW supports.
Solution
Check the HW specifications for the supported powers and insure that level is not
exceeded. The M6e supports powers between 5 and 31.5 dBm.
FAULT_UNIMPLEMENTED_FEATURE - (109h)
Cause
Attempting to invoke a command not supported on this firmware or hardware.
Appendix A: Error Messages 67
Common Error Messages
Solution
Check the command being invoked against the documentation.
FAULT_INVALID_BAUD_RATE - (10Ah)
Cause
When the baud rate is set to a rate that is not specified in the Baud Rate table, this error
message is returned.
Solution
Check the table of specific baud rates and select a baud rate.
68 Appendix A: Error Messages
Bootloader Faults
The following table lists the common faults discussed in this section.
Fault Message Code
FAULT_BL_INVALID_IMAGE_CRC 200h
FAULT_BL_INVALID_APP_END_ADDR 201h
FAULT_BL_INVALID_IMAGE_CRC – 200h
Cause
When the application firmware is loaded the reader checks the image stored in flash and
returns this error if the calculated CRC is different than the one stored in flash.
Bootloader Faults
Solution
The exact reason for the corruption could be that the image loaded in flash was corrupted
during the transfer or corrupted for some other reason.
To fix this problem, reload the application code in flash.
FAULT_BL_INVALID_APP_END_ADDR – 201h
Cause
When the application firmware is loaded the reader checks the image stored in flash and
returns this error if the last word stored in flash does not have the correct address value.
Solution
The exact reason for the corruption could be that the image loaded in flash got corrupted
during the transfer or, corrupted for some other reason.
To fix this problem, reload the application code in flash.
Appendix A: Error Messages 69
Flash Faults
The following table lists the common faults discussed in this section.
Fault Message Code
Flash Faults
FAULT_FLASH_BAD_ERASE_PASSWORD – 300h
FAULT_FLASH_BAD_WRITE_PASSWORD – 301h
FAULT_FLASH_UNDEFINED_ERROR – 302h
FAULT_FLASH_ILLEGAL_SECTOR – 303h
FAULT_FLASH_WRITE_TO_NON_ERASED_AREA – 304h
FAULT_FLASH_WRITE_TO_ILLEGAL_SECTOR – 305h
FAULT_FLASH_VERIFY_FAILED – 306h
300h
301h
302h
303h
304h
305h
306h
FAULT_FLASH_BAD_ERASE_PASSWORD – 300h
Cause
A command was received to erase some part of the flash but the password supplied with
the command was incorrect.
Solution
When this occurs make note of the operations you were executing, save FULL error
response and send a testcase reproducing the behavior to support@thingmagic.com.
FAULT_FLASH_BAD_WRITE_PASSWORD – 301h
Cause
A command was received to write some part of the flash but the password supplied with
the command was not correct.
Solution
When this occurs make note of the operations you were executing, save FULL error
response and send a testcase reproducing the behavior to support@thingmagic.com.
70 Appendix A: Error Messages
Flash Faults
FAULT_FLASH_UNDEFINED_ERROR – 302h
Cause
This is an internal error and it is caused by a software problem in module.
Solution
When this occurs make note of the operations you were executing, save FULL error
response and send a testcase reproducing the behavior to support@thingmagic.com.
FAULT_FLASH_ILLEGAL_SECTOR – 303h
Cause
An erase or write flash command was received with the sector value and password not
matching.
Solution
When this occurs make note of the operations you were executing, save FULL error
response and send a testcase reproducing the behavior to support@thingmagic.com.
FAULT_FLASH_WRITE_TO_NON_ERASED_AREA – 304h
Cause
The module received a write flash command to an area of flash that was not previously
erased.
Solution
When this occurs make note of the operations you were executing, save FULL error
response and send a testcase reproducing the behavior to support@thingmagic.com.
FAULT_FLASH_WRITE_TO_ILLEGAL_SECTOR – 305h
Cause
The module received a write flash command to write across a sector boundary that is
prohibited.
Appendix A: Error Messages 71
Flash Faults
Solution
When this occurs make note of the operations you were executing, save FULL error
response and send a testcase reproducing the behavior to support@thingmagic.com.
FAULT_FLASH_VERIFY_FAILED – 306h
Cause
The module received a write flash command that was unsuccessful because data being
written to flash contained an uneven number of bytes.
Solution
When this occurs make note of the operations you were executing, save FULL error
response and send a testcase reproducing the behavior to support@thingmagic.com.
72 Appendix A: Error Messages
Protocol Faults
The following table lists the common faults discussed in this section.
Fault Message Code
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
400h
401h
402h
403h
404h
405h
406h
407h
408h
409h
40Ah
40Bh
40Ch
40Eh
40Fh
410h
411h
420h
423h
424h
42Bh
42Fh
430h
Appendix A: Error Messages 73
Protocol Faults
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 protocol must be set before the reader can begin RF operations.
FAULT_INVALID_PROTOCOL_SPECIFIED – 402h
Cause
The protocol value was set to a protocol that is not supported with the current version of
SW.
74 Appendix A: Error Messages
Protocol Faults
Solution
This value is invalid or this version of SW does not support the protocol value. Check the
documentation for the correct values for the protocols in use and that you are licensed for
it.
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 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 other tags 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
Make sure the region and tag protocol have been set to supported values.
Appendix A: Error Messages 75
Protocol Faults
FAULT_PROTOCOL_WRITE_FAILED – 406h
Cause
An attempt to modify the contents of a tag failed. There are many reasons for failure.
Solution
Check that the tag is good and try another operation on a few more tags.
FAULT_NOT_IMPLEMENTED_FOR_THIS_PROTOCOL – 407h
Cause
A command was received which is not supported by a protocol.
Solution
Check the documentation for the supported commands and protocols.
FAULT_PROTOCOL_INVALID_WRITE_DATA – 408h
Cause
An ID write was attempted with an unsupported/incorrect ID length.
Solution
Verify the Tag ID length being written.
FAULT_PROTOCOL_INVALID_ADDRESS – 409h
Cause
A command was received attempting to access an invalid address in the tag data address
space.
Solution
Make sure that the address specified is within the scope of the tag data address space
and available for the specific operation. The protocol specifications contain information
about the supported addresses.
76 Appendix A: Error Messages
Protocol Faults
FAULT_GENERAL_TAG_ERROR – 40Ah
Cause
This error is used by the GEN2 module. This fault can occur if the read, write, lock, or kill
command fails. This error can be internal or functional.
Solution
Make a note of the operations you were performing and contact ThingMagic at http://
support.thingmagic.com
FAULT_DATA_TOO_LARGE – 40Bh
Cause
A command was received to Read Tag Data with a data value larger than expected or it is
not the correct size.
Solution
Check the size of the data value in the message sent to the reader.
FAULT_PROTOCOL_INVALID_KILL_PASSWORD – 40Ch
Cause
An incorrect kill password was received as part of the Kill command.
Solution
Check the password.
FAULT_PROTOCOL_KILL_FAILED - 40Eh
Cause
Attempt to kill a tag failed for an unknown reason
Solution
Check tag is in RF field and the kill password.
Appendix A: Error Messages 77
Protocol Faults
FAULT_PROTOCOL_BIT_DECODING_FAILED - 40Fh
Cause
Attempt to operate on a tag with an EPC length greater than the Maximum EPC length
setting.
Solution
Check the EPC length being written.
FAULT_PROTOCOL_INVALID_EPC – 410h
Cause
This error is used by the GEN2 module indicating an invalid EPC value has been
specified for an operation. This fault can occur if the read, write, lock, or kill command
fails.
Solution
Check the EPC value that is being passed in the command resulting in this error.
FAULT_PROTOCOL_INVALID_NUM_DATA – 411h
Cause
This error is used by the GEN2 module indicating invalid data has been specified for an
operation. This fault can occur if the read, write, lock, or kill command fails.
Solution
Check the data that is being passed in the command resulting in this error.
FAULT_GEN2 PROTOCOL_OTHER_ERROR - 420h
Cause
This is an error returned by Gen2 tags. Its a catch-all for error not covered by other codes.
78 Appendix A: Error Messages
Protocol Faults
Solution
Check the data that is being passed in the command resulting in this error. Try with a
different tag.
FAULT_GEN2_PROTOCOL_MEMORY_OVERRUN_BAD_PC 423h
Cause
This is an error returned by Gen2 tags. The specified memory location does not exist or
the PC value is not supported by the Tag.
Solution
Check the data that is being written and where its being written to in the command
resulting in this error.
FAULT_GEN2 PROTOCOL_MEMORY_LOCKED - 424h
Cause
This is an error returned by Gen2 tags.The specified memory location is locked and/or
permalocked and is either not writable or not readable.
Solution
Check the data that is being written and where its being written to in the command
resulting in this error. Check the access password being sent.
FAULT_GEN2 PROTOCOL_INSUFFICIENT_POWER - 42Bh
Cause
This is an error returned by Gen2 tags. The tag has insufficient power to perform the
memory-write operation.
Solution
Try moving the tag closer to the antenna. Try with a different tag.
Appendix A: Error Messages 79
Protocol Faults
FAULT_GEN2 PROTOCOL_NON_SPECIFIC_ERROR - 42Fh
Cause
This is an error returned by Gen2 tags. The tag does not support error specific codes.
Solution
Check the data that is being written and where its being written to in the command
resulting in this error. Try with a different tag.
FAULT_GEN2 PROTOCOL_UNKNOWN_ERROR - 430h
Cause
This is an error returned by M6e when no more error information is available about why
the operation failed.
Solution
Check the data that is being written and where its being written to in the command
resulting in this error. Try with a different tag.
80 Appendix A: Error Messages
Analog Hardware Abstraction Layer Faults
Analog Hardware Abstraction Layer Faults
FAULT_AHAL_INVALID_FREQ – 500h
Cause
A command was received to set a frequency outside the specified range.
Solution
Check the values you are trying to set and be sure that they fall within the range of the set
region of operation.
FAULT_AHAL_CHANNEL_OCCUPIED – 501h
Cause
With LBT enabled an attempt was made to set the frequency to an occupied channel.
Solution
Try a different channel. If supported by the region of operation turn LBT off.
FAULT_AHAL_TRANSMITTER_ON – 502h
Cause
Checking antenna status while CW is on is not allowed.
Solution
Do not perform antenna checking when CW is turned on.
FAULT_ANTENNA_NOT_CONNECTED – 503h
Cause
An attempt was made to transmit on an antenna which did not pass the antenna detection
when antenna detection was turned on.
Appendix A: Error Messages 81
Analog Hardware Abstraction Layer Faults
Solution
Connect a detectable antenna (antenna must have some DC resistance).
FAULT_TEMPERATURE_EXCEED_LIMITS – 504h
Cause
The module has exceeded the maximum or minimum operating temperature and will not
allow an RF operation until it is back in range.
Solution
Take steps to resolve thermal issues with module:
Reduce duty cycle
Add heat sink
Use Power Save Mode (non-DRM Compliant)
FAULT_POOR_RETURN_LOSS – 505h
Cause
The module has detected a poor return loss and has ended RF operation to avoid module
damage.
Solution
Take steps to resolve high return loss on receiver:
Make sure antenna VSWR is within module specifications
Make sure antennas are correctly attached before transmitting
Check environment to ensure no occurrences of high signal reflection back at
antennas.
FAULT_AHAL_INVALID_ANTENA_CONFIG – 507h
Cause
An attempt to set an antenna configuration that is not valid.
82 Appendix A: Error Messages
Analog Hardware Abstraction Layer Faults
Solution
Use the correct antenna setting or change the reader configuration.
Appendix A: Error Messages 83
Tag ID Buffer Faults
The following table lists the common faults discussed in this section.
Fault Message Code
Tag ID Buffer Faults
FAULT_TAG_ID_BUFFER_NOT_ENOUGH_TAGS_AVAILABLE – 600h
FAULT_TAG_ID_BUFFER_FULL – 601h
FAULT_TAG_ID_BUFFER_REPEATED_TAG_ID – 602h
FAULT_TAG_ID_BUFFER_NUM_TAG_TOO_LARGE – 603h
600h
601h
602h
603h
FAULT_TAG_ID_BUFFER_NOT_ENOUGH_TAGS_AVAILABLE – 600h
Cause
A command was received to get a certain number of tag ids from the tag id buffer. The
reader contains less tag ids stored in its tag id buffer than the number the host is sending.
Solution
Send a testcase reproducing the behavior to support@thingmagic.com.
FAULT_TAG_ID_BUFFER_FULL – 601h
Cause
The tag id buffer is full.
Solution
Make sure the baud rate is set to a higher frequency that the /reader/gen2/BLF frequency.
Send a testcase reproducing the behavior to support@thingmagic.com.
84 Appendix A: Error Messages
Tag ID Buffer Faults
FAULT_TAG_ID_BUFFER_REPEATED_TAG_ID – 602h
Cause
The module has an internal error. One of the protocols is trying to add an existing TagID
to the buffer.
Solution
Send a testcase reproducing the behavior to support@thingmagic.com.
FAULT_TAG_ID_BUFFER_NUM_TAG_TOO_LARGE – 603h
Cause
The module received a request to retrieve more tags than is supported by the current
version of the software.
Solution
Send a testcase reproducing the behavior to support@thingmagic.com.
Appendix A: Error Messages 85
System Errors
FAULT_SYSTEM_UNKNOWN_ERROR – 7F00h
Cause
The error is internal.
Solution
Send a testcase reproducing the behavior to support@thingmagic.com.
FAULT_TM_ASSERT_FAILED – 7F01h
Cause
System Errors
An unexpected Internal Error has occurred.
Solution
The error will cause the module to switch back to Bootloader mode. When this occurs
make note of the operations you were executing, save FULL error response and send a
testcase reproducing the behavior to support@thingmagic.com.
86 Appendix A: Error Messages
Appendix B: Getting Started - Devkit
Devkit Hardware
Included Components
With the devkit, you will receive the following components:
The M6e module and power/interface developers board
One USB cable
One antenna
One coax cable
One 9V power supply
International power adapter kit
Sample tags
One paper insert:
– QuickStart Guide - Details on which documents and software to download to get
up and running quickly, along with details on how to register for and contact
support.
Setting up the DevKit
When setting up the DevKit, use the following procedures:
Connecting the Antenna
Powering up and Connecting to a PC
Appendix B: Getting Started - Devkit 87
Devkit Hardware
WARNING!
Connecting the Antenna
ThingMagic supplies one antenna that can read tags from 20ʼ away with most of the
provided tags. The antenna is monstatic. Use the following procedure to connect the
antenna to the DevKit.
1. Connect one end of the coax cable to the antenna.
2. Connect the other end of the cable to the antenna port 1 connector on the DevKit.
Powering up and Connecting to a PC
After connecting the antenna you can power up the DevKit and establish a host
connection.
1. Connect the USB cable (use only the black connector) from a PC to the developerʼs
kit. There are two Devkit USB Interfaces
2. Plug the power supply into the DevKitʼs DC power input connector.
options.
3. The LED next to the DC input jack, labeled DS1, should light up. If it doesnʼt light up
check jumper J17
4. Follow the steps based on the Devkit USB Interfaces
port or /dev device file, as appropriate for your operating system the USB interface is
assigned.
5. To start reading tags start the Demo Application
to make sure the jumper is connecting pins 2 and 3
used and make note of the COM
(Universal Reader Assistant).
While the module is powered up, do not touch components. Doing so
may be damaged the devkit and M6e module.
88 Appendix B: Getting Started - Devkit
Devkit Hardware
Note
Devkit USB Interfaces
USB/RS232
The USB interface (connector labeled USB/RS232) closest to the power plug is to the
RS232 interface of the M6e through an FTDI USB to serial converter. The drivers for it are
available at
http://www.ftdichip.com/Drivers/VCP.htm
Please follow the instructions in the installation guide appropriate for your operating
system.
Native USB
To use the M6e native USB interface (connector labeled USB), if on Windows, a few
installation steps are required for Windows to recognize the M6e and properly configure
the communications protocol. In order to use the USB interface with Windows you must
have the m6eultra.inf file (available for download from rfid.thingmagic.com/devkit). The
installation steps are:
1. Plug in the USB cable to the M6e (devkit) and PC.
2. Windows should report is has “Found New Hardware - Mercury6eUltra” and open the
Hardware Installation Wizard.
3. Select the Install from a list or specific location (Advanced) option, click Next.
4. Select Donʼt search..., click Next, then Next again.
5. Click Have Disk and navigate to where the m6ultra.inf file is stored and select it, click
Open, then OK.
6. “Mercury6eUltra” should now be shown under the Model list. Select it and click Next
then Finished.
The M6e driver file has not been Microsoft certified so compatibility warnings
will be displayed. These can be ignored and clicked through.
7. A COM port should now be assigned to the M6e. If you arenʼt sure what COM port is
assigned you can find it using the Windows Device Manager:
a. Open the Device Manager (located in Control Panel | System).
b. Select the Hardware tab and click Device Manager.
Appendix B: Getting Started - Devkit 89
Devkit Hardware
c. Select View | Devices by Type | Ports (COM & LPT) The device appears as
Mercury6eUltra (COM#).
Devkit Jumpers
J8
Jumpers to connect M6e I/O lines to devkit.
J9
Header for alternate power supply. Make sure DC plug (J1) is not connected if using J9.
J10, J11, J13, J15
Jump pins OUT to GPIO# to connect M6e GPIO lines to output LEDs. Jumpe pins IN to
GPIO# to connect M6e GPIO to corresponding input switches SW[3-6]GPIO#. Make
sure GPIO lines are correspondingly configured as input or outputs (see Configuring GPIO
Settings).
J14
Can be used to connect GPIO lines to external circuits. If used jumpers should be
removed from J10, J11, J13, J15
.
J16
Jump pins 1 and 2 or 2 and 3 to reset devkit power supply. Same as using switch SW1
except allows for control by external circuit.
J17
Jump pins 1 and 2 to use the 5V INPUT and GND inputs to provide power. Jump pins 2
and 3 to use the DevKitʼs DC power jack and power brick power.
J19
Jump SHUTDOWN to GND to enable module. While grounded SHUTDOWN pushbutton
(SW2) will break circuit and shutdown the M6e (see M6e Digital Connector Signal
Definition). AUTO_BOOT controls Reset Line.
90 Appendix B: Getting Started - Devkit
Devkit Schematics
Available upon request from support@thingmagic.com.
Devkit Hardware
Appendix B: Getting Started - Devkit 91
Demo Application
A demo application which supports multi-protocol reading and writing is provided in the
MercuryAPI SDK package and as a standalone application, both are available on
rfid.thingmagic.com/devkit. The executable for this example is included in the MercuryAPI
SDK package under /cs/samples/exe/Universal-Reader-Assistant2.0.exe.
See the Universal-Reader-Assistant 2.0 User Guide (on rfid.thingmagic.com/devkit) for
usage details.
See the MercuryAPI Programming Guide for details on using the MercuryAPI.
Demo Application
92 Appendix B: Getting Started - Devkit
Notice on Restricted Use of the DevKit
Notice on Restricted Use of the DevKit
The Mercury6e Developers Kit (DevKit) is intended for use solely by professional
engineers for the purpose of evaluating the feasibility of applications.
The userʼs evaluation must be limited to use within a laboratory setting. This DevKit has
not been certified for use by the FCC in accordance with Part 15 of the FCC regulations,
ETSI, KCC or any other regulatory bodies and may not be sold or given for public use.
Distribution and sale of the DevKit is intended solely for use in future development of
devices which may be subject to regional regulatory authorities governing radio emission.
This DevKit may not be resold by users for any purpose. Accordingly, operation of the
DevKit in the development of future devices is deemed within the discretion of the user
and the user shall have all responsibility for any compliance with any regional regulatory
authority governing radio emission of such development or use, including without
limitation reducing electrical interference to legally acceptable levels. All products
developed by user must be approved by the appropriate regional regulatory authority
governing radio emission prior to marketing or sale of such products and user bears all
responsibility for obtaining the prior appropriate regulatory approval, or approval as
needed from any other authority governing radio emission.
Appendix B: Getting Started - Devkit 93
Notice on Restricted Use of the DevKit
94 Appendix B: Getting Started - Devkit
Appendix C: Environmental
WARNING!
Considerations
This Appendix details environmental factors that should be considered relating to reader
performance and survivability.
ElectroStatic Discharge (ESD) Considerations
The M6e antenna ports may be susceptible to damage from Electrostatic
Discharge (ESD). Equipment failure can result if the antenna or communication
ports are subjected to ESD. Standard ESD precautions should be taken during
installation to avoid static discharge when handling or making connections to
the M6 reader antenna or communication ports. Environmental analysis should
also be performed to ensure static is not building up on and around the antennas,
possibly causing discharges during operation.
ESD Damage Overview
In M6e-based reader installations where readers have failed without known cause, based
on anecdotal information ESD has been found to be the most common cause. Failures
due to ESD tend to be in the M6e power amplifier section (PA). PA failures typically
manifest themselves at the software interface in the following ways:
RF operations (read, write, etc.) respond with Assert - 7F01 - indicating a a fatal error.
This is typically due the the module not being able to reach the target power level due
to PA damage.
RF operations (read, write, etc.) respond with No Antenna Connected/Detected
even when a known good antenna is attached.
Unexpected Invalid Command errors, indicating command not supported, when that
command had worked just fine shortly before. The reason a command becomes
suddenly not supported is that the reader, in the course of its self protection routines,
Appendix C: Environmental Considerations 95
ElectroStatic Discharge (ESD) Considerations
has returned to the bootloader to prevent any further damage. This jump to boot
loader caused by power amp damage occurs at the start of any read tag commands.
Ultimately determining that ESD is the root cause of failures is difficult because it relies on
negative result experiments, i.e. it is the lack of failure after a configuration change, rather
than a positive flag wave that says “Iʼm ESD”. Such flag waves are sometimes, but only
sometimes, available at the unpackaged transistor level under high power microscopy.
The remoteness of microscopic examination from the installed field failures is indicative of
the high cost of using such analysis methods for chasing down ESD issues. Therefore
most ESD issue resolutions will be using the negative result experiments to determine
success.
ESD discharges come with a range of values, and like many things in life there is the
“matter of degree”. For many installations, the M6e has been successfully deployed and
operates happily. For these, there is no failure issue, ESD or otherwise. For a different
installation that with bare M6e, has a failure problem from ESD, there will be some
distribution of ESD intensities occurring. Without knowledge of a limit in the statistics of
those intensities, there may always be the bigger zap waiting in the wings. For the bare
M6e equipped with the mitigation methods described below, there will always be the
rouge ESD discharge that exceeds any given mitigation, and results in failure.
Fortunately, many installations will have some upper bound on the value of ESD events
given the geometry of that installation.
Several sequential steps are recommended for a) determining the ESD is the likely cause
of a given group of failures, and b) enhancing the M6eʼs environment to eliminate ESD
failures. The steps vary depending on the required M6e output power in any given
application.
Identifying ESD as the Cause of Damaged Readers
The following are some suggested methods to determine if ESD is a cause of reader
failures, i.e. ESD diagnostics. Please remember- some of these suggestions have the
negative result experiment problem.
Return failed units for analysis. Analysis should be able to say if it is the power
amplifier that has in fact failed, but wonʼt be able to definitively identify that the cause
is ESD. However, ESD is one of the more common causes of PA failure.
Measure ambient static levels with static meter. AlphaLabs SVM2 is such a meter, but
there are others. You may be surprised at the static potentials floating detected.
However, high static doesnʼt necessarily mean discharges, but should be considered
cause for further investigation. High levels that keep changing are highly indicative of
discharges.
Touch some things around the antenna, and operating area. If you feel static
discharges, that qualitatively says quite a bit about what is in front of the antenna.
96 Appendix C: Environmental Considerations
ElectroStatic Discharge (ESD) Considerations
What actually gets to the M6e is also strongly influenced by the antenna installation,
cabling, and grounding discussed above.
Use the mean operating time statistic before and after one or more of the changes
listed below to quantitatively determine if the change has resulted in an improvement.
Be sure to restart your statistics after the change.
Common Installation Best Practices
The following are common installation best practices which will ensure the readers isnʼt
being unnecessarily exposed to ESD in even low risk environments. These should be
applied to all installations, full power or partial power, ESD or not:
Insure that M6e, M6e enclosing housing (e.g. Vega reader housing), and antenna
ground connection are all grounded to a common low impedance ground.
Verify R-TNC knurled threaded nuts are tight and stay tight. Donʼt use a thread locking
compound that would compromise the grounding connection of the thread to thread
mate. If there is any indication that field vibration might cause the R-TNC to loosen,
apply RTV or other adhesive externally.
Use antenna cables with double shield outer conductors, or even full metallic shield
semirigid cables. ThingMagic specified cables are double shielded and adequate for
most applications. ESD discharge currents flowing ostensibly on the outer surface of
a single shield coaxial cable have been seen to couple to the inside of coaxial cables,
causing ESD failure. Avoid RG-58. Prefer RG-223.
Minimize ground loops in coaxial cable runs to antennas. Having the M6e and
antenna both tied to ground (per item 1) leads to the possibility of ground currents
flowing along antenna cables. The tendency of these currents to flow is related to the
area of the conceptual surface marked out by the antenna cable and the nearest
continuous ground surface. When this conceptual surface has minimum area, these
ground loop current are minimized. Routing antenna cables against grounded
metallic chassis parts helps minimize ground loop currents.
Keep the antenna radome in place. It provides significant ESD protection for the
metallic parts of the antenna, and protects the antenna from performance changes
due to environmental accumulation.
Keep careful track of serial numbers, operating life times, numbers of units operating.
You need this information to know that your mean operating life time is. Only with this
number will you be able to know if you have a failure problem in the first place, ESD
or otherwise. And then after any given change, whether things have improvement or
not. Or if the failures are confined to one instantiation, or distributed across your
population.
Appendix C: Environmental Considerations 97
ElectroStatic Discharge (ESD) Considerations
Note
Raising the ESD Threshold
For applications where full M6e power is needed for maximum tag read range and ESD is
suspected the following components are recommended additions to the installation to
raise the level of ESD the reader can tolerate:
Select or change to an antenna with all radiating elements grounded for DC. The MTI
MT-262031-T(L,R)H-A is such an antenna. The Laird IF900-SF00 and CAF95956
are not such antennas. The grounding of the antenna elements dissipates static
charge leakage, and provides a high pass characteristic that attenuates discharge
events. (This also makes the antenna compatible with the M6e antenna detect
methods.)
Install a Minicircuits SHP600+ high pass filter in the cable run at the M6e (or Vega or
other finished reader) end. This additional component will reduce transmit power by
0.4 dB which may affect read range in some critical applications. However the filter
will significantly attenuate discharges and improve the M6e ESD survival level.
The SHP600+ is not rated for the full +31.5 dBm output of the M6e reader at
+85 degree C. Operation at reduced temperature has been anecdotally
observed to be OK, but has not been fully qualified by ThingMagic.
Install a Diode Clamp* circuit immediately outboard from the SHP600 filter. This will
reduce transmit power by an additional 0.4 dB, but in combination with the SHP600
will further improve the M6e ESD survival level. * Not yet productized. Needs DC
power, contact support@thingmagic.com for details.
Further ESD Protection for Reduced RF Power Applications
In addition to the protective measures recommended above, for applications where
reduced M6e RF power is acceptable and ESD is suspected the following protective
measures can also be applied:
Install a one watt attenuator with a decibel value of +30 dBm minus the dBm value
needed for tag power up. Then run the reader at +30 dBm instead of reduced
transmit power. This will attenuate inbound ESD pulses by the installed decibel
value, while keeping the tag operation generally unchanged. Attenuators of 6 dB
have been shown to not adversely effect read sensitivity. Position the attenuator as
close to the M6e as feasible.
As described above add the SHP600 filter immediately adjacent to the attenuator, on
the antenna side.
Add Diode Clamp, if required, adjacent to the SHP600, on the antenna side.
98 Appendix C: Environmental Considerations
Variables Affecting Performance
Reader performance may be affected by the following variables, depending on the site
where your Reader is being deployed:
Environmental
Tag Considerations
Multiple Readers
Environmental
Reader performance may be affected by the following environmental conditions:
Metal surfaces such as desks, filing cabinets, bookshelves, and wastebaskets
may enhance or degrade Reader performance.
Variables Affecting Performance
Antennas should be mounted far away from metal surfaces that may adversely
affect the system performance.
Devices that operate at 900 MHz, such as cordless phones and wireless LANs,
can degrade Reader performance. The Reader may also adversely affect the
performance of these 900 MHz devices.
Moving machinery can interfere the Reader performance. Test Reader
performance with moving machinery turned off.
Fluorescent lighting fixtures are a source of strong electromagnetic interference
and if possible should be replaced. If fluorescent lights cannot be replaced, then
keep the Reader cables and antennas away from them.
Coaxial cables leading from the Reader to antennas can be a strong source of
electromagnetic radiation. These cables should be laid flat and not coiled up.
Tag Considerations
There are several variables associated with tags that can affect Reader performance:
Application Surface: Some materials, including metal and moisture, interfere with
tag performance. Tags applied to items made from or containing these materials
may not perform as expected.
Appendix C: Environmental Considerations 99
Tag Orientation: Reader performance is affected by the orientation of the tag in
Note
the antenna field. The ThingMagic antenna is circularly polarized, so it reads
face-to but not edge-to.
Tag Model: Many tag models are available. Each model has its own
performance characteristics.
Multiple Readers
The Reader adversely affect performance of 900 MHz devices. These devices also may
degrade performance of the Reader.
Antennas on other Readers operating in close proximity may interfere with one
another, thus degrading performance of the Readers.
Interference from other antennas may be eliminated or reduced by using either
one or both of the following strategies:
Variables Affecting Performance
w Affected antennas may be synchronized by a separate user application using
a time-multiplexing strategy.
w Antenna power can be reduced by reconfiguring the RF Transmit Power
setting for the Reader.
Performance tests conducted under typical operating conditions at your site are
recommended to help you optimize system performance.
100 Appendix C: Environmental Considerations
Loading...