Manualshelf

Design Guide

ManualsBrandsSparkfun Electronics ManualsRFIDSimultaneous RFID Reader - M6E Nano
81828384858687888990
Power Management
A DIVISION OF TRIMBLE
Functionality of the ThingMagic Nano 85
Power Management
The ThingMagic Nano is designed for power efficiency and offers several power
management modes. When transmitting, the power consumption can be minimized by
using the lowest RF power level that meets the application requirements, and powering
the module with highest DC input Voltage.
A “Power Mode” setting determines the power consumed during periods that the module
is not actively transmitting. Power Modes
- is set in /reader/powerMode.
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. Our terminology can be
a little confusing. “MINSAVE” refers to the minimum amount of power saving applied,
which results in a higher idle power level than “MAXSAVE”.
The details of the amount of power consumed in each mode is shown in the table under
Idle DC Power Consumption
. The behavior of each mode and impact on RF command
latency is as follows:
PowerMode.FULL – In this mode, the unit operates at full power to attain the best
performance possible. This mode is 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 20 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. MEDSAVE and MAXSAVE are the
same as MINSAVE
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 20 ms of delay from idle to RF on when initiating an RF
operation. (There is no known disadvantage to using SLEEP mode rather than any of
the M**SAVE modes, since their wake-up times are nearly identical.)
Note
See additional latency specifications under Event Response Times.