A DIVISION OF TRIMBLE 875-0069-07 RevA Micro Hardware Guide For: Micro (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 7/2012 01 Rev1 First Draft for early-access release 11/2012 02 Rev1 Updated Devkit section with additional board details.
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 Micro.
Micro A DIVISION OF TRIMBLE 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. W A R N I N G ! Operation of the Micro module requires professional installation to correctly set the TX power for the RF cable and antenna selected.
Micro A DIVISION OF TRIMBLE 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: “This device complies with Part 15....” AND “Any changes or modifications to the transmitting module not expressly approved by ThingMagic Inc.
Micro A DIVISION OF TRIMBLE 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 isotropically radiated power (e.i.r.p.
Micro A DIVISION OF TRIMBLE 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.
Micro A DIVISION OF TRIMBLE 10
A DIVISION OF TRIMBLE Contents Communication Regulation Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Micro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Federal Communication Commission Interference Statement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Industry Canada . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A DIVISION OF TRIMBLE Electro-Static Discharge (ESD) Specification. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Authorized Antennas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 FCC Modular Certification Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Assembly Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A DIVISION OF TRIMBLE Protocol Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Antenna Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 Using a Multiplexer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 Port Power and Settling Time. . . . . . . . . . . . . . . . . .
A DIVISION OF TRIMBLE FAULT_NO_PROTOCOL_DEFINED – 401h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 FAULT_INVALID_PROTOCOL_SPECIFIED – 402h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 FAULT_WRITE_PASSED_LOCK_FAILED – 403h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 FAULT_PROTOCOL_NO_DATA_READ – 404h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 FAULT_AFE_NOT_ON – 405h . . . . . . . . . . . . . . . .
A DIVISION OF TRIMBLE Devkit Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Included Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Setting up the DevKit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Connecting the Antenna . . . . . . . . . . . . . . . . . . .
A DIVISION OF TRIMBLE 16 Contents
A DIVISION OF TRIMBLE Micro Introduction The ThingMagic® Micro® embedded module is an RFID engines that you can integrate with other systems to create RFID-enabled products. Applications to control the Micro modules and derivative products can be written using the high level MercuryAPI. The MercuryAPI supports Java, .NET and C programming environments.
A DIVISION OF TRIMBLE 18 Micro Introduction
A DIVISION OF TRIMBLE Hardware Overview The following section provides detailed specifications of the Micro hardware including: Hardware Interfaces Power Requirements Environmental Specifications Assembly Information Micro Hardware Integration Hardware Overview 19
Hardware Interfaces A DIVISION OF TRIMBLE Hardware Interfaces Antenna Connections The Micro supports two monostatic bidirectional RF antennas through two U.FL connector or edge vias. See Cables and Connectors for more information on antenna connector parts and Micro 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 1 Watt, or +30 dBm (regulatory requirements permitting).
Hardware Interfaces A DIVISION OF TRIMBLE Digital/Power Interfaces The digital connector provides power, serial communications signals, shutdown and reset signals to the Micro module, and access to the GPIO lines. These signals are provided through edge vias and the Molex 53748-0208 connector. See Cables and Connectors for more information on parts.
Hardware Interfaces A DIVISION OF TRIMBLE Micro Digital Connector Signal Definition Molex 53748-0208 Pin # Edge Via Pin # Signal Direction (In/Out of Micro) Signal Notes 1-15, 21, 23, 29, 31 5-8 GND P/S Return Must connect all GND pins to ground 25, 27 1-4 Vin P/S Input 3.5 to 5.25VDC. Must connect all Vin supplies.
Hardware Interfaces A DIVISION OF TRIMBLE Note It is not recommended to use the TTL interface when planning to operate the module in Tag Streaming/Continuous Reading mode. The TTL interface (both the module side and the host side) cannot detect physical disconnections, as can the USB Interface, simplifying reconnection. TTL Level UART Interface TTL Level TX V-Low: Max 0.4 VDC V-High: 2.1 to 3.3 VDC 8 mA max TTL Level RX V-Low: -0.3 to 0.6 VDC V-High: 2.
Hardware Interfaces A DIVISION OF TRIMBLE USB Interface Supports USB 2.0 full speed device port (12 Megabits per second) using the two USB pins (USB_DM and USB_DP). General Purpose Input/Output (GPIO) The two GPIO connections, provided through the Micro Digital Connector Signal Definition, may be configured as inputs or outputs using the MercuryAPI. The GPIO pins connect through 100 ohm resistors to the high current PA0 and PA1 pins of the AT91SAM7S processor.
Hardware Interfaces A DIVISION OF TRIMBLE and individually pulled externally to either high or low logic level, module power consumption is as listed in the Micro Power Consumption table. GPIOs may be reconfigured individually after power up to become outputs. This configuration takes effect either at API execution or a few tens of milliseconds after power up if the configuration is stored in nonvolatile memory.
Hardware Interfaces A DIVISION OF TRIMBLE Shutdown Line ! C A U T I O N ! ! The polarity of the shutdown line is opposite from the 4-port M6e module. The SHUTDOWN line must be set HIGH (Vin level) or Open Circuit to ENABLE module. In order to shutdown/reset/power cycle the module the line can be 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 are powered down when set low.
Power Requirements A DIVISION OF TRIMBLE Power Requirements RF Power Output The Micro supports separate read and write power level which are command adjustable via the MercuryAPI. Power levels must be between: – Minimum RF Power = 0 dBm – Maximum RF Power = +30 dBm 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.
Power Requirements A DIVISION OF TRIMBLE Power Consumption The following table defines the power consumption specifications for the Micro in various states of operation. See Power Management for details. Micro Power Consumption Operation RF Transmit Power Setting (dBm) Nominal DC Power1 (Watts) Active Reader (RF On) +30 5.5 +27 3.5 +23 2.5 +10 2.0 No Tag Reading (Micro idle) Power Mode = FULL n/a 0.325 No Tag Reading (Micro idle) Power Mode = MINSAVE n/a 0.
Environmental Specifications A DIVISION OF TRIMBLE Environmental Specifications Thermal Considerations There are two ways of mounting the Micro, see Micro Hardware Integration for additional details. One is to solder the board to the motherboard using its side “vias”, with the RF shield can facing upward. The other is to use the board-to-board connectors to connect to the motherboard and solder the 4 tabs on the shield to the motherboard as well.
Environmental Specifications A DIVISION OF TRIMBLE Mounting 30 Ambient Temp (°C) RF Power (dBm) Duty Cycle % Time (m) to reach max temperature Soldered down 60 30 60 1.99 Soldered down 60 30 80 1.11 Soldered down 60 30 98 0.98 Board to board -40 30 98 No restriction Board to board 25 23 50 No restriction Board to board 25 23 60 2.93 Board to board 25 23 80 2.22 Board to board 25 23 98 1.
Environmental Specifications A DIVISION OF TRIMBLE Thermal Management Heatsinking For high duty cycles, it is essential to use the surface mount configuration - as shown in Micro Hardware Integration | Sample Board Layout Using Surface Mount Option - 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 heatsink.
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 2KV pulse. 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 Micro antenna ports may be susceptible to damage from Electrostatic Discharge (ESD).
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 6 dBiL. Antennas not included in this list or having a gain greater than 6 dBiL are strictly prohibited for use with this device without regulatory approval. The required antenna impedance is 50 ohms. Micro Authorized Antennas Vendor Model Type Polarization Linear Gain1 (dBi) Laird S9025P Patch Circular 4.
Authorized Antennas A DIVISION OF TRIMBLE 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. 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.
Assembly Information A DIVISION OF TRIMBLE Assembly Information Cables and Connectors The following are the cables and connectors used in the Micro Developer’s Kit interface board: Mating Connectors for Flip Mount Power-I/O: Molex 52991-0208 RF: Lighthorse LTI-IPXSF66GT-X1 or LTI-IPXSF54GT Digital Interface The cable assembly used consists of the following parts: Note Pin numbers and assignments are shown in the Micro Digital Connector Signal Definition table.
Assembly Information A DIVISION OF TRIMBLE Micro Mechanical Drawing Micro Dimensional Drawing 36 Hardware Overview
Micro Hardware Integration A DIVISION OF TRIMBLE Micro Hardware Integration In addition to the design and process recommendation shown in the schematics on the following pages the following should be considered: There is the potential for 24MHz harmonics radiating from pins 22 through 28 of the Micro. If emissions testing shows such harmonics the easiest fix is to put bypass capacitors (typically 39 to 100pf) directly at the offending pins on the carrier board.
4 Pin 29 30 31 32 C All GND pads should be connected to a top layer copper pour with no thermal reliefs. 01 Initial Release DATE BY RH 0.050 typ Function Gnd Antenna 1 Gnd Antenna 2 0.060 typ 27 25 23 21 19 17 15 13 11 9 7 5 3 D 1 0.515 1.030 0.980 Optional 0.110"D Mounting Hole No traces on top side in this area Module Outline Component Keepout 28 GND clearance around antenna ports (pin 30, 32) should be a minimum of 15mils to reduce capacitance. If the U.
4 D 3 2 1 REV. DESCRIPTION 01 Initial Release DATE BY RH SMT Reflow Profile D 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. C Generally speaking, unnecessary long exposure and exposure to more than 245C should be avoided. The profile shown has been used to assemble panelized boards similar to those on Sheet 4 of this document .
4 D Pin 1 3 5 7 9 11 13 15 17 19 Function Vin Vin Gnd Gnd USB 5VSENSE GPIO1 GPIO2 RS232 RX RS232 TX Shutdown 3 Pin 2 4 6 8 10 12 14 16 18 20 2 Function Vin Vin Gnd Gnd NC USB DP USB DM NC NC Ext Reset 1 REV. DESCRIPTION 01 Initial Release 1.708 0.500 0.150 typ RH D Antenna 2 0.100 typ 0.200 Antenna 1 1.200 1.030 0.018 0.910 DO NOT REFLOW SOLDER WITH THIS CONFIGURATION! 0.523 Pin20 0.515 0.200 0.010 Optional 0.
4 3 2 1 REV. DESCRIPTION 01 Initial Release DATE BY RH Sample Board Layout Using Surface Mount Option D D C C B B ThingMagic, A Division of Trimble This drawing contains information that is proprietary and confidential to ThingMagic, Inc, and should not be used without written permission. Four Cambridge Center, 12th Floor, Cambridge, MA 02142 866-833-4069 M6e-Micro Module Integration SMT Mounting Example A A SIZE DWG NO REV R.
4 3 2 1 REV. DESCRIPTION 01 Initial Release DATE BY RH D D Sample Board Layout Using Connectorized ‘Flip’ Option C C B B ThingMagic, A Division of Trimble This drawing contains information that is proprietary and confidential to ThingMagic, Inc, and should not be used without written permission. Four Cambridge Center, 12th Floor, Cambridge, MA 02142 866-833-4069 M6e-Micro Module Integration Flip Mounting Example A A SIZE DWG NO REV R.
Micro Hardware Integration A DIVISION OF TRIMBLE 38 Hardware Overview
A DIVISION OF TRIMBLE Firmware Overview The following section provides detailed description of the Micro firmware components: Boot Loader Application Firmware Custom On-Reader Applications Firmware Overview 39
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 Micro 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 Micro Applications to control the Micro module and derivative products are written using the high level MercuryAPI. The MercuryAPI supports Java, .NET and C programming environments.
Custom On-Reader Applications A DIVISION OF TRIMBLE Custom On-Reader Applications The Micro 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 Micro.
Serial Communication Protocol A DIVISION OF TRIMBLE Serial Communication Protocol The serial communication between a computer (host) and the Micro 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 Micro does not support programming to the serial protocol directly. All user interaction with the Micro 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 Micro The following section provides detailed descriptions of the Micro 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 Micro. Supported Regions The Micro 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. Region Regulatory Support North America (NA) FCC 47 CFG Ch.
Regulatory Support A DIVISION OF TRIMBLE Korea (KR2) KCC (2009) India (IN) Telecom Regulatory Authority of India (TRAI), 2005 regulations People’s Republic of China (PRC & CN) SRRC, MII Note: CN was previously called PRC2. The first frequency channel (917,300kHz) of the KR2 region will be derated to +22dBm to meet the new Korea regulatory requirements. All other channels operate up to +30dBm. 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 Quantization Region Frequency Quantization Minimum Frequency Maximum Frequency NA 250 kHz 902,000 kHz 928,000 kHz EU3 100 kHz 865,600 kHz 867,600 kHz IN 100 kHz 865,200 kHz 866,800 kHz KR 25 kHz 910,000 kHz 914,000 kHz KR2 25 kHz 917,000 kHz 923,500 kHz PRC 250 kHz 920,125 kHz 924,875 kHz CN 250 kHz 840,000 kHz1 845,000 kHz1 AU 250 kHz 920,750 kHz 925,250 kHz NZ 250 kHz 922,250 kHz 927,250 kHz JP 250 kHZ 9
Regulatory Support A DIVISION OF TRIMBLE Changes not stored in flash, thus changes made are not retained after a power cycle or a restart of the boot loader. Inability to change individual entries after uploading without reloading the entire table. Frequencies used in the order of entries in the table. If necessary for a region, the hop table can be 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 The Micro has the ability to support many different tag protocols. Using the MercuryAPI ReadPlan classes the Micro can be configured to single or multi-protocol Read operations.
Protocol Support A DIVISION OF TRIMBLE reading data faster than the transport can handle and send, and the reader’s buffer might fill up. Protocol Specific Functionality See the MercuryAPI Programmers Guide and language specific reference guides for details on supported Gen2 command functionality. I-PX Protocol Configuration Options The Micro supports multiple I-PX profiles including the ability to specify the Return Link Frequency, encoding and modulation scheme.
Protocol Support A DIVISION OF TRIMBLE protocol options are set in the MercuryAPI Reader Configuration Parameters (/reader/ iso18000-6b/*). The following table shows the supported combinations: Return Link Freq (kHz) Return Encoding Forward Link Freq (kHz) Forward Encoding Modulation Depth 40 FM0 10 Manchester 11% 40 FM0 10 Manchester 99% 160 FM0 40 Manchester 11% 160 FM0 40 Manchester 99% (default) Delimiter ISO18000-6B tags support two delimiter settings on the transmitter.
Antenna Ports A DIVISION OF TRIMBLE Antenna Ports The Micro has two monostatic antenna ports. Each port is capable of both transmitting and receiving. The modules also support Using a Multiplexer, allowing up to 8 total logical antenna ports, controlled using two GPIO lines and the internal physical port Antenna1/ Antenna2 (A1/A2) switching. Note The Micro does not support bistatic operation.
Antenna Ports A DIVISION OF TRIMBLE GPIO 1 & 2 Used for Antenna Switching Logical Antenna Setting GPIO Output 1 State GPIO Output 2 State Active Micro Physical Port 1 Low Low A1 2 Low Low A2 3 Low High A1 4 Low High A2 5 High Low A1 6 High Low A2 7 High High A1 8 High High A2 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 antenn
Antenna Ports A DIVISION OF TRIMBLE ONLY GPIO 2 Used for Antenna Switching Logical Antenna Setting GPIO Output 2 State Active Micro Physical Port 1 Low A1 2 Low A2 3 High A1 4 High A2 Port Power and Settling Time The Micro 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.
Tag Handling A DIVISION OF TRIMBLE Tag Handling When the Micro 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 Micro 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 1024 96-bit EPC tags in the TagBuffer at a time.
Tag Handling A DIVISION OF TRIMBLE Note It is recommended the USB Interface be used when operating the Micro in continuous reading mode. 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 Micro 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 Micro 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 Micro 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 Micro is idle.
Performance Characteristics A DIVISION OF TRIMBLE Performance Characteristics Event Response Times The following table provides some metrics on how long common Micro 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.
Save and Restore Configuration A DIVISION OF TRIMBLE Save and Restore Configuration The Micro supports saving module and protocol configuration parameters to the module flash to provide configuration persistence across boots. Currently the region, baud-rate, and default protocol can be saved across reboots. Future firmware upgrades will support saving other configuration values. See the MercuryAPI Programmers Guide and sample applications for details on saving and restoring reader configuration.
Common Error Messages A DIVISION OF TRIMBLE Appendix A: Error Messages Common Error Messages The following table lists the common faults discussed in this section.
Common Error Messages A DIVISION OF TRIMBLE Solution Check the following: Make sure the command is supported in the currently running program. Check the documentation for the opCode the host sent and make sure it is correct and supported. Check the previous module responses for an assert (0x7F0X) which will reset the module into the bootloader. FAULT_UNIMPLEMENTED_OPCODE – 102h Cause Some of the reserved commands might return this error code.
Common Error Messages A DIVISION OF TRIMBLE 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. FAULT_MSG_INVALID_PARAMETER_VALUE - (105h) Cause The reader received a valid command with an unsupported or invalid value within this command. For example, currently the module supports four antennas.
Common Error Messages A DIVISION OF TRIMBLE Solution Check the command being invoked against the documentation. FAULT_INVALID_BAUD_RATE - (10Ah) Cause When the baud rate is set to a rate that is not specified in the Baud Rate table, this error message is returned. Solution Check the table of specific baud rates and select a baud rate.
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 testcase 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 testcase 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 Micro 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). 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 testcase 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. Solution Send a testcase reproducing the behavior to support@thingmagic.
System Errors A DIVISION OF TRIMBLE System Errors FAULT_SYSTEM_UNKNOWN_ERROR – 7F00h Cause The error is internal. Solution Send a testcase 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 testcase reproducing the behavior to support@thingmagic.com.
A DIVISION OF TRIMBLE Appendix B: Getting Started - Devkit Devkit Hardware Included Components With the devkit, you will receive the following components: The Micro module and carrier board Power/interface developers board One USB cable One antenna One coax cable One 9V power supply International power adapter kit 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 suppor
Devkit Hardware A DIVISION OF TRIMBLE Connecting the Antenna ThingMagic supplies one antenna that can read tags from 20’ away with most of the provided tags. The antenna is monstatic. Use the following procedure to connect the antenna to the DevKit. 1. Connect one end of the coax cable to the antenna. 2. Connect the other end of the cable to the antenna port 1 connector on the DevKit.
Devkit Hardware A DIVISION OF TRIMBLE Devkit USB Interfaces USB/RS232 The USB interface (connector labeled USB/RS232) closest to the power plug is to the RS232 interface of the Micro 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.
Devkit Hardware A DIVISION OF TRIMBLE c. Select View | Devices by Type | Ports (COM & LPT) The device appears as M6eMicro (COM#). Note The carrier board can be used independently of the dev kit motherboard via the USB connector on the carrier board. If the carrier board is to be powered by the USB connector, a jumper (nearest the USB connector) must be installed that connects “VIN” to “+5USB” (these labels are silkscreened on the carrier board).
Devkit Hardware A DIVISION OF TRIMBLE J16 Jump pins 1 and 2 or 2 and 3 to reset devkit power supply. Same as using switch SW1 except allows for control by external circuit. J17 Jump pins 1 and 2 to use the 5V INPUT and GND inputs to provide power. Jump pins 2 and 3 to use the DevKit’s DC power jack and power brick power. J19 The jumper at J19 that connects Shutdown to ground must be REMOVED. With this jumper removed, the module is always operational. The shutdown switch has no affect on the Micro.
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/devkit. 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 DevKit A DIVISION OF TRIMBLE Notice on Restricted Use of the DevKit The Mercury6e Developers Kit (DevKit) 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.
Notice on Restricted Use of the DevKit A DIVISION OF TRIMBLE 94 Appendix B: Getting Started - Devkit
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 W A R N I N G ! The Micro antenna ports may be susceptible to damage from Electrostatic Discharge (ESD). Equipment failure can result if the antenna or communication ports are subjected to ESD.
ElectroStatic Discharge (ESD) Considerations A DIVISION OF TRIMBLE has returned to the bootloader to prevent any further damage. This jump to boot loader caused by power amp damage occurs at the start of any read tag commands. Ultimately determining that ESD is the root cause of failures is difficult because it relies on negative result experiments, i.e. it is the lack of failure after a configuration change, rather than a positive flag wave that says “I’m ESD”.
ElectroStatic Discharge (ESD) Considerations A DIVISION OF TRIMBLE What actually gets to the Micro is also strongly influenced by the antenna installation, cabling, and grounding discussed above. Use the mean operating time statistic before and after one or more of the changes listed below to quantitatively determine if the change has resulted in an improvement. Be sure to restart your statistics after the change.
ElectroStatic Discharge (ESD) Considerations A DIVISION OF TRIMBLE Raising the ESD Threshold For applications where full Micro power is needed for maximum tag read range and ESD is suspected the following components are recommended additions to the installation to raise the level of ESD the reader can tolerate: Select or change to an antenna with all radiating elements grounded for DC. The MTI MT-262031-T(L,R)H-A is such an antenna. The Laird IF900-SF00 and CAF95956 are not such antennas.
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.
