Mercury®5e-Class Embedded Modules User Guide
Mercury5e-Class Embedded Modules User Guide
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-totime.
Communication Regulation Information Communication Regulation Information EMC FCC 47 CFR, Part 15 Industrie Canada RSS-210 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.
Communication Regulation Information Note In the event that these conditions can not be met (for certain configurations or colocation 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 re-evaluating the end product (including the transmitter) and obtaining a separate FCC authorization.
Communication Regulation Information 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.
Contents Communication Regulation Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .i Federal Communication Commission Interference Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i User Manual Requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .ii End Product Labeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Loading FW and Using the Flash Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Working with Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Tag Operations Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Write Tag ID. . . . . . . . . . . .
FAULT_UNIMPLEMENTED_FEATURE - (109h) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FAULT_INVALID_BAUD_RATE - (10Ah) . . . . . . . . . . . . . . . . . . . .
Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 FAULT_INVALID_PROTOCOL_SPECIFIED – 402h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FAULT_GEN2 PROTOCOL_INSUFFICIENT_POWER - 42Bh. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 FAULT_GEN2 PROTOCOL_NON_SPECIFIC_ERROR - 42Fh . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 FAULT_GEN2 PROTOCOL_UNKNOWN_ERROR - 430h . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Analog Hardware Abstraction Layer Faults. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 1: Introducing the Mercury Embedded Reader About the Readers The ThingMagic® Mercury® embedded readers are RFID engines that you can integrate with other systems to create RFID-enabled products. A comprehensive user interface called the Reader Assistant provides screens to read from and write to tags. In addition, there are screens for adding firmware and debugging. This guide explains how to set up the reader to read and write to tags.
Product Line Overview Product Line Overview The embedded modules were designed to be incorporated into wide variety of products. The M4e is a general purpose, multi-protocol embedded reader. It utilizes a software (SW) radio architecture that allows the M4e to read all current existing RFID protocols, as well as being able to upgrade the firmware (FW) to read new protocols as they are designed. The M5e is a small form-factor, low power, low cost Gen2 module.
Software for the Reader Boot Loader The boot loader provides low-level functionality. This program provides a customer interface for upgrading the application firmware and storing data into flash. When a module is powered up or reset, the boot loader code is automatically copied from sector 0 of flash into the Microprocessor’s on-chip RAM, and executed.
Chapter 2: Setting Up the Reader Attaching the Antenna The antenna cable is attached to the Mercury5e or M5e-Compact reader at J2. The other end of the cable is attached to the antenna. Use the following procedure to connect a monostatic antenna to the reader.
Attaching the Antenna To attach a monostatic antenna: 1. Connect one end of the coax cable to the antenna. Antenna Coax cable 2. Connect the other end of the cable to J 2.
Powering Up the Reader 3. Attach a terminator to the open antenna port. When using a monostatic antenna, terminate the unused port (on the M5e) before the reader is powered on. If no terminator is available, a 3 dB attenuator can be substituted. ! C A U T I O N ! ! An unterminated antenna port can be damaged, if it is powered on. Powering Up the Reader After connecting the antenna and terminating the extra antenna, you can power up the reader. To power up: 1.
Powering Up the Reader 2. Attach a power supply into the reader’s electrical connection. 3. Connect the power supply to a 100–240 VAC power outlet. The reader begins to power up. Continue with the next chapter to start reading tags.
Chapter 3: Using the Reader Assistant The Reader Assistant is a graphical user interface developed to allow you to communicate with the DevKits and Mercury embedded modules. From the Reader Assistant, you can perform the following tasks: Read tags Write to tags Configure the reader Update applications in flash memory Load new firmware If you select Options > Show Advanced Features or press Ctrl+A, the Tag Operations and Debug tabs appear.
Starting the Reader Assistant Starting the Reader Assistant The following procedure explains how to install and activate the Reader Assistant on your computer system. To start the Reader Assistant and set up the serial port: 1. Copy the ReaderAssistant folder from the CD to a computer that is used to connect to the embedded module or run the executable file from the CD. 2. Set up the computer to the embedded module as described in the Mercury Embedded Modules DevKit Set Up Sheet. 3.
Communication Settings Communication Settings You use the Communication Settings screen to set the Com Port and the baud rate. It can also configure the baud rate used by the reader. The Communication Settings screen displays automatically the first time the Reader Assistant is launched. The Communication Settings screen also displays when the application settings file application_settings.dat is deleted. Otherwise, you can access the screen using the following procedure.
Communication Settings Serial Communications Problem If the host computer and the reader lose communications, an alert screen displays that warns you of the problem. The alert displays if the response message fails to arrive after a timeout period or if the response message contains an invalid CRC. .
Menu Commands Menu Commands The menu commands, File, Options, and Action provide additional actions that you can take in the Reader Assistant. File menu The File menu has the following commands: Save Application Settings – Ctrl+S Quit – Ctrl+Q Save Serial Log - Saves the current serial log to a file. Please note the default name for the save file is always offered and no checks are made for overwriting an existing file.
Configuring the Reader Configuring the Reader The Config tab allows you to configure the reader settings. All the settings are displayed in the Serial Log. For information about each setting, see the Config Tab Settings. Note Be sure to set the antenna port before attempting to read tags. Otherwise, the reader cannot read tags.
Configuring the Reader Name Description Advanced Settings Power Save Mode (M5e/M5e-Compact only) Allows you to set power saving modes: 0x00. Full Power Mode – Operates at full power 0x01. Minimal Savings Mode – Saves power without degrading system performance, 10 ms delay. 0x02. Medium Savings Mode – Shuts down analog section between serial commands and restarts when a command is issued, 50 ms delay. 0x03.
Configuring the Reader 4. For M5e/M5e-Compact only, select a User Mode and a Power Mode. Note Select User Mode 01 (Printer) or Gen2 Session=0 for maximum read rate on individual tags. Selecting User Modes where the Gen2 Session=1 (User Modes 00 or 03) may result in a slow single tag read rate.
Reading and Writing to Tags Reading and Writing to Tags The Read/Write tab can be used to quickly read tags to verify that the reader is working correctly. Set up the reader and provide tags to read. See the Mercury Embedded Modules DevKit Set Up Sheet provided with the DevKit. When you are connected, the reader type shows in the top field.
Reading and Writing to Tags To read tags from the Read/Write tab: 1. Click Start Reading Tags. The reader reads the tags and starts to display the EPCs and the running total number of times each EPC has been read (Reads) in the Read/Write screen. A yellow background is displayed with the date and timestamp as each tag is read. The most recently read tags display white backgrounds. The background gets darker as the time from when the tags were last read gets longer. See tag 6. 2.
Reading and Writing to Tags Advanced Settings You can access additional functionality by clicking Advanced. The functions include setting the search time, changing the font size, and writing to tags. To use advanced features: 1. Click Advanced. The following additional functions appear on the Read/Write screen. 2. Type a new value in the Search Time field to change the time in milliseconds. 3. Click the Font Size drop-down menu to change the size of the font in the screen. 4.
Reading and Writing to Tags b. Click Write Tag. A dialog opens to verify the tag id you want written. c. Click OK.
Serial Log Serial Log You can open a panel in any screen to display the Serial Log. To access the Serial Log, select Options > Show Serial Log. Note To save the current Serial Log to a file selct File > Save Serial Log.
Loading FW and Using the Flash Area Loading FW and Using the Flash Area The Firmware tab restarts the reader when it is selected. You can load the latest firmware from this screen. With the Advanced settings, you can read and write to the user flash area. There are three main functional sections within this tab. System Configuration section – displays version information from the reader. Application Image section – loads the FW image in one step.
Loading FW and Using the Flash Area Note If you have selected the Bootloader radio button under User Flash Area, all other Reader Assistant tabs will be disabled. You must select the Application radio button to re-enabled the other tabs.
Loading FW and Using the Flash Area The following table explains the Firmware tab settings: Firmware Tab Settings Name Description Bootloader Version The latest Bootloader installed. Gets the version number from the reader. Firmware Version The most recent installed firmware. Gets the version number from the reader Hardware Version The version of the hardware when it was built. Gets the version number from the reader. Firmware Date Date that the latest firmware was installed.
Working with Tags To modify the user flash area: 1. Click the Bootloader radio button to access the bootloader program. The user flash area is only accessible from the bootloader. 2. Click Read User Flash to populate the table with the contents of the flash. 3. To modify the flash contents, follow these steps: 4. a. Enter different byte values in the cells of the table. b. Click Modify User Flash to commit the modifications to the user flash area on the reader.
Working with Tags Chapter 3: Using the Reader Assistant 25
Working with Tags The following table explains the Tag Operations tab settings: Tag Operations Tab Settings Grouping Name Description Universal Time out (msec) Timeout for all commands that require it.
Working with Tags Grouping Name Description Tag Data Tag Data Data bytes, in hex, to be written to a tag when “Write Data” button is pressed. Address Start location within memory bank for “Read Data” or “Write Data” functions, in words. Maximum of 4 bytes (8 hex digits). Mem Bank Drop-down select of memory bank to be written to or read. Password 4 byte password, in hex, to be entered if needed for “Read Data” or “Write Data” operations. If not needed (tag is not locked), leave as “0”.
Working with Tags Grouping Name Description Read Tag IDs Read Single button Press to display the EPC of the first tag that responds. If the maximum EPC size is 496 bits and the tag has an EPC longer than 96 bits the tag will be read, but only the first 96 bits are displayed in the results field. Read Multiple button When pressed, information from all tags that respond will be collected and displayed until the Timeout expires. Metadata is also displayed if the ‘Retrieve Metadata’ checkbox is selected.
Working with Tags Reading Tag Data The following procedure explains how to read tag data. To read tag data: 1. Type an address location in the Address field. 2. Choose a selection from the Mem Bank menu. 3. Click Read Data and the information is shown in the Read Tag IDs field. Writing Tag Data First determine whether the first tag to respond will be written to or whether the first tag matching the Select criteria is to be written to, based on the Select Criteria Mem Bank selection.
Working with Tags 1. Enter the data to be compared in bytes 2. Enter the starting address bit offset from the start of memory in hex (4 bytes maximum) 3. Enter the length, in bits, of the portion of the data to be compared, as an integer. Only the portion of the data specified by the length will be compared. (“0” will always match). The length cannot exceed the entered data length. EPC Mem (04): Used to write to a tag selectively based on the any portion of the EPC memory contents of the tag.
Working with Tags Locking Tags The Lock tag area of the Tag Operations tab locks a specific address in the tag data section. To lock a tag: 1. Type the 32-bit password that allows you to lock the tag. If a password is not set in the tag, type 0. 2. Set the Mask Bit field as described in the Mercury Embedded Developer’s Guide: Lock Tag (25h). 3. Set the Action Bit field. 4. Click Lock Tag to lock the data in the tag.
Working with Tags Reading Tags The M5e reader can use the settings in the Tag Operations tab to read the tag EPCs and retrieve the tag read metadata. You can read a single tag or multiple tags. To read tags: 1. Type in the amount of time in which you want the reader to read tags. 2. To read a single tag, click Read Single. 3. To read multiple tags, click Read Multiple. The tag ids are displayed in the text field.
Debugging the Module Debugging the Module The Debug tab sends serial commands to the reader using hexadecimal format. You can also add scripts containing sequences of commands to the Script Contents panel. Note Write the scripts in a text editor and then add them to the New Command Scripts list. If you do not see the Debug tab, press Ctrl+A.
Debugging the Module Debug Tab Settings Name Description Send a Hexadecimal Command to Reader field Enter the command you want to send in hex format. Send Command button Click to send the command. Hex Command Scripts Lists the scripts that you added to the screen. Script Quick-run buttons Select a script and right-click a button to add the script to that button. Note: If you are running two scripts frequently, this is a quick way of selecting the two scripts to run.
Debugging the Module 2. Type the script within the panel and click Save. A Save as dialog opens and you can save your script. 3. To change the script, click Modify. 4. To run the script, right click a Script Quick-run button to attach the script to the button.
Debugging the Module 5. Click the Script Quick-run button to run the script. After the script is finished running, the following dialog appears. 6. Click OK and the results appear in the Serial Log panel. 7. To see the results from the Send a Hexadecimal Command to Reader field or to execute the Hex Command Script, select Action > Re-Synch Application and Reader.
Chapter 3: Using the Reader Assistant 37
38
Appendix A: Hardware Details This Appendix details the mechanicals for the embedded modules and also provides pin 1 locations for the M5e and M5e-Compact serial connectors. Mechanicals The following figures detail the hardware layouts that comprise the Mercury Embedded Modules.
Mechanicals M5e Mechanicals A-40
Mechanicals M5e-Compact Mechanical Antenna Connector The M5e has two MMCX connectors and the M5e-Compact has one MMCX connector for interfacing to the antennas. Communications Connector The communications interface on the modules provides power, serial communications signals, and access to the GPIO inputs and outputs.
Mechanicals Pin-out of the 12-pin digital connector Pin # Signal 1 +5V 2 +5V 3 GND 4 GND 5 Digital Output 1 6 Digital Output 2 7 Digital Input 1 8 Digital Input 2 9 RS-232 RX from host 10 RS-232 TX to host 11 Mfg test purposes 12 Mfg test purposes The following figure shows the diagrams of the M5e, and M5e-Compact communications interface as you face the boards..
Mechanicals Note The flat ribbon cable that connects with the communications interface on the M5e and M5e-Compact embedded modules is available from Parlex, Part Number: 100R12-152B; and can be purchased from standard electronic component suppliers.
Mechanicals A-44
Appendix B: Error Messages The following error codes were incorporated into the reader for help in locating errors. Common Error Messages The following table lists the common faults discussed in this section.
Common Error Messages FAULT_INVALID_OPCODE – (101h) Cause The opCode received is invalid or not supported with the current version of code. Solution Check the documentation for the opCode the host sent and make sure it is supported. 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.
Common Error Messages 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 two antennas, 1 and 2.
Common Error Messages 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 a Set Baud Rate (0x06h) command is issued for 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. Send the baud rate in the hex format.
Bootloader Faults 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 a Verify Image CRC (0x08), or Boot Firmware (0x02) command is issued, 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 Flash Faults The following table lists the common faults discussed in this section.
Flash Faults FAULT_FLASH_UNDEFINED_ERROR – 302h Cause This is an internal error and it is caused by a software problem in module. Solution Contact support at 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. Solution Make sure that you have the correct password for the flash sector.
Flash Faults Solution If the data spans two sectors, separate the data into two messages. 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 Verify that the data being sent is an even number of bytes.
Protocol Faults Protocol Faults The following table lists the common faults discussed in this section.
Protocol Faults 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. 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.
Protocol Faults 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. 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 Read Tag ID or Data command was sent but did not succeed. Solution The tag used has failed or does not have the correct CRC.
Protocol Faults 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. FAULT_PROTOCOL_INVALID_WRITE_DATA – 408h Cause In EPC0+, the first two bits determine the tag ID length. If the first two bits are 0b00, then the tag ID must be 96-bits. Otherwise the tag ID is 64 bits.
Protocol Faults FAULT_GENERAL_TAG_ERROR – 40Ah Cause This error is used by the M5e 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 Solution Check tag is in RF field and the kill password.
Analog Hardware Abstraction Layer Faults Analog Hardware Abstraction Layer Faults FAULT_AHAL_INVALID_FREQ – 500h Cause A command was received to set a frequency outside the specified range. For example, in North America the frequency range is from 902 MHz to 928 MHz. Solution Check the values you are trying to set and be sure that they fall within this range. FAULT_AHAL_INVALID_FREQ – 501h Cause With LBT enabled an attempt was made to set the frequency to an occupied channel.
Tag ID Buffer Faults 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 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 Report this problem to ThingMagic at http://support.thingmagic.com. FAULT_TAG_ID_BUFFER_NUM_TAG_TOO_LARGE – 603h Cause The module received a request to retrieve more tags than is supported by the current version of the software.
System Errors System Errors FAULT_SYSTEM_UNKNOWN_ERROR – 7F00h Cause The error is internal. Solution Make note of the operations you were executing and contact ThingMagic at http:// support.thingmagic.com. FAULT_TM_ASSERT_FAILED – 7F01h Cause An unexpect Internal Error has occured. 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 contact ThingMagic at support@thingmagic.com.
Appendix C: Antennas Authorized Antennas The following table contains the antennas authorized by the FCC for use with the Mercury5e and M5e-Compact embedded modules. Detailed information for each is available from their respective manufacturers.
Authorized Antennas 64
End User License and Warranty Agreement YOU SHOULD CAREFULLY READ THE FOLLOWING TERMS AND CONDITIONS OF THIS THINGMAGIC END USER LICENSE AND WARRANTY AGREEMENT (“AGREEMENT”) BEFORE USING THE PRODUCTS WHICH ARE ENCLOSED OR OTHERWISE ASSOCIATED WITH THIS AGREEMENT. USE OF THE PRODUCTS MEANS THAT YOU ARE BINDING YOU AND THE COMPANY YOU REPRESENT TO THIS AGREEMENT.
b. Limitations on Modification: You may not copy, modify, adapt, or translate the Firmware, or create derivative works based on the Firmware. c. Limitations on Reverse Engineering, Decompilation and Disassembly: You may not reverse engineer, decompile, or disassemble the Products, except and only to the extent that such activity is permitted by applicable law notwithstanding this limitation. d.
drawings set forth in the Documentation. If the Products fail to meet this warranty, ThingMagic (at its sole option) will either replace or repair the nonconforming Product. If neither of those can be done on a commercially reasonable basis, ThingMagic may, at its sole option, pay you an amount based on depreciation of the Product over a three (3) year useful life.
b. Electronic Toll and Traffic Management means the market for equipment and services which allow for toll collection and traffic monitoring utilizing vehicles equipped with RFID transponders, wireless communication, in road / roadside sensors, and a computerized system (hardware and software) to uniquely identify each vehicle, electronically collect the toll, and provide general vehicle / traffic monitoring and data collection. c.
Index A Analog Hardware Abstraction Layer Faults 59 application firmware 3 B boot loader 3 features 3 Bootloader error messages 49 BootLoader tab settings 23 Bootloader tab 21 C common fault messages 45 communications interface 41 D Demo feature 16 Demo tab read tags 17 E error messages bootloader 49 common 45 FAULT_AFE_NOT_ON 55 FAULT_AHAL_INVALID_FREQ 59 FAULT_BL_INVALID_APP_END_ADD R 49 FAULT_BL_INVALID_IMAGE_CRC 49 FAULT_DATA_TOO_LARGE 57 FAULT_FLASH_BAD_ERASE_PASSW ORD 50 Index FAULT_FLASH_BAD_WRI
Index _TOO_LARGE 61 FAULT_TAG_ID_BUFFER_REPEATED _TAG_ID 61 FAULT_UNIMPLEMENTED_OPCODE 46 FAULT_WRITE_PASSED_LOCK_FAIL ED 55 F fault messages 45 FAULT_AFE_NOT_ON 405h 55 FAULT_AHAL_INVALID_FREQ 500h 59 FAULT_BL_INVALID_APP_END_ADDR 201h 49 FAULT_BL_INVALID_IMAGE_CRC 200h 49 FAULT_DATA_TOO_LARGE 40Bh 57 FAULT_FLASH_BAD_ERASE_PASSWO RD 300h 50 FAULT_FLASH_BAD_WRITE_PASSWO RD 301h 50 FAULT_FLASH_ILLEGAL_SECTOR 303h 51 FAULT_FLASH_UNDEFINED_ERROR 302h 51 FAULT_FLASH_WRITE_TO_NON_ERAS ED_AREA 304h 51 FAULT_GE
Index L Lock tag area 31 M M4e description 2 M5e description 2 GUI 3 M5e Mechanicals 40 M5e-C GUI 3 M5e-C description 2 P Protocol faults 53 R read tag data 29 read the tag identifications 32 Reader Config tab 13 settings 13 reader settings configure 13 Index Regulatory Compliance i RFID engines 1 S software application firmware 2 bootloader 2 System errors 62 T Tag ID buffer faults 60 Tagops tab 24 kill tags 30 lock tag 31 read tags 32 settings 26 write tag ids 28 ThingMagic® Mercury® Embedded Modu
