MARS TOHKEN SOLUTION FRU4100Q Users Manual

FRU-4100Q/FRU-4100QJ

UHF RFID Reader Module

User Manual

Version 1.0

Chapter 1

Table of Contents

Chapter 1 .............................................................................................................................. 3

Introducing the FRU-4100Q/FRU-4100QJ ............................................................................. 3

UHF RFID Reader Module ....................................................................................................... 3

Package Content .................................................................................................................... 5

Tour of the FRU-4100Q/FRU-4100QJ UHF RFID Reader Module ......................................... 6

Installing the IndyTool ........................................................................................................... 7

Connecting the FRU-4100Q/FRU-4100QJ to a PC ............................................................... 8

Chapter 2 ............................................................................................................................ 12

Introduction .......................................................................................................................... 12

Indy Tool General Usage ...................................................................................................... 12

IndyTool Functions .............................................................................................................. 16

Chapter 3 ............................................................................................................................ 32

Introduction .......................................................................................................................... 32

Tracer Installation .................................................................................................................. 32

Tracer Usage ......................................................................................................................... 33

Known Issues ....................................................................................................................... 58

Federal Communications Commission (FCC) Statements: .................................................. 59

ii

Hardware Overview

Introducing the FRU-4100Q/FRU-4100QJ
UHF RFID Reader Module

FRU-4100Q/FRU-4100QJ is a high-performance UHF RFID reader module based on
Impinj R2000 chip and compliant with EPC C1 Gen2 / ISO 18000-6C and FCC modular
approval requirements. System Integrators, RFID device makers could use
FRU-4100Q/FRU-4100QJ to develop their own products with the benefits of cost­efficiency and high-performance.
FRU-4100Q/FRU-4100QJ supports dense reader mode (DRM), anti-collision, and Listen­Before- Talk (LBT) features. FRU-4100Q/FRU-4100QJ has an operating distance up to 9
meters when its adjustable TX power is set to 30 dBm with a 6 dBi antenna. In addition,
FRU-4100Q/FRU-4100QJ is small and ideal for adding UHF RFID read/write capabilities to
a wide range of products and solutions such as handheld PDA, label printers, stationary
readers, or any other device for UHF RFID applications. FRU-4100Q/FRU-4100QJ uses
Serial and USB interfaces to connect to an external processor board or PC host.

Chapter 1

Features

‧

Support for EPC C1 Gen2 / ISO 18000-6C tag protocol with anti-collision, DRM and

‧

Listen-Before-Talk features

‧

Adjustable transmit output level control from 5 dBm to 30 dBm in 1 dB step

‧

Maximum tag read rate of over 100 tags per second

‧

Maximum tag read distance of over 27 feet (9 m) with 6 dBi antenna

3

Protocol

Architecture

Power

Interface

RF

Performance

Compliance

Physical

Specifications

RFID EPCglobal Gen 2 (ISO 18000-6C), DRM
RFID ASIC IMPINJ R2000
Voltage 5V VDC

Current Consumption

Scan Mode : 1.5 A (Max),
Idle Modes : 0.33 A (Typical)

Connector

20-pin (ZIF FPC 0.5mm connector )
UART Baud rates: 9,600 to 115,200 bps, Logic levels: 3.3 / 5 V
USB USB 2.0 Full Speed (12 Mbps)
GPIO 4 GPIO pins, Logic levels: 3.3 / 5 V
API Interface Impinj

Antenna Connector

Four MMCX antenna connectors supporting 4 mono-

static antennas, with VSWR less than 2:1
Frequency

FCC(US)902-928MHz :FRU-4100Q

TELEC(Japan)916.8-920.4MHz:FRU-4100QJ

TX power Adjustable from 5 dBm to 30 dBm @ +/-1 .0 dBm accuracy
Frequency Stability ±20 ppm
Harmonic performance under 65.0dBc
Modulation Depth 90% nominal
Data Encoding FM0 or Miller code
Bit Rate Supports uplink data rates of up to 640 Kbps

Tag Read Rate Over 400 tags/second
Inventory Reliability Through anti-collision
Tag Read Distance 27 feet (9m) with a 6 dBi antenna (36 dBm EIRP)

Regulatory Certification obtained : FCC 47 CFR Ch. 1 Part 15 , TELEC

Environmental Compliance

Temperature Range
Humidity 10% ~ 85% Non-condensing

Shock & Vibration TBD
Dimensions

Operating: -20 to +60 degree C,

Storage: -30 to + 85 degree C

92.5mm ( L ) X 63mm ( W ) x 4.5 mm ( H )

4

Package Content

FRU-4100Q/FRU-4100QJ UHF RFID Reader Module

The following equipment is used in the description of this document.

The following devices are sold separately. It is not included in FRU-4100Q/FRU-4100QJ module.

RS232 Cable Power Adaptor

Interface board USB Cable

Antenna RFID Tag

5

Tour of the FRU-4100Q/FRU-4100QJ UHF
RFID Reader Module

This section describes the main components and features of the
interface board(selling separately; not included inFRU-4100Q/FRU­4100QJ).

Debug Port

UART Port

Mini USB Port

Power Inlet

6

Installing the IndyTool

First of all, install the IndyTool before connecting the interface board to a PC. It is possible for
multiple versions of IndyTool to co-exist on a single system, so long as a unique install path
is used for each, such as the default installation directory.

Installation Procedure

1.

Double click the IndyTool installer file, IndyTool v2.4.2.msi, to launch the installation wizard.

2.

When prompted, designate the desired installation directory. The default is:

[Program Files]\IMPINJ\IndyTool v2.4.2

3.

Installation includes the C++ runtime libraries and adds a desktop shortcut to the
IndyTool application.

4.

To Start the IndyTool application:

a.

Double click the desktop shortcut, or

b.

Use the Start Menu. For example, if installed to the default directory:
Click Start, select All Programs, IMPINJ, Impinj IndyTool v2.4.2, and click IndyTool.

c.

Open the IndyTool installation folder and double click IndyTool.exe.

7

Connecting the FRU-4100Q/FRU-4100QJ to a PC

Before operating the Indy tool software for development of the RFID device,
follow the steps made below to connect the FRU-4100Q/FRU-4100QJ to a PC.

Interface board, cables, AC adapter, etc. other than FRU-4100Q module are
sold separately.

1.

Install the Indy tool on your PC.

2.

Mount the UHF RFID Module onto the interface board(selling separately;).

Set up the jumper. The jumper settings are defined
below.

8

3.

Connect the interface board to a PC by using a miniUSB cable (default setting) or a RS232

cable, respectively described in options 3a and 3b.

Option a: By using a miniUSB cable

or

cable

Option b: By using a RS232

9

4.

Insert the power connector into the power inlet on the interface board, and then
plug the power adapter into an electrical socket.

5.

Connect antennas to FRU-4100Q/

connect at most 4 antennae at the same time.

6.

Open the IndyTool. Click Start to scan RFID tags by using the FRU-4100Q/FRU­4100QJ

UHF RFID Reader module.

FRU-4100QJ UHF RFID Reader Module. You can

10

Note: The GPIO settings can be turned on optionally by hardware or software, as
illustrated below.
By hardware, push the GPIO switches to the left.

By software, use the IndyTool to turn on the GPIO settings. The General purpose GPIO can be
configured as Input or Ouptut and the corresponding state is also reflected. The Refresh
button can be used to update the states of the GPIOs configured as input. The greyed state
boxes reflect the Input State. When configured as GPOs the state becomes user
selectable.

The ARM GPOs can be set Low and High via the ARM GPO control box.

11

IndyTool for Configuration and Development

Introduction

Overview

The IndyTool is a .Net-based graphical user interface (GUI) tool that uses the Indy® RFID
Host Library API to exercise the functionality of the reader platform, a platform that is based
on the Indy chip and firmware.

The IndyTool is dynamically linked to the Indy RFID Host Library. Therefore, there is no need
to install the interface library separately. However, the USB / UART host driver must be
installed prior to using IndyTool.

IndyTool is supported on Windows XP only.
The goal of this document is to explain the operation of the tool. This document does not

explain the underlying RFID functionality that it is controlling via the Indy RFID Host
Library API.

Chapter 2

Indy Tool General
Usage

General Guidelines



IndyTool will not modify the reader state without user intervention. The state of the
reader is only affected when the user executes a function within the application.



Multiple instances of IndyTool can be opened concurrently, however only one reader
in one instance can be connected at any one time.



All user input fields indicate the input type. The label (d) indicates a decimal input. The
label

(h) indicates a hexadecimal input is expected, and if any other characters are
inputted they will be corrected by the application. Unless otherwise specified all the
input fields in the GUI that are marked (h) do not require the 0x prefix.



All user commands are logged in the Status Window and will show continuous
progress or show single command execution depending on the status options.

 If a reader is disconnected or reset without using IndyTool, the application will show

the last known state of the reader and on the next command attempt, the status will
indicate the connection error. To recover, select disconnect, re-enumerate if
necessary, and connect back to the reader.

12

 IndyTool can be connected and disconnected to and from a reader at any time.

This will allow for a user to configure the reader, disconnect and subsequently
run any other application to run the reader.

 The target usage for IndyTool is for Engineering Development. The scope of this

document is to describe the functions in IndyTool and is not meant to describe the
MAC firmware fundamentals, which are a prerequisite to utilizing the system as a
whole.

IndyTool Main Window

The following figure shows the main application window.

Main Application Window

On IndyTool startup, all the readers connected to the system via USB and the indicated COM
port are auto-enumerated. The attached readers are indicated in the status window and a
pull down list is populated from which to select.

If there are no readers connected to the system, this will be displayed in the status window
and there will no readers in the pull down menu. If there is a library exception when starting
up the application or any other error, this will be indicated in the status window.

Status Window

The status window shows the outcome of a user command. All commands and functions will
generate some form of feedback in this window.

1.

Clear Button – Clears the current contents of the status window.

2.

Save Button – Save the current contents of the status window to a specified file.

3.

Skip Button – Skips all current status messages queued up by the application for display.
Under some high message traffic conditions, the status window will queue up messages
for display because it may not be able to keep up with influx of messages. This button will
flush the current queue and indicate in the status window how many messages were
skipped and show the tail end of the message queue.

4.

Remaining– This is count of queued up status messages waiting to be displayed in
the status window. The Skip button is most useful when this count is very large and
can be useful to flush the messages and see the final status in the queue.

5.

Status Options – Special options for controlling the status window:

a.

Keep History – [Checked] Append all status messages. [Unchecked] Clear
status window upon each command operation.

13

b.

<2/18/2010 11:05:49 AM> Inv, 42,

-

78.0, 3000, 11112222CCCCDDDDEEEEFFF

F, 7098

Inv, 42,

-

78.0, 3000, 11112222CCCCDDDDEEEEFFFF, 7098

Inv, 42,

-

78.0, 3000, 11112

222CCCCDDDDEEEEFFFF, 7098

Status Timestamps – [Checked] Show local timestamp on each status
message. [Unchecked] No timestamp.

c.

Read Only – [Checked] Does not allow user to input any text in status window.
[Unchecked] Allows the user to input notes in the status window, which can be
useful when logging data and results.

d.

Large Window Buffer – Increases the size of the window buffer before flushing.

6.

Packet Options – Special options for controlling Indy packet displaying

a.

Decoded Packets – Displays high level decoded packet information.

b.

Raw Packets 8 – Displays raw packet data in bytes.

c.

Raw Packets 32 – Displays raw packet data in 32-bit words.

d.

Packet Timestamps – Displays packet timestamps in milliseconds (when
available in the packet).

Status Timestamps

Decoded Packets

Raw Packets 8

Inv, 42, -78.0, 3000, 11112222CCCCDDDDEEEEFFFF, 7098

T:0005 V:01 F:02 L:0007 [ 45 6A 0A 00 58 6D 04 01 4A FE 00 00 30 00 AA AA BB BB CC CC DD DD EE EE FF FF 4A 5B ]

Raw Packets 32

T:0005 V:01 F:02 L:0007 [ 000A6A45 01046D58 0000FE4A AAAA0030 CCCCBBBB EEEEDDDD 5B4AFFFF ]

Packet Timestamps

[682579] Inv, 42, -78.0, 3000, 11112222CCCCDDDDEEEEFFFF, 7098

The status window will self flush automatically when the status window buffer is full. The
window will indicate how many times it has self flush at the top of the status window. The
current windows buffer if 2^16 characters which is approximately equivalent ot 1500
singulations of 96- bit EPCs. Use the large window buffer option to increase the windows
buffer to 2^22.

The Help Tab contains the decoded packet descriptions for reference. The following is the
summary of the decoded packet formats:


Inv, NB Rssi (d), Rssi (d), PC (h), EPC (h), CRC (h), TID (h)



Access, Command (s), Tag Error (h), Proto Error (h), Write Count (d), Data[] (h)



Debug, Overflow (d), Underflow (d), Data Type (d), Timestamp (d), Id (d), Counter

(d),

Data[] (h)



XY-Pair, Id (d), Calculation Time Us (d), X (d), Y (d), Res0 (d), Res1 (d), Res2 (d), Res3

(d)

Info Bar

The Info Bar indicates when a reader is connected or when no reader is connected. The Info
Bar will also indicate the type of connection either USB or UART.

Enumerate

The Enumerate Button will execute the reader enumeration process. The application will
scan the USB interface and the selected COM port for valid readers. The enumeration is

14

only performed when the application is started and when the user presses this button. If a
new reader is connected after the application is started, the enumeration process must be
executed to control the reader. The reader list will be repopulated when the enumeration is
complete. If the reader is not in the pull down list, check the cable connections to make sure
the reader is connected correctly. Depending on the situation and nature of readers using
the UART port, if the reader is not responding (in UART mode) it is best to shutdown the
application and restart to re-enumerate the radio.

When changing the COM port to enumerate, the application will need to be restarted (as
indicated in the status window) to apply the settings. The RFIDcomm.cfg is used to
configure the COM port to control, and by default (after installation) it is set to COM1.

Connect

The Connect Button will attempt to make a connection to the reader selected in the pull down
menu. Upon a successful connection, a new set of menus will appear as shown in the
following figure. If the reader is not connected successfully, it will be indicted in the status
window and no menus will appear.

After the reader is connected it is queried for its parameters.

1.

Serial Number

2.

Bootloader Version (if available and active)

3.

Mac Firmware Version and CRC

4.

RF Transceiver Info –R1000, R2000, R500

5.

Host To MAC Interface = USB or COMx

6. Build Target – 1 = R1000, 2 = R2000, 3 = R500

7. Region – 0 = FCC, 1 = ETSI, 2 = JAPAN

15

Connect

Serial Number: impinjserialnum01
MAC Version: 2.2.0.240 (CRC FFFFFFFF)
RFTrans Info: R1000 (000C00B0)
Host To MAC Interface: USB
Build Target: 1
Region: FCC (0)

Connect Success

The Info Bar will be updated with the name of the connected Reader and the activated Host
To MAC interface.

Disconnect and Reset

The Disconnect Button will attempt to disconnect from the connected reader. The menus
will disappear and the unconnected state will be indicated. The Reset Button will attempt to
reset the connected reader and will also make the menus disappear.

Cancel and Abort

The Cancel and Abort Button will issue the respective command to Reader when
executing a MAC Command. The status window will indicate the issuing of the command
and the reader will respond accordingly.

IndyTool Functions

These sections describe the functions found in the visible menus when a reader is
successfully connected.

Register Access

The Register Access menu is shown in the following figure.

16

There are five Read/Write Register access types:

1.

MAC – Regular MAC Register

a.

[Read] The read address and count are the inputs. The count indicates how
many consecutive addresses to be read. If the application reaches a register
that is not readable, it will stop reading.

b.

[Write] The write address and data are the inputs. This is single write access.

2.

MAC Bank – Banked MAC Register

a.

[Read] The read address and count are the inputs. The count indicates how many
consecutive addresses to be read. If the application reaches a register that is not
readable it will stop reading. A banked read will detect if the register is a banked
register and display the entire banked contents. If it is not a banked register, the
single value is displayed.

b.

[Write] The write address, data and bank number are the inputs. This is a single
write access. If the address is not banked, an error will be displayed.

3.

Bypass – MAC Bypass Register

a.

[Read] The read address and count are the inputs. The count indicates how
many consecutive addresses to be read. If the application reaches a register
that is not readable it will stop reading.

b.

[Write] The write address and data are the inputs. This is single write access.

4.

OEM – OEM Register

a.

[Read] The read address and count are the inputs. The count indicates how
many consecutive addresses to be read. If the application reaches a register
that is not readable, it will stop reading.

b.

[Write] The write address and data are the inputs. This is single write access.

5.

LinkProfile – Link Profile Transceiver Register

a.

[Read] The read address, count, and profile Id are the inputs. The count indicates
how many consecutive addresses to be read. If the application reaches a register
that is not readable, it will stop reading.

b.

[Write] The write address, profile Id, and data are the inputs. This is single write

access. All the results are displayed in the status window.

Read Register [Mac]

Read Mac [0000] = 020200F0 (Normal RO)

Write Register [Mac]

Write Mac [0003] = 0000FFFF

Read Register [MacBank]

Read Mac [0702][00] = 00000001 (Banked Sel:0701)
Read Mac Register Bank [0702][00] = 00000001
Read Mac Register Bank [0702][01] = 00000000
Read Mac Register Bank [0702][02] = 00000000
Read Mac Register Bank [0702][03] = 00000000
Read Mac Register Bank [0702][04] = 00000000
Read Mac Register Bank [0702][05] = 00000000
Read Mac Register Bank [0702][06] = 00000000
Read Mac Register Bank [0702][07] = 00000000
Read Mac Register Bank [0702][08] = 00000000
Read Mac Register Bank [0702][09] = 00000000
Read Mac Register Bank [0702][0A] = 00000000
Read Mac Register Bank [0702][0B] = 00000000

17

Read Mac Register Bank [0702][0C] = 00000000
Read Mac Register Bank [0702][0D] = 00000000
Read Mac Register Bank [0702][0E] = 00000000
Read Mac Register Bank [0702][0F] = 00000000

Write Register [MacBank]

Write Mac Register Bank Fail [INVALID_PARAMETER]

Write Register [LinkProfile]

Write Link Profile [0100][2] = 0000

Tag Access

The Tag Access menu is shown in the following figure.

The following are the available Tag Access functions:

1.

Read

2.

Write

3.

Kill

4.

Lock

5.

BlockWrite

6.

BlockErase

7.

QT_Read

8.

QT_Write

9.

QT_None

The following are the general inputs to the Tag Access functions:

1.

Memory Bank – The target for the access operation: EPC, TID, User, or Reserved.

2.

Offset – The offset of the first 16-bit word to access from the target memory bank.

3.

Word Count – The number of 16-bit words to access, starting at Offset.

4.

Values – The 16-bit word values used in access. The values are comma separated
hex values without the 0x prefix.

5.

Access Password – The access password for the access.

6.

Kill Password – The kill password for performing a kill operation.

7.

Kill Permissions – The kill permissions for performing a kill operation.

8.

QT Controls – The QT controls for performing a QT operation.

18