Tag operations, Custom tag commands, Flash memory – ThingMagic M5e-Compact User Manual
Page 45
![background image](/manuals/640737/45/background.png)
Tag Operations
Functionality of the Embedded Modules
45
In First Out (FIFO) — the first Tag found by the reader is the first one to be read out. See
.
The Tag buffer is reset when the
command is sent or when the
protocol is set or changed using
Set Current Tag Protocol (93h)
. This allows multiple Read
Tag Multiple
commands to be used to acquire one consistent tag buffer set.
Tag Operations
In addition to inventorying tags the M5e supports commands, defined in
, which operate on individual tags in a variety of ways. The various operations
can be performed on the first tag to respond, the default behavior for all but
, as well as on all tags in the field as part of a
. Most of the operations can be performed with
allowing them to be applied to a specific tag or set of tags.
Custom Tag Commands
Many tags now support non-”Gen2 Standard” operations. Features such as read locking
memory, setting digital outputs, reading sensor data - such as temperature - from sensor
tags among many others. The supported commands are listed in the
commands as well as in the
MercuryAPI Programmers Guide | Level 2 | Advanced
Tag
Operations section.
Flash Memory
The modules have on-board flash memory. This flash is divided into four different sectors
of varying sizes. Table 4 shows the memory map for the modules. Only sector 0x03 is set
aside for user data and the other sectors are used by the application FW. For cross-
platform and legacy development purposes two methods of accessing flash on the M5e-
family modules is supported, one based on the memory map of the M4e. The memory
map for the M4e is very different than the memory map for the M5e and M5e-Compact.
The flash sector utilities simplify the interface providing a means to develop interfaces
that work across these platforms. For all new development you must use