User's Guide
Table Of Contents
- THINGMAGIC M6e User Guide
- Introduction
- Hardware Overview
- Hardware Interfaces
- Digital/Power Connector
- USB Interface
- General Purpose Input/Output (GPIO)
- Power Requirements
- Special RF Power Output Requirements for the M6e-A
- Environmental Specifications
- Electro-Static Discharge (ESD) Specification
- Mounting Screw Clearance
- Assembly Information
- Antennas
- M6e Mechanical Drawing
- Authorized Antennas
- M6e-A Authorized Cables
- Firmware Overview
- New Features - Version 1.21.2
- Margin Read Support for Monza6 Tags
- NXP UCODE7 Configuration Support
- Gen2 Parameters in Metadata
- Support for Acura Gen2V2 Tags
- Support for GEN2V2 Embedded Tag Ops
- Gen2V2 Support
- Denatran Tag Support
- Configurable T4 for Gen2 Protocol
- Ability to “Read Data” Immediately After Sending a “Write EPC” or “Write Data” Command
- Decoupling Antenna Selection from AsyncOnTime
- Support for Additional Regions
- Support for Set/get Quantization Value and Minimum Frequency in Open Region
- Operational Notes
- Boot Loader
- Application Firmware
- Custom On-Reader Applications
- New Features - Version 1.21.2
- Communication Protocol
- Functionality
- Specifications
- Compliance and IP Notices
- Error Messages
- Getting Started – Development Kit and Carrier Board
- Environmental Considerations
ThingMagic M6e User Guide 36
www.JADAKtech.com
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.
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.
Save and Restore Configuration
The M6e supports saving module and protocol configuration parameters to the module flash to provide
configuration persistence across boots. This was introduced to support Autonomous Operation, but can
also be used to reduce the amount of communication necessary to bring a module up to operating state
following a reboot. The parameters that can be saved include:
• Region
• Baud Rate (for serial interface)
• Default Protocol
• RF power
• Antenna search list
• Gen2 “M” value
• Gen2 BLF (Tari will be 25 usec if BLF=250 and 6.25 usec if BLF=640)
Event Response Times
Start Command/
Event
End Event
Time
(msecs)
Notes
Power Up Application Active (with
CRC check)
1500 This longer power up period should
only occur for the first boot with new
firmware.
Power Up Application Active 120 Once the firmware CRC has been
verified subsequent power ups do
not require the CRC check be
performed, saving time.
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