manualshive.com logo in svg

ThingMagic Mercury6e M6e-30dBm, Hardware Manual

Share
Download
ThingMagic Mercury6e M6e-30dBm Hardware Manual Download Page 13

Mercury6e Introduction

 13 

Mercury6e Introduction

The ThingMagic

®

 Mercury6e

®

 (M6e) embedded module is an RFID engines that you can 

integrate with other systems to create RFID-enabled products. 

Applications to control the M6e 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 demoing 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 for hardware designers and software developers. It describes the 
hardware specifications and firmware functionality and provides guidance on how to 
incorporate the M6e module within a third-party host system. The rest of the document is 
broken down into the following sections:

 

Hardware Overview

 - This section provides detailed specifications of the M6e 

hardware. This section should be read in its entirety before designing hardware or 
attempting to operate the M6e module in hardware other than the ThingMagic 
DevKit.

 

Firmware Overview

 - This section describes provides a detailed description of the M6e 

firmware components including the bootloader and application firmware.

 

Communication Protocol

 - This section provides an overview of the low level serial 

communications protocol used by the M6e.

 

Functionality of the Mercury6e

 - This section provides detailed descriptions of the M6e 

features and functionality that are supported through the use of the MercuryAPI.

 

Appendix A: Error Messages

 - This appendix lists and provides causes and suggested 

solutions for M6e Error Codes.

 

Appendix B: Getting Started - Devkit

 - QuickStart guide to getting connected to the M6e 

Developer’s Kit and using the Demo Applications included with the MercuryAPI SDK.

Summary of Contents for Mercury6e M6e-30dBm

Page 1: ...M6e 31 5dBm Hardware Guide For M6e Firmware Ver 1 7 and later ...

Page 2: ...e markings Any person other than the U S Government who has been provided access to such data must promptly notify ThingMagic Inc 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 2011 ThingMagic a division ...

Page 3: ...on Table Date Version Description 4 2010 01 RevA First Draft for Beta release 8 2010 01 RevB Updated GPIO content Added FCC regulation info section 2 2011 02 Rev2 updated content to meet regulatory requirements ...

Page 4: ...4 ...

Page 5: ...16 Digital Power Connector 16 Control Signal Specification 17 General Purpose Input Output GPIO 19 Reset Line 20 Power Requirements 21 RF Power Output 21 Power Settings for Authorized Antennas and Cables 21 Power Supply Ripple 22 Power Consumption 22 Environmental Specifications 24 Operating Temperature 24 Electro Static Discharge ESD Specification 24 Assembly Information 25 Cables and Connectors ...

Page 6: ...alculation 35 User Programming Interface 36 Functionality of the Mercury6e 37 Regulatory Support 38 Supported Regions 38 Frequency Setting 38 Frequency Units 39 Frequency Hop Table 39 Protocol Support 40 ISO 18000 6C Gen2 40 Protocol Configuration Options 40 Protocol Specific Functionality 41 I PX 41 Protocol Configuration Options 41 ISO 18000 6B 41 Protocol Configuration Options 41 Antenna Ports ...

Page 7: ...T_INVALID_BAUD_RATE 10Ah 56 Bootloader Faults 57 FAULT_BL_INVALID_IMAGE_CRC 200h 57 FAULT_BL_INVALID_APP_END_ADDR 201h 57 Flash Faults 58 FAULT_FLASH_BAD_ERASE_PASSWORD 300h 58 FAULT_FLASH_BAD_WRITE_PASSWORD 301h 58 FAULT_FLASH_UNDEFINED_ERROR 302h 59 FAULT_FLASH_ILLEGAL_SECTOR 303h 59 FAULT_FLASH_WRITE_TO_NON_ERASED_AREA 304h 59 FAULT_FLASH_WRITE_TO_ILLEGAL_SECTOR 305h 59 FAULT_FLASH_VERIFY_FAILE...

Page 8: ...OR 42Fh 68 FAULT_GEN2 PROTOCOL_UNKNOWN_ERROR 430h 68 Analog Hardware Abstraction Layer Faults 69 FAULT_AHAL_INVALID_FREQ 500h 69 FAULT_AHAL_CHANNEL_OCCUPIED 501h 69 FAULT_AHAL_TRANSMITTER_ON 502h 69 FAULT_ANTENNA_NOT_CONNECTED 503h 69 FAULT_TEMPERATURE_EXCEED_LIMITS 504h 70 FAULT_POOR_RETURN_LOSS 505h 70 FAULT_AHAL_INVALID_ANTENA_CONFIG 507h 70 Tag ID Buffer Faults 72 FAULT_TAG_ID_BUFFER_NOT_ENOUG...

Page 9: ...n 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 rad...

Page 10: ...M 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 suc...

Page 11: ...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 is not more than that permitted for successful communication Thi...

Page 12: ...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 choi...

Page 13: ...in a third party host system The rest of the document is broken down into the following sections Hardware Overview This section provides detailed specifications of the M6e hardware This section should be read in its entirety before designing hardware or attempting to operate the M6e module in hardware other than the ThingMagic DevKit Firmware Overview This section describes provides a detailed des...

Page 14: ...14 Mercury6e Introduction ...

Page 15: ...are Overview 15 Hardware Overview The following section provides detailed specifications of the M6e hardware including Hardware Interfaces Power Requirements Environmental Specifications Assembly Information ...

Page 16: ... 17 dB return loss 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 To minimize the chance of damage due to antenna disconnection the M6e supports antenna detection Detection can be done aut...

Page 17: ...ons apply to control via the TTL UART M6e Digital Connector Signal Definition Molex 53261 1571 Pin Number Signal Signal Direction In Out of M6e Notes 1 GND P S Return Must connect both GND pins to ground 2 GND P S Return 3 5VDC P S Input Must connect both 5V supplies 4 5 VDC P S Input 5 GPIO1 Bi directional Input 5VDC tolerant 16mA Source Sink 6 GPIO2 Bi directional 7 GPIO3 Bi directional 8 GPIO4 ...

Page 18: ...at empties into a circular buffer The connected host processor s receiver must have the capability to receive up to 256 bytes of data at a time without overflowing Baud rates supported 9600 19200 38400 115200 230400 460800 921600 Note The baudrate in the Boot Loader mode depends on whether the module entered the bootloader mode after a power up or through an assert or boot bootloader user command ...

Page 19: ... than 1 2 Volts when sinking 8 mA Less than 0 2 Volts when sinking 0 3 mA Module power consumption can be adversely affected 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 M6E module configures its GPIOs as outputs to a...

Page 20: ...ader gpio outputList Once configured as inputs or outputs the state of the lines can be Get or Set using the gpiGet and gpoSet methods respectively See the language specific reference guide for more details Reset Line Upon power up the RESET pin 15 line is configured as an input The input value will determine whether the Boot Loader will wait for user commands or immediately load the Application F...

Page 21: ... RF cable and antenna selected Power Settings for Authorized Antennas and Cables This device has been designed to operate with the antennas listed in Authorized Antennas list using the cables in the Authorized Cables list For any combination of antenna and cable the maximum RF power is determined from antenna gain Max Linear Gain value from antenna list and antenna cable loss Insertion Loss value ...

Page 22: ...gs and power consumption specifications for the M6e Additional details about Power Transmit Modes can be found in the Power Management section M6e Power Consumption Operation Power Transmit Mode MaxPower1 Watts Voltage Volts Current mA RF Transmit Power Setting dBm Transmit CW Transmit Mode DRM 7 52 5 0 5 1400 31 5 Tag Reading Transmit Mode DRM 7 52 5 0 5 1400 31 5 Tag Reading Transmit Mode Low Po...

Page 23: ...TL RS232 operation Power consumption may vary if the USB interface is connected Note 2 Power consumption is defined for operation into a 17dB return loss load or better Power consumption may increase beyond this specification during operation into return losses worse than 17dB M6e Power Consumption Operation Power Transmit Mode MaxPower1 Watts Voltage Volts Current mA RF Transmit Power Setting dBm...

Page 24: ...rview Environmental Specifications Operating Temperature Clamshell temperature must not exceed 70 degrees C Heat sinking will be required for high duty cycle applications Electro Static Discharge ESD Specification Specifications to be determined ...

Page 25: ...cts each Molex 50079 8100 1 Wire 28 AWG 7x36 Black Teflon for Pin 1 connection Alpha 284 7 2 14 Wires 28 AWG 7x36 White Teflon for other connections Alpha 284 7 1 Note Pin numbers and assignments are shown in the M6e Digital Connector Signal Definition table Antennas The cable assembly used to connect the external RP TNC connectors on the M6e Devkit to the M6e MMCX connectors consists of the follo...

Page 26: ...Assembly Information 26 Hardware Overview M6e Mechanical Drawing ...

Page 27: ... required antenna impedance is 50 ohms Manufacturer Type Manufacturer Part Number Max Linear Gain dBiL Laird Patch S9025P 4 3 Laird Patch S8658WPL 6 0 Laird Patch DCE8658WPR 6 0 dBiL Laird Patch PEL90206 4 7 dBiL Laird Patch S9026X 4 5 dBiL MTI Patch MT 262013 6 0 dBiL MTI Patch MT 242043 6 0 dBiL MTI Patch MT 242042 4 1 dBiL MTI Patch MT 241026 0 2 dBiL Poynting Patch A PATCH 0025 5 dBiL Mobile M...

Page 28: ...for authorized shielded coaxial cables provided by ThingMagic Cable Description ThingMagic Part Number Insertion Loss 6 RTNC to RTNC Cable CBL P6 0 8 dB 12 RTNC to RTNC Cable CBL P12 1 5 dB 20 RTNC to RTNC Cable CBL P20 2 4 dB 20 RTNC to RTNC Plenum Cable CBL P20 PL 2 4 dB 25 RTNC to RTNC Cable CBL P25 3 0 dB ...

Page 29: ...Firmware Overview 29 Firmware Overview The following section provides detailed description of the M6e firmware components Boot Loader Application Firmware Custom On Reader Applications ...

Page 30: ...etrieving 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 M6e bootloader should effectively be invisible to the user The M6e is by default configured to auto boot into application firmware and for any operations that require the module be in bootloader mode the MercuryAPI will ...

Page 31: ...grammers Guide and the MercuryAPI SDK available on the ThingMagic website Upgrading the M6e New features developed for the M6e are made available to existing modules through an Application Firmware upgrade along with corresponding updates to the MercuryAPI to make use of the new features Firmware upgrades can be applied using the MercuryAPI to build the functionality into custom applications or us...

Page 32: ... support installing customer applications on the reader Continuous reader tag streaming scripting and other methods of configuring the module to operate in an autonomous or semi autonomous reading modes maybe supported through the MercuryAPI but custom application cannot be installed on the module ...

Page 33: ...Communication Protocol 33 Communication Protocol The following section provides an overview of the low level serial communications protocol used by the M6e ...

Page 34: ...ws for each command to have its own timeout because some commands require more time to execute than others The host must manage retries if necessary The host must keep track of the state of the intended reader if it reissues a command Host to Reader Communication Host to reader communication is packetized according to the following diagram The reader can only accept one command at a time and comma...

Page 35: ...t in format from the Request Packet CCITT CRC 16 Calculation The same CRC calculation is performed on all serial communications between the host and the reader The CRC is calculated on the Data Length Command Status Word and Data bytes The header is not included in the CRC Header Data Length Command Data CRC 16 Checksum Hdr Len Cmd CRC HI CRC LO 1 byte 1 byte 1 byte 2 bytes Status Word Status Word...

Page 36: ...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 For more information on the MercuryAPI see the MercuryAPI Programmers Guide and the MercuryAPI SDK available on the ThingMagic website ...

Page 37: ...ctionality of the Mercury6e 37 Functionality of the Mercury6e The following section provides detailed descriptions of the M6e features and functionality that are supported through the use of the MercuryAPI ...

Page 38: ...cts 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 Since this can take several milliseconds it is possible that tags are powered off during a frequency hop In addit...

Page 39: ...For example In the NA region setting a frequency of 902 999 kHz results in a setting of 902 750 kHz When setting the frequency of the module any frequencies outside of the valid range for the specified region are rejected Frequency Hop Table The frequency hop table determines the frequencies used by the M6e when transmitting The hop table characteristics are Contains up to 62 slots Valid frequenci...

Page 40: ...000 6C profiles including the ability to specify the Link Frequency encoding schemes Tari value and modulation scheme The protocol options are set in the MercuryAPI Reader Configuration Parameters reader gen2 The following table shows the supported combinations ISO 18000 6C Protocol Options Backscatter Link Frequency kHz Encoding Tari usec Modulation Scheme Notes 250 Miller M 8 12 5 PR ASK 250 Mil...

Page 41: ...ated as such I PX tags are fixed to one of the two frequencies and cannot communicate on the other unlike ISO 18000 6B C tags which can operate under multiple profiles ISO 18000 6B Protocol Configuration Options The M6e supports multiple ISO 18000 6B profiles including the ability to specify the Return Link Frequency encoding Forward Link Rate and modulation scheme The protocol options are set in ...

Page 42: ...es In order to enable automatic multiplexer port switching the module must be configured to use Use GPIO as Antenna Switch in reader antenna portSwitchGpos Once the GPIO line s usage has been enabled the following control line states are applied when the different Logical Antenna settings are used The tables below show the mapping that results using GPIO 1 and 2 for multiplexer control as is used ...

Page 43: ...enna settings which can be used ONLY GPIO 1 Used for Antenna Switching Logical Antenna Setting GPIO Output 1 State GPIO Output 2 State Active M6e Physical Port 1 Low Low J1 2 Low Low J2 3 Low Low J3 4 Low Low J4 5 Low High J1 6 Low High J2 7 Low High J3 8 Low High J4 9 High Low J1 10 High Low J2 11 High Low J3 12 High Low J4 13 High High J1 14 High High J2 15 High High J3 16 High High J4 Logical A...

Page 44: ... J4 active ONLY GPIO 2 Used for Antenna Switching Port Power and Settling Time The M6e allows the power and settling time for each logical antenna to be set using the reader configuration parameters reader radio portReadPowerList and 3 Low J3 4 Low J4 9 High J1 10 High J2 11 High J3 12 High J4 Logical Antenna Setting GPIO Output 2 State Active M6e Physical Port 1 Low J1 2 Low J2 3 Low J3 4 Low J4 ...

Page 45: ...ttings are defined does not affect search order Note Settling time is the time between the control lines switching to the next antenna setting and RF turning on for operations on that port This allows time for external multiplexer s to fully switch to the new port before a signal is sent if necessary Default value is 0 ...

Page 46: ...uryAPI Reader Read and Reader StartReading by default the M6e streams the tag results back to the host processor This means that tags are pushed out of the buffer as soon as they are processed by the M6e and put into the buffer The buffer is put into a circular mode that keeps the buffer from filling This allows for the M6e to perform continuous search operations without the need to periodically s...

Page 47: ... was read on Antenna ID Timestamp The time the tag was read relative to the time the command to read was issued in milliseconds If the Tag Read Meta Data is not retrieved from the Tag Buffer between read commands there will be no way to distinguish order of tags read with dif ferent read command invocations Tag Data When reading an embedded TagOp is specified for a Read Plan the TagReadData will c...

Page 48: ... only intended for use in cases where power consumption is not an issue This is the default Power Mode at startup Power Mode 1 This mode may add up to 50 ms of delay from idle to RF on when initiating an RF operation It performs more aggressive power savings such as automatically shutting down the analog section between commands and then restarting it whenever a tag command is issued Power Mode 2 ...

Page 49: ...when used with other M6e or similar DRM compliant readers and is fully compliant with the Gen2 DRM spectral mask Power Save Mode non DRM Compliant This mode reduces the power consumption during RF operations but is not 100 compliant with the DRM spectral mask This can result increased interference with other readers and reduce overall systems performance ...

Page 50: ...ent causes Event Response Times Start Command Event End Event Time msecs Notes Power Up Application Active with CRC check 800 This longer power up period should only occur for the first boot with new firm ware Power Up Application Active 100 Once the firmware CRC has been veri fied subsequent power ups do not require the CRC check be performed saving time Tag Read RF On 20 When in Power Mode 0 Tag...

Page 51: ...estore Configuration The M6e supports saving module and protocol configuration parameters to the module flash to provide configuration persistence across boots See the MercuryAPI Programmers Guide and sample applications for details on saving and restoring reader configuration ...

Page 52: ...Save and Restore Configuration 52 Functionality of the Mercury6e ...

Page 53: ...umber of arguments in the message the reader returns this message Solution Make sure the number of arguments matches the data length Fault Message Code FAULT_MSG_WRONG_NUMBER_OF_DATA 100h 100h FAULT_INVALID_OPCODE 101h 101h FAULT_UNIMPLEMENTED_OPCODE 102h 102h FAULT_MSG_POWER_TOO_HIGH 103h 103h FAULT_MSG_INVALID_FREQ_RECEIVED 104h 104h FAULT_MSG_INVALID_PARAMETER_VALUE 105h 105h FAULT_MSG_POWER_TO...

Page 54: ...e 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 This does not mean that they always will do this since ThingMagic reserves the right to modify those commands at anytime Solution Check the documentation for the o...

Page 55: ...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 If the module receives a message with an antenna value other than 1 to 4 it returns this error Solution Make sure the host...

Page 56: ... FAULT_UNIMPLEMENTED_FEATURE 109h Cause Attempting to invoke a command not supported on this firmware or hardware Solution Check the command being invoked against the documentation 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 ...

Page 57: ...rrupted during the transfer or corrupted for some other reason To fix this problem reload the application code in flash FAULT_BL_INVALID_APP_END_ADDR 201h Cause When the application firmware is loaded the reader checks the image stored in flash and returns this error if the last word stored in flash does not have the correct address value Solution The exact reason for the corruption could be that ...

Page 58: ...magic com FAULT_FLASH_BAD_WRITE_PASSWORD 301h Cause A command was received to write some part of the flash but the password supplied with the command was not correct 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 Message Code FAULT_FLASH_BAD_ERASE_PASSWORD 300h 300h FAULT...

Page 59: ...sword not matching 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_WRITE_TO_NON_ERASED_AREA 304h Cause The module received a write flash command to an area of flash that was not previously erased Solution When this occurs make note of the operations you were executin...

Page 60: ... 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 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 ...

Page 61: ...07h 407h FAULT_PROTOCOL_INVALID_WRITE_DATA 408h 408h FAULT_PROTOCOL_INVALID_ADDRESS 409h 409h FAULT_GENERAL_TAG_ERROR 40Ah 40Ah FAULT_DATA_TOO_LARGE 40Bh 40Bh FAULT_PROTOCOL_INVALID_KILL_PASSWORD 40Ch 40Ch FAULT_PROTOCOL_KILL_FAILED 40Eh 40Eh FAULT_PROTOCOL_BIT_DECODING_FAILED 40Fh 40Fh FAULT_PROTOCOL_INVALID_EPC 410h 410h FAULT_PROTOCOL_INVALID_NUM_DATA 411h 411h FAULT_GEN2 PROTOCOL_OTHER_ERROR 4...

Page 62: ...rameters are set up correctly The best way to check this is to try few tags of the same type to rule out a weak tag If none passed then it could be SW configuration such as protocol value antenna and so forth or a placement configuration like a tag location FAULT_NO_PROTOCOL_DEFINED 401h Cause A command was received to perform a protocol command but no protocol was initially set The reader powers ...

Page 63: ...ed The write command passed but the lock did not This could be a bad tag Solution Try to write a few other tags and make sure that they are placed in the RF field FAULT_PROTOCOL_NO_DATA_READ 404h Cause A command was sent but did not succeed Solution The tag used has failed or does not have the correct CRC Try to read a few other tags to check the HW SW configuration FAULT_AFE_NOT_ON 405h Cause A c...

Page 64: ...heck the documentation for the supported commands and protocols FAULT_PROTOCOL_INVALID_WRITE_DATA 408h Cause An ID write was attempted with an unsupported incorrect ID length Solution Verify the Tag ID length being written FAULT_PROTOCOL_INVALID_ADDRESS 409h Cause A command was received attempting to access an invalid address in the tag data address space Solution Make sure that the address specif...

Page 65: ...t 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 Solution Check the size of the data value in the message sent to the reader FAULT_PROTOCOL_INVALID_KILL_PASSWORD 40Ch Cause An incorrect kill password was received as part of the Kill command Solution Check the password FAULT_PROTOCOL_KILL_FA...

Page 66: ... fault can occur if the read write lock or kill command fails Solution Check the EPC value that is being passed in the command resulting in this error FAULT_PROTOCOL_INVALID_NUM_DATA 411h Cause This error is used by the GEN2 module indicating invalid data has been specified for an operation This fault can occur if the read write lock or kill command fails Solution Check the data that is being pass...

Page 67: ...o in the command resulting in this error FAULT_GEN2 PROTOCOL_MEMORY_LOCKED 424h Cause This is an error returned by Gen2 tags The specified memory location is locked and or permalocked and is either not writable or not readable Solution Check the data that is being written and where its being written to in the command resulting in this error Check the access password being sent FAULT_GEN2 PROTOCOL_...

Page 68: ...at 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 M6e when no more error information is available about why the operation failed Solution Check the data that is being written and where its being written to in the command resulting in this error Try with a diffe...

Page 69: ...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 If supported by the region of operation turn LBT off FAULT_AHAL_TRANSMITTER_ON 502h Cause Checking antenna status while CW is on is not allowed Solution Do not perform antenna checking when CW is turned on FAULT_ANTENNA_NOT_CONNECTED 503...

Page 70: ...module Reduce duty cycle Add heat sink Use Power Save Mode non DRM Compliant FAULT_POOR_RETURN_LOSS 505h Cause The module has detected a poor return loss and has ended RF operation to avoid module damage Solution Take steps to resolve high return loss on receiver Make sure antenna VSWR is within module specifications Make sure antennas are correctly attached before transmitting Check environment t...

Page 71: ...Analog Hardware Abstraction Layer Faults Appendix A Error Messages 71 Solution Use the correct antenna setting or change the reader configuration ...

Page 72: ...ding Solution Send a testcase reproducing the behavior to support thingmagic com FAULT_TAG_ID_BUFFER_FULL 601h Cause The tag id buffer is full Solution Send a testcase reproducing the behavior to support thingmagic com 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 Fault Message Code FAULT_TAG_ID...

Page 73: ...oducing 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 com ...

Page 74: ...ng 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 ...

Page 75: ...eled USB if on Windows a few installation steps are required for Windows to recognize the M6e and properly configure the communications protocol In order to use the USB interface with Windows you must have the m6eultra inf file included in the M6e alpha package sent The installation steps are 1 Plug in the USB cable to the M6e devkit and PC 2 Windows should report is has Found New Hardware Mercury...

Page 76: ... compatibility warnings will be displayed These can be ignored and clicked through 7 A COM port should now be assigned to the M6e If you aren t sure what COM port is assigned you can find it using the Windows Device Manager a Open the Device Manager located in Control Panel System b Select the Hardware tab and click Device Manager c Select View Devices by Type Ports COM LPT The device appears as M...

Page 77: ...nect the reader change the region and then Initialize Reader to change this value The protocol search display is only updated when one of the Read buttons is pressed not when the choice is made via the pull down menu Read on all connected antennas automatically activates antenna detection and will ignore ports with an undetectable antenna To read on these ports the antenna port must be explicitly ...

Page 78: ...Demo Application 78 Appendix B Getting Started Devkit ...

Reviews:

No comments

Brands by name

Popular brands

Load more brands