M6E-NANO-DEVKIT

A DIVISION OF TRIMBLE 875-0077-01 Rev E ThingMagic Nano Design Guide For ThingMagic Nano with Firmware Ver. 1.3.2 and later 1 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. Any reproduction of technical data or portions thereof marked with this legend must also reproduce the markings. Any person, other than the U.S. Government, who has been provided access to such data must promptly notify ThingMagic. ThingMagic, Mercury, Reads Any Tag, and the ThingMagic logo are trademarks or registered trademarks of ThingMagic, A Division of Trimble. Other product names mentioned herein may be trademarks or registered trademarks of Trimble or other companies. ©2015 ThingMagic – a division of Trimble Navigation Limited. ThingMagic and The Engine in RFID are registered trademarks of Trimble Navigation Limited. Other marks may be protected by their respective owners. All Rights Reserved.d ThingMagic, A Division of Trimble 1 Merrill Street Woburn, MA 01801 01 Revision E April 2016 2 A DIVISION OF TRIMBLE Revision Table Date Version Description 3/2015 01 Draft 1 Partial Draft for early-access release 4/2015 01 REV A First Release for prototype units with 1.3.1 firmware 4/2015 01 Rev B Second release for GA units with version 1.3.2 firmware Receive sensitivity values updated (RF Characteristics) Long-term exposure caution updated (ThingMagic Nano Regulatory Information) Thermal limits explained more fully (ThingMagic Nano Carrier Board) Minor Editorial Changes Minor changes following review by Engineering 6/2015 01 Rev C In the “Hardware Overview” section, the table of pin fumctions erroneously listed pin 39 as both a signal and a ground and omitted ground pin 37. This has been corrected. The “Host Board Design” section of the “Hardware Integration chapter changed. The “landing pads” outline changed to show heat sink areas. The table that indicated pad sizes and locations incorrectly has been removed and replaced by a reference to the carrier board design files, w hich provide the information in a much more convenient form. 9/2015 01 Rev D Ambiguity about whether RX and TX pins are inputs or outputs cleared up. 4/2016 01 Rev E Content added to reinforce that all GPI lines and the RX input line must be low when the module boots up and low when the module shuts down. 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 Federal Communication Commission Interference Statement This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one of the following measures: Reorient or relocate the receiving antenna. Increase the separation between the equipment and receiver. Connect the equipment into an outlet on a circuit different from that to which the receiver is connected. Consult the dealer or an experienced radio/TV technician for help. This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) This device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation. FCC Caution: Any changes or modifications not expressly approved by the party responsible for compliance could void the user's authority to operate this equipment. 5 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. To comply with FCCʼs RF radiation exposure requirements, the antenna(s) used for this transmitter must be installed such that a minimum separation distance of 21cm is maintained between the radiator (antenna) & userʼs/nearby peopleʼs body at all times and must not be co-located or operating in conjunction with any other antenna or transmitter. 2. The transmitter module must not be co-located with any other antenna or transmitter. As long as the two conditions above are met, further transmitter testing will not be required. However, the OEM integrator is still responsible for testing their end-product for any additional compliance requirements required with this module installed (for example, digital device emissions, PC peripheral requirements, etc.). Note In the event that these conditions can not be met (for certain configurations or co-location with another transmitter), then the FCC authorization is no longer considered valid and the FCC ID can not be used on the final product. In these circumstances, the OEM integrator will be responsible for reevaluating the end product (including the transmitter) and obtaining a separate FCC authorization. The OEM integrator has to be aware not to provide information to the end user regarding how to install or remove this RF module in the user manual of the end product. User Manual Requirement The user manual for the end product must include the following information in a prominent location; “To comply with FCC’s RF radiation exposure requirements, the antenna(s) used for this transmitter must be installed such that a minimum separation distance of 21 cm is maintained between the radiator (antenna) & user’s/nearby people’s body at all times and must not be co-located or operating in conjunction with any other antenna or transmitter.” AND “The transmitting portion of this device carries with it the following two warnings: 6 ThingMagic Nano Regulatory Information A DIVISION OF TRIMBLE “This device complies with Part 15....” 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.” Industry Canada Under Industry Canada regulations, this radio transmitter may only operate using an antenna of a type and maximum (or lesser) gain approved for the transmitter by Industry Canada. To reduce potential radio interference to other users, the antenna type and its gain should be so chosen that the equivalent isotropic radiated power (e.i.r.p.) is not more than that necessary for successful communication. This radio transmitter (identify the device by certification number, or model number if Category II) has been approved by Industry Canada to operate with the antenna types listed below with the maximum permissible gain and required antenna impedance for each antenna type indicated. Antenna types not included in this list, having a gain greater than the maximum gain indicated for that type, are strictly prohibited for use with this device Operation is subject to the following two conditions: (1) this device may not cause interference, and (2) this device must accept any interference, including interference that may cause undesired operation of the device. To reduce potential radio interference to other users, the antenna type and its gain should be so chosen that the equivalent isotropic ally radiated power (e.i.r.p.) is not more than that permitted for successful communication. This device has been designed to operate with the antennas listed in Authorized Antennas table. Antennas not included in these lists are strictly prohibited for use with this device. To comply with IC RF exposure limits for general population/uncontrolled exposure, the antenna(s) used for this transmitter must be installed to provide a separation distance of 7 ThingMagic Nano Regulatory Information A DIVISION OF TRIMBLE at least 21 cm from all persons and must not be collocated or operating in conjunction with any other antenna or transmitter. End Product Labeling The final end product must be labeled in a visible area with the following: “Contains ThingMagic Inc. ThingMagic Nano (or appropriate model number youʼre filing with IC) transmitting module FCC ID: QV5MERCURY6EN (IC: 5407A-MERCURY6EN)” Industrie Canada Conformément à la réglementation d'Industrie Canada, le présent émetteur radio peut fonctionner avec une antenne d'un type et d'un gain maximal (ou inférieur) approuvé pour l'émetteur par Industrie Canada. Dans le but de réduire les risques de brouillage radioélectrique à l'intention des autres utilisateurs, il faut choisir le type d'antenne et son gain de sorte que la puissance isotrope rayonnée équivalente (p.i.r.e.) ne dépasse pas l'intensité nécessaire à l'établissement d'une communication satisfaisante. Le présent émetteur radio (identifier le dispositif par son numéro de certification ou son numéro de modèle s'il fait partie du matériel de catégorie I) a été approuvé par Industrie Canada pour fonctionner avec les types d'antenne énumérés ci-dessous et ayant un gain admissible maximal et l'impédance requise pour chaque type d'antenne. Les types d'antenne non inclus dans cette liste, ou dont le gain est supérieur au gain maximal indiqué, sont strictement interdits pour l'exploitation de l'émetteur Le fonctionnement de lʼ appareil est soumis aux deux conditions suivantes: 1. Cet appareil ne doit pas perturber les communications radio, et 2. cet appareil doit supporter toute perturbation, y compris les perturbations qui pourraient provoquer son dysfonctionnement. Pour réduire le risque d'interférence aux autres utilisateurs, le type d'antenne et son gain doivent être choisis de façon que la puissance isotrope rayonnée équivalente (PIRE) ne dépasse pas celle nécessaire pour une communication réussie. Lʼ appareil a été conçu pour fonctionner avec les antennes énumérés dans les tables Antennes Autorisées (Authorized Antennas). Il est strictement interdit de lʼ utiliser lʼ appareil avec des antennes qui ne sont pas inclus dans ces listes. Au but de conformer aux limites d'exposition RF pour la population générale (exposition non-contrôlée), les antennes utilisés doivent être installés à une distance d'au moins 25 8 ThingMagic Nano Regulatory Information A DIVISION OF TRIMBLE cm de toute personne et ne doivent pas être installé en proximité ou utilisé en conjonction avec un autre antenne ou transmetteur. Marquage sur l’ étiquette du produit complet dans un endroit visible: "Contient ThingMagic transmetteur, FCC ID: QV5MERCURY6EN (IC:5407A-MERCURY6EN)" 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. 9 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Industrie Canada . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Authorized Antennas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Specifications Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Hardware Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Hardware Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Module Pin-out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Antenna Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Antenna Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Antenna Detection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Digital/Power Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Control Signal Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 General Purpose Input/Output (GPIO) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 ENABLE Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 DC Power Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 RF Power Output Impact on DC Input Current and Power. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Power Supply Ripple . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Idle DC Power Consumption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 RF Characteristics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 RF Output Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Receive Sensitivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Contents 11 A DIVISION OF TRIMBLE Receiver Adjacent Channel Rejection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Environmental Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Thermal Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Thermal Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Electro-Static Discharge (ESD) Specification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Shock and Vibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Authorized Antennas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 FCC Modular Certification Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Physical Dimensions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Tape-and-Reel Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 SMT Reflow Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Hardware Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Host Board Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 Landing Pads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 ThingMagic Nano Carrier Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Carrier Board Heat Sinking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Firmware Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Boot Loader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 Application Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Programming the ThingMagic Nano. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Upgrading the ThingMagic Nano . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Verifying Application Firmware Image . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 Custom On-Reader Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Communication Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Serial Communication Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Host-to-Reader Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Reader-to-Host Communication. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 CCITT CRC-16 Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 User Programming Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Functionality of the ThingMagic Nano. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 Regulatory Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Supported Regions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Frequency Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Frequency Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 12 Contents A DIVISION OF TRIMBLE Frequency Hop Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Protocol Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Gen2 (ISO 18000-6C) Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Gen2 Protocol Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Unsupported Gen2 Functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Unsupported Custom Gen2 Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Unsupported Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Antenna Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 Using a Multiplexer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 Port Power and Settling Time. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 Tag Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Tag Buffer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Tag Streaming/Continuous Reading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Tag Read Meta Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Power Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Power Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Performance Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Event Response Times . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Appendix A: Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Common Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 FAULT_MSG_WRONG_NUMBER_OF_DATA – (100h) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 FAULT_INVALID_OPCODE – (101h) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 FAULT_UNIMPLEMENTED_OPCODE – 102h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 FAULT_MSG_POWER_TOO_HIGH – 103h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 FAULT_MSG_INVALID_FREQ_RECEIVED (104h) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 FAULT_MSG_INVALID_PARAMETER_VALUE - (105h) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 FAULT_MSG_POWER_TOO_LOW - (106h) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 FAULT_UNIMPLEMENTED_FEATURE - (109h) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 FAULT_INVALID_BAUD_RATE - (10Ah) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 Bootloader Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 FAULT_BL_INVALID_IMAGE_CRC – 200h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 FAULT_BL_INVALID_APP_END_ADDR – 201h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Flash Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 FAULT_FLASH_BAD_ERASE_PASSWORD – 300h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 FAULT_FLASH_BAD_WRITE_PASSWORD – 301h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 FAULT_FLASH_UNDEFINED_ERROR – 302h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 FAULT_FLASH_ILLEGAL_SECTOR – 303h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Contents 13 A DIVISION OF TRIMBLE FAULT_FLASH_WRITE_TO_NON_ERASED_AREA – 304h . . . . . . . . . . . . . . . . . . . . . . . . . 93 FAULT_FLASH_WRITE_TO_ILLEGAL_SECTOR – 305h . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 FAULT_FLASH_VERIFY_FAILED – 306h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Protocol Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 FAULT_NO_TAGS_FOUND – (400h). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 FAULT_NO_PROTOCOL_DEFINED – 401h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 FAULT_INVALID_PROTOCOL_SPECIFIED – 402h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 FAULT_WRITE_PASSED_LOCK_FAILED – 403h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 FAULT_PROTOCOL_NO_DATA_READ – 404h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 FAULT_AFE_NOT_ON – 405h. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 FAULT_PROTOCOL_WRITE_FAILED – 406h. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 FAULT_NOT_IMPLEMENTED_FOR_THIS_PROTOCOL – 407h . . . . . . . . . . . . . . . . . . . . . . 98 FAULT_PROTOCOL_INVALID_WRITE_DATA – 408h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 FAULT_PROTOCOL_INVALID_ADDRESS – 409h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 FAULT_GENERAL_TAG_ERROR – 40Ah . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 FAULT_DATA_TOO_LARGE – 40Bh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 FAULT_PROTOCOL_INVALID_KILL_PASSWORD – 40Ch . . . . . . . . . . . . . . . . . . . . . . . . . . 99 FAULT_PROTOCOL_KILL_FAILED - 40Eh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 FAULT_PROTOCOL_BIT_DECODING_FAILED - 40Fh . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 FAULT_PROTOCOL_INVALID_EPC – 410h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 FAULT_PROTOCOL_INVALID_NUM_DATA – 411h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 FAULT_GEN2 PROTOCOL_OTHER_ERROR - 420h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 FAULT_GEN2_PROTOCOL_MEMORY_OVERRUN_BAD_PC - 423h . . . . . . . . . . . . . . . . . 101 FAULT_GEN2 PROTOCOL_MEMORY_LOCKED - 424h . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 FAULT_GEN2 PROTOCOL_INSUFFICIENT_POWER - 42Bh . . . . . . . . . . . . . . . . . . . . . . . 101 FAULT_GEN2 PROTOCOL_NON_SPECIFIC_ERROR - 42Fh . . . . . . . . . . . . . . . . . . . . . . . 102 FAULT_GEN2 PROTOCOL_UNKNOWN_ERROR - 430h. . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Analog Hardware Abstraction Layer Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 FAULT_AHAL_INVALID_FREQ – 500h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 FAULT_AHAL_CHANNEL_OCCUPIED – 501h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 FAULT_AHAL_TRANSMITTER_ON – 502h. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 FAULT_ANTENNA_NOT_CONNECTED – 503h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 FAULT_TEMPERATURE_EXCEED_LIMITS – 504h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 FAULT_POOR_RETURN_LOSS – 505h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 FAULT_AHAL_INVALID_ANTENA_CONFIG – 507h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Tag ID Buffer Faults . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 FAULT_TAG_ID_BUFFER_NOT_ENOUGH_TAGS_AVAILABLE – 600h . . . . . . . . . . . . . . . 106 FAULT_TAG_ID_BUFFER_FULL – 601h. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 FAULT_TAG_ID_BUFFER_REPEATED_TAG_ID – 602h . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 FAULT_TAG_ID_BUFFER_NUM_TAG_TOO_LARGE – 603h . . . . . . . . . . . . . . . . . . . . . . . 107 14 Contents A DIVISION OF TRIMBLE System Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 FAULT_SYSTEM_UNKNOWN_ERROR – 7F00h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 FAULT_TM_ASSERT_FAILED – 7F01h. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 Appendix B: Getting Started - Dev Kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Dev Kit Hardware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Included Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Setting up the Dev Kit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Connecting the Antenna . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Powering up and Connecting to a PC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Dev Kit USB Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 USB/RS232 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Dev kit Jumpers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Dev Kit Schematics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 Demo Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 Notice on Restricted Use of the Dev Kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 Appendix C: Environmental Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . 117 ElectroStatic Discharge (ESD) Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 ESD Damage Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 Identifying ESD as the Cause of Damaged Readers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 Common Installation Best Practices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 Raising the ESD Threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 Further ESD Protection for Reduced RF Power Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 Variables Affecting Performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 Environmental . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 Tag Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 Antenna Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Multiple Readers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Contents 15 A DIVISION OF TRIMBLE 16 Contents A DIVISION OF TRIMBLE Introduction The ThingMagic® Nano® embedded module is an RFID reader 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. The MercuryAPI Software Development Kit (SDK) contains sample applications and source code to help developers get started demonstrating and developing functionality. For more information on the MercuryAPI see the MercuryAPI Programmers Guide and the MercuryAPI SDK, available on the ThingMagic website. This document is intended for hardware designers and software developers. It describes the hardware specifications and firmware functionality of the ThingMagic Nano module and provides guidance on how to incorporate the module within a third-party host system. The document is broken down into the following sections: Hardware Overview - Detailed specifications of the ThingMagic Nano hardware. This section should be read in its entirety before designing hardware or attempting to operate the ThingMagic Nano module in hardware other than the ThingMagic Dev Kit. Hardware Integration - Describes the ideal attributes of a main board which incorporates the ThingMagic Nano module. Firmware Overview - A detailed description of the ThingMagic Nano firmware components including the bootloader and application firmware. Communication Protocol - An overview of the low level serial communications protocol used by the ThingMagic Nano. Functionality of the ThingMagic Nano - Detailed descriptions of the ThingMagic Nano features and functionality that are supported through the use of the MercuryAPI. Appendix A: Error Messages - Lists ThingMagic Nano Error Codes and provides causes and suggested solutions for when they are encountered. Appendix B: Getting Started - Dev Kit - Quick Start guide to getting connected to the ThingMagic Nano Developerʼs Kit and using the Demo Applications included with the MercuryAPI SDK. Appendix C: Environmental Considerations - Details about environmental factors that should be considered relating to reader performance and survivability. Introduction 17 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 further 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.118 in H) Tag / Transponder Protocols RFID Protocol Support EPCglobal Gen 2 (ISO 18000-6C) with nominal backscatter rate of 250 kbps RF Interface 18 Antennas Single 50 Ω connection (board-edge) RF Power Output Separate read and write levels, commandadjustable from 0 dBm to 27 dBm in 0.01 dB steps Introduction 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.9 MHz ▪ ‘Open’ (Customizable channel plan; 859-873 MHz and 915-930 MHz) Data/Control Interface Physical 41 board-edge connections providing access to RF, DC power, communication, and GPIO signals ▪ UART; 3.3V logic levels Control/Data Interfaces ▪ 9.6 to 921.6 kbps data rate ▪ Enable control GPIO Sensors and Indicators Four 3.3V bidirectional ports; API support .NET, Java, and Embedded “C” APIs Configurable as input (sensor) or output (indicator) Power Introduction 19 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. -20C to +60C (case temperature) Storage Temp. -40C to +85C Shock and Survives 1 meter drop during handling Vibration Performance Boot time ▪ Less than 150 msec for initial boot after firmware download ▪ Less than 30 msec for subsequent boots. Read/Write Performance 20 ▪ Up to 150 tags/sec to read 96-bit EPC ▪ 80 msec typical for standard write of 96-bit EPC Introduction 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 document 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. See Hardware Integration for antenna edge via locations and layout guidelines. The maximum RF power that can be delivered to a 50 ohm load from each port is 0.5 Watts, or +27 dBm (regulatory requirements permitting). 22 Hardware Overview 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. Damage may occur if antennas are disconnected during operation or if the module sees an open or short circuit at its antenna port. Antenna Detection ! C A U T I O N ! ! Like the Micro module, but unlike the M6e and M5e modules, the ThingMagic Nano does not support automatic antenna detection. When writing applications to control the ThingMagic Nano you must explicitly specify that antenna 1 is to be used. Using the MercuryAPI, this requires creation of a “SimpleReadPlan” object with the list of antennas set and that object set as the active /reader/read/plan. For more information see the MercuryAPI Programmers Guide | Level 2 API | Advanced Reading | “ReadPlan” section. Hardware Overview 23 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. See Hardware Integration for pinout details of both connections and layout guidelines 24 Hardware Overview 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. 11 ENABLE Enable/Shutdown TTL input that turns the module off and reduces its power consumption to nearly zero. Hi=Enable, Low=Shutdown module If left unconnected, module will stay in ENABLE state. 12 GPIO1 Bidirectional GPIO 13 GPIO2 Bidirectional GPIO 14 GPIO3 Bidirectional GPIO 15 GPIO4 Bidirectional GPIO Vin Power Supply Input 3.3 to 5.5VDC. Pins 16 and 17 are internally connected. Connect the DC power source to both pins to ensure sufficient current carrying capacity. 20 UART_TX Out UART Serial output, 3.3V logic 21 UART_RX In UART Serial input, 3.3V logic. Must be low when module is powered on or off. RFU Reserved Reserved for future use - leave unconnected RF RF Transmit and Receive Interface to antenna GND RF Ground Must connect all GND pins to ground as they also serve to remove heat from the module 16,17 22-28 39 37-38, 40-41 Hardware Overview Each line configurable as input or output interface (by default it is an input with internal pull-down). 25 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.7 V max Output High-level Voltage 3.0 V typ, 2.7 V min Output Low-level Current 10 mA max Output High-level Current 7 mA max Control Signal Specification The module communicates to a host processor via a TTL logic level UART serial port, accessed on the edge “vias”. The TTL logic level UART supports complete functionality. The USB port supports complete functionality except the lowest power operational mode. 26 Hardware Overview Hardware Interfaces A DIVISION OF TRIMBLE TTL Level UART Interface Only three pins are required for serial communication (TX, RX, and GND). Hardware handshaking is not supported.This is a TTL interface; a level converter is necessary to connect to devices that use a 12V RS232 interface. The RX line is a 3.3 volt logic CMOS input and is internally pulled up with a resistance value of between 20 and 60 kOhms (40 kOhms nominal). It must be low before the module is turned off and low before the module is turned on. This can be insured if interface drivers are used that are powered by the module itself, as shown in the interface board example. The connected host processorʼs receiver must have the capability to receive up to 256 bytes of data at a time without overflowing. These are the baud rates supported on the interface (bits per second): – 9600 – 19200 – 38400 – 115200 – 230400 – 460800 – 921600 Note Upon initial power up, the default baud rate of 115200 will be used. If that baud rate is changed and saved in the application mode, the new saved baud rate will be used the next time the module is powered up. (Check the firmware release notes to confirm that saving of settings is supported.) General Purpose Input/Output (GPIO) The four GPIO connections, described in the ThingMagic Nano Digital Connector Signal Definition, may be configured as inputs or outputs using the MercuryAPI. The GPIO pins should connect through 1 kOhm resistors to the module to ensure the input Voltage limits are maintained even if the module is shut off. Module power consumption can be increased by incorrect GPIO configuration. Similarly, the power consumption of external equipment connected to the GPIOs can also be adversely affected. The following instructions will yield specification compliant operation. On power up, the ThingMagic Nano module configures its GPIOs as inputs to avoid contention from user equipment that may be driving those lines. The input configuration is Hardware Overview 27 Hardware Interfaces A DIVISION OF TRIMBLE a 3.3 volt logic CMOS input and is internally pulled down with a resistance value of between 20 and 60 kOhms (40 kOhms nominal). Lines configured as inputs must be low whenever the module is turned off and low at the time the module is turned on. GPIOs may be reconfigured individually after power up to become outputs. Lines configured as outputs consume no excess power if the output is left open. 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. 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. ENABLE Line ! C A U T I O N ! ! The polarity of the ENABLE line is opposite from the 4-port M6e module. The ENABLE line (referred to as the SHUTDOWN line in the M6e) must be pulled HIGH or left unconnected in order for the module to be operational. To shut down the module, the line is set LOW or pulled to Ground. Switching from high to low to high is equivalent to performing a power cycle of the module. All internal components of the module are powered down when ENABLE is set LOW. 28 Hardware Overview 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 or if the GPIO lines are supplying current to external circuits. The most obvious impact of this 1A limit is that the module cannot be operated below 3.7 Volts when the RF power output level is set to 27 dBm. This limit is fully explained in the next section. The module will still operate if the DC input Voltage level falls below 3.3 V, but its specifications are not guaranteed. If the DC input Voltage falls below 3 VDC, a “brownout” self-protection function in the processor will gracefully turn the module off so that the module will not be in an undeterminate state once the voltage is restored. RF Power Output Impact on DC Input Current and Power The ThingMagic Nano supports separate read and write power level which are command adjustable via the MercuryAPI. The power level limits are: – Minimum RF Power = 0 dBm – Maximum RF Power = +27 dBm Hardware Overview 29 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. The input Voltage should be maintained above 3.7 Volts if the RF output power setting is above +25 dBm. 3.5 V is adequate for an RF output power level of +26 dBm, and 3.3 V is adequate for an RF output power level of +25 dBm and below. The chart 30 Hardware Overview 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. Once the 1A input current limit is reached, the input power appears to Hardware Overview 31 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 which of the Supported Regions is in use. Power Supply Ripple The following are the minimum requirements to avoid module damage and to insure performance and regulatory specifications are met. Certain local regulatory specifications may require tighter specifications. 32 Hardware Overview DC Power Requirements A DIVISION OF TRIMBLE 3.3 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”. There are 5 enumerated idle power modes defined in the API, but the Nano module only supports 3 options, so three of the settings behave identically. Each successive power mode turns off more of the moduleʼs circuits, which have to be restored when a command is executed, imposing a slight delay. The following table gives the power consumption levels and the delay to respond to a command for each. See Idle DC Power Consumption for details. ThingMagic Nano Power Consumption Operation DC Power Consumed at 5 VDC Time to Respond to a Read Command Power Mode = “FULL” 0.85 W Less than 5 msec Power Mode = “MINSAVE”, “MEDSAVE”, or “MAXSAVE” 0.04 W Less than 20 msec Power Mode = “SLEEP” 0.02 W Less than 20 msec ENABLE Line disabled .00015 W Module reboots when Enable line brought high These nominal values should be used to calculate metrics such as battery life. To determine the absolute maximum DC power that would be required under any condition, one must consider temperature, channel of operation, and antenna return loss. Hardware Overview 33 RF Characteristics A DIVISION OF TRIMBLE RF Characteristics RF Output Power The output power may be set to a separate value for read and write operations (for many tags, more power is required to write to read). The range of values for both settings 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.5 dB increments and linear interpolation is used to set values with greater granularity than this. The granularity of the RF output power setting should not be confused with its accuracy. The accuracy of the output level is specified to be +/- 1 dBm for each regional setting. 34 Hardware Overview RF Characteristics A DIVISION OF TRIMBLE Additional variation may be experienced if the DC input Voltage and temperature changes while the module is operational. This chart shows the typical transmit output variation over frequency. The typical variation is less than +/-0.5 dBm for all transmit levels, across the entire frequency band. DC Input Voltage also affects the transmit output level accuracy. The typical variation is less than +/- 0.20 dBm except at high RF output levels for low DC input voltages, as has been discussed in the RF Power Output Impact on DC Input Current and Power section. The following chart shows the accuracy of the RF power setting across all supported input DC voltages. Note that the actual RF output level starts to drop for +27 dBm output level Hardware Overview 35 RF Characteristics A DIVISION OF TRIMBLE settings at around 3.7 VDC input levels and the RF output level starts to drop for +25 dBm settings at around 3.3 VDC input levels. The output accuracy over temperature is typically +/- 0.75 dBm, with most variation occurring at lower transmit output power levels. 36 Hardware Overview RF Characteristics A DIVISION OF TRIMBLE Receive Sensitivity The receive 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. ThingMagic always quotes the receive sensitivity at the highest transmit level (+27 dBm for the Nano), but 1 dB of sensitivity is typically gained for every dB that the transmitter output level is reduced. The Gen2 “M” setting influences how data is encoded when sent from the tag to the reader. Higher “M” values send data at lower rates and are more noise immune, Hardware Overview 37 RF Characteristics A DIVISION OF TRIMBLE increasing the moduleʼs sensitivity. Lower “M” values send data at higher rates, decreasing the sensitivity somewhat. The region of operation is also a factor. The Nano has slightly better receive sensitivity in the regions that fall within the range of 865 to 868 MHz than in regions that fall within the range of 917 to 928 MHz. The following table gives the sensitivity for region and “M” value at a transmit output level of +27 dBm. Region North America and subsets of 917 to 928 MHz band EU and India (865 to 868 MHz “M” Value 8 4 2 Sensitivity -57 dBm -55 dBm -45 dBm 8 4 2 -60 dBm -58 dBm -49 dBm Note that sensitivity is strongly affected by the success rate required by the application. The sensitivity values in the table reflect a very high read success rate (greater than 90%). Tags typically will begin to respond sporadically at receive levels that are 5 dB lower than the values shown in this table. Receiver Adjacent Channel Rejection The ThingMagic Nano receives signals that are centered at +250 kHz from its own carrier. The width of the receive filter is adjusted to match the “M” value of the signal being sent by the tag. An M value of 2 require the widest filter and an M value of 8 requires the narrowest filter. If operating in an environment where many readers are present, observe the performance of one reader as the other readers are turned on and off. If the performance improves when the other readers are turned off, then the system may be experiencing reader-to-reader interference. This reader-to-reader interference will be minimized by using the highest “M” value that is consistent with the tag read rates required by the application. 38 Hardware Overview 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 plane that the ThingMagic Nano module is soldered to. It may be safely stored in temperatures ranging from -40 degrees C to +85 degrees C. Thermal Management Heat-sinking For high duty cycles, it is essential to use a surface mount configuration where all edge vias are soldered to a carrier or mother board, with a large area of ground plane, that will either radiate heat or conduct the heat to a larger heat-sink. A high density of PCB vias from the top to bottom of the board will efficiently conduct heat to a bottom mount heatsink. Often the weak link in thermal management design is not the thermal interface from the ThingMagic Nano to the heat-sink, but rather the thermal interface from the heat-sink to the outside world. Duty Cycle If overheating occurs it is recommended to first try reducing the duty cycle of operation. This involves modifying the RF On/Off (API parameter settings /reader/read/ asyncOnTime and asyncOffTime) values. A good place to start is 50% duty cycle using 250ms/250ms On/Off. If your performance requirements can be met, a low enough duty cycle can result in no heat sinking required. Or with adequate heat sinking you can run continuously at 100% duty cycle. Temperature Sensor The ThingMagic Nano module has an integrated temperature sensor, located near the components which generate the most heat. The temperature can be obtained through the user interface as a status indication. This information is also used by the firmware to prevent transmission when the module is too hot or too cold to operate properly. The temperature limits for allowing transmission are -20 C to +85 C. Hardware Overview 39 Environmental Specifications A DIVISION OF TRIMBLE Note The temperature level at which transmission is prevented, +85 C, is higher than the +60 C operating limit for two reasons: (1) The temperature indicated by the on-board sensor will always be higher than ambient temperature, due to heat generated by internal components, and (2) the temperature limit for transmission is chosen to prevent damage to the components, while the +60 C limit for operation is chosen to ensure that all specifications are met. 40 Hardware Overview Environmental Specifications A DIVISION OF TRIMBLE Electro-Static Discharge (ESD) Specification The Electro-Static Discharge Immunity specifications for the ThingMagic Nano are as follows: 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. See ElectroStatic Discharge (ESD) Considerations for methods to increase ESD tolerances. 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 and operation to avoid static discharge when handling or making connections to the ThingMagic Nano reader antenna or communication ports. Environmental analysis should also be performed to ensure static is not building up on and around the antennas, possibly causing discharges during operation. Shock and Vibration The ThingMagic Nano module is specified to survive a 1 meter drop onto a hard surface. It will also survive the following vibration limits: 4.02 Grms random, mounted on a non-resonant hard carrier Five shipments by air, MIL-STD-810G METHOD 514.6 ANNEX C, Figure 514.6C-5 General Exposure pg 514.6C-16, and Table 514.6C-VII, General Exposure. 5 minutes each of three axes. Hardware Overview 41 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. (Circularly polarized antennas can have a circular gain has high as 11.15 dBiC and still maintain a maximum linear gain of 8.15 dBiL.) The required antenna impedance is 50 ohms. ThingMagic Nano Authorized Antennas Vendor Model Type Polarizatio n Frequency Range MTI Wireless Laird MT-263020 Patch Circular S9025P Patch Circular Laird S8658WPL Patch Circular MTI Wireless MTI Wireless MTI-262013 Patch Circular MTI-242043 Patch Circular 902-928 MHz 902-928 MHz 865-960 MHz 902-928 MHz 865-956 MHz FG9026 Dipole Linear Laird 902-928 MHz Circular Gain (dBiC) 11 min Max Linear Gain (dBi) 8 5.5 4.3 8.5 6.0 7 min, 7.5 max 7.5 in EU band, 8.5 in NA band [Not Applicable] 6.0 6.0 8.15 Note: Most tags are linearly polarized, so the “max linear gain” value is the best number to use when calculating the maximum read distance between the module and a tag. FCC Modular Certification Considerations Trimble has obtained FCC modular certification for the ThingMagic Nano module. This means that the module can be installed in different end-use products by another equipment manufacturer with little or no additional testing or equipment authorization for the transmitter function provided by that specific module. Specifically: No additional transmitter-compliance testing is required if the module is operated with one of the antennas listed in the FCC filing No additional transmitter-compliance testing is required if the module is operated with the same type of antenna as listed in the FCC filing as long as it has equal or lower gain than the antenna listed. Equivalent antennas must be of the same general type (e.g. dipole, circularly polarized patch, etc.), must be of equal or less gain than an 42 Hardware Overview Authorized Antennas A DIVISION OF TRIMBLE antenna previously authorized under the same FCC ID, and must have similar in band and out of band characteristics (consult specification sheet for cut-off 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. The FCC regulations state that a host device using a module that has a modular grant can: 1. Be marketed and sold with the module built inside that does not have to be end-user accessible/replaceable, or 2. Be end-user plug-and- play replaceable. In addition, a host product is required to comply with all applicable FCC equipment authorizations, regulations, requirements and equipment functions not associated with the RFID module portion. For example, compliance must be demonstrated to regulations for other transmitter components within the host product; to requirements for unintentional radiators (Part 15B), and to additional authorization requirements for the non-transmitter functions on the transmitter module (for example, incidental transmissions while in receive mode or radiation due to digital logic functions). To ensure compliance with all non-transmitter functions the host manufacturer is responsible for ensuring compliance with the module(s) installed and fully operational. For example, if a host was previously authorized as an unintentional radiator under the Declaration of Conformity procedure without a transmitter certified module and a module is added, the host manufacturer is responsible for ensuring that the after the module is installed and operational the host continues to be compliant with Part 15B unintentional radiator requirements. Since this may depend on the details of how the module is integrated with the host, we shall provide guidance to the host manufacturer for compliance with Part 15B requirements. Hardware Overview 43 Physical Dimensions A DIVISION OF TRIMBLE Physical Dimensions The dimensions of the ThingMagic Nano module are shown in the following diagram and the table below: Attribute Value Width 22 +/-0.2 mm Length 26 +/-0.2 mm Height (includes PCB, shield, mask and labels) 3.0 maximum Mass 3.2 gms 44 Hardware Overview Physical Dimensions A DIVISION OF TRIMBLE Tape-and-Reel Dimensions The Nano is delivered in a tape-and-reel package. The reel measures 13 inches by 4 inches. The following drawing gives the dimensions of the tape. Hardware Overview 45 Physical Dimensions A DIVISION OF TRIMBLE 46 Hardware Overview 70   :$1*-6 32/