User Guide

ITEMTEST VERSION 2.9.0

USER GUIDE

© 2023, Impinj, Inc. [Link]

TABLE OF CONTENTS
1 Introduction .......................................................................................................................................... 1
2 Terms .................................................................................................................................................... 1
3 Installation ............................................................................................................................................ 1
3.1 Minimum System Requirements ................................................................................................... 1
3.2 Installing ItemTest ......................................................................................................................... 2
3.3 Installation Location ...................................................................................................................... 2
3.4 Starting the ItemTest Application .................................................................................................. 2
3.5 About ItemTest .............................................................................................................................. 3
3.6 Automatic Updating ....................................................................................................................... 3
4 Navigating the User Interface ............................................................................................................. 3
5 Adding/Deleting Data Sources ........................................................................................................... 5
5.1 Using Automatic Discovery to Add a Data Source........................................................................ 5
5.2 Manually Adding a Data Source.................................................................................................... 7
Enable HTTPS .......................................................................................................................... 7
5.3 Editing a Data Source ................................................................................................................... 8
5.4 Deleting a Data Source ................................................................................................................. 9
5.5 Toggling Readers On/Off .............................................................................................................. 9
5.6 Access Device Information .......................................................................................................... 10
5.7 Configuring Data Sources ........................................................................................................... 12
5.8 Export OpenAPI Schema ............................................................................................................ 13
5.9 Unreachable Data Sources ......................................................................................................... 14
6 Data Source Configuration ............................................................................................................... 15
6.1 Configuring a Data Source for Inventory ..................................................................................... 15
The Default Inventory Preset .................................................................................................. 15
The Active Preset .................................................................................................................... 15
6.2 Inventory Configuration for LLRP Interface ................................................................................. 16
Manual Settings....................................................................................................................... 17
Gateway Antenna Settings .............................................................................................. 18
Antenna Hub Numbering ................................................................................................. 19
RF Modes ........................................................................................................................ 19
Search Modes ................................................................................................................. 21
FastID™ .......................................................................................................................... 22
Estimated Tag Population ............................................................................................... 22
Session ............................................................................................................................ 22
Report Configuration ....................................................................................................... 23
Power and Sensitivity Settings ................................................................................................ 23
GPI Configuration .................................................................................................................... 25
Gen2 Filtering .......................................................................................................................... 26
Truncated Reply ...................................................................................................................... 29
Protected Mode ....................................................................................................................... 30
Frequency Settings ................................................................................................................. 31
Low Duty Cycle ....................................................................................................................... 32
6.3 Inventory Configuration for IoT Interface .................................................................................... 33
Antenna Configuration ............................................................................................................ 33
Gen2 Filtering .......................................................................................................................... 34
GPI Configuration .................................................................................................................... 36
Tag Event Configuration ......................................................................................................... 36
Protected Mode ....................................................................................................................... 36
6.4 Location Configuration ................................................................................................................ 36
Gen2 Parameters .................................................................................................................... 37
Gen2 Filtering .......................................................................................................................... 37
Antenna Configuration ............................................................................................................ 37
Interval Configuration .............................................................................................................. 38
Placement Configuration ......................................................................................................... 38
Location Reporting .................................................................................................................. 38
Frequency Configuration ......................................................................................................... 38

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide i

 6.5 Direction Configuration ................................................................................................................ 38
Sectors .................................................................................................................................... 38
Gen2 Filtering .......................................................................................................................... 38
6.6 Data Source Diagnostics ............................................................................................................. 38
Diagnostic Data Capture ......................................................................................................... 38
GPO Testing............................................................................................................................ 38
6.7 Data Source Presets ................................................................................................................... 38
Creating a Preset .................................................................................................................... 38
Saving A Preset....................................................................................................................... 38
Deleting A Preset .................................................................................................................... 38
Resetting A Preset .................................................................................................................. 38
Exporting A Preset .................................................................................................................. 38
Importing A Preset................................................................................................................... 38
Refreshing Capabilities ........................................................................................................... 38
7 Showcases ......................................................................................................................................... 39
7.1 Inventory Showcase .................................................................................................................... 39
Inventory Overview.................................................................................................................. 40
List View .................................................................................................................................. 40
Table View ............................................................................................................................... 43
Advanced Run Scenarios ........................................................................................................ 46
Run Scenario................................................................................................................... 46
Time ................................................................................................................................ 46
Power .............................................................................................................................. 47
Configure a Margin Test .................................................................................................. 47
Margin Test Logging ....................................................................................................... 48
Configure a GPI-Triggered Run ...................................................................................... 48
Additional Features ................................................................................................................. 51
Unique Tags Plot ............................................................................................................. 51
Manual Hexa Formatting ................................................................................................. 52
Reset Tags to State A ..................................................................................................... 53
Read Rate Window ......................................................................................................... 53
Inventory Logs ......................................................................................................................... 53
7.2 Location Showcase ..................................................................................................................... 54
Location Overview ................................................................................................................... 54
Point Display Settings ............................................................................................................. 56
Computed Position Settings .................................................................................................... 57
Custom Display Settings ......................................................................................................... 58
Custom Floor Plan Settings .................................................................................................... 58
Running the Location Showcase............................................................................................. 60
Location Logs .......................................................................................................................... 62
7.3 Direction Showcase .................................................................................................................... 62
Direction Overview .................................................................................................................. 63
Metrics Area ............................................................................................................................ 63
Running the Direction Showcase ............................................................................................ 64
Direction Logs ......................................................................................................................... 66
7.4 Tag Memory Showcase .............................................................................................................. 66
Tag Memory Overview ............................................................................................................ 66
Reading Tag Memory (Step-by-Step) ..................................................................................... 70
Writing Tag Memory (Step-by-Step) ....................................................................................... 72
Tag Memory Logs ................................................................................................................... 73
8 Tags of Interest .................................................................................................................................. 73
8.1 JSON Format Example ............................................................................................................... 73
8.2 Legacy CSV Format Example ..................................................................................................... 74
8.3 Tags of Interest Window ............................................................................................................. 74
8.4 TOI Import Exceptions ................................................................................................................ 75
9 Application Settings .......................................................................................................................... 75
9.1 Update Configuration .................................................................................................................. 75
9.2 Tag Logging ................................................................................................................................ 76
10 Uninstallation Procedure .................................................................................................................. 77

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide ii

 10.1 Uninstall Impinj ItemTest ............................................................................................................. 77
11 Software License & Notices .............................................................................................................. 78
11.1 Impinj Standard License .............................................................................................................. 78

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide iii

1 INTRODUCTION
Impinj ItemTest version 2.9.0 is a simple, easy-to-use, Windows-compatible application enabling
performance evaluation of one or many Impinj readers and/or gateways. ItemTest supports a wide range
of inventory use case tests, permits basic tag memory options, and allows a user to demonstrate the
direction capabilities of Impinj gateways.
ItemTest 2 is a total replacement of ItemTest 1.x. It offers enhanced performance and improved usability
features. It is architected in a deeply modular fashion so future features can be added quickly.
This User Guide describes how to install, configure, and use ItemTest to perform basic tests and
demonstrations of Impinj RAIN RFID. It includes detailed instructions showing how to exercise each feature
(demonstrable by "Showcases") on supported Impinj readers and gateways.

2 TERMS
Technical terms in this User Guide and their definitions are listed below:
• Reader: An Impinj reader without embedded antennas.
▪ Impinj Speedway Revolution R120, R220 and R420, and Impinj R700 Readers.
• Gateway: An Impinj reader with embedded antennas.
▪ Impinj xPortal, xSpan and xArray gateways.
• Electronic Product Code (EPC)
▪ Both a unique number identifying a RAIN RFID tag and a named memory bank in which said
number is stored.
• Tag Identifier (TID)
▪ Both a unique, non-alterable number written to a tag by the tag’s manufacturer and a named
memory bank in which said number is stored.
• Tag of Interest (TOI): A RAIN RFID tag for which the electronic product code (EPC) is known prior
to it being read.
• Data Source: An Impinj reader or gateway
• Showcase: A capability demonstration built into ItemTest. There are four Showcase types:
Inventory, Location, Direction, and Tag Memory Access.
▪ SpeedwayR and R700 readers support the Inventory and Tag Memory Showcases only.
▪ xSpan gateways support all the Showcase types except Location.
▪ xArray gateways support all four Showcase types.
• Effective/Equivalent Isotropically Radiated Power (EIRP): The effective electromagnetic power
radiated by an ideal antenna emitting a spherically uniform signal strength in all directions.

3 INSTALLATION
3.1 Minimum System Requirements
ItemTest 2 requires, at a minimum, a Windows 10 machine with Microsoft .NET Framework 6.0 Desktop
Runtime installed. ItemTest requires the machine to have a minimum of 4GB of RAM to operate but will
take advantage of as much memory as is available. Long running operations and/or operations involving
hundreds or thousands of tags are likely memory intensive. For those operations 8GB or more of RAM is
strongly recommended.

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 1

3.2 Installing ItemTest
Download the latest version of ItemTest 2 from the Impinj support web site at
[Link]
• It is recommended, though not required, that you uninstall any ItemTest 1.x versions prior to
launching ItemTest 2.
Double click the downloaded [Link] file to launch the installer.
Unlike ItemTest 1.x, ItemTest 2 is an unattended install and the application will immediately start
as soon as installation completes.

3.3 Installation Location

ItemTest 2's combined installation and auto-update system use the open-source tool, Squirrel; see
[Link] One uncommon aspect of this installation tool is that the installation path of
ItemTest is not user-settable during install.
The installation path on most machines will be: C:\Users\[UserName]\AppData\Local\ItemTest with C:\
being the typical drive letter and [UserName] being the current user’s username.
If desired, you can move the ItemTest folder and its contents after installation to a more convenient place,
assuming the new destination is one where you have read and write access rights. Be aware that if you
choose to move the ItemTest folder then you need to update the shortcuts generated at install time to point
to the new path. Finally, if you change the directory, be aware that the automatic updating feature will likely
reinstall any updates to the default directory referenced above.

3.4 Starting the ItemTest Application

Use this procedure to start ItemTest from a PC running Microsoft Windows 10.
Start ItemTest. If you do not know where your ItemTest application is located, click Start (the
Windows icon in lower left of screen), and type ItemTest. Click on the application name returned.
Make sure it is in fact ItemTest 2 and not ItemTest 1.x in the event if ItemTest 1.x has not been
uninstalled.
Upon starting you will see an ItemTest splash screen. This will be visible for roughly 2 to 6 seconds.
While this is visible, ItemTest is loading all necessary libraries in the background.
Once the libraries have been completely loaded you will see this screen.

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 2

Figure 1: Initial ItemTest Screen

NOTE: Be aware that ItemTest will launch as many instances as you wish. We strongly advise you
launch only one instance to prevent any inadvertent conflicts or confusion.

3.5 About ItemTest

To get version information about ItemTest, click the word About on the left-hand side under the heading
Settings. The main view will appear with the Impinj logo. Under it will appear application version information
and a button which, when clicked, brings up this document in the operating system’s PDF viewer.

3.6 Automatic Updating

ItemTest 2 now supports automatic updating via an open-source package called Squirrel. The built-in
upgrade engine will check a secured, remote Impinj site for application updates. For additional information
about configuring the updater see Section 9.1.

4 NAVIGATING THE USER INTERFACE

The User Interface is divided into grouped areas. The numbers below correspond to the numbered
elements in the figure.

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 3

Figure 2: Navigation

Use the numbers on this figure as a reference for the listed elements.

On the far left is the SHOWCASES selector section. When you select a Showcase, registered data
sources that can be used for the chosen Showcase become enabled. Enabled for use is indicated
by color: teal if enabled, gray if not.
Immediately below the SHOWCASES section is the DATA SOURCES section. The "+" button
causes ItemTest to display an Add Data Source page in the main area.
• In ItemTest a Data Source is synonymous with an Impinj reader or gateway.
• Likewise, clicking the "x" button appearing next to a previously added data source will remove
it.
Below the data sources section is the TAGS OF INTEREST section. Here you can add or remove
tags of interest (TOI) files. When ItemTest receives tag reports from active data sources in a running
Showcase, it will apply special coloring and grouping logic to EPCs matching in enabled TOI file(s).
Below TAGS OF INTEREST is the SETTINGS region. The few settings you can change here apply
to the application itself, as opposed to configuring data sources.
To the right of the above-mentioned areas, and typically the biggest area of the UI, is the main
display panel. The main display panel will show different content based on the current context.
• If you click on a data source, the main display area will fill with data source settings you can
change.
• If you click on an item under SHOWCASES, the Showcase-specific demo will appear.
If you click on the gear icon, appearing in the upper right when a Showcase has been selected,
ItemTest displays a settings page allowing you to configure Showcase-specific settings.

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 4

5 ADDING/DELETING DATA SOURCES
The first task with a newly installed ItemTest is to add one or more readers/gateways as data sources, as
these are how ItemTest retrieves information from RFID readers. ItemTest requires at least one data source
to run a Showcase.
To add a data source, the reader/gateway must be online, reachable by ItemTest, and not already
communicating with another client.

Figure 3: Add Data Source Dialog

The “+” button immediately to the right of DATA SOURCES opens the “Add a data source” dialog. From
this dialog, ItemTest provides two options for adding a data source: Automatic Discovery and manually.

5.1 Using Automatic Discovery to Add a Data Source

Automatic Discovery uses mDNS to find and create a list of all Impinj Readers on the network, whether
they are currently running (red) or are available to connect to (green), and what firmware they are running
with as shown in the image below.

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 5

Figure 4: Add Data Source Dialog

To add a data source using Automatic Discovery:

Click the Magnifying Glass button to the right of Add a data source.
From the generated list, select a data source.
Optionally, enter a Nickname to identify the device more easily. Nicknames must be unique but
can be changed after the data source is added. To change the nickname, right-click on the data
source and click Edit Data Source. In the screen that appears, enter the new nickname, and click
Save.
Select either the Impinj LLRP Interface or Impinj IoT Device Interface. Note that the IoT Device
Interface provides some different options than the LLRP interface, and allows the user to configure
each antenna individually. See Configuring Data Sources for more information about each
interface. (Using the IoT Device Interface also requires that HTTPS be enabled, see Section 5.2.1
below.)
Click the Add Data Source button to finalize. Upon clicking, ItemTest will:
• Initiate communications with the device.
• Retrieve the device’s capabilities and use these to present and validate settings throughout the
application.
• Present an error dialog if unable to communicate with the device.
To close the list, click on the arrow button above Online Data Sources.
NOTE: Automatic Discovery requires that mDNS be enabled on your server to find available devices.
Be aware many enterprises turn off mDNS for security purposes so practicality may be limited.

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 6

5.2 Manually Adding a Data Source
To add a data source manually:

Click the "+" button to bring up the add data source page.
To enter Hostname, enter either a hostname or IP address of an Impinj reader or gateway. You
can also add a port number to the hostname. The default port for LLRP is 5084.
• Example 1: [Link]
• Example 2: [Link]
• Example 3: [Link]:80
Optionally, enter a Nickname to identify the device more easily. Nicknames must be unique but
can be changed after the data source is added. To change the nickname, right-click on the data
source and click Edit Data Source. In the screen that appears, enter the new nickname, and click
Save.
Select either the Impinj LLRP Interface or Impinj IoT Device Interface. Note that the IoT Device
Interface provides some different options than the LLRP interface. See Configuring Data Sources
for more information about each interface. (Using the IoT Device Interface also requires that HTTPS
be enabled, see Section 5.2.1 below.)
Optionally, you can configure ItemTest to use TLS Protocol when making the connection to the
reader. You can also specify which version of TLS you want to use with the default being Operating
System Default.

Figure 5: Advanced Options

Click the Add Data Source button to finalize. Upon clicking, ItemTest will:
• Initiate communications with the device
• Determine if the selected interface is what is configured on the device (IoT or LLRP) and warn
the user if it is not a match.
• Retrieve the device’s capabilities and use these to present and validate settings throughout the
application.
• Present an error dialog if unable to communicate with the device.

Enable HTTPS
In order to use the IoT interface of a reader, HTTPS must be enabled. It is enabled by default in current
and recent firmware, but should you need to configure it, the procedure, using RShell, is as follows:

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 7

 1. Open a command-line application.
2. Type ssh root@[your_reader].
3. For the password, enter impinj
4. Type the command config network https enable

NOTE: The IoT interface allows multiple simultaneous client connections, which could result in
possible conflicts.

5.3 Editing a Data Source

To edit the properties of a data source, such as hostname, nickname, or TLS protocol, right click on the
data source in the sidebar and select “Edit Data Source” from the context menu.

Figure 6: Data Source Context Menu

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 8

Figure 7: Edit Data Source

NOTE: The data source interface cannot be changed in the edit data source screen. This is due to
preset incompatibilities between the user interfaces. If you need to change the interface, you
will need to add a new data source instead.

5.4 Deleting a Data Source

To permanently delete a data source, along with all associated presets, hover over the data source you
want to delete in the sidebar and click the “x” button.

Figure 8: Delete Button

5.5 Toggling Readers On/Off

You can toggle readers on and off by clicking the toggle button next to the data source in the sidebar. Some
Showcases have requirements constraining the device types used. For example, the Direction Showcase
only works with a single xArray or xSpan. The Inventory Showcase, in contrast, supports all device types,
and all enabled devices can be run simultaneously. Because of these Showcase-specific requirements,
each Showcase has its own set of enabled readers. Therefore, depending on the data sources you have
added, you may notice the enabled data sources changing between enabled and disabled states as you
select different Showcases.
Below are different showcases with different enabled data sources.

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 9

Figure 9: Different Showcases with Different Enabled Data Sources

Inventory may have any number of enabled data sources of any type. Direction may only have one data source enabled and
the enabled reader must be an xSpan or xArray. Tag Memory may have only one data source enabled but allows any type of
reader.

5.6 Access Device Information

Once a data source has been added to ItemTest, information about the connected device can be accessed
in a variety of ways. First, you can simply hover over the data source in the sidebar. This will show
information that was determined on first connection, such as hostname, interface (REST/LLRP), model,
and region.

Figure 10: Device Information on Hover

Some dynamic information about a device can be viewed via the “Device Information” option of the data
source context menu (Figure 6). ItemTest will attempt to connect to the reader over REST (for firmware 8.0
and above) or via RShell (for firmware below 8.0), and pull dynamic information about the device to display
in the user interface.

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 10

Figure 11: Dynamic Device Information

The device information includes:

• Reader Model: Specific model name.
• Product SKU: The SKU identifier (only available on firmware 8.0 and above).
• Serial Number: A unique identification number assigned to your device.
• Firmware Version: The firmware version currently installed on the device.
• Operating Region: The geographical region where your device is configured to operate.
• Power Source: The type of power supply your device is currently using.
Information about a device is also presented on its Data Source Configuration view, at the top of the screen.

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 11

Figure 12: Device Information on Data Source Configuration View

5.7 Configuring Data Sources

To achieve optimal results, configure the data sources for the Showcase you want to run. To open the
configuration page for a reader, click on its name under DATA SOURCES. Different readers have different
capabilities. The configuration page reflects these differences. For example, only xArrays and xSpans can
be configured for the Direction Showcase so the tab will not appear when configuring other models of
readers. See Section 6 for more information on configuring data sources.

NOTE: Presets for readers using the LLRP interface are saved locally by ItemTest, and remain
available if connection to the reader is lost. For readers using the IoT interface, presets are
saved directly on the device, and will become available again once the connection is re-
established.

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 12

Figure 13: Example Configuration of an Impinj R700 – LLRP Interface

5.8 Export OpenAPI Schema

On the Data Source Configuration view for a data source using the IoT interface, you can retrieve the
OpenAPI schema from the reader and save it to a JSON file on your local computer.
Open the configuration page for a reader by clicking on its name under DATA SOURCES.
In the upper right corner of the page, click on the icon for Export OpenAPI Schema.

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 13

 Figure 14: Export OpenAPI Schema Icon

Enter the directory and file name where the file should be saved.
Click SAVE.

5.9 Unreachable Data Sources

If ItemTest is unable to establish communications with a previously added data source, its name will still
appear in the data source list, but in a disabled state (gray color). You may click on the unreachable data
source name and then click the RETRY button to attempt a re-connection.

Figure 15: Unreachable Data Source in Sidebar

“My R700” is unreachable and the toggle switch is disabled in the sidebar.

Figure 16: Unreachable Data Source Screen

The unreachable data source may also be edited by right clicking the data source from the sidebar menu
and clicking “Edit Data Source”. Here you can change the properties of the data source and re-attempt
connection in case, for example, the hostname changed.

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 14

6 DATA SOURCE CONFIGURATION
Data source configuration is a critical task in conducting effective tests and performing demonstrations. A
variety of user-selectable settings control reader and tag behaviors. ItemTest offers a wide variety of
configuration options. Once you have determined the optimal settings, they can be saved to a user-created
“Preset”. Presets save time and ensure consistent application of settings across repeated invocations of
ItemTest. ItemTest groups settings by Showcase type.

6.1 Configuring a Data Source for Inventory

When a data source is added to ItemTest, you specify which interface will be used for communication with
that reader – either LLRP or IoT. Refer to Section 5, Adding/Deleting Data Sources, for more details.
Inventory can be configured for either interface, but there are differences in what features are available,
and how they are configured.
If you are configuring for IoT, it is recommended to read through the LLRP sections to learn the technical
details, and then proceed to Section 6.3 Inventory Configuration, as most concepts are the same.
The Default Inventory Preset
ItemTest has default LLRP presets available for all reader models, and this is the starting point for creating
a custom Inventory preset for your LLRP data source. The ‘default’ preset is automatically selected and
presented on the Inventory Configuration view for the data source. You can edit the ‘default’ preset directly
or make a copy to edit. The LLRP presets you create are persisted locally with ItemTest.
R700 readers ship with a pre-configured ‘default’ preset for the IoT interface already installed on the device.
Any custom IoT presets you create will also be persisted on the device.
When an IoT data source is added to ItemTest, the pre-configured ‘default’ preset is automatically selected
and presented on the Inventory Configuration view. You can edit the data shown for the ‘default’ preset,
but when you SAVE, you will be prompted to create a new preset with your modified settings – you cannot
modify the ‘default’ preset itself. ItemTest will suggest a name you can use for the new preset, such as
“copy_of_default”. Your new preset will then be saved to the reader and become its active preset in
ItemTest.
The Active Preset
A data source may have several inventory presets configured, either in ItemTest for LLRP interface, or on
the reader for the IoT interface. The preset that will be used when you run the Inventory Showcase in
ItemTest is considered the ‘active’ preset. You can view the other presets for the reader on the Inventory
Configuration view without making them the active preset. To change which preset is active, click SAVE,
with or without any edits.
ItemTest indicates which preset is currently active by using bold font in the Preset dropdown list, as shown
in Figure 17.

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 15

Figure 17: Inventory Configuration – Active Preset Indicator

6.2 Inventory Configuration for LLRP Interface

To open the configuration page for a reader, click on its name under DATA SOURCES.
Click on the text "Inventory" appearing at the top of the main display. This brings up the settings
applicable to the Inventory mode of operation. Pay attention to the possible appearance of a scroll
bar on the right hand if the content cannot fit entirely within the current viewport.

Figure 18: Data Source Inventory Configuration – LLRP Device Interface

In the figure above there are two data sources: an R700 using the LLRP interface and an R700
using the IoT interface. Both readers, in this example, are FCC devices. The settings depicted

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 16

 throughout this document reflect FCC options. This document will note any differences when using
readers for other regions.
The tabs at the top in the example show the selected device (an R420, named speedwayr-14-03-
e0) supports just one operational/Showcase mode. That mode is Inventory.
Manual Settings

Figure 19: Data Source Inventory Configuration - Manual Settings

In the MANUAL SETTINGS section, in the Antennas box, enter a comma-separated list of
antennas to be used.
The default value is the entire list of antennas reported by the device.
The number of antennas will vary by device type.
• Clicking All on a reader model will fill the box with the number of antennas the reader reports.
• Antenna Hub(s), external antenna multiplexers available from Impinj, when added to a reader
increase the number of antennas displayed. See Figure 21.
• The maximum number of Antenna Hubs supported on an R120 is one, giving a potential total
of 8 antenna ports.
• The maximum number of Antenna Hubs supported on an R220 is two, giving a potential total
of 16 antenna ports.
• The maximum number of Antenna Hubs supported on an R420 or R700 is four, giving a
potential total of 32 antenna ports.
• xArrays, xSpans and xPortals do not support Antenna Hubs.

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 17

 • If one or more Antenna Hubs have been added to a reader, then you will see in green text the
words “Antenna Hub” above the Antennas input box. See Figure 21.
• Clicking All when an xSpan is the data source fills the box with the numbers 1-13.
• Clicking All when an xArray is the data source fills the box with the numbers 1-52.
NOTE: Additional antennas may exist on certain gateway products that are not available for
configuration in ItemTest. They can, however, be configured using an API such as LLRP or
the Octane SDK. Please consult the device's User Guide to learn more about "virtual" antenna
numbers corresponding to specific beam polarizations.
To clear the Antennas box of its contents, click the Clear button.

Gateway Antenna Settings

When configuring an xArray, clicking the “Optimized” button fills the box with an antenna list Impinj
engineers have determined provides an optimal firing order that balances coverage area against
computation time.
If using an xArray or xSpan reader, you can graphically choose antennas by clicking the Select
button. This action displays the antenna selector dialog. Below are two figures, one showing the
display for an xSpan, the other for an xArray.

Figure 20: Graphical Antenna Selector – xSpan and xArray

• For an xSpan:
▪ Click any of the 1-13 numbered check boxes to toggle the inclusion of that antenna.
▪ Click the “Sector 2” check box to toggle antennas 2, 4, 6, 8, 10, and 12.
▪ Click the “Sector 3” check box to toggle antennas 3, 5, 7, 9, 11, and 13.
▪ Click the “All” check box to toggle all the antennas.
• For an xArray:
▪ Click any of the 1-52 numbered check boxes to toggle the inclusion of that antenna.
▪ Click the “Sector 1” check box to toggle antennas 1, 2, 3, and 4.
▪ Click the “Sector 2” check box to toggle antennas 5, 13, 21, 29, 37, and 45.

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 18

 ▪ Click the “Sector 3” check box to toggle antennas 6, 14, 22, 30, 38, and 46.
▪ Click the “Sector 4” check box to toggle antennas 7, 15, 23, 31, 39, and 47.
▪ Click the “Sector 5” check box to toggle antennas 8, 16, 24, 32, 40, and 48.
▪ Click the “Sector 6” check box to toggle antennas 9, 17, 25, 33, 41, and 49.
▪ Click the “Sector 7” check box to toggle antennas 10, 18, 26, 34, 42, and 50.
▪ Click the “Sector 8” check box to toggle antennas 11, 19, 27, 35, 43, and 51.
▪ Click the “Sector 9” check box to toggle antennas 12, 20, 28, 36, 44, and 52.
▪ Click the “Ring 1” check box to toggle antennas 5, 6, 7, 8, 9, 10, 11, and 12.
▪ Click the “Ring 2” check box to toggle antennas 13, 14, 15, 16, 17, 18, 19, and 20.
▪ Click the “Ring 3” check box to toggle antennas 21, 22, 23, 24, 25, 26, 27, and 28.
▪ Click the “Ring 4” check box to toggle antennas 29, 30, 31, 32, 33, 34, 35, and 36.
▪ Click the “Ring 5” check box to toggle antennas 37, 38, 39, 40, 41, 42, 43, and 44.
▪ Click the “Ring 6” check box to toggle antennas 45, 46, 47, 48, 49, 50, 51, and 52.
▪ Click the “All” check box to toggle all the antennas.

Antenna Hub Numbering

The following graphic depicts an R700 reader with four Antenna Hubs enabled and the resulting antenna
numbers.

Figure 21: Antenna Hub Port Numbering

RF Modes
To set the RF Mode, select one of the modes from the RF Mode dropdown list. Values are:
• Mode 0 - Max Throughput
▪ High Speed 640k bps backscatter data rate
▪ Fastest possible data transfer rates between tag and reader.
▪ Use when readers are sufficiently separated so that interference between readers is low.
▪ Not supported on all devices.

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 19

 • Mode 1 - Hybrid Mode (High throughput (M=2))
▪ Hybrid 80k/160k bps
▪ Provides a relatively fast read rate when there is modest interference from other readers, but
a low likelihood of co-channel, adjacent-channel, or alternate-channel interferers.
• Mode 2 - Dense Reader (M=4)
▪ Provides an intermediate read rate when the population of readers is large, and/or readers are
relatively close to one another, and the likelihood of interference is moderate to high.
• Mode 3 - Dense Reader (M=8)
▪ Provides a low read rate (~half that of Dense Reader M=4) for extreme interference
environments and where tags are stationary or moving slowly.
• Mode 4 - Max Miller (High throughput (M=4))
▪ Provides maximum reliability and read rate when the reader population is low, and the
likelihood of interference is low to moderate.
▪ Not all regions support this mode.
• Mode 1000 – Auto Set Dense Reader
▪ The reader monitors RF interference and then automatically and continuously optimizes the
reader's configuration, selecting the appropriate RF modes for the best, most reliable
performance in environments where tags might be moving.
▪ Not supported on all devices.
• Mode 1002 – Auto Set Dense Reader Deep Scan
▪ The reader cycles between a subset of reader modes and then continuously optimizes the
reader's configuration, selecting the appropriate configuration settings for the best, most
reliable performance in environments where tags are moving little (for example, static tags).
• Mode 1003 – Auto Set Static Fast
▪ A refinement of AutoSet Dense Reader Deep Scan; targeted toward static environments where
difficult to read tags are not expected.
• Mode 1004 – Auto Set Static Dense Reader
▪ A refinement of Auto Set Dense Reader Deep Scan; targeted toward static environments (i.e.,
tags are not experiencing much movement) where difficult to read tags are expected and speed
can be sacrificed to ensure the weakest tags are read.
• Mode 1005 – Auto Set Custom - Reserved for future use.

New Modes for R700 readers

If configuring an R700 reader, new modes will appear in the RF Mode dropdown.
• Mode 100 – same as Mode 0 (only appears for FCC R700 readers)
• Mode 201 – same as Mode 0 (only appears for EU traditional band, aka EU1, and FGX readers)
• Mode 301 – same as Mode 0 (only appears for EU high power band, aka EU2)
• Mode 120 – same as Mode 1 (only appears for FCC R700 readers)
• Mode 221 – same as Mode 1 (only appears for EU traditional band, aka EU1, and FGX readers)
• Mode 322 – same as Mode 1 (only appears for EU high power band, aka EU2)
• Mode 142 – same as Mode 2 (only appears for FCC R700 readers)
• Mode 240 – same as Mode 2 (only appears for EU traditional band, aka EU1)

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 20

 • Mode 340 – same as Mode 2 (only appears for EU high power band, aka EU2)
• Mode 243 – same as Mode 2 (only appears for FGX R700 readers)
• Mode 185 – same as Mode 3 (only appears for FCC R700 readers)
• Mode 284 – same as Mode 3 (only appears for EU traditional band, aka EU1, and FGX readers)
• Mode 381 – same as Mode 3 (only appears for EU high power band, aka EU2)
• Mode 140 – same as Mode 4 (only appears for FCC R700 readers)
• Mode 341 – same as Mode 4 (only appears for EU high power band, aka EU2)
• Mode 242 – same as Mode 5 (only appears for EU traditional band, aka EU1, and FGX readers)
• Mode 1110 – same as Mode 1002 (only appears for FCC R700 readers)
• Mode 1210 – same as Mode 1002 (only appears for EU traditional band, aka EU1)
• Mode 1310 – same as Mode 1002 (only appears for EU high power band, aka EU2)
• Mode 1111 – same as Mode 1003 (only appears for FCC R700 readers)
• Mode 1211 – same as Mode 1003 (only appears for EU traditional band, aka EU1)
• Mode 1311 – same as Mode 1003 (only appears for EU high power band, aka EU2)
• Mode 1112 – same as Mode 1004 (only appears for FCC R700 readers)
• Mode 1212 – same as Mode 1004 (only appears for EU traditional band, aka EU1)
• Mode 1312 – same as Mode 1004 (only appears for EU high power band, aka EU2)

NOTE: Not all modes may be available in the dropdown. For example, Max Miller (Mode 4) is not
available for Japan device SKUs, and Mode 0 is not available on certain readers. If operating
an R700, you will need to ensure you are operating in the correct mode. Some EU countries
support high power channels (EU2), such as France, while others presently do not, such as
Germany.

Search Modes
Select the Search Mode from the Target dropdown list. Values are Impinj terms of art and are explained
below:
• Single Target:
▪ In Single Target, the reader first reads all tags in the 'A' state. After being read the tag internally
moves to the 'B' state. Depending on the Session chosen, you may or may not read the same
tags repeatedly.
▪ This mode may work best in high population, dynamic environments.
• Dual Target
▪ Instructs the device to read all tags in the ‘A’ state and once read, the tag moves to its internal
'B’ state. Once no tags reply to the 'A'-state query, the device reads all tags in the 'B' state.
Upon replying to the reader, the tag moves back again to its 'A' state. The device repeats this
process subject to any user-provided timeouts, or infinitely, if a timeout has not been provided.
▪ This mode is suggested for small population, dynamic environments.
• TagFocus™, aka Single Target w/ Suppression:
▪ Same as Single Target, but mimics Sessions 2/3 persistence times so long as the tag continues
to hear the TagFocus™ command from the device. This feature allows other, weaker tags to
be read.
▪ This search mode requires Impinj Monza 4 or newer Impinj tag integrated circuits (ICs).

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 21

 ▪ Once the tag no longer hears the device emitting the TagFocus™ command, it reverts to
Session 1 persistence times. Meaning, it will revert quickly to the ‘A’ state and be available for
another reader down to query within seconds. In practice, only about 70%-80% of moderately
sized tag populations supporting TagFocus™ will behave as intended. This is largely due to
tags sometimes missing the continual emission of TagFocus™ commands from the device.
• Single Target Reset:
▪ Reader inventories tags that are in inventory state B and resets the inventory flag to state A so
that they will respond to reader queries.
▪ This is useful for high-throughput applications when used in conjunction with Single Target and
session 2 or 3, which have relatively long decay times in the absence of RF, and unbounded
decay times when powered.
• Dual Target Select B to A:
▪ Inventories all tags in the A state and once no more tags are found in the field of view in the A
state, the reader issues a command to switch all tags from the B state back to the A state.
▪ Use this search mode for applications with large numbers of tags entering and exiting the field
randomly.

FastID™
If using tags with Impinj Monza or M700 chips, you can use Impinj’s patented FastID™ feature. FastID™
enables an Impinj tag IC to append its TID to its backscattered EPC. This is the fastest way to get both the
EPC and TID. Check the Enable Fast ID checkbox to receive the tag's EPC and internal Tag Identifier
(TID) at the same time when using tags with Impinj ICs. “Impinj Serialized TID” is an older name with the
same meaning as the official term, FastID™.
NOTE: If reading non-Impinj tags, Enable FastID will return tag TIDs but at a substantially slower rate
versus reading Impinj-based tags. This is due to the device having to issue a separate
command to read TID memory.

Estimated Tag Population

Enter an estimate of the expected number of tags in the Estimated Tag Population box.
• Set this to a power of two and choose a value relatively close to the average number of tags the
device is expected to see at any given time.
• The value must be a 16-bit positive integer.
• If there is variability in the number of tags that may be seen, always choose the lowest value in the
range. It is more efficient for the device to inventory a tag population exceeding the expected value
than it is to set the value too high.
• The default value is 32.
If using Octane Firmware 8.1 and above, there will be a Tag Population Estimation Algorithm dropdown
underneath the Estimated Tag Population textbox (for LLRP interface) or in Other Reader Settings (for
IoT interface). This feature allows Impinj devices to adapt the tag population estimate as the inventory is
being run, which allows for more accurate inventorying. It is recommended for nearly all RF environments.
The options in the dropdown are:
• Reader Default – ItemTest does not explicitly turn the feature on and defers to the device default.
• Enabled – ItemTest explicitly tells the reader to use the feature.
• Disabled – ItemTest explicitly tells the reader to not use the feature.

Session
Select a Session from the Session dropdown list. Values are:
• Session 0

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 22

 ▪ Impinj strongly recommends that you NOT use Session 0. This session is mainly for specific
types of testing that are beyond the scope of this User Guide. Unless you are well-versed in
the implications of Session 0, choosing it is likely to result in dramatically poor performance for
many use cases.
• Session 1
▪ Use when you want tags to quickly revert their inventoried state (reverts to the ‘A’ state between
0.5 and 5 seconds regardless of RF being on/off).
• Session 2
▪ An inventoried tag reverts to the ‘A’ state at least 2 seconds after RF power is off.
▪ There is no upper bound, other than technical, governing how long it takes an unenergized tag
to revert to the ‘A’ state.
• Session 3
▪ Behavior is identical to Session 2.

Report Configuration
Some of the data coming back in the reader’s tag reports is configurable. You can choose which extra
metrics should be included in the tag reports by checking the checkbox next to them. This data will show
up in the data grid of the Inventory Showcase in their own column. The configurable properties are as
follows:
• Report Phase Angle – The delta in phase angle between the forward link carrier wave and the
backscatter signal.
• Report Doppler Frequency – The delta in RF frequency between the forward link carrier wave
and the backscatter signal.
• Report XPC Words (R700 Only) – Certain RFID tags support XPC word reporting which is extra
data encoded in the EPC memory bank that contains information about the tag/tagged item. If the
tag does not support XPC word reporting, a blank entry will show up in the tag’s XPC Word column.

Power and Sensitivity Settings

• You can set the power and sensitivity for all antennas or set both for individual antennas. The
maximum permissible output power varies by region, device type, and power source (i.e., if the
reader is powered by brick, POE or POE+). To make reader-wide changes (i.e., use the same
values for all antennas), under POWER AND SENSITIVITY SETTINGS, select the RF power of
the reader from the Power (dBm) dropdown list.

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 23

Figure 22: Power Settings

▪ In certain environments, you may wish to lower power to reduce spectrum congestion, or to
reduce the read range of tags.
▪ Power levels can be set individually by clicking the INDIVIDUAL ANTENNAS drop down. All
antennas currently supported by the selected reader will appear. Here you can set power levels
by antenna, which can be useful for fine-tuning the reader in certain use cases. Remember to
use the scroll bar on the right to scroll any antennas into view that might not be visible,
especially when configuring an xArray due to its high antenna count.
▪ The maximum value you will see in the power dropdown depends on the type of device and its
source of power. You are encouraged to read the User Guide for your device to learn more
about the conditions governing the maximum power displayed. As an example, an Impinj R700
powered via a PoE+ (802.3at) source supports a higher maximum power output than one
powered via a POE (802.3af) source.
▪ The maximum radiated power varies by region. Selecting 30 dBm won’t necessarily produce
30 dBm of power as measured at the antenna port. The 30 dBm figure accounts for local radio
regulations and, in the case of gateway products, the antenna gain.
▪ For all devices, the default Power (dBm) value is 30 dBm.

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 24

Figure 23: Individual Tx Power Configuration

• To add a sensitivity filter either device-wide or per antenna, set the desired value in the Rx
Sensitivity box. Note that for devices except the Impinj R700, the most sensitive value permitted
is -80 dBm. This corresponds to ItemTest 1's "Max Sensitivity" value. For the newest device, the
Impinj R700 reader, the maximum sensitivity supported is now -90 dBm.
▪ Sensitivity per antenna is configurable and appears directly under the power entry box under
the section titled INDIVIDUAL ANTENNAS.
▪ In certain environments, you might want to reduce sensitivity to limit range without reducing
power.

GPI Configuration
ItemTest allows inventory operations to be started and stopped by GPI signals. Using ItemTest, a user can
validate proper GPI signaling prior to deploying reader and GPI-enabled triggering devices, such as photo
eyes and infrared “people detectors.”

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 25

Figure 24: GPI Triggering

Click the checkbox in the START column next to the GPI port carrying the “start” signal. Only one
GPI port can be enabled to receive the “start” signal.
Click the LEVEL dropdown immediately to the right to choose the signal level that will start the
inventory operation. Options are Low and High.
Click the checkbox in the STOP column for the GPI Port carrying the “stop” signal. This port does
not need to be the same as the start GPI port.
Just as you did for the START LEVEL, click the rightmost LEVEL dropdown to choose the signal
level that will stop the inventory operation. Options are Low and High.
You will get an error (red highlight around the GPI boxes) if you configure both the Start and Stop
to have the same level on the same GPI.
To suppress any unwanted signal bounce, enter the number of milliseconds over which to
debounce the signal by entering a value in DEBOUNCE (MS). The default is 10 milliseconds. The
maximum value is 1000 milliseconds.
In the screenshot above, the reader will start to inventory when it senses a High signal on GPI Port
#1 and will stop inventorying when receiving a Low signal on the same port.

Gen2 Filtering
For LLRP Gen2 Filtering, there are several filtering modes to select from:
• Filter 1
• Filter 2
• Filter 1 and 2
• Filter 1 or 2

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 26

 • Use Tag Select Filters
The first four convenience options allow you to configure either one or two filters, and how the filters are
combined, per GS1 “Gen2” specifications. The final option, Use Tag Select Filters, allows configuration of
a more complex set of filters (up to five), with specification of the match and non-match behaviors for each
filter.
Mode
• For the first four options, the mode indicates how many filters to use, and the logical operator
to apply between filters. Filters can be applied individually (e.g., just apply Filter 1) or combined
using Boolean AND or OR operations, with the operands being the filter values. See Figure 25.
• If you choose ‘Use Tag Select Filters’, you will be presented with inputs for up to five filters.
Use the Match Action and Non-match Action inputs to control how the filters are combined.
See Figure 26.
Filter Verification
• Filter verification enables or disables the backup hardware filtering feature, which acts as a
secondary filter for any tags that ignore the Gen2 filtering.
• Options are Enable, Disable, Passive, or Reader Default. Note that filter verification is enabled
on SpeedwayR readers by default. It is only disabled by default on the R700.
Filter (or Mask, for ‘Use Tag Select Filters’ mode)
• This is the hexadecimal string (e.g., "F71F8F22") used to Select a population of tags before
inventorying.
• Each character is a hexadecimal representation of a 4-bit nibble.
• The least significant bits of the mask can be dropped by specifying a ‘Bit Length’ that is less
than four times the number of characters in the mask. For example, if the mask is “E”, this is
represented in binary as “1110”. If the ‘Bit Length’ is 4, then all four bits will be applied.
However, if the ‘Bit Length’ is 3, then only the bits “111” will be used.
Bit Length
• Since the filter is applied bit-by-bit, the length is the number of bits represented by the filter.
For example, you would enter 16 if the filter were 4 hex characters, such as "ABCD".
• Value is initially set to 0, and then is automatically calculated for you based on the entered
Filter or Mask value.
• The value must be an integer.
• You can enter a value less than what is calculated, if you wish to use fewer bits than what is
represented by the characters in the Filter or Mask value. (See Filter section above.)

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 27

Figure 25: Gen2 Filters for LLRP – Filter 1 and 2 Mode

Figure 26: Gen2 Filters for LLRP – Use Tag Select Filters

Offset
• Offset (also referred to as ‘bit pointer’) is an offset into the selected memory bank that tells the
reader where in memory to start applying the filter/mask.
• Default value is set to 32 for EPC, which is the bit offset where the readable EPC starts in the
memory bank. For the other memory banks, you can set the offset to 0, or to a custom value.
• Must be a non-negative integer.
Memory Bank
Specifies which memory bank on the tag is of interest:
• EPC is the memory partition containing the EPC.
• TID is the memory partition containing the read-only tag identifier written by the IC
manufacturer.
• User is the memory partition containing the user memory (if applicable).
• Reserved is the memory partition containing reserved memory (if applicable).
Filter Option

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 28

 • A dropdown with just two values: ‘Match’ or ‘Don’t Match’. This is used to either select or
deselect tag populations. You are encouraged to consult GS1 Gen2 specifications for
additional clarity on these concepts.
Match Action and Non-match Action
When using Tag Select Filtering, you indicate for each filter what should be done for tags that match
a filter (Match Action), and what should be done for tags that don’t match a filter (Non-match
Action). The options are to Select, Do Nothing, or Unselect. These allow you to create
combinations of filters making use of the AND, OR and NOT concepts of Boolean logic.

Truncated Reply
• If you are using an Impinj R700, ItemTest supports configuring the reader for truncated reply. See
Figure 27. This feature is designed to work with homogeneous tag populations, where
“homogenous” means all tags have identical EPC lengths, for example, 96 bits if reading tags
encoded as SGTIN-96.
• Truncated reply is most effective with tags supporting the Gen2V2 standard.
• Truncated reply may be used to substantially increase the tag read rate by reducing the number of
bits a tag backscatters. Click the Enable checkbox to turn on truncated reply only if you are well
versed in its implications.
• There are two ways to use truncated reply:
▪ The first is when there is a known EPC prefix common to all the tags. This is the Mask. When
truncated reply is enabled and a Mask is set, the reader produces a full EPC by concatenating
the “known” prefix (i.e., the portion you set) with the partial part of the EPC backscattered by
tags. When using this method of truncated reply, Gen2 Filters are NOT permitted. Said
alternatively, the presence of a Mask prohibits Gen2 filtering.
▪ The second option is termed a “zero-length truncated reply.” Here there is no foreknowledge
about the tags’ prefixes and the user is interested in obtaining only the trailing bits of EPCs. In
this case, the reader reports only the trailing portion of the EPC. With zero-length EPC enabled,
the user may still use Gen2 Filters.
− The zero-length term refers to the Mask being empty.
• In both methods, the user must enter the expected length of the EPC, so the reader knows where
the backscatter stops. If a tag population has tags with varying lengths, do not use truncated reply!
• ItemTest supports Truncated Reply only in the Inventory Showcase, and only on R700 readers.

Figure 27: Truncated Reply Configuration

Gen2 V2 Tags Only

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 29

 • Check this box if the tags to be inventoried are all Gen2 V2 tags. Enabling this setting ensures
maximum data integrity due to an additional CRC check. See the “EPC™ Radio-Frequency
Identity Protocols Generation-2 UHF RFID Specification for RFID Air Interface Protocol for
Communications at 860 MHz – 960 MHz Version 2.0.1 Ratified” document for details.
• If this box is checked, non-Gen2 V2 tags will not be successfully decoded.
• Must be checked in order to use FastID™ with truncated reply at the same time.
▪ Impinj chips tag ICs currently supporting this setting as of May 2020 are:
− Impinj Monza R6-P
− Impinj M700
If any doubt exists about a tag population’s Gen2V2 compatibility, please do not enable.
Tag Mask (optional)
• This is the hexadecimal string (e.g., "E280") representation of the bit sequence a tag must
have in its EPC memory bank. The initial position to begin the match is determined by the Bit
Pointer.
• The end of the mask is where matching tags begin backscattering their EPC contents.
• If left empty, Gen2 Filters may be used, but if the tag mask length is non-zero, Gen2 Filters
must be disabled.
• Each character is a hexadecimal representation of a 4-bit nibble.
EPC Length (in words)
• This value must be set correctly to observe meaningful improvement in tag read rate.
• Specify the EPC length, in 16-bit words, all tags in the field of view are expected to have. Only
tags of this length can be decoded properly. Tags with EPCs that are not this length will
respond but will not be successfully decoded.
• Default value is set to 0.
• Must be an integer. Remember the EPC Length is specified in words, not bits.
Bit Pointer
• The bit pointer is the offset in EPC memory to start applying the Mask.
• The default value is set to 32 as a convenience to you because the EPC starts at bit 32 (i.e.,
start of the 3rd word) in the EPC memory bank.
• Must be a non-negative integer.

Protected Mode
ItemTest supports Protected Mode for the Impinj M700 series of tags. When in Protected Mode, tags will
not listen to or respond to any commands. They are hidden from inventory until they receive the
appropriately formatted command and correct password. The Protected Mode setting in ItemTest enables
you to access those tags so that they are included when an Inventory Showcase is run.
As shown in the figure below, you can configure Protected Mode in the settings page of your reader under
the following conditions:
• You have an R700 Reader, running either the LLRP or IoT Interface.
• You have one or more Protected Mode-compatible tags encoded with a single password.
• You know that password.
NOTE: Protected Mode requires FastID™.

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 30

Figure 28: Protected Mode in Settings – LLRP Interface

To configure Protected Mode:

Click the Read Protected Mode Tags check box.
Enter the password in the Access Password text box.
Ensure that FastID™ is enabled under Manual Settings.
The protected tags will appear in Inventory the next time Inventory Showcase is run.
NOTE: Activating Protected Mode from the main configuration page is most useful when you have
several protected tags with the same password. It allows you to temporarily remove protection
from those tags in order to read them but provides for no other interactions. To turn protected
mode on or off for a specific Protected Mode-compatible tag, see the Tag Memory Showcase
section.

Frequency Settings
• When using an FCC device ONLY, you can set Reduced Power frequencies under Frequency
Settings by choosing up to 10 of them. The reader will transmit a maximum of 10 dBm when
hopping to these frequencies. By marking frequencies as low power, you may mitigate potential
interference with some legacy 900 MHz FCC equipment. “Carving out" these channels is likely to
reduce reader performance, so you should only set these frequencies when there is provable
interference.
▪ Available only on FCC devices
▪ Defaults to "Disabled" (i.e., no channels will have lowered power)

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 31

 ▪ If any frequency channels are checked in the dropdown, the reduced power configuration will
become "Enabled"
▪ You can select a maximum of 10 frequencies with reduced power.
• When using a reader supporting fixed frequencies (e.g., EU1, EU2, JPN, GX2, etc.) you can specify
the frequencies the reader will use under Frequency Settings. By staggering the choice of
channels between adjacent readers, you can reduce the amount of interference between devices,
if desired.
• Defaults to using a single channel for fixed-frequency regions.
▪ Example: Channel 1 for China readers, Channel 3 for EU readers
• Use Specified Frequencies: if checked, the frequency channel checkboxes become enabled and
you can specify which channels to use for channel hopping. See Figure 29.

Figure 29: Use Specified Frequencies

NOTE: See the Impinj Octane LLRP guide for information about the default channel for each region.
Low Duty Cycle
Click the Low Duty Cycle Enable checkbox to enable low duty cycle mode. Low duty cycle mode allows
the device to temporarily turn off RF to reduce power consumption when tags are not in the field of view. In
low duty cycle mode, the device stops emitting RF after reading no tags for the user specified Empty Field
Timeout, in milliseconds. Then every specified Field Ping Interval milliseconds, the device emits a quick
burst of RF searching for the presence of any tag. If no tags respond to this quick search, the device
resumes its cycle of RF sleeping and periodic check-for-tags-wake-up. If any tags are found, the device
inventories all tags and only then resumes its sleep once the Empty Field Timeout passes without a tag
response.
• Low duty cycle: Empty Field Timeout (ms):
▪ This is the amount of time that must pass without seeing any tags before entering low duty
cycle mode.
▪ The value must be a positive integer.
• Low duty cycle: Field Ping Interval (ms):
▪ Once in low duty cycle mode, this is how often the reader should perform a quick check for
tags. If a tag is detected, the device will exit low duty cycle mode and run normally.
▪ The value must be a positive integer.
Click the “Save” button to apply all configuration settings to the selected device.

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 32

6.3 Inventory Configuration for IoT Interface
The IoT interface is first available with the R700 series of readers. As previously discussed, you can save
your desired configuration in a preset. For IoT, the presets are stored on the reader. They are available to
both ItemTest and any other IoT client, such as the reader’s WebUI.

Figure 30: Data Source Inventory Configuration – IoT Interface

Antenna Configuration
The IoT Inventory Configuration view (see Figure 30) allows you to configure the settings for each antenna
individually, in the ANTENNA CONFIGURATION section.
To add a new antenna, click the ADD ANTENNA button. If there are no more antennas to add, the button
is disabled and grayed out. To remove an antenna, click the REMOVE ANTENNA button.
Antenna options, except for RF Mode, can be unique to each antenna. The only exception, RF Mode, must
be the same across all antenna configurations. If you modify the RF Mode in the configuration for a specific
antenna, ItemTest will automatically adjust the value for RF Mode in all other configured antennas to be
the same.
. Configurable options for each antenna are:
• Antenna Port: ItemTest automatically assigns the next available Port when you add an Antenna.
To change this, click the Antenna Port dropdown list and select a port from the list of those
available.
• Search Mode: Select from the Search Mode dropdown list. See Search Modes in Manual Settings
for more information.
• Session: Default value is Session 2. See Sessions in Manual Settings for more information.

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 33

 • Power (dBm): Default power setting for R700 is 30 dBm. See Power and Sensitivity Settings in
Manual Settings for more information.
• RF Mode: As previously mentioned, this value must be the same for all configured antennas, and
ItemTest will adjust the values automatically to match. See RF Modes in Manual Settings for more
information.
• Tag Population: Default tag population is 32. See Estimated Tag Population in Manual Settings
for more information.
• Fast ID: Check Fast ID to get both the EPC and Tag Identifier (TID) when using tags with Impinj
ICs. See FastID™ in Manual Settings for more information.
• Rx Sensitivity: Default is -80 dBm. Rx Sensitivity allows you to reduce sensitivity without reducing
power. See Power and Sensitivity Settings in Manual Settings for more information.
• Max Sensitivity: Check Max Sensitivity to automatically set the Rx Sensitivity to the maximum
supported value for the reader.

Gen2 Filtering
Gen2 filtering for the IoT interface differs from the LLRP interface.
For readers using the IoT interface (e.g. R700), you can configure up to five filters. Click on the Add Filter
button to begin configuring the filter(s). See Figure 31 and Figure 32.

Figure 31: Gen2 Filters for IoT – No filters configured

Figure 32: Gen2 Filters for IoT – Two filters configured, with Intersection link

Filter Verification
• Filter verification enables or disables the backup hardware filtering feature, which acts as a
secondary filter for any tags that ignore the Gen2 filtering. When active, a tag filter verification

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 34

 check will be performed on-reader for each tag singulated. This prevents tags from being
reported that did not match the filter criteria, yet erroneously participated in the inventory round
because they failed to receive the filter spec broadcast in the Select command.
• Options are Enable, Disable, Passive, or Reader Default. Note that filter verification is disabled
by default on the R700 reader.
• Active filter verification is incompatible with inventory of tags in Protected Mode.
Filter Link
• When multiple filters are specified, the Filter Link indicates if included tags must match any
(Union) or all (Intersection) of the provided filters.
Mask
• This is the hexadecimal string (e.g., "F71F8F22") used to Select a population of tags before
inventorying.
• Each character is a hexadecimal representation of a 4-bit nibble.
• You can drop the least significant bits from the mask by specifying a ‘Length’ that is less than
four times the number of characters in the mask. For example, if the mask is “E”, this is
represented in binary as “1110”. If the ‘Length’ is 4, then all four bits will be applied. However,
if the ‘Length’ is 3, then only the bits “111” will be used.
Length
• Since the mask is applied bit-by-bit, the length is the number of bits represented by the mask.
For example, you would enter 16 if the mask were 4 hex characters, such as "ABCD".
• Value initially defaults to 0, and then is automatically calculated for you based on the value
entered for Mask.
• The value must be an integer.
• You can enter a value less than what is calculated, if you wish to use fewer bits than what is
represented by the characters in the ‘Mask’ value. (See Mask section above.)
Offset
• Offset (also referred to as ‘bit pointer’) is an offset into the selected memory bank that tells the
reader where in memory to start applying the mask.
• The value defaults initially to 32 for EPC, which is the bit offset where the readable EPC starts
in the memory bank. For the other memory banks, you can set the offset to 0, or to a custom
value.
• Must be a non-negative integer.
Memory Bank
Specifies which memory bank on the tag is of interest:
• EPC is the memory partition containing the EPC.
• TID is the memory partition containing the read-only tag identifier written by the IC
manufacturer.
• User is the memory partition containing the user memory (if applicable).
Filter Action
Specifies if tags matching the provided criteria should be included (Include) or excluded (Exclude)
from the set.

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 35

 GPI Configuration
GPI Configuration with the IoT interface is similar to the LLRP interface, but the debounce option is
removed, as it is not currently supported by the IoT interface. For detailed information about GPI Ports, see
GPI Configuration.

Tag Event Configuration

Tag Event Configuration for the IoT interface is used to enable XPC Word reporting, as well as to control
other information in the Tag Events.

Figure 33: Tag Event Configuration – IoT Inventory Configuration

The following items can be enabled or disabled for the tag event:
• EPC – The base64url-encoded EPC of the tag.
• EPC Hex – The hex-encoded EPC of the tag.
• XPC Hex – The hex-encoded Extended Protocol Control (XPC) word(s) reported by the tag.
XPC_W1 is delivered first, followed by XPC_W2.
• Antenna Port – The port number of the antenna.
• TID Hex – The hex-encoded TID of the tag. (Requires FastID™ to be enabled in order for TID
information to be available to report.)
• Transmit Power – The transmit power used by the reader, specified in 25 cdBm increments.
• RSSI – The peak received power of the EPC backscatter in cdBm.
• Frequency – The frequency that was used to read the tag, in kHz.
• PC Word – The PC word (16-bits) backscattered by the inventoried tag.
• Reader Last Seen Time – The UTC time at which the tag was last seen.
• Phase Angle – The phase angle in degrees of the tag that was read, accurate to two decimal
places.

Protected Mode
The Protected Mode section includes the options for configuring the reader to read tags that are in protected
mode (tags must support this). All that is needed to enable the feature is the Access Password. For detailed
information about Protected Mode and how to use it, see Protected Mode.

6.4 Location Configuration

To configure an xArray data source for location, click an xArray data source and then the Location tab as
shown in the figure below. Please note that all subsections within this section will refer to this figure.

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 36

 Figure 34: Location Configuration Screen

Gen2 Parameters
On the Location tab, select the Reader Operation mode for the Gen 2 parameters from the Mode
dropdown list. Values include:
• In the RF Mode drop down choose an appropriate mode. See Section [Link] RF Modes for
detailed information.
• In the Session drop down you can choose only 2 or 3. The reader’s location algorithm prohibits
using session 0 or 1.
• Power (dBm): this value represents the output power.
Gen2 Filtering
• See Section 6.2.4 Gen2 Filtering for detailed information.
Antenna Configuration
• In Disabled Antennas you may choose up to a maximum of 24 antenna/beams to disable. Users
may choose to disable select beams to a) better confine the read zone and/or b) optimize the time
spent on antennas/beams where tags are most likely to be present. By disabling beams that are
likely to have fewer tags, the reader does not waste time reading areas producing little data.

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 37

 Interval Configuration
• In Compute Window enter a value to control the amount of time over which the location is
computed. Fundamentally, this value is loosely related to the amount of history the algorithm uses
to calculate the position of each tag. Slow moving and stationary items typically will do better with
longer compute windows, while fast moving items should have shorter windows.
▪ Defaults to 10 seconds. This value is reasonable for tracking items at a slow walking speed.
• In Tag Age Interval enter a value to control the length of time a tag must remain un-read before
being reported as having exited.
▪ Defaults to 20 seconds.
• In Update Interval Seconds enter a value to control how often the reader emits location reports,
including diagnostics.
▪ Default is 5 seconds
Placement Configuration
• In Height (cm) enter the height of the xArray above the height where most tags will appear when
measured directly under the xArray. As an example: if tagged items are moving through on a plastic
cart that has two levels, where the bottom level is 20 cm above the ground and the top level is 90
cm above the ground, you may want to first take the mid-point ((90 + 20) ÷ 2) = 55cm. And assuming
that the xArray in this example is installed so that the bottom of it is 320cm above the ground, then
a reasonable value for Height (cm) would be 320cm - 55cm = 265cm. In other worse, the height
you enter is the distance between the xArray and where most tags are likely to be relative to the
xArray. Caution: this value is not the height of the xArray above the floor, unless the majority of
tagged items are likely to be actually at floor-level.
• For X location (cm) enter a value representing the distance on your x-axis of this xArray from
whatever you have chosen to be your origin.
• For Y location (cm) enter a value representing the distance on your y-axis of this xArray from
whatever you have chosen to be your origin.
• For Orientation (degrees) enter a value that represents the anti-clockwise degree of rotation
with respect to the 0 orientation, where the LEDs are aligned to the positive direction of the Y
Axis. Please consult the xArray User Guide for additional information for more detailed
information.
Location Reporting
• Check the box for Enable location update report if you want to receive update reports per the
interval specified above. If this box is unchecked, then the only reports you will receive and Entry
and Exit reports provided you have checked the boxes for those reports.
• Check the box for Enable location Exit report to receive Exit reports.
• Check the box for Enable location Entry reports to receive Entry reports.
• If no boxes are checked (not recommended), then you will receive no location reports
whatsoever.
Frequency Configuration
• If you are in a non-hopping region then you can choose the frequencies/channels you wish to
use. For specific information, please see Section 6.2.7.

6.5 Direction Configuration

6.6 Data Source Diagnostics

6.7 Data Source Presets

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 38

7 SHOWCASES
Showcases are demonstrations of reader use-cases that ItemTest supports. Choose a Showcase type to
test or demonstrate one or more devices. The Showcase types are: Inventory, Location, Direction, and Tag
Memory. Multiple devices can be used in certain Showcases.
Each Showcase type is aware of compatible device types and readers. Consequently, clicking on a
Showcase will dynamically toggle off data sources if there are too many, or if the data source is not
supported by the Showcase.

7.1 Inventory Showcase

Inventory is a Showcase used to discover all tags within range of selected readers and list their associated
EPC and other information such as the RSSI and reader antenna they were read with.
An example of an inventory use case is obtaining the counts of each type of tagged apparel items in a
clothing store.

Figure 41: Inventory Showcase

Ensure you have added one or more DATA SOURCES and have configured their Inventory-specific
settings. Click on the word "Inventory" in the SHOWCASES section (left hand side of the application).
At the bottom, you will see useful information at the bottom of the table:
• Run Scenario - the type of run (Continuous, Timed or Margin Test)
• Unique Tags - the count of unique EPCs
• Read Rate (reads/s) - displays the average reads/second while the Showcase is running.
To configure the Inventory Showcase, click on the gear icon in the upper right corner.

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 39

Figure 42: Gear Icon

Inventory Overview
The main area fills with the settings specific to the Inventory Showcase as shown below.

Figure 43: Inventory Visualization Settings Page

List View
Click on the List View button to display per-tag information in real-time. A running Inventory Showcase with
a list view display type is structurally similar to this:

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 40

Figure 44: List View

Once the Inventory Showcase is running in List View, the background color of each tag row will change
based on the time since the tag was last read. Recently read tags have a white background; older tags
display progressively darker backgrounds as the time since last read increases.
The following is an example of running an Inventory Report in list view:

Figure 45: Inventory List View Showcase

Descriptions of the columns:

• EPC:
▪ Each row has the EPC of the tag read.
▪ White rows indicate the tag was seen within the last second. As tags go longer without being
read, the background gradually becomes darker.

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 41

 ▪ Note that the EPC column may not be visible if all participating readers use the IoT interface,
and none of them are configured to report the EPC in the tag reads. Please refer to Section
6.3.4, Tag Event Configuration.
▪ EPCs may be displayed in either hexadecimal or base64 format.
• TID:
▪ The tag identifier (TID)
▪ Note that the TID column is only displayed if at least one of the readers participating in the
Inventory Showcase is configured to use FastID™.
▪ TIDs may be displayed in either hexadecimal or base64 format.
• Read Count:
▪ The number of times the tag has been read across all devices.
• Last Read From:
▪ Nickname or hostname of the device that most recently read the tag.
• First Seen:
▪ Time stamp of when the tag was first read.
• Last Seen:
▪ Time stamp of when the tag was last read.
• Time since last seen:
▪ The time delta since the tag was last read.
• Tag Model Information:
▪ Make and model of the reported tag, derived from the TID (requires FastID™ to be enabled).
• Last RSSI:
▪ Received Signal Strength Indicator value of the most recent read.
• RSSI Avg:
▪ The average Received Signal Strength Indicator value.
• RSSI Max:
▪ The maximum Received Signal Strength Indicator value.
• RSSI Min:
▪ The minimum Received Signal Strength Indicator value.
• Antenna:
▪ The last antenna that read the tag.
• Power:
▪ Output power of the device when the tag was read the first time. This value is useful when
performing Margin Read tests.
• Phase Angle
▪ The RF phase angle of a singulated tag during normal inventory (EPC backscatter).
• Doppler Freq
▪ Reports the Doppler shift for a singulated tag. Doppler shift is the total phase rotation across
the packet divided by the accumulation time. The value is a signed integer with units in Hz.
(Note: R700 does not support reporting of Doppler Frequency – for LLRP, there is no value in
the tag report, and for IoT a dummy value may be presented.)

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 42

 • PC Word
▪ The PC word (16-bits) backscattered by the inventoried tag.
• XPC Words
▪ The hex-encoded Extended Protocol Control (XPC) word(s) reported by the tag. XPC_W1 is
delivered first, followed by XPC_W2. Available for R700 readers only.
• CR Handle Hex
▪ Collision Resolution Handle in hex. Not available in all firmware versions.

NOTE: ItemTest supports column re-arrangement. Click a column header and drag it to another slot
in the table to rearrange. Clicking a column header performs lexical sorting.

You may also change the EPC of a tag in List View by right-clicking the tag you want to modify and selecting
“Change EPC” from the context menu. This will open a dialog where you can change the EPC. Once
changed, rerun the Inventory showcase and you should see the tag with your new EPC.

Figure 46: Change EPC Dialog

Table View
Click on Table View instead of List View to see table summaries of both TOI (Tags Of Interest) files and
strays. A "stray" tag is any tag that does not appear in a TOI file.

Figure 47: Inventory Showcase Table View Configuration Panel

If Table View is selected, you can choose to Flip rows and columns. Toggling this to the disabled position
organizes the table columns according to tag type (i.e., TOI file source or stray) and sets rows by data
source, as shown in Figure 48 and Figure 50. Toggling to the enabled position organizes table columns
according to data source and sets rows by tag type, as shown in Figure 49 and Figure 51.
When Show Totals Row is toggled on, you will see a summary footer at the bottom of the screen. In Figure
48 and Figure 49, Show Totals Row is toggled on, and you can see the presentation of the footer.
The following figures are examples of Inventory Showcases that have been run with table view set.

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 43

Figure 48: Inventory Showcase -- Table View, with enabled TOI files

Figure 49: Inventory Showcase -- Table View, with enabled TOI files, rows and columns flipped

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 44

Figure 50: Detail of Inventory Showcase -- Table View, with no TOI files

Figure 51: Detail of Inventory Showcase -- Table View, with no TOI files, rows and columns flipped

Below are descriptions of the columns and rows in the Inventory Table View examples shown above:
• Data Sources:
▪ My XSpan, My R420, My R700 LLRP, My R700 IoT: Nickname or hostname of the data
sources enabled for these example inventory runs.
▪ Total: This row (or column, if flipped) combines the information about tag reads from all data
sources enabled for the inventory run.
• Name:
▪ MyListOfTags, OtherTags, MySecondListOfTOIs: the names of enabled TOI files used in
these examples.
▪ Strays: a default category for tags found whose EPCs do not appear in any of the enabled TOI
files.
• Values:
▪ In standard Table View layout (Figure 48), for each TOI file and data source combination, the
value indicates the number of unique tags read by that data source that are found in the TOI
file. The percentage of tags in the TOI file that this represents is shown in parentheses.
▪ If the showcase is configured to flip the rows and columns (Figure 49), then the number of
unique tags for the data source / TOI file combination is shown in column Unique Tags, and
the total number of times the data source read those tags is shown in column Total Reads.
▪ For each data source, the number of unique tags read that are not found in any of the enabled
TOI files is presented under Strays.
▪ The value for Total indicates the number of unique tags read by all enabled data sources that
are found in the TOI file. The percentage of tags in the TOI file that this represents is shown
in parentheses.

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 45

Footer Summary Statistics (displayed if Show totals row is enabled in Inventory Showcase configuration,
Figure 47):
• All files - Count of all unique tags found that matched with any TOI file.
• All files % - Percent of all tags tracked in TOI files that were found in this inventory run.
• Overall Total - Count of all unique TOI tags and Strays found.

Advanced Run Scenarios

There are several scenarios available for running the Inventory Showcase.

Run Scenario

Figure 52: Inventory Run Configuration

• Continuous - Runs Forever: Select this option if you want the Inventory Showcase to run
continuously until you click the "Stop" button. This is the default scenario.
• Timed: Select this option if you want the Inventory Showcase to run for a specific amount of
time. You can do multiple automated timed runs by specifying the parameters in the TIME
group box.
• Margin Test – Sequential Runs with Increasing Power Levels: Select this option if you want
the Inventory Showcase to perform power sweeps to determine, for example, the minimum
power level required to energize the tag(s) under test.
• GPI-Triggered – A GPI Trigger Initiates the Inventory: Select GPI-Triggered if you want the
Inventory Showcase to be triggered by a GPI. GPI Triggers are configured on a per-reader
basis. You can find more information about how to configure GPI Triggers in Section 6.2.3.

Time
Here you configure timer-specific settings for Timed and Margin Test run scenarios.
• Start Delay (s)
▪ Specifies how much time to delay before starting the initial inventory run.
▪ Value in seconds. Default is 0 seconds.

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 46

 ▪ Must be a positive integer.
• On Time (s)
▪ Specifies how long, in seconds, the device should be on during each run.
▪ Value in seconds. Default is 10 seconds.
▪ Must be a positive integer.
• Off Time (s)
▪ Specifies the amount of time, in seconds, the device should be off before starting the next
run in the set.
▪ Value in seconds. Default is 0 seconds.
▪ Must be a positive integer.
• Beep On Start
▪ Select this option if you would like to hear an audible beep every time a run begins.
▪ Useful if you cannot be in front of your PC when running the test.
• Total Runs
▪ For Timed mode, enter the number of inventory tests to perform.
▪ The Total Runs option is disabled in Margin Test mode since the number of runs that will
be performed is dictated by the Start Power, End Power, and Power Step, and is calculated
automatically.

Power
If Margin Test mode has been selected, then the power settings can be specified by selecting appropriate
values from the dropdowns for the options in the POWER box.
• Start Power (dBm)
▪ Specifies the start power value to start incrementing from.
▪ Defaults to 29
• End Power (dBm)
▪ Specifies the final power value to end incrementing at.
▪ Defaults to 30
• Power Step (dBm)
▪ Specifies how much to increase the power by during each increment.
▪ Defaults to 0.25

Configure a Margin Test

A Margin Test is also referred to as a Power Sweep. This run scenario is useful for determining the
minimum power required to read a tag or group of tags.

Click the Gear icon to display the Run Configuration for the Inventory Showcase.

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 47

Figure 53: Margin Test Configuration

Select the Margin Test run scenario.

Enter the Start Power (dBm). In the example, 18 dBm is chosen.
Enter the End Power (dBm). In the example, 30 dBm is selected.
Enter the Power Step (dBm) value. The dropdown has 20 choices – 5 dB broken down into 1/4
dB increments. In the example figure the power increases in 1/2 dB steps.
Click Save to apply the settings.
NOTE: Note that margin tests can be executed using multiple devices. All device types support
running a margin test.

Margin Test Logging

ItemTest will create a log file (see Section 9.2) for each power step executed in the margin test. To
illustrate, if the start power is 15 dBm, with a power increment of 0.25 dBm, and an ending power of 18
dBm, then you would have 18 dBm – 15 dBm = 3 dBm of test range x 4 (this is the number of 0.25 dBm
steps per dBm) for a total of 12 log files.

Configure a GPI-Triggered Run

ItemTest is capable of GPI-triggered inventory runs. The purpose of this mode is to use a GPI trigger
to start and stop the device.
First, set up a preset on a GPI-capable reader to use GPI triggers -- click the Data Source, which takes
you to the settings for the data source (Figure 54). Scroll down to the GPI Configuration box on the
Inventory tab. You may need to scroll down to bring the GPI Configuration box fully into view. (GPI
configuration is also discussed in Section 6.2.3.)

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 48

Figure 54: Inventory Preset Configuration for GPI

In the Start column, check the box next to the port where a received signal should Start an
inventory.
• Specifies the type of GPI trigger that would start a run.
In the LEVEL column, use the dropdown to select the signal type for the Start.
• Low
• High
In the Stop column, check the box next to the port where a received signal should Stop an
inventory.
• Specifies the type of GPI trigger that would stop a run.
In the LEVEL column, use the dropdown to select the signal type for the Stop.
• Low
• High
Enter a value for the DEBOUNCE (MS) setting.
• After the device initially detects a transition, subsequent transitions are ignored for the set value
of milliseconds.
• Default is 10 milliseconds; 50 milliseconds is reasonable in most situations. The maximum
usable value is 1000 milliseconds.
• 0 indicates to not perform debounce.
Click the Save button to commit your changes.
NOTE: The number of GPIs exposed to the reader varies based on device type.

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 49

 Next, configure the Inventory Showcase for the GPI Triggered run scenario.
1. Ensure that only one data source having a GPI auto-start is enabled (Figure 55).

Figure 55: Data Source with GPI Trigger selected

Click on the word Inventory in the SHOWCASES section to bring up the Inventory Showcase.
Click on the gear icon to configure the Inventory Showcase for GPI Triggering, as shown below:

Figure 56: Inventory Showcase - GPI Triggered Run Scenario Settings

Under INVENTORY RUN CONFIGURATION in the RUN SCENARIO section click the GPI
Triggered – Start controlled by a GPI radio button. Select Always reset stopwatch if you’d like
the stopwatch displayed on the Inventory Showcase to be reset every time GPI Start is received.
Next click Save; if there are error conditions you will see a dialog box containing one of the warnings
below:
• If there is no data source enabled, then you see an error telling you that a data source is not
enabled (corrective action: enable a GPI-supporting data source).
• If the enabled data source does not support GPI triggering (e.g., gateway products) then you
see an error telling you that the enabled data source does not support GPI triggering (corrective
action: disable this data source and enable a different data source, one that has GPI triggering
capabilities).
• If more than one data source is enabled then you will see an error telling you that only one data
source can be enabled when using GPI triggering (corrective action: enable only one (1) data
source).
• If there is just one data source enabled but it does not have an auto start GPI configured then
you will see an error telling you that you must enable a data source with a GPI configured for
auto start (corrective action: ensure you check one of the Start boxes in the data source
configuration).

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 50

 If no error conditions exist, the settings will be saved, and you are returned to the Inventory
Showcase – click the play button ► to start the showcase. You will see the stopwatch is running,
■
and the play button displays instead of ►. The stopwatch indicates that the showcase is running
but it does NOT mean the reader is reading tags. The reader only starts reading and reporting
tags once the GPI auto start condition physically occurs.
As soon as the GPI auto start condition physically occurs (e.g., GPI 1 goes high because a light
sensor was tripped) then:
• If you enabled Always reset stopwatch in the showcase settings, the stopwatch will
instantaneously reset to 00:00:00.000 and immediately begin running afresh (you do not
have to do anything; the UI will automatically adjust the stopwatch).
• The reader starts inventorying and tag reads appear in the showcase area.
• If an auto stop GPI is configured and the condition physically occurs, the reader will stop
inventorying, but the showcase will continue running, allowing further auto start GPIs and auto
stop GPIs to occur, and tag reads to be recorded by the showcase.

To stop the GPI Triggered run, click the stop button ■, which immediately stops the showcase.

Additional Features
The Inventory Showcase configurations available in the Additional Features section of the Inventory
Visualization Settings Page (Figure 43) are highlighted in Figure 57 below. These configurations are
discussed in the following sections.

Figure 57: Inventory Showcase – Additional Features

Unique Tags Plot

When checked, a plot displaying the cumulative count of unique tags during the inventory appears at the
bottom of both List View and Table View inventory Showcases. The x-axis is time, and the y-axis is the
cumulative tag count.
The tag plot is useful for assessing the time required for enabled device(s) to read a targeted tag population.

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 51

Figure 58: Unique Tag Plot

Manual Hexa Formatting

On the Inventory Showcase List View, EPCs, TIDs and other values may be displayed in either hexadecimal
or base64 format.
Once an Inventory Run is complete and you are viewing the results, you can change the display format of
the EPC, TID and other columns by making use of the context menu.

Figure 59: Inventory Showcase – Adjusting column format for a completed run

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 52

By default, during an Inventory run, ItemTest will decide what format to use for each column based on the
interface of the readers participating in the run.
• Readers using the LLRP interface provide EPCs and TIDs in hexadecimal format.
• For readers using the IoT interface, whether EPCs, TIDs, and other data are reported in
hexadecimal or base64 can be configured in the selected preset. Please refer to Tag Event
Configuration.
• If any participating reader will report the EPC in hexadecimal, then the column in the Inventory
Showcase List View will be in hexadecimal.
• If any participating reader is configured for FastID™, and will report the TID in hexadecimal,
then the column in the Inventory Showcase List View will be in hexadecimal.

You can also choose to override the default column format in an active Inventory run by selecting Enable
Manual Hexa Formatting in the Additional Features section of Inventory Showcase Configuration (Figure
57). With this option selected, whatever format you have selected via the context menu will be applied to
the column(s) during an active inventory run.

Reset Tags to State A

When a tag in the ‘A’ state is read by a reader, the tag internally moves to the 'B' state. Depending on the
search mode (see Section [Link]) configured in the active preset on the reader, the reader may or may
not read tags in the ‘B’ state. By selecting Reset Tags to State A, you can choose to reset tags to the ‘A’
state before running the Inventory showcase. (Note that the reader(s) accomplish the resetting of tag state
by making use of the Single Target Reset search mode (see Single Target Reset in Section [Link])).
There are two options for when resetting of the tags can be performed:
• Before initial run: The tags will be reset before the start of the showcase, whether the
Continuous, Timed, Margin Test or GPI Triggered run scenario is selected.
• Before each run: The tags will be reset before each run that is executed in a multi-run scenario,
(e.g., Timed, Margin Test and GPI Triggered). (For Continuous run scenario, the result of
selecting ‘before each run’ is the same as selecting ‘before initial run’, as there is only one run.)
Reset Tags Duration (s): Here you can specify a duration in seconds for which the action of resetting tags
can be executed by the reader(s). Allowed values are from 1 to 999 seconds, with a default value of 5
seconds.

Read Rate Window

By default, the tag read rate is calculated over the entire length of the run (not including the start delay or
the off time between runs in a multi-run scenario).
Alternately, you can choose to have the tag read rate calculated over a specific amount of time preceding
the current time, by setting the value for Read Rate Window (s) in the Additional Features section of
Inventory Showcase Configuration (Figure 57) to a positive non-zero value.
For example, if the Read Rate Window is set to 30 seconds, then when the Inventory is running and more
than 30 seconds have elapsed, the read rate will be calculated using only the tag reads that have been
reported during the preceding 30 seconds.
To return to the default of calculating the read rate over the entire length of the run, set the Read Rate
Window to 0 seconds.

Inventory Logs
If logging is enabled (see Section 9.2), running an Inventory Showcase causes ItemTest to generate
Inventory log files. Each execution of an Inventory Run, including automated runs as described in Section
7.1.4 generates a csv-formatted file whose contents depend on the information being reported in the tag

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 53

reads for the various enabled readers. If any of the readers report a particular field, then a column for that
value will be included in the log file.
The header of the log file includes:
• The time and date when the run occurred.
• A line for each participating reader, containing information about the reader and the preset running
on the device.
• The final line of the header lists the titles of columns in the csv-formatted file. Some possible
columns are Timestamp, EPC, TID, Antenna, RSSI, Frequency, Hostname, PhaseAngle,
DopplerFrequency.
• Note that TIDs are logged only by those readers that have FastID™ enabled.
• GPI events will appear in the logs as non-CSV-formatted comments designated with a leading “#”.
They will appear amongst the tag reads at the time of their occurrence on dedicated lines.

Figure 60: Example of an Inventory Log File

7.2 Location Showcase

Impinj xArray gateways can track the 2-D coordinates of tagged items with an optimal resolution of 1m in
certain environments. Use cases where xArrays have been used to track location include retail, where
tagged merchandise is tracked as it moves between display cases, and tracking the location of work-in-
progress items in manufacturing facilities ranging from commercial tractors to electronic sub-assemblies.
The greater the density of xArrays in the coverage area, the more accurate the reported location. In the
following, we will show how to configure and demo both a single xArray and multiple xArray environment.
Location Overview
When an xArray is selected as the data source, and while Location is selected under SHOWCASES, the
main view will appear as shown in Figure 61.

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 54

 Figure 61: Location View (xArray only)

• The Location Visualization Toolbar just above the grid provides quick access to some, but not
all, of the visualization options for the Location Showcase. From left to right, the options are:
▪ Show/Hide Gridlines – Toggling will show/hide the gridlines. The X and Y axis will always stay
visible.
▪ Show/Hide xArrays – Toggling will show/hide the xArray icons on the plot.
▪ Enable/Disable Fullscreen – Toggling will make the grid full screen. It can be useful for
demos.
▪ Enable/Disable Keep Out Areas – ItemTest can be configured to have Keep Out Areas on
the grid which will ensure tags do not get plotted in certain areas. If a tag were to be plotted in
a Keep Out Area, it will plot to the nearest edge of the configured Keep Out Area. More details
on how to configure Keep Out Areas can be found in Section 7.2.5.
▪ Show/Hide Keep Out Areas – If you would like to use the keep out areas you have configured,
but not show them on the plot, you can hide them.
• Directly to the right of the toolbar is an indicator that reports the current position of your mouse
pointer on the grid. Default is in centimeters, but it can be changed by clicking on the grid to feet or
meters.
• More visualization options can be found by clicking the gear icon in the top right (Figure 62).

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 55

 Figure 62: Location Visualization Settings (xArray only)

Point Display Settings

• Display only computed position – When selected, the computed position of the tag will be
displayed as circles on the plot. The location is computed using reported locations provided by all
readers.
• Display all reported positions – When selected, the reported position of the tag from all readers
will be displayed as squares on the plot. There can be multiple reported positions for the same tag
if multiple xArrays saw the tag.
• Display all reported locations and computed positions – When selected, both computed and
reported positions are plotted,
• Heat Map – When selected, displays a heat map of tag reports received. Only the heat signatures
of the tags can be seen.

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 56

 Figure 63: Heat Map Example

The example above shows a single reader heat map with tags placed in a square formation and a
large group of tags in the bottom right. The persistence before decaying, radius of each point, and
intensity of the colors can be controlled and are explained below.

• Heat Map Settings:

▪ Persistence: A representation of time the heat should stay on-screen before decaying. The
value must be between 0 and 2147483647. Values closer to 0 cause decay to occur more
quickly.
▪ Radius (cm): The radius in centimeters of the heat map circle around the location of a tag. A
circle with specified radius will get hotter at the x and y location for a tag when it reports. The
value must be between 0 and 2147483647.
▪ Intensity (0-255): The Intensity reflects how “hot” a point on the heat map gets each time it is
encountered. The value must be between 0 and 255. Values closer to 255 are “hotter” (red)
while values closer to 0 are “colder” (blue) when tags appear.

Computed Position Settings

• Enable Movement Threshold (cm) – When this setting is enabled, subsequent tag locations are
not updated if they are within the specified distance (in centimeters) of the first reported location. If
a new location exceeds the threshold, a new location is reported, and subsequent reports are now
compared to this new position. The suppression of updated positions helps to visually separate
static tags, or very slow-moving tags, from those that are moving more quickly.
• Enable Smooth Movement Time (s) – When this setting is enabled, updates between subsequent
tag locations are animated over a time interval given by the specified value (in whole integer
seconds). To avoid missing any intermediate reported positions, this value should be less than or
equal to the lowest update interval for all xArrays included in the running Location showcase.

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 57

 Custom Display Settings
• Visible Gridlines – Determines whether the gridlines will show on the plot or not. Also configurable
in the Location toolbar.
• Visible Reader(s) – Determines whether the readers will show on the plot or not. Also configurable
in the Location toolbar.
• Maximize Window – Determines whether the plot will be full screen or not. Can also enter full
screen from the Location toolbar.
• Black Background – Sets the background of the plot to be black. Very useful for demoing the heat
map.
• Enable Tags of Interest Summary – Creates a tag of interest summary window at the start of a
location run that can be used to toggle the visibility of the tags from each file.

Figure 64: Location Running with Tags of Interest Summary

• Exclude Low Confidence Tags – When checked, it will apply a filter on low confidence tags that
do not meet the configured threshold. Based on the number of tag reads per cycle, the bottom X
percent will be hidden from the location plot where X is the number specified in the text box.
• Stray Tag Color – Allows you to customize the color of stray tags (tags not found in an enabled
Tags of Interest file) in the visualization. Can accept color names or hex codes. Default is gray.

Custom Floor Plan Settings

• Enable Floor Plan – When checked, will use the floor plan specified as the background image of
the Location plot. This is useful for displaying xArrays in their actual space.
• Floor Plan
▪ Specifies the file name to load into the background image of the Location plot.
▪ Images (.png, .jpg, etc.) can be used as the floor plan.

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 58

 ▪ The Floor Plan Position can be configured below the floor plan file picker. If left unconfigured,
ItemTest will use the image size unless it is greater than the screen size and then it will adjust
to fit to the screen.
• Configure Layout – You can also further configure the floor plan and add Keep Out Areas by
clicking this button. It will open a window for adjusting the floor plan and creating and placing Keep
Out Areas on the plot.

Figure 65: Configure Layout Window with Floor Plan Image and Keep Out Area

• Enable Keep Out Areas - ItemTest can be configured to have Keep Out Areas on the grid which
will ensure tags do not get plotted in certain areas. If a tag were to be plotted in a Keep Out Area,
it will plot to the nearest edge of the configured Keep Out Area. An example of how this works can
be found below in Figure 66 below.
• Show/Hide Keep Out Areas - If you would like to use the keep out areas you have configured, but
not show them on the plot, you can hide them. This is also configurable in the Location toolbar.

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 59

 Figure 66: Location Running with Multiple xArrays and Visible Keep Out Areas

Running the Location Showcase

Toggle on the xArray data sources you want to run making sure they are configured properly. For
more on configuring xArrays for Location, see Section 6.4.
Click the “Play” button – visually this is an encircled triangle on its side – in the upper left portion of
the application. This starts the selected gateways.
If tags are in the RFID field of view, they will begin to show up on the Location plot as they come
in.
• ItemTest presents the computed position of tags as a colored dot and reported position as a
colored square.
• The tag’s position is based on the X and Y reported by the xArray(s).
• The tag’s color corresponds to the color associated with the EPC if such an assignment has
been made in an enabled TOI file. If the tag is not found in an enabled TOI file and no color is
configured, it will be gray.
As tags are being plotted, you can click and drag to pan around the grid and mouse wheel up/down
to zoom in and out.
Hovering over a computed position will show the summary of the tag and will include the EPC and
all the hostnames of readers that found the tag. Hovering over a reported position will only show
the EPC and the single reader that reported that location.
Hovering over the icon for an xArray will display a summary of reported tag locations for that xArray,
including the position and orientation of the xArray, the cycle time, and the number of unique tags
and raw reads performed during that cycle time. The report is available while a Location Showcase
is running but will show the statistics for the most recent cycle for as long as the pointer hovers
over the icon. Even after a Location Showcase has stopped running, the report is available and will
show the statistics for the last reported cycle. Figure 68 shows an example summary report.

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 60

Figure 67: Location Running with 4 xArrays, a Custom Floor Plan, and an enabled TOI File

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 61

Figure 68: Example xArray Summary Report

Location Logs
Location reports can be logged to a file. See Section 9.2 for details. The data fields captured during a
Location Showcase run are:
• Hostname
• Timestamp
• HostTimestamp
• ReportType
• EPC
• LocationXCentimeter
• LocationYCentimeter
• Confidence
• Diagnostic Data (list of internal diagnostic type value pairs used for debug)

7.3 Direction Showcase

Impinj xSpan and xArray gateways natively have the ability to detect and report the direction of travel of
tags passing by. Example use cases of this feature include tracking tagged objects and employees wearing
tags in and out of secure areas, and tracking objects passing through doorways. xArray’s 2-D tag tracking
capability allows customers to track tagged medical assets passing through intersecting hallways, aka “4-
way” intersections.

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 62

 Direction Overview
When an xSpan or xArray is selected as the data source, and while Direction is selected under
SHOWCASES, the main view will appear as shown in either of the halves depicted in Figure 69.
• Note the xArray icon (right) and the number and arrangement of sectors. Only sectors 2 and 3 are
shown for xSpan (left).

Figure 69: Direction View (Left: xSpan, Right: xArray)

• xSpan As Data Source (left image above)

▪ Sector 2 is the one closest to the LED on the front of the xSpan; Sector 3 is opposite that.
There are just these two sectors with an xSpan; the two sectors are 180 degrees apart.
• xArray As Data Source (right image above)
▪ Sectors 2 (top) through 9 appear. Sector numbers increase in a clockwise manner and the
width of a sector is approximately 45 degrees.
▪ An xArray can track tags across more than two sectors, provided the sectors are not
immediately adjacent.
− This means up to four sectors can be used to track direction with an xArray.
− xArray permits tracking tags entering and exiting in V-shapes, L-shapes, and many other
patterns that result from combinations of two, three and four sectors all being observed
nearly simultaneously.
Metrics Area
• Appearing on the right side of the main window is a top row containing running totals. Just below
that is a table where information about every tag read by the gateway appears.

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 63

Figure 70: Direction Metrics

▪ Processing Tags - this number represents the number of tags currently being tracked by the
gateway. A tag is in the “processing” state from the time its Entry Report is received until the
time its Exit Report is received.
▪ Recent Exits - reports the most recent exited tags. “Recent” is defined as the last two seconds.
▪ Total Tags - the total number of tags the gateway has tracked since the Showcase started.
• Tag Table Columns
▪ TAGGED ITEM - the EPC (hyphenated every 16 bits, or every Gen2 word)
▪ ENTRY - a horizontally split cell where the top number indicates the sector associated with the
Entry Report and the bottom timestamp is the Entry Report timestamp.
▪ CURRENT - The current sector the gateway calculates the tag to be in.
▪ STATUS - a horizontally split cell showing both the status of a tag (Processing or Exited) via
an icon on the top, and the number of seconds the tag has been in the processing state.
− Gears icon = Processing status
− Door with Arrow icon = Exited status
− The status time stops upon receipt of a tag’s exit report.
▪ Clicking a column header sorts the column.
NOTE: If the tag is read again after an exit report has been generated for it, a new row appears in the
table for the tag, and its status timer will run.
Running the Direction Showcase
Toggle on an xSpan or xArray data source. (Recall that only one gateway can be selected for
direction.)
Click the “Play” button – visually this is an encircled triangle on its side – in the upper left portion of
the application. This starts the selected gateway.
A read tag will first appear in the sector in its Tag Entry Report.
• ItemTest presents the tag as a colored dot, appearing at a random place within the entry sector.
• The dot’s position is random within the sector for no other reason than to aid visualization.
• The dot’s color corresponds to the color associated with the EPC if such an assignment has
been made in an enabled TOI file.
• The dot’s color will be teal if there is no match made in a TOI file, or if no TOI file has been
enabled.
• There is a chance two or more dots could be randomly plotted on top of each other. Observe
the real-time list metrics on the right to help resolve any ambiguity in this infrequent case.

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 64

 The metrics table to the right will contain a new row with the EPC, Tag Entry Report data and the
Status column will show a gear icon (indicating “processing”) with a running timer underneath.
• The value entered in Update Interval set in the Direction Configuration of the xSpan governs
the frequency of tag update reports. Every Update Interval seconds the gateway sends a new
report containing the sector the tag is in.
NOTE: All times in the direction UI are host timestamps. Direction logs record reader timestamps. To
avoid confusion, Impinj always recommends time synching both the Impinj device and host
computer running ItemTest. See the Impinj RShell Reference Manual for device NTP
configuration.
• If the current sector has not changed, the dot corresponding to the tag will not move.
• If the current sector changes from the tag’s last reported sector, the dot replots in the current
sector and the value in the Current column likewise updates to show the current sector.

Figure 71: Example xArray

Upon determining a tag has exited – that is, the gateway is no longer reading the tag and the
algorithm has completed processing – the gateway sends an Exit Report for the tag.
• Visually, the tag will slide via animation from its current position to the word “Exit” appearing
next to the exit sector.
• If a tag exits from the sector where it is currently plotted, the tag “slides” backwards from its
current position to the word “Exit” on the same sector.
• The metrics table Exit column updates to reflect the sector on which the tag exited, and the
timestamp of the Exit report will appear underneath.
• Exited tags appear in the metrics table as a door icon. A tag’s status timer stops immediately
upon receipt of an Exit Report.

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 65

Figure 72: Example xSpan Running Direction

Direction Logs
Direction reports can be logged to a file. See Section 9.2 for details. The data fields captured during a
Direction Showcase run are:
• HostTimestamp, EPC, ReportType, FirstSeenSector, FirstSeenTimestamp, LastSeenSector,
LastSeenTimestamp, and Hostname.

7.4 Tag Memory Showcase

The Tag Memory Showcase can be used to read and write the various memory banks of a single tag. An
example use case could be writing additional identifying information to a tag user memory, such as a link
to a website about the tagged product.
Tag Memory Overview
You can access the Tag Memory Showcase in two ways:
Click on the Tag Memory Showcase
Run an Inventory job in List View, stop the job, right mouse click on any of the tags appearing in
the list, and select “Tag Memory Access” from the context menu.
The figure below demonstrates the second method:

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 66

Figure 73: Tag Memory Access Window

ItemTest allows you to read/write to the memory banks of tags whose EPC or TID is known ahead of time.

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 67

Figure 74: Tag Memory Showcase

The Tag Memory Showcase screen displays a status bar and Read and Write buttons for interacting with
a tag matching the EPC in the EPC box or the TID in the TID box, depending on which one is selected.
Only one data source can be used to perform a tag memory operation at a time. The EPC or TID can be
entered manually or pulled from the Inventory showcase using the above steps. The TID will only populate
if FastID™ is enabled, otherwise it will be empty.
NOTE: You must enter a full EPC or TID in the EPC or TID box. The reader uses this as a Select
Filter to ensure it is interacting with one and only one tag, during the Tag Memory operation.
This is done to prevent inadvertent mass-writing of tags.
The following is a list of Tag Memory operation parameters:
• Memory Bank:
▪ Select the memory bank to access.
• Word Count:
▪ Specify the number of words to read or write. The maximum word count in one operation is 32
words.
• Word Offset:
▪ Specify an offset into the selected memory bank. This moves the start location of memory
operation.
NOTE: The offset is specified in words (i.e., 16-bit words) and not bits.
• Access Password:
▪ You must provide a passcode if the memory you seek to access is locked.
• Turn on Protected Mode Button:

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 68

 ▪ Click this button to put a tag into Protected Mode. Requires a password. Currently valid for the
Impinj M700 series of tags only.
• Turn off Protected Mode Button:
▪ Click to take a tag out of Protected Mode. Requires a password. Currently valid for the Impinj
M700 series of tags only.
• Tag Memory Displays:
▪ Hexadecimal Tag Memory Display: This section (labelled Tag Memory and depicted as
boxes with “….” In them) displays the hex memory data of the tag retrieved or written by the
operation. Each box represents a word (4 hex characters, cumulatively representing 16 bits).
If performing a read operation, the boxes fill with the memory contents retrieved from the tag.
If performing a write operation, enter the information to be written to the tag in these boxes.
See the Read and Write Buttons topic below for a step-by-step tutorial.
▪ ASCII Tag Memory Display: This section (labelled ASCII) displays the ASCII representation
of the memory data. It is extended (i.e., 8-bit) ASCII. Use it to read or write human-readable
data to tags. You can edit it any time. As you type or delete a new character in this box, the
hex memory updates to stay consistent with the extended ASCII display; it also functions vice
versa.
• Status Bar:
▪ This bar displays the status of the operations. When an operation is executed, the reader
returns the result of the operation and ItemTest displays it. ItemTest translates the reader
message into a user-friendly status message so you can discern and troubleshoot any
problems that may occur. Some tag memory operations may yield results for which no
explanatory text appears.
• Read and Write Buttons:
▪ Read Button
− Click the read button to start a read operation with the selected parameters.
− Once the read operation starts, if the device does not find a tag with a matching EPC within
5 seconds, the operation times out.
− If the operation completes, the read data will appear on the memory displays and a status
message will appear indicating success.
− ItemTest disables all the components of the window until the operation either completes or
times out.
▪ Write Button
− To write to the selected tag, write the hex data inside the “….” boxes and click the write
button.
− Once the write operation starts, if the device does not find a tag with a matching EPC after
5 seconds, it will time out.
− If the operation completes, the data you typed into the boxes will remain unchanged, but
the status message will update to reflect the number of words written.
− ItemTest disables all the components of the window until the operation either completes or
times out.
− The BlockWrite feature is optimized for speed, using 32-bit block writes, and is
recommended for use with all modern tags.
NOTE: The Turn On Protected Mode and Turn Off Protected Mode buttons only appear in Tag
Memory if the tag is one of the Impinj M700 series.

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 69

 Reading Tag Memory (Step-by-Step)
By default, you will notice the selected memory bank is EPC. The memory has not been read yet
and the boxes default to “….”. This indicates an unread status of memory.

Figure 75: Tag Memory Showcase – EPC Memory Bank

Use the Memory Bank drop down to select the User Memory bank. On selection, the memory
screen will present additional textboxes. This is because, in this example, the tag we are writing to
happens to be a Monza X-8K Tag. This tag type has considerably more user memory (512 words
or 8,192 bits) than typical tags. Since an operation cannot have a word count exceeding 32 words,
a maximum of 32 textboxes will be shown on the display at any given time. (You can access the
rest of this particular tag type’s memory using the Word Offset feature and doing successive 32-
word reads).

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 70

Figure 76: Tag Memory Showcase – User Memory Bank

Notice that only one textbox is enabled. This is because the word count is set to 1. Assume we
want to read 29 words for this read operation. Select 29 in the Word Count drop down. This will
enable the first 29 “…” memory boxes. Leave the Word Offset at 0.

Figure 77: Tag Memory Showcase – Word Count

Click the Read button to begin the operation. Once the attempt to read the tag’s memory completes,
the status bar will contain a message. If a red message appears, the read failed and you should try
again. On success, you will see something like what is depicted below in green text:

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 71

Figure 78: Tag Memory Showcase – Read Success

Writing Tag Memory (Step-by-Step)

Obtain a tag with user memory:
• Make sure the user memory is not perma-locked. If perma-locked, you will not be able to alter
the memory.
• If locked, make sure you know the access password.
• In this example, we are using a Monza 4U tag and we know the access password
(“AABBCCDD” in this simple example).
Next, type “Wireless memory is cool!” into the ASCII textbox. See Figure 79. Notice that ItemTest
automatically generates the hexadecimal after each keystroke is entered. It requires 2 hexadecimal
characters to represent 1 ASCII character (recall, this is 8-bit ASCII) so every keystroke in the
ASCII textbox produces 2 hex characters in the Tag Memory boxes.
If the tag is locked and you enter no or the wrong password, when you click Write, you will receive
an error. This can be resolved, in this example, by simply entering the Access Password, which
happens to be “AABBCCDD” for this tag. Once the password is entered, click the Write button
again and you should now see a SUCCESS message in green text:

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 72

Figure 79: Tag Memory Showcase – Writing Tag Memory Success

Tag Memory Logs

Logging is not supported for Tag Memory Operations.

8 TAGS OF INTEREST
In the TAGS OF INTEREST section, ItemTest allows you to colorize and group tags using a TOI file.
ItemTest will keep statistics on the counts of tags in the TOI file if seen and apply a set color when displaying
tags in a Showcase.
To add TOIs, click on the "+" button next to the TAGS OF INTEREST section on the left side of the
application.
You are prompted to enter the path to the TOI file.
• ItemTest supports two different TOI formats: CSV (traditional format, identical to ItemTest 1
format) and JSON (new to ItemTest 2)
▪ For a CSV file, the filename is used as the name of the TOI file in the application.
▪ For a JSON file, the TOI name is taken from a dedicated field titled “Name”.

8.1 JSON Format Example

A JSON formatted TOI should be formatted as shown below:

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 73

Figure 80: Tags of Interest File Format

▪ The "Version:" field in the TOI file must be set to "1.0.0".

▪ The name can be anything you desire. It will be the name that appears in the TAGS OF
INTEREST section.
• You can use standard Windows color names. See [Link]
us/dotnet/api/[Link]?view=windowsdesktop-7.0
• You can also use hex strings in the form #XXXXXX to denote a color. The alpha channel value
is not used.
• Color strings that cannot be parsed will be ignored and ItemTest will assign the default color.

8.2 Legacy CSV Format Example

A CSV formatted file should be formatted as shown below:
▪ EPC
▪ Color=<color>
▪ Here is an example of a CSV formatted TOI file:

8.3 Tags of Interest Window

Once you have imported your TOI file(s), you can view them within ItemTest by clicking on the TOI's name
under the TAGS OF INTEREST section.

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 74

Figure 81: Tags of Interest Display Table (JSON Format)

NOTE: You can see how many total tags are currently marked as a tag of interest using the badge
next to the “Tags of Interest” header in the sidebar.

8.4 TOI Import Exceptions

NOTE: You will get an error if you attempt to load a TOI file where the "Name:" field is identical to a
previously imported TOI file. If the same EPC appears in an already enabled TOI File, you will
not be able to enable the file until disabling the other TOI file containing the duplicate EPC.
NOTE: You may assign the same color to different EPCs, if desired, though this will make it difficult
to differentiate visually the tags in a running Showcase.

9 APPLICATION SETTINGS
9.1 Update Configuration
The check for updates can be configured by following the steps below:
Click the word Updates under SETTINGS on the left side of the application.
By clicking the Check for Updates button, you can immediately determine if a new version is
available. You will need Internet connectivity so the update agent can communicate with the remote
update server. If there is an update you will be prompted to install it.
• Installing a new version will overwrite the old binaries.
• Installing a new version will preserve the existing configuration settings and any custom presets
you may have created.
Checking the Automatic Updates box and setting the interval via the Check Update Interval
dropdown enables automatic periodic update checks. You will always be prompted to install a new

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 75

 update and must manually confirm. Please note that the upgrade agent runs only at application
startup.
Click OK to install if an update has been found.
You must restart ItemTest to finish the upgrade.

9.2 Tag Logging

You can enable detailed logs by clicking on the Tag Logging text appearing under the SETTINGS section
in the left sidebar.

Figure 82: Log Tag Data

To enable logging, slide the toggle next to Log tag data to the right. The color will become teal.
Click the BROWSE button to select the directory where logs should be stored.
A user-defined Prefix is optional. If you enter a prefix, it will be added to the beginning of any file
created.
• Prefixes must not contain Windows file system reserved characters (e.g., /, ~, <, >, \*, \, etc.).
• The names of generated files are a unique combination of the prefix (if configured), date, and
timestamp.
When toggled, Generate Unique Tag Log generates a second log file whose content is a list of
the unique EPCs.
The contents of the file will vary based on the Showcase. See each Showcase section in this
document for details about the contents of logs captured during a logged Showcase.

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 76

10 UNINSTALLATION PROCEDURE
10.1 Uninstall Impinj ItemTest
In Windows 10 click the Start button.
Type "Add or remove programs".
Under Apps and Features scroll until you find ItemTest.
Click the Uninstall button underneath and follow the directions.

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 77

11 SOFTWARE LICENSE & NOTICES
ItemTest Gen2 RFID Utility
Copyright (C) 2005-2022 IMPINJ, Inc.
All Rights Reserved

11.1 Impinj Standard License

This license applies to the standard-licensed version of ItemTest.

IMPINJ, INC.
PLEASE READ THIS ITEMTEST LICENSE AGREEMENT (“AGREEMENT”) CAREFULLY BEFORE USING THE ITEMTEST
SOFTWARE AND ASSOCIATED DOCUMENTATION (“SOFTWARE,” “DOCUMENTATION,” AND COLLECTIVELY, “LICENSED
MATERIALS”).
BY USING ANY LICENSED MATERIALS, YOU ACKNOWLEDGE THAT YOU HAVE READ AND UNDERSTOOD ALL THE TERMS
AND CONDITIONS OF THIS AGREEMENT AND YOU WILL BE CONSENTING TO BE BOUND BY THEM. IF YOU DO NOT ACCEPT
THESE TERMS AND CONDITIONS, DO NOT USE THE LICENSED MATERIALS AND RETURN THE LICENSED MATERIALS
UNUSED IN THE ORIGINAL SHIPPING CONTAINER TO THE PLACE OF PURCHASE FOR A FULL REFUND IF YOU PAID A
LICENSE FEE FOR THE SOFTWARE. YOUR RIGHT TO RETURN AND REFUND EXPIRES 30 DAYS AFTER PURCHASE FROM
IMPINJ OR AN AUTHORIZED IMPINJ RESELLER AND APPLIES ONLY IF YOU ARE THE ORIGINAL END USER CUSTOMER.
The following terms govern your use and access of the Licensed Materials, except to the extent there is a separate signed agreement
between you and Impinj governing your use of the Software. To the extent of a conflict among the provisions of the foregoing
documents, the order of precedence is: (i) the signed agreement; and (ii) this Agreement.
1. License.
(a) Subject to the terms and conditions of this Agreement, Impinj, Inc. (“Impinj”), grants to you (“Licensee”) a limited, non-exclusive,
non-transferable license, without the right to sublicense: (i) to install and use one (1) copy of the Software, in object code format only,
on computer hardware for which all corresponding license fees (if any) have been paid and only in conjunction with Licensee’s proper
use of an Impinj Gen2 RFID reader, each solely in accordance with the Documentation for Licensee’s internal business purposes.
(b) The license set forth above does not include any rights to and Licensee shall not (i) reproduce (except as set forth in Section 1(c)),
modify, make error corrections, translate or create any derivative work of all or any portion of the Licensed Materials, (ii) sell, rent,
lease, loan, provide, distribute or otherwise transfer all or any portion of the Licensed Materials, (iii) reverse engineer, reverse
assemble or otherwise attempt to gain access to the source code of all or any portion of the Licensed Materials, (iv) use the Licensed
Materials for third-party training, commercial time-sharing or service bureau use, (v) remove, alter, cover or obfuscate any copyright
notices, trademark notices or other proprietary rights notices placed or embedded on or in the Licensed Materials, (vi) use any
component of the Software other than solely in conjunction with operation of the Software and Impinj Gen2 RFID reader, (vii) unbundle
any component of the Software, (viii) use any component of the Software for the development of or in conjunction with any software
application intended for resale that employs any such component, (ix) use the Licensed Materials in life support systems, human
implantation, nuclear facilities or systems or any other application where failure could lead to a loss of life or catastrophic property
damage, or (x) cause or permit any third party to do any of the foregoing.
If Licensee is a European Union resident, Licensee acknowledges that information necessary to achieve interoperability of the
Software with other programs is available upon request.
(c) Licensee may make a single copy of the Software and Documentation solely for its back-up purposes; provided that any such copy
is the exclusive property of Impinj and its suppliers and includes all copyright and other intellectual property right notices that appear
on the original.
(d) Impinj is not obligated under this Agreement to provide any updates, corrections, enhancements, modifications or bug fixes to the
Licensed Materials (“Updates”) to Licensee. If Impinj provides any Update to Licensee, such Update shall be deemed part of the
Licensed Materials and subject to the license and all other terms and conditions hereunder, unless Impinj provides other terms along
with the Update. Licensee shall have no license or right to use any Upgrade unless Licensee, at the time of acquiring any such Update,
already holds a valid license to the original Software and has paid the applicable fees for, or is otherwise authorized to use, the Update.
(e) Licensee acknowledges that the Software may contain or is provided with copyrighted software of Impinj’s suppliers as identified
in associated documentation or other printed or electronic materials ("Third Party Software") which are obtained under a license from
such suppliers. Licensee’s use of any Third Party Software shall be subject to and Licensee shall comply with the applicable restrictions
and other terms and conditions set forth in such documentation or materials.
2. Ownership. Impinj or its suppliers own and shall retain all right, title and interest (including without limitation all intellectual property
rights), in and to the Licensed Materials and any Update, whether or not made by Impinj. Licensee acknowledges that the licenses
granted under this Agreement do not provide Licensee with title to or ownership of the Licensed Materials, but only a right of limited
use under the terms and conditions of this Agreement. Except as expressly set forth in Section 1, Impinj reserves all rights and grants
Licensee no licenses of any kind hereunder. All information or feedback provided by Licensee to Impinj with respect to the Software
shall be Impinj’s property and deemed confidential information of Impinj.
3. Confidentiality. Licensee agrees that the Licensed Materials contain confidential information, including trade secrets, know-how,
and information pertaining to the technical structure or performance of the Software, that is the exclusive property of Impinj as between

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 78

Licensee and Impinj. In addition, Impinj’s confidential information includes any confidential or trade secret information related to the
Licensed Materials. During the period this Agreement is in effect and at all times thereafter, Licensee shall maintain Impinj’s
confidential information in confidence and use the same degree of care, but in no event less than reasonable care, to avoid disclosure
of Impinj’s confidential information as it uses with respect to its own confidential and proprietary information of similar type and
importance. Licensee agrees to only use Impinj’s confidential information incidentally in the customary operation of the Software.
Licensee shall not sell, license, sublicense, publish, display, distribute, disclose or otherwise make available Impinj’s confidential
information to any third party nor use such information except as authorized by this Agreement. Licensee agrees to immediately notify
Impinj of the unauthorized disclosure or use of the Licensed Materials and to assist Impinj in remedying such unauthorized use or
disclosure. It is further understood and agreed that any breach of this Section 3 or Section 1(b) is a material breach of this Agreement
and any such breach would cause irreparable harm to Impinj and its suppliers, entitling Impinj or its suppliers to injunctive relief in
addition to all other remedies available at law.
4. Disclaimer. THE LICENSED MATERIALS ARE PROVIDED “AS IS”, AND IMPINJ AND ITS SUPPLIERS MAKE NO WARRANTY,
EXPRESS, IMPLIED, STATUTORY OR OTHERWISE, WITH RESPECT TO LICENSED MATERIALS OR ANY PART THEREOF,
INCLUDING WITHOUT LIMITATION ANY IMPLIED WARRANTY OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE, NONINFRINGEMENT, OR THOSE ARISING FROM COURSE OF PERFORMANCE, DEALING, USAGE OR TRADE.
IMPINJ’S SUPPLIERS MAKE NO DIRECT WARRANTY OF ANY KIND TO LICENSEE FOR THE LICENSED MATERIALS. NEITHER
IMPINJ NOR ANY OF ITS SUPPLIERS WARRANT THAT THE LICENSED MATERIALS OR ANY PART THEREOF WILL MEET
LICENSEE’S REQUIREMENTS OR BE UNINTERRUPTED, OR ERROR-FREE, OR THAT ANY ERRORS IN THE LICENSED
MATERIALS WILL BE CORRECTED. SOME STATES/JURISDICTIONS DO NOT ALLOW THE EXCLUSION OF IMPLIED
WARRANTIES SO THE ABOVE EXCLUSIONS MAY NOT APPLY TO LICENSEE. THIS LIMITED WARRANTY GIVES LICENSEE
SPECIFIC LEGAL RIGHTS. LICENSEE MAY ALSO HAVE OTHER RIGHTS, WHICH VARY FROM STATE/JURISDICTION TO
STATE/JURISDICTION.
5. Term and Termination. This Agreement is effective until terminated. Licensee may terminate this Agreement at any time by
destroying all copies of the Software. This Agreement and all licenses granted hereunder will terminate immediately without notice
from Impinj if Licensee fails to comply with any provision of this Agreement. Upon any termination, Licensee must destroy all copies
of the Licensed Materials. Sections 1(b), 2, 3, 4, 5, 6, 7, 8 and 9 shall survive any termination of this Agreement.
6. Export. The Software is specifically subject to U.S. Export Administration Regulations. Licensee agrees to strictly comply with all
export, re-export and import restrictions and regulations of the Department of Commerce or other agency or authority of the United
States or other applicable countries, and not to transfer, or authorize the transfer of, directly or indirectly, the Software or any direct
product thereof to a prohibited country or otherwise in violation of any such restrictions or regulations. Licensee’s failure to comply
with this Section is a material breach of this Agreement. LICENSEE ACKNOWLEDGES THAT LICENSEE IS NOT A NATIONAL OF
CUBA, IRAN, IRAQ, LIBYA, NORTH KOREA, SUDAN OR SYRIA OR A PARTY LISTED IN THE U.S. TABLE OF DENIAL ORDERS
OR U.S. TREASURY DEPARTMENT LIST OF SPECIALLY DESIGNATED NATIONALS.
7. Government Restricted Rights. As defined in FAR section 2.101, DFAR section 252.227-7014(a)(1) and DFAR section 252.227-
7014(a)(5) or otherwise, the Software provided in connection with this Agreement are “commercial items,” “commercial computer
software” and/or “commercial computer software documentation.” Consistent with DFAR section 227.7202, FAR section 12.212 and
other sections, any use, modification, reproduction, release, performance, display, disclosure or distribution thereof by or for the U.S.
Government shall be governed solely by the terms of this Agreement and shall be prohibited except to the extent expressly permitted
by the terms of this Agreement. Any technical data provided that is not covered by the above provisions shall be deemed “technical
data-commercial items” pursuant to DFAR section 227.7015(a). Any use, modification, reproduction, release, performance, display or
disclosure of such technical data shall be governed by the terms of DFAR section 227.7015(b).
8. Limitation of Liability. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT SHALL IMPINJ OR ITS
SUPPLIERS BE LIABLE FOR THE COST OF PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES, LOSS OF PROFITS,
OR FOR ANY SPECIAL, CONSEQUENTIAL, INCIDENTAL, PUNITIVE OR INDIRECT DAMAGES (OR DIRECT DAMAGES IN THE
CASE OF IMPINJ’S SUPPLIERS) ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, TORT (INCLUDING WITHOUT
LIMITATION NEGLIGENCE), STRICT LIABILITY OR OTHERWISE ARISING OUT OF OR UNDER THIS AGREEMENT OR ANY
USE OR INABILITY TO USE THE LICENSED MATERIALS, OR FOR BREACH OF THIS AGREEMENT. IMPINJ’S TOTAL LIABILITY
ARISING OUT OF OR UNDER THIS AGREEMENT, OR USE OR INABILITY TO USE THE LICENSED MATERIALS, OR FOR
BREACH OF THIS AGREEMENT, WHETHER IN CONTRACT, TORT (INCLUDING WITHOUT LIMITATION NEGLIGENCE), STRICT
LIABILITY OR OTHERWISE, SHALL NOT EXCEED THE GREATER OF THE PRICE PAID FOR THE SOFTWARE (IF ANY) OR TEN
U.S. DOLLARS (US$10.00). THE LIMITATIONS SET FORTH IN THIS SECTION SHALL APPLY EVEN IF IMPINJ AND/OR ITS
SUPPLIERS ARE ADVISED OF THE POSSIBILITY OF SUCH DAMAGE, AND NOTWITHSTANDING THE FAILURE OF ESSENTIAL
PURPOSE OF ANY LIMITED REMEDY.
9. General. This Agreement is governed and interpreted in accordance with the laws of the State of Washington, U.S.A. without
reference to conflicts of laws principles and excluding the United Nations Convention on Contracts for the Sale of Goods. The parties
consent to the exclusive jurisdiction of, and venue in, King County, Washington, U.S.A. Licensee shall not transfer, assign or delegate
this Agreement or any rights or obligations hereunder, whether voluntarily, by operation of law or otherwise, without the prior written
consent of Impinj. Subject to the foregoing, the terms and conditions of this Agreement shall be binding upon and inure to the benefit
of the parties to it and their respective heirs, successors, assigns and legal representatives. This Agreement constitutes the entire
agreement between Impinj and Licensee with respect to the subject matter hereof, and merges all prior negotiations and drafts of the
parties with regard thereto. No modification of or amendment to this Agreement, nor any waiver of any rights under this Agreement,
by Impinj shall be effective unless in writing. If any of the provisions of this Agreement is held by a court of competent jurisdiction to
be invalid or unenforceable under any applicable statute or rule of law, such provision shall, to that extent, be deemed omitted.

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 79

Copyright © 2023, Impinj, Inc. All rights reserved.

Impinj gives no representation or warranty, express or implied, for accuracy or reliability of information in this document. Impinj
reserves the right to change its products and services and this information at any time without notice.
EXCEPT AS PROVIDED IN IMPINJ’S TERMS AND CONDITIONS OF SALE (OR AS OTHERWISE AGREED IN A VALID WRITTEN
INDIVIDUAL AGREEMENTWITH IMPINJ), IMPINJ ASSUMES NO LIABILITY WHATSOEVER AND IMPINJ DISCLAIMS ANY
EXPRESS OR IMPLIEDWARRANTY, RELATED TO SALE AND/OR USE OF IMPINJ PRODUCTS INCLUDING LIABILITY OR
WARRANTIES RELATING TO FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT.
NO LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO ANY PATENT, COPYRIGHT, MASKWORK RIGHT,
OR OTHER INTELLECTUALPROPERTY RIGHT IS GRANTED BY THIS DOCUMENT.
Impinj assumes no liability for applications assistance or customer product design. Customers should provide adequate design and
operating safeguards to minimize risks.
Impinj products are not designed, warranted or authorized for use in any product or application where a malfunction may reasonably
be expected to cause personal injury or death, or property or environmental damage (“hazardous uses”), including but not limited to
military applications; life-support systems; aircraft control, navigation or communication; air-traffic management; or in the design,
construction, operation, or maintenance of a nuclear facility. Customers must indemnify Impinj against any damages arising out of the
use of Impinj products in any hazardous uses

Impinj, and Impinj products and features are trademarks or registered trademarks of Impinj, Inc. For a complete list of Impinj
Trademarks, visit [Link]/trademarks. All other product or service names may be trademarks of their respective companies.

The products referenced in this document may be covered by one or more U.S. patents. See [Link]/patents for details.

© 2023, Impinj, Inc. ItemTest Version 2.9.0: User Guide 80