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 13
www.JADAKtech.com
1. Action bits: meant to trigger a feature upon a SELECT command on the related bit:
Parallel encoding (at address 0x202)
Tag Power indicator (at address 0x204)
2. Permanent bits: permanently stored bits in the memory
Max. Backscatter Strength (at address 0x209)
PSF Alarm bit (at address 0x20F)
Refer Mercury API v1.29.4 release notes for API commands to work with this functionality.
Gen2 Parameters in Metadata
Now that modification of the Gen2 parameters are allowed at will, it is desirable to include current Gen2
settings as metadata when tags are read so that the active setting under which the tag was read is
reported.
For example, Gen2 Q value can change dynamically so a user trying to determine the best static value
would benefit from knowing the value that the automated algorithm selected. Gen2 parameters included in
metadata are:
• Gen2 Q
• Gen2 Link Frequency
• Gen2 Target
Gen2 Q, BLF and Target parameters have been added to the TagReadData.TagMetadata method. The
Read code sample in the MercuryAPI SDK shows how to activate this functionality.
Support for Acura Gen2V2 Tags
NMV2D tag support has been added in M6e FW, which returns 352 (256+96) bits in TAM2 reply for
ProtModes 0x02 and 0x03 and 256 bits for ProtModes 0x00 and 0x01. Previous release version of FW
v1.7.1 replies with 256 bits irrespective of any ProtMode.
The NMV2D tag supports the same set of commands as NXP UCODE AES tag except following:
• NXP UCODE AES tag chip only supports ProtMode=1 while NMV2D tag supports ProtModes=0,1,2,3.
• Untrace-Access and Untrace-Authen commands do not work for NMV2D tag as they do for UCODE AES
tag.
Refer to the Authenticate, ReadBuffer and Untraceable code samples in the MercuryAPI SDK to test this
functionality.
Support for GEN2V2 Embedded Tag Ops
In previous firmware releases, GEN2V2 operations that supported the NXP UCODE DNA tag were only
available as stand-alone, single tag functions. Now support for embedded tag operations has been added
for both NXP UCODE DNAtag and the NMV2D tag. This allows for high speed secure reading in
Asynchronous modes.
Refer to the Authenticate, ReadBuffer and Untraceable code samples in the MercuryAPI SDK to test this
functionality.
Gen2V2 Support
The M6e supports the Gen2V2 features of the NXP DNA tags. These features include: