A DIVISION OF TRIMBLE 875-0077-01 RevA ThingMagic Nano Design Guide For ThingMagic Nano with Firmware Ver. 1.3.
A DIVISION OF TRIMBLE 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.
A DIVISION OF TRIMBLE Revision Table Date Version Description 3/2015 01 Draft 1 First Draft for early-access release 4/2015 01 REV A First Release 3
A DIVISION OF TRIMBLE 4
Communication Regulation Information A DIVISION OF TRIMBLE Communication Regulation Information ! C A U T I O N ! ! Please contact ThingMagic support - support@thingmagic.com - before beginning the process of getting regulatory approval for a finished product using the ThingMagic Nano.
ThingMagic Nano Regulatory Information A DIVISION OF TRIMBLE W A R N I N G ! Operation of the ThingMagic Nano 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: 1.
ThingMagic Nano Regulatory Information A DIVISION OF TRIMBLE 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: QV5MERCURY6EN” or “Contains FCC ID: QV5MERCURY6EN.
ThingMagic Nano Regulatory Information A DIVISION OF TRIMBLE End Product Labeling The final end product must be labeled in a visible area with the following: “Contains ThingMagic Inc.
ThingMagic Nano Regulatory Information A DIVISION OF TRIMBLE 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.
ThingMagic Nano Regulatory Information A DIVISION OF TRIMBLE 10
A DIVISION OF TRIMBLE Contents Communication Regulation Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 ThingMagic Nano Regulatory Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Federal Communication Commission Interference Statement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Industry Canada . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A DIVISION OF TRIMBLE Receiver Adjacent Channel Rejection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Environmental Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Thermal Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Thermal Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A DIVISION OF TRIMBLE Frequency Hop Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Protocol Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 ISO 18000-6C (Gen2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Gen2 Protocol Configuration Options . . . . . . . . . . . . .
A DIVISION OF TRIMBLE FAULT_FLASH_WRITE_TO_NON_ERASED_AREA – 304h . . . . . . . . . . . . . . . . . . . . . . . . . 91 FAULT_FLASH_WRITE_TO_ILLEGAL_SECTOR – 305h . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 FAULT_FLASH_VERIFY_FAILED – 306h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Protocol Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A DIVISION OF TRIMBLE System Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 FAULT_SYSTEM_UNKNOWN_ERROR – 7F00h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 FAULT_TM_ASSERT_FAILED – 7F01h. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Appendix B: Getting Started - Dev Kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A DIVISION OF TRIMBLE 16 Contents
A DIVISION OF TRIMBLE Introduction The ThingMagic® Nano® embedded module is an RFID engine that you can integrate with other systems to create RFID-enabled products. Applications to control the ThingMagic Nano modules and derivative products can be written using the high level MercuryAPI. The MercuryAPI supports Java, “.NET” and C programming environments.
Specifications Summary A DIVISION OF TRIMBLE Specifications Summary The table below summarizes the specifications of the ThingMagic Nano module. Many of these specifications are discussed in detail in the Hardware Overview chapter. Physical 22 mm L x 26 mm W x 3.0 mm H Dimensions (.866 in L x 1.024 in W x 0.
Specifications Summary A DIVISION OF TRIMBLE Pre-configured for the following regions: ඵ FCC (NA, SA) 917.4-927.2 MHz ඵ ETSI (EU) 865.6-867.6 MHz ඵ TRAI (India) 865-867 MHz Regulatory ඵ KCC (Korea) 917-923.5 MHz ඵ MIC (Japan) 916.8 – 923.4 MHz ඵ ACMA (Australia) 920-926 MHz ඵ SRRC-MII (P.R.China) 920.1-924.
Specifications Summary A DIVISION OF TRIMBLE DC Voltage: 3.3 to 5.5 V for +25 dBm out 3.7 to 5.5 V for +27 dBm out DC Power Nominal DC power consumption when reading: Required 3.6 W@ 5 VDC for +27 dBm out 3.3 W@ 5 VDC for +25 dBm out 1.5 W@ 5 VDC for 0 dBm out ඵ 0.84 W in ready mode Idle Power ඵ 0.015 W in sleep mode Consumption ඵ 0.00025 W in shutdown mode Environment ඵ FCC 47 CFR Ch. 1 Part 15 Certification ඵ Industrie Canada RSS-21 0 ඵ ETSI EN 302 208 v1.4.1 Operating Temp.
A DIVISION OF TRIMBLE Hardware Overview The following section provides detailed specifications of the ThingMagic Nano hardware including: Hardware Interfaces DC Power Requirements RF Characteristics Environmental Specifications Authorized Antennas Physical Dimensions Tape-and-Reel Dimensions Hardware Overview 21
Hardware Interfaces A DIVISION OF TRIMBLE Hardware Interfaces Module Pin-out Connections are made to the module using 41 edge pads (“vias”) that allow the module to be surface mounted to a main board. Here is a bottom view of the module, showing the numerical interfaces of the module: The sections that follow explain in detail how these connections are used. Antenna Connections The ThingMagic Nano supports one monostatic bidirectional RF antenna through edge vias.
Hardware Interfaces A DIVISION OF TRIMBLE Antenna Requirements The performance of the ThingMagic Nano is affected by antenna quality. Antennas that provide good 50 ohm match at the operating frequency band perform best. Specified performance is achieved with antennas providing 17 dB return loss (VSWR of 1.33) or better across the operating band. Damage to the module will not occur for any return loss of 1 dB or greater.
Hardware Interfaces A DIVISION OF TRIMBLE Digital/Power Interfaces The edge via connections provides power, serial communications signals, an enable control, and access to the GPIO lines to the ThingMagic Nano module.
Hardware Interfaces A DIVISION OF TRIMBLE ThingMagic Nano Digital Connector Signal Definition Edge Via Pin # Signal Signal Direction (In/Out of ThingMagic Nano) Notes 1-9, 18-19 GND Signal Return Must connect all GND pins to ground as they also serve to remove heat from the module 10 Vout DC Power Output 3.4V DC output. Maximum load 5 mA. Turns off when ENABLE is pulled low. Leave unconnected if not used.
Hardware Interfaces A DIVISION OF TRIMBLE The following table gives the Voltage and Current limits for all communication and control interfaces: Specification Limits Input Low-level Voltage 1.0 V max to indicate low state; no lower than 0.3 V below ground to prevent damage Input High-level Voltage 1.9 V min to indicate high state; 3.7 V max when module is powered up, no more than 0.3 V higher than Vout when module is turned off to prevent damage. Output Low-level Voltage 0.3 V typ, 0.
Hardware Interfaces A DIVISION OF TRIMBLE TTL Level UART Interface A level converter is 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 connected host processor’s receiver must have the capability to receive up to 256 bytes of data at a time without overflowing.
Hardware Interfaces A DIVISION OF TRIMBLE 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.
DC Power Requirements A DIVISION OF TRIMBLE DC Power Requirements The module is specified to operate with DC input levels of between 3.3 and 5.5 V. All specifications are maintained as long as the total input current is below 1 A. At 1 A, the internal Voltage regulator’s protection circuit allows no more current to be taken in. This 1A current limit will be reached slightly sooner if current is drawn out the Vout line, and the GPIO lines are supplying current to external circuits.
DC Power Requirements A DIVISION OF TRIMBLE Note 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. As shown in the chart, the current draw when the RF output level is set to +27 dBm reaches the limit of 1A when the DC input voltage is below 3.7 V. Below the 3.7 VDC input level, the RF level will no longer reach 27 dBm, although no error message will be returned.
DC Power Requirements A DIVISION OF TRIMBLE below shows the impact of the input DC Voltage on the RF output level for +25 dBm and +27 dBm RF power levels. The power drawn by the module is fairly constant, rising slightly as the DC Input Voltage is lowered.
DC Power Requirements A DIVISION OF TRIMBLE decrease, but this is because the RF output level is no longer reflecting the desired setting. This chart shows these dependencies: Note: Power consumption is defined for operation into a 17 dB return loss load (VSWR of 1.33) or better. Power consumption may increase, up to 4 W, during operation into return losses worse than 17 dB and high ambient temperatures. Power consumption will also vary based on Supported Regions in use.
DC Power Requirements A DIVISION OF TRIMBLE 3.5 to 5.5 VDC 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. Idle DC Power Consumption When not actively transmitting, the ThingMagic Nano module falls back into one of 3 idle states, called “power modes”.
RF Characteristics A DIVISION OF TRIMBLE RF Characteristics RF Output Power The output power is may be configured to a separate value for read and write operations (for many tags, more power is required to write to read). The range of values is from 0 dBm to +27 dBm, in 0.01 dB increments. (For example, 27 dBm will be configured as “2700” in units of centi-dBm.) The modules are calibrated when they are manufactured in 0.
RF Characteristics A DIVISION OF TRIMBLE discussed in the RF Power Output Impact on DC Input Current and Power section. The output accuracy over temperature is typically +/1 0.75 dBm, with most variation occurring at lower transmit output power levels.
RF Characteristics A DIVISION OF TRIMBLE Receive Sensitivity The receiver sensitivity is influenced by both user-defined settings and by external environmental factors. These factors are: Transmit Level Gen2 “M” setting Region of Operation Receive sensitivity is strongly influenced by the amount of interference caused by the reader’s own transmit signal. This interference can be reduced by reducing the transmit level.
RF Characteristics A DIVISION OF TRIMBLE subsets of that region adopted by countries around the world (917 to 928 MHz). The following table gives the sensitivity for these factors for a transmit output level of +27 dBm. The following table shows the impact of “M” value and frequency range on the sensitivity.
Environmental Specifications A DIVISION OF TRIMBLE Environmental Specifications Thermal Considerations The module will operate within its stated specifications over a temperature range o f-20 to +60 degrees C, measured at the ground plan that the ThingMagic Nano module is soldered to. It may be safely stored in temperatures ranging from -40 degrees C to +85 degrees C.
Environmental Specifications A DIVISION OF TRIMBLE Electro-Static Discharge (ESD) Specification IEC-61000-4-2 and MIL-883 3015.7 discharges direct to operational antenna port tolerates max 1 KV pulse. It will tolerate a 4 kV air discharge on the I/O and power lines. It is recommended that protective diodes be placed on the I/O lines as shown in the carrier board schematic diagram (see Hardware Integration). Note Survival level varies with antenna return loss and antenna characteristics.
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 8.15¬dBiL. Antennas not included in this list or having a gain greater than 8.15 dBiL¬are strictly prohibited for use with this device without regulatory approval. The required antenna impedance is 50 ohms.
Authorized Antennas A DIVISION OF TRIMBLE band and out of band characteristics (consult specification sheet for cutoff frequencies). If the antenna is of a different type or higher gain than those listed in the module’s FCC filing, see ThingMagic Nano Authorized Antennas, a class II permissive change must be requested from the FCC. Contact us at support@thingmagic.com and we can help you though this process. A host using a module component that has a modular grant can: 1.
Physical Dimensions A DIVISION OF TRIMBLE Physical Dimensions The dimensions of the ThingMagic Nano module are provided in the following diagram and table: Attribute Width Length Height (includes PCB, shield, mask and labels) Mass 42 Value 22 +/-0.2 mm 26 +/-0.2 mm 3.0 maximum 3.
Physical Dimensions A DIVISION OF TRIMBLE Tape-and-Reel Dimensions Hardware Overview 43
70 :$1* -6 32/<67<5(1( ,9 176 ; 1DQR $R UG $QJOH VW $QJOH 6(&7,21 ; ; 352326(' (0%266(' &$55,(5 7$3( ',0(16,216 6&$/( *(1(5$/ 72/(5$1&( 3 , 7+,6 '5$:,1* &217$,16 ,1)250$7,21 7+$7 ,6 35235,(7$5< 72 & 3$.
Physical Dimensions A DIVISION OF TRIMBLE The Nano is delivered in a tape-and-reel package. The reel measures 13 inches by 4 inches.
SMT Reflow Profile A DIVISION OF TRIMBLE SMT Reflow Profile Short profiles are recommended for reflow soldering processes. Peak zone temperature should be adjusted high enough to ensure proper wetting and optimized forming of solder joints. Generally speaking, unnecessary long exposure and exposure to more than 245C should be avoided. To not overstress the assembly, the complete reflow profile should be as short as possible.
A DIVISION OF TRIMBLE Hardware Integration The ThingMagic® Nano® embedded module is an RFID engine that you can integrate with other systems to create RFID-enabled products. This chapter discusses topics relating to this, including requirements for a host board design and characteristics of the Nano Carrier Board that ThingMagic offers for use in Development Kits and for applications where a module with standard connectors is required.
Host Board Design A DIVISION OF TRIMBLE Host Board Design Landing Pads The position of each of the pads is given in the following table. The dimensioning origin is at the center of the module edge that includes the RF pad. The tolerances of these positions should be maintained to within +/-0.2mm. All pads are 2.0 mm long by 0.75 mm wide.
Host Board Design A DIVISION OF TRIMBLE Pin Number 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 Hardware Integration X Position (mm) -10.5 -10.5 -10.5 -10.5 -10.5 -10.5 -10.5 -10.5 -10.5 -10.5 -10.5 -10.5 -10.5 -10.5 10.5 10.5 10.5 10.5 10.5 10.5 10.5 10.5 10.5 10.5 10.5 10.5 10.5 10.5 10.5 10.5 10.5 10.5 2.5 1.25 0 -1.25 7.5 6.25 5 Y Position (mm) -2 -3.25 -4.5 -5.75 -7 -8.25 -9.5 -10.75 -12 -13.25 -14.5 -15.75 -17 -18.25 -19.5 -20.
Host Board Design A DIVISION OF TRIMBLE 40 41 3.75 2.5 -0.5 -0.5 Peripheral pads as shown on the footprint are what the ThingMagic Nano module will mount to. These peripheral pads are at a pitch of 1.25 mm. The intention for the ThingMagic Nano module is to use routed-through via connections with 0.7 mm diameter edge vias. The pads of the ThingMagic Nano module underside should align with the copper pads of the footprint, with a pad exposure extending outside the M6e-Nano edge be a nominal 0.5 mm. A 0.
Host Board Design A DIVISION OF TRIMBLE module pad positional tolerance shall be not more than +/-0.2 mm to support contact alignment during fixturing. The circuitry feeding the RF pad of the M6e-Nano shall be optimized for connecting to a coplanar wave guide with ground plane beneath. The CPW-G will have dimensions as shown in the following diagram. The area beneath the module should be kept clear of traces and copper.
ThingMagic Nano Carrier Board A DIVISION OF TRIMBLE ThingMagic Nano Carrier Board ThingMagic has created a Carrier Board for the ThingMagic Nano module, as an example of a host board for this module and to make it compatible with the standard Development Kit main board. It has the size and dimensions of the M6e module (69 mm x 43 mm), and uses the same connector for power and control (Molex 53261-1571 - 1.
ThingMagic Nano Carrier Board A DIVISION OF TRIMBLE 1 amp per pin rating. which mates with Molex housing p/n 51021-1500 with crimps p/n 63811-0300). The pin definitions are the same as for the M6e, for the functions that are supported by both, with one exception: The “SHUTDOWN” line of the M6e has reversed polarity and is the “ENABLE” line in the ThingMagic Nano. Pin Number Signal Signal Direction with respect to Carrier Board Notes 1,2 GND Power and Signal Return Must connect both pins to ground.
ThingMagic Nano Carrier Board A DIVISION OF TRIMBLE W A R N I N G ! The buffer on the Nano Carrier Board is driven by the Vout pin on the ThingMagic Nano. Current supplied to this buffer will count toward the 1A total current that the ThingMagic Nano draws from its power source.
ThingMagic Nano Carrier Board A DIVISION OF TRIMBLE The following page provides a schematic diagram for the Nano Carrier Board.Contact support@thingmagic.com to obtain this in a PDF file.
ThingMagic Nano Carrier Board A DIVISION OF TRIMBLE 56 Hardware Integration
A B M6e Pin Pin Pin Pin Pin Pin Pin Pin Pin Pin Pin Pin Pin Pin Pin Interface Pinout 1 GND 2 GND 3 +5V 4 +5V 5 GPIO1 6 GPIO2 7 GPIO3 8 GPIO4 9 RS-232_RX_TTL 10 RS-232_TX_TTL 11 USB_DM 12 USB_DP 13 USB_5VSENSE 14 SHUTDOWN 15 RESET 53261-1571 M1 M2 J6 VIN 7 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 5 R1 DNP 4 MH7 MH4 MH3 MH8 MH2 D2 TVS-4 Optional ESD Protection TVS-4 D3 DNP J5 DNP J3 1 2 3 1 2 3 SPI_MOSI__USBDM SPI_CLK__USBDP MH1 TVS-4 D1 GPIO4__VSENSE R2 DNP Jump Pin 1-2 for USB
ThingMagic Nano Carrier Board A DIVISION OF TRIMBLE Carrier Board Heat Sinking The ThingMagic Nano can run at full RF power at room temperature on stand-offs in the Dev Kit. If you wish to test the ThingMagic Nano under extreme temperature conditions, you may want to mount it on the heat spreader that is supplied with the Micro modules for the xPRESS Sensor Hub. Make sure it is assembled as shown in these pictures so no live signals are shorted to ground.
A DIVISION OF TRIMBLE Firmware Overview The following section provides detailed description of the ThingMagic Nano firmware components, including: Boot Loader Application Firmware Custom On-Reader Applications Firmware Overview 59
Boot Loader A DIVISION OF TRIMBLE 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. Note Unlike previous ThingMagic modules (M4e and M5e) the ThingMagic Nano bootloader should effectively be invisible to the user.
Application Firmware 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 ThingMagic Nano Applications to control the ThingMagic Nano module and derivative products are written using the high level MercuryAPI. The MercuryAPI supports Java, “.
Custom On-Reader Applications A DIVISION OF TRIMBLE Custom On-Reader Applications The ThingMagic Nano 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.
A DIVISION OF TRIMBLE Communication Protocol The following section provides an overview of the low level serial communications protocol used by the ThingMagic Nano.
Serial Communication Protocol A DIVISION OF TRIMBLE Serial Communication Protocol The serial communication between a computer (host) and the ThingMagic Nano 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.
Serial Communication Protocol 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.
User Programming Interface A DIVISION OF TRIMBLE User Programming Interface The ThingMagic Nano does not support programming to the serial protocol directly. All user interaction with the ThingMagic Nano 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.
A DIVISION OF TRIMBLE Functionality of the ThingMagic Nano The following section provides detailed descriptions of the ThingMagic Nano features and functionality that are supported through the use of the MercuryAPI.
Regulatory Support A DIVISION OF TRIMBLE Regulatory Support ! C A U T I O N ! ! Please contact ThingMagic support - support@thingmagic.com - before beginning the process of getting regulatory approval for a finished product using the ThingMagic Nano. Supported Regions The ThingMagic Nano 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.
Regulatory Support A DIVISION OF TRIMBLE Korea (KR2) KCC (2009) The first frequency channel (917,300kHz) of the KR2 region is derated to +22dBm to meet the regulatory requirements. All other channels operate up to +27dBm. In the worst case scenario, each time the derated channel is used it will stay on that channel for 400ms.
Regulatory Support A DIVISION OF TRIMBLE 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.
Regulatory Support A DIVISION OF TRIMBLE Regional Frequency Specifications Region Frequency Quantization (kHz) Minimum Frequency (kHz) Maximum Frequency (kHz) Number of Channels in Default Hop Table NA2 (Reduced FCC) 200 917,400 kHz 927,200 kHz 50 EU3 (ETSI) 100 865,600 kHz 867,600 kHz 4 IN (India) 100 865,000 kHz 867,000 kHz 5 KR2 (Korea) 100 917,000 kHz 923,500 kHz 6 PRC 125 920,125 kHz 924,875 kHz 16 AU (Australia) 250 920,000 kHz 926,000 kHz 10 NZ (New Zealand) 250
Regulatory Support A DIVISION OF TRIMBLE Frequencies are used in the order of entries in the table, so if a random order is required, the frequencies must be pre-randomized before entering. If necessary for a region, the hop table are randomized to create a pseudo-random sequence of frequencies to use. This is done automatically using the default hop tables provided for each region.
Protocol Support A DIVISION OF TRIMBLE Protocol Support Unlike the M6e and Micro modules, the ThingMagic Nano does not have the ability to support tag protocols other then ISO 18000-6B (gen2). Future support for ISO 18000-63 (Gen2V2) is likely, however. ISO 18000-6C (Gen2) Gen2 Protocol Configuration Options The ThingMagic Nano supports limited ISO-18000-6C profiles, with only the Backscatter Link Frequency (BLF) and “M” value as configurable options.
Protocol Support A DIVISION OF TRIMBLE Unsupported Gen2 Functionality The ThingMagic Nano module firmware can perform some Gen2 functions as a standalone command, but cannot do so as part of an embedded TagOps command: Here is the list of supported standard Gen2 functions: As Embedded TagOPs As Stand-alone TagOPs Gen2 Read Data Yes Yes Gen2 Write Tag No Yes Gen2 Write Data No Yes Gen2 Lock Tag No Yes Gen2 Kill Tag No Yes Gen2 Block Write No Yes Gen2 Block Erase No Yes Gen2 Block Per
Protocol Support A DIVISION OF TRIMBLE NXP G2X and G2i Change EAS and Alarm NXP G2X and G2i Calibrate NXP G2i ChangeConfig Monza 4QT ReadWrite AMS/IDS SL900A Sensor Tag Commands Functionality of the ThingMagic Nano 75
Unsupported Features A DIVISION OF TRIMBLE Unsupported Features Unlike other ThingMagic modules, the ThingMagic Nano module currently does not support gathering reader statistics independent of the meta data that can be gathered with tag reads. The statistics not supported include: RF On-time Noise Floor, Noise Floor with Transmit On Frequency Temperature Antenna Ports Current Protocol The ThingMagic Nano module currently does not support Save and Restore of settings.
Antenna Port A DIVISION OF TRIMBLE Antenna Port The ThingMagic Nano has one monostatic antenna port. This port is capable of both transmitting and receiving. The module also supports Using a Multiplexer, allowing up to 8 total logical antenna ports, controlled using two GPIO lines. Note The ThingMagic Nano does not support bistatic (separate transmit and receive port) operation.
Antenna Port A DIVISION OF TRIMBLE GPIO 1 & 2 Used for Antenna Switching GPIO Output 1 State GPIO Output 2 State Logical Antenna Setting Low Low 1 Low High 2 High Low 3 High High 4 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.
Antenna Port A DIVISION OF TRIMBLE Port Power and Settling Time The ThingMagic Nano allows the power and settling time for each logical antenna to be set using the reader configuration parameters /reader/radio/portReadPowerList and /reader/antenna/settlingTimeList, respectively. The order the antennas settings are defined does not affect search order. Note Settling time is the time between the control lines switching to the next antenna setting and RF turning on for operations on that port.
Tag Handling A DIVISION OF TRIMBLE Tag Handling When the ThingMagic Nano performs inventory operations (MercuryAPI Read commands) data is stored in a Tag Buffer until retrieved by the client application, or streamed directly to the client if operating in Tag Streaming/Continuous Reading mode. Tag Buffer The ThingMagic Nano 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 48 96-bit EPC tags in the Tag Buffer at a time.
Tag Handling A DIVISION OF TRIMBLE Note 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.
Tag Read Meta Data A DIVISION OF TRIMBLE Tag Read Meta Data In addition to the tag EPC ID resulting from ThingMagic Nano 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: Meta Data Field Description Antenna ID The antenna on with the tag was read.
Power Management A DIVISION OF TRIMBLE Power Management The ThingMagic Nano 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 ThingMagic Nano 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 ThingMagic Nano is idle.
Performance Characteristics A DIVISION OF TRIMBLE Performance Characteristics Event Response Times The following table provides some metrics on how long common ThingMagic Nano 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.
Common Error Messages A DIVISION OF TRIMBLE Appendix A: Error Messages This appendix discusses error messages that you might see in API transport logs or passed up by the API to the host program. Categories of messages include: Common Error Messages Bootloader Faults Flash Faults Protocol Faults Analog Hardware Abstraction Layer Faults Tag ID Buffer Faults System Errors Common Error Messages The following table lists the common faults discussed in this section.
Common Error Messages A DIVISION OF TRIMBLE 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. Solution Check the following: Make sure the command is supported in the currently running program.
Common Error Messages A DIVISION OF TRIMBLE 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. 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.
Common Error Messages A DIVISION OF TRIMBLE Solution Check the HW specifications for the supported powers and insure that level is not exceeded. The ThingMagic Nano supports powers between 5 and 30 dBm. FAULT_UNIMPLEMENTED_FEATURE - (109h) Cause Attempting to invoke a command not supported on this firmware or hardware. Solution Check the command being invoked against the documentation.
Bootloader Faults A DIVISION OF TRIMBLE 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.
Flash Faults A DIVISION OF TRIMBLE Flash Faults The following table lists the common faults discussed in this section.
Flash Faults A DIVISION OF TRIMBLE 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 test case 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.
Flash Faults A DIVISION OF TRIMBLE Solution When this occurs make note of the operations you were executing, save FULL error response and send a test case 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.
Protocol Faults A DIVISION OF TRIMBLE Protocol Faults The following table lists the common faults discussed in this section.
Protocol Faults A DIVISION OF TRIMBLE 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.
Protocol Faults A DIVISION OF TRIMBLE 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.
Protocol Faults A DIVISION OF TRIMBLE 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.
Protocol Faults A DIVISION OF TRIMBLE 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.
Protocol Faults A DIVISION OF TRIMBLE 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.
Protocol Faults A DIVISION OF TRIMBLE 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.
Protocol Faults A DIVISION OF TRIMBLE 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 ThingMagic Nano when no more error information is available about why the operation failed.
Analog Hardware Abstraction Layer Faults A DIVISION OF TRIMBLE 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.
Analog Hardware Abstraction Layer Faults A DIVISION OF TRIMBLE Solution Connect a detectable antenna. (Antenna must have some DC resistance.) (Does not apply to Micro or ThingMagic Nano as they do not detect antennas.) 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.
Analog Hardware Abstraction Layer Faults A DIVISION OF TRIMBLE Solution Use the correct antenna setting or change the reader configuration.
Tag ID Buffer Faults A DIVISION OF TRIMBLE Tag ID Buffer Faults The following table lists the common faults discussed in this section. Fault Message Code FAULT_TAG_ID_BUFFER_NOT_ENOUGH_TAGS_AVAILABLE – 600h 600h FAULT_TAG_ID_BUFFER_FULL – 601h 601h FAULT_TAG_ID_BUFFER_REPEATED_TAG_ID – 602h 602h FAULT_TAG_ID_BUFFER_NUM_TAG_TOO_LARGE – 603h 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.
Tag ID Buffer Faults A DIVISION OF TRIMBLE 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 test case 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.
System Errors A DIVISION OF TRIMBLE System Errors FAULT_SYSTEM_UNKNOWN_ERROR – 7F00h Cause The error is internal. Solution Send a test case reproducing the behavior to support@thingmagic.com. FAULT_TM_ASSERT_FAILED – 7F01h Cause 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 test case reproducing the behavior to support@thingmagic.
A DIVISION OF TRIMBLE Appendix B: Getting Started - Dev Kit This appendix provides instructions on the use of the ThingMagic Nano Development Kit: Dev Kit Hardware Demo Application Notice on Restricted Use of the Dev Kit Dev Kit Hardware Included Components With the dev kit, you will receive the following components: The ThingMagic Nano module soldered onto carrier board Power/interface developers board One USB cable One antenna One coax cable One 9V power supply International power
Dev Kit Hardware A DIVISION OF TRIMBLE 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.
Dev Kit Hardware A DIVISION OF TRIMBLE 1. Connect the USB cable (use only the black connector) from a PC to the developer’s kit. There are two Dev Kit USB Interfaces options. 2. Plug the power supply into the Dev Kit’s DC power input connector. 3. The LED next to the DC input jack, labeled DS1, should light up. If it doesn’t light up check jumper J17 to make sure the jumper is connecting pins 2 and 3 4.
Dev Kit Hardware A DIVISION OF TRIMBLE Dev Kit USB Interfaces USB/RS232 The USB interface (connector labeled USB/RS232) closest to the power plug is to the RS232 interface of the ThingMagic Nano 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. The ThingMagic Nano does not support a native USB port, so this port on the Dev Kit is inoperable.
Dev Kit Hardware A DIVISION OF TRIMBLE Dev kit Jumpers J8 Jumpers to connect ThingMagic Nano I/O lines to dev kit. (4)For added safety, you should remove all 3 jumpers for USB connections and the AUTO_BT connection to the module. These lines are not supported, but are connected to the ThingMagic Nano module for test purposes, so should be left unconnected for all applications. J19 The jumper at J19 that connects Shutdown to ground must be REMOVED.
Dev Kit Hardware A DIVISION OF TRIMBLE J10, J11 Jump pins OUT to GPIO# to connect ThingMagic Nano GPIO lines to output LEDs. Jump pins IN to GPIO# to connect ThingMagic Nano GPIO to corresponding input switches SW[3,4]GPIO#. Make sure GPIO lines are correspondingly configured as input or outputs (see Configuring GPIO Settings). J13, J15 Not used. J14 Can be used to connect GPIO lines to external circuits. If used jumpers should be removed from J10, J11.
Demo Application A DIVISION OF TRIMBLE Demo Application A demo application which supports multi-protocol reading and writing is provided in the MercuryAPI SDK package. The executable for this example is included in the MercuryAPI SDK package under /cs/samples/exe/Universal-Reader-Assistant.exe and is also available for direct download from rfid.thingmagic.com/dev kit. Note: The Universal Reader Assistant included in the MercuryAPI SDK maybe an older revision than the one available for standalone download.
Notice on Restricted Use of the Dev Kit A DIVISION OF TRIMBLE Notice on Restricted Use of the Dev Kit The Mercury6e Developers Kit (Dev Kit) 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.
A DIVISION OF TRIMBLE Appendix C: Environmental Considerations This Appendix details environmental factors that should be considered relating to reader performance and survivability.
ElectroStatic Discharge (ESD) Considerations A DIVISION OF TRIMBLE ElectroStatic Discharge (ESD) Considerations W A R N I N G ! The ThingMagic Nano antenna port 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 ThingMagic Nano reader antenna or communication ports.
ElectroStatic Discharge (ESD) Considerations A DIVISION OF TRIMBLE 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 ThingMagic Nano has been successfully deployed and operates happily. For these, there is no failure issue, ESD or otherwise.
ElectroStatic Discharge (ESD) Considerations A DIVISION OF TRIMBLE 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 ThingMagic Nano, ThingMagic Nano reader housing, and antenna ground connection are all grounded to a common low impedance ground.
ElectroStatic Discharge (ESD) Considerations A DIVISION OF TRIMBLE charge leakage, and provides a high pass characteristic that attenuates discharge events. (This also makes the antenna compatible with the ThingMagic Nano antenna detect methods.) Install a Minicircuits SHP600+ high pass filter in the cable run at the ThingMagic Nano (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.
Variables Affecting Performance A DIVISION OF TRIMBLE 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 A DIVISION OF TRIMBLE Tag Orientation: Reader performance is affected by the orientation of the tag in 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.
Variables Affecting Performance A DIVISION OF TRIMBLE 122 Appendix C: Environmental Considerations
